Adding comments to commands

You can add comments to JES2 commands to explain the intended action. This option often aids in later problem diagnosis. (All JES2 commands are recorded in OPERLOG.) The rules for coding comments are:

Delimiters
Use the beginning delimiter ( /* ) and the ending delimiter ( */ ). They cannot be interchanged. See the following example. If you omit the beginning delimiter, JES2 includes the comment text as part of the command. If you omit the ending delimiter, JES2 fails the command and issues the $HASP649 INVALID COMMAND message.
$t a,t=11.15,'$slne4'/* at 11:15 AM START LINE 4 AUTOMATICALLY */
Note: The JES2 command processor deletes all comments, just as it deletes blanks. If you need to retain comments, enclose the comment within apostrophes. In the following example, JES2 retains the first comment, AUTO START, but deletes the second comment, AT 11:15 AM START LINE 4 AUTOMATICALLY.
$t a,t=11.15,'$slne4/*AUTO START*/' /* AT 11:15 AM START LINE 4 AUTOMATICALLY */
If you enter a command with a comment and omit the comment delimiters, the command fails because JES2 compresses the command and deletes all the blanks. For example:
$h j123 INVALID COMMAND WITHOUT COMMENT DELIMITERS
This command is not valid. JES2 issues a message because 123INVALID is not a valid job identifier.
Placement
Place comments anywhere within a command. For example:
$d/*SAME */ spl/*COMMAND*/,v/*AS*/=spo/*THE ONE*/ol12,/*BELOW* $d spl,v=spool12 /* SAME COMMAND AS THE ONE ABOVE */
Because JES2 deletes all blanks and comments within commands, both examples of the display spool command shown above are equivalent to $DSPL,V=SPOOL12.