HLI: Model 204 completion and ABEND codes
This topic describes the completion codes that might be encountered when using the Model 204 HLI facility. There are two broad categories of completion codes:
- Return codes for HLI calls
- Job run ABEND codes
This topic presents the codes in the following tables:
- Completion return codes 0-3 lists completion codes that are returned by Model 204 to the host language application program for operations which completed normally, or with a warning. RETCODE is 0, 1, 2, and 3.
- Completion return codes 4 and greater lists completion codes that usually indicate that a call was unsuccessful. RETCODE is greater than or equal to 4.
- Job run ABEND codes lists completion codes that are generated for severe errors that cause the HLI job run to abend.
For more information about individual completion return codes for conditions that are unique to a specific function call, refer to the usage notes for the particular call.
Completion return codes 0-3
The following table describes the completion codes that are returned by Model 204 to the host language application program for operations which completed normally, or with a warning. RETCODE is 0, 1, 2, and 3.
|0||IFATTN||IFDIAL connection completed.|
|IFCHKPT||Checkpointing status depends on which function code is specified in the call:
|IFDIAL connection established.|
|IFHNGUP||IFDIAL connection dropped.|
|All except IFCHKPT||Function completed successfully.|
|1||IFCHKPT||Checkpointing status depends on which function code is specified in the call:
|Nonnumeric value could not be converted, or integer portion of the value is too large for output area. Errors may occur for B, P, F, and Z edit formats.|
|IFMORE||Nonnumeric value could not be converted, or integer portion of the value is too large for output area. Errors may occur for B, P, F, and Z edit formats.|
|IFREAD||Call IFWRITE next to provide Model 204 with input.|
|Illegal call. Thread already exists.|
|IFWRITE||Call IFWRITE next to provide Model 204 with input.|
|2||IFCHKPT||Checkpoint request timed out. Checkpoint not taken.|
|IFFLS||The file indicator was used to identify the file of the current record and no current record was found.|
|IFFTCH||Indicates no more records to fetch in the current set.|
|IFREAD||Call IFREAD next to get more output from Model 204.|
|IFRPRM and IFSPRM||TBO has been enabled or disabled for a file such that the group of files in the job violates the restriction that TBO files may not open for update while any non-TBO file is open on a read-only thread. The parameter reset was successful, but the M204.0498 error was issued and the file is closed.|
|IFWRITE||Call IFREAD next to get more output from Model 204.|
|Any other call||Indicates no records in the current set.|
|3||IFCHKPT||Caller is not allowed to wait for checkpoints. Call ignored.|
|All except IFCHKPT||Return code number reserved for future use, or control of necessary resource could not be obtained and call may be reexecuted.|
Completion return codes 4 and greater
The following table describes the completion codes which usually, but not always, indicate that a call was unsuccessful. RETCODE is greater than or equal to 4.
Note: The error message is written to the Model 204 journal and is available to the application program using the IFGERR call.
|4||All calls||Error message has been produced. For more information about conditions that are unique to a specific function call, refer to the Notes for the particular call.|
|5||IFCHKPT||Checkpoint not active during recovery. Call ignored.|
|Compiled IFAM calls||The name used by an E (execute) call has not been defined.|
|6||Compiled IFAM calls||The name used by an E (execute) call or standard compile and execute call has been defined by an incompatible function.
IFGET, IFMORE, and IFPUT specs can be shared, but they cannot be referred to by IFFIND calls. Similarly, IFFIND compilations cannot be referred to by IFGET-type calls. IFFIND and IFFNDX cannot share specs.
|7||Compiled IFAM calls||Not enough space exists to compile the current call. Error message indicates which server table is full. Use IFFLUSH to recover from this condition.
Many Host Language Interface calls not directly affected by the Compiled IFAM feature use space in QTBL and VTBL. These functions return a code of 4 if either table fills.
|For an updating call where the FILEMODL file option is set to NUMERIC VALIDATION, Model 204 encountered invalid values for BINARY and FLOAT numeric field types. For more information about FILEMODL, see File model feature.
For information about binary and float values, see Storing data in fields.
|All calls||The function has been cancelled. The transaction is automatically backed out and control is returned to the application program.|
|12||IFREAD and IFWRITE||IFREAD called when IFWRITE was expected, or IFWRITE called when IFREAD was expected.|
|IFREAD||No output ready from Model 204; call IFWRITE to provide more input. The answer area is not altered.|
|15||IFEFCC and IFERLC||An updating function received an error when there was no conflict to search for.|
|40||IFBOUT||An IFBOUT was issued from a read-only thread. IFBOUT is only valid on update threads.|
|All calls||Function requires update privileges, but none were granted. Issue IFSTRT with thread update privileges and give file or group password with update privileges.|
|50||All calls (IFAM2 and IFAM4)||An updating function was issued on a thread which has been quiesced for checkpointing by a previous call to IFCHKPT.|
|60||All calls||No current file or group. Function cannot complete.|
|61||All calls||Function attempted against file or group with broken FISTAT setting. Function cannot complete.|
|80||All calls in IFAM1||No current thread.
|An IFDIAL connection already exists for this application program. The attempt to establish more than one simultaneous connection for this application is ignored.|
|IFSTRT in IFAM1||Illegal call to IFSTRT. A thread already exists.|
|IFSTRT in IFAM2 and IFAM4||Model 204 is not yet available for user processing. Recovery may still be in progress. Call IFSTRT again.|
|95||IFDTHRD and IFSTHRD||Nonexistent new thread specified. Call ignored.|
|96||IFDTHRD||New thread is already current thread and thus is not detached.|
|100||in IFAM1||LOGIN failed.|
|in IFAM2 and IFAM4||No current thread exists. Call IFSTRT.|
|IFATTN||The connection was lost.|
|IFHNGUP||The connection was lost prior to call.|
|IFREAD||No current Model 204 connection exists or the connection is lost.|
|IFSTRT in IFAM2 and IFAM4||LOGIN failed.|
|IFWRITE||No current Model 204 connection exists or the connection is lost.|
|101||IFDIAL in IFAM1||Invalid BATCH204 module loaded. Check STEPLIB for correct release.|
|IFSTRT in IFAM1||Failure to dynamically load the IFAM1 load module, because the entry point was specified incorrectly when relinking.|
|A uniqueness violation has occurred (field level constraint). A UNIQUE violation corresponds to errors handled by ON FCC ON units in SOUL. For information about ON units, see On units 2.|
|An AT-MOST-ONE violation occurred (field level constraint). An AT-MOST-ONE violation corresponds to errors handled by ON FCC ON units in SOUL. For information about ON units, see On units 2.|
|260||IFOPEN||A file or group could not be opened.|
|300||All calls||Thread restarted in Host Language Interface Model 204 service program. Call lost.|
|325||in IFAM2||IQB not large enough. Adjust the Model 204 parameters LIBUFF, LOBUFF, and IFAMBS as necessary.|
|350||in IFAM2||Invalid string length. Adjust the Model 204 parameters LIBUFF and LOBUFF as necessary.|
|400||IFSTRT and IFSETUP in IFAM2 and IFAM4||Invalid language code.|
|Other calls in IFAM2 and IFAM4||Invalid parameter list.|
|500||IFCALL||Invalid function number passed to IFCALL.|
|in IFAM1 using IFDIAL||Invalid function called.|
|800||in IFAM2 and IFAM4||No Host Language Interface Model 204 threads currently available. Try again later or increase number of defined threads.|
|IFDIAL||All Model 204 IFDIAL connections are busy. Check to see that the proper number of IODEV=29 initialization statements were included for the Host Language Interface Model 204 service program.|
|1000||IFFNSH||Normal return code from IFFNSH. (See 1nnn.)|
|in IFAM2 and IFAM4||The application program disconnected from Model 204 normally.|
|All other calls||Model 204 is no longer available.|
|1001||in IFAM2 and IFAM4||Host Languages Interface Model 204 service program is not up, the Host Language interface is halted or drained, or no host language threads were defined in Model 204 This may indicate that the IFAM4 load module was link-edited without the REUS option.|
|IFDIAL||Host Language Interface Model 204 is not up, or no IODEV=39 statements were included in initialization, or CRAM channel name does not exist. Connection is impossible.|
|1002||in IFAM2||Insufficient SQA or CSA space to use CRAM connection.|
|1003||in IFAM2 and IFAM4||Insufficient memory in the IFAM application to allocate the necessary control blocks.|
|Not enough memory for CRAM open.|
|1004||in IFAM2||An initial IFCSA call was not made.|
|1nnn||IFFNSH in IFAM1||IFFNSH returns 1000 and the highest Model 204 journal error message return code encountered during the run.|
Job run ABEND codes
The follwing table describes the user ABEND completion codes that are generated when Model 204 detects severe errors and abends the HLI application program job run.
|100||IFAM1||CCASNAP DD statement is missing.|
|250||IFAM2 and IFAM4||Invalid parameter list. Completion code could not be set.|
|1000||IFAM2||Serious CRAM error. Save all output from application and Host Language Interface Model 204 service program for Technical Support personnel.|
For more information about how IFAM4 sets the job step return code, see IFAM4 jobs: Job errors and ABENDs.