Are you sure about that? Any posted read that is not responded to will get a disconnected machine forced regardless of whether it is VM or CP read. The forced disconnect is in response to terminal errors during I/O and is relevant to this discussion only if a read is posted while disconnected. It is all as documented, I do believe., and is not a bug. The reason for it is fairly obvious. If there is no secuser for the machine, someone has to log on to respond to the read. If nobody logs on, then the read triggers the logoff force timer. This is nothing new to XA.
If, whenever you logon, a CP Read is posted, it is because you do not have SET RUN ON. That CP Read bears no relationship to the logoff timer. That goes back to the earliest releases of VM and probably beyond to CP40 and CP67. I only got into VM at the VM370 Release 1 level as a user, Release 2 as a sysprog., so I cannot speak to the earlier systems. Regards, Richard Schuh ________________________________ From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Kris Buelens Sent: Tuesday, January 25, 2011 12:34 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Forced logoff by SYSTEM? Logically the Virtual Machine would be in VM READ. But in the VM/XA branch of VM -on which z/VM is based- any VM READ of a disconnected user without secondary user gets translated in a CP READ. I find this a bug, VM/SP and VM/HPO did it right. Without setting a secondary user on it, one cannot even use CP SEND to respond to the VM READ, because it is no longer there. Even CP SEND CP xxx BEGIN can't help: the VM READ will be reposted, but it gets again translated into a CP READ. Then, why not using SET SECUSER followed by SEND BEGIN? There are cases where one doesn't want a secondary user: namely for servers intercepting messages (WAKEUP, PROP, PIPE *STARMSG, ...) 2011/1/25 Shimon Lebowitz <shim...@iname.com<mailto:shim...@iname.com>> The OP (that's me) has mentioned opening a PMR over the fact that PERFSVM did in fact abend. I thought that after creating a VMDUMP, the virtual machine would be in a CP READ, but I guess I misunderstood. Shimon On Tue, Jan 25, 2011 at 4:37 AM, Stephen Powell <zlinux...@wowway.com<mailto:zlinux...@wowway.com>> wrote: What probably happened to the OP is this: (1) The virtual machine was autologged, (2) It ran a program, (3) the program abended, causing CMS to issue the "CMS" prompt, instead of the usual "Ready;" prompt, Then it issued a VM READ. At this point, CMS is waiting for the user to issue the DEBUG command to obtain virtual machine status at the time of the ABEND. Any other command will cause ABEND cleanup processing to occur. But that is a moot point, really. The point is that the virtual machine is in a VM READ state at this point in time. And after being in a VM READ state for 15 minutes, CP forces it off. -- Kris Buelens, IBM Belgium, VM customer support
