The remainder of this appendix lists and describes error messages that are generated during macro assembly.
Note: For error messages generated by the DML precompiler and returned to the ERRSTAT field of the IDMS communications block following DML requests, see the Messages and Codes Guide.
@ACCEPT
INDECIPHERABLE COMBINATION OF OPERANDS
Excessive or conflicting operands prevent interpretation of the macro.
Severity: 08
@BIND
LRC MUST BE SPECIFIED OR LRSIZ MUST BE OMITTED
The LRC parameter was omitted but the LRSIZ parameter was specified. If the LRSIZ parameter is specified, the LRC parameter must also be specified.
Severity: 08
INDECIPHERABLE COMBINATION OF OPERANDS
Excessive or conflicting operands prevent interpretation of the macro.
Severity: 08
TOO MANY OPERANDS SPECIFIED
Parameters were specified that are not allowed for the BIND statement being issued.
Severity: 08
@COMMIT
'ALL' PARAMETER MUST BE BLANK OR 'ALL'
The first positional parameter ALL must be specified as ALL or must be omitted.
Severity: 08
@CONNECT
BOTH RECORD NAME AND SET NAME ARE REQUIRED FOR CONNECT
Either the REC or SET parameter was omitted.
Severity: 08
@DISCON
BOTH RECORD NAME AND SET NAME ARE REQUIRED FOR DISCONNECT
Either the REC or SET parameter was omitted.
Severity: 08
@ERASE
TYPE OF ERASE IS MISSING OR INCORRECT
The (required) parameter for type of erase was omitted or invalid. Valid parameters are REC, PERMANENT, SELECTIVE, or ALL.
Severity: 08
RECORD NAME IS REQUIRED FOR ERASE
The required REC parameter was not specified.
Severity: 08
@FIND
TYPE OPERAND IS MISSING OR INVALID
This type of FIND/OBTAIN was not specified (NEXT, FIRST, PRIOR, LAST, NTH).
Severity: 08
SET,AREA, USING, AND OCCUR ARE NOT ALLOWED FOR FORMAT 1
SET, AREA, USING, or OCCUR parameters were specified. These parameters are not allowed on FIND DBKEY statements.
Severity: 08
DBKEY, USING, AND OCCUR ARE NOT ALLOWED FOR FORMAT 2
DBKEY, USING, or OCCUR parameters were specified. These parameters are not allowed on FIND CURRENT statements.
Severity: 08
REC, SET, AND AREA ARE MUTUALLY EXCLUSIVE FOR FORMAT 2
Two or more of the REC, SET, or AREA parameters were specified. Only one of these parameters can be specified on FIND CURRENT statements.
Severity: 08
DBKEY AND USING ARE NOT ALLOWED FOR FORMAT 3
Either a DBKEY or a USING parameter was specified. These parameters are not allowed on FIND WITHIN SET/AREA statements.
Severity: 08
EITHER SET OR AREA MUST BE SPECIFIED
Neither SET nor AREA parameters were specified; one of these parameters must be specified.
Severity: 08
OCCUR IS USED ONLY WITH FORMAT 3 FIND NTH
OCCUR parameters were specified. These parameters are only allowed with FIND NTH WITHIN SET/AREA statements.
Severity: 08
REC, AREA, DBKEY, USING, AND OCCUR NOT ALLOWED FOR FORMAT 4
REC, AREA, DBKEY, USING, or OCCUR parameters were specified. These parameters are not allowed on FIND OWNER statements.
Severity: 08
SET OPERAND IS REQUIRED FOR FORMAT 4
The required SET parameter was not specified on a FIND OWNER statement.
Severity: 08
SET, AREA, DBKEY, USING, AND OCCUR ARE NOT ALLOWED FOR FORMAT 5
SET, AREA, DBKEY, USING, or OCCUR parameters were specified. These parameters are not allowed on FIND CALC/DUPLICATE statements.
Severity: 08
REC OPERAND IS REQUIRED FOR FORMAT 5
The required REC parameter was not specified on a FIND CALC/DUPLICATE statement.
Severity: 08
AREA, DBKEY, AND OCCUR ARE NOT ALLOWED FOR FORMAT 6
AREA, DBKEY, or OCCUR parameters were specified and are not allowed for FIND WITHIN SET USING SORT KEY statements.
Severity: 08
REC, SET, AND USING ARE REQUIRED FOR FORMAT 6
REC, SET, or USING parameters were not specified and are required for FIND WITHIN SET USING SORT KEY statements.
Severity: 08
KEEP OPERAND NOT SPECIFIED AS SHARED OR EXCLUSIVE
The KEEP parameter was specified without either the SHARED or EXCLUSIVE parameter.
Severity: 08
UNEXPECTED ERROR IN FORMAT 3 FIND
This is a system internal error.
Severity: 20
@IDMSINR
@MODE MACRO DOES NOT PRECEDE THIS DML MACRO
The @MODE macro was not specified before this macro. The @MODE macro must precede all other macros and must occur only once.
Severity: 16
@MODE CONTAINED ERRORS, OR WAS NOT FIRST MACRO
The @MODE macro was coded incorrectly or was not specified before this macro. The @MODE macro must precede all other macros and must occur only once.
Severity: 16
INVALID TYPE 'type' SPECIFIED IN @IDMSINR MACRO
This is a system internal error.
Severity: 20
INVALID OPERAND 'operand' IN @IDMSINR MACRO DML-SEQUENCE = 9999
This is a system internal error.
Severity: 20
INVALID MODE 'mode' IN @IDMSINR MACRO
This is a system error.
Severity: 20
@IF
INVALID SPECIFICATION FOR MEMBER OPERAND OR EMPTY OPERAND
The MEMBER/EMPTY parameter was specified incorrectly. Either MEMBER or EMPTY must be specified.
Severity: 08
SET, GOTO, AND EITHER MEMBER OR EMPTY ARE REQUIRED FOR IF
A required MEMBER or EMPTY, SET, or GOTO parameter was not specified. SET, GOTO and either MEMBER or EMPTY parameters are required in an IF statement.
Severity: 08
@KEEP
TYPE NEITHER SHARED NOR EXCLUSIVE
Either the SHARED or EXCLUSIVE parameter is required on KEEP statements.
Severity: 08
INDECIPHERABLE COMBINATION OF OPERANDS
Excessive or conflicting operands prevent interpretation of the macro.
Severity: 08
@LRF
Key-value MISPLACED
The named key-value parameter was coded in an incorrect position. Parameters must be coded in the following sequence: FIRST/NEXT, REC, IOAREA, ONLRSTS, GOTO, and WHERE.
Severity: 08
KEY-value,variable-value MISPLACED
The named positional pair of parameters was coded more than once or in incorrect sequence within a logical-record DML statement. Parameters must be coded in the following sequence: FIRST/NEXT, REC, IOAREA, ONLRSTS, GOTO, and WHERE.
Severity: 08
KEYWORD PARAMETERS INVALID FOR LRF ACCESS MACROS
Logical-record DML statements must be coded using positional-pair parameter notation at assembly time.
Severity: 08
Key-value NOT PAIRED
The named key-value positional parameter was coded without a corresponding variable value parameter.
Severity: 08
Key-value IS AN INVALID PARAMETER
The named key-value parameter is invalid. Valid key-value parameters in logical-record DML statements are: FIRST/NEXT, REC, IOAREA, ONLRSTS, GOTO and WHERE.
Severity: 08
"REC" MUST BE SPECIFIED
The REC parameter was not specified on a logical record request. All LRF access macros must specify a logical record name.
Severity: 08
"WHERE" INVALID WHEN LRSIZ OMITTED ON @BIND
The LRSIZ parameter (specified on @BIND SUBSCH) was not specified; therefore, no storage was made available for WHERE clause resolution. Add the LRSIZ parameter to @BIND SUBSCH and reassemble.
Severity: 08
SPECIFY BOTH "ONLRSTS" AND "GOTO" OR NEITHER
Either the ONLRSTS or the GOTO parameter was omitted from a logical record request; both parameters are needed to encode a DMLA ON clause. Either remove the parameter specified or add the omitted parameter.
Severity: 08
MACRO ERROR: PASSED VERB verb
The named verb was incorrectly passed. This is a system internal error.
Severity: 08
@MODE
MULTIPLE OCCURRENCES OF @MODE MACRO
The @MODE macro was specified more than one time; the @MODE macro must occur only once.
Severity: 08
INVALID SPECIFICATION mode FOR MODE OPERAND
The named mode is not valid. Valid mode parameters are BATCH, CICS, CICS-EXEC, IDMSDC, INTERCOMM, SHADOW, and DCBATCH.
Severity: 16
INVALID SPECIFICATION debug FOR DEBUG OPERAND
The named debug parameter is not valid. Valid debug parameters are YES or NO.
Severity: 16
INVALID SPECIFICATION quotes FOR QUOTES OPERAND
The named quotes parameter is invalid. Valid parameters for quotes are YES or NO.
Severity: 16
@MODIFY
RECORD NAME IS REQUIRED FOR MODIFY
The record REC parameter was not specified.
Severity: 08
@OBTAIN
KEEP OPERAND NOT SPECIFIED AS SHARED OR EXCLUSIVE
The KEEP parameter was specified without either the SHARED or EXCLUSIVE parameter. If the KEEP parameter is specified, either SHARED or EXCLUSIVE must also be specified.
Severity: 08
@PXE
LRPXE 9999 CHARACTERS TOO SHORT
Lrc-block-size (specified on @BIND SUBSCH) is too small to contain the specified WHERE clause. Increase lrc-block-size and reassemble.
Severity: 08
DMLA/@PXE INCONSISTENCY: PXE TYPE=type
This is a system internal error.
Severity: 12
DMLA/@PXE INCONSISTENCY: V-TYPE=type
This is a system internal error.
Severity: 12
DMLA/@PXE INCONSISTENCY: MAX=9999/9999
This is a system internal error.
Severity: 12
DMLA/@PXE INCONSISTENCY: LEN=9999/9999
This is a system internal error.
Severity: 12
@READY
EITHER AREA OPERAND OR ALL OPERAND MUST BE SPECIFIED
Neither the AREA nor ALL parameter was specified. One of these parameters is required for this macro.
Severity: 08
EITHER RDONLY OPERAND OR UPDATE OPERAND MUST BE SPECIFIED
Neither the RDONLY nor UPDATE parameter was specified. One of these parameters is required for this macro.
Severity: 08
INVALID SPECIFICATION FOR UPDATE OR RDONLY OPERAND
The UPDATE/RDONLY parameter was specified incorrectly. Valid parameters for UPDATE/RDONLY are: YES or SHARED, PROTECTED or PROTECT, or EXCLUSIVE.
Severity: 08
ALL OPERAND IS NOT SPECIFIED AS 'ALL'
The parameter ALL must be specified as ALL.
Severity: 08
@RETURN
BOTH SET AND DBKEY ARE REQUIRED OPERANDS FOR RETURN
The SET and/or DBKEY parameters were not specified. Both of these parameters are required for this macro.
Severity: 08
EITHER TYPE OPERAND OR USING OPERAND MUST BE SPECIFIED
Neither the type-of-return parameter (i.e., CURRENT, FIRST, LAST, NEXT, or PRIOR) nor the USING parameter was specified. RETURN macros must include one of these parameters.
Severity: 08
INVALID SPECIFICATION FOR TYPE OPERAND
The type operand was not specified correctly. Valid parameters are CURRENT, FIRST, LAST, NEXT, or PRIOR.
Severity: 08
@ROLLBAK
POSITIONAL PARAMETER 'CONTINUE' INVALID
The CONTINUE parameter must be specified as CONTINUE or must be omitted.
Severity: 08
@STORE
RECORD NAME IS REQUIRED FOR STORE
The required REC parameter was not specified.
Severity: 08
|
Copyright © 2014 CA.
All rights reserved.
|
|