First guess: Take a peek on VMUTIL's disk to see if you might have an
ERASE EXEC accessed.
In any case, changing the "CMS" stage to a "COMMAND" stage would prevent
it from running any accessed ERASE EXECs.
Personally, I'd stop using the stack altogether and re-write the pipe
(untested) as:
'PIPE (NAME Erase332Stats)' ,
'| COMMAND LISTFILE * 332STATS A (TODAY NOHEADER',
'| SORT 1-8 DESCENDING',
'| DROP FIRST 1',
'| SPECS /ERASE/ 1 W1-3 NW',
'| CONSOLE',
'| COMMAND'
RETURN
Mike Walter
Hewitt Associates
Any opinions expressed herein are mine alone and do not necessarily
represent the opinions or policies of Hewitt Associates.
"Tom Duerbusch" <[EMAIL PROTECTED]>
Sent by: "The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU>
01/02/2007 01:00 PM
Please respond to
"The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU>
To
IBMVM@LISTSERV.UARK.EDU
cc
Subject
OK Pipers, a new challenge
OK, this is a real simple pipe.
'LISTF * 332STATS A (TODAY STACK'
'PIPE STACK ',
'| SORT 1-8 DESCENDING',
'| DROP FIRST 1',
'| SPECS /ERASE / 1 W1-3 NW',
'| CONSOLE',
'| CMS '
RETURN
It erases all "* 332sstats" files except for the lastest one.
I think it works great, but perhaps not.
As you can see, I create a CMS 'erase' command, display it on the
console and execute it.
After all the rexx subsitutions take place and the pipe is build, a
"trace i" shows the following:
>O> "PIPE STACK | SORT 1-8 DESCENDING | DROP FIRST 1 | SPECS
/ERASE /
1 W1-3 NW | CONSOLE | CMS "
11 *-* RETURN
0000009 FILES PURGED
I would have expected to see:
erase 090101 332stats a
erase 100101 332stats a
erase 110101 332stats a
etc
so, why am I not getting the CMS command, listed. Obviously, I'm doing
something wrong here. But 9 files being purged is the right number.
The process is being kicked off by VMUTIL. So I plan on disabling it
and log on and do the commands myself to see what is actually out there.
But that shouldn't have any effect on why I'm not seeing the CMS
commands echoed to the console.
Thanks
Tom Duerbusch
THD Consulting
Happy New Year
The information contained in this e-mail and any accompanying documents may
contain information that is confidential or otherwise protected from
disclosure. If you are not the intended recipient of this message, or if this
message has been addressed to you in error, please immediately alert the sender
by reply e-mail and then delete this message, including any attachments. Any
dissemination, distribution or other use of the contents of this message by
anyone other than the intended recipient
is strictly prohibited.
