Troubleshooting › Identify and Resolve the Problem › Agent Technology Troubleshooting Checklist

Agent Technology Troubleshooting Checklist

The following items may help you identify the problem.

1. Are z/OS UNIX Services configured and operational?

   You should be able to initiate a USS shell session and issue various UNIX commands to verify that z/OS UNIX Services itself is operating correctly. Pay particular attention to the USS configuration parameters specified in the Installation Guide.

2. Are proper security definitions in place?

   The user that starts the services must belong to the same group as the owning group for the Agent Technology files. The userid should NOT be UID(0).

3. Are all the required processes running?

   Full Agent Technology requires awservices, aws_orb and aws_sadmin processes to be running. From a UNIX shell session or batch job with superuser (su) privileges, issue "ps - ef" (or the z/OS command "D OMVS,A=ALL") and verify that these processes are running.

4. Are your environment variable settings correct?

   You must correctly set a number of environment variables for Agent Technology to operate correctly. Set these environment variables in the $AGENTWORKS_DIR/agentworks.profile file for the Agent Technology processes. A subset of these variables must be available to the Agent Technology started task and to any task that starts an individual Agent. This subset of environment variable settings is located in the file referenced by the ENVFILE DD in the Agent Technology started task JCL. A sample of the ENVFILE is delivered in the Common Services CAW0OPTV library. The ENVFILE data set must have the same DCB attributes as the CAW0OPTV library.

   Note: For more information, see this guide and the Reference Guide.

5. If you are unable to see a mainframe Agent at the manager machine, ensure that the mainframe is classified as an IBM3090 machine. Additionally ensure that the $AGENTWORKS_DIR/services/config/aws_sadmin.cfg file contains the correct SNMP_COMMUNITY and SNMP Trap destination information to direct the traps to the manager machine. Also use the awservices list command to ensure that the Agent is actually running.
6. If both Agent Technology and the individual Agent are running but are not communicating, check if your system is running more than one TCP/IP stack. If so, you should add a SYSTCPD DD to your Agent Technology startup proc and to the Agent's startup proc. Additionally, both agentworks.profile and ENVFILE should contain the following 2 environment variables:

   _BPXK_SETIBMOPT_TRANSPORT=NNNNNN
   RESOLVER_CONFIG="//'VTAM.TCPIP.TCPIP.DATA'"
   

   where NNNNNN specifies the name of the TCP/IP task to connect to, and 'VTAM.TCPIP.TCPIP.DATA' points to the SYSTCPD for the TCP/IP task.