Using And Writing Command Procedures; Using Command Procedures; Calling A Command Procedure - IBM System 360 User Manual

Operating system: time sharing option terminal
Hide thumbs Also See for System 360:
Table of Contents

Advertisement

Using and Writing Command Procedures
In many cases a given function is performed by a sequence of commands.
For example, several commands are needed to allocate data sets for a
compilation.
Every time you want to accomplish that function you must
enter the same sequence of commands, or else, you can simplify your work
by using a command procedure.
A command procedure is a set of TSO
commands, and, optionally, subcommands and data that have been placed in
a data set.
Whenever you want to accomplish the functions performed by
the command procedure you can use the EXEC command to call the
procedure.
The cOJIlITland procedure you call may c ontai n symbolic values.
A symbolic value stands as a symbol for an operand or the value of an
operand.
Symbolic values are used so that the command procedure can be
easily modified when it is called by the EXEC coremand.
This section consists of two parts.
The first part, "Using Command
Procedures", describes how to call a command procedure and how to assign
actual values to symbolic values.
The second part, "Writing Command
Procedures" describes how to write a command procedure and place it in a
data set.
Using Command Procedures
Use the EXEC command to call a command procedure and to assign values to
any symbolic values it may contain.
You will not get any prompting
messages once execution of the command procedure has begun.
CALLING A COMMAND PROCEDURE
To call a command procedure, enter an EXEC command.
In the EXEC command
you identify the command procedure in one of two ways:
1.
If the command procedure is in a data set, enter EXEC followed by
the name of the data set.
The following example, if your LOGON
identifier is JP, calls the command procedure that resides in the
JP.COMPROC.CLIST data set:
READY
exec
c omproc
Note that if you omit the descriptive qualifier the system assumes
CLIST.
If the descriptive qualifier is not CLIST you must enter
the fully qualified name enclosed in apostrophes.
For example, if
the command procedure resides in the
data
set JP.COMPROC.CP, you
must enter:
READY
exec 'jp.comproc.cp·
2.
If the command procedure resides in a member of a partitioned data
set called a command procedure library, enter only the member name.
(The command procedure library must have been defined by your
installation.>
The following example shows how to call the command
procedure in member PRoe 3 of your command procedure library:
READY
proc3
Using and Writing Command Procedures
81

Advertisement

Table of Contents
loading

Table of Contents