Automating the STC Startup

We recommend that you configure your system so that the CA 7 Data Provider for AAI primary STC starts automatically at IPL. Make sure that CA7 is active before CA 7 Data Provider for AAI starts up. To ensure that CA7 and the CA 7 Data Provider for AAI are synchronous, CA7 must be active at all times.

We also recommend that you automate the shutdown of the CA 7 Data Provider for AAI using the secondary STC based on CAI7JCL member AI7Ccode. Alternatively, you can shut id down through the ISPF interface.

This page includes the following:

Console Messages

When you automate the STC startup, the CA 7 Data Provider for AAI issues console messages that help you manage and monitor the primary STC. These messages consist of the following:

<+message ID><instance code of the CA 7 Data Provider for AAI><message text>

Example:

+AI7.CN07E: YYYX CA 7 Server for AAI has FAILED on DD MMM YYYY at HH:MM:SS

Where YYYX is the instance code of the CA 7 Data Provider for AAI that issued the message

All console messages are issued using the TSO SEND command. The message ID has a “+” prefix.

Note:

The CA 7 Data Provider for AAI main processing runs under OMVS. It uses child processes to perform various z/OS-related activities, including the TSO SEND function to generate console messages.

Console messages that are generated from the CA 7 Data Provider for AAI are not issued from the main task STC name, but they are associated with a BPXAS task name operating as a child process. Take this information into account when you automate the capture of these console messages.

Server Start Up

The following console message confirms that the server started successfully:

+AI7.CN01I: YYYX CA 7 Server for AAI is now active on DD MMM YYYY at HH:MM:SS

If an error in the configuration settings is identified during start up, the CA 7 Data Provider for AAI terminates with the following console message:

+AI7.CN07E: YYYX CA 7 Server for AAI has FAILED on DD MMM YYYY at HH:MM:SS

Server Shutdown

When the CA 7 Data Provider for AAI primary STC is shut down, either automatically or manually through a Command Request, the following console message confirms that the server was shut down successfully:

+AI7.CN06I: YYYX CA 7 Server for AAI terminated on DD MMM YYYY at HH:MM:SS

Server Errors

The CA 7 Data Provider for AAI is extremely robust, so it is very unlikely that it fails. However, it traps certain error conditions and attempts to work around these. When doing so, it continues processing while trying to recover any data that has not been delivered.

The errors that can occur and that are trapped are:

  • Various FTP/SFTP connection failures when trying to deliver data

  • Failure during Event data report creation

  • Failure to start the separate Definition Data Delivery “child” process

In all of these cases, various retry attempts are made. If the attempts do not resolve the problem, processing will still continue.

To make sure that this errors are brought to you attention so that they can be investigated, the CA 7 Data Provider for AAI issues various console messages that can be captured automatically:

+AI7.CN02W: YYYX CA 7 Server for AAI Event Data Delivery failure - Continuing

+AI7.CN03E: YYYX CA 7 Server for AAI Event Data generation failure - Continuing

+AI7.CN04E: YYYX CA 7 Server for AAI Definition Data Spawn failure - Skipping

+AI7.CN05E: YYYX Definition Data Delivery Request failure - Review LOGS

Should a report generation or data delivery failure occur in the Asynchronous Definition Data Delivery (ADDD) child process, it will issue a console message highlighting the failure. This happens although the CA 7 Data Provider for AAI primary STC will perform a number of retry attempts to run the “Child” process again. The message console in such failure is as follows:

+AID.CN01E: YYYX Definition Data Delivery failed on DD MMM YYYY at HH:MM:SS