ELR31 LR SYNTAX ERROR
Reason: Command syntax error encountered.
Action: Review the allowable syntax for the command and reenter.
ELR32 LR SYNTAX ERROR
Reason: Command syntax error encountered.
Action: Review the allowable syntax for the command and reenter.
ELR33 LR SYNTAX ERROR
Reason: Command syntax error encountered.
Action: Review the allowable syntax for the command and reenter.
ELR34 LR SYNTAX ERROR
Reason: Command syntax error encountered.
Action: Review the allowable syntax for the command and reenter
ELR35 LR SYNTAX ERROR
Reason: Command syntax error encountered.
Action: Review the allowable syntax for the command and reenter.
ELR36 LR SYNTAX ERROR
Reason: Command syntax error encountered.
Action: Review the allowable syntax for the command
ELR37 VARIABLE SYMBOL/TOKEN MISMATCH
Reason: The entered command requires variable substitution, but the command line contains insufficient tokens.
Action: Review the syntax and correct the command entry.
ELR51 INVALID ENCODED VALUE
Reason: An apparent internal error has occurred.
Action: If it recurs, contact Technical Support.
ELR52 INVALID TOKEN
Reason: An invalid token has been encountered during command parsing.
Action: Review the syntax and correct the command entry.
ELR53 SUBSCRIPTING NOT IMPLEMENTED
Reason: CA IDMS DMLO does not yet support entry of subscripted fields in this context.
Action: Reenter command without subscripted fields.
ELR55 UNKNOWN QUALIFIER
Reason: An unknown qualifier was encountered.
Action: Ensure the qualifier is required and is correct.
ELR56 EXCESSIVE QUALIFIERS
Reason: CA IDMS DMLO supports a maximum of four levels of qualification.
Action: Reenter the command with fewer qualifiers.
ELR57 UNKNOWN ELEMENT NAME
Reason: The indicated element is not known to CA IDMS DMLO.
Either the name is incorrect, or the record which contains the element has not yet been referenced.
Action: Correct the element name or ensure that the parent record is loaded (via the INIT command).
ELR58 QUALIFICATION REQUIRED FOR -
Reason: Multiple elements exist with the indicated name.
Action: Reenter the command with a different element or with qualifiers which allow CA IDMS DMLO to determine which particular element is wanted.
ELR59 ELEMENT/QUALIFIER MISMATCH -
Reason: The specified element does not correspond with the entered qualifier.
Action: Correct the element name or the qualifier.
ELR5A AMBIGUOUS QUALIFICATION FOR -
Reason: The qualification as entered is still insufficient to specify the element wanted.
Action: Change the qualification or add another level of qualification.
ELR61 LR UNPAIRED PARENTHESIS
Reason: Left and right parentheses must be paired.
Action: Review the syntax and correct the command entry.
ELR62 LR LITERAL FORMAT ERROR
Reason: A literal of incorrect format has been entered.
Action: Review the syntax and correct the command entry.
ELR63 LR INTERNAL XDE ENCODING ERROR
Reason: An apparent internal error has occurred.
Action: If it recurs, contact Technical Support.
ELR64 LR INTERNAL ERROR - INVALID LIT FLAG
Reason: An apparent internal error has occurred.
Action: If it recurs, contact Technical Support.
ELR65 LR INTERNAL ERROR - DATA TYPE CONVERT
Reason: An apparent internal error has occurred.
Action: If it recurs, contact Technical Support.
ELR66 INVALID DATA IN FIELD -
Reason: Data contained in the specified field does not conform to its usage, resulting in erroneous WHERE construct.
Action: Specify a different field or alter the data content of the field before entering the WHERE command.
ESQ00 FUNCTION NOT IMPLEMENTED
Reason: A scratch/queue function has been requested that is not yet implemented.
Action: Enter another command.
ESQ01 INCOMPLETE COMMAND
Reason: The scratch/queue command is incomplete.
Action: Check the syntax and reenter.
ESQ02 INVALID KEYWORD
Reason: The indicated word is inappropriate or misspelled.
Action: Check the syntax and reenter.
ESQ03 RECORD/FIELD NEEDED AT
Reason: The scratch/queue syntax requires a record or field name where indicated.
Action: Check the syntax and reenter.
ESQ04 NUMERIC FIELD / LITERAL NEEDED AT
Reason: The scratch/queue syntax requires a numeric field or literal where indicated.
Action: Check the syntax and reenter.
ESQ05 INVALID LENGTH
Reason: The specified length is negative or zero.
Action: Correct the contents of the specified length field or specify another field.
ESQ06 FIELD NAME NEEDED AT
Reason: The scratch/queue syntax requires a field name where indicated.
Action: Check the syntax and reenter.
ESQ07 USAGE MUST BE BINARY FULLWORD
Reason: The scratch/queue syntax requires that usage of the indicated field must be 4-byte binary.
Action: Specify a more appropriate field.
ESQ08 IMPROPER OPTION
Reason: The specified option is not appropriate for the scratch/queue command.
Action: Check the syntax and reenter.
ESQ09 AMBIGUOUS KEYWORD
ESQ10 DUPLICATE OR CONFLICTING KEYBOARD
Reason: The scratch/queue command contains a duplicate keyword or conflicting words.
Action: Check the syntax and reenter.
ESQ11 NO ENTRIES TO DISPLAY
Reason: A SHOW entity command was entered, and there are no occurrences of the entity to display.
Action: None.
ESQ12 NO UNUSED DEFAULT BUFFERS
Reason: The scratch/queue processor logic attempted to allocate an unused default buffer name to execute the command, but all 10 of the buffers have been used already.
Action: Specify an explicit buffer name in the command.
ESQ13 UNABLE TO DETERMINE DATA AREA
Reason: The scratch/queue processor is unable to determine a data buffer for a command.
Action: Specify an explicit buffer name in the command.
ESQ14 UNABLE TO DETERMINE SCRATCH/QUEUE AREA ID
Reason: The scratch/queue processor is unable to determine what area ID is wanted for a command. You may have included ?T in a SCRATCH command, but not selected an area from the resultant selection list.
Action: Explicitly specify a SCRATCH/QUEUE ID in the command.
E1001 PRINT ERROR
Reason: One of the following caused this message:
Action: Contact Technical Support.
E2001 KEYWORD NOT RECOGNIZED - keyword/command/operand
Reason: The keyword, command, and/or operand that was entered has not been defined to CA IDMS DMLO.
Action: There are three possible courses of action:
E2002 OPERAND MUST BE NUMERIC LITERAL
Reason: A non-numeric operand was entered with the LINE command.
Action: Enter a numeric value and press the ENTER key.
E2003 INVALID OPERAND
Reason: Either of these reasons caused this message:
Action:
E2004 FIELD NOT UNIQUE - SPECIFY RECORD
Reason: The field-name specified was found in multiple records.
Action: Reenter the command using the record-name operand to specify the record which contains the field you want to access.
E2005 RECORD NAME NOT IN SUBSCHEMA
Reason: The name of the record or field specified could not be found.
Action:
E2006 FIELD NOT IN RECORD
Reason: The field-name specified was not found in the record specified.
Action:
E2010 RECORD NOT BOUND
Reason: BIND has not been issued for the named record, and the AUTOBIND option is not active.
Action:
E2012 FIELD IS WITHIN REPEATING GROUP - DISPLAY RECORD
Reason: The field-name specified is within a repeating group.
Action: To display this field, you must display the entire record and use the windowing commands. Follow these steps:
E2014 TWO OPERANDS REQUIRED
Reason: Only one operand was found on the EQUATE command.
Action: There are two possible courses of action:
E2015 SECOND OPERAND NOT DEFINED
Reason: The second operand has not been defined to CA IDMS DMLO.
Action: Possible courses of action are as follows:
See the CA IDMS DMLO online documentation for command details.
E2016 FIRST OPERAND ALREADY DEFINED
Reason: The <new-symbol> entered on the EQUATE command has already been defined.
Action:
E2017 OPERAND REQUIRED FOR SHOW
Reason: The SHOW command was entered without an operand.
Action:
E2018 UNKNOWN SHOW REQUEST
Reason: The operand specified in the SHOW command has not been defined to CA IDMS DMLO.
Action: There are two possible actions to be taken:
E2019 FORMAT ERROR(S)
Reason: A format error(s) occurred when processing new or modified data was entered. The field entered was in the wrong format (for example, more than one decimal point entered in a numeric field. '1.2.3').
Action:
E2020 INVALID COMMIT REQUEST
Reason: The second operand entered in the COMMIT command is not defined to CA IDMS DMLO.
Action: Correct the second operand and reenter the command.
E2021 INVALID ROLLBACK REQUEST
Reason: The second operand of the ROLLBACK command has not been defined to CA IDMS DMLO.
Action: Correct the second operand and retry the command.
E2022 SECOND COMMAND INVALID
Reason: The first keyword or operand after the IF command is not defined to CA IDMS DMLO.
Action: Validate the keyword or operand and retry.
E2023 USER ID MUST BE ENTERED
Reason: The level of security which your installation has established requires your user ID to be entered before the signon process can be completed.
Action: Supply your assigned user ID. If you have not been assigned a user ID, see your DBA.
E2024 PASSWORD IS REQUIRED
Reason: Security established at your installation requires your password to be entered before the signon process can be completed.
Action: Key in your assigned password. If you have not been assigned a password, see your DBA.
E2025 PLEASE ENTER SUBSCHEMA NAME
Reason: The name of the subschema that you want to access must be supplied before you can signon to CA IDMS DMLO.
Action: Enter the subschema name through which you want to access the database.
E2026 VERSION MUST BE NUMERIC
Reason: The version number of the schema was entered as a non-numeric value.
Action: Reenter the version number using a numeric value.
E2027 LOGICAL DATA WIDTH MUST BE NUMERIC
Reason: The value that was entered for the logical data width was entered as a non-numeric value.
Action: Reenter the field as a numeric value. (This value must be from 80 to 264.)
E2028 USER DOES NOT EXIST, TRY AGAIN
Reason: The user ID entered has not been defined to CA IDMS DMLO.
Action: Validate the user ID. If it is valid, check with your DBA to verify that the user ID has been defined to CA IDMS DMLO.
E2029 SUBSCHEMA/SCHEMA/VERSION COMBINATION NOT FOUND
Reason: There are four possible causes:
Action: Verify the field(s) that were entered. If the fields are valid see your DBA.
E2030 PASSWORD INCORRECT - REENTER
Reason: The password that was entered does not match the password that was registered for the user ID entered.
Action: Validate the password. If it is correct, validate the user ID. If the user ID is correct see your DBA.
E2031 NOT AUTHORIZED FOR SUBSCHEMA ACCESS
Reason: The user ID entered does not have authorization to access the requested subschema.
Action: Validate the user ID. If the user ID is correct see your DBA.
E2032 MORE THAN ONE SCHEMA, PLEASE SPECIFY
Reason: The subschema that was entered has multiple schemas defined.
Action: Enter the schema name for the subschema you want to access.
E2033 INVALID DISPLAY OPTION
Reason: The operand entered on the DISPLAY command has not been defined to CA IDMS DMLO.
Action: There are two possible courses of action:
Correct the operand and reenter the command.
E2034 CONTINUE ONLY VALID FOR THE LAST
Reason: The CONTINUE operand on the DISPLAY command can only be used if a second screen is waiting to be viewed. (See the CA IDMS DMLO online help facility for more details on the DISPLAY CONTINUE command.)
Action: Delete CONTINUE operand and reenter the command.
E2035 NODE OR DICTIONARY COULD NOT BE BOUND
Reason: Bind run-unit failed for node or dictionary specified.
Action:
E2036 DBNAME GIVEN COULD NOT BE BOUND
Reason: The subschema and DBNAME entered at signon could not be bound. (For more information, see the CA IDMS error status code 1469 information.)
Action:
E2037 ONLY DBNAME CAN BE CHANGED
Reason: More than DBNAME was changed for Error Message E2036 screen.
Action: Rekey only the new DBNAME and press the ENTER key, or press the PA1 key (you will get the Interrupt screen), key in FINISH and reinitialize your CA IDMS DMLO session.
E2038 LOGICAL DATA WIDTH IS OUT OF RANGE
Reason: The Logical Data Width entered is either less than 80 or greater than 264. A value outside of this range is not permitted.
Action: Enter a value between 80 and 264 as specified on the Signon screen.
E2039 DDS TARGET NODE INACTIVE OR DISABLED
Reason: The node name specified at signon is unavailable. (For more information, see CA IDMS Error Status Code 1480.)
Action: Choose another node or verify the node name you selected.
E2040 SPECIFIED DATABASE UNKNOWN TO CV
Reason: The DBNAME you supplied at signon was misspelled or inaccurate. (See CA IDMS Error Status Code 1481 for more information.)
Action: Verify the spelling of the DBNAME or check with your DBA on the spelling of names valid for your installation.
E2041 SUBSCHEMA NOT ALLOWED UNDER SPECIFIED DATABASE
Reason: The subschema name and DBNAME entered at signon are mutually exclusive. (See CA IDMS Error Status Code 1482 for more information.)
Action: Choose a different database and/or subschema. Check with your DBA for valid database and subschema combination(s).
E2042 SET ORDER IS NOT SORTED
Reason: A FORMAT 6 FIND/OBTAIN command named a set that is not a sorted set.
Action: Correct and reenter the command.
E2043 RECORD DOES NOT PARTICIPATE IN ANY SORTED SETS
Reason: A FORMAT 6 FIND/OBTAIN command named a record that is not a member of any sorted set.
Action: Correct and reenter the command.
E2044 RECORD IS NOT A MEMBER OF SET
Reason: A FORMAT 6 FIND/OBTAIN command named a record that is not a member of the sorted set named.
Action: Correct and reenter the command.
E2045 PAGE NUMBER IS TOO LARGE
Reason: A FORMAT 6 FIND/OBTAIN command specified a database key with a page number outside the range valid for your subschema.
Action: Correct the page number to be valid for your subschema.
E2046 LINE INDEX NUMBER IS TOO LARGE
Reason: A FORMAT 6 FIND/OBTAIN command specified a database key with a line index number outside the range valid for your subschema.
Action: Correct the line index number to be valid for your subschema.
E2047 BIND OPERAND IS NOT A KEYWORD - CORRECT KEYWORD IS 'ALL'
Reason: Allowable formats are BIND record-name or BIND ALL.
Action: Correct and reenter the command.
E2048 INVALID OPERAND FOR BIND - VALID OPERAND IS 'ALL'
Reason: Allowable formats are BIND record-name or BIND ALL.
Action: Correct and reenter the command.
E2049 SUBSCHEMA MARKED NOT USABLE
Reason: The subschema that was found had the ERR-026 flag set to 1.
Action: The subschema compile was not successful or a GENERATE was not issued. Correct the subschema or issue a GENERATE.
E2050 PA KEY/PF KEY NOT RECOGNIZED
Reason: The value entered on Signon screen for the INTERRUPT key is not one of the supported keys. Valid values are PA1, PA2, PA3, and PF1 through PF24.
Action: Change the value after the interrupt field on the Signon screen to one of the supported keys and reenter.
E2051 KEYWORD MISSING
Reason: At least one required keyword is missing from the entered command.
Action: Reference the command syntax and make the appropriate corrections.
E4501 INVALID READY SYNTAX
Reason: A CA IDMS DML READY command was entered using invalid syntax.
Action: Correct the syntax and reenter the command.
E4502 READY USAGE-MODE SECURITY VIOLATION
Reason: A ready request specified a secured usage mode. That is, the user is not authorized to ready the area in the usage mode requested.
Action: Contact your system administrator.
E4505 AREA: area-name HAS ALREADY BEEN READIED
Reason: A CA IDMS DML READY command was issued for an area that has already been readied. An area cannot be readied more than once. Also, an area's usage-mode cannot be changed during a session. Thus, attempting to re-ready an area in a different mode will not work.
Action: None needed; area-name is already readied. If an area's usage-mode must be changed, the current CA IDMS DMLO session must be terminated and a new one begun.
E4506 RECORD NOT BOUND
Reason: The record-name specified in an INITIALIZE command is not bound.
Action: Bind the record and reissue the command.
E5001 DML OR DML/O COMMAND REQUIRED
Reason: The first word on the command line is not recognized as a CA IDMS DML or CA IDMS DMLO command, either directly or as an EQUATE symbol.
Action: There are two possible courses of action:
E5005 FIRST OPERAND NOT DEFINED
Reason: The first operand is undefined in a command of the form EQUATE <symbol> NULL.
Action: Correct the first operand.
E5006 FIRST OPERAND INVALID
Reason: The first operand in an EQUATE begins with an invalid character.
Action: Correct the first operand.
E5007 UNAVAILABLE VARIABLE
Reason: Substitution was not possible for a variable symbol.
Action: If the symbol was &D, &R, &S, or &A, appropriate currency must be established.
If the symbol was a token variable (&1-&9), additional word(s) must be appended at the end of the command line.
E5008 UNKNOWN VARIABLE
Reason: A variable symbol other than &D, &R, &S, &D, &1 - &9 was found in a command.
Action: Correct the invalid symbol.
E5009 UNAVAILABLE AND UNKNOWN VARIABLES
Reason: Combination of E5007 and E5008.
Action: See above.
E5010 INVALID DBKEY FORMAT
Reason: The command contains an invalid database key literal.
Action: Correct the literal to an acceptable format:
ppppppp-llll X'hhhhhhhh' F'nnnnnnn'.
E5011 SOURCE OPERAND INVALID
Reason: Invalid source operand in MOVE command.
Action: See CLIST Example #2 for acceptable operands.
E5012 KEYWORD ''TO'' MISSING
Reason: Invalid syntax in MOVE command.
Action: See CLIST Example #2 for acceptable format.
E5013 INCORRECT LENGTH FOR SOURCE FIELD
Reason: MOVE source field must be four-byte field with binary or hex USAGE mode.
Action: Correct the command.
E5014 OPTIONS MUST BE Y OR N
Reason: Y/N are only valid selections to specify PROFILE data to be saved.
Action: Correct the selection.
E5015 NO PROFILES FOR YOUR USER ID
Reason: No PROFILEs found for specified user ID for LOAD or ERASE.
Action: Change user ID or bypass PROFILE processing.
E5016 PROFILE NAME MUST NOT BE BLANK
Reason: Blank PROFILE name specified for PROFILE save function.
Action: Enter PROFILE name or bypass PROFILE processing.
E5018 REQUESTED PROFILE NOT FOUND
Reason: Specified PROFILE not found for LOAD or ERASE.
Action: Change PROFILE name or bypass PROFILE processing.
E5019 ERROR RETRIEVING PAGE INFO
Reason: A CA IDMS DMLO internal error occurred. The page info associated with the returned database key could not be retrieved. As a result, the database key could not be converted to decimal format. The database key displayed in hexadecimal format on the keypad display screen is accurate and set currency is updated.
Action: If the problem recurs, contact Technical Support.
E5501 NO CLISTS AVAILABLE
Reason: The user has requested either a CLIST or PROFILE list, but neither user nor global have been previously saved.
Action: Select another function.
E5502 SOURCE USER ID NOT FOUND
Reason: A COPY operation has been requested from another CA IDMS DMLO USER, but the user does not exist.
Action: Correct the user ID to one which exists, and retry the request.
E5503 SOURCE CLIST NOT FOUND
Reason: A COPY/RENAME operation has been requested, but the selected CLIST or PROFILE does not exist for the source user ID.
Action: Select another PROFILE or CLIST for the COPY operation.
E5504 TARGET CLIST EXISTS
Reason: An attempt has been made to overlay an existing CLIST or PROFILE with a COPY or RENAME operation.
Action: Either select another target CLIST or PROFILE name, or issue a REPLACE operation against the indicated CLIST or PROFILE.
E5505 NO CLISTS FOR USER ID
Reason: A maintenance operation has been specified, but no CLIST or PROFILE exists for the user.
Action: Either specify another user ID or select another function.
E5506 REQUESTED CLIST NOT FOUND
Reason: An operation against a specific CLIST or PROFILE member was attempted using a specific name, but the named CLIST or PROFILE does not exist.
Action: Either specify the correct CLIST or PROFILE name, or use the LIST function to specify the name choice.
E5507 OPTIONS MUST BE Y OR N
Reason: The specification of a PROFILE component for SAVE at the end of a session was specified as other than Y-Yes or N-No.
Action: Correct the indicated option and retry the transaction.
E5508 PROFILE NAME MUST NOT BE BLANK
Reason: You requested a PROFILE save at the end of a session, but did not supply a PROFILE name.
Action: Specify a PROFILE NAME and press the ENTER key, or press the indicated key to bypass the save operation.
E5509 CLIST NOT FOUND
Reason: You requested the execution of a CLIST, but the CLIST name you provided does not exist.
Action: Either specify a correct CLIST name, or use the LIST process to select a CLIST for execution.
E5510 ONLY 9 ARGUMENTS ALLOWED
Reason: A CLIST has been executed, but more than nine (9) argument variables were passed as part of the CLIST invocation.
Action: Correct the CLIST invocation stream to contain less than 9 variables.
E5511 CLIST NAME REQUIRED
Reason: An EXEC command was entered without a CLIST name.
Action: Supply a CLIST name and retry the transaction.
E5512 COMMAND NOT ALLOWED AT THIS POINT
Reason: You entered a command which is not allowed at this point in the CA IDMS DMLO session. For example you requested a PROFILE maintenance at other than signon time, or you entered a CLIST-only command when no CLIST is active.
Action: Remove the error command.
E5513 UNAVAILABLE CLIST VARIABLE
Reason: CA IDMS DMLO encountered a CLIST symbolic variable but you did not supply a value at CLIST you requested a PROFILE maintenance at other than signon time, or you entered a CLIST-only command when no CLIST is active.
Action: Alter the CLIST so that the variable is no longer required, or be sure to supply a value (or null indication ',') when required.
E5514 CLIST RECURSION ERROR
Reason: A CLIST has attempted to invoke another level of CLIST, but the lower-level CLIST is currently active at a higher level in the current CLIST nest.
Action: Remove the recursive CLIST call and reexecute.
E5515 USER CLIST NAME REQUIRED
Reason: The user has attempted to initiate an edit session on a CLIST, but did not supply a CLIST name.
Action: Supply a CLIST name or access the list process to select a CLIST.
E5516 INTERNAL EDITOR ERROR
Reason: An internal interface error has occurred when invoking an edit session on a CLIST.
Action: Contact Technical Support with this error and a description of the procedural steps that preceded this error.
E5517 CLIST CURRENTLY IN USE
Reason: You attempted to edit a CLIST, but the CLIST has been locked by another terminal or user.
Action: Specify another CLIST, or retry the request at a later time.
E5518 SYSTEM CLIST MAY NOT BE CREATED
Reason: You attempted to CREATE a CLIST for the SYSTEM level user ID, but you are not signed on as the SYSTEM user.
Action: Either CREATE the CLIST for a user other than the SYSTEM user, or signon as the SYSTEM user and CREATE the CLIST.
E5519 INVALID COMMAND SYNTAX
Reason: You entered invalid command syntax for a CLIST or PROFILE maintenance command.
Action: Correct the syntax.
E5520 SYNTAX REQUIRES x
Reason: CA IDMS DMLO encountered an improper Menu Mode. The parser presents the syntactical phrase which is required.
Action: Correct the syntax.
E5521 ADDITIONAL OPERANDS NEEDED
Reason: CA IDMS DMLO encountered an incomplete Menu Mode command.
Action: Correct the syntax.
E5522 SUPERFLUOUS OPERANDS PRESENT
Reason: CA IDMS DMLO encountered a Menu Mode command with too many operands.
Action: Correct the syntax.
E5523 BIND OPERAND MUST BE RECORD-NAME OR ''ALL''
Reason: You entered a BIND command with a missing or improper operand.
Action: Correct the syntax.
E5524 READY OPTION MUST BE R/U/P
Reason: You entered a value other than R-Retrieval, U-Update, P-Profile, or blank in the initial CA IDMS DMLO Signon screen.
Action: Enter one of the indicated options, or enter a blank on the Signon screen and enter READYLIST during the session to explicitly READY areas.
E5525 LOWER CASE AND OPTIONS 1-8 MUST BE Y/N
Reason: You entered a value other than Y-Yes or N-No in one of the ENVIRONMENT options.
Action: Correct the indicated value to Y or N and retry the transaction.
E5526 LOGICAL DATA WIDTH MUST BE NUMERIC AND 80-255
Reason: You entered an invalid data width (screen width).
Action: Correct the data width and retry.
E5527 INTERRUPT VALUE NOT RECOGNIZED
Reason: You specified a value for the interrupt key which does not correspond to a PF key or PA key value.
Action: Correct the interrupt value and retry.
E5528 INCOMPLETE COMMAND
Reason: You entered an incomplete operand in a MOVE or CLIST IF statement.
Action: Correct the operand. Review online help or the CA IDMS DML Online User Guide for syntax information.
E5529 INVALID LITERAL
Reason: CA IDMS DMLO encountered an invalid literal in a MOVE or CLIST IF statement.
Action: Correct the syntax. Review online help or the CA IDMS DML Online User Guide for syntax information.
E5530 "OF RECORD" NEEDED FOR DUP FIELD NAME
Reason: A MOVE or CLIST IF statement contains an element-name which appears in more than one record in the current subschema.
Action: Specify OF RECORD-NAME to qualify the ELEMENT and retry the statement.
E5531 FIELD/RECORD NOT FOUND
Reason: An ELEMENT or RECORD in a MOVE or CLIST IF statement does not exist in the current dictionary/node.
Action: Correct the ELEMENT or RECORD name, and retry the statement.
E5532 RELATIONAL NOT FOUND
Reason: You specified an invalid relational operator in a CLIST IF statement.
Action: Correct the syntax.
E5533 PREMATURE END OF IF GROUP
Reason: CA IDMS DMLO reached the end of a CLIST, but an ENDIF was not encountered for an active CLIST IF statement.
Action: Correct the IF statement and retry the CLIST.
E5534 MISSING KEYWORD 'TO'
Reason: A MOVE statement does not contain the TO keyword.
Action: Correct the MOVE statement and retry the transaction.
E5535 INVALID SOURCE FIELD DATA
Reason: CA IDMS DMLO encountered an inconsistent SOURCE operand in a MOVE statement.
Action: Correct the MOVE statement and retry the transaction.
E5546 INVALID KEYWORD
Reason: The IFC or MOVE command contains an invalid keyword.
Action: Review the syntax for the command of interest, and reenter.
E5547 NEED RECORD NAME, FOUND
Reason: The syntax requires a record-name where the indicated token was found.
Action: Reenter the command with a record-name.
E5548 SUBSCRIPTING NOT IMPLEMENTED
Reason: Reference to a subscripted field has appeared in the IFC/MOVE command. This is currently unsupported by CA IDMS DMLO.
Action: Remove the offending reference.
E5550 MEMBER RECORD NOT IN SUBSCHEMA
Reason: The specified record is not included in the current subschema.
Action: Specify a different record-name, or start a new CA IDMS DMLO session with a different subschema.
E6001 REC NOT IN SUBSCHEMA,VERSION NOT IDD-OWNED
Reason: Record-name not member of current subschema, or the specified record/version is not in the dictionary.
Action: Change record-name or version number.
E6002 NO ELEMENTS EXIST FOR RECORD
Reason: Record has no associated elements.
Action: Enter new record-name, or do a dictionary update for the named record.
E6003 INTERNAL HASH ERROR
Reason: An internal error occurred in the CA IDMS DMLO hash lookup routine.
Action: If the problem recurs, contact Technical Support.
E6008 RECORD NOT IN SPECIFIED AREA
Reason: A FIND/OBTAIN specifying both record and area was entered for which the record does not reside in the specified area.
Action: Change the record or area as required, or use &A to ensure the area matches the record.
E6009 AMBIGUOUS KEYWORD
Reason: The syntax of the current command allows words which are not distinguishable based on the number of letters entered for the specified word.
Action: Reenter the command using more leading letters for the specified keyword. You should refer to the command syntax to determine the minimum spelling.
E6012 VERSION MISMATCH WITHOUT REPLACE OPTION
Reason: The INIT command has been specified for a dictionary-owned record/version that has already been loaded from the dictionary. The specified version does not match the prior version.
Action: To load a new version of the same record, you must specify the REPL option on the INIT command.
E6013 VERSION REQUIRED FOR REPLACE OPTION
Reason: The REPL option of the INIT command has been specified without the VERSION option.
Action: Add a VERSION specification to the command.
E6016 UNAUTHORIZED REQUEST
Reason: The specified maintenance command is restricted for use by your CA IDMS DMLO system administrator.
Action: Contact your CA IDMS DMLO system administrator.
E6017 NO ROWS TO PRINT
Reason: A PRINT request was specified, but there are no display rows formatted.
Action: Issue a DISPLAY command, then a PRINT command.
E6019 MEMBER RECORD NOT BOUND
Reason: An attempt was made to construct a search key for an OBTAIN/RETURN with USING option, and the record that is the member of the sorted set has not been bound and AUTOBIND is not active.
Action: Set AUTOBIND ON or INIT record-name and reissue the OBTAIN/RETURN command.
E6020 INVALID TARGET DATA TYPE
Reason: You entered a command that specified a literal as the target item of a MOVE statement.
Action: Change the target data item to a record or field name and reissue the command.
F0000 NORMAL TERMINATION
Reason: CA IDMS DMLO terminated normally.
Action: Press the ENTER key to complete the exit from CA IDMS DMLO.
F0003 TERMINATED BY FINISH OR ROLLBACK DURING STARTUP
Reason: The PA1 key was pressed during the signon process and either a FINISH or ROLLBACK command was entered on the returned screen. An error status of 0069 is also returned with this message. This is because the run-unit was never bound.
Action: Press the ENTER key to complete the exit from CA IDMS DMLO.
F0069 SUBSCHEMA CONTROL TABLE NOT FOUND
Reason: The address of the subschema control table cannot be found. This is because the address was never established or it was once established, but now it is lost.
Action: Reinvoke CA IDMS DMLO, and try again. If the problem recurs, contact Technical Support.
F0077 RUN-UNIT COULD NOT BE FOUND
Reason: The subschema entered on the signon screen was located, but it could not be loaded. This message is for CA IDMS/DC environments only.
Action: The subschema you are accessing must be on either the core image library if you are running under z/VSE, or if you are running under z/OS, or z/VM, it must be in the load library.
F0100 TERMINAL READ/WRITE ERROR
Reason: The terminal read or write routine has issued a return code greater than zero to CA IDMS DMLO. A possible line or terminal error has occurred.
Action: Reinvoke CA IDMS DMLO, and try again. If the problem recurs, contact Technical Support.
F0102 INTERNAL SCAN ERROR ON INPUT DATA
Reason: The 3270 scan routine cannot locate the end-of-record marker for the data string that was entered.
Action: Reinvoke CA IDMS DMLO, and try again. If the problem recurs, contact Technical Support.
F0103 TEMPORARY STORAGE ACQUIRE ERROR
Reason: One of the following caused this message:
Action: Reinvoke CA IDMS DMLO, and try again. If the problem recurs, contact Technical Support.
F0105 NO RECORDS TO BIND
Reason: CA IDMS DMLO could not find any records in the subschema that was being accessed.
Action: Verify the subschema. If records do exist, contact Technical Support.
F0106 BIND RUN UNIT FAILED FOR CA IDMS DMLO
Reason: The bind run unit failed for the subschema you requested.
Action:
F0107 DUPLICATE KEYWORD FOUND
Reason: CA IDMS DMLO located a duplicate keyword in the keyword table.
Action: Contact Technical Support.
F0108 DUPLICATE HASH ENTRY
Reason: CA IDMS DMLO located a duplicate area or record name in the internal table.
Action: Contact Technical Support.
F0109 NO AREAS TO READY
Reason: CA IDMS DMLO could not find any area in the subschema being accessed.
Action: Verify the subschema. If areas do exist, contact Technical Support.
F0118 RECORD HAS NO FIELDS
Reason: A request was entered to process a record that did not have any elements defined.
Action: Verify the record description in the subschema. If elements do exist, contact Technical Support.
F1002 PUSH STACK OVERFLOW
Reason: CA IDMS DMLO received a non-zero return code from the storage routine.
Action: Allocate more storage to CA IDMS DMLO. If the problem recurs, contact Technical Support.
F1003 ENTER STACK OVERFLOW
Reason: CA IDMS DMLO received a non-zero return code from the storage routine.
Action: Allocate more storage to CA IDMS DMLO. If the problem recurs, contact Technical Support.
F1718 INVALID USAGE FOR DEPENDS ON FIELD
Reason: A record with an occurs depending on group has an object field whose usage mode is not numeric.
Action: Verify the record. If the field is defined as numeric, contact Technical Support.
F1719 INVALID USAGE FOR SUBSCRIPTED FIELD
Reason: The usage mode for a subscripted field must be filler, hexadecimal, or picture X.
Action: Contact Technical Support.
F1938 PACKED FIELD GREATER THAN 16 BYTES
Reason: CA IDMS DMLO encountered a field with a usage mode of packed decimal and a length greater than 16 bytes.
Action: Contact Technical Support.
F2001 BIND RUN UNIT FAILED FOR DIRECTORY
Reason: The bind run unit failed for subschema 'IDMSNWKA'.
Action:
F2002 BIND RECORD FAILED
Reason: A request to bind a record in the subschema 'IDMSNWKA' failed.
Action:
F2003 READY AREA FAILED
Reason: A request to ready area 'DDLDML' failed.
Action:
F2004 OBTAIN FOR SSA-024 FAILED
Reason: A non-zero status was returned while CA IDMS accessed the dictionary record 'SSA-024' that relates to your subschema.
Action:
F2005 OBTAIN FOR SS-026 FAILED
Reason: A non-zero status was returned while CA IDMS was accessing the dictionary record 'SS-026' that relates to your subschema.
Action:
F2006 OBTAIN FOR SSR-032 FAILED
Reason: A non-zero status was returned while CA IDMS was accessing the dictionary record 'SSR-032' that relates to your subschema.
Action:
F2007 OBTAIN FOR SSOR-034 FAILED
Reason: A non-zero status was returned while CA IDMS was accessing the dictionary record 'SSOR-034' that relates to your subschema.
Action:
F2008 OBTAIN FOR SR-036 FAILED
Reason: A non-zero status was returned while CA IDMS was accessing the dictionary record 'SR-036' that relates to your subschema.
Action:
F2009 OBTAIN FOR SDR-042 FAILED
Reason: A non-zero status was returned while CA IDMS was accessing the dictionary record 'SDR-042' that relates to your subschema.
Action:
F2010 OBTAIN FOR ACCESS-045 FAILED
Reason: A non-zero status was returned while CA IDMS was accessing the dictionary record 'ACCESS-045' that relates to your subschema.
Action:
F2011 OBTAIN FOR USER-047 FAILED
Reason: A non-zero status was returned while CA IDMS was accessing the dictionary record 'USER-047' that relates to your subschema.
Action:
F2012 OBTAIN FOR PROG-051 FAILED
Reason: A non-zero status was returned while CA IDMS was accessing the dictionary record 'PROG-051' that relates to your subschema.
Action:
F2013 OBTAIN FOR SSDR-074 FAILED
Reason: A non-zero status was returned while CA IDMS was accessing the dictionary record 'SSDR-074' that relates to your subschema.
Action:
F2014 OBTAIN FOR RCDSYN-079 FAILED
Reason: A non-zero status was returned while CA IDMS was accessing the dictionary record 'RCDSYN-079' that relates to your subschema.
Action:
F2015 OBTAIN FOR NAMESYN-083 FAILED
Reason: A non-zero status was returned while CA IDMS was accessing the dictionary record 'NAMESYN-083' that relates to your subschema.
Action:
F2016 OBTAIN FOR SRCD-113 FAILED
Reason: A non-zero status was returned while CA IDMS was accessing the dictionary record 'SRCD-113' that relates to your subschema.
Action:
F2017 CALC-FIELD NAME NOT FOUND
Reason: Your subschema contains a partial view of a record whose location mode is CALC. The CALC keyfield is not contained with the partial view.
Action: CA IDMS DMLO will not process this type of situation. Reinvoke CA IDMS DMLO and specify a different subschema.
F2018 FINISH FOR DIRECTORY FAILED
Reason: A non-zero status was returned from either the FINISH for the run unit using the subschema 'IDMSNWKA', or from the Directory Interface.
Action:
F2019 DUPLICATE RECORD NAME ENCOUNTERED
Reason: Duplicate record names have been found in the requested subschema. CA IDMS DMLO cannot process subschemas that have duplicate record names.
Action: Validate your subschema. If no duplicate record names exist, contact Technical Support.
F2020 INVALID FIELD BLOCK CHAIN POINTER
Reason: An error has occurred within CA IDMS DMLO.
Action: Contact Technical Support.
F2021 DUPLICATE SET NAME ENCOUNTERED
Reason: Duplicate set names have been found in the requested subschema. CA IDMS DMLO cannot process subschemas that have duplicate set names.
Action: Validate your subschema. If no duplicate set names exist, contact Technical Support.
F2022 DUPLICATE AREA NAME ENCOUNTERED
Reason: Duplicate area names have been found in the requested subschema. CA IDMS DMLO cannot process subschemas that have duplicate area names.
Action: Validate your subschema. If no duplicate area names exist, contact Technical Support.
F2023 INVALID PICTURE FOR FIELD
Reason: The field name and picture clause which follow the message are invalid or not supported with the current release.
Action: If the picture is invalid, correct the source.
F2024 BIT FIELD LENGTH TOO LONG FOR DISPLAY
Reason: The requested bit field has exceeded your logical data width display area. (You defined this area when you signed on to CA IDMS DMLO. For more information on logical data width refer to the CA IDMS DMLO online help facility.)
Action:
F2025 SSR-032 DLENGTH DATA INCORRECT (SHORT)
Reason: The record length defined in the SSR-032 record is less than the actual record length because of an invalid record length calculation for records containing BIT fields.
Action: Reinvoke CA IDMS DMLO and bypass binding any records with BIT fields. CA IDMS DMLO cannot access these records.
F2026 SESSION STORAGE UNAVAILABLE
Reason: Request for storage returned a 'NOT AVAILABLE' condition.
Action:
F2027 PROGRAM LOAD FAILURE
Reason: A module required by CA IDMS DMLO could not be loaded.
Action: Verify that USDMAIN, USDDRCT, USDERRS are located in the library used for the CA IDMS DMLO environment.
F2028 OBTAIN FOR SSMR-068 FAILED
Reason: A non-zero status was returned while CA IDMS was accessing the dictionary record 'SSMR-068' that relates to your subschema.
Action:
F2029 OBTAIN FOR SSCR-070 FAILED
Reason: A non-zero status was returned while CA IDMS was accessing the dictionary record 'SSCR-070' that relates to your subschema.
Action:
F2030 SORTED SET IS MISSING SSCR-070
Reason: A sorted set is indicated by your subschema but no SSCR-070 records were found.
Action:
F2031 INTERNAL ERROR, MISSING SET HTE
Reason: CA IDMS DMLO could not find a set control block.
Action: Contact Technical Support.
F2033 DUPLICATE RECORDS FOUND FOR PROGRAM DBMSDMLO
Reason: More than one record for the program DBMSDMLO was found in the data dictionary. Only one such record may be present.
Action: Contact your system administrator.
F2034 INVALID VERSION NUMBER FOR PROGRAM DBMSDMLO
Reason: The version number parameter supplied to program DBMSDMLO must have the value 1 or 2 or 3. It does not.
Action: Contact your system administrator. The version number supplied to program DBMSDMLO must match the requested security level.
F2100 IDMSNWKA BIND FAILURE IN SUBSCH-CHK
Reason: Attempt to BIND dictionary subschema failed in USDSSLD0.
Action: Have DBA check CA IDMS and CA IDMS DMLO environment.
F2101 IDMSNWKA BIND FAILURE IN FIELD-LOAD
Reason: Attempt to BIND dictionary subschema failed in USDSSLD0.
Action: Have DBA check CA IDMS and CA IDMS DMLO environment.
F2110 IDD RECORD BIND FAILURE IN SUBSCH-CHK
Reason: Attempt to BIND dictionary subschema failed in USDSSLD0.
Action: Have DBA check CA IDMS and CA IDMS DMLO environment.
F2111 IDD RECORD BIND FAILURE IN FIELD-LOAD
Reason: Attempt to BIND a dictionary network record failed in USDSSLD0.
Action: Have DBA check CA IDMS and CA IDMS DMLO environment.
F2120 DDLDML READY FAILURE IN SUBSCH-CHK
Reason: Attempt to READY dictionary area DDLDML failed in USDSSLD0.
Action: Have DBA check CA IDMS and CA IDMS DMLO environment.
F2121 DDLDML READY FAILURE IN FIELD-LOAD
Reason: Attempt to READY dictionary area DDLDML failed in USDSSLD0.
Action: Have DBA check CA IDMS and CA IDMS DMLO environment.
F4001 BIND RUN UNIT FAILED FOR USDPROF
Reason: PROFILE module USDPROFx could not BIND.
Action: Ensure that all installation instructions for the PROFILE module and database have been followed.
F4002 BIND RECORD FAILED FOR USDPROF
Reason: PROFILE module USDPROFx could not BIND.
Action: Ensure that all installation instructions for the PROFILE module and database have been followed.
F4003 READY AREA FAILED FOR USDPROF
Reason: PROFILE module USDPROFx could not READY USD-DATA-AREA.
Action: Ensure that all installation instructions for the PROFILE module and database have been followed.
F4020 GETSTG REQUEST FAILED IN USDPROF
Reason: USDPROFx was unable to obtain storage.
Action: If problem occurs repeatedly, the storage pool in your TP environment may need to be enlarged.
F4100 USDPROF IDMS-STATUS ERROR
Reason: Improper error-status from PROFILE database i/o.
Action: Ensure that all installation instructions for the PROFILE module and database have been followed.
F4440 CA IDMS/DMLO INTERNAL ERROR
Reason: A CA IDMS DMLO internal error occurred.
Action: If problem recurs, contact Technical Support.
F4441 CA IDMS/DMLO INTERNAL ERROR
Reason: A CA IDMS DMLO internal error occurred.
Action: If problem recurs, contact Technical Support.
F4442 CA IDMS/DMLO INTERNAL ERROR
Reason: A CA IDMS DMLO internal error occurred.
Action: If problem recurs, contact Technical Support.
F4443 CA IDMS/DMLO INTERNAL ERROR
Reason: A CA IDMS DMLO internal error occurred.
Action: If problem recurs, contact Technical Support.
F4444 CA IDMS/DMLO INTERNAL ERROR
Reason: A CA IDMS DMLO internal error occurred.
Action: If problem recurs, contact Technical Support.
F4445 CA IDMS/DMLO INTERNAL ERROR
Reason: A CA IDMS DMLO internal error occurred.
Action: If problem recurs, contact Technical Support.
F4446 CA IDMS/DMLO INTERNAL ERROR
Reason: A CA IDMS DMLO internal error occurred.
Action: If problem recurs, contact Technical Support.
F4447 CA IDMS/DMLO INTERNAL ERROR
Reason: A CA IDMS DMLO internal error occurred.
Action: If problem recurs, contact Technical Support.
F4448 CA IDMS/DMLO INTERNAL ERROR
Reason: A CA IDMS DMLO internal error occurred.
Action: If problem recurs, contact Technical Support.
F4449 CA IDMS/DMLO INTERNAL ERROR
Reason: A CA IDMS DMLO internal error occurred.
Action: If problem recurs, contact Technical Support.
F5001 FREEMAIN FAILURE
Reason: A CA IDMS DMLO internal error occurred.
Action: If problem recurs, contact Technical Support.
F5101 ATTEMPT BEYOND START OF TERMINATOR STACK
Reason: A CA IDMS DMLO internal error occurred.
Action: If problem recurs, contact Technical Support.
F7701 LINK FAILED
Reason: LINK to PROFILE module, USDPROF, failed.
Action: Ensure that USDPROFx has been linked and defined to your TP monitor according to installation instructions.
F7702 LINK FOR GSIHELP FAILED
Reason: LINK to HELP module, GSIHELP, failed.
Action: Ensure that the installation instructions appropriate for your TP monitor have been followed.
F7708 LINK FOR USXUMAN FAILED
Reason: Access to full-screen editor failed.
Action: Ensure that CA IDMS DMLO and other Computer Ensure that CA IDMS DMLO and other CA Products have been correctly installed, and the libraries are accessible to CA IDMS/DC.
F7709 LINK FOR USXDRVR FAILED
Reason: Access to full-screen editor failed.
Action: CA products have been correctly installed, and the libraries are accessible to CA IDMS/DC.
F7720 LOAD FOR USDPROF0 FAILED
Reason: Access to CA IDMS DMLO profile module failed.
Action: Ensure that CA IDMS DMLO and other CA Products have been correctly installed, and the libraries are accessible to CA IDMS/DC.
F7721 LOAD FOR USDCMNT0 FAILED
Reason: Access to CA IDMS DMLO CLIST module failed.
Action: Ensure that CA IDMS DMLO and other CA Products have been correctly installed, and the libraries are accessible to CA IDMS/DC.
F8801 USDMLXIT(01)
F8802 USDMLXIT(02)
F8803 USDMLXIT(03)
F8804 USDMLXIT(04)
F8805 USDMLXIT(05)
Reason: Requested termination message from your installation's USDMLXIT user exit program.
Action: See your DBA for specifics.
F8806 USDMLXIT(06)
F8807 USDMLXIT(07)
F8808 USDMLXIT(08)
F8809 USDMLXIT(09)
Reason: Requested termination message from your installation's USDMLXIT user exit program.
Action: See your DBA for specifics.
F9000 SECURITY VIOLATION - TOO MANY ATTEMPTS
Reason: The user ID or the password was entered incorrectly three times.
Action: Re-invoke CA IDMS DMLO and enter the correct user ID and/or password.
F9800 INTERNAL ERROR IN HASH LOGIC
Reason: CA IDMS DMLO internal error.
Action: Contact Technical Support.
F9900 USDTPARM - MISSING INITIAL EYECATCH
Reason: The customization module USDTPARM does not have the expected format.
Action: Review the installation procedure with particular attention to changes to, and assembly of USDTPARM.
F9901 USDTPARM - CORRUPT MENU-MODE COMMAND TABLE
Reason: The customization module USDTPARM does not have the expected format.
Action: Review the installation procedure with particular attention to changes to, and assembly of USDTPARM.
F9902 USDTPARM - CORRUPT MENU-MODE STATIC LINES
Reason: The customization module USDTPARM does not have the expected format.
Action: Review the installation procedure with particular attention to changes to, and assembly of USDTPARM.
F9903 USDTPARM - CORRUPT MENU-MODE HELP TEXT
Reason: The customization module USDTPARM does not have the expected format.
Action: Review the installation procedure with particular attention to changes to, and assembly of USDTPARM.
F9904 USDTPARM - CORRUPT SS EXCLUSION LIST
Reason: The customization module USDTPARM does not have the expected format.
Action: Review the installation procedure with particular attention to changes to, and assembly of USDTPARM.
F9905 USDTPARM - CORRUPT DISPLAY CHARACTERS
Reason: The customization module USDTPARM does not have the expected format.
Action: Review the installation procedure with particular attention to changes to, and assembly of USDTPARM.
F9906 USDTPARM - CORRUPT KEYWORD TBL BOUNDS
Reason: The customization module USDTPARM does not have the expected format.
Action: Review the installation procedure with particular attention to changes to, and assembly of USDTPARM.
F9907 USDTPARM - CORRUPT KEYWORD TBL ENTRY
Reason: The customization module USDTPARM does not have the expected format.
Action: Review the installation procedure with particular attention to changes to, and assembly of USDTPARM.
F9990 INTERNAL ERROR
Reason: CA IDMS DMLO internal error.
Action: Contact Technical Support.
F9991 INTERNAL ERROR
Reason: CA IDMS DMLO internal error.
Action: Contact Technical Support.
F9992 INTERNAL ERROR - MAIN(XPNDVAR)
Reason: CA IDMS DMLO internal error.
Action: Contact Technical Support.
F9993 VB50 EYECATCHER MISSING
Reason: Subschema control blocks not as expected.
Action: Contact Technical Support.
F9994 VB50 EYECATCHER MISSING
Reason: Subschema control blocks not as expected.
Action: Contact Technical Support.
F9995 INTERNAL ERROR
Reason: CA IDMS DMLO internal error.
Action: Contact Technical Support.
F9996 INTERNAL ERROR
Reason: CA IDMS DMLO internal error.
Action: Contact Technical Support.
F9997 INTERNAL ERROR
Reason: CA IDMS DMLO internal error.
Action: Contact Technical Support.
F9998 INTERNAL ERROR
Reason: CA IDMS DMLO internal error.
Action: Contact Technical Support.
F9999 INTERNAL ERROR VALUE TOO LARGE
Reason: An error has occurred within CA IDMS DMLO.
Action: Contact Technical Support.
ISQ01 ACTION = (K)ill ACTION = (K)ill, (S)elect -or- Pxx to exit
Reason: SHOW SCRATCH command entered, or ?T variable appeared in command.
Action: In either case you may DELETE (K) a scratch area. If ?T was used, you must select an item, or press the indicated key to return to processing.
I1001 PRINT SUCCESSFUL
Reason: The print that was requested has been completed.
Action: None. This message is informative only.
I2001 FIELD RESET TO USAGE MODE LENGTH nnn BYTES,
Reason: The field-name was previously changed to hexadecimal usage mode. This message is returned after the field has been reset to its native mode by using the 'SET field-name NATIVE' command.
Action: None. This message is informative only.
I2002 USAGE CHANGED
Reason: The field or record in the 'SET field-name HEX' command was changed to hexadecimal usage mode.
Action: None. This message is informative only.
I2003 EQUATE SUCCESSFUL
Reason: This message is displayed after a successful execution of an EQUATE command.
Action: None. This message is informative only.
I2004 NO PF KEYS ARE ASSIGNED YET
Reason: This message indicates there have not been any PF keys programmed during this CA IDMS DMLO session.
Action: None. This message is informative only.
I2005 FALSE
Reason: This message is displayed as the result of a false condition in the CA IDMS DML 'IF' command.
Action: None. This message is informative only.
I2006 TRUE
Reason: This message is displayed as the result of a true condition in the CA IDMS DML 'IF' command.
Action: None. This message is informative only.
I2007 CHECK ALL RECORDS TO BE BOUND
Reason: This message is displayed after successful completion of the initialization process. CA IDMS DMLO is prompting you to indicate which records you want access to (or bound) during the CA IDMS DMLO session.
Action: To bind a record, position the cursor in the unprotected area next to the record to be bound and enter any keyboard character, then press the ENTER key. To bind all records, key in BIND ALL in the command input area, and press the ENTER key.
I2008 INDICATE READY MODE FOR AREAS - SU SR PU PR EU ER
Reason: This message appears when the READYLIST command is entered and the READY SCREEN appears. CA IDMS DMLO is prompting you to enter usage modes for the areas that are to be readied.
Action: To enter the usage mode for an area, position the cursor in the unprotected area following the area name; enter one of the modes indicated in the message; and press the ENTER key. (Refer to the appropriate CA IDMS reference manual for more information on usage modes.)
I2009 NOTHING TO SHOW FOR REQUEST
Reason: The SHOW command was executed. The requested operand did not have any data to display.
Action: None. This message is informative only.
I4504 ALL AREAS READIED IN (SHARED) RETRIEVAL
Reason: A CA IDMS DML READY command was issued with no operands. By default, this results in all areas being readied in a usage mode of shared retrieval. This message is a reminder that this has occurred.
Action: None needed unless some or all areas should have been readied in a different usage mode. If this is the case, terminate the CA IDMS DMLO session by entering a FINISH command, and begin a new session. (Once an area has been readied, its usage mode cannot be changed.) In the new session, ready areas by using individual CA IDMS DML READY commands, or use the CA IDMS DMLO READYLIST feature.
I5001 AUTOHEX MODE NOW on/off
Reason: The SET command for this option was processed.
Action: None.
I5002 COBOL DISPLAY MODE NOW on/off
Reason: The SET command for this option was processed.
Action: None.
I5003 COMMAND DISPLAY WILL BE as input / as used
Reason: The SET command for this option was processed.
Action: None.
I5004 LOWER CASE OPTION NOW on/off
Reason: The SET command for this option was processed.
Action: None.
I5005 EXIT FOR ALL VERBS NOW on/off
Reason: The SET EXIT .. ALL was processed.
Action: None.
I5006 EXIT FOR DML VERB NOW on/off
Reason: The SET EXIT .. verb was processed.
Action: None.
I5007 EQUATE CANCELED
Reason: An EQUATE symbol NULL has been processed.
Action: None.
I5008 PF KEY COMMAND CLEARED
Reason: A NULL command has been "autoset" to a PF key.
Action: None.
I5009 MACRO COMMAND ACCEPTED
Reason: A macro command has been "autoset" to a PF key.
Action: None.
I5010 PROFILE RESTORED
Reason: A PROFILE has been restored.
Action: See below.
I5011 MAKE ANY REQUIRED CHANGES AND/OR PRESS ENTER
Reason: A PROFILE has been restored. Any items may be changed.
Action: Press the ENTER key when variables are as needed.
I5012 ERROR-STATUS 0000 RETURNED FROM finish / rollback
Reason: A successful FINISH or ROLLBACK was processed.
Action: None.
I5013 NO VARIABLES CURRENTLY SET
Reason: A SHOW VARIABLES request was entered, but none of the variables have values.
Action: None.
I5014 PROFILE xxxxxxx ERASED
Reason: A ( PROFILE %ERASE ) request was processed.
Action: None.
I5015 ALL PROFILES ERASED FOR USER
Reason: A ( %ALL %ERASE ) request was processed.
Action: None.
I5536 EXEC CLIST in STEP MODE
Reason: Indicates the operation mode under which the CLIST is operating.
Action: None.
I5537 MAPIN DATA PROCESSED IN STEP MODE
Reason: Indicates the operation mode under which MAPIN data is processed.
Action: None.
I5538 AUTOBIND OF RECORDS IS NOW ON
Reason: Indicates the status of the SET AUTOBIND option.
Action: None.
I5539 CLIST XXXXXXXX ERASED
Reason: The specified CLIST or PROFILE has been erased.
Action: None.
I5540 ALL CLISTS ERASED FOR USER
Reason: All CLISTs or PROFILES have been erased for the current user.
Action: None.
I5541 COPY/REPLACE COMPLETED
Reason: The current maintenance operation was successfully completed.
Action: None.
I5542 RENAME COMPLETED
Reason: The specified CLIST or PROFILE has been successfully renamed.
Action: None.
I5543 SELECTED CLISTS ERASED
Reason: The specified CLISTs or PROFILES have been successfully erased.
Action: None.
I5544 PROMPT : AWAITING REPLY
Reason: CA IDMS DMLO encountered a "PROMPT" command in the current CLIST.
Action: Execution will continue after you enter the RESUME command. You may enter any valid commands prior to that time.
I6004 RECORD FOUND : VERSION
Reason: The dictionary-owned record has been found with the indicated version number.
Action: None.
I6005 ACTION = (B)ind, (I)nit ACTION = (B)ind, (I)nit, (S)elect -or- Pxxx to exit
Reason: A SHOW RECORDS command was entered, or ?R was encountered in a command.
Action: No action required for SHOW RECORDS command. If ?R is part of a command, however, you must either (S)elect an entry or press the indicated key to continue processing.
You may enter B or I in either case.
I6006 ACTION = READY mode ACTION = READY mode, (S)elect -or- Pxxx to exit
Reason: A SHOW AREAS command was entered, or ?A was encountered in a command.
Action: No action required for SHOW AREAS command. If ?A is part of a command, however, you must either (S)elect an entry or press the indicated key to continue processing.
You may enter a READY mode for any non-readied area in either case.
I6007 ACTION = any character to Select
Reason: A ?S selection variable for SET was encountered in a command.
Action: You must (S)elect an entry or press the indicated key to continue processing.
I6014 INVALID CHARACTER TRANSLATE RESULT IS NOW x
Reason: The command "SET INVCHAR x" was entered.
Action: None.
I6015 ACTION = (S)elect or PAx to exit
Reason: A list of available subschemas has been requested.
Action: Select a subschema or press the indicated key to return to the Signon screen.
I6018 nnnn PROFILES/CLISTS KILLED
Reason: A "mass delete" request has been processed.
Action: None; this message is for information only.
USXD002E INVALID COMMAND
Reason: An invalid primary command was encountered. The cursor will be on the command.
Action: Check the syntax of the command. Correct and reenter the command.
USXD202E INVALID PARAMETER ON COMMAND
Reason: A valid command has been entered with an unrecognizable parameter.
Action: Check the syntax of command parameter. Correct and reenter the parameter.
USXD204E ENTER LOCATE PARAMETER
Reason: A line number was not included as a parameter in the LOCATE command.
Action: Check the syntax of the command. Correct the command (include line number parameter) and reexecute.
USXD206E ONLY A NUMBER, MAX, HALF, CSR, OR PAGE IS ALLOWED
Reason: An illegal option has been used with the LEFT, RIGHT, UP, or DOWN command.
Action: Check the syntax of the parameter. Correct the parameter (you may have included some erroneous characters in the syntax line) and reexecute.
USXD208E ONLY "ON" OR "OFF" IS ALLOWED. "ON" IS THE DEFAULT
Reason: An illegal option has been used with the NULLS command or CAPS command.
Action: Check the syntax of the parameter. Correct the parameter (you may have included some erroneous characters in the syntax line) and reexecute.
USXD210E NO PARAMETER IS ALLOWED ON COMMAND
Reason: A parameter has been included in the syntax of the CANCEL command which excludes parameters.
Action: Check the syntax of the command. Correct the command (delete the parameter) and reexecute.
USXF001I FOUND CHARS "string"
Reason: The string indicated has been found in the text. The cursor will be positioned at the beginning of the found string.
Action: None.
USXF003I REP "string" WITH "replacement-string"
Reason: The string indicated has been replaced with the replacement string. The cursor will be positioned at the replacement string.
Action: None.
USXF004E MUST ENTER A FIND OR CHANGE COMMAND FIRST
Reason: The RFIND (repeat find) or RCHANGE (repeat change) command was entered without a FIND or a CHANGE command being entered first.
Action: Be sure to enter the FIND command or the CHANGE command before the RFIND command or the RCHANGE command.
USXF005I BOTTOM OF DATA REACHED
Reason: The bottom of the text was reached before the string was found. If you enter an RFIND (repeat find) or an RCHANGE (repeat change) at this time, the editor will begin searching for the string at the top of the text.
Action: None.
USXF006E ENCLOSE STRING IN QUOTES
Reason: A single quotation mark was found where a pair is required or embedded blanks were found in the search string.
Action: Check quotation marks, correct, and reenter the command. If a string has embedded blanks, enclose it in quotation marks.
USXF007E INVALID FIND SYNTAX
Reason: The string specified in the FIND command is invalid. If the string has embedded blanks or quotation marks, it may appear to the editor to be more than one string; you can only specify one string in the FIND command.
Action: Check the syntax of the command. If the string has embedded blanks, enclose it in quotation marks. If the string has embedded single quotation marks, enclose it in double quotation marks. If the string has embedded double quotation marks, enclose it in single quotation marks. Then reenter the command.
USXF008E INVALID CHANGE SYNTAX
Reason: A string specified in the CHANGE command is invalid. If one of the strings has embedded blanks or quotation marks, it may appear to the editor that you are entering more than two strings; you can only specify two strings in the CHANGE command.
Action: Check the syntax of the command. If a string has embedded blanks, enclose it in quotation marks. If a string has embedded single quotation marks, enclose it in double quotation marks. If a string has embedded double quotation marks, enclose it in single quotation marks. Then reenter the command.
USXF009I NO CHAR "string" FOUND
Reason: The editor has searched the entire text without finding the indicated string.
Action: None.
USXF010W ERROR CHARACTERS "string"
Reason: The string used to replace the one found is too long.
Action: Adjust the length of the found string or reduce the length of the replacement string to match the length of the one found.
USXF012I FOUND nnn OCCURRENCES OF "string"
Reason: A string specified in the FIND ALL command has been found the specified number of times.
Action: None.
USXF014I CHANGED nnn OCCURRENCES OF "string"
Reason: A string specified in the CHANGE ALL command has been changed in the text the specified number of times.
Action: None.
USXF016E CHANGE COMMAND NOT ENABLED IN BROWSE MODE
Reason: The CHANGE command was used in the Browse Option to search for and change the next occurrence of a string.
Action: None. The CHANGE command can only be used when editing text (Edit Option) and not while in Browse mode.
USXF018W CHANGED nnn OCCURRENCES WITH nnn ERRORS OF "string"
Reason: The string identified in the CHANGE ALL command has been changed successfully (nnn OCCURRENCES) with (nnn ERRORS).
Action: Look for the error message on the line number field(s) and make the necessary correction(s).
USXI002E INVALID COMMAND
Reason: An invalid line command has been entered.
Action: Check the syntax of the line command on the line number field. Correct and reenter the command.
USXI006E INVALID ON THIS LINE
Reason: A line command has been entered on a line for which the command is invalid.
Action: Reenter the line command on an appropriate line.
USXI008E INVALID SCROLL AMOUNT
Reason: An invalid Scroll Option was entered in the SCROLL field.
Action: Check the syntax of the Scroll Option next to the word SCROLL. Be sure the option starts in the left-most position of the field. Correct syntax or position.
USXL002W BLOCK COMMAND INCOMPLETE
Reason: A partial sequence of Line Commands, in block form, is incomplete and cannot be executed.
Action: If you are just scrolling or using the FIND command to locate the line to complete the block command, this message serves as a warning. Complete the command and execute. Otherwise, check the syntax of the commands to be sure all commands in block form are in pairs. Correct the commands and reexecute.
USXL004E COMMAND CONFLICT
Reason: A sequence of Line Commands cannot be executed.
Action: Check the order of the commands. Correct the commands and reexecute.
USXL006W MOVE/COPY PENDING
Reason: A move or copy cannot be executed because of a missing 'A'(after), 'B' (before), 'C' (copy), or 'M' (move) line command or COPY Primary command.
Action: Enter the missing command.
USXL008E ITERATION COUNT MISMATCH
Reason: Block (RR) line command iterations have conflicting values.
Action: Check the syntax of the command. Make sure that the values of the iterations match (one or both may be left blank).
USXL009E LINE COMMAND RANGE CONFLICT
Reason: A sequence of Line Commands cannot be executed because the range of one line command overlaps the range of another.
Action: Check the order of the commands. Correct the commands and reexecute.
W2001 MODIFIED DATA ENTERED, COMMAND IGNORED
Reason: This message is displayed when data has been entered in the unprotected area and in the command input area. The data entered in the unprotected area always takes precedence over any command entered. (Refer to the CA IDMS DMLO online help for a detailed discussion.)
Action: To enter the command, rekey the first character in the displayed command and press the ENTER key.
Note: This will not occur if MAPIN mode is FAST.
W2003 OCCURS DEPENDING ON CONTROL FIELD ALTERED - REDISPLAY RECORD
Reason: A control field in an 'OCCURS DEPENDING ON' clause has been changed.
Action: CA IDMS DMLO has changed the field in the record data buffer. If you want to add or delete data in a field, enter 'DISPLAY record-name'. This will reformat the record to allow data to be added or deleted in the display record buffer area.
W2004 A REDEFINING FIELD WAS MODIFIED
Reason: This message indicates that a field in a redefined group has been changed.
Action: CA IDMS DMLO has changed the field in the record data buffer. To view the record in its new format enter the 'DISPLAY record-name' command. This will avoid possible confusion when the display is different.
W2008 RECORD DISPLAY INCOMPLETE - TOO MANY (FIELDS/OCCURS)
Reason: The record to be displayed could not fit into the display buffer area. The display buffer area ran out of line storage space.
Action: Enter the 'DISPLAY record-name CONTINUE' command to view the remaining fields.
W2009 RECORD DISPLAY INCOMPLETE - FIELD TOO LONG
Reason: The record to be displayed could not fit into the display buffer area. The display buffer area ran out of line storage space.
Action: Enter the 'DISPLAY record-name CONTINUE' command to view the remaining fields. (If you were displaying a field, the entire record must be displayed to use the CONTINUE option.)
W2010 USAGE MODE MAY NOT BE CHANGED FOR A BIT FIELD
Reason: The usage mode can be changed for any type of field except bit.
Action: None.
W4503 READY AREA(S) FAILED...STAT: nnnn AREA: area-name
Reason: An attempt to ready an area failed. If an unqualified ready was attempted, one of the readies failed, and others in the group may not have been processed. In the message, area-name is the name of the area that could not be readied; nnnn is the CA IDMS status code generated when the failure occurred.
Action: Correct the situation described by the status code, and reenter the READY command, or contact your system administrator.
W5001 MODIFIED DATA ENTERED, PF KEY IGNORED
Reason: Record data was changed at the same time that a PF key associated with a command was pressed, and MAPIN mode was not FAST.
Action: None.
W5002 EXIT CHANGES DISALLOWED
Reason: Installation parameters disallow changes to user exit specifications.
Action: None.
W5003 HELP NOT YET AVAILABLE FOR TSO
Reason: HELP function requested but not available for this environment.
Action: None.
W5004 HELP NOT YET AVAILABLE FOR CICS
Reason: HELP function requested but not available for this environment.
Action: None.
W5545 RECORD ALREADY BOUND
Reason: Record has already been bound.
Action: None.
|
Copyright © 2014 CA.
All rights reserved.
|
|