RPG/400 Help

Continuation Line Options Summary Chart

The valid entries for positions 54 through 67 are:

*----------------------------------------------------------------*
|          Continuation Line Options                             |
*----------*----------*------------------------------------------*
| OPTION   | ENTRY    | EXPLANATION                              |
| (54-59)  | (60-67)  |                                          |
*----------*----------*------------------------------------------*
| "COMIT"  | Blank    | This file is specified for commitment    |
|          |          | control.  Use the "COMIT" and "ROLBK"    |
|          |          | operation codes to group changes to this |
|          |          | file so that the changes all happen      |
|          |          | together, or do not happen at all.       |
*----------*----------*------------------------------------------*
| "ID"     | Field    | Positions 60-65 contain the left-        |
|          | name     | justified name of a 10-character alpha-  |
|          |          | numeric field which need not be further  |
|          |          | defined.  This field contains the name   |
|          |          | of the program device that supplied the  |
|          |          | record processed in the file.  The field |
|          |          | is updated each time a record is read    |
|          |          | from a file.  Also, you may move a       |
|          |          | program device name into this field to   |
|          |          | direct an output or device-specific      |
|          |          | input operation (other than a            |
|          |          | "READ"-by-file-name or an implicit cycle |
|          |          | read) to a different device.  When       |
|          |          | moving a literal into the field, blank   |
|          |          | the field first, and use the "MOVEL"     |
|          |          | operation to place the literal left-     |
|          |          | justified in the field.  Initially, the  |
|          |          | field is blank. A blank field indicates  |
|          |          | the requester device.  If the requester  |
|          |          | device is not acquired for your file,    |
|          |          | you must not use a blank field.  The     |
|          |          | "ID" field is maintained for each call   |
|          |          | to a program.  If you call program B     |
|          |          | from within program A, the "ID" field    |
|          |          | for program A is not affected.  Program  |
|          |          | B uses a separate "ID" field.  When you  |
|          |          | return to program A, its "ID" field has  |
|          |          | the same value as it had before you      |
|          |          | called program B.  If program B needs to |
|          |          | know which devices are acquired to       |
|          |          | program A, program A must pass this      |
|          |          | information (as a parameter list) when   |
|          |          | it calls program B.  When you specify    |
|          |          | "ID" but not "NUM", the RPG/400 program  |
|          |          | assumes "NUM" is present with a value of |
|          |          | 1.  To determine the name of the         |
|          |          | requester device, you may look in the    |
|          |          | appropriate area of the file information |
|          |          | data structure.  Or, you may process one |
|          |          | of the input or output operations        |
|          |          | described above with the "ID" field      |
|          |          | blank.  After the operation, the "ID"    |
|          |          | field has the name of the requester      |
|          |          | device.                                  |
*----------*----------*------------------------------------------*
| "IGNORE" | Blank    | This option lets you ignore a record     |
|          |          | format from an externally described      |
|          |          | file.  On the continuation line, posi-   |
|          |          | tions 19 through 28 specify the external |
|          |          | name of the record format to be ignored, |
|          |          | and positions 60 through 67 must be      |
|          |          | blank.  The program runs as if the       |
|          |          | record format did not exist.             |
*----------*----------*------------------------------------------*
| "IND"    | Indi-    | Indicators from 01 to the number speci-  |
|          | cator    | fied are saved and restored for each     |
|          | number   | device attached to a mixed or multiple   |
|          |          | device file.  Before an input operation, |
|          |          | the indicators for the device associated |
|          |          | with the previous input or output opera- |
|          |          | tion are saved.  After the input opera-  |
|          |          | tion, the indicators for the device      |
|          |          | associated with this current input oper- |
|          |          | ation are restored.  Specify a number    |
|          |          | from 01 through 99, right-justified, in  |
|          |          | positions 60 through 65.  No indicators  |
|          |          | are saved and restored if "IND" is not   |
|          |          | specified or if the option "NUM" has the |
|          |          | entry 1.  If you specified the keyword   |
|          |          | "INDARA", the number you specify for     |
|          |          | "IND" must be less than any response     |
|          |          | indicator you use in your DDS.  For      |
|          |          | example, if you specify "INDARA" and     |
|          |          | CF01(55) in your DDS, the maximum value  |
|          |          | for "IND" is 54. "IND" must not be used  |
|          |          | with shared files.  When you specify     |
|          |          | "IND" but not "NUM", the RPG/400 program |
|          |          | assumes "NUM" is present with a value of |
|          |          | 1.                                       |
*----------*----------*------------------------------------------*
| "INFDS"  | Data     | This entry lets you define and name a    |
|          | struc-   | data structure to contain the            |
|          | ture     | exception/error information.  The data   |
|          | name     | structure name is entered in positions   |
|          |          | 60 through 65 and left justified.  If    |
|          |          | "INFDS" is specified for more than one   |
|          |          | file, each associated data structure     |
|          |          | must have a unique name.                 |
*----------*----------*------------------------------------------*
| "INFSR"  | Subrou-  | The file exception/error subroutine      |
|          | tine     | named (left justified) in positions 60   |
|          | name     | through 65 may receive control following |
|          |          | file exception/errors.  The subroutine   |
|          |          | name may be "*PSSR", which indicates the |
|          |          | user defined program exception/error     |
|          |          | subroutine is to be given control for    |
|          |          | errors on this file.                     |
*----------*----------*------------------------------------------*
| "NUM"    | Maximum  | The number specified must be greater     |
|          | number   | than zero and right-justified in posi-   |
|          | of       | tions 60 through 65.  The lesser of this |
|          | devices  | number and the number of devices defined |
|          |          | for the "WORKSTN" file on the create-    |
|          |          | file command is the maximum number of    |
|          |          | devices that this file can acquire.      |
|          |          | With a shared file, the "NUM" value is   |
|          |          | not used to restrict the number of       |
|          |          | acquired devices.  When you specify      |
|          |          | "ID", "IND", or "SAVDS" but not "NUM",   |
|          |          | the RPG/400 program assumes "NUM" is     |
|          |          | present with a value of 1.               |
*----------*----------*------------------------------------------*
| "PASS"   | "*NOIND" | Specify "PASS *NOIND" on the file        |
|          |          | description specification continuation   |
|          |          | line for a program described "WORKSTN"   |
|          |          | file if you are taking responsibility    |
|          |          | for passing indicators on input and      |
|          |          | output.  With "PASS *NOIND", the RPG/400 |
|          |          | language does not pass indicators to     |
|          |          | data management on output and does not   |
|          |          | receive them on input. Pass indicators   |
|          |          | by describing them as fields (in the     |
|          |          | form "*INxx, *IN," or "*IN,xx") in the   |
|          |          | input or output record. They must be     |
|          |          | specified in the sequence required by    |
|          |          | the data description specifications      |
|          |          | (DDS).  You can use the DDS listing to   |
|          |          | determine this sequence.  If you do not  |
|          |          | specify "PASS *NOIND" and you use the    |
|          |          | keyword "INDARA" in the DDS for the      |
|          |          | "WORKSTN" file, indicators are not       |
|          |          | passed to data management on output nor  |
|          |          | received from data management on input.  |
*----------*----------*------------------------------------------*
| "PLIST"  | Param-   | This entry is valid only when the device |
|          | eter     | specified in positions 40 through 46 of  |
|          | list     | the main file-description line is        |
|          | name     | "SPECIAL".  Positions 60 through 65 give |
|          |          | the left-justified name of the parameter |
|          |          | list to be passed to the special         |
|          |          | routine.  The parameters identified by   |
|          |          | this entry are added to the end of the   |
|          |          | parameter list passed by the program.    |
*----------*----------*------------------------------------------*
| "PRTCTL" | Data     | The dynamic printer control option is    |
|          | struc-   | being used.  The data structure speci-   |
|          | ture     | fied left-justified in positions 60      |
|          | name     | through 65 refers to the forms control   |
|          |          | information and line count value.  The   |
|          |          | "PRTCTL" option is valid only for a      |
|          |          | program described file.                  |
*----------*----------*------------------------------------------*
| "RECNO"  | Field    | This entry is optional for disk files to |
|          | name     | be processed by relative-record number.  |
|          |          | A "RECNO" field must be specified for    |
|          |          | output files processed by relative-      |
|          |          | record number, output files that are     |
|          |          | referenced by a random "WRITE" calcu-    |
|          |          | lation operation, or output files that   |
|          |          | are used with "ADD" on the output spec-  |
|          |          | ifications.                              |
|          |          |                                          |
|          |          | "RECNO" can be specified for             |
|          |          | input/update files.  The relative-record |
|          |          | number of the record retrieved is placed |
|          |          | in the field named, left justified, in   |
|          |          | positions 60 through 65 for all oper-    |
|          |          | ations that reposition the file (such as |
|          |          | "READ, SETLL", or "OPEN").  It must be   |
|          |          | defined as numeric with zero decimal     |
|          |          | positions.                               |
|          |          |                                          |
|          |          | The field length must be sufficient to   |
|          |          | contain the longest record number for    |
|          |          | the file. "RECNO" is valid for "DISK"    |
|          |          | files only.  The contents of positions   |
|          |          | 60 through 65 may be not valid when the  |
|          |          | RPG/400 compiler does the blocking and   |
|          |          | unblocking of records.                   |
*----------*----------*------------------------------------------*
| "RENAME" | Record   | This entry, which is optional, allows    |
|          | format   | you to rename record formats in an       |
|          | name     | externally described file.  Positions 19 |
|          |          | through 28 of the continuation line      |
|          |          | specify the external name of the record  |
|          |          | format that is to be renamed.  Positions |
|          |          | 60 through 67 specify the left-justified |
|          |          | name of the record as it is used in the  |
|          |          | program.  The external name is replaced  |
|          |          | by this name in the program.             |
*----------*----------*------------------------------------------*
| "SAVDS"  | Data     | Positions 60-65 contain the left-        |
|          | struc-   | justified name of the data structure     |
|          | ture     | saved and restored for each device.      |
|          | name     | Before an input operation, the data      |
|          |          | structure for the device operation is    |
|          |          | saved. After the input operation, the    |
|          |          | data structure for the device associated |
|          |          | with this current input operation is     |
|          |          | restored.  This data structure cannot be |
|          |          | a data area data structure, file infor-  |
|          |          | mation data structure, or program status |
|          |          | data structure, and it cannot contain a  |
|          |          | compile-time array or prerun-time array. |
|          |          |                                          |
|          |          | If "SAVDS" is not specified, no saving   |
|          |          | and restoring is done. "SAVDS" must not  |
|          |          | be specified for shared files.  When you |
|          |          | specify "SAVDS" but not "NUM", the       |
|          |          | RPG/400 program assumes "NUM" is present |
|          |          | with a value of 1.                       |
*----------*----------*------------------------------------------*
| "SFILE"  | Record   | If the main file-description line con-   |
|          | format   | tains E in position 19 and "WORKSTN" in  |
|          | name     | positions 40 through 46, this option     |
|          |          | must be used to define any subfiles to   |
|          |          | be used in the file.  Positions 60       |
|          |          | through 67 must specify, left justified  |
|          |          | the RPG/400 name of the record format to |
|          |          | be processed as a subfile.               |
|          |          |                                          |
|          |          | Positions 47 through 52 must specify the |
|          |          | name of the relative-record number field |
|          |          | for this subfile.  The relative-record   |
|          |          | number of any record retrieved by a      |
|          |          | "READC" or "CHAIN" operation is placed   |
|          |          | into the field named in positions 47     |
|          |          | through 52.  This field is also used to  |
|          |          | specify the record number that RPG/400   |
|          |          | uses for a "WRITE" operation to the      |
|          |          | subfile or for output operations that    |
|          |          | use "ADD".  The field name specified in  |
|          |          | positions 47 through 52 must be defined  |
|          |          | as numeric with zero decimal positions.  |
|          |          | The field must have enough positions to  |
|          |          | contain the largest record number for    |
|          |          | the file.  (See the "SFLSIZ" keyword in  |
|          |          | the Data Description Specifications Ref- |
|          |          | erence.)                                 |
|          |          |                                          |
|          |          | Relative record number processing is     |
|          |          | implicitly defined as part of the        |
|          |          | "SFILE" definition.  If multiple sub-    |
|          |          | files are defined, each subfile requires |
|          |          | a separate continuation line.  Do not    |
|          |          | use SFILE with SLN.                      |
*----------*----------*------------------------------------------*
| "SLN"    | Field    | Positions 60-65 contain the left-        |
|          | name     | justified name of a start line number    |
|          |          | ("SLN") field.  The "SLN" field deter-   |
|          |          | mines where a record format is written   |
|          |          | to a display file.  The main file-       |
|          |          | description line must contain "WORKSTN"  |
|          |          | in positions 40 through 46 and a C or O  |
|          |          | in positions 15.  The data description   |
|          |          | specifications for the file must specify |
|          |          | the keyword "SLNO(*VAR)" for one or more |
|          |          | record formats.  When you specify "SLN"  |
|          |          | on the continuation line, the "SLN"      |
|          |          | field will automatically be defined in   |
|          |          | the program as a numeric field with      |
|          |          | length of 2 and with 0 decimal posi-     |
|          |          | tions.  Do not use SLN with SFILE.       |
*----------*----------*------------------------------------------*


[ Top of Page | Previous Page | Next Page | Table of Contents ]