APPENDIX 2A - User-defined compile commands

Some iSeries shops, instead of using the standard compile commands (such as CRTRPGMOD, CRTBNDRPG, etc.), use their own compile commands. Usually this is done because some preprocessing is needed before executing the standard compile command.

In similar cases, running a conversion would not result to a success, as most of compiles would fail.

In order to have both the iWEB Batch Conversion job and command WEBCOMPILE adopting a user-defined compile command, you should proceed as follow.

1. In the conversion target library you should define a data area with the same name as the standard compile command (CRTRPGMOD, CRTBNDRPG, CRTSQLRPGI, etc.)
2. In this data area you should provide the prototype of your corresponding user defined command, as an example:
   MYLIB/MYBNDRPG PGM(&O/&N) SRCFILE(&L/&F) SRCMBR(&N)
   During execution, the Batch Converter job would run the user-defined command instead of the standard one, after replacing
   • &N with the source member name (same as the object name)
   • &O with the name of the target object library
   • &L with the source library name
   • &F with the source file name
   Should you use, instead of a user-defined command a call to some program of yours, please make sure that in your prototype the parameters are within quotes (').
   Example
   call MYLIB/PRECOMP parm('&N' '&O' '&F' '&L')