× 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.


  • Subject: Re: Problems with authority...
  • From: Chuck Lewis <clewis@xxxxxxxxxx>
  • Date: Thu, 22 Mar 2001 16:12:33 -0500

ALAN !!

Bingo - you are so right and I knew that and TOTALLY spaced it (*JOBCTL) !

Thanks !

Chuck

alan shore wrote:

> The problem is not so much as having the correct authority to QBATCH, but the 
>user needs to have *JOBCTL (Job Control authority) within the profiles special 
>authority parameter. QSECOFR should definitely have this. Check your test 
>profile for this. NOTE a *USER profile will NOT be given this automatically.(I 
>believe)
>
> >>> Chuck Lewis <clewis@iquest.net> 03/22/01 02:46PM >>>
> Hi Folks,
>
> I'm stuck on this one...
>
> We have a user that needs to be able to hold and release jobq QBATCH (so
> run jobs from a 3rd part package that submit to QBATCH and then move
> them to another jobq so they don't hold other stuff up. No way to change
> a jobd or anything because they all use the same one...).
>
> So what I did was set up a test User Profile that mirrors this person
> and have been playing around with it. I have Limited Capabilities *YES
> (I know...) so the command line can be used. I then tried hldjobq qbatch
> and of course got CPF2207 - Not authorized to use object QBATCH in
> library QGPL type *JOBQ.
>
> So I did a GRTOBJAUT OBJ(QGPL/QBATCH) OBJTYPE(*JOBQ) USER("Test
> profile") AUT(*ALL).
>
> I signed on as the "Test profile" and STILL could not do this (same
> error) - anyone know why this would happen ? I've got this working fine
> via a CL application for another user but I the CL is compiled as
> Owner(QSECOFR)...
>
> Thanks !
>
> Chuck
>
> +---
> | 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
> +---
>
> +---
> | 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
> +---

+---
| 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 ...

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.