z/OS JES2 Initialization and Tuning Reference
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Parameter Description for PUN(nn)

z/OS JES2 Initialization and Tuning Reference
SA32-0992-00

CKPTLINE=nnnnn|100
Specifies the number of cards (1-32767) to be punched per logical page. This value is the only one used to define a logical page for punches.

Modification: $T PUN(nn) operator command.

Note: To switch off checkpointing, specify CKPTLINE=0.
CKPTPAGE=nnnnn|1
Specifies the number (1-32767) of logical pages to be punched before each checkpoint is taken.

Modification: $T PUN(nn) operator command.

{CLass|Queue}=c1...cn|BK
Specifies the output classes to be processed initially by this card punch. You can specify any number of classes (A-Z and 0-9) up to the maximum of 15 classes.

Modification: $T PUN(nn) operator command.

CReator=cccccccc
Specifies the 1- to 8-character userid whose output can be selected by this punch. Wildcard specifications are allowed on this parameter.

If this parameter is allowed to default, JES2 can select all output for processing, regardless of userid.

Modification: $T PUN(nn) operator command.

Forms=xxxxxxxx,...,xxxxxxxx
Specifies the 1- to 8-alphameric character forms name of the forms that are to be loaded initially in this punch. Wildcard specifications are allowed on this parameter.

If you do not specify a value, JES2 provides the forms identifier specified by the STDFORM= parameter on the OUTDEF statement.

Modification: $T PUN(nn) operator command.

JOBname=jccccccc
Specifies the 1- to 8-character job name for jobs whose output can be selected by this punch. Wildcard specifications are allowed on this parameter.

If this parameter is allowed to default, JES2 can select all output for processing, regardless of jobname.

Modification: $T PUN(nn) operator command.

LIMit=m|m-n|m-*
Specifies that output is selected for specific punches based upon the amount of the output (in records). The values m and n specify within what output size range (in records) a job output element (JOE) must fall to be processed by this punch. The integer m specifies the lower output size limit and n specifies the upper output size limit.

For both variables m and n, you can specify a range of values from 0-4294967295. m and n can be equal. If they are not equal, n must be larger than m.

Start of changeIf you code only m, that value becomes both the lower and upper limit. If m-* is specified, the upper limit is set to the default value of 4294967295.End of change

After a warm start, the original size of the output (before any punching) will be used to determine where the remainder of the output will be punched. That is, the original size of the JOE will be used to determine output device selection.

The default values are m=0 and n=4294967295.

Modification: $T PUN(nn) operator command.

Pause=Yes|No
Specifies whether (Yes) or not (No) this card punch is to pause between data set groups.

Modification: $T PUN(nn) operator command.

PRMode=(vvvvvvvv[,vvvvvvvv...])
Specifies one to eight names used by JES2 to direct output data sets to this output device. Wildcard specifications are allowed on this parameter. If only one PRMODE is specified, the parentheses are optional. Users can assign a PRMODE value to the data sets by using JCL OUTPUT statements. However, if the user does not specify a process mode for the data set, JES2 will assign a process mode. If the data set contains formatting controls that can only be processed by a page-mode printer, JES2 defaults the PRMODE= specification to PAGE. For all other data sets, the default is LINE.
Your installation may have output devices capable of printing other than line-mode data sets. If so, you can specify a name(s) on this parameter designating the output device as capable of accepting such data sets. For installation-defined process modes, use the Uvvvvvvv form of the process mode designation. The U identifies the process mode as installation defined. Installation-defined and IBM-defined process mode designations may be mixed on one PRMODE= parameter statement. For example, you can specify names on this parameter designating the output device as capable of accepting data sets that can be printed on either a plotter device (for example, UPLOT2) or a line-mode printer by specifying:
PRMODE=(UPLOT2,LINE)
Note:
  1. You can specify only up to eight process modes on a single device; however, you can specify as many as 255 different modes throughout a particular JES2 member.
  2. Within a job entry network, receiving nodes must designate the same process mode as that specified on the data set(s) sent to them. If the receiving node has not specified the same process mode, the data set(s) will not be printed.
  3. To specify a null processing mode, use PRMode=().

Default: LINE, except for those data sets containing formatting controls that can only be processed by page-mode printers. The default for these data sets is PAGE.

Modification: $T PUN(nn) operator command.

RANGE={J|S|T}nnnnn[-nnnnn]|J1-999999
Specifies the job ID range for output jobs that can be selected by this punch. Use “J” to specify batch jobs, “S” to specify stated tasks, and “T” for TSO/E jobs. You can specify a single job number or range (up to 65534) of jobs. If you code this parameter, you can specify one or two values:
  • If you specify one value, that value becomes both the low and the high end of the range.
  • If you specify two values, the first value is the low end of the range and the second value the high end. The two values can be equal. If they are not equal, the second value must be larger than the first value.

Modification: $T PUN(nn) operator command.

Routecde=rtcode | LOCAL
Specifies up to four internal route codes to be assigned to this card punch. Wildcard specifications are allowed on this parameter for userids only. A route code indicates that this card punch is to be eligible for punch routing.
The maximum size of a route code is 18 characters. You can specify a route code in any of the forms listed below.
  • Ummmm
  • destid
  • remote
  • user
Note: If destid is used, it must be previously defined on a DESTDEF statement in the initialization stream. Explanations of the different forms of specifying route codes follow.
Ummmm
Indicates that output for special local routing is selected. The special routing numbers range from 1 to 32767.
destid
Indicates that output routed to the specified node(s) is selected. If destid is specified alone, it refers to both the node and the remote.
remote
Indicates that output routed to a remote is selected. Remote can be specified in any of the following ways:
LOCAL | ANYLOCAL
Indicates that output routed to the local node is selected.
Rmmmm
Indicates that output routed to the specified remote is selected. Rmmmm can also be specified as RMmmmm or RMTmmmm. The value specified for mmmm can range from 1 to 32767.
destid
Indicates that output routed to a destid referring to a remote is selected.
user
Indicates that output routed to a specific userid is selected. Generic userids are also valid. A generic userid is a userid that ends in an asterisk (*), and refers to all userids that begin with any character preceding the *. Note that the * can only be specified in the last position of the userid.

A userid at the local node must be in the form of a valid TSO/E userid. It must begin with an alphabetic (A-Z) or a special character ( @ # or $ ), and the remaining characters may be alphabetic, numeric, or special characters.

You can override the destinations specified by this parameter with the set operator command ($T). If you specify only one route code the parentheses are optional. To specify a null route code, use Routecde=( ) to cause this punch to select no work if Routecde is also specified in the WS list. Use the Unnnn form to specify this punch as a special local punch.

Note: Route codes for local devices should be used cautiously. When a card punch has been assigned a route code or route codes, it is considered available only for a job that requests punched output through the DEST keyword on the /*OUTPUT control statement or JCL OUTPUT statement, or through the /*ROUTE control statement or by operator command.

Modification: $T PUN(nn) operator command.

Sep=Yes|No
Specifies whether (Yes) or not (No) separator cards are not to be initially provided between data set groups. (Separator cards can be specified later by the JES2 $T command.) This specification can be overridden by a JES2 Exit 1 routine. See z/OS JES2 Installation Exits for information about Exit 1.

Modification: $T PUN(nn) operator command.

SEPDS=Yes|No
Specifies whether data set separator cards are desired for the data sets within the job output elements (JOEs) selected for processing by the specific device. JES2 does not actually generate data set separator cards based on this parameter specification. If you enabled Exit 15 (Output Data Set/Copy Separators), SEPDS=Yes causes the exit to generate separator cards for each data set selected by this device. See z/OS JES2 Installation Exits for information about Exit 15.

Modification: $T PUN(nn) operator command.

Note: Be careful not to confuse this parameter with the SEP= parameter.
SETUP=HALT|NOHALT
Specifies whether JES2 issues the device setup message ($HASP190) after a change of device characteristics (for example, forms control).

SETUP=HALT halts the punch and issues the setup message. This allows the operator to verify the changes to the punch.

SETUP=NOHALT allows the punch to process output without setup verification by the operator. The punch uses any previously existing setup characteristics that you have not changed to process output.

Modification: $T PUN(nn) operator command.

START=Yes|No
specifies whether (Yes) or not (No) this card punch (if it is ready) starts automatically when JES2 starts processing.
Note: If the punch is to be started automatically and is unavailable when JES2 is started, it remains unusable until the next time JES2 is started, unless the UNIT= keyword is specified on this device statement. If UNIT= is specified, the specified unit is started although it may have been offline during JES2 initialization.

Modification: $S PUNnnnn operator command or $P PUNnnnn operator command.

TRace=Yes|No|P
Specifies whether tracing is activated or deactivated for all punches. To trace a punch you must also provide the following initialization statements:
  • TRACE(n) START=Yes
  • TRACEDEF ACTIVE=Yes

This parameter setting can be overridden by the $T PUN(nnnn) operator command. Punch tracing is also controlled by trace IDs 11 and 12, the TRACE(n) and TRACEDEF initialization statements, and the $S TRACE command. (See z/OS JES2 Initialization and Tuning Guide, the TRACE(n) and TRACEDEF initialization statements in this chapter , and z/OS JES2 Commands for a description of the $S TRACE command for further information concerning the tracing facility.)

Modification: $T PUN(nn) command

Note: If you modify this parameter value and then restart JES2 with a hot start, the parameter values in effect before termination will be used. (For further information, see z/OS JES2 Initialization and Tuning Guide.)
UNIT={hhhh|/hhhh}
Specifies a 3- or 4-digit hexadecimal device number. Device numbers can be specified by any of the following formats:
UNIT=hhh
UNIT=hhhh
UNIT=/hhh
UNIT=/hhhh
where hhh and hhhh represent the device numbers.

A slash (/) can optionally precede the device number (for compatibility with other initialization statements that require a slash to denote a 4-digit device number).

If UNIT= is specified, this card punch is allowed to start although it may have been offline during JES2 initialization.

If not specified, JES2 does not assign an available card punch; instead, a card punch can be dynamically assigned using a $T PUNnn command.

Modification: $T PUN(nn) operator command.

Volume=(v1[,v2][,3][,4])|()
Specifies the 5- to 6-character volume serial number of a volume containing a spool data set. Only output jobs containing tracks on the specified volume can be selected for punching. As many as four volumes can be specified. Use commas to separate individual volume IDs and enclose the list in parenthesis if more than one ID is specified.

Modification: $T PUN(nn) operator command.

Writer=xxxxxxxx
Specifies the 1- to 8-character writer name assigned to this punch. If not specified, there is no writer name. Wildcard specifications are allowed on this parameter.

Modification: $T PUN(nn) operator command.

WS=criteria | (W,Q,R,PRM,LIM/F)
Specifies the output selection criteria (listed below) for this device. Criteria not specified are not considered during output selection, although they are used by JES2 to determine setup requirements.
Unless otherwise noted, if the criterion is specified before the slash, an exact match is required; if after the slash, an exact match is preferred (and attempted in left to right priority) but not required, only the priority order is considered. The criteria that may be coded follow:
CLass|Queue
Specifies that a match must be found for the output classes specified on this device. If Q is omitted from the WS= list, all output queues (beginning with queue A) will be searched for work.
Note: If specified before the slash, the priority of the device characteristics table class list is from left to right. If specified after the slash, there is no device characteristics table class list priority ordering. To increase performance, this criterion should be placed before the slash.
CReator
Specifies that output for the current userid is preferred. JES2 attempts to consecutively select all eligible output for a particular userid. However, output is only grouped in this manner depending upon the specification of the current work selection list and output queues. If specified to the left of the slash, an exact match is required.
Forms
Specifies that the current FORMS specification is either required or preferred. If FORMS is omitted from the criteria list, work selection will not contain any forms checking.
JOBname
Specifies that JES2 gathers all output for a job and attempt to process that output consecutively. The JOBNAME= parameter for a particular device determines what job name JES2 selects when JES2 has processed all output that matches the current job name.
  • If JOBname= is specified before the slash in the WS= list:

    JES2 selects only those jobs that match the value specified on JOBNAME= for a specific device. When JOBNAME= is specified as a generic name, JES2 only processes jobs that match that pattern and attempts to process all output for that job name consecutively.

  • If JOBname= is specified after the slash in the WS= list:

    JES2 uses the value specified on JOBNAME= to select new job names for the specific device. If there are no job names that match the JOBNAME= specification, JES2 selects jobs as if JOBname were not listed in the WS= list. A device gathers and processes all output for a particular job before again examining the value specified on JOBNAME= for more jobs.

If you require JES2 to group jobs based on job name but do not want JES2 to prefer a particular JOBNAME= pattern, specify JOBNAME=* on the device statement and code JOBname after the slash in the WS= list.

LIMit
Specifies that the limits of output, as noted on the LIMIT= keyword (on this initialization parameter) will be supported, that is, the amount of generated output must fall within the LIMIT= specification.

This subparameter has no effect as a work selection value for files received from a node that does not provide a page count for its files. For more information, see the sending node's reference documentation.

PRMode|PMD
Specifies that the current PRMODE= specification is preferred. If more than one mode is specified, they are in left to right priority order.
Note: To print output, a match must be found; this criterion should be placed before the slash.
Priority
Specifies that output priority will be considered. Priority is not matched with any other parameter; rather, it specifies that a higher output priority receives greater output preference. If specified before the slash, the importance of selecting output by priority is increased.
Note: To prevent performance degradation, this criterion should be placed after the slash.
Routecde
Specifies that only output destined for a destination specified by a route code listed on the ROUTECDE= parameter is eligible for selection by this device.
Note: If Routecde is specified before the slash, the route code(s) are in left to right priority order; if specified after the slash, there is no such priority order. To prevent performance degradation, this criteria should be placed before the slash.
RANGE
Specifies that the current job ID range is preferred. If specified to the left of the slash, an exact match is required.
Volume
Specifies that only output with tracks on the currently specified volume can be selected for printing. If specified to the left of the slash, the volumes are considered to be in left to right priority order. If specified to the right of the slash, no priority order exists, but an exact match is still required.
Writer
Specifies that the writer name (W=) specification is either required or preferred.
Note: Embedded comments are not allowed within the WS= parameter specification.

Modification: $T PUN(nn) operator command.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014