HP Alpha Server

HP Alpha Server
June 6, 2008 at 09:23:42
Specs: Open//VMS V7.3-2 , EV67
The command "set noverify" I have at the beginning of a script outputs to the target file along with the intended output when it is called from another script. But, when I run the script itself as @CURR_EPOCH_TIME.COM
it doesn't do it. The code for calling the script is:
$ @CURR_EPOCH_TIME.COM/output = TARGET.FILE
But, when I TYPE the target file I get:
$ type TARGET.FILE
$ set noverify
1212716451

But, when I run the script manually I get:
$ @CURR_EPOCH_TIME.COM
1212716435

Set Noverify is not there.
Can anyone explain why this happens? I don't want "set noverify" in the target file.
I hope I'm being clear.
Thanks alot.
Mike

Michael Ledesma
System Administrator
Petro Heating Oil Svc's


See More: HP Alpha Server

Report •


#1
June 6, 2008 at 12:21:08
Hi Michael,

I simulated your procedure to try to reproduce your situation. Whether or not the "set noverify" is shown in the target file or at the terminal is dependent on whether verify is already on or off before you run the procedure.

Example:

$ ty CURR_EPOCH_TIME.COM
$ set noverify
$ run calc_epoch.exe
$ exit

$ @CURR_EPOCH_TIME.COM/output=TARGET.FILE
$ type TARGET.FILE
1212716435
$ set verify
$ @CURR_EPOCH_TIME.COM/output=TARGET.FILE
$ type TARGET.FILE
$ set noverify
1212716435
$ set noverify
$ @CURR_EPOCH_TIME.COM/output=TARGET.FILE
$ type TARGET.FILE
1212716435
$

To get a target file with only the returned numeric value, I would change standard output inside the DCL script for only that command.

For Example:

$ type CURR_EPOCH_TIME.COM
$ assign/user_mode target.file sys$output
$ run calc_epoch.exe
$ exit

$ @CURR_EPOCH_TIME.COM
$ type target.file
1212716435

Cheers!

Keith Cayemberg


Report •

#2
June 9, 2008 at 07:22:15
There is one trick to silently switch off verification without displaying the SET NOVERIFY command in case it was enabled:
Start the file with a comment line like this:
$! 'f$verify(0)'
exploiting the fact that symbol substitution takes place also in DCL comment lines.

But in Your particular case Keith is right, the output file should be kept separate from DCL output.


Report •

#3
June 9, 2008 at 08:24:27
Excellent! Thanks guys!
Mike

Michael Ledesma
System Administrator
Petro Heating Oil Svc's


Report •

Related Solutions


Ask Question