Parameters

GLOBMPF=

Specifies whether messages that are routed to the global processor should be presented to the Message Processing Facility (MPF) on the global processor.

YES: Specifies that messages routed to the global processor should be presented to MPF on the global.
NO: Specifies that messages routed to the global should not be presented to MPF on the global. If NO is specified, then MPF processing must be performed on the system that a message originates from.

Messages that originate from the global processor are eligible for MPF on the global regardless of the GLOBMPF value.

The GLOBMPF option does not influence the routing of messages to the global processor. Installations wishing to use the GLOBMPF option must ensure that routing mechanisms are in place to direct the proper set of messages to the global. This could include the activation of DLOG which will result in the hardcopy message set being presented to the global, the definition of a physical console or extended MCS console on the global which receives the proper set of routing codes (or all routing codes), or the marking of target messages with the 'AUTO' attribute together with an extended console on the global receiving 'AUTO' messages.

When using the GLOBMPF function, remember that MPF processing may have to be adjusted as part of a DSI. Ensure that the MPF options on the old and new global are set up correctly. The SET MPF operator command can be used to change the MPF options for a particular system.

SYN=

Specifies a set of prefixes (or synonyms) to be used as SYSTEM scoped command prefixes. A command entered with a SYSTEM scoped prefix will execute on the system on which the command is entered.

Up to six SYSTEM scoped prefixes may be defined. Each prefix must be one to eight characters in length and must contain characters in the range of X'41' to X'FE'. Prefixes cannot be supersets or subsets of existing SYSTEM or SYSPLEX scoped prefixes. A list of prefixes already in use can be displayed by issuing the DISPLAY OPDATA command.

Prefixes that consist of all numerics are NOT allowed, they will be rejected during initialization. Do not use a prefix that is a command, an abbreviation of a command, or a command invocation. Any character specified or assumed for this parameter must not be specified for the EDIT parameter.

If you define a prefix using this parameter, all prefixes ,including the default character (8), must be specified. You must explicitly define the default character (8) if you want to continue to use it as a SYSTEM scoped command prefix.

If a prefix is specified on both the SYN= and PLEXSYN= parameter, the prefix will be defined as a SYSTEM scoped (SYN=) prefix only.

The prefix (8) is not included in the response to the DISPLAY OPDATA command because it is not registered thru CPF.

PLEXSYN=

Specifies a set of prefixes (or synonyms) to be used as SYSPLEX scoped command prefixes. A command entered with a SYSPLEX scoped prefix, from any system in the SYSPLEX, will execute on the global processor.

Up to six SYSPLEX scoped prefixes may be defined. Each prefix must be one to eight characters in length and must contain characters in the range of X'41' to X'FE'. Prefixes cannot be supersets or subsets of existing SYSTEM or SYSPLEX scoped prefixes. A list of prefixes already in use can be displayed by issuing the DISPLAY OPDATA command.

If the default prefix character (*) is not explicitly specified using this parameter, it will be automatically added by JES3. When other prefixes are specified, inclusion of the (*) is recommended for clarity.

If a prefix is specified on both the SYN= and PLEXSYN= parameter, the prefix will be defined as a SYSTEM scoped (SYN=) prefix only.

If JES3 is unable to define (*) as a SYSPLEX prefix, the (*) will be used by JES3 as a SYSTEM scoped prefix.

If you specify an invalid subparameter, JES3 uses the parameter default (*).

CIFSS=

Specifies how the installation wants messages issued within a CI/FSS address space to be routed. They can be routed to a single JES3 destination class or individually for each message.

FSSDEF: Specifies that CI/FSS messages are to be routed to the JES3 destination class specified on the MSGDEST parameter of the FSSDEF initialization statement that defines the CI/FSS to JES3. FSSDEF is the default.
MSGROUTE: Specifies that CI/FSS messages are to be routed according to JES3 message processing for each individual message (such as the MSGROUTE statement), rather than the FSSDEF statement.

DLOG=

Specifies whether JES3 or MVS™ is to maintain the hardcopy log for the sysplex. When JES3 maintains the hardcopy log, it is DLOG. When MVS maintains the hardcopy log, it is SYSLOG or OPERLOG.

ON

Specifies that you want JES3 to write a system log for the sysplex to a spool data set for subsequent processing by output service. The log is written in JES3 format from the global processor.

Note: JES3 systems using DLOG require a value higher than the default for the LOGLIM parameter in the CONSOLxx parmlib member to prevent write-to-log (WTL) buffer shortages and SYSLOG constraints. IBM® recommends setting the LOGLIM value equal to or greater than:

LOGLIM = 4,000 + (2,000 x n )

n is the number of JES3 local processors at your installation.

If necessary, see z/OS MVS Initialization and Tuning Reference for more information about the LOGLIM parameter in CONSOLxx.

OFF

Specifies that JES3 is not to maintain the system log for the sysplex. In this case, the hardcopy log will be written to OPERLOG or SYSLOG as specified in the CONSOLxx HARDCOPY statement for each system.