How can I ensure the Defender for z/OS agent will startup even if the associated Db2 subsystem is down

Version 1
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    BMC AMI Defender for z/OS


    COMPONENT:

    BMC AMI Defender for z/OS


    APPLIES TO:

    BMC AMI Defender for z/OS, versions v5.8.3 and v5.8.04 (versions PRIOR to v5.9.01)



    QUESTION:

    How can I ensure the Defender for z/OS agent will startup even if the associated Db2 subsystem is down?


    ANSWER:

     

    There is an optional sub-parameter on the START parameter that controls this behavior. The default is to FAIL, that is the AMI Defender STC will shut down if the associated Db2 subsystem is not available. If you change this to ACCEPT, it will carry on with its start up without Db2.  See this example and the explanations from the documentation below:
     
    START(NOTREADY( WAIT(3) ACCEPT))  +
     
    This tells the Agent to wait and retry if DB2 is not connectable and accept the unavailable Db2 if it is not ready within the time interval specified.  Per the reference manual:
     
    STA (START)
    Specifies that zDefender is to interface with DB2 to start the DB2 IFCID traces indicated in IFCIDs(). The indicated traces will be started only for the DB2 subsystems in the SSIDs parameter. zDefender will wait as indicated for each specified DB2 subsystem to become active. You may specify STArt without any subparameters; doing so is equivalent to coding
    START(CLASS(32) CON() REC('-') NOTREADY(WAIT(5) FAIL))
    STArt requires one of the following privileges or authorities:
    · TRACE privilege
    · SQLADM authority
    · System DBADM authority
    · SYSOPR authority
    · SYSCTRL authority
    · SYSADM authority
    · SECADM authority.
     
    NOTR (NOTREADY)
    Specifies the action that zDefender is to take if one or more of the specified DB2 subsystems is not ready to accept START TRACE commands. Specify one or both of the parameters described below. If you omit NOTReady it defaults to WAIT(5) FAIL. Note that the NOTReady specification applies only to initial zDefender startup and has no effect on any MODIFY SET(DB2(START)) commands. (See The Modify or F Command in “CorreLog zDefender for z/OS Installation and Operation.”)
     
    WAIT(minutes)
    Specifies how long zDefender is to wait (in the aggregate) for all of the specified DB2 subsystems to become ready. Specify a number of minutes between 0 and 1440 inclusive. If you omit WAIT it defaults to five minutes.
     
    ACC (ACCEPT)
    FAIL

    Specifies the action that zDefender is to take if one or more of the specified DB2 subsystems is still not ready after waiting for the interval specified by WAIT. If you omit ACCEPT or FAIL it defaults to FAIL, that is, zDefender terminates with an error.
     
     
    Please be aware that this is only valid for v5.8.3 and v5.8.04 releases.

     


    Article Number:

    000175083


    Article Type:

    FAQ/Procedural



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles