|
|
|
Reason:
The monitor request has a user exit associated with it. When the load was attempted from the TRLINK library, the module eeeeeeee was not found. The profile name is indicated as pppppppp.
Action:
The monitor request continues without the user exit.
Determine why the user exit is not available for loading from TRLINK. Correct the problem and resubmit the request. The exit may not have been link edited into the library.
Origin: TNMIUEX
Reason:
The monitor request has a user exit associated with it. When CA Mainframe Application Tuner attempted to relocate the user exit into extended CSA, a conditional getmain issued for the ECSA failed because not enough ECSA storage was available. The profile name is indicated by pppppppp.
Action:
The monitor request continues without the user exit.
Determine why extended common storage was not available to relocate the routine. Correct the problem and resubmit the request.
Origin: TNMIUEX
Reason:
The monitor request has a user exit eeeeeeee located in common storage. The profile name is indicated by pppppppp.
Action:
The monitor request continues.
Origin: TNMIUEX
Reason:
The monitoring exit TUNADABS was not located or an error was returned from a call to TUNADABS.
|
RC |
RS |
Reason |
|
04 |
04 |
Unable to load TUNADABS |
|
04 |
08 |
Bad return from TUNADABS |
The Adabas user exit becomes inactive. Statistics will still be gathered, but the details offered by the user exit will not be present.
Action:
The monitor request continues.
Origin: TNUADABX, TNUADAAX, TNUADABC, TNUADAAC
Reason:
The monitoring exit TUNADABS has been activated for this address space. The user exit will produce data that is used by a corresponding monitor.
Action:
The address space continues operation.
Origin: TUNADABS
Reason:
The JOB/STC/TSU was never found for a deferred monitor request. The profile name is indicated by pppppppp.
Action:
The request is cancelled.
Resubmit the request.
Origin: TNMINIT, TNMLJOB, TNMWJOB
Reason:
The JOB/STC/TSU for the named profile was never found. The profile name is indicated by pppppppp.
Action:
The monitor request is terminated. The user that submitted the request is notified of the termination.
Determine why the monitor never saw the JOB/STC/TSU and resubmit the request.
Origin: TNMINIT, TNMLJOB, TNMSCHD, TNMWJOB
Reason:
The JOB/STC/TSU for the named profile was found and while trying to update the entry in the monitor persistence table, an error occurred. The profile name is indicated by pppppppp.
Action:
The monitor request is terminated. The user that submitted the request is notified of the termination.
Determine why the request could not be updated in the monitor persistence table and resubmit the request.
Origin: TNMLJOB
Reason:
The monitor request for the specified Profile was cancelled by an administrator. The profile name is indicated by pppppppp.
Action:
The monitor request is cancelled. Resubmit the monitor request if the job is to be monitored.
Origin: TNMLJOB, TNMWJOB
Reason:
The CICS | IMS monitor routine was not located for the monitor specified by pppppppp. CICS may not be initialized to a point where the DFHCSA is completely built, causing the release to be unavailable. In addition, IMS may not be fully initialized in the region either.
Action:
The monitor request will continue but CICS | IMS transaction monitoring will not take place.
Resubmit the monitor request after CICS | IMS is fully initialized.
Origin: TNMICIC, TNMIIMS
Reason:
During the initialization of a monitor, a section of extended common storage is reserved to record the monitor data and maintain information. This area is freed at monitor termination.
Action:
Operation continues.
Origin: TNMINIT
Reason:
While attempting to load the supporting load modules for either CICS or IMS monitoring, CA Mainframe Application Tuner detected that no more ECSA was available. CA Mainframe Application Tuner was not able to load these modules.
Action:
Monitoring is terminated and will not be possible until the ECSA shortage condition is corrected.
Determine why there is a shortage of ECSA storage in your system and correct that problem before starting more monitors with CA Mainframe Application Tuner.
If this problem persists, contact Customer Support.
Origin: TNMICIS, TNMIIMS
Reason:
During the initialization of the monitor, a section of extended common storage is reserved to record the CICS | IMS | DB2 data collected. CICS | IMS | DB2 Additionally, the reserved area is used to contain the CICS | IMS | DB2 monitoring code. The packet supports the release of CICS | IMS | DB2 specified by the field rr. This area is freed when that monitor is terminated.
Action:
Operation continues.
Origin: TNMICIC, TNMIIMS
Reason:
During the start up of a monitor, an initialization SRB is scheduled into the target address space to gather required information. The initialization SRB has abended.
Action:
The Request is terminated.
Contact Customer Support.
Origin: TNMSCHD
Reason:
During the start up of a monitor, an initialization SRB is scheduled into the target address space to gather required information. The initialization SRB abended. CA Mainframe Application Tuner requests an SDUMP to a SYS1.DUMPnn data set. Additionally, a record of the problem is recorded to SYS1.LOGREC.
Action:
The Request is terminated. Contact Customer Support.
Origin: TNMINIT, TNMIDSO
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |