Re: QRPLOBJ

Folks,

You have to remember WHY QRPLOBJ even exists. This is key to the whole
thing.

If you delete the program first then everyone who has ran it, and may call
it again, will abort with a nasty message. The job keeps a pointer to
that object. When the object is moved to QRPLOBJ then the pointer gets
changed to that object. If you just delete it you'll get some nasty
pointer not found type message.

What stops the pointer from going to QRPLOBJ? Well, restarting the job
for one.

You have to ask yourself what solution you're willing to take:
- accept the current security failures that the OP was trying to work
around.
- accept the nasty message which may occur when the object is deleted
- modify the security model to accept QRPLOBJ
- severely restrict implementing changes, even those which may fix
critical errors, to system outage times to avoid calls to QRPLOBJ and the
alternative nasty message.
- Rewrite the system that if the security model detects QRPLOBJ then the
called program, and the calling program, work out how to use the new model
(perhaps some combo of LR, etc?).



Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Alan Campin <alan0307d@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 07/12/2017 12:39 PM
Subject: Re: QRPLOBJ
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



What happens if you delete the program instead of using QRPLOBJ?

*_>_O DLTPGM PGM(@OBJLIB/@OBJNAM)
*_>_R CRTBNDRPG PGM(@OBJLIB/@OBJNAME
*_>_C SRCFIL(@SRCLIB/@SRCFIL) SRCMBR(@SRCMBR)



On Wed, Jul 12, 2017 at 6:55 AM, Glenn Gundermann <
glenn.gundermann@xxxxxxxxx> wrote:

Instead of leaving it to the system to move the existing program to
QRPLOBJ, you could have the promotion program do it as part of the

process:

- Delete any older versions of QRPLOBJ/PGM_A
- Move the current version <lib>/PGM_A to QRPLOBJ
- Compile PGM_A


Yours truly,

Glenn Gundermann
Email: glenn.gundermann@xxxxxxxxx
Work: (905) 486-1162 x 239
Cell: (416) 317-3144


On 12 July 2017 at 08:15, Alan Shore <ashore@xxxxxxxx> wrote:

Hi Glenn
I can answer this one - I had the same situation many moons ago, the

first

place that I worked on an AS/400
The program that is moved over to RPLLIB may not keep the same name

These are just SOME of the program names in our QRPLOBJ
QDABCD8901
QDABCFE7E5
QDABD5FFAB
QDABD5F3AA
QDABD6C605
QDABD62C2B
QDABFB6932
QDABF4603B

However - I just noticed that the text of those programs are the

library

name and program name of the original program
Maybe the text can be used if the library name is QRPLOBJ


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
Glenn Gundermann
Sent: Wednesday, July 12, 2017 8:08 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: QRPLOBJ

Hi Gad,

How about adding an entry for QRPLOBJ/PGM_A as part of your promotion
procedure.


Yours truly,

Glenn Gundermann
Email: glenn.gundermann@xxxxxxxxx
Work: (905) 486-1162 x 239
Cell: (416) 317-3144


On 12 July 2017 at 06:23, Gad Miron <gadmiron@xxxxxxxxx> wrote:

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
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)

mailing

list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please

take

a moment to review the archives at
http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our

affiliate

link: http://amzn.to/2dEadiD

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take

a

moment to review the archives at

http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD



--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD