Starting the NetView Program before JES
JES can be started at the same time as the NetView® program or delayed until NetView automation is active. The advantage of the second approach is that JES messages that occur during initialization can be captured with the automation table, allowing you to detect what was running on the system at the time of failure during JES start-up. Such information can help you decide if the initialization process should continue normally or if some recovery is required; it might become a vital part of your recovery during the initialization process.
If you decide to start the NetView program
before JES, special setup is required. The setup includes:
- The NetView procedure
must be started with the START command using the SUB=MSTR operand.
For example, if you are using the sample procedures that are included with the NetView program, the following statement should be added as the last statement of the COMMNDxx member of SYS1.PARMLIB:
The first statement starts the NetView subsystem address space. The second statement starts the NetView application. It does not matter which statement you put first.S CNMPSSI,SUB=MSTR S CNMPROC,SUB=MSTR - The NetView procedure must be stored in the SYS1.PROCLIB, not in a user library supported by JES.
- The NetView procedure
must contain only a single job step. Note: You can circumvent the single-job-step restriction if you:
- Write a user-written driver that invokes the programs from each step via the MVS™ LINK macro interface.
- Combine the DD statements from each step into a single group.
- Specify your program on the EXEC statement for the job.
- All data sets must be referenced by
VOL=SERor be cataloged in the master catalog. - No SYSIN, SYSOUT or VIO data set can be referenced.
- The NOSTART parameter must be coded on the JES statement in the IEFSSNxx member of SYS1.PARMLIB to delay the start of JES until the NetView program is active.
- The JES statement must be coded before the NETVIEW statement in the IEFSSNxx member of SYS1.PARMLIB.
- If you start your NetView program
with
SUB=MSTR, the JES job log is allocated by default when the DSIRQJOB task requests a job ID for the NetView job. If you do not want the JES job log, you can change the JES job log constant in DSICTMOD. - After DSIRQJOB receives a job ID from JES, if JES ends abnormally or stops without notifying DSIRQJOB to release the job ID, DSIRQJOB and the NetView program cannot be stopped before JES becomes active again. If JES ends abnormally or is stopped by a user from the command line, the user can use the NetView MVS Command Revision to circumvent this. For details about implementing this circumvention, see the information about starting the NetView program before JES in IBM Z® NetView Installation: Getting Started.