[Info-vax] turning verify on and off

[Jan-Erik Soderholm]

Phillip Helbig---undress to reply wrote 2013-02-03 14:54:
> In article <kelp3j$okb$1 at dont-email.me>, Stephen Hoffman
> <seaohveh at hoffmanlabs.invalid> writes:
>
>>> I have some batch jobs which constantly execute in a loop.
>>> Occasionally, I want to turn verify on for a while then turn it off
>>> without resubmitting the job, in order to test things.  What about
>>> procedures which call other procedures etc?  Obviously one needs
>>> something more refined than turning verify on or off in all the
>>> procedures at once.  I've thus come up with the following scheme.  I've
>>> stolen bits of it from other folks, but haven't seen one quite so
>>> complex as this.  The functionality should be obvious to DCL
>>> programmers.  I welcome comments for improving it.
>>
>> Are you seeking to add complexity to that verification procedure, or
>> are you looking for a simpler approach?
>
> Neither.  I'm just wondering if something could be done more elegantly.
>
>> If the latter, I rewrote
>> sys$manager:sylogin.template and a few other DCL procedures a while
>> back, and you can see the one-liner that I tend to use in that.  Stick
>> that line inside a loop, and you're off and verifying.
>
> Yes.  My procedure differs mainly in avoiding hard-coding the name of
> the logical and turning it on in some and off in others in a call tree.
>
>> If you want to add a somewhat more practical form of complexity to your
>> DCL, add the ability for the procedure to periodically checkpoint
>> itself, and to restart.  That helps with recovering state from a reboot
>> or crash or restart, too.  That also means your long-running procedure
>> can be force-exited or deleted, and then restarted how and as needed.
>> In a batch procedure, the SET RESTART_VALUE command can sometimes be
>> useful.  There are other ways to perform this checkpoint-restart, too.
>
> Yes, nice functionality, and I have used it, but it is essentially
> orthogonal to the verify question.
>

I've used RESTART_VALUE to get the current "phase" from a batch job.

box1> type a.com
$ set restart_value = "Phase_1"
$ wait 00:10:00

box1> subm a
Job A (queue SYS$BATCH, entry 16) started on SYS$BATCH

box1> write sys$output f$getqui("DISPLAY_ENTRY", "CHECKPOINT_DATA", 16)
Phase_1