|
|
|
Reason:
During initialization, CA Mainframe Application Tuner allocates the LINKLIST libraries to permit CSECT resolution for modules area loaded from LINKLIST libraries. CA Mainframe Application Tuner is currently creating the list of libraries. The creation time varies depending on the size of the LINKLIST.
Action:
None.
Origin: TNSLNKA
Reason:
During initialization, CA Mainframe Application Tuner allocates the LPALIST libraries to permit CSECT resolution for modules area loaded from those libraries. CA Mainframe Application Tuner is currently creating the LPALIST libraries. The creation time varies depending on the size of the LPALIST.
Action:
None.
Origin: TNSLNKA
Reason:
During server space initialization, CA Mainframe Application Tuner allocates the libraries in the linklist for its csect resolution function. A data set name found in the linklist table was not catalogued. The name of that data set immediately follows this message.
Action:
CA Mainframe Application Tuner skips this data set.
If the linklist data set is to be used by CA Mainframe Application Tuner, ensure it is catalogued and restart the server address space.
Origin: TNSLNKA
Reason:
During server space initialization, CA Mainframe Application Tuner allocates the libraries in the linklist for its csect resolution function. A data set name found in the linklist table was not found on the volume specified by the system catalog. The name of that data set immediately follows this message.
Action:
CA Mainframe Application Tuner skips this data set.
If the linklist data set is to be used by CA Mainframe Application Tuner, ensure it is located on the same volume specified by the system catalog and restart the server address space.
Origin: TNSLNKA
During server space initialization, CA Mainframe Application Tuner allocates the libraries in the linklist for its csect resolution function. A data set name found in the linklist table could not be allocated using the DYNALLOC SVC. The name of that data set immediately follows this message.
Action:
CA Mainframe Application Tuner skips this data set. If this problem persists, contact Customer Support.
Origin: TNSLNKA
Reason:
During server initialization, a call to the IBM® Binder API which issues GETMAIN for buffer type bbbb from subpool 229, failed with return code rrrrrrrr.
Action:
The server continues to initialize; however, monitor requests will not be able to resolve CSECTs residing in LPA. Contact Customer Support.
Origin: TNSLPAP
Reason:
During server initialization, a call to the IBM Binder API STARTD request failed with return code rrrrrrrr and reason code ssssssss. These codes are documented in IBM manual MVS Program Management: Advanced Facilities.
Action:
The server continues to initialize; however, monitor requests will not be able to resolve CSECTs residing in LPA. This message will be followed by TN1112E indicating the data set name and DD name being processed at the time of the failure. Contact Customer Support.
Origin: TNSLPAP
Reason:
During server initialization, a call to the IBM Binder API CREATEW request failed with return code rrrrrrrr and reason code ssssssss. These codes are documented in IBM manual MVS Program Management: Advanced Facilities.
Action:
The server continues to initialize; however, monitor requests will not be able to resolve CSECTs residing in LPA.
This message will be followed by TN1112E indicating the data set name and DD name being processed at the time of the failure. Contact Customer Support.
Origin: TNSLPAP
Reason:
During server initialization, a call to the IBM Binder API failed resulting in message TN1110E or TN1111E. This message follows indicating the data set being processed at the time of the failure.
Action:
The server continues to initialize; however, monitor requests will not be able to resolve CSECTs residing in LPA. Contact Customer Support.
Origin: TNSLPAP
Reason:
During server initialization, a call to the IBM Binder API INCLUDE request failed with return code rrrrrrrr and reason code ssssssss. These codes are documented in IBM manual MVS Program Management: Advanced Facilities.
Action:
The server continues to initialize; however, monitor requests will not be able to resolve CSECTs residing in LPA. This message will be followed by TN1116E indicating the data set, member, and DD name being processed at the time of the failure. Contact Customer Support.
Origin: TNSPDSE
Reason:
During server initialization, a call to the IBM Binder API GETN request failed with return code rrrrrrrr and reason code ssssssss. These codes are documented in IBM manual MVS Program Management: Advanced Facilities.
Action:
The server continues to initialize; however, monitor requests will not be able to resolve CSECTs residing in LPA. This message will be followed by TN1116E indicating the data set, member, and DD name being processed at the time of the failure. Contact Customer Support.
Origin: TNSPDSE
Reason:
During server initialization, a call to the IBM Binder API GETD request failed with return code rrrrrrrr and reason code ssssssss. These codes are documented in IBM manual MVS Program Management: Advanced Facilities.
Action:
The server continues to initialize; however, monitor requests will not be able to resolve CSECTs residing in LPA. This message will be followed by TN1116E indicating the data set, member, and DD name being processed at the time of the failure. Contact Customer Support.
Origin: TNSPDSE
Reason:
During server initialization, a call to the IBM Binder API failed resulting in message TN1113E, TN1114E, or TN1115E. This message follows indicating the data set being processed at the time of the failure.
Action:
The server continues to initialize; however, monitor requests will not be able to resolve CSECTs residing in LPA. Contact Customer Support.
Origin TNSPDSE
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |