----------------------------- TSO COMMAND PROCESSOR -------------------------
ENTER TSO COMMAND OR CLIST BELOW:
===> timegame
ENTER SESSION MANAGER MODE ===> NO (YES or NO)
– On the COMMAND line of any ISPF/PDF panel as long as the member name
is preceded by "tso".
------------------------------ EDIT - ENTRY PANEL ---------------------------
COMMAND ===> tso timegame
ISPF LIBRARY:
PROJECT ===> PREFIX
GROUP ===> REXX ===> ===> ===>
TYPE ===> EXEC
MEMBER ===> TIMEGAME (Blank for member selection list)
OTHER PARTITIONED OR SEQUENTIAL DATA SET:
DATA SET NAME ===>
VOLUME SERIAL ===> (If not cataloged)
DATA SET PASSWORD ===> (If password protected)
PROFILE NAME ===> (Blank defaults to data set type)
INITIAL MACRO ===> LOCK ===> YES (YES, NO or NEVER)
FORMAT NAME ===> MIXED MODE ===> NO (YES or NO)
To reduce the search time for an exec that is executed implicitly and to differentiate
it from a TSO/E command, precede the member name with a %:
READY
%timegame
When a member name is preceded by %, TSO/E searches a limited number of
system files for the name, thus reducing the search time. Without the %, TSO/E
searches several files before it searches SYSEXEC and SYSPROC to ensure that
the name you entered is not a TSO/E command.
Exercises - Running the Example Execs
Create a PDS exec library using Checklist #1 or Checklist #2 in “Appendix A.
Allocating Data Sets” on page 185. Then try the example execs from the beginning
of this chapter. Run them explicitly with the EXEC command and see if the results
you get are the same as the ones in this book. If they are not, why aren’t they the
same?
Now write an exec to allocate your PDS to SYSPROC or SYSEXEC using Checklist
#3 on page 191 or Checklist #4 on page 192. Then run the example execs
implicitly. Which way is easier?
Running an Exec
18
z/OS V1R1.0 TSO/E REXX User’s Guide
To Next Page
Loading...
Need help?
General
