|
|
This section contains the following topics:
Reason:
This message is issued by IN25FSYM, indicating that dynamic allocation for SRVPRINT DD has failed. Logging activities is disabled. This message is usually followed by IBM IKJ5635 message providing the dynamic allocation text unit that failed.
Action:
Determine and correct the cause for failure then retry the action.
Reason:
This message is issued by IN25FSYM. The hour and minute of the timestamp found in the symbolic does not match the timestamp provided by the caller for the same symbolic. Requested action is not performed.
Action:
Provide the correct timestamp value and try the action again.
Reason:
This message is issued by IN25FSYM. User did not provide one or more PROTSYM data set names to perform symbolic search. Requested action is not performed.
Action:
Provide at least one or up to a maximum of eight PROTSYM fully qualified data set names to be used for symbolic search.
Reason:
This message is issued by IN25FSYM. Dynamic allocation of data set with nnnnnnnn DD name has failed. Return code from Dynamic Allocation is rr and the reason code is ssssssss.
Action:
Use the return code and reason code to determine the cause of the failure. Correct the error and retry the action.
Reason:
This message is issued by IN25FSYM. Dynamic unallocation of dddddddd DD name has failed. The Dynamic Unallocation return code is rr and reason code is ssssssss.
Action:
Use the return code and reason code to determine the cause of the failure. Correct the error and retry the action. If the error persists call CA Technical Support.
Reason:
This message is issued by IN25FSYM. Loading of program named pppppppp has failed. The return code is rr.
Action:
Make sure that the data set containing the pppppppp program is in the LINKLIST or defined in the STEPLIB DD.
Reason:
This message is issued by IN25FSYM. Routine named rrrrrrrr has failed with a return code of rr. This message is usually associated with IN25SAPI and rrrrrrrr is the failed SAPI function.
Action:
Determine the error and retry the request.
Reason:
This message is issued by IN25FSYM. The data set name provided in LD@DSSDSN is invalid.
Action:
LD@DSSDSN should contain a valid DD name to be used for DSS logging. It is usually specified as DSSLOG. Correct the DD name and retry the action.
Reason:
SRVPRINT log file not opened. Endevor activity log disabled.
Action:
We recommend that //SRVPRINT DD SYSOUT=* be defined in the job’s JCL so that relevant error can be captured to assist in problem analysis. This would avoid the need to recreate the error.
Reason:
Dynamic allocation of activity log has failed. This message is usually followed by IBM IKJ5635 message providing the dynamic allocation text unit that failed.
Action:
Determine and correct the cause of the error and retry the request.
Reason:
IN25NDVR encountered an error trying to LOAD IN25DALC. Endevor List request will not be performed.
Action:
Make sure that the data set containing IN25DALC load module is either defined in the LINKLIST or is defined in the STEPLIB concatenation.
Reason:
IN25NDVR cannot LOAD the Endevor API. Endevor List request will not be performed.
Action:
Make sure that Endevor AUTHLIB and CONLIB data sets are either defined in the LINKLIST or defined in the job’s JCL.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |