RE: Suppression of joblogs

["phil Kestenbaum" <pkestenbaum@xxxxxxxxx>]

You can do so on the Job Description for the user.

Message logging:                                                
  Level  . . . . . . . . . . . . . . . . . . . . :   4          
  Severity . . . . . . . . . . . . . . . . . . . :   40          
  Text . . . . . . . . . . . . . . . . . . . . . :   *NOLIST    
Log CL program commands  . . . . . . . . . . . . :   *NO        

severity 0 means that a job log will be generated for everything, you can push 
this Severity to 40, it will cut down on the job log. Higher than 40 and you 
can miss some details on problem (A job Abend is bet. 50 -60). If you 
absolutely want nothing, put 99 in Severity.

*NOLIST is tied to the Severity. Won't generate a list unless 40 or higher

-----Original Message-----
From: James H H Lampert [mailto:jamesl@xxxxxxxxxxx]
Sent: Friday, June 17, 2005 2:12 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Suppression of joblogs


We will soon have a situation in which an emulation 
session will be abended (through disconnection) more often 
than it will be canonically signed off. It will be one 
particular user profile (limited, ATTN-disabled, and 
SysRq-disabled) involved, on one particular device 
description series.

The box involved is on V4R5.

Is there a way to gimmick either the user profile or the 
job description so that disconnecting the emulator won't 
produce a spooled joblog? Preferably without eliminating 
any possibility of getting a joblog from an application 
crash?

--
JHHL