Error Codes and Messages › IMGR Messages

IMGR Messages

This section details messages generated by inventory management functions along with possible causes and corrective actions to take in error situations.

Note: The following messages, which indicate that no match is found and are documented in this section with an E suffix, can also appear with a W suffix: IMGR001W, IMGR005W, IMGR007W,IMGR009W, IMGR011W, and IMGR013W.

IMGR001E

NO ENVIRONMENTS MATCH environment name OR USER NOT AUTHORIZED TO USE THIS ENV

Reason:

Either the environment specified on the request does not exist, or the user making the request is not authorized to access the named environment.

Action:

Make sure that the environment was specified correctly. See your administrator if necessary to obtain access privileges.

IMGR002E

NO MAP INFO AVAILABLE WITH SEARCH=search type ON ENVIRON environment name STAGE stage id

Reason:

The environment and stage named in the message are not mapped to a subsequent environment or stage location.

Action:

Contact your administrator.

IMGR003E

"TO" LOCATION environment name/stage id IS INVALID FROM environment name/stage id

Reason:

The second environment name/stage pair named in the message is not a valid target location for the requested action.

Action:

Correct and resubmit the request, or see your administrator.

IMGR004E

environment name IS AN INVALID "TO" ENVIRONMENT FROM environment name

Reason:

The second environment named in the message is not a valid target environment for the first named environment.

Action:

Correct and resubmit the request, or see your administrator.

IMGR005E

NO SYSTEMS MATCH system name IN ENVIRONMENT environment name

Reason:

The system named in the message has not been defined to the environment named in the message.

Action:

Make sure that the system and environment names were specified correctly.

IMGR006E

UNKNOWN PROCESSOR TYPE processor type

Reason:

CA Endevor SCM does not recognize the processor type identified in the message.

Action:

Specify the processor type correctly.

IMGR007E

NO SUBSYSTEMS MATCH subsystem name IN SYSTEM system name

Reason:

The subsystem named in the message was not defined to the system named in the message.

Action:

Make sure that the subsystem and system names were specified correctly.

IMGR008E

NO SYMBOLICS FOR [GENERATE/DELETE/MOVE] PROCESSOR processor group name IN SYSTEM system name - STAGE stage id

Reason:

No symbolics were defined for the processor named in the message at the system and stage identified in the message.

Action:

Define the symbolics used in the processor to CA Endevor SCM, and resubmit the job.

IMGR009E

NO ELEMENT MATCH(ES) FOUND AT SPECIFIED LOCATION

Reason:

The element is not associated with the type at the specified stage.

Action:

Make sure that you have specified the element name correctly.

IMGR009W

NO ELEMENT MATCH(ES) FOUND AT SPECIFIED LOCATION

Reason:

Informational message. No elements were found that matched the criteria specified.

Action:

None.

IMGR011E

NO STAGES MATCH stage id IN ENVIRONMENT environment name

Reason:

The stage ID in the message is not associated with the environment named in the message.

Action:

Make sure that the stage and environment names were specified correctly.

IMGR012E

NO PROCESSOR GROUP MATCH group name FOR TYPE type name IN SYSTEM system name - STAGE stage id

Reason:

The processor group named in the message is not defined for the type named in the message at the system/stage identified in the message.

Action:

Make sure that you have specified the processor group name correctly.

IMGR013E

NO TYPES MATCH type name IN SYSTEM system name - STAGE stage id

Reason:

The type named in the message is not defined to the system/stage identified in the message.

Action:

Make sure that you have specified the type name correctly.

IMGR014E

NO TYPE ID MATCH id number IN SYSTEM system name - STAGE stage id

Reason:

The type ID named in the message is not defined to the system/stage identified in the message.

Action:

Contact your administrator.

IMGR015E

NO DATA SETS MATCH data set key IN SYSTEM system name - STAGE stage id

Reason:

Internal error.

Action:

Contact your administrator.

IMGR016E

TYPE SEQUENCE RECORD NOT DEFINED FOR SYSTEM system name - STAGE stage id

Reason:

No type sequence record was defined for the system and stage named in the message.

Action:

Define a type sequence record.

IMGR017E

field name NAME CONTAINS INVALID SYNTAX (OR INVALID FOR THE FUNCTION)

Reason:

The field named in the message contains invalid syntax.

Action:

Correct the syntax.

IMGR018E

NO APPROVER GROUPS MATCH approver group name IN ENVIRONMENT environment name

Reason:

The approver group named in the message is not defined to the environment named in the message.

Action:

Make sure that you have specified the approver group name correctly. Define the approver group if necessary.

IMGR019E

NO GROUP JUNCTIONS MATCH approver group relationship IN ENVIRONMENT environment name

Reason:

The approver group relationship named in the message is not defined to the environment named in the message.

Action:

Make sure that you have specified the approver group relationship correctly. Define the approver group relationship if necessary.

IMGR020E

NEXT LOCATION NOT FOUND FROM ENV environment name STG stage id

Reason:

There is no "next" location on the map for the named environment and stage.

Action:

Contact your administrator.

IMGR021E

NEXT SYSTEM LOCATION NOT FOUND FROM ENV environment name STG stage id SYS system name

Reason:

There is no "next" location on the map for the named environment, stage, and system.

Action:

Contact your administrator.

IMGR022E

NEXT SUBSYSTEM LOCATION NOT FOUND FROM ENV environment name STG stage id SYS system name SBS subsystem name

Reason:

There is no "next" location on the map for the named environment, stage, system, and subsystem.

Action:

Contact your administrator.

IMGR023E

NEXT TYPE LOCATION NOT FOUND FROM ENV environment name STG stage id SYS system name TYPE type name

Reason:

There is no "next" location on the map for the named environment, stage, system, and type name.

Action:

Contact your administrator.

IMGR024E

NO ELEMENTS FOUND AFTER ENV environment name STG stage id SYS system name SBS subsystem name TYPE type name

Reason:

CA Endevor SCM found no elements at any map location, beginning from and including the named location.

Action:

Contact your administrator.

IMGR025E

NO NEXT ENVIRONMENT IN MAP. FROM ENV is environment name

Reason:

The named environment is not mapped to another environment in the C1DEFLTS table.

Action:

Contact your administrator.

IMGR026E

NEXT TYPE LOCATION NOT FOUND FROM ENV environment name STG stage id SYS system name TYPE ID type id

Reason:

There is no "next" location on the map for the named environment, stage, system, and type ID.

Action:

Contact your administrator.

IMGR031E

SYS system name ROUTE INCOMPLETE BTWN environment 1/stage id 1 — environment 2/stage id 2

Reason:

The named system is not mapped to a system at the indicated target location.

Action:

Contact your administrator.

IMGR032E

SBS sub-system name ROUTE INCOMPLETE UNDER SYS system name BTWN environment 1/stage id 1 — environment 2/stage id 2

Reason:

The named subsystem is not mapped to a subsystem at the indicated target location.

Action:

Contact your administrator.

IMGR033E

TYPE type name ROUTE INCOMPLETE UNDER SYS system name BTWN environment 1/stage id 1 — environment 2/stage id 2

Reason:

The named type is not mapped to a type at the indicated target location.

Action:

Contact your administrator.

IMGR034E

PRG processor group name ROUTE INCOMPLETE UNDER SYS system name TYP type name BTWN environment 1/stage id 1 — environment 2/stage id 2

Reason:

The named processor group is not mapped to a processor group at the indicated target location.

Action:

Contact your administrator.

IMGR100E

RC=return code - reason code ALLOCATION ERROR ddname - data set name

Reason:

Internal error.

Action:

Contact your administrator.

IMGR101E

RC=return code VSAM READ ERROR - ON DDNAME ddname

Reason:

Internal error.

Action:

Contact your administrator.

IMGR200E

ENVIRONMENT environment name STAGE stage-name LOCATION INVALID.

Reason:

The request has been cancelled because unknown environment stage location was specified on request.

Action:

See accompanying error messages for a resolution.

IMGR201E

VSAM I/O ERROR ON IMR FUNCTION AGAINST DDNAME ddname, RC= return code FEEDBK= feedback code

Reason:

An I/O error occurred against the MCF file. The ddname in the above statement identifies the file. The VSAM return and feedback codes are also supplied on the message.

Action:

See the appropriate IBM VSAM manual first. Have all output available, for example JES spool files and dump information, before calling your administrator.

IMGR202E

CONSTRUCTION OF TAGGED FIELD OBJECT FAILED DURING BC1PIMGU INITIALIZATION

Reason:

Internal error. An error occurred while calling internal OBJECT initialization routines during BC1PIMGU initialization.

Action:

Resolve any accompanying error messages first. Gather related output, for example, JES spool file, logs, and dumps, before calling your administrator.

IMGR203E

SYSTEM system name ALREADY DEFINED IN ENV environment name STAGE ID stage id

Reason:

The request to create a system definition failed because the system record is already defined.

Action:

See accompanying error messages for a resolution.

IMGR204E

FIELD MAPPING BLOCKS COULD NOT BE BUILT DURING [junction/approvers/procgroup/subsystem/system/type]

Reason:

Internal error. BC1PIMGU called an internal OBJECT routine to create an FMB structure. This routine failed to process the request.

Action:

Resolve any accompanying error messages first. Gather related output, for example, JES spool file, logs, and dumps, before calling your administrator.

IMGR205E

TDF FIELD CODE X "error code" INVALID DURING [system/subsystem/type/appr_grp/appr_jun/proc_grp/proc_sym/data set] [create/delete/read/update]

Reason:

Internal error. Invalid tagged field code.

Action:

See accompanying error messages for a resolution.

IMGR206E

TDF FIELD CODE X "error code" MISSING DURING [system/subsystem/type/appr_grp/appr_jun/proc_grp/proc_sym/data set] [create/delete/read/update]

Reason:

Internal error. A required field was missing from the TFC chain.

Action:

See accompanying error messages for a resolution.

IMGR207E

TDF FIELD CODE X "error code" IS NOT APPLICABLE DURING [system/subsystem/type/appr_grp/appr_jun/proc_grp/proc_sym/data set] [create/delete/read/update]

Reason:

Internal error. Invalid tagged field code for this request.

Action:

See accompanying error messages for a resolution.

IMGR208E

TDF FIELD CODE X "error code" DUPLICATED DURING [system/subsystem/type/appr_grp/appr_jun/proc_grp/proc_sym/data set] [create/delete/read/update]

Reason:

Internal error. A duplicate field code was encountered on the TFC chain.

Action:

See accompanying error messages for a resolution.

IMGR209E

TDF FIELD CODE X "error code" EXCEEDED ITS OCCURRENCE DURING [system/subsystem/type/appr_grp/appr_jun/proc_grp/proc_sym/data set] [create/delete/read/update]

Reason:

Internal error. An occurring field code exceeded its maximum on the TFC chain.

Action:

See accompanying error messages for a resolution.

IMGR210E

SYSTEM system name DOES NOT EXIST IN ENV environment name STAGE ID stage id

Reason:

Request fails. System definition must exist for this environment/stage location.

Action:

See accompanying error messages for a resolution.

IMGR211E

TYPE RECORDS EXIST FOR SYSTEM system name IN ENV environment name STAGE ID stage id

Reason:

Request fails. Type definition records must not exist for this system at this environment/stage location.

Action:

See accompanying error messages for a resolution.

IMGR212E

SUBSYSTEM RECORDS EXIST FOR SYSTEM system name IN ENV environment name STAGE ID stage id

Reason:

Request fails. Subsystem records must not exist for this system at this environment/stage location.

Action:

See accompanying error messages for a resolution.

IMGR213E

SUBSYSTEM subsystem name EXISTS FOR SYSTEM system name IN ENV environment name STAGE ID stage id

Reason:

Request fails. This subsystem must not exist under this system at this environment/stage location.

Action:

See accompanying error messages for a resolution.

IMGR214E

SUBSYSTEM subsystem name DOES NOT EXIST FOR SYSTEM system name IN ENV environment name STAGE ID stage id

Reason:

Request fails. Subsystem must exist for this system at this environment/stage location.

Action:

See accompanying error messages for a resolution.

IMGR215E

ELEMENTS EXIST FOR SYSTEM system name SUBSYSTEM subsystem name IN ENV environment name STAGE ID stage id

Reason:

Request fails. For this request, elements must not exist for this system/subsystem at this environment/stage location.

Action:

See accompanying error messages for a resolution.

IMGR216E

SYSTEM system name WAS NOT UPDATED DURING INVENTORY CHANGE ON DDNAME ddname, RC= return code FEEDBK= feedback code

Reason:

VSAM I/O error occurred while updating the system record timestamp field. This user request most likely completed. The user must resolve the problem which caused the system record update to fail.

Action:

See the appropriate IBM VSAM manual first. Have all output available, for example, JES spool files and dump information, before calling your administrator.

IMGR217E

TYPE type name ALREADY EXISTS FOR SYSTEM system name IN ENV environment name STAGE ID stage id

Reason:

Request fails. Type already defined for this system under this environment/stage location.

Action:

See accompanying error messages for a resolution.

IMGR218E

TYPE SEQUENCE RECORD FOR SYSTEM system name IN ENV environment name STAGE ID stage id NOT FOUND

Reason:

The type sequence record is always created at the time the system record is defined. This request fails when this condition occurs. Try deleting the system record, and if this is possible, recreate it.

Action:

Resolve any accompanying error messages first. Gather related output, for example, JES spool file, logs, and dumps, before calling your administrator.

IMGR219E

MAXIMUM OF 256 TYPE RECORDS ALREADY DEFINED FOR SYSTEM system name IN ENV environment name STAGE ID stage id

Reason:

Request fails. This is an internal limitation. Only 256 type definition records may exist per system.

Action:

See accompanying error messages for a resolution.

IMGR220E

TYPE SEQUENCE SLOT FOR SYSTEM system, DESIGNATED FOR TYPE type name UPDATE, CONTAINED INVALID DATA

Reason:

Request fails. Invalid data was found within the type sequence record where the type ID slot was assigned for the type during a create type request.

Action:

Resolve any accompanying error messages first. Gather related output, for example, JES spool file, logs, and dumps, before calling your administrator.

IMGR221E

MAXIMUM OF 256 DATA SETS ALREADY DEFINED FOR SYSTEM system IN ENV environment name STAGE ID stage id

Reason:

Request fails. This is an internal limitation. Only 256 data sets may be defined per system.

Action:

See accompanying error messages for a resolution.

IMGR222E

TYPE type name NOT DEFINED FOR SYSTEM system name IN ENV environment name STAGE ID stage id

Reason:

Request fails. The type definition must exist for this system under this environment/stage location.

Action:

See accompanying error messages for a resolution.

IMGR223E

processor name PROCESSOR RECORD WRITE FAILURE ON DDNAME ddname, RC= return code FEEDBK= feedback code

Reason:

VSAM I/O error occurred while writing this processor record to the MCF which is identified by the DDname value in the above message. The VSAM return code and feedback values are returned.

Action:

See the appropriate IBM VSAM manual first. Have all output available, for example, JES spool files and dump information, before calling your administrator.

IMGR224E

ELEMENTS EXIST FOR SYSTEM system name TYPE type name IN ENV environment name STAGE ID stage id

Reason:

Request fails. Elements must not exist for this system and type under this environment/stage location.

Action:

See accompanying error messages for a resolution.

IMGR225E

TYPE SEQUENCE SLOT FOR SYSTEM system name, DESIGNATED FOR TYPE type name, WAS NOT FOUND

Reason:

Request fails. During a delete type request, the type sequence record did not contain the type record id.

Action:

Resolve any accompanying error messages first. Gather related output, for example, JES spool file, logs, and dumps, before calling your administrator.

IMGR226E

STAGE 1 INFORMATION ACCESS FOR ENVIRONMENT environment name FAILED WITH A NOTFOUND CONDITION

Reason:

Stage 1 of this location could not be located. If this message occurs during a delete type request, the action is incomplete. The junction record deletion logic is not done and the system record timestamp update count logic is also not done.

Action:

Resolve any accompanying error messages first. Gather related output, for example, JES spool file, logs, and dumps, before calling your administrator.

IMGR227E

APPROVER JUNCTION INVENTORY NOT ON MCF FOR ENV environment name

Reason:

Request fails. The approver junction inventory for this environment was not defined on the MCF.

Action:

See accompanying error messages for a resolution.

IMGR228E

APPROVER GROUP approver group name NOT DEFINED FOR JUNCTION INVENTORY IN ENV environment name

Reason:

Request fails. A junction record with this approver group was not defined on the MCF.

Action:

See accompanying error messages for a resolution.

IMGR229E

JUNCTION FOR APPROVER GROUP ALREADY DEFINED IN ENV environment name

Reason:

Request fails. The junction inventory definition was already defined for the requested approver group.

Action:

See accompanying error messages for a resolution.

IMGR230E

MAXIMUM OF 256 JUNCTION RECORDS FOR THE SAME INVENTORY IS ALREADY DEFINED

Reason:

Request fails. This is an internal limitation. Only 256 junction definitions having the same inventory may be defined per environment.

Action:

See accompanying error messages for a resolution.

IMGR231E

APPROVER GROUP approver group name NOT DEFINED FOR ENVIRONMENT environment name

Reason:

Request fails. The specified approver group is not defined for this environment.

Action:

See accompanying error messages for a resolution.

IMGR232E

APPROVER GROUP approver group name ALREADY DEFINED FOR ENVIRONMENT environment name

Reason:

Request fails. The specified approver group is already defined for this environment.

Action:

See accompanying error messages for a resolution.

IMGR233E

TYPE SEQUENCE NOT DEFINED FOR SYSTEM system name IN ENV environment name STAGE ID stage id

Reason:

Request fails. During a type sequence update or read request, the type sequence record was not found for this system under this environment/stage location.

Action:

Resolve any accompanying error messages first. Gather related output, for example, JES spool file, logs, and dumps, before calling your administrator.

IMGR234E

TFC COULD NOT BE BUILT DURING symbols/typeseq read

Reason:

Internal error. BC1PIMGU called an internal OBJECT routine to create a tagged field collection block (TFC). This routine failed to process the request.

Action:

Resolve any accompanying error messages first. Gather related output, for example, JES spool file, logs, and dumps, before calling your administrator.

IMGR235E

TDF COULD NOT BE BUILT DURING symbols/typeseq read

Reason:

Internal error. BC1PIMGU called an internal OBJECT routine to create a tagged data field block (TDF). This routine failed to process the request.

Action:

Resolve any accompanying error messages first. Gather related output, for example, JES spool file, logs, and dumps, before calling your administrator.

IMGR236E

NO TYPES WERE FOUND FOR SYSTEM system name IN ENV environment name STAGE ID stage id

Reason:

Request fails. During a type sequence update request, no type records were found for this system. The requester type count indicated that type records should be defined for this system under this environment/stage location.

Action:

Resolve any accompanying error messages first. Gather related output, for example, JES spool file, logs, and dumps, before calling your administrator.

IMGR237E

PROCESSOR GROUP processor group name ALREADY DEFINED FOR SYSTEM system name TYPE type name

Reason:

Request fails. The processor group is already defined for this system and type.

Action:

See accompanying error messages for a resolution.

IMGR238E

PROCESSOR GROUP processor group name NOT DEFINED FOR SYSTEM system name TYPE type name

Reason:

Request fails. The specified processor group is not defined for the system and type.

Action:

See accompanying error messages for a resolution.

IMGR239E

ELEMENTS EXIST WHICH USE PROCESSOR GROUP processor group name

Reason:

Request fails. Elements still exist that use this processor group.

Action:

See accompanying error messages for a resolution.

IMGR240E

UNKNOWN PROCESSOR TYPE X "processor type value" FROM CALLER

Reason:

Request fails. The caller specified an invalid processor type. The processor type should be one of the following: x&rq.01&rq., x&rq.02&rq. or x&rq.03&rq..

Action:

See accompanying error messages for a resolution.

IMGR241E

NO MATCHING DATA FOR SYMBOL symbol name IN TDF CHAIN.

Reason:

Request fails. Caller did not provide override data for the symbolic name anywhere in the tagged data field (TDF) chain.

Action:

See accompanying error messages for a resolution.

IMGR242E

PROCESSOR NAME WITHIN THE TDF CHAIN IS NOT DEFINED WITHIN GROUP group name

Reason:

Request fails. The Processor name specified within the caller tagged data field (TDF) chain is not defined within this processor group.

Action:

See accompanying error messages for a resolution.

IMGR243E

REQUIRED TDF ENTRY entry name MISSING FROM CHAIN

Reason:

Request fails. The caller failed to include this required tagged data field (TDF) entry within the TFC chain.

Action:

See accompanying error messages for a resolution.

IMGR244E

CATALOGUE SEGMENT WAS NOT FOUND FOR ELEMENT TYPE

Reason:

The catalogue segment does not exist for this element or type.

Action:

Contact your administrator.

IMGR245E

NO MATCH IN MCF DDN ddname FOR CATAL ENTRY: catalog-key

Reason:

Internal error. Sync error between the master control file and the catalog.

Action:

Contact your administrator.

IMGR246E

CATALOGUE SEGMENT ALREADY EXISTS FOR ELEMENT TYPE

Reason:

The catalogue segment already exists for this element or type.

Action:

Contact your administrator.

IMGR247E

$IMR REQUEST FAILED, $IMR ERROR MESSAGE FOLLOWS

Reason:

Internal error. The $IMR request failed. Review the other messages to determine the reason.

Action:

Contact your administrator.

IMGR248I

ELEMENT ENTRY FOR LOCATION ALREADY EXISTS, A CATALOGUE UPDATE WILL BE PERFORMED

Reason:

Informational message. A catalogue entry already exists for this element or type. The entry will be updated.

Action:

None.

IMGR249I

ELEMENT ENTRY FOR LOCATION DOES NOT EXIST, A CATALOGUE ADD WILL BE PERFORMED

Reason:

Informational message. A catalogue entry does not exist for this element or type. The entry will be created.

Action:

None.

IMGR250E

SECOND ATTEMPT TO RECORD IN CATALOGUE FAILED: inventory location

Reason:

A previous Update action failed with a segment not found condition. An Add action with Update was attempted, which also failed.

Action:

Contact your administrator.

IMGR251E

LOOP DETECTED WHILE TRYING TO GENERATE AN ALIAS ELEMENT NAME

Reason:

CA Endevor SCM generated an alias for an element. The alias already exists as an element.

Action:

Contact your administrator.

IMGR252E

INVALID CATALOGUE RECORDS FOUND FOR THIS ELEMENT

Reason:

Internal error. A catalogue record exists for this element or type, but the data found in the record is invalid.

Action:

Contact your administrator.

IMGR253E

SEGMENT FOUND WITH INVALID INVENTORY inventory location

Reason:

An invalid catalog segment was found for this element.

Action:

Contact your administrator.

IMGR254E

SEGMENT FOUND WITH INVALID ENVIRONMENT environment name SYSTEM system name

Reason:

An invalid catalog segment was found for this element.

Action:

Contact your administrator.

IMGR255C

REG. ERROR: ELM EXISTS W/SAME PROC GRP O/P TYPE (processor group output type) AT LOC environment/stage - system/subsystem/type

Reason:

Registration error. A duplicate element was found within the same processor group output type. This is a caution message and processing continues.

Action:

None.

IMGR255E

REG. ERROR: ELM EXISTS W/SAME PROC GRP O/P TYPE (processor group output type) AT LOC environment/stage - system/subsystem/type

Reason:

Registration error. A duplicate element was found within the same processor group output type.

Action:

Duplicates are not allowed. Change the element name or processor group output type.

IMGR255W

REG. ERROR: ELM EXISTS W/SAME PROC GRP O/P TYPE (processor group output type) AT LOC environment/stage - system/subsystem/type

Reason:

Registration error. A duplicate element was found within the same processor group output type. This is a warning message and processing continues.

Action:

None.

IMGR256E

PROCESSOR GROUP xx FOR ENV environment STG stage SYS system TYPE type DOES NOT EXIST

Reason:

This processor group does not exist within this inventory location.

Action:

Verify that the processor group name is correct. If so, make sure the processor group is properly defined.

IMGR257C

REG. ERROR: ELEMENT NAME ALREADY EXISTS AT environment/stage - system/subsystem

Reason:

Registration error. A duplicate element was found in a non-mapped location. This caution message is issued and processing continues.

Action:

None.

IMGR257E

REG. ERROR: ELEMENT NAME ALREADY EXISTS AT environment/stage - system/subsystem

Reason:

Registration error. A duplicate element found in a non-mapped location.

Action:

Duplicates are not allowed. Change the element name.

IMGR257W

REG. ERROR: ELEMENT NAME ALREADY EXISTS AT environment/stage - system/subsystem

Reason:

Registration error. A duplicate element was found in a non-mapped location. This warning message is issued and processing continues.

Action:

None.

IMGR258E

ELM EXTENSION RECORD element extension record key NOT FOUND IN ENV env STGID stage id

Reason:

An element extension record was not found within this directory location.

Action:

Contact your administrator.

IMGR259E

REQUIRED ELEMENT RECORD PARAMETER MISSING FROM ELEMENT EXTENSION QUERY CALL

Reason:

The parameter list passed to the element extension subroutine must contain the address of the element record. This parameter is invalid.

Action:

Contact your administrator.

IMGR260E

INVALID EXTENSION DATA FOUND IN ELEMENT AT inventory location

Reason:

An element extension record was found, but the data is invalid.

Action:

Contact your administrator.

IMGR261E

INVALID EXTENSION TYPE PARAMETER SPECIFIED ON THE ELEMENT EXTENSION CALL

Reason:

Internal error. The first parameter on the call to the element extension subroutine is the extension type. The value specified is invalid.

Action:

Contact your administrator.

IMGR900E

TRUNC OCCURRED WHILE MOVING RECORD TYPE type id TO BUFFER - CALL ENDEVOR TECHNICAL SUPPORT

Reason:

An internal error occurred.

Action:

Contact your administrator.

IMGR901E

INVALID PARAMETER LIST RECEIVED - CALL ENDEVOR TECHNICAL SUPPORT

Reason:

An internal error occurred.

Action:

Contact your administrator.

IMGR902E

STORAGE UNAVAILABLE TO PROCESS REQUEST - CALL ENDEVOR TECHNICAL SUPPORT

Reason:

An internal error occurred.

Action:

Contact your administrator.