Re: Getting the library name from a CL program

Eric,

I run it at 40.

IBM actually came out with some of the materialize invocation info
instructions in V4R1 so that you could get the invocation stack info safely.
Before that and before ile, techniques such as walking the PASA ( auto
storage ) space of a job were used.

-Steve


----- Original Message -----
From: "DeLong, Eric" <EDeLong@Sallybeauty.com>
To: <midrange-l@midrange.com>
Sent: Thursday, November 15, 2001 2:08 PM
Subject: RE: Getting the library name from a CL program


> Have you gotten this to work at all QSECURITY levels?  I believe this MI
> technique will fail for seclvl >= 40.
>
> Eric DeLong
> Sally Beauty Company
> MIS-Sr. Programmer/Analyst
> 940-898-7863 or ext. 1863
>
>
>
> -----Original Message-----
> From: Steve Richter [mailto:srichter@AutoCoder.com]
> Sent: Thursday, November 15, 2001 11:29 AM
> To: midrange-l@midrange.com
> Subject: Re: Getting the library name from a CL program
>
>
>
> ----- 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
>
>
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>