|
|
|
Reason:
This message is issued inside of the job that is being measured.
Action:
Informational.
Origin: TNEISRB
Reason:
During start up of a monitor facility, it was determined that the monitor data set has no space allocated to record the samples.
Action:
The monitor request is cancelled. Check the space allocated to the monitor data set and reinvoke the monitor.
Origin: TNMOMON
Reason:
During initialization of the monitor facility, an open for the monitor data set returned without opening the data set.
Action:
The monitor request is cancelled.
Check to see if a security failure occurred for the monitor data set.
Origin: TNMOMON
Reason:
During initialization of the monitor facility, an open for the monitor data set returned without opening the data set.
Action:
The monitor request is cancelled. Check to see if a security failure occurred for the monitor data set.
Origin: TNMTASK
Reason:
During start up of a monitor facility, it was determined that the monitor data set has no space allocated to record the samples.
Action:
The monitor request is cancelled. Check the space allocated to the monitor data set and reinvoke the monitor.
Origin: TNMBTND
Reason:
The facility that resolves module addresses into CSECTs has abended. There may be a dump for that reason.
Action:
The monitor continues but the CSECT resolution may not be operational.
Resolve the problem that caused the CSECT resolution facility to abend and reinvoke the monitor. If the problem persists, contact Customer Support.
Origin: TNMCESD
Reason:
While reading the module mmmmmmm during the CSECT resolution phase of the monitoring, CA Mainframe Application Tuner found that the module did not have the required record types. CA Mainframe Application Tuner abandons the module and continues.
Action:
The monitor continues but the CSECT resolution may not be operational. If the problem persists, contact Customer Support.
Origin: TNMCSCT
Reason:
The routine that resolves csect names has run out of space in the table it uses to keep track of unique load module names. This is probably because the job step being monitored has a very large number of unique load modules associated with it.
Action:
The csect resolution function is terminated. Monitoring continues but some load modules may not be resolved to the csect level. Contact Customer Support.
Origin: TNMCESD
Reason:
A problem occurred with the monitor data set that caused the DCB abend exit to be entered
Action:
If the abend is an x37 then CA Mainframe Application Tuner recovers from the abend, closes the monitor data set, and terminates the monitor.
Reallocate the monitor data set with more space before the next execution of the monitor request.
Origin: TNMOMON
Reason:
The appropriate recovery process for the problem encountered has completed.
Action:
None.
Origin: TNMOMON
Reason:
While writing data to the monitor data set, an overflow condition was encountered by the DCB error exit. The monitor data set is full.
Action:
The monitor data set is closed and an indicator is set to show that some monitor data was not collected. The data in the data set is valid and may be analyzed with reasonable results.
Use the Profile option (Option 0 on the main menu) to specify a larger primary and/or secondary allocation for the monitor data sets.
If this problem persists, contact Customer Support.
Origin: TNMOMON
Reason:
This message is sent to the submitter of the monitor request to indicate that the monitor data set has run out of space. The message is sent using the TSO SEND command.
Action:
The monitor data set is closed and an indicator is set to show that some monitor data was not collected. The data in the data set is valid and may be analyzed with reasonable results.
Use the Profile option (Option 0 on the main menu) to specify a larger primary and/or secondary allocation for the monitor data sets.
If this problem persists, contact Customer Support.
Origin: TNMWRIT
Reason:
The task that provides the Call Attach Facility (CAF) interface to DB2 has abended. This facility provides CA MAT access to the DB2 catalogs for a variety of functions. A dump is available.
Action:
Monitoring continues, but resolution of SQL statements and other functions requiring access to the DB2 catalog will not be available. The data in the data set is valid and may be analyzed with reasonable results.
If this problem persists, contact Customer Support.
Origin: TNMCAFE
Reason:
The task that provides the Call Attach Facility (CAF) interface to DB2 could not LOAD the interface routines required to access DB2. CA MAT uses LOAD with the ERRET keyword to trap any abend issued by LOAD. This abend is in R1 and the reason code for the abend is in R15. See the proper z/OS manual for more information. The contents of R1 and R15 are displayed in hexadecimal format.
Action:
Monitoring continues, but resolution of SQL statements and other functions requiring access to the DB2 catalog will not be available. The data in the data set is valid and may be analyzed with reasonable results.
The member TUNDB2xx in the data set pointed to by the TUNPARM DD-statement in the Server JCL provides a list of load libraries containing DB2 modules. It is likely that the data set name related to this release of DB2 does not contain these modules. Correct the data set name.
If this problem persists, contact Customer Support.
Origin: TNMCAFE
Reason:
The task that provides the Call Attach Facility (CAF) interface to DB2 could not obtain a connection to DB2. This facility provides CA Mainframe Application Tuner access to the DB2 catalogs for a variety of functions.
Action:
Monitoring continues, but resolution of SQL statements and other functions requiring access to the DB2 catalog will not be available. The data in the data set is valid and may be analyzed with reasonable results.
If this problem persists, contact Customer Support.
Origin: TNMCAFE
Reason:
The task that provides the Call Attach Facility (CAF) interface to DB2 obtained other than a RC=00 from the OPEN call. This facility provides access to the DB2 catalogs for a variety of functions.
Action:
Monitoring continues, but resolution of SQL statements and other functions requiring access to the DB2 catalog will not be available. The data in the data set is valid and may be analyzed with reasonable results.
If this problem persists, contact Customer Support.
Origin: TNMCAFE
Reason:
CA Mainframe Application Tuner is unable to open the LINKLIST concatenation group SYSnnnnn possibly due to problems associated with one or more of the data sets in that group.
Action:
Monitoring continues, but CA Mainframe Application Tuner bypasses the OPEN for this DCB group. CSECT resolution is not available for load modules located in any of the libraries that are part of this DCB group.
Contact Customer Support.
Origin: TNMLNKA
Reason:
CA Mainframe Application Tuner is unable to open the LPALIST concatenation group SYSnnnnn possibly due to problems associated with one or more of the data sets in that group.
Action:
Monitoring continues, but CA Mainframe Application Tuner bypasses the OPEN for this DCB group. CSECT resolution is not available for load modules located in any of the libraries that are part of this DCB group.
Contact Customer Support.
Origin: TNMLNKA
Reason:
The task that provides the Call Attach Facility (CAF) interface to DB2 has timed out, it is waiting/running in DB2, this user abend allows us to regain control if we do not get a response from DB2 in 90 seconds. A logrec is available.
Action:
Monitoring continues, but resolution of SQL statements will not be accessed from the DB2 catalog, instead, SQL statements will be obtained from the DB2 SPA control block.
Add parm CAFSTALL=nn to TUNSSP00, the default time out value is 90. If this problem persists, contact Customer Support.
Origin: TNMTERM
Reason:
The task that provides the Call Attach Facility (CAF) interface to DB2 returned back a return code of 8 and a reason code of x'00F30034' indicating that the GRANT EXECUTE for the CA Mainframe Application Tuner provided plan of xxx in the message was not performed for the DB2 system zzz.
If this message is issued, then there is a possibility that some of the DB2 statements will be incorrect since CA Mainframe Application Tuner must obtain that information from volatile control blocks within DB2
Action:
Monitoring continues, but resolution of SQL statements and other functions requiring access to the DB2 catalog will not be available. The data in the data set is valid and may be analyzed with reasonable results.
Review the installation chapters for DB2 and make sure CA Mainframe Application Tuner has been granted access to the plan for the indicated system.
If this problem persists, contact Customer Support.
Origin: TNMCAFE
Reason:
There was an error executing plan TRInnDB2 (where nn is the version number of CA Mainframe Application Tuner) to obtain the SQL statement source from the DB2 catalog. The messages following the above prefix are returned by the DB2 message utility DSNTIAR and indicate the nature of the failure
Action:
Monitoring continues, but resolution of SQL statements and other functions requiring access to the DB2 catalog will not be available. The data in the data set is valid and may be analyzed with reasonable results.
Review the installation chapters for DB2 and make sure CA Mainframe Application Tuner has been granted access to the plan for the indicated system.
If this problem persists, contact Customer Support.
Origin: TNMADB2
Reason:
There was an error when trying to issue an EXPLAIN for the profile listed above. The messages following the above prefix are returned by the DB2 message utility DSNTIAR and indicate the nature of the failure
Action:
Monitoring continues, but resolution of SQL statements and other functions requiring access to the DB2 catalog will not be available. The data in the data set is valid and may be analyzed with reasonable results.
Review the installation chapters for DB2 and make sure CA Mainframe Application Tuner has been granted access to the plan for the indicated system.
If this problem persists, contact Customer Support.
Origin: TNMEXPL
Reason:
The active sampling of the target job is finished, but CA Mainframe Application Tuner is gathering DB2 and SQL information. This can result in a completion status of 100%, yet the monitor status remains Active.
Action:
None. When CA Mainframe Application Tuner completes gathering the required information, the status will be updated to Completed.
Origin: TNMCAFE
Reason:
The task that provides the Call Attach Facility (CAF) interface to DB2 has timed out, it is waiting/running in DB2. An internal user abend is generated permitting CA Mainframe Application Tuner to regain control if DB2 does not respond in the time frame specified by the CAFSTALL parameter in TUNSSPxx.
Action:
Monitoring continues, but resolution of SQL statements will not be accessed from the DB2 catalog, instead, SQL statements will be obtained from the DB2 SPA control block.
Add or increase parm CAFSTALL=nn in TUNSSPxx, the default time out value is 90. If this problem persists, contact Customer Support.
Origin: TNMCAFE
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |