RE: Why is joblog no complete?

I haven't been able to find clear definition on LOGLMT.  From what I can
find LOGLMT looks like it's not a characteristic of a job -- it's a
characteristic of a job that is ending.  The only references I can find for
LOGLMT are for ENDJOB and ENDPJ.

Are you sure the job wasn't canceled?  If you look in the DSPLOG history
log, what is the end code on the "Job nnnnnn/uuuuuuu/jjjjjjj ended..."
(CPF1164) message?

-Jim



-----Original Message-----
From: John Allen [mailto:jallen@xxxxxxxxxxx]
Sent: Saturday, August 16, 2003 12:45 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Why is joblog no complete?



When I prompt on the ENDJOB command I get the following:
                                                                       
Job name . . . . . . . . . . . .                 Name                  
  User . . . . . . . . . . . . .                 Name                  
  Number . . . . . . . . . . . .                 000000-999999         
How to end . . . . . . . . . . .   *CNTRLD       *CNTRLD, *IMMED       
Delay time, if *CNTRLD . . . . .   30            Seconds               
Delete spooled files . . . . . .   *NO           *NO, *YES             
Maximum log entries  . . . . . .   *SAME         Number, *SAME, *NOMAX 
Additional interactive jobs  . .   *NONE         *NONE, *GRPJOB, *ALL  
                                                                       
How does one go about finding out what the actual parameter value is when it
shows *SAME when prompted? (I was signed on as QSECOFR when I prompted on
the ENDJOB command.)

I have looked at other batch jobs and I see much longer joblogs

When a batch end with LR on and Return what determines the LOGLMT?
I am not using ENDJOB to end the batch job