Re: CPF1340

Okay, I'm probably going to try this on Monday on our development machine.  At the end of the day, what it really does is stop the materialization of the joblog into the QEZJOBLOG output queue (or wherever your system sends its joblogs).  The data is still there, just not as a spooled file, until you clean it up.

Quick side question: what's the cycle to get rid of a single job in PND?  Normally I'd delete the joblog and job would go away. Since there is no joblog, is there another technique?

Yes, I agree that JOB_INFO should show PND.  The SQL services while potentially very useful seem to me to be less stable than the rest of the OS.  We have an outstanding issue with 7.3 where SYSTRIGGER shows phantom trigger entries.  IBM took all our information including an object dump and hasn't responded in over a week.

Yes those jobs stay in the system.
I just signed on to a new 5250 session.
I entered in one command: SIGNOFF *LIST
I signed back on. That other job is still there.
Status of job . . . . . . . . . . . . . . . : JOBLOG PENDING
4. Work with spooled files
(No spooled output files)
10. Display job log, if active, on job queue, or pending
5>> signoff *list

They get cleaned up just the same with GO CLEANUP "Job logs and other
system output"

The only thing I don't like is
SELECT *
FROM TABLE(QSYS2.JOB_INFO(JOB_USER_FILTER => 'ROB')) X
WHERE JOB_NAME LIKE '%ROBHQ1%';
shows JOB_STATUS as 'OUTQ'.

Been running this way for a LONG time.
Had this "former" coworker who liked to show the end users CLROUTQ
QEZJOBLOG...
He was #1 on the day our department had a head count reduction.

Rob Berendt