RE: QSTRUPPGM issues (was: no subject) -- MIDRANGE-L

Subject: RE: QSTRUPPGM issues (was: no subject)
From: rob@xxxxxxxxx
Date: Thu, 18 Sep 2014 10:07:42 -0400
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Generic 'you should not be running jobs as qsecofr' instructions are
guidelines. Not hard and fast rules.
First, yes, running under a default profile causes issues. "Hey user
GENERIC has this file locked. Call them up and have them sign out."
But there are times when you need special authority. And, as far as I'm
concerned there's no difference in this rule between QSECOFR and a generic
user defined IQSECOFR.
The existing job I was trying to deal with was already running under a
generic profile, QPGMR.

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2025 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.