Previous Topic: Stop the CA Chorus ComponentsNext Topic: Stop CA Chorus Infrastructure Management for Networks and Systems Components

Managing CA Chorus Components › How to Stop CA Chorus › Stop CA Chorus for DB2 Database Management

Stop CA Chorus for DB2 Database Management

You can stop and restart each of the CA Database Management Solutions for DB2 for z/OS and CA Chorus for DB2 Database Management independently. If you stop Xmanager, Xnet, or both, the CA Chorus agents in your other products can no longer communicate and provide service to CA Chorus users until Xmanager, Xnet, or both are restarted.

If you are performing a complete shutdown of the products, the following procedure provides a logical order for the shutdown. This logical order can be useful if you are automating a shutdown procedure for the products. Each product can be stopped independent of the other products. If you must shut down a single product, go to that step and issue the appropriate shutdown command. When the product is restarted, it automatically rejoins your network of CA Chorus agents.

Follow these steps:

  1. Stop the Object Framework Services agent (OFA) by entering the following console command: 
    P OFAPROC

    Message ETJOF002I: OFA SHUTDOWN COMPLETE is logged.

  2. Stop CA Insight DPM data collectors by entering the following console command for each DB2 subsystem: 
    P db2ssidDC
    db2ssid

    Identifies the DB2 subsystem ID.

    Message IEF404I ssidDB2 - ENDED - TIME=hh:mm:ss is logged.

  3. Stop the CA Insight DPM program call owner: 
    P IDB2PC

    Message IEF404I IDB2PC - ENDED - TIME=hh:mm:ss is logged.

  4. Stop Xnet by entering the following console command: 
    P PXNPROC

    Message IEF404I PXNPROC - ENDED - TIME=hh:mm:ss is logged.

  5. Stop Xmanager: 
    P PTXMAN

    Message IEF404I PTXMAN - ENDED - TIME=hh:mm:ss is logged.