Using System State Manager › SSM Global Events › DELETE Event Example

DELETE Event Example

The following example shows how the DELETE event can execute a request rule called SSMDELGX, which is passed in the name and table of the deleted resource. The rule checks whether that deleted resource is a prerequisite for another resource in the table and issues a warning message.

SSMV2_GBLEXIT_TBL ----------- TABLE DATA EDITOR ----------- COLUMNS 00001 00124
Command ===> Scroll ===> PAGE
COL--> EXIT_EVENT    EXIT_RES_TABLE    EXIT_RES_NAME    EXIT_ACTION
*********************************TOP OF DATA **********************************
000001  DELETE                            RULE("SSMDELGX &SSM!TABLE,&SSM!NAME")
********************************BOTTOM OF DATA*********************************
)REQ SSMDELGX
)PROC

/********************************************************************/
/* Throw away rule name and parse input parameters                  */
/********************************************************************/
PARSE UPPER ARG . parms
PARSE VAR parms xtable ',' xname

/********************************************************************/
/* See if deleted resource is a prereq for another resource in this */
/* table                                                            */
/********************************************************************/
ADDRESS SQL
"SELECT NAME FROM "xtable" WHERE PREREQ IN ('"xname"')" 

/********************************************************************/
/* If a row is returned then issue a warning message                */
/********************************************************************/
IF name.0 > 0 
THEN DO
   msgtext = 'Resource 'xname' was deleted from table 'xtable' and is',
   'a prereq for 'name.1
   ADDRESS WTO "TEXT('"msgtext"') ROUTE(1)"
END  /* THEN DO */
)END

Non-standard and Complex Resource Management

Standard resources managed within the SSM component start through a traditional z/OS START command initialize, and then stay active until it is desired to stop them or the system is being IPLd. Additionally, these standard resources produce specific WTO's that indicate their true current state, such as when it reached its initialization or UP state or when it is being STOPPED. Within SSM, it may be desired to manage the state of resources that do not adhere to the characteristics of these standard types of resources. This section describes the actions needed to manage various non-standard resources within SSM and identify supporting sample rules and programs in which more information can be found.

Manage USS Deamon Server Processes

USS daemon server processes such as INETD and FTP can be managed within SSM by implementing logic as described within the SSMUSS1 sample OPS/REXX program. This sample OPS/REXX program located in the opsmvshlq.SAMPLE.REXX dsn, is intended to demonstrate an automated technique that can be used within the System State Manager component to monitor and control specific USS processes. The default logic of this sample program is intended to handle USS daemon server processes specifically INETD and/or FTP, but can be used to managing any USS process that behaves in the same manner. Refer to this sample program for complete logic details as well as implementation steps needed to manage these types of resources.