Re: Problems with authority... -- MIDRANGE-L

>  From:    clewis@iquest.net (Chuck Lewis)
>  
>  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

I do not know if this helps or not, but I have recently been experimenting 
with multiple JOBQ in the same sub system ... we have identified some jobs as 
taking much longer to execute than the mob, so the goal is to have QBATCH 
JOBQ to be the default for the fast jobs & QBATCH2 is in the SBMJOB CL for 
those jobs we have identified as being the slow pokes ... it seems that we 
not hurting from having small number of JOBQ running at same time ... one 
doing one quick job right after another & other doing 5 minutes on this job 
10 minutes on that job ... so long as they are independent & can in fact be 
separated.

You have to assign new JOBQ to a SUB SYSTEM or jobs in that JOBQ won't do 
anything.

There is stuff with CHGJOB that can control things for a user such that you 
do not normally want a user to be mucking with because it can mess up the 
applicatiion, so we have created CL in which off of a menu the user can 
change ONLY the stuff we want them to be able to change ... this is one way 
you can let a user have a different default JOBQ than some other user.  Of 
course there are scenarios where you want several people doing related stuff 
using the same JOBQ.

Our ERP CLs that SBMJOB use a data area pre-seeded by a user menu option with 
stuff like put this JOB on HOLD, put this report on HOLD, etc.  I recently 
been testing some software where I put my SBMJOBs automatically on hold, then 
before I release them I CHGJOB to increase the logging.

Basically with our ERP everyone is using the same JOBD but we all can have 
different JOBQ ... I have not really dug into the code to figure out how that 
is done, other than CL populating some variables that I would hate to mess 
with on a global level.


MacWheel99@aol.com (Alister Wm Macintyre) (Al Mac)
AS/400 Data Manager & Programmer for BPCS 405 CD Rel-02 mixed mode (twinax 
interactive & batch) @ http://www.cen-elec.com Central Industries of 
Indiana--->Quality manufacturer of wire harnesses and electrical 
sub-assemblies - fax # 812-424-6838

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