• First block of parameters
• Second block of parameters
• Third block of parameters

2.4.1 First block of parameters

These are the most important set of parameters.

1. Optional initial setup user program
   Experience has shown that some development shops use some special environments
   of their owns to compile objects.
   If that is the case, than a special user-created program may be run,
   in the batch conversion job submitted by GWCS, in order to set up such special environment
   at the very beginning of the process.
2. User library lists for compiling modules and programs
   This is the library list needed to resolve references to program external definitions at compile time,
   such as database files and display files.
   Example of such a library list:

   library1,library2,library3

3. User library lists for resolving dspf field references
   The iWEB conversion of display files is some kind of operation very similar to a display file compile.
   Masks representing library/dspf/rcdfmt are created on the IFS.
   If display files use REFFLD, MSGID, or ERRMSGID keywords referencing *LIBL,
   then a library list able to appropriate resolve such references should be provided.
   Example of such a library list:

   librarya,libraryb,libraryc

4. Target library for converted programs
   Generally, one would not want the converted programs, though running both in 5250 and in WEB mode,
   to replace the existing 5250 programs.
   One would rather have them generated in a separate library, to be properly mentioned at iWEB Runtime start.
   Therefore, create a separate program target library, and mention it in this parameter.
5. Target library for the sources of the converted programs
   In the same way, one would want to keep the generated sources of the converted programs
   separated from the sources of the original 5250 programs.
   Please specify here the name of such a library.
   Source files do not have to be there: they would be dynamically created.
6. Target release for all the converted programs
   That is up to your needs and to OS/400 previous releases available on your iSeries.

2.4.2 Second block of parameters

This block of parameters deals with compile commands.
The Batch Converter job, submitted from the GWCS (Graphical WEB Conversion Session), would convert RPG III sources
to ILE RPG (RPG IV) sources, then generate and execute the appropriate creation commands.
The create commands used for RPG IV converted sources are: CRTRPGMOD, CRTBNDRPG,CRTSQLRPGI,and CRTPGM.

There might be cases, where the developer needs some parameters be used for all objects created through a given command.
This screen provides a way to implement that.

You should just enter a string to be appended to the generated create command.
A syntax checker would immediately validate your input.

2.4.3 Third block of parameters

The might be cases where the developer would like some special areas of the application screens
to have specific evidence.
In this page you may define rectangles to identify such areas.
Should you use this facility, you must make sure that all the application screens fit the rules you specify.