CA Agent Technology Best Practices › Installation Verification

Installation Verification

Once the AT z/OS services have successfully started:

To verify they are running properly

1. Check on the state of the AT Services within OMVS as follows:
   1. Issue the following command:

      .  agentworks.profile
      

      Note: Do not enclose this command in quotes and do not forget the period and space before the actual invocation of the agentworks.profile script.

   2. Issue the following command:

      awservices list
      

   3. The first two lines of the report produced should read:

      RUNNING aws_orb:aws_orb
      RUNNING aws_sadmin:aws_sadmin
      

      Note: You may see several other services and agents, or both, listed in the report with a status of Stopped. This is normal.

2. Check the status of the AT services ports within OMVS as follows:
   1. Issue the following command:

      onetstat
      

   2. The report produced should list all of the AT ports (see the Overview section earlier in this chapter) and show them in the appropriate status, as follows:

      Listen – For all TCP/IP socket ports

      UDP – For the SNMP listener port (normally 6665)

3. Ensure all of the Agent/Services MIBS have been loaded into the Object Store. To do this, within OMVS:
   1. Issue the following command:

      . agentworks.profile
      

   2. Issue the following command:

      agentctrl -m
      

   3. The report produced must show the awsAdmin MIB, as well as at least one other Agent MIB if Agents have been registered. For example:

      <awsAdmin> is registered
      <caiDatacom> is registered
      <caiDb2mvs> is registered
      <caiIDMS> is registered
      <caiSysAgtzOS> is registered
      <caiSysAgtCics> is registered
      <caiSysAgtMqs> is registered
      

4. In you encounter problems, review the log files within the AT zFS (under directory $AGENTWORKS_DIR/services/var/log) to help diagnose the problem. These files are overwritten each time the AT services are started.