This section contains the following topics:
This chapter lists all DC messages.
Reason:
MAPOUT ERROR ON USER MAP; #MREQ RC=14 was issued because a disconnect (S005) condition occurred when it was doing the MAPOUT for VARMI100.
Action:
None.
Reason:
Startup failed with a DC200005 message.
Action:
Check the JCL for the correct journal file names, and for the backup journal name. This might also occur if the system failed while a journal dump (DSEXJNL1) was running.
Note: If a journal is dumping when a system failure occurs, you may receive the DC200005 message followed by an ABEND. Try to restart CA Dispatch, and if a WARMSTART SUCCESSFUL message is issued, you can shut down the system with a STOPCADS command and run DSEXJFIX. If the system "hangs" after the WARMSTART SUCCESSFUL message you can cancel CA Dispatch and then run DSEXJFIX and DSEXPFIX.
Reason:
Message DC200006 is issued at CA Dispatch startup time.
Action:
CA Dispatch database files are currently locked, probably with a 0966 return code. See the 0966 recovery procedures outlined in this guide.
Reason:
When starting CA Dispatch the WARMSTART task fails with U3962 abend and the DC203006 is displayed. This means that information is missing on the current Journal files.
Action:
The only way to recover is to use your offloaded journal tapes and do a rollback using DSEXBR08. Follow the rollback with the DSEXJFIX job to initialize the current journals.
For more information, see the Rollback section of the Backup, Restore and Recovery chapter in the Systems Programmer Guide.
Reason:
This message is informational only and might be seen during CA Dispatch shutdown. It is normal and no cause for concern.
Action:
None
Reason:
This message is informational only and might be seen during CA Dispatch shutdown. It is normal and no cause for concern.
Action:
None
Reason:
The date in the dialog load module does not match the date stored in the MODULE-067 record in the dictionary for this process. Therefore, the source lines for the abend have not been displayed on the Dialog Abort Information screen.
Action:
None.
Reason:
An error occurred in the <process-name version-number> of dialog <dialog-name>, which caused abnormal termination of the dialog. The messages that follow in the print log give additional diagnostic information.
Action:
None if prior message DC171017 was issued with RC=14; otherwise, contact Technical Support and provide the text of the message.
Reason:
This message is a continuation of message DC466014 above. Abnormal termination of the dialog occurred at offset <hex-offset> into the dialog and at the source sequence number indicated for the process, which was named in message DC466014. Additional diagnostic information may follow.
Action:
None if prior message DC171017 was issued with RC=14; otherwise, contact Technical Support and provide the text of the message.
Reason:
While you were viewing information on a screen, another user may have updated it.
Action:
Press PF2.
Reason:
The question marks that appear on your screen indicate fields with invalid or incomplete entries.
Action:
Access the help text for information about correcting these fields. Press PF1 to access the help text and then press PF7 to go to the screen with the explanations.
Reason:
You selected an option on a menu screen that is not available.
Action:
Enter the correct option.
Reason:
You successfully updated the CA Dispatch database with either report distribution or status information.
Action:
No action required.
Reason:
You attempted to use a screen that requires Sysgen information be entered first on the appropriate Sysgen screen.
Action:
Supply the required Sysgen information.
Reason:
You have not specified an option on a menu or a scroll screen.
Action:
Select the option you want.
Reason:
You are adding either a base report, a report recipient, or a recipient record to the database. This message is also issued from the Online Viewing Recipient Selection Screen (VOVMI300) if an OLV user record was not defined.
Action:
Press PF10 to add or PF2 to cancel.
Reason:
You did not specify a report name on a scroll screen.
Action:
Enter the report name in the report field. If you cannot remember the report name, scroll through the screens until you find it.
Reason:
You pressed PF10 to add a record to the database, but the record already exists. Your request to add was ignored.
Action:
No action required.
Reason:
Incomplete attempt to delete a record from the database. Before CA Dispatch can delete this record, you must confirm the deletion by pressing Enter.
Action:
Press Enter. If you do not want to delete the record, press PF2 to cancel.
Reason:
You are deleting a record from the database. Before CA Dispatch can complete this process, the deletion must be confirmed. You pressed Enter and CA Dispatch deleted the record.
Action:
No action required.
Reason:
You are adding either a base report, a report recipient, or a recipient record to the database, and you pressed PF10 to complete the function. CA Dispatch is informing you that it has added the record to the database.
Action:
No action required.
Reason:
You entered data in fields on a report recipient or a recipient screen, but the record does not yet exist in the database.
Action:
Use the ADD function to add the record or PF2 to cancel.
Reason:
The user cannot access a recipient list because none was created.
Action:
Add a list of valid recipients for this user.
Reason:
You attempted to view information on recipients of a base report, but no recipients were defined for the report.
Action:
Enter CANCEL.
Reason:
You defined a sequence of report pages to be printed for a particular recipient through the Report Definition Screen, Pages (VRDMU140), but the starting and ending definitions are out of sequence.
Action:
Check your input and correct the error.
Reason:
The requested printing of the label will occur as soon as the printer is operable and available.
Action:
No action required.
Reason:
You are viewing all recipients of microfiche copies of a base report and are at the end of the recipient list.
Action:
No action required.
Reason:
You are attempting to define a recipient of microfiche copies of a base report, but microfiche copies have already been assigned for this recipient.
Action:
Enter CANCEL.
Reason:
CA Dispatch attempted to print a label for a bundle or a report, but could not access the printer.
Action:
No action required.
Reason:
When defining labels through VRDMU700, you must specify the device or class on which you want the label to print.
Action:
Specify the device or class.
Reason:
You are entering fields on the Report Recipient Definition Screen (Fiche) (VRDMU160), but the record does not yet exist on the database.
Action:
Enter the ADD command to add or CANCEL to cancel the operation.
Reason:
You successfully updated the Delivered Time on the Feedback Update Screen (VRDMU500).
Action:
No action required.
Reason:
You are inquiring into the CA Dispatch status screens, but no status information is available for the bundles or reports about which you are inquiring.
Action:
No action required.
Reason:
You are inquiring into the CA Dispatch report definition or status screens.
Action:
Enter the report name in the report field. If you cannot remember the report name, look through the scroll screens until you find it.
Reason:
You attempted to execute a function for which you do not have password authority.
Action:
Enter CANCEL.
Reason:
User Sysgen information defined to the database is incomplete.
Action:
Select Option 9 to update Sysgen information.
Reason:
User Sysgen information defined to the database is incomplete.
Action:
Select Option 0, Option 1, or both to update Sysgen information.
Reason:
You attempted to delete a recipient record from the database through the Recipient Definition Screen (VRDMU310), but reports are still defined to the recipient..
Action:
You must first delete all those reports assigned to the recipient through the appropriate Report Recipient Definition Screens (VRDMU130). To display a list of the reports assigned to the recipient, press PF5 while viewing the Recipient Definition Screen (VRDMU310).
Reason:
You pressed PF5 while viewing the Recipient Definition Screen (VRDMU310) to display a list of the reports assigned to the recipient, but there are no reports assigned to him/her.
Action:
No action required.
Reason:
You entered numbers incorrectly.
Action:
Correct the numbers in the field where the cursor is located.
Reason:
You are on the first page of a scroll screen.
Action:
No action required.
Reason:
You are on the last page of a scroll screen.
Action:
No action required.
Reason:
You are on the only page of a scroll screen.
Action:
No action required.
Reason:
When inquiring into the status of a bundle, CA Dispatch showed that no reports were queued to that bundle.
Action:
No action required.
Reason:
The particular report about which you are inquiring using the Active Recipients Report Status Screen (VRDMI830) has not yet been queued to this bundle.
Action:
No action required.
Reason:
There are no reports queued to the bundle that you are inquiring about.
Action:
No action required.
Reason:
You requested to see a list of the active bundles using the Active Bundles Status Screen (VRDMU820), but there are no active bundles.
Action:
No action required.
Reason:
You pressed a function key in order to move to the next level deeper into the screens, but before you can do this you must add the information that you entered on this screen to the database.
Action:
Enter the ADD command to add and try the function key again.
Reason:
You pressed PF8 on the Report Recipient Definition Screen (VRDMU160) to call up the next offline fiche recipient, but there are no recipients of offline fiche.
Action:
If you are defining a recipient, add by entering the ADD command or enter the Cancel command.
Reason:
To delete information from the CA Dispatch database, you must use the DELETE command.
Action:
Enter the Delete command.
Reason:
You attempted to display status report information and there are no status reports on the database.
Action:
Enter the Cancel command.
Reason:
You inquired about the status of a particular report, but no status records exist on the CA Dispatch database.
Action:
No action required.
Reason:
You inquired into the status of a report and requested information on the next job through PF5 or PF6 of the status screen (VRDMI410), but there are no more job status records.
Action:
No action required.
Reason:
You inquired into the Recipient Status Screen (VRDMI420) for status information on a certain recipient's piece of a base report, but there is no status information available on that recipient.
Action:
Enter the Cancel command.
Reason:
You requested a specific report and it does not exist on the database or you did not define the PRINTER/*PRINTER definition.
Action:
Define PRINTER/*PRINTER report definition if needed.
Reason:
You requested a display of information on a particular report recipient and the recipient does not exist on the database.
Action:
No action required.
Reason:
You are requesting report status information for a recipient, but there is none.
Action:
No action required.
Reason:
You are inquiring into a series of status records; this record is the first of multiple records.
Action:
No action required.
Reason:
You are inquiring into a series of status records; this record is the last of multiple records.
Action:
No action required.
Reason:
You selected Option 6 of the Sysgen Option Menu to "Initialize as ENF checkpoint."
Action:
No action required.
Reason:
You are attempting to return a tape to the CA Dispatch scratch pool, but not all the archived data sets have been deleted from the tape.
Action:
Either do not return the tape to the pool or delete the remaining data sets.
Reason:
A user has attempted to View or Print a Distributed file from Dispatch Online Viewing (screens VOVMI010 or VOVMI310).
Action:
Use Output Management Web Viewer to view or print this report.
Reason:
The CA Dispatch Distribution task has encountered a report that caused an I/O error. This may mean that the report is incomplete. l nnnnnnnn represents the JES ID; l rrrrrrrr represents the report name; l jjjjjjjj represents the job name. In addition to this message, I/OE will appear in the last four positions of the report description field of the printed output and the message +I/O ERROR+ will appear for each entry on the Manifest Report with an I/O error.
This message can also be caused by an empty data set and will not have a JES number, report or job name.
Action:
No action required.
Reason:
You selected a particular maildrop and either entered a maildrop name that is not defined to the database or you did not place your cursor in the proper position on a scroll screen.
Action:
Check the maildrop name or the position of the cursor.
Reason:
You are attempting to copy an address from one maildrop to another through the Maildrop Address Screen (VSGMU135), but you specified a maildrop name that is invalid.
Action:
Check to see if you have the correct maildrop name and reenter the information.
Reason:
You are attempting to copy an address from one maildrop to another through the Maildrop Address Screen (VSGMU135). CA Dispatch shows you the address for your confirmation before it updates its database.
Action:
Press Enter to update the database or enter CANCEL.
Reason:
The batch program PURGE has deleted some or all of the bundle information in which this report was originally included. At this point, we no longer have complete bundle status information.
Action:
No action required.
Reason:
The report you are trying to extract is contained on the volume currently being used by the archive system.
Action:
Change the current volume on VSGMU210 by blanking out the VOLSER field.
Reason:
The job name you selected is not defined in the database.
Action:
Verify your selection and reenter it.
Reason:
You incorrectly entered the JES number.
Action:
Verify the JES number and reenter it correctly.
Reason:
Database report statistics were not found for your selection.
Action:
Verify your selection and reenter it.
Reason:
You incorrectly entered the JES number.
Action:
Verify the JES number and reenter it correctly.
Reason:
You are trying to extract a report from the current archive tape.
Action:
Press Enter to allow extract from the current archive tape or enter CANCEL to cancel the request. Note that the extract will only occur after the archive task is ended.
Reason:
You are trying to add a DJDE record when the default process has not been built yet.
Action:
Go to the SYSGEN screen and create the defaults (the IDEN record will be built when screen VSGMU170 is entered).
Reason:
An informational message stating that you have successfully reprinted a report from Online Viewing.
Action:
None.
Reason:
The User Sysgen option is set to N. X1 is invalid for this user ID.
Action:
None, unless the report administrator wishes to change the option on the VSGMU135 screen.
Reason:
CA IDMS temporary file can not be accessed.
Action:
Exit from OLV process and retry. If problem persists, increase the size of the scratch file area.
Reason:
No CA IDMS storage area is available.
Action:
The IDMS storage pool will have to be increased. Exit from the OLV process, then retry. If the problem persists, increase the size of the scratch file area.
Reason:
An invalid command was entered.
Action:
Reenter a valid command.
Reason:
Invalid additional parameters were entered for a valid command.
Action:
Reenter or correct the command with a valid 1st or 2nd parameter.
Reason:
PF7 (page up) was pressed when page 1 was being displayed.
Action:
No action required.
Reason:
PF8 (page up) was pressed when the last page was being displayed.
Action:
No action required.
Reason:
Cursor must be on a valid line (after line 2, and a valid line of the report).
Action:
Reset the cursor to a valid line, and press Enter.
Reason:
The Find command search string was invalid or not found on the pages selected to be searched.
Action:
Enter the correct search string or increase the number of pages to be searched.
Reason:
The cursor must be on a print line in the report.
Action:
Reset the cursor to a valid line, and press Enter.
Reason:
This is a display of the requested information (line and column number). The cursor is positioned on an L command.
Action:
No action required.
Reason:
The requested MSGCLASS information does not exist.
Action:
Enter the next command or PF key.
Reason:
This message is displayed for one of the following reasons:
Action:
Enter the next command or press the appropriate PF key.
Reason:
You are viewing a report that has an LRECL greater than 256. The Online Viewing screen system only shows up to 256 columns; all data after that column will be truncated.
Action:
No action required.
Reason:
The CA Dispatch Online Viewing dialog could not find the page being requested. There is probably a problem with the LDS file.
Action:
Page past the bad page and continue your processing. If valid data is missing, save all error information and contact Technical Support.
Reason:
Only Yes and No are valid entries on the screen to print, archive, or delete a report.
Action:
Enter a correct request.
Reason:
Insures that the user's request was honored.
Action:
No action required.
Reason:
No records exist on the VSAM Linear data set.
Action:
Enter a new OLV request.
Reason:
Internal logic error.
Action:
Contact Technical Support. Supply the exact message information and the command that you entered.
Reason:
Internal logic error.
Action:
Contact Technical Support. Supply the exact message information and the command that you entered.
Reason:
Internal logic error.
Action:
Contact Technical Support. Supply the exact message information and the command that you entered.
Reason:
Internal logic error.
Action:
Contact Technical Support. Supply the exact message information and the command that you entered.
Reason:
Internal logic error.
Action:
Contact Technical Support. Supply the exact message information and the command that you entered.
Reason:
Online Viewing users receive this message when invoking the MJ, ML and MM line commands for MSGCLASS reports resulting from a REPRINT function, Online Viewing Conversion, or Online Viewing Unload/Reload batch process.
Action:
Contact Technical Support. Supply the exact message information and the command that you entered.
Reason:
There are no MSGCLASS entries in the Online Viewing File or no entries were found for the selection entries.
Action:
Verify the selection entries.
Reason:
A request was made to print pages but no pages were set to be printed.
Action:
The P command must be issued (to designate pages for print) before the PRINT command is used to go to the print screen and the print is requested.
Reason:
The cursor was incorrectly positioned to make the selection.
Action:
Reposition the cursor correctly.
Reason:
You are trying to erase an online retention MSGCLASS entry that has view entries on file; such MSGCLASS entries cannot be deleted.
Action:
Enter CANCEL to exit.
Reason:
No storage is available for GETSTG command.
Action:
Wait for other users to sign off. Increase the IDMS storage pool parameter in the DSSYSXA CADSOPTN member.
Submit the DSEXUSR1 job in CADSJCL and review the output to ensure that it executed properly.
Reason:
A coding error occurred in your security exit.
Action:
Contact your systems programming department.
Reason:
The security exit is incurring system problems.
Action:
Contact Technical Support.
Reason:
A security error has been detected by the security exit.
Action:
Contact your systems programming department.
Reason:
This message appears with message DC900130 and provides further information about the security violation.
Action:
Contact your systems programming department.
Reason:
The security exit or external security definitions do not permit you to view the selected screen.
Action:
Contact your systems programming department.
Reason:
You cannot delete this report definition until all Online Viewing entries for this report have expired or are deleted.
Action:
Delete the online view entries or wait for them to expire.
Reason:
The cursor was incorrectly positioned for making the selection.
Action:
Correctly reposition the cursor and make your selection.
Reason:
There are no reports in the Online Viewing file.
Action:
No action required.
Reason:
You are attempting to update MSGCLASS days and generations.
Action:
Enter ADD to add a new definition.
Reason:
CA Dispatch is being shut down; you cannot sign on.
Action:
No action required.
Reason:
You issued a STOPCADS before the CA Dispatch system was fully initialized.
Action:
Try STOPCADS again later.
Reason:
CA Dispatch is being shut down. No more online processing is allowed.
Action:
No action required.
Reason:
Internal logic error. Possibly this report was deleted by another user. File l xxxxxxxx indicates which database file is having a problem and l nnnn is the error status.
Action:
Use PF2, PF3, or PF4 to exit the screen.
Reason:
Your terminal is not a 3278 mode 2, 3, 4, or 5 type terminal.
Action:
Contact Technical Support.
Reason:
This is a request for information.
Action:
Enter a valid password for the user ID that is signed on to the terminal.
Reason:
The JES command entered did not contain TO in the second and third characters.
Action:
Retype the command with TO as the second and third characters.
Reason:
There is an invalid entry in the Mode field.
Action:
Review the help text for valid entries; press PF1 or enter HELP.
Reason:
There is no status for the mode you have selected.
Action:
No action required.
Reason:
You can use only one of the two fields entered.
Action:
Enter one of the fields.
Reason:
You have submitted a JES command.
Action:
No action required.
Reason:
The cursor must be on a valid data line, under the PRI (priority) heading.
Action:
Set your cursor and press the PF key.
Reason:
There are no reports associated with this job.
Action:
No action required.
Reason:
This is a custom user-defined message issued from the security exit RDFGEX06 for the verification process.
Action:
Follow user-defined procedures.
Reason:
A verification error, as designated by the user in the security exit RDFGEX06, has occurred.
Action:
Follow user-defined procedures.
Reason:
There are no events defined for this report.
Action:
Add an event or exit the screen.
Reason:
A message entry is not valid for the event level.
Action:
The message entry is ignored during processing.
Reason:
The cursor position is invalid for event selection.
Action:
Reposition the cursor and try the function key again.
Reason:
The PF9 function cannot add event records.
Action:
Press Enter to add the records.
Reason:
This event level cannot be the first record for a report event list. The online will ignore all "+" level events until a non - "+" level is encountered.
Action:
Enter the appropriate event level record first.
Reason:
No MSGCLASS events are defined.
Action:
Add an event or exit the screen.
Reason:
The report recipient you are working with has been deleted by another user.
Action:
Add the report recipient again or exit the screen.
Reason:
While in ADD mode the screen will not modify individual fields for an existing user.
Action:
Enter this report recipient screen in normal mode to modify fields.
Reason:
The recipient is not on the database, therefore the report recipient cannot be added.
Action:
Add the recipient or exit the screen.
Reason:
The report does not exist for the recipient you are trying to add.
Action:
Correct the report name and retry the function or first add the report definition.
Reason:
An informational message stating that you have successfully reprinted a report from Online Viewing.
Action:
None.
Reason:
A CA Dispatch user has started a task.
Action:
No action required.
Reason:
A CA Dispatch user has ended a task.
Action:
No action required.
Reason:
A user has issued the S ARCH XT command for archive processing to begin in a region separate from CA Dispatch processing. JCL has been submitted to start that job running.
Action:
No action required.
Reason:
A user has issued the S EXTR XT command for extract processing to begin in a region separate from CA Dispatch processing. JCL has been submitted to start that job running.
Action:
No action required.
Reason:
A CA Dispatch report has the Passthru Record flag set on, but has also set options that only apply to printed output. Displayed options are ignored.
Action:
Correct the options that were set incorrectly.
Reason:
An attempt is being made to add a record to the database and the AR area is full.
Action:
For instructions on how to expand the AR area, see the Systems Programmer Guide.
Reason:
An attempt is being made to add a record to the database and the OV area is full.
Action:
See the Systems Programmer Guide for instructions on how to expand the OV area.
Reason:
An attempt is being made to add a record to the database and the RD-STAT area is full.
Action:
See the Systems Programmer Guide for instructions on how to expand the RD-STAT area.
Reason:
An attempt is being made to add a record to the database and the RD-MISC area is full.
Action:
Contact Technical Support for instructions on how to free the area.
Reason:
Invalid entry for the command field.
Action:
Reenter a valid command.
Reason:
Length of PREFIX plus OFFSET is greater than SKIP value.
Action:
See your Xerox user manual for maximum values.
Reason:
A User ID, which has no recipient IDs defined to it was selected from screen VSGMU230. VSGMU235 issues this message.
Action:
Add recipient IDs using screen VSGMU235.
Reason:
An attempt was made to add a recipient (on screen VSGMU235) who has not been defined to the distribution database.
Action:
Add the recipient ID using screen VRDMU310 or specify a correct recipient ID.
Reason:
System defaults or user limits prevented a reprint request from being done. The first number is the size of the report and the second is the limit being used.
Action:
Redo the print by page process. Either limit the number of pages or request an increase of your limit from your CA Dispatch administrator.
Reason:
Processing of the requested function cannot continue because the required database record (as indicated) cannot be retrieved.
Action:
Exit the current screen and redo the process that failed. If the error occurs again, contact your CA Dispatch administrator to redo Sysgen screen processing to create the missing record.
Reason:
There are no message class reports in the Online Viewing database.
Action:
A report's MSGCLASS data must be processed by CA Dispatch in order to be added to the Online Viewing database.
Reason:
The specified Online Viewing module received the indicated error and is displaying it on the screen.
Action:
View the CA Dispatch log files for any supporting error messages. If there are no other error messages or the actions for those error messages do not resolve the problem, save all error information and contact Technical Support.
Reason:
Informational message from the CA Dispatch help text batch utility.
Action:
None.
Reason:
Informational message from the CA Dispatch help text batch utility.
Action:
None.
Reason:
Informational message from the CA Dispatch help text batch utility.
Action:
None.
Reason:
Informational message from the CA Dispatch help text batch utility.
Action:
None.
Reason:
Informational message from the CA Dispatch help text batch utility.
Action:
None.
Reason:
Informational message from the CA Dispatch help text batch utility.
Action:
None.
Reason:
The help text batch utility ended with errors.
Action:
Check the error messages, make corrections, and rerun the job.
Reason:
The help text batch utility ended successfully.
Action:
None.
Reason:
This message is informational only.
Action:
Check the parameter and rerun the job.
Reason:
The CA Dispatch Online Viewing dialog could not find the first OV-VIEW database record for the current screen list, although it had been found previously. Another Online Viewing user may have been deleted it.
Action:
Exit from the current screen, then attempt the process again. If the problem persists, save all error information, and contact Technical Support.
Reason:
The CA Dispatch Online Viewing dialog could not find the OV-BASE database record for the report being viewed, although it had been found previously. Another Online Viewing user may have been deleted it.
Action:
Exit from the current screen, then attempt the process again. If the problem persists, save all error information and contact Technical Support.
Reason:
The CA Dispatch Online Viewing dialog could not find the OV-VIEW database record for the current screen list, although it had been found previously. Another Online Viewing user may have been deleted it.
Action:
Exit from the current screen, then attempt the process again. If the problem persists, save all error information and contact Technical Support.
Reason:
The maildrop being added for the recipient does not have an address defined.
Action:
Either correct the maildrop parameter if incorrect or add the required maildrop on the Maildrop Sysgen Screen (VSGMU130). If a maildrop is not defined to this screen, a maildrop address cannot be used and the default maximum time and pages from the Sysgen Control Information Screen will be used when processing a bundle.
Reason:
You are trying to reprint from OLV and the Sysgen reprint class is not defined.
Action:
Access the Dedicated Sysout Information Control Screen (VSGMU105) and enter the required value.
Reason:
An attempt was made to extract a report defined with the "passthru" option and send it to OLV.
Action:
None.
Reason:
You are trying to access a printer that is not defined to CA Dispatch.
Action:
Define the printer.
Reason:
The OLV program OVBGDBOV has successfully recovered from a database deadlock condition. This message is preceded by an IDMS deadlock message.
Action:
None.
Reason:
The OLV program OVBGDBPR has successfully recovered from a database deadlock condition. This message is preceded by an IDMS deadlock message.
Action:
None.
Reason:
The indicated subtask has been ended.
Action:
None.
Reason:
You attempted to execute a function for which you do not have password authority.
Action:
Enter CANCEL.
Reason:
All reports have been deleted but they are "soft" deletes. No reports are displayed, but the records still exist.
Action:
When you run the batch job DSEXPSAR or DSEXTMIG, the report will be deleted from the archive definition.
Reason:
The user profile created for this report was executed before the report was presented on the terminal.
Action:
This message is informational only.
Reason:
The default profile created for this report was executed before the report was presented on the terminal.
Action:
This message is informational only.
Reason:
An SPRO command and an EPRO command were issued but no Online Viewing commands were entered during the profile session to build a profile.
Action:
Issue the SPRO command, then issue Online Viewing commands. Save them with the EPRO command.
Reason:
A DPRO command was issued but no profile was stored on the Online Viewing database to delete.
Action:
This message is informational only.
Reason:
An SPRO command was entered. All commands subsequently entered will be recorded in a named profile that will be saved when you enter the EPRO command.
Action:
This message is informational only.
Reason:
An SPRO DEF command was entered. All commands subsequently entered will be recorded in a default profile that will be saved when you enter the EPRO command.
Action:
This message is informational only.
Reason:
An EPRO command was entered. All commands are saved in the named profile and can be executed the next time the report is viewed by this user.
Action:
This message is informational only.
Reason:
An EPRO DEF command was entered. All commands are saved in the default profile and will be executed the next time the report is viewed by a user who does not have a profile.
Action:
This message is informational only.
Reason:
A DPRO command was entered. The named profile for this user was deleted.
Action:
This message is informational only.
Reason:
A DPRO DEF command was entered. The current default profile was deleted.
Action:
This message is informational only.
Reason:
The profile record stored on the database is formatted incorrectly.
Action:
Create another profile.
Reason:
The profile record has a 256-byte limit. This message is issued when the limit is exceeded.
Action:
The most recent command issued was not saved in the profile. Either issue the EPRO command to save the profile or create a new profile.
Reason:
A profile command was issued from an Online Viewing screen other than the Online Viewing Screen for Report (VOVMI320).
Action:
USER and RECIPIENT information is needed to implement profiling; it is supported only through the Online Viewing Screen for Report (VOVMI320).
Reason:
Profile generation does not support all Online Viewing commands. Commands not included are LOCATE, Print commands, and RESET versions of FREEZE and COLUMNS. This command is not recorded on the profile.
Action:
Enter another command.
Reason:
No printer definitions were entered as part of the PRINTER/*PRINTER report name/job name combination.
Action:
If not already done, add a definition for report PRINTER, job name *PRINTER. Add site-specific printer definitions as recipients owned by this report.
Reason:
The printer name specified is not allowed to be overridden.
Action:
To allow overrides, access the Sysgen User Definition Screen (VSGMU235) and set the Printer ID Override flag to Y.
Reason:
A Recipient Extension record must exist before Download can occur.
Action:
Cancel from the current screen. Add a Recipient Extension record through screen VRDMU150 for this recipient of the selected report.
Reason:
The Recipient Extension record does not allow downloads by request.
Action:
Cancel from the current screen. Change the Selected Download option to Y through screen VRDMU150 for this recipient of the selected report.
Reason:
A database error exists. The download request could not be created.
Action:
Exit CA Dispatch and log on again. Then retry the function that caused the error. Review the log for any CA IDMS messages that have occurred and take appropriate action based on those messages. Refer to the CA IDMS Error Codes Messages volumes for more information. Report the problem to Technical Support.
Reason:
A database error exists. The download request could not be created.
Action:
Exit CA Dispatch and log on again, then retry the function that caused the error. Review the log for any CA IDMS messages that have occurred and take appropriate action based on those messages. Refer to the CA IDMS Error Codes Messages volumes for more information. Report the problem to Technical Support.
Reason:
A database error exists. The download request could not be created.
Action:
Exit CA Dispatch and log on again, then retry the function that caused the error. Review the log for any CA IDMS messages that have occurred and take appropriate action based on those messages. Refer to the CA IDMS Error Codes Messages volumes for more information. Report the problem to Technical Support.
Reason:
A database error exists. The download request could not be created.
Action:
Exit CA Dispatch and log on again, then retry the function that caused the error. Review the log for any CA IDMS messages that have occurred and take appropriate action based on those messages. Refer to the CA IDMS Error Codes Messages volumes for more information. Report the problem to Technical Support.
Reason:
A database error exists. The download request could not be created.
Action:
Exit CA Dispatch and log on again, then retry the function that caused the error. Review the log for any CA IDMS messages that have occurred and take appropriate action based on those messages. Refer to the CA IDMS Error Codes Messages volumes for more information. Report the problem to Technical Support.
Reason:
A download or upload request has been modified.
Action:
None.
Reason:
A download or upload request has been created.
Action:
None.
Reason:
The Recipient Archive Retrieval Screen (VARMI220) has been requested for a particular report and no reports are available in archive.
Action:
Enter END to exit the screen.
Reason:
On the Report Recipient Copy Screen, Reports (VRDMU135), the "From" report and job name were entered and not found on the database.
Action:
Correct the "From" report and job name.
Reason:
On the Report Recipient Copy Screen, Reports, (VRDMU135) the "From" report recipient was entered and not found on the database.
Action:
Correct the "From" report recipient.
Reason:
On the Report Recipient Copy Screen, Reports (VRDMU135) the ADD command is not present on the command line and is required for the copy function.
Action:
Enter ADD on the command line.
Reason:
On the Active Bundle Status Screen, (VRDMU820), a Locate Maildrop command (L xxxxxxxx) did not find a matching maildrop.
Action:
Enter a valid Maildrop ID for the L xxxxxxxx command.
Reason:
On the Report Recipient Copy Screen, Reports (VRDMU135), during the recipient copy function, the "To" recipient being created is also found as a current recipient. This is a warning to ensure that creating a duplicate recipient is the desired action.
Action:
If you want to create the duplicate recipient, press Enter. If you do not want to create the duplicate recipient, enter CANCEL on the command line.
Reason:
While signed on and working on an OLVO region, the user has requested a service that will cause an update to be performed on the CA Dispatch main region. That region is currently not available.
Action:
Repeat the action when the CA Dispatch main region becomes available.
Reason:
The screen program has received an unexpected return code.
Action:
Contact Technical Support.
Reason:
On Report Recipient Definition Screen, Pages (VRDMU140), the locate command (L nnn) was issued. The locate value was not numeric.
Action:
Correct the locate command (L nnn) by entering a numeric value.
Reason:
On the Report Recipient Copy Screen, Reports (VRDMU135), the entries required to perform a copy are complete. The ADD command must be used to add the new recipient to the database.
Action:
Enter ADD in the command line or press PF 10 to complete the recipient copy.
Reason:
On the Report Recipient Copy Screen, Reports (VRDMU135), during the recipient copy function, the "To" recipient being created was not entered.
Action:
Enter the desired 'To' report recipient.
Reason:
On the Report Recipient Copy Screen, Reports (VRDMU135), for the "From" report recipient, a relative duplicate number has been entered. This relative number is greater than the actual number of duplicate recipients.
Action:
Correct the relative duplicate number for the "From" recipient.
Reason:
On the Report Recipient Definition Screen, Pages (VRDMU140), a MOVE, COPY, or BLOCK command has been partially issued but is not complete.
Action:
The command may be completed by entering the proper line command. RESET may be entered to cancel the command.
Reason:
On the Active Bundle Status Screen (VRDMU820), a Locate Bundle command (LBxxxxxxxx) did not find a matching bundle.
Action:
Enter a valid bundle ID for the LBxxxxxxxx command.
Reason:
On the Subtask Status Screen (TS), you entered a start command (S xxxx).
Action:
Enter the proper command in response to the message.
Reason:
On the Subtask Status Screen (TS),, you entered an end command (E xxxx).
Action:
Enter the proper command in response to the message.
Reason:
An automated download transfer request was processed but was not found when attempting to add it to the history generation list. The request was probably deleted before the STATUS task was started.
Action:
None.
Reason:
An attempt was made to delete a MSGCLASS report on screen VOVMI200 while the MSG subtask was currently processing it.
Action:
Attempt the deletion at a later time.
Reason:
The CA Dispatch Active Bundle process was unable to delete a Logical Bundle because of an error condition.
Action:
View the CA Dispatch log files for any supporting error messages. If there are no other error messages or the actions for those error messages do not resolve the problem, save all error information and contact Technical Support.
Reason:
The CA Dispatch Active Bundle process was unable to delete a report from a Logical Bundle because of an error condition.
Action:
View the CA Dispatch log files for any supporting error messages. If there are no other error messages or the actions for those error messages do not resolve the problem, save all error information and contact Technical Support.
Reason:
You attempted to send a report that was archived with resources back through distribution through screen VARMI200 or VARMI220.
Action:
None.
Reason:
This message is informational only.
Action:
None.
Reason:
The PC Control record cannot be created without proper information.
Action:
Enter a PC file, PC directory path, and retention information, then press Enter.
Reason:
The group name you entered on the ADD line was not previously defined.
Action:
Add the PC group or reenter the value with a defined PC group name.
Reason:
The PC group being deleted still has PC user/group entities defined to it.
Action:
Delete all of the lower-level PC user/group entities.
Reason:
The specified entities are successfully deleted.
Action:
None.
Reason:
The PC User/Group value cannot be blank.
Action:
Enter a valid PC User/Group name.
Reason:
This message is informational only.
Action:
None.
Reason:
The user requested the transfer of a file using the generations suffix (.GEN or .V??) but the system default for file generations is set to 0.
Action:
Go to the PC Control Screen (VPCMU100) and enter a value (greater than zero) in the file generations field.
Reason:
No entities have been added yet.
Action:
None.
Reason:
The PC User/Group exists in the group name entered.
Action:
Enter a different group name.
Reason:
The PC User/Group cannot be duplicated in a group.
Action:
None.
Reason:
Duplicate PC groups are not allowed.
Action:
None.
Reason:
Addition of lower level PC User/Group successful.
Action:
None.
Reason:
This message is informational only.
Action:
None.
Reason:
No requests of the specified type exist.
Action:
Exit from the current screen.
Reason:
This occurs on the PC Upload Request Screen (VOVMU360) when the flag for PC UPLOAD is not set to Y on the PC Control Screen (VPCMU100).
Action:
Contact your Report Administrator.
Reason:
This message is informational only.
Action:
None.
Reason:
PC = Y and VIEW ONLINE = N
Action:
Correct the PC or View Online option. PC cannot be Yes without View Online being Yes. All other combinations are valid.
Reason:
Only 1-3 characters can follow a period.
Action:
Correct the field entry.
Reason:
If the PC file name contains .GEN or .V??, retention by generations will be used. An invalid retention generation number exists (not 1-99).
Action:
Correct the Retention Generations field or remove .GEN or .V?? from the PC File field.
Reason:
An attempt was made to process an upload request but the report base definition does not exist for the report and job name in the request.
Action:
Add the report base definition to the CA Dispatch report database. The report name can be any value. The job name must be the same as the PC User ID of the user who will attempt the upload.
Reason:
The displayed CA Dispatch subtask was not started due to an MVS ATTACH error.
Action:
Attempt to restart the displayed subtask. If the problem persists, contact Technical Support.
Reason:
An error occurred in the specified program.
Action:
Perform the desired function again. If the problem persists, contact Technical Support.
Reason:
An attempt was made to begin the transfer process but no PC requests exist.
Action:
None.
Reason:
An error has been found during the PC download process. The text in the error message has been returned from the PC through RTC or communications.
Action:
If the error text does not clarify the problem, check for accompanying error messages in both the CA Dispatch and RTC logs.
Reason:
An error has been found during the PC download process. The text in the error message has been returned from the PC through RTC or communications.
Action:
If the error text does not clarify the problem, check for accompanying error messages in both the CA Dispatch and RTC logs.
Reason:
An error has been found during the PC download process. The text in the error message has been returned from the PC through RTC or communications.
Action:
If the error text does not clarify the problem, check for accompanying error messages in both the CA Dispatch and RTC logs.
Reason:
The DSPCVIEW module was called from module DSPCAUTO but returned with a non-zero return code. An automatic download request could not be processed.
Action:
Try the transfer again. If that fails, sign off CA Dispatch, then get back on and try the transfer again. If the error persists, call Technical Support.
Reason:
On the PC Upload Request Screen (VOVMU360), the report and job are not located on the database. The report and job name must be defined to allow PC upload processing.
Action:
Correct the report and job name if an error has been made. Consult the CA Dispatch Report Administrator if new definitions must be created.
Reason:
The programs for the report transfer facility cannot be found.
Action:
Do not try to run this function until the OM Document Viewer RTC option is installed.
Reason:
An automated download transfer request was processed but was not downloaded because the STATUS task has not processed the previous download request that has the same User ID and PC file/path name. The first date/time stamp contains the date and time the request was processed. The second date/time stamp contains the date and time the report was originally created.
Action:
This is a warning message. The next auto transfer cycle will again check this download request to see if it is available for transfer. Be sure ENF and the Status task are active. If the download request continues to be bypassed, the previous download request for the same user ID and PC file/path name can be manually marked complete using the Request Queue List Screen (VPCMU310), Option C.
Reason:
STAE processing for program pppppppp, has been entered due to an abend condition which prevents further processing.
Action:
Investigate the abend that occurred and take appropriate action.
Reason:
An attempt was made to retrieve a report from Archive while in the Online Viewing Only region and program DSLCCHEK cannot determine if the main region is active. The report will not be retrieved.
Action:
Back out of the current screen, reenter the screen, and retry the request. If the error persists, contact Technical Support.
Reason:
To change a pending, automated transfer request from PENDING to COMPLETED, press Enter.
Action:
Press Enter to modify the request or press PF2 to cancel.
Reason:
The automated transfer request is now "complete".
Action:
Press PF3 to return or process the next request.
Reason:
The option value C was entered for a transfer request that is not pending and automated.
Action:
Change C value to a valid option.
Reason:
A program exception occurred in program DSRQSDEL and its STAE recovery routine was invoked.
Action:
Try the update again. If the problem persists, contact Technical Support.
Reason:
Internal program error.
Action:
Contact Technical Support.
Reason:
The requested function cannot be performed in OLVO.
Action:
Sign on to the main CA Dispatch system to perform the desired task.
Reason:
Either the CA Dispatch region is not active, or the OLVO region cannot read the file pointed to by DISPCTL DD statement.
Action:
If accompanied by the DC900375 message in the JESLOG, take the action described in that message.
Reason:
An attempt to open either the DISPCTL or CAICTL files in program DSRQSDEL failed.
Action:
Validate that the specified file is defined to the CA Dispatch startup JCL. If the problem persists, contact Technical Support.
Reason:
An unsupported update was attempted from a screen in a CA Dispatch Online Viewing Only system.
Action:
Perform the update from the main CA Dispatch system.
Reason:
You specified more than one value for the maximum number of pages to be searched for the FIND command.
Action:
Reenter the command.
Reason:
You specified more than one search start column for the FIND command.
Action:
Reenter the command.
Reason:
You specified more than one search end column for the FIND command.
Action:
Reenter the command.
Reason:
You specified more than one directional parameter on the FIND command.
Action:
Reenter the command.
Reason:
The OLVO region cannot open the file indicated in the DISPCTL DD statement.
Action:
Be sure this DD statement is included in the OLVO startup JCL.
Reason:
You requested that the ACIF be rerun to correct errors on the prior running of the utility, but this is not an ACIF report.
Action:
None.
Reason:
You entered an invalid parameter of xxxxxxxx on the FIND command.
Action:
Reenter the command.
Reason:
You entered a string that is larger than the start and end column range specified.
Action:
Reenter the string or enlarge the start/end column range.
Reason:
You specified both the printer and class/destination overrides. You can only enter one. The printer override fills in the appropriate class/dest combination.
Action:
Delete one of the entries.
Reason:
You specified an invalid profile name.
Action:
Reenter the profile name.
Reason:
You specified a profile during a SPRO command that already exists.
Action:
Reenter the profile name.
Reason:
You specified a SPRO, DPRO, SWITCH, or EXEC without specifying the profile name.
Action:
Reenter the command specifying the profile name.
Reason:
You entered the LISTPROF command to list all the profiles for the report/recipient, but none exist.
Action:
None.
Reason:
Request priority options T and B are only valid for pending request processing.
Action:
None.
Reason:
Multiple M (Move) options were entered on screen VRDMI840.
Action:
Enter only one M option.
Reason:
Multiple B or A options or both were entered on screen VRDMI840.
Action:
Enter only one B or A option.
Reason:
The SORT command was entered on screen VRDMI840 without any parameters.
Action:
Reenter the SORT command with any combination of REPORT, JOB, RECIPIENT, and PAGES.
Reason:
The l nth sort parameter specified with the SORT command on screen VRDMI840 is invalid.
Action:
Reenter the SORT command with any combination of REPORT, JOB, RECIPIENT and PAGES.
Reason:
The SORT command entered on screen VRDMI840 successfully completed.
Action:
None.
Reason:
You entered the DOWN or UP command and have marked a report for moving but have not yet specified where to move it.
Action:
None.
Reason:
The ATTENTION or PA1 Key has been pressed while in the ISPF interface.
Action:
ATTENTION and PA1 Keys are not valid methods to use to terminate the ISPF interface. In emergency situations, terminate ISPF from another session by issuing:
DMCT V PTE pterm-ID OFF
The pterm-ID for the user in the ISPF interface can be found by issuing:
DMCT DIS PTE
After the pterm-ID has been varied offline, it should be varied back online so that it can be used again. Issue the following:
DMCT V PTE pterm-ID ON
Reason:
The displayed CA Dispatch subtask was not started due to an MVS ATTACH error.
Action:
Attempt to restart the displayed subtask. If the problem persists, contact Technical Support.
Reason:
You requested a reprint using class/dest overrides, but did not specify any such overrides.
Action:
Enter a class and destination override combination.
Reason:
You did not specify a maildrop.
Action:
Enter a maildrop name.
Reason:
A program exception occurred in program CADSRB00 and its STAE recovery routine was invoked.
Action:
Try the desired RIDF function again. If the problem persists, contact Technical Support.
Reason:
All RIDF selection criteria are blank.
Action:
At least one of the criteria must be specified.
Reason:
Program CADSRF00 has ended prematurely due to an error condition.
Action:
Re-attempt the desired RIDF function. If the error reoccurs, it will be preceded by another error message. Save all error information and contact Technical Support.
Reason:
No reports were found by CADDSPL for the input queue type displayed on screen VOPMI200.
Action:
None.
Reason:
An invalid option was entered next to an RIDF report.
Action:
None.
Reason:
An error has occurred while trying to access the SPLHDR2 control block for a given report. rc is the return code from the CADDSPL.
Action:
This message will be preceded by error messages from the CA Dispatch LDS I/O Manager. Take the specified action for the preceding message.
Reason:
CADDSPL started task is not executing.
Action:
Start CADDSPL.
Reason:
No records were found by CADDSPL. This will occur if no reports were sent to the interface.
Action:
Send report output data to the class/destination values set on screen VSGMU105.
Reason:
An invalid parameter list was passed to CADDSPL. This is an internal logic error.
Action:
Contact Technical Support.
Reason:
An error was encountered by CADDSPL during processing of #CAS9SPL request. Internal logic error.
Action:
Contact Technical Support.
Reason:
RIDF encountered an error updating a report on the CADDSPL LDS.
Action:
This message will be preceded by error messages from the CA Dispatch LDS I/O Manager. Take the specified action for the preceding message.
Reason:
Either an invalid LDS Token was passed on a read request or the SPLHDR2 record contains bad data pointers. Internal logic error.
Action:
Contact Technical Support.
Reason:
RIDF encountered an error deleting a report from CADDSPL.
Action:
This message will be preceded by error messages from the CA Dispatch LDS I/O Manager. Take the specified action for the preceding message.
Reason:
An invalid LDS Token was passed on an update request. This is an internal logic error.
Action:
Contact Technical Support.
Reason:
An invalid LDS Token was passed on an update request. This is an internal logic error.
Action:
Contact Technical Support.
Reason:
An invalid LDS Token was passed on an update request. This is an internal logic error.
Action:
Contact Technical Support.
Reason:
An invalid return code of XX with reason code YY was returned by CADDSPL during an update function.
Action:
Contact Technical Support.
Reason:
A program exception occurred in program CADSRF00 and its ESTAE recovery routine was invoked.
Action:
Re-attempt the desired RIDF function. If the problem persists, contact Technical Support.
Reason:
A user attempted to update an entry displayed in a Report Input Display Facility queue. When attempting to perform this function, Dispatch determined the RIDF entry no longer exists because the report has been deleted from the LDS.
Action:
Press Enter for to cause CA Dispatch to redisplay the RIDF queue.
Reason:
This message appears in the CA Dispatch log when a terminal user is displaying report names. CA Dispatch is unable to match a job token ID with an entry in an internal list of job tokens prepared by the RPI function.
Action:
System operation continues. If this message re-appears, recycle CA Dispatch. If the message continues to appear, contact Technical Support.
Reason:
A user attempted to perform an extended display of an entry displayed in a Report Input Display Facility queue. When attempting to perform this function, CA Dispatch determined that the RIDF entry no longer exists because the report has been deleted from the LDS.
Action:
Press PF2 for CA Dispatch to redisplay the RIDF queue.
Reason:
A user attempted to perform an extended display from the Active Bundle Detail Status Screen. When attempting to perform this function, CA Dispatch determined that the bundle no longer exists because it has been deleted by another user.
Action:
Press PF2 for CA Dispatch to redisplay the Active Bundles Status screen.
Reason:
The CA Dispatch Bundle Status Task is successfully started and ready to process.
Action:
None.
Reason:
An error occurred in the specified database program. This message is followed by messages DC900432 through DC900434.
Action:
You can review the log for any CA IDMS messages that have occurred and take appropriate action based on those messages. Refer to the CA IDMS Error Codes Messages volumes for more information. Contact Technical Support.
Reason:
IDMS Error Status value from database error.
Action:
None.
Reason:
IDMS database record from database error.
Action:
None.
Reason:
IDMS database set from database error.
Action:
None.
Reason:
A program exception occurred in the Bundle Status Task program CADSRLSE and its STAE recovery routine was invoked.
Action:
Restart the Bundle Status Task. If the problem persists, save all error information and contact Technical Support.
Reason:
The CA Dispatch Bundle Status Task ended successfully.
Action:
None.
Reason:
The REFRESH task code was entered without specifying a program name.
Action:
Enter the program name to be refreshed.
Reason:
The entered program could not be refreshed.
Action:
Re-attempt the refresh command. If the problem persists, check the error logs for additional information.
Reason:
The displayed program was refreshed by the indicated user.
Action:
None.
Reason:
A SNAP or TRACE task code was entered without specifying any parameters.
Action:
Enter the SNAP or TRACE parameters.
Reason:
A SNAP or TRACE command could not be processed.
Action:
Re-attempt the command.
Reason:
Invalid parameter values were entered for a SNAP or TRACE command.
Action:
Reenter the command with the correct parameters.
Reason:
A SNAP or TRACE processing for component nnnnnnnn is either turned ON or OFF by the displayed user.
Action:
None.
Reason:
The SPINOFF task code was entered specifying valid keywords.
Action:
None.
Reason:
The displayed maildrop will be compared against the Active Bundle Queue. If a complete match of all entered keywords is successful, the bundle will be closed.
Action:
None.
Reason:
The displayed destinations will be compared against the Active Bundle Queue. If a complete match of all entered keywords is successful, the bundle will be closed.
Action:
None.
Reason:
The displayed forms will be compared against the Active Bundle Queue. If a complete match of all entered keywords is successful, the bundle will be closed.
Action:
None.
Reason:
The displayed class will be compared against the Active Bundle Queue. If a complete match of all entered keywords is successful, the bundle will be closed.
Action:
None.
Reason:
The displayed number of bundles has been released by the SPINOFF task code.
Action:
None.
Reason:
The Spinoff task found no active bundles to compare user criteria against.
Action:
None.
Reason:
The Spinoff task found no matching active bundles to close.
Action:
None.
Reason:
The displayed Bundle for the displayed Maildrop has been closed.
Action:
None.
Reason:
The SPINOFF task code was entered without specifying a Keyword parameter.
Action:
Enter a valid keyword (such as MAILDROP=a,FORMS=b,DEST1=c,DEST2=d,CLASS=e).
Reason:
The SPINOFF task code was entered specifying an invalid keyword. This message is followed by message DC900457.
Action:
Enter a valid keyword (such as MAILDROP=a,FORMS=b,DEST1=c,DEST2=d,CLASS=e).
Reason:
The SPINOFF task code that was entered specified an invalid keyword. This is an informational message displaying valid keyword syntax.
Action:
None.
Reason:
This message is displayed to confirm that a bundle is about to be deleted from screen VRDMU820 or VRDMI830.
Action:
Press Enter to continue deletion process or press PF2 to cancel it.
Reason:
This message is displayed to reconfirm that a bundle is about to be deleted from screen VRDMU820 or VRDMI830.
Action:
Press Enter to continue the deletion process or enter CANCEL to cancel it.
Reason:
The bundle is now deleted.
Action:
None.
Reason:
The AFP Default Control record does not exist on the database.
Action:
Enter the required information on screen VSGMU240.
Reason:
No AFP resource groups exist to be displayed on screen VSGMU245.
Action:
Enter the required information on screen VSGMU245 to add resource groups.
Reason:
The entered resource group name already exists on the database.
Action:
Enter a different name.
Reason:
The entered AFP library group name is invalid.
Action:
Enter a different name.
Reason:
No AFP library groups exist to be displayed on screen VSGMU250.
Action:
Enter the required information on screen VSGMU250 to add AFP library groups.
Reason:
The entered AFP library group already exists on the database.
Action:
Enter a different name.
Reason:
An AFP library group was selected for deletion but it is still defined to one or more AFP resource groups.
Action:
Remove the library group from the resource group definitions and perform the delete again.
Reason:
You tried to enter the cut and paste panel, but you already have column suppression or freezing in effect.
Action:
Enter CANCEL to exit the screen, enter COL RESET to reset column processing, then reselect Cut/Paste.
Reason:
An identifier "i" was specified on the cut line, but no matching identifier was found to signal the end of the cut string.
Action:
Add the identifier "i" in the column that indicates the end of the cut.
Reason:
An identifier "i" was specified on the cut line, but another identifier, "a" was encountered before identifier "i" had ended.
Action:
Add the identifier "i" in the column that indicates the end of the cut, or change the identifier "a" to "i".
Reason:
No AFP Resource Library Names exist to be displayed on screen VSGMU255.
Action:
Enter the required information on screen VSGMU255 to add AFP Resource Libraries.
Reason:
The Copy Library Group entered on screen VSGMU255 does not exist as an AFP Library Group definition.
Action:
Enter an existing AFP Library Group name.
Reason:
No AFP Resource Library Names exist for the Copy Library Group name entered on screen VSGMU255.
Action:
Enter a Library Group name that has libraries defined to it.
Reason:
The AFP Resource Library Names from the Copy Library Group definition have been successfully copied to the current AFP Library Group definition.
Action:
None.
Reason:
No AFP Userlib Library Names exist to be displayed on screen VSGMU246.
Action:
Enter the required data on VSGMU246 to add AFP userlib libraries.
Reason:
The Copy Resource Group entered on screen VSGMU246 does not exist as an AFP Resource Group definition.
Action:
Enter an existing AFP Resource Group name.
Reason:
No AFP Userlib Library Names exist for the Copy Resource Group name entered on screen VSGMU246.
Action:
Enter a Resource Group name that has Userlib libraries defined to it.
Reason:
The AFP Userlib Library names from the Copy Resource Group definition have been successfully copied to the current AFP Resource Group definition.
Action:
None.
Reason:
The AFP Resource Library names from the current Library Group cannot be copied to itself.
Action:
Enter a Copy Library Group name that is different than the current Library Group name.
Reason:
The AFP Userlib Library names from the current Resource Group cannot be copied to itself.
Action:
Enter a Copy Resource Group name that is different than the current Resource Group name.
Reason:
An error occurred accessing the CADDSPL Interface by Online Viewing.
Action:
This message is preceded by error messages from the CA Dispatch LDS I/O Manager. Take the specified action indicated by the preceding messages.
Reason:
You requested the AUTOXFER function that was used for transferring reports to the PC in CA Dispatch Release 5.1. It is no longer available.
Action:
None.
Reason:
On the Cut Line definition, you specified Cut criteria identifier "a" more than once.
Action:
Change the Cut criteria identifier to another value.
Reason:
In the Paste Line criteria, you specified Paste criteria identifier "a" more than once.
Action:
Delete one of the "a" entries or change it to another identifier.
Reason:
You specified a Paste criteria (identifier "a") that was not specified in the Cut criteria.
Action:
Enter the paste criteria identifier that matches the desired Cut criteria columns.
Reason:
You tried to rename a default profile.
Action:
None.
Reason:
You tried to rename a profile to a default profile.
Action:
None.
Reason:
An error occurred while attempting to allocate a report file for a binary transfer. This message will be preceded by a DC970033 message.
Action:
Re-attempt the transfer request. If the error persists, save all error information and contact Technical Support.
Reason:
An error occurred while attempting to de-allocate a report file for a binary transfer. This message will be preceded by a DC970033 message.
Action:
Re-attempt the transfer request. If the error persists, save all error information and contact Technical Support.
Reason:
An error occurred while attempting to open a report file for a binary transfer.
Action:
Re-attempt the transfer request. If the error persists, save all error information and contact Technical Support.
Reason:
An error occurred while attempting to close a report file for a binary transfer.
Action:
Re-attempt the transfer request. If the error persists, save all error information and contact Technical Support.
Reason:
An error occurred while attempting to write to a report file for a binary transfer.
Action:
Re-attempt the transfer request. If the error persists, save all error information and contact Technical Support.
Reason:
An error occurred for CADDSPL while retrieving a report for a binary transfer.
Action:
This message is preceded by error messages from the CA Dispatch LDS I/O Manager. Take the specified action for the preceding message. Attempt the transfer request again. If the error recurs, it will be preceded by another error message. Save all error information and contact Technical Support.
Reason:
Physical Sequential File name in error.
Action:
None.
Reason:
A program exception occurred in program CADSXFSQ and its ESTAE recovery routine was invoked.
Action:
Re-attempt the transfer request. If the error persists, save all error information and contact Technical Support.
Reason:
Program CADSXFSQ received an error from an ACIF Status File function.
Action:
This message is preceded by a combination of messages DC970120 through DC970130. Perform the action required for the messages. Attempt the transfer request again. If the error recurs, it will be preceded by another error message. Save all error information and contact Technical Support.
Reason:
Program CADSSETR received an error on a CAICCI Inquiry request on behalf of the specified user.
Action:
This message contains the CAICCI error message text indicating the error encountered. Attempt the transfer request again. If the problem persists, save all error information and contact Technical Support.
Reason:
(a) The specified user is attempting to initiate a PC transfer but is already transferring under another session.
Action:
(a) None.
Reason:
(b) The specified user is attempting to initiate a PC transfer but is already transferring under multiple sessions. This is an internal logic error.
Action:
(b) Contact Technical Support.
Reason:
Program CADSSETR received an error on a CAICCI Init request on behalf of the specified user.
Action:
This message contains the CAICCI error message text indicating the error encountered. Attempt the transfer request again. If the problem persists, save all error information and contact Technical Support.
Reason:
Program CADSSETR received an error on a CAICCI Receive request on behalf of the specified user.
Action:
This message contains the CAICCI error message text indicating the error encountered. Attempt the transfer request again. If the problem persists, save all error information and contact Technical Support.
Reason:
CA Dispatch Program CADSSETR has successfully established a CAICCI signon on behalf of the specified CA Link user.
Action:
None.
Reason:
Program CADSCANR received an error on a CAICCI Cancel request on behalf of the specified user.
Action:
This message is followed by a DC900528 message indicating the error encountered. Attempt the transfer request again. If the problem persists, save all error information and contact Technical Support.
Reason:
Program CADSCANR received an error on a CAICCI Term request on behalf of the specified user.
Action:
This message is followed by a DC900528 message indicating the error encountered. Attempt the transfer request again. If the problem persists, save all error information and contact Technical Support.
Reason:
Program CADSCANR received a CAICCI error. This message contains the error text.
Action:
None.
Reason:
Program CADSCANR has successfully canceled a CAICCI session for the specified user.
Action:
None.
Reason:
An attempt has been made to start the CA Dispatch CAICCI Transfer Router, CADSXCRT, for the specified CA Dispatch VTAM applid. However, the transfer router is already active.
Action:
End the transfer router with the CADSXCRE task code and then restart.
Reason:
The CA Dispatch CAICCI Transfer Router task, CADSXCRT, is successfully started for the specified CA Dispatch VTAM applid.
Action:
None.
Reason:
The CA Dispatch CAICCI Transfer Router task, CADSXCRT, has successfully ended for the specified CA Dispatch VTAM applid.
Action:
None.
Reason:
The CA Dispatch CAICCI Transfer Router task, CADSXCRT, has abnormally terminated for the specified CA Dispatch VTAM applid.
Action:
If this occurs during shutdown processing, it is a normal situation. If not a shutdown, restart the transfer router with the CADSXCRS task. If the problem persists, save all error information and contact Technical Support.
Reason:
The CA Dispatch CAICCI Transfer Router received an error on a CAICCI Inquiry request.
Action:
This message contains the CAICCI error message text indicating the error encountered. Restart the transfer router with the CADSXCRS task. If the problem persists, save all error information and contact Technical Support.
Reason:
The CA Dispatch CAICCI Transfer Router received an error on a CAICCI Init request.
Action:
This message contains the CAICCI error message text indicating the error encountered. Restart the transfer router with the CADSXCRS task. If the problem persists, save all error information and contact Technical Support.
Reason:
The CA Dispatch CAICCI Transfer Router received an error on a CAICCI Receive request.
Action:
This message contains the CAICCI error message text indicating the error encountered. Restart the transfer router with the CADSXCRS task. If the problem persists, save all error information and contact Technical Support.
Reason:
The CA Dispatch CAICCI Transfer Router received an error on a CAICCI Term request.
Action:
This message contains the CAICCI error message text indicating the error encountered. Restart the transfer router with the CADSXCRS task. If the problem persists, save all error information and contact Technical Support.
Reason:
The CA Dispatch CAICCI Transfer Router received an invalid response message from a PC.
Action:
This message is bypassed. If message persists, end the transfer router with the CADSXCRE task and restart it with the CADSXCRS task. If problem persists, save the error information; contact Technical Support.
Reason:
The CA Dispatch CAICCI Transfer Router received an invalid service message from a PC.
Action:
This message is bypassed. If the message persists, end the transfer router with the CADSXCRE task and restart it with the CADSXCRS task. If the problem persists, save all error information and contact Technical Support.
Reason:
The CCI component of CA Common Services for z/OS (CCS for z/OS ) is either not installed or inactive.
Action:
Either install the CCI component, or activate it.
Reason:
An attempt has been made to end the CA Dispatch CAICCI Transfer Router, CADSXCRT, for the specified CA Dispatch VTAM applid; however, the transfer router shutdown is already active.
Action:
None.
Reason:
The CA Dispatch CAICCI Transfer Router shutdown task CADSXCRE has abnormally terminated for the specified CA Dispatch VTAM applid.
Action:
Issue a DCMT D ACTIVE TASKS command at the Enter Next Task Code prompt. If the CADSXCRT task is still active, attempt the shutdown again. If the problem persists, save all error information and contact Technical Support.
Reason:
The CA Dispatch CAICCI Router shutdown received an error on a CAICCI Inquiry request.
Action:
This message contains the CAICCI error message text indicating the error encountered. Re-attempt to end the router with the CADSXCRE task. If the problem persists, save all error information and contact Technical Support.
Reason:
The CA Dispatch CAICCI Router shutdown received an error on a CAICCI Init request.
Action:
This message contains the CAICCI error message text indicating the error encountered. Re-attempt to end the router with the CADSXCRE task. If the problem persists, save all error information and contact Technical Support.
Reason:
The CA Dispatch CAICCI Router shutdown received an error on a CAICCI Send request.
Action:
This message contains the CAICCI error message text indicating the error encountered. Re-attempt to end the router with the CADSXCRE task. If the problem persists, save all error information and contact Technical Support.
Reason:
The CA Dispatch CAICCI Router shutdown received an error on a CAICCI Term request.
Action:
This message contains the CAICCI error message text indicating the error encountered. Re-attempt to end the router with the CADSXCRE task. If the problem persists, save all error information and contact Technical Support.
Reason:
The CA Dispatch CAICCI Transfer Server did not receive a response from the client in the required amount of time.
Action:
The session is disconnected. Re-attempt the transfer request. If the problem persists, save all error information and contact Technical Support.
Reason:
During abort processing, the CA Dispatch CAICCI Transfer Server did not receive a response from the client in the required amount of time.
Action:
The session is disconnected. Check previously issued messages to find the reason for the abort. Re-attempt the transfer request. If the problem persists, save all error information and contact Technical Support.
Reason:
The CA Dispatch CAICCI Transfer Server has lost its connection with the client.
Action:
Re-attempt the transfer request. If the problem persists, save all error information and contact Technical Support.
Reason:
The specified user is attempting to initiate a PC transfer but is already transferring under multiple sessions. This is an internal logic error
Action:
Contact Technical Support.
Reason:
The specified user is attempting to initiate a PC transfer but is already transferring under another session.
Action:
None.
Reason:
The specified user is attempted to initiate a PC transfer but is already transferring under another session.
Action:
None.
Reason:
The CA Dispatch CAICCI Transfer Server for the specified user is successfully started.
Action:
None.
Reason:
The CA Dispatch CAICCI Transfer Server received an error from the PC.
Action:
This message is followed by a DC900575 message indicating the error encountered. Re-attempt the transfer request. If the problem persists, save all error information and contact Technical Support.
Reason:
The CA Dispatch CAICCI Transfer Server is ending due to an error condition.
Action:
This message is followed by the DC900576 and DC900577 messages. See earlier written messages to determine the reason for the error condition. Re-attempt the transfer request. If the problem persists, save all error information and contact Technical Support.
Reason:
The CA Dispatch CAICCI Transfer Server received an invalid message from the client.
Action:
This message is followed by the DC900575 message that contains the invalid message. Re-attempt the transfer request. If the problem persists, save all error information and contact Technical Support.
Reason:
The CA Dispatch CAICCI Transfer Server cannot find the common communication storage for the Transfer Router. This is an internal logic error. Contact Technical Support.
Action:
Contact Technical Support.
Reason:
The CA Dispatch CAICCI Transfer Server encountered an error during signon of the specified user.
Action:
The error message text is self explanatory. Fix the signon problem and re-attempt the transfer request. If the problem persists, save all error information and contact Technical Support.
Reason:
The specified user requested signoff from the PC transfer session.
Action:
None.
Reason:
The CA Dispatch CAICCI Transfer Server encountered an error in one of the CA Dispatch security programs during user signon.
Action:
Try the transfer request again. If the problem persists, save all error information and contact Technical Support.
Reason:
The CA Dispatch CAICCI Transfer Server received an error on a CAICCI Inquiry request on behalf of the specified user.
Action:
This message is followed by a DC900572 message indicating the error encountered. Re-attempt the transfer request. If the problem persists, save all error information and contact Technical Support.
Reason:
The CA Dispatch CAICCI Transfer Server received an error on a CAICCI Init request on behalf of the specified user.
Action:
This message is followed by a DC900572 message indicating the error encountered. Re-attempt the transfer request. If the problem persists, save all error information and contact Technical Support.
Reason:
The CA Dispatch CAICCI Transfer Server received an error on a CAICCI Send request on behalf of the specified user.
Action:
This message is followed by a DC900572 message indicating the error encountered. Re-attempt the transfer request. If the problem persists, save all error information and contact Technical Support.
Reason:
The CA Dispatch CAICCI Transfer Server received an error on a CAICCI Receive request on behalf of the specified user.
Action:
This message is followed by a DC900572 message indicating the error encountered. Re-attempt the transfer request. If the problem persists, save all error information and contact Technical Support.
Reason:
The CA Dispatch CAICCI Transfer Server received an error on a CAICCI Converse request on behalf of the specified user.
Action:
This message is followed by a DC900572 message indicating the error encountered. Re-attempt the transfer request. If the problem persists, save all error information and contact Technical Support.
Reason:
The CA Dispatch CAICCI Transfer Server received an error on a CAICCI Term request on behalf of the specified user.
Action:
This message is followed by a DC900572 message indicating the error encountered. Re-attempt the transfer request. If the problem persists, save all error information and contact Technical Support.
Reason:
The CA Dispatch CAICCI Transfer Server received a CAICCI error. This message contains the error text.
Action:
None.
Reason:
The CA Dispatch CAICCI Transfer Server task CADSKWIK is abnormally terminating for the specified user.
Action:
If this occurs during shutdown processing, it is a NORMAL situation. If not a shutdown, re-attempt the transfer request. If the problem persists, save all error information and contact Technical Support.
Reason:
The CA Dispatch CAICCI Transfer Server task, CADSKWIK, has ended.
Action:
None.
Reason:
This text is associated with various CA Dispatch CAICCI Transfer Server messages.
Action:
None.
Reason:
This error information is associated with various CA Dispatch CAICCI Transfer Server messages.
Action:
None.
Reason:
CAICCI Origin ID associated with various CA Dispatch CAICCI Transfer Server messages.
Action:
None.
Reason:
Program CADSXCCI received a record from the client that is greater that 256 bytes long.
Action:
The client file being uploaded is not supported for upload. Upload a different file.
Reason:
Program CADSXCCI determined that it received an invalid data block from the client during an upload.
Action:
Re-attempt the transfer request. If the problem persists, contact Technical Support.
Reason:
Program CADSXCCI received an error from the client.
Action:
The message contains the error text from the PC. Re-attempt the transfer request. If the problem persists, save all error information and contact Technical Support.
Reason:
Program CADSXCCI is indicating that the specified user with the specified Origin ID is ending the transfer.
Action:
None.
Reason:
Program CADSXCCI received an invalid message from the client.
Action:
This message is followed by the error message text that contains the invalid message. Re-attempt the transfer request. If the problem persists, save all error information and contact Technical Support.
Reason:
Program CADSXCCI encountered a CAICCI error during the transfer.
Action:
This message displays the CAICCI error message text that contains the error. Try the transfer request again. If the problem persists, save all error information and contact Technical Support.
Reason:
While performing the indicated function, program CADSXCCI did not receive a response from the client in the required amount of time.
Action:
The session is disconnected. Re-attempt the transfer request. If the problem persists, save all error information and contact Technical Support.
Reason:
Program CADSXCCI has received an error attempting to transfer the report using the IND$FILE interface.
Action:
Re-attempt the transfer using the standard CAICCI interface. Make sure your client software includes IND$FILE transfer support. If the problem persists, save all error information and contact Technical Support.
Reason:
The specified user is attempting to initiate an IND$FILE transfer but is already using IND$FILE under another session.
Action:
None.
Messages DC900600 to DC900608 are the Audit Trail Messages.
All audit trail messages are saved in the DSLOG SYSOUT data set of the region where the user is signed on. The user can set up the started task JCL to have the DSLOG sent as SYSOUT back through CA Dispatch for archiving, thereby preserving the audit trail in CA Dispatch. Every message sent to the DSLOG is saved with a date and time stamp preceding the message.
Reason:
A database update has been made from the online screens.
UUUUUUUU = User name PPPPPPPP = Panel name FFFFFFF = database function (ADDED, UPDATED, DELETED or EXTRACT) DDD..DDD = descriptive text about the record being updated
An example of a message from the Report Base Definition screen:
04/08/18 04:12:33 DC900600 User:SMIKE01 Panel:VRDMU110 UPDATED REPORT:TESTRP
An example of a message from the Report Recipient Definition Screen:
04/08/18 04:12:33 DC900600 User:SMIKE01 Panel:VRDMU130 ADDED REPORT:TESTRPT
An example of a message from the CA OM Web Viewer Report List Screen when an archived report is requested for viewing:
05/07/21 04:12:33 DC900600 User:SIELE01 Panel:DSXARPS EXTRACT REQUEST ISSUED FOR RPT:AL JOB:SIELE01A, 07/21/2005, 15:05
Action:
None.
Reason:
A reprint from archive has been requested from the online screens.
UUUUUUUU = User name
PPPPPPPP = Panel name
RRRRRRRR = Report being reprinted
JJJJJJJJ = Jobname of the report being reprinted
T = Type of reprint (O-OLV, P-Print all, R-Print Selective,
A-Arch, C-Arch new date/time)
MM/DD/YY = Date report was originally archived
HH/MM = Time report was originally archived
CCC...CC = Recipient if the reprint type = R (Selective) RNRNRNRN = Report name for distribution to use during processing JNJNJNJN = Jobname for distribution to use during processing
An example a reprint for all recipients without changing report or job name:
08/18/2004 04:12:55 DC900601 User:SUSER01 Panel:VARMI200 Reprint/Arch:TESTRPT,SUSER01A,P, DATE:07/26/2005, TIME:16:06,,,
An example that obtains a reprint for a specific recipient and changes the report name and job name:
08/18/2004 04:13:10 DC900601 User:SUSER01 Panel:VARMI200 Reprint/Arch:TESTRPT,SUSER01A R, DATE:07/26/2005, TIME:16:06,KEVIN SMITH,DEFDTEST,DEFDJOB1
Action:
None.
Reason:
An Online Viewing reprint has been requested from the Report Route Screen (VOVMI110) or from the Online Viewing Print Request Screen (VOVMI330).
UUUUUUUU = User name
PPPPPPPP = Panel name, either VOVMI330 or VOVMI110
RRRRRRRR = Report being reprinted
JJJJJJJJ = Jobname of the report being reprinted
T = Type of reprint (P-Printer *Printer, O-Orig Rpt/Rcp, C-Orig
Rpt/Rcp with Class/Dest Overrides)
reprint is from panel VOVMI110
JNJNJNJN = Jobname for distribution to use during processing if the
reprint is from panel VOVMI110
CCC...CCC = Recipient if the reprint was from panel VOVMI330
PPPPPPPP = Profile name used for customized print if the request
was from panel VOVMI330 An example a reprint from panel VOVMI110:
08/18/2004 04:12:55 DC900602 User:SUSER01 Panel:VOVMI110 Reprint/OLV:TESTRPT,SUSER01A,NEWRPT,NEWJOB
An example a reprint from panel VOVMI330:
08/18/2004 04:13:10 DC900602 User:SUSER01 Panel:VOVMI330 Reprint/OLV:TESTRPT,SUSER01A,KEVIN SMITH,C,TESTPROF
Action:
None.
Reason:
A PC selective download request has been added using the online screens.
UUUUUUUU = User name PPPPPPPP = Panel name RRRRRRRR = Report for download JJJJJJJJ = Jobname of the report for download CCC...CCC = Recipient if the reprint was from panel VOVMI330 DDDDDD = Create date of the report being downloaded TTTTTT = Create time of the report being downloaded PCPCPCPC = PC User for whom the request is being created
An example of a PC download request would look like:
08/18/2004 04:12:33 DC900603 User:SUSER01 Panel:VOVMI350 Added Download Rqst:TESTRPT,SUSER01A,KEVIN SMITH,930104,1245,SMIKE01
Action:
None.
Reason:
A PC selective upload request has been added using the online screens.
UUUUUUUU = User name PPPPPPPP = Panel name RRRRRRRR = Report name to be used during distribution JJJJJJJJ = Jobname to be used during distribution FFFFFFFFFFFF = PC File name of the file to be uploaded CCC...CCC = Recipient requesting the upload PCPCPCPC = PC User for who the request is being created
An example of a PC upload request:
08/18/2004 04:12:33 DC900604 User:SUSER01 Panel:VOVMU360 Added Upload Rqst:TESTRPT,SUSER01A,KEVIN SMITH,930104,1245,SUSER01
Action:
None.
Reason:
A bundle was updated from the online screens.
UUUUUUUU = User name PPPPPPPP = Panel name DDD...DDD = Descriptive text about the bundle being updated
An example of a report being deleted from a bundle (and causing this message to be produced):
08/18/2010 06:25:26 DC900605 User:USERN01 Panel:VOPMI810 Updated Bundle:A22BUNDL DELETED TESTRPT,SUSER01A,K. SMITH
An example of a bundle resorted by report, then job, then recipient, then pages:
08/18/2010 06:25:36 DC900605 User:USERN01 Panel:VOPMI810 Updated Bundle:A22BUNDL SORT RPT,JOB,RCP,PAGES
Action:
None.
Reason:
A bundle was updated from the online screens.
UUUUUUUU = User name PPPPPPPP = Panel name QQQQQ = RIDF Queue (ARCH, RPI, OTHER) RRRRRRRR = Report name of the entry that was updated JJJJJJJJ = Jobname of the entry that was updated DDD...DDD = Descriptive text about the update
For example, a report being deleted out of the RIDF produces this message:
08/18/2010 06:25:26 DC900606 User:USERN01 Panel:VOPMI820 Updated RIDF Queue:RPI TESTRPT,TESTJOB1 DELETED
For example, a report being put on HOLD through the RIDF produces this message:
08/18/2010 06:25:26 DC900606 User:USERN01 Panel:VOPMI820 Updated RIDF Queue:ARCH TESTRPT,TESTJOB1 HELD
Action:
None.
Reason:
Someone started or ended one of the subtasks from the online system.
UUUUUUUU = User name
PPPPPPPP = Panel name
NNNNNN = Started or Ended
TTTTTT = Name of the task started or ended (RPI, RPO, ARCHIVE,
EXTRACT, DIST, STAT)
For example, a user starting the RPI task produces this message:
08/18/2010 06:25:26 DC900607 User:USERN01 Panel:VOPMI100 STARED Task:RPI
Action:
None.
Reason:
A report was processed by RPI under the undefined report definition as defined on screen VSGMU110. rrrrrrrr, jjjjjjjj, nnnnn is the original report, job name, and job # of the report processed.
Action:
None.
Reason:
A record to be downloaded to the PC during a binary transfer has an invalid record length. This is an internal logic error.
Action:
Contact Technical Support.
Reason:
The binary PC download foreground program, CADSDLBF, encountered an error condition.
Action:
This message contains the error message text from CADSDLBF. Check any previously issued messages for additional information. Re-attempt the transfer request. If the problem persists, save all error information and contact Technical Support.
Reason:
The binary PC download background program, CADSDLBB, had its STAE recovery routine invoked.
Action:
Check the CAILOG and any previously issued messages for additional information. Re-attempt the transfer request. If the problem persists, save all error information and contact Technical Support.
Reason:
An error occurred while attempting to begin a binary PC download.
Action:
Check any previously-issued messages from CADSXCCI for any additional information. Re-attempt the transfer request. If the problem persists, save all error information and contact Technical Support.
Reason:
An error occurred while attempting to write data during a binary PC download.
Action:
Check any previously-issued messages from CADSXCCI for any additional information. Re-attempt the transfer request. If the problem persists, save all error information and contact Technical Support.
Reason:
An error occurred while attempting to end a binary PC download.
Action:
Check any previously-issued messages from CADSXCCI for any additional information. Re-attempt the transfer request. If the problem persists, save all error information and contact Technical Support.
Reason:
An error occurred while attempting to allocate a report file for a binary download. This message is preceded by a DC970033 message.
Action:
Re-attempt the transfer request. If the error persists, save all error information and contact Technical Support.
Reason:
An error occurred while attempting to de-allocate a report file for a binary download. This message is preceded by a DC970033 message.
Action:
Re-attempt the transfer request. If the error persists, save all error information and contact Technical Support.
Reason:
An error occurred while attempting to open a report file for a binary download.
Action:
Re-attempt the transfer request. If the error persists, save all error information and contact Technical Support.
Reason:
An error occurred while attempting to read from a report file for a binary download.
Action:
Re-attempt the transfer request. If the error persists, save all error information and contact Technical Support.
Reason:
An error occurred while attempting to close a report file for a binary download.
Action:
Re-attempt the transfer request. If the error persists, save all error information and contact Technical Support.
Reason:
An error occurred while attempting to delete the ACIF Status File for the binary download report.
Action:
This message is preceded by a combination of messages DC970120 through DC970130. Perform the action required by the messages. Re-attempt the transfer request. If the error recurs, it will be preceded by another error message. Save all error information and contact Technical Support.
Reason:
PC Download Binary File name in error.
Action:
None.
Reason:
A program exception occurred in program CADSDLBF and its ESTAE recovery routine was invoked.
Action:
Re-attempt the transfer request. If the error persists, save all error information and contact Technical Support.
Reason:
An error occurred while attempting to reprint a bundle. ssss is the error status and rrrrrrrrrrrr is the IDMS database record.
Action:
Review the log for any CA IDMS messages that have occurred and take appropriate action based on those messages. Refer to the CA IDMS Error Codes Messages volumes for more information.
Reason:
A user attempted to reprint a bundle while the CADDSPL task was inactive.
Action:
Start the CADDSPL task and retry the reprint. If this error recurs, save all error information and contact Technical Support.
Reason:
A user has requested that a bundle be printed but some of the reports were unavailable. A common reason for getting this error message is when a report associated with this bundle was deleted.
Action:
None.
Reason:
A user requested that a bundle be reprinted but the report is already reprinting.
Action:
None.
Reason:
Client has updated the CADDSPL Option fields, Task Suffix or Root LDS DSN on the VSGMU110 Sysgen Control Information Screen. In order for the change to take effect, you must recycle the CA Dispatch main region.
Action:
Re-cycle the CA Dispatch main region.
Reason:
This is an internal logic error with CA Dispatch LDS Buffer Manager, CADSLDIO.
Action:
Contact Technical Support.
Reason:
The address of the LDS I/O Manager was not provided on a $LDSREAD macro with the CALL=NO option.
Action:
Contact Technical Support.
Reason:
Program CADSLDIO received bad return code values from program CADS9SPL.
Action:
See the previously-issued messages from CADS9SPL and contact Technical Support.
Reason:
An invalid record was read from CADDSPL. This is an internal logic error.
Action:
The requesting task will abend with a U1434 abend code. If the task is RPI, MSG or Archive, enter the Report Input Display Facility screen, VOPMI200, and place the report in HOLD status. If the task is RPO, do not release the Logical Bundle for printing. If the task is OLV, do not view the report until the problem is resolved. Save all error information and contact Technical Support.
Reason:
A request for an invalid LDS input queue was made. This is an internal logic error.
Action:
Contact Technical Support.
Reason:
The CADDSPL started task is not executing.
Action:
Start the CADDSPL task.
Reason:
No records were found by CADDSPL. This will occur if no reports were sent to the interface.
Action:
Send report output data to the class/destination values set on screen VSGMU105.
Reason:
An invalid parameter list was passed to CADDSPL. This is an internal logic error.
Action:
Contact Technical Support.
Reason:
An error was encountered by CADDSPL during processing of #CAS9SPL request. Internal logic error.
Action:
Contact Technical Support.
Reason:
Either an invalid LDS Token was passed on a read request or the SPLHDR2 record contains bad data pointers. Internal logic error.
Action:
Contact Technical Support.
Reason:
An invalid LDS Token was passed on an update request. This is an internal logic error.
Action:
Contact Technical Support.
Reason:
An invalid LDS Token was passed on an update request. This is an internal logic error.
Action:
Contact Technical Support.
Reason:
An invalid LDS Token was passed on an update request. This is an internal logic error.
Action:
Contact Technical Support.
Reason:
An invalid return code of rc with reason code reas was returned by CADDSPL during an update function.
Action:
Contact Technical Support.
Reason:
An attempt to modify a report from the LDS failed because CADDSPL is in quiesce (read only) mode and all update activity is prohibited.
Action:
Restart task processes when CADDSPL is in update mode. To enable update mode, issue the following command from the MVS console:
F SPLx,RESUME
Reason:
A report cannot be deleted while it is being processed.
Action:
Wait until the report is not in OPEN status on screen VOPMI200 before attempting any updates.
Reason:
An invalid LDS Token was passed on an update request. This is an internal logic error.
Action:
Contact Technical Support.
Reason:
An invalid LDS Token was passed on an update request. This is an internal logic error.
Action:
Contact Technical Support.
Reason:
An attempt to delete a report from the LDS failed because CADDSPL is in quiesce (read only) mode and all update activity is prohibited.
Action:
Reissue the delete request when CADDSPL is in update mode. To enable update mode, issue the following command from the MVS console:
F SPLx,RESUME
Reason:
An attempt to delete a report from the LDS failed. The following list explains the possible return codes and reasons associated with the failure.
SPLHDR2 for the report has been deleted but the report blocks have been abandoned.
The report is not found in the data space.
The report is open and cannot be deleted.
SPLHDR2 for the report cannot be found in the index.
CADDSPL is quiesced.
Reason:
CA Dispatch Log Driver Task was shutdown by either a STOPCADS or E DLOG command.
Action:
Issue S DLOG to restart Log Driver if needed.
Reason:
CA Dispatch Log Driver Task or CA Dispatch address space is abending.
Action:
If CA Dispatch Log Driver Task abended, restart with an S DLOG command. If CA Dispatch address space abended, restart it. In either case, save all abend information and contact Technical Support.
Reason:
An error occurred in program CADSJSAL while attempting to allocate or deallocate a JES data set.
Action:
Save all error information and contact Technical Support.
Reason:
An error occurred in program CADSJSAL while attempting to allocate a JES data set for input.
Action:
Restart the abending CA Dispatch task. If the problem persists, contact Technical Support.
Reason:
An error occurred in program CADSJSAL while attempting to allocate a JES data set for output.
Action:
Restart the abending CA Dispatch task. If the problem persists, contact Technical Support.
Reason:
An error occurred in program CADSJSAL while attempting to deallocate a JES data set.
Action:
Restart the abending CA Dispatch task. If the problem persists, contact Technical Support.
Reason:
An invalid destination was used to allocate a JES data set for the output bundle ID displayed.
Action:
The system reattempted the allocation with a blank destination value. Correct the invalid destination value.
Reason:
An invalid output name was used to allocate a JES data set for the bundle ID displayed.
Action:
The system reattempted the allocation with a blank output name value. Correct the invalid output name value.
Reason:
An invalid parmlist was used to allocate a JES data set for the output bundle ID displayed.
Action:
The system reattempted the allocation with a corrected parmlist. Correct the value.
Reason:
An I/O Error occurred in CADSJSIO while reading data from a JES data set.
Action:
Restart the abending task. If the problem persists, place the data set in HOLD status and contact Technical Support.
Reason:
An I/O Error occurred in CADSJSIO while writing data to a JES data set.
Action:
Restart the abending task. If the problem persists, contact Technical Support.
Reason:
An error occurred in program CADSTPAL while attempting to allocate or deallocate a tape data set.
Action:
Save all error information and contact Technical Support.
Reason:
An I/O Error occurred in CADSTPIO while reading data from a tape data set.
Action:
Restart the abending task. If the problem persists, contact Technical Support.
Reason:
An I/O Error occurred in CADSTPIO while writing data to a tape data set.
Action:
Restart the abending task. If the problem persists, contact Technical Support.
Reason:
An I/O Error occurred in CADSTPIO while writing data to a tape data set.
Action:
Restart the abending task. If the problem persists, contact Technical Support.
Reason:
An error occurred in program CADSDSAL while attempting to allocate or deallocate a DASD data set.
Action:
Save all error information and contact Technical Support.
Reason:
An I/O Error occurred, in CADSDSIO, reading data from a DASD data set.
Action:
Restart the abending task. If the problem persists, contact Technical Support.
Reason:
An I/O Error occurred in CADSDSIO while writing data to a DASD data set.
Action:
Restart the abending task. If the problem persists, contact Technical Support.
Reason:
An I/O Error occurred in CADSFTIO while reading data from a FileTek device.
Action:
Restart the abending task. If the problem persists, contact Technical Support.
Reason:
An I/O Error occurred in CADSFTIO while writing data to a FileTek device.
Action:
Restart the abending task. If the problem persists, contact Technical Support.
Reason:
The CA Dispatch Sysgen control record for Distribution was not found by the CA Dispatch initialization task.
Action:
Access screen VSGMI100 and define all CA Dispatch Sysgen information.
Reason:
The CA Dispatch Sysgen control record for Archive was not found by the CA Dispatch initialization task.
Action:
Access screen VSGMI100 and define all CA Dispatch Sysgen information.
Reason:
A program specified in the CA Dispatch Program Vector Table could not be loaded.
Action:
Save the program name and contact Technical Support.
Reason:
The CA Dispatch startup process is successfully completed.
Action:
None.
Reason:
An error occurred in the specified database program. This message is followed by messages DC970043 through DC970045.
Action:
Contact Technical Support.
Reason:
This is an IDMS Error Status value from a database error.
Action:
None.
Reason:
This is an IDMS database record from a database error.
Action:
None.
Reason:
This is an IDMS database set from a database error.
Action:
None.
Reason:
The CA Dispatch Central Vector Table could not be allocated in the IDMS Storage Pool. A CA Dispatch bundle recovery program has started to determine if a backup is needed.
Action:
Increase the STORAGE POOL value in the current CA Dispatch Usergen option member.
Reason:
CA Dispatch can only execute on MVS/ESA or higher operating systems.
Action:
Contact Technical Support.
Reason:
The CA Dispatch Central Program Table could not be loaded into the IDMS program pool.
Action:
Contact Technical Support.
Reason:
The CA Dispatch Log Driver Subtask could not be started.
Action:
Try to start the Log Driver with the S DLOG command. If this fails, all messages will be written to the operator's console and will not prevent CA Dispatch from executing. Contact Technical Support.
Reason:
The VTAM line VTMSYS01 was not built using the CA Dispatch Usergen.
Action:
Use the CA Dispatch Usergen procedure to add a VTAM line named VTMSYS01 if a VTAM line is required.
Reason:
The CA Dispatch Recovery Termination Manager subtask was invoked due to a system abend.
Action:
Save all abend information and attempt to fix the problem. If the problem persists, contact Technical Support.
Reason:
The CA Dispatch Recovery Termination Manager subtask was successfully started.
Action:
None.
Reason:
The CA Dispatch Recovery Termination Manager subtask was invoked due to a system abend.
Action:
Save all abend information and attempt to fix the problem. If the problem persists, contact Technical Support.
Reason:
The CA Dispatch Recovery Termination Manager subtask has finished processing a system abend.
Action:
None.
Reason:
The CA Dispatch Recovery Termination Manager subtask has ended successfully.
Action:
None.
Reason:
The CA Dispatch bundle recovery program has started the process of determining whether a restore is needed.
Action:
None.
Reason:
The bundle structures are being restored from the bundle recovery data set created by the bundle recovery backup.
Action:
None.
Reason:
Bundle recovery will restore from the CADDSPL Spool Interface if a problem occurred creating or reading the bundle recovery dataset.
Action:
Bundle recovery will check each processed report in the CADDSPL Spool Interface to see if it previously was part of a bundle.
If the report was part of a bundle, bundle recovery will requeue the report to be processed by RPI.
It is possible that a report or bundle could be created twice if bundle recovery was processing the bundle recovery data set, built a bundle, encountered a later error and then restored from the CADDSPL Spool Interface. The reports successfully restored from the bundle recovery data set will also be written to RPI as part of the second restore operation.
Reason:
The Bundle Recovery program has successfully finished restoring the bundle structures.
Action:
None.
Reason:
The Bundle Recovery program found that there were no bundle structures to restore.
Action:
None.
Reason:
The bundle recovery program encountered an error that caused some or all of the bundle structures to not be restored.
Action:
If the problem persists, contact Technical Support.
Reason:
The CA Dispatch bundle recovery program has started determining if a backup is needed.
Action:
None.
(represents one of the following messages)
Reason:
The bundle recovery program has successfully finished backing up the bundle structures.
Action:
None.
Reason:
The Bundle Recovery program found that there were no bundle structures to back up.
Action:
None.
Reason:
The bundle recovery program encountered an error that prevented the bundle structures from being backed up.
Action:
This message will be preceded by messages indicating the actual cause of the failure. No bundle recovery data set exists; the bundle recovery program will restore from CADDSPL upon startup.
If the problem persists, contact Technical Support.
Reason:
The bundle recovery program could not allocate the bundle control file for input or output processing.
Action:
If the problem persists, contact Technical Support.
Reason:
The bundle recovery program could not deallocate the bundle control file.
Action:
If the problem persists, contact Technical Support.
Reason:
The bundle recovery program could not open the bundle control file for Input or Output processing.
Action:
If the problem persists, contact Technical Support.
Reason:
The bundle recovery program could not read or write to the bundle control file for input or output processing.
Action:
If the problem persists, contact Technical Support.
Reason:
The bundle recovery program could not close the bundle control file.
Action:
If the problem persists, contact Technical Support.
Reason:
The Bundle Recovery program could not allocate the bundle data file for Input or Output processing.
Action:
If the problem persists, contact Technical Support.
Reason:
The Bundle Recovery program could not deallocate the bundle data file.
Action:
If the problem persists, contact Technical Support.
Reason:
The Bundle Recovery program could not open the bundle data file for Input or Output processing.
Action:
If the problem persists, contact Technical Support.
Reason:
The Bundle Recovery program could not read or write to the bundle data file for Input or Output processing.
Action:
If the problem persists, contact Technical Support.
Reason:
The Bundle Recovery program could not close the bundle data file.
Action:
If the problem persists, contact Technical Support.
CADDSPLx is the STCname of the initialization address space
Reason:
The Bundle Recovery program encountered an error attempting to read a report from CADDSPL while restoring bundled reports from it.
Action:
If the problem persists, contact Technical Support.
CADDSPLx is the the STCname of the initialization address space
Reason:
The Bundle Recovery program encountered an error attempting to update a report on CADDSPL while restoring bundled reports from it.
Action:
If the problem persists, contact Technical Support.
Reason:
The CA Dispatch Recovery Termination Manager detected and successfully terminated a CA Dispatch foreground subtask.
Action:
None.
Reason:
The CA Dispatch Recovery Termination Manager detected but could not terminate a CA Dispatch foreground (MVS) subtask. This will usually result in an SA03 abend after CA Dispatch completes its shutdown processing.
Action:
Save all dump and error information and contact Technical Support.
Reason:
An invalid SMF record was written. This is an internal logic error
Action:
Contact Technical Support.
Reason:
(a) An error was received from SMF.
Action:
(a) Contact your system programmer.
Reason:
A job scheduler interface program encountered an error and passed the indicated text for reference.
Action:
Consult the appropriate Error Messages Guide for job scheduler interface.
Reason:
A job scheduling interface was selected on screen VSGMU110 but the associated interface module was not found.
Action:
Have your system's personnel add the module indicated into the CA Dispatch load library.
Reason:
An error occurred in program CADSJSDO while attempting to allocate a dynamic OUTPUT request.
Action:
Save all error information and contact Technical Support.
Reason:
An error occurred in program CADSJSDO while attempting to delete a dynamic OUTPUT request.
Action:
Save all error information and contact Technical Support.
Reason:
File name of the file that encountered the dynamic allocation or deallocation error.
Action:
See previously-issued dynamic allocation error messages.
Reason:
An error occurred in the specified database program. This message is followed by messages DC970102 through DC970104.
Action:
You can also review the log for any CA IDMS messages that have occurred and take appropriate action based on those messages. Refer to the CA IDMS Error Codes Messages volumes for more information. Contact Technical Support.
Reason:
This is an IDMS Error Status value from a database error.
Action:
None.
Reason:
This is an IDMS database record from a database error.
Action:
None.
Reason:
This is an IDMS database set from a database error.
Action:
None.
Reason:
The table to build ACIF JCL statements has run past the end.
Action:
Contact Technical Support.
Reason:
The CA Dispatch ACIF JCL program, CADSAFJC, cannot find the JOBCARD member in the ACIF Parameter Library that is specified on the Default AFP Resources Screen, VSGMU241.
Action:
Add the JOBCARD member to the ACIF Parameter Library. This member should contain JCL JOB statements for ACIF JCL execution. After adding the member, rerun the ACIF request.
Reason:
The CA Dispatch database record that contains the default AFP resource definitions cannot be found on the database.
Action:
Add all the required information on the Default AFP Resources Screen, VSGMU241 and rerun the ACIF request.
Reason:
The CA Dispatch Inline AFP Resource Group specified in the message cannot be found.
Action:
Either add an Inline AFP Resource Group on the Inline AFP Resource Group Definition Screen, VSGMU245, or change the Resource Group name on the Report Archive Definition Screen, VARMU100, to an existing Resource Group name. After making the changes, rerun the ACIF request.
Reason:
The CA Dispatch Inline AFP Library Group specified in the message cannot be found.
Action:
Modify the Inline AFP Library Group name on the Inline AFP Resource Group Definition Screen, VSGMU245, for the Resource Group being processed to the name of an existing Library Group. After making the changes, rerun the ACIF request.
Reason:
The CADSAFJC program issued a database request, which encountered an error.
Action:
This message is preceded by messages DC970101 through DC970104. See these messages for the appropriate action.
Reason:
An error occurred while attempting to allocate an ACIF Parameter library. This message is preceded by a DC970033 message.
Action:
See if the ACIF Parm Library can be browsed online. If yes, save all error information and contact Technical Support.
Reason:
An error occurred while attempting to open an ACIF Parameter library.
Action:
See if the ACIF Parm Library can be browsed online. If so, save all error information and contact Technical Support.
Reason:
An error occurred while attempting to read an ACIF Parameter library.
Action:
See if the ACIF Parm Library can be browsed online. If yes, save all error information and contact Technical Support.
Reason:
An error occurred while attempting to close an ACIF Parameter library.
Action:
See if the ACIF Parm Library can be browsed online. If yes, save all error information and contact Technical Support.
Reason:
An error occurred while attempting to deallocate an ACIF Parameter library. This message is preceded by a DC970033 message.
Action:
See if the ACIF Parm Library can be browsed online. If yes, save all error information and contact Technical Support.
Reason:
ACIF Parm Library name in error.
Action:
None.
Reason:
An error occurred while attempting to open the ACIF JCL JES Reader file. Most likely the ACIFRDR DD SYSOUT=(A,INTRDR) statement is missing from either the CA Dispatch startup JCL or the CA Dispatch External Archive JCL.
Action:
Add the statement to the JCL Procedures CADSDISP and CADSXTAR in your CA PROCLIB.
Reason:
An error occurred while attempting to allocate an new ACIF Status file. This message is preceded by a DC970033 message.
Action:
Rerun the ACIF request. If the problem persists, save all error information and contact Technical Support.
Reason:
An error occurred while attempting to allocate an existing ACIF Status file. This message is preceded by a DC970033 message.
Action:
Rerun the ACIF request. If the problem persists, save all error information and contact Technical Support.
Reason:
An error occurred while attempting to deallocate an ACIF Status file. This message is preceded by a DC970033 message.
Action:
Rerun the ACIF request. If the problem persists, save all error information and contact Technical Support.
Reason:
An error occurred while attempting to open an ACIF Status file.
Action:
Rerun the ACIF request. If the problem persists, save all error information and contact Technical Support.
Reason:
An error occurred while attempting to open an ACIF Status file.
Action:
Rerun the ACIF request. If the problem persists, save all error information and contact Technical Support.
Reason:
An error occurred while attempting to close an ACIF Status File.
Action:
Rerun the ACIF request. If the problem persists, save all error information and contact Technical Support.
Reason:
An error occurred while attempting to write to an ACIF Status File.
Action:
Rerun the ACIF request. If the problem persists, save all error information and contact Technical Support.
Reason:
An error occurred while attempting to read an ACIF Status File.
Action:
Rerun the ACIF request. If the problem persists, save all error information and contact Technical Support.
Reason:
CADSAFST was called with an invalid function code.
Action:
Contact Technical Support.
Reason:
An attempt to read an ACIF Status File found that the file no longer exists.
Action:
Rerun the ACIF request. If the problem persists, save all error information and contact Technical Support.
Reason:
ACIF Status File name in error.
Action:
None.
Reason:
An error occurred while attempting to allocate an existing ACIF Report file in order to delete it. This message is preceded by a DC970033 message.
Action:
See if the file exists. If it does, save all error information and contact Technical Support.
Reason:
An error occurred while attempting to deallocate an existing ACIF Report file in order to delete it. This message is preceded by a DC970033 message.
Action:
See if the file exists. If it does, save all error information and contact Technical Support.
Reason:
CADSAFRP was called with an invalid function code.
Action:
Contact Technical Support.
Reason:
An attempt to delete an ACIF Status File found that the file no longer exists.
Action:
None.
Reason:
ACIF Report File name in error.
Action:
None.
Reason:
This message is received on the VPCMU310 screen when trying to delete a PC download request and can occur from the Main region or the Online Viewing Only region. Additionally, a "Dynamic Allocation Error = 0860" message will appear on the CA Dispatch Job Log and PCLOG.
Action:
Re-attempt the desired ACIF function. If the error recurs, it will be preceded by another error message. Save all error information and contact Technical Support.
The PC Control Screen (VPCMU100) may have missing Binary Transfer data in the Unit or Prefix fields. Enter the missing data in these two required fields.
Reason:
A program exception occurred in program CADSUBSQ and its STAE recovery routine was invoked.
Action:
Re-attempt the desired ACIF function. If the problem persists, contact Technical Support.
Reason:
The displayed CA Dispatch subtask was not started due to an MVS ATTACH error.
Action:
Re-attempt the desired ACIF function. If the problem persists, contact Technical Support.
Reason:
Program CADSUFSQ received an error from an ACIF Status File function.
Action:
This message is preceded by messages DC970120 through DC970130. Perform the action required of the preceding messages.
Reason:
Program CADSUFSQ received an error while processing the ACIF report file.
Action:
Contact Technical Support.
Reason:
An error return code was received from the IBM DSPSERV macro trying to create an internal Dispatch data space. Usually this message is generated in connection with the DC970182 message.
Action:
Review the action specified for DC970182.
Reason:
The data space requested could not be created by the IBM DSPSERV macro. The xxxxxxxx indicates which data space is having a problem and nn is the return code value.
Action:
Make sure that you have reviewed the requirements for "Updating the MAXCAD Assignment" outlined in Chapter 4 of the Getting Started Guide.
Review your IEFUSI installation exit for any system limitation on Data Space allocation. (see in z/OS MVS Installation Exits)
Contact Technical Support.
Reason:
An error occurred on the DSPSERV macro used to delete the named CA Dispatch data space.
Action:
MVS job termination will automatically delete data space. If the problem persists, contact Technical Support.
Reason:
An error occurred on the MVS/ESA ALESERV macro used to delete an ALET for the named CA Dispatch data space.
Action:
MVS job termination will automatically delete data space. If the problem persists, contact Technical Support.
Reason:
An invalid data space name was passed while attempting to delete the named CA Dispatch data space.
Action:
Internal logic error. Contact Technical Support.
Reason:
An invalid data space name was passed while attempting to allocate or free storage from the named CA Dispatch data space.
Action:
Internal logic error. Contact Technical Support.
Reason:
Internally allocated storage from the named CA Dispatch data space was overwritten.
Action:
Internal logic error. Contact Technical Support.
Reason:
Name of the CA Dispatch subtask that has abended.
Action:
Save all abend information and contact Technical Support.
Reason:
Abend code for CA Dispatch subtask that has abended.
Action:
Save all abend information and contact Technical Support.
Reason:
A CA Dispatch subtask program has abended.
Action:
Save all abend information and contact Technical Support.
Reason:
A CA Dispatch subtask program has abended.
Action:
Save all abend information and contact Technical Support.
Reason:
Offset of the abend with the abending program.
Action:
Save all abend information and contact Technical Support.
Reason:
Program Status Word at the time of the abend.
Action:
Save all abend information and contact Technical Support.
Reason:
General purpose registers at the time of the abend.
Action:
Save all abend information and contact Technical Support.
Reason:
This message indicates the status of the SDUMP macro in program CADSSTAE. The various message values are based on return codes from the SDUMP macro.
Action:
If the dump is successful, offload it to tape and send it to Technical Support for problem determination. If the dump was suppressed by DAE, there has already been a dump written for the same abend so this action is not necessary. If the dump is not successful, a SYSUDUMP will be written for the abend. Contact your system programmer to correct the problem.
Reason:
The CAIENF (CA Event Notification Facility) address space is required in order to run the CA Dispatch Status task.
Action:
Start your CAIENF address space (usually this is a "S ENF" command), and restart the CA Dispatch Status task.
Reason:
During initial checking, a specific ENF event has been found inactive. This event has to be active in order to run the CA Dispatch Status task. The following status is required for the CA Dispatch Status task :
CAS9280I - Event(DISP144 ) Status(*Active*) *Record* P CAS9280I - Event(DISP145 ) Status(*Active*) *Record* P CAS9280I - Event(DISP146 ) Status(*Active*) *Record* P CAS9280I - Event(ENFTERM ) Status(*Active*) Norecord P CAS9280I - Event(JOBINIT ) Status(*Active*) *Record* P CAS9280I - Event(JOBPRINT) Status(*Active*) *Record* P CAS9280I - Event(JOBTERM ) Status(*Active*) *Record* P CAS9280I - Event(STEPTERM) Status(*Active*) *Record* P
Action:
Activate the required event with the "ENF EVENT(eventname,ACT)" Operator command and restart the CA Dispatch Status task.
Reason:
The CA Dispatch Status task has been unable to restart its process from the last checkpoint taken on its previous run. The most frequent reason is ENF does not record the event.
Action:
This is a warning message. If this one appears frequently, check your ENF parameters especially for the following events:
CAS9280I - Event(DISP144 ) Status(*Active*) *Record* P CAS9280I - Event(DISP145 ) Status(*Active*) *Record* P CAS9280I - Event(DISP146 ) Status(*Active*) *Record* P CAS9280I - Event(JOBINIT ) Status(*Active*) *Record* P CAS9280I - Event(JOBPRINT) Status(*Active*) *Record* P CAS9280I - Event(JOBTERM ) Status(*Active*) *Record* P CAS9280I - Event(STEPTERM) Status(*Active*) *Record* P
If any of them has a Norecord status, use the 'ENF EVENT(eventname,REC)' Operator command.
Reason:
This message indicates a successful initialization of the CA Dispatch Status task.
Action:
None.
Reason:
This is an internal error. The xxxx is the hexadecimal value of the ENF macro return code. The yyyy is the hexadecimal value of the ENF macro info code.
Note: A special value of FFFF0001 indicates an unexpected event.
Action:
Save all abend information and contact Technical Support.
Reason:
This is an internal error. A specific initial function has failed. The xxxx is the hexadecimal value of the ENF macro return code. The yyyy is the hexadecimal value of the ENF macro info code.
Action:
Save all abend information and contact Technical Support.
Reason:
This is an internal error. CA Dispatch was unable to get the data for a specific event. The xxxx is the hexadecimal value of the ENF macro return code. The yyyy is the hexadecimal value of the ENF macro info code.
Action:
Save all abend information and contact Technical Support.
Reason:
This is an informational message. It follows DC970311 message(s) and indicates the shutdown of the Status task.
Action:
Message DC970311 indicates a lack of customization of one CAIENF event that CA Dispatch is looking for. Correct the Event customization in the CAIENF base.
Reason:
This is an informational message. It indicates that CA Dispatch received an Event from CAIENF that contained either; a blank JobID, or a JobID that does not conform to JES standards.
Action:
This may not be an error. It may mean that jobs are being generated in alternate ways. However, CA Dispatch only process and keep Status information based on JobIDs, so it will not use or save this record.
Reason:
This is a debugging message activated through the CA Dispatch "TRACE STATUS ON" command. This message is sent either before and after the CAIENF Event interface or in some specific place of the RDFGSTAT. Its purpose is for use by Technical Support during debugging. When the message appears after a CAIENF Event interface, the interface return code is added to the message text. The following are the CAIENF Event interface points :
The following messages are part of the RDFGSTAT design debugging :
Action:
Send this information on request from Technical Support.
Reason:
This is an informational message. It indicates when ENF Checkpoint Recovery of ENF Events is starting and completing. If the checkpoint was cleared using the option on the VSGMU190 screen, then no checkpoint will be passed and these messages will not be received.
Checkpoint recovery of ENF events is starting at the date/time indicated.
Checkpoint recovery of ENF events is complete.
Action:
None.
Reason:
CA Dispatch determined during initialization that it was establishing a link to a CADDSPLx task that is currently defined and in use by another CA Dispatch system.
Action:
The initialization process will automatically set the CADDSPL Option fields to blank and allow the initialization to continue. Update the CADDSPL Option fields Task Suffix and Root LDS DSN values on the Sysgen Control Information Screen (VSGMU110) with unique CADDSPL Task Suffix and Root LDS DSN values. Note that in order for the change to take effect, you must recycle the CA Dispatch main region
Reason:
As part of shutdown processing, Archive is terminating cleanly.
Action:
No action required.
Reason:
The CA Dispatch task RDBGSTAT (report status), which tracks report bundles from report status distribution, is abending. A dump of the task is written to the log file but CA Dispatch (online) will remain running.
Action:
Perform the following steps:
If you are not at a full-screen console, press PF4 until you see the Enter Next Task Code prompt, then enter the following command:
START STAT
Rnn,99START STAT
The report status distribution task RDBGSTAT will be restarted.
Note: Be sure to print the log file after the system is restarted.
Reason:
The CA Dispatch task ARBGARCH (report archiving), which processes reports from CADDSPL and archives them, is abending. A dump of the task is written but the CA Dispatch main region will remain running.
Action:
Perform the following steps:
START ARCH
R nn,99START ARCH
The report archival task ARBGARCH will be restarted.
Note: Save all error information.
Reason:
The CA Dispatch task ARBGEXTR (report extract), which selects reports from archival and sends them to report distribution, is abending. A dump of the task is written to the log file, but CA Dispatch (online) will remain running.
Action:
Perform the following steps:
START EXTR
Rnn,99START EXTR
The report extract task ARBGEXTR will be restarted.
Note: Be sure to print the log file after the system is restarted.
Reason:
A job that produces reports under the control of CA Dispatch has abended. Before CA Dispatch was informed of the abend, it printed a report from that job.
Action:
None.
Reason:
A database error occurred during Bin/Bundle processing of STAT.
Action:
Take corrective action for the indicated error status. You can also review the log for any CA IDMS messages that have occurred and take appropriate action based on those messages. Refer to the CA IDMS Error Codes Messages volumes for more information.
Reason:
The CA Dispatch shutdown task STOPCADS was successfully initiated.
Action:
None.
Reason:
Used by CADSMF05 to create WTO messages for MSGCLASS Event processing.
Action:
Defined by the user.
Reason:
Used by CADSIF07 to create WTO messages for Report Event processing.
Action:
Defined by the user.
Reason:
The job that runs External Archive has begun execution but it cannot find a request for External Archive to run. It will end. One possible reason for this is that an E ARCH was issued.
Action:
External Archive is a job that runs separately from CA Dispatch. Its execution is not totally under the control of CA Dispatch. Investigate the execution of this job compared to the commands issued online to CA Dispatch.
Reason:
The job that runs External Archive has begun execution and found that another copy of it is already executing. It will end. One possible reason for this is that an S ARCH XT was issued twice.
Action:
External Archive is a job that runs separately from CA Dispatch and its execution is not totally under the control of CA Dispatch. Investigate the execution of this job compared to the commands issued online to CA Dispatch.
Reason:
The job that runs External Archive has begun execution and failed to open the SYSCTL data set. This data set is required for it to execute properly.
Action:
Examine the JCL for External Archive and correct the specification for the SYSCTL and CAICTL DD statements.
Reason:
The background portion of Archive has abended while running in external mode.
Action:
Retain the OS dump produced for this abend and the CV log for this portion of time. Contact Technical Support.
Reason:
The job that runs External Extract has begun execution but it cannot find a request for external extract to run. It will end. One possible reason for this is that an E EXTR was issued.
Action:
External Extract is a job that runs separately from CA Dispatch. Its execution is not totally under the control of CA Dispatch. Investigate the execution of this job compared to the commands issued online to CA Dispatch.
Reason:
The job that runs external extract has begun execution and another copy of external extract is already executing. It will end. One possible reason for this is that an S EXTR XT was issued twice.
Action:
External Extract is a job that runs separately from CA Dispatch. Its execution is not totally under the control of CA Dispatch. Investigate the execution of this job compared to the commands issued online to CA Dispatch.
Reason:
The job that runs External Extract has begun execution and failed to open the SYSCTL data set. This data set is required for it to execute properly.
Action:
Examine the JCL for External Extract and correct the specification for the SYSCTL and CAICTL DD statements.
Reason:
The background portion of extract has abended while running in external mode.
Action:
Retain the OS dump produced for this abend and the CV log for this portion of time. Contact Technical Support.
Where reason is one of the following:
ALLOC JES FILE
ALLOC DASD DSN
CLOSE DASD DSN
ALLOC OPTL DSN
CLOSE OPTL DSN
Reason:
While processing report reportname jobname, extraction was unable to allocate or close a data set.
Action:
See prior DC970033 and DC970099 messages for the dynamic allocation error codes and resource name and fix the problem. If the problem persists, save all information and contact Technical Support.
Where xxxxxx is the VOLSER of the tape the extract task is trying to obtain.
Reason:
Another job has exclusive control of the tape. This message often occurs when an extract request is made for a report on the tape currently being accessed by the Archive task.
Note: This error can also occur when there are no drives available to mount a tape.
Action:
Determine which job controls the Volser in question and if possible eliminate the contention. The Extract task will retry the allocation request for the Volser. See the Active Archive Volser Management section in the User Guide for the Report Administrator for more information.
Reason:
The Archive task is active but it cannot establish communication with the database.
Action:
Restart the Archive task (S ARCH).
Reason:
The Archive task is active in external mode but it cannot establish communication with the database.
Action:
Restart the Archive task (S ARCH XT).
Reason:
An invalid return code was encountered in the VCFGALOC module.
Action:
Restart the abended ARCH task. If the problem persists, contact Technical Support.
Reason:
An invalid return code was encountered in the VCFGALOC module.
Action:
Restart the abended ARCH task. If the problem persists, contact Technical Support.
Reason:
An error occurred in the specified database program. This message is followed by messages DC980072 through DC980074.
Action:
Contact Technical Support.
Reason:
This is an IDMS Error Status value from a database error.
Action:
None.
Reason:
This is an IDMS database record from a database error.
Action:
None.
Reason:
This is an IDMS database set from a database error.
Action:
None.
Reason:
You are trying to extract a report from the current archive tape. Note that the Extract task will retry the allocation request for the Volser, and the extract will only occur after the current archive tape is freed.
Action:
Press Enter to allow extract from the current archive tape or enter CANCEL to cancel the request.
See the Active Archive Volser Management section in the User Guide for the Report Administrator for more information about ways to free the current archive tape for use by the EXTRACT subtask.
Reason:
The External Archive database program ARBGDB cannot make connection to the main CA Dispatch region.
Action:
If the main CA Dispatch region is active, restart the External Archive task (S ARCH XT). If the main CA Dispatch region is not active, start it.
ARCHx is the specific Archive task.
Reason:
Both the report and jobname are missing in the SPLHDR2 record. The associated DC980095 message should indicate available job information. This is an illogical condition. The archive request will be placed on hold and the Archive task will be shut down.
Action:
Review the Archive queue. Determine if there is a problem during CADDSPL intercept or SAPI processing. Restart the archive task. If the problem persists, contact Technical Support.
Reason:
A report is being requeued for reasons indicated by previous messages.
Action:
Archive processing requeues the report for additional analysis.
Reason:
A report is being requeued after an ABEND in archive processing while processing the report.
Action:
Archive processing requeues the report for additional analysis.
Reason:
An error occurred attempting to allocate a tape device or open a file on a tape.
Action:
Determine if there is a problem with the tape or tape drive. Archive will attempt to allocate the tape in four minutes. If the problem persists, contact Technical Support.
Reason:
The use of symbolics in the Archive data set name is limited to &RPTN. and &JOBN. This message indicates that a symbolic character ("&") was found but did not have either of the literals "RPTN" or "JOBN" following it.
Action:
Modify the DSN Prefix field on the Sysgen Archival Control Information Screen (VSGMU210) to contain valid symbolic parameters.
Reason:
An error occurred attempting to access a report on CADDSPL.
Action:
This message is preceded by additional error messages. Save all error information and contact Technical Support.
Reason:
An error occurred attempting to update a report on CADDSPL.
Action:
This message is preceded by additional error messages. Save all error information and contact Technical Support.
Reason:
The archive task has had no work for the specified number of minutes. This message appears after every five minutes of idle time, with the number of minutes increased each time.
Action:
No action necessary. This message is informational only. It is provided to allow other programs such as CA OPS or CA Opera to take some action, such as shutting down the task, after a user-determined idle period.
Reason:
The extract task has had no work for the specified number of minutes. This message appears after every five minutes of idle time, with the number of minutes increased each time.
Action:
No action necessary. This message is informational only. It is provided to allow other programs such as CA OPS or CA Opera to take some action, such as shutting down the task, after a user-determined idle period.
Reason:
An error occurred attempting to allocate an archive output file on tape. This message is preceded by a DC970029 message.
Action:
Determine if there is a problem with the tape or tape drive. Archive will attempt to allocate the tape in four minutes. If the problem persists, contact Technical Support.
Reason:
An error occurred attempting to deallocate an Archive output file on tape. This message is preceded by a DC970029 message.
Action:
Determine if there is a problem with the tape or tape drive. If the problem persists, contact Technical Support.
Reason:
An error occurred attempting to process the status file used for ACIF archiving of AFP resources.
Action:
This message is preceded by additional error messages. Perform the action associated with those messages. If the problem persists, save all error information and contact Technical Support.
Reason:
Specifies the report, job name and JES job number of the report that encountered a previously issued error message.
Action:
None.
Reason:
This dynamic allocation error (DYNALLOC) in OVFGSOUT for the output file occurred when doing a reprint from Online Viewing. No output was written.
Action:
Check the return code from DYNALLOC for the action required. If the Class or Destination is invalid, correct it on the Dedicated Sysout Control Information Screen (VSGMU105) and reprint the report.
Enter: ALL/ALLTAPE/ALLOPT/ARCHxTAPE/ARCHxOPT
Reason:
A subparameter is missing.
Action:
Enter the required subparameter ALL, ALLTAPE, ALLOPT, ARCHxTAPE or ARCHxOPT where x specfies the archive subtask
Reason:
This message is informational only.
Action:
No action required.
Reason:
This message is informational only.
Action:
No action required.
Reason:
An invalid subparameter was entered.
Action:
Enter a valid subparameter ALL, ALLTAPE, ALLOPT, ARCHxTAPE or ARCHxOPT where x specfies the archive subtask
Reason:
This is an error in the field after the second attempt to enter the correct subparameter.
Action:
Enter CLEAR again.
Reason:
A storage request for program CADSABSQ failed due to an insufficient amount of available IDMS storage.
Action:
Restart Archive. If the problem persists, shut down the CA Dispatch address spaces and increase the STORAGE parameter in the CA Dispatch Usergen parameter list. Run the Usergen JCL procedure, restart CA Dispatch and restart Archive. If the problem persists, contact Technical Support.
Reason:
The CADSAFSQ subtask was not started due to an MVS ATTACH error.
Action:
Restart Archive. If the problem persists, contact Technical Support.
Reason:
A program exception occurred in program CADSABSQ and its STAE recovery routine was invoked.
Action:
Restart Archive. If the problem persists, contact Technical Support.
Reason:
Program CADSAFSQ has ended prematurely due to an error condition.
Action:
Restart Archive. If the error recurs, it will be preceded by another error message. Save all error information and contact Technical Support.
Reason:
An error occurred attempting to archive AFP resources.
Action:
Restart Archive. If the error recurs, it will be preceded by another error message. Save all error information and contact Technical Support.
Reason:
An error occurred attempting to allocate a report file for archiving AFP resources. This message is preceded by a DC970033 message.
Action:
Restart Archive. If the error recurs, it will be preceded by another error message. Save all error information and contact Technical Support.
Reason:
An error occurred attempting to deallocate a report file for archiving AFP resources. This message is preceded by a DC970033 message.
Action:
Restart Archive. If the error recurs, it will be preceded by another error message. Save all error information and contact Technical Support.
Reason:
An error occurred attempting to open a report file for archiving AFP resources.
Action:
Restart Archive. If the error recurs, it will be preceded by another error message. Save all error information and contact Technical Support.
Reason:
An error occurred attempting to close a report file for archiving AFP resources.
Action:
Restart Archive. If the error recurs, it will be preceded by another error message. Save all error information and contact Technical Support.
Reason:
An error occurred attempting to write to a report file for archiving AFP resources.
Action:
Restart Archive. If the error recurs, it will be preceded by another error message. Save all error information and contact Technical Support.
Reason:
An error occurred for CADDSPL while retrieving a report for archiving AFP resources.
Action:
This message is preceded by error messages from the CA Dispatch LDS I/O Manager. Take the specified action for the preceding message. Restart Archive. If the error recurs, it will be preceded by another error message. Save all error information and contact Technical Support.
Reason:
The Physical Sequential File name is in error.
Action:
None.
Reason:
A program exception occurred in program CADSAFSQ and its ESTAE recovery routine was invoked.
Action:
Restart Archive. If the error persists, save all error information and contact Technical Support.
Reason:
Program CADSAFSQ received an error from an ACIF Status File function.
Action:
This message is preceded by messages DC970120 through DC970130. Perform the action required of the preceding messages. Restart Archive. If the error recurs, it will be preceded by another error message. Save all error information and contact Technical Support.
Reason:
Program CADSAFSQ received an error from an ACIF #DISP# File function.
Action:
This message is preceded by messages DC970150 through DC970158. Perform the action required of the preceding messages. Restart Archive. If the error recurs, it will be preceded by another error message. Save all error information and contact Technical Support.
Reason:
Archive or Extract tasks failed to load module LSMCALL to perform FileTek optical disk I/O functions.
Action:
Add FileTek optical disk loadlib to SYSLIB DD concatenation.
Reason:
A storage request for program pppppppp failed due to an insufficient amount of available IDMS storage.
Action:
Restart RPI. If the problem persists, shut down the CA Dispatch address spaces and increase the STORAGE parameter in the CA Dispatch Usergen parameter list. Run the Usergen JCL procedure, restart CA Dispatch, and restart RPI. If the problem still persists, contact Technical Support.
Reason:
The RPI Subtasks have abended with the specified code. Issued by program CADSIB00.
Action:
Determine if the abend code is listed in the Messages Guide. If so, attempt to correct the problem and restart the RPI Subtasks. If the problem persists, contact Technical Support.
Reason:
Specifies the report name, job name, and JES number of the report being processed at the time of the abend. Precedes message DC980201. Issued by program CADSIB00.
Action:
None.
Reason:
Internal PC request table has exceeded its limits. Issued by program CADSIB03. This is an internal logic error.
Action:
Contact Technical Support.
Reason:
A program exception occurred in program CADSIB03.
Action:
Save the abend information from CAILOG and contact Technical Support.
Reason:
An error occurred in the specified database program. This message is followed by messages DC980212 through DC980214.
Action:
Contact Technical Support.
Reason:
This is an IDMS Error Status value from a database error.
Action:
None.
Reason:
This is an IDMS database record from a database error.
Action:
None.
Reason:
This is an IDMS database set from a database error.
Action:
None.
Reason:
Indicates that the xx IDMS area is full.
Action:
If the file is maintained by a CA Dispatch database maintenance utility, then that utility must be executed to delete expired database records. If the file is not maintained by a utility, one of the database expansion utilities must be executed to enlarge the database area. See the CA Dispatch Systems Programmer Guide.
Reason:
RPI encountered a recoverable error attempting to process Report: RRRRRRRR, Job: JJJJJJJJ and Job#: NNNNNNN.
Action:
Check the CAILOG for any previously issued messages for additional information. Take appropriate action, than remove report from hold on the VOPMI200 Screen. If the problem persists, save all error information and contact Technical Support.
Reason:
As part of shutdown processing, RPI is marking all Logical Bundles ready for writing by RPO. This is an informational message issued by program CADSIF00.
Action:
No action required.
Reason:
A condition was encountered by RPI and it is terminating itself. Program CADSIF00.
Action:
Restart RPI. If the problem persists, save all information and contact Technical Support.
Reason:
As part of shutdown processing, RPI is terminating cleanly.
Action:
No action required. This is an informational message only.
Reason:
Information needed to execute the RPI task has not been added to the CA Dispatch database.
Action:
Enter online screen VSGMI100, enter the required information, and restart RPI.
Reason:
An RPI foreground program issued a database request, which encountered an error.
Action:
Restart RPI. If the problem persists, save all error information and contact Technical Support.
Reason:
RPI Program CADSIF02 encountered an error attempting to retrieve the next available report from CADDSPL. The CA Dispatch DSLOG file contains error messages from the LDS I/O manager that indicate the actual problem.
Action:
Restart RPI. If the problem persists, save all error information and contact Technical Support.
Reason:
A report recipient was designated for automated download but no report recipient PC extension record was found by RPI.
Action:
Select Option X3 on the VRDMU130 screen for the given report recipient and add the appropriate PC extension data listed on screen VRDMU150.
Reason:
A report was encountered that contained ANSI carriage control characters and had a lines per page value of zero specified on the Report Base Definition Screen (VRDMU110).
Action:
The report is bundled without carriage control conversion. If this is not what you want, change the Lines Per Page field on the Report Base Definition Screen (VRDMU110) to a non-zero value.
Reason:
RPI program, CADSIF06, has successfully recovered from a database deadlock condition. This message will be preceded by an IDMS deadlock message.
Note: This is an informational message. It may occur more frequently in CA Dispatch when running more than one RPI task. It indicates that CA Dispatch has recovered from a database deadlock and is continuing to process the report.
Action:
None.
Reason:
A report was marked for Online Viewing but due to an error it could not be added to Online Viewing and is marked to be archived.
Action:
This message should be preceded by a message for the error that caused the problem.
Reason:
A report was marked for Online Viewing but the Online Viewing Pages Table, from which OLV database records are created, is missing. This is an internal logic error.
Action:
Contact Technical Support.
Reason:
A command entered through Report Event Processing in RPI is in error or the scheduling module cannot be found.
Action:
Correct the command entered on screen VRDMU116 or have your Systems personnel add the module indicated into the CDMSLIB used by CA Dispatch.
Note: Type identifies the Scheduler being processed. Type 1 = CA Scheduler, Type 2 = CA 7. Module identifies the name of the module you were trying to access, or actually did access. RC identifies the problem encountered, IN = Invalid scheduling type; must be 1 or 2. NF = module Not Found, ccc = return code from the scheduler module.
Reason:
The action on the database is invalid; must be C, F or M.
Action:
Correct the event actions defined for reports.
Reason:
A bad request was made between modules. This is an internal logic error.
Action:
Contact Technical Support.
Reason:
This is an internal logic error; table address is missing.
Action:
Contact Technical Support.
Reason:
This is an internal logic error; table pointer is missing.
Action:
Contact Technical Support.
Reason:
There is insufficient storage available for RPI task or OLV.
Action:
Restart RPI or OLV.
Reason:
One of the fields in a Report Event Definition is incorrect.
Action:
Put the report on hold in the RPI queue, then go to the VRDMU115 screen for that report and check the Event Definition for errors in column number, comparator, action, or search text.
Reason:
RPI Program CADSIF04 was performing a Bundle Reprint and encountered an error attempting to process Report: RRRRRRRR and Job: JJJJJJJJ. This is an internal logic error.
Action:
Contact Technical Support.
Reason:
A storage request for program pppppppp failed due to an insufficient amount of available IDMS storage.
Action:
Restart RPO. If the problem persists, shut down the CA Dispatch address spaces and increase the STORAGE parameter in the CA Dispatch Usergen parameter list. Run the Usergen JCL procedure, restart CA Dispatch, and restart RPO. If the problem still persists, contact Technical Support.
Reason:
The RPO Driver Task has abended with a program exception.
Action:
Restart RPO. If the problem persists, contact Technical Support.
Reason:
This is an informational message indicating that the RPO Driver Task is normally terminating the specified number of active RPO Agents.
Action:
No action required.
Reason:
This is an informational message indicating that all RPO Agent Tasks are finished and the RPO Driver Task is terminating.
Action:
No action required.
Reason:
The RPO Agent Subtask has abended with the specified code.
Action:
Determine if the abend code is listed in the Messages Guide. If so, attempt to correct the problem, enter screen VRDMU820 and release the bundle marked in error. If the problem persists, contact Technical Support.
Reason:
Specifies the bundle ID, report name, and job name of the Logical Bundle being processed at the time of the abend. Precedes message DC980405. Program CADSOB00.
Action:
None.
Reason:
An RPO Agent program encountered an error.
Action:
This message is usually preceded by error messages issued by the indicated program. Follow the action detailed by the preceding messages.
Reason:
An error occurred in the specified database program. This message is followed by messages DC980412 through DC980414.
Action:
Contact Technical Support.
Reason:
This is an IDMS Error Status value from a database error.
Action:
None.
Reason:
This is an IDMS database record from a database error.
Action:
None.
Reason:
This is an IDMS database set from a database error.
Action:
None.
Reason:
A condition was encountered by RPI and it is terminating itself.
Action:
Enter VRDMU820 and release the bundle marked in error. If the problem persists, contact Technical Support.
Reason:
As part of shutdown processing, RPO Agent is terminating cleanly.
Action:
None.
Reason:
An error occurred while attempting to allocate a JES output data set for the bundle. This message will be preceded by DC970020 and DC970022 messages.
Action:
Save all error information and contact Technical Support.
Reason:
An error occurred while attempting to open a JES output data set for the bundle.
Action:
Save all error information and contact Technical Support.
Reason:
An error occurred while attempting to write the Maildrop Start Separator Page to the bundle data set.
Action:
This message is preceded by additional error messages. Save all error information and contact Technical Support.
Reason:
An error occurred while attempting to write a Recipient Separator Page to the bundle data set.
Action:
This message is preceded by additional error messages. Save all error information and contact Technical Support.
Reason:
An error occurred attempting write report data to the bundle data set.
Action:
This message is preceded by additional error messages. Save all error information and contact Technical Support.
Reason:
An error occurred attempting to perform the indicated function to CADDSPL.
Action:
This message is preceded by additional error messages. Save all error information and contact Technical Support.
Reason:
The indicated report/job cannot be found by CADDSPL.
Action:
Contact Technical Support.
Reason:
An error occurred while attempting to write the Maildrop End Separator Page to the bundle data set.
Action:
This message is preceded by additional error messages. Save all error information and contact Technical Support.
Reason:
An error occurred while attempting to allocate a JES output data set for the bundle. This message is preceded by DC970020 and DC970023 messages.
Action:
Save all error information and contact Technical Support.
Reason:
An RPO Agent foreground program issued a database request, which encountered an error.
Action:
This message is preceded by messages DC980411 through DC980414. See these messages for appropriate action.
Reason:
An embedded DJDE was found in the report but the DJDE User Exit could not be loaded.
Action:
CA Dispatch is installed with a default RDFGEX02. This module or a user-written version must be placed into the CA Dispatch load library. This message is informational only; it does not affect the processing of RPO.
Reason:
An error occurred while writing either a DEFAULT or REPORT DJDE to the specified bundle.
Action:
See the message that precedes the DC980440 and take its specified action.
Reason:
Screen VSGMU170 has not been filled in.
Action:
Go to the default DJDE screen VSGMU170 and fill in the values.
Reason:
AFP resource type ttttttt, with name rrrrrrrr cannot be found in the defined AFP libraries for the bundle.
Action:
The bundle will continue to print. Access the Inline AFP Resource screens from screen VSGMU100. Access screen VSGMU245 and find the Inline AFP Resource Group that is defined for one of the bundle's recipients (screen VRDMU130). Determine the Library Group specified on the Inline AFP Library Resource Definition Screen (VSGMU250). Enter S next to the correct Library Group name and, on screen VSGMU255, enter the AFP Resource Library name that contains the resource being flagged.
Reason:
Default AFP resource type ttttttt, with name rrrrrrrr cannot be found in the defined AFP libraries for the bundle.
Action:
The bundle will continue to print. Access the Inline AFP Resource screens from screen VSGMU100. Access screen VSGMU241 and insert the correct Default Pagedef and Formdef Library names.
Reason:
AFP resource type ttttttt, with name rrrrrrrr cannot be loaded into the bundle.
Action:
The bundle will continue to print. This message is preceded by another error message. Reference that error message to determine the problem.
Reason:
Default AFP resource type ttttttt, with name rrrrrrrr cannot be loaded into the bundle.
Action:
The bundle will continue to print. This message is preceded by another error message. Reference that error message to determine the problem.
Reason:
An error occurred attempting to allocate an AFP Resource library. This message is preceded by a DC970033 message.
Action:
See if you can browse the AFP Resource Library online. If you can, save all error information and contact Technical Support.
Reason:
An error occurred attempting to open an AFP Resource library.
Action:
See if you can browse the AFP Resource Library online. If possible, save all error information and contact Technical Support.
Reason:
An error occurred attempting to read an AFP Resource library.
Action:
See if you can browse the AFP Resource Library online. If possible, save all error information and contact Technical Support.
Reason:
An error occurred attempting to close an AFP Resource Library.
Action:
See if you can browse the AFP Resource Library online. If possible, save all error information and contact Technical Support.
Reason:
An error occurred attempting to deallocate an AFP Resource library. This message is preceded by a DC970033 message.
Action:
See if you can browse the AFP Resource Library online. If possible, save all error information and contact Technical Support.
Reason:
The bundle ID of the bundle in error.
Action:
None.
Reason:
The AFP resource library name in error.
Action:
None.
Reason:
The AFP resource name in error.
Action:
None.
Reason:
An error occurred while attempting to write the AFP resource to the bundle data set.
Action:
This message is preceded by additional error messages. Save all error information and contact Technical Support.
Reason:
An error occurred during the writing of a bundle to JES and the RPO Agent task is checking for and cleaning up any resources still held. For example, file closing and deallocations.
Action:
This message is preceded by additional error messages. Save all error information and check those messages for the appropriate action.
mmmmm can be OPEN, READ, CLOSE or GETRP
Reason:
An error occurred while accessing CADDSPL by Online Viewing.
- RC = 8 indicates an invalid parameter list was sent to the LDS access service.
- RC = 12 indicates an error from ENFSPL.
- RC = 8 indicates an invalid parameter list was sent to the LDS access service.
- RC = 12 indicates an error from ENFSPL.
Action:
This message is preceded by additional error messages from the CA Dispatch LDS I/O Manager. Save all error information and check those messages for the appropriate action.
Reason:
A storage request for program pppppppp failed due to an insufficient amount of available IDMS storage.
Action:
Restart MSG. If the problem persists, shutdown the CA Dispatch address spaces and increase the Storage parameter in the CA Dispatch Usergen parameter list. Run the Usergen JCL procedure, restart CA Dispatch, and restart MSG. If the problem still persists, contact Technical Support.
Reason:
The MSG Subtask has abended with the specified code. Issued by program CADSMB00.
Action:
Determine if the abend code is listed in the Messages Guide. If so, attempt to correct the problem and restart the MSG Subtask. If the problem persists, contact Technical Support.
Reason:
Specifies the report name, job name and JES number of the report being processed at the time of the abend. Precedes message DC980601, which is issued by program CADSMB00.
Action:
None.
Reason:
An error occurred in the specified database program. This message is followed by messages DC980612 through DC980614.
Action:
Contact Technical Support.
Reason:
This is an IDMS Error Status value from a database error.
Action:
None.
Reason:
This is an IDMS database record from a database error.
Action:
None.
Reason:
This is an IDMS database set from a database error.
Action:
None.
Reason:
Indicates that the xx IDMS area is full.
Action:
If the file is maintained by a CA Dispatch database maintenance utility, the utility must be executed to delete expired database records. If the file is not maintained by a utility, one of the database expansion utilities must be executed to enlarge the database area. See the CA Dispatch Systems Programmer Guide for more information.
Reason:
Indicates that a recoverable error occurred for a data set. The data set was placed on hold.
Action:
Check the CAILOG for any previously issued messages for additional information and take appropriate action. If the problem persists, save all error information and contact Technical Support.
Reason:
A condition was encountered by MSG and it is terminating itself; see program CADSMF00.
Action:
Restart MSG. If the problem persists, save all information and contact Technical Support.
Reason:
As part of shutdown processing, MSG is terminating cleanly.
Action:
None.
Reason:
Information needed to execute the MSG task has not been added to the CA Dispatch database.
Action:
Enter online screen VSGMI100, enter the required information, and restart MSG.
Reason:
An MSG foreground program issued a database request, which encountered an error.
Action:
This message is preceded by messages DC980611 through DC980614. See these messages for the appropriate action.
Reason:
MSG Program CADSMF02 encountered an error attempting to retrieve the next available report from CADDSPL. The CA Dispatch DSLOG file contains error messages from the LDS I/O manager that indicate the actual problem.
Action:
Restart MSG. If the problem persists, save all error information and contact Technical Support.
Reason:
RPO program CADSMF04 has successfully recovered from a database deadlock condition. This message will be preceded by an IDMS deadlock message.
Action:
None.
Reason:
A report was marked for Online Viewing but the Online Viewing Pages Table, from which OLV database records are created, is missing. This is an internal logic error.
Action:
Contact Technical Support.
Reason:
A command entered through Report Event Processing in MSG is in error or the scheduling module cannot be found.
Action:
Correct the command entered on screen VRDUM116, or have your system programmer add the module indicated into the CDMSLIB used by CA Dispatch
Be aware of the following:
Type
Identifies the scheduler being processed
Module
Identifies the name of the module you were trying to access, or actually did access
RC
Identifies the problem encountered.
Reason:
The action on the database is invalid; must be C, F or M.
Action:
Correct event actions defined for MSGCLASS.
Reason:
A bad request was made between modules. This is an internal logic error.
Action:
Contact Technical Support.
Reason:
The table address is missing. This is an internal logic error.
Action:
Contact Technical Support.
Reason:
The table pointer is missing. This is an internal logic error.
Action:
Contact Technical Support.
Reason:
There is insufficient storage available for the MSG task.
Action:
Restart MSG.
Reason:
An error occurred while attempting to allocate a JES output data set for MSGCLASS. This message is preceded by DC970020 and DC970022 messages.
Action:
Save all error information and contact Technical Support.
Reason:
An error occurred while attempting to deallocate a JES output data set for MSGCLASS. This message is preceded by DC970020 and DC970022 messages.
Action:
Save all error information and contact Technical Support.
Reason:
An error occurred while attempting to open a JES output data set for MSGCLASS.
Action:
Save all error information and contact Technical Support.
Reason:
An error occurred while attempting to close a JES output data set for MSGCLASS.
Action:
Save all error information and contact Technical Support.
Reason:
An error occurred while attempting to write a JES output data set for MSGCLASS.
Action:
Save all error information and contact Technical Support.
Reason:
MSG Program CADSMF06 encountered an error attempting to retrieve a MSGCLASS report from CADDSPL. The CA Dispatch DSLOG file contains error messages from the LDS I/O manager that indicate the actual problem.
Action:
Restart MSG. If the problem persists, save all error information and contact Technical Support.
Reason:
The name of MSGCLASS Report, Job or Jes#, or both is in error.
Action:
None.
|
Copyright © 2011 CA.
All rights reserved.
|
|