This is not a LINUX machine - it is DISKANCT - as supplied by IBM
(basically).
-Original Message-
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Bruce Hayden
Sent: Thursday, August 07, 2008 4:46 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Shutting Down DISKACNT
That is incorrect - the "CP" means that you are sending a CP command,
and DISKACNT is the userid. So - the command is exactly correct -
send the CP command EXT to DISKACNT. Coding it as 'CP SEND DISKACNT
EXT" assumes that the virtual machine is in a state to read commands
from the console, and th
lto:[EMAIL PROTECTED] On
Behalf Of Kris Buelens
Sent: Thursday, August 07, 2008 3:29 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Shutting Down DISKACNT
I'd say this should have been correct. My guess is that DISKACNT was
already stopped (disk full?), and as CMS runs by default with SET
AUTOREAD ON in
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Shutting Down DISKACNT
I'd say this should have been correct. My guess is that DISKACNT was
already stopped (disk full?), and as CMS runs by default with SET
AUTOREAD ON in a disconnected machine, the resulting VM READ is
translated into CP READ due to
I'd say this should have been correct. My guess is that DISKACNT was
already stopped (disk full?), and as CMS runs by default with SET
AUTOREAD ON in a disconnected machine, the resulting VM READ is
translated into CP READ due to the disconnect (without SECONDARY user)
state. Try with a CP SP CON
What is the proper way (without using FORCE) to shutdown DISKACNT? I use the
following EXEC:
/* */
ShutdownDiskAcnt:
'SET SECUSER DISKACNT *'
Sleep 02 sec
'CP SEND CP DISKACNT EXT'
