This chapter lists messages preceded by the characters DCD.
This section contains the following topics:
The DCD messages follow.
Reason:
You supplied an invalid date in the first date field of the statement nnnnnnnnnnnnnnnn.
Action:
Make sure that the date format is correct and be sure you used the correct delimiters.
Reason:
You supplied an invalid time in the first time field of the statement nnnnnnnn.
Action:
Make sure the time format is correct and be sure you used the correct delimiters.
Reason:
You supplied an invalid date in the second date field of the statement nnnnnnnn.
Action:
Make sure the date format is correct and be sure you used the correct delimiters.
Reason:
You supplied an invalid time in the second time field of the statement nnnnnnnn.
Action:
Make sure the time format is correct and be sure you used the correct delimiters.
Reason:
The date, time, or both that you supplied in the first date and time fields of the statement are later than the second date and time supplied.
Action:
Make sure that the first date and time precedes the second date and time chronologically.
Reason:
You did not supply certain fields with the statement nnnnnnnn
Action:
Supply the missing fields.
Reason:
You input the PLAN or LATE statement specifying CA 7 Job Management, or CA Scheduler Job Management input and a job name on the schedule was not found on the CA Dispatch database. The interface between the schedule and CA Dispatch is the job name.
Action:
The job names for reports to be planned with schedule input must be defined to CA Dispatch.
Reason:
The statement nnnnnnnn named in the message is too long. Statements cannot be more than eight characters long.
Action:
Check your input to see if you input the correct statement. Also check to see whether you included the proper delimiters.
Reason:
The operand nnnnnnnn named in the message is too long; operands cannot be more than eight characters long.
Action:
Check your input to see if you input the correct operand. Also check to see whether you included the proper delimiters.
Reason:
The statement you input is not a recognized valid statement in CA Dispatch.
Action:
Check your input to see if you entered the statement correctly.
Reason:
You input a field containing more than 63 characters; this exceeds the maximum field length permitted in CA Dispatch.
Action:
Check your input to see if you included the proper delimiters to indicate the end of field.
Reason:
You supplied a statement that requires a complete From and To date range; you did not include one of the required date parameters.
Action:
Check your input to see if you supplied both dates for the range and if you included the proper delimiters to indicate the end of one field and the beginning of the next.
Reason:
You input a statement with more than eight operands; this exceeds the maximum number permitted in CA Dispatch.
Action:
Check your input to see if you included the correct delimiters to indicate the end of the operands, or the statement.
Reason:
You input a statement with more than eight fields; this exceeds the maximum number of fields permitted in CA Dispatch.
Action:
Check your input to see if you included the correct delimiters to indicate the end of the fields.
Reason:
You input a statement that requires a From and To date range, but CA Dispatch read the transaction as having more than two date parameters.
Action:
Check your input to see if you supplied only two dates for the range and if you included the proper delimiters to indicate the end of the date fields.
Reason:
You included operands in a statement that cannot be used in the same execution of the statement. For example, this message displays if you specify both a From and a To date range and a specific Day.
Action:
Check your input to see if you included mutually exclusive statements, and also check your delimiters.
Reason:
You input a statement with multiple date operands when only one date operand was required.
Action:
Check your input to see if you included mutually exclusive statements and also check your delimiters.
Reason:
You input a field in this transaction that cannot be used in the specified operand.
Action:
Check your input to see if the fields you included are allowable in the specified operand. Also check your delimiters; an omitted delimiter can cause CA Dispatch to read an operand or a statement as a field in an operand.
Reason:
You input an operand field in this transaction that cannot be used in the specified statement.
Action:
Check your input to see if the operands you included are allowable in the specified statement. Also check your delimiters; an omitted delimiter can cause CA Dispatch to read a statement as an operand in the previous statement.
Reason:
You input a statement and CA Dispatch read the transaction as having more than one of the same operand. For example, CA Dispatch may have read two DAY operands as part of the same statement.
Action:
Check your input to see if you supplied only one operand. Also check your delimiters; an omitted delimiter can cause CA Dispatch to read an operand from a later statement as part of the previous statement.
Reason:
You input a statement to CA Dispatch without an ending period.
Action:
Insert the period "." at the end of a CA Dispatch transaction.
Reason:
You input a statement that creates a report that lists base reports and recipients. CA Dispatch found a report on its database for which there are no recipients defined. This message is informational only.
Action:
You may want to define recipients for this report.
Reason:
CA Dispatch found an error condition on its database and terminated this run.
Action:
None.
Reason:
This message is informational only.
Action:
None.
Reason:
This message is informational only.
Action:
None.
Reason:
CA Dispatch found a right parenthesis indicating the end of a date range, but did not find the left parenthesis to indicate the beginning of the range.
Action:
Check your input to see if you entered the transaction correctly.
Reason:
CA Dispatch has found a left parenthesis indicating the beginning of a date range, but did not find the right parenthesis to indicate the end of the range.
Action:
Check your input to see if you entered the transaction correctly.
Reason:
You input the first part of a date range in a transaction but CA Dispatch cannot find the second part of the range.
Action:
Check your input to see if you included the second part of the range. Also check your input to see if you entered the correct delimiters.
Reason:
You input the second part of a date range in a transaction but CA Dispatch cannot find the first part of the range.
Action:
Check your input to see if you included the second part of the range. Also check your input to see if you entered the correct delimiters.
Reason:
You used a quote in a statement but forgot to include the closing quote.
Action:
Correct your input and resubmit the transaction.
Reason:
An CA IDMS® database error occurred.
Symptom: Error messages are displayed by a batch report.
Action:
The following Error Status codes may occur when running a batch maintenance job:
ERROR STATUS 0229
0269
0329
0369
0829
0869
These errors can occur when running the batch jobs while CA Dispatch is up and running. This status code is a "file open" error, and is caused when the batch job tries to update or delete a record while another task is viewing or adding a record. In most cases you can rerun the job and the error does not occur again. To prevent a further occurrence of this error, run the local version of the batch maintenance procedure, which runs with CA Dispatch down. Local versions are DSEXLODL, DSEXTMIG, DSEXVIEW, DSEXPURG.
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. If any other error status codes are encountered, contact Technical Support.
Reason:
This message indicates the completion of a requested process in the OVBTUTI1 program.
Action:
None.
Reason:
An error occurred while running the batch utility program. Other error messages accompany this message.
Action:
Correct your input and resubmit the transaction.
Reason:
The OLV file Report or Job name did not have a matching OV‑BASE record. All invalid records are backed up and only valid records are restored. The report still shows in Online Viewing after the restore, but is not viewable. The batch VIEW process (DSEXVIEW or DSEXPSVW) removes the report from Online Viewing. JES number, file name and record number refer to the OV‑BASE record, which is the report that is deleted.
Action:
No action is required; however, continued database error messages may require corrective action.
Reason:
This is an informational message from program OVBTUTI1; it provides database record counts for the backup process. The record counts are displayed in the NNNNNNNN variables.
Action:
None.
Reason:
This is an informational message from program CADSVIEW that provides database record counts for each of two program passes.
Action:
None.
Reason:
ADJ for the PLAN or LATE report was provided more than once.
Action:
Correct input and rerun PLAN or LATE.
Reason:
The minutes in the ADJ operand for PLAN or LATE are greater than 59.
Action:
Correct input and rerun PLAN or LATE.
Reason:
SCHD parm was used, but the file (SCHDPLAN) included a history record used for SCHDLATE.
Action:
Rerun the report using the proper scheduling input file.
Reason:
SCHD parm was specified, but the input file (SCHDLATE) had a scheduled record as used for PLAN (SCHDPLAN).
Action:
Rerun the report using the proper scheduling input file.
Reason:
TMSTVEXT, the CA 1 Tape Management (CA 1) program that releases volumes back to the scratch pool for an externally‑managed tape, could not be loaded.
Action:
Insure the EDM feature of CA 1 is properly installed.
Reason:
This job was not scheduled to run by the scheduling system.
Action:
None.
Reason:
These values are audit trail record counts for database processing. This message is informational only.
Action:
None.
Reason:
Bad return code from OPEN.
Action:
Check the other error messages and correct the problem, then rerun the job.
Reason:
GETMAIN failed.
Action:
Increase the REGION parm on the job statement and rerun the job.
Reason:
This is an informational message from program CADSARUT to notify you that the Archive Batch Utility completed successfully.
Action:
None.
Reason:
An attempt to obtain storage for the Archive Batch Utility common area failed.
Action:
Increase the REGION size for the CADSARUT step.
Reason:
An attempt to LOAD the required load modules for the Archive Batch Utility has failed.
Action:
Make sure that the CADSLOAD being used contains the following members; CADSARCD, CADSARDP, CADSARDF, ARFGTAPM, CADSTPAL, CADSTPIO, CADSTIME, CADSLDIO and CADS9SPL.
Reason:
You supplied an invalid EXEC Parameter.
Action:
Check your input parm to see if you input the correct parameters. Also check to see whether you included the proper delimiters.
Reason:
Program CADSARUT received a non‑zero return code from the CONDENSE process program CADSARCD.
Action:
Check the other error messages and correct the problem, then rerun the job.
|
Copyright © 2011 CA.
All rights reserved.
|
|