|
|
|
Reason:
CA Mainframe Application Tuner has started monitoring the JOB/STC/TSU jjjjjjjj. The program name yyyyyyyy is from the EXEC card of the batch job, STC, or logon proc.
Action:
None.
Origin: TNMSMPL
Reason:
The user userid has initiated a monitor that will be recording data into the data set dsname. This message is always preceded by the message TN0101I.
Action:
None.
Origin: TNMSMPL
Reason:
Based on automatic monitoring criteria, the observation rate was changed for the profile pppppppp. This will not affect the accuracy of the unit of work being monitored.
Action:
None.
TNMSMPL
Reason:
Based on automatic monitoring criteria, the initial observation rate for the profile pppppppp was set to ssss. The maximum number of observations to take was specified as nnnnn, and the elapsed time for the monitor was specified as eeeee.
Action:
None.
Origin: TNMSMPL
Reason:
The monitor has started but will be delayed until the delay time expires. The monitor is fully armed and waiting for a fixed interval.
Action:
None.
Origin: TNMSMPL
Reason:
Based on automatic monitoring criteria, the final observation rate for the profile pppppppp was set to ssss. The maximum number of observations to take was specified as nnnnn, and the elapsed time for the monitor was specified as eeeee.
Action:
None.
Origin: TNMTERM
Reason:
A monitor was run in Quality Assurance mode for profile pppppppp. When running in this mode CA Mainframe Application Tuner performs all function normally, but automatically runs the internal sampler trace in record mode and prints statistics related to errors in one of 3 categories in this message.
Action:
None.
Origin: TNMTERM
Reason:
Displayed at the end of each measurement session. This message will display for auditing purposes the amount of ECSA and SRB time CA Mainframe Application Tuner used while measuring the job.
The SRB CPU Time in the OverView screen includes the SRB CPU Time listed here.
Action:
None.
Origin: TNMTERM
Reason:
A deferred monitoring request has been activated.
Action:
The request begins monitoring the target JOB.
Origin: TNMTASK
Reason:
A monitoring request is completed. The TSO user is notified.
Action:
The request is terminated normally.
User response: None.
Origin: TNMTASK
Reason:
The job step specified in the monitor definition has ended before monitoring could be initialized.
Action:
Monitoring is not done for this job step.
For deferred monitors, this may happen if the job step is extremely short in duration. You may require more test data to obtain a meaningful monitoring session. If this was not a deferred monitor, you should start the monitoring earlier in the life of the job step.
Origin: TNMTASK
Reason:
A monitoring request is stopped by the user
Action:
The request is terminated.
Origin: TNMTASK
Reason:
During monitor initialization it was determined that the target job is no longer valid. During initialization the ASCB was assigned to another job before the monitor was activated.
Action:
The request is terminated.
Determine that the job to be monitored is active.
Olrigin: TNMTASK
Reason:
During initialization of the monitor for the profile pppppppp an abend occurred.
Action:
The request is terminated abnormally. Contact Customer Support.
Origin: TNMTASK
Reason:
This message is issued to the TSO user when a monitor request is ended with a status that is not known.
Action:
The monitor request is terminated. Contact Customer Support.
Origin: TNMTASK
Reason:
The monitor data set for profile pppppppp has been filled. No more records could be placed into the data set.
Action:
The monitor request is terminated.
If additional monitor data is required, reallocate the monitor data set with a larger space allocation.
Origin: TNMTASK
Reason:
A monitor request was forced inactive or in some other way terminated. It is possible that the request will be forced inactive by the recovery action of some other error handler.
Action:
The monitor request is terminated. Resubmit the request. If the problem persists, contact Customer Support.
Origin: TNMTASK
Reason:
This message is issued to the TSO user when a monitor request is submitted but cannot immediately start.
Action:
The request is queued waiting for the JOB to start.
Origin: TNMTASK
Reason:
This message is issued to the TSO user when a monitor request is submitted and abends during the data gathering phase.
Action:
The monitor request is terminated. Attempt to determine what happened and resubmit the request. If the problem persists, contact Customer Support.
Origin: TNMTASK
Reason:
This message is issued to the TSO user when a monitor request is submitted and the required 90K of ECSA is not available.
Action:
The monitor request is terminated. Attempt to correct the CSA shortage problem and resubmit the request. If the problem persists, contact Customer Support.
Origin: TNMTASK
Reason:
While allocating the primary control block for a monitor session, it was determined that the control block size could not contain all the data areas and code required to perform the monitoring
Action:
Monitoring is terminated. This may be the result of application of system maintenance that did not SMP apply correctly. Contact Customer Support.
Origin: TNMTASK
Reason:
An abend occurred while monitoring a CICS region. Additional messages are issued that specify the nature of the abend.
Action:
The monitor is terminated. A software record is recorded in the SYS1.LOGREC data set and a dump is created. Contact Customer Support.
Origin: TNMSMP
Reason:
The subtask is still fetching statements from the DB2 catalog even though the monitor session has ended.
The monitor is terminated. Informational message.
No action required. If you wish to stop the monitor, you may do so from the Monitor Status Panel. If you cancel the monitor while CA Mainframe Application Tuner is still resolving the DB2 statements, some DB2 information might be missing.
Origin: TNMSSQL
Reason:
The subtask for obtaining statements from the DB2 catalog could not be initialized because TUNPARM member TUNDB2xx did not contain a DB2Vxxx for this version of DB2. This entry defines the DSNLOAD library to use when calling the CAF interface.
Action:
The monitor continues but no static SQL will be explained and the SQL displayed will be obtained from DB2 internal control blocks.
Supply the correct DB2Vxxx= entry for this version of DB2. For example: DB2V810=SYS2.DB2V810.SDSNLOAD
Origin: TNMISQL
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |