Re: Suppression of joblogs

["David A Parnin" <daparnin@xxxxxxxxxxxxxxxxxx>]

For either a CHGJOB or CHGJOBD you could change the text option of the LOG
parameter to be *NOLIST then you will only get a job long if the job ends
abnormally.  You can specify the level and severity.

Dave Parnin
Nishikawa Standard Company
Topeka, IN  46571
daparnin@xxxxxxxxxxxxxxxxxx




                                                                                
                              
                      rob@xxxxxxxxx                                             
                              
                                               To:       
MIDRANGE-L@xxxxxxxxxxxx@SMTP@CTB                     
                      12/18/2003 03:01         cc:                              
                              
                      PM                       Subject:  Suppression of joblogs 
                              
                      Please respond to                                         
                              
                      Midrange Systems                                          
                              
                      Technical                                                 
                              
                      Discussion                                                
                              
                      <midrange-l@midra                                         
                              
                      nge.com>                                                  
                              
                                                                                
                              
                                                                                
                              



When a job completes without any hassles how do you prevent it from
generating a joblog?  We already have them go to a nonprinting output
queue.  However we don't want them to generate at all.

All messages in the joblog at sev 00.
The CPI1125 job submitted message has...LOG(4 10 *SECLVL) LOGCLPGM(*NO)...

For testing purposes I tried the following
SBMJOB CMD(DSPOBJD OBJ(ROB) OBJTYPE(*USRPRF) OUTPUT(*PRINT))
       JOB(R4)
       LOG(1 10 *SECLVL)
       LOGCLPGM(*NO)
That, and the following 3 options, all generated joblogs.
       LOG(2 10 *SECLVL)
       LOG(3 10 *SECLVL)
       LOG(4 10 *SECLVL)

The following option
       LOG(0 10 *SECLVL)
does not generate a joblog.  Even if I attempt to induce an error by
introducing an error, like this nonexistant user.
SBMJOB CMD(DSPOBJD OBJ(ROBXTYH) OBJTYPE(*USRPRF) OUTPUT(*PRINT))
       JOB(R5)
       LOG(0 00 *SECLVL)
       LOGCLPGM(*NO)
"Job 700333/ROB/R5 ended abnormally." appears in DSPMSG ROB.  However
WRKJOB 700333/ROB/R5 results in
Job 700333/ROB/R5 not found.

I wouldn't mind getting a joblog.  However only when the joblog contains a
message with a severity greater than or equal of the one expressed.

Rob Berendt
--
"All creatures will make merry... under pain of death."
-Ming the Merciless (Flash Gordon)
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.