+ Reply to Thread
Results 1 to 8 of 8

Thread: Joblog stop already

  1. #1
    Guest.Visitor Guest

    Default Joblog stop already

    The AS400 I am using is V3R2. It was set up with job logs, being sent to the Queue QEZJOBLOG and showing up in users' spooled files, quite a few years ago. I would rather not have people see the job logs mixed in with their print jobs. Instead I would specifically have to do a wrkusrjob to see joblogs. I can't seem to find a manual, which specifies how to do this and I have seen it done on another job. Anyone have any ideas.

  2. #2
    Guest.Visitor Guest

    Default Joblog stop already

    You might check out the SPLFOWN parameter of the CHGPRTF command (CRTPRTF, too, I'm sure). It doesn't allow you to specify a specific user profile, so you might want to experiment with Group Profiles. If you go this route and get it working, post it here; I'd be interested. How do your users look at their spooled files: WRKSPLF, WRKUSRJOB, WRKSMBJOB, WRKOUTQ? Some, or all of these? I know of no simple property you can change to make this happen, except possibly the SPLFOWN (which I've never used, just discovered in response to your question). One way to minimize the confusion is to have someone in I.S. clean out the QEZJOBLOG output queue daily, reviewing job logs for possible problems and, if none, delete them. Or, if you don't care about reviewing them, just schedule a job to clear that output queue every night, just before any nightly processing begins (so you still have joblogs from nightly processing, if you need them). If you need to look into a job log, it's there for the day, but it's automatically cleared out overnight; you can always move it to another output queue if you don't want it cleared. Users then would only see a few, if any, QPJOBLOG spooled files in with there.

  3. #3
    Guest.Visitor Guest

    Default Joblog stop already

    you can use WRKSPLF ASTLVL(*BASIC) or press F21 from WRKSPLF if already available in V3R2

  4. #4
    Guest.Visitor Guest

    Default Joblog stop already

    Setting the assistance level to *BASIC for users, did exactly what I wanted. WRKSPLF hides the joblog, wrkoutq allows you to work with them if you have authority. I guess the most obvious, is the first over looked. Thanks for the help.

  5. #5
    Guest.Visitor Guest

    Default Joblog stop already

    Ahh, so simple. I'll remember that one, thanks.

  6. #6
    Guest.Visitor Guest

    Default Joblog stop already

    Another way, if you want to separate them out like we do. Every day we run a command the does a chgprtf prtf(qpjoblog) outq(jlogddd) ddd is day of week. Then all job logs for monday go in jlogmon, etc. When the user looks are their default outq they then don't see them.

  7. #7
    Guest.Visitor Guest

    Default Joblog stop already

    what is the command to change this??

  8. #8
    Guest.Visitor Guest

    Default Joblog stop already

    LaRissa ChgUsrPrf usrprf(profilename) astlvl(*basic) For mass changes, put a '2' next to each profile you wish to change on the WrkUsrPrf screen and on the command line put astlvl(*basic) . Bill

+ Reply to Thread

Similar Threads

  1. Replies: 2
    Last Post: 12-03-2008, 05:45 PM
  2. JOBLOG PENDING message
    By J.Pluta in forum General
    Replies: 9
    Last Post: 08-15-2007, 08:42 AM
  3. *INLR causing joblog to wrap
    By scatterload in forum RPG
    Replies: 7
    Last Post: 04-26-2007, 01:05 PM
  4. job stuck with status 'JOBLOG PENDING'
    By GlenKerner in forum General
    Replies: 1
    Last Post: 10-26-2004, 10:53 AM
  5. Joblog on User Outq
    By Guest.Visitor in forum Application Software
    Replies: 3
    Last Post: 10-02-2000, 07:08 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts