Adding applications
Next, you add some applications. For this exercise, you are going to create 3 applications: TSO, VTAM, and JES, because they are well-known applications. The policies that you create for them are fairly basic.
Procedure
-
Enter a 6 (or APL) on the Entry Type
Selection panel or =APL from any other panel in the Customization
Dialog. The APL Selection panel is displayed.
COMMANDS ACTIONS VIEW HELP ------------------------------------------------------------------------------ Entry Name Selection Entry Type : Application PolicyDB Name : TEST_PDB Enterprise Name : TEST_SYSTEMS Action Entry Name C Short Description ******************************* Bottom of data ******************************** No entries currently exist. Use the NEW command to create an entry. Command ===> _________________________________________________ SCROLL===> PAGE -
You are going to create 3 applications: TSO, VTAM, and JES, starting with TSO. To create the
TSO application, enter NEW TSO on the command line. You see a panel as
follows:
COMMANDS HELP ----------------------------------------------------------------------------- Define New Entry Command ===> _______________________________________________________________ More: + Define new entry of type Application Entry name . . . . . . . TSO Subsystem Name . . . . . ____________ Object Type . . . . . . INSTANCE (CLASS INSTANCE) Category . . . . . . . . _________ (IBM-defined, user-defined or blank, see help) Subcategory . . . . . . _________ (IBM-defined, user-defined or blank, see help) Job Type . . . . . . . . __________ (MVS NONMVS TRANSIENT) Job Name . . . . . . . . ____________________________ Transient Rerun . . . . __________ (YES NO) Scheduling Subsystem . . __________ (MSTR, JES Subsystem) JCL Procedure Name . . . ____________________________ Short Description . . . ________________________________________ Long Description 1 . . . _________________________________________________ Long Description 2 . . . _________________________________________________ Long Description 3 . . . _________________________________________________ Long Description 4 . . . _________________________________________________ Long Description 5 . . . _________________________________________________ -
Do not change the default entry name of TSO. Press Enter to complete the default entries. Edit
the entries, as required. While the other values default to acceptable values, it is better to enter
different values:
Table 1. Application Definition Panel Options. Field Description Subsystem Name The name by which automation knows the resource. It is better to keep it the same as your current job name because that is the name by which your operators know the resource. If your TSO runs as TSO, then use TSO as the automation name. If it currently runs as TCAS or anything else, then use that name. The only time that you might not want to do so is if the job name is different on each system. SA z/OS links the same application definition to multiple systems, but if you want a different automation name on each system, you either have to define separate applications for each system or you make use of the automation symbol (AOCCLONE) functionality of SA z/OS (recommended).
Object type Leave as INSTANCE for now. An object type of Class defines a set of common characteristics that can be inherited by multiple instances later on. Category Set one of the options that are listed, as SA z/OS provides some additional automation settings and options for these resources. Subcategory Set if you are setting the Application Type. The Subcategory is used to differentiate between the different parts of an IMS, Db2, or CICS product for example. Job Type For a normal address space, the job type is set to MVS. Job type NONMVS is specified when the APL represents, for example, a UNIX System Services process or a NetView REXX script.
TRANSIENTS are address spaces or jobs that shut down on their own. TRANSIENTS leave data installed and therefore it is not required to rerun them.
Job Name For subsystems of type MVS, job name is the name of the address space, as shown in an MVS D A,L command. Typically, the job name matches your subsystem name. For subsystems of type NONMVS, it is a unique qualifier to distinguish the subsystem from other subsystems. Transient Rerun Valid if the subsystem is defined as a transient and indicates whether SA z/OS can ever rerun the transient before the next system IPL. Scheduling Subsystem Set to MSTR for all of the address spaces that get started before JES. Leave blank for resources that run under the default JES subsystem. If you want to specify it for subsystems that run under JES, enter the proper JES z/OS® subsystem name, which is typically JES2 or JES3. JCL Procedure Name Name of the JCL procedure that is used to start the address space. If not specified, SA z/OS uses the following start command: S jobnameIf specified, the start command is:
S procname,JOBNAME=jobnameThis command runs an address space from the procedure with the specified job name. For help information, press PF1.
-
Press Enter to confirm your input and press PF3 to close the panel. You then see a
Policy Selection panel as follows:
ACTIONS HELP ------------------------------------------------------------------------------ Policy Selection Entry Selected Entry Type : Application PolicyDB Name : TEST_PDB Entry Name : TSO Enterprise Name : TEST_SYSTEMS Action Policy Name Policy Description _________ DESCRIPTION Enter description _________ UPWARD CLASS Select a class to inherit data from _________ APPLICATION INFO Define application information _________ AUTOMATION FLAGS Define application automation flags _________ APPLICATION SYMBOLS Define application symbols _________ TRIGGER Select trigger _________ SERVICE PERIOD Select service period _________ PACING GATE Select pacing gate _________ RELATIONSHIPS Define relationships _________ MESSAGES/USER DATA Define messages and user data _________ STARTUP Define startup procedures _________ SHUTDOWN Define shutdown procedures _________ THRESHOLDS Define error thresholds _________ MINOR RESOURCES Define application minor flags and thresholds _________ SYSTEM ASSOCIATION Define primary and secondary associations _________ -------------------- -----RESOURCES------------------------------- _________ GENERATED RESOURCES List resources generated for this entry _________ MEMBER OF List resources where this entry is a member _________ -------------------- --------------------------------------------- _________ WHERE USED List application groups linked to this entry _________ COPY Copy data from an existing entry ******************************* Bottom of data ******************************* Command ===> ________________________________________________ SCROLL===> PAGE -
Select the SHUTDOWN policy by entering an S next
to SHUTDOWN and press Enter. The Subsystem Shutdown
Processing panel for TSO is displayed.
COMMANDS HELP -------------------------------------------------------------------------- Subsystem Shutdown Processing Command ===> _____________________________________________________________ Entry Type : Application PolicyDB Name : TEST_PDB Entry Name : TSO Enterprise Name : TEST_SYSTEMS Shutdown Pass Interval. . (hh:mm:ss) Line Commands: S/C (Cmd), R (Rep) Cmd Phase Description Cmd Rep ___ INIT Executed when shutdown is initiated ___ NORM Executed when normal shutdown is invoked ___ IMMED Executed when immediate shutdown is invoked ___ FORCE Executed when force shutdown is invoked ___ FINAL Executed after final termination messageThis panel defines commands and replies that are issued before the application is shut down (INIT). This policy includes three increasingly aggressive shutdown command sequences (NORM, IMMED, and FORCE) and the commands that are issued after the application is shut down (FINAL).
-
For this exercise, define a NORM shutdown command. Select NORM by entering
C in the Cmd column and press Enter. If you are going
to specify a Reply, you type an R instead. The Command Processing:
SHUTNORM panel is displayed.
COMMANDS HELP ------------------------------------------------------------------------------ Command Processing : SHUTNORM Line 00000001 Col 001 075 Mixed case. . . NO (YES NO) Cmd Ps AutoFn/* Command Text ___ __ ________ _____________________________________________________________ ___ __ ________ _____________________________________________________________ ___ __ ________ _____________________________________________________________ ___ __ ________ _____________________________________________________________ ___ __ ________ _____________________________________________________________ ___ __ ________ _____________________________________________________________ ___ __ ________ _____________________________________________________________ ___ __ ________ _____________________________________________________________ ******************************* Bottom of data ******************************* Command ===> _______________________________________________ Scroll ===> PAGESA z/OS issues commands in passes (the Ps column). In the first pass, all the pass 1 commands are issued. SA z/OS then waits a while (the Shutdelay interval on the Application Information Policy panel) before it issues the pass 2 commands and waits again. TSO can be shut down, for example, in two passes. The first pass is an attempt to stop TSO with an MVS STOP command. If that does not succeed, the second pass uses the MVS CANCEL command. You define the processing on the panel as shown here.
-
For TSO, enter 1 for the pass, and MVS P TSO as
the command text.
Cmd Ps AutoFn/* Command Text ___ _1 ________ MVS P &SUBSJOB_______________________________________________ ___ __ ________ _____________________________________________________________ ___ __ ________ _____________________________________________________________ ___ __ ________ _____________________________________________________________Prefix the stop command with "MVS" because the commands are issued from inside the NetView. The MVS literal is required to direct the command out to the z/OS operating system.
The job name in the stop command is specified as &SUBSJOB rather than as TSO. &SUBSJOB is a symbolic value that SA z/OS substitutes with the application’s job name before it issues the command. If you ever change the job name, you can change it in one place rather than locating all occurrences of the old job name.
- Press PF3 three times to return to the Entry Name Selection panel.
-
For this exercise, define a NORM shutdown command. Select NORM by entering
C in the Cmd column and press Enter. If you are going
to specify a Reply, you type an R instead. The Command Processing:
SHUTNORM panel is displayed.
- Repeat this process (step 2-6) for VTAM® and JES with appropriate job and procedure names and shutdown commands. For JES, you need to enter the correct Category of JES2 or JES3 and specify a Scheduling Subsystem of MSTR like as follows:
COMMANDS HELP
------------------------------------------------------------------------------
Define New Entry
Command ===> __________________________________________________________________
More: +
Define new entry of type Application
Entry name . . . . . . . JES____________
Subsystem Name . . . . . JES____________
Object Type . . . . . . INSTANCE (CLASS INSTANCE)
Category . . . . . . . . JES2_______ (IBM-defined, user-defined or blank,
see help)
Subcategory . . . . . . ___________ (IBM-defined, user-defined or blank,
see help)
Job Type . . . . . . . . ___________ (MVS NONMVS TRANSIENT)
Job Name . . . . . . . . JES________
Transient Rerun . . . . _____ (YES NO)
Scheduling Subsystem . . MSTR (MSTR, JES Subsystem)
JCL Procedure Name . . . _____________
Short Description . . . ________________________________
Long Description 1 . . . ____________________________________________________
Long Description 2 . . . ____________________________________________________
Long Description 3 . . . ____________________________________________________
Long Description 4 . . . ____________________________________________________
Long Description 5 . . . ____________________________________________________-
When you finish defining these 3 applications, your Entry Name Selection
panel now looks as follows:
COMMANDS ACTIONS VIEW HELP ------------------------------------------------------------------------------ Entry Name Selection Row 1 to 3 of 3 Entry Type : Application PolicyDB Name : TEST_PDB Enterprise Name : TEST_SYSTEMS Action Entry Name C Short Description __________ JES __________ TSO __________ VTAM ******************************* Bottom of data ******************************* Command ===> _________________________________________________ SCROLL===> PAGE