Category: DB macros.
Fatal error, processing stopped. When unpacking data from the DDI file, a pointer calculated was out of range.
Contact your APS Administrator.
Fatal error, processing stopped. When unpacking data from the DDI file, text calculated was out of range.
Contact your APS Administrator.
Fatal error, processing stopped. When deleting an entity from the DDI file, a file error occurred.
Contact your APS Administrator.
Fatal error, processing stopped. APS attempted to search the DDI file and found it empty.
Check JCL to be sure it is pointing to the correct DDI file.
Fatal error, processing stopped. A SAVE or CANCEL on the DDI file failed.
Contact your APS Administrator.
Fatal error, processing stopped. A CREATE or UPDATE on the DDI file failed.
Contact your APS Administrator.
Fatal error, processing stopped. A READ on the DDI file failed.
Contact your APS Administrator.
Fatal error, processing stopped. When unpacking data from the DDI file, a pointer calculated was out of range.
Contact your APS Administrator.
Fatal error, processing stopped. When unpacking data from the DDI file, the text calculated was out of range.
Contact your APS Administrator.
An error occurred when reading the DDI file.
Reload the entity into the file.
On the JCL parameter NAME= the name that followed (a PSB or DBD name) was greater than 8 characters.
Correct the error and resubmit.
APS found an invalid JCL parameter. Valid parameters are:
Correct the error and resubmit.
You specified more than 1000 PSB names on the PSB= parameter.
Correct the error and resubmit.
APS did not find the segment named in the PSB in either the DBD or the DDI statements source.
Correct the error and resubmit.
APS did not find the segment parent specified on the PSB in the DBD.
Correct the error and resubmit.
Software error.
Contact your APS Administrator.
Software error.
Contact your APS Administrator.
APS did not find the named record in the DDI file. Reloading into the DDI file may be necessary.
Correct error and resubmit.
The named record is locked on the DDI file.
Run the DDI unlock utility and resubmit.
Fatal error, processing stopped. When unpacking data from the DDI file, a pointer calculated was out of range.
Contact your APS Administrator.
Fatal error, processing stopped. When unpacking data from the DDI file, text calculated was out of range.
Contact your APS Administrator.
Fatal error, processing stopped. A SAVE or CANCEL on the DDI file failed.
Contact your APS Administrator.
Fatal error, processing stopped. A CREATE or UPDATE on the DDI file failed.
Unlock the DDIFILE. If this is unsuccessful, contact your APS Administrator.
Fatal error, processing stopped. A READ on the DDI file failed.
Contact your APS Administrator.
Fatal error, processing stopped. A CREATE on the DDI file failed.
Ensure there is enough space for the entity on the DDI file and resubmit the job.
Fatal error, processing stopped. A CREATE or UPDATE on the DDI file failed.
Contact your APS Administrator.
Fatal error, processing stopped. A DELETE on the DDI file failed.
Contact your APS Administrator. Please be ready to give complete information when calling. See Generator Reporting.
While processing DDI statements for a DBD, APS found a version field that is not-numeric.
Correct error and resubmit.
While processing DDI statements for a DBD, APS found a version field that is greater than 255.
Correct error and resubmit.
While processing DDI statements for a DBD, APS found a MOD field that is not numeric.
Correct error and resubmit.
While processing DDI statements for a DBD, APS found a MOD field is greater than 255.
Correct error and resubmit.
While processing a PSB, APS did not find the DBDNAME= or PSBNAME= parameter.
Correct error and resubmit.
While processing a PSB, APS found the DBDNAME= parameter with a nonexistent name for the DBD.
Correct error and resubmit.
While processing a PSB, APS detected more than 10 DBD references.
Correct error and resubmit.
While processing a PSB, the PSBNAME= parameter had no name associated with it.
Correct error and resubmit.
While processing a PSB, APS detected more than 10 PSB references.
Correct error and resubmit.
APS found a continuation character at the end of a PSB or DBD. APS did not find a DBDGEN, FINISH, or END for a DBD; APS did not find a PSBGEN or END for a PSB.
Correct error and resubmit.
APS found a DBD name longer than 8 characters.
Change the name of the DBD character to be 8 characters or less.
Invalid keyword passed as a parameter to DDIDDG.
Change the keyword.
You did not close a parameter with a right parenthesis.
Add a right parenthesis to the parameter.
Parameter is missing a right parenthesis.
Add right parenthesis to parameter.
APS found something other than *DDI starting in column 7 of the DDI source.
Correct the statement and resubmit.
DDI statements for VSAM processing must have a valid type starting in column 12. Valid types are:
Correct the statement and resubmit.
APS requires A DDN= followed by a name up to 8 characters for alternate indices. This name is the VSAM ddname of the file where APS defines the alternate index.
Correct the statement and resubmit.
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.
Correct the statement and resubmit.
You must supply a short record name on all REC statements. This name may be up to 8 characters.
Correct the statement and resubmit.
When defining a file with multiple records, only the first REC statement can have a COPY=. This copybook member should contain a definition for all records in the file.
Correct the statement and resubmit.
All REC statements require a maximum record length.
Correct the statement and resubmit.
APS did not find a NAME= parameter on a REC statement. APS requires a COBOL record name up to 30 characters. The name of the first record is also the long file name for the file.
Correct the statement and resubmit.
APS did not find a DDN= parameter on a VSM statement. APS requires a ddname for the file; it can be up to 8 characters.
Correct the statement and resubmit.
APS did not find a COPY= parameter followed by an 8 character name on a REC statement. This copybook member gives the record description.
Correct the statement and resubmit.
APS found a SOURCE= parameter with a value other than P (PDS member) or C (COBOL copybook member).
Correct the statement and resubmit.
APS found a VSM statement with an invalid TYPE=. Valid record types are:
Correct the statement and resubmit.
All REC statements require MAXLEN=.
Correct the statement and resubmit.
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=.
Correct the statement and resubmit.
You must code at least one IDX statement for a keyed VSAM file. The IDX statement must follow the first REC statement for the file.
Correct the statement and resubmit.
APS found a SUB statement without NAME=. This is the name of the VSAM subschema and may be up to 8 characters.
Correct the statement and resubmit.
APS 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.
Correct the statement and resubmit.
APS found a REC statement with an invalid keyword. Valid keywords are:
Correct the statement and resubmit.
APS found a SUB statement with an invalid keyword. Valid keywords are:
Correct the statement and resubmit.
APS found a SUB statement with a PROCOPT= followed by an invalid processing option. Valid options are:
Correct the statement and resubmit.
APS did not find any PSB names or DBD names on the JCL parameter.
Correct the error and resubmit.
APS found an error specifying a second argument on the DBD= parameter. Either a right parenthesis is missing or you supplied a non-numeric character.
Correct the error and resubmit.
When processing the PSB, APS did not find a PROCSEQ or indices specified in the DBD.
Correct the error and resubmit.
When processing the DBD, APS did not find the specified segment for the XDFLD in the DDI file.
Correct the error and resubmit.
APS did not find the named VSAM record on the DDI file.
Correct the error and resubmit.
APS found an invalid statement in the DBD, DDI statements, or PSB source.
Correct error and resubmit.
APS found a DDI statement with an illegal keyword. Valid keywords are:
Correct error and resubmit.
APS found a statement in the DDI source that did not start with *DDI.
Correct error and resubmit.
When processing a DBD, APS did not find the NAME= or ACCESS= parameter.
Correct error and resubmit.
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.
Correct error and resubmit.
You did not previously define the label specified on the current data set with operands.
Correct error and resubmit.
When processing a DBD, APS found a FLD statement without a segment before it.
Correct error and resubmit.
When processing a DBD, APS found an LCHILD statement without a segment before it.
Correct error and resubmit.
When processing a DBD, APS found an XDFLD statement without a segment before it.
Correct error and resubmit.
The PSB name is missing from the parameter supplied to generate the step.
Correct error and resubmit.
While processing a PCB, APS found the TYPE = parameter missing or invalid.
Correct error and resubmit.
While processing a PSB, APS found a SENSEG parameter without a prior PCB statement.
Correct error and resubmit.
While processing a PSB, APS found a SENFLD statement without a prior SENSEG statement.
Correct error and resubmit.
While processing a DBD, APS found a DBD DDI statement with something other than name or version.
Correct error and resubmit.
APS found a comma at the end of a DDI statement and the next READ found the end of file.
Correct the error and resubmit.
When processing the DDI statements, APS found a statement with a comma at the end and you did not continue the statement on the next line.
Correct error and resubmit.
Another job locked the DBD specified on the control card for update.
Resubmit the job.
While reading the DDI file, APS did not find the named DBD.
Ensure the DBD name on the DBD and DDI statements are the same. Check to see that the DBD named on the PSB is correct and check to see if you loaded the DBD in the DDI file. Then, resubmit the job.
While reading the DDI file, APS did not find the named PSB.
Ensure that you loaded the PSB into the DDI file. Resubmit the job.
When processing the DDI statements for the DBD, APS found a REC statement without a DBD statement before it.
Correct the input and resubmit the job.
APS found an invalid keyword in the DDI source. Valid keywords are:
Correct the input and resubmit the job.
When processing the DDI statements for a DBD, the SEG= parameter named a segment not found in the DBD.
Correct the input and resubmit.
When processing the DDI statements, APS found a FLD statement without a REC statement before it.
Correct the input and resubmit.
The IMSNAME keyword in the DDISRC must reference a DBDSRC NAME keyword defined in the segment being processed.
Correct the input and resubmit.
A nonblank character must be in column 72 for continuation or you must continue the next line in column 16.
Correct the input and resubmit.
While processing the DDI statements, APS found a FLD statement with an invalid parameter. Valid FLD parameters are:
Correct the input and resubmit.
While processing DDI statements for PCB-level DDI overrides, APS encountered a FLD statement without a IMSNAME= keyword or with spaces following IMSNAME=.
Correct the input and resubmit.
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.
Correct the input and resubmit.
While processing DDI statements for PCB-level DDI overrides, APS 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:
Correct the input and resubmit.
While processing DDI statements for a PCB-level override, APS 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:
Correct the input and resubmit.
When processing a PSB statement for DDI overrides, APS encountered a keyword other than NAME=. NAME= is the only valid keyword.
Correct the input and resubmit.
While processing a VSAM file definition, APS found an IDX statement for an ESDS or relative record file.
Correct and resubmit.
While processing a VSAM file definition, APS found a TYPE = parameter other than P for the primary IDX.
Correct statement and resubmit.
While executing one step in the PSBGEN utility, APS noticed the named PSB or subschema neither a DL/I nor VSAM type.
This is only a note; no response necessary. APS will continue processing.
While processing a DBD, APS found a duplicate COBOL name on the DDI statements. This prevents a COBOL program from compiling.
Create unique COBOL names through the DDI statements.
While processing a DBD, APS did not find a DDI statement specifying a COBOL name for the field.
This is an informational message. Processing will continue.
When processing *DDI statements, APS found a NAME= followed by a name greater than 30 characters in length. APS will truncate the name on the right to a length of 30.
Use a name of 30 characters or less.
When processing *DDI statements for VSAM, APS found a NAME=followed by a name greater than 30 characters in length. APS will truncate the name on the right to a length of 30.
Use a name of 30 characters or less.
PCB processed referenced a DBD for an IGNORE option.
Information item only; no user action required.
CREATE was unsuccessful for the entity named for reasons stated in prior error messages.
Correct the errors and resubmit.
On a cancel of a CREATE, a boundary violation occurred on the DDI file, probably due to lack of space.
Run the DDI unlock utility and increase the space on the DDI file.
An UPDATE was unsuccessful for the entity named for reasons stated in prior error messages.
Correct errors and resubmit.
On a cancel of an UPDATE, a boundary violation occurred on the DDI file, probably due to lack of space.
Run the DDI unlock utility and increase the space on the DDI file.
On a CREATE, a boundary violation occurred on the DDI file probably due to lack of space.
Run the DDI unlock utility and increase the space on the DDI file.
On an UPDATE, a boundary violation occurred on the DDI file, probably due to lack of space.
Run the DDI unlock utility and increase the space on the DDI file.
Symbol generation for the named PSB or subschema was unsuccessful for reasons stated in prior error messages.
Correct errors and resubmit.
Symbol generation for the PSB or subschema named was successful but APS issued warning messages in prior messages.
This is an informational message. No response necessary.
When processing the DDI statements, APS did not add information to the DDI file for reasons stated in prior error messages.
Correct the input and resubmit.
When attempting to add or update records on the DDI file, a VSAM error occurred.
Ensure there is enough space for the file. Run the DDI unlock utility and resubmit the job.
The CREATE of an entity on the DDI file was unsuccessful for reasons mentioned in prior error messages.
Correct the errors and resubmit.
The update of an entity on the DDI file was unsuccessful for reasons mentioned in prior error messages.
Correct the errors and resubmit.
APS found an invalid JCL parameter for reasons mentioned in prior error messages.
Correct errors and resubmit.
Copyright © 2002 Micro Focus International Limited. All rights reserved.
This document and the proprietary marks and names
used herein are protected by international law.