Thank you for all the advice. It helped me wrap my head around how to
handle Spool files better. We are using SFPURGER on a different VM syste
m,
we just need to get it set up on the VM I was having this trouble with.
What a Team!
You may want to look at the SFPURGER CMS Utility also...you can specify the
number of days and it will purge all old stuff. SFPURGER is documented in
the CMS Commands and Utilities Reference at:
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/HCSD8B10/3.8?SHELF=hcsh2a80&DT=200510150
The most frequent reason for a file to become SYSTEM HOLD, is that the spool
got full while it was being created, so it signals the user that the file,
is incomplete.
When you find system held console files, you should probably issue
CP SEND CP userid SP CON START
to have the console spooling sta
Try something like:
CHANGE userid RDR spoolid NOSYS
Or
PURGE userid RDR spoolid
-Original Message-
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Richard Clapper
Sent: Tuesday, March 13, 2007 1:23 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: DMSWRC687E
I&#
Sent: Tue 3/13/2007 1:22 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: [IBMVM] DMSWRC687E
I'm trying to display very old Spool files, and DISCARD them, using RDRL =
in
CMS. The Spool files are simply Console Logs from a USER. I receive the=
following messages:
DMSWRC687E This is a SYSTEM
I'm trying to display very old Spool files, and DISCARD them, using RDRL
in
CMS. The Spool files are simply Console Logs from a USER. I receive the
following messages:
DMSWRC687E This is a SYSTEM HELD file--this file cannot be received
DMSWDC653E Error executing RECEIVE 0008 (
