NetView REXX trace output going to syslog
The 'TRACE A' REXX output is going to both netlog and syslog. Customer does not want to see it in SYSLOG and wishes to know how to disable that logging.
This is caused by the fact that the CLIST is running under an autotask that has a console assignment because it was started like this - 'autotask opid=auto55,console=*master *'
Here is what the NetView REXX manual says in this regard -
To test REXX automation command lists by tracing their execution, use the TRACE command. If your command list is being executed by a NetView automated operator (autotask), the result of SAY or TRACE is not visible unless the autotask is assigned an MVS console ID. The results are visible in the network log regardless of whether the autotask is assigned to a console.
Resolving the problem
Do not run clists you are tracing on autotasks used for console assignments. Customers can enter NetView command DISCONID to see if a task is used for console assignments, of the keyword *ANY* is shown or a MVS console name is listed in the output, for example:
CNM492I OPERATOR ID CONSOLE ID CONSOLE NAME
CNM492I ----------- ---------- ------------
CNM492I AUTCON 0 * *ANY*
CNM492I AUTCON01 EXTENDED * sysnameHMC
In this excerpt we can see task AUTCON is assigned *ANY* and task AUTCON01 is assigned to the MVS console representing the HMC on this system (ie. it represents a real external MVS console) so those 2 tasks should be exempt from running customer rexx or clist programs, particularly those that involve tracing.
|Systems and Asset Management||Tivoli NetView for z/OS|
NV NVz NVzOS
Translate this page: