RE: CHGJOB

["Popeil, Russ" <Russ.Popeil@xxxxxxxxx>]

Check out the article that Wayne Evans and I wrote in Midrange computing 
Midrange Computing October 1994
       Modifying OS/400 Commands 

Russ Popeil
IBM Certified Specialist - RPG Programmer & AS/400 Sales Associate 
Avnet Computer - Integrated Solutions. Bottom-Line Results.
Office: 516-677-9346, Fax: 516-677-0296, Beeper: 516-786-5846
eMail:  Russ.popeil@avnet.com
http://www.avnetcomputer.com



> -----Original Message-----
> From: Jewel, Jerry [SMTP:jerry.jewel@nissan-usa.com]
> Sent: Tuesday, June 02, 1998 3:00 PM
> To:   'MIDRANGE-L@midrange.com'
> Subject:      RE: CHGJOB
> 
> Eric,
> 
> Your solution can take a number of paths:
> 
> POLITICAL (THE-BIG-STICK):  Change the user's password to *NONE.
> Compose a polite but strongly-worded email on what you've done and why.
> Send it to the user; copy his/her manager, copy your help desk.  Reset
> the password the following day.
> 
> OBJECT AUTHORITY (THE-WHEEL-OF-AUTHORITY):  Play with object authority
> (to the job queue or CHGJOB command) and user special authority
> (*JOBCTL) if your current production security strategy makes this
> manageable.  [In many shops, unfortunately, *ALLOBJ authority has gotten
> away from reasonable use.]  Be careful, they need access to QINTER to
> start interactive jobs.  Also, your programmers, using brute force, may
> have imbedded CHGJOB's within the production CL's.
>  
> COMMAND VALIDITY CHECKER (THE-SUGAR-PILL):  Duplicate the CHGJOB command
> into a library higher than QSYS in the system library list.  Change
> VLDCKR parm of the duplicated command to point to a program of yours
> which forces *SAME or * into offending parms (if they are not
> QSYSOPR/QSECOFR or some other simple test).  This is a little tricky,
> finding which parm is which; RPG is more forgiving on number of parms
> passed.  I've done this in the past, to "quietly" ignore changes to
> TIMESLICE, JOBQ, RUNPTY, PURGE.  I believe a tech tip on this ran within
> the last year in News/400 or Midrange Computing magazines.
> 
> Regards,
> Jerry Jewel
> Better living through fine code and hot coffee!
> jerry.jewel.@nissan-usa.com
> ---------------------------------
> 
> > Recently users have discovered that they can move their batch jobs to 
> > QINTER.  This really degrades performance on an F35.  What is the best
> > way 
> > to keep users from moving their jobs to QINTER yet still allowing them
> > to 
> > move jobs to other jobqs.  Thanks in advance for any assistance.
> > 
> > Eric Kempter
> > 
> +---
> | 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
+---