DDI-1037-00-F Unexpected EOF on DBD-PSB file AMB found a continuation character at the end of a PSB or DBD. AMB did not find a DBDGEN, FINISH, or END for a DBD; AMB did
not find a PSBGEN or END for a PSB.
DDI-2001-00-E Invalid card type DDI statements for VSAM processing must have a valid type starting in column 12. Valid types are:
DDI-2002-00-E DDNAME required for ALT indices AMB requires A DDN= followed by a name up to 8 characters for alternate indices. This name is the VSAM ddname of the file where AMB defines the alternate index.
DDI-2003-00-E DDN for primary IDX VSM DDN If you supply a ddname for a primary index, it must be the same name as the ddname of the file. If you do not supply a ddname, it defaults to the VSAM ddname.
DDI-2007-00-E Record name missing AMB did not find a NAME= parameter on a REC statement. AMB requires a COBOL record name up to 30 characters. The name of the
first record is also the long file name for the file.
DDI-2008-00-E File DDN missing AMB did not find a DDN= parameter on a VSM statement. AMB requires a ddname for the file; it can be up to 8 characters.
DDI-2009-00-E Member name missing AMB did not find a COPY= parameter followed by an 8 character name on a REC statement. This copybook member gives the record
description.
DDI-2013-00-E AVG length greater than maximum On a variable length file, the average length of the record is larger than the maximum length. AVGLEN= should be less than
or equal to MAXLEN=.
DDI-2015-00-E Subschema name missing AMB found a SUB statement without NAME=. This is the name of the VSAM data view and may be up to 8 characters.
DDI-2016-00-E Subschema records missing AMB found a SUB statement without REC=. This name should be the COBOL record name of the first record in the VSAM file and
can be up to 30 characters.
DDI-2021-00-E Improper format in the DBD parameter AMB found an error specifying a second argument on the DBD= parameter. Either a right parenthesis is missing or you supplied
a non-numeric character.
DDI-2030-00-E Illegal dataset You defined a label field in a data set statement without operands; but the access method specified in the DBD statement does
not allow labeling without operands. Access must be HDAM or HIDAM.
DDI-2041-00-E Expected continuation not found When processing the DDI statements, AMB found a statement with a comma at the end and you did not continue the statement on
the next line.
DDI-2045-00-E REC has no DBD before IT When processing the DDI statements for the DBD, AMB found a REC statement without a DBD statement before it. See Coding IMS
DDI Statements.
DDI-2052-00-E xmlDDI FLD card has no IMSNAME While processing DDI statements for PCB-level DDI overrides, AMB encountered a FLD statement without a IMSNAME= keyword or
with spaces following IMSNAME=. See Coding IMS DDI Statements.
DDI-2053-00-E A PCB card was not entered for all PCBs While processing DDI statements for PCB-level overrides, you did not enter enough PCB statements to match all the TP and DB
PCBs in the PSB. See Coding IMS DDI Statements.
DDI-2054-00-E REC card has no PCB card before it While processing DDI statements for PCB-level DDI overrides, AMB encountered a REC statement out of order. A REC statement
must have a PCB statement preceding it. The proper statement sequence for PCB-level DDI statements is:
DDI-2055-00-E PCB card has no PSB card before it While processing DDI statements for a PCB-level override, AMB encountered a PCB statement out of order. A PCB statement must
have a REC statement following it. The proper sequence for PCB-level DDI statements is:
DDI-5008-00-D DDI info for was not added When processing the DDI statements, AMB did not add information to the DDI file for reasons stated in prior error messages.