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

[Dave Murvin <davem@xxxxxxxx>]

I thought about that, but although is seems simpler, for my purposes and 
in my belief, that would look kind of sloppy to the customers.  It will 
be bad enough having to tell them "That option is not available on this 
release" if they use CMD9 to see all of the parameters and want to try 
one of them.  In other words, why show them something they can not use.  
I think the parameters that are not available for a release will still 
show up in the help text (with appropriate release comments) when the 
customer displays the entire help text.  I haven't looked at that 
problem yet.

On 10/22/2010 12:43 PM, Albert York wrote:
> It seems to me the simplest solution is to have all of the parameters
> available on the command but have the command call a C/L program which
> determines which paramters to use and calls the API accordingly. You
> could issue an informational message 'Parameter xyz is not valid for
> this release - value ignored'.