Adds or changes switches for a request placed in a batch or output
|/AFTER:date and/or time, or day of week (or TODAY) and/or time
ensures that the request will not be processed until after he revised date
and/or time specified. NOV-12-79, and 18:00 illustrate two arguments to
this switch. If you give both date and time, separate them with a space.
When given alone, the time may be preceded by a plus sign (+), which will
delay processing by the indicated length of time from the present.
Alternatively, you can give a day of the week (for example, MONDAY) or
TODAY as argument; then the job will not be printed until the beginning of
the following day. If you follow this argument with a plus sign and a
time, the job will be further delayed by this amount.
|| gives the decimal line number of the control file at which processing
is to begin (for BATCH), or the decimal page number of the file at which
the output is to begin (for CARDS, PAPER-TAPE, PLOT, and PRINT)|
|| specifies the decimal number of spooled cards the job is allowed to
|| tells how many copies of the file to produce|
|| deletes the file after processing. Opposite of /PRESERVE.|
||sets the request's dependency count to the new value n. This switch
can also be followed by a signed value, such as +n or -n, which will
increase or decrease the old value by the specified amount.
A batch request is not processed until its dependency count is 0. See
the TOPS-10/20 Batch Reference Manual for more information about dependency
||specifies the node on whose line printer the log file of your batch job
is to be printed (for BATCH), or the node on whose line printer or other
output device your request is to be processed (CARDS, PAPER-TAPE, PLOT, and
PRINT). Two colons (::) following the node name are optional.|
||specifies the decimal number of feet of spooled paper tape the job is
allowed to punch.|
|| specifies that the file consists of ASCII text, or COBOL SIXBIT
text; or (ELEVEN) contains four eight-bit bytes in each 36-bit word; or is
FORTRAN ASCII text, where column 1 of each line is interpreted as a
carriage control character.
||specifies, in six or fewer characters, new forms (determining the size
of banner, header, and trailer sections; the paper color, width, and
weight; vertical format, carriage control tape, the number of plotter steps
per inch, etc.) to use with the job|
||allows the output to be produced on any available device. Use along
with argument PRINT to cancel the /LOWERCASE or /UPPERCASE switch, or with
PLOT, PRINT, CARDS, or PAPER-TAPE to cancel the /UNIT switch.|
|| causes a header section containing the jobname to be plotted, printed,
or punched before the file itself is produced.|
||does not change the jobname, but specifies which job to modify. Same
as jobname in "identifier" argument.|
||places a new limit of n cards, feet, or pages on the output of the
||specifies that the file is to be produced on a line printer capable of
printing lowercase characters.|
|| designates the mode for punching the file onto cards. See the
/MODE switch in the PUNCH command description for details.
|| designates the mode for punching the file onto paper tape. See
the /MODE switch in the PUNCH command description for details.
|| designates the mode for plotting the file. See the /MODE switch
in the PLOT command description for details.
|| designates the mode for printing the file. See the /MODE switch
in the PRINT command description for details.
||prevents a header section containing the jobname from being produced
before the file is produced.|
||labels the header section of output (the section displaying the
jobname) with a message or notation of up to 12 characters. The message
must be enclosed in double quotation marks if it contains spaces or
|| says whether you want the log file to be printed always, or only
in the case of unhandled errors occurring within the job, or never. No
matter which option you choose, the log file is always created.
||specifies the decimal number of spooled line printer pages the job is
allowed to print.|
||saves the file after it is processed. Opposite of /DELETE.|
||assigns a new number n reflecting the urgency of the request. This n
must be from 1 to 63, with larger numbers receiving earlier
||specifies the IBM host system on whose CPU the JCL batch job is to be
run. The node name must be of six or fewer characters and must be followed
by two colons (::).|
||specifies the name of a remote print queue to print the file.|
||scans your files and processes only those lines whose first characters
are the title you give. This title can contain up to 12 characters
(including the quotation marks that must enclose the title if it contains
spaces). The switch is used along with the COBOL report writer.|
|| specifies whether the job should be started again if the system
crashes and restarts.
||does not change the sequence number of the job but rather specifies
which job to modify. Giving this switch is an alternative to supplying a
request ID as the request identifier when you have several jobs with the
same jobname (if you supply only the jobname to identify the job, the
MODIFY command affects all of them).|
|| determines the spacing between printed lines.
||revises the limit for the maximum amount of CPU time available to the
job; given in hours, minutes, and seconds.|
||limits to n the maximum number of minutes of spooled plotter time
allowed for the job.|
|| changes your declaration, if two or more jobs are submitted from
the same connected directory, whether they must run at separate times.
||directs your request to the line printer of the specified octal unit
||specifies that the file is to be produced on a line printer that uses
uppercase characters only.|
||specifies the user whose request is to be modified; for privileged
users only. This switch is required to modify a request from a user other
The MODIFY command affects a batch or output request only before
processing has begun. After processing has begun, you can only cancel the
request with the CANCEL command, and then make a new request.
You can use the /DEPENDENCY-COUNT switch to specify the order in which
your batch jobs are processed. Set the dependency count of all but the
first job to some positive value when you submit them, and include MODIFY
commands in each job's control file to bring the next job's dependency
count to 0 at the appropriate time. See Example 4.
In the singular case when you want to modify several queue requests of
the same jobname using only one command, and that jobname is purely
numerical (for example, 5045), you must use the /JOBNAME:jobname switch as
second argument to the MODIFY command. Do not also give the request ID or
jobname as a command argument if you give the /JOBNAME:jobname switch.