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

You mean like this?

d api_program PR extpgm('API_NAME')
d objname 10 Const
d objlibr 10 Const
* Added at V5R2
d objtype 10 Const Options(*NoPass)
* Added at V5R3
d errstr LikeDS(errorStruct)
d Options(*VarSize: *NoPass)
* Added at i6.1
D extension 20 Const Options(*NoPass)

D currentVRM S 6

// If currentVRM = VxRyMz

Select ;
When currentVRM >= CON_I6_1 ;
api_program(parm1: parm2: type: errStr: ext) ;
When currentVRM >= CON_V5R3 ;
api_program(parm1: parm2: type: errStr) ;
When currentVRM >= CON_V5R2 ;
api_program(parm1: parm2: type) ;
Other ;
api_program(parm1: parm2) ;
EndSL ;

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"The direct use of force is such a poor solution to any problem, it is
generally employed only by small children and large nations."
-- David Friedman

I am looking at creating a command that calls an API that uses
different
(additional) parms over various releases. What I would like to do is
create a command that uses this API and will run on multiple releases
(starting at V5r2), but still be able to use the new options that were
added in later releases.

I could make the command dumb and only use the options that were
available in V5R2, but I don't really want to do that.

About all I can come up with so far is to create different versions of
the command (including help text, command processor and validity
checker) for each release where the API parms were enhanced. Then when
the "application" is restored to a machine, determine the current
release for that machine and do a bunch of renames to get the latest
version that would run on that release during the post install process

This sounds doable, but also sounds messy.

Does anyone have any other options or ideas?

Thanks

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