Re: Getting the library name from a CL program

["Steve Richter" <srichter@xxxxxxxxxxxxx>]

----- Original Message -----
From: "Joe Pluta" <joepluta@PlutaBrothers.com>


> Here's a silly question.  I've always been able to get the library a
program
> was called from in RPG by using the program status data structure.  In a
C/S
> environment, this is really important, because it allows you to have
> multiple environments based on just the library you call your initial
> program from.

The MI way is to MATINVS, step back in the documented materialized template
to the call stack entry you want, get the system pointer to the invocation
entry pgm, then MATPTR the pgm sysp to get the name and context ( library )
of the pgm.  Not a far fetched as it might appear. And it is also a
documented method that will work from release to release.

How is the library used to control mult env?  Does a dtaara holding config
info provide more functionality?   Can you not rely on the libl throughout
the transaction because you are jumping the dtaq boundary to another job and
losing the libl of the client?

Steve Richter