>For the cases where z/OS is loading a disabled wait state, and one of >these >consoles is the SYNCHDEST console or the NIP console, this behavior is >unfortunate (to say it politely. When it happens to me, I say it using >more colorful language). But there isn't anything z/OS can do about this. >We really do want the system reset done to release the DASD reserves. I figured that you would know the actual technical background for losing the data on the console screen. The problem is that many in IBM development and service/support do not appear to know this and judge from their own testing under VM. And the customer more or less gets ridiculed as being unable to read.
> For this reason (among others), I recommend using the System Console >(aka Operating System Messages on the HMC) as the SYNCHDEST and >NIP console. I'd love to. Unfortunately there's no way my colleague will be allowed to generate the HMC as NIP console. This installation is firmly in the era of 'each system it's own green screen' (and it's own NIP console) and is unlikely to change. And the HMC *is* set as synchdest console (I had seen to that). Doesn't help when the wait state message doesn't explain why the wait state was loaded. *That* message was a 'normal' message earlier that went to the green screen (which got released). Barbara ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
