This chapter describes the LIB/CCF messages.
The LIB/CCF messages have the following format:
xxxnnnnc message-text
Where:
The component identifier of CCF, CDF (for Library Chain Definition Function messages), or CCV (for LIB/CCF-AllFusion CA‑Vollie batch CCFB100 program messages).
An LIB/CCF message number.
A message type indicator that can be one of the following:
Informational
Warning, but processing continues
User error
Severe error that requires administrator intervention
Unrecoverable LIB/CCF system error that requires Computer Associates Technical Support
The text of the message.
Reason:
Informational.
Action:
None.
Reason:
The Library Interface initialization failed with a return code of nn.
Action:
See the CA Roscoe Extended Facilities for System Programmers Guide for a list of return codes and their meanings.
Reason:
The Library Interface activation failed with a return code of nn.
Action:
See the CA Roscoe Extended Facilities for System Programmers Guide for a list of return codes and their meanings.
Reason:
The specified member could not be found in the CA Roscoe library with this prefix. Processing for this prefix is bypassed. Processing of any other specified prefixes continues.
Action:
Verify that the LIBRCCF=pfx CA Roscoe initialization parameter specifies the correct prefix for the CA Roscoe key where LIB/CCF is installed.
Reason:
The specified member could not be found.
Action:
Verify that the LIBRCCF=pfx CA Roscoe initialization parameter specifies the correct prefix for the CA Roscoe key where LIB/CCF is installed.
Reason:
The specified data set could not be allocated.
Action:
Verify that the correct data set name was specified in LIB/CCF Option 12.0 for the specified prefix and that the data set exists.
Reason:
An error was encountered while processing the specified member. Processing for this prefix is bypassed. Processing of any other specified prefixes continues.
Action:
Examine the LDR for errors using the prefix specified in the message.
Reason:
An error was encountered while processing $CHGT004. Processing for this prefix is bypassed. Processing of any other specified prefixes continues.
Action:
Examine CCF option 12.4 for the prefix specified in the message.
Reason:
Insufficient storage was available for GETMAIN processing.
Action:
Increase the region size and re-execute the CA Roscoe initialization job.
Reason:
Insufficient storage was available for GETMAIN processing for the specified prefix. Processing of subsequent LIBRCCF=pfx initialization parameters is bypassed.
Action:
Increase the region size and re-execute the CA Roscoe initialization job.
Reason:
Informational.
Action:
None.
Reason:
Informational.
Action:
None.
Reason:
Either this function does not support the specified command or you misspelled the command.
Action:
Verify the spelling of the command. Request tutorial help to review valid commands for this function.
Reason:
The FIND command in this function requires that you supply the change request ID as a parameter (for example, FIND WO000934 or FIND 934).
Action:
Supply the change request ID in either of these forms: WOnnnnnn or nnn.
Reason:
The specified change request ID exceeds eight characters in length.
Action:
Supply the change request ID in either of these forms: WOnnnnnn or nnn.
Reason:
The specified change request ID is longer in length than the six digit portion of a CR ID or does not begin with the literals WO.
Action:
Supply the change request ID in either of these forms: WOnnnnnn or nnn.
Reason:
The change request ID is specified in the format WOnnnnnn, but characters in positions 3-8 are not numeric.
Action:
Supply the change request ID in the correct format: WOnnnnnn or nnn.
Reason:
The format of the specified change request ID is invalid.
Action:
Supply the change request ID in either of these forms: WOnnnnnn or nnn.
Reason:
The change request ID is specified in a format less than or equal to six characters in length, but is not all numeric.
Action:
Supply the change request ID in either of these forms: WOnnnnnn or nnn.
Reason:
The command requires the number of the entry as a parameter.
Action:
Enter the number found to the left of the entry.
Reason:
The entry number parameter is not in the allowed range.
Action:
Enter the number found to the left of the entry.
Reason:
The entry number parameter is not numeric.
Action:
Enter the number found to the left of the entry.
Reason:
The specified selection is not available from this selection list.
Action:
Enter a valid selection list command.
Reason:
An attempt to dynamically allocate a data set failed. The message format is: DAIRRC,SVC99RC,DDNAME. Use the Dynamic Allocation Interface Routine (DAIR) return code, the SVC99 return code, and the ddname for problem determination. A panel accompanies this message that provides additional information, such as the data set name.
Action:
Notify the CCF system administrator with the information provided.
Administrator Response: See the IBM SPL: System Macros and Facilities Volume 1 for return code meanings, then correct the cause of the failure.
Reason:
An attempt to dynamically allocate a master file failed. The message format is: DAIRRC,SVC99RC,DDNAME. Use the Dynamic Allocation Interface Routine (DAIR) return code, the SVC99 return code, and the ddname for problem determination. A panel accompanies this message that provides additional information, such as the data set name.
Action:
Notify the CCF system administrator with the information provided.
Administrator Response: See the IBM SPL: System Macros and Facilities Volume 1 for return code meanings, then correct the cause of the failure.
Reason:
The function terminated due to the indicated VSAM error during JOB SUBMISSION to the INTRDR.
Action:
Notify the CCF system administrator with the VSAM error reason code.
Administrator Response: Correct the indicated error.
Reason:
CCF allocated a message data set named prefix.userid.CCF.MSGS or, if no prefix is set, userid.CCF.MSGS. Use ISPF BROWSE to view the message data set for problem determination. This is a temporary data set. Continued CCF processing replaces the data set (you can rename it to retain it).
Action:
Notify the CCF system administrator before you continue CCF processing.
Administrator Response: Examine the user's message data set and correct the indicated error.
Reason:
The function terminated due to the update error indicated in the $CCF$ LISTING file on your minidisk.
Action:
Notify the CCF system administrator before you continue CCF processing.
Administrator Response: Examine the user's $CCF$ LISTING file and correct the indicated error.
Reason:
The function terminated due to the update error indicated in the CCFPRINT listing file.
Action:
Notify the CCF system administrator before you continue CCF processing.
Administrator Response: Examine the user's job listing and correct the indicated error.
Reason:
The specified programmer is not defined to CCF as reporting to you.
Action:
If the programmer's name was entered correctly, notify the CCF system administrator.
Administrator Response: Verify that the programmer's name was defined in Option 12.3 as reporting to this manager. If the programmer's name is converted in Option 12.8, you must specify the converted CCF ID/KEY in Option 12.3.
Reason:
The specified programmer is not defined to CCF as reporting to you.
Action:
Specify another programmer or request the CCF system administrator define the programmer to you.
Administrator Response: Use Option 12.3 to define the requested programmer to the manager. If the programmer's name is converted in Option 12.8, you must specify the converted CCF ID/KEY in Option 12.3.
Reason:
The requested application was defined as requiring an authorization code.
Action:
Supply the authorization code. If you do not know the authorization code, contact the CCF system administrator.
Administrator Response: Obtain a user's authorization code from Option 12.1. Obtain a manager's authorization code from Option 12.2.
Reason:
You entered an incorrect authorization code.
Action:
Supply the correct authorization code. If you do not know the authorization code, contact the CCF system administrator.
Administrator Response: Obtain a user's authorization code from Option 12.1. Obtain a manager's authorization code from Option 12.2.
Reason:
The function was not performed due to the indicated external security message.
Action:
See the CCF system administrator to obtain security authorization.
Reason:
The function terminated due to the error indicated on the previous LCDF panel.
Action:
Notify the CCF system administrator.
Administrator Response: Correct the indicated error.
Reason:
The function terminated due to the error indicated on the previous LCDF panel.
Action:
Notify the CCF system administrator.
Administrator Response: Correct the indicated error.
Reason:
The function terminated due to the error indicated on the previous LCDF panel.
Action:
Notify the CCF system administrator.
Administrator Response: Correct the indicated error.
Reason:
The function terminated due to an internal error.
Action:
Notify the CCF system administrator.
Administrator Response: Contact Computer Associates Technical Support for assistance.
Reason:
The module is already logged out.
Action:
Wait for the module to become available.
Reason:
You already logged out the site-defined maximum number of modules.
Action:
Reduce the number of logged out modules through the login function. If this is not possible, contact the CCF system administrator.
Administrator Response: Increase the Option 12.0 LOGLIMIT keyword specification.
Reason:
The module is already logged out.
Action:
Wait for the module to become available.
Reason:
The module has at least one outstanding Job Submission Record (JSR) in Option 11. Depending on site option, either the control group or the programmer who submitted the job is responsible for processing the JSR from Option 11.
Action:
Wait for the module to become available.
Reason:
The module is already logged out.
Action:
Wait for the module to become available.
Reason:
The selected production master file does not have a history master file defined to it.
Action:
Notify the CCF system administrator.
Administrator Response: Correct the indicated error.
Reason:
The management code (MCD) defined for the production master file is incorrect.
Action:
Notify the CCF system administrator.
Administrator Response: Specify the correct MCD base code for the production master file in
Option 12.11.3.
Reason:
The management code (MCD) defined for the test master file is incorrect.
Action:
Notify the CCF system administrator.
Administrator Response: Specify the correct MCD base code for the test master file in Option 12.11.3.
Reason:
Your request was placed in the control group's queue.
Action:
Informational message, no response required.
Reason:
Informational.
Action:
None.
Reason:
Informational.
Action:
None.
Reason:
Informational.
Action:
None.
Reason:
Informational.
Action:
None.
Reason:
Informational.
Action:
None.
Reason:
Informational.
Action:
None.
Reason:
Informational.
Action:
None.
Reason:
Informational.
Action:
None.
Reason:
Informational.
Action:
None.
Reason:
CCF tried to build a batch job stream, but the named JCL skeleton was not found in the ISPSLIB skeleton library concatenation.
Action:
Notify the CCF system administrator with the skeleton name.
Administrator Response: Verify that the CCF skeleton library is allocated to the ISPSLIB skeleton file name. If the allocation is correct, add the indicated skeleton to the CCF skeleton library.
Reason:
You requested a function that is restricted to the control group, but you are not defined as a control group member.
Action:
None.
Reason:
Incorrectly formatted data was found in the change request.
Action:
Notify the CCF system administrator.
Administrator Response: Contact Computer Associates Technical Support for assistance.
Reason:
CCF attempted to LOCATE the CCF messages data set, but the LOCATE failed.
Action:
Contact the CCF system administrator with the LOCATE return code (RC=nn).
Administrator Response: Use the LOCATE return code (RC=nn) returned in the message text to determine the LOCATE error. See the IBM documentation on data management services for the meaning of the return code and possible problem resolution.
Reason:
CCF attempted to SCRATCH the CCF messages data set, but the SCRATCH failed.
Action:
Contact the CCF system administrator with the SCRATCH return code and service code (RC=nn,nn).
Administrator Response: Use the SCRATCH return code and service code returned in the message text to determine the SCRATCH error. See the IBM documentation on data management services for the meaning of the return code and possible problem resolution.
Reason:
CCF attempted to UNCATLG the CCF messages data set, but the UNCATLG failed.
Action:
Contact the CCF system administrator with the UNCATLG return code (RC=nn).
Administrator Response: Use the UNCATLG return code (RC=nn) returned in the message text to determine the UNCATLG error. See the IBM documentation on data management services for the meaning of the return code and possible problem resolution.
Reason:
You must supply the indicated field for the function.
Action:
Supply the field and press Enter to continue.
Reason:
The indicated field must have a numeric value.
Action:
Supply a numeric value for the field and press Enter to continue.
Reason:
The copy job ended with a non-zero return code (RC=nn) and CCF created the member COPYERR in your CA Roscoe library.
Action:
See member COPYERR in your CA Roscoe library for details of the error. If you cannot correct the error yourself, notify the CCF system administrator.
Administrator Response: Examine the user's COPYERR member and correct the indicated problem.
Reason:
You specified an invalid option for the jump command.
Action:
Enter a valid option (=n or =n.n, where n is a valid option).
Reason:
Informational.
Action:
None.
Reason:
The amount specified for SCROLL is not FULL, HALF, MAX, or n.
Action:
Enter an acceptable SCROLL value.
Reason:
CCF could not find the profile table required for this function.
Action:
Notify the CCF system administrator.
Administrator Response: Use Option 12.0 to recreate the profile table on the CCF system master file. See the LIB/CCF Implementation Guide for the profile table keywords or use the online help facility.
Reason:
You specified an incorrect management code (MCD) base for the CCF system master file.
Action:
Notify the CCF system administrator.
Administrator Response: Specify the correct CCF system master file MCD base code for the Option 12.0 SYSBASE keyword.
Reason:
The function terminated due to incorrect values in the CCF profile table.
Action:
Notify the CCF system administrator.
Administrator Response: Supply the SYSMAST and SYSBASE keywords in Option 12.0.
Reason:
The function terminated due to the error described in the CCFPRINT listing file.
Action:
Notify the CCF system administrator.
Administrator Response: Examine the user's job output and correct the error described in the CCFPRINT listing file.
Reason:
A CCF batch job failed allocating a required file. The file name is indicated in the diagnostic.
Action:
Notify the CCF system administrator.
Administrator Response: Review the file requirements for this job. Correct and resubmit.
Reason:
Informational.
Action:
None.
Reason:
An invalid parameter was found on a batch job. See the reason indicated in the diagnostic.
Action:
Review the reason indicated. Correct and resubmit.
Reason:
The CR identified in the diagnostic has an invalid format on the CCF system master file.
Action:
Notify the CCF system administrator.
Administrator Response: Check the format of the change request.
Reason:
A CCF batch job failed because of an invalid control statement.
Action:
Review the control statement requirements. Correct and resubmit.
Reason:
The job requires you specify the ddname.
Action:
Supply the ddname statement and rerun the job.
Reason:
The job requires you specify the statement.
Action:
Supply the statement and rerun the job.
Reason:
A CCF batch job failed because too many input records for the record type are indicated in the diagnostic.
Action:
Review the input statement requirements for this job.
Reason:
The job did not complete successfully due to unacceptable step condition codes.
Action:
Check the job output to determine the reason for the error. Correct the error, then resubmit the job using option 11.
Reason:
You are not permitted to open a change request.
Action:
Contact the CCF system administrator to request access to this function.
Reason:
A change request must have a type of PROBLEM or MODIFICATION.
Action:
Place an X next to the appropriate type.
Reason:
You are not authorized to open a change request for the specified application.
Action:
Enter Help for a list of applications for which you are authorized.
Reason:
CCF provides an opportunity to verify and correct the information on this panel before proceeding.
Action:
Press Enter to proceed or use the END or JUMP commands to exit this activity.
Reason:
Informational.
Action:
None.
Reason:
The change request you entered was found among the opened or closed change requests.
Action:
If you entered the change request ID incorrectly, it might already be an open or closed request. Check the change request status report for the change request number.
Reason:
There are no unassigned change requests in your queue.
Action:
Informational, no action required.
Reason:
The name specified is not identified in the CCF system tables as a manager.
Action:
If the ccf ID is spelled correctly, notify the CCF system administrator. Administrator Response: Review system tables and update as appropriate.
Reason:
The CR you entered does not have a status of UNASSIGNED.
Action:
If you entered the change request ID correctly, it might already be assigned.
Reason:
The manager name specified is not defined with authority for the application.
Action:
Notify the CCF system administrator.
Administrator Response: Review CCF system tables and update as appropriate.
Reason:
Informational.
Action:
None.
Reason:
CCF provides an opportunity to verify and correct the information on this panel before proceeding.
Action:
Press Enter to proceed or use the END or JUMP commands to exit this activity.
Reason:
There are no assigned change requests in your queue.
Action:
Informational, no action required.
Reason:
The change request does not exist or does not have a status of ASSIGNED.
Action:
If the change request ID is correct, the change request might have a status of UNASSIGNED or CLOSED.
Reason:
The entry specified was not available from the selection list.
Action:
View selection list and specify one of the available entries.
Reason:
If the change request ID is correct, the change request might have a status of UNASSIGNED or CLOSED.
Action:
Check the validity of the CR ID entered.
Reason:
The production master file has no corresponding history master file.
Action:
Notify the CCF system administrator.
Administrator Response: Define a history master file for the requested production master file using Option 12.11.3.
Reason:
You entered an invalid language. CCF uses the language to determine what action takes place when a member is logged in. For example, a language of COBOL can compile the member, whereas a language of ASM can assemble the member.
Action:
Press HELP for a list of valid languages. If you are unsure of the correct language for the member, contact your manager or CCF system administrator. Supplying an incorrect language causes login problems.
Reason:
Informational.
Action:
None.
Reason:
The logout was rejected because a like-named member was found on the test master file.
Action:
If the production master file was defined with another test master file (check the list of AVAILABLE FILES on the logout panel), try to logout the member using that production/test master file pair. If the production master file is defined only to one test master file, verify that another user is using the like-named member. If not, delete it from or rename it on the test master file.
Reason:
The function was not performed due to the reason indicated.
Action:
None.
Reason:
The module is already logged out (CCF did not find the module on the production master file during that logout and assumed a new module).
Action:
None.
Reason:
The module requested is already logged out to the specified TEST master file.
Action:
None.
Reason:
The module specified is already logged out. Your CCF configuration permits multiple logout.
Action:
None.
Reason:
The change request was opened for an application that is no longer defined to CCF.
Action:
Notify the CCF system administrator.
Administrator Response: Obtain the application name from the change request and define it in Option 12.2.
Reason:
Informational.
Action:
None.
Reason:
The requested module could not be found on the master file.
Action:
Verify spelling. Check the master file index.
Reason:
Informational.
Action:
None.
Reason:
Informational.
Action:
None.
Reason:
Your logout request was placed in the control group's module movement queue (Option 9).
Action:
None.
Reason:
Informational.
Action:
None.
Reason:
CCF created the member HISTERR in your CA Roscoe or AllFusion CA‑Vollie library. It contains information on the error.
Action:
Notify the CCF system administrator.
Administrator Response: Examine the user's HISTERR member and correct the described error.
Reason:
The module indicated is currently logged out to another programmer. CCF was configured at this site to permit multiple logouts.
Action:
Login of this module can require coordination.
Reason:
The function terminated due to the error described in the CCFPRINT listing file.
Action:
Notify the CCF system administrator.
Administrator Response: Examine the user's CCFPRINT listing file and correct the described error.
Reason:
Informational.
Action:
None.
Reason:
Informational.
Action:
None.
Reason:
Library Chain Definition error. For a mixed master file pair, where one supports wide records and the other does not, the COPY ALL LEVELS option was specified and is invalid.
Specify COPY CURRENT LEVEL specified instead.
Action:
Notify the CCF administrator.
Administrator Response: Correct the chain using Option 12.11.2 as indicated.
Reason:
The member was LOCKed on the production master file to the indicated users and cannot be promoted until it is UNLOCKed. Either the user ID who locked the member or someone who has ALL authority towards the data set can UNLOCK it.
Action:
Re-issue the function after the member is UNLOCKed.
Reason:
Invalid data was found in the Module Tracking Record (MTR) control member.
Action:
Notify the CCF system administrator.
Administrator Response: Contact Computer Associates Technical Support for assistance.
Reason:
CCF could not find the specified entry number.
Action:
Enter the number found to the left of the entry.
Reason:
Informational.
Action:
None.
Reason:
The logout did not complete.
Action:
Try logout of another module. Then retry logout of this module. CCF table error.
Reason:
The production master file for this function is not defined to CCF.
Action:
Notify the CCF system administrator.
Administrator Response: Correct the indicated error.
Reason:
The entry was already processed or deleted.
Action:
Perform a function to refresh the selection list to confirm.
Reason:
The requested module has no corresponding history module.
Action:
Save the changes made to the test module (by copying it), delete the logout, then logout the module again to recreate the history member. Update the module with the saved changes before login.
Reason:
The language assigned to the module is no longer defined to CCF.
Action:
Notify the CCF system administrator.
Administrator Response: Use Option 12.5 to redefine the language. If the language was intentionally removed from Option 12.5, the programmer should specify a new language for the module through the Option 5 HISTORY command. Use of the command requires the Option 12.0 HISTUPD keyword to specify YES.
Reason:
The function was not performed due to the error indicated.
Action:
Correct the indicated error.
Reason:
Invalid data was found in the Module Movement Record (MMR) control member.
Action:
Notify the CCF system administrator.
Administrator Response: Contact Computer Associates Technical Support for assistance.
Reason:
The indicated module could not be found on the master file.
Action:
Check master file. If logout was NEW, add the module.
Reason:
The FIND command for this function requires a character string.
Action:
Enter the FIND command with the character string (do not use delimiters).
Reason:
The FIND command did not find the character string.
Action:
Verify the character string entered. Do not use delimiters.
Reason:
FIND request complete.
Action:
Informational, no response required.
Reason:
An RFIND command was issued before a FIND command.
Action:
Issue the FIND command before issuing the RFIND command.
Reason:
No match found.
Action:
Informational, no response required.
Reason:
Informational.
Action:
None.
Reason:
Informational.
Action:
None.
Reason:
The requested archive level no longer exists for this module. The archive cross level compare is not possible.
Action:
None.
Reason:
The archive cross level compare is not possible.
Action:
None.
Reason:
The archive cross level compare is not possible.
Action:
None.
Reason:
The selected Module Tracking Record (MTR) was not created on an z/OS and OS/390 system. You must process the MTR from the originating operating system (indicated in the MTR).
Action:
None.
Reason:
The selected Module Movement Record (MMR) was not created on an z/OS and OS/390 system. You must process the MMR from the originating operating system (indicated in the MMR).
Action:
None.
Reason:
The selected System Link Record (SLR) was not created on an z/OS and OS/390 system. You must process the SLR from the originating operating system (indicated in the SLR).
Action:
None.
Reason:
The selected Job Submission Record (JSR) was not created on an z/OS and OS/390 system. You must process the JSR from the originating operating system (indicated in the JSR).
Action:
None.
Reason:
You cannot promote the member into the Q/A library or reject it into the reject library because the member already exists in the library.
Action:
Retry the function later.
Reason:
Informational, no response required.
Action:
None.
Reason:
Informational. The programmer configured CCF to disallow update of member history.
Action:
Informational, no response required.
Reason:
The function terminated due to a history member format error.
Action:
Notify the CCF system administrator.
Administrator Response: Contact Computer Associates Technical Support for assistance.
Reason:
A DB2 plan name is required for this function.
Action:
Enter the plan name.
Reason:
An invalid value was found for a keyword in the BIND options.
Action:
Review the BIND options member and correct the error.
Reason:
The specified character string in the message is not valid in a DB2 bind options member.
Action:
Delete the invalid data by editing the bind options member on your test master file. Update the member and retry the BIND command.
Reason:
You specified the keyword more than once in the member.
Action:
Delete the duplicate keywords by editing the bind options member on your test master file. Update the member and retry the BIND command.
Reason:
The specified character string in the message is not valid in a DB2 bind options member.
Action:
Delete the invalid data by editing the bind options member on your test master file. Update the member and retry the BIND command.
Reason:
A BIND options member was processing when memory was exceeded.
Action:
Check the BIND options member for validity.
Reason:
Processing of a BIND options member failed.
Action:
Notify the CCF system administrator.
Administrator Response: Verify the member input to the BIND contains valid BIND options. Contact Computer Associates Technical Support for assistance.
Reason:
The BIND options member has unidentified format.
Action:
Review the BIND options member for validity.
Reason:
Informational.
Action:
None.
Reason:
Informational.
Action:
None.
Reason:
Informational.
Action:
None.
Action:
CCF created a member called CCFERROR on your CA Roscoe or AllFusion CA‑Vollie library that describes the error that occurred.
Action:
Notify the CCF system administrator.
Administrator Response: Examine the CCFERROR member and correct the error described.
Reason:
CCF created a member called CCFERROR on your CA Roscoe or AllFusion CA‑Vollie library that describes the error that occurred.
Action:
Examine the CCFERROR member and correct the error.
Reason:
While processing the BIND options member, an invalid owner name was found.
Action:
Review the BIND options OWNER name.
Reason:
The LANGUAGE subcommand of the BIND command is valid only for a new bind options member.
Action:
Do not specify the LANGUAGE command for an existing member.
Reason:
The LANGUAGE subcommand of the BIND command requires a one- to three-character language.
Action:
Supply the language with the command.
Reason:
The DESCRIPTION subcommand of the BIND command is valid only for a new bind options member.
Action:
Do not specify the LANGUAGE command for the existing member.
Reason:
The DESCRIPTION subcommand of the BIND command requires a 1- to 30-character description.
Action:
Supply a description with the command.
Reason:
Processing the BIND options member found invalid syntax.
Action:
Review the format of the BIND options member.
Reason:
The requested function cannot be performed because there is at least one Module Tracking Record (MTR) in Option 5 for this change request.
Action:
Try the function after the MTRs are processed.
Reason:
The requested function cannot be performed because there is at least one Module Movement Record (MMR) in Option 9 for this change request.
Action:
Try the function after the MMRs are processed.
Reason:
A LINK request is currently outstanding for the same LKED SYSIN MEMBER or LKED JCL MEMBER and PROD MAST. You cannot make a duplicate request.
Action:
None.
Reason:
The requested function cannot be performed because there is at least one System Link Record (SLR) in Option 10 for this change request.
Action:
Try the function after the SLRs are processed.
Reason:
The requested function cannot be performed because there is at least one Job Submission Record (JSR) in Option 11 for this change request.
Action:
Try the function after the JSRs are processed.
Reason:
The member specified for the link edit or bind request was not found on the production master.
Action:
Verify that you specified the correct member.
Reason:
The specified link edit SYSIN member does not contain a link-edit name card.
Action:
Logout the link edit SYSIN member, add a link edit NAME card, login the module, and try the link edit request again.
Reason:
Informational.
Action:
None.
Reason:
Informational.
Action:
None.
Reason:
You must specify either RENT or NORENT to indicate whether the module is re-enterable. See the IBM Linkage Editor Manual for details on link edit options.
Action:
Place an X next to the option.
Reason:
You must specify either REUS or NOREUS to indicate whether the module is reusable. See the IBM Linkage Editor Manual for details on link edit options.
Action:
Place an X next to the option.
Reason:
You must specify either REFR or NOREFR to indicate whether the module is refreshable. See the IBM Linkage Editor Manual for details on link edit options.
Action:
Place an X next to the option.
Reason:
You must specify either TEST or NOTEST to indicate whether the module is tested with the TSO TEST command. See the IBM Linkage Editor Manual for details on link edit options.
Action:
Place an X next to the option.
Reason:
Informational.
Action:
None.
Reason:
CCF allocated a message data set named prefix.userid.CCF.MSGS or, if NOPREFIX is set, userid.CCF.MSGS. Use ISPF BROWSE to view the message data set for problem determination. This is a temporary data set. Continued CCF processing replaces the data set (you can rename it to retain it).
Action:
Correct the linkage editor errors described in the message data set and retry the link edit.
Reason:
IEBCOPY was executed to backup the load module before the link edit, but IEBCOPY errors occurred. CCF allocated a message data set named prefix.userid.CCF.MSGS or, if NOPREFIX is set, userid.CCF.MSGS. Use ISPF BROWSE to view the message data set for problem determination. This is a temporary data set. Continued CCF processing replaces the data set (you can rename it to retain it).
Action:
Correct the IEBCOPY errors described in the message data set and retry the link edit.
Reason:
The specified link edit SYSIN member on the production master file contains an invalid NAME statement.
Action:
Logout the link edit SYSIN member, correct the link edit NAME card, login the module, and try the link edit request again. See the IBM Linkage Editor Manual for details on the NAME statement.
Reason:
One of the named fields must be specified.
Action:
Place an X next to the appropriate field. See the LIB/CCF Programmer's Guide for a description of each field.
Reason:
These fields are mutually exclusive.
Action:
Specify only one of the fields. See the LIB/CCF Programmer's Guide for a description of each field.
Reason:
These fields are mutually exclusive.
Action:
Specify only one of the fields. See the LIB/CCF Programmer's Guide for a description of each field.
Reason:
The request to CLOSE or LINK found some tasks were incomplete.
Action:
Review the status of remaining tasks for this CR.
Reason:
IEBCOPY was executed to backup the load module before the link edit, but IEBCOPY errors occurred. CCF created a member called COPYERR on your CA Roscoe or AllFusion CA‑Vollie library.
Action:
Correct the IEBCOPY errors described in the COPYERR member.
Reason:
You are trying an online DB2 bind in a non-z/OS and OS/390 system.
Action:
Submit the bind to an z/OS and OS/390 system.
Reason:
The BIND function failed due to a DB2 problem.
Action:
Review the return code and notify the CCF system administrator.
Administrator Response: Review the DB2 messages and See with the DB2 systems administrator at your site.
Reason:
An operation requiring DB2 was requested and DB2 was not available.
Action:
Review the return code and notify the CCF system administrator.
Administrator Response: Review the DB2 messages and See with the DB2 systems administrator at your site.
Reason:
Informational.
Action:
No response required.
Reason:
Only a B for bind or L for link-edit is valid from this function.
Action:
Enter a B or L.
Reason:
You requested a function that requires the name of the DB2 subsystem, but it is not defined in Option 0 (CCF PARMS).
Action:
Define the DB2 subsystem name using Option 0.
Reason:
The BIND failed. Note the return code and message.
Action:
Review the return code and notify the CCF system administrator.
Administrator Response: Review the DB2 messages and See with the DB2 systems administrator at your site.
Reason:
The member specified in SYSIN is not a BIND options member.
Action:
Review CCF and DB2 documentation.
Reason:
You entered incorrect syntax.
Action:
Review DB2 documentation for correct syntax.
Reason:
Informational.
Action:
None.
Reason:
Informational.
Action:
None.
Reason:
Informational.
Action:
None.
Reason:
The CA Netman update with CCF closure information was terminated due to the error the NTMnnn message indicated.
Action:
Notify the CCF system administrator.
Administrator Response: Correct the indicated error, then rerun the Unicenter CA‑Netman update through
CCF batch program execution.
Reason:
The Unicenter CA‑Netman update with CCF closure information was terminated due to the load error the job log indicated.
Action:
Notify the CCF system administrator.
Administrator Response: Correct the indicated error, then rerun the Unicenter CA‑Netman update through CCF batch program execution.
Reason:
The Unicenter CA‑Netman update with CCF closure information was terminated due to the absence of CCF closure information.
Action:
Notify the CCF system administrator.
Administrator Response: Correct the indicated error, then rerun the Unicenter CA‑Netman update through CCF batch program execution.
Reason:
The requested report could not be generated because CCF did not find any change requests, members, or jobs (depending on the report type requested) that met the criteria specified (if any).
Action:
None.
Reason:
Informational.
Action:
None.
Reason:
Depending on how you are defined to CCF (as a programmer, manager, or control group member), you can request the report based on a single programmer or for an entire group of programmers. See the LIB/CCF Programmer's Guide, LIB/CCF Manager's Guide, or LIB/CCF Control Group Guide for more information on requesting reports.
Action:
Specify either PGMR or GROUP.
Reason:
The requested function requires that the specified programmer report to you.
Action:
Choose another programmer or request the CCF system administrator define the programmer to you.
Reason:
You are not authorized to select this report.
Action:
If you require access to this service, notify the CCF system administrator.
Reason:
CCF was installed so that only the user that last updated this module and that user's manager can request the history report.
Action:
None.
Reason:
CCF was installed so that only the user assigned the change request and that user's manager can request the Change Request Report.
Action:
None.
Reason:
The format of the CR is not valid and can be corrupted.
Action:
Notify the CCF system administrator.
Administrator Response: Review the content of 73-80 in the CR data.
Reason:
The change request has no close section, indicating that is not yet closed.
Action:
None.
Reason:
The LCDF report is generated for either library definitions or chains. A chain provides information on the libraries defined in a promotion path. A library definition provides information for an individual master file or operating system file.
Action:
Specify either LIBRARY DEFINITIONS or CHAINS.
Reason:
When specifying LIBRARY DEFINITIONS, do not supply a CHAIN NUMBER.
Action:
To request a report for a particular chain number, specify CHAINS instead of LIBRARY DEFINITIONS.
Reason:
When specifying CHAINS, do not supply a LIBRARY NAME.
Action:
To request a report for a particular library name, specify LIBRARY DEFINITIONS instead of CHAINS.
Reason:
The selection was not 1, 2, 3, or 4.
Action:
Enter a valid selection.
Reason:
You requested an operation requiring DB2 and DB2 was not available.
Action:
Review the return code and notify the CCF system administrator.
Administrator Response: Review the DB2 messages and See with the DB2 systems administrator at your site.
Reason:
The job submitted to produce a DB2 report failed.
Action:
Review the return code and notify the CCF system administrator.
Administrator Response: Review the DB2 messages and See with the DB2 systems administrator at your site.
Reason:
Invalid data was found in the Module Movement Record (MMR) control member.
Action:
Notify the CCF system administrator.
Administrator Response: Contact Computer Associates Technical Support for assistance.
Reason:
The entry must be in rejected status to be deleted.
Action:
Use the REJECT command to reject the entry and then use the DELETE command.
Reason:
A REJECT command was previously issued for this entry, therefore, the entry is already in a rejected status.
Action:
None.
Reason:
Rejected entries are eligible only for deletion.
Action:
Issue the DELETE command to remove the rejected entry from the list.
Reason:
You can only DELETE entries for your own requests.
Action:
None.
Reason:
Only rejected entries are eligible for unlocking. The unlock function is only applicable when a module's login request was rejected, making it necessary for the programmer to access the module in the reject library to make modifications.
Action:
None.
Reason:
Informational.
Action:
None.
Reason:
The module is not locked on the current master file. Therefore, the UNLOCK command is not applicable.
Action:
None.
Reason:
The selected Module Movement Record (MMR) was not created on a VM/ESA system. You must process the MMR from the originating operating system (indicated in the MMR).
Action:
None.
Reason:
Invalid data was found in the Job Submission Record (JSR) control member.
Action:
Notify the CCF system administrator.
Administrator Response: Contact Computer Associates Technical Support for assistance.
Reason:
Invalid data was found in the Job Submission Record (JSR) control member.
Action:
Notify the CCF system administrator.
Administrator Response: Contact Computer Associates Technical Support for assistance.
Reason:
You requested a function that is restricted to the control group, but you are not defined as a control group member.
Action:
None.
Reason:
The only valid selection characters from this list are D and S. You specified some other character where the cursor is positioned.
Action:
Correct the indicated error.
Reason:
The change request ID that you specified is not found.
Action:
Correct the change request ID to be valid.
Reason:
The specified change request is currently UNASSIGNED. You can only select a CR that is assigned to you.
Action:
Correct the change request ID if miskeyed or contact your manager to have the CR assigned to you.
Reason:
This change request currently has no modules logged out for it.
Action:
Correct the change request ID if miskeyed.
Reason:
Informational.
Action:
Issue the SELECTF command to obtain the current status of all modules for this change request.
Reason:
The GROUP PROCESSING select list cannot be built due to an abnormal condition encountered in the change request activity records.
Action:
Press HELP for details, then notify the CCF system administrator.
Administrator Response: Contact Computer Associates Technical Support for assistance.
Reason:
Invalid data was found in the change request. The function was terminated.
Action:
Do not attempt further processing on this change request and notify the CCF system administrator.
Administrator Response: Contact Computer Associates Technical Support for assistance.
Reason:
Informational. Issue the SELECTF command to obtain the current status of all modules for this change request.
Action:
None.
Reason:
You cannot use the GROUP PROCESSING function (SELECTx commands) for change requests that were initiated before CCF release 3.8.
Action:
None.
Reason:
Informational.
Action:
None.
Reason:
Informational.
Action:
None.
Reason:
Informational.
Action:
None.
Reason:
Informational.
Action:
None.
Reason:
Informational.
Action:
None.
Reason:
Informational.
Action:
None.
Reason:
Informational.
Action:
None.
Reason:
Informational.
Action:
None.
Action:
None.
Reason:
Informational.
Action:
None.
Reason:
The command requires the specification of a change request ID as a parameter in the format of WOnnnnnn or nnnnnn.
Action:
Reissue the command in the correct format.
Reason:
Informational.
Action:
None.
Reason:
The GPO function failed for the reason indicated in the message.
Action:
Notify the CCF system administrator.
Administrator Response: Correct the indicated error.
Reason:
The GPO selection list failed because of insufficient memory in the CA Roscoe EPL.
Action:
Notify the CCF system administrator.
Administrator Response: Review the site parameters for the CA Roscoe CCF environment.
Reason:
The DATE or TIME field (where the cursor is positioned) is invalid.
Action:
Correct the indicated error and continue.
Reason:
The MONTH field (where the cursor is positioned) is invalid.
Action:
Correct the indicated error and continue.
Reason:
The DAY field (where the cursor is positioned) is invalid.
Action:
Correct the indicated error and continue.
Reason:
The HOUR field (where the cursor is positioned) is invalid.
Action:
Correct the indicated error and continue.
Reason:
The MINUTE field (where the cursor is positioned) is invalid.
Action:
Correct the indicated error and continue.
Reason:
The specified DATE and TIME is less than the current date and time.
Action:
Specify a date and time that is greater than or equal to the current date and time.
Reason:
The specified DATE is greater than 99 days from today. CA Scheduler cannot schedule a job for this date.
Action:
Correct the DATE to occur in 99 days from today.
Reason:
The line select character where the cursor is positioned is invalid.
Action:
Supply a valid value and continue.
Reason:
Informational.
Action:
Provide the destination for the move.
Reason:
You entered the line selection characters in an illogical sequence.
Action:
Correct the indicated error and continue.
Reason:
Informational.
Action:
Provide the lines to move.
Reason:
Informational.
Action:
Provide the lines to move.
Reason:
This is a prompt to choose a predecessor.
Action:
Select a predecessor job (a job that must successfully execute before the scheduled jobs or enter END to indicate that the jobs do not have a predecessor job). Enter your selection and continue.
Reason:
The job scheduler status found no jobs scheduled for the CR specified.
Action:
Informational message, no action required.
Reason:
The job scheduler status found no jobs scheduled for the CR specified.
Action:
Informational message, no action required.
Reason:
Select a predecessor job (a job that must successfully execute before the scheduled jobs or enter END to indicate that the jobs do not have a predecessor job).
Action:
Enter your selection and continue.
Reason:
The job that was selected for a predecessor is not in PENDING status.
Action:
Select a predecessor job (a job that must successfully execute before the scheduled jobs or enter END to indicate that the jobs do not have a predecessor job).
Reason:
The SORT command lets you specify a panel field TITLE name as a parameter.
The parameter you specified does not match any title names on the displayed panel.
Action:
Correct the indicated error and continue.
Reason:
The SSTATUS command is only available when a scheduler (Unicenter CA‑7 or CA Scheduler) was defined for use from CCF.
Action:
Select another command or CCF function and continue.
Reason:
Unicenter CA‑7 is not defined as the scheduler available for use from CCF and, therefore, the REDEMAND command is not available.
Action:
Select another command or CCF function and continue.
Reason:
Informational.
Action:
None.
Reason:
Informational.
Action:
None.
Reason:
Informational.
Action:
None.
Reason:
Informational.
Action:
None.
Reason:
You entered more than one selection character on the list.
Action:
Remove all but one selection character or enter END to indicate that no predecessor job is selected.
Reason:
Informational.
Action:
None.
Reason:
A LINE command with a value of zero is not valid.
Action:
Correct the indicated error and continue.
Reason:
You can change the job order by using MOVE line commands to reorder the presented list. MOVE line commands are: M, MM, Mn, B, and A. When the list is in the correct processing order, enter END to continue processing.
Action:
Reorder the list. Enter END to continue processing.
Reason:
You submitted the job to a scheduler and, therefore, it might not process.
Action:
Resubmit and selecting the CHECKOFF step for RESTART can affect the PROCESS function.
Reason:
Informational.
Action:
None.
Reason:
Informational.
Action:
None.
Reason:
Informational.
Action:
None.
Reason:
Informational.
Action:
None.
Reason:
Informational.
Action:
None.
Reason:
Informational.
Action:
None.
Reason:
The specified DATE is not a valid date.
Action:
Be sure you specify numeric values for the date.
Reason:
You cannot LOAD the Unicenter CA‑7 interface program U7SVC. Processing terminated without the job being scheduled.
Action:
Notify the CCF system administrator.
Administrator Response: Provide the U7SVC program for CCF. Manually schedule the job using the the SET=NDB parameter on the DEMAND command.
Reason:
You cannot LOAD the Unicenter CA‑7 interface program CAJCCMD0. Processing terminated without the job being scheduled.
Action:
Notify the CCF system administrator.
Administrator Response: Provide the CAJCCMD0 program for CCF. Manually schedule the job using the L=RDRQ parameter on the ADD JOB command.
Reason:
An error was detected from the CAJCCMD0 program.
Action:
Do not continue CCF processing. Notify the CCF system administrator.
Administrator Response: See the user's CCF.MSGS data set for a scheduler error message. If no message is found, See SYSLOG. Correct the problem and manually schedule the job using the L=RDRQ parameter on the ADD JOB command.
Reason:
The selected predecessor job is not scheduled the same day as the job being scheduled, as CA Scheduler requires.
Action:
Correct the indicated error.
Reason:
An error was detected from the U7SVC program.
Action:
Do not continue CCF processing. Notify the CCF system administrator.
Administrator Response: See the CA7 BROWSE file for an error message. Correct the problem and manually schedule the job using the SET=NDB parameter on the DEMAND command.
Reason:
An error was detected from the CAJCCMD0 program.
Action:
Do not continue CCF processing. Notify the CCF system administrator.
Administrator Response: See the user's SCHEDERR member for a scheduler error message. If no message is found, See SYSLOG. Correct the problem and manually schedule the job using the L=RDRQ parameter on the ADD JOB command.
Reason:
An error was detected from the U7SVC program.
Action:
Do not attempt further CCF processing. Notify the CCF system administrator.
Administrator Response: See the CA7 BROWSE file for an error message. Correct the problem and manually schedule the job using the SET=NDB parameter on the DEMAND command.
Reason:
No modules meet the selection criteria for the indicated change request.
Action:
None.
Reason:
The function terminated during CCF scheduling processing due to an CA Librarian update error.
Action:
Do not attempt further CCF processing. Notify the CCF system administrator.
Administrator Response: See the user's SCHEDERR member for the update error messages. Correct the error condition and manually complete the update.
Reason:
Invalid data was found in the System Link Request (SLR) control member.
Action:
Notify the CCF system administrator.
Administrator Response: Contact Computer Associates Technical Support for assistance.
Reason:
Invalid data was found in the System Link Request (SLR) control member.
Action:
Notify the CCF system administrator.
Administrator Response: Contact Computer Associates Technical Support for assistance.
Reason:
The RESTART command requires the JCL restart parameter (usually stepname or procstepname.stepname).
Action:
Reissue the command with the parameter.
Reason:
You cannot restart the selected step due to the absence of a stepname. Either the JCL does not contain a stepname for this step or the CCF removed the stepname because the step is an execution of a PROC.
Action:
Select a previous restartable step or use the RESTART command to restart at a PROC stepname.
Reason:
The RESTART function requires an S to select a step for restart.
Action:
Place an S on the selection list for the job step.
Reason:
The function terminated due to the detection of an invalid JOBCARD statement in the saved JCL.
Action:
Notify the CCF system administrator.
Administrator Response: Correct the statement by updating the saved JCL on the CCF system master. The JCL is in the Y member name as indicated on the third record of the JSR.
Reason:
The function terminated due to the detection of an invalid -MCD statement in the saved JCL.
Action:
Notify the CCF system administrator.
Administrator Response: Correct the statement by updating the saved JCL on the CCF system master. The JCL is in the Y member name as indicated on the third record of the JSR.
Reason:
The RESTART function allows only one selection.
Action:
Correct the indicated error.
Reason:
You cannot restart the selected step due to the absence of a stepname. CCF removed the stepname because the step is an execution of a PROC.
Action:
Use the RESTART command to restart the step by specifying a parameter to indicate procstepname.stepname to restart.
Reason:
The function terminated due to the error indicated.
Action:
Notify the CCF system administrator.
Administrator Response: The JCL member must be missing due to a previous update error when trying to save it. At this point, the JSR can only be PROCESSED to remove it. If you cannot recover or reconstruct the JCL from the job listing, then you must determine the functions that the job was to perform and perform them manually.
Reason:
A job resubmitted had a PROC without a PEND statement.
Action:
Notify the CCF system administrator.
Administrator Response: Correct the JCL by updating the saved JCL on the CCF system master. The JCL is in the Y member name as indicated on the third record of the JSR.
Reason:
The CHECKOFF did not complete normally, possibly leaving the JSR outstanding in option 11.
Action:
Notify the CCF system administrator. If the JSR appears in option 11, remove it using the PROCESS command.
Administrator Response: If the JSR was never added due to system failure, no action is required. Otherwise, the user should have reported an update error, which you should investigate. If the JSR was added, it was after the job completed and was due to a lockout of the user or poor response time.
Reason:
The job statement was missing from the LINK JCL skeleton when attempting to submit the production link edit.
Action:
Notify the CCF system administrator.
Administrator Response: Correct the JCL used.
Reason:
The function is restricted to a CCF administrator and you are not authorized access.
Action:
None.
Reason:
Informational.
Action:
None.
Reason:
The variable field where the cursor is positioned is either missing or specified with an invalid value.
Action:
Correct the field to a valid value.
Reason:
The variable field where the cursor is positioned is either missing or specified with an invalid value.
Action:
Correct the field to a valid value.
Reason:
You specified the variable keyword where the cursor is positioned more than once.
Action:
Remove all but one entry for the variable keyword.
Reason:
The specified JCL skeleton member, indicated by the cursor is not defined in the skeleton library.
Action:
Correct or add the skeleton name before saving the table.
Reason:
The table must contain at least one entry.
Action:
Provide a table entry or enter CANCEL.
Reason:
The specified change request is not assigned to the specified programmer.
Action:
Correct the indicated error and continue.
Reason:
Informational.
Action:
None.
Reason:
You must specify at least one skeleton name (or NOP) for a LANGUAGE where the cursor is positioned.
Action:
Enter a skeleton name or NOP.
Reason:
You must assign the change request to a programmer before you can reassign it.
Action:
Correct the indicated error and continue.
Reason:
You cannot reassign to both manager and programmer at the same time.
Action:
Reassign managers and programmers separately.
Reason:
The function was not performed because you entered an invalid manager name.
Action:
Correct the manager name where the cursor is positioned.
Reason:
The function was not performed because you entered an incorrect manager name.
Action:
Correct the manager name where the cursor is positioned.
Reason:
The function was not performed because the manager had no CRs outstanding.
Action:
None.
Reason:
The function was not performed because an entry for a keyword is required.
Action:
Supply an entry for the required keyword before you can save the table.
Reason:
The function was not performed due to the unavailability of the resource.
Action:
Try again later.
Reason:
Another administrator ID dequeued the resource while your ID was in use. You cannot update the resource.
Action:
Try again later.
Reason:
You are trying to:
or
Action:
Either choose a group identifier that is not in use or delete all references to the identifier in the other tables.
Reason:
You are trying to delete a group identifier where work is assigned.
Action:
Reassign the work orders to another user or group before deleting the group.
Reason:
You are trying to convert a system identifier to a group identifier. You can only convert system identifiers to individual CCF identifiers.
Action:
Choose a CCF identifier that is not a group.
Reason:
The VSAM catalog name must contain all alphabetic characters. The name contains a special character.
Action:
Reenter the correct VSAM catalog name.
Reason:
You specified a file organization of BDAM and the user supplied a VSAM catalog name.
Action:
Remove the VSAM catalog name or specify a file organization of VSAM.l
Reason:
You specified a file organization of VSAM and the user did not supply a VSAM catalog name.
Action:
Supply a VSAM catalog name or specify a file organization of BDAM.
Reason:
The volume serial number supplied contains a special character.
Action:
Reenter the correct volume serial number.
Reason:
A volume serial number is required for a BDAM master file, but none was supplied.
Action:
Supply a valid volume serial number.
Reason:
You specified a file organization other than BDAM or VSAM.
Action:
Specify BDAM or VSAM as the file organization.
Reason:
A file organization is required for the master file, but none was supplied.
Action:
Supply a valid file organization of BDAM or VSAM.
Reason:
The FCT name must be alphabetic.
Action:
Supply a valid FCT name for the master file.
Reason:
A FCT name is required for the master file, but none was supplied.
Action:
Supply a valid FCT name for the master file.
Reason:
An CA Librarian master file name is required.
Action:
Specify a valid name for the CA Librarian master file.
Reason:
No entries were supplied for the current system table.
Action:
Specify a valid entry for the system table.
Reason:
A maximum of 999 entries are allowed.
Action:
You cannot add more entries.
Reason:
An error occurred accessing the production master file.
Action:
Check the system table information for the production master file.
Reason:
An error occurred accessing the test master file.
Action:
Check the system table information for the test master file.
Reason:
The submit of the CCF JCL failed for the reason indicated.
Action:
Make corrections and reprocess.
Reason:
An error occurred while trying to read the P entry in the chain.
Action:
Check the P entry in table 4 for the current chain.
Reason:
An error occurred accessing the history master file.
Action:
Check the system table information for the history master file.
Reason:
System table 7 does not contain a HISTORY master file for module.
Action:
Check the system table information for the history master file.
Reason:
The display was larger than the terminal size. Only a partial display is shown.
Action:
No action required.
Reason:
An error occurred unlocking the module. The complete details of the error are in the member LOCKERR.
Action:
Check your AllFusion CA‑Vollie member LOCKERR.
Reason:
The programmer, as specified, cannot be found in the CCF tables.
Action:
Check the spelling of the name. Contact the CCF administrator.
Reason:
The SYSIN input control statements contain an error.
Action:
Correct the indicated error and resubmit.
Reason:
The application name, as specified, cannot be found in CCF tables.
Action:
Correct the application name and resubmit.
Reason:
An authorization code is required for this function.
Action:
Supply the authorization code on the indicated statement.
Reason:
An authorization code is required for this function. The code supplied was not valid.
Action:
Correct the authorization code as indicated.
Reason:
The -NAME statement in SYSIN specified a programmer name not related to a manager.
Action:
Correct the programmer name as indicated.
Reason:
The -USER name is not authorized for the application (-APPL) defined in CCF system tables.
Action:
Verify the spelling. Correct the -APPL name to one where the user has authority.
Reason:
The application name, as specified, cannot be found in CCF tables.
Action:
Correct the application name as indicated.
Reason:
The source that created the DBRM was not found on the master file.
Action:
Notify the CCF system administrator.
Administrator Response: Correct the indicated error.
Reason:
The history member for the source that created the DBRM was not found on the CCF HISTORY master file.
Action:
Notify the CCF system administrator.
Administrator Response: Correct the indicated error.
Reason:
The change request that initiated the compile was not found on the CCF SYSTEM master file.
Action:
Notify the CCF system administrator.
Administrator Response: Correct the indicated error.
Reason:
The name found in the PDS directory does not match the internal name found in the DBRM.
Action:
Notify the CCF system administrator.
Administrator Response: Correct the indicated error.
Reason:
There are incomplete control statements from SYSIN or insufficient information from the DBRM.
Action:
Notify the CCF system administrator.
Administrator Response: Correct the indicated error.
Reason:
An SQL error occurred attempting to update the CCF DB2 table.
Action:
Notify the CCF system administrator.
Administrator Response: Correct the indicated error.
Reason:
A DBRM with the same name and time stamp is already in the CCF table. This can occur if the same jobstep was repeated or the time stamp was overridden.
Action:
Notify the CCF system administrator.
Administrator Response: Correct the indicated error.
Reason:
No member found when reading the DBRMLIB.
Action:
Notify the CCF system administrator.
Administrator Response: Review contents of the PDS specified as the DBRMLIB.
Reason:
CCF did not correctly build the DB2 clean-up job JCL.
Action:
Correct the indicated error.
Reason:
An internal CCF error occurred.
Action:
Notify the CCF system administrator.
Administrator Response: Contact Computer Associates Technical Support for assistance.
Reason:
An internal CCF error occurred.
Action:
Notify the CCF system administrator.
Administrator Response: Contact Computer Associates Technical Support for assistance.
Reason:
An internal CCF error occurred.
Action:
Notify the CCF system administrator.
Administrator Response: When in the AllFusion CA‑Vollie environment, check table 9. When in the VM/ESA environment, contact Computer Associates Technical Support for assistance.
Reason:
An error occurred while attempting to LIBPARM the master file.
Action:
Notify the CCF system administrator.
Administrator Response: Contact Computer Associates Technical Support for assistance.
Reason:
A CCF function requiring LIB/CMS services failed.
Action:
Notify the CCF system administrator.
Administrator Response: Contact Computer Associates Technical Support for assistance.
Reason:
Allocation of the CCF system master was not performed before this operation. This is an internal CCF error.
Action:
Notify the CCF system administrator.
Administrator Response: Contact Computer Associates Technical Support for assistance.
Reason:
An illogical condition was encountered.
Action:
Notify the CCF system administrator.
Administrator Response: Contact Computer Associates Technical Support for assistance.
Reason:
An illogical condition was encountered.
Action:
Notify the CCF system administrator.
Administrator Response: Contact Computer Associates Technical Support for assistance.
Reason:
CCF internal error. Data from the $CCFCOMI module was expected in table 9.
Action:
Notify the CCF system administrator.
Administrator Response: Contact Computer Associates Technical Support for assistance.
Reason:
Movement in VM/ESA must be online or submitted to VSE/ESA or z/OS and OS/390 batch.
Action:
Change the machine type for submit or contact the CCF administrator.
Reason:
The members SLRCNTL0 or SLRCNTL1 on the CCF system master are corrupt.
Action:
Notify the CCF system administrator.
Administrator Response: Contact Computer Associates Technical Support for assistance.
Reason:
The member SLRCNTL1 on the CCF system master is corrupted.
Action:
Notify the CCF system administrator.
Administrator Response: Contact Computer Associates Technical Support for assistance.
Reason:
You requested a function for which an operating system library is required. The required library is not defined.
Action:
Notify the CCF system administrator to add information to the chain or submit to a different operating system.
Administrator Response: Define the library in the chain or NOP the library entry.
Reason:
The CCF system is not configured to allow the indicated machine for batch jobs.
Action:
Specify a valid machine type or notify the CCF system administrator.
Administrator Response: Review the CCF configuration, if required.
Reason:
The skeleton name for this language and operating system could not be found in the skeleton library.
Action:
Notify the CCF system administrator.
Administrator Response: Change the language table or update the skeleton library with the correct skeleton.
Reason:
No skeleton could be found for the language required for this module for the operating system you specified.
Action:
Notify the CCF system administrator or try another operating system.
Administrator Response: Correct the language table.
Reason:
You entered the END command, which cancelled the intended function.
Action:
Either re-issue the command to execute it properly or enter the next function.
Reason:
An invalid machine type was encountered.
Action:
Supply a correct machine type (z/OS and OS/390, VSE/ESA, or VM/ESA) and continue.
Reason:
The print destination is not valid.
Action:
You must direct report print to the system spool or to a VM/ESA file.
Reason:
An invalid VM/ESA file identifier was encountered.
Action:
Supply the correct file ID and continue.
Reason:
The function was not performed due to the error indicated.
Action:
Review the VM/ESA SPOOL command. Correct and continue.
Reason:
An invalid spool command option was found.
Action:
Review the VM/ESA SPOOL command. Correct and continue.
Reason:
An invalid spool command option was found.
Action:
Review the VM/ESA SPOOL command. Correct and continue.
Reason:
When a job is sent to a batch machine, you can ask CCF to verify that the JCL and machine ID are correct (specify YES) or submit using the default information with no CCF verification.
Action:
Choose a response and continue.
Reason:
You must establish a link for this function in write (W) or multi-write (MW) mode.
Action:
Choose the appropriate response and continue.
Reason:
Both AUTO and NOAUTO were found.
Action:
Make the correction and continue.
Reason:
Both LIBE and NOLIBE were found.
Action:
Make the correction and continue.
Reason:
Both MAP and NOMAP were found.
Action:
Make the correction and continue.
Reason:
Both STR and NOSTR were found.
Action:
Make the correction and continue.
Reason:
Mutually exclusive options were encountered.
Action:
Make the correction and continue.
Reason:
Both CLEAR and NOCLEAR were found.
Action:
Make the correction and continue.
Reason:
Both VSAM and VM/ESA were found.
Action:
Make the correction and continue.
Reason:
You must make an explicit designation of a VM/ESA file.
Action:
Specify a VM/ESA file and continue.
Reason:
This message is issued from batch logout. The test master file defined in table 4 has no corresponding entry in table 10.
Action:
Notify the CCF system administrator.
Administrator Response: Review table 4 and 10 entries.
Reason:
This message is issued from batch logout. The change request indicates a chain ID that does not match the master file ID and chain ID.
Action:
Notify the CCF system administrator.
Administrator Response: Review the master file ID and chain ID.
Reason:
This message is issued from $CCVS005 and batch logout. Entry defined in table 4 was not also defined in table 10.
Action:
Notify the CCF system administrator.
Administrator Response: Review table 4 and 10 entries.
Reason:
This message accompanies any message with a suffix of E and indicates that job checkoff was terminated.
Action:
You must check this job off manually using the on-line CCF JSR processor.
Reason:
The parm field for the execution of the Batch Checkoff Program (CCFB100) does not contain the CCF-generated job number in the format JCnnnn (for VM/ESA-generated jobs) or Vnnnnnn (for AllFusion CA‑Vollie-generated jobs). The checkoff operation is terminated.
Action:
Correct the parm field and resubmit the job.
Reason:
The JSR entry for this job was not found. The checkoff operation is terminated. Return codes are:
The JSR entry for this job was not found in module JSRCNTL0.
12 Module JSRCNTL0 was not found on the System Master.
Action:
Check the $CCFGEN parameters to make sure the System Master was defined correctly.
Reason:
The JSR entry for this job is incomplete or incorrect.
Action:
Contact Computer Associates Technical Support.
Reason:
The indicated master could not be dynamically allocated.
Action:
If the dtfname is SYSMAST, check the $CCFGEN macro for correct information. For all other masters, check the online CCF tables for correct information.
Reason:
The number of expected print lines was exceeded. Most likely, a fatal error occurred during the update of a master file.
Action:
The IOU messages preceding this message identify the problem.
Reason:
All steps of the job were successful. The JSR entry for this job was removed.
Action:
None.
Reason:
The Batch Checkoff Program (CCFB100) functions under VSE/SP2 only. All checkoff operations were terminated. Most likely, the JCL skeleton for EOJ processing was incorrectly modified.
Action:
See the LIB/CCF Implementation Guide for details.
Reason:
The previous CA Librarian step passed a return code of nn.
Action:
See the AllFusion CA-Librarian VSE/ESA System Services Reference Guide for an explanation of the return codes.
If you are a VSE/SP2 user and this message appears, most likely your JCL skeleton was incorrectly modified. See the LIB/CCF Implementation Guide for details.
Reason:
The previous CA Librarian step passed a non-zero return code. All further processing was suspended.
Action:
If you are a VSE/SP2 user and this message appears, most likely your JCL skeleton was incorrectly modified. See the LIB/CCF Implementation Guide for details.
Reason:
FAIROPN cannot open the indicated master file.
Action:
If the dtfname is SYSMAST, check the $CCFGEN parameters to make sure the System Master was defined correctly. For all other masters, check the online CCF tables for valid entries for the indicated master.
Reason:
An error occurred allocating or freeing memory during an LCDF function.
Action:
Notify the CCF system administrator.
Administrator Response: Contact Computer Associates Technical Support for assistance.
Reason:
Informational.
Action:
None.
Reason:
An LCDF internal error occurred.
Action:
Notify the CCF system administrator.
Administrator Response: Contact Computer Associates Technical Support for assistance.
Reason:
An LCDF panel selection is not valid at this point.
Action:
Review valid selections. Correct and continue.
Reason:
You cannot issue the indicated command from the current screen.
Action:
Enter a valid command and continue.
Reason:
The valid values for SCROLL are PAGE, HALF, MAX, DATA, or nn for number of lines.
Action:
Correct the entry and continue.
Reason:
The JUMP function is not valid at this point in LCDF.
Action:
Enter a valid command and continue.
Reason:
The LCDF function is not valid at this point.
Action:
Correct the indicated error.
Reason:
The field indicated must contain some value.
Action:
Correct the field in error and continue.
Reason:
The indicated field must be blank or a numeric value.
Action:
Correct the field in error and continue.
Reason:
The chain number specified does not exist.
Action:
Review the chain number entered.
Reason:
An internal LCDF error occurred. A diagnostic was not produced because of insufficient memory.
Action:
Notify the CCF system administrator.
Administrator Response: Contact Computer Associates Technical Support for assistance.
Reason:
An internal LCDF error occurred.
Action:
Notify the CCF system administrator.
Administrator Response: Contact Computer Associates Technical Support for assistance.
Reason:
An internal LCDF error occurred.
Action:
Notify the CCF system administrator.
Administrator Response: Contact Computer Associates Technical Support for assistance.
Reason:
The only valid library types at this point are PROD, TEST, or Q/A.
Action:
Correct the library type and continue.
Reason:
Library type was found blank so the LDR should also be blank.
Action:
Assure the library type (PROD, TEST, Q/A, REJ) is filled in before the LDR name.
Reason:
The valid actions are DELETE (D) or INSERT (I).
Action:
Specify a valid action and continue.
Reason:
Check the range for an insert (I) command.
Action:
Correct the command range and continue.
Reason:
The library is already defined as another type.
Action:
Review the other uses of this library.
Reason:
The library is already specified as another type.
Action:
Review library names and types.
Reason:
This process requires the first library type to be PROD.
Action:
Correct the indicated error and continue.
Reason:
Entry validation found a library without a type.
Action:
Correct the indicated error and continue.
Reason:
Entry validation found a library without a type.
Action:
Correct the indicated error and continue.
Reason:
Entry validation found a library type of PROD in a location other than first.
Action:
Review the library chain. Correct and continue.
Reason:
Entry validation found a Q/A library in an invalid location.
Action:
Review the library chain. Correct and continue.
Reason:
Entry validation found a REJ library in an invalid location.
Action:
Review the library chain. Correct and continue.
Reason:
Entry validation found a library type of TEST in a location other than last in the chain.
Action:
Review the library chain. Correct and continue.
Reason:
Source MOVE options are current level (C) or all levels (A)
Action:
Correct the MOVE option to be C or A and continue.
Reason:
You specified an invalid STATUS option.
Action:
STATUS options are lock types TEST (T), PROD0 (0), PROD1 (1), or PROD2 (2). Supply a correct option and continue.
Chapter 3. LIB/CCF Messages 3-67
CDF0260E -CDF0340E
Reason:
OP SYS MOVE value must be N, O, L, or C.
Action:
Correct the indicated error and continue.
Reason:
The first entry is the PROD master. It is the anchor for the chain.
Action:
You can change the name.
Reason:
You must use the cc and dd commands in pairs.
Action:
Correct the indicated error and continue.
Reason:
For REJ libraries, the promote must be to the next highest library.
Action:
Correct the indicated error and continue.
Reason:
For all libraries except REJ, this field has no meaning and must be blank.
Action:
Correct the indicated error and continue.
Reason:
Maximum chain entries is 255. This includes entries that were deactivated but are not yet deleted.
Action:
Notify the CCF system administrator.
Administrator Response: You can use Option 12.11.5 to delete deactivated entries.
Reason:
The PROD LDR must name a corresponding history file.
Action:
Enter the name of an existing history file and continue.
Reason:
Acceptable CA Librarian master file types are BDAM or VM/ESA.
Action:
Supply a valid master file type and continue.
Reason:
MCD code must be numeric. Blank indicates no MCD security.
Action:
Correct the indicated error and continue.
Reason:
Valid VM/ESA link mode values are R, RR, W, WR, M, MR, or MW.
Action:
Correct the indicated error and continue.
Reason:
You must fill in the history file field.
Action:
Correct the indicated error and continue.
Reason:
Supply the data set name.
Action:
Correct the indicated error and continue.
Reason:
You specified a VM/ESA master file and further VM/ESA information is required.
Action:
Supply the required information and continue.
Reason:
VM/ESA owner, address, and password must all be present or all be blank.
Action:
Supply the required information and continue.
Reason:
An error occurred writing to the CCF system master. The specific diagnostic is
reported on $CCF$ listing.
Action:
Notify the CCF system administrator.
Administrator Response: Determine the error from the update listing.
Reason:
You specified a DSN that fails to meet z/OS and OS/390 DSN rules.
Action:
Correct the indicated error and continue.
Reason:
The chain number field must be numeric.
Action:
Enter a valid chain number and continue.
Reason:
The library definition record (LDR) was not found.
Action:
Review the data entered for spelling errors.
Reason:
CCF found the character entered for the LOCK was not a T, 0, 1, or 2.
Action:
Enter a valid character for the LOCK parameter.
Reason:
You specified an LDR that does not exist.
Action:
Supply a correct LDR and continue.
Reason:
While trying to update an LDR for a system file, you specified a backup LDR that is not for a system file.
Action:
Correct the indicated error and continue.
Reason:
Enter Y to supply a new modifier. Blank indicates no new modifier.
Action:
Correct the indicated error and continue.
Reason:
Modifiers are not valid for some LDRs (for example, PROD master).
Action:
Correct the indicated error and continue.
Reason:
A substitute LDR requires an eight-character name of the user.
Action:
Correct the indicated error and continue.
Reason:
Primary LDRs must have blank in the modifier name.
Action:
Correct the indicated error and continue.
Reason:
The MODIFIER name must be unique.
Action:
Correct the MODIFIER name.
Reason:
When going from TEST to Q/A, you can either move the module into Q/A at
LOGIN (Y) or leave the module in the TEST library and notify Q/A (N).
Action:
Specify Y or N and continue.
Reason:
To deactivate a chain, you must specify a verification response. Y indicates to proceed and N indicates not to proceed.
Action:
Specify Y or N and continue.
Reason:
An LDR is missing. The chain is corrupted.
Action:
Notify the CCF system administrator.
Administrator Response: Contact Computer Associates Technical Support for assistance.
Reason:
You cannot update or delete a deactivated chain.
Action:
None.
Reason:
The indicated value where the cursor is positioned must be blank or *.
Action:
Correct the indicated error and continue.
Reason:
Defines the type of access allowed to PROD and Q/A master files from ELIPS and CA Roscoe.
Action:
Supply a valid value and continue.
Reason:
The DELETE function is only valid for LDR MODIFIERS.
Action:
None.
Reason:
The TEST library must be the last entry in the chain.
Action:
Insert the TEST library as the last entry and delete it from its current position.
Reason:
Informational.
Action:
None.
Reason:
The function cannot be performed until you make a selection.
Action:
Specify a selection from the list using the S selection character.
Reason:
This list does not support multiple entry selection.
Action:
Specify only one selection.
Reason:
You must use the character S as a selection character on this list.
Action:
Correct the character where the cursor is positioned.
Reason:
Informational.
Action:
None.
Reason:
You must convert the indicated LCDF component to version 3.9 format before you can use it.
Action:
Notify the CCF system administrator.
Administrator Response: Specify CCF Option 12.11 for the automatic conversion.
Reason:
The indicated LCDF component was converted to version 3.9 format. You cannot update it with this version of CCF.
Action:
Notify the CCF system administrator.
Administrator Response: LCDF was converted to a more recent release. A previous release cannot update it.
Reason:
The specified VM/ESA ADDRESS is not a valid disk address.
Action:
The valid disk address is 0 - F, 1-4 characters. Correct and continue.
Reason:
Internal error. LCDF issued the indicated message and it was not found in the message table.
Action:
Notify the CCF system administrator.
Administrator Response: Contact Computer Associates Technical Support for assistance.
|
Copyright © 2003 CA.
All rights reserved.
|
|