× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. March 2006

Re: WRKJOBSCHDE command lock

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.

This thread ...
Follow-Ups:
Replies:
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.