SR=options
System resources used. Anyone or more of the following groups of resources can be specified. Options are
separated by colons. The default is a listing of the job's usage of resources in all of the following groups:
CPU Time executing in CPU, 1/0 waiting time, and time waiting for CPU. CPU gives the totals for the entire job.
7-8 SR-OOll 0
I
DS Permanent dataset space accessed, permanent dataset space saved, temporary dataset space used, disk sectors moved, fast secondary storage (FSS) sectors moved (SSD or Buffer Memory), user I/O requests, memory-resident datasets used, number of OPEN calls, and number of CLOSE calls
FSU FSS usage. An FSS device is either an SSD or the Buffer Memory in the lOS. When a job uses an FSS device not configured as a generic resource, the FSU option reports device usage. The option reports the following information in the user log and system log:
Device name
Maximum concurrent allocation
Unit allocation integral (sector*sec) Number of sectors transferred
GRU Generic resource usage. For each generic resource named on the JOB control statement, the following information appears in the user log and system log:
Generic resource name
Device type (tape, disk, or ISP) Job limit
Maximum concurrent allocation
Unit allocation integral (tape unit*sec or sector*sec)
Number of sectors transferred Number of tape blocks transferred Number of tape volumes mounted JNU Jobname and user number
JSQ Job sequence number
MM Minimum job size (words), maximum job size (words), execution-time memory usage in million words/second, I/O wait-time memory usage in million words/second, maximum field length used (words), minimum field length used (words), maximum JTA used (words), and minimum JTA used (words)
NBF Number of 512-word blocks (sectors) received from a front end and number of 512-word blocks (sectors) queued to a front end
SR-OOll
a
7-9TASK Time executing in CPU, 1/0 wait time, and time waiting for CPU. The TASK option breaks down the time information according to user task number, and provides a total for the entire job.
WT Time waiting in the input queue before beginning execution
7.5 ECHO - ENABLE OR SUPPRESS LOGFILE MESSAGES
The ECHO control statement controls the message classes written to your logfile by turning them ON or OFF. ECHO may be used more than once during a job to toggle the printing or suppression of message classes.
ECHO is a system verb. ON is the default at the start of a job.
The keywords ON and OFF may be used in any combination. Ensure that the classes specified do not overlap between the keywords, however, and that both defaults are not included.
Format:
7-10
ON=classi When a COS or a program issues messages, they are written to your logfile in the classes specified. If any other classes were specified but not turned off by this statement, the union of the two sets of classes is enabled. If the ECHO control statement contains only the keyword ON or ON=ALL, all messages are written to the logfile.
OFF=classi
Messages in the classes specified are not written to the job's logfile. If any other classes were specified but not turned on by this statement, the union of the two sets of classes is suppressed. If the ECHO control statement contains only the keyword OFF or OFF=ALL, all messages in defined classes are suppressed.
Messages that are not classified may not be turned off.
SR-0011 0
The operating system recognizes the following classes:
Description
ABORT ABxxx and system traceback messages that COS issues when a job fails
JCL Messages that originate in the job's JCL input file PDMERR Error messages produced by PDM
PDMINF Dataset information messages produced by PDM
When a job calls a procedure, the echo state of the job is the same upon return from the procedure as before, even though the procedure may use a different echo state. The following occurs when ECHO is used with CALL and procedure invocations:
• The echo state of the caller is saved so that on return to the caller the same state is in effect as before the call.
• When the procedure includes an ECHO statement, the new echo state is in effect only for the duration of the procedure. If the procedure does not include an ECHO statement, the echo state of the caller is in effect.
7.6 EXIT - EXIT PROCESSING
An EXIT control statement points to the place in the control statement file where processing of control statements resumes following a job step abort from a program. If no job step abort occurs, the EXIT control statement indicates the end of control statement processing. EXIT is a system verb. It has no parameters.
Format:
EXIT.
SR-0011 0 7-11
7.7 IOAREA - CONTROL USER'S ACCESS TO IIO AREA
The IOAREA control statement locks or unlocks that portion of the user field containing the user's DSP and IIO buffers. Locking denies the user access, unlocking allows the user access. This area follows the High Limit Memory (HLM) address of the user field. The user of the stack version of the COS libraries needs to note that IOAREA does not protect IIO buffers or DSPs that have been allocated within the user's stack space. IOAREA is a system verb.
Format:
I
IOAREA, LOCK • 1 UNLOCK
I
_ _ _ _ _ _ _ 1
LOCK UNLOCK
The keywords LOCK and UNLOCK are mutually exclusive. A parameter must be specified on the control statement. When the control statement is not used, the user's IIO area is assumed to be unlocked.
If LOCK is selected, the system sets the limit address to the base of the DSPs, thereby denying direct access to the user's DSP area and IIO buffers. When the IIO area is locked, the library IIO routines make a system request to gain access to the IIO area. Although the system request introduces additional overhead in job processing, i t should prevent accidental destruction of the IIO area.
If UNLOCK is selected, the system sets the limit address to the value specified in JCFL, allowing access to the user's DSP area and IIO buffers.
7.8 JOB - JOB IDENTIFICATION
The JOB control statement defines the job to COS and must be the first statement in a control statement file. The JOB control statement cannot be continued, and no leading blanks are allowed. JOB is a system verb.
Format:
JOB,JN=jn,MFL=fl,T=tl,P=p,US=US,OLM=olm,CL=jcn,gn=nr,S.
7-12 SR-0011 0
IN=jn
T=tl
P=p
US=us
OLM=olm
CL=jcn
Job name; 1 to 7 alphanumeric characters. This name identifies the job and its subsequent output. IN is a required parameter.
Maximum field length allowed the job, in 54-bit words.
The job's maximum field length is set to the greater of fl, rounded up to the nearest multiple of 512 words, or the amount needed to load the Control Statement Processor (CSP). The job is aborted if the maximum field length is greater than the system maximum.
If this parameter is omitted, the maximum field length is set by the site parameter.
If MFL is present without a value, the field length is the system maximum. The system maximum is the smaller of the total amount of memory available after COS is initialized minus the job's JTA size (refer to section 1) or an
installation-defined maximum job field length.
Time limit in seconds that the job may run. If this parameter is omitted, the time limit is set to a value determined by an installation parameter. If T is present without a value, a maximum of 16,777,215 (approximately 194 days) is allowed.
Priority level 0 to 15 at which the job enters the system.
If P is 0, the job is not initiated. If omitted, a value specified by the installation is assumed.
User number; 1 to 15 alphanumeric characters. The default is no user number. This parameter identifies the user
submitting the job. Specific usage is installation defined.
Maximum size of $OUT. oim is a count of 512-word blocks.
A block holds about 45 print lines. The installation defines the default and maximum values for oim.
Name of the installation-defined job class that this job fits in; 1 to 7 alphanumeric characters. The job is aborted if i t does not fit the requirements of its class or if the class does not exist. The default is no class name.
Type and number of dedicated resources required by a job.
gn is a generic resource name of 1 to 7 alphanumeric
characters. A generic resource name corresponds to a device type. For example, a generic name of SSD could be given to
t
The f l parameter on the JOB statement excludes the job's Job Table Area (JTA); space for the JTA is added by the system.SR-0011 0 7-13
gn=nr
(continued)
an SSD. Site administration defines generic names. COS provides one generic name (*TAPE, which refers to a dual density tape unit capable of 1600 or 6250 b/i), but sites may define up to 16 generic names. Contact your CRI site analyst for the generic names used at your site.
nr
is the decimal number of units of the specified resource type. Ifgn
refers to a tape device type,nr
is the number of tape units to be used concurrently. If
gn
refers to a disk device type,nr
is the decimalnumber of sectors required. The default is O. A job is initiated only when the amount of each resource reserved is eligible for use. The job is aborted if i t attempts to access more resources than are reserved with the JOB control statement.
S System job. This is a privileged parameter that designates the job as a system job. Privileges are verified during account processing.
7.9 LIBRARY - LIST AND/OR CHANGE LIBRARY SEARCHLIST
The LIBRARY control statement lets you specify the library datasets that will be searched during the processing of control statement verbs.
LIBRARY may also be used to list the current or new searchlist to the logfile for verification.
When modifying the searchlist, the current members of the searchlist can be retained in the new searchlist by including an asterisk in the LIBRARY control statement. The asterisk corresponds to all members of the
current searchlist in their present order. If the asterisk is omitted, the new searchlist contains only the library dataset names identified on the LIBRARY control statement. LIBRARY is a system verb.
When a job initiates, the default library searchlist consists of the library dataset.
Format:
DN=dni
7-14
•
Library dataset names that will be part of the new
library searchlist. A maximum of 64 names can be given.
The order in which they appear on the control statement is
SR-0011 0
DN=dni the order in which they are searched. An asterisk included (continued) in the list signifies the current searchlist members are to
be part of the new searchlist in their current order.
V For verification, list the current library searchlist on the logfile. When specified along with the new searchlist, the new searchlist is listed.
7.10 MEMORY - REQUEST MEMORY CHANGE
The MEMORY control statement lets you request a new field length, change the mode of field length reduction, or both. Section 3 discusses job memory management. MEMORY is a system verb.
You must specify at least one parameter for the MEMORY control statement.
Format:
MEMORY[,FL=fl1[,USER].
AUTO
FL=fl
USER AUTO
Field length. f l specifies the number of words to be allocated to the job. If FL is specified without a value, the new field length is set to the maximum allowed the job.
Field length reduction is managed by the user (user mode) Field length reduction is managed by the system (automatic mode)
The field length is set to the larger of the requested amount rounded up to the nearest multiple of 512 words or the smallest multiple of 512 decimal words large enough to contain the user code/data, LFT, DSP, and buffer areas. Field length management is in user mode for the duration of the next job step.
When the USER parameter is specified, the job is placed in user mode until a subsequent request is made to return i t to automatic mode. When the AUTO parameter is specified, the job is placed in automatic mode.
The job step is aborted if completing the request results in a field length greater than the maximum allowed the job. The maximum is the smaller of the total number of words available to user jobs minus the job's JTA or the amount determined by the MFL parameter on the JOB control statement.
SR-0011 0 7-15
Examples:
MEMORY,FL,USER.
The job's field length is set to the maximum allowed and the job is placed in user mode until an explicit request is made to return i t to automatic mode.
MEMORY, AUTO.
The job is returned to automatic mode. Its field length is reduced at the next job step.
MEMORY,FL=28988.
The field length is adjusted. If the job is in user mode by explicit user request, no change in mode occurs; otherwise, the job is placed in user mode for the duration of the next job step.
MEMORY,FL=28988,AUTO.
The field length is adjusted and the job is placed in user mode for the duration of the next job step. After the next job step, the job is put in automatic mode.
7.11 MODE - SET OPERATING MODE
The MODE control statement sets or clears mode flags in the Exchange Package for the job. MODE is a system verb.
Format:
7-16
MODE,FI=option,BT=option,EMA=option,AVL=option,ORI=option.
FI=option Floating-point interrupt mode. option can be either of the following:
ENABLE DISABLE
Enables floating-point error interrupts;
default.
Disables floating-point error interrupts;
floating-point errors are ignored.
SR-0011 0
BT=option Bidirectional transfer mode. The BT parameter is used
EMA=option
AVL=option
ORI=option
on CRAY X-MP series computer systems only. option can be either of the following:
ENABLE DISABLE
Enable bidirectional memory transfers; default.
Disable bidirectional memory transfers; block reads and writes are not performed concurrently.
Extended memory addressing mode. The EMA parameter is used on CRAY X-MPt series computer systems only: it causes an abort on CRAY-! systems. option can be either of the following:
ENABLE DISABLE
Enables extended memory addressing
Disables extended memory addressing; the default is an installation option released as EMA=DISABLE. On the CRAY X-MP model 48, the default is released as EMA=ENABLE.
Second vector logical functional unit mode. The AVL parameter is used on CRAY X-MPt series computer systems only; i t causes an abort on CRAY-1 systems. option can be either of the following:
ENABLE
DISABLE
Makes two logical functional units available, the first of which shares reservation logic with the vector floating multiply unit.
Makes only one vector logical unit available.
The vector multiply reservation path is not shared; default is an installation parameter released as AVL=DISABLE.
Operand range error interrupt mode. The ORI parameter is used on CRAY X-MP series computer systems only; option can be either of the following:
ENABLE DISABLE
Enables interrupts on operand range errors;
default.
Disables interrupts on operand range errors
t Not available on all CRAY X-MP systems. Check with a CRI site analyst to determine if this feature is available.
SR-0011 0 7-17
I
7.12 NORERUN - CONTROL DETECTION OF NONRERUNNABLE FUNCTIONS
The NORERUN control statement specifies whether COS is to recognize
functions that would make a job rerunnable. The current rerunnability of the job is not affected. NORERUN is a system verb.
Format:
NORERUN,ENABLE .
ENABLE DISABLE
DISABLE
The keywords ENABLE and DISABLE are mutually exclusive.
The default for the system as released is NORERUN,ENABLE;
however, this is an installation option.
ENABLE instructs the system to begin monitoring functions performed by the job and to declare the job nonrerunnable if any of the nonrerunnable functions are performed.
DISABLE instructs the system to stop monitoring functions for nonrerunnable operations. If a job has already been declared to be nonrerunnable, specifying DISABLE does not make the job rerunnable again.
7.13 OPTION - SET USER-DEFINED OPTIONS
The OPTION control statement specifies user-defined options, such as the format of the job's listing. OPTION is a system verb.
Format:
: OPTION[,LPP=n)
~PN=~]~STAT=~:F]'
,---LPP=n
7-18
Number of lines per page (0 through 255) for a job
listing. If 0 is specified, the current number of lines per page is not changed. The default is an installation parameter.
This value is used by CRI products that do pagination and is available to user software through the GETLPP subroutine call. It has no effect on IIO processing from user jobs that do not perform their own pagination.
SR-0011 0
I
PN=P ANY
ON STAT=OFF
SR-0011
a
Select processor. Select a processor by specifying its number as the argument. Use ANY to indicate that any processor is acceptable. The default is ANY.
If the processor specified by p is not available (because i t does not exist on the mainframe or is inoperative), an error message appears and the job aborts.
Specifies the level of I/O statistics gathered for
datasets local to the job. The statistics appear on the user logfile when the dataset is released. The statistics can be on two levels:
• User level statistics (sometimes called accounting information) that identify the type of system requests you made for the dataset.
• System level statistics (sometimes called device information) that indicate how the system handled the requests device by device.
The options are as follows:
ON User information as defined by the site or, if not defined by the site, as determined by the preset categories of USR. ON is the default if STAT is specified without an option.
OFF No statistics. OFF is the default if STAT is not specified on the OPTION control statement.
The output is a logfile message of one or more lines with the following format:
SY005 -
Idn
xWROS, xIOS, XREQ, xSECTRS, xx.xxSECIdv
xSECTRS mode: XREQ, xSECTRS, xx.xxSEC The first line of the message reports the followinguser-level information (it is issued when STAT equals ON):
Idn
XWROS xIOS
Local dataset name
Size of the dataset in words (decimal) Number of I/O suspensions performed for the dataset by F$RCL
7-19
I
XREQ Number of the start liD requests (F$WDC, F$RDC, and F$QIO) resulting in queue manager requests xSECTRS Number of sectors moved as a result of theF$WDC, F$RDC, F$BIO, and F$QIO requests xX.xxSEC Time in seconds that the job spent in liD
suspension waiting for the dataset Subsequent lines in the message report system level
information. Each line corresponds to an 1/0 transmission to a device on which the dataset resides. A line appears for every device on which the dataset has space allocated.
The lines contain the following information:
Idv
xSECTRS
mode
xREQ
xSECTRS
Logical device name (optional)
Number of sectors allocated on the device for the dataset (optional)
Direction of 1/0 data transfer requests: READ or WRITE
Number of data transfer requests issued to the device driver
Number of sectors moved as a result of the data transfer requests
xX.xxSEC Time in seconds that the system (queue manager) waited for the device driver to
respond to the data transfer requests
STAT gathers 1/0 statistics on every dataset created or
STAT gathers 1/0 statistics on every dataset created or