Reason:
The combination of SELECTS, EXCLUDES, and DATE SPECIFICATIONS failed to yield any entities for validation.
Action:
Respecify parameters so that something may be selected, and rerun the job.
Reason:
The keyword parameter major command represented by "x" was out of sequence.
Action:
Correct the major command sequence and rerun the job.
Reason:
An EXCLUDE value represented by 'x' is not one of the fixed ENTITY types valid for audit.
Action:
Refer to Chapter 4, Batch Utilities or "Passive Enforcement" for valid ENTITY types, correct the invalid EXCLUDE value and rerun the job.
Reason:
The keyword parameter indicated by 'x', STARTDATE OR ENDDATE, contains an invalid date configuration.
Action:
Refer to Batch Utilities, correct the date specification on the STARTDATE or ENDDATE parameter and rerun the job.
Reason:
The dictionary and node names, "x/y", specified or defaulted for audit cannot be located as a valid network database name.
Action:
Correct the DICTIONARY and NODE parameters and rerun the job. Insure that the SYSCTL is pointing to the correct central version.
Reason:
USER-DEFINED entities selected for audit cannot exceed the number represented by "n".
Action:
If the number of USER-DEFINED entities to be audited exceeds the maximum number indicated in the message, divide them across more than one audit run.
Reason:
A value "x" was encountered as one of the SELECT specifications. The value was neither one of the fixed entity types, nor the name of a USER-DEFINED ENTITY in the dictionary to audit.
Action:
Correct the indicated value and rerun the job.
Reason:
The keyword parameter major command represented by "x" was out of sequence.
Action:
Correct the major command sequence and rerun the job.
Reason:
An EXCLUDE value was specified which does not represent one of the fixed ENTITY types.
Action:
Refer to Chapter 4, Batch Utilities or "Passive Enforcement" for valid ENTITY types, correct the invalid EXCLUDE value and rerun the job.
Reason:
The SELECT criteria for print yielded no printable templates, or the indicated ENTITY owned no templates.
Action:
Correct CA IDMS Enforcer structure or select another ENTITY and rerun the job.
Reason:
The indicated structure and version were not found.
Action:
Correct the DICTIONARY, NODE, and/or SNAPSHOT parameters and rerun the job.
Reason:
The documentation subroutine encountered an unrecoverable error. The integer represented by "n" may be one of the following values:
Action:
Contact CA Technical Support with the indicated error message and integer code. For errors 8 and 12, review the job log for additional system presented diagnostics.
Reason:
USER-DEFINED entities selected for audit cannot exceed the number represented by "n".
Action:
If the number of USER-DEFINED entities to be printed exceeds the maximum number indicated in the message, divide them across more than one print run.
Reason:
A value "x" was encountered as one of the SELECT specifications. The value was neither one of the fixed entity types, nor the name of a USER-DEFINED ENTITY in the CA IDMS Enforcer structure.
Action:
Correct the indicated value, and rerun the job.
Reason:
The indicated DICTIONARY/NODE was successfully downloaded to a logical offload output file.
Action:
None.
Reason:
The indicated DICTIONARY/NODE could not be located in the data structure.
Action:
Correct the DICTIONARY/NODE specification, and rerun the job.
Reason:
A SYSTEM TABLE download has successfully completed (ESXDLOD).
Action:
None.
Reason:
A SYSTEM TABLE download has been requested for a CA IDMS Enforcer structure which owns no SYSTEM TABLES.
Action:
Select a CA IDMS Enforcer structure which contains SYSTEM TABLES and rerun the job.
Reason:
The command is not active for the current screen. The invalid command was either entered on the command line or substituted from a PFKEY.
Action:
Refer to the user guide or use the online HELP facility to determine valid commands.
Reason:
An attempt has been made to add a system table which already exists.
Action:
Select another name for ADD, modify the indicated table, or request a system table list.
Reason:
An attempt has been made to modify or delete a system table which does not exist.
Action:
Select another table name for modify or delete, or request a system table list.
Reason:
The CA IDMS Enforcer communication area stack has been compromised by a system failure, and recovery cannot continue.
Action:
Exit CA IDMS Enforcer, logoff the terminal, or have all terminal resources freed using the DCMT V LT terminal-id RESOURCES DELETE command. If the condition reoccurs consistently, contact CA Inc. Product Support.
Reason:
An ENTITY name has been entered incorrectly.
Action:
Either respecify the ENTITY name correctly, or enter blanks in the ENTITY NAME field to display and select from the ENTITY LIST.
Reason:
A process has been attempted, but field values conflict with allowable procedures.
Action:
Determine the cause of the field conflict. If the screen directives do not reveal the cause, refer to the user guide or the online HELP facility to resolve the field conflict.
Reason:
A DICTIONARY/NODE list has been requested, but no structures exist in the CA IDMS Enforcer database.
Action:
Either use the ADD STRUCTURE utility to create a skeletal structure, or upload a downloaded structure using batch utilities described in the user guide.
Reason:
An equal command (=n.n) has been attempted, but the transfer point does not exist, or is invalid from this function.
Action:
Specify a valid transfer. A table of transfer points is contained in the user guide and in the online documentation.
Reason:
Upon exit from CA IDMS Enforcer, a severe error has occurred during an attempt to return the terminal to UPPER case mode.
Action:
Review the message text supplied in the message. If the error is not correctable, contact CA Technical Support with the full message text.
Reason:
During screen processing, an invalid value was detected in one or more fields.
Action:
If the screen directives do not supply enough information to determine the cause of the error, review the contents of the user guide or the online HELP facility to correct the field contents.
Reason:
The indicated screen requires a user-supplied option value from the list of options, but none was entered.
Action:
Enter one of the indicated options.
Reason:
An attempt has been made to copy a structure or a structural component onto itself.
Action:
Specify a different target or source for the function.
Reason:
The indicated DICTIONARY/NODE structure, x/y, cannot be the target of an ADD or COPY because it already exists.
Action:
If the DICTIONARY/NODE is to be overlaid, specify the REPLACE option as YES.
Reason:
An attempt has been made to modify a system table from a set of RANGES to a set of VALUES, or vice versa.
Action:
Delete and re-add the system table.
Reason:
The user has requested a delete of a system table, and subsequently entered the END command to terminate the deletion.
Action:
None.
Reason:
The current function was successfully completed.
Action:
None.
Reason:
A NODE value was specified on the entry specification screen, but no DICTIONARY/NODE combination with the specified NODE exist.
Action:
Specify a different NODE value, or enter an asterisk (*) in the NODE value for all possible NODES.
Reason:
A DICTIONARY and NODE value were specified on the entry specification screen, but the combination does not exist.
Action:
Specify different DICTIONARY/NODE values or asterisks (*) to display all DICTIONARY/NODES.
Reason:
The program name represented by "x" has passed an invalid parameter configuration to a subroutine.
Action:
Contact CA with the full message text.
Reason:
A system internal failure has occurred during EDITOR interface processing.
Action:
Contact CA with the message text including the return code represented by "nnnn".
Reason:
A system internal failure has occurred during EDITOR interface processing.
Action:
Contact CA Technical Support with the message text and the return code represented by "nnnn".
Reason:
A system internal failure has occurred during EDITOR interface processing.
Action:
Contact CA Technical Support with the message text and return codes represented by "nnnn".
Reason:
A system internal failure has occurred during EDITOR interface processing.
Action:
Contact CA Technical Support with the message text and the return code represented by "nnnn".
Reason:
A system internal failure has occurred during EDITOR interface processing.
Action:
Contact CA Technical Support with the message text and the return code represented by "nnnn".
Reason:
A DICTIONARY value was specified on the entry specification screen, but no DICTIONARY/NODE combination with the specified DICTIONARY exist.
Action:
Specify a different DICTIONARY value, or enter an asterisk (*) in the DICTIONARY value for all possible DICTIONARIES.
Reason:
A system failure occurred, but the CA IDMS Enforcer session was successfully recovered.
Action:
None.
Reason:
The CA IDMS Enforcer communication storage has been compromised.
Action:
Contact CA Product Support with the integer return code and the name of the CA IDMS Enforcer program in which the error has occurred.
Reason:
While several of CA IDMS Enforcer list functions allow multiple line commands per each screen iteration, the current function only allows the specification of a single line command.
Action:
Determine the single line entry to process, remove the other line commands, and retry the transaction.
Reason:
The user has responded with the END command at the structure delete confirmation screen.
Action:
None.
Reason:
A structure copy indicated that the DICTIONARY/NODE was to be replaced, but the structure does not exist.
Action:
Alter the REPLACE option to NO and retry the transaction.
Reason:
The indicated field requires a numeric value, but a value other than 0 through 9 has been encountered.
Action:
Correct the indicated fields.
Reason:
The DICTIONARY/NODE structure represented by "x/y" contains no ENTITIES.
Action:
This is a system internal error. Contact CA Technical Support.
Reason:
An unexpected program condition has been encountered in program "x".
Action:
Contact CA Technical Support with the message text.
Reason:
A line command has been entered on a list screen, but the command is not valid for the current list processing.
Action:
Enter a valid line command. If the screen directive does not provide enough information, access the user guide or the online HELP system for correct line command entries.
Reason:
The dictionary and node, "x/y", contains no SEVERITY CLASSES.
Action:
This is a system internal error. Contact CA Technical Support.
Reason:
One or more (M)odifies of Severity Level assignments were successful.
Action:
None.
Reason:
The indicated fields require a valid date, but the entries are invalid.
Action:
Correct the fields to a valid date in Month/Day/Year format.
Reason:
A system table list was requested, but no system tables exist in this CV.
Action:
Populate the system tables using batch utilities ESXDLOD and ESXULOD, or by using the ADD option of the System Table Maintenance function online.
Reason:
An enforcement table has been successfully generated. The length of the table in bytes is presented in the indicated integer "n".
Action:
None.
Reason:
A system failure occurred during generation, or enforcement implementation. Possible returns are:
|
Code |
Action |
|---|---|
|
0004 |
Generation failed due to missing structure parameters. Contact CA Technical Support. |
|
0008 |
Generation failed due to severe logic error. Contact CA Technical Support. |
|
0104 |
Structure implant failed due to missing structure parameters. Contact CA Technical Support. |
|
0112 |
Storage failure. Increase storage pool. |
|
0116 |
Single-thread lock failure. Cycle central version. If symptom reoccurs, contact CA Technical Support. |
|
terminal-id |
Structure lock failure, return code is 0120. A CA IDMS online utility request to update the dictionary has invoked the Active Enforcement screen presenting full enforcement diagnostics, and 60 seconds have elapsed. The message indicates the owning terminal. Have the owning terminal free their active enforcement session, and retry the generation. If the terminal has already freed the session, a deadlock error has probably left usage count above zero for the structure. For stalled generations, use the ENFRESET function as described in Operations. To prevent future deadlock errors, see Chapter 5, "Operations" for information on different CA IDMS Enforcer Tuning Parameter modes. |
|
0124 |
Area cannot be readied due to another run unit against the CA IDMS Enforcer database. Check area status and retry when area is freed. |
|
0200-1499 |
CA IDMS/DB status error during structure implant. Return is CA IDMS/DB status return. If error is not correctable, contact CA Technical Support. |
Reason:
An illegal copy has been attempted.
Action:
This is a probable internal error. Primary structures may be copied to snapshots of the same structure.
Reason:
This message is identical to return code 120 related to message ENF0040E preceding.
Action:
Refer to message ENF0040E above.
Reason:
The indicated ENTITY does not exist in the current structure.
Action:
Correctly specify the ENTITY name, or enter blanks to allow selection from the ENTITY list.
Reason:
The indicated TEMPLATE does not exist in the current ENTITY.
Action:
Correctly specify the TEMPLATE name, or enter blanks to allow selection from the TEMPLATE list.
Reason:
A template without fields has been encountered, or an invalid field number has been derived by program logic.
Action:
Contact CA Technical Support.
Reason:
An attempt has been made to modify or delete a field in template editing, before establishing field currency.
Action:
Establish currency at the field to modify or delete.
Reason:
Field currency was modified by cursor positioning, but the cursor was not on a exact field boundary. Currency is located to the beginning of the field in which the cursor is located.
Action:
None.
Reason:
Spaces were entered in the Field Identifier.
Action:
Correct the Field Identifier and retry the transaction. For valid entries, consult the user guide or the online HELP system.
Reason:
The length of the field to be added or modified will cause the overall length of the template to exceed the maximum length of the indicated ENTITY.
Action:
Correct the length and retry the transaction.
Reason:
Two or more conflicting values have been entered in the Field Identifier. The conflicting values are represented by "x" and "y". Non-unique field designators are not allowed.
Action:
Correct the Field Identifier and retry the transaction.
Reason:
A compression character (+) was entered as a leading character. Compressible fields must be designated with at least one alphabetic lower case character.
Action:
Correct the contents of the Field Identifier. Refer to the user guide or the online HELP system for valid Field Identifier construction.
Reason:
A field ADD was attempted, but the cursor was not positioned on a field boundary.
Action:
Position to a field boundary using the RIGHT, LEFT, FIRST, or LAST command before attempting the ADD.
Reason:
The RIGHT or LAST command was entered and the currency was at the last field, or the LEFT or FIRST command was entered and the currency was at the first field.
Action:
None.
Reason:
A request for extended field editing was made for a field type which does not support extended editing.
Action:
Either modify the characteristics of the field so that extended editing is possible, or move field currency to another field.
Reason:
The request to delete a system table completed successfully. The table was not associated with any template fields in CA IDMS Enforcer which resulted in no template or field change requirements.
Action:
None.
Reason:
An ADD or COPY of a TEMPLATE has been requested, but the TEMPLATE NAME field is spaces.
Action:
Specify a TEMPLATE NAME as the target of the ADD or COPY.
Reason:
An attempt has been made to add (insert) a new field, or increase the length of an existing field, but the altered length will overflow the maximum template length.
Action:
Create enough trailing wildcards by shortening existing fields or deleting fields. Then, re-add or modify the original field.
Reason:
An attempt to associate a compressible field with a system table type other than a set of non-numeric VALUES has been made.
Action:
You can indicate another system table defined as a set of VALUES, or return to the template edit function and re-specify the field value type or the field identifier to a field other than a compressible field.
Reason:
An attempt has been made to ADD or COPY-TO a template, but the template name or search order already exists.
Action:
Determine whether the name or search order is duplicated, alter the redundant value, and retry the transaction.
Reason:
The requested action on a template field, "x", indicates that field MODIFICATION, DELETION, or ADDITION has been cancelled from the confirmation screen using the END command.
Action:
None.
Reason:
The target of a template copy has been specified as "REPLACE", but the template does not exist.
Action:
Either respecify the transaction without the REPLACE option, or correct the template name to that of an existing template.
Reason:
The indicated DICTIONARY/NODE combination does not exist on the CA IDMS Enforcer database.
Action:
Respecify DICTIONARY/NODE, or add the indicated DICTIONARY/NODE structure.
Reason:
An attempt to access the dictionary and node structure represented by "x/y" failed. Either the task category resource for the current CA IDMS Enforcer function could not be located in the system dictionary or the user ID is not defined in the user catalog.
Action:
Either select another CA IDMS Enforcer function or contact the security administrator at your company with this message. For additional information on security, see Operations.
Reason:
A system failure occurred during active enforcement while attempting to load an enforcement structure into core. For a listing of possible return codes and actions, see ENF0040E in this guide.
Reason:
Active enforcement failed because 60 seconds elapsed without the freeing of the single-thread lock used to insure enforcement table integrity.
Action:
If the condition occurs a second time, a severe system error has left the single-thread lock allocated. Recycle the central version to clear the lock.
Reason:
The entity name associated with this message passed naming compliance but the template against which the name passed was not the first in the search order.
Action:
None.
Reason:
The user has terminated a template delete by entering the END command from the confirmation screen.
Action:
None.
Reason:
A template list has been requested for the indicated entity, but no templates have been defined.
Action:
Add or copy templates to the indicated entity, and retry the transaction.
Reason:
A field add or modification was attempted for a DATA TYPE of numeric, but the field length is greater than 9.
Action:
If the numeric portion of the template must be more than 9 characters in length, divide the field into two separate numeric fields.
Reason:
An attempt has been made to add a field value which already exists in the value set for the current field.
Action:
Alter the indicated field value to a non-existing value, or unspecify the request.
Reason:
An attempt to associate a compressible field with a numeric data type or a field value type other than S-Systable or V-Value has been made.
Action:
Alter the field value type to S-Systable or V-Value, specify A-Alphanumeric or A-Alphabetic data type, or specify a non-compressible field.
Reason:
The length of an entry in the value set or value range field exceeds the defined length of the field.
Action:
Correct the length of the value entry, or alter the length of the field.
Reason:
A value has been provided in the value set or value range list which does not match the data type of the current field, ALPHABETIC, ALPHANUMERIC, or NUMERIC.
Action:
Correct the value entry to match the data type indicated in the messages by "x".
Reason:
A modification or delete of a field value or field value range has been attempted, but the value entry does not exist.
Action:
Correct the transaction type or value entry, and retry the transaction.
Reason:
The following message appears in CA IDMS utility output when enforcement is enabled. The suffix to the ENF0076 portion of the message indicates the severity level of the template against which compliance was established. If the severity level is associated with the prevention of updates, the message will state "UPDATE ABORTED" and will be associated with a CA IDMS utility message prefix of "*+ E", and the entity will not be added to the dictionary. If the severity level is not associated with the prevention of updates, the message will state "UPDATE ALLOWED" and will be associated with a CA IDMS utility message prefix of "*+ W", and the entity will be added to the dictionary.
Action:
None.
Reason:
A field has been defined as an indirect reference, but the ENTITY/TEMPLATE to which the field is indirected contains a field which is indirected. Only one level of indirection is allowed.
Action:
Either remove the indirection from the target ENTITY/TEMPLATE, or specify another ENTITY/TEMPLATE.
Reason:
The length of the indirected field must exactly match the maximum entity length of the ENTITY to which indirection is to be established.
Action:
Alter the length of the current field, or select an ENTITY which is the length of the current field.
Reason:
A template is attempting to be added with a search order which already exists.
Action:
Alter the search order and retry the transaction.
Reason:
At attempt has been made to replace a template, but the search order from the source template is in conflict with the configuration of search orders in the target entity.
Action:
Either alter search orders in the target entity to be non-conflicting, or select another source template for the copy.
Reason:
A field has been defined as D-Data value type, A-Alphanumeric data type, but the field identifier does not contain wildcards (*).
Action:
Alter the field identifier to contain wildcards (*), or change the data type and/or value type of the field.
Reason:
A field is being added or modified to contain the same lower case character as the preceding or following field. Two contiguous fields may not use the same field designator (lower case character).
Action:
Select another lower case character as the field designator.
Reason:
Display mode has been enabled for a CA IDMS batch compiler (System Generation, Schema, Subschema, or Data Dictionary Definition Language compiler), and a naming compliance failure has occurred. This message designates the beginning of the batch diagnostics associated with the compliance failure.
Action:
None.
Reason:
Display mode has been enabled for a CA IDMS batch compiler (System Generation, Schema, Subschema, or Data Dictionary Definition Language compiler), and a naming compliance failure has occurred. This message designates the end of the batch diagnostics associated with the compliance failure.
Action:
None.
Reason:
A single field exists in the current template, and a delete has been attempted against it. Templates must contain at least one field.
Action:
Either modify the single field, or add new fields to rearrange the template.
Reason:
A request to BROWSE a template could not be completed due to an internal system error.
Action:
Contact CA Technical Support.
Reason:
Template replacement has been cancelled by the user through the END command from the confirmation screen.
Action:
None.
Reason:
This message is displayed upon first entry to the value list or range set process after a system table or a template field has been initially defined.
Action:
Add a value or range set in the skeletal occurrences provided using line command "A" (ADD) to the left of the FIELD VALUE or the INCLUDE/EXCLUDE? screen fields.
Reason:
Range specifications require that the "to" range is greater than or equal to the "from" range.
Action:
Correct the range values and retry the transaction.
Reason:
A severe logic error has been encountered during active enforcement.
Action:
Contact CA Technical Support.
Reason:
Enforcement has been disabled, and the active enforcement tables removed from core.
Action:
None.
Reason:
The OVERRIDE command was entered from the on-line active enforcement display, but the user is not authorized for name override.
Action:
Refer to Operations to determine further action, if any.
Reason:
The from and to entities in a copy request are of different lengths.
Action:
Correct the source or target entity so that the lengths are identical.
Reason:
Multiple CA IDMS utility sessions (System Generation, Schema, Subschema, Data Dictionary Definition Language Compilers or the Data Dictionary Menu Facility) have compromised enforcement control tables.
Action:
Re-issue signon to the current compiler.
Reason:
An attempt has been made to add an ENTITY which already exists in the target DICTIONARY/NODE.
Action:
Correct ENTITY-TYPE to a new value.
Reason:
An attempt has been made to replace an ENTITY which does not exist.
Action:
Correct ENTITY-TYPE to an existing value, or unspecify the REPLACE option.
Reason:
The user cancelled an ENTITY REPLACEMENT by entering END from the confirmation screen.
Action:
None.
Reason:
An attempt has been made to copy over an ENTITY which currently exists, but the REPLACE option was not specified.
Action:
Select another ENTITY as the target of the COPY operation or specify the REPLACE option.
Reason:
The user cancelled an ENTITY DELETION by entering END from the confirmation screen.
Action:
None.
Reason:
The template length specified for enforcement is greater than the entity length.
Action:
Re-specify Enforcement Template Length to either match the entity length displayed or indicate a value less than the maximum allowable.
Reason:
User defined entity types are added by specifying the CLASS TYPE IS ENTITY parameter of the ADD CLASS NAME IS statement. Class name must be a 1- through 20-character name.
Action:
Specify a 20 character entity type name.
Reason:
The user or group has not been granted execution privileges to access the CA IDMS Enforcer "task-name" to which control was being transferred. This is a CA IDMS security failure.
Action:
Either select another function, or have the security administrator grant execution privileges to this user/group.
Reason:
Dictionary and node replacement has been cancelled by the user through the END command from the confirmation screen.
Action:
None.
Reason:
A template field has been specified which is greater in length than the template length indicated for enforcement.
Action:
Re-specify the template field with a value that is equal to or less than enforcement template length.
Reason:
Bracket mode edits have detected an invalid field value in the field identifier.
Action:
Specify another value in the field identifier and retry the transaction, or bypass bracket mode by specifying N in the template bracket mode screen field.
Reason:
More than one lower-case character has been specified to designate the WORDSET (system table) portion of the bracket mode template.
Action:
Alter the field identifier to contain a single lower-case character, or bypass bracket mode by specifying N in the template bracket mode screen field.
Reason:
A Field Value Type other than S-Systable was found for the WORDSET portion of the bracket mode template.
Action:
Specify "S" in the Field Value Type screen field and press enter, or bypass bracket mode by specifying N in the template bracket mode screen field.
Reason:
A compressible character has been detected in the current template field.
Action:
Specify a field designator other than a compressible type, or bypass bracket mode by specifying N in the template bracket mode screen field.
Reason:
The field identifier contains a literal value which is invalid for the WORDSET portion of a bracket mode template.
Action:
Specify a single lower-case character in field 02, or bypass bracket mode by specifying N in the template bracket mode screen field.
Reason:
A field identifier specified as a wildcard (*) is not associated with the required field value type D for data only, and/or the required field data type A which indicates alphanumeric.
Action:
Correct the contents of field value type, and/or field data type.
Reason:
More than three fields exist and the field beyond field number 03 contains a field designator other than wildcards (*).
Action:
Delete all fields beyond field number 03. Deleted fields are automatically converted to wildcards. Otherwise, change the bracket mode to N and continue.
Reason:
The WORDSET portion (PREFIX.WORDSET.SUFFIX) of the bracketed template requires assignment of a system table.
Action:
Specify Y at the Extended Field Edit prompt to associate a system table with field 02.
Reason:
No CA IDMS Enforcer system tables could be found.
Action:
Alter the Template Bracket Mode screen field to N and exit the Edit Template function. To define a system table, access the System Table Maintenance utility option. When your table is defined, you can continue with previous activities.
Reason:
A system table specified in 'table-name' could not be located in the CA IDMS Enforcer database.
Action:
Alter the Template Bracket Mode screen field to N and exit the Edit Template function. To define the system table, access the System Table Maintenance utility option. When your table is defined, you can continue with previous activities.
Reason:
A database error occurred while attempting to locate a system table.
Action:
Contact CA Technical Support with this error message. To exit the Edit Template function, specify N at the Template Bracket Mode field and enter the END command.
Reason:
A range type system table, which is invalid for a bracketed template, is associated with a field.
Action:
Specify Y in the Extended Edit screen prompt and assign a value type system table to the Field Identifier.
Reason:
A system table, which contains no values, has been associated with a bracketed template field.
Action:
To specify values in the system table, specify N at the Template Bracket Mode prompt, enter the END command, and access the System Table Maintenance function. When the table contains values, continue with previous activity.
Reason:
Three fields (PREFIX.WORDSET.SUFFIX) are required to establish a bracketed template.
Action:
Define three fields following instructions outlined in the online tutorial or in Operations.
Reason:
The template definition passed all bracket mode edits.
Action:
None.
Reason:
Bracket mode is a tutorial driven processor which steps you through template field definitions required to establish a bracketed template. Current activity toward defining a bracketed template has completed successfully.
Action:
Press the Enter key to continue editing and defining the bracket template.
Reason:
Bracket mode is a tutorial driven processor which steps you through template field definitions required to establish a bracketed template. Additional edits are required to complete the template definition.
Action:
Press the Enter key to continue editing and defining the bracket template.
Reason:
A table has been specified at the System Table Reference screen which is defined as a range type table and bracket mode edits are operant.
Action:
Specify another system owned table which is defined as a value type table to satisfy bracket mode requirements.
Reason:
A table has been specified at the System Table Reference screen which contains no values and bracket mode edits are operant.
Action:
Either specify another system table or exit the Edit Template function and specify values using the System Table Maintenance function.
Reason:
The Field Identifier for delete separates two fields containing the same field designator (identical lower-case characters) and field designators are required to be unique.
Action:
Alter one or both fields on either side of the Field Identifier for delete to contain unique lower-case characters.
Reason:
Either a user/group global resource type could not be located in the user catalog or a task category resource type could not be located in the system dictionary.
Action:
Either select another function or contact the security administrator at your company with this message.
Reason:
An error has been detected in the parameter list supplied/returned during a security check.
Action:
Contact CA Technical Support with this message.
Reason:
A return code other than 0 through 12 has been returned from a security check.
Action:
Contact CA Technical Support with this message.
Reason:
Either a user/group global resource type could not be located in the user catalog or an update/browse activity resource for a document or chapter could not be located in the system dictionary.
Action:
Contact the security administrator at your company with this message.
Reason:
The indicated file function could not be performed with the specified file.
Action:
See the "Messages" chapter (Exhibit 5.1) of the user guide to determine the reason the error occurred and the appropriate action to take.
Two types of errors can be reported by the return codes of n1, n2, n3, and n4--non-VSAM file errors and VSAM file errors. The error is described by n2 and n4. For VSAM file errors, n4 is always equal to 28. The error is described by n1, n2, and n3. A general return code is given by n4 for both non-VSAM and VSAM errors. All return codes are decimal values.
|
n4 |
Reason |
Action |
|---|---|---|
|
4 |
End-of-file |
Call Product Support. |
|
8 |
Open error or file is not open |
Look for JCL errors or for the use of improper files. |
|
12 |
An I/O error has occurred |
Find cause for I/O error. |
|
16 |
Request not recognized |
Call Product Support. |
|
20 |
File was already opened |
Call Product Support. |
|
24 |
Parameter list error |
Call Product Support. |
|
28 |
VSAM error n1=R15 return code from VSAM n2=low order byte from R0 GENCB/MODCB type of error n3=VSAM feedback byte error in I/O request |
Use n1, n2, and n3 to check for possible user errors. If there are no user errors, call Product Support. |
|
32 |
Insufficient storage |
Increase storage for job step. |
|
36 |
SYNAD error occurred |
Call Product Support. |
|
40 |
BPAM FIND error n1=R15 n2=R0 |
Use n1 and n2 (as described in Data Management Macro Instructions) to check for errors. |
|
44 |
BPAM STOW error n1=R15 n2=0 |
Use n1 and n2 (as described in Data Management Macro Instructions) to check for errors. |
|
n2 |
Reason |
Action |
|---|---|---|
|
0 |
n4=8, use of unopened file n4=24, parameter list error |
Call Product Support. Call Product Support. |
|
1 |
JCL/label overrode parm list |
Remove DCB information from JCL and ensure that the correct files are referenced. |
|
2 |
Parm list overrode JCL/label |
Remove DCB information from JCL and ensure that the correct files are referenced. |
|
3 |
Unrecognized request |
Call Product Support. |
|
4 |
Z/OS x13 ABEND trapped at open |
Fix cause for x13 ABEND. |
|
5 |
Tried to update seq. file |
Call Product Support. |
|
6 |
VSAM write at other than load |
Call Product Support. |
|
7 |
SOS table could not expand |
Call Product Support. |
|
8 |
Z/OS DCB open failed |
Call Product Support. |
|
9 |
SOS table buffer pointer lost |
Call Product Support. |
|
10 |
SOS table file CB not built |
Call Product Support. |
|
11 |
Z/OS DD statement Missing |
Supply missing DD statement. |
|
12 |
VSAM ACB open failed |
Call Product Support. |
|
13 |
Record format invalid |
Call Product Support. |
|
14 |
Macro format invalid |
Call Product Support. |
|
15 |
Record length not numeric |
Call Product Support. |
|
16 |
Record length too large |
Call Product Support. |
|
17 |
Block size not numeric |
Call Product Support. |
|
18 |
Block size too large |
Call Product Support. |
|
19 |
Invalid Z/VSE sysname table |
Assemble a valid sysname table. |
|
20 |
Z/VSE sysname table entry missing |
Assemble a sysname table with an entry for the missing one. |
|
21 |
Z/VSE LU number too large |
Use an LU number within range. |
|
22 |
Z/VSE sysname is not numeric or is misspelled |
Correct to a valid sysname. |
|
23 |
Z/VSE sysname blank |
Do not use blank sysname. |
|
24 |
Z/VSE LU not assigned |
Call Product Support. |
|
25 |
Z/VSE DTF prototype missing |
Call Product Support. |
|
26 |
Z/VSE logic module missing |
Generate missing logic module. |
|
27 |
Z/VSE CCW mismatch |
Call Product Support. |
|
28 |
File is not a PDS |
Allocate file to a PDS. |
Exhibit 5.1: Return Codes
Reason:
An unexpected CA IDMS/DB status error occurred during CA IDMS Enforcer processing in program "a." The invalid CA IDMS/DB status is presented in "b," and the CA IDMS/DB call sequence is presented in "c."
Action:
Refer to the error status values in the CA IDMS/DB error messages manual. If the reason for the error is not apparent, contact CA, Product Support.
Reason:
An upload structure file has been successfully installed into the indicated DICTIONARY/NODE.
Action:
To implement the structure, use the online generation utility.
Reason:
An upload was attempted against the indicated DICTIONARY/NODE, but it already exists in the CA IDMS Enforcer database.
Action:
Either specify another DICTIONARY/NODE as the target of upload, or specify the REPLACE parameter.
Reason:
The structure file is empty.
Action:
Check the DD statement of LODFILE for accuracy. Re-execute the download (ESXDLOD) to create a valid load file.
Reason:
A system internal error has occurred because of an invalid record in the load file.
Action:
Review the output file from the download run (ESXDLOD).
Reason:
A SYSTEM TABLE download file has been successfully uploaded into the CA IDMS Enforcer database.
Action:
None.
|
Copyright © 2013 CA.
All rights reserved.
|
|