[Info-vax] Reopen OPERATOR.LOG from batch?

[Bob Gezelter]

On Thursday, September 5, 2019 at 9:33:23 AM UTC-4, bill... at navistar.com wrote:
> On Thursday, September 5, 2019 at 7:55:45 AM UTC-5, Jan-Erik Söderholm wrote:
> > Hi.
> > 
> > The online HELP for REPLY/LOG says:
> > 
> > "The current terminal must be enabled as an operator terminal."
> > 
> > And HELP for REPLY/ENABLE says:
> > 
> > "The /ENABLE qualifier cannot be entered from a batch job."
> > 
> > So then, how to close/reopen OPERATOR.LOG from a batch job?
> > 
> > Jan-Erik.
> 
> I rename, close, and archive the OPERATOR.LOG files on our clusters daily from a single batch job that uses SYSMAN to execute a procedure on all of the cluster members.  This code snippet is basically what you need.
> 
> $       define /user SYS$COMMAND OPA0:
> $       reply/enable
> $       define /user SYS$COMMAND OPA0:
> $       reply /log      ! create the new log file

Jan-Erik,

To understand why the DEFINE/USER, place a SHOW LOGICAL SYS$COMMAND in place of the REPLY commands, to wit:

$       define /user SYS$COMMAND OPA0:
$       show logical sys$command

Check the output. Then comment out the DEFINE command and repeat. The difference should be obvious (hint: do a SHOW DEVICE/FULL on two devices.)

- Bob Gezelter, http://www.rlgsc.com