automation control: getting started - ibm · r elated documents. ibm automation control for z/os...

IBM Automation Control for z/OS

Getting StartedVersion 1 Release 1.1

SC34-2697-01

IBM

ii Automation Control: Getting Started

Contents

Figures . . . . . . . . . . . . . . . v

Tables . . . . . . . . . . . . . . . vii

About this publication . . . . . . . . ixIntended audience . . . . . . . . . . . . ixWhat this publication contains . . . . . . . . ixPublications . . . . . . . . . . . . . . x

IBM Automation Control for z/OS Library . . . xRelated publications . . . . . . . . . . . xAccessing terminology online . . . . . . . xiAccessing publications online . . . . . . . xiOrdering publications . . . . . . . . . . xii

Accessibility . . . . . . . . . . . . . . xiiService Management Connect . . . . . . . . xiiiTivoli technical training . . . . . . . . . . xiiiSupport information . . . . . . . . . . . xiiiConventions used in this publication . . . . . xiii

Typeface conventions . . . . . . . . . . xiiiPrivacy policy considerations . . . . . . . . xiv

Part 1. Overview . . . . . . . . . . 1

Chapter 1. Product Introduction . . . . 3Product Benefits . . . . . . . . . . . . . 3Automation Control components . . . . . . . 4System Operations Key Concepts . . . . . . . 5

Policy-based automation . . . . . . . . . 5Grouping Support . . . . . . . . . . . 6Goal driven automation . . . . . . . . . 6Relationships . . . . . . . . . . . . . 8

Chapter 2. Planning . . . . . . . . . 11Roles and Responsibilities . . . . . . . . . 11Planning for Automation Control . . . . . . . 12Deploying IBM Automation Control for z/OS . . . 12

Identify initial target systems . . . . . . . 12Establishing Naming Conventions . . . . . . 12Installing and deploying SMP/E . . . . . . 13Configuring the Target Systems. . . . . . . 13Building a Minimal Automation Policy . . . . 14Starting Automation Control and Verifying YourInstallation . . . . . . . . . . . . . 14Improving Your Automation Policy . . . . . 15Restarting Automation Control . . . . . . . 15Testing your Automation Policy . . . . . . 15Training your Operators . . . . . . . . . 15Expanding and Maintaining Your AutomationPolicy . . . . . . . . . . . . . . . 16

Additional Deployment Plans . . . . . . . . 16Planning worksheet . . . . . . . . . . . 16

Chapter 3. Installation andConfiguration . . . . . . . . . . . . 17Installing IBM Automation Control for z/OS . . . 17Configuring IBM Automation Control for z/OS . . 17

Preparing to Configure IBM Automation Controlfor z/OS . . . . . . . . . . . . . . 18

Start IBM Automation Control for z/OS for the FirstTime. . . . . . . . . . . . . . . . . 21

Quick planning exercise . . . . . . . . . 21Starting the Customization Dialog . . . . . . 22Creating a basic PDB . . . . . . . . . . 23Adapting the System Name . . . . . . . . 25Adapt Application Job Names . . . . . . . 26Changing System Defaults . . . . . . . . 28Building the Configuration Files . . . . . . 29Starting the Automation Manager . . . . . . 29Starting the Subsystem Interface Task. . . . . 30Starting the Automation Agent . . . . . . . 30Verification . . . . . . . . . . . . . 31

Chapter 4. Security . . . . . . . . . 33

Part 2. User Guide . . . . . . . . . 35

Chapter 5. Customization . . . . . . . 37Customization Tools . . . . . . . . . . . 37What is in a Policy Database? . . . . . . . . 38

Building Blocks . . . . . . . . . . . . 39Cloning Definitions . . . . . . . . . . . 41

Customization Dialog Tutorial . . . . . . . . 41Starting the Customization Dialog . . . . . . 41Getting Help . . . . . . . . . . . . . 42Creating an Empty PDB . . . . . . . . . 42Creating a System . . . . . . . . . . . 44Creating a Group . . . . . . . . . . . 46Adding Applications . . . . . . . . . . 47Relationships and Dependencies . . . . . . 53Application Groups. . . . . . . . . . . 55Reporting . . . . . . . . . . . . . . 57Adding More Systems . . . . . . . . . . 59Cloning with Symbolic Values . . . . . . . 59Defaults, Classes, and Inheritance . . . . . . 62

Adapt the Sample Policies . . . . . . . . . 64A New Policy Database . . . . . . . . . 64Adding Sample Policies . . . . . . . . . 67Bulk Update . . . . . . . . . . . . . 69Complete the Replication . . . . . . . . . 88Building your Policy . . . . . . . . . . 88

Chapter 6. Operations . . . . . . . . 93Console Operations. . . . . . . . . . . . 93

The Automation Manager’s Started Task. . . . 94The Automation Agent’s Started Task. . . . . 95

Operating Automation Control . . . . . . . . 97

© Copyright IBM Corp. 2014 iii

Automation Control . . . . . . . . . . 97Infrastructure . . . . . . . . . . . . . 99Resources . . . . . . . . . . . . . 101Monitoring Resources. . . . . . . . . . 111Starting and Stopping Resources . . . . . . 117Application Groups . . . . . . . . . . 122Automation Policy Management . . . . . . 127

Chapter 7. Processor HardwareInterfaces . . . . . . . . . . . . . 133Related Hardware Documentation . . . . . . 133Introduction and Overview. . . . . . . . . 133

Mainframes that are supported . . . . . . 133Scope of Control . . . . . . . . . . . 134Connectivity and Functionality at a Glance . . 134

Preparation and Configuration . . . . . . . 136Selecting the appropriate Interface to Use . . . 136Preparing the Autotasks . . . . . . . . . 137Enabling LPAR Management Startup . . . . 138Hardware Preparation . . . . . . . . . 139

Hardware Resource Security . . . . . . . . 139Customization . . . . . . . . . . . . . 139

CNMSTYLE customization . . . . . . . . 139Building Blocks. . . . . . . . . . . . 140

Mapping Processor Hardware Interface Items toCustomization Dialog . . . . . . . . . . 141Usage and Operation . . . . . . . . . . . 147

Operating the Processor Hardware Interfaces 147

HMC task mapping . . . . . . . . . . 148Other functions. . . . . . . . . . . . . 149

Chapter 8. Support . . . . . . . . . 151Modifying the Maximum Number of LanguageProcessor (REXX) Environments for NetView . . . 151Modifying the IEFUSI exit . . . . . . . . . 151Modifying the NetView Subsystem InterfaceProcedure . . . . . . . . . . . . . . 151

Changing Symbolic Variables . . . . . . . 151Specifying the Subsystem Command Designator 152

Saving Automation Manager data sets intoGeneration Data Groups. . . . . . . . . . 152Additional Configuration Considerations . . . . 153

Configuring the Operator Environment. . . . 153Working with Data Logs and Databases . . . 154

Part 3. Appendixes . . . . . . . . 155

Appendix. Automation productcomparison . . . . . . . . . . . . 157Summary of Differences with System Automationfor z/OS . . . . . . . . . . . . . . . 157Component View . . . . . . . . . . . . 157

Index . . . . . . . . . . . . . . . 161

iv Automation Control: Getting Started

Figures

1. Automation Control Single Point of Control 52. ForceDown Relationships . . . . . . . . 73. OnDemand Relationships . . . . . . . . 84. Application Relationships . . . . . . . . 95. Automation Policy Lifecycle . . . . . . . 376. Policy Database and SOCNTL Distribution 397. Simple Entry Structure . . . . . . . . . 408. Complex Entry Structure . . . . . . . . 419. Manager/Agent Overview in Automation

Control . . . . . . . . . . . . . . 93

10. z/OS Task Structure and the AutomationAgent . . . . . . . . . . . . . . 97

11. Operator Request Priorities to hold downResource . . . . . . . . . . . . . 119

12. Basic Group . . . . . . . . . . . . 12313. Move Group . . . . . . . . . . . . 12414. Server Group . . . . . . . . . . . 12515. Automation Policy Lifecycle . . . . . . 12816. Processor Hardware Interfaces . . . . . . 134

© Copyright IBM Corp. 2014 v

vi Automation Control: Getting Started

Tables

1. Worksheet for job names . . . . . . . . 212. Application Definition Panel Options. . . . . 493. Possible Job name values . . . . . . . . 594. Resource Types (partial list) . . . . . . . 1015. Resource Status Overview . . . . . . . 1046. Agent Status that indicates Automated

Recovery is pending . . . . . . . . . 1087. Statuses indicating Manual Intervention is

required . . . . . . . . . . . . . 1088. Selected Automation Control Message Classes 1149. Default Desired Status settings . . . . . . 117

10. Files maintained by the Automation Manager 12911. Actions for the different Automation Manager

start types . . . . . . . . . . . . 12912. Outline of an SOCNTL Naming Scheme 13013. HMC Operation Management Tasks . . . . 13614. Required Hardware Setup Tasks . . . . . 13715. Required Software Setup Task List . . . . 13716. Processor Hardware Interface Items . . . . 14217. HMC Operations Management Tasks 14818. Component View of Automation Control 158

© Copyright IBM Corp. 2014 vii

viii Automation Control: Getting Started

About this publication

IBM Automation Control for z/OS describes new single system automation forz/OS systems that are defined as monoplexes or as members of sysplexes. Thetechnology is based on the existing technologies of System Automation for z/OSand NetView for z/OS. This publication, IBM Automation Control for z/OS GettingStarted provides information about installing, configuring, securing, customizing,and operating automation software.

Intended audienceThis publication is for automation programmers, operators, and systemprogrammers who install and configure automation software.

What this publication containsThis publication contains the following sections:

Part I—Overview

Part I contains the following chapters:v Chapter 1, "Product Introduction"

Provides an introduction to IBM Automation Control for z/OSv Chapter 2, "Planning"

Describes a planning process for working with IBM Automation Control forz/OS

v Chapter 3,"Installation and Configuration"Describes the installation and configuration processes for IBM AutomationControl for z/OS

v Chapter 4, "Security"Describes the security functionality for IBM Automation Control for z/OS

Part II—User Guide

Part II contains the following chapters:v Chapter 5, "Customization"

Describes the customizing processes for automation models available within IBMAutomation Control for z/OS

v Chapter 6, "Operations"Describes how to operate a customer automation model within IBM AutomationControl for z/OS

v Chapter 7, "Processor Hardware Interfaces"Describes how to use the Processor Hardware Interfaces available with IBMAutomation Control for z/OS

v Chapter 8, "SupportDescribes additional support procedures for a full integration of IBMAutomation Control for z/OS

Part III—Appendixes

© Copyright IBM Corp. 2014 ix

Part III contains the following appendix:v Appendix A, "Automation Component Comparison"

Review a range of automation software functionality with IBM automationproducts in Appendix A

PublicationsThis section lists publications in the IBM Automation Control for z/OS library andrelated documents.

IBM Automation Control for z/OS LibraryThe following documents are available in the Automation Control library:v IBM Automation Control for z/OS Getting Started, SC34-2697-01

Provides information about installing, configuring, and customizing the IBMAutomation Control for z/OS product.

Related publicationsThe following documents are available in the IBM System Automation for z/OSlibrary:v IBM System Automation for z/OS Planning and Installation Guide, SC34-2716,

describes how to install System Automation for z/OS.v IBM System Automation for z/OS Customizing and Programming Guide, SC34-2715,

describes how to customize and fine-tune the automation facilities of SystemAutomation for z/OS.

v IBM System Automation for z/OS Defining Automation Policy, SC34-2717, describeshow to create complex automation models in System Automation for z/OS.

v IBM System Automation for z/OS User’s Guide, SC34-2718, describes the conceptsand how to use the System Automation for z/OS product for complexautomation facilities.

v IBM System Automation for z/OS Messages and Codes Manual, SC34-2719, describesthe messages for the System Automation for z/OS product, and other sense,condition, or reason codes that are included.

v IBM System Automation for z/OS Operator’s Commands, SC34-2720, describes theoperator commands available with the System Automation for z/OS product.

v IBM System Automation for z/OS Programmer’s Reference, SC34-2721, describes theprogramming routines available with the System Automation for z/OS product.

v IBM System Automation for z/OS Product Automation Guide, SC34-2714, describesproduct automation and integration for CICS, DB2 and IMS in the SystemAutomation for z/OS product.

v IBM System Automation for z/OS TWS Automation Guide, SC34-2722, describesTWS automation working with System Automation for z/OS.

v IBM System Automation for z/OS End-to-End Adapter, SC34-2723, describes theEnd-to-End Adapter working with System Automation for z/OS.

v IBM System Automation for z/OS Monitoring and Configuration Agent Guide,SC34-2724, describes extra configuration of the monitoring tools and agents thatwork with System Automation for z/OS.

The following documents are available in the IBM® Tivoli® NetView® for z/OS®

library:v Installation: Getting Started, GI11-9443, describes how to install and configure the

base NetView functions.

x Automation Control: Getting Started

v Administration Reference, SC27-2869, describes the NetView program definitionstatements that are required for system administration.

v Automation Guide, SC27-2846, describes how to use automated operations toimprove system and network efficiency and operator productivity.

v Command Reference Volume 1 (A-N), SC27-2847, describe the NetView commands,which can be used for network and system operation and in command lists andcommand procedures.

v Command Reference Volume 2 (O-Z), SC27-2848, describe the NetView commands,which can be used for network and system operation and in command lists andcommand procedures.

v Messages and Codes Volume 1 (AAU-DSI), GC27-2856, and Messages and CodesVolume 2 (DUI-IHS), GC27-2857, describe the messages for the NetView product,the NetView abend codes, the sense codes that are included in NetViewmessages, and generic alert code points.

v Messages and Codes Volume 2(DUI-IHS), GC27-2857, and Messages and CodesVolume 1 (AAU-DSI), GC27-2856, describe the messages for the NetViewproduct, the NetView abend codes, the sense codes that are included in NetViewmessages, and generic alert code points.

v Programming Pipes, SC27-2859, describes how to use the NetView pipelines tocustomize a NetView installation.

v Programming: REXX and the NetView Command List Language, SC27-2861, describeshow to write command lists for the NetView product with the RestructuredExtended Executor language (REXX) or the NetView command list language.

v Security Reference, SC27-2863, describes how to implement authorization checkingfor the NetView environment.

v Troubleshooting Guide, GC27-2865, provides information about documenting,diagnosing, and solving problems that occur in the NetView product.

v Tuning Guide, SC27-2874, provides tuning information to help achieve certainperformance goals for the NetView product and the network environment.

v User’s Guide: NetView, SC27-2867, describes how to use the NetView product tomanage complex, multivendor networks and systems from a single point.

Accessing terminology onlineThe IBM Terminology website consolidates the terminology from IBM productlibraries in one convenient location. You can access the Terminology website athttp://www.ibm.com/software/globalization/terminology

Accessing publications onlineThe format of the publications is PDF, HTML, or both. To access the publicationsusing a web browser, use the IBM Automation Control for z/OS KnowledgeCenter, and the System Automation for z/OS and NetView for z/OS KnowledgeCenters.

IBM posts publications for this and all other Cloud and Smarter Infrastructureproducts, as they become available and whenever they are updated, to theKnowledge Center at http://www-01.ibm.com/support/knowledgecenter/.

Note: If you print PDF documents on other than letter-sized paper, set the optionin the File → Print window that allows Adobe Reader to print letter-sized pages onyour local paper.

About this publication xi

http://www.ibm.com/software/globalization/terminology

http://www-01.ibm.com/support/knowledgecenter/

(artname: sout.gif) IBM System Automation for z/OS Knowledge Center

(artname: sout.gif) IBM Tivoli Netview for z/OS Knowledge Center

Ordering publicationsYou can order many Tivoli publications online at http://www.ibm.com/e-business/linkweb/publications/servlet/pbi.wss.

You can also order by telephone by calling one of these numbers:v In the United States: 800-879-2755v In Canada: 800-426-4968

In other countries, contact your software account representative to order Tivolipublications. To locate the telephone number of your local representative, performthe following steps:1. Go to http://www.ibm.com/e-business/linkweb/publications/servlet/pbi.wss2. Select your country from the list and click Go.3. Click About this site in the main panel to see an information page that

includes the telephone number of your local representative.

AccessibilityAccessibility features help users that have a disability, such as restricted mobilityor limited vision, to use information technology products successfully.

Document Accessibility

The IBM Automation Control for z/OS Information Center is compliant withaccessibility standards. The publication is also offered in Adobe Portable DocumentFormat (PDF) and should also be compliant with accessibility standards. If youexperience difficulties when use the PDF file, send an email to [email protected],or write to the following address:

IBM Deutschland Research & Development GmbH,Department 3282,Schoenaicher Strasse 220,D-71032 Boeblingen,Federal Republic of Germany

In the request, ensure that you include the publication number and title. When yousend information to IBM, you grant IBM a nonexclusive right to use or distributethe information in any way it believes appropriate without incurring anyobligation to you.

IBM and Accessibility

See the IBM Human Ability and Accessibility Center for more information aboutthe commitment that IBM has to accessibility at http://www.ibm.com/able.

xii Automation Control: Getting Started

http://www-01.ibm.com/support/knowledgecenter/SSWRCJ_3.5.0/

http://pic.dhe.ibm.com/infocenter/tivihelp/v3r1/index.jsp?topic=%2Fcom.ibm.itnetviewforzos.doc%2Fic-homepage.html

http://www.ibm.com/e-business/linkweb/publications/servlet/pbi.wss



http://www.ibm.com/able

Service Management ConnectConnect, learn, and share with Service Management professionals: product supporttechnical experts who provide their perspectives and expertise.

Access Service Management Connect at https://www.ibm.com/developerworks/servicemanagement/. Use Service Management Connect in the following ways:v Become involved with transparent development, an ongoing, open engagement

between other users and IBM developers of Tivoli products. You can access earlydesigns, demonstrations, product roadmaps, and prerelease code.

v Connect one-on-one with the experts to collaborate and network about Tivoliand the (enter your community name here) community.

v Read blogs to benefit from the expertise and experience of others.v Use wikis and forums to collaborate with the broader user community.

Tivoli technical trainingFor Tivoli technical training information, see the IBM Tivoli Education website athttp://www.ibm.com/software/tivoli/education.

Support informationIf you have a problem with your IBM software, you want to resolve it quickly. IBMprovides the following ways for you to obtain the support you need:

OnlineAccess the IBM Software Support site at https://www.ibm.com/support/home/.

IBM Support AssistantThe IBM Support Assistant is a free local software serviceability workbenchthat helps you resolve questions and problems with IBM softwareproducts. The Support Assistant provides quick access to support-relatedinformation and serviceability tools for problem determination. To installthe Support Assistant software, go to http://www.ibm.com/software/support/isa.

Conventions used in this publicationSeveral conventions are used in this publication for special terms, actions,commands, and paths that are dependent on your operating system.

Typeface conventionsThis publication uses the following typeface conventions:

Bold

v Lowercase commands and mixed case commands that are otherwisedifficult to distinguish from surrounding text

v Interface controls (check boxes, push buttons, radio buttons, spinbuttons, fields, folders, icons, list boxes, items inside list boxes,multicolumn lists, containers, menu choices, menu names, tabs, propertysheets), labels (such as Tip:, and Operating system considerations:)

v Keywords and parameters in text

Italic

About this publication xiii

https://www.ibm.com/developerworks/servicemanagement/

https://www.ibm.com/developerworks/servicemanagement/

http://www.ibm.com/software/tivoli/education

https://www.ibm.com/support/home/

https://www.ibm.com/support/home/

http://www.ibm.com/software/support/isa

http://www.ibm.com/software/support/isa

v Citations (examples: titles of publications, diskettes, and CDsv Words defined in text (example: a nonswitched line is called a

point-to-point line)v Emphasis of words and letters (words as words example: "Use the word

that to introduce a restrictive clause."; letters as letters example: "TheLUN address must start with the letter L.")

v New terms in text (except in a definition list): a view is a frame in aworkspace that contains data.

v Variables and values you must provide: ... where myname represents....

Monospace

v Examples and code examplesv File names, programming keywords, and other elements that are difficult

to distinguish from surrounding textv Message text and prompts addressed to the userv Text that the user must typev Values for arguments or command options

Bold monospace

v Command names, and names of macros and utilities that you can typeas commands

v Environment variable names in textv Keywordsv Parameter names in text: API structure parameters, command

parameters and arguments, and configuration parametersv Process namesv Registry variable names in textv Script names

Privacy policy considerationsIBM Software products, including software as a service solutions, (“SoftwareOfferings”) may use cookies or other technologies to collect product usageinformation, to help improve the end user experience, to tailor interactions withthe end user or for other purposes. In many cases no personally identifiableinformation is collected by the Software Offerings. Some of our Software Offeringscan help enable you to collect personally identifiable information. If this SoftwareOffering uses cookies to collect personally identifiable information, specificinformation about this offering’s use of cookies is set forth below.

This Software Offering does not use cookies or other technologies to collectpersonally identifiable information.

If the configurations deployed for this Software Offering provide you as customerthe ability to collect personally identifiable information from end users via cookiesand other technologies, you should seek your own legal advice about any lawsapplicable to such data collection, including any requirements for notice andconsent.

For more information about the use of various technologies, including cookies, forthese purposes, See IBM’s Privacy Policy at http://www.ibm.com/privacy andIBM’s Online Privacy Statement at http://www.ibm.com/privacy/details thesection entitled “Cookies, Web Beacons and Other Technologies” and the “IBM

xiv Automation Control: Getting Started

http://www.ibm.com/privacy

http://www.ibm.com/privacy/details

Software Products and Software-as-a-Service Privacy Statement” athttp://www.ibm.com/software/info/product-privacy.

About this publication xv

http://www.ibm.com/software/info/product-privacy

xvi Automation Control: Getting Started

Automation Control for z/OS 1.1.1

Welcome to the IBM Automation Control for z/OS documentation, where you canfind information about how to install, maintain, and use the IBM AutomationControl for z/OS.

Getting started

Product IntroductionIBM® Automation Control for z/OS® (Automation Control) providesautomation and easier operation of z/OS and UNIX System Services (USS)applications and resources, processor hardware, and zEnterprise™ BladeCenters.

(artname: pdf.gif) Product Manual and Program Directory (PDFs)Common tasks

PlanningInstallingConfiguringThe configuration of this product is supported by the Configuration Assistant.Troubleshooting and support

(artname: sout.gif) IBM Software Support home pageMore information

(artname: sout.gif) Subscribe IBM Z Software – Operations and Managementedition

© Copyright IBM Corp. 2014 xvii

http://www.ibm.com/support/entry/portal/overview/software/software_support_(general)

http://www.pages02.net/ibm-zsystemsservices/itsm/subscribe/

http://www.pages02.net/ibm-zsystemsservices/itsm/subscribe/

xviii Automation Control: Getting Started

Product Manual and Program Directory (PDF)

You can download the Automation Control manual as a PDF:

IBM Automation Control for z/OS 1.1.1Getting Started

ACzos_GettingStarted.pdf

Program Directory ACzos_ProgramDirectory.pdf

© Copyright IBM Corp. 2014 xix

xx Automation Control: Getting Started

Automation Control for z/OS

IBM Automation Control for z/OS describes new single system automation forz/OS systems that are defined as monoplexes or as members of sysplexes.

© Copyright IBM Corp. 2014 xxi

xxii Automation Control: Getting Started

Part 1. Overview

Refer to this information for an understanding of the benefits, the functionality andthe security of the Automation Control for z/OS product.

© Copyright IBM Corp. 2014 1

2 Automation Control: Getting Started

Chapter 1. Product Introduction

IBM Automation Control for z/OS (Automation Control) provides automation andeasier operation of z/OS and UNIX System Services (USS) applications andresources, processor hardware, and zEnterprise™ BladeCenters.

IBM Automation Control for z/OS is based on the advanced automationtechnologies of System Automation and NetView® for z/OS.

This IBM Automation Control for z/OS Getting Started manual can help you preparefor work with this new automation product, starting with early planning,configuring the product, making it secure, showing you how to customize yourautomation environment. This manual also describes the basic operational tasksthat you perform on a daily basis.

Given the breadth of capabilities, all of the above can be explained only briefly. Forfurther reading and reference purposes, consult the associated product libraries forSystem Automation and NetView for z/OS.

Although the subject of the book is IBM Automation Control for z/OS, referencesto System Automation for z/OS and NetView for z/OS cannot be avoidedcompletely. When such references are used in text, examples, or illustrations, keepin mind that they are used to denote technology from those products that is usedin the IBM Automation Control for z/OS product.

Product BenefitsThe following product benefits and services are provided by Automation Control:v Policy-based automation that helps reduce complexity, implementation time,

coding, support effort, and can replace scriptsv Sample add-on policy using best practices that can be included based on your

needs (Plug and Play)v Access to industry-standard sample automation policies for customers in small

or medium-sized enterprisesv Avoids manual policy customization by providing autodiscovery of your

systemsv Comprehensive automation for z/OS, IMS™, CICS®, DB2®, Tivoli® Workload

Scheduler, and Tivoli OMEGAMON® XE on z/OSv Simplified operations by goal-driven automation to keep applications in line

with business goalsv Reduced complexity and management at the business application level by

grouping of resourcesv Accelerated startup and shutdown, and correct recovery by managing

relationships between resourcesv Faster time to value through the Configuration Assistant for the runtime

environmentv A single point of control for a limited number of systems in a sysplexv Enables proactive automation that is based on performance data from Tivoli

OMEGAMON for XE on z/OS to help fix performance or availability problemsbefore they cause an outage


v Allows the detection of problems simply and quickly through the IBM TivoliEnterprise Portal topology view

v Higher degree of automation through automation that is based on joblogmessages

v Visualization, control and automation of local IBM System z® or IBM zEnterprisehardware that includes BladeCenters, virtual hosts, and virtual servers

v Integration with Tivoli Enterprise solutions that include IBM Tivoli Monitoring,IBM Tivoli Workload Scheduler, and Tivoli System Automation for IntegratedOperations Management

Automation Control componentsAutomation Control is a single package that inherits functionality from IBM’spremier automation products: NetView for z/OS providing the automationplatform. Also, System Automation for z/OS that provides solutions for automatedoperations of both software and hardware.

The NetView for z/OS product provides basic message automation capabilities,access to logs, and the platform for the System Automation solutions.

System Operations is based on System Automation for z/OS. System Operationsprovides an Automation Manager, which runs as a separate address space and anAutomation Agent that runs on the NetView platform. The two components areresponsible for managing the automated startup and recovery of your z/OSapplications within a single z/OS system.

Processor Operations is based on System Automation for z/OS. ProcessorOperations runs on the NetView platform and controls the logical partitions,system images, blades, and virtual processors on the local processor, that is, IBMSystem z or IBM zEnterprise® with the optionally attached zEnterprise BladeCenterExtension. You can perform initial program load (IPL), set the time of day clock,respond to hardware messages, monitor hardware status, and detect and resolvewait states. Together these product pieces provide the functional components thatare shown in Figure 1 on page 5. These are the components:v Automation Agent: Observes, reacts, and performs the combined manager/agent

solution for automated operations of software. It runs on the NetView platformand it is responsible for the following functions for the applications that run onz/OS:1. Start2. Stop3. Restart and recovery and4. Event and Status Monitoring

v Automation Manager: Coordinates and controls part of the combinedmanager/agent solution for automated operations of software. AutomationManager runs in a separate address space and takes actions that are based onthe current goals for automation.

v Customization Dialog: An ISPF application that creates an automation policyand customizes all resources to be automated through System Operations orthrough the hardware interfaces. The configuration files that are built by thedialog contain the artifacts that are required by both the Automation Managerand the Automation Agent for automated operation purposes.


System Operations Key Concepts

Policy-based automationPolicy-based automation focuses on separating your business and operationalpolicies from the mechanics of actually performing the automation according to thepolicies. Policy-based automation focuses on setting your policies and AutomationControl deals with implementing them.

Automation Control policy-based automation includes resource information,groups of resources, and relationships in the decision-making process before acting.Resource information defines resource class and name, as well as how to start,stop, and monitor the resource. Resources can be members of system-wide groupsand relationships.

The power of a policy

v You are able to define automation requirements easily:In a policy, you can define which resources belong together and are managed asone (business entity). For example, a DB2 System consists of many resources.With Automation Control, you can group and aggregate resources to moremeaningful manageable entities, for example, My-HumanResource-Applicationand so forth. You can monitor on this level, issue commands on this level, andmanage at the business level rather than at the single IT resource level.

v In policies, you can specify how resources are dependent and related to eachother. For example, which of the other resources must be available before acertain resource can be started. In another example, my database must be upand running before my application is started.

v Policy definitions can be reused, copied, and cloned for similar applicationselsewhere in the enterprise.

Custo

miz

ation D

ialo

g

AutomationManager

Single point

of control

on Status

Display Facility

Override goals in automation policy

Automation Policy

DependencyManagementOrders

Status

StartStopRestart / Recover Automation

Agent

Events StatusMonitoring

Processor HW Interfaces

Apps

(artname: automationcomponents.gif)Figure 1. Automation Control Single Point of Control

Chapter 1. Product Introduction 5

v Because the underlying technology is responsible for the detailed actions, theseactions are performed in a consistent and reliable manner. With traditionalprogramming solutions, the testing of abnormal conditions is difficult and proneto be incomplete. The action of automation under these abnormal conditions is,however, critical to the entire automation solution.

The Sample Add-on policy includes automation modules for base operatingsystem, major middleware, and systems management software. Today’s wide rangeof add-on policies are based on best practices and can help reduce time and effortin creating a policy or updating one.

Another possibility to populate your policy is by using the autodiscovery function.If you use this method, the data of all your address spaces that include the UNIXSystem Services are gathered on your system.

Grouping SupportModern applications are often composed of many components, such as dataservers, networking, and security components. In Automation Control, you canmonitor and automate on the group level.

For example, to have all applications in an application group available, rather thaneach application individually, instruct Automation Control to keep the applicationgroup available.

Groups can be nested and can have dependencies. A group’s status is aggregatedfrom its members’ status. There are three types of groups: BASIC, MOVE, andSERVER.

BASICIn a BASIC application group, all of its components must be availablebefore the group is considered to be available.

MOVEIn a MOVE application group, exactly one of its components must beavailable before the group is considered to be available. In MOVE groups,you can specify alternative components to start if their primary componentfails to start.

SERVER In a SERVER application group, any number of components can bespecified that must be available before the group is considered to beavailable. In SERVER groups, you can specify what happens if theircomponents fail to start.

Groups can be created for grouping only without any additional capability, formonitoring, and for automation. The first type of a group is used to link resourcesto a system when they are not in any other group for other reasons. Simple groupscan be for any type of group that is listed.

Goal driven automationThe Automation Agent knows how to perform a limited number of actions againsteach application, usually just Start and Stop.

In order to complete a complex action, such as recovering from the failure of anapplication, many actions have to be undertaken in quite a complex sequence. Forexample, you cannot restart the resources dependent upon the database until the


database itself is restarted, which in turn cannot happen until all of the resourcesthat were dependent upon the failed resource are brought down.

Rather than having these sequences of actions that are coded as a fragile script,Automation Control computes the sequence of actions that are required to performthe recovery from its goals and its knowledge of the interdependencies betweenthe resources. If something unexpected happens during the recovery, AutomationControl dynamically recomputes its recovery plan and smoothly moves topursuing it.

Automation Control manages and recovers through goal driven automation. Thereare major goals, set through default Desired status values, schedules, and operatorrequests and minor goals, set as the Desired status on each resource. In response tothe major goals, it computes the current Desired status for each resource. If theresource is not in its Desired state, it simply waits until its dependencies aresatisfied and then tells the agent to start or stop it as appropriate. How long doesit wait? As long as it takes the dependent resources to be brought into compliancewith its goal state. If it is impossible to start the dependent resources, it tells theoperator and, if one is available, switches to using an alternate resource or set ofresources.

Consider this simple scenario that is illustrated in Figure 2:

If resource B fails, Automation Control first stops resource C, then restarts resourceB before it restarts resource C. The only major goal during this scenario is forresource C to be Available, and that is probably an implicit one.

Now consider this scenario that is illustrated in Figure 3 on page 8:

A/APLHasParent

B/APL

C/APL

HasParent

ForceDown

(artname: goal_forcedown.gif)Figure 2. ForceDown Relationships


At 7:00 p.m., the Prime schedule changes from setting an Available goal to settingan Unavailable goal. Then, Automation Control shuts down resource E, thenresource D and finally resource C. Why? Because C and D are defined as onlyneeding to be running when there is a demand for them to be run. With resource Eshut down, they are no longer needed. At 11:00 p.m. when the schedule changesagain and switches back to setting an Available goal, resources C, D, and E arerestarted, in that order.

RelationshipsMost resources are dependent on services that are provided by some otherresources. Almost everything uses JES, the VTAM® product, or TCPIP, for example.

These dependencies are modeled in your policy as Relationships. Each relationshipexpresses something of the nature of the dependency that it describes such as,HasParent, MakeAvailable, PrepareUnavailable, and so forth.

Relationships can be active or passive. Active relationships propagate goals forresources across the dependency. Passive relationships do not. Have AutomationControl start TSO and it propagates the request across its active relationship to theVTAM product and then to JES.

Resources sometimes depend on other resources such as start and stop sequences.Automation Control uses relationships for the specification of dependencies. Anactive relationship generates automatic propagation of availability requests tosupporting resources if dependent resources are to be made available.

Relationships can be specified together with a condition that must be satisfied forthe supporting resource. The specified action first must be processed for thedependent resource. Several action/condition combinations for dependencies aresupported by Automation Control.

When Automation Control starts a resource, it waits until all of the necessaryconditions to do so are satisfied. Typically, you wait until all of the supportingresources for starting it are up. Relationships expressing a condition for stoppingthe resource are ignored.

A/APLHasParent

B/APL

C/APL

D/APL

E/APL

HasParent

HasParent

HasParent

OnDemand

OnDemand

Prime Schedule

(artname: goal_ondemand.gif)Figure 3. OnDemand Relationships


After the resource starts, Automation Control no longer must perform a start actionagainst it and ignores its dependencies. If one of its supporting resources fails, noaction is taken against the dependent resource, unless it also failed as aconsequence. If you want Automation Control to act, you can add a ForceDownrelationship, for example. This relationship definition sets a temporary goal inAutomation Control to bring the dependent resource down if the condition on theForceDown relationship becomes satisfied.

Figure 4 shows the dependencies that a CICS application has on other resources.First, the CICS application depends on the CICS product itself. A HasParentrelationship is used to express the fact that, the CICS product must be up andrunning before the CICS application can be started.

Likewise, this relationship also expresses the fact in order to stop CICS, and alsoits children, here the CICS application must be stopped first. Relationships can beexpressed on multiple levels. Much like the CICS application has a dependency onCICS, so has CICS to VTAM. Again, a HasParent relationship is used to expressthis kind of dependency.

Through Automation Control, you configure relationships in a flexible manner. Youexpress a particular behavior in a robust manner that would otherwise be hard toput in scripted code.

CICSapplication

CICS

VTAM

HasParent

HasParent

Start

(artname: relationships1.gif)Figure 4. Application Relationships


Chapter 2. Planning

As with any other software product, successful deployment and use of IBMAutomation Control for z/OS depends on planning and preparedness. Workthrough a process of planning for your first Automation Control deployments.

Roles and ResponsibilitiesThis information is written from the point of view of the person responsible foroverseeing the successful installation and deployment of Automation Control. Thisperson is typically called an automation programmer or automation administrator.The term automation programmer is used in this information.

The automation programmer is responsible for the listed actions:v Understanding the capabilities and requirements of Automation Controlv Negotiating an initial plan for installation and deployment to one or more test

systems. Subsequent plans are needed to deploy it to more test and productionsystems

v Using the Automation Control Customization Dialog to model the resources andautomation policies on the systems that Automation Control is going toautomate

v Activating the Automation Control programs to load the policy the automationprogrammer defines and tests

v Educating the operators about how to best work with Automation Controlv Refining, updating, and maintaining the automation policy for the systems that

Automation Control is deployed to.

During this process (which is expected to take several days) the assistance of anumber of other individuals within their organization is required:

System Programmers

System programmers have low-level access to the operating system, are able to runSMP/E installations, install procedures and programs and move data. Systemprogrammers do all these tasks.

Capacity Planners

Capacity planners know how much space and spare compute capacity is availableon the customers’ systems and are responsible for the timely provision of morecapacity. Capacity planners must incorporate the deployment of AutomationControl into their plans.

Security Administrators

Security administrators define and maintain the security databases on thecustomers’ systems. Security administrators are needed to create profiles anddefine permissions so that Automation Control can be used.

Operators


Operators are the ultimate users of Automation Control, managing the computersystems that Automation Control is installed on. Operators are responsible for anymanual operations that are required for the computer system, including recoveringfrom any problems or failures that occur. Automation Control automates their basicduties, so the users must learn how to work with it to accomplish their goals.

Planning for Automation ControlAutomation Control has three major components: the Customization Dialog,System Operations (SysOps), and Processor Operations (ProcOps). While there issome commonality in the planning for these components, there are also some stepsthat are unique to each component.

For the purposes of the chapter, it is assumed that you are installing theCustomization Dialog and only SysOps for Automation Control. If you want todeploy ProcOps, review the IBM System Automation for z/OS Planning andInstallation Guide.

Deploying IBM Automation Control for z/OS

Identify initial target systems

About this task

Who: Automation programmer, system programmer, capacity planner

Procedure1. Identify the system where the system programmer runs the SMP/E installation

of IBM Automation Control for z/OS. For more information, see the ProgramDirectory.

2. Identify the system where the automation programmer runs the CustomizationDialog. The system must have TSO access, and access to several cylinders ofdisk storage. The amount of storage depends on the size of the policy. For aninstallation with 3 systems, 20 cylinders at minimum are preferable. Runningthe Customization Dialog does not influence the operation of the system it runson. A reasonable system availability is recommended so that the CustomizationDialog can be used as required.

3. Identify the system or systems that Automation Control automates first. Thesystem must be a test system, as it is shut down (intentionally or otherwise)once or twice during testing and training. The system is also not the systemwhere you run the Customization Dialog, as you may need to run the dialog toupdate the policy to prevent Automation Control from shutting down thepolicy. About capacity, Automation Control requires two copies of the SMP/Etarget libraries, space for several automation policies, and space for logs andVSAM files. See both the NetView and the IBM System Automation for z/OSPlanning and Installation Guide for more details.

Establishing Naming Conventions

Who: Automation programmer, system programmer

As a part of the deployment process you must establish a number of naming rulesthat are related to the installation of Automation Control:v High-level qualifier (HLQ) for SMP/E libraries on SMP/E installation system


v High-level qualifier for SMP/E libraries on deployed systemsv High-level qualifier for locally allocated data setsv High-level qualifier for Automation Policy Databases (PDBs)v High-level qualifier for SysOps Control (SOCNTL) staging data setsv High-level qualifier for active automation policy. (For your first deployment, use

a normal PDSE, but consider the use of GDGs for later deployments.)v Domain name that is used for NetView component (five characters, unique

within the SNA network)v Manager/Agent communication group suffix for unique identification (two

characters, unique within the sysplex).

If you are going to use the Single Point of Control function, you must plan yourgroupings. Then, work out the two character suffix, used to identify the systems(up to a maximum of three) that are connected together within each single point ofcontrol cluster.

Installing and deploying SMP/E

About this task

Who: System programmer, security administrator

Procedure1. Perform the SMP/E installation on the appropriate system. Apply any available

maintenance.2. The security administrator ensures that the system programmer has ALTER

access to the HLQs where they are to deploy the SMP/E target libraries to. Youmust use a system where the Customization Dialog is run and on the systemswhere Automation Control is deployed for automation.

3. The system programmer must transmit the SMP/E target libraries to the systemwhere the Customization Dialog is run and the systems where AutomationControl is deployed for automation. You can duplicate these data sets or waituntil you must distribute an update to them. Updating the data sets that theproduct is using is not recommended.

4. On the system where the Customization Dialog is run, the system programmermust make the INGEDLG routine available to the automation programmerunder ISPF. It is suggested that access to the Customization Dialog is restrictedas the automation policies that are used to edit, compose part of your operationruntime data. See the IBM System Automation for z/OS Planning and InstallationGuide

5. The security administrator must provide the following permissions for theautomation programmer:v READ access to the SMP/E target librariesv ALTER access to the HLQ used for the Automation Policy Databases (PDBs)

and the System Operations Control File (SOCNTL) staging data sets.

Configuring the Target Systems

About this task

Who: System programmer, automation programmer, security administrator

Chapter 2. Planning 13

Procedure1. Before Automation Control is started on a target system, you must perform an

installation process and configure the system to work with it.2. The security administrator must give the system programmer and the

automation programmer ALTER access to the HLQ for the locally allocated andactive automation policy data sets. He must also give the user ID that theAutomation Control started tasks that are run under, access to the data sets asfollows:v READ for SMP/E and active automation policyv UPDATE for the locally allocated data sets

3. The automation programmer must run the Automation Control ConfigurationAssistant tool. A set of tailored jobs, procedures, and parameter files isproduced. Then, the automation programmer must run the produced jobs. Thesystem programmer copies the procedures and the parameters file into thesystem production libraries, and tailors them to or consolidates them withexisting procedures, as required. For more information, see “Installing IBMAutomation Control for z/OS” on page 17

4. The security administrator ensures that the procedures and data sets areproperly authorized. See Chapter 4, “Security,” on page 33.

Building a Minimal Automation Policy

About this task

Who: Automation programmer, system programmer

Procedure1. The automation programmer must gather data from the target systems.2. The automation programmer must use the Customization Dialog to create an

Automation Policy Database containing a minimal automation policy for eachtarget system. The Policy Database contains details of the address spaces thatrun there along with the specific policy that is used for that automation. Mostautomation options in this policy are disabled. The purpose is to check that theinstallation is successful.

3. When it is complete, you must build the SOCNTL data set for the automationmodel. For more information, see “Installing IBM Automation Control forz/OS” on page 17.

Starting Automation Control and Verifying Your Installation

About this task

Who: Automation programmer, system programmer, security administrator

Procedure1. Deploy the minimal automation policy (SOCNTL data set) that you built

following the instructions in “Installing IBM Automation Control for z/OS” onpage 17.

2. Continue to follow the instructions to start the Automation Control AutomationManager and the Automation Control Automation Agent. Both the Managerand the Agent come up. No applications are stopped or started.

3. Log on to NetView component.


4. Perform the configuration validation step with the operational commandINGAMS described in “Installing IBM Automation Control for z/OS” on page17.

What to do next

It is advisable to have the system programmer and security administrator availableto help deal with any problems that are encountered.

Improving Your Automation Policy

Who: Automation programmer, system programmer, operators

The automation programmer now must produce a more comprehensiveautomation policy for the target systems. The automation programmer can eitherbuild upon the minimal policy he already has or he can start over using thesupplied samples. The system programmer or operator, or both are able to assist todetermine data about the system and to decide upon the best policy option to use.

For more information, see Chapter 5, “Customization,” on page 37.

Restarting Automation Control

About this task

Who: Automation programmer

Procedure1. Copy the SOCNTL data sets over to the target system after your improved

automation policy is built.2. Place them where Automation Control can find them.3. Start Automation Control if it is not already running.4. Use the operational command INGAMS to have it load your improved policy.

What to do next

You can now use the commands that are detailed in Chapter 6, “Operations,” onpage 93 to explore your policy. When there are errors in your policy, you mightfind that Automation Control is trying to start or stop items unnecessarily.

Testing your Automation Policy


You now must test the Stop and Start command instructions, and dependencydefinitions for the resources that you define to Automation Control. There is morework that is involved on the first systems you deploy to and many of the policiesare new. As you add more systems into the policy, the testing load is reducedbecause you can reuse tried and tested policies from earlier systems.

Training your Operators

Who: Automation programmer, operator

Chapter 2. Planning 15

At a minimum, the operators must read Chapter 6, “Operations,” on page 93 andwork through it on your test systems. You must also run some training ordiscussion sessions, or both, to establish local procedures for using AutomationControl. After your operators are trained, they can help you with the testing,which improves their familiarity with the product.

Expanding and Maintaining Your Automation Policy


You can now expand your automation policy, activating or defining automation formore address spaces and testing it as you go. You also must update the policy ifthe system programmers add, remove, or change the address spaces that run onthe system.

Additional Deployment PlansAfter you are comfortable working with Automation Control on your test system,you must plan its deployment to further test systems and production systems.

The deployment to the initial test systems is similar. Except that you are moreexperienced with the product with a large pool of tested automation policies thatare available for new systems.

Planning worksheetThe INGDOPT Configuration Options file contains a list of options to configureAutomation Control. Print a copy and you can write in the values agreed upon inyour planning meeting.

The comments in the file provide guidance as to the meaning and usage of thevalues. It is helpful to read “Installing IBM Automation Control for z/OS” on page17, which describes the use of the file with the Configuration Assistant andChapter 4, “Security,” on page 33, which describes the security model.

The output of the Configuration Assistant is normally written to staging data setsfrom which the system programmer copies/merges/adapts it into the appropriatePROCLIB and PARMLIB data sets. Writing the output directly into the productionlibraries is not recommended as it could overwrite the output from earlier runs ifyou are using libraries that are shared between multiple systems.


Chapter 3. Installation and Configuration

The following installation and configuration procedures are available forAutomation Control for z/OS.

Installing IBM Automation Control for z/OS

This product is installed through System Modification Program Extended (SMP/E)according to the Program Directory of IBM Automation Control for z/OS. Refer tothe Program Directory (GI11-9708) for detailed instructions about the installationprocedure.

Configuring IBM Automation Control for z/OSThe configuration of this product is supported by the Configuration Assistant.

Instead of manually adapting configuration jobs, start procedures, and initializationfiles to your environment, this assistant generates these files for you. The settingsthat are implemented are taken from the user-customized INGDOPT ConfigurationOptions file.

The generated files are created as members within a dynamically allocatedconfiguration data set (CONFLIB). In this data set, they are populated with thevalues that you define in the INGDOPT Configuration Options file.

The CONFLIB data set contains these items:v Jobs to allocate all data sets that are required by SA z/OS during run timev Procedures to start the components of SA z/OS to be copied to your target

SYS1.PROCLIB

v Runtime configuration members for both Automation Manager and AutomationAgent

v Parameter files that are ready to be copied to your target SYS1.PARMLIBv VTAM definitions that are files ready to be copied to your target VTAMLSTv Jobs to delete data set files in case you must reconfigure or delete SA z/OS

againv A job to verify the success of the installation and configuration process.

All members within the CONFLIB data set can be inspected, if required. If youapplied changes to the generated members, be aware that the CONFLIB data set isnewly allocated when running the configuration assistant another time.

Note: The security administrator must give the system programmer and theautomation programmer ALTER access to the HLQ for the locally allocated andactive automation policy data sets. The security administrator must also authorizethe user ID used by the SA z/OS started tasks for accessing the data sets asfollows:v READ for SMP/E and active automation policyv UPDATE for the locally allocated data sets


Preparing to Configure IBM Automation Control for z/OS

Preparation consists of the following steps:1. Allocate a data set where you can maintain working copies of the INGDOPT

Configuration Options file and the Configuration Assistant job. See “Allocate adata set for work files.”

2. Create a work copy of the INGDOPT Configuration Options file and theConfiguration Assistant sample job (INGDCONF). See “Create Working Copies”on page 19.

3. Edit the working copy of the INGDOPT Configuration Options file to reflect theparameters of your installation. These parameters are then used to build thenecessary artifacts to complete the configuration. See “Editing the Work Copyof the INGDOPT Configuration Options File” on page 19.

4. Edit and submit the work copy of the INGDCONF sample job. This job allocatesthe CONFLIB data set and configures the rest of the configuration jobs. See“Editing and Submitting the Work Copy of the INGDCONF ConfigurationAssistant Job” on page 19.

5. Follow the instructions documented in CONFLIB in $INGREAD.

Note: The user ID under which these jobs are submitted must be authorized toread the SMP/E target libraries. Runtime-specific data sets are allocated with ahigh-level qualifier as is specified in the INGDOPT Configuration Options file. Theuser must have ALTER access to create these data sets.

Allocate a data set for work filesAllocate a data set where you can maintain working copies of the INGDOPTConfiguration Options file and the Configuration Assistant job. The workingcopies are specific for each system controlled by IBM Automation Control forz/OS.

Compose the name of that library out of a high-level qualifier (HLQ), the systemname both of your choice and the low-level qualifier (LLQ) named CONFWRK.This naming scheme must not be changed because it is used by the ConfigurationAssistant job. For example, if you decide to use the HLQ of 'USER' and youconfigure a z/OS system named SYS1, the recommended name for the work dataset is USER.SYS1.CONFWRK.

The length of the data set name must not exceed 35 characters because thefollowing data sets are allocated by other JCLs later on:hlq.system.CONFLIB.&SYSNAME.hlq.system.CONFLIB.VTAMLIB

&SYSNAME. represents a system symbol which is resolved when running theseJCLs on the individual systems.

The characteristics for the data set (PDS or PDSE) are as follows:RECFM=FB,LRECL=80

As an initial size for the CONFWRK data set, you might allocate the following numberof tracks:Primary Quantity . . 15Secondary Quantity . 5Directory Blocks . . 5Block Size . . . . . 27920


Create Working Copies

The INGDOPT Configuration Options file and the INGDCONF ConfigurationAssistant are supplied as members in the sample data set that is part of SMP/EDDDEF name SINGSAMP.

Create a work copy of the INGDOPT and INGDCONF members in the work dataset, which you allocated in the previous step. Do not change the members in thedata set that belongs to SMP/E DDDEF SINGSAMP.

Editing the Work Copy of the INGDOPT Configuration OptionsFileYou define various settings that vary from installation to installation in the INGDOPTConfiguration Options file. Typical examples are data set high-level qualifiers,system name, and the NetView domain name. These settings are used to build theconfiguration files in the CONFLIB data set.

Next, edit the INGDOPT Configuration Options file according to the syntax rulesand the documentation that you find within that file.

The INGDOPT Configuration Options file contains comprehensive documentationon the purpose of the parameters.

Editing and Submitting the Work Copy of the INGDCONFConfiguration Assistant JobThis job runs the Configuration Assistant and allocates the CONFLIB partitioneddata set.

The data set stores the generated JCLs, start procedures, parmlib members, andother initialization and configuration members. Follow the instructions that aregiven in the INGDCONF job to adapt the job statements and the JCL variableswithin your INGDCONF work copy. When finished, submit the job.

Follow the Instructions as Documented in $INGREADDocumentation member $INGREAD was tailored to your installation and created inthe CONFLIB data set.

Follow the instructions documented there and complete the basic configuration.When you are finished with $INGREAD, proceed with the configuration described inthese sections.

Completing Member Configuration

Configure the System Logger (optional)

Configuring the System Logger allows gathering resource-related history data.Even though this configuration is not mandatory for resource automation, it isrecommended for problem determination tasks.

This step must be performed on the target system, where IBM Automation Controlfor z/OS is to be configured. See the configuration step "Configure the SystemLogger" in the "Traditional SA z/OS Configuration" section of IBM SystemAutomation for z/OS Planning and Installation Guide.

Chapter 3. Installation and Configuration 19

Note: If the system logger is not configured, the INGDVRFY verification job issues awarning message. Ignore that message if you do not want to configure the systemlogger for automation.

Update SMFPRMxx (optional)

If you plan to use SMF records for the availability reporting of automatedresources, you must update the SMFPRMxx member.

This step must be performed on the target system, where IBM Automation Controlfor z/OS is to be configured. See the configuration step "Update SMFPRMxx" inthe "Traditional SA z/OS Configuration" section of IBM System Automation for z/OSPlanning and Installation Guide.

Install the TSO REXX Function Package (optional)

The function package is used for the following functions:v Batch interface (see also member EVJSJ001 in *.SINGSAMP library)v Relational Data Services (RDS)v Syntax checking for automation table overridesv Preloader function of the Automated Discovery feature

If you plan to use these functions, you must configure the TSO REXX FunctionPackage on the target system where IBM Automation Control for z/OS is to beinstalled.

See the configuration step "Configure Function Packages for TSO" in the"Traditional SA z/OS Configuration" section of IBM System Automation for z/OSPlanning and Installation Guide.

Configuration of Alert Notification for IBM Automation Control for z/OS(optional)

IBM Automation Control for z/OS provides an alert-based notification service thatalerts subject matter experts. You can escalate automation problems that requiremanual intervention by sending alerts, events, or trouble tickets to different kindsof notification targets.

For more information, see "Alert-Based Notification" in IBM System Automation forz/OS Customizing and Programming Guide.

For configuration instructions, see the configuration step "Configure the SystemLogger" in the "Traditional SA z/OS Configuration" section of IBM SystemAutomation for z/OS Planning and Installation Guide.

Verifying Your ConfigurationSubmit the INGDVRFY Configuration Verification job on the target system whereIBM Automation Control for z/OS was configured.

This job is in the CONFLIB library. After the job terminates, investigate the job logfor INGVxxxx messages. If required, correct the configuration according to thosemessages.


Start IBM Automation Control for z/OS for the First TimeBefore you proceed to details about the contents of the automation policy andtechniques in the Customization Dialog for resource definitions, use this section toget a jump-start with a correct Policy Database (PDB) for a plain z/OS system.

You can use the procedure to complete the initial configuration as explainedpreviously. This procedure is expected to take less than 30 minutes.

After you validate your configuration and you have a basic policy, then you canskip the section.

Quick planning exerciseThe created basic policy contains a number of standard applications (started tasks)on z/OS systems. The started tasks must match the naming standards that are inplace on the target system.

The following planning sheet guides you in identifying the real job names that areused in the PDB and ensures that the applications are named correctly.

Table 1. Worksheet for job names

Application Description Default Job Name Real Job NameDefault ProcedureName

Real ProcedureName

AM AutomationManager

AM INGEAMSA See Note 1

AM2 Spare AutomationManager

AM2 INGEAMSA See Note 2

APPC AdvancedPeer-to-PeerCommunication

APPC

ASCH APPC Scheduler ASCH

BLSJPRMI Build SNAP Tablesfor IPCS

BLSJPRMI

DLF Data LookasideFacility

DLF

FFST™ First FailureSupportTechnology™

FFST

HSM Hierarchical StorageManager

HSM

IRRDPTAB RACF® dynamicparse table loader

IRRDPTAB

JES2 Job EntrySubsystem 2

JES

LLA Library Lookaside LLA

OAM Object AccessMethod

OAM

OMPROUTE Open MVS™

MultiProtocolRouting Daemon

OMPROUTE

OMVS UNIX SystemServices subsystem

OMVS

RACF Resource AccessControl Facility

RACF

RESOLVER TCP/IP NameResolver

RESOLVER


Table 1. Worksheet for job names (continued)

Application Description Default Job Name Real Job NameDefault ProcedureName

Real ProcedureName

RMF™ ResourceMeasurementFacility™

RMF

RMFGAT RMF Monitor IIIData Gatherer

RMFGAT

RRS Resource RecoveryServices

RRS

SYSVAPPL AutomationApplication

n/a n/a INGENVSA See Note 3

SYSVIPLC IPL Data Gatherer SYSVIPLC HSAPIPLC See Note 4

SYSVSSI AutomationSubsystem Interface

SYSVSSI

TCPIP TCP/IP TCPIP

TSO Time SharingOption

TSO

VLF Virtual LookasideFacility

VLF

VTAM VirtualTelecommunicationAccess Method

VTAM

ZFS z/OS File System ZFS

Notes:

1. When you specified sa_am_start_proc in the Options File, use this value, otherwise use what is specified forsa_am_start_job.1

2. When you specified sa_am_start_proc in the Options File, use this value, otherwise use what is specified forsa_am_start_job.2

3. When you specified sa_saagent_start_proc in the Options File, use this value, otherwise use what is specified forsa_saagent_start_job

4. When you specified sa_ipldata_start_proc in the Options File, use this value, otherwise use what is specified forsa_ipldata_start_job

In all likelihood, most of the listed applications are not changed because mostinstallations already use the default names. However, for some applications,different job names might be used and therefore the job name attribute for suchapplications has to be adopted in the basic policy. Also, some of the applicationsmight not exist on the target system, so those applications can be deleted orunlinked from the basic policy. Take note of those applications that require a jobname change or that can be deleted.

Starting the Customization Dialog

About this task

The Configuration Assistant provided you with a REXX script called INGEDLG.

Procedure1. Copy this script into a data set in your SYSPROC or SYSEXEC concatenation.2. Start it as follows:v %INGEDLG


v Alternatively, start it directly out of the CONFLIB with the TSO EXECcommand. For example: TSO EXEC ’MYHLQ.SYSA.CONFLIB(INGEDLG)’ AfterINGEDLG is started, you see a panel as follows:

MENU OPTIONS HELP------------------------------------------------------------------------------

Automation Control for z/OS 1.1.1 Customization DialogOption ===> _____________________________________________________________

0 Settings User parameters

BR Browse Browse the Policy Database1 Edit Edit the Policy Database2 Build Build functions for Policy Database3 Report Generate reports from Policy Database4 Policies Maintain Policy Database list5 Data Management Import policies into a Policy DatabaseU User User-defined selections

X Exit Terminate Customization Dialog

To switch to another Policy Database, specify the Policy Database namein the following field, or specify a ? to get a selection list.Current Policy Database . . . ____________________

Licensed Materials - Property of IBM© Copyright IBM Corp. 1990, 2014

Creating a basic PDB

About this task

The first thing that you must do is to create a Policy database.

Procedure1. 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 pressEnter. Alternatively you may use option 4 Policies to get to the following panel:

MENU COMMANDS ACTIONS VIEW HELP------------------------------------------------------------------------------

Policy Database Selection Row 1 of 23Command ===> ________________________________________________ SCROLL===> PAGE

Action Policy Database Enterprise Name******************************* Bottom of data ********************************PF 1=HELP 2=SPLIT 3=END 4=RETURN 5=RFIND 6=RCHANGEPF 7=UP 8=DOWN 9=SWAP 10=LEFT 11=RIGHT 12=RETRIEVE

2. 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 1Command ===> ____________________________________________________________

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=RCHANGEPF 7=UP 8=DOWN 9=SWAP 10=LEFT 11=RIGHT 12=RETRIEVE

3. The Policy Database Name field enters the name within the CustomizationDialog if you must select or build the PDB. The value that is entered here mustbe a single word but may include @, $, #, ? and _ (underscore). TEST_PDB isrecommended.

4. The Enterprise Name field enters the name of your business or the section of itthat you are going to define in the PDB. The value that you enter here must bea single word but may include underscores. TEST_SYSTEMS is recommended.

5. The Data Set Name field enters the name of the data set on disk that holds thepolicy database. A useful convention is to have the name end with a .PDBextension, and to use the same name with a .SOCNTL extension for theAutomation Control File that gets built from it. If you enter a value withoutsingle quotation marks, it is taken to be relative to your TSO user ID. If youenter a value with single quotation marks, it is taken as an absolute. Forexample, 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 specifiedfor sa_automation_policy in the INGDOPT Configuration Assistant Options fileand put single quotation marks around it. The section at the bottom with theadd-on policies adds the sample policies to your empty policy database.

6. Enter C in front of it and press Enter.


Select Add-on Policy Components Row 1 to 13 of 13Command ===> ____________________________________________________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 *******************************

For the basic PDB, only the Base z/OS components and one of the JESsubsystems are required.

7. To deselect all components, which are not required, specify M in front and pressEnter. The SELECTED status is now only shown for Base z/OS and either forJES2 or for JES3. It depends what type of JES that you use on the target system.

8. When finished, press PF3.9. 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 yourselfon the Entry Type Selection panel for your new policy database:

Entry Type SelectionOption ===> ___________________________________________________________________

Enter number or entry type or use "BR <entry type>" for browse

1 ENT Enterprise 30 TMR Timers2 GRP Groups 32 TPA Tape Attendance3 SBG SubGroups 33 MVC MVS Components4 SYS Systems 34 MDF MVSCOMP Defaults5 APG ApplicationGroups 35 SDF System Defaults6 APL Applications 36 ADF Application Defaults7 EVT Events 37 AOP Automation Operators8 SVP Service Periods 38 NFY Notify Operators9 TRG Triggers 39 NTW Networks10 PRO Processors 40 XDF Sysplex Defaults11 MTR Monitor Resources 41 RES Resident CLISTs12 ENS zEnterprise Ensembles 42 SCR Status Display13 PAC Pacing Gates

20 PRD Product Automation 99 UET User E-T Pairs21 MSG Messages

Adapting the System Name

About this task

You now have a basic PDB that is built from the sample add-on policy that isprovided by the product. In this policy, the default system that is being automated


is called SYS1. This name has to be changed to match the name of your system.

Procedure1. Select 4 on the Option line and you see a single system that is listed as shown

here:

------------------------------------------------------------------------------Entry Name Selection Row 1 from 3

Command ===> __________________________________________________ SCROLL===> CSR

Entry Type : System PolicyDB Name : TEST_PDBEnterprise Name : TEST_SYSTEMS

Action Entry Name Short Description_________ SYS1 System 1 of the Monoplex

2. To rename the policy entry name of the system, enter r and press Enter. In thepop-up panel that is displayed next, enter the name of your system and pressEnter again. The entry name is renamed, but one more renaming action isnecessary.

3. Enter SI and press Enter. This action leads you to the SYSTEM INFORMATIONpolicy. Here again, you have to change the field Image/System name to matchthe name of your system. Before the change, the panel might look like asfollows:

------------------------------------------------------------------------------System Information

Command ===> ___________________________________________________________________

Entry Type : System PolicyDB Name : TEST_PDBEntry Name : SYS1 Enterprise Name : TEST_SYSTEMS

Operating system : MVSImage/System name. . . . SYS1

The following specifications are for MVS systems only:Primary JES. . . . . . . JES2 Primary JES2/JES3 subsystem nameSystem monitor time. . . 00:59 Time between monitor cycles (hh:mm or NONE)Gateway monitor time . . 00:15 Time between monitor cycles (hh:mm or NONE)Automation table(s). . . INGMSG01

4. Rename SYS1 here to your system name and press PF3 to leave the dialog box.You now see a group of messages that flow through the panel that shows theresources that are defined for your system. The message flow reflects thecontents of the basic policy.

5. Press PF3 twice to return to the Entry Type Selection panel.

Adapt Application Job Names

Use the notes that you took during the planning exercise to change the default jobnames (where necessary) to the real job names. Then, either delete or unlink thoseapplications that are not used on the target system.

Select 6 on the Option line and press Enter. The Entry Name Selection panel forentry type Application is displayed.


Entry Name Selection Row 1 from 31Command ===> ______________________________________________________ SCROLL===> CSR

Entry Type : Application PolicyDB Name : TEST_PDBEnterprise Name : TEST_ENTERPRISE

Action Entry Name C Short Description__________ AM Automation Manager__________ AM2 Spare Automation Manager__________ APPC Advanced Peer-to-Peer Communication__________ ASCH APPC Scheduler__________ BLSJPRMI Build SNAP Tables for IPCS__________ C_AM * Class for Automation Manager Definitions__________ C_APPL * Class for general APL definitions__________ C_JES2 * Class for Job Entry Subsystem 2__________ DLF Data Lookaside Facility__________ DSIRQJOB NetView JES-JobID-Requestor__________ FFST First Failure Support Technology__________ HSM Hierarchical Storage Manager__________ IRRDPTAB RACF dynamic parse table loader__________ JES2 Job Entry Subsystem 2__________ LLA Library Lookaside__________ OAM Object Access Method__________ OMPROUTE Open MVS MultiProtocol Routing Daemon__________ OMVS Unix System Services subsystem__________ RACF Resource Access Control Facility__________ RESOLVER TCP/IP Name Resolver__________ RMF Resource Measurement Facility__________ RMFGAT RMF Monitor III Data Gatherer__________ RRS Resource Recovery Services__________ SYSVAPPL Automation Application__________ SYSVIPLC IPL Data Gatherer__________ SYSVSSI Automation Subsystem Interface__________ TCPIP TCP/IP__________ TSO Time Sharing Option__________ VLF Virtual Lookaside FacilityAI________ VTAM Virtual Telecommunication Access Method__________ ZFS z/OS File System

To change a job name for an application, enter AI next to that application and pressEnter. A panel is shown as follows:

Application Information Line 00000001Command ===> ____________________________________________________Scroll ===> PAGE

Entry Type : Application PolicyDB Name : TEST_PDBEntry Name : VTAM Enterprise Name : TEST_ENTERPRISE

Category . . . . . . . . . __________ (IBM-defined, user-defined or blank,see help)

Subcategory . . . . . . . __________ (IBM-defined, user-defined or blank,see help)

Subsystem Name . . . . . . VTAM_______Job Type . . . . . . . . . _________ (MVS NONMVS TRANSIENT)Job Name . . . . . . . . . VTAM____Transient Rerun . . . . . ___ (YES NO)Scheduling Subsystem . . . ________ (MSTR, JES Subsystem)JCL Procedure Name . . . . _________________________

For example, if the VTAM job name is NET on the target system, change the valueof the Job Name field in the panel appropriately. If you press PF3 twice, youreturn to the Entry Name Selection panel.

Follow the same steps if you must enter the JCL Procedure Name.

To delete an application you do not need, enter D next to it and press Enter. Yousee a confirmation panel and press Enter again. However, if you want to use this


application in the future, unlink it. The definitions are kept in the policy but theCustomization Dialog does not create a resource for it. You can link such anapplication any time later again.

To unlink an application you do not need, enter W next to it and press Enter. Younotice that the application is linked to a group called BASE_SYS. Enter M (forreMove) next to it and press PF3.

Changing System Defaults

About this task

When you create the basic PDB the first time, you have no experience yet withcustomization and operations of the product. It is recommended to monitor whatis going on to further familiarize yourself with the product, and then switch onautomation. The approach protects you from stumbling into pitfalls whereunintended automation might happen by accident.

To do so, you can switch automation globally off by setting the Automation flag toLOG in the System Defaults (SDF). No automation takes place but the commandsthat the automation would run are shown in the netlog.

Procedure1. Select 35 on the Option line and press Enter. You see a single system

SYSTEM_DEFAULTS similar to what is shown here:

------------------------------------------------------------------------------Entry Name Selection Row 1 from 1

Command ===> _____________________________________________________SCROLL===> CSR

Entry Type : System Defaults PolicyDB Name : TEST_PDBEnterprise Name : TEST_ENTERPRISE

Action Entry Name Short Description__________ SYSTEM_DEFAULTS System Defaults

2. Under Action, specify AF and press Enter. You enter the Automation FlagProcessing dialog that is shown here:

------------------------------------------------------------------------------Automation Flag Processing

Command ===> _________________________________________________________________

Entry Type : System Defaults PolicyDB Name : TEST_PDBEntry Name : SYSTEM_DEFAULTS Enterprise Name : TEST_ENTERPRISE

Resource : System Defaults

Line Commands: Exi (Exits), Dis (Disable Times)Automation Level: YES, NO, LOG, EXITS

Cmd Flag Auto Exits DisableTimes

___ Automation (A) LOG___ Initstart (I) _______ Start (S) _______ Recovery (R) _______ Terminate (T) _______ Restart (RS) ____


3. Change the value of Automation from YES to LOG and press PF3. Noautomation happened accidentally. But do not forget to turn the flag back toYES after you are familiar with the product.

4. Press PF3 again until you are back on the initial panel, the primary panel, ofthe Customization Dialog.

Building the Configuration Files

About this task

You completed the steps to create a basic automation policy. You now create theconfiguration files (SOCNTL).

Procedure1. Enter option 2 from the Automation Control for z/OS Customization Dialog to

start the Build dialog.

Build ParametersOption ===> ___________________________________________________________________

1 Build a complete enterprise2 Build sysplex group or stand alone system

Sysplex / System name. . (*, ?, or name)3 Build entry type or entry name

Entry Type. . . . . . . . SDF (*, ?, or type)Entry Name. . . . . . . . SYSTEM_DEFAULTS (*, ?, or name)

4 View build report

Build options:Output Data Set . . . .Mode. . . . . . . . . . ONLINE (ONLINE BATCH)Type. . . . . . . . . . MODIFIED (MODIFIED ALL)Configuration . . . . . NORMAL (NORMAL ALTERNATE)

Job statement information: (used for BATCH build)//AOFBUILD JOB//*//*

2. The Configuration Assistant already created a SOCNTL file for you. So, in theOutput Data Set field, enter the value that you specified forsa_automation_policy in the Configuration Options file and append’.SOCNTL’, surrounded by single quotation marks. For example:'USER.POLICY.NAME.PDB.SOCNTL'.

3. Change Type from MODIFIED to ALL.4. Select Option 1 Build a complete enterprise and press Enter. Messages are

displayed and after a time, the build process completes successfully.

Results

You created a SOCNTL file from your basic policy that can be used to load on thetarget system. For the remaining steps, you need a console to enter systemcommands on the target system.

Starting the Automation Manager

About this task

The Automation Manager is started with a standard MVS Start command:


Procedure

Issue: S INGEAMSA,JOBNAME=AM,TYPE=COLD,SUB=MSTR

Results

The Automation Manager initializes and issues the following message when theinitialization is complete:

HSAM1308I SA z/OS PRIMARY AUTOMATION MANAGER INITIALIZATIONCOMPLETE,TYPE=COLD

If this message is not displayed, see which of these actions can help you:1. Find the messages that are displayed on the MVS console to identify the cause2. Verify that you have the proper authority3. Be sure that you performed correctly all steps of the configuration that are

described in the chapter

Starting the Subsystem Interface Task

About this task

The Subsystem Interface Task is started with a standard MVS Start command:

Procedure

Issue: S CNMSJ010,JOBNAME=SYSVSSI,SUB=MSTR

Results

After the task is initialized, the following message appears:

CNM541I NetView subsystem SYSV is fully functional



Starting the Automation Agent

About this task

The Automation Agent is started with a standard MVS Start command:

Procedure

Issue: S INGENVSA,JOBNAME=SYSVAPPL,SUB=MSTR

Results

After the Automation Agent is initialized up to the point where logging on ispossible, it responds with the following message:


*002 DSI802A ING01 REPLY WITH VALID NCCF SYSTEM OPERATOR COMMAND



After this message is displayed, you are able to log on to the NetView 3270console.

The Automation Manager instructs the Automation Agent to load the SOCNTLdata set. When done, another message is displayed:

HSAM1330I LOAD_ACF REQUEST COMPLETED SUCCESSFULLY ON SYS1.AOF767I AUTOMATION OPTIONS: 729. STOP - CANCEL AUTOMATION. PAUSE - SUSPEND AUTOMATION. NOSTART - DO NOT AUTOMATE SUBSYSTEM STARTUP. RUNMODE=x - SET RUNMODE (CURRENT *ALL). ENTER - CONTINUE*003 AOF603D ENTER AUTOMATION OPTIONS OR ’R’ (RE-DISPLAY) - DOMAIN ING01

What to do next

Press Enter to close this message.

VerificationAbout this task

When the Automation Manager and the Automation Agent are both startedsuccessfully, log on to the NetView console.

Procedure1. To log on, enter LOGON APPLID(domain). For domain, use the value that you

specified for net_netview_domain_id in the INGDOPT Configuration Options file.A panel is shown as follows:


NN NN VV VVNNN NN EEEEEE TTTTTTTT VV VV II EEEEEE WW WW TMNNNN NN EE TT VV VV II EE WW W WWNN NN NN EEEE TT VV VV II EEEE WW WWW WWNN NNNN EE TT VV VV II EE WWWW WWWWNN NNN EEEEEE TT VVV II EEEEEE WW WWNN NN V

5697-NV6 © Copyright IBM Corp. 1986, 2014 - All Rights ReservedU.S. Government users restricted rights - Use, duplication, or disclosure

restricted by GSA ADP schedule contract with IBM corporation.Licensed materials - Property of IBM Corporation

Domain = ING01 Automation Control

OPERATOR ID ==> or LOGOFFPASSWORD ==>PROFILE ==> Profile name, blank=default

HARDCOPY LOG ==> device name, or NO, default=NORUN INITIAL COMMAND ==> YES or NO, default=YES

Takeover session ==> YES, NO, or FORCE, default=NO

Enter logon information or PF3/PF15 to logoff

2. For OPERATOR ID, specify OPER1. For the PASSWORD, specify OPER1. Theentries are default credentials that are set up for you to get into AutomationControl initially.

Note: Secure the environment as soon as possible following the guidelines inChapter 4, “Security,” on page 33.

3. After you log on, press Enter, when you see message: =X= *** DSI662I SCREENHELD.

4. Enter INGAMS on the command line for the operational command INGAMS. Apanel as follows is then displayed:

INGKYAM0 SA z/OS - Command Dialogs Line 1 of 2Domain ID = IPUFL ---------- INGAMS ---------- Date = 08/24/14Operator ID = JMH Sysplex = MONOPLX1 Time = 12:34:25

Cmd: A Manage B Show Details C Refresh Configuration D Diagnostic

CMD System Member Role Status Sysplex XCF-Group Release Comm PA--- -------- --------- ----- ---------- -------- --------- ------- ---- ---

SYS1 SYS1 AGENT READY SYS1PLEX INGXSG V1R1M1 XCFSYS1 SYS1$$$$1 PAM READY SYS1PLEX INGXSG V1R1M1 XCF

The statuses of the Primary Automation Manager (PAM) and of theAutomation Agent are READY.


Chapter 4. Security

You can secure the product. Only authorized personnel are able to accessproduct-specific data sets, find out runtime information about automatedresources, or change the status of such resources.

After the initial configuration, the product is set up so that you familiarize yourselfwith the functions for testing purposes and you make it secure for your productionenvironment. However, before you begin, you are advised to change the defaultpasswords of the operator IDs that come with the product. You locate the defaultoperators that are defined in <nv_hlq_smpe>.DSIPARM member DSIOPFEX. Copythis member to <sa_hlq_user>.DSIPARM, edit it and change the PASSWORDparameter for each of them. For example, to change OPER1's password to XYZ123,specify:OPER1 OPERATOR PASSWORD=XYZ123

PROFILEN DSIPROFA

Use a System Authorization Facility (SAF) product, such as the z/OS ResourceAccess Control Facility (RACF) to secure your environment as follows:v Operators are defined and authenticated by a SAF productv Command authorization is done by a SAF product that is based on the issuer of

a commandv Resource authorization is done by a SAF product that is based on the issuer of

particular commands

For additional information about how to fully secure refer to the "Security" chapterof "Installation and Configuration" in IBM System Automation for z/OS Planning andInstallation.


Part 2. User Guide

The following user guide contains a description of the key functional areas youmay wish to use with Automation Control for z/OS.


Chapter 5. Customization

Automation Control starts and stops your applications, recovers them if they failand coordinates actions across large groups of applications.

To do this, Automation Control needs a model of your application workload andsome policy definitions to understand how you work. This information is enteredthrough an ISPF application that is called the Customization Dialog and isprovided as a part of Automation Control.

The data in the model is stored in a data set known as a Policy Database, which iscompiled into another data set called the System Operations Configuration File(SOCNTL). The SOCNTL data set is used at run time. Copy the SOCNTL data setto each system that loads automation policy. The PDB data set, however, remainson the single system where you run the Customization Dialog.

Customization ToolsWhile Automation Control's primary modeling tool is the Customization Dialog,Automation Control provides a number of extra tools. The tools assist you ingathering data about your systems and creating an automation model that is builtaround tried and trusted practices.

Customization Dialog

The Customization Dialog is an ISPF (Interactive System Productivity Facility)application that performs a number of actions upon your Policy Databases (PDBs).You also edit the data within the PDBs. The following actions are available to youwhen working with a Policy Database. With the listed actions, you can constructand fine-tune an automation model for your systems.v Create a new empty database, or one from templates, called add-on policiesv Create and edit the individual entries within your database

Model

PDB

SOCNTL

Distribute

SOCNTL

ISPFCustomization

Dialog

AutomationManager

AutomationAgent

BuildBuild

(artname: acf2.gif)Figure 5. Automation Policy Lifecycle


v Build the configuration files from the data in your databasev Perform updates with a text or flat filev Import data from other databases or from add-on policiesv Import data into your database from the Discovery Tool

Add-on Policies

Automation Control provides an add-on or sample policy that you can use as abasis to start your automation model. You have some options for creating yourautomation model.v Start with a populated add-on policy and review it to change the definitions to

match your own systemsv Start with a blank system and use the discovery tool to get your model startedv Start with a blank model and create your entire model through the editor

While all three approaches have their advantages, for your first model it isrecommended that you use an add-on policy.

The Discovery Tool

The Discovery tool contains a probe that captures data about the address spacesthat are active on a system when it is run. An analysis job then reviews thecaptured data and maps it to resources that are known to Automation Control.Where it finds a match it outputs a set of records. Use the set of records to importthe definition into a Policy Database through the Customization Dialog. Tune andguide its mapping from the discovered data to the known data and you expandthe set of recognized resources with your own definitions.

While the discovery tool can provide a basic automation model for a systemquickly, you must learn the basics of using the dialog to edit the data manually.Manual editing is required to complete the models the Discovery Tool producesand to expand the things it can discover.

What is in a Policy Database?An Automation Control Policy Database (PDB) contains the data that models thesystems and applications that you want Automation Control to automate. Alsoincluded is the required policy to tell Automation Control how you want it toautomate those resources.

Although IBM Automation Control for z/OS automates resources on a singlesystem, the Customization Dialog supports the definition of the models formultiple systems within the same policy database. The result is a considerablebenefit in terms of sharing resource definitions and standardizing the automationof resources across multiple systems.

Figure 6 on page 39 shows a single policy database that is used to define yourautomation model and then used to produce an SOCNTL data set from that policydatabase. The SOCNTL data set is then distributed to multiple different systems,where the automation extracts just the resources that it needs to run on thatsystem.


You can, for example, define a single set of TSO automation and link the set toevery system definition that you deployed Automation Control to. The systems allrun TSO in the same way with the same policies. Where you must create somesystematic variations in naming, Automation Control provides a symbolicsubstitution mechanism, tailoring the automation for each system when built bythe Customization Dialog policies.

Building BlocksThere are many different entity types within a Policy Database, but you do nothave to understand them all. The defaults for most of entity types are a goodstarting point and there are a few that are not required for Automation Control.The following resources are considered the most important.

Resources

Resource is a generic term that means any actual or logical entity that is modeledby Automation Control. Address Spaces are modeled as APL (Application) typeresources, active and passive Monitors are modeled as MTR (Monitor) typeresources. Systems are modeled as SYS (System) type resources, logical groupingsof applications that are managed by APG (Application group) type resources. TheCustomization Dialog recognizes the abbreviations that are given here for theresource type specified.

General naming conventions are used for all resources:name/type

The /system element is for those resources that are associated with a specificsystem:name/type/system

PDB

StagingSOCNTL

Distribute

TargetSOCNTL

CustomizationDialog

Build

TargetSOCNTL

TargetSOCNTL

Automation

Automation

Automation

(artname: PDB_External2.gif)Figure 6. Policy Database and SOCNTL Distribution

Chapter 5. Customization 39

Application (APL) Resources

The Application (APL) resources represent the individual address spaces (andother entities) that are to be automated.

For example, you might define Application (APL) resources for JES, VTAM, andTSO.

Application Group (APG)

Application Group (APG) is a group of Applications (APL). It is used to managethe applications and to link them to systems. For an Application to be linked to asystem, it must be a member of an Application Group that is linked to the System.

For example, you might define an Application Group that is called BASE_SYS asshown in Figure 7. Make the JES, VTAM, and TSO resources members.

System (SYS)

System (SYS) defines a single system that is to be automated. It includesdefinitions for automatically responding to events that happen on the system.

For example, you might define a System that is called SYS1 as shown in Figure 7.Connect the BASE_SYS APG to it to instruct automation that it must run theresources in the APG on the SYS1 System.

Group (GRP)

Group (GRP) is a collection of one or more systems (SYS). While Groups arerequired for most functions to automate systems, they are not required for thesingle-system automation model used by Automation Control.

For example, you might define a Group that is called GROUP_SYS1 to hold theSYS1 System. Or use MONOPLEX1 as shown in Figure 7.

Enterprise (ENT)

Enterprise (ENT) is the logical top of the tree and contains some global data aboutyour business and global policies that are used by Automation Control. Eachpolicy database contains only a single enterprise.

If you follow the examples, you now define a relationship as follows:

Building up a structure complex enough to model an actual system is a matter ofcreating extra Applications and Application Groups. Then, link them into the

MONOPLEX1 SYS1 BASE_SYS TSO

VTAM

JES

Group System Application Group Applications

(artname: entry_structure_2c.gif)Figure 7. Simple Entry Structure


structure. To extend the automation to cover more systems, you create new Systemresources and link them into the structure:

Cloning DefinitionsReusing the definitions between different systems is good practice, but sometimesthe definitions are not the same on each system.

The Customization Dialog provides a mechanism to help. For each system, you candefine over 30 distinct clone values, which can then be used in the data fields todescribe the applications in the model.

For example, you might set the clone value AOCCLONE1 to S1 on SYS1 and S2 onSYS2. You could then modify your VTAM APL so the job name isNET&AOCCLONE1. The result of this is that it would run with the job name ofNETS1 on SYS1 and NETS2 on SYS2.

You can provide a description of the clone values under the definition of yourEnterprise.

Customization Dialog TutorialThe following short tutorial guides you through the basics of creating automationpolicy with the Customization Dialog. The tutorial is highly recommended for newusers.

Starting the Customization Dialog

Your system programmers install the dialog on the system where you are going toperform your customization activities. The Configuration Assistant provides youwith a REXX script called INGEDLG. That script links into your regular ISPFpanels, or you issue a command to start them.

After the INGEDLG script starts, you see a panel as follows:

BASE_SYS TSO

VTAM

JES

Group System Application Group Applications

MONOPLEX1

MONOPLEX2

MONOPLEX3

SYS1

SYS2

SYS3

(artname: entry_structure_1c.gif)Figure 8. Complex Entry Structure







To switch to another Policy Database, specify the Policy Database namein the following field, or specify a ? to get a selection list.Current Policy Database . . . IACZ_DEMO


Getting Help

You can press PF1 for help with the panel that you are on. Pressing it a secondtime gets you general help with the dialog.

If there is a message that is displayed on the screen, PF1 gives you assistance withthe message. Pressing it a second time takes you to the assistance panel for thescreen you are on. Pressing it a third time takes you to the general assistancepanel.

Creating an Empty PDB

The first thing that you must do is to create a Policy Database. Enter ? in theCurrent Policy Database field at the bottom of the pane and press Enter. Option 4Policies is available for creating an empty PDB.

You see a panel as follows:


Policy Database Selection Row 1 of 23Command ===> ________________________________________________ SCROLL===> PAGE

Action Policy Database Enterprise Name******************************* Bottom of data ********************************PF 1=HELP 2=SPLIT 3=END 4=RETURN 5=RFIND 6=RCHANGEPF 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:



Create a New Policy Database Row 1 of 1Command ===> ____________________________________________________________

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 ********************************


The Policy Database Name field displays the name that is displayed within theCustomization Dialog if you select or build the PDB. The value that is entered heremust be a single word but may include underscores. TEST_PDB (without thequotation marks) is recommended.

The Enterprise Name field displays the name of your business or the section of itthat you are going to define in the PDB. The value that is entered here must be asingle word but may include underscores. TEST_SYSTEMS (also without thequotation marks) is recommended.

The Data Set Name field displays the name of the data set on disk that holds thepolicy database. A useful convention is to have the name end with a .PDBextension, and to use the same name with a .SOCNTL extension for the SystemOperations Control file that gets built from it. If you enter a value withoutquotation marks, it is taken to be relative to your TSO user ID. If you enter a valuewith quotation marks, it is taken as an absolute. For example, TEST.PDB mightresult in the data set USER.TEST.PDB, and ’AUTO.TEST.PDB’ results in the data setAUTO.TEST.PDB.

For the data set name, you might have to share the PDB with other members ofyour automation team. It is better to create the name under a shared prefix with aname that is easily specifiable to your security product ('AUTO.POLICY.TEST.PDB'for example). You need permission to create the data set before you can do so.

The Model Policy Database field is used to select a template or an existing PDB touse as a model for your new PDB. The only one provided with AutomationControl is *EMPTY, so leave it selected.

The section at the bottom of the panel with the add-on policy adds the samplepolicies to your empty policy database. Leave it alone for now.

When you are finished with your input, press Enter twice. (The first press validatesyour input, the second runs your request.)


A panel prompts you for details about where you want the data set created. Youwant a size of about 3 CYLINDERS for now. Leave everything else as is and pressEnter.

After a few messages (you must press Enter to clear them), you see the Entry TypeSelection panel for your new policy database:

MENU HELP------------------------------------------------------------------------------

Entry Type SelectionOption ===> _________________________________________________________

Enter number or entry type or use "BR <entry type>" for browse

1 ENT Enterprise 30 TMR Timers2 GRP Groups 32 TPA Tape Attendance3 SBG SubGroups 33 MVC MVS Components4 SYS Systems 34 MDF MVSCOMP Defaults5 APG ApplicationGroups 35 SDF System Defaults6 APL Applications 36 ADF Application Defaults7 EVT Events 37 AOP Automation Operators8 SVP Service Periods 38 NFY Notify Operators9 TRG Triggers 39 NTW Networks10 PRO Processors 40 XDF Sysplex Defaults11 MTR Monitor Resources 41 RES Resident CLISTs12 ENS zEnterprise Ensembles 42 SCR Status Display13 PAC Pacing Gates

20 PRD Product Automation 99 UET User E-T Pairs21 MSG MessagesPF 1=HELP 2=SPLIT 3=END 4=RETURN 5=RFIND 6=RCHANGEPF 7=UP 8=DOWN 9=SWAP 10=LEFT 11=RIGHT 12=RETRIEVE

You use the panel to select the item that you want to edit. Many of these items arefor advanced users in Automation Control. You need to focus on the mostimportant items required now.

Next, you define a system (SYS), and a group (GRP) and link them together.

Creating a System

First, you define the System. Type 4 on the Policy line and press Enter. You see apanel as follows:

COMMANDS ACTIONS VIEW HELP------------------------------------------------------------------------------

Entry Name SelectionCommand ===> _______________________________________________ SCROLL===>PAGE

Entry Type : System PolicyDB Name : IACZ_DEMOEnterprise Name : IACZ_DEMO

Action Entry Name Short Description******************************* Bottom of data *******************************


Enter new SYS1 on the command line and press Enter to create a system SYS1. Yousee a panel as follows:


COMMANDS HELP------------------------------------------------------------------------------

Define New EntryDefine new entry of type System

Entry name . . . . . . . SYS1_______________

Operating system . . . . MVS (MVS VM VSE LINUX CF)Image/System name . . . ____________

Specify information for NMC Focal Point Communication (MVS systems only):Heartbeat interval . . . . __ (1 - 60 minutes)Missing heartbeat delay . ____ (1 - 3600 seconds)

Short Description . . . _________________________________Long Description 1 . . . _______________________________________________Long Description 2 . . . _______________________________________________Long Description 3 . . . _______________________________________________Long Description 4 . . . _______________________________________________Long Description 5 . . . _______________________________________________


Enter the name of your system (for example SYS1) as the Entry name and pressEnter to complete all default entries. Edit the default entries if required, and add adescription, if you want. Press PF3 to exit the panel.

You now see a system Policy Selection panel, which looks as follows.

ACTIONS HELP------------------------------------------------------------------------------

Policy Selection Entry createdCommand ===> ________________________________________________ SCROLL===>PAGE

Entry Type : System PolicyDB Name : IACZ_DEMOEntry Name : SYS1 Enterprise Name : IACZ_DEMO

Action Policy Name Policy Description___________ DESCRIPTION Enter description___________ SYSTEM INFO Enter and display system information___________ AUTOMATION SYMBOLS Define system automation symbols (AOCCLONEx)___________ AUTOMATION CONSOLE Enter MVS route codes for notifications___________ APPLICATION GROUPS Select application groups___________ MONITOR RESOURCES Select monitor resources___________ AUTOMATION TIMERS Select timers___________ USER E-T PAIRS Select user entry-type pairs___________ RESIDENT CLISTS Select resident clists___________ TAPE ATTENDANCE Select tape attendance___________ APPLICATION DEFAULTS Select application defaults___________ SYSTEM DEFAULTS Select system defaults___________ MVSCOMP DEFAULTS Select MVS component defaults___________ MVS COMPONENT Select MVS components___________ NETWORK Select network definitions___________ AUTOMATION OPERATORS Select automation operators___________ STATUS DISPLAY Select status display facility details___________ NOTIFY OPERATORS Select notify operators___________ OPC SYSTEM DETAILS Select OPC system details___________ CONTROLLER DETAILS Select OPC controller details___________ WORKSTATION DOMAINS Select OPC Workstation domainsPF 1=HELP 2=SPLIT 3=END 4=RETURN 5=RFIND 6=RCHANGEPF 7=UP 8=DOWN 9=SWAP 10=LEFT 11=RIGHT 12=RETRIEVE


You do not have to enter any additional data for the system, but you can reviewthe additional definitions if you want. When you are finished, press PF3 to returnto the Entry Type Selection panel.

Creating a Group

Next, you must create a group to hold the system. Starting from the Entry TypeSelection panel (=1), enter 2 or GRP on the option line at the top and you see apanel as follows:

Note: You can navigate to any entry by using the fast path notation of equal sign(=) followed by the three character shorthand for the entry type. For example, =GRPentered on any Command or Option takes you to the Group dialog.


Entry Name SelectionCommand ===> ________________________________________________ SCROLL===> PAGENo entries currently exist. Use the NEW command to create an entry.

Entry Type : Group PolicyDB Name : IACZ_DEMOEnterprise Name : IACZ_DEMO

Action Entry Name Short Description******************************* Bottom of data ********************************


Enter new on the command line and press Enter. You see a panel like this one:

COMMANDS HELP------------------------------------------------------------------------------

Define New EntryCommand ===> ___________________________________________________________

Define new entry of type Group

Entry name . . . . . . . ___________________

Group Type . . . . . . . SYSPLEX (STANDARD SYSPLEX)ProcOps Commands . . . . NO (YES NO)

Short Description . . . _______________________________Long Description 1 . . . _____________________________________________Long Description 2 . . . _____________________________________________Long Description 3 . . . _____________________________________________Long Description 4 . . . _____________________________________________Long Description 5 . . . _____________________________________________


In the Entry Name field, enter GROUP_ followed by the sysname for the system (forexample, GROUP_SYS1) and press Enter. Then, press PF3 to close the panel.

You now see a panel like this one:


ACTIONS HELP------------------------------------------------------------------------------

Policy Selection Entry createdCommand ===> ________________________________________________ SCROLL===> PAGE

Entry Type : Group PolicyDB Name : IACZ_DEMOEntry Name : GROUP_SYS1 Enterprise Name : IACZ_DEMO

Action Policy Name Policy Description__________ DESCRIPTION Enter description__________ GROUP INFO Define group information__________ SUBGROUPS Select subgroups for group__________ SYSTEMS Select systems for group__________ -------------------- -----SYSPLEX SPECIFIC POLICY-----------------__________ SYSPLEX Define sysplex policy__________ NMC DEFINITIONS Define NMC Data__________ APPLICATION GROUPS Select application groups for sysplex__________ SYSPLEX DEFAULTS Select sysplex resource defaults for group__________ -------------------- -----LOCAL PAGE DATA SET POLICY--------------__________ LOCAL PAGE DATA SET Define local page data set recovery__________ JOB DEFINITIONS Define handling of jobs__________ -------------------- -----LONG RUNNING ENQUEUE POLICY-------------__________ JOB/ASID DEFINITIONS Define handling of long running jobs and ASID__________ COMMAND DEFINITIONS Define "hung" commands__________ COMMAND FLOODING Define check intervals for command flooding__________ RESOURCE DEFINITIONS Define long running enqueue resources__________ RECOVERY OPTIONS Define dump and miscellaneous options__________ -------------------- ---------------------------------------------__________ COPY Copy data from an existing entry******************************* Bottom of data ********************************PF 1=HELP 2=SPLIT 3=END 4=RETURN 5=RFIND 6=RCHANGEPF 7=UP 8=DOWN 9=SWAP 10=LEFT 11=RIGHT 12=RETRIEVE

Select the SYSTEMS policy item (type an s in front of it and press Enter) and yousee a panel like this one.


Systems for Group Row 1 of 1Command ===> ________________________________________________ SCROLL===> PAGE

Entry Type : Group PolicyDB Name : IACZ_DEMOEntry Name : GROUP_SYS1 Enterprise Name : IACZ_DEMO

Action Status System_________ SYS1******************************* Bottom of data *******************************


Select SYS1. The Status turns to SELECTED. Press PF3 multiple times to return tothe Entry Policy Selection panel.

Adding Applications

Next, you add some applications. Enter a 6 (or APL) on the Entry Type Selectionpanel or =APL from any other panel in the Customization Dialog. The APLSelection panel appears:



Entry Name SelectionCommand ===> _________________________________________________ SCROLL===> PAGENo entries currently exist. Use the NEW command to create an entry.Entry Type : Application PolicyDB Name : IACZ_DEMO

Enterprise Name : IACZ_DEMO

Action Entry Name C Short Description******************************* Bottom of data ********************************


You are going to create 3 APLs: TSO, VTAM, and JES, because they arewell-known applications. The policies that you create for them are fairly basic.

To create the TSO application, enter new tso on the command line. You see a panellike this one:

COMMANDS HELP-----------------------------------------------------------------------------

Define New EntryCommand ===> _______________________________________________________________

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 defaultentries. Edit the entries, as required.

While the other values default to acceptable values, it is better to enter differentvalues:


Table 2. Application Definition Panel Options.

Field Description

Subsystem Name The name by which automation knows theresource. It is better to keep it the same asyour current job name because that is thename by which your operators know theresource. If your TSO runs as TSO, then useTSO as the automation name. If it currentlyruns as TCAS or anything else, then use thatname.

The only time that you might not want todo so is if the job name is different on eachsystem. Automation Control links the sameapplication definition to multiple systems,but if you want a different automation nameon each system you either have to defineseparate applications for each system or youmake use of the automation symbol(AOCCLONE) functionality of AutomationControl (recommended).

Object type Leave as INSTANCE for now. An object type ofClass defines a set of common characteristicsthat can be inherited by multiple instanceslater on.

Application Type Set one of the options that are listed, asAutomation Control provides someadditional automation settings and optionsfor these resources.

Subtype Set if you are setting the Application Type.The Subtype is used to differentiate betweenthe different parts of an IMS, DB2, or CICSproduct for example.

Job Type For a normal address space, the job type isset to MVS. NONMVS address spaces arenot normal address spaces, for exampleUNIX System Services processes or NetViewREXX scripts. TRANSIENTS are addressspaces or jobs that shut down on their own.TRANSIENTS leave data installed andtherefore it is not required to rerun them.

Job Name For subsystems of type MVS, the name ofthe address space, as shown in an MVS DA,L command. Typically, the job namematches your subsystem name. Forsubsystems of type NONMVS, it is a uniquequalifier to distinguish the subsystem fromother subsystems.

Transient Rerun Valid if the subsystem is defined as atransient and indicates whether AutomationControl can ever rerun the transient beforethe next system IPL.


Table 2. Application Definition Panel Options. (continued)

Field Description

Scheduling Subsystem Set to MSTR for all of the address spacesthat get started before JES. Leave blank forresources that run under the default JESsubsystem. If you want to specify it forsubsystems that run under JES, you mustenter the proper JES z/OS subsystem name,which is typically JES2 or JES3.

JCL Procedure Name Name of the JCL procedure that is used tostart the address space. If not specified, thestart command is as follows:

S jobname

If specified, the start command is as follows:

S procname,JOBNAME=jobname

This command runs an address space fromthe 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 Row 1 of 20Command ===> ________________________________________________ SCROLL===> PAGE

Entry Type : Application PolicyDB Name : IACZ_DEMOEntry Name : TSO Enterprise Name : IACZ_DEMO

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_________ PACING GATE Select pacing gate_________ SERVICE PERIOD Select service period_________ 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 *******************************PF 1=HELP 2=SPLIT 3=END 4=RETURN 5=RFIND 6=RCHANGEPF 7=UP 8=DOWN 9=SWAP 10=LEFT 11=RIGHT 12=RETRIEVE

Select the SHUTDOWN policy. Enter an S next to SHUTDOWN and press Enter.

The Subsystem Shutdown Processing panel for TSO is displayed:


COMMANDS HELP--------------------------------------------------------------------------

Subsystem Shutdown ProcessingCommand ===> _______________________________________________________________


Shutdown Pass Interval. . (hh:mm:ss)

Line Commands: S/C (Cmd), 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 message


This panel defines commands and replies that are issued before the application isshut down (INIT). Included in the policy are three, increasingly more aggressiveshutdown command sequences (NORM, IMMED, and FORCE) and the commandthat is issued after the application is shut down (FINAL). For this exercise, define aNORM shutdown command. Select NORM by entering C in the Cmd column andpress Enter. If you are going to specify a Reply, you type an R instead.

The shutdown Command Processing panel is displayed:

COMMANDS HELP------------------------------------------------------------------------------

Command Processing : SHUTNORM Line 00000001 Col 001 075Command ===> _______________________________________________ Scroll ===> PAGE

Mixed case. . . NO (YES NO)

Cmd Ps AutoFn/* Command Text___ __ ________ ________________________________________________________________ __ ________ ________________________________________________________________ __ ________ ________________________________________________________________ __ ________ ________________________________________________________________ __ ________ ________________________________________________________________ __ ________ ________________________________________________________________ __ ________ ________________________________________________________________ __ ________ ________________________________________________________________ __ ________ _____________________________________________________________

******************************* Bottom of data *******************************


Automation Control issues commands in passes (the Ps column). In the first pass,all the pass 1 commands are issued. Automation Control then waits a while (theShutdelay interval on the Application Information Policy panel) before it issues thepass 2 commands and waits again. TSO can be shut down, for example, in twopasses. The first pass is an attempt to stop TSO with an MVS STOP command. Ifthat does not succeed, the second pass uses the MVS CANCEL command. Youdefine 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__________________________________________________ __ ________ ________________________________________________________________ __ ________ ________________________________________________________________ __ ________ _____________________________________________________________

You must prefix the stop command with the MVS literal because the commandsare issued from inside the NetView component of Automation Control. The MVSliteral is required to direct the command out to the z/OS operating system. The jobname in the stop command is specified as &SUBSJOB rather than as TSO.&SUBSJOB is a symbolic value that Automation Control substitutes with theapplication’s job name before it issues it the command. If you ever change the jobname, you must change it in one place rather than locating all occurrences of theold job name.

Press PF3 three times to return to the Entry Name Selection panel.

Repeat this process for VTAM and JES with appropriate job and procedure namesand shutdown commands. For JES you must enter the correct Application Type ofJES2 or JES3 and specify a Scheduling Subsystem of MSTR like as follows:

COMMANDS HELP------------------------------------------------------------------------------

Define New EntryCommand ===> ______________________________________________________________


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 are finished, your Entry Name Selection panel now looks something asfollows:



Entry Name Selection Row 2 of 3Command ===> _________________________________________________ SCROLL===> PAGE

Entry Type : Application PolicyDB Name : IACZ_DEMOEnterprise Name : IACZ_DEMO

Action Entry Name C Short Description__________ JES__________ TSO__________ VTAM******************************* Bottom of data *******************************


Relationships and Dependencies

Next, Automation Control would now issue all of the start commands at the sametime and the starts for VTAM and TSO would fail. To avoid complications, youmust specify the sequence in which the resources must be started (and stopped).

The functionality that Automation Control uses is known as relationships that arerun from the source (or dependent) resource to the target (or supporting) resource.Each type of relationship has a name and some can be complex. You are going touse one of the simple ones here: HasParent. A HasParent relationship embodies tworules:v The dependent resource cannot be started until the supporting resource is

runningv The supporting resource cannot be stopped while the dependent resource is still

running.

The dependent resource is sometimes referred to as the child, and the supportingresource is sometimes referred to as the parent.

The relationships that you must create are as follows:TSO ---- HasParent --> VTAMVTAM --- HasParent --> JES

You start by selecting the TSO application and selecting RELATIONSHIPS from itsPolicy Selection panel.

The Relationship Selection List panel is displayed:



Relationship Selection ListCommand ===> ________________________________________________________________No entries currently exist. Use the NEW command to create an entry.Entry Type : Application PolicyDB Name : IACZ_DEMOEntry Name : TSO Enterprise Name : IACZ_DEMO

External Startup. . . ________ (INITIAL ALWAYS NEVER)External Shutdown . . ________ (FINAL ALWAYS NEVER)

Action # Type Supporting Resource Auto Chain******************************* Bottom of data *******************************


Type new on the command line and press Enter to create a relationship:

COMMANDS HELP------------------------------------------------------------------------------

Define RelationshipCommand ===> ______________________________________________________________


Description. . . . . ________________________________________

Relationship Type. . _________________ MAKEAVAILABLE MAKEUNAVAILABLEPREPAVAILABLE PREPUNAVAILABLEHASPARENT HASPASSIVEPARENTHASMONITOR PEEROFFORCEDOWN EXTERNALLY

Supporting Resource. __________________Resource Name

Sequence Number. . . ___ Sequence Number (1-99,blank)

Automation . . . . . _________ ACTIVE PASSIVEChaining . . . . . . _______ STRONG WEAKCondition . . . . . _______________________________________________

Satisfy condition(? for list of possible values)



Enter hasparent as the Relationship Type and VTAM/APL/= as the SupportingResource. The specific notation for the supporting resource, with the equal sign (=)as a placeholder for the system name, means that the VTAM application that issharing the same system as the TSO application. If you linked the same pair ofapplication definitions to three different systems, each copy of TSO would bedependent on the corresponding copy of VTAM.

You then must repeat the entry to create a HasParent relationship from VTAM toJES.


Relationship Selection List Row 1 of 1Command ===> _______________________________________________________

Entry Type : Application PolicyDB Name : IACZ_DEMOEntry Name : VTAM Enterprise Name : IACZ_DEMO

External Startup. . . _________ (INITIAL ALWAYS NEVER)External Shutdown . . _________ (FINAL ALWAYS NEVER)

Action # Type Supporting Resource Auto Chain______ __ HASPARENT JES/APL/=

******************************* Bottom of data *******************************


Application GroupsAlthough you defined the three applications and a system, they are currently notconnected. You must create an application group, make the applications membersof the group and then link it to the system. You use a simple group. A simplegroup is a group without an automation name that does not appear in the modelthat the automation manager uses to run the system and the applications.

Select 5 from the Entry Selection Panel and you see something as follows:


Entry Name SelectionCommand ===> ______________________________________________ SCROLL===> PAGENo entries currently exist. Use the NEW command to create an entry.Entry Type : ApplicationGroup PolicyDB Name : IACZ_DEMO

Enterprise Name : IACZ_DEMO

Action Entry Name Short Description******************************* Bottom of data ********************************

Enter new base_sys on the command line and press Enter:


COMMANDS HELP------------------------------------------------------------------------------

Define New EntryCommand ===> ________________________________________________________

Define new entry of type ApplicationGroupEntry name . . . . . . . BASE_SYSType . . . . . . . . . . SYSTEM (SYSTEM SYSPLEX)Nature . . . . . . . . . BASIC (BASIC MOVE SERVER)Default Preference . . . _____ (0 to 3200, *DEF)Automation Name . . . . ______________Automatically link . . . YES (for Application-Resources)Behavior . . . . . . . . ACTIVE (ACTIVE PASSIVE)Prepare Move . . . . . . ___ (YES NO)Move Mode . . . . . . . ________ (PARALLEL SERIAL)Short Description . . . ___________________________Long Description 1 . . . ________________________________________Long Description 2 . . . ________________________________________Long Description 3 . . . ________________________________________Long Description 4 . . . ________________________________________Long Description 5 . . . ________________________________________


Press Enter to start the defaulting process. The automation name gets set to theentry name. A Simple group is not used for automation. Because you do not createa resource, overwrite the Automation Name with blank spaces. You provide adescription if you want. Press PF3 when you are finished and you see the PolicySelection panel.

ACTIONS HELP------------------------------------------------------------------------------

Policy Selection Entry createdCommand ===> ________________________________________________ SCROLL===>PAGE

Entry Type : ApplicationGroup PolicyDB Name : IACZ_DEMOEntry Name : BASE_SYS Enterprise Name : IACZ_DEMOAction Policy Name Policy Description_________ DESCRIPTION Enter description_________ APPLGROUP INFO Define applicationgroup information_________ APPLICATIONS Select applications for system APG_________ TRIGGER Select trigger_________ SERVICE PERIOD Select service period_________ RELATIONSHIPS Define relationships_________ MESSAGES/USER DATA Define messages and user data_________ -------------------- -----RESOURCES-------------------------------_________ RESOURCES Select resources and set preferences_________ GENERATED RESOURCES List resources generated for this entry_________ MEMBER OF List resources where this entry is a member_________ -------------------- ---------------------------------------------_________ WHERE USED List systems linked to this entry_________ COPY Copy data from existing entry******************************* Bottom of data ********************************PF 1=HELP 2=SPLIT 3=END 4=RETURN 5=RFIND 6=RCHANGEPF 7=UP 8=DOWN 9=SWAP 10=LEFT 11=RIGHT 12=RETRIEVE

Select the APPLICATIONS Policy:



Applications for ApplicationGroup Row 1 of 3Command ===> ______________________________________________ SCROLL===> PAGE

Entry Type : ApplicationGroup PolicyDB Name : IACZ_DEMOEntry Name : BASE_SYS Enterprise Name : IACZ_DEMO

Action Status Application_________ JES_________ TSO_________ VTAM******************************* Bottom of data ********************************PF 1=HELP 2=SPLIT 3=END 4=RETURN 5=RFIND 6=RCHANGEPF 7=UP 8=DOWN 9=SWAP 10=LEFT 11=RIGHT 12=RETRIEVE

Then, select the three applications by typing an s next to each of them:

Entry Type : ApplicationGroup PolicyDB Name : IACZ_DEMOEntry Name : BASE_SYS Enterprise Name : IACZ_DEMO

Action Status Application_________ SELECTED JES_________ SELECTED TSO_________ SELECTED VTAM

Press PF3 to return to the Application Group Policy Selection panel.

Then, select the WHERE USED policy:


Where Used Row 1 of 1Command ===> _______________________________________________ SCROLL===>PAGE

Entry Type : ApplicationGroup PolicyDB Name : IACZ_DEMOEntry Name : BASE_SYS Enterprise Name : IACZ_DEMOAction Status Name Type_________ SYS1 SYS******************************* Bottom of data ********************************

Select SYS1 and press Enter and then press PF3. You see some resource creationmessages displayed.

You now make the link between the Applications and the System, with just asimple group. Press PF4. You return to the main Customization Dialog panel.

Reporting

Select option 3 Report on the Automation Control for z/OS 1.1.1 CustomizationDialog panel to display the Report Selection Menu.


MENU HELP-----------------------------------------------------------------------------

Report Selection MenuOption ===> ______________________________________________________________

1 Report Create Policy Database Report

2 Unlinked Create List of entries not linked in Policy Database3 ViewUnlinked View List of unlinked entries

4 Resources Create List of generated Resources5 ViewResources View List of generated Resources

6 MemberList Create List of unused members in configuration data set7 ViewMemberList View List of unused members

8 StatusMsgs Create Status Messages Report9 ViewStatusMsgs View Status Messages Report

A Symbols Create List of Symbols (AOCCLONEx) in Policy DatabaseB ViewSymbols View List of Symbols

Enter option 4 to generate a Resource Report. After it finishes, enter a 5 to view theresources report. The resources that are linked to specified systems are displayed:

************************************************************************** Function RESOURCE REPORT* Policy Database name IACZ_DEMO* Policy Database data set name ’MIK.IACZ.DEMO.PDB’* Product Version Automation Control for z/OS 1.1.1** UserId MIK* Creation Date Monday, 4 Aug 2014* Creation Time 08:37*************************************************************************

Monitor resources (MTR) for system: SYS1

Application resources (APL) for system: SYS1JES/APL/SYS1 JES via APG: BASE_SYSTSO/APL/SYS1 TSO via APG: BASE_SYSVTAM/APL/SYS1 VTAM via APG: BASE_SYS

ApplicationGroup (APG) resources for system: SYS1Sysplex ApplicationGroup (APG) resources

You see the system and the three resources that you linked to the system. There areno APG resources because you used a Simple group, which does not generate aresource.

The other reports work in a similar way except for Option 1, which provides formore specifications. Option 1 shows a default report data set name. Or, if no reportis run yet, you are prompted for the name of the data set and member the report isto be written to. You have the option of running the report in batch model to freeup your TSO account. Locate and browse the data set through ISPF to review theoutput. If you generate a report in HTML format, you can download it to your PCto browse it.


Adding More Systems

If you want to add extra systems, you must create the systems and link them totheir System Group and the BASE_SYS Application Group. Complete the followingsteps:v Select Option 4 Systems from Entry Selection panel.v Enter new SYSx to create the Systems policy.v Use APPLICATION GROUPS policy to select the BASE_SYS APG.v Use WHERE USED policy to select their System Group.

Then, run the resources report again:

Application resources (APL) for system: SYS1

JES/APL/SYS1 JES via APG: BASE_SYSTSO/APL/SYS1 TSO via APG: BASE_SYSVTAM/APL/SYS1 VTAM via APG: BASE_SYS





As you can see, it is easy to reuse existing policy elements to populate extrasystems.

Cloning with Symbolic ValuesThere are times when the policy is similar but not the same on each system. So farin this example, the job name for VTAM is VTAM, but now suppose that it isNETnn, where nn was the systems subarea identifier. The following job names forVTAM are given as shown in Table 3.

Table 3. Possible Job name values

SYS1 NET31

SYS2 NET47

SYS3 NETT2

The subarea identifiers are deliberately used to make the values diverse.

Now, you might think that you are required to define a different VTAMApplication for each system and a different application group to link it to theappropriate system. Fortunately, Automation Control supports a mechanism that iscalled Cloning. With Cloning, you specify substitutable fields in variousparameters, including an Application’s job name, and specify different values tosubstitute for each system.

First, you must edit the Application Information panel for the VTAM APL andspecify NET&AOCCLONE1. as the job name:


COMMANDS HELP------------------------------------------------------------------------------

Application Information Line 00000001Command ===> ______________________________________________ Scroll===> PAGEEntry Type : Application PolicyDB Name : IACZ_DEMOEntry Name : VTAM Enterprise Name : IACZ_DEMO

Category . . . . . . . . . ____________ (IBM-defined, user-defined or blank,see help)

Subcategory . . . . . . . ___________ (IBM-defined, user-defined or blank,see help)

Subsystem Name . . . . . . VTAM_______Job Type . . . . . . . . . _________ (MVS NONMVS TRANSIENT)Job Name . . . . . . . . . NET&AOCCLONE1.Transient Rerun . . . . . ____ (YES NO)Scheduling Subsystem . . . ____ (MSTR, JES Subsystem)JCL Procedure Name . . . . ______________Job Log Monitor Interval . _____ (mm:ss NONE)Captured Messages Limit . ___ (0 to 999)Desired Available . . . . __________ (ALWAYS ONDEMAND ASIS)Restart after IPL . . . . ________ (START NOSTART NONE)Monitor for IPL complete . ___ (YES NO)Start Delay . . . . . . . ________ (time for "UP" status checks, hh:mm:ss)Start Cycles . . . . . . . __ (start delay checks, 0 to 99)UP Status Delay . . . . . ________ (time to delay "UP" status, hh:mm:ss)Restart option . . . . . . ___________ (ALWAYS ABENDONLY NEVER)External Startup . . . . . _______ (INITIAL ALWAYS NEVER)PF 1=HELP 2=SPLIT 3=END 4=RETURN 5=RFIND 6=RCHANGEPF 7=UP 8=DOWN 9=SWAP 10=LEFT 11=RIGHT 12=RETRIEVE

Press PF3 to save the change and then select one of the systems:

ACTIONS HELP------------------------------------------------------------------------------

Policy Selection Row 1 of 28Command ===> _________________________________________________ SCROLL===>PAGE


Action Policy Name Policy Description________ DESCRIPTION Enter description________ SYSTEM INFO Enter and display system information________ AUTOMATION SYMBOLS Define system automation symbols (AOCCLONEx)________ AUTOMATION CONSOLE Enter MVS route codes for notifications________ APPLICATION GROUPS Select application groups________ MONITOR RESOURCES Select monitor resources________ AUTOMATION TIMERS Select timers________ USER E-T PAIRS Select user entry-type pairs________ RESIDENT CLISTS Select resident clists________ TAPE ATTENDANCE Select tape attendance________ APPLICATION DEFAULTS Select application defaults________ SYSTEM DEFAULTS Select system defaults________ MVSCOMP DEFAULTS Select MVS component defaults________ MVS COMPONENT Select MVS components________ NETWORK Select network definitions________ AUTOMATION OPERATORS Select automation operators________ STATUS DISPLAY Select status display facility details________ NOTIFY OPERATORS Select notify operators________ OPC SYSTEM DETAILS Select OPC system details________ CONTROLLER DETAILS Select OPC controller details________ WORKSTATION DOMAINS Select OPC Workstation domainsPF 1=HELP 2=SPLIT 3=END 4=RETURN 5=RFIND 6=RCHANGEPF 7=UP 8=DOWN 9=SWAP 10=LEFT 11=RIGHT 12=RETRIEVE

You want the System Automation Symbols policy, where you must enter thecorrect data for the AOCCLONE1 symbolic:


COMMANDS HELP------------------------------------------------------------------------------

System Automation Symbols (AOCCLONEx)Command ===> _________________________________________________________________


More: +AOCCLONE . . . . ________General Use:Description . . ________________________________________________________________AOCCLONE1. . . . 31General Use:Description 1 . Network subarea identifier______________________________________AOCCLONE2. . . . ________General Use:Description 2 . ________________________________________________________________AOCCLONE3. . . . ________General Use:Description 3 . ________________________________________________________________AOCCLONE4. . . . ________General Use:Description 4 . ________________________________________________________________AOCCLONE5. . . . ________General Use:Description 5 . ________________________________________________________________AOCCLONE6. . . . ________General Use:Description 6 . ________________________________________________________________AOCCLONE7. . . . ________PF 1=HELP 2=SPLIT 3=END 4=RETURN 5=RFIND 6=RCHANGEPF 7=UP 8=DOWN 9=SWAP 10=LEFT 11=RIGHT 12=RETRIEVE

There is no reason why you are using AOCCLONE1 for the subarea identifier. Ifyou are consistent between systems about the value that you assign to each cloneidentifier, you can set up the values how you want. There are a total of 37 clonevalues that can be assigned. You must plan carefully to avoid conflicts. Under theEnterprise Entry, there is a policy that defines your AOCCLONE descriptions on aglobal basis. The dialog shows the descriptions whenever you edit a system’s clonevalues.

Repeat the definitions for SYS2 and SYS3, being sure to enter the correct values:


More: +AOCCLONE . . . . ________General Use:Description . . ________________________________________________________________AOCCLONE1. . . . 47______General Use:Description 1 . Network subarea identifier______________________________________


More: +AOCCLONE . . . . ________General Use:Description . . ________________________________________________________________AOCCLONE1. . . . T2______General Use:Description 1 . Network subarea identifier______________________________________

You cannot check the definitions with resources report because this report lists theApplication automation name but not its job name.


The Symbol report (A to generate and B to view) shows us our defined symbols:

**********************************************************************-------- Symbolname ----------- |General UseSystem |Value |Description*-------- AOCCLONE ------------ |*-------- AOCCLONE1 ------------ |SYS1 |31 |Network subarea identifierSYS2 |47 |Network subarea identifierSYS3 |T2 |Network subarea Identifier

And a full report verifies that the job name for VTAM is correctly defined:

ApplicationsSubsystem Name VTAMJob Name NET&AOCCLONE1.

RelationshipsRelationship Type Supporting ResourceHASPARENT JES/APL/=

To actually see the results of the substitution, you would have to generate a fullSOCNTL data set and load the data set into a running instance of AutomationControl.

Although you now run different jobs on each of the systems, the definition youmade for the applications in your dependency structure is still present. They arepresent because, the dependencies are defined in terms of the automation namesassigned to the Applications rather than assigned to their job names.

Defaults, Classes, and Inheritance

Defaults are a mechanism that can save you some time. Automation Controlprovides defaults that are hardcoded for most values. You can also specify yourown set of defaults for Systems, MVS Component Automation, and ApplicationAutomation. Select ADF for the entry and define a new entry, for example, with thename MY_DEFAULTS:

COMMANDS HELP------------------------------------------------------------------------------

Application Information DefaultsCommand ===> ___________________________________________________________

Entry Type : Application Defaults PolicyDB Name : IACZ_DEMOEntry Name : MY_DEFAULTS Enterprise Name : IACZ_DEMO

Captured Messages Limit. . ___ (0 to 999)Monitor Routine . . . . . ________ (name NONE)Startup information:Restart after IPL . . . . _______ (START NOSTART)Start Delay . . . . . . . ________ (time for "UP" status checks, hh:mm:ss)Start Cycles . . . . . . . __ (start delay checks, 0 to 99)Restart Option . . . . . . _________ (ALWAYS ABENDONLY NEVER)Shutdown information:Shutdown Pass Interval . . ________ (hh:mm:ss)Cleanup Delay . . . . . . ________ (hh:mm:ss)

The defaults are mainly for the timing intervals between various actions that theagent takes during the automation of the resource.


Classes and Inheritance

A powerful technique available with the Customization Dialog is that of classesand inheritance. When you create an application, you can say that it is a CLASSdefinition rather than an INSTANCE of an application:

COMMANDS HELP------------------------------------------------------------------------------



Entry name . . . . . . . DB2_CLASS

Subsystem Name . . . . . ______________Object Type . . . . . . CLASS (CLASS INSTANCE)Category . . . . . . . . __________ (IBM-defined, user-defined or blank,

see help)Subcategory . . . . . . __________ (IBM-defined, user-defined or blank,

see help)

An application that is defined as a CLASS does not generate automateableresources. It can, however, be specified as the upward class of other applications:

COMMANDS HELP------------------------------------------------------------------------------

Define New EntryCommand ===> _____________________________________________________________


Entry name . . . . . . . DB2_T100MSTR_____

Subsystem Name . . . . . T100MSTR_____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 . . . . . . . . T100MSTRTransient Rerun . . . . ___ (YES NO)

Select Policy UPWARD CLASS:


Upward Link to Class Row 1 of 1Command ===> ______________________________________________ SCROLL===> PAGE

Entry Type : Application PolicyDB Name : IACZ_DEMOEntry Name : DB2_T100MSTR Enterprise Name : IACZ_DEMO

Action Status Entry Name Type Upward Class Link________ SELECTED DB2_CLASS******************************* Bottom of data ********************************

With this specification, the application that is linked to the class inherits all of theclass’s policies. If you are running, five DB2 subsystems, you can create a singleDB2 Application Class, which holds all of the complicated DB2 automationpolicies. Then, you link it as the Upward Class of the five Application instancesthat represent your DB2 subsystem. You do not have to type in and maintain yourpotentially complex DB2 automation five times.


Adapt the Sample PoliciesWhen you are using the Customization Dialog tutorial, you notice there are manytasks that are involved in creating your own automation policy from scratch. MostAutomation Control customers find it much easier to start with the set of samplepolicies that come with Automation Control.

You now use the *BASE_AND_PRODUCTS add-on or sample policy andcustomize the key components that are required for this installation. You can startwith a new Policy Database, by following the instructions that are given in “ANew Policy Database.” Alternatively you start with the Policy Database youcreated, installed, and verified as described in “Start IBM Automation Control forz/OS for the First Time” on page 21.

A New Policy Database

You must create a new Policy Database. Start from the main menu:






To switch to another Policy Database, specify the Policy Database namein the following field, or specify a ? to get a selection list.Current Policy Database . . . IACZ_DEMO


Select option 4 for the Policies choice:


Policy Database Selection Row 1 of 27Command ===> ________________________________________________ SCROLL===>PAGEAction Policy Database Enterprise Name______ IACZ_DEMO IACZ_DEMO

Type new IACZ_FULL on the command line and press Enter. You can use whatevername you want for your enterprise:



Create a New Policy Database Row 1 of 1Command ===> _______________________________________________________

To define a new Policy Database, specify the following information:Policy Database Name . . IACZ_FULL__________Enterprise Name. . . . . IACZ_FULL__________Data Set Name. . . . . . IACZ.FULL.PDB_______________Model Policy Database. . *EMPTY____________ Policy Database name or "?"

for list of namesAdd-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 ********************************

Complete the Data Set Name field. Remember you might not want to use apersonal HLQ if the data set is to be shared between several updaters.

Enter c in the Action field to customize the policy.


Select Add-on Policy Components Row 1 to 14 of 14

Components of Add-on Policy : *BASE_AND_PRODUCTS

Select one or more components to be added to your Policy Database:

Action Status ComponentSELECTED z/OS Health CheckerSELECTED Automation Command ReceiverSELECTED Automation RDS ArchiverSELECTED Base z/OSSELECTED Communication Services (USS)SELECTED CICSSELECTED DB2SELECTED Event/Automation ServiceSELECTED IMSSELECTED Job Entry Subsystem 2 (JES2)

m SELECTED Job Entry Subsystem 3 (JES3)SELECTED OMEGAMON for z/OSSELECTED Processor Operations (ProcOps)SELECTED Tivoli Workload Scheduler (TWS)

******************************* Bottom of data ********************************

Enter m in the Action field to remove selections that are not needed, for example,Job Entry SubSystem (JES3).

Press Enter and then press PF3 to close this panel.


Create a New Policy Database Row 1 to 1 of 1

To define a new Policy Database, specify the following information:Policy Database Name . . IACZ_FULLEnterprise Name. . . . . IACZ_FULLData Set Name. . . . . . ’IACZ.FULL.PDB’

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

CUSTOMIZED *BASE_AND_PRODUCTS YES******************************* Bottom of data ********************************


Press Enter and the data set allocation panel comes up:

COMMANDS HELP------------------------------------------------------------------------------

New Policy Database data set InformationCommand ===>

New Policy Database : IACZ_FULLAttributes to be used for allocation of the new data set:

Managed storage. . . . . YES YES NOManagement class . . . . Blank for default management class *Storage class. . . . . . Blank for default storage class *Volume serial. . . . . Blank for authorized default volume

Data class . . . . . . . Blank for default data class *Space units. . . . . . CYLINDERS CYLS TRKS BLKS KB MBPrimary quantity . . . 3 1 to 999 - In above unitsSecondary quantity . . 1 0 to 999 - In above unitsDirectory blocks . . . 50 1 to 999Record format. . . . : FBRecord length. . . . : 80Block size . . . . . . 32720Data Set Name type . . PDS LIBRARY PDSDevice Type. . . . . . SYSDA

* Used only if Managed storage = YES

Press Enter to begin creating a Policy Database.

Ensure that you have at least 3 CYLINDERS as your Primary Quantity. 4 or 5 isbetter if you have many systems, more applications, or both to define.

Press Enter when you are ready. You see some progress messages as your PDB iscreated and the sample policies are copied over.

COMMANDS HELP- ┌──────────────────────────────────────────────────────────────────────────┐│ Command Progress Display │

C │ ││ Source : ’SYS1.IACZ.V111.SINGIPDB’ │

N │ Target : ’USER1.IACZ.FULL.PDB’ │A │ Copy complete ││ Adding entry for "IACZ_FULL" to list of Databases ││ Rename of entries associated with Enterprise name ││ Rename complete ││ Open the selected add-on policies. ││ Analyze add-on policy ’*BASE_AND_PRODUCTS’. ││ Read data from add-on policy ’*BASE_AND_PRODUCTS’. ││ Opening tables. ││ Progress : _____________________ 36 % ││ ││ ││ PF 1=HELP 2=SPLIT 3=END 4=RETURN 5=RFIND 6=RCHANGE ││ PF 7=UP 8=DOWN 9=SWAP 10=LEFT 11=RIGHT │└──────────────────────────────────────────────────────────────────────────┘

Data Set Name type . . PDS LIBRARY PDS

On completion, you are on the Entry Type Selection panel for your new PDB.

Look at the APLs and APGs that are defined (options 5 and 6). As you can see,there are quite a few of them. Many of the APLs likely have the wrong job namesfor your systems.

At this stage, the default system name might need to be renamed.

You must also prepare the recovery flag for certain MVSESA resources.


Adding Sample Policies

Before you begin

Start from the main menu with your policy database selected:






To switch to another Policy Database, specify the Policy Database namein the following field, or specify a ? to get a selection list.Current Policy Database . . . IACZ_FULL


Procedure1. Select option 5 Data Management.

MENU HELP------------------------------------------------------------------------------

Data Management MenuOption ===> 2_______________________________________________________________

1 Import from PDB Import from a Policy Database

2 Import from Add-on Import from predefined add-on policies

3 Update via File Write selected data to file or read data from file

2. Select option 2 - Import from Add-on. The Import Add-on Policies panel isdisplayed:

ACTIONS HELP------------------------------------------------------------------------------

Import Add-on Policies Row 1 of 1Option ===>

1 Import selected add-on policies2 View import report

Current Policy Database: IACZ_FULLAdd-on policies to be added to the current policy database:Action Status Add-on Policy Customizable

*BASE_AND_PRODUCTS YES******************************* Bottom of data *******************************

3. Enter an s in the Action column for it to select the *BASE_AND_PRODUCTSpolicy and press Enter.

4. Enter 1 on the option line and press Enter. After you see some processingprogress messages, you see this panel:


OPTIONS ACTIONS HELP------------------------------------------------------------------------------

Entries of selected Add-on Policies Row 1 of 179Option ===> SCROLL===> CSR

1 Modify data 2 Check data 3 Run import 4 View report

Action Entry Name Type C D Short Description_______ MONOPLX1 GRP Automation Control Sample Monoplex_______ SYS1 SYS System 1 of the Sample Monoplex_______ AM_X APG Automation Manager Group for Monoplex_______ BASE_ITM APG ITM Base Components_______ BASE_SYS APG Y Base z/OS, Network and Automation_______ CICS APG Y All CICS Components_______ CICS_SHARED APG Y CICS Shared Servers for CF Structures_______ CICS1 APG Y CICS Instance #1_______ CICS1TG APG Y CICS Transaction Gateway APG_______ CMD_RECEIVER APG Y Automation Command Receiver_______ CPSM APG Y CICSPlex SM_______ DB21 APG Y DB2 Subsystem - DB21_______ EVT_AUTO_SRV APG Event/Automation Service_______ FTP_DAEMON_GROUP APG Y File Transfer Protocol Daemon_______ IMS APG Y IMS All Components_______ IMS_SUPPORT APG Y IMS Support subsystems_______ IMSA_CSLMGR APG Y IMSPlex A Common Service Layer Manager_______ IMS1 APG Y IMS Instance #1_______ IMS1_APPLICATIONS APG Y IMS Application Regions_______ IMS1_CTRL APG Y IMS Control Region_______ KAH_TEMA APG Automation Monitoring Agent (TEMA)_______ OM_ZOS APG OMEGAMON for z/OSPF 1=HELP 2=SPLIT 3=END 4=RETURN 5=RFIND 6=RCHANGEPF 7=UP 8=DOWN 9=SWAP 10=LEFT 11=RIGHT 12=RETRIEVE

This panel can be used to import policies into your existing policy databaseselectively and carefully . You must now import all the policies that you thinkyou need for your initial automation. It might be no more than the starter setthat you put together for the verification test or it can be every policy in thesample. You can return to this panel to import more policies at any time. Onthis panel you can do the following things:v Remove policies that you do not want to import by entering an M against

them. Important: Be warned that if you remove something you actually wantthere is no way to restore it on this import run.

v Change entry names and short descriptions.v Change entry names by entering an R against them.v Request a global substitution of 1 string for another by entering 1 on the

option line.v Ask for the data to be verified and cross checked by entering 2 on the option

line.v Ask for the import run to be performed by entering 3 on the option line.v View the report of your last import run that is run by entering 4 on the

option line.

It is not sufficient to change the entry name to differentiate it from previousinstances of the policy that might be imported. You must perform a globalsubstitution. Changing the entry name of the SYS1 entry to SYS2 does notimport it a second time. However, performing a global substitution of SYS1with SYS2 does import it.

Note: Global substitution works by affecting all policies that are still in the list.Use with caution and with small groups of policies or you might seeunexpected consequences.


5. Press PF3 to exit without doing anything. Any changes that were not importedare lost.

Bulk UpdateAlthough you could go through each of the defined applications (APL) insequence, open up its Application Information policy item and update its jobname. There is an alternative faster way of editing application policy information.

Export

Press PF3 to go to the main Automation Control for z/OS 1.1.1 CustomizationDialog panel and select option 5 Data Management:

MENU HELP------------------------------------------------------------------------------

Data Management MenuOption ===> 3_______________________________________________________________

1 Import from PDB Import from a Policy Database

2 Import from Add-on Import from predefined add-on policies

3 Update via File Write selected data to file or read data from file

Select option 3 Update via File from the Data Management Menu:

MENU HELP------------------------------------------------------------------------------

Policy Database Update SelectionOption ===> 1________________________________________________________________

1 Write selected data from Policy Database to fileEntry Type . . . . . . . APL_______________ (? or type)Output File Name . . . . IACZ.FULL.FLATFILE

2 Perform syntax check for data in file3 Update Policy Database with data from file

Input File Name. . . . . ____________________________Mode . . . . . . . . . . ONLINE (ONLINE BATCH)

4 View write / update report

5 Edit output file

6 Append NEW/DEL templates to output file

Job statement information: (used for BATCH update)//AOFBUILD JOB________________________________________________________________//*___________________________________________________________________________//*___________________________________________________________________________

Specify APL as the selection criteria and give it an output data set name. The dataset has ALTER access as it must allocate it. Press Enter.

If the output data set name does not exist, it is allocated when the file updatestarts. If a name is not specified, a default data set name is used, which is the PDBdata set name with .UPD appended as low-level qualifier.

You now have the Entry Name Selection panel, showing all the APLs in the samplepolicy:



Entry Name Selection Row 1 of 105Command ===> _______________________________________________ SCROLL===>PAGE

Action Status Entry Name Short Description_______ AM Automation Manager_______ AM2 Spare Automation Manager_______ APPC Advanced Peer-to-Peer Communication_______ ASCH APPC Scheduler_______ BLSJPRMI Build SNAP Tables for IPCS_______ C_AM Class for Automation Manager Definitions_______ C_APPL Class for general APL definitions_______ C_CICS Class for CICS_______ C_CICS_CMAS Class for CICS CPSMCMAS_______ C_CICS_SHAREDSERVERS Class for CICS Shared Servers_______ C_CICS_TG Class for CICS Transaction Gateway_______ C_CICS_WUI Class for CICS CPSMWUI_______ C_CICS_XACTIONSERVER Class for CICS Transaction Server_______ C_DB2_DEPENDENTS DB2 Class - DIST,DBM1,IRLM_______ C_DB2_MSTR DB2 Class - DB2 Master_______ C_DB2_NORM DB2 Class - DB2 Master Normal Mode_______ C_IMS_APPLICATIONS Class for IMS Application Regions_______ C_IMS_CONTROL Class for IMS Control regions_______ C_IMS_DBCTL Class for IMS Control Regions (DBCTL)_______ C_IMS_DBDC Class for IMS Control Regions (DB/DC)_______ C_IMS_FDBR Class for IMS Fast DB Recovery (FDBR)_______ C_IMS_GENERIC Class for IMS OM regions_______ C_IMS_SUBORDINATES Class for IMS Subordinate Regions_______ C_IMS1_BMP_APPLS Class for IMS1 BMP RegionsPF 1=HELP 2=SPLIT 3=END 4=RETURN 5=RFIND 6=RCHANGEPF 7=UP 8=DOWN 9=SWAP 10=LEFT 11=RIGHT 12=RETRIEVE

Select all of the APLs that are not classes. The classes all start with a C_ prefix.Type s * on the command line and press Enter. Then, enter an m against each ofthe C_ APLs and press Enter. You must scroll down to get all of the C_ APLs.

You end up with the following panel:


Entry Name Selection Row 25 of 105Command ===> ________________________________________________ SCROLL===>PAGE

Action Status Entry Name Short Description_______ C_IMS1_SUBORDINATES Class for IMS1 Subordinate Regions_______ C_IMS1_TP_APPLS Class for IMS1 FP/MP Regions_______ C_JES2 Job Entry Subsystem 2_______ C_TWS Used for TIVOLI Workload scheduler defs_______ C_USS_APPL Class for USS Application_______ C_USS_FILE Class for USS Files_______ C_USS_PORT Class for USS Port_______ SELECTED CICSDT CICS Shared Data Tables CF Support_______ SELECTED CICSNC CICS Shared Named Counter CF Support_______ SELECTED CICSTS CICS Shared Temp. Storage CF Support_______ SELECTED CICS1AR1 CICS1 Application Owning Region #1_______ SELECTED CICS1TGD CICS1 Transaction Gateway Daemon_______ SELECTED CICS1TGM CICS1 Transaction Gateway Master Process_______ SELECTED CICS1TOR CICS1 Terminal Owning Region_______ SELECTED CMDRCVR Automation Command Receiver Task_______ SELECTED CPSMCMAS CICSPlex SM Address Space (CMAS)_______ SELECTED CPSMLIST CICSPlex SM CPSM Event Listener_______ SELECTED CPSMWUI CPSM Web User Interface Server_______ SELECTED CRON Time-based job scheduler in Unix like OS_______ SELECTED DB21ADMT DB21 Administrative Scheduler_______ SELECTED DB21DBM1 DB21 Database Services_______ SELECTED DB21DIST DB21 Distributed Data Facility_______ SELECTED DB21IRLM DB21 Resource Lock Manager_______ SELECTED DB21MSTR DB21 Master


Press Enter and you see the Policy Selection panel:


Policy Selection Row 1 of 24Command ===> ________________________________________________ SCROLL===>PAGESelect one or more policies to be written to file:

Action Status Policy Name_______ SELECTED DESCRIPTION_______ UPWARD CLASS_______ SELECTED APPLICATION INFO_______ AUTOMATION FLAGS_______ APPLICATION SYMBOLS_______ RELATIONSHIPS_______ MESSAGES/USER DATA_______ STARTUP_______ SHUTDOWN_______ THRESHOLDS_______ MINOR RESOURCES_______ CICS CONTROL_______ DB2 CONTROL_______ OPC CONTROL_______ IMS CONTROL_______ SELECTED USS CONTROL_______ JES2 SPOOLFULL CNTL_______ JES2 SPOOLFULL CMDS_______ JES2 SPOOLSHORT CNTL_______ JES2 SPOOLSHORT CMDS_______ JES2 DRAIN CMDS_______ JES3 SPOOLFULL CMDSPF 1=HELP 2=SPLIT 3=END 4=RETURN 5=RFIND 6=RCHANGEPF 7=UP 8=DOWN 9=SWAP 10=LEFT 11=RIGHT 12=RETRIEVE

For now, we want the DESCRIPTION, APPLICATION INFORMATION, and USSCONTROL policy data. Enter an S against them to select them and press Enter.

Press Enter again after you selected them and you see a Confirmation Panel:

COMMANDS HELP------------------------------------------------------------------------------

Write to File Confirmation Row 1 of 79Command ===> SCROLL===>PAGEThe following entries have been selected to write data to file.Press ENTER to write data to file.Press CANCEL or END to cancel writing data.Selected Names DescriptionAM Automation ManagerAM2 Spare Automation ManagerAPPC Advanced Peer-to-Peer CommunicationASCH APPC SchedulerBLSJPRMI Build SNAP Tables for IPCSCICSDT CICS Shared Data Tables CF SupportCICSNC CICS Shared Named Counter CF SupportCICSTS CICS Shared Temp. Storage CF SupportCICS1AR1 CICS1 Application Owning Region #1CICS1TGD CICS1 Transaction Gateway DaemonCICS1TGM CICS1 Transaction Gateway Master ProcessCICS1TOR CICS1 Terminal Owning RegionCMDRCVR Automation Command Receiver TaskCPSMCMAS CICSPlex SM Address Space (CMAS)CPSMLIST CICSPlex SM CPSM Event ListenerCPSMWUI CPSM Web User Interface ServerCRON Time-based job scheduler in Unix like OSDB21ADMT DB21 Administrative SchedulerDB21DBM1 DB21 Database ServicesDB21DIST DB21 Distributed Data FacilityPF 1=HELP 2=SPLIT 3=END 4=RETURN 5=RFIND 6=RCHANGEPF 7=UP 8=DOWN 9=SWAP 10=LEFT 11=RIGHT 12=RETRIEVE


The panel, when you scroll it, contains the names of all of the APLs that you wantto export.

Press Enter and a progress dialog is displayed:

COMMANDS HELP- ┌──────────────────────────────────────────────────────────────────────────┐│ Command Progress Display │

C │ ││ Writing data to file for APL CICS1TGD. │

T │ Writing data to file for APL CICS1TGM. │P │ Writing data to file for APL CICS1TOR. │P │ Writing data to file for APL CMDRCVR. ││ Writing data to file for APL CPSMCMAS. │

S │ Writing data to file for APL CPSMLIST. │A │ Writing data to file for APL CPSMWUI. │A │ Writing data to file for APL CRON. │A │ Writing data to file for APL DB21ADMT. │A │ Writing data to file for APL DB21DBM1. │B │ │C │ │C │ │C │ PF 1=HELP 2=SPLIT 3=END 4=RETURN 5=RFIND 6=RCHANGE │C │ PF 7=UP 8=DOWN 9=SWAP 10=LEFT 11=RIGHT │C └──────────────────────────────────────────────────────────────────────────┘CICS1TGM CICS1 Transaction Gateway Master ProcessCICS1TOR CICS1 Terminal Owning Region

On completion, you return to the Policy Database Update Selection panel:

MENU HELP------------------------------------------------------------------------------

Policy Database Update Selection Data written to fileOption ===> _________________________________________________________

1 Write selected data from Policy Database to fileEntry Type . . . . . . . APL________________ (? or type)Output File Name . . . . IOCZ.FULL.FLATFILE______________

2 Perform syntax check for data in file3 Update Policy Database with data from file

Input File Name. . . . . IOCZ.FULL.FLATFILE______________Mode . . . . . . . . . . ONLINE (ONLINE BATCH)

4 View write / update report

5 Edit output file

6 Append NEW/DEL templates to output file

You notice that the name of our output file is completed under option 3 Import.Now, do not use the Customization Dialog to edit any of the APL data, which arewritten to file. The import step that we intend to make issues a warning if thosedata sets are edited through the dialog between when we exported the data andwhen we reimport it. And if you confirm running the import, then it overwritesthe intermediate changes in the PDB.

UpdateYou might want to do some research and planning before you start the updatestep. Find out all your job name and procedure names. Find out your UNIXSystem Services paths, ports, and files. If you must use AOCCLONE values toshare definitions between multiple systems, plan the clone values that you aregoing to use. Then, work out the job names with the clone substitutions specified.

Select option 5 to edit the data in the file:


File Edit Edit_Settings Menu Utilities Compilers Test Help───────────────────────────────────────────────────────────────────────────────EDIT MIK.IACZ.FULL.FLATFILE Columns 00001 00072Command ===> _______________________________________________ Scroll===> CSR

****** ***************************** Top of Data ******************************000001 * UserId MIK000002 * PolicyDB Name IACZ_FULL000003 * PolicyDB Data Set MIK.IACZ.FULL.PDB000004 * Version 1.1.1000005 * Creation Date Monday,4 Aug 2014000006 * Creation Time 08:31:56000007000008 FILE CREATION TIMESTAMP 20140804083156000009000010 UPD APL - AM000011 DESCRIPTION ( field replacement )000012 Short Description : Automation Manager000013 Long Description 1 : At least on Automation Manager operat000014 Long Description 2 : Primary AM and one operating as Secon000015 Long Description 3 : should be available.000016 Long Description 4 :000017 Long Description 5 :000018 APPLICATION INFO ( field replacement )000019 Restart after IPL :000020 Start Delay :000021 Start Cycles :000022 Restart option :000023 External Startup :000024 Startup Parameters :000025 External Shutdown :F1=Help F2=Split F3=Exit F5=Rfind F6=Rchange F7=UpF8=Down F9=Swap F10=Left F11=Right F12=Cancel

The file display is a standard ISPF edit session on the data set holding theexported data. The data in the file is case-sensitive and the indentations on the leftside are needed to indicate which fields belong together, so the rule here is only tochange the minimum you have to.

For each Application in the file (starting with a UPD APL line), you must scrolldown to its job name. Type it over with the correct job name for your system. Forexample, if the job name of your automation manager is IACZAM, you would findthe current job name:

000032 Monitor Interval :000033 Application Type :000034 Subtype :000035 Subsystem Name : AM000036 Job Type :000037 Job Name : AM000038 Transient Rerun :000039 Scheduling Subsystem :000040 JCL Procedure Name :000041 Job Log Monitor Interval :

and type it over with the correct job name:


000032 Monitor Interval :000033 Application Type :000034 Subtype :000035 Subsystem Name : AM000036 Job Type :000037 Job Name : IACZAM000038 Transient Rerun :000039 Scheduling Subsystem :000040 JCL Procedure Name :000041 Job Log Monitor Interval :

You can update the contents of other fields, for example, the JCL Procedure Name.While it is suggested that the SUBSYSTEM name match the job name, changing ithere means you must make a number of corresponding changes to Applicationrelationships and other definitions. It is simpler to leave it for now.

If you are using AOCCLONE values, remember to type the job name in with the&AOCCLONE. value specified, not a resolved value:

000032 Monitor Interval :000033 Application Type :000034 Subtype :000035 Subsystem Name : VTAM000036 Job Type :000037 Job Name : NET&AOCCLONE1.000038 Transient Rerun :000039 Scheduling Subsystem :000040 JCL Procedure Name :000041 Job Log Monitor Interval :

For APLs where your systems run multiple instances, IMS, DB2, CICS,WebSphere®, set the job names for just one set of instances. We duplicate andrename them later using a different mechanism.

The UNIX System Services Applications have a USS CONTROL section:

USS CONTROL ( policy replacement )User ID :Monitoring Command :Process Command/Path : /usr/sbin/inetdwith Filter : /etc/inetd.confFile Name :IP Stack :Port Number :

In addition to correcting the job name, you must check the UNIX System Servicesdata as well. Blank is acceptable. It defaults to a value from a class. But you canexplicitly specify it, however if it is wrong it must be fixed.

Interruptions

If you need to interrupt your work, press PF3 to save the file and you are returnedto the Policy Database Update Selection screen. Do not attempt to import yourdata until you are finished. Doing so, means you get a warning for ALTERED datain the PDB and you must confirm the import. If you import the data when youinterrupt the work, then it is recommended to reexport it before you make anyfurther updates. You exit the Customization Dialog and log off TSO if you want.

To resume editing the data, choose option 5 again. Or open the data set throughthe normal ISPF editor. You may also print it or download it. Although be careful


with downloading it to edit it on your workstation as code page mismatches causeproblems. If you did download it to edit it, you must upload it into the same dataset before you can import your updates.

Import

When you make all your updates, return to the Policy Database Update Selectionscreen and choose option 2. The syntax and alignment of the data file is validated.

MENU HELP- ┌──────────────────────────────────────────────────────────────────────────┐│ Command Progress Display │

O │ ││ Checking syntax of function UPD for APL TWSSVE2E. ││ Checking syntax of function UPD for APL TWSSVJSC. ││ Checking syntax of function UPD for APL TWSSVPIF. ││ Checking syntax of function UPD for APL TWSTRKR. ││ Checking syntax of function UPD for APL VLF. ││ Checking syntax of function UPD for APL VTAM. ││ Checking syntax of function UPD for APL WEBSRV. ││ Checking syntax of function UPD for APL ZFS. ││ SUMMARY : Check completed. 0 syntax error(s) and 0 altered ││ ..........cont. object(s) detected. ││ ││ Press ENTER to continue ││ ││ PF 1=HELP 2=SPLIT 3=END 4=RETURN 5=RFIND 6=RCHANGE ││ PF 7=UP 8=DOWN 9=SWAP 10=LEFT 11=RIGHT │└──────────────────────────────────────────────────────────────────────────┘

The '0 altered objects' means that none of the APLs are modified in the PDB sincethe data are written to file. There are no updates to the automation policy.

Pressing Enter brings you back to the Policy Database Update Selection panel. Toactually write the data from the file to the PDB, choose option 3.

You get another progress dialog where it also runs the syntax check (and stops if itfinds any problems) after which it then applies your policy updates.

When it is finished, it returns you to the Policy Database Update Selection screen.You can view the Update report with option 4 and then press PF3 to return to themain menu. The APLs now have the right job names for your system. You cancheck by viewing the APL definitions.

Setting Up Your Systems

The sample policies come with a single system called SYS1. You now must create aSystem and a System Group object for each of the systems where you aredeploying Automation Control.

If you have a look at the policies that are attached to the SYS1 system, you notethat many of them have data that is provided. There are Application Groups thatare linked, defaults that are defined, MVS Component automation definitions thatare linked, and so on. To add your new systems properly, we must duplicate all ofthis extra data.

It is assumed that the actual system names are TST1, TST2, and TST3.

The first system that we can do by renaming the SYS1 entry. On the Entry NameSelection screen for Systems, enter RENAME against the SYS1 system:



Entry Name Selection Row 1 of 1Command ===> ________________________________________________ SCROLL===>PAGE

Entry Type : System PolicyDB Name : IACZ_FULLEnterprise Name : IACZ_FULL

Action Entry Name Short DescriptionRENAME__ SYS1 System 1 of the Sample Monoplex******************************* Bottom of data *******************************

Press Enter and you are prompted for the new name:

ion Entry Name Short DescriptionAME SYS1 System 1 of the Sample Monoplex*** ┌────────────────────────────────────────────────────────┐ **

│ Entry Rename ││ ││ Description : System 1 of the Sample Monoplex ││ Old Name : SYS1 ││ ││ New Name . . ____________________ ││ ││ Press ENTER to rename member. ││ Press CANCEL to cancel rename. ││ F1=Help F2=Split F3=End F9=Swap F12=Cancel │└────────────────────────────────────────────────────────┘

Enter the name of the first system you want to produce (TST1) and press Enteragain. A progress dialog appears and when completed you are back on the EntryName Selection panel with the system renamed:


Entry Name Selection Policy savedCommand ===> _______________________________________________ SCROLL===>PAGEEntry Type : System PolicyDB Name : IACZ_FULL

Enterprise Name : IACZ_FULLAction Entry Name Short Description_________ TST1 System 1 of the Sample Monoplex******************************* Bottom of data *******************************

Now, the Entry name (the name of the policy element that defines the system) ischanged. To update the SYSNAME for the system, we must select it and edit itsSYSTEM INFO policy:

COMMANDS HELP------------------------------------------------------------------------------

System InformationCommand ===> _____________________________________________________________

Entry Type : System PolicyDB Name : IACZ_FULLEntry Name : TST1 Enterprise Name : IACZ_FULL

More: +Operating system : MVSImage/System name. . . . SYS1

The following specifications are for MVS systems only:Primary JES. . . . . . . JES2 Primary JES2/JES3 subsystem nameSystem monitor time. . . 00:59 Time between monitor cycles (hh:mm or NONE)

Type over the old SYS1 sysname with TST1 to complete the rename.


If you are using JES3, you also want to type over the PRIMARY JES field with thesubsystem name (automation name) of your JES3 Application. The default is JES3.

It is recommended when you change all relationships from JES2 to JES3 of theshipped sample policies you can use the INGEFUJ3 member in the SINGSAMPlibrary to update the policy via file.

Now press PF3 and we are finished.

For TST2, we have to create System. Type new TST2 on the command line of theEntry Name Selection panel and press Enter:

COMMANDS HELP------------------------------------------------------------------------------


Define new entry of type SystemEntry name . . . . . . . TST2Operating system . . . . MVS (MVS VM VSE LINUX CF)Image/System name . . . _________________________________________________

Specify information for NMC Focal Point Communication (MVS systems only):Heartbeat interval . . . . __ (1 - 60 minutes)Missing heartbeat delay . ____ (1 - 3600 seconds)

Short Description . . . _______________________________________Long Description 1 . . . _________________________________________________Long Description 2 . . . _________________________________________________Long Description 3 . . . _________________________________________________Long Description 4 . . . _________________________________________________Long Description 5 . . . _________________________________________________

Press Enter to default the data. You can add a specific description for this system.If you leave the description blank, then it will be copied in the next step. Press PF3to leave the panel.

You come back to the System Policy panel where you must scroll down and selectthe COPY policy:

Action Policy Name Policy Description__________ -------------------- -----PROCESSOR OPERATIONS SPECIFIC POLICY----__________ PROCESSOR Select processor or partition__________ TARGET SYSTEM INFO Basics, time zones, and interested operators__________ IPL INFO Define IPL information__________ -------------------- ---------------------------------------------__________ WHERE USED List groups/subgroups linked to this entrys_________ COPY Copy data from existing entry******************************* Bottom of data ********************************

Pressing Enter brings up a panel where you can choose the System the data is tobe copied from:



Select Entry for Copy Row 1 of 2Command ===> _______________________________________________ SCROLL===>PAGE

Entry Type : System PolicyDB Name : IACZ_FULLEntry Name : TST2 Enterprise Name : IACZ_FULL

Action Entry Name Short Description_________ TST1 System 1 of the Sample Monoplex******************************* Bottom of data ********************************

Select TST1 and press Enter.

A Command Progress dialog will ’chatter’ away for a while, showing you what itis doing and then return you to the policy selection panel. If you look at some ofthe policies, they are the same for TST1. If you had the Description copied, youmay want to update the Description now.

Do the same to create a TST3 system.

System Groups (GRP):

You now must rename and copy your System Groups.

The provided sample group is called MONOPLX1. Rename it to match your firstsystem, GROUP_TST1 in this case.

Then, edit its policies and update its description and its Sysplex Policy Definitionitem:

COMMANDS HELP------------------------------------------------------------------------------

Sysplex Policy DefinitionCommand ===> ______________________________________________________________

Entry Type : Group PolicyDB Name : IACZ_FULLEntry Name : GROUP_TST1 Enterprise Name : IACZ_FULL

Sysplex Name. . . . . . . . . . . . . TSTPLEX_Sysplex Timer Monitoring. . . . . . . NO _ YES NONumber Monitored Sysplex Timers . . . _ 1 2Temporary Data Set HLQ. . . . . . . . ____________________

Data set HLQ (max. 17 chars)Started Task Job Name . . . . . . . . ____________________Couple Data Set HLQ . . . . . . . . . _____________________

CDS type Alternate volumes Desired monitoring

The Sysplex Name must be set to the correct value.

Create groups for TST2 and TST3 with the new and COPY method. The copy inthis case does not have a progress dialog. It shows a short message that indicates aPartial Copy. Press PF1 to get the long message that explains which data could notbe copied. To complete them, you must:v Edit the SYSTEMS policy item to select the correct systemv Edit the APPLICATION GROUPS policy and select the AM_PLEX APG.

You end up with:



Entry Name Selection Row 1 of 3Command ===> SCROLL===> PAGE

Entry Type : Group PolicyDB Name : IACZ_FULLEnterprise Name : IACZ_FULL

Action Entry Name Short Description_________ GROUP_TST1 Test System 1_________ GROUP_TST2 Test System 2_________ GROUP_TST3 Test System 3******************************* Bottom of data *******************************

ReviewTo have a look at what you created so far, go look at the resource report. You seethe three systems, each with resources that are attached to them.

You must go through the resource report in some detail and identify resources thatare linked to systems that they do not run on. For example, some of your testsystems may not run DB2, CICS, IMS, and TWS. After you identify these systems,go into the APPLICATION GROUP policies for the systems and unlink theappropriate groups from the systems.

Regenerate the resource report to verify your updates.

Duplicating Applications (Method 1)For a number of applications, you have only a single instance that is defined at themoment; DB2, CICS, IMS, and so forth. This single instance is probably linked toeach system that runs an instance, although not necessarily the one that is defined.

If you have multiple instances of an application on the same system or, you runinstances on different systems that have different parameters, you must duplicatetheir definitions.

Now, most of these applications have all of their application resources that aregathered within an application group, so we must duplicate that as well. You can,however, look at its members to get a list of the Applications we must duplicate.

For this tutorial, you are going to duplicate an instance of DB2 to reflect it runningwith a subsystem id of D911, rather than the id of DB21 used in the sample.

The DB21 sample has the following members (see its APPLICATIONS policy).



Applications for ApplicationGroup Row 16 of 79

Command ===> _________________________________________________ SCROLL===>PAGE

Entry Type : ApplicationGroup PolicyDB Name : IACZ_FULLEntry Name : DB21 Enterprise Name : IACZ_FULL

Action Status Application_________ CPSMWUI_________ CRON_________ SELECTED DB21ADMT_________ SELECTED DB21DBM1_________ SELECTED DB21DIST_________ SELECTED DB21IRLM_________ SELECTED DB21MSTR_________ DLF_________ DSIRQJOB_________ FFST_________ FTP_PORT_________ FTPD

You must review the APPLGROUP INFO policy. The Application Group Typecannot be changed.

COMMANDS HELP------------------------------------------------------------------------------

Application Group InformationCommand ===> ________________________________________________________________

Entry Name : DB21 Enterprise Name : IACZ_FULLThe following field was specified when the Application Group wasdefined and cannot be modified:Application Group Type : SYSTEMNature. . . . . . . . . . . BASIC______ (BASIC MOVE SERVER)Default Preference. . . . . _____ (0 to 3200, *DEF)Automation Name . . . . . . DB21_______Behavior. . . . . . . . . . ACTIVE___ (ACTIVE PASSIVE)Desired Available . . . . . ________ (ALWAYS ONDEMAND ASIS)Monitor for IPL complete. . ____ (YES NO)Prepare Move. . . . . . . . ___ (YES NO)Move Mode . . . . . . . . . ________ (PARALLEL SERIAL)Status Determination. . . . ______ (CSONLY)Inform List . . . . . . . . ____________________________

(SDF NMC IOM SMF EIF TTT USR NONE)Owner . . . . . . . . . . . _______________Info Link . . . . . . . . . __________________________________Automatically link Application-Resourcesinto APG. . . . . . . . . YES (YES NO)


What is important here is that it is a SYSTEM group, a BASIC group and anACTIVE group.

You also must look up its RESOURCES policy:


COMMANDS ACTIONS HELP

------------------------------------------------------------------------------Select System Row 1 of 3

Command ===> _________________________________________________ SCROLL===>PAGE

Entry Type : ApplicationGroup PolicyDB Name : IACZ_FULLEntry Name : DB21 Enterprise Name : IACZ_FULL

Action System Selected Resources________ TST1 5________ TST2 5________ TST3 5******************************* Bottom of data ********************************

The RESOURCES policy shows us that it is linked to all 3 of our test systems.Selecting TST1 shows:


Select Resources Row 1 of 5Command ===> _______________________________________________ SCROLL===>PAGEEntry Type : ApplicationGroup Entry Name : DB21System : TST1Number of selected Resources : 5Show all Resources . . . . . . . . NO YES NOShow only Resources with String. .

Action Status Resource Name Entry NameSELECTED DB21ADMT/APL/TST1 DB21ADMTSELECTED DB21DBM1/APL/TST1 DB21DBM1SELECTED DB21DIST/APL/TST1 DB21DISTSELECTED DB21IRLM/APL/TST1 DB21IRLMSELECTED DB21MSTR/APL/TST1 DB21MSTR

******************************* Bottom of data *******************************

As the DB21 group is a BASIC group, there are no additional parameters for theresources. A Move or Server group has fields to set targets and preference valuesfor the resources:


Select Resources Row 1 of 2Command ===> _______________________________________________ SCROLL===>PAGEEntry Type : ApplicationGroup Entry Name : AM_PLEXSysplex : GROUP_TST1Number of selected Resources : 2Availability Target. . . . . . . *ALL (-1 to 2 , *ALL)Satisfactory Target. . . . . . . (Level at which group is available)Show all Resources . . . . . . . NO (YES NO)Show only Resources with String.

Action Preference Resource Name Entry Name700 AM/APL/SYS1 AM700 AM2/APL/SYS1 AM2

******************************* Bottom of data ********************************

If you are duplicating a similar group, we must note these values and settings soyou can re-create them on our new group.

Back to our DB2 example. Create a group that is called D911:


COMMANDS HELP------------------------------------------------------------------------------


Define new entry of type ApplicationGroupEntry name . . . . . . . D911______________________Type . . . . . . . . . . SYSTEM_ (SYSTEM SYSPLEX)Nature . . . . . . . . . BASIC__ (BASIC MOVE SERVER)Default Preference . . . _______ (0 to 3200, *DEF)Automation Name . . . . __________Automatically link . . . YES (for Application-Resources)Behavior . . . . . . . . ACTIVE___ (ACTIVE PASSIVE)Prepare Move . . . . . . ___ (YES NO)Move Mode . . . . . . . _________ (PARALLEL SERIAL)Short Description . . . _________________Long Description 1 . . . ____________________________________Long Description 2 . . . ____________________________________Long Description 3 . . . ____________________________________Long Description 4 . . . ____________________________________Long Description 5 . . . ____________________________________

Ensure that the Group Type, Nature, and Behavior fields are set the same as thegroup you are copying.

Use the COPY policy to import the data for the DB21 group. Once done, if you gointo the APPLICATIONS policy, you note it is linked to the same APLs as theDB21 group was. Remove them from the group by entering an M against each one.The action leaves your new D911 group with no members.

Now you must create some APLs. The first one to do is the DB2 Master AddressSpace, as it is the most complicated. The old APL was called DB21MSTR, so youwant to create an APL called D911MSTR. Before you do so, though you are goingto review at the APPL INFO for the DB21MSTR application:

COMMANDS HELP------------------------------------------------------------------------------

Application Information Line 00000001Command ===> _______________________________________________ Scroll===> PAGE

Entry Type : Application PolicyDB Name : IACZ_FULLEntry Name : DB21MSTR Enterprise Name : IACZ_FULL

Category : DB2 (IBM-defined, user-defined or blank,see help)

Subcategory . . . . . . . MSTR_______ (IBM-defined, user-defined or blank,see help)

Subsystem Name . . . . . . DB21MSTR___Job Type . . . . . . . . . ___________ (MVS NONMVS TRANSIENT)Job Name . . . . . . . . . DB21MSTRTransient Rerun . . . . . ___ (YES NO)Scheduling Subsystem . . . ____ (MSTR, JES Subsystem)JCL Procedure Name . . . . ___________Job Log Monitor Interval . _____ (mm:ss NONE)Captured Messages Limit . ___ (0 to 999)Desired Available . . . . _________ (ALWAYS ONDEMAND ASIS)Restart after IPL . . . . _________ (START NOSTART NONE)Monitor for IPL complete . ___ (YES NO)Start Delay . . . . . . . ________ (time for "UP" status checks,hh:mm:ss)Start Cycles . . . . . . . __ (start delay checks, 0 to 99)UP Status Delay . . . . . ________ (time to delay "UP" status,hh:mm:ss)Restart option . . . . . . ____________ (ALWAYS ABENDONLY NEVER)External Startup . . . . . _______ (INITIAL ALWAYS NEVER)


Note the Application Type is set to DB2 and cannot be changed. If you scrolldown, you also see:

Shutdown Pass Interval . . ________ (hh:mm:ss)Cleanup Delay . . . . . . ________ (hh:mm:ss)Command Prefix . . . . . . -DB21_________________Message Prefix . . . . . . _________________________Sysname . . . . . . . . . ________________________

So create a D911MSTR and specify its Application Type as DB2 and its Subtype asMSTR:

COMMANDS HELP------------------------------------------------------------------------------


Define new entry of type ApplicationEntry name . . . . . . . D911MSTR_________Subsystem Name . . . . . D911MSTR___Object Type . . . . . . INSTANCE (CLASS INSTANCE)Category . . . . . . . . DB2_______ (IBM-defined, user-defined or blank,

see help)Subtype . . . . . . . . MSTR______ (IBM-defined, user-defined or blank,

see help)Job Type . . . . . . . . __________ (MVS NONMVS TRANSIENT)Job Name . . . . . . . . D911MSTRTransient 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 . . . __________________________________________


Then, copy in the data from the DB21MSTR application.

If you look at the APPLICATION INFO, you see that we still have the old DB21value. Change it to D911. The character in front of it may need changing as well.Talk to your operator or system programmer.

Shutdown Pass Interval . . ________ (hh:mm:ss)Cleanup Delay . . . . . . ________ (hh:mm:ss)Command Prefix . . . . . . -D911_________________Message Prefix . . . . . . _________________________Sysname . . . . . . . . . ________________________

Now, look up its DB2 CONTROL policy:


COMMANDS HELP------------------------------------------------------------------------------

DB2 Control Entries Line 00000001Command ===> ______________________________________________ Scroll===> PAGE

Entry Type : Application PolicyDB Name : IACZ_FULLEntry Name : D911MSTR Enterprise Name : IACZ_FULL

Subsystem : D911MSTRSubtype : MSTR defined in policy APPLICATION INFOSubsystem ID . . . . . . DB21_______________________Active Log data set . . . _____________________________

DSN1.DB21.LOGCOPY1Log Full Threshold . . . (1 to 99 percent)Process iteration delays:STOP Tablespace Delay . ________ (00:00:00 to 23:59:59)Active Log Alert . . . . ________ (00:00:00 to 23:59:59)Log Alert Threshold . . __ (1 to 99)Log Offload Interval . . ________ (00:00:00 to 23:59:59)******************************* Bottom of data *******************************

The Subsystem ID needs changing to D911 and the name of the Active Log dataset also needs changing.

The procedure for making the D911IRLM, D911DIST, D911DBM1, and D911ADMTapplications is much the same.

Next, you must check the relationships for D911ADMT:


Relationship Selection List Row 1 of 1Command ===> ______________________________________________________________

Entry Type : Application PolicyDB Name : IACZ_FULLEntry Name : D911ADMT Enterprise Name : IACZ_FULL

External Startup. . . INITIAL (INITIAL ALWAYS NEVER)External Shutdown . . FINAL (FINAL ALWAYS NEVER)

Action # Type Supporting Resource Auto ChainHASPARENT DB21MSTR/APL/=StartsMeAndStopsMe

******************************* Bottom of data ********************************

There is a dependency upon the DB21MSTR resource here. Select the relationshipand change the supporting resource to the D911 version, D911MSTR/APL/= in thiscase:


COMMANDS HELP------------------------------------------------------------------------------

Define RelationshipCommand ===> ______________________________________________________________

Entry Type : Application PolicyDB Name : IACZ_FULLEntry Name : D911ADMT Enterprise Name : IACZ_FULL

Subsystem Name : D911ADMTDescription. . . . . ADMT started and stopped by MSTR

Relationship Type. . HASPARENT MAKEAVAILABLE MAKEUNAVAILABLEPREPAVAILABLE PREPUNAVAILABLEHASPARENT HASPASSIVEPARENTHASMONITOR PEEROFFORCEDOWN EXTERNALLY

Supporting Resource. D911MSTR/APL/=Resource Name

Sequence Number. . . Sequence Number (1-99,blank)Automation . . . . . ACTIVE PASSIVEChaining . . . . . . STRONG WEAKCondition . . . . . StartsMeAndStopsMe

Satisfy condition(? for list of possible values)

When complete, open up the WHERE USED policy and select the D911 APG:

________ CPSM APG________ DB21 APG________ SELECTED D911 APG________ FTP_DAEMON_GROUP APG________ IMS APG

When you have done that, we must go into the D911 APG and link it to thesystems that it must be on.


Where Used Row 1 of 3Command ===> ________________________________________________ SCROLL===>PAGEEntry Type : ApplicationGroup PolicyDB Name : IACZ_FULLEntry Name : D911 Enterprise Name : IACZ_FULLAction Status Name Type_________ TST1 SYS_________ SELECTED TST2 SYS_________ TST3 SYS******************************* Bottom of data ********************************

You see some resource generation messages when you leave the panel.

Duplicating Applications (Method 2)An alternative method of duplicating a set of applications is available that youmight find easier to use. For this example, you are again going to duplicate theDB21 application, but to an identity of DM22.

Go back to the main ISPF option menu Automation Control for z/OS and selectoption 5 – Data Management. Then, you want suboption 3 – Update via file.

You want to export the DB21 APG, so set up option 1 thus:


1 Write selected data from Policy Database to fileEntry Type . . . . . . . APG (? or type)Output File Name . . . . IOCZ.FULL.DB21.APG________

Put a 1 on the option line and press Enter. Select just DB21 from the followingmenu and press Enter again. Select all of the policies that are offered on the nextpanel and press Enter a third time. When the confirmation panel appears, pressEnter again.

Now you want option 5 Edit the file.

You are going to modify the DB21 entries to create a set of entries for DM22. Thesyntax for this file is described in "Data Management" section in IBM SystemAutomation for z/OS Defining Automation Policy.

You want to create an entry:

000007000008 NEW APG - DM22000009 Type : SYSTEM000010 Nature : Basic000011000012 UPD APG - DM22000013 DESCRIPTION ( field replacement )

You also want to apply the DB21 policy to it, so you must change the UPD line:

000009000010 UPD APG - DM22000011 DESCRIPTION ( field replacement )000012 Short Description : DB2 Subsystem - DB21000013 Long Description 1 : All DB2 address spaces require

Then, you must adjust the APPLGROUP INFO data a little:

000018 APPLGROUP INFO ( field replacement )000019 * Type : SYSTEM000020 Nature : Basic000021 Default Preference :000022 Automation Name : DM22000023 Behavior : ACTIVE000024 Desired Available :

Remove the WHERE USED SYS lines for systems that you do not want the APGused on.

When you are done, press PF3. Then, after a check of the data set name on option3, use option 2 to run a syntax check. Confirmation is made. Then, you can useoption 3 to import the data in the file.

Now you must do the same for the APLs. Export the data for the 5 DB21 APLsinto a single flat file, and then go into edit on it. On the Policy Selection panel, youneed select the normal APL policies and the DB2 policy item (as it is a DB2).



Policy Selection Row 3 of 24Command ===> ________________________________________________ SCROLL===>CSR

Select one or more policies to be written to file:

Action Status Policy Name________ SELECTED APPLICATION INFO________ SELECTED AUTOMATION FLAGS________ SELECTED APPLICATION SYMBOLS________ SELECTED RELATIONSHIPS________ SELECTED MESSAGES/USER DATA________ SELECTED STARTUP________ SELECTED SHUTDOWN________ SELECTED THRESHOLDS________ SELECTED MINOR RESOURCES________ CICS CONTROL________ SELECTED DB2 CONTROL________ OPC CONTROL________ IMS CONTROL________ USS CONTROL________ JES2 SPOOLFULL CNTL________ JES2 SPOOLFULL CMDS________ JES2 SPOOLSHORT CNTL________ JES2 SPOOLSHORT CMDS________ JES2 DRAIN CMDS________ JES3 SPOOLFULL CMDS________ JES3 SPOOLSHORT CMDS________ SELECTED WHERE USED

For each APL you must add a NEW statement:

000009000010 NEW APL - DM22ADMT000011 Object Type : INSTANCE000012 Subsystem Name : DM22ADMT000013 Application Type : DB2000014 Subtype : ADMT000015000016 UPD APL - DM22ADMT000017 DESCRIPTION ( field replacement )

The data for it can be taken from the APPLICATION INFO section and adapted forthe new APL where appropriate.

You then must update the UPD APL section for the APL to refer to the DM22 DB2:


UPD APL - DM22ADMTDESCRIPTION ( field replacement )

Short Description : DM22 Administrative SchedulerMonitor Routine :Monitor Interval :Application Type : DB2Subtype : ADMTSubsystem Name : DM22ADMTJob Type :Job Name : DM22ADMTTransient Rerun :Scheduling Subsystem :

* APPLICATION SYMBOLS no data availableRELATIONSHIPS ( policy replacement )

Relationship Type : HASPARENTSupporting Resource : DM22MSTR/APL/=Description : ADMT started and stopped bySequence Number :Automation :Chaining :

* SHUTDOWN no data available* THRESHOLDS no data available* MINOR RESOURCES no data availableWHERE_USED APG : DM22

Repeat for the other 4 APLs. Remember to look up and set the appropriateApplication Subtype value for each one and to get all of the data for the MSTR. Itis not the same layout as the other four APLs.

When you are done run a syntax check and then an import. If you must do itagain and want to go back to the DB21 APL definitions, rerun the export stepagain. It overwrites whatever is in the output file.

Complete the ReplicationReplicate samples until you have enough definitions for all of the applications youwant to run on the system.

Building your PolicyBefore you can distribute your policy to your target system, you must build it intoa staging data set.

As it is the first time we are building this policy, we first must allocate the stagingdata set. Outside of the Customization Dialog, use the ISPF 3.2 dialog. You can usePF2 to start a split screen session to do it:


Menu RefList Utilities Help------------------------------------------------------------------------------

Data Set UtilityOption ===> a__________________________________________________________

A Allocate new data set C Catalog data setR Rename entire data set U Uncatalog data setD Delete entire data set S Short data set information

blank Data set information V VSAM UtilitiesISPF Library:Project . . ___________ Enter "/" to select option

Group . . . ___________ / Confirm Data Set DeleteType . . . . ___________Other Partitioned, Sequential or VSAM Data Set:

Name . . . . . . . iocz.full.socntl______________________________________Volume Serial . . . _________ (If not cataloged, required for option "C")Data Set Password . . _________ (If password protected)

Although our convention is to allocate it with the same name as the PolicyDatabase data set, but with an SOCNTL suffix rather than a PDB suffix. Yoursystem programmers require it to be allocated under a different name. You mighthave to allocate it on your behalf.

The data set is a standard FB80 PDS:

Data Set Name . . . : MIK.IOCZ.FULL.SOCNTLManagement class . . . STANDARD_____ (Blank for default management class)Storage class . . . . SMS__________ (Blank for default storage class)Volume serial . . . . KEYSM4 (Blank for system default volume) **Device type . . . . . ______ (Generic unit or device address) **Data class . . . . . . _________ (Blank for default data class)Space units . . . . . CYLINDER (BLKS, TRKS, CYLS, KB, MB, BYTES

or RECORDS)Average record unit (M, K, or U)Primary quantity . . 3_____ (In above units)Secondary quantity 1_____ (In above units)Directory blocks . . 50____ (Zero for sequential data set) *Record format . . . . FB__Record length . . . . 80_____Block size . . . . . 32720__Data set name type PDS______ (LIBRARY, HFS, PDS, LARGE, BASIC, *

EXTREQ, EXTPREF or blank)Extended Attributes ___________ (NO, OPT or blank)Expiration date . . . ___________ (YY/MM/DD, YYYY/MM/DDEnter "/" to select option YY.DDD, YYYY.DDD in JulianformAllocate Multiple Volumes _ DDDD for retention period in days

or blank)

3 Cylinders are ample for your initial allocation.

Return to the Automation Control Dialog when you allocate it.

You want option 2 (Build) from the main Automation Control for z/OS 1.1.1Customization Dialog panel. The build dialog is displayed:


MENU HELP------------------------------------------------------------------------------

Build ParametersOption ===> ________________________________________________________________

1 Build a complete enterprise2 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

Build options:Output Data Set . . . . _________________________________________Mode. . . . . . . . . . ONLINE____ (ONLINE BATCH)Type. . . . . . . . . . ALL_______ (MODIFIED ALL)Configuration . . . . . NORMAL____ (NORMAL ALTERNATE)

Job statement information: (used for BATCH build)//AOFBUILD_JOB_______________________________________________________________//*__________________________________________________________________________//*__________________________________________________________________________

Specify your output data set name and ask for a full build (option 1).

You see a process dialog with messages that indicate the elements that areprocessed:

MENU HELP┌──────────────────────────────────────────────────────────────────────────┐│ Command Progress Display ││ ││ ............... Fragment Z996AAPG built for APG CICS_SHARED ││ ............... Fragment Z995AAPG built for APG CICS1 ││ ............... Fragment Z994AAPG built for APG CICS1TG ││ ............... Application Group CMD_RECEIVER has no automation name ││ ..........cont. specified. ││ ............... Fragment Z992AAPG built for APG CPSM ││ ............... Fragment Z991AAPG built for APG DB21 ││ ............... Fragment Z99NAAPG built for APG DM22 ││ ............... Fragment Z99OAAPG built for APG D911 ││ ............... Fragment Z990AAPG built for APG FTP_DAEMON_GROUP ││ ││ ││ ││ PF 1=HELP 2=SPLIT 3=END 4=RETURN 5=RFIND 6=RCHANGE ││ PF 7=UP 8=DOWN 9=SWAP 10=LEFT 11=RIGHT │└──────────────────────────────────────────────────────────────────────────┘/AOFBUILD JOB

On completion, you get a Build Successful message back. You can use option 4 toreview the Build Report (which is all of the messages that scrolled past while thebuild was occurring).

Distribute Your PolicyThe SOCNTL data set that we are building the policy into holds automation policyfor ALL of the systems that are defined in the Policy Database.

However, the SOCNTL data set resides on the system you used to create and buildthe policy. You must allocate production SOCNTL data sets on the systems whereyou are going to deploy Automation Control. Make arrangements to copy the data


over to them. Using XMIT and manually receiving them is one option, andNetView FTP are others. NetView FTP is a separate product, and not part of theNetView for z/OS product.

See Chapter 6, “Operations,” on page 93 for some considerations about how tomanage the SOCNTL data on the deployed system.

MaintenanceYou must update your automation policy over time, and as a result of testing.

You can copy your PDB data set in its entirety to make a backup.v Use the dialog to change your policy.v Rebuild and Redistribute your policy when you are done.

See Chapter 6, “Operations,” on page 93 on managing the updates on the targetsystems to avoid incidents.


Chapter 6. Operations

Automation Control uses technology from the IBM’s NetView component andSystem Automation products. You use Automation Control to operate a singlesystem. There are references to the components and functions of those products.

Automation Control uses a Manager/Agent model to automate applications oncomputer systems. It performs primary start or stop and recover automation forapplications, and also performs operating system automation. The automationagent has a ProcOps focal point function that allows local CPC, related LPARS, andOS operation.

Automation Control works as follows:

1. Messages get generated from Applications and the Operating System.2. The messages get routed into the Automation Agent.3. The Automation Agent then determines the nature of the message and the

response appropriate to the message.4. Local automation messages trigger an automated response back to the z/OS

system from within the agent itself.5. State change messages trigger an update to the Automation Manager.6. After the Automation Manager processed the state change and worked out its

implications, it sends some orders down to the Automation Agent.7. The agent receives the orders and runs them, possibly resulting in commands

that are being issued to the z/OS system.

The user interface for managing applications is a NetView console. However, youmust use the operating system consoles to actually stop and restart the AutomationManager and the Automation Agent.

Console OperationsThese operations are required to get Automation Control operational.

AutomationManager

AutomationAgent

Started tasksz/OS

NetView

(artname: AM_Overview_3.gif)Figure 9. Manager/Agent Overview in Automation Control


They must be performed at an MVS Master Console, accessible either directly orthrough SDSF. You can automate these operations within the z/OS IPL sequencewith a COMMNDxx PARMLIB member after you are satisfied with yourAutomation Control installation.

The Automation Manager’s Started Task

Naming Conventions

The name of your Automation Manager started task is confirmed by your systemprogrammer after the Configuration Assistant is used. The Configuration Assistantgenerates the INGEAMSA start procedure by default, which is used in thefollowing examples.

Starting the Automation Manager

The Automation Manager is started with a standard MVS Start command:

S INGEAMSA,JOBNAME=AM,SUB=MSTR

More parameters are passed at run time. They are documented in "Starting andStopping SA z/OS" in IBM System Automation for z/OS User’s Guide. Your systemprogrammer sets up the task so that no additional parameters are required.

Although the SUB=MSTR parameter is not strictly required, you must use thisparameter if you are going to have Automation Control automate the start,recovery, and shutdown of JES and other subsystems that run the SUB=MSTRparameter. You omit it for testing, although you must conduct a test with itapplied, as the SUB=MSTR parameter is a more restrictive environment for JCL.

Starting a Backup

The Automation Manager is designed to run in a HOT backup configuration. Thefirst started task becomes the primary manager and runs automation. A secondinstance of the task is then started to provide a failover capability if the primaryautomation manager fails.

Your system programmer advises you whether this step is required. Typically itwould be handled by Automation Control itself, but under some circumstances itmight be manually required. A typical start command for it would be as follows:

S INGEAMSA,JOBNAME=AM2,SUB=MSTR

The command runs a second instance of the Automation Manager under adifferent job name.

Again, the SUB=MSTR parameter can be omitted for testing.

Stopping an Automation Manager

If you are stopping an Automation Manager to recycle it, use command:

P AM

If you must stop the Automation Manager because of a specific requirement, use:

F AM,STOP,IMMED


or

F AM,STOP,FORCE

If you are shutting down the system, Automation Control is able to shut itselfdown, but if it cannot shut down, use:

F AM,STOP,DEFER

This command instructs the Automation Manager to keep running until the agentconnected to it has shutdown and then the Automation Manager stops itself.

During production use, you usually do not have to stop the Automation Manager.It should send itself a STOP,DEFER before it shuts down the NetView component.During testing, you might have to shut it down manually.

Additional Operations

There are other commands that the Automation Manager responds to. They aredocumented in "Starting and Stopping SA z/OS" in IBM System Automation forz/OS User’s Guide.

The Automation Agent’s Started Task

Naming Conventions

The Configuration Assistant generates a start procedure named INGENVSA bydefault. This procedure is used in the following examples.

The agent task requires a subsystem interface task to be started before the agenttask is started. The name of the subsystem interface task is also provided by yoursystem programmer. The Configuration Assistant generates the CNMSJ010procedure by default. This procedure is used in the following examples.

Starting the Automation Agent

The Automation Control Agent is started with a standard MVS start command.Your system programmer set it up, so only minimal extra parameters are required.

If Automation Control is being used to automate the system (as opposed totesting), it must be started with the SUB=MSTR parameter.

Before you can start the agent task, you must start its subsystem interface (SSI)task. To do so, issue this command:

S CNMSJ010,JOBNAME=SYSVSSI,SUB=MSTR

After the task is initialized, the following message appears:

CNM541I NETVIEW SUBSYSTEM ssi_name IS FULLY FUNCTIONAL

You can start the Agent task with this command:

S INGENVSA,JOBNAME=SYSVAPPL,SUB=MSTR

Chapter 6. Operations 95

Failure to specify the SUB=MSTR parameter results in the command being unableto properly automate JES, VLF, LLA, and anything else running the SUB=MSTRparameter. You may omit the parameter for testing however. Ensure that you do atest with the SUB=MSTR parameter as the parameter creates a more restrictiveenvironment for JCL.

Stopping the Automation Agent

You can issue stop commands from either the NetView console or from a z/OSconsole by replying to the Automation Control Agent’s outstanding WTOR:

*0004 DSI802A CNM01 REPLY WITH VALID NCCF SYSTEM OPERATOR COMMAND

Usually, you use the following command from a NetView Console to stop theAutomation Control Agent:

CLOSE STOP

The instruction causes the NetView component to shut down all operator logins,autotasks, and other started tasks. The instruction likely causes your NetView loginto terminate when it is issued.

If the Automation Control Agent does not shut down, you can issue the followingstronger shutdown command from the z/OS console:

R 0004,CLOSE IMMED

The following instruction causes the NetView component to abend any tasksconditionally that are not terminated. If the Automation Control Agent still is notshut down, try the command:

R 0005,CLOSE ABEND

The following instruction causes the main NetView address space to abend andterminate. The subsystem address space does not require termination. If you muststop it to clean up after testing, use the following stop command:

P SYSVSSI

If this instruction does not stop the subsystem address space, then leave it running.This address space does not interfere with anything and attempting to stop it moreaggressively can cause you to have to restart the system.


Operating Automation ControlAfter the started tasks are started and have initialized, you must log on to theagent to operate Automation Control.

The Automation Control Agent hosts its user interface environment. Figure 10shows how an operator can communicate to both the Automation Manager and thestarted tasks.

Automation ControlThe Automation Control Agent is built under a NetView environment. To use theagent to interact with automation, you must log on to the NetView component.You can control automation only with the NetView component.

Log on to Automation ControlYour system programmer advises you how to reach the NetView login panel forthe Automation Control Agent. The login panel looks as follows:

NN NN VV VVNNN NN EEEEEE TTTTTTTT VV VV II EEEEEE WW WW TMNNNN NN EE TT VV VV II EE WW W WWNN NN NN EEEE TT VV VV II EEEE WW WWW WWNN NNNN EE TT VV VV II EE WWWW WWWWNN NNN EEEEEE TT VVV II EEEEEE WW WWNN NN V

5697-NV6 © Copyright IBM Corp. 1986, 2014 - All Rights ReservedU.S. Government users restricted rights - Use, duplication, or disclosure

restricted by GSA ADP schedule contract with IBM corporation.Licensed materials - Property of IBM Corporation

Domain = IPSNM Automation Control NM

OPERATOR ID ==> or LOGOFFPASSWORD ==>PROFILE ==> Profile name, blank=default

HARDCOPY LOG ==> device name, or NO, default=NORUN INITIAL COMMAND ==> YES or NO, default=YES

Takeover session ==> YES, NO, or FORCE, default=NO

Enter logon information or PF3/PF15 to logoff

AutomationManager

AutomationAgent

Started tasksz/OS

NetViewOperator

(artname: GUIs3.gif)Figure 10. z/OS Task Structure and the Automation Agent


Enter your user ID and password into the fields and press Enter.

You see some panels of text with a row of three asterisks in the lower left corner:

- IPSNM OPERATOR: AUT- IPSNM OPERATOR: AUT- IPSNM OPERATOR: AUT- IPSNM OPERATOR: AUT=X= ***

Press Enter to page forward through the messages. Eventually, you see anAutomation Control panel. Press PF3 to exit it and you are on a NetView consolesimilar to this one:

AUTOMATION CONTROL NM Tivoli NetView IPSNM MIK 08/19/14 04:11:21

???

The input field is at the lower part of the panel, under the question marks. Thispanel is the NetView console.

Logging Off

To log off, enter LOGOFF in the Input field and then press Enter. After you arelogged out, log back in.

Help

You can access assistance for a command or for an explanation of a message byentering the following command:

HELP subject

A full screen help panel appears. Press PF7 and PF8 to scroll and PF3 to return tothe NetView console.

To get a list of commands that you can use in the Automation Controlenvironment, enter this command:

HELP COMMANDS

On the panel that is displayed, place the cursor on any row and press Enter todisplay full screen information with a detailed description.


Issue the following command to display all the help that is associated with theNetView component:

INDEX

displays all help associated with the NetView component.

ROLL KeyThe NetView console provides multiple interactive commands that runimmediately. However, the console shows you the 3270 interface for a singlecommand. To switch between different commands, you must press the ROLL key,usually PF6.

When you start a new program, previous versions of the program stop running,replacing the older version in the roll stack. If you issue the DISPINFO command,then issue the DISPRELS command followed by the DISPINFO command againand press PF3 twice, to return you to the NCCF console. The first instance of theDISPINFO command is automatically stopped when you issue the command asecond time.

InfrastructureThere are two commands that you can use to review the infrastructure thatAutomation Control uses to perform its automation. The commands that you useare INGAMS and DISPSYS.

The INGAMS CommandThe INGAMS command displays the agent and the manager and indicates whetherthey have their automation policy loaded. It also shows any backup managers thatare active.

On the NetView Console, enter this command:

INGAMS

You then see the following panel:

INGKYAM0 SA z/OS - Command Dialogs Line 1 of 2Domain ID = IPSFO ---------- INGAMS ---------- Date = 08/03/14Operator ID = OPER1 Sysplex = KEY1PLEX Time = 11:09:48

Cmd: A Manage B Show Details C Refresh Configuration D Diagnostic

CMD System Member Role Status Sysplex XCF-Group Release Comm PA--- -------- --------- ----- ---------- -------- --------- ------- ---- ---

KEY1 KEY1$$$$2 SAM READY KEY1PLEX INGXSGF1 V1R1M1 XCFKEY1 KEY1$$$$1 PAM READY KEY1PLEX INGXSGF1 V1R1M1 XCFKEY1 KEY1 AGENT READY KEY1PLEX INGXSGF1 V1R1M1 XCF

Command ===>PF1=Help PF2=End PF3=Return PF6=Roll

PF9=Refresh PF10=Previous PF11=Next PF12=Retrieve

What is important is that there is a Primary Automation Manager (PAM) and anAGENT present and that both have a READY status. The Secondary AutomationManager (SAM) is a backup manager.


You can exit the display by pressing PF3.

The DISPSYS CommandThe DISPSYS command displays information about the system that the commandis issued on.

On the NetView console, enter this command:

DISPSYS

You see the following panel:

AOFKADAE SA z/OS - Command Dialogs Line 1 of 132Domain ID = IPSFO ---------- DISPSYS ---------- Date = 04/03/14Operator ID = OPER1 System = KEY1 Time = 10:38:05

System : KEY1 in Sysplex : KEY1PLEXDomain : IPSFOSysplex Group : KEY1PLEXXCF Group name : INGXSGF1XCF PlexID : INGPX$A1

SoftwareOperating System : z/OS 01.13.00NetView : N/A

Tower(s) : N/AAutomation : IBM Automation Control for z/OS V1R1M1

Tower(s) : SYSOPS PROCOPS

ConfigurationData set : AUTO.TEST.PDB.SOCNTL(ACFZ996)Built by : ADMIN1 03/17/14 17:59:58Activated : 03/20/14 10:01:58CFG Token : 2014031717594700220B822097

Message automation table(s)INGMSGSA INGMSG01 INGMSGU

FlagsAutomation : YesInit Start : YesStart : YesRecovery : YesTerminate : YesRestart : Yes

Scheduling Subsystem : JES2Type : JES2

Root for SDF updates : KEY1

USS path : /usr/lpp/ing/ussauto/lib/

IPL Complete ConsiderationsTime Limit :Important Resources :

Sysplex TimingDefined : UnknownCurrent : UnknownID’s : None

Heartbeat Interval : 5 Minute(s)Missing Heartbeat Delay : 30 Seconds

Captured Messages (maximum is 25)


PF8=Forward PF9=Refresh PF12=Retrieve


The most important information on the panel is the identification of theautomation policy that is being used. The identification is the Configuration Dataset in the middle of the panel. This information is also available on the INGAMSDetails panel (line command B).

To scroll the panel with PF7 and PF8 and press PF3 to exit it.

ResourcesResources are the elements that Automation Control uses to model started tasksand other elements of the z/OS system that Automation Control can automate. Theautomation manager interface works in terms of resources.

All resources have 2- or 3-part hierarchical names:

name/type

or

name/type/system

The name is something that your automation modelers choose. In some casesAutomation Control requires that it matches a real world name, for example,system names.

The type identifies the nature of the resource:

Table 4. Resource Types (partial list)

ResourceCode Resource Type Resource Description

APL Application A started task or other automateable entity, typically a startedtask

APG Application Group A group of resources that are defined and managed within theautomation manager

MTR Monitor A resource that represents a monitor

SYS System A resource that represents a z/OS system

SYG System Group A group of all the resources that are running on a system

The system qualifier is present for all resources that are linked to a specific system.There is a full list of resource types in IBM System Automation for z/OS User’s Guide.

There are four commands to view data about these resources:v INGLIST and INGINFO, which show data from the Automation Manager

perspectivev DISPSTAT and DISPINFO, which show data from the Automation Agent

perspective

There are also two commands that can be used to dynamically observe theresources:v SDF, which shows a dynamic dashboardv INGNTFY, which sends messages to your NetView console every time a resource

changes status


The INGLIST CommandThe INGLIST command queries the resources that are known to the AutomationManager to view some information about them and to initiate actions againstthem.

To start the INGLIST interface, type the following command:

INGLIST resource

where resource is an optional parameter that represents the name of the resourcethat you want to inquire about. It might include wildcards, such as the followingexample:

INGLIST RMF*

The command produces a response such as this:

INGKYST0 SA z/OS - Command Dialogs Line 1 of 7Domain ID = IPSNM -------- INGLIST --------- Date = 07/21/14Operator ID = MIK Sysplex = SYSPLEX_GROUP_01 Time = 05:54:32A Update B Start C Stop D INGRELS E INGVOTE F INGINFO G MembersH DISPTRG I INGSCHED J INGGROUP K INGCICS L INGIMS M DISPMTR P INGPACT INGTWS U User X INGLKUP / scrollCMD Name Type System Compound Desired Observed Nature--- ----------- ---- -------- ------------- ------------ ----------- --------_ RMF APL KEY1 SATISFACTORY AVAILABLE AVAILABLE_ RMFGAT APL KEY1 SATISFACTORY AVAILABLE AVAILABLE

Command ===>PF1=Help PF2=End PF3=Return PF4=DISPSTAT PF5=Filters PF6=Roll


You can enter commands against individual resources in the CMD column on theleft side of the panel. The primary commands that you probably want to use are B(Start), C, (Stop), E (INGVOTE) and F (INGINFO). Refer to “The INGINFOCommand” to start and stop resources. Type an F next to the RMF resource andpress Enter.

The INGINFO CommandYou can either start the INGINFO command from the INGLIST panel or you canstart it from the command line:

INGINFO resource

The resource is the name of the resource that you want to know about. TheINGINFO command works with a single resource at a time, if the resource nameyou specify resolves to multiple resources. Thus you must make a selection. Issuethe following command, for example:

INGINFO RMF*

The results might be as follows:


AOFKSEL4 SA z/OS - Command Dialogs Line 1 of 7Domain ID = IPSNM ---------- INGINFO ---------- Date = 07/21/14Operator ID = MIK Time = 06:01:42

Multiple instances found for RMF*Select one item to be processed, then press ENTER.

Sel Name Type System Description--- ----------- ---- -------- ------------------------------------------_ RMF APL KEY1 Resource Measurement Facility_ RMFGAT APL KEY1 RMF monitor III Data Gatherer

Command ===>PF1=Help PF2=End PF3=ReturnPF6=Roll PF12=Retrieve

Use the input field under the SEL column to select one of the resources that theAutomation Manager recognizes and matches the resource name template that youprovided. Type an S in the field and press Enter to select one.

The INGINFO panel shows lots of detailed information about a resource:

INGKYIN0 SA z/OS - Command Dialogs Line 1 of 491Domain ID = IPSNM ---------- INGINFO ---------- Date = 07/21/14Operator ID = MIK Sysplex = SYSPLEX_GROUP_01 Time = 06:04:54

Resource => RMF/APL/KEY1 format: name/type/systemTarget => System name, domain ID or sysplex name

Resource : RMF/APL/KEY1Description : Resource Measurement Facility

Status...Observed : AVAILABLEDesired : AVAILABLEAutomation : IDLEStartability : YESCompound : SATISFACTORY Last changed : 2014-07-23 01:44:13Health Status : N/A

Dependencies...PreStart : SatisfiedStart : SatisfiedPreStop : SatisfiedStop : UnsatisfiedStartability : Satisfied

Trigger : -None-

Inherited Group Trigger(s)...

You can scroll up and down the panel by pressing PF7 and PF8 to scroll it. To exitthis panel, press PF3.

The INGINFO Display

The INGINFO command output displays the following sections:


Statuses

The Status block gives you status information about the resource:

Observed : AVAILABLEDesired : AVAILABLEAutomation : IDLEStartability : YESCompound : SATISFACTORYHealth Status : N/A

The statuses are as follows:

Table 5. Resource Status Overview

Status Description

Observed For APLs, it is the status reported by the automation agent.

For other resources, it is a status that is inferred or detected by theAutomation Manager.

Desired The goal state for the resource. Is it up (AVAILABLE) or down(UNAVAILABLE).

Automation What the Automation Manager recognizes the agent is doing for theresource at the moment. Usually it is Idle.

Startability An estimation by the Automation Manager of whether it is possible tostart the resource. If not YES, then there is a problem with one or moreprerequisite resources that make it impossible to start this resource.

Compound An aggregate status, synthesized from all of the other statuses to give anoverall opinion on the state of the resource. SATISFACTORY is good,but means that the resource is in its goal state, not that it is up.

Health Status A status that is calculated from the health status that is returned byhealth monitor resources. N/A means that there is no health monitorresource that is attached to the resource we are looking at.

Resource Dependencies

The Dependency Block gives you information about the state of the resource’sprerequisite resources:

PreStart : SatisfiedStart : SatisfiedPreStop : SatisfiedStop : UnsatisfiedStartability : Satisfied

The conditions to perform each action, PreStart, Start, PreStop, and Stop, areevaluated over all resources that are defined as being related to this resource inyour automation policy. The panel shows the result of that evaluation.

If a dependency is Satisfied, then the corresponding action can be taken, whennecessary. If it is unsatisfied, then it cannot be taken. In this example, the Stopdependency is unsatisfied. The AM does not inform the Agent to issue thecommands to stop the resource until the Stop dependency is satisfied. The stopdependency becoming satisfied is not sufficient, on its own, to cause the AM to tellthe agent to stop the resource. There are a number of other elements that affectthat decision, primary among which is the resource’s desired state.


A prerequisite resource is a resource that has to be in a certain state beforesomething specific can be done to this resource. Most resources are independent ofeach other. However, where there is a dependency between the resources, arelationship is present in the automation model to represent this dependency.

Some typical relationships would be as follows:MakeAvailable/WhenAvailablePrepUnavailable/WhenAssumedDown

The first relationship indicates that the resource that is the target of therelationship must be up before this resource can be started. The second relationshipindicates that we cannot issue the commands to prepare the resource to be shutdown until the target resource is ready. That is, the supporting resource is down orcan be safely assumed to be down.

There is also a special relationship, called HasParent, that is a combination of twonormal relationships: MakeAvailable/WhenAvailable from child to parent (that is,that resource has to be up before this one can be started) and MakeUnavailable/WhenAssumedDown going the other way (that is, this resource must be down beforethat one can be stopped).

For example, the relationships for RMF are:Backward Relationships:

RMFGAT/APL/KEY1 HasParent

Forward Relationships:JES2/APL/KEY1 HasParent

In this example, the RMFGAT resource is a child of this resource. The resourcemust be running before the RMFGAT resource can be started and that theRMFGAT resource must be stopped before this resource can be stopped. Likewise,the RMF resource itself is a child of JES2. JES2 must be up before the RMF resourceis started and that you shut down the RMF resource before you shut down JES2.

History

The History section is at the bottom of the INGINFO panel and looks like asfollows:

History :2014-07-28 19:14:43 Startup for RMF/APL/KEY1 completedHSAL6269I Status/Automation is IdleHSAL6348I Group Observer Update RequestedHSAL6282I Status/Compound is SatisfactoryHSAL6172I Group Observer update sent

2014-07-28 19:14:42 Agent status for RMF/APL/KEY1 = UPHSAL6261I Status/Observed is AvailableHSAL6271I Status/Automation is BusyHSAL6348I Group Observer Update RequestedHSAL6157I Make Available order completedHSAL6426I Agent ordered timer purgedHSAL6172I Group Observer update sent

2014-07-28 19:14:42 Agent status for RMFGAT/APL/KEY1 = ACTIVEHSAL6315I Shutdown supporters are active

2014-07-28 19:14:42 Agent status for RMF/APL/KEY1 = ACTIVEHSAL6260I Status/Observed is StartingHSAL6271I Status/Automation is Busy

2014-07-28 19:14:40 Agent status for RMF/APL/KEY1 = STARTEDHSAL6260I Status/Observed is StartingHSAL6476I Resource Seen ActiveHSAL6419I Resource Marked Available


Each major entry represents a work item that the AM processed. That is, an updatefrom the automation agent. Between the work items are HSAL messages that aregenerated from the automation logic engine.

The messages record:v Observations such as a change in a resources status: HSAL6260I Status/Observed

is Starting

v Conclusions that are reached: HSAL6315I Shutdown supporters are activev Decisions that are made: HSAL6126I Resource can be startedv Actions that are taken: HSAL6152I Make Available order sent

The history sequence that is illustrated shows messages that are displayed towardsthe end of an automated startup of RMF. The bold lines show what is happeningon the automation agent with the oldest ones at the bottom. The messages inbetween are sorted with the oldest ones at the top of each group.

If things are not working properly, the history sequence shows valuableinformation for problem determination.

The DISPSTAT CommandThe agent also has its own, internal representation of the resources that are beingautomated. The name of the agent’s resource is the same as the name of themanager’s resource, but without the type and system qualifiers. Agent resourcesare known, for historical reasons, as subsystems.

For example, the agent resource for RMF/APL/KEY1 is RMF.

Only APL resources have corresponding agent subsystems.

The DISPSTAT command displays a summary of the agent’s information about oneor more SUBSYSTEMs. You can start DISPSTAT from the command line, althoughpressing PF4 in the INGLIST interface transfers you to a DISPSTAT view for thesame set of resources. Press PF3 again to reach the INGLIST interface again.

The command’s parameter on the command line is a list of one or moreSUBSYSTEMS, which can include wildcards:

DISPSTAT RMF*

Pressing Enter then produces a panel such as this:

INGKYDS0 SA z/OS - Command Dialogs Line 1 of 4Domain ID = IPSNM -------- DISPSTAT --------- Date = 07/21/14Operator ID = MIK System = KEY1 Time = 06:00:46A dispflgs B setstate C ingreq-stop D thresholds E explain F info G treeH trigger I service J all children K children L all parents M parentsCMD Resource Status System Jobname A I S R T RS Type Activity--- ----------- -------- -------- -------- - - - - - -- -------- ---------_ RMF UP KEY1 RMF - - - - - - MVS --none--_ RMFGAT UP KEY1 RMFGAT - - - - - - MVS --none--

Command ===>PF1=Help PF2=End PF3=Return PF4=INGLIST PF5=Filters PF6=Roll



The important information here is the resource (SUBSYSTEM) name, its status, itsMVS Job Name, and the Activity field. Pressing PF10 and PF11 scrolls through acouple of extra information panels and PF7 and PF8 scrolls the list up and down.

The CMD field on the left lets you enter commands against a resource. The mostimportant are SETSTATE (B : reset the state of the resource), EXPLAIN (E : detailedinformation about the resources current state) and INFO (F: Display detailedinformation about the resource).

The J, K, L, and M commands manipulate the set of resources that information isdisplayed for based on the relationships that are defined between the resources. If,for example, you entered M against RMF, then JES2 would appear in the panel.

The DISPINFO CommandThe DISPINFO command is the agent’s detailed resource information panel.

You can initiate it from the command line, from inside the DISPSTAT panel (linecommand F) or by pressing PF4 in the INGINFO panel. If you do the latter, youare shown the agent resource corresponding to the AM resource that you werelooking at.

From the command line, enter the following command:

DISPINFO RMF

This command takes only a single resource. So if the string that you specifiedresolves to more than one resource, you are presented with a selection panel,where you can refine your resource specification.

The panel that is displayed looks as follows:

AOFKINFO SA z/OS - Command Dialogs Line 1 of 137Domain ID = IPSNM -------- DISPINFO ---------- Date = 07/21/14Operator ID = MIK Time = 06:14:42

Subsystem => RMF Target => KEY1 System name, domain IDor sysplex name

Subsystem : RMF on System : KEY1

Description : RMF automation policy...

Class : None

Job Name : RMFASID : 0095

Job Type : MVS

Current status : UPLast Monitored : 06:02:59 on 07/29/14Last Changed : 19:14:42 on 07/28/14Last MessageAOF571I 19:14:42 : RMF SUBSYSTEM STATUS FOR JOB RMF IS UP - UP

MESSAGE RECEIVED

Monitor : INGPJMONMonitor Status : ACTIVEMonitor Interval : None specified

Command ===>PF1=Help PF2=End PF3=Return PF4=INGINFO PF6=RollPF8=Forward PF9=Refresh PF12=Retrieve


The DISPINFO Display

The DISPINFO command displays the following panels:

Status

The Status section shows the resources current agent status, when it was lastupdated, and the message that is associated with that status change.

There are many agent statuses, but the primary flows that are listed are:

A normal flow for a resource that is being started: AUTODOWN -> STARTED - >ACTIVE -> UP RESTART

A normal flow for a resource that is being stopped: UP -> AUTOTERM -> AUTODOWN

Table 6 shows the statuses indicate that automated recovery is impending:

Table 6. Agent Status that indicates Automated Recovery is pending

Status Description

STOPPING The resource is being shut down outside of automation.Depending on your automation policy settings, AutomationControl might try to restart it.

ABENDING The resource is failed and is shutting down. Again, AutomationControl might try to restart it.

INACTIVE When Automation Control ran a monitor to check that theresource was running, the monitor reported that the resourcewas not active. Automation Control tries to restart it.

Table 7 shows the statuses indicating there is a problem that automation cannot fixon its own. The operators must examine the resource and get it to a state fromwhich it can be restarted. They might have to call in support. The statuses are:

Table 7. Statuses indicating Manual Intervention is required

Status Description

STARTED2 The resource is started, but it does not issue the messageindicating that it is up yet. If the resource is just running slow,this might clear itself.

HALTED An event occurs to the resource while it was up that impacts itsavailability or functionality. This might fix itself.

BREAKING The resource failed and is shut down. The nature of the failureindicates that Automation Control might not automaticallyrestart it.

BROKEN Similar to BREAKING, but the resource is down.

ZOMBIE The resource’s final termination message is received byAutomation Control, but the address space is not terminatedwithin a reasonable timeframe.

STUCK Automation Control issues all the shutdown commands that ithas for the resource, but it has not shutdown.

STOPPED The resource is shut down outside of automation andAutomation Control is instructed not to automatically restart it.


Table 7. Statuses indicating Manual Intervention is required (continued)

Status Description

CTLDOWN The resource is down and Automation Control is instructed notto start it. The agent does not treat this situation as an error.

DENIED The agent automation flag for the resource is turned off,preventing Automation Control from acting for the resource. Youcan use the INGAUTO command to re-enable automation for theresource after you determined that it is appropriate to do so.

Flags

Flags show the current, effective setting of the automation agent flags for thisresource.

Flags - Automation : YesInit Start : YesStart : YesRecovery : YesTerminate : YesRestart : Yes

Each flag controls a different aspect of automation (Start After IPL, Start fromDown, Recovery, Shutdown, Restart). If it turned off, the value of theAUTOMATION flag overrides all of the others. You can use the INGAUTOcommand to change the values and the DISPFLGS command to display both theeffective and the actual value.

Thresholds

There are some thresholds that are defined in the automation policy for theresource.

Thresholds - SUBSYSTEMCritical : 02 in 00:05:00Frequent : 02 in 00:30:00Infrequent : 02 in 01:00:00

These definitions are counted in terms of application failures (unsolicitedshutdowns or recoverable abends) within the time specified. If the Criticalthreshold for a resource is exceeded (in this case, if the abend occurs more thantwice within 5 minutes). Then, automated recovery is suspended and the resource’sstate is changed to BROKEN to await operator assessment.

Startup and Shutdown Details

The section gives the details of how Automation Control is instructed to start andstop the resource. In addition to checking that the instructions are correct, it canalso act as a reference if you must perform a startup or a shutdown manually. Usethe INGAUTO command to turn the resources Automation flag OFF during theprocess.


Active Startup : None

Active Shutdown : None

Start Up Mechanism -Scheduling Subsystem : JES2

External startup : NEVER

Start Up Process -Prestart :

None

Startup :

Start command to be used :MVS S RMF

User Start Up Commands :None specified

Poststart :None

Refreshstart :None

Anystart :None

Start Delay : 00:02:00Start Cycles : 1

Shutdown Mechanism -

External shutdown : NEVER

Captured Messages

The Captured Messages section shows the last few messages that the agent isprocessing for the resource:

Captured Messages for RMF (maximum is 4) -

2014-07-21 19:14:42 :IEF403I RMF - STARTED - TIME=19.14.41AOF571I 19:14:42 : RMF SUBSYSTEM STATUS FOR JOB RMF IS UP - UP

MESSAGE RECEIVED2014-07-21 19:14:43 :

ERB100I RMF: ACTIVE2014-07-21 19:14:44 :

ERB306D ZZ : REPLY WITH OPTIONS OR GO

The colors of the messages indicate their severity - Green (Normal), Yellow(Unusual), and Red (Critical).

If the resource ends with an abend, the section can be used to see the messagesthat are captured. Use the timestamp to find correlated messages in the Syslog andNetlog.

Policy Definitions

The Policy Definition section shows automated actions that Automation Control isinstructed to perform beyond a simple automated restart.


This example tells Automation Control that when the ERB603D WTOR is issuedduring a normal RMF start, it automatically responds GO to it.

Policy Definitions for RMF -

ERB306D :REPLY=(NORM,,’GO’)

These actions are mostly controlled by the Recovery automation flag. If you do notwant Automation Control to act, use the INGAUTO command to turn it OFF forthe resource.

Monitoring ResourcesAlthough you can monitor resources by repeatedly refreshing and reorganizing theINGLIST panel, Automation Control provides some mechanisms to do monitoringmore efficiently.

Status Display Facility (SDF)Status Display Facility (SDF) is a dynamically updated dashboard view of yoursystem. Your automation programmer can change the layout of the dashboardinformation. What you see could be different to the examples that are shown here.

You typically use SDF to monitor the system during normal operations to look forproblems. If you have multiple systems with Automation Control installed, there isa focal pointing mechanism that can concentrate all of the dynamic updates to asingle dashboard. Here, you can monitor all of the systems.

You start SDF from the NetView console by typing the following command:

SDF

The high-level resources panel might look as follows:

KEY1 SUMMARY-STATUSKEY1

|--------- Resources ---------|

>APPLS

>GROUPS

>MONITORS

|--------- Messages ----------|

>WTOR >MESSAGES

|------- Special Items -------|

>TWS >Tape Devices

07/21/14 07:09===>1=Help 2=Detail 6=Roll 8=Zoom 12=Top

The dynamic fields, prefixed with a greater than symbol (>) have a color accordingto the worst status contained within them. Cool colors (BLUE, GREEN) are used


for normal statuses, more neutral colors (CYAN, WHITE) are used for intermediatestatuses. Hot colors (YELLOW, PINK, RED) are used for critical statuses.

To see more detail, place the cursor on a status and press PF8. A panel is displayedshowing all of the status posts in that category (you might have to scroll with PF10and PF11 to see all of them).

KEY1 KEY1: SUBSYSTEM-STATUS 1/19 of 19

NETVIEWEM_DFD_MASTEREM_CFRZAPLMIKMONMAMIKMONXPALWAYSXPFINALMIKFTPEM_AFD_PARENTFD_SIMPLEFD_TRIGGERXPNEVERFD_CHILDSLOWSTARTNONMVSEM_B

07/21/14 07:12===>1=Help 2=Detail 6=Roll 9=Bottom 10=Previous 11=Next 12=Top13=EXPLAIN 17=SETSTATE 18=INGVOTE 19=INGREQ 23=INGLIST 24=INGINFO

Your automation programmer can set up your automation policy so that only someof the defined resources are shown in SDF. If they do so, you must be aware thatthere can be activities that the SDF display does not show.

You must press PF7 to go back up to the higher level panel. If the list of resourcesis too large to fit on the screen, you must use PF10 and PF11 to scroll through thelist.

The PF13 through PF24 keys can be set to issue Automation Control commandsdirectly against a resource. Put the cursor over the resource and press the Shiftplus the PF Key.

To see more detail about an item, place the cursor over the item and press PF2. Adetail record is displayed for the status change event:


1 of 19 ---- Detail Status Display ---- 07/21/14 07:14:59

Component . . . : NETVIEW System . . . . : KEY1

Color . . . . . : GREEN Priority . . . : 640

Date . . . . . : 07/21/14 Time . . . . . : 19:14:03

Reporter . . . : AUTWRK16 Node . . . . . : IPSNM

Jobname . . . . : NETBTST1

Reference value : NETVIEW

AOF571I 19:14:01 : NETVIEW SUBSYSTEM STATUS FOR JOB NETBTST1 IS UP - AT IPL

===>1=Help 3=Return 4=Delete 6=Roll 7=Up 8=Down 11=Bottom 12=Top

This record shows some details of the resource and the captured message that isassociated with the status value. The detail records are maintained as an orderedstack and you may scroll up and down this stack with the PF7 and PF8 keys. PressPF3 to return to the dynamic SDF panels.

You can also show the detail display from the top-level SDF panel by pressing PF2while the cursor is over a dynamic field. In this case, it initially shows the detailsof the most critical status record.

The INGNTFY Command and FunctionsThe INGNTFY command turns on and off message notification.

When the command is turned on, the messages that you select to see are sent toyour NetView console. INGNTFY is set in the Policy Database through thecustomization dialog. The INGNTFY command provides the following functions:

Autowrap

If you do not have autowrap turned on, you must press enter to clear informationon the panel.

To turn on autowrap, enter:

AUTOWRAP 10

This instruction makes the NetView component wait 10 seconds before the screenis cleared of information and shows the next page of messages that are buffered.You can set other times if you want. Setting a value of 0 flushes the buffer andreturns to real-time monitoring.

To stop autowrap, issue the following command:

AUTOWRAP NO

This instruction means that you have to manually press Enter to clear theinformation on the screen and see the next set of messages.


Message Classes

Messages within Automation Control are organized into classes, and they are usedon the INGNTFY panel to select the messages that you want to see.

Table 8. Selected Automation Control Message Classes. See IBM System Automation forz/OS Messages and Codes for the full table.

Class code Description

40 All automation agent messages. OK for testing, but can become congestedwhen automation is working hard.

46 User intervention is required. Automation wants an operator to do something.

50 Critical Threshold exceeded messages. Relevant resources are automaticallyrecovered.

80 All automation manager messages. OK for testing, but can become congestedwhen automation is working hard.

81 Intervention is required. Issued for resources where Automation Controlthinks operator intervention is required.

82 Automation is denied. Automation Control wants to do something to aresource but the automation flag is off.

90 Infrastructure. Issued if the AM encounters a problem.

A basic set of messages for an operator to monitor are 46, 50, 81, 82 and 90.

Getting Messages

To monitor messages, you must enter the INGNTFY command:

INGNTFY

A list of all currently defined Notify Operators are displayed. Some operatorsmight be predefined in your automation policy.

AOFKAANT SA z/OS - Command Dialogs Line 1 of 1Domain ID = IPSNM ---------- INGNTFY ---------- Date = 07/20/14Operator ID = MIK Time = 08:25:00

Cmd: A Add C Show/Change settings D Delete O Turn OFF msg receiving

Cmd Operator System Log Rcv Description Classes--- -------- -------- --- --- -------------------- ----------------------------_ SYSOPS KEY1 N Y 44 45 46 50 51 52 80


PF9=Refresh PF12=Retrieve


Messages that are monitored by the SYSOPS pseudo-id get echoed onto the SysLogand Master Consoles.

To add yourself as a new message receiver, enter an A as a command against anyof the existing entries.

AOFKAASN SA z/OS - Command DialogsDomain ID = IPSNM ---------- INGNTFY ---------- Date = 07/20/14Operator ID = MIK Time = 08:28:16

Status/Action => ADD Operator status:ON - Set your notifications ONOFF - Set your notifications OFFADD - Add or Modify an operatorDELETE - Remove an operatorQUERY - Look up an operator

Operator ID => Operator for ADD, DELETE or QUERYClasses => 44 45 46 50 51 52 80Description =>

Held Messages - Information => Immediate Action =>Eventual Action => Immediate Decision =>System Wait =>

Target => KEY1 System name, domain ID or sysplex name

AOF710A VERIFY/REVISE INPUT AND THEN PRESS ENTERCommand ===>

PF1=Help PF2=End PF3=Return PF6=RollPF12=Retrieve

You must specify your NetView user ID, the classes of messages you want toreceive and then press Enter.

Press PF3 to exit the panel and press PF9 to refresh the list of notificationoperators.

Stopping and Restarting the Message Flow

If you want to stop receiving messages, use the O command code on the INGNTFYpanel.

From the NetView Console you can type the following command to turn offmessages:

INGNTFY OFF

You can turn back on messages by typing this command:

INGNTFY ON

There is no confirmation message when used this way.


Message Display

The messages that are displayed on your NetView console appear as follows:

IACz NM Tivoli NetView IPSNM MIK 07/20/14 08:31:26| IPSNM HSAL6030I IMSC11F2/APL/KEY1; IN AUTOMATION| IPSNM HSAL6030I IMSC11M1/APL/KEY1; IN AUTOMATION| IPSNM HSAL6030I IMSC11FD/APL/KEY1; IN AUTOMATION| IPSNM HSAL6020I IMSC11F1/APL/KEY1; AWAITING AUTOMATION| IPSNM HSAL6020I IMSC11F2/APL/KEY1; AWAITING AUTOMATION| IPSNM HSAL6020I IMSC11M1/APL/KEY1; AWAITING AUTOMATION| IPSNM HSAL6020I IMSC11FD/APL/KEY1; AWAITING AUTOMATION----------------------------------------------------------------------------| IPSNM HSAL6020I SNA1DBM1/APL/KEY1; AWAITING AUTOMATION| IPSNM HSAL6020I SNA1DIST/APL/KEY1; AWAITING AUTOMATION| IPSNM HSAL6020I SNA1IRLM/APL/KEY1; AWAITING AUTOMATION| IPSNM HSAL6012E APPLGR_IO/APG/KEY1; INTERVENTION REQUIRED; AUTOMATION

INHIBITED| IPSNM HSAL6012E APPLGR_SAM/APG/KEY1; INTERVENTION REQUIRED; AUTOMATION

INHIBITED| IPSNM HSAL6012E IMSMC1CTL/APG/KEY1; INTERVENTION REQUIRED; AUTOMATION

INHIBITED| IPSNM HSAL6012E IMSMC1APPL/APG/KEY1; INTERVENTION REQUIRED; AUTOMATION

INHIBITED| IPSNM HSAL6020I IMSC11F1/APL/KEY1; AWAITING AUTOMATION| IPSNM HSAL6020I IMSC11F2/APL/KEY1; AWAITING AUTOMATION| IPSNM HSAL6020I IMSC11M1/APL/KEY1; AWAITING AUTOMATION| IPSNM HSAL6020I IMSC11FD/APL/KEY1; AWAITING AUTOMATION| IPSNM HSAL6020I APPLGR_IO/APG/KEY1; AWAITING AUTOMATION| IPSNM HSAL6020I APPLGR_SAM/APG/KEY1; AWAITING AUTOMATION| IPSNM HSAL6020I IMSMC1CTL/APG/KEY1; AWAITING AUTOMATION| IPSNM HSAL6020I IMSMC1APPL/APG/KEY1; AWAITING AUTOMATION| IPSNM HSAL6020I IMSMC1FDBR/APG; AWAITING AUTOMATION| IPSNM HSAL6030I IMSC11F1/APL/KEY1; IN AUTOMATION???

The messages are color-coded according to severity – Green (OK), Yellow(Warning), Red (Problem).

Held Messages

If you asked for the messages to be held on the INGNTFY panel, the messagesmove to the top of the panel when the screen is cleared. They remain there untilyou place your cursor on them and press Enter.

You can use the DM utility command to remove the messages:

DM *

This command deletes all held messages. In general, you hold important messages.

Message Help

You can use help to get details about a message:

HELP HSAL6020

This example shows of the message:


HSAL6020I resource; AWAITING AUTOMATION

Explanation: The resource is automatable, but is waiting forprerequisites to be satisfied. These could be either dependencies ortriggers.

The variable resource shows the name of the resource.

System Action: Automation waits until the prerequisites for automationare satisfied and then starts processing.

Operator Response: If the prerequisites involve operator action, forexample, manually setting a trigger, check that this was done.

System Programmer Response: None.

Classes: 80, 84.

Starting and Stopping Resources

Default AvailabilityIn your automation policy, each resource has a Default Desired Status setting.

The possible values for the setting are as follows:

Table 9. Default Desired Status settings

Default DesiredStatus setting Description

Always The resource is always up.

In the absence of any other instruction, the resource is started andis recovered if it fails. This is usually the most common setting.

On Demand The resource is up if it is needed and it is down otherwise.

If the resource is needed to support a resource that you must start,then this resource is started and recovered if it fails. If the demandfor it goes away, it is shut down.

As Is Automation does not start or stop the resource unless instructed todo so.

If the resource is running, it is left alone, but it is not recovered if itfails. If it is down, it is also left alone. Use this status setting forresources that you do not want automation to take action.

There is some inference of these settings through the parent-child tree, with theAM working out an effective Default Desired State for each resource. TheINGINFO panel shows the value:

Desired Available : Always

The Default Desired Status provides the background availability goals that you areworking with as an operator. It explains that the automation with the on demandsetting can take your commands and amplify them, if, for example, you askAutomation Control to stop the only resource that is providing demand for a chainof on demand resources. Then Automation Control shuts down all the resources inthe chain in response to your request to stop the one resource at the bottom.Automation Control is working to minimize the dependencies in running yoursystem. If it causes operational problems, then you must discuss the matter withyour automation programmer.


Groups

Groups of resources are covered in “Application Groups” on page 122, but notethat any non-passive group overrides the Default Desired Status settings of all ofits members. You start and stop groups the same way that you start and stopapplication resources.

Persistent RequestsThe mechanism that Automation Control provides for operators to requestresources to be started and stopped is a persistent request-based mechanism.

When you request a resource to be started or stopped, Automation Control storesthat fact. The requests interface with the automation by changing the resource’sDesired Status setting. If there is a request from an operator against the resource,its Desired Status setting is set to the value that the operator requested.

If you ask for a resource to be stopped, Automation Control stops it. It is keptdown until you cancel that request. If you ask for a resource to be startedAutomation Control brings it up and recovers it if it fails. It is kept up until youcancel that request. When you tell Automation Control to stop or start a resource,you are changing its Desired state (overriding the default Desired state) untilfurther notice.

The expectation here is that all regular starting and stopping of resources isautomated through one or more Automation Control schedules, the defaultsettings, or both. So operators take direct control of a resource to stop it or start itunder exceptional circumstances. The correct action after the operators completetheir action is to cancel the request against the resource to return control of it toAutomation Control. The operators must not issue a request for the counter action.Use request and cancel, not request and counter-request.

Request Priorities

If there are multiple requests against a resource from different sources, forexample, an operator and a schedule, then the requests priority is used todetermine which request takes priority and actually sets the resources Desiredstatus. The priorities are divided into three broad bands, LOW, HIGH and FORCE.FORCE is only used by operators and for certain scenarios where an automatedshutdown of a dependent resource is required in response to the failure of thesupporting resource. Within each priority band, requests from the Operator havethe highest priority.

For example, if you put a DOWN request in at 6:00 a.m. (causing the resource tobe stopped), and at 7:00 a.m. a schedule puts in an UP request. Then, the resourceremains down and is not started at 7:00 a.m. because the higher priority operatorrequest is still present against the resource.


When you complete the necessary actions to bring the resource down, you mustcancel your stop request to return the resource to Automation Control’s control.Automation Control can then start it in response to, for example, a schedulerequest.

Votes

A request asks for the Desired state of a resource to be set to a specific state. Theautomation model, however, contains many resources that are connected byvarious dependencies, which generally serve to prevent resources from beingstarted and stopped. Consider a request to stop JES2; it has many children, all ofwhich place a condition on its shutdown that they are shut down first. Expectingan operator to know and manually request that each of these children is stopped isunreasonable. Thus, objects that represent the request and its action get propagatedthrough the resource structure. They are called votes.

The propagation of votes to resources depends on the action that the votesrepresent and the relationships that are present within the structure. Votes for stoprequests tend to be propagated to child resources that are dependent on thestopping of the resource. Votes for start requests tend to get propagated to parentsthat are supporters of the start of the resource.

Each resource examines all of the votes that are passed to it and selects the onewith the highest priority. The priority comes from the request that originated thevote. In a tie breaker, for example, votes from two or more requests from the samesource (OPERATOR, SCHEDULE, and so on) are present, and a vote to be UPbeats a vote to be DOWN.

Locked Votes

When you are working with Automation Control, you might encounter a lockedvote. Locked votes occur because the resources did not reach a finite state yet.When you request Automation Control to stop a resource, it starts issuingcommands from a list of shutdown commands until the resource actually comesdown. If it does not stop, it posts it to an error status. While the agent is working,the vote that triggered the request against the resource is locked. No furtherchange can occur. The agent goes from half way through shutting a resource downto starting it. At the end of the shutdown process (successful or otherwise) the voteis unlocked. You then replace it with a more forceful shutdown sequence if it fails.

5 am 6 am 7 am 8 am

OperatorStop

OperatorStop

OperatorStop

ScheduleStart

ScheduleStart

APL UP

APL DOWN

(artname: requestoverlap.gif)Figure 11. Operator Request Priorities to hold down Resource


Starts follow a similar process, but during a start you can override the lock byspecifying INTERRUPT=YES on your INGREQ request, replacing the start votewith, for example, a shutdown vote. However, there is no guarantee that thedefault shutdown sequence actually works.

The INGREQ CommandINGREQ is the main dialog for entering requests to be sent to the AutomationManager.

You can enter a request directly, through any of the available front ends or fromthe INGLIST panel with commands B (Start) or C (Stop). When not started directly,some of the input fields are prefilled.

INGKYRU0 SA z/OS - Command Dialogs Page 1 of 2Domain ID = IPSNM ---------- INGREQ ---------- Date = 07/14/14Operator ID = MIK Time = 05:03:50

Resource => RMF/APL/KEY1 format: name/type/systemTarget => System name, domain ID or sysplex name

Request => Request type (START/UP, STOP/DOWN or CANCEL)Type => NORM Type of processing (NORM/IMMED/FORCE/user) or ?Scope => Request scope (ONLY/CHILDREN/ALL)Priority => LOW Priority of request (FORCE/HIGH/LOW)Expire => , Expiration date(yyyy-mm-dd), time(hh:mm)AutoRemove => - see help for listRestart => NO Restart resource after shutdown (YES/NO)Override => NO (ALL/NO/TRG/FLG/DPY/STS)Verify => YES Check affected resources (YES/NO/WTOR)Comment =>

Appl Parms =>

AOF710A VERIFY/REVISE INPUT AND THEN PRESS ENTERCommand ===>

PF1=Help PF2=End PF3=Return PF6=RollPF8=Next Panel PF12=Retrieve

The most important things on the panel are the resource name, the requestedaction (START or STOP) and the Restart Option.

To start a resource, enter its resource name, START as the request and press Enter.To stop a resource, do the same but with STOP as the request.

You now see a verification panel:


AOFKVFY1 SA z/OS - Command Dialogs Line 1 of 2Domain ID = IPSNM ---------- INGREQ ---------- Date = 07/14/14Operator ID = MIK Time = 08:15:02

Verify affected resources for request STOP

CMD: S show overrides T show trigger details V show votesCmd Name Type System TRG SVP W Action Type Observed Stat--- ----------- ---- -------- --- ---- - ------ ---------- -------------_ RMF APL KEY1 Y STOP NORM AVAILABLE_ RMFGAT APL KEY1 Y STOP NORM AVAILABLE


PF10=GO PF11=CANCEL PF12=Retrieve

The panel lists the resources that are affected by the action, the resources that votesare directly propagated to. Press PF10 to send the request to the AutomationManager. It then takes the actions that you requested. Column W indicates througha YES/NO indicator that the vote is considered by Automation Control to be theoverriding or "winning" request. It is the highest priority vote on the resource anddetermines if the list of resources is acceptable.

The INGVOTE Command - Purging Your RequestThe request that you just added with the INGREQ dialog remains in theAutomation Manager until you remove it. To remove the vote, you must use theINGVOTE command.

The INGVOTE command runs against a single resource and shows you all of thevotes and requests that accumulated against it.

INGKYRQ0 SA z/OS - Command Dialogs Line 1 of 5Domain ID = IPSNM ---------- INGVOTE ---------- Date = 07/14/14Operator ID = MIK Sysplex = SYSPLEX_GROUP_01 Time = 09:15:32

Resource => RMF/APL/KEY1Target => System name, domain ID or sysplex name

Desired Available..: Always

Cmd: C cancel request K Kill request S show request detailsCmd Action WIN Request/Vote Data--- ------ --- ----------------------------------------------------------------_ STOP Y Request : MakeUnAvailable

Created : 2014-07-14 09:15:19Originator : OPERATOR(MIK)Priority : 01720000 Should Be Down - OperatorStatus : Winning/Satisfied



In this case, the request is entered against RMF, so you can cancel it directly fromby entering a K against it. (C does the same thing, but goes through a verificationpanel).


If we look at RMFGAT before you cancel the request, you see this information:

INGKYRQ0 SA z/OS - Command Dialogs Line 1 of 5Domain ID = IPSNM ---------- INGVOTE ---------- Date = 07/14/14Operator ID = MIK Sysplex = SYSPLEX_GROUP_01 Time = 09:18:46

Resource => RMFGAT/APL/KEY1Target => System name, domain ID or sysplex name

Desired Available..: Always

Cmd: C cancel request K Kill request S show request detailsCmd Action WIN Request/Vote Data--- ------ --- ---------------------------------------------------------------

STOP Y Vote : MakeUnAvailableFrom Req. : MakeUnAvailable for RMF/APL/KEY1Created : 2014-07-14 09:15:19Originator : OPERATOR(MIK)Priority : 01720000 Should Be Down - Operator



The INGVOTE command indicates that it is a vote, not a request, and an inputfield is not displayed for it. The From Request field indicates the resource that therequest was entered against. You have to run the INGREQ REQ=CANCELcommand against that resource if you want to cancel the request behind the vote.

Application GroupsApplication Groups (APG) are active automation elements that manage theavailability of a small set of applications.

For example, a group might be all the resources that are needed to run a CICS oran IMS. Or, at a higher level, a complete application, consisting of subgroups tomanage the complex resources that are needed to make the application work.

The advantages of groups are that they automatically manage the availability ofthe resources they are looking after. They provide you with a single point ofcontrol to request that the resources are stopped or started. The down side is thatif an operator does not tell the groups what he wants, the groups can end upworking at cross purposes.

Application Group Types

There are three types of Application Groups (APG) available within AutomationControl:v Basicv Movev Server

Basic Groups

Basic Groups manage the resources that are defined to them as if the resourceswere a single resource. Request that the group starts and all the resources start,stops and it stops all of the resources. If one of the resources fails and cannot berestarted, the group as a whole is broken, which can lead to the group of resources


being shut down.

Figure 12 shows a Basic group that contains two applications; B/APL and C/APL.The group is dependent on A/APL application. Neither the B/APL or C/APLapplication can be started before the A/APL application is up. The E/APL andF/APL applications are dependent on the group, and cannot be started until bothmembers of the group, B/APL and C/APL, are up. The G/APL and D/APLapplications, however, are directly dependent on specific group members. Thesetwo applications can be started as soon as that particular member is up, andregardless of the state of the other member.

Move Groups

Move Groups manage the availability of a single resource on a single system. Theresource is a single APL or is a Basic group (or even a Server Group or anotherMove group). The group is responsible for picking the member to initially activateand for picking other members to activate as required to maintain its availability.

B/APL C/APL

BASIC / APG

A/APL

D/APL E/APL F/APL

J/APLI/APLH/APL

G/APL

(artname: Group_Basic_2.gif)Figure 12. Basic Group


Figure 13 shows a Move group with three alternate members: B1/APL, B2/APL,and B3/APL. Because it is a Move group, only one of these applications can be upat any given time. The group itself is dependent on the A/APL application. It mustbe up before any of the Bn/APL resources can be started. Again, the E/APL andF/APL applications are dependent on the group. These applications can be startedwhen any one of the three Bn/APL applications is up. The three Cn/APLapplications are directly dependent on the corresponding Bn/APL applications.They are only started if the Move group chose to start its Bn/APL parent and thatapplication is up.

Server Groups

Like Move Groups, they manage the availability of resources. A server group getsa set of resource instances and a target number of them to keep available. It isresponsible for picking the instances that originally get started and for "moving"them around to maintain availability.

B1/APL B2/APL B3/APL

MOVE / APG

A/APL

C1/APL C2/APL C3/APL

D1/APL D2/APL D3/APL

E/APL F/APL

J/APLI/APL

(artname: Group_Move_2.gif)Figure 13. Move Group


Figure 14 shows a Server group with three equivalent members: the B1/APL,B2/APL, and B3/APL. The Server group’s goal is to have two of its members up,so the third is down. The group is dependent on the A/APL application. None ofits members can be started until the A/APL application is up. Again, the E/APLand F/APL applications are dependent on the group. They can be started after twomembers of the group become available. The three Cn/APL applications aredirectly dependent on the corresponding the Bn/APL applications. The Cn/APLapplications are started if the Server group chooses to start its Bn/APL applicationand that application is up.

On a single system a Server group can be used in scenarios where, you must beable to dynamically expand and reduce the available capacity that an applicationpresents. This is done by dynamically changing the resources availability target.

RelationshipsRelationships for a group work on the group and are passed onto the group’smembers.

If a group is a child of a resource, every member of the group is also considered tobe a child of the resource from the point of view of working out what can bestopped and started. There is an exception for Move and Server groups. Move andServer groups allow their members to be stopped (provided the group as a wholeis not being stopped) while their stop dependency is unsatisfied. They must beable to change their set of active members.

RunmodesRunmodes are not groups, but they can provide a similar function at some levels.

Runmodes are defined as sets of runtokens that are used to tag individualresources. You then select the runmode that you want to be active on a system.

B1/APL B2/APL B3/APL

SERVER / APG

A/APL

C1/APL C2/APL C3/APL

D1/APL D2/APL D3/APL

E/APL F/APL

J/APLI/APL

(artname: Group_Server_2.gif)Figure 14. Server Group


The INGRUN command can be used to activate or deactivate a particularrunmode. It is suggested that runmodes rather than large groups of unrelatedresources are used for "bulk" application control on a system.

For more information about Runmodes, see IBM System Automation for z/OS User’sGuide.

Operating Application GroupsYou start and stop groups with the same commands, INGREQ and INGVOTE, thatyou use to operate standard APL resources. These commands request that thegroup is started or stopped according to its predefined policies.

Operating Group Members:

Operations on Group Members are not recommended because your instructions arein conflict with the groups directives.

Move and Server groups activate a different resource, while Basic groups decide toshut down the whole group. All types of groups can override your directive. Or,the groups delay a directive until some recovery action is taken to reduce itsimpact upon availability.

If you must use application groups, you can use the INGREQ and INGVOTEcommands as for any other resource; however, watch for unexpected reactions toyour instructions.

Manage Application GroupsWith Basic groups, there is nothing that you can do to isolate individual members.With Move and Server groups, you have the option of modifying the groupspreferences to temporarily override the policy set for the group in theCustomization Dialog.

You can use this facility to, for example, change the member that a move groupselects to be active.

To do so, you must run the INGGROUP group and specify the name of the groupthat you want to manage:

INGKYGRA SA z/OS - Command DialogsDomain ID = IPSNM ---------- INGGROUP ---------- Date = 07/08/14Operator ID = MIK Sysplex = SYSPLEX_GROUP_01 Time = 09:01:30

Specify or revise the following data:

Target => System name, domain ID or sysplex name

Action => EXCLUDE-AVOID-INCLUDE or ACTIVATE-PACIFY orADJUST or RESET DEFAULT or OVERRIDES, POLICY orRECYCLE-CANCEL

Opt.Parms =>

Group(s) => SRVGRP1/APG/KEY1

System(s) =>

Command ===>PF1=Help PF2=End PF3=Return PF4=Members PF6=Roll

PF10=GO PF12=Retrieve


You must press PF4 to show the members and the policy for them:

INGKYGRB SA z/OS - Command Dialogs Line 1 of 2Domain ID = IPSNM ---------- INGGROUP ---------- Date = 07/08/14Operator ID = MIK Sysplex = SYSPLEX_GROUP_01 Time = 09:04:24

Group: SRVGRP1/APG/KEY1 Nature: Server Passive: NODescription: .Excluded :Avoided :Mode : Normal Availability Target: 1 Adjust: 0 Result=> 0__

Satisfactory Target=> 0 Adjust: 0Rolling Recycle: None

Name Type System Pref Adj Result Avl Eff Stat Act----------- ---- -------- ---- ----- ------ ---- ---- ---- ----SRVAPPL1 APL KEY1 700 0 ___700 No 950 Sel --SRVAPPL2 APL KEY1 700 0 ___700 No 700 Uns --


PF9=Refresh PF10=GO PF11=Reset PF12=Retrieve

The Result column can be edited. If you enter a new preference value for themember, the software calculates an adjustment to be applied to the base policyvalue to make the resulting preference the value that you specified. The Actcolumn indicates any actions that are likely to be taken as a result of applyingyour change.v To force a member to be stopped, enter a result of 1.v To force a member to be started, enter a result greater than the highest value in

the Eff column.v To return to the default values specified in your automation policy, press PF11.

A table of valid preference values is documented in the IBM System Automation forz/OS User’s Guide.

After the changes, you must press PF10 to activate those changes. If you exit thedialog with PF3, your changes are discarded.

You can also, for a Server group, change the values the Availability Target andSatisfactory Target fields. The Availability target sets the number of group membersthat are started. The Satisfactory target specifies a lower number that have to bestarted for the group’s dependencies to be considered satisfied. For example, if fivemembers are started, you can set the satisfactory target to 2 to begin startingresources that are dependent on the group while the remaining three members arestill initializing.

These panels are available for Basic groups, but you cannot change anything.

Automation Policy Management

Customization and PoliciesTo work, Automation Control requires a model of your application workload andsome policy definitions that characterize your environment.

This information is entered through an ISPF application that is called theCustomization Dialog that is provided as a part of Automation Control. The datain the model is stored in a data set known as a Policy Database (PDB). The PDB


gets built (compiled) into another data set called a Systems OperationsConfiguration File (SOCNTL) that is used by Automation Control at run time. TheSOCNTL file then must be copied onto each system that loads its automationpolicy from it.

The SOCNTL file is defined to the Automation Manager task, usually through itsHSAPRMxx member, which resides in a data set in your systems PARMLIBconcatenation. The SOCNTL file can be anywhere on your system where both theAutomation Manager and the Automation Agent can read it. Although, you canuse a generation data group (GDG) for the deployed version of your SOCNTL file,it is not strictly required.

When the Automation Manager initializes, it pulls the name of the SOCNTL filethat the Automation Manager is meant to use out of the HSAPRMxx member andloads. Then, the Automation Manager processes the parts of the SOCNTL file it issupposed to load. A SOCNTL file data set contains data for many systems. So theAutomation Manager first must determine which files are required for use both bythe Automation Manager and the agent before Automation Manager loads them.

When the Automation Agent initializes, it requests of the Automation Managerwhich SOCNTL data set it is meant to use. The Automation Manager respondswith the name of the data set that is loaded and the agent then loads itscorresponding files from the SOCNTL data set.

Note: Safeguard: The data that is loaded by the Automation Manager includes aCustomization Timestamp. The time stamp identifies the last time that the datawas edited in the Customization Dialog before the SOCNTL data set was built. Thetime stamp is included in the response sent to the agent and is checked against thetime stamp that the agent extracts from the data that is going to load. If the twotime stamps do not match, the agent refuses to proceed with the load and you donot have automation for your system. If this mismatch happens, use the MVSMODIFY command to modify the Automation Manager and request it to load anew automation configuration file.

For example, if your Automation Manager loads an automation policy that youbuilt yesterday, when it comes up and you overwrite the SOCNTL file with a

Model

PDB

SOCNTL

Distribute

SOCNTL

ISPFCustomization

Dialog

AutomationManager

AutomationAgent

BuildBuild

(artname: acf2.gif)Figure 15. Automation Policy Lifecycle


policy that was built today, when you stop and restart the Automation Agent thereis an issue. The Agent refuses to load the automation policy from the SOCNTL filebecause the time stamps do not match.

To fix the situation, you must instruct the Automation Manager to load the newconfiguration data with a modify command:

F INGEAMSA,REFRESH,SOCNTL_dataset_name

The Automation Manager loads the new configuration data and token and theninstructs the agent to load them. Because the tokens now match, the agent canproceed.

COLD, WARM, and HOT startsThe Automation Manager maintains data in following data sets that are used if itfails or is restarted.

Table 10. Files maintained by the Automation Manager

File Description

TakeOver File This data set stores a snapshot of the current internal state datawithin the Automation Manager.

Schedule File This data set stores data about service period overrides.

Configuration File This data set stores the name of the current SOCNTL data set inuse.

There are three different start options for the Automation Manager:

Table 11. Actions for the different Automation Manager start types

Actions Description

COLD Reads the SOCNTL data set name from HSAPRMxx, and erases theSchedule and Takeover data.

WARM Reads the SOCNTL data set name from the Configuration data set,erases the Takeover data, and restores the schedule data.

HOT Reads the SOCNTL data set name from the Configuration data set,and restores the Takeover data and the Schedule data.

Following a HOT start, the automation agents are instructed to analyze theirsystems and return status data for all of the applications that the agents areautomating.

The HOT start process is the same process that a Secondary Automation Manager(SAM) runs if it is necessary for SAM to take over as the Primary AutomationManager (PAM). If you lose both the Primary and the Secondary managers, youcan start a new automation manager with a HOT start. The HOT start attempts totake over as a PAM from the data that is left in the files. The command that isused would be as follows:

S INGEAMSA,JOBNAME=AM,SUB=MSTR,START=HOT

The command does not work if there is already an automation manager that isrunning on the system (because that is already the Primary manager). In thissituation, the newly started manager becomes a SAM.


Although it is common practice among customers to hardcode the AutomationManager’s start type as HOT, unexpected and unwanted behavior follows aprolonged system or automation outage. The automation gets restored to exactlythe state that it was in when the failure occurred. If the Automation Manager wasstopping something at the time, it continues to do so after the HOT start iscomplete. The goal of a HOT start is to enable a SAM to take over if the PAM failsor is shut down. A gap of no more than 60-120 seconds is expected. If the system isrestarted between when automation last ran and when it is being started,Automation Control automatically purges all requests that are flagged as beingpurged during the system’s next IPL.

Manage your Systems Operation Control File (SOCNTL)The Automation Manager tracks the location of the SOCNTL data set in its files,and if an agent gets recycled, it asks the Automation Manager the location of theSOCNTL data set.

The Automation Manager then sends it the name of the SOCNTL data set and thecustomization token it saved from its SOCNTL data. Then, the Agent finds theSOCNTL data set on disk and checks its customization token. If you have, forexample, overwritten the SOCNTL data set with a newer one. The agent finds it,but does not load it because the customization tokens do not match.

To recover from a token mismatch, use the command that is given at the end of“Customization and Policies” on page 127.

If you do not want the new configuration that is loaded now, you must find acopy of the old configuration. If the data set name is different, use the modifycommand to tell the Automation Manager to reload it. If you cannot do that, youcannot use automation until it is acceptable to activate the new configuration.Alternatively, your automation programmer can attempt to rebuild the oldconfiguration in the Customization Dialog.

As this situation is not preferable, there are two techniques available to you tomanager versions of the SOCNTL data set.

Simple Data Sets

If you are going to manage your SOCNTL data set as a simple data set, you mustuse a strong naming convention:

Table 12. Outline of an SOCNTL Naming Scheme

Data Set Description

MY.SOCNTL.OLD The data set you last used in production

MY.SOCNTL.CURRENT The data set you are currently using in production

MY.SOCNTL.NEW The next data set to use.

New SOCNTL data sets are installed by overwriting the MY.SOCNTL.NEW dataset. When you activate a new configuration, copy CURRENT over OLD and NEWover CURRENT, then load the updated configuration. The copying is best donewith a batch job. To instruct the Automation Manager to load the overwrittenpolicy from inside the Automation Agent use the INGAMS command:

INGAMS REFRESH,CFG=*


INGAMS instructs the Automation Manager to reload its configuration from thedata set that it is using (which is MY.SOCNTL.CURRENT). If you must switch it tothe old SOCNTL, you use:

INGAMS REFRESH,CFG=’MY.SOCNTL.OLD’

Remember to change the setting back to MY.SOCNTL.CURRENT when it isappropriate to do so.

Generation Data Groups

It is recommended that you use a Generation Data Group (GDG) to hold yourSOCNTL data. The GDG avoids many of the complications of using simple datasets. Although working with them is a little more complicated, you generally haveto use batch jobs to update them. The benefit significantly outweighs the cost.

A GDG is a data set that automatically maintains its history. When you copy a newSOCNTL data set on top of it, the old one is still kept as an accessible data set. Youcan configure the number of generations of the data set that are kept. Typically 5are used for SOCNTLs, although you can have more if you want.

The command to load an SOCNTL from a GDG is:

F AM,REFRESH,MY.SOCNTL.GDG(0)

or

INGAMS REFRESH,CFG=MY.SOCNTL.GDG(0)

The commands instruct it to load the current generation. What it stores to its file,however, is the actual name of the file on disk, MY.SOCNTL.GDG.G0000012, forexample. If an updated SOCNTL is written to the GDG, it is saved as fileMY.SOCNTL.GDG.G0000013. If the Agent must reload the old configuration(generation 12) the file is still available on disk for it to load it from. The 12 dataset is deleted after generation 18 is created (assuming you are keeping fivegenerations).

To activate a new configuration with GDGs, issue:

INGAMS REFRESH,CFG=*(0)

The current generation of the GDG is available.

To step back to an older configuration, issue:

INGAMS REFRESH,CFG=*(-1)

It is up to you to track which older generation is the one you must revert to, if thenew configuration does not work. The INGAMS 'Show Details' subcommand (B)show you which data set you are currently using when issued against the PAM:


INGKYAM3 SA z/OS - Command Dialogs Line 28 of 51Domain ID = IPSNM ---------- INGAMS ---------- Date = 01/14/14Operator ID = MIK Sysplex = SYSPLEX_GROUP_01 Time = 05:27:12

Diagnostic InfoSnapshot size : 4083260Number of resources : 422Number of requests : 109Number group requests : 99History records : 261249Max History records : 262144

Config dataset name : TEST.AOCZ.SOCNTLConfig member : HSAZ999

Z999CLGC STRUCTURE 20140109013917Z999CSCH SCHEDULE 20140111035447Z999CRES STRUCTURE 20140111035447

Config token : 2014011103544700026F7A2084Config version : 01

Command ===>PF1=Help PF2=End PF3=Return PF6=RollPF7=Back PF9=Refresh PF12=Retrieve

You have to scroll down to see the Config dataset name.

The danger when you use GDGs is that you copy so many "new" SOCNTL datasets in, your current SOCNTL data set falls off the bottom of the stack. Use astaging data set as a remedy and copy the SOCNTL data into the GDG just beforeyou go to activate it. If you find your current data is getting close to the bottom ofthe stack, you can copy it into a temporary data set. Then, write it back to the topof the stack and tell the AM to switch to it.


Chapter 7. Processor Hardware Interfaces

With the Processor Hardware Interfaces’ Automation Control component, users canmanage the local IBM mainframe hardware. By working with the component youcan achieve the following:v Consolidate, reduce, and automate manual Hardware Management Console

(HMC) operations for the local processorv Use the same user interface and automation environments that Automation

Control provides for application and system managementv Satisfy specific hardware operation and automation requirements by having the

choice between two interfaces, different in function scope and connectivity

You must complete these steps before you can use the interfaces. Throughout thechapter, references to sections in chapters of supplemental documentation help youto gather the information that is required to complete these steps. The topics thatare covered in the chapter are as follows:

Related Hardware Documentation

The following documents contain processor hardware information, relevant to theprocessor hardware interfaces:v System z Application Programming Interfaces

v System z Hardware Management Web Services API

Go to the IBM Resource Link/Library online facility to download the publicationsthat are valid for your processor.

Introduction and OverviewThe interfaces provide the automation and operation base to monitor and controlSystem z mainframe processor hardware and zEnterprise BladeCenters Extensions(zBX) with the Automation Control product. The two interfaces are listed asfollows:

Processor Operations

Processor Operations is based on TCP/IP, SNMP, and HTTP protocols. ProcessorOperations runs hardware commands and receives hardware events from thesupported mainframes and zBX.

LPAR Management

The LPAR Management interface provides a subset of the Processor Operationscommands to query and change LPAR-related hardware settings that are notdependent on external network protocols.

Mainframes that are supportedv System zv IBM zEnterprise System, IBM System z10, IBM System z9


Scope of Controlv Local processor only

Connectivity and Functionality at a GlanceAutomation Control can monitor and control the local Central Processor Complex(CPC) on which it is running. This includes all configured LPARs, systems, andz/VM guests that are running on this system. A zEnterprise BladeCenterExtension, attached to the local CPC with all entitled blades and virtual servers canalso be managed.

Figure 16 shows a type 2818 z114 processor of the zEnterprise class and anattached type 2458 zBX Blade Extension unit.

Figure Annotations

v z114 and zBX. Other supported mainframe or zEnterprise BladeCenter Extensiontypes are also valid.

v CPC Support Element (SE). The processor hardware interfaces use the SystemsManagement functions of the SE to operate the CPC and its LPARs. SEcustomization is required before the processor hardware interfaces can accessand use it.

z114 Optional zBX

HMC2

CPCSupportElement

Logical Partitions

OSA

LP1

LP2

LP3

z/OS A

z/OS B

z/VM A

Automation Control

- System z API

- HMC Web API

Blade Center Chassis

p

Bla

de

Bla

de

x

Virtual Servers

VS5

VS1

VS2

VS3

VS4

VS6

Card

PSM

Guest1

Guest2

SNMP, HTTP, TCP/IP Path

INTERNALPath

HMC1Optional

Intra Network

- ACTIVATE, DEACTIVATE ofLPARs, Blades, VM-Guestsand Virtual Servers

- LOAD a system (IPL)- Manage LPAR Controls- Set CPC Power-modes- Monitor SE/HMC security log- Monitor OS msgs in a LPAR- Issue ALERTS on HW-Msgs- Maintain Activation Profiles

Usage Examples

FirewallBridgeRouter

With Automation Controlrunning in LP1, followingHMC tasks can beautomated:

Processor LANCustomer Network

(artname: IAC_HW_Interfaces.jpg)Figure 16. Processor Hardware Interfaces


v HMC1, HMC2. Hardware Management Consoles. At least one HMC is attachedand operational in a valid CPC environment. The HMC must be customizedbefore the processor hardware interfaces can use the console. In a zBXattachment, the HMC must be configured as an Ensemble HMC.

v System z API, HMC Web API. The processor hardware interfaces ofAutomation Control use both APIs. See section “Related HardwareDocumentation” on page 133.

v Processor LAN – Customer Network. Together with the CPC and its own IntraNetwork, a processor LAN environment is available, enabling the SE - HMCcommunication for one or multiple CPCs. Support Elements are always attachedto the processor LAN. An extra HMC, configured for the processor hardwareinterfaces, might be attached to the Customer Network.

v SNMP Path. The Processor Operations hardware interface requires a TCP/IPinfrastructure for its SNMP-based communication. This means, that in the z/OSLPAR where Automation Control is running, an IP Stack must be active, with aconnection (OSA-card) to the customer network. This enables the communicationwith an attached HMC. Usually, Firewall/Bridge/Router network componentsare used to secure and isolate the two networks. This might require additioncustomization steps to grant TCP/IP based processor hardware interfacecommunication.

v HTTP Path. The communication between Processor Operations and theEnsemble HMC to manage zBX resources is based on the HTTP protocol. TheHMC web API provides this support. Similar to the SNMP path, this requires aTCP/IP infrastructure.

v TCP/IP Path. The communication between Processor Operations and a z/VMguest virtual machine is based on TCP/IP socket service. On the z/VM side, thePSM (ProcOps Service Machine) component of Processor Operations providesthis support. See the figure annotation "z/VM, PSM, Guests". Similar to theSNMP path, this requires a TCP/IP infrastructure. On the z/VM PSM host side,TCP/IP infrastructure is required.

v INTERNAL Path. The Basic Control Program Internal Interface (BCPii) allowscommunication between the LPAR Management interface of Automation Controland the SE of the local processor. More network elements, such as IP stack,network cards, or routers are not required. For Automation Control, thecomplete physical connection is located inside the CPC cage.The BCPii implementation that is used in Automation Control is not compatiblewith the BCPii base component of z/OS. The available z/OS BCPiidocumentation does not apply for Automation Control. Application programsexploiting the z/OS BCPii and Automation Control might run concurrently onthe same z/OS system.

v Logical Partitions. With Automation Control active in one LPAR, you canmonitor and control each accessible LPAR of your local CPC. The LPARManagement interface manages CPC LPAR configuration and runtime attributes.The Processor Operations interface also uses the integrated console of each LPARfor message monitoring and command forwarding. Finally, LPAR hardwarecommands such as ACTIVATE or LOAD are provided with ProcessorOperations.

v z/OS A, z/OS B, z/VM A. This represents the operating systems running in theprocessor's LPARs. In the Figure 16 on page 134, Automation Control is runningon partition LP1 on z/OS system A. To monitor and control a system, each onemust be defined in the Automation Control policy, together with the processorand related connection path (protocol) information.

Chapter 7. Processor Hardware Interfaces 135

v z/VM, PSM, Guests. The guest machines of a z/VM host, running in an LPARof the local CPC can be managed with Processor Operations. The PSM (ProcOpsService Machine) component of Processor Operations must be installed on thez/VM host system. The PSM provides the required TCP/IP connection services.This support is independent of any z/VM virtual server management that isprovided by Unified Resource Manager on IBM zEnterprise Systems.

v BladeCenter Chassis. In a zBX attachment in a zEnterprise Ensembleenvironment, you can manage the resources in a BladeCenter, such as blades orvirtual servers with Processor Operations.

v Usage Examples. Operation, configuration, and recovery tasks for a CPC and itsLPARs are performed using the Hardware Management Console. By using theprocessor hardware interfaces of Automation Control, many of these tasks canbe done with the Automation Control user interfaces, or run automated.

Preparation and Configuration

Selecting the appropriate Interface to Use

There are multiple aspects to consider for this decision. One criteria is the interfacefunction set, another is the set-up requirements to get the interface working.Table 13 lists function availability, and set-up requirements for each interface. YESmeans the HMC task is supported by the interface, and NO means the interfacedoes not support the HMC task.

Table 13. HMC Operation Management Tasks

HMC OperationsManagement Tasks Processor Operations LPAR Management

Load (IPL) a system,Power-ON OFF CPC

YES NO

Manage CPC capacity, servertime, power mode

YES NO

Manage zBX YES NO

Receive hardware events YES NO

Manage Activation Profiles(CPC, LPAR, LOAD)

YES YES

Query CPC/LPARconfiguration

YES YES

Change LPAR performancesettings

YES YES

Query CPC capacity, timeprotocol, power mode

YES YES

Query LPAR status data (forexample, PSW)

YES YES

For more information about these tasks see the HMC console and the SystemzHardware Management Console Operations Guide of your CPC. For more informationabout zBX management tasks, see the zEnterprise System Hardware ManagementConsole Operations Guide for Ensembles of your zEnterprise BladeCenter Extension.


Table 14. Required Hardware Setup Tasks

Required Hardware SetupTasks Processor Operations LPAR Management

Microcode level validation YES(Use IBM Resource Link or contact your IBM Softwaresupport to validate if service level recommendations existfor your SE or HMC, related to the API (web API, SNMP,BCPii). If so, the necessary Microcode levels (MCLs) areapplied. Automation Control has no prerequisite hardwareMCLs for its processor hardware interfaces.)

Customize API settings forSupport Element

YES(SE, HMC or both can bespecified as the connectionend points for a CPCconnection in theAutomation ControlCustomization Dialog.)

YES

Customize API settings forHardware ManagementConsole

NO

Customize API settings forEnsemble HMC

YES(Required for zBX ensembleconnections only.)

NO

Customer NetworkPreparation

YES(Regardless of the ProcessorOperations connectionendpoints, SE or HMC,connectivity between theprocessor LAN and thecustomer network is alwaysrequired.)

NO

Table 15. Required Software Setup Task List

Required Software SetupTask list Processor Operations LPAR Management

z/OS IP stack YES(Processor Operationsspecifies the IP stack to usefor a SE/HMC connection, incase Automation Controlruns in a multiple IP stackenvironment. Using aseparate IP stack forProcessor Operationsconnections is a way toisolate this IP traffic fromregular business traffic.)

NO

IBM Automation Control forz/OS Customization

See “Customization” on page139.

YES YES

Preparing the AutotasksThe work of the processor hardware interfaces in Automation Control isdistributed between the individual user operator tasks and sets of specializedautomated operator task for each interface. Automation Control provides all of therequired pre-definitions for these autotasks.


For security purposes, these specialized tasks are assigned to the AutomatedOperator role with INGAUTO as their default group. See Chapter 4, “Security,” onpage 33 for more information.


DSIPARM member AOFOPFPO contains the autotask definitions that are used forProcessor Operations. There are more autotasks pre-defined than used byAutomation Control.

Predefined tasks range Used tasks

ISQBT001 - ISQBT040

ISQCM001 - ISQCM040

ISQET001 - ISQET010

ISQEM001 - ISQET010

ISQBT001

ISQCM001

ISQET001

ISQEM001

LPAR Management

DSIPARM member AOFOPFPO contains the autotask definitions.

There are more autotasks that are predefined than used by Automation Control.

Predefined tasks Used tasks

AUTHW001 - AUTHW0033 AUTHW001

AUTHW002

Enabling LPAR Management StartupThe LPAR Management function start depends on the activation of theAUTHW001 and AUTHW002 autotasks.

When Automation Control is started, the autotasks that are defined as automatedfunction operators in your automation policy entry Automation Operators areactivated. This also activates the connection to your local processor.

Automated Function name Autotask name Task function description

HWOPER01HWOPER02

AUTHW001AUTHW002

Monitors the ConnectionCommunication task

Create an Automated Operators entry of HW_OPERS and define the HWOPER01and HWOPER02 automated functions. Select each of the automated functions(HWOPER01, HWOPER02) and type the associated autotask name from the tablein the Primary Automation Operators field. Leave the other fields empty. Finally,the HW_OPERS entry must be assigned to the system, where Automation Controlis supposed to be active. Use the WHERE USED policy of your HW_OPERS entryto do this.

For more policy-related information, see "Entry Type Reference" in IBM SystemAutomation for z/OS Defining Automation Policy.


Hardware PreparationDepending on the interface, use the following documentation references provided.For Processor Operations follow the SNMP connection instructions. For LPARManagement, follow the BCPii or BCP Internal Interface connection instructions.

Always use the highest SE/HMC workplace version information. The informationabout how to navigate and enter the SE/HMC data is related to the Classic Styleuser interface view. System z API Customization information can be found in theseresources:v See "Installing SA z/OS on Host Systems", section "Preparing the Hardware" in

IBM System Automation for z/OS Planning and Installation Guide.v Web API-related Customization information for zEnterprise Ensemble

connections for zBX can be found in "Installing SA z/OS on Host Systems",section "Preparing Ensemble HMC Communication" in IBM System Automationfor z/OS Planning and Installation Guide.

v Equivalent virtual hardware preparation of the Processor Operation support forz/VM guest machines, is documented in "Installing SA z/OS on Host Systems",section "Preparing the VM PSM" in IBM System Automation for z/OS Planning andInstallation Guide.

Hardware Resource Security

Automation Control provides the operator role concept and the TARGET commandparameter-based security options, as explained in Chapter 4, “Security,” on page33. For the processor hardware, ensemble connection, and z/VM guest machineresources, an extra authorization layer is implemented.

See the appendix "Controlling Access to the Processor Hardware Functions" in IBMSystem Automation for z/OS Planning and Installation Guide.

For HMC web API, see "Preparing Ensemble HMC Communication" in IBM SystemAutomation for z/OS Planning and Installation Guide.

The definition of a PSM security resource profile is required for the ProcessorOperations z/VM guest system support. Follow the scheme that is described in theappendix "Controlling Access to the Processor Hardware Functions" of IBM SystemAutomation for z/OS Planning and Installation Guide.

Ensure the security network name and security resource name parts of the SAFprofile name match what you defined in the Automation Control customizationdialogs for this PSM processor type.

Customization

CNMSTYLE customizationFor both of the processor hardware interfaces make sure that the AutomationControl TOWER.SA statement in your active CNMSTYLE specification includeskeyword PROCOPS. Only if so, Processor Operations or LPAR Management runsfully enabled.

See the following tower definition statement in DSIPARM member CNMSTGENfor the recommended location for your additional configurations, for example:


************************************************************************* Final SA license specification *************************************************************************TOWER = SATOWER.SA = SYSOPS license PROCOPS SATELLITE

Building BlocksThe building blocks are managed only if the key elements of the processorhardware interfaces are defined in the Automation Control policy. There are fourpolicy entry types important for the hardware interfaces: Processor, System,Enterprise, and if an attached zBX must be managed, zEnterprise Ensemble.

Processor (PRO)

This entry defines the local processor (CPC) that you want to control. The entryincludes definitions that are required to access the mainframe and details abouteach processor partition that you want to manage, such as partition name and thesystem name that is running in this partition. For example, you define a processorthat is called PROC1 with an LPAR of LP1, which has SYS1 as the system definedto run in it. Because you decided to use the Processor Operations interface protocolfor PROC1, you can use the Processor Operations policy of your SYS1 system entryto specify basic LOAD information to use when initializing SYS1 under ProcessorOperations control.

See “Usage and Operation” on page 147, for more information about the differentprocessor hardware interfaces.

To learn more about these policy entries, see "Entry Type Reference", sections"System Entry Type", and "Processor Entry Type" in IBM System Automation forz/OS Defining Automation Policy.

System (SYS)

This entry contains all definitions that Automation Control needs to manage asystem in the context of application automation. For Processor Operations use, theprocessor operations definitions are provided. These specific system policydefinitions are not required for the LPAR Management interface.

To learn more about the Processor Operations specific system policy definitions,see "Entry Type Reference", sections "System Entry Type", in IBM SystemAutomation for z/OS Defining Automation Policy.

zEnterprise Ensemble (ENS)

This entry contains the definitions for the connection to an Ensemble HMC for zBXmanagement purposes. If your local processor is defined as an ensemble membernode and has a zEnterprise BladeCenter Extension (zBX) attached, you can managethe virtual servers running in the zBX blades with Processor Operations. Theensemble definitions include the HMC address and login credentials. ProcessorOperations uses this data to communicate with the HMC using the Web API. Forexample, processor PROC1 has a zBX attached and you define the connection to itsensemble HMC as MYENS.

To obtain more policy-related information, see "Entry Type Reference", section"zEnterprise Ensemble Entry Type" in IBM System Automation for z/OS DefiningAutomation Policy.


Enterprise (ENT)

For Processor Operations only, the PROCOPS FOCAL POINTS policy of yourEnterprise entry must be defined. The minimum required definition is the primaryfocal point name. This is the NetView domain name of your Automation ControlProcessor Operations instance. Note, that the backup focal point name specificationis not used. It is reserved for future use.

To obtain more policy-related information, see "Entry Type Reference", section"Enterprise Entry Type", sub-section "PROCOPS FOCAL POINTS Policy Items" inIBM System Automation for z/OS Defining Automation Policy.

Mapping Processor Hardware Interface Items to Customization Dialog

Table 16 on page 142 lists the functional elements of the processor hardwareinterfaces shown in “Connectivity and Functionality at a Glance” on page 134 andshows their relationship to the related policy entries in the Automation ControlCustomization Dialog.

Not all required data input fields of the listed policy entries are referenced in thistable. To learn more about these policy entries and all required customization inputdata, see "Entry Type Reference", sections "Processor Entry Type", "System EntryType", and "zEnterprise Ensemble Type" in IBM System Automation for z/OSDefining Automation Policy.

Some policy entry customization items must also be defined in the SE, HMC, orzEnterprise Ensemble HMC configuration settings. Make sure, these definitions areidentical in their readable form. Examples of such items are the Auth Token,needed for an INTERNAL connection definition (must be defined in uppercase), orthe Ensemble Name required for an Ensemble HMC HTTP connection (might bedefined in mixed case characters). See “Hardware Preparation” on page 139 formore information.


Table 16. Processor Hardware Interface Items

Processor Hardware Interface Items Policy EntryRelated Policy information andcomments

z114 PROCESSOR Policy: Processor Information

Fields: Processor Type

Processor Mode

Network Name

CPC name

No processor hardware-specific nameor device type must be defined. Usethe generic type name Mainframe toclassify the processor as realhardware. By default, the ProcessorMode is set to LPAR. This is correctfor all supported mainframeprocessors.

Your mainframe processor must havean address in the (SNA) format:Network_Name.NAU. The IBMmainframes have a factory setnetwork name of IBM390PS and aNAU name that is derived from theunique CPC serial number. Bothnames can be changed by thecustomer. The SNA format processoraddress is stored in the SE and canbe determined with the SE or HMC(CPC details).

CPC Support Element PROCESSOR Policy: Processor Information

Fields: TCP/IP address or host namefirst Adapter

Make sure that the address is valid inyour customer network and that thehost name gets correctly resolved.

HMC1, HMC2 PROCESSOR Policy: Processor Information

Field: TCP/IP address or host namesecond Adapter/HMC

Make sure that the address is a validin your customer network and thatthe host name gets correctly resolved.

If you have multiple HMCs in yourenvironment, make sure that theHMC that you plan to use forProcessor Operations has yourprocessor that is defined in its CPCgroup. In case of an attached zBX,the Ensemble HMC that you want touse for blade and virtual servermanagement, can also be used tomanage the CPC and the LPARs.


Table 16. Processor Hardware Interface Items (continued)


SNMP Path PROCESSOR Policy: Processor Information

Field: Connection Protocol

The SNMP value enables ProcessorOperations SNMP communication.

HTTP Path PROCESSOR Policy: Processor Information


Set the HTTP value if your CPC is partof an zEnterprise Ensemble and has azBX attached. This requires acorresponding ENSEMBLE policyentry, with this processor defined asa member. See "BladeCenter Chassis"below.

TCP/IP Path PROCESSOR Policy: Processor Information

Field: Processor Type

Use the PSM processor type to definea connection to a ProcessorOperations Service Machine, which isrequired to manage z/VM guests.This automatically assigns theconnection protocol TCPIP for thisprocessor.

INTERNAL Path PROCESSOR Policy: Processor Information


The value INTERNAL enables the BCPiiconnection protocol for LPARManagement.

Logical Partitions (LPARs) PROCESSOR Policy: LPARs and Systems

Fields: LPAR Name

Target Mode

Target System Name

Processor Operations and LPARManagement require that you defineat least one LPAR of your CPC andassign a defined system to it,otherwise the interfaces do not work.




PSM PROCESSOR Policy: Processor Information

Fields: Processor Type

For the z/VM guest support, define aprocessor of type PSM.

See “Other functions” on page 149for details.

Policy: Guests and Systems

Here you define the name of thevirtual machine as defined on thez/VM host system, the architecturemode of the virtual machine, and thecorresponding target system name.

z/OS A, z/OS B,

z/VM A

SYSTEM Policy: System information

Field: Operating system

Image/System name

For a list of the supported operatingsystem environments, see section“Other functions” on page 149fordetails.

The Image/System name is used byProcessor Operations as the targetsystem name parameter to addresscommands to this systems CPC,LPAR, or integrated console.

In LPAR Management commands,the target system name parameter isused as a shortcut of the parameterformat processorname.LPARname.

Policy: Processors (ProcessorOperations Policy)

Selection panel is shown.

If you are not already assigned asystem in the LPARs and Systemspolicy of the processor entry, selectthe CPC-LPAR pair that you want touse for this system. Unassignedtarget systems are ignored byProcessor Operations and LPARManagement. You can define asystem entry for any of thesupported operating systems. See“Other functions” on page 149 fordetails.




z/VM guest SYSTEM Policy: System information

Field: Operating system

Image/System name

The z/OS, z/VM, Linux for Systemz, and z/VSE operating systems aresupported by Processor Operations asz/VM guest operating systems.

The name that is defined as theImage/System name is identical tothe operating system name, whichmay be different to the system entryname. The Image/System name isused by Processor Operations as thetarget system name parameter toaddress commands to this guestsystems PSM, virtual machine, orconsole.

Usage Examples SYSTEM Policy: (Processor Operations Policy)

Target System Info

IPL Info

In the Target System Info policy, youcan specify if Processor Operationsshould start a connection to theprocessor hardware/LPAR of thistarget system automatically, after theProcessor Operations initial startup iscomplete.

In the IPL Info policy, you canspecify for z/OS or z/VM targetsystems the automatic responses toimportant IPL operator promptmessages.




BladeCenter Chassis zEnterprise

Ensemble

Policy: Ensemble Info

Fields: TCP/IP Address or Hostnameof primary HMC

TCP/IP Address or Hostname ofalternate HMC

Userid

Password

The cabinet in a BladeCenter rack,where the blades are mounted, iscalled the chassis. To manage theseblades and their virtual servers, aconnection to an Ensemble HMC isrequired. This HMC is connected tothe CPC and the attached zBX.

You might define a primary, andoptionally, an alternate EnsembleHMC so that you can monitor theavailability of the alternate, while theprimary HMC is still active. If anHMC switch (manual or automatic)occurs, the alternate HMC becomesthe new primary. The IP address ofthe "old" primary becomes the IPaddress of the "new" primary.

Make sure, the primary/alternateaddresses are valid in your customernetwork and that the host names getcorrectly resolved.

The session between ProcessorOperations and an Ensemble HMC isa secure session (HTTPS), requiringuser ID, and password specifications.

Policy: Processors

Selection panel is shown

Processors that are defined with anHTTP connection protocol are listed.Select the processor that is defined asa member in the zEnterpriseEnsemble that you are currentlyediting.


Usage and Operation

Operating the Processor Hardware InterfacesThe Automation Control product offers two hardware interfaces. Depending onyour processor policy protocol definitions, one or both hardware interfaces can beused after the Automation Control Agent is started.

Details about the hardware interface commands can be found in "ProcessorOperations Commands" in IBM System Automation for z/OS Operator's Commands.

LPAR Management

This interface is based on the internal BCPii processor communication protocol anddoes not require TCP/IP. No start or stop commands are available to control theinterface. It is activated automatically as part of the Automation Control start. Asession to the Support Element of your local CPC is established after the BCPiistart is complete. When the Automation Control Agent is stopped, the BCPiiconnection to the local CPC is stopped.

Operation

Command Description

ISQCCMD This is the command interface to performthe LPAR management functions. See "Howto Monitor and Control Resources", section"Logical Partitions", sub-section "LPARManagement Functions" in IBM SystemAutomation for z/OS User’s Guide for details.


This interface requires TCP/IP. In addition to the LPAR Management tasks, thelocal CPC, its partitions, and an optionally attached zBX can be managed. Thez/VM guest systems can be also controlled.

Command Description

ISQSTART This command starts Processor Operations.Depending on your Processor Operationspolicy definitions for each entity, a ProcessorOperations connection to the target systemsand its associated CPC, an Ensemble HMCis established.

ISQSTOP This command stops Processor Operations.All active connections to the CPC, EnsembleHMC, or z/VM PSM are closed.

Operation

Command Description

ISQXDST Processor Operations Status System dialog.Shows the status of the monitoredcomponents: processor (THW), system(TGT), and the communication link.


Command Description

ISQCCMD Interface to perform the LPAR ManagementFunctions and to perform HW commoncommands such as ACTIVATE/DEACTIVATE/LOAD.

ISQECMD Interface to perform the zEnterpriseEnsemble management commands for zBXresources, such as DISCOVERY orACTIVATE/DEACTIVATE for virtual serversor blades.

ISQSEND The command communicates with the"Operating System Messages" integratedconsole (SE/HMC) for each LPAR, in orderto send commands to and receive responsesfrom the operating system running in thisLPAR.

HMC task mapping

Table 17 shows the mapping of operator HMC tasks to the correspondingcommands for each processor hardware interface.

Table 17. HMC Operations Management Tasks

HMC OperationsManagement Tasks Processor Operations LPAR Management

Load (IPL) a system ISQCCMD LOAD -

Power-ON CPC, activateLPAR

ISQCCMD ACTIVATE -

Deactivate LPAR, Power-OFFCPC

ISQCCMD DEACTIVATE -

Manage CPC capacity ISQCCMD

TCM,CBU,OOCOD

-

Manage server time network ISQCCMD STP -

Manage CPC power mode ISQCCMD POWERMOD -

Manage zBX ISQECMD -

Manage hardware ActivationProfiles

ISQCCMD PROFILE ISQCCMD PROFILE

Query CPC/LPARconfiguration and status

ISQCCMD GETSINFOGETIINFO

CPCDATA

ISQCCMD GETSINFOGETIINFO

CPCDATA

Change LPAR settings ISQCCMD ICNTL ISQCCMD ICNTL

Query CPC capacity, timeprotocol

ISQCCMD

TCDATA STPDATA

ISQCCMD

TCDATA STPDATA

Query LPAR status data (forexample, PSW)

ISQCCMD

GETIPSW

ISQCCMD GETIPSW


Other functions

Operating System Environments

While these systems are running on your local processor, you can define them inthe Automation Control PDB as Processor Operations target systems. You can thenperform base operator tasks, such as console message monitoring, LPARmanagement, activation, and IPLs for all these systems from a single point ofcontrol, the Automation Control Processor Operations focal point. The followingoperating system environments are supported:v Operating Systems: z/OS, z/VM, Linux on System z, z/VSEv Coupling Facility Control Code (CFCC)

Managing z/VM guest systems with Processor Operations

If a z/VM guest system is running in an LPAR of your local processor, ProcessorOperations can be used to manage guest systems running on this z/VM host. Inyour automation policy, define a PSM processor and define each guest that youwant to manage as a system associated with the PSM processor. You can then useProcessor Operations commands to monitor and control these guests.

To learn more about the policy entries, see "Entry Type Reference", section"Processor Entry Type", sub-section "Policy Items for PSM Processors" in IBMSystem Automation for z/OS Defining Automation Policy.

For information on how to prepare and install the PSM support, see to "InstallingSA z/OS on Host Systems", section "Preparing the VM PSM" in IBM SystemAutomation for z/OS Planning and Installation Guide.

Writing Automation Scripts

All operator commands of the processor hardware interfaces are implemented asAPIs. You can use these APIs to write your own automation REXX scripts,supplementing the existing set of commands with your environment-specificsequence of Processor Operations or LPAR Management commands. For moreinformation refer to "How to Automate Processor Operations-Controlled Resources"in IBM System Automation for z/OS Customizing and Programming Guide.

Automating Messages

In addition to the product Automation Control entries in the automation table, youcan add your own entries with the INGMSGU member. This is also valid formessages that are coming from the processor hardware interface. Messages withthe message IDs of ISQ900I, ISQ800I, and ISQ700I might be of special interest. SeeIBM System Automation for z/OS Messages and Codes for more information aboutthese messages.

Alert notifications for Processor Operations managed CPCs

Processor Operations receives hardware messages and status changes from thetarget hardware for connected systems. Some hardware messages and statuschanges might point to severe problems, which might affect the availability of themanaged systems. Processor Operations uses the INGALERT Automation Control


command to inject alerts into a system and provides built-in alert points forselected hardware problems. The following set of built-in alert points is availablefor Processor Operations:

Alert ID Description Resource Type

ISQHWMSG One of the followingimportant hardwaremessages was issued on thetarget hardware:

v Hardware problem

v Power problem

v Licensed internal codeproblem

v Licensed internal codedetected a problem

MVSESA

ISQHWST Target hardware (CPC) statusthat is changed to one of thefollowing statuses:

v DEGRADED

v SERVICE REQUIRED

MVSESA

For more information, see "Alert Based Notification" in section "Enable Alerting" inIBM System Automation for z/OS Customizing and Programming Guide.

For Hardware Messages details, refer to the Hardware Messages task, which isavailable on the Hardware Management Console. For a list of the available CPCstatuses, use the Acceptable Status tag in the details window that is shown for aselected CPC on your Hardware Management Console.


Chapter 8. Support

The following support procedures are available for managing your AutomationControl for z/OS environment.

Modifying the Maximum Number of Language Processor (REXX)Environments for NetView

The Automation Control Agent runs REXX code. REXX Language Processorenvironments are required to do so and are allocated on a system-wide basis. Youmight have to allocate more environments. Refer to IBM Tivoli NetView forz/OS Installation: Configuring Additional Components for more information.

Modifying the IEFUSI exitYou can use the IEFUSI exit to limit the region size and region limit, and to limitthe size of data spaces and hiperspaces for jobs that are started on an MVS system.If you have the IEFUSI exit on your system, modify it as needed to accommodatethe region sizes for the various data spaces that are created by the AutomationAgent:v Internal trace data space that is created at initialization that is managed through

the TRSIZE parameter in the CNMPROC startup procedurev Internal data space that is required for message automation

The IEFUSI exit is passed the address of the program name on input. Refer to z/OSMVS Installation Exits for more information.

Modifying the NetView Subsystem Interface ProcedureThe NetView subsystem is already created for you by the Configuration Assistant.However, if you have to set the parameters for the Program-to-Program interface(PPI) or set a particular command designator, see the following description.

Update the NetView subsystem interface procedure, CNMPSSI (CNMSJ010)member in the SYS1.PROCLIB data set, as required for your environment:

Changing Symbolic VariablesReview and modify the following symbolic variables as required for yourinstallation:

ARM Enables the NetView subsystem for MVS automatic restart management(ARM) and supplies a name (up to 16 characters) by which this NetViewsubsystem is to be known to ARM.

The CNMPSSI ARM parameter can have the following values:

*ARM Specifies that the NetView subsystem is to be enabled. TheNetView component generates a NetView ARM element name.

name Specifies that the NetView subsystem is to be enabled andidentifies the NetView ARM element name. This name can be 1 -16 alphanumeric characters in length. The first character must bealphabetic. The name can contain the special characters #, @, and $.


*NOARMSpecifies that the NetView subsystem is not to be enabled.*NOARM is the default value.

PPIOPTSpecifies whether you want to initialize the PPI facility. The PPIOPTparameter can have the following values:

PPI Specifies that the PPI facility is to be started and initialized for theNetView subsystem address space. You cannot request this optionfor more than one subsystem address space. If the PPI is alreadyactive on another subsystem address space, it does not initialize formore requests. PPI is the default value.

NOPPISpecifies that the PPI facility is not initialized for the subsystemaddress space.

P256BUFSpecifies the number of 256-byte PPI buffers. The default value is 300.

P4000BUFSpecifies the number of 4000-byte PPI buffers. The default value is 0.

REG Specifies the region size for the NetView subsystem buffer address space inKB (the number specified times 1024). The default value is 16600.

The default value allows for 4200 total message and command buffers. Tocalculate the correct region size for your network, refer to IBM TivoliNetView for z/OS Tuning Guide.

ROUTECDESpecifies the route code to be used for messages that are issued by the SSIaddress space.

Messages that can be issued before this parameter is processed use thedefault route code 1, regardless of the value set here. Valid values are inthe range 1 – 128.

&SQ1 Specifies the high-level qualifiers for user-defined data sets. The defaultvalue is NETVIEW.V6R2M1.

You can also adjust the CNMPSSI parameters using the SSI statements in theCNMSTYLE member.

Specifying the Subsystem Command DesignatorTo specify the NetView subsystem command designator, use theMVSPARM.Cmd.Designator statement in the CNMSTYLE member. For moreinformation about the MVSPARM.Cmd.Designator statement, see the IBM TivoliNetView for z/OS Administration Reference.

Saving Automation Manager data sets into Generation Data Groups

About this task

During the lifecycle of an Automation Manager, log data is written into uniqueAutomation Manager data sets. If an unexpected Automation Manager abendoccurs, IBM service might request these data sets for problem determination. Thebest practice *BASE_AND_PRODUCTS sample policy ensures that two AutomationManagers are active at the same time. When an Automation Manager abend


occurs, the Automation Manager is restarted by Automation Control. Now, thecontent of the Automation Manager data sets is overwritten.To prevent this situation, follow these steps to save the data sets into generationdata groups before the restart of the Automation Manager instance.

Procedure1. In the Automation Control Automation Manager start procedure:

a. Modify the startup procedure of your Automation Manager generated bythe Configuration Assistant. Refer to the setting made in the INGDOPTConfiguration Options file keyword <sa_am_start_proc>.

b. Activate by uncommenting the SLQAUX symbol.c. Remove the job end statement. For more information, see the corresponding

comment section in the JCL.d. Save your changes.

2. In the Automation Policy:a. Add the string SLQAUX=AM1 in the SYMBOL 1 field for the APL entry AM in

policy APPLICATION SYMBOLS.b. Add the string SLQAUX=AM2 in the SYMBOL 1 field for the APL entry AM2

in policy APPLICATION SYMBOLS.c. Add the string &SUBSSYMBOL1 in the Startup Parameters field for the APL

entry C_AM in policy STARTUP.d. Build the SOCNTL file.e. Refresh the configuration in your runtime environment.

Additional Configuration ConsiderationsThis section describes additional configuration considerations for setting upNetView components, including the following topics:

Configuring the Operator EnvironmentThe following topics describe aspects of the operator environment that you cancustomize:

Defining NetView OperatorsYou can define your NetView operators either by using an SAF security product,through DSIPARM member DSIOPF, or both. For detailed information aboutdefining NetView operators, refer to the IBM Tivoli NetView for z/OS SecurityReference.

Specifying the Degree of Security VerificationThe recommended degree of security for Automation Control is already describedin Chapter 4, “Security,” on page 33. If you cannot follow these recommendations,read this section.

You can define the degree of security verification to be performed when anoperator logs on by using the SECOPTS statements in the CNMSTUSR orCxxSTGEN member. For information about changing CNMSTYLE statements, seeIBM Tivoli NetView for z/OS Installation: Getting Started.

Use the REFRESH command to refresh many types of security that is used whilethe NetView component is running. The REFRESH command can be used tochange the security settings in the CNMSTUSR or CxxSTGEN member.

Chapter 8. Support 153

If you want information about... Refer to...

changing CNMSTYLE statements IBM Tivoli NetView for z/OS Installation:Getting Started

SAF checking IBM Tivoli NetView for z/OS Security Reference

REFRESH command IBM Tivoli NetView for z/OS CommandReference Volume 1 (A-N)

Defining PA and PF KeysDuring logon, an operator runs the PFKDEF command list, CNME1010, which (asa default) references keys defined in the sample CNMKEYS. This command canalso be included in the operator profile.

To change the NetView default PF key settings or the default line of text at thebottom of many NetView panels that describes PF key settings, modify CNMKEYS.

For specific information about modifying CNMKEYS, refer to the IBM TivoliNetView for z/OS Customization Guide.

Working with Data Logs and Databases

Printing the Network LogThe network log is used as a protocol for all processes and actions that arecompleted within Automation Control. This log also contains the diagnostics datain case of an error. IBM service might require this data. There are two NetView logdata sets in place that are used alternatively by the DSILOG task.

You can use the INGEPRT JCL to print the NetView log. The INGEPRT JCL wascopied to your PROCLIB data set during configuration. Further details aredescribed in the INGEPRT JCL.

It might be advisable to switch the NetView log data set right before rerunning ascenario to gather service data. This switch might avoid alternating the NetViewlog while log data is gathered.

You can use the SWITCH DSILOG command to switch the NetView log. Refer toIBM Tivoli NetView for z/OS Command Reference Volume 2.


Part 3. Appendixes


Appendix. Automation product comparison

IBM Automation Control for z/OS provides many, but not all, of the features andfunctions that are available in the enterprise versions of System Automation forz/OS and NetView for z/OS. The information contains a more detailed functionalcomparison of the three products.

It can serve as a reference for the administrators and operators. It is of particularhelp, when used with the product information of System Automation for z/OS andNetView for z/OS.

Automation Control does not co-exist with NetView for z/OS in the same LPAR,when both require access to the subsystem interface. However, Automation Controlcan co-exist with an instance of NetView for z/OS when that instance is used fornetwork management tasks.

Summary of Differences with System Automation for z/OS

IBM Automation Control for z/OS 1.1.1 is based on the advanced automationcapabilities of System Automation for z/OS and NetView for z/OS, but has thefollowing limitations:v Single system automation that is based on the NetView platformv A single point of control for up to three systems in the sysplexv Automated hardware operations through TCP/IP-based or internal hardware

interfaces on the local processor onlyv A user-defined Automation Table (if required) containing no more than 3000

characters

Automation Control does not support the following functions:v I/O Operationsv Network managementv NetView Management Consolev Full screen automationv Terminal Access Facilityv Remote operations beyond the provided single point of controlv Gateway communication between NetView domains. Instead, XCF

communication in the physical sysplex is used for the single point of control,v Integration into End-to-end Automation that is provided by IBM Tivoli System

Automation Application Managerv Geographically Dispersed Parallel Sysplex™ (GDPS®)

For more differences, refer to the following sections.

Component ViewThe IBM Automation Control for z/OS product includes some components of theenterprise versions of System Automation for z/OS and NetView for z/OS. Thissection provides an overview of the components and which of the productsinclude them.


Table 18. Component View of Automation Control

ComponentIBM Automation Controlfor z/OS

System Automation forz/OS NetView for z/OS

Network ManagementConsole

No Yes Yes

NetView TOWERStatements

Yes (Limited to SA-Towerand sub-towers.)

Yes Yes

I/O Operations No Yes n/a

Processor Operations Yes (Limited to local CPC.) Yes n/a

GDPS Support No Yes Yes

Discovery Library Adapter No Yes Yes

End-to-end Automation No Yes n/a

Plexwide OperatorAssistance

Yes (Limited to INGPLEXIPL.)

Yes n/a

Status Display Facility Yes (A maximum number ofthree systems can bepresented by SDF if theybelong to the same sysplex.Only one system can bepresented, if it is amonoplex.)

Yes n/a

SA for IntegratedOperations ManagementAdapter

Yes Yes n/a

Command Facility Yes (Limited to subset ofNetView commands. For acomplete reference, issue theINDEX command on theNetView console. WithAutomation Control, allMVS console commands arestarted through the NetViewcommand MVS except theROUTE command.)

Yes Yes

General AlertingCapabilities

Yes Yes Yes

Command processorsupport (REXX, PIPE)

Yes (Limited to subset of thePIPE commands. For acomplete reference, issue theHELP PIPE command on theNetView console.)

Yes Yes

Command processorsupport (HLL)

No Yes Yes


Table 18. Component View of Automation Control (continued)



NetView Timers Yes (Timer-relatedcommands such as CHRONare not supported in userscripts. However, you canuse Automation Control tospecify timers that areassociated with subsystems(resource of type APL). Issuethe HELP TIMER commandon the NetView console fordetails.)

No No

Automation Table Yes (Limited to generatedAutomation Table withoutoverrides and 3000-characteruser-defined INGMSGUAutomation Table.

Although you cannot usefull functionality of theAUTOTBL command, youcan issue the AUTOTBLcommand with the TESToption to check the syntaxof statements in yourINGMSGU AutomationTable prior to enabling thetable when AutomationControl is restarted.)

Yes Yes

Message Revision Table Yes. Yes Yes

Command Revision Table Yes. Yes Yes

Program-to-ProgramInterface (PPI)

Yes Yes Yes

Stylesheet Yes (Limited to a subset ofstylesheet options. )

Yes Yes

NETLOG Yes Yes Yes

CANZLOG No Yes Yes

SLOGCMDR Log definitiondefaults

No Yes Yes

Joblog monitoring Yes Yes n/a

SA Monitoring Agent Yes Yes n/a

SAPlex wide automationsupport

No Yes n/a

XCF communication in thephysical sysplex

Yes (Limited to 3 systems inthe sysplex.)

Yes Yes

Gateway communicationbetween NetView domains

No Yes Yes

Packet trace No n/a Yes

Connection Management No n/a Yes

Appendix. Automation product comparison 159

Table 18. Component View of Automation Control (continued)



Dynamic VirtualIP-Address Management

No n/a Yes

Discovery Manager andother sysplex management

No n/a Yes

Web Application No n/a Yes

NetView Installation Exits No n/a Yes

Policy services No n/a Yes

XCF support No n/a Yes

TSO Command Server No n/a Yes

UNIX Command Server No n/a Yes

Web Services Gateway No n/a Yes

Canzlog UI and API No n/a Yes

Other IP Management No n/a Yes

Hardware Monitor (NPDA) No n/a Yes

Session Monitor (NLDM) No n/a Yes

Terminal Access Facility Yes (Terminal Access Facilityonly available forAutomation Control’sOMEGAMON Classicsession support.)

n/a Yes

SNA Topology Manager No n/a Yes

4700 Support Facility No n/a Yes

Automated OperationsNetwork

No n/a Yes

Multisystem Manager No n/a Yes

Browse Facility No n/a Yes

Status Monitor No n/a Yes

Resource Object DataManager (RODM)

No n/a Yes

Graphic Monitor FacilityHost System

No n/a Yes

NetView Tivoli EnterpriseMonitoring Agent

No n/a Yes

Subsystem Interface (SSI) Yes n/a Yes

Correlation Engine No n/a Yes

Common Base EventManager

No n/a Yes

Event/Automation Service Yes (Limited to E/ASSupport to emit EIF events.)

n/a Yes

UNIX System Services No n/a Yes

Help Facility Yes n/a Yes

Stylesheet processing(CNMSTRLY)

No n/a Yes


Index

Aaccessibility xiiadapting sample policy 64add-on policy 37adding applications 47adding sample policy 67adding systems 59alert notification for IBM SA z/OS

configuring 19application (APL) resources 39application group (APG) 39application group types 122application groups 122ARM parameter

CNMPSSI start procedurespecifying NetView interface 151

automation agentnaming conventions 95starting 95stopping 96

Automation Controlbenefits 3components 4components view 158deploying 12installing 17introduction 3logging off 98logging on 97planning 11security 33starting for the first time 21verifying your installation 14

automation managernaming conventions 94starting 94stopping 94

automation manager data setssaving into Generation Data

Groups 152automation policy

maintenance 91automation policy management 127autowrap 113

BBase SA z/OS

configuring 17basic groups 122books

See publicationsbuilding policy 88building the configuration files 29bulk update 69

Cclasses 62, 63clone values 41

cloning 59cloning definitions 41Cloud and Smarter Infrastructure

knowledge centers xiCNMKEYS 154CNMPSSI 151CNMSJ010 job 151CNMSTYLE customization 139COLD, WARM, and HOT starts 129command designator, subsystem 152completing the policy replication 88component view 158Configuration Assistant

preparing 18using 17

configuration options file 19configuring SA z/OS 17conventions

typeface xiiicreating a basic PDB 23creating a group 46creating a new policy database 64creating a system 44creating an empty PDB 42creating application groups 55customization 37customization dialog 37, 38, 127

mapping processor hardwareinterfaces 141

customization dialog tutorial 41customization tools 37

Ddata log 154data spaces 151databases 154default availability 117defaults 62defining

PA and PF keys 154deploying IBM Automation Control for

z/OS 12discovery tool 37DISPINFO 107

display panels 108DISPSTAT 106DISPSYS 100distributing policy 90DSIOPF

operator definition 153duplicating applications (method 1) 79duplicating applications (method 2) 85

Eeducation

See Tivoli technical trainingempty policy database 42enterprise (ENT) 39

entry typeshardware interfaces 140

exporting 69exporting sample policy 69

Ggeneration data groups 130getting help 42getting messages 113group (GRP 39groups 126

Hheld messages 113

IIEFUSI exit 151importing sample policy 75infrastructure 99INGAMS 99INGDOPT configuration options file 19INGESAF member 33INGINFO 102

display panels 103INGLIST 102INGNTFY 113INGREQ 120INGVOTE 121inheritance 62, 63install the TSO REXX Function

Package 19installing IBM Automation Control for

z/OS 17

Kkeys, defining 154

Llocked votes 118logon ID 153

Mmainframes supported 133manuals

See publicationsmessage classes 113message display 113message help 113modifying the maximum number of

language processor (REXX)environments for NetView 151

monitoring resources 111


move groups 122

NNetView

configuration 153operator definition 153operator environment 153

Oonline publications

accessing xioperating group members 126operating groups 126operating the processor hardware

interfaces 147operations 93operations infrastructure 99operations overview 93operator ID

defining 153ordering publications xii

PP256BUF operand 152P4000BUF operand 152PA keys, defining 154persistent requests 118PF keys, defining 154planning 11planning worksheet 16policy

building 88policy database 23, 37, 38

creating 64policy updates

interruptions 74PPIOPT operand 152printing the network log 154processor hardware interfaces 133

connectivity and functionality 134deciding which to use 136mapping to customization dialog 141preparing the autotasks 138usage and operation 147

publications xaccessing online xiordering xii

purging your requestINGVOTE 121

RREG (region size) operand 152relationships 125remote commands 153reporting 57request priorities 118resource dependencies 53resource relationships 53resources 39, 101

default availability 117

restarting Automation Controlsummary 15

reviewing policy 79REXX language processor

environments 151RMTCMD command 153roles and responsibilities 11ROLL key 99ROUTECDE operand 152runmodes 125

Ssample policy 37

adapting 64adding 67exporting 69importing 75updating 72

saving of automation manager data setsinto Generation Data Groups 152

SDF 111SECOPTS statements 153security 33

operator definition 153server groups 122service xiiiservice management connect xiiisetting up your systems 75simple data sets 130SMC xiiiSOCNTL 37, 38, 127

managing 130SQ1 operand 152SSI 151start Automation Control for the first

time 21starting a backup 94starting and stopping resources 117starting Automation Control

summary 14starting the automation agent 94starting the customization dialog 22, 41status display facility (SDF) 111stopping and restarting the message

flow 113subsystem command designator 152subsystem interface 151summary of differences to System

Automation for z/OS 157support xiiisymbolic values 59SYS1.PARMLIB member

configuring 19SYS1.PROCLIB member

configuring 19system (SYS) 39system groups (GRP) 78system logger

configuring 19system operations configuration file

(SOCNTL) 37systems operation control file

managing 130

TTivoli technical training xiiitraining, Tivoli technical xiiitypeface conventions xiii

Uupdate SMFPRMxx 19updating sample policy 72

Vverifying

degree of security 153votes 118VTAM connectivity

configuring 19

Zz/OS exit routine 151


IBM®

Product Number: 5698-LSA

Printed in USA

SC34-2697-01

automation control: getting started - ibm · r elated documents. ibm automation control for z/os...

Documents