We have a new Windows user app that is going to be scheduled and writes out thousands of lines that the support of the job says is not needed to keep (but the developers won't turn off........whatever)
Please advise how one would code an NT_job so that ENVAR STDOUT= and/or ENVAR STDERR= would go to NULL or NUL, (i.e. would just go off to never-never land and not be saved to the spool file)
And likewise if the syntax is different for Unix, how to code a UNIX_JOB so that ENVAR STDOUT= and/or ENVAR STDERR= would go to NULL or NUL, (i.e. would just go off to never-never land and not be saved to the spool file
Note, would like to know how to use this using ENVAR STDOUT/STDERR in the job def....not how to do this inside a bat file or Unix script
Release : 11.3
Component : CA WORKLOAD AUTOMATION AGENTS
You can code the ENVAR STDOUT in the NT_JOB and UNIX_JOB as below;
NT_JOB:
ENVAR STDOUT="> NUL"
UNIX_JOB:
ENVAR STDOUT=/dev/null