Yea, well there are any number of similar issues that arise when you cut and paste. I tend to use RDi snippets now to insert my boilerplate. It lets me set replacement values in the process of inserting. Program name is one of them, and that is replaced with the new program name wherever it appears in the snippet. It is far more robust than just copy and modify until it works.
Mark Murphy
Atlas Data Systems
mmurphy@xxxxxxxxxxxxxxx
-----Alan Shore <ashore@xxxxxxxx> wrote: -----
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
From: Alan Shore <ashore@xxxxxxxx>
Date: 07/13/2017 08:08AM
Subject: RE: QRPLOBJ
That's a good idea - and I have used it in the past - but programs tend to be copied to create other programs and these type of fields are sometimes forgotten to be changed, so the program name and this field are out of sync
THAT came back and bit me on you know where - which was rough as I was not the person creating the new program
AND
It was documented ALL OVER the place of what to do in those situations
Alan Shore
E-mail : ASHORE@xxxxxxxx
Phone [O] : (631) 200-5019
Phone [C] : (631) 880-8640
'If you're going through hell, keep going.'
Winston Churchill
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mark Murphy/STAR BASE Consulting Inc.
Sent: Thursday, July 13, 2017 8:03 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: QRPLOBJ
Sounds like you are using the PSDS to retrieve the program name to pass to the authority program. Instead just use a constant that you define in the program. The parameter value does not change now when you are calling from QRPLOBJ.
Mark Murphy
Atlas Data Systems
mmurphy@xxxxxxxxxxxxxxx
-----Gad Miron <gadmiron@xxxxxxxxx> wrote: -----
To: midrange-l@xxxxxxxxxxxx
From: Gad Miron <gadmiron@xxxxxxxxx>
Date: 07/12/2017 06:23AM
Subject: QRPLOBJ
Hello guys
Need some help with a QRPLOBJ issue
We have here a (admittedly primitive) small home grown authorization system
where users are authorized to certain PGMs (and to PGM's features) in
certain Libraries.
Like:User Bob is authorized to LIB1/PGM_A
this system is implemented by having each PGM call (in *INZSR) a certain
authority checking program (passing it's *PSSR's User, PGM and Library)
that returns a pass/fail indication
This works fine until some programmer compiles a PGM while it is in use by
some user.
The compile replaces the PGM and moves the original PGM obj to QRPLOBJ
The scenario is as follows:
User has authority to LIB1/PGM_A
PGM_B calls PGM_A
PGM_A checks authority of user to LIB1/PGM_A – User passes the check.
LIB1/PGM_A is compiled. PGM_A in LIB1 is replaced, original PGM_A is
moved to QRPLOBJ
PGM_A returns to caller (PGM_B)
PGM_B (re)calls PGM_A
PGM_A in QRPLOBJ gets called.
PGM_A checks authority of user to QRPLOBJ/PGM_A – User fails the check.
Any idea how to circumvent the issue?
TIA
Gad
midrange.com
