× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hello,

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


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.