Testing Your Initialization Stream

You use the JES3 initialization stream checker utility to test your JES3 initialization statements before you perform a hot start with refresh, warm, or cold start of JES3. The initialization stream checker detects most syntax errors and some logical errors in the initialization stream. You can run this utility as a batch job or as a TSO job using a command list (CLIST).

You must perform two steps to use the initialization stream checker:
  1. Step 1 gathers data for the initialization stream checker.
  2. Step 2 runs the initialization stream checker.

Step 1 obtains hardware configuration data that the initialization stream checker uses to detect logical errors in the DEVICE, HWSNAME, RJPLINE, and SETNAME initialization statements. If you omit this step, the initialization stream checker performs only syntax checking. The following topics contain sample JCL for obtaining configuration data.

Step 2 runs the initialization stream checker. The initialization stream checker examines all initialization statements for correct syntax, except the DYNALLOC statements, and creates the JES3 intermediate initialization tables.

The initialization stream checker detects logical errors in the DEVICE, HWSNAME, RJPLINE, and SETNAME statements by comparing the JES3 initialization data with the configuration data that you obtain in step 1. The initialization stream checker can detect the following types of logical errors:
  • Subgeneric splits; for example, devices defined to JES3 as belonging to one subgeneric group and defined to MVS™ as belonging to a different subgeneric group. See Grouping I/O devices for information about defining subgeneric groups.
  • Writer burster-trimmer-stacker mismatches for the 3800 printer.
  • Missing or incorrect parameters required to define hardware.