|
|
|
|
|
This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.
Explanation: You are not authorized to save the current ruler. Control-D security exit CTDX004, routine RULSAVE, determined that you cannot save rulers.
The ruler is not saved.
Corrective Action: If you think you should be able to save rulers, contact your INCONTROL administrator.
Explanation: The RESTORE skeleton that is used for restoring reports converted to Control-D from other products (CA-View, CA Dispatch, and so on) cannot be read from the SKL library.
The restore request ends NOT OK.
Corrective Action: Proceed according to the CTMMEM return code displayed in the message. CTMMEM return codes are described in the DOCIMEM member in the IOA DOC library. After correcting the action, request RESTORE of the problematic report.
Explanation: The DASYSIN file for the CTDSMFRP utility contains a blank statement. The DASYSIN file should contain selection criteria statements for the SMF report.
The CTDSMFRP utility terminates with a return code of 08.
Corrective Action: Provide correct selection criteria statements.
Explanation: This is one of two messages with the same ID, but different text.
There are no Control-D SMF records to match the selection criteria for the SMF report (the CTDSMFRP utility), or no selection criteria were specified when running the CTDSMFRP utility, or SMF was not set to YES in CTDPARM.
The CTDSMFRP utility terminates with a return code of 04.
Corrective Action: No action is required.
Explanation: This is one of two messages with the same ID, but different text.
There is insufficient memory to read the RESTORE skeleton that is used for restoring reports converted to Control-D from other products (for example, CA-View, CA Dispatch).
The current restore request ends NOT OK.
Corrective Action: Increase the REGION size of the online environment.
Explanation: Dynamic allocation of the internal reader (INTRDR) by a Control-D command failed during an attempt to submit a restore job for reports converted to Control-D from other products (such as, CA-View, CA Dispatch).
In this message, rc is the return code of the failed dynamic allocation.
The restore job is not submitted. The current restore request ends NOT OK.
Corrective Action: Refer to the IBM manual that deals with information returned from an SVC 99. Take appropriate action based on the return code displayed in the message.
Explanation: There is insufficient memory for the SYSDATA record that is needed to restore reports converted to Control-D from other products (for example, CA-View, CA Dispatch).
The current restore request ends NOT OK.
Corrective Action: Increase the REGION size of the Online environment.
Explanation: Open of scratch list file issued by the CTDDELRP utility in the DASCRLST DD statement failed.
Possible causes are:
The CTDDELRP utility ends with errors.
Corrective Action: Check the JCL for the job; correct and rerun the utility.
Explanation: This information message indicates that the CTDDCD program of the CTDDELRP utility, which deletes unneeded CDAM data sets, has started.
Corrective Action: No action is required.
Explanation: This information message indicates that the CDAM scratch list is empty. This message is issued by the CTDDCD program of the CTDDELRP utility, which is used to delete unneeded compressed sysout data sets.
Corrective Action: No action is required.
Explanation: Normal termination message of the CTDDCD program (of the CTDDELRP utility) which is used to delete unneeded compressed sysout data sets.
Corrective Action: No action is required.
Explanation: The CTDDCD program (used in the CTDDELRP utility and in the New Day procedure), which is used to delete unneeded data sets, ended with errors.
The CTDDCD program continues processing and completes with a condition code of 04.
Corrective Action: Refer to previous messages and the CTDA18E message.
Explanation: This information message is issued by the CTDDCD program of the CTDDELRP utility to indicate that the dsn compressed sysout data set was deleted successfully.
Corrective Action: No action is required.
Explanation: Warning message from the CTDDCD program (of the CTDDELRP utility) indicating that the dsn compressed sysout data set could not be deleted. The reason for the failure is described in the CTDA18E message.
Corrective Action: No action is required.
Explanation: This warning from the CTDDCD program indicates that a data set could not be deleted and displays the reason for the message, the related system function, the return code, and the status code. The header for this message is provided by the CTDA17E message.
Possible values for rsn are:
The CTDDELRP utility or the New Day procedure continues processing and completes with a condition code of 04.
Corrective Action: Perform the action described below as appropriate for the reason in the message.
If you cannot solve the problem, refer to the IBM manual System Programming Library: Data Management for an explanation of reason and status codes. See the LOCATE, SCRATCH, or UNCATALOG section, depending upon the function displayed in the message:
Explanation: CTDDCD issues this message to report that open of scratch rejects file failed (the DASCRREJ DD statement).
Possible causes are:
The CTDDELRP utility or the New Day procedure ends with errors.
Corrective Action: Correct the JCL, and rerun the job.
Explanation: There may be a missing DAIN DD statement in the JCL job.
The CTDCRL program terminates.
Corrective Action: Add a DAIN DD statement to the job.
Explanation: There may be a missing DAOUT DD statement in the job JCL.
The CTDCRL program terminates.
Corrective Action: Add a DAOUT DD statement to the job.
Explanation: This information message indicates that the CTDCRL program started processing.
Corrective Action: No action is required.
Explanation: This information message indicates that the CTDCRL program ended and read num records.
Corrective Action: No action is required.
Explanation: This information message indicates that the CTDCRL program ended and wrote num records.
Corrective Action: No action is required.
Explanation: This information message indicates that the CTDCRL program finished processing.
Corrective Action: No action is required.
Explanation: The SORT utility invoked by the CTDDELRP utility failed to open the ddName DD statement.
The CTDDELRP utility stops.
Corrective Action: Ensure all DD statements are valid. Restart the CTDDELRP utility.
Explanation: Internal sort program ended with errors. This message is from the CTDDELRP utility, which cleans unnecessary entries from the Active User Report List file. The utility uses the site sort program internally.
The utility terminates with a condition code of 08.
Corrective Action: Refer to the sort messages for the job and to the user guide for the sort facility used at your site.
Explanation: The CTDDELRP Control-D utility, which cleans unnecessary entries from the Active User Report List file, failed to open the scratch list file using the DASCRLST DD statement. Possible causes are:
The utility terminates with a condition code of 08.
Corrective Action: Correct the JCL and rerun the job.
Explanation: This information message indicates that the CTDDELRP utility is waiting for another CTDDELRP job or a restore job to terminate. CTDDELRP is cleans unnecessary entries from the Active User Report List file. To maintain data integrity, CTDDELRP cannot run concurrently with another CTDDELRP or a restore job.
When the contending job terminates, CTDDELRP resumes processing.
Corrective Action: No action is required.
Explanation: Open of the Active Transition file failed. This file is referenced by the DAWORK DD statement. The DAWORK DD statement is probably missing. This error message is issued by the CTDDSO program, which is the first step of the CTDDELRP utility.
CTDDSO terminates with a condition code of 08.
Corrective Action: Check for previous messages indicating the reason for the open failure. Correct the problem, and rerun the CTDDELRP utility.
Explanation: This information message is produced by the CTDDELRP utility. It indicates the jobName job is ready for migration by the missionName Migration Mission.
The sysout compressed data sets for the jobName job will not be deleted until the Migration Mission runs successfully.
Corrective Action: No action is required.
Explanation: This information message indicates that the CTDDELRP utility, which cleans unnecessary entries from the Active User Report List file, cannot find a SYSDATA record that corresponds to an index record in the Active User Report List file.
The SYSDATA record was probably manually deleted from the Active User Reports List file.
The index record and index file are deleted to maintain database integrity. Processing continues.
Corrective Action: No action is required.
Explanation: The CTDDELRP utility, which is used to clean unnecessary entries from the Active User Report List file, did not receive input parameters from a DADELIN DD statement. The CTDDELRP utility should be supplied with input parameters indicating actions for the utility to perform.
The CTDDSO program terminates with a condition code of 08.
Corrective Action: Verify that input parameters are specified by means of the DADELIN DD statement, and rerun the job.
Explanation: The CTDDELRP utility, which cleans unnecessary records from the Active User Report List file, failed to open the Print Control Record Scratch file referenced by the DAXREP DD statement. The DAXREP DD statement is probably missing. This error message is issued by the CTDDSO program, which is the first step of the CTDDELRP utility.
The CTDDSO program terminates with a condition code of 08.
Corrective Action: Correct the error, and rerun the CTDDELRP utility.
Explanation: An I/O error occurred while writing the file referenced by the DAXREP DD statement. This message is issued by the CTDDSO program, which is the first step of the CTDDELRP utility.
The CTDDELRP utility terminates.
Corrective Action: Run the CTDBLXRP utility to rebuild the Print Control Record. Rerun the CTDDELRP utility.
Explanation: The file referenced by the DAXREP DD statement has insufficient space allocated. This message is issued by the CTDDSO program, which is the first step of the CTDDELRP utility.
The CTDDELRP utility continues processing.
Corrective Action: To prevent this problem in the future, allocate more space to the file referenced by the DAXREP DD statement. Run the CTDBLXRP utility to rebuild the Print Control Record.
Explanation: An error was encountered while trying to delete a Print Control Record. This message is issued by the CTDDSO program, which is the first step of the CTDDELRP utility.
Possible values of rc are:
The CTDDELRP utility continues processing.
Corrective Action: Run the CTDBLXRP utility to rebuild the Print Control Record.
Explanation: This information message indicates that the CTDDELRP utility is running in SIMULATION mode. In SIMULATION mode, the CTDDELRP utility produces a report that indicates which entries would have been deleted and which data sets would have been erased if the utility were running in PRODUCTION mode.
Corrective Action: Examine the output of the CTDDELRP utility to determine if the proper entries would have been deleted from the Active User Report List file and the proper CDAM data sets would have been erased. Make any changes required to prevent the deletion of needed Active User Report List entries or CDAM data sets.
Rerun the utility in PRODUCTION mode to delete unneeded entries in the Active User Report List file and to erase CDAM data sets that no longer have references in that file.
Explanation: If an asterisk (*) was entered in the CLASS field, a value must be inserted in the EXTWTR field, the DEST field, or the FORM field.
Corrective Action: Insert a value in the EXTWTR, DEST, or FORM field.
Explanation: Mixed generic and non-generic classes were specified. When setting GENERIC to Y, only the classes specified in the GENCLAS Installation Parameter are allowed. When setting GENERIC to N, only classes not specified by the GENCLAS Installation Parameter are allowed.
Corrective Action: Correct the CLASS field.
Explanation: User entered an invalid value in the CONTID field in the Decollating Mission Definition screen.
Corrective Action: Enter a valid option in the CONTID field.
Explanation: A recipient that was defined in a DO USER parameter of the decollating mission does not appear in the Control-D Recipient Tree. This message appears while exiting the Decollating Mission Definition screen, or after using the CHKUSR command.
The Decollating Mission Definition screen is not exited; an error message containing the invalid user name is displayed.
Corrective Action: Correct the invalid user name in the decollating mission definition, or add a new user to the Control-D Recipient Tree.
Explanation: A value was set for the DO REMARK parameter in the Decollating Mission Definition screen, but no text was entered for the remark.
Corrective Action: Enter text in the DO REMARK parameter field.
Explanation: There is an invalid value in the T field on a DO USER line in the Decollating Mission Definition screen.
Valid values are:
Corrective Action: Enter a valid option in the T field.
Explanation: User entered the SYSOUT option in the ON statement line on the Decollating Mission Definition screen, in a JES3 site. DO SYSOUT is supported in JES2 sites only. Your site must be a JES3 site.
Corrective Action: Specify any valid option other than SYSOUT in the ON statement, for example, ON CLASS, ON DSN, and so on.
Explanation: DO CTBRULE has been specified without a rule name. If a DO CTBRULE statement is specified, a rule name must be included in the statement.
Corrective Action: Specify the rule name, or delete the DO CTBRULE statement.
Explanation: The first character specified in the rule name in the DO CTBRULE statement is, but should not be, numeric. The rule name must be a member name, and member names cannot begin with a numeric character.
Corrective Action: Correct the specified rule name so that the first character is not numeric.
Explanation: The value of the MAX COPIES field must be, but is not, greater than or equal to the value of the COPIES field.
Corrective Action: Change the value of either COPIES or MAX COPIES so that MAX COPIES is greater than or equal to COPIES.
Explanation: Mandatory fields are missing in the ON CLASS/TRNCLASS statement. The list of mandatory fields is defined in the WDN130 optional wish. A list of missing mandatory fields is provided in this message. This list contains one or more of the following fields: EXTWTR, DEST, FORM
Corrective Action: Fill in the missing mandatory fields.
Explanation: Option A (All) is specified for the SYNONYM parameter for use with the DO USER=*FORCE action. When SYNONYM is set to A, report pages are sent to all users in the Recipient Tree that have the specified synonym. This parameter cannot be specified when the statement DO USER=*FORCE is chosen, because USER=*FORCE causes the Recipient Tree to be searched until the first user with the specified synonym is found.
Corrective Action: Change the parameter to F (first), or clear it.
Explanation: The user specified an invalid SYNONYM parameter.
The valid options for the SYNONYM parameter:
Corrective Action: Change the parameter to F, A or blank.
Explanation: An executing Restore Mission failed to created or update an internal Printing Mission record in the Active User Report file.
When a record with status WAITING FOR PRINT is restored, the Control-D Decollation monitor writes an internal Printing Mission record to indicate that there are reports waiting to be printed by the Printing Mission specified in the DO PRINT parameter. These records are produced with the following key:
X’FE’,C’PRINTMS’,Printing_Mission_Name.
rc is the return code from the CTDXRP routine.
The Restore Mission restores the reports but terminates with NOTOK status. The restored reports will not be selected by any Printing Mission whose name is specified in the DO PRINT Decollation Mission parameter.
Corrective Action: These reports can be manually scheduled for Deferred Printing by using the P line command to display the Print Window under Option U and then specifying the Printing Mission name. If the problem persists, report the return code to BMC Customer Support.
Explanation: This information message denotes the normal start of the RSTRESET Control-D utility.
The RSTRESET utility changes the status of all active restore missions to ENDED NOT OK, and changes the status of all reports selected for restoring to BACKED UP.
Corrective Action: No action is required.
Explanation: This information message indicates that the RSTRESET Control-D utility ended normally.
Corrective Action: No action is required.
Explanation: The CTDRESET utility has failed to open the Active Mission file.
The utility does not reset reports restore processing.
Corrective Action: Call your INCONTROL Administrator.
Explanation: The specified Restore Mission name is not defined in the Restore Mission Definition library.
When you request a Restore, a validity check is done for the Restore Mission name. A search is made for the $$PARMS member in the library allocated to the DACMD xx DD statement, where xx is the application ID. The member contains a RSTLIB parameter, which specifies the name of the Restore Mission Definition library. If the Restore Mission name is not found in this library, this message is issued.
Corrective Action: Specify a Restore Mission name which exists in the Restore Mission Definition library. If you are not familiar with the names used in your data center, consult your INCONTROL administrator.
Explanation: Internal error in the Restore Mission validation process.
When you request a Restore, a validity check is done for the Restore Mission name. A search is made for the $$PARMS member in the library allocated to the DACMD xx DD statement, where xx is the application ID. The member contains a RSTLIB parameter, which specifies the name of the Restore Mission Definition library. The parameter was missing from the member.
Corrective Action: Consult your INCONTROL administrator who will specify the RSTLIB parameter in the $$PARMS member.
Explanation: Syntax errors were detected in the Display Types definition member. The Display Type definition member was loaded and analyzed and syntax errors were detected. Specific errors were previously displayed with the erroneous source lines.
The User Reports Entry Panel is not displayed.
Corrective Action: Correct the Display Types definition errors in the $$FRM member of the PARM library, and try to reenter the User Reports Entry Panel.
Explanation: An internal error occurred while attempting to display the error messages that resulted from the syntax check of the Display Type definitions.
The error messages are not displayed.
Corrective Action: Ask your INCONTROL administrator to notify BMC Customer Support.
Explanation: There was an attempt to display an invalid User Report List display combination. Available Report List display combinations are predefined in the $$FRM member of the PARM library. The exact combination must exist in the member.
For each combination, the following three characteristics are defined:
The User Report List screen is not displayed.
Corrective Action: Specify a valid (existing) display combination.
Explanation: An internal error occurred while attempting to place the Display Type’s header in the screen.
The User Report List screen is not displayed.
Corrective Action: Have your INCONTROL administrator notify BMC Customer Support.
Explanation: An INSERT operation was attempted on a User Report List whose current Display Type does not contain the USER field. To insert a new user record in a User Report List, the USER field must be specified.
The new record is not inserted.
Corrective Action: Insert a record when using a Display Type that contains the USER field, or add this field to the definition of the current Display Type.
Explanation: An INSERT operation was attempted on a User Report List whose current Display Type contains a protected USER field. To insert a new user record in a User Report List, the USER field must be specified.
The new record is not inserted.
Corrective Action: Either insert the record when using a Display Type that contains an unprotected USER field, or define the USER field in the current Display Type as unprotected.
Explanation: An INSERT operation was attempted on a User Report List whose current Display Type does not contain the JOBNAME field. To insert a new user record in a User Report List, the JOB field must be specified.
The new record is not inserted.
Corrective Action: Either insert a record when using a Display Type that contains the JOB field, or add this field to the definition of the current Display Type.
Explanation: An INSERT operation was attempted on a User Report List whose current Display Type contains a protected JOBNAME field. To insert a new user record in a User Report List, the JOB field must be specified.
The new record is not inserted.
Corrective Action: Either insert the record when using a Display Type that contains an unprotected JOB field, or define the JOB field in the current Display Type as unprotected.
Explanation: An attempt was made to specify an option (for example, Insert, Update, and so on) however, the OPTION field is not present in the current Display Type. The OPTION field must be defined in a Display Type in order to specify a required operation or option on a record of the User Report List.
No operations are performed on the User Report List.
Corrective Action: Add the OPTION field to the Display Type.
Explanation: An internal error occurred while attempting to process the User Report List.
The User Report List screen is not processed.
Corrective Action: Have your INCONTROL administrator notify BMC Customer Support.
Explanation: The user attempted to update or modify the contents of the USER field, the JOB field, or both. The USER and the JOB fields may not be modified when updating a record.
The record is not updated.
Corrective Action: Try updating the record again without modifying the USER or JOB fields.
Explanation: The user modified or updated the contents of a field, but the field length defined in the Display Type definition is shorter than the size of the field in the Control-D database.
A field can be updated in the Control-D database only if its length in the screen is not less then its database length. While this is normally the case, an error might have been made if the Display Type field was defined especially for the site.
The record is not updated.
Corrective Action: Modify the length of the field in the DISPLAY TYPE definition to the recommended length. A list of field lengths can be found in the $$FIELD member in the PARM library.
Explanation: An internal error occurred while attempting to insert or update a user record.
The record is not inserted or updated.
Corrective Action: Have your INCONTROL administrator notify BMC Customer Support.
Explanation: An internal error occurred while attempting to insert a user record.
The record is not inserted.
Corrective Action: Have your INCONTROL administrator notify BMC Customer Support.
Explanation: The contents of a field that do not fit on the physical screen were modified or updated. Display formats with a logical length of 132 columns may be used on a physical screen of 80 columns, but some of the fields are not displayed at all, and some are truncated. An editable field that is truncated may not have its contents modified or updated.
The record is not updated. The cursor is positioned on the problematic field.
Corrective Action: Modify the Display Type definition to allow the entire field to be displayed, or use a physical screen which displays the entire field.
Explanation: This Display Type is not authorized for the current user. The INCONTROL administrator can authorize (or deny) the use of certain Display Types for certain users.
The User Report List screen is not displayed.
Corrective Action: Request a Display Type for which you are authorized, or see your INCONTROL administrator for authorization and access to specified Display Type.
Explanation: Entry to the User Report List attempted without specifying a Display Type in the User Reports Entry Panel. To view the User Report List, specify a valid Display Type in the DISPLAY TYPE field.
The User Report List is not displayed.
Corrective Action: Specify a valid Display Type.
Explanation: A date in the FROM DATE or TO DATE field of the User Reports Entry Panel is invalid. The specified date must be a valid date in the format used in your installation. For more information, see the Control-D and Control-V User Guide.
The User Report List is not displayed.
Corrective Action: Correct the date specification and retry.
Explanation: The relative date in the FROM DATE or TO DATE field of the User Reports Entry Panel is invalid.
For information about valid combinations for this field, see the Control-D and Control-V User Guide.
The User Report List is not displayed.
Corrective Action: Correct the date specification and retry.
Explanation: The value in the REMARK or CC field of the User Reports Entry Panel is invalid.
For information about valid combinations for this field, see the Control-D and Control-V User Guide.
The User Report List is not displayed.
Corrective Action: Correct the REMARK or CC specification and retry.
Explanation: The Display Type code specified in the DISPLAY command in the User Report List is invalid. The DISPLAY command requires a one letter Display Type parameter. This parameter must indicate an existing Display Type.
The current Display Type is not changed.
Corrective Action: Specify a valid Display Type with the DISPLAY command.
Explanation: More than one letter is specified for the Display Type code in the DISPLAY command in the User Report List. The DISPLAY command requires a 1-letter Display Type parameter. This parameter must indicate an existing Display Type.
The current Display Type is not changed.
Corrective Action: Specify a valid, 1-letter Display Type with the DISPLAY command.
Explanation: The Display Type specified contains only Long format lines. A Display Type cannot have all its lines defined as Long format lines. At least one line must be defined for Short format. Long format lines are used only when Additional Information is requested for a record. Short format lines are always displayed.
For information on customizing IOA display format members, see the INCONTROL for z/OS Administrator Guide.
The User Report List is not displayed.
Corrective Action: Modify the Display Type definition to contain at least one Short format line.
Explanation: There is an attempt to change the Display Type using the DISPLAY command, while a new record is being inserted using the Insert line option. The insert operation must be complete before a Display Type is changed.
The DISPLAY command is not performed.
Corrective Action: Complete the insert operation, and then retry the DISPLAY command.
Explanation: There was an attempt to modify or update the contents of a numeric field with a non-numeric value. The updated field must have a numeric value.
The record is not updated.
Corrective Action: Specify a numeric value in the field before updating the record.
Explanation: The report for which view is requested contains no report lines. An empty report usually indicates that a ruler was applied to a report, which contained a combination of Include and Exclude criteria that left no lines in the report.
The VIEW option is not performed.
Corrective Action: Check the ruler or rulers for the report. Request that the report be displayed without problematic rulers or without rulers entirely.
Explanation: You cannot un-restore a record that is not scheduled to be restored. Only records in the WAIT-RESTORE state can be un-restored.
The un-restore operation is not performed.
Corrective Action: No action is required.
Explanation: The CTDTUSR User Report List program resides below the 16MB line. The CTDTUSR User Report List program is designed to run above the 16MB line to achieve better resource utilization, especially when running under the Online monitor. For some reason, the program is not taking advantage of this ability.
The system continues as usual.
Corrective Action: Have your INCONTROL administrator notify BMC Customer Support.
Explanation: This information message indicates that the restore request to the backed up (migrated) report is canceled.
The variables in this message are:
Corrective Action: No action is required.
Explanation: An unauthorized operation was attempted on a DEMO record. DEMO records are reserved for demonstration and training purposes, and are normally accessed by specifying DEMO in the User Reports Entry Panel. Some operations are not permitted on DEMO records. To protect the integrity of the DEMO records, Update and Delete operations are not permitted on these records.
The unauthorized operation is not performed.
Corrective Action: No action is required.
Explanation: There was an attempt to delete a report entry from the History User Report List file that has a status of WAIT RESTORE. Report entries in WAIT RESTORE state cannot be deleted.
The delete operation is not performed.
Corrective Action: User should first use the No Restore option to change the status of the report entry to BACKEDUP, and then perform the delete again.
Explanation: The Control-D Notepad Facility received a nonzero return code from the CTDNPS routine; notes cannot be obtained. The message usually accompanies another error message that defines a specific error according to the return code (rc).
Corrective Action: Contact your system programmer for assistance.
Explanation: The Control-D Notepad Facility received a nonzero return code from routine CTDTNTP; notes cannot be displayed. The message represents an internal error in the Control-D Notepad Facility. The return code (rc) indicates the error.
Corrective Action: Contact BMC Customer Support for assistance.
Explanation: The CTDX004 Control-D security exit determined that you are not authorized to read or write tag notes in the displayed report.
Corrective Action: If you think you should be able to read or write tag notes, contact your INCONTROL administrator.
Explanation: An invalid mission type was specified.
Corrective Action: Correct the mission type and continue.
Explanation: This information message indicates that the memName member has been saved successfully. All missions are stored on members.
Corrective Action: No action is required.
Explanation: The CNDREC# parameter in IOAPARM has been changed but the IOA Conditions file has not been rebuilt.
A difference was detected between the length of the IOA Conditions file and the length specified in the IOAPARM member of the PARM library.
This is usually due to using the IOAPARM member (read from the IOA Load library) for the wrong monitor.
The monitor shuts down.
Corrective Action: To correct this situation, do one of the following:
After correcting the problem, restart the monitor.
Explanation: The CTDSE01 module was not found and was not linked into the CTDCMI module. To perform security checking during ordering of missions, Control-D calls the CTDSE01 security exit. If your security checking is performed by CTDX001, link a dummy security exit into CTDCMI to prevent this message from being issued.
The mission is ordered.
Corrective Action: Check whether or not the security exit should exist.
Explanation: This information message indicates that the CTDNDAY process started deleting unneeded INP records from the Control-D Active User File.
Corrective Action: No action is required.
Explanation: This information message indicates that the CTDNDAY process completed deleting unneeded INP records from the Control-D Active User File.
Corrective Action: No action is required.
Explanation: This error message indicates that the CTDNDAY process failed to delete the unneeded INP records from the Control-D Active User File. The CTDNDAY process finished executing with a conditional code of 08.
Corrective Action: Examine the SYSPRINT and IOA Log File for error messages to clarify the cause of the problem. If possible, fix the problem and rerun CTDNDAY.
Explanation: This information message indicates the number of INP records deleted from the Active User File during the CTDNDAY run.
Corrective Action: No action is required.
Explanation: This error message is issued during Control-D audit service initialization if an error is detected in the AUDTPARM audit configuration member.
The variables in this message are:
The audit service initialization stops, but the component continues to work without Control-D auditing.
Corrective Action: Examine the following message that explains the reason for the error. For Control-D auditing to work properly, correct the invalid line in the AUDTPARM member and restart the task.
Explanation: An invalid block name is detected in the AUDTPARM audit configuration member.
The audit service initialization stops, but the component continues to work without Control-D auditing.
Corrective Action: Examine the preceding CTDAD1E message where the invalid block coordinates are specified. For Control-D auditing to work properly, correct the error in the AUDTPARM member and restart the task.
Explanation: An invalid parameter name is detected in the AUDTPARM audit configuration member.
The audit service initialization stops, but the component continues to work without Control-D auditing.
Corrective Action: Examine the preceding CTDAD1E message where the invalid parameter coordinates are specified. For Control-D auditing to work properly, correct the error in the AUDTPARM member and restart the task.
Explanation: An invalid parameter value is detected in the AUDTPARM audit configuration member.
The audit service initialization stops, but the component continues to work without Control-D auditing.
Corrective Action: Examine the preceding CTDAD1E message where the invalid parameter coordinates are specified. For Control-D auditing to work properly, correct the error in the AUDTPARM member and restart the task.
Explanation: A parameter value length in the AUDTPARM audit configuration member exceeds the maximum allowable length for this parameter.
The audit service initialization stops, but the component continues to work without Control-D auditing.
Corrective Action: Examine the preceding CTDAD1E message where the invalid parameter coordinates are specified. For Control-D auditing to work properly, correct the error in the AUDTPARM member and restart the task.
Explanation: A mandatory parameter is missing from a block of the AUDTPARM audit configuration member.
The audit service initialization stops, but the component continues to work without Control-D auditing.
Corrective Action: Examine the preceding CTDAD1E message where the invalid block coordinates are specified. For Control-D auditing to work properly, correct the error in the AUDTPARM member and restart the task.
Explanation: An EVENT block is not defined in the AUDTPARM audit configuration member for the level specified by the LEVELA parameter of the LEVEL block.
The audit service initialization stops, but the component continues to work without Control-D auditing.
Corrective Action: Examine the preceding CTDAD1E message where the invalid block coordinates are specified. For Control-D auditing to work properly, correct the error in the AUDTPARM member and restart the task.
Explanation: This information message indicates that the CTDAPRV utility has started.
Corrective Action: No action is required.
Explanation: This information message indicates that the CTDAPRV utility has completed successfully without errors.
Corrective Action: No action is required.
Explanation: This error message indicates that the CTDAPRV utility discovered problems during processing and the utility has stopped running.
Corrective Action: Examine the job log for error messages describing the problem. Make any necessary corrections and rerun the utility.
Explanation: The parm input parameter specified in the JCL for the CTDAPRV utility is not valid and the utility has stopped running.
Corrective Action: Correct the invalid input parameter (parm) in the JCL and rerun the job.
Explanation: The parm input parameter for the CTDAPRV utility has already been specified. The parameter which can be specified only once is specified twice in the current statement. The utility has stopped running.
Corrective Action: Remove the extra input parameter from the input parameters stream in JCL and rerun the job.
Explanation: The parm input parameter for the CTDAPRV utility exceeds the maximum allowable length. The utility has stopped running.
Corrective Action: Correct the invalid input parameter (parm) in the JCL and rerun the job.
Explanation: The statement stat is specified for the CTDAPRV utility without any parameters. The utility has stopped running.
Corrective Action: Add the required parameters to the statement in the JCL and rerun the job.
Explanation: This error message indicates that the CTDRETC utility discovered errors in the input parameters. Additional information about the errors is available in the job log.
Corrective Action: Examine the job log for error messages describing the problem. Make any necessary corrections in the input parameters and rerun the utility.
Explanation: The CTDAPRV utility issues this error message when the invoked SORT utility ends with errors. The utility has stopped running.
Corrective Action: Examine the messages issued by the SORT utility to SYSOUT to identify the problem. Make appropriate changes to the JCL and rerun the job.
Explanation: The SHOUT command without parameter EMAIL is specified for the CTDAPRV utility, and the EMAIL destination is not specified for the corresponding Approval entry in the Approval Tree. The utility does not send the SHOUT message and continues to work.
Corrective Action: Specify the EMAIL destination in the Approval Tree or in the input parameter and rerun the job.
Explanation: This information message indicates that the CTDAPRV utility selected nnnnn reports for processing.
Corrective Action: No response required.
Explanation: This information message indicates that the CTDAUTR utility has begun.
Corrective Action: No action is required.
Explanation: This information message indicates that the CTDAUTR utility has finished without errors
Corrective Action: No action is required.
Explanation: This error message indicates that the CTDAUTR utility has finished with errors. The problem is described by previous error messages issued to the job log.
The utility stops.
Corrective Action: Examine the job log for error messages describing the reason for the problem. Fix the problem and rerun the utility.
Explanation: The value of the parm input parameter specified for the CTDAUTR utility is longer then the maximum allowed.
The utility stops.
Corrective Action: Correct the invalid input parameter and rerun the job.
Explanation: The parm input parameter specified for the CTDAUTR utility is not valid.
The utility stops.
Corrective Action: Correct the invalid input parameter and rerun the job.
Explanation: The required parm input parameter for the CTDAUTR utility is missing.
The utility stops.
Corrective Action: Insert the missing parameter to the JCL and rerun the job.
Explanation: The parm input parameter for the CTDAUTR utility has been specified more then once.
The utility stops.
Corrective Action: Delete the extra input parameter from the JCL and rerun the job.
Explanation: The number of USERID input parameters specified for the CTDAUTR utility is more than the allowed maximum number. The utility stops.
Corrective Action: Correct the input parameters and rerun the job.
Explanation: The SORT utility invoked by the CTDAUTR utility ended with errors. The CTDAUTR utility issues this message whenever the SORT utility ends with a return code (rc) other than 0.
Refer to the documentation for your SORT utility for an explanation of the return code (rc) value.
The utility stops.
Corrective Action: To correct this problem, use the following procedure:
Explanation: This error message is issued if the FILE parameter is specified for the CTDAUTR utility when the required action is to receive list of authorized recipients (ACTION=RECIPIENTS). The FILE parameter can be specified only in case the required action is to receive the list of available reports (ACTION=REPORTS).
The utility stops.
Corrective Action: Correct the input parameters and rerun the job.
Explanation: This information message is issued when the CTDAUTR utility has been submitted to receive a list of authorized recipients and all recipients are authorized for the specified User ID (user-id). This situation can occur in the following cases:
The utility ends with a return code of zero without issuing the requested report.
Corrective Action: No action is required.
Explanation: This information message is issued when the CTDAUTR utility has been submitted to receive list of available reports and all available reports are authorized for the specified User ID (user-id). This situation can occur when the user and security exits are missing from the environment specified in the ENV parameter.
The utility ends with a return code of zero and a list of all Control-D reports available from the User files specified in the FILE parameter is issued.
Corrective Action: No action is required.
Explanation: This information message is issued when the CTDAUTR utility has been submitted to receive a list of authorized recipients and no recipients are authorized for the specified User Id (user-id) according to the Control-D Recipient tree and security definitions.
The utility ends with a return code of zero without issuing the requested report.
Corrective Action: No action is required.
Explanation: This information message is issued when the CTDAUTR utility has been submitted to receive a list of available reports and no reports are authorized for the specified User Id (user-id) according to the Control-D Recipient tree and security definitions.
The utility ends with a return code of zero without issuing the requested report.
Corrective Action: No action is required.
Parent Topic |