RE: Losing Authority to a file in Batch -- MIDRANGE-L

Subject: RE: Losing Authority to a file in Batch
From: Jim Damato <jdamato@xxxxxxxxxxxxxxxxx>
Date: Mon, 26 Jan 2004 12:53:26 -0600
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/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Have you ever had to expose your system to a security audit?  Programs
compiled as USRPRF(*OWNER) are among the first things to go.

-Jim

James P. Damato
Manager - Technical Administration
Dollar General Corporation
<mailto:jdamato@xxxxxxxxxxxxxxxxx>



-----Original Message-----
From: Malchow, Grizzly [mailto:GMalchow@xxxxxxxxxxxxxxxxxxxxx]
Sent: Friday, January 23, 2004 12:58 PM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: Losing Authority to a file in Batch


Apparently my user profile has been changed. Whenever I used to compile
programs, the user ID default was *OWNER. Now I noticed that the default
is *USER. I recompiled with *owner and that solved my problems.
Thanks everyone.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: Losing Authority to a file in Batch , Al Barsa
RE: Losing Authority to a file in Batch , rob

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.