|
Perfect! Thanks a lot: I changed the ownership CHGOBJOWN to QSECOFR and did a CHGPGM *USRPRF *OWNER. It works perfectly well. One more question the Attribute Routing Data in the old user profile is PGMR04 with no request data. I could find a routing entry in subsystem INTER0 for program QCMD having compare value as PGMR04. My question is can I use the same routing data in the new production support job description? and what significance does this attribute have?? Thanks again, Sachin -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Donald Whittaker Sent: Wednesday, January 19, 2005 5:59 PM To: Midrange Systems Technical Discussion Subject: Re: Production Support User Profiles.- Urgent The program that dumps may need to be created with an owner that has *ALLOBJ authority (which you seem to have done by using QSECOFR), and may also need to be created as USRPRF(*OWNER). Try checking that (via DSPPGM) to see how it is set. HTH, Don --- "Chaudhary, Sachin (GE Equipment Services, Consultant)" <sachin.chaudhary@xxxxxx> wrote: > Hi > I am in a fix right now regarding production support > user profiles. Due to absence of the security > officer, her backup asked me to create a new user > profile for production support. > > There already exists a user profile PRODSUPPRT. > I would mention that there is an initial program > associated to production support user profile and as > a process the initial program prompts for the > programmer's user id QPGMR#NXX , when this > programmer logs in to the PRODSUPPRT id it disables > this user profile QPGMR#NXX . > > In exit program of the SIGNOFF command of PRODSUPPRT > user id , this User profile is again enabled (when > this programmer signs off from PRODSUPPRT id). > > Now the programs dumps when one of the CL commands > is executed from the program: > 1. RTVUSRPRF > 2. CHGUSRPRF - to enable and disable user QPGMR#NXX > user profile while this user is logged into > PRODSUPPRT. > ---Error User Prodsupprt does not have authority to > CHGUSRPRF. > Also note that All programmer ids (QPGMR#NXX) and > PRODSUPPRT ids are a part of *PGMR group. > > I require something like PRODSUPPRT id of PGMR group > have authority to use and change (enable and > disable) all profiles of PGMR group only, which > should serve my purpose. > > The user profile PRODSUPPRT has a special authority > of *SPLCTL, and dump resolution says that special > authority *SECADM required for this. The strange > thing is that Sec. Officer bckp says she has not > changed the user profile and PRODSUPPRT was working > fine earlier. > > Also , I read in one of the sec. officer docs that > the initial program and its calling programs should > be compiled only with QSECOFR user id??? I dont know > why is this so, but still I did that, but pgm dumps > still?? > > Request your help. > Rgds, > Sachin > > -- > 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. > > __________________________________ Do you Yahoo!? Yahoo! Mail - You care about security. So do we. http://promotions.yahoo.com/new_mail -- 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.
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.