Re: Using CL to call RPG pgms

[dkahn@xxxxxxxxxxxxxxxxx]

Igor.Beslic@xxxxxxxxxxxx wrote:

> I'm wondering would it be to complicated to perform all this within
> RPG pgm (for example in separate module or subprocedure) with use of
> different APIs (QCMDEXC) and explicit file OPENing. (inexaple. if I
> define file in f spec with USROPN keyword would I get err. message if
> file is not in LIBL on pgm start).

No. Only when you actually open the file.

> I suppose there exist some actions (as file override options for RPG
> pgm that will be run) that must be defined in CL??

No. You can perform the file overrides from within the RPG program if you
need to.

> What is better practice? It's probably metter of programers style but
> it would be nice to know how other programers do that.

If you need a CL wrapper round a program anyway, then I would tend to put
things in there that CL is designed for, such as file overrides. However,
I'm a little surprised that you have such a need for CL programs. Why is it
that you need to set the library list and perform file overrides for every
program? Have you hard-coded these in the CL programs? That is certainly
not good practice. Generally these things are resolved through the work
management facilities of OS/400. Look into job descriptions and routing
entries for example.  These are really questions for the midrange-l list
rather than rpg400-l though.

--
Dave...
               _________  ,___o
             __________   _\ <;_        http://www.audax.uk.net
           ___________   (_)/ (_)       http://www.twickenhamcc.co.uk
=======================================================
The opinions expressed in this communication are my own and do not
necessarily reflect those of my employer.


______________________________________________________________________
This message may contain confidential information which may also be legally 
privileged and is intended only for the use of the parties to whom it is 
addressed. If you are not an intended recipient you are hereby notified that 
any disclosure, copying, distribution or use of any information in this e-mail 
is strictly prohibited. If you receive this message in error please notify the 
sender by return e-mail and then destroy it. Further, we make every endeavour 
to keep our network free from viruses. However, you do need to verify that this 
e-mail and any attachments are free of viruses as we can take no responsibility 
for any computer viruses which might be transferred by way of this e-mail. All 
information and attachments remain the property of Stolt Offshore Group and 
should be held as confidential.