Re: Infoprint Server

["Buddy McClean" <Buddy.McClean@xxxxxxxxxxxx>]

I adjusted the log values for all 3. No trouble with restarting the job. The writer stops a dozen times a day already. 
Thanks 

> > > Sam_L <lennon_s_j@xxxxxxxxxxx> 4/9/2018 1:26 PM >>>
I'm doing this from memory and don't have access to experiment...

After you've changed logging on the writer and job, make sure you run 
your processing again, because I don't think the logging change will 
change anything that already exists in the log.

And make sure you are looking at the correct writer and job.  Seem to 
recollect that there were three jobs associated with the process, one of 
them being the writer, and one of the other two never showed anything 
useful.

Sam



On 4/9/2018 1:16 PM, Buddy McClean wrote:
> Thanks Sam
>   
> I have changed the logging for the writer. I changed the job description for the jobs. So far I can't see any more messages than before I changed it. I will keep searching.
>
>
> > > > Sam_L <lennon_s_j@xxxxxxxxxxx> 4/6/2018 3:08 PM >>>
> That's virtually no logging. You need to work with the job and change it
> to LOG(4 00 *SECLVL).
> And change the writer job too.  One or the other should then provided
> some more useful error or warning message.
>
> Sam
>
> On 4/5/2018 5:02 PM, Buddy McClean wrote:
> > Thanks Sam,
> >    
> > When I look at the BCH job for the particular printer under QSPL using WRKACTJOB, the logging is at level-4 Severity-0 Text-*NOLIST.
> > Doing a 5 and 10 to view job log yields nothing that indicates error.
> >    
> > Looking at the message queue for the WTR job, I see the msg to notify me of incomplete print ( CPF3422 and 3433 ), but the possible causes don't seem applicable and pretty vague.
> >