During JES2 initialization, two kinds of errors can occur. The first can occur when JES2 cannot open the data set containing the initialization statements. This happens, for instance, when a DD statement is named in the HASPPARM=ddname start option, but the named DD statement is not defined in the JES procedure. JES2 acknowledges the error with the following messages:

    $HASP450 OPEN FAILED FOR JES2 PARAMETER LIBRARY
    $HASP441 REPLY Y TO CONTINUE INITIALIZATION OR N TO TERMINATE

The second message allows the operator to restart initialization processing with a correctly defined data set.

The second error can occur when JES2 encounters an error in the statements in the initialization data set. Initially, JES2 goes into CONSOLE mode, and the operator is informed of the statement in error. Also, JES2 flags each statement in error and reads the next one in the data set. If the data set is printed out, each statement that was in error will have an error message ($HASP467) printed beside it. (See Specifying the Start Options for a description of the LIST option and Figure 1 for an example of these diagnostic messages.) The text of the $HASP267 diagnostic messages and an explanation of each is listed in z/OS JES2 Messages.

If any errors were encountered (when not in console mode) after all parameter statements have been read, JES2 issues the following messages:

    $HASP451  ERROR ON JES2 PARAMETER LIBRARY
    $HASP441  REPLY Y TO CONTINUE INITIALIZATION OR N TO TERMINATE

The operator's reply should be based on a careful examination of the initialization statement. If the reply is N, JES2 issues the following message:

    $HASP428 CORRECT THE ABOVE PROBLEMS AND RESTART JES2