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

Hi guys,

To stop the display of the OS level parm in the prompting of the command, you could do something like this:

PARM KWD(OSLEVEL) TYPE(*CHAR) LEN(4) CONSTANT('THIS') MIN(1) MAX(1)

Then:
1) OSLEVEL would never show in the prompting
2) THIS would be passed to the CPP for OSLEVEL parm

I am not sure how this would affect the rest of your requirements.

Regards,

Kevin Wright

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Dave Murvin
Sent: Wednesday, 20 October 2010 11:02 AM
To: Midrange Systems Technical Discussion
Subject: Re: How to call API with different parms over different
releases


Thanks Mark,

I will take another look at the prompt override program. I
was hoping
that I did not have to display the OS level as a parm, but I
may have to
go with this.

On the renaming the different versions of the command, I guess I was
thinking that they would just reinstall the licensed program
when they
changed the OS release and the install process would fix
everything. I
now see that this is a bad idea and I had just not thought
through the
process far enough to see the problem.

I already have a service program for the QSZRTVPR API, but have not
checked out the QSZCHKTG API before.

On 10/19/2010 5:04 PM, Mark S. Waterbury wrote:

I would*not* go with the idea of installing (or renaming) different
versions of the command, because then what would happen

when the user or

customer upgrades to a newer version of the OS, some

time_after_ they

have installed your command? *:-o*

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