Re: Passing unwanted parameters

[Simon Coulter <shc@xxxxxxxxxxxxxxxxx>]

On 13/01/2009, at 9:53 AM, Rory Hewitt wrote:

> Basically we have a backwards compatibility issue, where we have a  
> 'router'
> program, which calls certain (user-specified) programs. We now want to
> change the parameters to pass to those programs (just adding an  
> extra one).
> However, since the program being called is only known at run-time,  
> there's a
> problem. Plus there might be hundreds of programs to call, and our  
> users may
> decide to change them piecemeal...

Externally define the parameter behaviour (*DTAARA, control file,  
etc.). Your router program checks this and only if set passes the new  
parameter.

Users modify their exit programs (piecemeal or wholesale) and test  
for the extra parameter. If present use it, if not behave the old way.

Once all user programs are modified they can set the control flag to  
pass the new parameter.

> I guess I could retrieve the MAX parameters value for the called  
> program
> (one of the API's must do this) and see whether it's an ILE program  
> (in
> which case I can pass the new parameter) or it's an OPM program  
> that's been
> changed to define the new parameter...

QCLRPGMI format PGMI0100 will give you the type of program and MIN  
and MAX number of parameters.


Regards,
Simon Coulter.
--------------------------------------------------------------------
   FlyByNight Software         OS/400, i5/OS Technical Specialists

   http://www.flybynight.com.au/
   Phone: +61 2 6657 8251   Mobile: +61 0411 091 400        /"\
   Fax:   +61 2 6657 8251                                   \ /
                                                             X
                 ASCII Ribbon campaign against HTML E-Mail  / \
--------------------------------------------------------------------