RE: How NOT to use an API on a previous release

Doug,

I think you can use procedure pointers to dynamically call the QPMLPMGT service program procedures...

Search the archives for GETSPGMPTR.

hth,
Eric DeLong

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Doug Davie
Sent: Tuesday, April 29, 2008 10:31 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: How NOT to use an API on a previous release


In one of my RPG *MODULEs, I am using the API dlpar_get_info from the
service program QPMLPMGT to retrieve LPAR information.
This *MODULE is bound together with 5 other *MODULEs into my *PGM.
I display the LPAR information retrieved on the screen.

QPMLPMGT became available in V5R3, yet I must still support customers
on releases prior to that.
When my customer on V5R2 attempts to run this program, they receive:
CPD0192: Service program QPMLPMGT not found.

It seems that when the program is initialized, it recognizes right off
that QPMLPMGT is not available.
Is there a way to get it to not check until I need it?
For example, I thought of something like this:


D GetLparInfo PR 10I 0 EXTPROC('dlpar_get_info')
D Receiver 344
D Format 10I 0 Value
D RcvrLen 10I 0 Value

MONITOR;
RtnValue = GetLparInfo(Receiver:Format:RcvrLen);
ON-ERROR;
RtnValue = 0;
ENDMON;

If RtnValue > 0
....