Re: How to call API with different parms over different releases

[Dave Murvin <davem@xxxxxxxx>]

 Thanks Chris, but I am using my new command to call the API.  (We 
programmers don't use no stinkin easy to use system commands! ;-) ) The 
issues are that this API has additional parms added in V5R4 and again in 
V7.1.  I would like the command to only show the options available at 
the release it is being run on, so the V5R2 guys don't see the parms 
available in V5R4 and V7.1.

Additionally, I will be creating the program package to be able to run 
at V5R2 or later.  When a customer restores the program package 
(RSTLICPGM)  to a system running V5R4 or V7.1, I would like them to be 
able to use the additional API parameters available on their current 
release.

I just don't see any way to do this without creating a complete command 
for each release, then renaming them all except for the one for the 
current release at RSTLICPGM time.

I can make the API parameters optional, but how do I make the command 
PARMS, validator and help text optional too?

Thanks

On 10/19/2010 3:06 PM, Chris Bipes wrote:
> Where there is a command, there is an API.  Search for the API and you
> will find that the new stuff is optional, most likely.  Commands are for
> users while API's are for programmers.;-)