| From (Pos. 26-32) | To (Pos. 33-39) | Format | Length | Keyword | Information |
|---|---|---|---|---|---|
| 1 | 8 | Character | 8 | *FILE | The first 8 characters of the file name. |
| 9 | 9 | Character | 1 | Open indication (1 = open). | |
| 10 | 10 | Character | 1 | End of file (1 = end of file) | |
| 11 | 15 | Zoned decimal | 5,0 | *STATUS | Status code. For a description of these codes, see File Status Codes. |
| 16 | 21 | Character | 6 | *OPCODE | Operation code The first five positions (left-adjusted) specify the type of operation by using the character representation of the calculation operation codes. For example, if a READE was being processed, READE is placed in the leftmost five positions. If the operation was an implicit operation (for example, a primary file read or update on the output specifications), the equivalent operation code is generated (such as READ or UPDAT) and placed in location *OPCODE. Operation codes which have 6 letter names will be shortened to 5 letters.
|
| 22 | 29 | Character | 8 | *ROUTINE | First 8 characters of the name of the routine (including a subprocedure) in which the file operation was done. |
| 30 | 37 | Character | 8 | If OPTION(*NOSRCSTMT) is specified, this is the source listing line number of the file operation. If OPTION(*SRCSTMT) is specified, this is the source listing statement number of the file operation. The full statement number is included when it applies to the root source member. If the statement number is greater than 6 digits, that is, it includes a source ID other than zero, the first 2 positions of the 8-byte feedback area will have a "+ " indicating that the rest of the statement number is stored in positions 53-54. | |
| 38 | 42 | Zoned decimal | 5,0 | User-specified reason for error on SPECIAL file. | |
| 38 | 45 | Character | 8 | *RECORD | For a program described file the record identifying indicator is placed left-adjusted in the field; the remaining six positions are filled with blanks. For an externally described file, the first 8 characters of the name of the record being processed when the exception/error occurred. |
| 46 | 52 | Character | 7 | Machine or system message number. | |
| 53 | 66 | Character | 14 | Unused. | |
| 77 | 78 | Binary | 2 | Source Id matching the statement number from positions 30-37. |
| From (Pos. 26-32) | To (Pos. 33-39) | Format | Length | Keyword | Information |
|---|---|---|---|---|---|
| 67 | 70 | Zoned decimal | 4,0 | *SIZE | Screen size (product of the number of rows and the number of columns on the device screen). |
| 71 | 72 | Zoned decimal | 2,0 | *INP | The display's keyboard type. Set to 00 if the keyboard is alphanumeric or katakana. Set to 10 if the keyboard is ideographic. |
| 73 | 74 | Zoned decimal | 2,0 | *OUT | The display type. Set to 00 if the display is alphanumeric or katakana. Set to 10 if the display is ideographic. Set to 20 if the display is DBCS. |
| 75 | 76 | Zoned decimal | 2,0 | *MODE | Always set to 00. |
INFDS File Feedback Example
To specify an INFDS which contains fields in the file feedback section, you can make the following entries:
- Specify the INFDS keyword on the file description specification with the name of the file information data structure
- Specify the file information data structure and the subfields you wish to use on a definition specification.
- Specify special keywords left-adjusted, in the FROM field (positions 26-32) on the definition specification, or specify the positions of the fields in the FROM field (position 26-32) and the TO field (position 33-39).
FFilename++IPEASFRlen+LKlen+AIDevice+.Keywords+++++++++++++++++++++++++++++Comments++++++++++ FMYFILE IF E DISK INFDS(FILEFBK) DName+++++++++++ETDsFrom+++To/L+++IDc.Keywords+++++++++++++++++++++++++++++Comments++++++++++ DFILEFBK DS D FILE *FILE * File name D OPEN_IND 9 9N * File open? D EOF_IND 10 10N * File at eof? D STATUS *STATUS * Status code D OPCODE *OPCODE * Last opcode D ROUTINE *ROUTINE * RPG Routine D LIST_NUM 30 37 * Listing line D SPCL_STAT 38 42S 0 * SPECIAL status D RECORD *RECORD * Record name D MSGID 46 52 * Error MSGID D SCREEN *SIZE * Screen size D NLS_IN *INP * NLS Input? D NLS_OUT *OUT * NLS Output? D NLS_MODE *MODE * NLS Mode? |
- Note:
- The keywords are not labels and cannot be used to access the subfields. Short entries are padded on the right with blanks.
Open Feedback Information
Positions 81 through 240 in the file information data structure contain open feedback information. The contents of the file open feedback area are copied by RPG to the open feedback section of the INFDS whenever the file associated with the INFDS is opened. This includes members opened as a result of a read operation on a multi-member processed file.
A description of the contents of the open feedback area, and what file types the fields are valid for, can be found in the |iSeries Information Center.
INFDS Open Feedback Example
To specify an INFDS which contains fields in the open feedback section, you can make the following entries:
- Specify the INFDS keyword on the file description specification with the name of the file information data structure
- Specify the file information data structure and the subfields you wish to use on a definition specification.
- Use information in the |iSeries Information Center database and file systems category to determine which fields you wish to include in the INFDS. To calculate the From and To positions (positions 26 through 32 and 33 through 39 of the definition specifications) that specify the subfields of the open feedback section of the INFDS, use the Offset, Data Type, and Length given in the Information Center and do the following calculations:
From = 81 + Offset To = From - 1 + Character_Length Character_Length = Length (in bytes)
For example, for overflow line number of a printer file, the |Information Center gives:
Offset = 107 Data Type is binary Length = 2 Therefore, From = 81 + 107 = 188, To = 188 - 1 + 2 = 189. See subfield OVERFLOW in example below
FFilename++IPEASFRlen+LKlen+AIDevice+.Keywords+++++++++++++++++++++++++++++Comments++++++++++ FMYFILE O F 132 PRINTER INFDS(OPNFBK) DName+++++++++++ETDsFrom+++To/L+++IDc.Keywords+++++++++++++++++++++++++++++Comments++++++++++ DOPNFBK DS D ODP_TYPE 81 82 * ODP Type D FILE_NAME 83 92 * File name D LIBRARY 93 102 * Library name D SPOOL_FILE 103 112 * Spool file name D SPOOL_LIB 113 122 * Spool file lib D SPOOL_NUM 123 124I 0 * Spool file num D RCD_LEN 125 126I 0 * Max record len D KEY_LEN 127 128I 0 * Max key len D MEMBER 129 138 * Member name D TYPE 147 148I 0 * File type D ROWS 152 153I 0 * Num PRT/DSP rows D COLUMNS 154 155I 0 * Num PRT/DSP cols D NUM_RCDS 156 159I 0 * Num of records D ACC_TYPE 160 161 * Access type D DUP_KEY 162 162 * Duplicate key? D SRC_FILE 163 163 * Source file? D VOL_OFF 184 185I 0 * Vol label offset D BLK_RCDS 186 187I 0 * Max rcds in blk D OVERFLOW 188 189I 0 * Overflow line D BLK_INCR 190 191I 0 * Blk increment D FLAGS1 196 196 * Misc flags D REQUESTER 197 206 * Requester name D OPEN_COUNT 207 208I 0 * Open count D BASED_MBRS 211 212I 0 * Num based mbrs D FLAGS2 213 213 * Misc flags D OPEN_ID 214 215 * Open identifier D RCDFMT_LEN 216 217I 0 * Max rcd fmt len D CCSID 218 219I 0 * Database CCSID D FLAGS3 220 220 * Misc flags D NUM_DEVS 227 228I 0 * Num devs defined |
Input/Output Feedback Information
Positions 241 through 366 in the file information data structure are used for input/output feedback information. The contents of the file common input/output feedback area are copied by RPG to the input/output feedback section of the INFDS:
- If a POST for any file with factor 1 blank has been specified anywhere in your program:
- only after a POST for the file.
- If a POST for any file with factor 1 blank has not been specified anywhere in your program:
- after each I/O operation, if blocking is not active for the file.
- after the I/O request to data management to get or put a block of data, if blocking is active for the file.
For more information see POST (Post).
A description of the contents of the input/output feedback area can be found in the |Information Center.
INFDS Input/Output Feedback Example
To specify an INFDS which contains fields in the input/output feedback section, you can make the following entries:
- Specify the INFDS keyword on the file description specification with the name of the file information data structure
- Specify the file information data structure and the subfields you wish to use on a definition specification.
- Use information in the |Information Center to determine which fields you wish to include in the INFDS. To calculate the From and To positions (positions 26 through 32 and 33 through 39 of the definition specifications) that specify the subfields of the input/output feedback section of the INFDS, use the Offset, Data Type, and Length given in the |Information Center and do the following calculations:
From = 241 + Offset To = From - 1 + Character_Length Character_Length = Length (in bytes)
For example, for device class of a file, the |Information Center gives:
Offset = 30 Data Type is character Length = 2 Therefore, From = 241 + 30 = 271, To = 271 - 1 + 2 = 272. See subfield DEV_CLASS in example below
FFilename++IPEASFRlen+LKlen+AIDevice+.Keywords+++++++++++++++++++++++++++++Comments++++++++++ FMYFILE IF E DISK INFDS(MYIOFBK) DName+++++++++++ETDsFrom+++To/L+++IDc.Keywords+++++++++++++++++++++++++++++Comments++++++++++ DMYIOFBK DS D * 241-242 not used D WRITE_CNT 243 246I 0 * Write count D READ_CNT 247 250I 0 * Read count D WRTRD_CNT 251 254I 0 * Write/read count D OTHER_CNT 255 258I 0 * Other I/O count D OPERATION 260 260 * Cuurent operation D IO_RCD_FMT 261 270 * Rcd format name D DEV_CLASS 271 272 * Device class D IO_PGM_DEV 273 282 * Pgm device name D IO_RCD_LEN 283 286I 0 * Rcd len of I/O |
Device Specific Feedback Information
The device specific feedback information in the file information data structure starts at position 367 in the INFDS, and contains input/output feedback information specific to a device.
The length of the INFDS when device specific feedback information is required, depends on two factors: the device type of the file, and on whether DISK files are keyed or not. The minimum length is 528; but some files require a longer INFDS.
- For WORKSTN files, the INFDS is long enough to hold the device-specific feedback information for any type of display or ICF file starting at position 241. For example, if the longest device-specific feedback information requires 390 bytes, the INFDS for WORKSTN files is 630 bytes long (240+390=630).
- For externally described DISK files, the INFDS is at least long enough to hold the longest key in the file beginning at position 401.
More information on the contents and length of the device feedback for database file, printer files, ICF and display files can be found in the |iSeries Information Center database and file systems category.
The contents of the device specific input/output feedback area of the file are copied by RPG to the device specific feedback section of the INFDS:
- If a POST for any file with factor 1 blank has been specified anywhere in your program:
- only after a POST for the file.
- If a POST for any file with factor 1 blank has not been specified anywhere in your program:
- after each I/O operation, if blocking is not active for the file.
- after the I/O request to data management to get or put a block of data, if blocking is active for the file.
Notes:
- After each keyed input operation, only the key fields will be updated.
- After each non-keyed input operation, only the relative record number will be updated.
For more information see POST (Post).
INFDS Device Specific Feedback Examples
To specify an INFDS which contains fields in the device-specific feedback section, you can make the following entries:
- Specify the INFDS keyword on the file description specification with the name of the file information data structure
- Specify the file information data structure and the subfields you wish to use on a definition specification.
- Use information in the |Information Center to determine which fields you wish to include in the INFDS. To calculate the From and To positions (positions 26 through 32 and 33 through 39 of the definition specifications) that specify the subfields of the input/output feedback section of the INFDS, use the Offset, Data Type, and Length given in the |Information Center and do the following calculations:
From = 367 + Offset To = From - 1 + Character_Length Character_Length = Length (in bytes)
For example, for relative record number of a data base file, the |Information Center gives:
Offset = 30 Data Type is binary Length = 4 Therefore, From = 367 + 30 = 397, To = 397 - 1 + 4 = 400. See subfield DB_RRN in DBFBK data structure in example below
FFilename++IPEASFRlen+LKlen+AIDevice+.Keywords+++++++++++++++++++++++++++++Comments++++++++++ FMYFILE O F 132 PRINTER INFDS(PRTFBK) DName+++++++++++ETDsFrom+++To/L+++IDc.Keywords+++++++++++++++++++++++++++++Comments++++++++++ DPRTFBK DS D CUR_LINE 367 368I 0 * Current line num D CUR_PAGE 369 372I 0 * Current page cnt * If the first bit of PRT_FLAGS is on, the spooled file has been * deleted. Use TESTB X'80' or TESTB '0' to test this bit. D PRT_FLAGS 373 373 D PRT_MAJOR 401 402 * Major ret code D PRT_MINOR 403 404 * Minor ret code |
FFilename++IPEASFRlen+LKlen+AIDevice+.Keywords+++++++++++++++++++++++++++++Comments++++++++++ FMYFILE IF E DISK INFDS(DBFBK) DName+++++++++++ETDsFrom+++To/L+++IDc.Keywords+++++++++++++++++++++++++++++Comments++++++++++ DDBFBK DS D FDBK_SIZE 367 370I 0 * Size of DB fdbk D JOIN_BITS 371 374I 0 * JFILE bits D LOCK_RCDS 377 378I 0 * Nbr locked rcds D POS_BITS 385 385 * File pos bits D DLT_BITS 384 384 * Rcd deleted bits D NUM_KEYS 387 388I 0 * Num keys (bin) D KEY_LEN 393 394I 0 * Key length D MBR_NUM 395 396I 0 * Member number D DB_RRN 397 400I 0 * Relative-rcd-num D KEY 401 2400 * Key value (max D * size 2000) |
FFilename++IPEASFRlen+LKlen+AIDevice+.Keywords+++++++++++++++++++++++++++++Comments++++++++++ FMYFILE CF E WORKSTN INFDS(ICFFBK) DName+++++++++++ETDsFrom+++To/L+++IDc.Keywords+++++++++++++++++++++++++++++Comments++++++++++ DICFFBK DS D ICF_AID 369 369 * AID byte D ICF_LEN 372 375I 0 * Actual data len D ICF_MAJOR 401 402 * Major ret code D ICF_MINOR 403 404 * Minor ret code D SNA_SENSE 405 412 * SNA sense rc D SAFE_IND 413 413 * Safe indicator D RQSWRT 415 415 * Request write D RMT_FMT 416 425 * Remote rcd fmt D ICF_MODE 430 437 * Mode name |
FFilename++IPEASFRlen+LKlen+AIDevice+.Keywords+++++++++++++++++++++++++++++Comments++++++++++ FMYFILE CF E WORKSTN INFDS(DSPFBK) DName+++++++++++ETDsFrom+++To/L+++IDc.Keywords+++++++++++++++++++++++++++++Comments++++++++++ DDSPFBK DS D DSP_FLAG1 367 368 * Display flags D DSP_AID 369 369 * AID byte D CURSOR 370 371 * Cursor location D DATA_LEN 372 375I 0 * Actual data len D SF_RRN 376 377I 0 * Subfile rrn D MIN_RRN 378 379I 0 * Subfile min rrn D NUM_RCDS 380 381I 0 * Subfile num rcds D ACT_CURS 382 383 * Active window D * cursor location D DSP_MAJOR 401 402 * Major ret code D DSP_MINOR 403 404 * Minor ret code |
Get Attributes Feedback Information
The get attributes feedback information in the file information data structure starts at position 241 in the INFDS, and contains information about a display device or ICF session (a device associated with a WORKSTN file). The end position of the get attributes feedback information depends on the length of the data returned by a get attributes data management operation. The get attributes data management operation is performed when a POST with a program device specified for factor 1 is used.
More information about the contents and the length of the get attributes data can be found in the |Information Center.
INFDS Get Attributes Feedback Example
To specify an INFDS which contains fields in the get attributes feedback section, you can make the following entries:
- Specify the INFDS keyword on the file description specification with the name of the file information data structure
- Specify the file information data structure and the subfields you wish to use on a definition specification.
- Use information in the |Information Center to determine which fields you wish to include in the INFDS. To calculate the From and To positions (positions 26 through 32 and 33 through 39 of the definition specifications) that specify the subfields of the get attributes feedback section of the INFDS, use the Offset, Data Type, and Length given in the |Information Center and do the following calculations:
From = 241 + Offset To = From - 1 + Character_Length Character_Length = Length (in bytes)
For example, for device type of a file, the |Information Center gives:
Offset = 31 Data Type is character Length = 6 Therefore, From = 241 + 31 = 272, To = 272 - 1 + 6 = 277. See subfield DEV_TYPE in example below
FFilename++IPEASFRlen+LKlen+AIDevice+.Keywords+++++++++++++++++++++++++++++Comments++++++++++ FMYFILE CF E WORKSTN INFDS(DSPATRFBK) DName+++++++++++ETDsFrom+++To/L+++IDc.Keywords+++++++++++++++++++++++++++++Comments++++++++++ DDSPATRFBK DS D PGM_DEV 241 250 * Program device D DEV_DSC 251 260 * Dev description D USER_ID 261 270 * User ID D DEV_CLASS 271 271 * Device class D DEV_TYPE 272 277 * Device type D REQ_DEV 278 278 * Requester? D ACQ_STAT 279 279 * Acquire status D INV_STAT 280 280 * Invite status D DATA_AVAIL 281 281 * Data available D NUM_ROWS 282 283I 0 * Number of rows D NUM_COLS 284 285I 0 * Number of cols D BLINK 286 286 * Allow blink? D LINE_STAT 287 287 * Online/offline? D DSP_LOC 288 288 * Display location D DSP_TYPE 289 289 * Display type D KBD_TYPE 290 290 * Keyboard type D CTL_INFO 342 342 * Controller info D COLOR_DSP 343 343 * Color capable? D GRID_DSP 344 344 * Grid line dsp? * The following fields apply to ISDN. D ISDN_LEN 385 386I 0 * Rmt number len D ISDN_TYPE 387 388 * Rmt number type D ISDN_PLAN 389 390 * Rmt number plan D ISDN_NUM 391 430 * Rmt number D ISDN_SLEN 435 436I 0 * Rmt sub-address D * length D ISDN_STYPE 437 438 * Rmt sub-address D * type D ISDN_SNUM 439 478 * Rmt sub-address D ISDN_CON 480 480 * Connection D ISDN_RLEN 481 482I 0 * Rmt address len D ISDN_RNUM 483 514 * Rmt address D ISDN_ELEN 519 520 * Extension len D ISDN_ETYPE 521 521 * Extension type D ISDN_ENUM 522 561 * Extension num D ISDN_XTYPE 566 566 * X.25 call type D |
FFilename++IPEASFRlen+LKlen+AIDevice+.Keywords+++++++++++++++++++++++++++++Comments++++++++++ FMYFILE CF E WORKSTN INFDS(ICFATRFBK) DName+++++++++++ETDsFrom+++To/L+++IDc.Keywords+++++++++++++++++++++++++++++Comments++++++++++ DICFATRFBK DS D PGM_DEV 241 250 * Program device D DEV_DSC 251 260 * Dev description D USER_ID 261 270 * User ID D DEV_CLASS 271 271 * Device class D DEV_TYPE 272 272 * Device type D REQ_DEV 278 278 * Requester? D ACQ_STAT 279 279 * Acquire status D INV_STAT 280 280 * Invite status D DATA_AVAIL 281 281 * Data available D SES_STAT 291 291 * Session status D SYNC_LVL 292 292 * Synch level D CONV_TYPE 293 293 * Conversation typ D RMT_LOC 294 301 * Remote location D LCL_LU 302 309 * Local LU name D LCL_NETID 310 317 * Local net ID D RMT_LU 318 325 * Remote LU D RMT_NETID 326 333 * Remote net ID D APPC_MODE 334 341 * APPC Mode D LU6_STATE 345 345 * LU6 conv state D LU6_COR 346 353 * LU6 conv D * correlator * The following fields apply to ISDN. D ISDN_LEN 385 386I 0 * Rmt number len D ISDN_TYPE 387 388 * Rmt number type D ISDN_PLAN 389 390 * Rmt number plan D ISDN_NUM 391 430 * Rmt number D ISDN_SLEN 435 436I 0 * sub-addr len D ISDN_STYPE 437 438 * sub-addr type D ISDN_SNUM 439 478 * Rmt sub-address D ISDN_CON 480 480 * Connection D ISDN_RLEN 481 482I 0 * Rmt address len D ISDN_RNUM 483 514 * Rmt address D ISDN_ELEN 519 520 * Extension len D ISDN_ETYPE 521 521 * Extension type D ISDN_ENUM 522 561 * Extension num D ISDN_XTYPE 566 566 * X.25 call type * The following information is available only when program was started * as result of a received program start request. (P_ stands for protected) D TRAN_PGM 567 630 * Trans pgm name D P_LUWIDLN 631 631 * LUWID fld len D P_LUNAMELN 632 632 * LU-NAME len D P_LUNAME 633 649 * LU-NAME D P_LUWIDIN 650 655 * LUWID instance D P_LUWIDSEQ 656 657I 0 * LUWID seq num * The following information is available only when a protected conversation * is started on a remote system. (U_ stands for unprotected) D U_LUWIDLN 658 658 * LUWID fld len D U_LUNAMELN 659 659 * LU-NAME len D U_LUNAME 660 676 * LU-NAME D U_LUWIDIN 677 682 * LUWID instance D U_LUWIDSEQ 683 684I 0 * LUWID seq num |
Blocking Considerations
The fields of the input/output specific feedback in the INFDS and in most cases the fields of the device specific feedback information section of the INFDS, are not updated for each operation to the file in which the records are blocked and unblocked. The feedback information is updated only when a block of records is transferred between an RPG program and the OS/400 system. However, if you are doing blocked input on a data base file, the relative record number and the key value in the data base feedback section of the INFDS are updated:
- On every input/output operation, if a POST for any file with factor 1 blank has not been specified anywhere in your program.
- Only after a POST for the file, if a POST for any file with factor 1 blank has been specified anywhere in your program.
You can obtain valid updated feedback information by using the CL command OVRDBF (Override with Database File) with SEQONLY(*NO) specified. If you use a file override command, the ILE RPG compiler does not block or unblock the records in the file.
For more information on blocking and unblocking of records in RPG see ILE RPG Programmer's Guide.
File Status Codes
Any code placed in the subfield location *STATUS that is greater than 99 is considered to be an exception/error condition. When the status code is greater than 99; the error indicator -- if specified in positions 73 and 74 -- is set on, or the %ERROR built-in function -- if the 'E' extender is specified -- is set to return '1'; otherwise, the file exception/error subroutine receives control. Location *STATUS is updated after every file operation.
You can use the %STATUS built-in function to get information on exception/errors. It returns the most recent value set for the program or file status. If a file is specified, %STATUS returns the value contained in the INFDS *STATUS field for the specified file.
The codes in the following tables are placed in the subfield location *STATUS for the file information data structure:
| Code | Device1 | RC2 | Condition |
|---|---|---|---|
| 00000 | No exception/error. | ||
| 00002 | W | n/a | Function key used to end display. |
| 00011 | W,D,SQ | 11xx | End of file on a read (input). |
| 00012 | W,D,SQ | n/a | No-record-found condition on a CHAIN, SETLL, and SETGT operations. |
| 00013 | W | n/a | Subfile is full on WRITE operation. |
| |||
| Code | Device1 | RC2 | Condition |
|---|---|---|---|
| 01011 | W,D,SQ | n/a | Undefined record type (input record does not match record identifying indicator). |
| 01021 | W,D,SQ | n/a | Tried to write a record that already exists (file being used has unique keys and key is duplicate, or attempted to write duplicate relative record number to a subfile). |
| 01022 | D | n/a | Referential constraint error detected on file member. |
| 01023 | D,SQ | n/a | Error in trigger program before file operation performed. |
| 01024 | D,SQ | n/a | Error in trigger program after file operation performed. |
| 01031 | W,D,SQ | n/a | Match field out of sequence. |
| 01041 | n/a | n/a | Array/table load sequence error. |
| 01042 | n/a | n/a | Array/table load sequence error. Alternate collating sequence used. |
| 01051 | n/a | n/a | Excess entries in array/table file. |
| 01071 | W,D,SQ | n/a | Numeric sequence error. |
| 011214 | W | n/a | No indicator on the DDS keyword for Print key. |
| 011224 | W | n/a | No indicator on the DDS keyword for Roll Up key. |
| 011234 | W | n/a | No indicator on the DDS keyword for Roll Down key. |
| 011244 | W | n/a | No indicator on the DDS keyword for Clear key. |
| 011254 | W | n/a | No indicator on the DDS keyword for Help key. |
| 011264 | W | n/a | No indicator on the DDS keyword for Home key. |
| 01201 | W | 34xx | Record mismatch detected on input. |
| 01211 | all | n/a | I/O operation to a closed file. |
| 01215 | all | n/a | OPEN issued to a file already opened. |
| 012163 | all | yes | Error on an implicit OPEN/CLOSE operation. |
| 012173 | all | yes | Error on an explicit OPEN/CLOSE operation. |
| 01218 | D,SQ | n/a | Record already locked. |
| 01221 | D,SQ | n/a | Update operation attempted without a prior read. |
| 01222 | D,SQ | n/a | Record cannot be allocated due to referential constraint error |
| 01231 | SP | n/a | Error on SPECIAL file. |
| 01235 | P | n/a | Error in PRTCTL space or skip entries. |
| 01241 | D,SQ | n/a | Record number not found. (Record number specified in record address file is not present in file being processed.) |
| 01251 | W | 80xx 81xx | Permanent I/O error occurred. |
| 01255 | W | 82xx 83xx | Session or device error occurred. Recovery may be possible. |
| 01261 | W | n/a | Attempt to exceed maximum number of acquired devices. |
| 01271 | W | n/a | Attempt to acquire unavailable device |
| 01281 | W | n/a | Operation to unacquired device. |
| 01282 | W | 0309 | Job ending with controlled option. |
| 01284 | W | n/a | Unable to acquire second device for single device file |
| 01285 | W | 0800 | Attempt to acquire a device already acquired. |
| 01286 | W | n/a | Attempt to open shared file with SAVDS or IND options. |
| 01287 | W | n/a | Response indicators overlap IND indicators. |
| 01299 | W,D,SQ | yes | Other I/O error detected. |
| 01331 | W | 0310 | Wait time exceeded for READ from WORKSTN file. |
Notes:
| |||
The following table shows the major/minor return code to *STATUS value mapping for errors that occur to AS/400 programs using WORKSTN files only. See the |Information Center for more information on major/minor return codes.
| Major | Minor | *STATUS |
|---|---|---|
| 00,02 | all | 00000 |
| 03 | all (except 09,10) | 00000 |
| 03 | 09 | 01282 |
| 03 | 10 | 01331 |
| 04 | all | 01299 |
| 08 | all | 012851 |
| 11 | all | 00011 |
| 34 | all | 01201 |
| 80,81 | all | 01251 |
| 82,83 | all | 01255 |
Notes:
| ||
[ Top of Page | Previous Page | Next Page | Table of Contents | I
No comments:
Post a Comment