|
The export procedure of the service program I mentioned is used by a never ending job that repeatedly calling it every 60 seconds. It cause the QRPLOBJ lib to max out, which cause this job and other jobs that need QRPLOBJ start to fail. I found several other programs that is doing the same thing to create the userspace. Instead of changing all those programs, I just wonder changing QALWUSRDMN system value would be a better approach (Doesn't sound like it at the moment). It makes sense if said I move a program object to production lib and system auto put the existing one to QRPLOBJ because other job is using the current object. It just doesn't make sense to do this for QTEMP library (May be IBM is doing this for thread safe programming language like c). -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx Sent: Monday, March 13, 2006 7:11 AM To: Midrange Systems Technical Discussion Subject: RE: What is the effect of removing *ALL from system value QALWUSRDMN? Lim, I'm kinda curious. I still delete user spaces before reusing them. Someone on this list was suggesting that I use the option on QUSCRTUS to replace it if it already exists. Made sense to me, but it won't if I am going to start experiencing what you are. I still wonder what security risk they were attempting to guard against. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com "Lim Hock-Chai" <Lim.Hock-Chai@xxxxxxxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 03/10/2006 05:12 PM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> cc Fax to Subject RE: What is the effect of removing *ALL from system value QALWUSRDMN? The program is using QUSPTRUS to get the user space pointer. In that case removing the *ALL entry is not going to work for me. I just have to change the program to delete the existing user space in QTEMP before create it again. It just seems weird for system to move the existing object in QTEMP to QRPLOBJ lib. What is the purpose of this action? -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx Sent: Friday, March 10, 2006 3:48 PM To: Midrange Systems Technical Discussion Subject: Re: What is the effect of removing *ALL from system value QALWUSRDMN? I am not sure what security risk they are trying to guard against. I do know that if you create a user space in a library that is not in this system value, then you cannot use QUSPTRUS on it. You would have to use QUSRTVUS. Once you get over pointer phobia and use QUSPTRUS one would never go back to QUSRTVUS. Using QUSRTVUS makes about as much sense as if IBM dropped the ADD and the + capabilities in RPG and required you to call some api passing several parameters like factor1, factor2, result, and the error code data structure. Rob Berendt --
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.