Tom (and some others),
The original post indicated use of "you could use VMUTIL, or some other
home grown exec to issue a close on behalf of a disconnected machine."
See the text:
> Almost every z/VM customer is forced to devise a method to close service
virtual machine consoles at midnight, o
Back in my IBM days, I used to close all the console spool files every hour.
They went to another DVM on the same system which tracked their timely arrival
and then transferred them to my local DVM, which also tracked them and dealt
them out to Keeper DVM'S. I, or my backup (or OPS), got MSG ale
I use:
cp spool console to maint eof
Which closes the console after every 50,000 records.
If you need it done at midnight or some other time, you could use VMUTIL, or
some other home grown exec to issue a close on behalf of a disconnected machine.
Tom Duerbusch
THD Consulting
>>> Mike Walter
there.
>
> But putting the almighty(?) dollar first on technical issues like these is
> like the "tail wagging the dog".
>
>
>
>
>
> *Alan Altmark *
> Sent by: The IBM z/VM Operating System
>
> 02/11/2011 07:27 PM
> Please respond to
> The IB
g the dog".
Alan Altmark
Sent by: The IBM z/VM Operating System
02/11/2011 07:27 PM
Please respond to
The IBM z/VM Operating System
To
IBMVM@LISTSERV.UARK.EDU
cc
Subject
Re: Closing console (and other o/p UR devices) at midnight or other times.
On Friday, 02/11/2011 at 04:24 E
On Friday, 02/11/2011 at 04:24 EST, Mike Walter
wrote:
> See? Alan's reply is precisely why I thought "it seemed prudent to run
it
> past others for wider consideration."
>
> I suspect that there will be many new LoZ (a new "Linux on System Z"
> acronym seen recently, and MUCH less to type) cu
l the knife twist right there at the end?);-)
Mike Walter
Aon Corporation
The opinions expressed herein are mine alone, not my employer's.
"Alan Altmark"
Sent by: "The IBM z/VM Operating System"
02/11/2011 03:00 PM
Please respond to
"The IBM z/VM Operating
On Friday, 02/11/2011 at 03:10 EST, Martin Zimelis
wrote:
> David's comment is a perfect example of the reason Rich is exactly
right: The
> requirement should specify the effect you want, not the method of
> implementation.
>
> And don't forget to include the business case for the enhancemen
Maybe a good idea, but I doubt it will fly..
With the advent of the FOR command it is simple to put "CP FOR abc CMD CLOSE
CONS" in a WAKEUP file.
But if they did buy it how about an enhancement to XAUTOLOG with AT
hh:mm:ss?
Come to think of it a full date would be better yet.. AT mm/dd/yy hh:mm:s
David's comment is a perfect example of the reason Rich is exactly right:
The requirement should specify the effect you want, not the method of
implementation.
And don't forget to include the business case for the enhancement in the
requirement.
Marty
@LISTSERV.UARK.EDU
Subject: Closing console (and other o/p UR devices) at midnight or other times.
Almost every z/VM customer is forced to devise a method to close service
virtual machine consoles at midnight, or at some time of day. z/VM old-timers
have done this for ages, but new z/VM customers don't
#2, but for clarity:
A) hh:mm:ss is based on CP time, or the virtual TOD in the virtual machine?
B) what happens in a SSI configuration if a virtual machine moves to a new CP
with a different clock?
If only #2 were implemented, the new SPOOL command could be entered in the
directory entry of s
It's probably best not to dictate how *you* want it implemented. Be very specific in
the wording of the requirement and they will figure it out.
On 02/11/2011 01:45 PM, Mike Walter wrote:
Almost every z/VM customer is forced to devise a method to close service virtual
machine consoles at mid
Almost every z/VM customer is forced to devise a method to close service
virtual machine consoles at midnight, or at some time of day. z/VM
old-timers have done this for ages, but new z/VM customers don't often
have the skills necessary to implement automated closures - or even
recognize the a
14 matches
Mail list logo
