Reason:
You encountered an internal error. The message indicates the function attempted (ffff) and a return code (rrrrrr). The execution of the Batch Transaction Generator utility (DDBTGLM) terminates and, if the trace facility is enabled, a core dump is produced. The message can appear on both SYSPRINT and the console.
Action:
Consult DSF Return Codes for an explanation of the return code (rrrrrr).
Reason:
You encountered an internal error. The message indicates the function attempted (ffff), the operand (* .oooooooo), the request type (t), a return code (rr) and a brief explanation of the error encountered (xxxxxxxxxx). The execution of the Batch Transaction Generator utility (DDBTGLM) terminates and, if the trace facility is enabled, a core dump is produced. The message can appear on both SYSPRINT and the console.
Action:
If the appropriate action is not clear from the brief explanation included in the message, contact CA Support. For information about contacting CA Support, see Troubleshooting.
Reason:
CA Datacom Datadictionary has encountered an invalid return code from VPE when attempting to open the DDCFBLD work file for output. A typical example is a missing DD or DLBL statement from the DDCFBLD utility JCL.
Action:
Correct the JCL and rerun.
Reason:
The attribute-value specified on the transaction for the attribute specified below this message is invalid because it does not match one of the legal values for this attribute. The set of legal values is determined by the TYPE=V (VALUE) fields for the attribute involved.
Action:
Correct the attribute-value in the transaction and resubmit the transactions. If the value appears to be correct, contact CA Support. For information about contacting CA Support, see Troubleshooting.
Reason:
The attribute identified following this message on the report is not an updatable attribute through the DDUPDATE utility, or the -USR transaction does not identify a Security Administrator.
Action:
Correct the update request or the -USR transaction and resubmit the job.
Warning: If this error message is received when processing a 4099 transaction on a field that is part of a table in the DATA-DICT database, DO NOT ignore the error. Have a user who is a Security Administrator for CA Datacom Datadictionary reprocess the transactions into DDUPDATE. DO NOT simply ignore the 4099 transaction to get around the error.
Removing the 4099 transaction results in CA Datacom Datadictionary taking the default values for the attribute-values that are on the transaction. These default values are very often inappropriate for fields within the DATA-DICT database. A wide variety of unpredictable and serious errors in CA Datacom Datadictionary processing can result. Other products that use the contents of the CA Datacom Datadictionary such as CA Ideal and CA Dataquery may also be affected.
Reason:
The CA Datacom Datadictionary batch utility has encountered an unexpected DSF return code on the SYSINITI command issued internally to open the DSF session.
Action:
Look for an accompanying numbered CA Datacom Datadictionary error message immediately preceding this error or a CA Datacom/DB error message in the job log. If such a message is available, use it to help resolve the error. If not, ensure that the Multi-User Facility is up and available, that the CA Datacom Datadictionary batch URT named in the DDSYSTBL macro is available, and that CAIVPE code is available. If you cannot resolve the error, contact CA Support. For information about contacting CA Support, see Troubleshooting.
Reason:
The CA Datacom Datadictionary batch utility has encountered an unexpected DSF return code on the attempt to open SYSIN.
Action:
Look for an accompanying numbered CA Datacom Datadictionary error message immediately preceding this error. If such a message is available, use it to help resolve the error. If not, ensure that the ROSFD macro for SYSIN has been included in the DDVPEFT assembly and that the DDVPEFT load module is available. If you cannot resolve the error, contact CA Support. For information about contacting CA Support, see Troubleshooting.
Reason:
The CA Datacom Datadictionary batch utility has encountered an unexpected DSF return code on the attempt to open SYSPUNCH.
Action:
Look for an accompanying numbered CA Datacom Datadictionary error message immediately preceding this error. If such a message is available, use it to help resolve the error. If not, ensure that the ROSFD macro for SYSPUNCH has been included in the DDVPEFT assembly and that the DDVPEFT load module is available. If you cannot resolve the error, contact CA Support. For information about contacting CA Support, see Troubleshooting.
Reason:
You have encountered an internal error.
Action:
Look for an accompanying numbered CA Datacom Datadictionary error message immediately preceding this error. If such a message is available, use it to help resolve the error. If not, contact CA Support. For information about contacting CA Support, see Troubleshooting.
Reason:
You have encountered an internal error.
Action:
Look for an accompanying numbered CA Datacom Datadictionary error message immediately preceding this error. If such a message is available, use it to help resolve the error. If not, contact CA Support. For information about contacting CA Support, see Troubleshooting.
Reason:
You have encountered an internal error.
Action:
Look for an accompanying numbered CA Datacom Datadictionary error message immediately preceding this error. If such a message is available, use it to help resolve the error. If not, contact CA Support. For information about contacting CA Support, see Troubleshooting.
Reason:
The CA Datacom Datadictionary batch utility has encountered an unexpected DSF return code on the USRINITI command attempting to process the -USR transaction.
Action:
Look for an accompanying numbered CA Datacom Datadictionary error message immediately preceding this error. If such a message is available, use it to help resolve the error. If not, ensure the following:
If you cannot resolve the error, contact CA Support. For information about contacting CA Support, see Troubleshooting.
Reason:
The CA Datacom Datadictionary batch utility has encountered an unexpected DSF return code attempting to read SYSIN.
Action:
Look for an accompanying numbered CA Datacom Datadictionary error message immediately preceding this error. If such a message is available, use it to help resolve the error. If not, ensure that the ROSFD macro for SYSIN specifies the record size, block size, and other parameters that are actually being used in the DDVPEFT assembly. If you cannot resolve the error, contact CA Support. For information about contacting CA Support, see Troubleshooting.
Reason:
You have encountered an internal error.
Action:
Look for an accompanying numbered CA Datacom Datadictionary error message immediately preceding this error. If such a message is available, use it to help resolve the error. If not, ensure that the DATA-DICT HSD table is available. Running the -HSD RESET function of the DDCFBLD utility may eliminate the problem. If you cannot resolve the problem, contact CA Support. For information about contacting CA Support, see Troubleshooting.
Reason:
The CA Datacom Datadictionary profile for this user or your external security product does not include authorization to run the batch CA Datacom Datadictionary utility.
Action:
Check with your Security Administrator to determine if you can be authorized to run the batch CA Datacom Datadictionary utility.
Reason:
After submitting the DDBDULM or DDDDULM utility, either of the following was detected:
The following appear in the message text:
|
CMD=ccccc |
The CA Datacom/DB command, such as LOCKY. |
|
DBFILNAME=ttt |
The DATACOM-NAME attribute-value for the table in the User Requirements Table. |
|
DBELM1=eeee1 |
The DATACOM-NAME attribute-values for the elements involved. |
|
DBKEYNAM=kkkkk |
The DATACOM-NAME attribute-value for the key involved. |
|
rrr |
The CA Datacom/DB external return code. |
Action:
Correct the control statement and resubmit the job.
Reason:
After submitting the DDBDULM or DDDDULM utility, either of the following was detected:
Action:
Make the following corrections and resubmit the job.
Reason:
The value for the DBASEID= keyword is shorter than five characters or contains non-numeric data.
Action:
Correct the control statement and resubmit the job.
Reason:
The keyword is not in the correct position in the DDBDULM or DDDDULM control statement.
Action:
Correct the control statement and resubmit the job.
Reason:
The keyword is not in the correct position in the DDBDULM or DDDDULM control statement.
Action:
Correct the control statement and resubmit the job.
Reason:
The keyword is not in the correct position in the DDBDULM or DDDDULM control statement.
Action:
Correct the control statement and resubmit the job.
Reason:
The value for the DBASEID= keyword is not in the correct position in the DDBDULM or DDDDULM control statement.
Action:
Correct the control statement and resubmit the job.
Reason:
The INDEX or DUMP keyword is not in the correct position in the DDBDULM or DDDDULM control statement.
Action:
Correct the control statement and resubmit the job.
Reason:
The value for the FILETBL= keyword is not in the correct position in the DDBDULM or DDDDULM control statement.
Action:
Correct the control statement and resubmit the job.
Reason:
An error has been encountered in one of the Batch Transaction Generator utility (DDBTGLM) control statements. This message is printed immediately following the invalid statement. The Batch Transaction Generator ignores the invalid statement and continues processing. The message can appear on both SYSPRINT and the console.
Action:
Correct the invalid statement.
Reason:
The -USR transaction is invalid. This can be caused by incorrect syntax or by entering more than one -USR transaction.
Action:
Correct the error and resubmit.
|
Copyright © 2014 CA.
All rights reserved.
|
|