Specifying JES2 command and message prefixes

The CONCHAR= parameter on the CONDEF initialization statement specifies the prefix:
  • For all JES2-issued messages
  • By which JES2 identifies commands destined for the particular member of a multi-access spool (MAS).
Normally, JES2-initiated messages are tagged with a “$” at the beginning of the text.However, the “$” character is taken from the value of CONCHAR=; therefore, a different specification of this value for each member allows the origin of the message to be uniquely identified.

You can determine whether the CONCHAR= value applies only to the MVS system on which the JES2 member is running, or to all MVS systems in the sysplex through the SCOPE= parameter on the CONDEF initialization statement.

If you specify CONDEF ...,SCOPE=SYSTEM...., the CONCHAR value is recognized on this MVS system alone. In order to issue a JES2 command that is to take effect on a specific JES2 member, an installation would have to direct the command to that system through one of the following:
  • The MVS ROUTE command

    or

  • A sysplex-scope command prefix (such as the system name, if the installation uses IEECMDPF SAMPLIB member).

If each member of a MAS specifies CONDEF ...,SCOPE=SYSTEM,...., and the same value for the CONCHAR= parameter, then a ROUTE *ALL command can be used to make global changes to parameters on all members in that MAS. Because the MVS ROUTE *ALL command provides a single-system image for all JES2 members and MVS systems in the sysplex, the SCOPE=SYSTEM specification would be more valuable for a large MAS. However, with a single console displaying output from multiple MVS and JES2 images, it might be difficult to determine which member issued a message.

To identify the member that originated a command or message, you would have to notice the MVS system ID (SYS1) on each console display in response to a command: 
SYS1        $d condef
               $HASP830 CONDEF 942
     $HASP830 CONDEF  AUTOCMD=20,CONCHAR=$,BUFNUM=200,CMDNUM=100,
     $HASP830         BUFFREE=200,BUFWARN=80,MASMSG=200,RDIRAREA=Z,
     $HASP830         RDRCHAR=$,SCOPE=SYSTEM,DISPLEN=64,DISPMAX=100

If you specify CONDEF ...,SCOPE=SYSPLEX.... on each member of a MAS, the CONCHAR= value is recognized as belonging to this JES2 member, no matter on which MVS system in the sysplex the command entered. The SCOPE=SYSPLEX specification might be valuable for a smaller MAS, where the CONCHAR value for each member can be remembered easily. Note that the JES2 limit of 22 CONCHAR= values indicates that a MAS of more than 22 members could not use this scheme.

If you use this method, you cannot enter the MVS ROUTE *ALL command to send messages to each member. SCOPE=SYSPLEX implies that JES2 still provides a multisystem image to installations.