Re: WRKJOBSCHDE command lock -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: Re: WRKJOBSCHDE command lock
From: fbocch2595@xxxxxxx
Date: Wed, 15 Mar 2006 14:57:28 -0500
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>

Rob, so by securing QDFTJOBSCD noone will able to update the job scheduler 
except allobj folks or those authorized to QDFTJOBSCD?  There's no downside to 
doing this?   

-----Original Message-----
From: rob@xxxxxxxxx
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Sent: Tue, 14 Mar 2006 11:29:26 -0500
Subject: RE: WRKJOBSCHDE command lock

Once again, forget about securing the interface, and secure the object 
instead.  WRKOBJ *ALL *JOBSCD
That way will cover WRKJOBSCDE, ADDJOBSCDE, various job schedule entry 
api's, etc.

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: WRKJOBSCHDE command lock , rob

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