Kris:
I answered him privately - the "CP" in CP DISKACNT EXT is not
correct; DISKACNT is not a CP command!
David Wakser
-----Original Message-----
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Kris Buelens
Sent: Thursday, August 07, 2008 4: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 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 START in DISKACNT.
2008/8/7 Wandschneider, Scott <[EMAIL PROTECTED]>:
> 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'
> Sleep 02 sec
> 'CP SEND DISKACNT END'
> Sleep 02 sec
> 'CP SEND CP DISKACNT LOGOFF'
>
> AllDone:
> Exit
>
> However, I receive the following error message:
> HCPCFX6768I Your SECUSER set to VMUTIL by VMUTIL.
> HCPRET8067A ENTER END OR SUMMARY
> HCPCMD001E Unknown CP command: END
> CONNECT= 00:59:41 VIRTCPU= 000:01.71 TOTCPU= 000:03.68 LOGOFF AT
> 02:00:06 EDT THURSDAY 08/07/08
>
> Thanks in Advance,
> Scott R Wandschneider
> Senior Systems Programmer
> Infocrossing, a WIPRO Company
> 11707 Miracle Hills Dr.
> Omaha, NE 68154
> Office 402.963.8905
>
>
>
>
>
>
--
Kris Buelens,
IBM Belgium, VM customer support
