220001

'EJECT' NOT ALONE ON CARD. TOKEN ASSUMED.

EJECT must appear as the only entry on the card unless it is to be used as other that a compiler directive.

Severity: W

220002

INVALID 'SPACE' COMMAND PARAMETER.

SPACE must be followed by a blank and, optionally, a 1-digit number greater than 0 indicating the number of lines to be spaced.

Severity: W

220003

'SPACE' NOT ALONE ON CARD. TOKEN ASSUMED.

SPACE must appear as the only entry on the card unless it is to be used as other than a compiler directive.

Severity: W

220004

SEQUENCE ERROR. RUN ABORTED.

Input was out of sequence.

Severity: F

220005

STRING EXCEEDS MAXIMUM OR AVAILABLE LENGTH.

The specified string exceeds the maximum allowable length for this parameter.

Severity: E

220006

HEX STRING EXCEEDS MAXIMUM OR AVAILABLE LENGTH.

The specified hex string exceeds the maximum allowable length for this parameter.

Severity: E

220007

HEX STRING CONTAINS INVALID CHARACTERS.

The specified hex string contains invalid hexadecimal characters.

Severity: E

220008

Ictl-parameter INVALID ICTL PARAMETER SPECIFICATION.

The ICTL parameter was incorrectly specified. Check the syntax. (IPSB compiler)

Severity: E

220009

Octl-parameter INVALID OCTL PARAMETER SPECIFICATION.

The OCTL parameter was incorrectly specified. Check the syntax. (IPSB compiler)

Severity: E

220010

Iseq-parameter INVALID ISEQ PARAMETER SPECIFICATION.

The ISEQ parameter was incorrectly specified. Check the syntax. (IPSB compiler)

Severity: E

220011

Core-size-parameter INVALID COMPILER TABLE SIZE SPECIFICATION.

The core-size parameter must be a 1- to 6-digit number optionally followed by a K. There must be at least one space between the number and the K. (IPSB compiler)

Severity: F

220012

Parameter UNEXPECTED END OF FILE (PERIOD MISSING).

Invalid syntax has been encountered. Check for missing periods. (IPSB compiler)

Severity: E

220013

Keyword UNKNOWN KEYWORD FOR STATEMENT TYPE.

The keyword encountered is not valid for the current statement type. (IPSB compiler)

Severity: E

220014

UNEXPECTED END OF FILE SEARCHING FOR STATEMENT.

End of file occurred before sufficient control input was found.

Severity: E

220015

Keyword INVALID STATEMENT TYPE. SKIPPING TO NEXT PERIOD.

The statement encountered is not valid for the current section. (IPSB compiler)

Severity: E

220016

Ipsb-name MISSING OR INVALID IPSB NAME.

The IPSB name must be a 1-to 8-character alphanumeric string. (IPSB compiler)

Severity: E

220017

Subschema-name MISSING OR INVALID SUBSCHEMA NAME.

The subschema name must be a 1- to 8-character alphanumeric string. (IPSB compiler)

Severity: F

220018

Language-parameter INVALID PROGRAM LANGUAGE SPECIFICATION.

Language must be COBOL, PL/I, or Assembler. (IPSB compiler)

Severity: E

220019

Subschema-name SUBSCHEMA NOT FOUND IN LOAD LIBRARY.

The subschema named could not be found. (IPSB compiler)

Severity: F

220020

Subschema-name ERROR LOADING SUBSCHEMA MODULE.

The subschema named could not be loaded. (IPSB compiler)

Severity: F

220021

INSUFFICIENT STORAGE FOR COMPILATION.

The IPSB compiler has run out of an internal work space. Contact technical support. (IPSB compiler)

Severity: F

220022

Subschema-name LOADED SUBSCHEMA MODULE INVALID.

The subschema named was used to load a module, but the module is not a valid subschema. (IPSB compiler)

Severity: F

220023

Parameter-name DIAGNOSTIC TABLE SIZE EXCEEDED. TOO MANY ERRORS.

Too many errors have occurred, causing an overflow of the table. Correct the previous errors. (IPSB compiler)

Severity: F

220025

Keyword INVALID KEYWORD, SKIPPING TO NEXT PERIOD.

The keyword encountered is not valid. Compilation resumes with the next statement. (IPSB compiler)

Severity: E

220026

MISSING KEYWORD, SKIPPING TO NEXT PERIOD.

A required keyword is missing. compilation resumes with the next statement.

220027

Parameter INVALID, PARAMETER TOO LONG.

The character string specified is greater in length than the maximum allowed for this parameter. (IPSB compiler)

Severity: E

220031

Area-name INVALID AREA NAME.

The character string as specified is not a valid area name. (IPSB compiler)

Severity: E

220032

Area-name AREA NOT DEFINED IN SUBSCHEMA.

All areas used in an IPSB must be defined in the subschema previously specified in the IPSB statement. (IPSB compiler)

Severity: E

220033

Usage-mode INVALID USAGE-MODE, SHARED RETRIEVAL ASSUMED.

The usage mode as specified is incorrect. Check the syntax. (IPSB compiler)

Severity: W

220034

Area-name AREA HAS BEEN PREVIOUSLY SPECIFIED.

An area name can be used in only one AREA statement. (IPSB compiler)

Severity: E

220035

Record-name INVALID RECORD NAME.

A record name must be a 1- to 16-character alphanumeric string. (IPSB compiler)

Severity: E

220036

Option INVALID DELETE OPTION, ERASE ALL ASSUMED.

The DELETE option was specified incorrectly. Check the syntax. (IPSB compiler)

Severity: W

220037

Field-name INVALID FIELD NAME.

A field name must be a 1- to 8-character alphanumeric string. (IPSB compiler)

Severity: E

220038

Stored-option INVALID, STORED PHYSICALLY ASSUMED.

The stored option was specified incorrectly. Check the syntax. (IPSB compiler)

Severity: W

220039

Position INVALID/MISSING STARTING POSITION.

The starting position must be a 1- to 5-digit number, greater than 1, and less than the record-length - 1. (IPSB compiler)

Severity: E

220040

Length INVALID/MISSING LENGTH SPECIFICATION.

The length must be a 1- to 5-digit number that indicates the length of the field. (IPSB compiler)

Severity: E

220041

Usage INVALID USAGE, DISPLAY ASSUMED.

The usage has been specified incorrectly. Check the syntax. (IPSB compiler)

Severity: W

220042

Record-name RECORD HAS BEEN PREVIOUSLY SPECIFIED.

A record name can appear in only one RECORD statement. (IPSB compiler)

Severity: E

220043

Record-name RECORD NOT DEFINED IN SUBSCHEMA.

The record named must be defined in the subschema previously specified in the IPSB statement. (IPSB compiler)

Severity: E

220044

Field-name FIELD HAS BEEN PREVIOUSLY SPECIFIED.

A field name must be unique within any one record definition. (IPSB compiler)

Severity: E

220045

Start-position STARTING POSITION INVALID IF STORED VIRTUALLY.

Starting position must not be specified if the field is stored virtually. This clause is ignored. (IPSB compiler)

Severity: W

220046

Record-name PREVIOUS RECORD HAS ONLY ONE CONCATENATED KEY.

The record preceding the current record has only one destination parent concatenated key defined. This can cause abnormal termination at run time. (IPSB compiler)

Severity: E

220047

Key-name LOGICAL CONCATENATED KEY PREVIOUSLY DEFINED.

Only one logical destination parent concatenated key field can be defined within any one record. (IPSB compiler)

Severity: E

220048

Key-name PHYSICAL CONCATENATED KEY PREVIOUSLY DEFINED.

Only one physical destination parent concatenated key field can be defined within any one record. (IPSB compiler)

Severity: E

220049

Parameter LENGTH OR STARTING POSITION INVALID FOR /SX.

Length and/or starting position must not be specified for /SX fields. (IPSB compiler)

Severity: W

220050

Field-name INVALID INDEXED FIELD NAME.

An indexed field name must be a 1- to 8-character alphanumeric string. (IPSB compiler)

Severity: E

220052

Record-name INVALID/MISSING TARGET RECORD.

If present, the target record as specified is not a valid record name. (IPSB compiler)

Severity: E

220053

Record-name INVALID/MISSING SOURCE RECORD.

If present, the source record as specified is not a valid record name. (IPSB compiler)

Severity: E

220054

Record-name INVALID/MISSING POINTER RECORD.

If present, the pointer record as specified is not a valid record name. (IPSB compiler)

Severity: E

220055

Constant INVALID SHARED INDEX CONSTANT.

The shared index constant must be a 1-byte, self- defining Assembler constant enclosed in double quotes. (IPSB compiler)

Severity: E

220056

Field-name MISSING SEARCH FIELD(S).

At least one field must be specified as a search field. (IPSB compiler)

Severity: E

220057

Field-name INVALID FIELD(S) SPECIFICATION.

A field name has been specified incorrectly. Check the syntax. (IPSB compiler)

Severity: E

220058

Value INVALID NULL INDEX VALUE.

The null index value must be a 1-byte, self-defining Assembler constant enclosed in double quotes, or BLANK or ZERO. (IPSB compiler)

Severity: E

220059

Index-name INDEX HAS BEEN PREVIOUSLY SPECIFIED.

An index name can be used in only one INDEX statement. (IPSB compiler)

Severity: E

220061

Record-name RECORD NOT DEFINED IN RECORD SECTION.

The record named must be defined by a RECORD statement in the RECORD SECTION. (IPSB compiler)

Severity: E

220062

Field-name FIELD NOT DEFINED IN SOURCE RECORD.

The field named must be defined within the source record definition in the RECORD SECTION. (IPSB compiler)

Severity: E

220063

Record-name NO SEQUENCE FIELD DEFINED FOR POINTER RECORD.

All pointer records must have a sequence field defined corresponding to the sort-key field of the indexed set of which it is a member. (IPSB compiler)

Severity: E

220064

Length LENGTH SPECIFIED GREATER THAN SUBSCHEMA LENGTH.

The record length specified must not be greater than the length as defined in the subschema. (IPSB compiler)

Severity: E

220065

Length LENGTH SPECIFIED LESS THAN CONTROL LENGTH.

The minimum record length specified is less than the control length of the record. It is rounded up to the control length. (IPSB compiler)

Severity: W

220066

Length INVALID/MISSING LENGTH SPECIFICATION.

The length must be a 1- to 5-digit number that indicates the length of the segment this record represents. (IPSB compiler)

Severity: E

220067

Record-name RECORD IS NOT VARIABLE LENGTH IN SCHEMA.

A maximum and minimum length has been specified, but the record is not of variable length. (IPSB compiler)

Severity: E

220069

Clause MISSING PARENT CLAUSE.

A parent segment must be specified for all but root segments. (IPSB compiler)

Severity: E

220070

Access-method INVALID ACCESS METHOD.

The access method has been specified incorrectly. Check the syntax. (IPSB compiler)

Severity: E

220071

Dbd-name INVALID/MISSING DBDNAME.

The DBD name must be a 1- to 8-character alphanumeric string. (IPSB compiler)

Severity: E

220072

Option INVALID/MISSING PROCESSING OPTIONS.

Processing options have been specified incorrectly. Check the syntax. (IPSB compiler)

Severity: E

220073

INVALID KEY FEEDBACK LENGTH.

The value specified for the key feedback length must be numeric. (IPSB compiler)

Severity: E

220074

Option INVALID POSITIONING.

Positioning has been specified incorrectly. Check the syntax. (IPSB compiler)

Severity: E

220077

Segment-name INVALID SEGMENT NAME.

A segment name must be a 1- to 8-character alphanumeric string. (IPSB compiler)

Severity: E

220078

Set-name INVALID SET NAME.

A set name must be a 1- to 16-character alphanumeric string. (IPSB compiler)

Severity: E

220079

Record-name INVALID RECORD NAME.

A record name must be a 1- to 16-character alphanumeric string. (IPSB compiler)

Severity: E

220080

Use-option INVALID USE OPTION.

The USE option has been specified incorrectly. Check the syntax. (IPSB compiler)

Severity: E

220082

Option PROCESSING SEQUENCE MUST BE SPECIFIED.

Processing sequence must be specified for all access methods except HDAM. (IPSB compiler)

Severity: E

220083

Option PROCESSING SEQUENCE MUST NOT BE SPECIFIED.

Processing sequence must not be specified if the access method is HDAM. (IPSB compiler)

Severity: E

220085

Index-name INDEX NOT DEFINED IN INDEX SECTION.

The indexed field named must be defined by an INDEX statement in the INDEX SECTION. (IPSB compiler)

Severity: E

220086

Segment-name SEGMENT HAS BEEN PREVIOUSLY DEFINED.

A segment name can be used only once within any one PCB. (IPSB compiler)

Severity: E

220087

Record-name RECORD NOT DEFINED IN RECORD SECTION.

The record named must be defined by a RECORD statement in the RECORD SECTION. (IPSB compiler)

Severity: E

220088

Segment-name SEGMENT NOT PREVIOUSLY DEFINED.

The segment named must be previously defined by a SEGMENT statement within the same PCB. (IPSB compiler)

Severity: E

220489

Parent-name PARENT MUST NOT BE SPECIFIED ON ROOT SEGMENTS.

Remove the PARENT clause from this SEGMENT statement. (IPSB compiler)

Severity: E

220090

Set-name SET NOT DEFINED IN SUBSCHEMA.

The set named must be defined in the subschema previously specified in the IPSB statement. (IPSB compiler)

Severity: E

220091

Set-name INVALID USE OF SET.

Processing sequence set can be specified only if the access method is HISAM or INDEX. (IPSB compiler)

Severity: E

220092

INVALID MEMBER OF SET.

The IDMS record is not a valid member of the set specified. (IPSB compiler)

Severity: E

220093

INVALID OWNER OF SET.

The IDMS record is not a valid owner of the set specified. (IPSB compiler)

Severity: E

220094

Index-name INVALID USE OF INDEX.

Processing sequence index can be specified only if the access method is HIDAM or secondary index. (IPSB compiler)

Severity: E

220095

Segment-name INVALID INVERSION OF SEGMENTS.

A segment appears in the inversion that is not in the hierarchic path of the destination parent in its physical database. (IPSB compiler)

Severity: E

220096

Rule INVALID RULE SPECIFIED.

An insert or replace rule has been specified incorrectly. Check the syntax. (IPSB compiler)

Severity: E

220097

Parent-name LOGICAL PARENT CONCATENATED KEY IS UNDEFINED.

If a logical destination parent is specified, its concatenated key must be defined within the record definition of the logical child. (IPSB compiler)

Severity: E

220098

Parent-name PHYSICAL PARENT CONCATENATED KEY IS UNDEFINED.

If a physical destination parent is specified, its concatenated key must be defined within the record definition of the logical child. (IPSB compiler)

Severity: E

220100

set-name INVALID INDEXED SET NAME.

The name specified for an indexed set must be a 1- to 16-character name. (IPSB compiler)

Severity: E

220101

set-name INDEXED SET NOT DEFINED IN SUBSCHEMA.

The specified indexed set must be defined in the subschema. (IPSB compiler)

Severity: E

220102

subschema-name SUBSCHEMA DOES NOT CONTAIN INDEXED SETS.

'INDEXED-SET' was specified in the IPSB SECTION, but no indexed sets were found in the subschema. (IPSB compiler)

Severity: E

220103

INVALID EXIT ROUTINE NAME

The index suppression exit routine name must be a 1- to 8-character name. (IPSB compiler)

Severity: E

221001

'EJECT' NOT ALONE ON CARD. TOKEN ASSUMED.

EJECT must appear as the only entry on the card unless it is to be used as other than a compiler directive. (Syntax Generator)

Severity: W

221002

INVALID 'SPACE' COMMAND PARAMETER.

SPACE must be followed by a blank and, optionally, a 1-digit number greater than 0 indicating the number of lines to be spaced. (Syntax Generator)

Severity: W

221003

SPACE NOT ALONE ON CARD. TOKEN ASSUMED.

SPACE must appear as the only entry on the card unless it is to be used as other than a compiler directive. (IPSB compiler)

Severity: W

221004

SEQUENCE ERROR. RUN ABORTED.

Input was out of sequence. (Syntax Generator)

Severity: F

221005

STRING EXCEEDS MAXIMUM OR AVAILABLE LENGTH.

The character string specified is greater in length than the maximum allowed for this parameter. (Syntax Generator)

Severity: E

221006

HEX STRING EXCEEDS MAXIMUM OR AVAILABLE LENGTH.

The hexadecimal string specified is greater in length than the maximum allowed for this parameter. (Syntax Generator)

Severity: E

221007

HEX STRING CONTAINS INVALID CHARACTERS.

Other than valid characters appear in the hexadecimal string specified. (Syntax Generator)

Severity: E

221009

Dbd-name - DBD NOT FOUND IN LIBRARY.

The DBD name listed prior to this message was not in the library designated by the STEPLIB JCL statement. (Syntax Generator)

Severity: E

221010

Dbd-name - DBD NOT LOADED - ERROR.

An error has occurred during load processing for the specified DBD. (Syntax Generator)

Severity: E

221011

Dbd-name - DBD NOT LOCATED.

A DBD was not located in the already loaded chain. This is a system internal error. (Syntax Generator)

Severity: E

221012

UNEXPECTED END OF FILE PROCESSING IPSB STATEMENT.

End of file occurred before sufficient control input was found. (Syntax Generator)

Severity: F

221013

Keyword UNKNOWN KEYWORD FOR STATEMENT TYPE.

The keyword encountered is not valid for the current statement type. (Syntax Generator)

Severity: E

221014

PRIMARY INDEX NOT FOUND.

The LCHILD statement for the named index was not found. (Syntax Generator)

Severity: E

221015

Keyword INVALID STATEMENT TYPE. SKIPPING TO NEXT PERIOD.

The statement encountered is not a valid statement type. (Syntax Generator)

Severity: E

221016

Segment-name - SEGMENT NOT FOUND IN DBD.

The named segment was not found in the appropriate DBD. (Syntax Generator)

Severity: E

221017

Segment-name - SEGMENT PHYSICAL OWNER NOT FOUND.

An attempt to establish a path to the physical owner of a destination parent segment was unsuccessful. (Syntax Generator)

Severity: E

221018

Segment-name - SEGMENT HAS NO FIELDS - REQUIRED.

A logical child segment has been encountered that has no fields defined for it. (Syntax Generator)

Severity: E

221019

Segment-name - SEGMENT PARENT NOT FOUND.

While determining the length of a logical child concatenated key, the root segment could not be found. The probable cause is an incorrectly defined path. (Syntax Generator)

Severity: E

221020

Segment-name - SEGMENT SEQUENCE FIELD REQUIRED.

The sequence field for an index pointer record was not found. (Syntax Generator)

Severity: E

221021

Psb-name - PSB NOT FOUND IN LIBRARY.

The named PSB was not found in any library accessible through a STEPLIB JCL statement. (Syntax Generator)

Severity: F

221022

Psb-name - PSB NOT LOADED - ERROR.

An error has occurred during load processing for the specified PSB. The PSB named could not be loaded. (Syntax Generator)

221023

GENERATION TERMINATED - TOO MANY ERRORS.

Too many errors have occurred for this processing run. (Syntax Generator)

Severity: F

221024

Dbd-name DBD NOT VALID FOR USE WITH CA IDMS DLI Transparency.

A loaded DBD has been found to contain an invalid format. The probable cause is that the IBM version of the DBD was loaded. Use the CA IDMS DLI Transparency assembled DBD. (Syntax Generator)

Severity: F

221025

Psb-name PSB NOT VALID FOR USE WITH CA IDMS/DLI Transparency.

A loaded PSB has been found to contain an invalid format. Use the CA IDMS DLI Transparency assembled PSB. (Syntax Generator)

Severity: F

221026

Dbd-name DBD FOR LOGICAL PARENT NOT FOUND IN ANY PCB.

During generation of a load IPSB, the named DBD was referenced as a logical parent DBD, but no PCB in the load PSB defined the logical parent as a physical segment. (Syntax Generator)

Severity: F

221500

DATABASE CAPACITY EXCEEDED.

Database capacity is not sufficient to load all necessary records. Reallocate the database files with more space. Issued by Step 2. (Load Utility)

221501

SEGMENT=segment-name NOT IN IPSB.

The named segment has been found in the input file, or workfile, but is not defined in any PCB within the IPSB. Issued by Steps 1, 2, 4, and 6. (Load Utility)

221503

NO LOGICAL RELATIONSHIPS.

Database load Processing (Step 2) encountered no logical relationships. Steps 3 through 6 are not required to complete the database load. (Load Utility)

221506

IPSB=ipsb-name NOT FOUND.

The named IPSB could not be loaded. Make sure that the correct IPSB resides in the data set(s) referenced by CDMSLIB. Issued by Steps 1, 2, 4, and 6. (Load Utility)

221508

INITIAL DATABASE LOAD COMPLETE.

Database load processing (Step 2) has been successfully completed. (Load Utility)

221509

PREFIX RESOLUTION COMPLETE.

Prefix resolution processing (Step 4) has been successfully completed. (Load Utility)

Severity: F

221510

PREFIX UDPDATE COMPLETE.

Prefix update processing (Step 6) has been successfully completed. (Load Utility)

221511

PCB DBDNAME=dbdname NOT FOUND.

Prefix resolution or prefix update processing failed to find a DBD in the IPSB that matches the named DBD. The named DBD was referenced in the logical workfile produced by the database load (Step 2). Issued by Steps 4 and 6. (Load Utility)

221512

INVALID INPUT CONTROL FORMAT.

Invalid processing control statements have been encountered. Rerun the step in question with correctly formatted control specifications. Issued by Steps 1, 2, 4, and 6. (Load Utility)

221513

PROCESSING TERMINATED-ERROR(S).

A fatal error condition was detected. This message is usually preceded by a message indicating the specific error condition. Issued by Steps 1, 2, 4, and 6. (Load Utility)

221514

SEGM=segment-name - NO LOGICAL PARENT.

A logical child record in the workfile has no corresponding logical parent record in the workfile. This message may be the result of an incomplete Step 3 sort, or it may indicate that multiple logical workfiles from Step 2 were not merged prior to the Step 3 sort. Issued by Steps 4 and 6. (Load Utility)

221516

PARAMETER 'IPSB' REQUIRED.

The control format for a processing step is incomplete. Specify the IPSB name required for processing. Issued by Steps 2, 4, and 6. (Load Utility)

221517

INVALID IPSB PROCOPTS - 'LOAD' REQUIRED.

Use of the Load Utility within the CA IDMS DLI Transparency Run-Time Interface requires that each PCB in the IPSB be specified with PROCOPT=LOAD. Issued by Steps 2, 4, and 6. (Load Utility)

221519

DBDNAME=dbdname NOT IN IPSB.

The named DBD was not found in the IPSB. Use the same IPSB as you used in Step 2 processing. Issued by Steps 4 and 6. (Load Utility)

221521

RELATED WORKFILES MISSING.

This message usually appears after messages 221514 and 221518, to indicate the probable error cause. Issued by Steps 4 and 6. (Load Utility)

221522

NO FURTHER PROCESSING REQUIRED.

Database Load Processing (Step 2) has been successfully completed. No logical relationships were found, and no additional processing is necessary. (Load Utility)

221523

STATUS=code RETURNED-SEGMENT= segment-name.

An unexpected DL/I status code has been returned to the Load Utility. This message usually indicates a fatal error. Issued by Steps 2 and 6. (Load Utility)

221524

CHECK IPSB FOR PROBLEM(S).

An error has been detected that may be related to an IPSB specification. Issued by Steps 2 and 6. (Load Utility)

221525

UNEXPECTED END OF FILE-SYSIPT.

End of file was encountered before sufficient process control information was found. Issued by Steps 1, 4, and 6. (Load Utility)

221526

INVALID IPSB FORMAT.

The IPSB that was loaded does not have a valid format. Issued by Steps 1, 4, and 6. (Load Utility)

Severity: F

221527

PARAMETER 'PROCESS=' REQUIRED.

The JCL for the step did not include the PROCESS control parameter. PROCESS= is required. Issued by Steps 1, 2, 4, and 6. (Load Utility)

221528

INSUFFICIENT STORAGE.

More main storage is required for successful processing. Increase the storage specification, and rerun the processing step in question. Issued by Steps 1, 2, 4, and 6. (Load Utility)

221530

CALC PROCESSING COMPLETE.

The Pre-Load CALC Processing (Step 1) has been successfully completed. (Load Utility)

Severity: F

221531

I/O ERROR ON FILE=SYS999.

An I/O error has been detected during file processing. Determine the nature of the cause, and re-run the processing step. Issued by Steps 1, 2, 4, and 6. (Load Utility)

221532

ERROR OPENING FILE=SYS999.

An attempt to open a required file has not been successful. Check for missing file definitions, or conflicts in file definitions. Issued by Steps 1, 2, 4, and 6. (Load Utility)

221542

LOAD OF SUBSCHEMA=subschema-name FAILED.

The subschema specified in the IPSB was not available for CALC processing. Make sure that subschema is accessible through a STEPLIB JCL statement. Issued by Steps 1 and 2. (Load Utility)

221543

AREA=area-name NOT IN SUBSCHEMA.

The specified area name was found in the load IPSB, but was not found in the subschema. Make sure that the subschema contains all required area names. Issued by Steps 1 and 2. (Load Utility)

223902

ipsb-name COMPILE DATE: mm/dd/yy TIME: HHmmsshh

Issued during IPSB validation, this indicates the original IPSB compilation date/time. Date is in month/day/year format. Time is in hours/minutes/seconds/hundreth seconds. (IPSB decompiler)

223902

subschema COMPILE DATE: mm/dd/yy TIME: HHmmsshh

Issued during IPSB validation, this indicates the corresponding subschema compilation date/time. Date and time formats are as indicated above. (IPSB decompiler)

223903

REQUESTED MODULE IS NOT AN IPSB.

IPSB validation has determined that the loaded module does not contain a format similar to that of a CA IDMS DLI Transparency IPSB. Due to the environment associated with CA IDMS DLI Transparency, this module may be a native DL/I PSB. (IPSB decompiler)

223904

REQUESTED IPSB RELEASE LEVEL NOT SUPPORTED.

IPSB validation has found that the requested IPSB loaded for decompilation is for a release level of CA IDMS DLI Transparency that is not supported by the IPSB decompiler. (IPSB decompiler)

223905

ERROR IN LOAD OF IPSB=ipsbname

Issued when an error has occurred during an attempt to access the specified IPSB load module. (IPSB decompiler)

223906

ERROR OPENING FILE=SYSxxx

Produced when a request to open a specific file has been unsuccessful, probably due to missing or conflicting file definitions. SYSxxx can include SYSIPT, SYSLST, OR SYSPCH. (IPSB decompiler)

223907

ERROR ON FILE=SYSxxx FUNC=xxxx STAT=xxxx.

Produced when a request to close, or read/write to/from a specific file has resulted in an error condition. Here, SYSxxx can be the file names SYSIPT, SYSLST, or SYSPCH. The FUNC= and STAT= operands of the message relate to the processing functions and resulting statuses that are common to the I/O utility module IDMSUTIO (IDMSUTIO is used for all I/O functions for the Decompiler). (IPSB decompiler)

223908

UNEXPECTED END OF FILE - SYSIPT

If no valid IPSB-directive control statement is encountered before end-of-file occurs while reading the SYSIPT input file, this message is issued, and decompilation terminates. (IPSB decompiler)

223909

CA IDMS DLI Transparency IPSB DECOMPILATION TERMINATED-ERROR(S).

If an error occurs during SYSIPT processing, IPSB loading, IPSB identity and release level validation, or SYSLST or SYSPCH processing, this message is issued as an indication of the final status of the current processing run. (IPSB decompiler)

223910

CA IDMS DLI Transparency IPSB DECOMPILATION COMPLETE

Issued when IPSB decompilation process has completed without encountering any problem situations. This is the final message issued by the decompiler after a successful run. (IPSB decompiler)