Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Output data set groups z/OS JES2 Initialization and Tuning Guide SA32-0991-00 |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
An output group can point to a data set group that defines data sets that have identical characteristics and contain the output of a job, a started task, or a time-sharing user. Each data set group is a processing entity with a set of processing characteristics. JES2 groups output for jobs processed at the local node use the
following processing characteristics:
You can use the OUTPUT JCL statement to describe these characteristics. Note that the SYSOUT DD statement and the /* OUTPUT JECL statement support all these characteristics except GROUPID and OUTDISP. JES2 also groups output data sets on the following criteria which
a user can specify on the OUTPUT JCL statement:
These fields can also be modified through SDSF while output resides on the output or hold queue. When JES2 groups on the information on these fields, it attempts to match the character string exactly. Therefore, it is important to ensure the user specifies the exact string in each of the above so that JES2 can group the output properly. For example, JES2 will not group NAME='JOHN' and NAME='JOHN ' together. You can change the SYSOUT characteristics that affect grouping by using JES2 Exit 40. See z/OS JES2 Installation Exits for more information about Exit 40. The following tables illustrate how one output group can represent one of several SYSOUT data sets:
JES2 duplicates output groups built for job-related output depending on the number of job copies requested on the /*JOBPARM statement (up to the maximum allowed by the COPIES= parameter on the OUTDEF statement). This allows the devices available for output to govern the number of copies processed for a particular job. JES2 uses several factors to group SYSOUT data sets. The groups also conform to a set of rules, discussed below. Table 3 summarizes these rules. Note: If the output groups are transmitted through an
NJE network, do not use the /*JOBPARM JECL statement to produce multiple
copies. Instead, use the COPIES= parameter at the DD level. If COPIES=
is used at the DD level, JES2 does not duplicate output groups and
the output groups are handled appropriately.
JES2 uses the following factors to group output:
JES2 forms output groups whose data sets always agree on the following
characteristics:
If DMNDSET=YES on the OUTDEF initialization statement and the data set matches the job's message class or if USERSET=YES on the OUTDEF initialization statement and the user assigned the output group a name, then JES2 scans the setup characteristics of the output group's data sets to determine which, if any, of the setup characteristics vary. Otherwise, the output groups will also agree on setup characteristics.
To delay printing data sets, an installation can specify:
JES2 does not group spin data sets; each data set constitutes a “group” of one data set. |
Copyright IBM Corporation 1990, 2014
|