|
|
|
Reason:
A time value entered in the Open/ CA Mainframe Application Tuner command is not valid.
Action:
The Open/CA Mainframe Application Tuner command is rejected.
Correct the time value in the appropriate keyword and resubmit the request.
Origin: TNOVTIME
Reason:
When invoking the monitor, the schedule associated with the monitor could not be found.
Action:
Monitor is not invoked.
Either remove the schedule definition from the monitor profile or define the missing schedule.
Origin: TNOMIMON
Reason:
A date defined in the schedule is not valid. Must be of the ISO9000 standard of yyyy/mm/dd.
Action:
Monitor is not invoked. Correct the invalid date in the schedule.
Origin: TNOMIMON
Reason:
A time defined in the schedule is not valid. Must be of the form of hh:mm.
Action:
Monitor is not invoked. Correct the invalid time in the schedule.
Origin: TNOMIMON
Reason:
One or more of the scheduling options is not valid.
Action:
Monitor is not invoked.
Review the schedule and resubmit the monitor.
Origin: TNOMIMON
Reason:
An abend was detected in the server. This message is the first in a series of messages and indicate the abend code and associated reason code.
Action:
A SDUMP is taken and the abend is recorded in LOGREC. Contact Customer Support.
Origin: Various places in CA Mainframe Application Tuner.
Reason:
An abend was detected in the server. This message indicates the PSW, Instruction Length, and Interrupt code.
Action:
A SDUMP is taken and the abend is recorded in LOGREC. Contact Customer Support.
Origin: Various places in CA Mainframe Application Tuner.
Reason:
An abend was detected in the server. This message displays the data located at the error PSW location minus 8 bytes for 16 bytes.
Action:
A SDUMP is taken and the abend is recorded in LOGREC. Contact Customer Support.
Origin: Various places in CA Mainframe Application Tuner.
Reason:
An abend was detected in the server. This message displays the program name where the error occurred, its load point (LP), its entry point (EP), and the displacement into the program from the load point where the error occurred.
Action:
A SDUMP is taken and the abend is recorded in LOGREC. Contact Customer Support.
Origin: Various places in CA Mainframe Application Tuner.
Reason:
An abend was detected in the server. This message displays the major program name along with the length of the program and the subpool of storage where the program was loaded into.
Action:
A SDUMP is taken and the abend is recorded in LOGREC. Contact Customer Support.
Origin: Various places in CA Mainframe Application Tuner.
Reason:
An abend was detected in the server. This message displays the contents of general programming registers 0 through 3 at the time of error.
Action:
A SDUMP is taken and the abend is recorded in LOGREC. Contact Customer Support.
Origin: Various places in CA Mainframe Application Tuner.
Reason:
An abend was detected in the server. This message displays the contents of general programming registers 4 through 7 at the time of error.
Action:
A SDUMP is taken and the abend is recorded in LOGREC. Contact Customer Support.
Origin: Various places in CA Mainframe Application Tuner.
Reason:
An abend was detected in the server. This message displays the contents of general programming registers 8 through 11 at the time of error.
Action:
A SDUMP is taken and the abend is recorded in LOGREC. Contact Customer Support.
Origin: Various places in CA Mainframe Application Tuner.
Reason:
An abend was detected in the server. This message displays the contents of general programming registers 12 through 15 at the time of error.
Action:
A SDUMP is taken and the abend is recorded in LOGREC. Contact Customer Support.
Origin: Various places in CA Mainframe Application Tuner.
Reason:
This message is issued during server initialization and indicates the level of security CA Mainframe Application Tuner will be performing. sssss can be NONE, LOCAL, or BOTH.
Action:
None. Information message only.
Origin: TNSSEC
Reason:
This message is issued during server initialization and displays the default logon ID specified in the TUNSSP00 member along with its group. If no group was specified in TUNSSP00, *BLANK will be displayed in the message.
Action:
None. Information message only.
Origin: TNSSEC
Reason:
The RACROUTE return codes indicate that the user listed does not have access to the resource listed. This message is issued by the server.
Action:
Access is denied. Function requested is not performed.
This is an informational message indicating the security parameters used. If the user is supposed to have access to the resource, adjust the security setting appropriately.
Origin: TNOSECV
Reason:
The RACROUTE return codes indicate that the TSO/batch user listed does not have access to the resource listed. This message is issued by the client before the request is sent to the server.
Action:
Access is denied. Function requested is not performed.
This is an informational message indicating the security parameters used. If the user is supposed to have access to the resource, adjust the security setting appropriately.
Origin: TNUSECV
Reason:
This message is issued during server initialization and displays the security class and the security resource prefix to be used. These options are specified in the TUNSSP00 member.
Action:
None. Information message only.
Origin: TNSSEC
Reason:
The server will sign on a user inside of the server while processing a request on behalf of the user. If for some reason, the sign on fails, this message will be displayed along with the return and reason codes from the RACROUTE.
Action:
Access is denied. Function requested is not performed.
Use the RACROUTE return and reason code to determine why the user could not be signed on in the server Started Task.
Origin: TNOSECI
Reason:
The RACROUTE return codes indicate that the user listed does not have access to the resource. This message is issued in conjunction with either message TN5221E or TN5222E, and displays the security facility (CLASS) used along with the actual RACROUTE return and reason codes.
Action:
Access is denied. Function requested is not performed.
This is an informational message indicating the security parameters used. If the user is supposed to have access to the resource, adjust the security setting appropriately.
Origin: TNOSECV
Reason:
During initialization of the Open facility, the required routines were not available. The Open facility cannot be initialized.
Action:
Open initialization is discontinued. Contact Customer Support.
Origin: TNOINIT
Reason:
The RACROUTE return codes indicate that the user listed does not permission to measure the job and job type listed.
Action:
Measurement session is canceled.
This is an informational message indicating the reason why the measurement session was canceled. If you need to measure the address space (job) listed in the message, contact the appropriate security personnel at your company.
Origin: TNMINIT
Reason:
The address space that CA Mainframe Application Tuner was monitoring is an IMS-dependent region that includes the IMS Intercept. When this monitor was finishing up its work, an attempt to stop the IMS Intercept was unsuccessful because the Intercept was still busy.
Action:
None. This is an informational message only. The current monitor terminates successfully; however, it leaves the IMS Intercept active.
This message means that while this monitor was terminating, it attempted and failed to gain the lock needed to terminate the IMS Intercept. If there are multiple monitors taking measurements of the same IMS-dependent region, the last monitor will remove the IMS Intercept.
Origin: TNMTIMS
Reason:
The address space that CA Mainframe Application Tuner was monitoring is an IMS-dependent region that includes the IMS Intercept. When this monitor was finishing up its work, an attempt to stop the IMS Intercept was unsuccessful because the Intercept was still busy.
Action:
None. This is an informational message only. The current monitor terminates successfully; however, it leaves the IMS Intercept active.
This means that at least two different monitors were active at the same time and that this monitor was terminating. When the last monitor completes, the IMS Intercept will be removed from the IMS-dependent region.
Origin: TNMTIMS
Reason:
The ABENDing component was executing in the Mode of mmmmmmmmmm. es rather than mmmmmmmmmm will be Primary, Secondary, Home Space, or Access Register.
Action:
A SDUMP is taken and the abend is recorded in LOGREC. Contact Customer Support.
Origin: Various places in CA Mainframe Application Tuner.
Reason:
An abend was detected in the server. This message displays the contents of the 64-bit general programming registers 0 through 3 at the time of error.
Action:
A SDUMP is taken and the abend is recorded in LOGREC. Contact Customer Support.
Origin: Various places in CA Mainframe Application Tuner.
Reason:
An abend was detected in the server. This message displays the contents of the 64-bit general programming registers 4 through 7 at the time of error.
Action:
A SDUMP is taken and the abend is recorded in LOGREC. Contact Customer Support.
Origin: Various places in CA Mainframe Application Tuner.
Reason:
An abend was detected in the server. This message displays the contents of the 64-bit general programming registers 8 through 11 at the time of error.
Action:
A SDUMP is taken and the abend is recorded in LOGREC. Contact Customer Support.
Origin: Various places in CA Mainframe Application Tuner.
Reason:
An abend was detected in the server. This message displays the contents of the 64-bit general programming registers 12 through 15 at the time of error.
Action:
A SDUMP is taken and the abend is recorded in LOGREC. Contact Customer Support.
Origin: Various places in CA Mainframe Application Tuner.
Reason:
An abend was detected in the server. This message displays the contents of the access registers 0 through 3 at the time of error.
Action:
A SDUMP is taken and the abend is recorded in LOGREC. Contact Customer Support.
Origin: Various places in CA Mainframe Application Tuner.
Reason:
An abend was detected in the server. This message displays the contents of the access registers 4 through 7 at the time of error.
Action:
A SDUMP is taken and the abend is recorded in LOGREC. Contact Customer Support.
Origin: Various places in CA Mainframe Application Tuner.
Reason:
An abend was detected in the server. This message displays the contents of the access registers 8 through 11 at the time of error.
Action:
A SDUMP is taken and the abend is recorded in LOGREC. Contact Customer Support.
Origin: Various places in CA Mainframe Application Tuner.
Reason:
An abend was detected in the server. This message displays the contents of the access registers 12 through 15 at the time of error.
Action:
A SDUMP is taken and the abend is recorded in LOGREC. Contact Customer Support.
Origin: Various places in CA Mainframe Application Tuner.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |