RE: ICF file compilation

[Buck Calabro <Buck.Calabro@xxxxxxxxxxxx>]

>I require information regarding compilation of ICF files on AS/400, I
>have used the following command for compilation
>
>CRTICFF FILE (*LIBL/ISPI0100) SRCFILE (*LIBL/QDDSSRC)  +
>              ACQPGMDEV (ISPI0100) AUT(*ALL)
>
>
>Is the above command sufficient for compilation or do we need to add
>other parameters to the command.

It depends entirely upon how the application was designed.  Does the RPG
program do an ACQ?  If so, then you probably need to compile with
ACQPGMDEV(*NONE).


>I had noticed another command being executed after the above command is
>run.
>
>ADDICFDEVE FILE(ISPI0100) PGMDEV (ISPI0100) MODE (BLANK)   +
>               FMTSLT (*RECID) RMTLOCNAME (*REQUESTER)
>
>
>Is this command mandatory for the ICF file to be compiled and
>accessible
>in a HLL program.

It depends upon...
You need at least one ICF device entry; this is the link between the program
and the physical device.  The DEVID must match the PGMDEV of the ICFDEVE:

FSWTCMNCF  CF   E             WORKSTN USROPN
F                                     DEVID(PGMDEV)

C                   MOVEL     'SWITCH'      PGMDEV
C     PGMDEV        ACQ       SWTCMNCF                             81

xxxICFDEVE PGMDEV(SWITCH)

and the RMTLOCNAME must match the RMTLOCNAME on an actual device:
xxxICFDEVE RMTLOCNAME(DMS100)

DSPDEVD(NORTEL100)
DEVD        NORTEL100
RMTLOCNAME  DMS100

In this way, when your program acquires the "logical" device (the DEVID) the
system traces it through the ICFDEVE to the actual device to be used.

In your case, *REQUESTER is a special "logical" device, meaning the
interactive terminal that is running the program.

I think that in order to answer your question better, we need to understand
how your program is interacting with the remote location.

>Send your reply to my id.

It's traditional to send the reply to the list so that all the readers can
contribute to the discussion.
Regards,
  --buck