Assignil'j3 Values To Symbolic Values; Writing Command Procedures - IBM System 360 User Manual
Operating system: time sharing option terminal
Hide thumbs
Also See for System 360:
- Operating manual (48 pages) ,
- Manual (44 pages) ,
- Hardware maintenance manual (508 pages)
Table of Contents
Advertisement
ASSIGN ING VALUES
TO
SYMBOLIC VALUES
If the command procedure contains symbolic values, the installation
should provide you with a list of the symbolic values used" what meaning
is associated with each symbolic value, whether you must supply an
actual value for each symbolic value, and whether a symbolic value will
assume a default value if you fail to provide one.
Figure 14 shows a
sample sheet for a command procedure such as your installation may
provide you
r----------------------------------------------------------------------,
I
Command Procedure: LISTUPDT (member name)
I
Purpose: Update inventory list
I
Symbolic values:
I
WEEKIN
WEEKOUT
NEW
OUTPUT(*)
I
I
WEEKIN:
Required.
Replace with name of input data set.
I
WEEKOUT:
Required.
Replace with name of output data set.
I
NEW:
Optional.
Code NEW if output data set does not exist.
I
Omi t if output data set already exists.
I
OUTPUT<*):
Optional.
Directs reports prepared by procedure to
I
your terminal.
If you want to direct reports to a
I
data set, replace the
*
with the data set name.
If
I
OUTPUT is not specified, reports go to a central
I
printer.
L _____________________________________________________________________ J
Figure 14.
symbolic Values for a Command Procedure
After you decide which values you are going to replace for the required
symbolic values, and which optional symbolic values you are going to
use, enter the values in the
EXEC
command used. to call the procedure.
The values must follow the name of the
da
ta set or member that contains
the procedure.
If the procedure resides in a data set, enclose the
values in apostrophes.
The required values must be entered in the order
given to you.
Optional values can be entered in any order after you
enter the required val ues.
The following example calls the procedure
shown
in
Figure 14.
The name of the input data set is JP.W26IN.DATA.
'l'he name of the output data set is JP.W260UT.DATA.
The output data set
does not yet exist.
The reports produced by the command procedure are
directed to the JP.W26REP.DATA data set.
READY
listupdt
w26in
w260ut
output (w26rep)
new
Note:
If syntax errors or certain other error conditions arise in
executing a command within a procedure, the procedure will be terminated
and the remaining commands will not be executed.
Writing Command Procedures
FUnctions that are performed on a regular basis, such as calling a
compiler, can be simplified when the commands that perform the fUnctions
are kept as command procedures.
Once the commands are placed in a
partitioned or sequential data set or in a command procedure library (a
partitioned data set), any terminal user who wants to perform those
functions need only enter an EXEC command.
Command procedures contain commands and, optionally, subcoromands,
data and line numbers.
A command procedure may also contain command
procedure statements (PROC, WHEN, and END) that control execution of the
procedure.
The PROC statement defines symbolic values in the procedure,.
The WHEN statement initiates or terminates a procedure according to
certain conditions.
The END statement may be used to mark the end of
the procedure.
82
TSO Terminal User's Guide
(Release 21.7)
Advertisement
Table of Contents
