• Subject: System failure and recovery failure.
  • From: "David Morris" <dmorris@xxxxxxxxxxxxx>
  • Date: Mon, 17 Jan 2000 10:03:36 -0700

Group,

This weekend, a damaged object in QUSRSYS caused my system to IPL. During the 
IPL, a problem with the QPGMR profile prevented the system from coming up 
properly. 
I traced the problem back to the QPGMR autostart jobs which all failed.  After 
manually 
starting the servers etc. everything works normally.

It appears as though my QPGMR profile is not authorized to itself. Going 
through my 
audit journal, I cannot see where QPGMR's authority to its profile has ever 
been changed.  
On my system, QPGMR is only used as a group profile and has no password.  When 
my 
system failed, QPGMR was *EXCLUDE to QPGMR *USRPRF. I granted all except exist, 
alter and reference.  QPGMR still could not submit a job. I found two 
work-arounds, neither 
satisfactory.  The first was to grant QPGMR *ALLOBJ, the second was to grant 
*PUBLIC 
*USE to QPGMR.

Because I have not IPL'd since applying a new CUM and PTF's in December, I have 
quite a bit of history to wade through (note to self; IPL at least weekly). 
Does anyone have 
a clue what I should be looking for? At this point, I am considering 
re-creating the QPGMR 
profile.

Thanks,

David Morris

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.