WAKEUP has been shipped as part of CMS since (I think it was) z/VM 1.3.0 
So, whatever level your CMS is at is the current WAKEUP level.  However, 
not much has changed with WAKEUP in several releases.

Colleen M Brown 
IBM z/VM and Related Products Development and Service 



From:
"Wandschneider, Scott" <scott.wandschnei...@infocrossing.com>
To:
IBMVM@LISTSERV.UARK.EDU
Date:
03/16/2010 11:42 AM
Subject:
Re: VMUTIL PARM Question
Sent by:
The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU>



Version 1.2 must be current then - Thanks!

Thank you,

Scott


-----Original Message-----
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On 
Behalf Of Ron Schmiedge
Sent: Tuesday, March 16, 2010 10:37 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: VMUTIL PARM Question

WAKEUP VERSION on my z/VM 5.4 system says 1.2 (RC=00012)

On Tue, Mar 16, 2010 at 9:23 AM, Wandschneider, Scott
<scott.wandschnei...@infocrossing.com> wrote:
> Frank excellent suggestion - My PRAMS file has been carried forward so 
many times, it still says:
>
> *  THIS IS THE DEFAULT 'WAKEUP PARMS' FILE THAT IS SUPPLIED WITH       *
> *  THE VM/SP  IPO/E SYSTEM FOR THE VIRTUAL MACHINE 'VMUTIL'.           *
>
> Btw way what is the current version of WAKEUP, mine is 1.2?
>
> Thank you,
>
> Scott
>
>
> -----Original Message-----
> From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On 
Behalf Of Frank M. Ramaekers
> Sent: Tuesday, March 16, 2010 9:59 AM
> To: IBMVM@LISTSERV.UARK.EDU
> Subject: Re: VMUTIL PARM Question
>
> I've added this comment to the beginning of my WAKEUP TIMES:
>
> 
*-----------------------------------------------------------------------*
> *ALL     |HH:MM:SS|DATESTAM| user-text (once a day)                     
*
> *MM/DD/YY|HH:MM:SS|DATESTAM| user-text (once)                           
*
> *==/DD/YY|HH:MM:SS|DATESTAM| user-text (once a month)                   
*
> *==/==/==|HH:MM:SS|DATESTAM| user-text (once a day)                     
*
> *==/01/==|HH:MM:SS|DATESTAM| user-text (on the 1st)                     
*
> *        |        |        |                                           
 *
> *DAYOFWEK|HH:MM:SS|DATESTAM| user-text (once a week)                   
 *
> *WEEKEND |HH:MM:SS|DATESTAM| user-text (on weekends)                   
 *
> *S-S     |HH:MM:SS|DATESTAM| user-text (same as above)                 
 *
> *WEEKDAY |HH:MM:SS|DATESTAM| user-text (on weekdays)                   
 *
> *M-F     |HH:MM:SS|DATESTAM| user-text (same as above)                 
 *
> *        |        |        |                                           
 *
> *==/==/==|+05     |TIMESTAM| user-text (every 5 minutes)               
 *
> *WEEKEND |+10:30  |TIMESTAM| user-text (every 10 mins 30 secs. 
weekends)*
> *WEEKDAY |+20     |TIMESTAM| user-text (every 20 mins weekdays)         
*
> *DAYOFWEK|+5      |TIMESTAM| user-text (every 5 mins on day)           
 *
> *M-F     |+02:30:0|TIMESTAM| user-text (every 150 mins. on weekdays)   
 *
> 
*-----------------------------------------------------------------------*
>
>
> Frank M. Ramaekers Jr.
>
>
>
> -----Original Message-----
> From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On 
Behalf Of Bill Munson
> Sent: Tuesday, March 16, 2010 9:06 AM
> To: IBMVM@LISTSERV.UARK.EDU
> Subject: Re: VMUTIL PARM Question
>
> Scott,
>
> I believe that the Wakeup Parms file is restricted to one week of
> activity.
>
> 
 ************************************************************************
> *                                                                      *
> *  THIS IS THE DEFAULT 'WAKEUP PARMS' FILE THAT IS SUPPLIED WITH       *
> *  THE VM/370 IPO/E SYSTEM FOR THE VIRTUAL MACHINE 'VMUTIL'.           *
> *                                                                      *
> *  NOTE THAT THERE ARE 4 FIELDS IN THIS FILE:                          *
> *                                                                      *
> *  FIELD 1:  COLUMNS 01 TO 03  --  DAYS OF THE WEEK                    *
> *  FIELD 2:  COLUMNS 10 TO 17  --  TIME OF DAY                         *
> *  FIELD 3:  COLUMNS 19 TO 26  --  LAST DATE THAT LINE WAS EXECUTED    *
> *  FIELD 4:  COLUMNS 28 TO 80  --  ANY CP/CMS/EXEC COMMAND             *
> *                                                                      *
> *  VALID PARAMETERS:                                                   *
> *                                                                      *
> *  FIELD 1:                                                            *
> *           'ALL'  -- EXECUTE THIS LINE EVERY DAY OF THE WEEK          *
> *           'MON'  -- EXECUTE THIS LINE ONLY ON MONDAYS                *
> *           'TUE'  -- EXECUTE THIS LINE ONLY ON TUESDAYS               *
> *           'WED'  -- EXECUTE THIS LINE ONLY ON WEDNESDAYS             *
> *           'THU'  -- EXECUTE THIS LINE ONLY ON THURSDAYS              *
> *           'FRI'  -- EXECUTE THIS LINE ONLY ON FRIDAYS                *
> *           'SAT'  -- EXECUTE THIS LINE ONLY ON SATURDAYS              *
> *           'SUN'  -- EXECUTE THIS LINE ONLY ON SUNDAYS                *
> *           'M-F'  -- EXECUTE THIS LINE ONLY MONDAY THRU FRIDAY        *
> *           'S-S'  -- EXECUTE THIS LINE ONLY SATURDAYS AND SUNDAYS     *
> *                                                                      *
> *  FIELD 2:                                                            *
> *                                                                      *
> *           HH:MM:SS  -- THIS FIELD CONTAINS THE TIME THAT             *
> *                        YOU WANT THE COMMAND TO BE EXECUTED           *
> *                                                                      *
> *  FIELD 3:                                                            *
> *                                                                      *
> *           MM/DD/YY  -- THIS FIELD CONTAINS THE LAST DATE THAT        *
> *                        THE COMMAND WAS EXECUTED.  THIS IS TO         *
> *                        INSURE THAT IF IT WAS EXECUTED ONCE ON        *
> *                        THAT DAY, IT WONT BE EXECUTED AGAIN INCASE    *
> *                        'VMUTIL' MUST BE RE-STARTED.                  *
> *                        THIS FIELD IS UPDATED BY 'VMUTIL' AFTER THE   *
> *                        COMMAND LINE IS EXECUTED.                     *
> *                                                                      *
> *  FIELD 4:                                                            *
> *                                                                      *
> *          CP/CMS/EXEC COMMAND                                         *
> *                     -- PLACE ANY COMMAND TO BE EXECUTED IN THIS      *
> *                        FIELD.                                        *
> *                                                                      *
> *          NOTE:  IF THE KEY ENTRY 'MSG01' IS ENTERED IN FIELD 4       *
> *                 WHERE THE COMMAND LINE IS ENTERED, A MESSAGE         *
> *                 TO THE OPERATOR WILL BE SENT STATING THE CURRENT     *
> *                 DATE AND TIME.                                       *
> *                                                                      *
> *                 IF THE COMMAND BEING ISSUED IS A CMS COMMAND,        *
> *                 THE COMMAND MUST BE PREFIXED WITH 'CMS'              *
> *                                                                      *
> *                 IF THE COMMAND BEING ISSUED IS A CP COMMAND,         *
> *                 THE COMMAND MUST BE PREFIXED WITH 'CP'               *
> *                                                                      *
> *                 IF THE COMMAND BEING ISSUED IS AN EXEC,              *
> *                 THE COMMAND MUST BE PREFIXED WITH 'EXEC'             *
> *                                                                      *
> *                 'VMUTIL' GENERATES A LOG FILE OF ALL TRANSACTIONS    *
> *                 THAT TAKES PLACE, IT IS NAMED 'VMUTIL LOG A0'.       *
> *                 IN THIS 'WAKEUP PARMS' FILE IT IS PRINTED AND        *
> *                 ERASED AT 08:00:00 HOURS.                            *
> *                                                                      *
> *                 IF THERE IS AN '*' IN COLUMN 1 OF THIS FILE, THE     *
> *                 LINE IS TREATED AS A COMMENT AND IS NOT EXECUTED.    *
> *                                                                      *
> ************************************************************************
>
> good luck
>
> Bill Munson
> Sr. z/VM Systems Programmer
> Brown Brothers Harriman & CO.
> 525 Washington Blvd.
> Jersey City, NJ 07310
> 201-418-7588
>
>
>
>
>
> "Wandschneider, Scott" <scott.wandschnei...@infocrossing.com>
> Sent by: The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU>
> 03/16/2010 09:58 AM
> Please respond to
> The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU>
>
>
> To
> IBMVM@LISTSERV.UARK.EDU
> cc
>
> Subject
> VMUTIL PARM Question
>
>
>
>
>
>
> What is the proper syntax for a WAKE PARM for VMUTIL to execute in the
> future.  For example, say I want to execute "CP SET SHARE USERA RELATIVE
> 300 2.7% LIMITHARD" at 08:00 on Saturday, May 1, 2010?  I'm thinking it
> would be "SAT 08:00:00 04/24/10 CP SET SHARE USERA RELATIVE 300 2.7%
> LIMITHARD".  Is this correct?
>
> Thank you,
> Scott R Wandschneider
> Senior Systems Programmer|| Infocrossing, a Wipro Company || 11707 
Miracle
> Hills Drive, Omaha, NE, 68154-4457|| �u: 402.963.8905 || �|
> :847.849.7223  ||  : scott.wandschnei...@infocrossing.com **Think Green 
 -
> Please print responsibly**
>
>
>
>
> *************************** IMPORTANT NOTE
> ***************************** The opinions expressed in this
> message and/or any attachments are those of the author and not
> necessarily those of Brown Brothers Harriman & Co., its
> subsidiaries and affiliates ("BBH"). There is no guarantee that
> this message is either private or confidential, and it may have
> been altered by unauthorized sources without your or our knowledge.
> Nothing in the message is capable or intended to create any legally
> binding obligations on either party and it is not intended to
> provide legal advice. BBH accepts no responsibility for loss or
> damage from its use, including damage from virus.
> ************************************************************************
>
> _____________________________________________________
> This message contains information which is privileged and confidential 
and is solely for the use of the
> intended recipient. If you are not the intended recipient, be aware that 
any review, disclosure,
> copying, distribution, or use of the contents of this message is 
strictly prohibited. If you have
> received this in error, please destroy it immediately and notify us at 
privacy...@ailife.com.
>



Reply via email to