Parameter Description for R(nnnnn).PU(m)

CCTL=Yes|No
For SNA remote punches only, specify that carriage control characters are to be placed in the output stream transmitted to this remote punch. CCTL=No is required when the SELECT=BASICnn parameter of the R(nnnnn).PU(m) initialization statement is specified. When CCTL=No is specified, data will not be compressed or compacted, and SCS control characters will not be placed in the output string.

Modification: $T Rnnnnn.PUm operator command.

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

Modification: $T Rnnnnn.PUm operator command.

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

For SNA remote punches, the CKPTPAGE= and CKPTLINE= parameters determine the number of logical records within an SNA chain. JES2 will not take a checkpoint until it receives acknowledgment that the chain was received successfully by the RJE workstation. The chain size is the number of logical pages specified by CKPTPAGE=.

For BSC remote punches, the CKPTPAGE= and CKPTLINE= parameters determine the number of logical records sent to the RJE workstation before a checkpoint is taken. The checkpoint is not taken until JES2 receives acknowledgment that the RJE workstation successfully received the data.

Modification: $T Rnnnnn.PUm operator command.

CLass | Queue=c1[...cn]
Specifies the output classes, in priority sequence, to be processed initially by this card punch. You can specify any number of classes (A-Z and 0-9) up to a maximum number of 15 classes.

Modification: $T Rnnnnn.PUm operator command.

CMPCT=Yes|No
For SNA remote punches only - Specifies that this punch has compaction capabilities. CMPCT=Yes forces this punch to use compaction if the corresponding RJE workstation initialization statement (RMT(nnnnn) ) specifies COMPACT=Yes. Specifying CMPCT=Yes also causes the data to be compressed. CMPCT=NO turns off compaction even if compaction is specified on the RMT(nnnnn) initialization statement.
Note:
  1. If the RMT(nnnnn) initialization statement specifies compaction and the R(nnnnn).PU(m) initialization statement does not specify CMPCT=No, compression will be forced regardless of the COMPress= specification.
  2. CMPCT=Yes is valid only if CCTL=Yes.
  3. COMPACT= must be nonzero. If COMPACT=0, no compaction table is used and overrides a CMPCT=Yes specification.

Modification: $T Rnnnnn.PUm operator command.

COMPACT=nn|0
Specifies the compaction table (0-99) to be used for all outbound remote punch data. The COMPACT= parameter of the RMT(nnnnn) statement must indicate that compaction is supported by this punch. A compaction table value of 0 indicates no compaction table will be used, and will also override CMPCT=Yes, if it was specified.

Note that if a compaction table number is specified that does not match any compaction table defined by a COMPACT initialization statement, JES2 uses the default of 0.

Modification: $T Rnnnnn.PUm operator command.

COMPress=Yes|No
Specifies that this punch has compression/expansion capabilities. COMP=Yes forces this punch to use compression only if the corresponding RJE workstation (RMT(nnnnn) ) initialization statement has COMPRESS=Yes specified. COMP=No turns off compression for this punch even if the corresponding RMT(nnnnn) initialization statement specifies COMPRESS=Yes.
For SNA remote punches only:
  • COMPRESS=Yes is valid only if CCTL=Yes.
  • If COMPRESS=Yes, the corresponding bit in the RJE BIND is set on.

Modification: $T Rnnnnn.PUm operator command.

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

If you allow this parameter to default, JES2 selects all output for processing, regardless of the userid.

Modification: $T Rnnnnn.PUm operator command.

FLUSH=Yes|No
Specifies whether (Yes) or not (No) JES2 causes a blank card to be punched at the end of each data set or following each copy of a data set.

Intelligent workstations can use this parameter to create files that do not contain blank cards between data sets.

Modification: $T Rnnnnn.PUm operator command.

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

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

Modification: $T Rnnnnn.PUm operator command.

JOBname=jccccccc
Specifies the name of jobs whose output can be selected by this punch.

If you allow this parameter to default, JES2 selects all output for processing, regardless of the jobname. Wildcard specifications are allowed on this parameter.

Modification: $T Rnnnnn.PUm operator command.

LIMit=m|m-n|m-*
Specifies that output is to be selected for specific punches based upon the amount of the output (in records). The designated 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 0-4294967295. m and n can be equal. If they are not equal, n must be larger than m.

If 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.

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.

Default: If you omit this parameter, JES2 uses the defaults m=0 and n=4294967295.

Modification: $T Rnnnnn.PUm operator command.

LRECL=nnn|80
For SNA remote punches only, specifies the maximum logical record length (1-255) of data transmitted to this punch.

Modification: $T Rnnnnn.PUm 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.
Your installation may have output devices capable of punching other than line-mode data sets. If so, you can specify one or more names 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. 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 causing an error condition because the page-mode specifications are incompatible with remote punch processing.

Modification: $T Rnnnnn.PUm operator command.

RANGE={J|S|T}nnnnnn[-nnnnnn]|J1-65534
Specifies the job ID range for output jobs that can be selected by this punch. Use “J” to specify batch jobs, “S” to specify started 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 Rnnnnn.PUm operator command.

Routecde=
Specifies up to four internal route codes to be assigned to this punch. A route code indicates that this punch is eligible for special routing.
The maximum size of a route code is 18 characters. Wildcard specifications are allowed on this parameter for userids only. You can specify a route code in any of the forms listed below.
  • Ummmmm
  • destid
  • remote
  • user
Explanations of the different forms of specifying route codes follow:
Ummmmm
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 RJE workstation remote.
Note: If you specify a destid on the Routecde parameter, you must place the DESTID initialization statement before the R(nnnnn).PU(m) statement in the initialization stream.
LOCAL | ANYLOCAL
Indicates that output routed to the local node is selected.
remote
Indicates that output routed to an RJE workstation is selected. remote can be specified in any of the following ways:
Rmmmmm
Indicates that output routed to the specified RJE workstation is selected. Rmmmmm can also be specified as RMmmmmm or RMTmmmmm. The value specified for mmmmm can range from 1 to 32767.
destid
Indicates that output routed to a destid referring to an RJE workstation 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 the characters 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 destination specification 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 Unnnnn form to specify this punch as a special local punch.

If you do not specify a route code value, JES2 assigns the route code of the RJE workstation to which the punch is attached. (See the description of the RMT(nnnnn) statement in this topic for more information about the route code.)

Modification: $T Rnnnnn.PUm operator command.

SELECT=PUNCHnn|EXCHnn|BASICnn
For SNA remote punches only, specifies the device type (PUNCH, EXCH, or BASIC) and device subaddress (n-1) to which output queued for this remote device will be sent. The SELECT options and their meanings are:
Option
Meaning
PUNCH(nn)
Output sent to punch (card format)
EXCHnn
Output sent to exchange diskette device
BASICnn
Output sent to basic exchange diskette device

The value nn specifies the desired device number. The value of nn may range from 1-15 (subaddress 0-14). If nn is omitted, then any available device (subaddress 15) of the specified type (PUNCH, EXCH, or BASIC) will be used. When BASIC is specified, NOCCTL must be specified and LRECL must not exceed 128. See the RJE workstation publication for your device for valid device type subaddresses and their requirements.

Example: To cause all output to this RJE workstatio route code to be sent to a basic exchange diskette with subaddress 0, specify: 
SELECT=BASIC1
Note: If this is the only punch defined, Specification of BASICnn or EXCHnn for a SNA device will cause the media-byte presentation service portion of the bind to be changed to reflect non-card format.

If you do not specify a value, JES2 defaults to the standard device selection of punch and subaddress selection based upon punch number.

Modification: $T Rnnnnn.PUm operator command.

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

Modification: $T Rnnnnn.PUm operator command.

SEPDS=Yes|No
Specifies whether you desire data set separator cards for the data sets within the job output elements (JOEs) selected for processing by the specific device. If you enabled Exit 15 (Output Data Set/Copy Separators), the exit can test for SEPDS=Yes to cause 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 Rnnnnn.PUm 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 requiring setup verification by the operator. The punch uses any previously existing setup characteristics that you have not changed to process output.

Modification: $T Rnnnnn.PUm operator command.

START=Yes|No
Specifies whether (Yes) or not (No) this punch is started automatically when JES2 starts processing.

Modification: $S Rnnnnn.PUm operator command or $P Rnnnnn.PUm operator command.

SUSPEND=Yes|No
For BSC remote punches only, Specifies whether (Yes) or not (No) JES2 interrupts the punching of a data set every time this remote punch sends an end-of-transmission (EOT) message. An RJE workstation operator might interrupt punching in order to transmit jobs or JES2 commands to the JES2 member.

Modification: $T Rnnnnn.PUm operator command.

Specifies whether tracing is activated or deactivated for all remote punches. To trace a remote punch, you must also provide the following initialization statements:
  • TRACE(n) START=Yes
  • TRACEDEF ACTIVE=Yes
TRace=Yes|No|P
Note: TRACE=Yes is identical to specifying TRACE=P. This parameter setting can be overridden by the $T R(nnnnn).PU(M) operator command. Remote 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 topic, and z/OS JES2 Commands for a description of the $S TRACE command for further information concerning the tracing facility.)

Modification: $T Rnnnnn.PUm command

Note: If you modify this parameter value and then restart JES2 with a hot start, the parameter value in effect before termination will be used. (For further information, see z/OS JES2 Initialization and Tuning Guide.)
Volume=(v1[,v2][,v3][,v4])|()
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 Rnnnnn.PUm command.

Writer=xxxxxxxx
Specifies the 1- to 8-character writer name assigned to this punch. Wildcard specifications are allowed on this parameter.

Default: no writer name

Modification: $T Rnnnnn.PUm 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 CLass/Queue 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 punch 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:
  1. 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.
  2. If WS= is added to this remote punch statement, you must specify Routecde in the WS= list.
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 punching. 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 Rnnnnn.PUm operator command.