How to schedule an automatic start or stop of resources in relationship?
search cancel

How to schedule an automatic start or stop of resources in relationship?

book

Article ID: 27854

calendar_today

Updated On:

Products

CMDB for z/OS NetSpy Network Performance NetMaster Network Automation SOLVE NetMaster Network Management for SNA NetMaster Network Management for TCP/IP NetMaster File Transfer Management SOLVE:Operations Automation SOLVE:Access Session Management SOLVE:FTS

Issue/Introduction

Question

How to schedule an automatic start or stop of resources in relationship?

 

 

 

Environment

Release: SLOPEM00200-11.9-SOLVE:Operations-Automation
Component:

Resolution

Answer

Parent resources will override the desired state of their children, so you only need one availability map controlling the parent resource and all the child resources will follow the lead of the parent.

The Status Monitor will indicate when a child resource has had its desired state overridden by a parent resource by displaying a P (for Parental Override) in the Override Flags (Ovr) column. Entering an S beside the child resource will display the Modes and States screen showing the desired state override with a reason of "SCHEDULE OF parent-resource".

During activation the resource(s) will be started from the top down i.e. the parent starts then the first level of children, then the level of children below that etc.

During inactivation the resource(s) will be stopped from the bottom up i.e. the last children are stopped, then the level of children above that, then the level of children above that etc. until the resources are the top are finally shut down.

The description above applies to systems running in Automated mode. In Manual mode the desired states of all the resources will be set to ACTIVE or INACTIVE and their logical states set to ATTENTION. Their Actual State remains unchanged.

 

Example

Resource A has a child of Resource B which has a child of Resource C. If Resource A has an availability map which says it must be INACTIVE at 9pm, then at 9pm Resource A's Desired State will be set to INACTIVE. This will cause Resource B's Desired State to be set to INACTIVE also, via a Parental Override. The same thing happens with Resource C. If the system is running Automated then Resource C will be shut down, then Resource B and finally Resource A. In Manual Mode they will be highlighted (usually in PINK) and have a logical state of ATTENTION.

 

Overriding the scheduled desired state

You can use DSI and DSA to override a resource's scheduled desired state. DSI and DSA only work on the resource against which they were issued i.e. their effects do not propagate through the relationship tree.