Page History
...
- The physical file CUSMST will be created in QTEMP first.
- The logical view CUSMSTV1 will be created in library QTEMP next.
- The I/O module I@CUSMST is then compiled into library QTEMP.
- The list of actions continues. This is indicated by the "+" sign at the bottom right of the screen. If desired use the roll up and roll down keys to scroll backwards and forwards through the list of actions/reasons displayed.
Input Options
| Warning |
|---|
| WARNING: submitted batch job library list. Make sure that the job description being used does not cause the library in which the file resides to be made the IBM i "current library". Jobs submitted to make files operational where the "current library" and the library in which the file resides are the same may fail or produce unexpected results. |
Produce File and I/O Module Source Listings
...
How this feature is implemented depends on the version of RPG code being compiled. For more information on the different versions of RPG code that can be compiled refer, to ILE Implementation.
This facility is provided for compatibility with the operating system and because it is required by some installations. It is strongly recommended that this option is not used. Refer to the IBM supplied CL reference manual for details.
Mandatory field. Default value is determined from the system definition data area. Refer to System Definition Data Area DC@A01. Allowable values are:
If RPG/400 Code Is Being Compiled
YES
Use the IGNDECERR(*YES) parameter.
NO
Use the IGNDECERR(*NO) parameter.
If RPG/IV Code Is Being Compiled
YES
Use the FIXNBR(*ZONED) parameter.
NO
Use the FIXNBR(*NONE) parameter.
...
When the program is called, it is passed two parameters:
| Type | Lenght | Dec | Description |
|---|---|---|---|
A | 10 | Name of physical file created or recreated. | |
A | 10 | Name of library in which physical file resides. |
If the user program fails the create / recreate job will end abnormally. Messages on the job log will indicate the cause of the failure. However, the file will have been successfully created or recreated and will be usable. In this case correct the problem in the user program and independently resubmit for execution.
...