Creating a basic PDB
About this task
The first thing that you must do is to create a Policy database.
Procedure
- From the Automation Control for z/OS 1.1.1 Customization Dialog panel,
enter ? in the Current Policy Database field at the
bottom of the page and press Enter. Alternatively you may use option 4 Policies to get to the following panel:
MENU COMMANDS ACTIONS VIEW HELP ------------------------------------------------------------------------------ Policy Database Selection Row 1 of 23 Command ===> ________________________________________________ SCROLL===> PAGE Action Policy Database Enterprise Name ******************************* Bottom of data ******************************** PF 1=HELP 2=SPLIT 3=END 4=RETURN 5=RFIND 6=RCHANGE PF 7=UP 8=DOWN 9=SWAP 10=LEFT 11=RIGHT 12=RETRIEVE - To create a PDB, type the word new on
the command line and press Enter.
You now see a panel as follows:
COMMANDS ACTIONS HELP ------------------------------------------------------------------------------ Create a New Policy Database Row 1 of 1 Command ===> ____________________________________________________________ To define a new Policy Database, specify the following information: Policy Database Name . . __________________ Enterprise Name. . . . . __________________ Data Set Name. . . . . . ______________________________________ Model Policy Database. . *EMPTY______________ Policy Database name or "?" for list of names Add-on policies to be added to a standard SA model policy database: Action Status Add-on Policy Customizable ________ *BASE_AND_PRODUCTS YES ******************************* Bottom of data ******************************** PF 1=HELP 2=SPLIT 3=END 4=RETURN 5=RFIND 6=RCHANGE PF 7=UP 8=DOWN 9=SWAP 10=LEFT 11=RIGHT 12=RETRIEVE - The Policy Database Name field enters the name within the Customization Dialog if you must select or build the PDB. The value that is entered here must be a single word but may include @, $, #, ? and _ (underscore). TEST_PDB is recommended.
- The Enterprise Name field enters the name of your business or the section of it that you are going to define in the PDB. The value that you enter here must be a single word but may include underscores. TEST_SYSTEMS is recommended.
- The Data Set Name field enters the name of the data set on disk that holds the policy database. A useful convention is to have the name end with a .PDB extension, and to use the same name with a .SOCNTL extension for the Automation Control File that gets built from it. If you enter a value without single quotation marks, it is taken to be relative to your TSO user ID. If you enter a value with single quotation marks, it is taken as an absolute. For example, TEST.PDB might result in data set USER.TEST.PDB, while 'AUTO.TEST.PDB' results in a data set 'AUTO.TEST.PDB'. Use what you specified for sa_automation_policy in the INGDOPT Configuration Assistant Options file and put single quotation marks around it. The section at the bottom with the add-on policies adds the sample policies to your empty policy database.
- Enter C in front of it and press
Enter.
For the basic PDB, only the Base z/OS components and one of the JES subsystems are required.Select Add-on Policy Components Row 1 to 13 of 13 Command ===> ____________________________________________________SCROLL===> CSR Components of Add-on Policy : *BASE_AND_PRODUCTS Select one or more components to be added to your Policy Database: Action Status Component _______ SELECTED z/OS Health Checker _______ SELECTED Automation Command Receiver _______ SELECTED Automation RDS Archiver _______ SELECTED Base z/OS _______ SELECTED Communication Services (USS) _______ SELECTED CICS _______ SELECTED DB2 _______ SELECTED Event/Automation Service _______ SELECTED IMS _______ SELECTED Job Entry Subsystem 2 (JES2) _______ SELECTED Job Entry Subsystem 3 (JES3) _______ SELECTED OMEGAMON for z/OS _______ SELECTED Processor Operations (ProcOps) _______ SELECTED Tivoli Workload Scheduler (TWS) ******************************* Bottom of data ******************************* - To deselect all components, which are not required, specify M in front and press Enter. The SELECTED status is now only shown for Base z/OS and either for JES2 or for JES3. It depends what type of JES that you use on the target system.
- When finished, press PF3.
- Press Enter to review the contents of the New
Policy Database Dataset Information panel and press Enter
once more to create the policy.
After a few messages (you must press Enter to clear them), you find yourself on the Entry Type Selection panel for your new policy database:
Entry Type Selection Option ===> ___________________________________________________________________ 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 12 ENS zEnterprise Ensembles 42 SCR Status Display 13 PAC Pacing Gates 20 PRD Product Automation 99 UET User E-T Pairs 21 MSG Messages
Parent topic: Start IBM Automation Control for z/OS for the First Time