How to Add/Remove Applications from System Automation Policy Database
Quick reference
- Overview
- Understanding the Policy Database
- Adding an Application to the Policy Database
- Deleting an Application from the Policy Database
- Activating Policy Changes
- Verifying Changes
- System Automation Command Quick Reference from SDSF
Overview
This guide provides step-by-step instructions for managing applications in the IBM Z System Automation Policy Database (PDB). The Policy Database contains automation policies that define how applications are monitored, started, stopped, and managed by System Automation.
Prerequisites:
- Access to the z/OS system with System Automation installed
- Authority to update the Policy Database
- Knowledge of the application being added/removed
- Familiarity with ISPF panels
System Information:
- Sysplex: LTEPLEX
- Policy Database: SYSAUTO.PDB
System Automation Components:
| STC Name | STC User | Description |
|---|---|---|
| AUTOPROC | AUTOPROC | System Automation Netview Agent server |
| AUTOMAN | AUTOMAN | System Automation manager server |
| AUTOSSI | AUTOSSI | System Automation subsystem interface |
Understanding the Policy Database
What is the Policy Database?
The Policy Database (PDB) is a file that contains:
- Application definitions
- Automation policies
- Dependency relationships
- Monitoring rules
- Recovery actions
Key Concepts
Application Group (AGP):
- Logical grouping of applications
- Simplifies management and monitoring
Application Resource (APL):
- Represents a started task, job, or subsystem
- Contains automation policies
- Defines monitoring and recovery behavior
Automation Policy:
- Defines how System Automation Policy manages the application
- Includes start/stop commands
- Specifies monitoring intervals
- Defines recovery actions
Dependencies:
- Relationships between applications
- Controls startup/shutdown order
- Ensures prerequisite applications are available
Adding an Application to the Policy Database
Step 1: Access the Policy Database Editor
-
Log on to TSO/ISPF
-
Navigate to the System Automation panels:
TSO SAOr from ISPF command line:
=SA -
Select option 1 - Edit the Policy Database
0 Settings User parameters BR Browse Browse the Policy Database 1 Edit Edit the Policy Database 2 Build Build functions for Policy Database 3 Report Generate reports from Policy Database 4 Policies Maintain Policy Database list 5 Data Management Import policies into a Policy Database U User User-defined selections X Exit Terminate Customization Dialog To switch to another Policy Database, specify the Policy Database name in the following field, or specify a ? to get a selection list. Current Policy Database . . . LTEPLEX_PDB
Step 2: Create a New Application Resource
-
Select option 6 APL Applications
Enter number or entry type or use "BR <entry type>" for browse 1 ENT Enterprise 30 TMR Timers 2 GRP Groups 32 TPA Tape Attendance 3 SBG SubGroups 33 MVC MVS Components 4 SYS Systems 34 MDF MVSCOMP Defaults 5 APG ApplicationGroups 35 SDF System Defaults 6 APL Applications 36 ADF Application Defaults 7 EVT Events 37 AOP Automation Operators 8 SVP Service Periods 38 NFY Notify Operators 9 TRG Triggers 39 NTW Networks 10 PRO Processors 40 XDF Sysplex Defaults 11 MTR Monitor Resources 41 RES Resident CLISTs 42 SCR Status Display 13 PAC Pacing Gates 50 DMN Remote Domains 51 REF Resource References 20 PRD Product Automation 21 MSG Messages 99 UET User E-T Pairs -
On Command line type Command ===> new
-
Fill in the Application Resource Definition panel:
Define new entry of type Application Entry name . . . . . . . MYAPP Subsystem Name . . . . . MYAPP Object Type . . . . . . INSTANCE (CLASS INSTANCE TEMPLATE) 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 . . . . . . . . MYAPP Transient Rerun . . . . (YES NO) Scheduling Subsystem . . (MSTR, JES Subsystem) JCL Procedure Name . . . Short Description . . . MYAPP Long Description 1 . . . Long Description 2 . . . -
PF3 to save the entry.
Step 3: Define Policy Selection
-
From the Application Resource panel, select:
Option 2 - Automation Policy -
Configure the Upward Class settings by placing a S on that line and hitting enter:
Entry Type : Application PolicyDB Name : LTEPLEX_PDB Entry Name : MYAPP Enterprise Name : LTEPLEX_PDB Action Policy Name Policy Description DESCRIPTION Enter description s UPWARD CLASS Select a class to inherit data from -
Attach C_APPL by placing a S and hit enter:
Entry Type : Application PolicyDB Name : LTEPLEX_PDB Entry Name : MYAPP Enterprise Name : LTEPLEX_PDB Action Status Entry Name Category Upward Class Link C_AM s C_APPL -
PF3 to save the changes.
-
Configure Application Info by placing a S and hit enter:
Entry Type : Application PolicyDB Name : LTEPLEX_PDB Entry Name : MYAPP Enterprise Name : LTEPLEX_PDB Action Policy Name Policy Description UPWARD CLASS Select a class to inherit data from s APPLICATION INFO Define application information -
Take Default by PF3 to save the changes.
Note: If the application is one from the below chart do not take defaults
Category Subcategory CICS AOR TOR FOR DOR QOR CMAS WUI DB2 MSTR SPAS IRLM DBM1 DIST WLMS ADMT IMS CTL TP DBRC DLS FP BMP FDR ITM KAHAGENT TEMS LIFELINE ADVISOR AGENT OPC CONTROLLER TRACKER SERVER DATASERVER -
Configure Relationship by placing a S:
Entry Type : Application PolicyDB Name : LTEPLEX_PDB Entry Name : MYAPP Enterprise Name : LTEPLEX_PDB Action Policy Name Policy Description 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 s RELATIONSHIPS Define relationships -
On Command line type Command ===> NEW and hit enter
-
Define the relationship:
Relationship Type. . HASPARENT MAKEAVAILABLE MAKEUNAVAILABLE PREPAVAILABLE PREPUNAVAILABLE HASPARENT HASPASSIVEPARENT HASMONITOR PEEROF FORCEDOWN EXTERNALLY Supporting Resource. JES2/APL/= -
PF3 to save changes.
-
PF3 to save relationship.
-
Configure Where used by placing a S and hitting Enter
Entry Type : Application PolicyDB Name : LTEPLEX_PDB
Entry Name : MYAPP Enterprise Name : LTEPLEX_PDB
Action Policy Name Policy Description
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
-------------------- ---------------------------------------------
s WHERE USED List application groups linked to this entry
- Place a S next to BASE_SYS and hit Enter
Entry Type : Application PolicyDB Name : LTEPLEX_PDB
Entry Name : MYAPP Enterprise Name : LTEPLEX_PDB
Action Status Name Type
s BASE_SYS APG
- PF3 to save the changes.
- PF3 to save all changes to policy before build.
- Activate the Policy Changes
Deleting an Application from the Policy Database
Step 1: Access the Policy Database Editor
-
Log on to TSO/ISPF
-
Navigate to the System Automation panels:
TSO SAOr from ISPF command line:
=SA -
Select option 1 - Edit the Policy Database
0 Settings User parameters BR Browse Browse the Policy Database 1 Edit Edit the Policy Database 2 Build Build functions for Policy Database 3 Report Generate reports from Policy Database 4 Policies Maintain Policy Database list 5 Data Management Import policies into a Policy Database U User User-defined selections X Exit Terminate Customization Dialog To switch to another Policy Database, specify the Policy Database name in the following field, or specify a ? to get a selection list. Current Policy Database . . . LTEPLEX_PDB
Step 2: Delete the Application Resource
-
Return to Application Resources Select option 6 APL Applications
Enter number or entry type or use "BR <entry type>" for browse 1 ENT Enterprise 30 TMR Timers 2 GRP Groups 32 TPA Tape Attendance 3 SBG SubGroups 33 MVC MVS Components 4 SYS Systems 34 MDF MVSCOMP Defaults 5 APG ApplicationGroups 35 SDF System Defaults 6 APL Applications 36 ADF Application Defaults 7 EVT Events 37 AOP Automation Operators 8 SVP Service Periods 38 NFY Notify Operators 9 TRG Triggers 39 NTW Networks 10 PRO Processors 40 XDF Sysplex Defaults 11 MTR Monitor Resources 41 RES Resident CLISTs 42 SCR Status Display 13 PAC Pacing Gates 50 DMN Remote Domains 51 REF Resource References 20 PRD Product Automation 21 MSG Messages 99 UET User E-T Pairs -
Locate the application to remove
-
Enter line command D (Delete) next to the application:
D MYAPP My Application Description -
Confirm the deletion when prompted, press ENTER:
Name : MYAPP Short description : Press ENTER to confirm delete of this entry. Press CANCEL or END to cancel delete. The following links exist in the WHERE USED policy: Name Type Short Description BASE_SYS APG Base z/OS, Network and Automation
Activating Policy Changes
After adding or removing applications, activate the changes:
Rebuild and Activate
Build Policy Database with the new Application
Step 1: Access the Policy Database for a Build
-
Log on to TSO/ISPF
-
Navigate to the System Automation panels:
TSO SAOr from ISPF command line:
=SA -
Select option 2 - Build functions for Policy Database
Step 2: Build a Complete Enterprise
- Select option 1 - Build a Complete Enterprise and hit enter:
Option ===> 1 1 Build a complete enterprise 2 Build sysplex group or stand alone system Sysplex / System name. . (*, ?, or name) 3 Build entry type or entry name Entry Type. . . . . . . . (*, ?, or type) Entry Name. . . . . . . . * (*, ?, or name) 4 View build report 5 Delete unused build output members Build options: Output Data Set . . . . 'SYSAUTO.PDB.SOCNTL.BUILD' Mode. . . . . . . . . . ONLINE (ONLINE BATCH) Type. . . . . . . . . . MODIFIED (MODIFIED ALL) Configuration . . . . . NORMAL (NORMAL ALTERNATE TERTIARY)Note: Type Modified, this is needed after the first build to make updates.
- To refresh the Automation Control file, submit the following sample jcl:
//BACKUP EXEC PGM=IEBCOPY //INLIB DD DSN=SYSAUTO.PDB.SOCNTL.BUILD,DISP=SHR //OUTLIB DD DSN=SYSAUTO.PDB.SOCNTL(+1), // UNIT=SYSDA, // DISP=(NEW,CATLG), // VOL=SER=LTECAT, // LIKE=SYSAUTO.PDB.SOCNTL.BUILD //SYSPRINT DD SYSOUT=H //SYSIN DD * COPY OUTDD=OUTLIB,INDD=INLIB //* - Issue a =sdsf on the command line to get to the console.
- Issue a
/%sae1 @refto dynamically take effect.
Verifying Changes
Verify Automation is Active
-
Issue the display command:
/%SAE1 DISPSTAT MYAPP -
Review the output:
Test Automation Behavior
-
Test Auto-Start:
- Stop the application manually:
%SAE1 SASTART MYAPP - Verify System Automation restarts it automatically
- Check the automation log for restart messages
- Stop the application manually:
-
Test Auto-Stop:
- Stop the application manually:
%SAE1 SASTOP MYAPP - Verify System Automation stops
- Stop the application manually:
System Automation Command Quick Reference from SDSF
| Command | Description |
|---|---|
/%SAE1 @ref | Refresh automation control file (dynamically activate changes) |
/%SAE1 SASTART <appname> | Start an application |
/%SAE1 SASTOP <appname> | Stop an application |
/%SAE1 DISPSTAT <appname> | Display status of an application |
/%SAE1 INGVOTE | Display outstanding votes |
IBM System Automation Documentation