DL/I Status Codes

This appendix describes DL/I status codes returned after an application issues a DL/I call.

Applications refer to the DL/I status codes to process user requests.

  • AC

    Description

    Error with the SSA that was passed to a DL/I call such as GU, GHU, GN, GHN, GNP, GHNP, ISRT, DLET, or REPL.

    Reason

    • SSA is not specified in a hierarchical sequence.

    • DL/I failed to find the segment name defined in SSA from PCB.

    • A segment name is defined in the database PCB statement but not in the accessed hierarchical sequence.

    • A duplicate SSA is defined at the same level.

    Action

    Check and correct the hierarchical sequence or name of the segment defined in SSA.

  • AD

    Description

    Invalid function parameter or unsupported parameter type.

    Reason

    • The function parameter is not valid.

    • The parameter sequence is not valid.

    • I/O PCB was not used to call a service.

    • PCB was not used to call the database.

    Action

    Check that the function code or parameter sequence is valid.

  • AH

    Description

    One or more SSA parameters were called.

    Reason

    ISRT call does not contain an SSA parameter.

    Action

    Check that the ISRT call contains an SSA parameter.

  • AI

    Description

    An error occurred while opening the database.

    Reason

    • A DBPCB call was issued on a data set, which is being opened for load, using an option other than L or LS.

    • An ISRT call was issued on an already loaded data set using L or LS option.

    Action

    Check that the data set was loaded.

  • AJ

    Description

    SSA is invalid.

    Reason

    • SSA contains an invalid command code.

    • A relational operator specified in the qualification statement is invalid.

    • A bracket is missing or is not used in pair in the qualification statement.

    • Qualified SSA is used in a DLET, REPL, or ISRT call.

    Action

    Correct the SSA format.

  • AK

    Description

    An invalid field name exists in SSA.

    Reason

    • An invalid field name is defined in SSA.

    • The field name defined in SSA does not exist in DBD.

    Action

    Correct the field name in SSA.

  • AM

    Description

    The call is not compatible with the processing option defined in PROCOPT of PCB.

    Reason

    • A DLET, REPL, or ISRT call, which references PCB, does not have a proper processing option. Processing options for these calls must be D for DLET, R for REPL, or I for ISRT.

    • The processing option for the referenced PCB was not set to L when the init load program issued an ISRT call.

    Action

    Correct the function or make the necessary changes in the PCB.

  • AO

    Description

    A physical I/O error has occurred in TSAM.

    Reason

    • An error has occurred in TSAM.

    • A TSAM database file was deleted or is not accessible.

    Action

    Check for an error in TSAM.

  • AP

    Description

    A CHKP call was issued with an invalid number of parameters.

    Reason

    Specified more than four parameters for the CHKP call.

    Action

    Correct the CHKP call statement.

  • DA

    Description

    Attempted to change the field of an unmodifiable segment.

    Reason

    • A DLET or REPL call has attempted to change the key field of a segment.

    • The REPL option of PSB has attempted to change a field defined as NO.

    Action

    Modify the call.

  • DJ

    Description

    A DLET or REPL was issued on a segment that is not in a hold state.

    Reason

    • DLET or REPL is executed without a preceding GHU, GHN, or GHNP call.

    • A DLET call was issued on a already deleted segment.

    Action

    Modify the call.

  • DX

    Description

    The DLET call violates the rule of the segment’s delete rule.

    Reason

    A program has issued a DLET call that violates the delete rule of the segment.

    Action

    Check with the DBA to see what delete rule was specified for the segment.

  • GA

    Description

    A segment at a higher level was retrieved.

    Reason

    A segment at a higher level was retrieved for an unqualified GN or GNP call.

    Action

    Informative status code.

  • GB

    Description

    End of database was reached during a sequential search.

    Reason

    End of database was reached while processing a GN call.

    Action

    Application program determines the action to take.

  • GD

    Description

    An ISRT call was issued when the current position on the segment is no longer valid.

    Reason

    Attempted to execute ISRT when the existing position on the segment was deleted or does not exist.

    Action

    Application program determines the action to take.

  • GE

    Description

    There is no segment instance satisfying the search criteria.

    Reason

    • For a Get call, a segment instance satisfying the search criteria is not found.

    • For an ISRT call, a parent segment of the segment being inserted is not found.

    Action

    Application program determines the action to take.

  • GG

    Description

    A segment with an invalid segment pointer is found.

    Reason

    • An invalid value was found in the segment prefix area that the segment pointer points to.

    • The segment, which the segment points to, does not exist at the specified location.

    Action

    • Check if data was successfully loaded into the database. If you are using a COBOL application to load the data, terminate the program using the GO BACK command, instead of the STOP RUN command, to load the data successfully.

    • For HDAM or HIDAM, check if the length of the record is specified so that one record is inserted into one CI space.

  • GK

    Description

    A new segment type was retrieved at the same level.

    Reason

    A new segment type was retrieved at the same level for an unqualified GN or GNP call.

    Action

    Informative status code.

  • GP

    Description

    No parentage was specified.

    Reason

    • The program issued a GNP call when there was no the parentage established.

    • The segment level specified by the GNP call is higher than the level of the parent.

    Action

    Specify parentage before issuing a GNP call, and then check the segment level specified by the GNP.

  • II

    Description

    A duplicate segment name exists in the database.

    Reason

    • An ISRT call attempted to insert a segment that already exists in the database.

    • There is an existing segment with an equal physical or logical twin sequence field.

    Action

    Delete the duplicate segment value and then try again.

  • IX

    Description

    A program issued an ISRT call that violates the insert rule of the segment.

    Reason

    • Attempted to insert a logical child segment whose logical or physical parent segment does not exist.

    • Attempted to insert a concatenated segment, which does not have a logical or physical parent segment, through the physical path.

    • Attempted to insert a concatenated segment through the logical path, but there is no segment whose key matches the key of the logical or physical parent in the I/O Area.

    Action

    Correct the ISRT or the program.

  • LB

    Description

    A duplicate segment was found in the database when loading the segment.

    Reason

    • A segment with an equal physical twin sequence field is found.

    • A segment without a physical twin forward pointer attempted to insert the second segment of this segment type for the parent.

    Action

    Correct the ISRT call or LOAD command.

  • LC

    Description

    The key field of the loaded segment is not in hierarchical sequence.

    Reason

    The specified data is not in hierarchical sequence.

    Action

    Check the segment and decide where to load the segment.

  • NI

    Description

    A duplicate segment exists in a unique secondary index.

    Reason

    Duplicate index segment is found while attempting to IMS INSERT or UPDATE a source segment for a secondary index specified with a unique sequential field.

    Action

    The action is determined by the application. If there are duplicate secondary index entries, specify the index as non-unique and provide an overflow entry-sequenced data set.

  • V1

    Description

    An invalid segment length was specified.

    Reason

    • An ISRT or REPL call was issued on a variable-length segment whose length was specified with a value outside the range defined in the BYTES item of the SEGMENT section in DBD.

    • The segment length specified for an ISRT or REPL call exceeded the record length of the data set. For a fixed-length segment, the data length must be within the value set in the BYTES item of the SEGMENT section in DBD. For a variable-length segment, the data length must be within the value specified in the input and output buffer of the segment data. You must also consider the length of the segment prefix of each access method.

    Action

    Correct the application or the value of BYTES item in the DBD SEGMENT section.

  • ZZ

    Description

    An internal error occurred during HiDB operation.

    Reason

    There are various reasons causing a malfunction of HiDB.

    Action

    The action is made by checking the displayed OpenFrame error code.

For detailed information about each statue code, refer to "Chapter 17. DL/I Status Codes" in IBM IMS V7 Application Programming: Database Manager.