When the options are specified on the JCL procedure (on the EXEC statement) or by specifying the PARM= parameter on the MVS START command, JES2 suppresses the $HASP426 (SPECIFY OPTIONS) message and completes initialization without operator intervention unless CONSOLE control statements have been added to the JES2 initialization data set or an initialization statement is in error. z/OS MVS JCL Reference gives the rules about using the MVS START command. These rules govern the use of the PARM= parameter on the EXEC JCL statement and apply to how you specify JES2 start options with a JCL procedure. The examples below illustrate both correct and incorrect use of these rules in starting JES2:

S JES2,PARM=(FORMAT,SPOOL=VALIDATE)   ...  is incorrect.
S JES2,PARM=(FORMAT,'SPOOL=VALIDATE') ...  is correct.
S JES2,PARM='FORMAT,SPOOL=VALIDATE'   ...  is correct.
S JES2,PARM=(FORMAT,SPOOL='VALIDATE') ...  is incorrect.

When the options are specified (from the JCL procedure or on the MVS START command), JES2 does some initial verification, and then issues the $HASP493 message indicating that initialization has started. After it has accepted the options, JES2 reads the specified initialization data set. Message $HASP492 indicates that initialization is complete. JES2 is then ready to start processing jobs. If the NOREQ options is specified, JES2 automatically starts processing. Otherwise, you will receive the following messages:

$HASP400 ENTER REQUESTS

This message requests the operator to use the $S command to start JES2 processing. JES2 issues the $HASP492 message to indicate whether initialization was performed for all members of the MAS configuration or only for the member indicated by memname (the member name). $HASP492 also indicates the type of start performed to start member activity.