Special command processing

$J commands cannot be issued from NJE, RJE, internal reader, or the JES2 initialization stream; they are restricted to the SVC34 subsystem interface (SSI) and as automatic commands. However, you can issue a $J command as the object of a $VS command, typically used to enter MVS™ system commands through JES2.

Because of the critical nature assigned to $J commands, JES2:
  • Does not restrict several limits set by the CONDEF initialization statement as follows:
    • CMDNUM= the number queued commands
    • DISPMAX= the output produced by the command
    • RDIRAREA= the default out-of-line area
  • Does not support the use of the semicolon (;) as a command separator. Only one $J command is allowed for each SVC 34 request
  • Ignores spaces and comments (/* comment */) as in typical processing
  • Support L= is supported to direct responses to out-of-line area of a specific console, although RDIRAREA= is ignored
  • Calls RACF® for all commands, similar to other JES2 commands noting that the first qualifier is determined by the monitor address space name. For example, jesxMON.action.object where jesx is the monitored subsystem name
Parent topic: Controlling the JES2 health monitor