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

Oh. Sorry. This invalidates my answer too.

One thing you might try, is to have a parameter that specifies the OS
release... and then reference that value in PMTCTL. Then you could
CHGCMDDFT at installation time and/or when the OS version is determined to
change.

But I'm not sure how you would hide that parameter from the user, assuming
that's important to you.

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"Some see the problem in every opportunity, some see the opportunity in
every problem."
-- Kevin Cowling

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.;-)

--
Dave Murvin

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.