|
|
|
|
|
This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.
Explanation: Control-V was unable to create an index file.
Even though the index file is not created, the decollated report is produced.
Possible values for rc are shown in the following table:
rc |
Explanation |
|---|---|
16 |
Insufficient memory. |
20 |
Insufficient space on the volumes to create the index file. |
28 |
Size of the index file calculated internally is not big enough for all entries. |
40 |
Dynamic allocation error. |
44 |
Dynamic deallocation error. |
48 |
Sort error. |
Other |
Internal error. |
This message is followed by the REPG06E message.
The index is not created.
Corrective Action: Take appropriate actions to correct the problem associated with the specified return code:
rc |
Explanation |
|---|---|
16 |
Increase the REGION size of the Control-D or Control-V Decollation monitor. |
20 |
Clear space on the volumes defined for index files in Control-V Installation Parameters or add another volume to the Control-V Installation Parameters. |
28 |
First check that definition of every subindex is correctly defined in the decollation mission. If this is not the source of the problem, contact BMC Customer Support with the decollation mission definition and sample pages of the report. |
40 |
For a description of the return code received, see the IBM manual MVS Programming: Authorized Assembler Services Guide. If you cannot resolve the problem, record the return code, internal return code and reason code. Contact BMC Customer Support. |
44 |
Take the same action outlined for return code 40 above. |
48 |
Check the sort messages in the Control-D or Control-V Decollation monitor sysout. If you cannot resolve the problem, record the sort messages and contact BMC Customer Support. |
other |
Record the return code, internal return code and reason code and contact BMC Customer Support. |
Explanation: Option H (Hold), F (Free), D (Delete), R (Rerun) or C (Change) was requested for a Report decollating mission. The status of the mission, as displayed on the Status screen, has not been updated completely by all the Control-D monitors.
This message is relevant only for Report decollating missions that can be processed by any active Control-D monitor (that is, the MONITOR field of the Report decollating mission definition was left blank).
The request is ignored.
Corrective Action: Try again later.
Explanation: The user pressed PF06 in order to specify a new tag note. However, the cursor is not on a report line. When specifying a new tag note, the cursor must point to the report line for which a note will be written.
Corrective Action: Place cursor in the desired position within a report line.
Explanation: PF6 was pressed to define a new tag note. The Control-D Notepad Facility is waiting for further actions. To define a new tag note, specify start and end positions in the string for which a note will be written. Specify start and end positions separately, by setting the cursor in the desired position, and pressing PF6.
Corrective Action: Put cursor at the end of the specified string, or press PF5 to cancel the current tag note specification.
Explanation: Start and end positions for the tag note string are specified on different report lines. In the current release of the Control-D Notepad Facility, start and end positions for the tag note string must be specified in the same report line.
Corrective Action: Specify start and end positions for the tag note string in the same report line.
Explanation: An internal program error was detected by the Control-D Notepad Facility when specifying a new tag note.
Corrective Action: Call BMC Customer Support.
Explanation: The ruler was changed, and there were tag notes defined for the old ruler. After applying the new ruler, tag note strings are moved to other positions.
Specify tag notes after a ruler is defined, verified and applied to a report, because tag notes are related to the applied ruler.
If the strings being moved by a new ruler are related to tag notes, they will not be marked as note strings.
Corrective Action: In order to have these strings marked as note strings in their former positions, press PF6. After that the notes will be available.
Explanation: You must specify the Restore Mission name in the displayed Restore Window when you request restoration of a report.
Corrective Action: Specify the Restore Mission name.
Explanation: The user name specified in the GIVETO Option prompt window is the user name to which the report belongs. The GIVETO Option allows a copy of a report to be given to another user but not to the owner of the report.
Corrective Action: Specify another user name in the GIVETO Option prompt window or cancel the GIVETO request by specifying N (for NO) in the CONFIRM field of the GIVETO window.
Explanation: This information message indicates the normal completion of the GIVETO Option (option G) of the User Report List screen.
Corrective Action: No action is required.
Explanation: This information message indicates that a VIEW request was performed. The text of the message specifies the report name, job name, jobID, user name, file type, and return code.
Corrective Action: No action is required.
Explanation: The FT Control monitor could not load the XCOMJOB module.
The FT Control monitor shuts down.
Corrective Action: Make sure XCOMJOB exists on the STEPLIB DD statement of the CTD2AS4 member in the PROCLIB library.
Explanation: The data set identified by dsn could not be dynamically allocated.
The FT Control monitor shuts down.
Corrective Action: If the DSN name is the AS4LOG file, ensure that the AS4LOG file exists with that data set name. Otherwise, notify BMC Customer Support.
Explanation: XCOM is currently not available.
The FT Control monitor continues its regular cycles, issuing requests to the XCOM server.
Corrective Action: Check XCOM availability. Refer to the Application Program Interface chapter in the XCOM manual. If XCOM stops and restarts between FT Control monitor cycles, the transfer process will continue.
Explanation: The Control-D AS/400 Users Table (CTDAS4US) was not loaded.
The FT Control monitor shuts down.
Corrective Action: Make sure that the library pointed to by the AS4NMDD DD name includes the CTDAS4US member.
Explanation: This message indicates that an invalid MODIFY command was issued.
The FT Control monitor continues without modification.
Corrective Action: Reissue the MODIFY command with the correct syntax.
Explanation: This information message indicates that the FT Control monitor stopped due to operator request. The F CTD2AS4,STOP or P CTD2AS4 command was executed.
The FT Control monitor shuts down.
Corrective Action: Use the S CTD2AS4 command to restart the file Transfer monitor when the report packet transfer process should resume.
Explanation: Attempt to open the IOA Log file failed.
The FT Control monitor shuts down.
Corrective Action: Notify your local INCONTROL administrator.
Explanation: This information message indicates that some or all of the CDAM files of the report to be viewed or printed migrated, and are not immediately available. At installations using DF/HSM, a request for online viewing or printing of a report causes sending direct HSM recall request for the HSM migrated files. Optional wish WD1623 defines whether the running program should wait for request completion or continue running and try to access the report later.
HSM recall request is sent to recall these migrated CDAM files for later access. Then, according to optional wish WD1623, either wait for the request completion or continue running.
Corrective Action: Wait until the recall request has successfully completed. Then, according to optional wish WD1623, either regain access to the report or try again to view the report.
Explanation: Online Viewing Security Exit 4 denied your request to display a report list by setting a non-zero return code when called with function code SELFUNC. Function code SELFUNC normally grants or denies access to display a report list depending on the selection criteria specified on the Option U Selection screen.
Corrective Action: Modify the selection criteria on the Option U Selection screen or contact your IOA or security administrator to determine why the request was denied.
Explanation: Option X to list a report indexes in the Index Window was specified in the Active Report List screen but the selected report has no index.
Corrective Action: Define one or more indexes with DO INDEX statements in the Report Decollation Mission if this report should be indexed.
Explanation: Control-D or V failed to dynamically allocate an index file.
The index file is not allocated.
Corrective Action: For a description of the return code received, see the IBM manual MVS Programming: Authorized Assembler Services Guide. If you cannot resolve the problem, record the reason code and contact BMC Customer Support.
Explanation: The CTVX001 exit, could not retrieve an index value from a non-Control-V index file.
The system stops.
Corrective Action: Contact BMC Customer Support.
Explanation: The function requested during a call to the CTDAMFM module was invalid.
The request fails.
Corrective Action: Specify a valid function for the CTDAMFM module.
Explanation: There was not enough memory in the CTDAMFM module to perform GETMAIN.
The request fails.
Corrective Action: Specify the region size as 0.
Explanation: An error occurred during an attempt to load the CTDAMFM module. Either the CTDAMFM module is not in the appropriate library, or there was not enough space to load it.
Formatting of the Active Mission file (AMF) stops.
Corrective Action: Ensure that the CTDAMFM module exists in the appropriate library, and that there is enough space to load it.
Explanation: The DBFILE parameter in the CTDDIB utility is not set to ACT, PRM, HST, MIG or MG n. The CTDDIB utility creates an index file from an existing data file. The user tried to run the CTDDIB utility without a valid DBFILE parameter.
The CTDDIB utility terminates.
Corrective Action: Rerun the CTDDIB utility after setting the DBFILE parameter to ACT, PRM, HST, MIG, or MGn depending on the type of file for which the index is being created, as follows:
Explanation: An invalid date is specified in the EXPDATE parameter or this parameter is specified in the PROD mode, although it must only be specified in the TEST mode.
The CTVCLMIG utility ends with a return code of 12.
Corrective Action: Correct the EXPDATE parameter and rerun the utility.
Explanation: This information message identified that the CTVDELI utility began execution. This utility scans the Migrated User Report List file and erases index files and index records that are no longer needed.
Corrective Action: No action is required.
Explanation: This information message indicates that the CTVDELI utility finished executing without errors. This utility scans the Migrated User Report List file and erases index files and index records which are no longer needed.
Corrective Action: No action is required.
Explanation: The CTVDELI utility ended with errors. This utility scans the Migrated User Report List file and erases index files and index records that are no longer needed. The problem is described in one or more preceding messages.
The CTVDELI utility terminates with a return code of 08.
Corrective Action: Check preceding error messages, correct the problem, and rerun the job.
Explanation: The parm parameter is not valid for the CTVDELI utility. This message is issued by the CTVDELI Control-V utility, which scans the Migrated User Report List file, and erases index files that are no longer needed.
The CTVDELI utility terminates with a condition code of 08.
Corrective Action: Correct the parameter syntax and resubmit the job. For more information, see the CTVDELI utility in the INCONTROL for z/OS Utilities Guide.
Explanation: A subparameter of the parm parameter is missing. This message is issued by the CTVDELI Control-V utility, which scans the Migrated User Report List file, and erases index files that are no longer needed.
The CTVDELI utility terminates with a condition code of 08.
Corrective Action: Correct the parameter syntax, and resubmit the job. For more information, see the CTVDELI utility in the INCONTROL for z/OS Utilities Guide.
Explanation: The parm parameter is specified more than once in the CTVDELI utility. This message is issued by the CTVDELI Control-V utility, which scans the Migrated User Report List file, and erases index files that are no longer needed.
The CTVDELI utility terminates with a condition code of 08.
Corrective Action: Remove the redundant parameter, and resubmit the job. For more information, see the CTVDELI utility in the INCONTROL for z/OS Utilities Guide.
Explanation: Open of the Control-V Migrated User Report List file failed. This file is referenced by the DAMIG DD statement. This message is issued by the CTVDELI utility, which scans the Migrated User Report List file and erases index files that are no longer needed.
Possible causes are:
The CTVDELI utility terminates with a condition code of 08.
Corrective Action: Correct the JCL for the CTVDELI utility, and rerun the job. For more information, see the CTVDELI utility in the INCONTROL for z/OS Utilities Guide.
Explanation: Open of the Parameters file for the CTVDELI utility failed. Possible causes are:
The CTVDELI utility terminates with a condition code of 12.
Corrective Action: Correct the JCL, and rerun the job. For more information, see the CTVDELI utility in the INCONTROL for z/OS Utilities Guide.
Explanation: The SORT utility invoked by the CTVDELI utility failed to open the data set referenced by the ddName DD statement.
The CTVDELI utility stops.
Corrective Action: Ensure all DD statements are valid, and rerun the CTVDELI utility. For more information, see the CTVDELI utility in the INCONTROL for z/OS Utilities Guide.
Explanation: The internal sort program ended with errors. This message is issued by the CTVDELI utility, which scans the Migrated User Report List file and erases index files that are no longer needed. The utility uses the site sort program.
The CTVDELI terminates with a condition code of 08.
Corrective Action: Check the explanations of the sort messages for the job in the manual for your sort facility.
Explanation: This information message indicates that the CTVDELI utility is waiting for a CTDDELRP job, a restore job, or another CTVDELI job to terminate.
The CTVDELI utility scans the Migrated User Report List file, and erases index files that are no longer needed. To ensure data integrity, CTVDELI cannot run concurrently with the CTDDELRP utility, a restore job, or another CTVDELI job.
When the contending job terminates, the CTVDELI utility resumes processing.
Corrective Action: No action is required.
Explanation: The CTVDELI utility did not receive input parameters by way of the SYSIN DD statement. The CTVDELI utility scans the Migrated User Report List file, and erases index files that are no longer needed. The utility requires input parameters indicating which actions it should perform.
The CTVDELI utility terminates with a condition code of 08.
Corrective Action: Verify that input parameters are specified by way of the SYSIN DD statement. Rerun the CTVDELI utility.
Explanation: This information message indicates that the CTVDELI utility is running in SIMULATION mode. In SIMULATION mode, the CTVDELI utility produces a report that indicates which indexes would have been deleted if the utility were running in PRODUCTION mode.
Corrective Action: Examine CTVDELI output to determine if the proper indexes would have been deleted from disk. Make any changes required to prevent the incorrect deletion of indexes that are needed for any reason. Rerun the utility in PRODUCTION mode to actually delete unneeded indexes from disk.
Explanation: The CTVDELI utility encountered index dsn, which could not be located, possibly because the data set is not cataloged. The CTVDELI utility scans the Migrated User Report List file and erases unneeded index files.
The index with the data set name dsn is not deleted.
Corrective Action: Determine why the data set could not be located. Correct the problem. Rerun the CTVDELI utility if necessary.
Explanation: The CTVDELI utility encountered the dsn index, which could not be deleted. This message is issued by the CTVDELI utility, which scans the Migrated User Report List file, and erases index files that are no longer needed.
Possible causes include the following:
The dsn index is not deleted.
Corrective Action: Determine why the data set could not be deleted. Correct the problem. Rerun the job if necessary.
Explanation: The CTVDELI utility encountered the dsn index, which could not be uncataloged. This message is issued by the CTVDELI utility, which scans the Migrated User Report List file, and erases index files that are no longer needed.
The index is not uncataloged.
Corrective Action: Determine why the data set could not be uncataloged. Correct the problem. Rerun the job if necessary.
Explanation: This information message indicates that no values of the specified index appear in the user’s report.
Corrective Action: No action is required.
Explanation: A migrated report could not be accessed because the media to which it was migrated was not found. The $SYSDATA entry that corresponds to this migrated report specifies a migrated media which does not appear in the IOASPRM.
The migrated report is not accessed.
Corrective Action: Have your INCONTROL administrator correct the IOASPRM to reference the migrated media that appears in the $SYSDATA entry.
Explanation: The user attempted to handle (view, print, and so on) a report by means of a user entry but no corresponding $SYSDATA entry was found. The $SYSDATA record was probably deleted manually.
The user cannot view, print, and so on, the report.
Corrective Action: No action is required.
Explanation: The user entered an invalid value. The only values that are valid for this field are Y, N, or B.
Corrective Action: Correct the value entered.
Explanation: The value in the field is not valid. The value in this field must be from 1 through 12.
The SORT command is not performed.
Corrective Action: Correct the value specified for this field, and try again.
Explanation: The value that specifies the sort order is not valid. The value that specifies the sort order must be A (ascending) or D (descending).
The SORT command is not performed.
Corrective Action: Enter A or D to specify the sort order, and try again.
Explanation: More that five fields specify the sort. The SORT command supports a maximum of five sort fields.
The SORT command is not performed.
Corrective Action: Redefine the sort using a maximum of five fields, and try again.
Explanation: The sort field number is invalid, or the sort order, or both. Each field number must be a value from 1 through 12, and the sort order must be either A (ascending) or D (descending).
The SORT command is not performed.
Corrective Action: Correct the values, and try again.
Explanation: The sort field number is missing. At least one sort field, and no more than five, must be specified.
The SORT command is not performed.
Corrective Action: Enter at least one value to specify the sort field, and no more than five, and try again.
Explanation: An internal error occurred in the sort program. At least one sort field, and no more than five, must be specified.
The SORT command is not performed.
Corrective Action: Ask your INCONTROL administrator to report this error to BMC Customer Support.
Explanation: Attempt to edit a ruler failed, because no report entry exists that corresponds to the ruler.
Corrective Action: Either create a report entry that corresponds to the selected ruler, or create a ruler for the report entry you would like to edit by specifying ‘E’ next to the report entry.
Explanation: The rulerName print ruler was not located. A print ruler with the specified name was not defined or the ruler name was misspelled.
The report is not printed.
Corrective Action: Verify that the desired ruler exists and is spelled correctly. If necessary, define the ruler, use another ruler that is already defined, or print the report without a ruler.
Explanation: The SPAGE command was specified during viewing of a report with an index. Command SPAGE is not supported for viewing a report with an index.
The command is not performed.
Corrective Action: To print a report section pointed to by an index value, use either of the following:
Explanation: This information message indicates that the command VALUE was entered to display the currently selected index value, but no index value had been used to view the report. If an index value is not used to view a report, the whole report is viewed and this command is not applicable.
The command is not performed.
Corrective Action: No action is required.
Explanation: The value of the TO PAGE parameter specified in the Print window is greater than the number of pages in the reportName report. The maximum value for the TO PAGE parameter is the number of pages in the report.
The reportName report is not printed.
Corrective Action: Specify a valid TO PAGE value in the Print window, and try again.
Explanation: Tag notes for the report being viewed cannot be accessed because of an internal error. Each tag note is associated with a string in the report. The line numbers for the page are not correct. Therefore, the tag note strings cannot be located.
The tag notes and associated strings are not displayed.
Corrective Action: Record the report for which the error occurred and the actions taken while viewing the report. Contact BMC Customer Support.
Explanation: The tag notes of the report cannot be accessed because of an internal error. Each tag note is associated with a string in the report. The page number in which the string appears was not calculated correctly because of an internal error. Therefore, the tag note strings cannot be located.
The tag notes and associated strings are not displayed.
Corrective Action: Record the report for which the error occurred and the actions taken while viewing the report. Contact BMC Customer Support.
Explanation: A tag note cannot be created for the specified string. Each tag note is associated with a string in the original report, before it was edited by a Control-D ruler.
A tag note cannot be associated with any of the following types of strings:
The Notepad window is not displayed for note creation.
Corrective Action: Choose a different string to associate with the tag note.
Explanation: The value $SYSDATA was specified in the USER parameter in display type J of the Control-D or Control-V USER REPORTS ENTRY PANEL. It is not possible to display $SYSDATA records when using display type J (the JOB ARCHIVE display).
The User Report list is not displayed.
Corrective Action: Specify a valid user name or leave the USER parameter empty. To display $SYSDATA records, change the display type.
Explanation: Attempted to view a report stored in a CDAM file failed because at least one CDAM file extent is missing. It was probably deleted from the disk manually or by another process.
The report is not displayed.
Corrective Action: Attempt to find and restore any missing file extents.
Explanation: WRAP was requested when SHOWCC was turned OFF. SHOWCC must be ON, when WRAP is requested.
WRAP is not activated.
Corrective Action: Set SHOWCC ON, and request WRAP again.
Explanation: WRAP was specified for a report when a ruler was turned ON. WRAP is not available when a ruler is turned ON.
WRAP is not activated.
Corrective Action: Turn OFF the ruler to use WRAP.
Explanation: An internal error caused the application to try to create an empty note, or a note longer than 80 characters. A note cannot be empty or longer than 80 characters.
The note is not created.
Corrective Action: Ask your INCONTROL administrator to contact BMC Customer Support for assistance.
Explanation: An error occurred while information was being read from the fileName CDAM file. The return code (rc) indicates why the error occurred.
Valid values for rc, and their explanations, are:
Return Code |
Explanation |
|---|---|
4 |
No data found |
8 |
No space for data vector |
12 |
Error during access of the active user file |
20 |
Invalid function |
24 |
Internal error in converting vsa |
28 |
Insufficient memory to load the note pad |
32 |
ENQ (enqueue) or dequeue error |
36 |
USER not authorized to add, delete or update note |
40 |
Record to replace or delete not found |
080204 |
CDAM processing error. For more details, see CTD922E or CTD926E messages in the job log. |
The report is not displayed.
Corrective Action: Ask your INCONTROL administrator for help.
Explanation: This information message is issued if a recipient was added to the ADDITIONAL USER field.
ACT is the Active User Reports file.
PRM is the Permanent User Reports file.
Corrective Action: No action is required.
Explanation: This information message is issued if a recipient was deleted from the ADDITIONAL USER field.
Corrective Action: No action is required.
Explanation: This information message indicates that the ADDITIONAL USER field was modified.
Corrective Action: No action is required.
Explanation: An error occurred during a read of a CDAM file. The return code (rc) indicates why the error occurred.
Valid values for rc, and their explanations, are:
Return Code |
Explanation |
|---|---|
4 |
End of data sets |
8 |
Point error |
12 |
Get error |
16 |
Unrecognized request |
20 |
Allocation error |
24 |
Open error |
28 |
Subsystem not operational |
32 |
Wrong data read from the file |
36 |
Unrecognized cache routine name |
56 |
Invalid media specified for report |
The file is not accessed.
Corrective Action: Ask your INCONTROL administrator for assistance.
Explanation: A CDAM request was not performed because the CDAM subsystem was not active.
The request is not performed.
Corrective Action: Run the IOASINIT procedure to start the CDAM subsystem.
Explanation: An error occurred during access of a Note record noterecord in the Active User file. A return code (rc) of 32 indicates an error during access of the Active User file.
The note is not accessed.
Corrective Action: Run the CTDGIR utility to check the integrity of the Active User file.
Explanation: This information message indicates that the CTVJAR Job Archiving utility has started.
Corrective Action: No action is required.
Explanation: This information message indicates that the CTVJAR Job Archiving utility ended successfully.
Corrective Action: No action is required.
Explanation: This information message indicates that the CTVJAR Job Archiving utility failed. Other messages generated in response to the failure describe the cause for the failure.
Job archiving ends.
Corrective Action: Examine all messages issued by the Job and correct the failure. If necessary, correct the input and rerun the CTVJAR Job Archiving utility.
Explanation: This information message indicates that the CTVJAR Job Archiving utility was run in TEST mode. CTVJAR was activated using the TEST parameter in the PARM field of the executive statement. When CTVJAR is active in TEST mode, no updates are performed to the Active User file. Only a report is created.
Note:
If the user sets the SYNC parameter to YES in CTVJAR, active generic decollation will close the recently created CDAM file. The active generic decollation will wait for new decollations until the CTVJAR Job Archiving utility is terminated.
No updates are performed to the Active User file. A report is created.
Corrective Action: Do the following:
Explanation: The CTVJAR Job Archiving utility received an invalid return code from the SORT utility. CTVJAR called the SORT utility to sort the entry being consolidated, but the sort failed.
In this message, rc is the invalid return code
The system terminates the CTVJAR utility.
Corrective Action: Examine the messages generated by the SORT utility for a description of the problem. Correct the problem and rerun the CTVJAR utility.
Explanation: The CTVJAR Job Archiving utility was unable to open the file referenced by the SORTIN DD statement. Either the SORTIN DD statement is missing from the JCL of CTVJAR, or the definition of the SORTIN DD statement is invalid.
The CTVJAR utility terminates.
Corrective Action: Correct the DD statement and rerun the CTVJAR utility.
Explanation: Control-V called the CTDRPUF routine to create a report entry in the Active User file of the newly archived report. However, CTDRPUF was unable to create the new report.
In this message, rc is the CTVJAR return code
CTVJAR processing continues with the next report.
Corrective Action: Check the IOA log for all messages generated for this failure. If the cause for the failure remains unclear, contact BMC Customer Support.
Explanation: There are invalid parameters in the SYSIN file. This is a summary message. Preceding messages clarify the error. The CTVJAR Job Archiving utility issues the return code rc.
The system terminates job archiving.
Corrective Action: Check all messages generated for this error. Correct the input parameters, and rerun the CTVJAR Job Archiving utility.
Explanation: The user attempted to execute the CTVJAR Job Archiving utility without specifying the parm parameter. The parm parameter is mandatory for CTVJAR.
The CTVJAR Job Archiving utility terminates.
Corrective Action: Add the parm parameter and rerun the CTVJAR utility.
Explanation: An invalid parameter was specified in the parameter statement for the CTVJAR Job Archiving utility.
In this message, parm is the invalid parameter that was specified.
The CTVJAR Job Archiving utility terminates.
Corrective Action: Correct the values in the PARM statement, and rerun the CTVJAR Job Archiving utility.
Explanation: The parm parameter was specified more than once in the input for the CCTVJAR Job Archiving utility. The parm parameter can be specified only once in the input for this utility.
In this message, parm is the redundant parameter specified by the user.
The CTVJAR Job Archiving utility terminates.
Corrective Action: Ensure that the parm parameter is specified only once, and rerun the CTVJAR Job Archiving utility.
Explanation: A later date value was specified in FODATE than in TODATE in the input for the CTVJAR Job Archiving utility. The FODATE and TODATE parameters indicate a date range for reports to be consolidated by CTVJAR. A date range is valid only if FODATE is earlier than, or the same as, TODATE.
The CTVJAR Job Archiving utility terminates.
Corrective Action: Ensure that the date value specified for FODATE is not later than the date value for TODATE. Rerun CTVJAR.
Explanation: An invalid date value was specified in the ddName DD statement in the input for the CTVJAR Job Archiving utility.
The CTVJAR Job Archiving utility terminates.
Corrective Action: Check and correct the date value and rerun the CTVJAR utility.
Explanation: Control-V found a SYSDATA record for the fileName CDAM file. However, the fileName CDAM file contained no user records that corresponded to the SYSDATA record. In the input for the CTVJAR Job Archiving utility, the user specified a CDAM file that contained no user records in the input for the CTVJAR utility.
In this message, fileName is the name of the problematic CDAM file.
The CTVJAR utility ignores the SYSDATA record, and continues processing normally.
Corrective Action: Check why the user records are missing. If the user records were deleted using the U screen, restore user records from a backup.
Explanation: The CTVXVAL internal routine was unable to process the indexFile index file.
The system skips the index file, and continues processing.
Corrective Action: To determine the cause, check the other messages generated by the failure of CTVXVAL.
Explanation: An internal routine failed with a return code of 08. The CTVJAR Job Archiving utility uses the CTDTRE routine to determine the validity of each user name supplied by the user for the consolidated report.
The CTVJAR utility terminates.
Corrective Action: Determine the cause by checking preceding error messages generated by the failure. Verify that the user tree is properly defined and rerun the CTVJAR utility.
Explanation: The userName user name could not be found by the CDTRE utility. The CTVJAR Job Archiving utility uses the CTDTRE utility program to determine the validity of the user name supplied by the user for the consolidated report. The userName user name was specified by the USER parameter of the CTVJAR utility, but could not be found in the Control-D recipient tree.
CTVJAR terminates.
Corrective Action: Correct the user parameter and rerun CTVJAR.
Explanation: The CTVJAR Job Archiving utility terminated execution without creating consolidated reports. This occurred under option SYNC=NO, because too many CDAM datasets matching selection criteria are opened by the Control-D decollation monitor.
Corrective Action: Execute the utility with parameter SYNC=YES.
Explanation: This information message indicates that the SPAGE command with the INCLUDE parameter was issued during online viewing of a report. The range of pages identified in the message is printed after exit from online viewing.
Corrective Action: No action is required.
Explanation: This information message indicates that the SPAGE command with the EXCLUDE parameter was issued during online viewing of a report. The range of pages identified in the message is not printed after exit from online viewing.
Corrective Action: No action is required.
Explanation: This information message indicates that the SPAGE RESET command was issued during online viewing of a report. No pages are printed after exit from online viewing.
Corrective Action: No action is required.
Explanation: The specified error occurred while a report was being viewed online, during processing of the SPAGE command.
Possible values of text are:
The SPAGE command is not processed.
Corrective Action: If possible, fix the problem and try again.
Where space is a problem, try increasing the REGION size.
If these measures fail, do the following:
Explanation: An attempt has been made to view a $SYSDATA record in the Permanent file, but it does not exist in that file.
Corrective Action: No action is required.
Explanation: An error occurred while accessing the Global Index Database above DB2.
The variables in this message are:
Valid values for rc, and their explanations, are:
Return Code |
Explanation |
|---|---|
12 |
Invalid function |
20 |
Not enough storage |
48 |
SETPATH was not issued before value accessing |
56 |
Error opening the CTDGIDB2 member |
60 |
Invalid parameter found in the CTDGIDB2 member |
64 |
Obligatory parameter missing from the CTDGIDB2 member |
68 |
Duplicate parameter found in the CTDGIDB2 member |
72 |
More than 10 fields found in a PATH description in the CTDGIDB2 member. |
76 |
DB2 open error |
80 |
Accessing path not present in the CTDGIDB2 member |
84 |
SQL error |
85 |
SQL error if time-out occurs |
88 |
Error in loading the DB2 interface module |
The system action depends on the identity of the component that was accessing the Global Index database. Usually, the current routine terminates. Additional messages clarifying the source of the error are written to the IOA Log file before this message.
Corrective Action: Search the IOA Log file and the relevant job log for messages clarifying the source of the error. Correct the error and restart IOA application server. If the error persists, contact BMC Customer Support.
Explanation: The Global Index facility was invoked with an invalid function.
The request is not performed.
Corrective Action: Request a valid function for the Global Index facility.
Explanation: A request for an index value was performed before a SETPATH request. SETPATH must be performed before the index value is requested
The SETPATH request fails.
Corrective Action: Put the SETPATH request before the request for an index value, and try again.
Explanation: An error occurred while opening the CTDGIDB2 member.
The Global Index request is not performed.
Corrective Action: Search the relevant job log for messages clarifying the source of the error. Determine whether the CTDGIDB2 member exists in the library pointed to by the DADPARM DD statement. After resolving the problem, either restart the IOA application server or rerun the job, depending on which component was accessing the Global Index database.
Explanation: An invalid statement statement was detected in the CTDGIDB2 member.
The Global Index request is not performed.
Corrective Action: Correct the CTDGIDB2 member and either restart the IOA application server or rerun the job, depending on which component is accessing the Global Index database.
Explanation: An obligatory parameter is missing in the CTDGIDB2 member.
The obligatory parameters are:
The Global Index request is not performed.
Corrective Action: Correct the CTDGIDB2 member and either restart the IOA application server or rerun the job, depending on which component is accessing the Global Index database.
Explanation: A duplicate statement duplic_stmt was detected in the CTDGIDB2 member, although this statement can be specified only once.
The Global Index request is not performed.
Corrective Action: Correct the CTDGIDB2 member and either restart the IOA application server or rerun the job, depending on which component is accessing the Global Index database.
Explanation: Too many fields are specified for path number num. A maximum of 10 fields can be specified.
The Global Index request is not performed.
Corrective Action: Correct the CTDGIDB2 member and either restart the IOA application server or rerun the job, depending on which component is accessing the Global Index database.
Explanation: An error occurred while opening the DB2 subsystem.
The variables in this message are:
The Global Index request is not performed.
Corrective Action: For the explanation of the return and reason codes, refer to your DB2 documentation. If necessary contact your DB2 administrator.
Explanation: Either the requested index path or the DB2 table was not found in the CTDGIDB2 member.
The variables in this message are:
The Global Index request is not performed.
Corrective Action: Do the following:
Explanation: DB2 issued a SQL error code.
This message (CTDGIHE) is followed by the DB2 messages, which provide the error code and a detailed explanation of the error.
The Global Index request is not performed.
Corrective Action: Do the following:
Explanation: A GETVSA request was issued, but a GETVAL request had not been issued before it.
The possible cause is an internal error in the application that calls the CTDGID interface routine.
The Global Index request is not performed.
Corrective Action: Contact your INCONTROL administrator.
Explanation: An SQL error occurred during inserting line to DB2 table when decollation mission loads data to Global Index database. Control-D decollates the report without loading data to Global Index database. The decollation mission is set to status ENDED- NOT "OK" after it is completed.
Corrective Action: Do the following actions:
Parent Topic |