The z/OS Agent includes several components. Each component has one (or more) logging mechanisms to aid in testing and troubleshooting. Most messages from each of the components go through the zDC to the zRemote Agent log. Download these messages by requesting the logs in the System Information overview panel of the AppMon Client. Analyzing the zRemote Agent log with the corresponding agent's log gives complete picture of the activity between components for better error determination.
CICS Agent logging
Control the CICS Agent log level either by the DTAX Transaction or by specifying an optional initparm at CICS region startup.
There are two different sets of CICS logs.
One set of messages occur when the DTAX issues the DISABLE and ENABLE command. These messages write to the CICS CSMT Transient Data Queue. View these messages in the CICS job log. DTAX also writes a set of messages to the CEEOUT SYSOUT statement when errors occur in the connection between the zDC and the DTAX transaction. View these messages in the CICS Job log. As long as the DTAX transaction can connect to the zDC, it logs its messages to the zRemote Agent.
The CICS Agent monitoring the CICS transaction activity routes its log messages to the zDC, and subsequently to the zRemote Agent. In this scenario with all the connectivity intact, all the component logs can be gathered for error diagnosis from the AppMon Client System Information overview panel. The log shows if there are any corrupted PurePaths, timeouts, or other errors that may have occurred. You may also see some statistical information in these logs.
If the CICS Agent has difficulties during startup, enable more granular logging for Agent startup by specifying FINE in the
INITPARM for this unique CICS Region. INITPARM details are described here.
IMS Agent logging
There are two sets of IMS Agent logs.
The first set of IMS messages are from the IMS Injection job. These are messages that occur as IMS in injecting its Agent into the IMS Control Region. These messages only appear in the job log of the agent injection job. The second set of IMS messages is from the Agent as it monitors IMS activity. These messages are sent to the zDC which is then routed to the zRemote Agent.
DTLOGLEVEL sets the zDC log level specified in the zDC
SYSIN parameters. View log message output in the zDC joblog. The joblog helps determine errors that may occur during zDC start up or when connecting with the zRemoteAgent. Once the zDC successfully connects to the zRemote Agent, error messages from the zDC, CICS and IMS Agents route to the zRemoteAgent. You can change this log level value dynamically using a zDC modify command.
zLocal Agent logging
DTAGTCMD parameter defined in the zDC
SYSIN parameters sets the zLocal Agent log level for the zDC. The standard Agent
loglevel parameter is used, and this value can not be changed dynamically.
There are two sets of logs created for the zLocal Agent. Both are created in the OMVS file system. One set is a temporary set of logs only valid for the current execution of the zDC, and the location of these logs defaults to the home directory of the zDC user ID. You can override the location by using the
DTCHDIR() parameter defined in the zDC SYSIN. Finsd a sample in member ZDCSYSIN in the sample PDS
&*HLQ* .LZDT``70 0.AZDTSAMP where HLQ is your high-level qualifier.
These log files can not be viewed from within the AppMon Client, but they are seldom used, primarily for issues with agent startup or abends. The zLocal Agent also creates a standard set of Agent logs, one for bootstrapping, and one for the agent itself. These logs are located in the standard Agent log locations on the OMVS file system. You can view these logs from the AppMon Client in the System Information overview panel.
zRemote Agent logging
The zRemote Agent can have two logs if using the Bootstrap agent. The zRemote Agent log level is set in the AppMon Client and can be changed as needed. The zRemote Agent logs are created on the machine where the zRemote Agent is installed, in the standard Agent log locations. You can view the zRemote Agent logs either directly on the machine hosting the zRemote Agent or by requesting them from the AppMon Client in the System Information overview panel.
The zRemote Agent bootstrap log should be similar to a Java Agent bootstrap log, containing the following:
- The initial connect messages.
- Any optional messages about downloading a new agent library.
The actual zRemote Agent log should be similar to a Java Agent log, containing the following messages:
- The actual zRemote Agent log messages once the bootstrap agent loads the agent library.
- Log messages that are sent from all CICS/IMS Agents and the zDC.
- Log messages that are sent from the zLocal Agent.
If the z/OS components communicate correctly, there is no need to look at JOB output of the z/OS components. Access all component logs using the System Information overview pane in the AppMon Client.