well u can always code something similar to: hex15 = '15'x 'CP SYSTEM RESET CLEAR'hex15'IPL .... '
-------- Original Message -------- Subject: Re: PSW 000A0000 00000100 From: Pat Carroll <pcarr...@llbean.com> Date: Tue, June 29, 2010 3:53 pm To: LINUX-390@VM.MARIST.EDU Good thought, but if this is automated (via an exec) a reset clear will probably blow away the exec ;) Patrick Carroll | Technology Architect II L.L.Bean, Inc.(r) | Double L St. | Freeport ME 04033 http://www.llbean.com | pcarr...@llbean.com | 207.552.2426 CONFIDENTIALITY NOTICE: This e-mail and any attachments may contain confidential information that is legally privileged. The information is solely for the use of the intended recipient(s). Any disclosure, copying, distribution, or other use of this information is strictly prohibited. If you have received this e-mail in error, please notify the sender by return e-mail and delete this message. -----Original Message----- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of David Kreuter Sent: Tuesday, June 29, 2010 3:49 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: PSW 000A0000 00000100 Wouldn't a class G SYSTEM RESET CLEAR prior to the IPL reset the i/o status and hence let the IPL sequence go forward? Or is it too far down the wrong road? David Kreuter -------- Original Message -------- Subject: Re: PSW 000A0000 00000100 From: Pat Carroll <pcarr...@llbean.com> Date: Tue, June 29, 2010 3:35 pm To: LINUX-390@VM.MARIST.EDU Mark, Since he's using a dedicated boot disk, would it help (in the meantime) if there's a forced delay between virtual machine creation time and Linux IPL command (i.e, sleep 5)? Patrick Carroll | Technology Architect II L.L.Bean, Inc.(r) | Double L St. | Freeport ME 04033 http://www.llbean.com | pcarr...@llbean.com | 207.552.2426 CONFIDENTIALITY NOTICE: This e-mail and any attachments may contain confidential information that is legally privileged. The information is solely for the use of the intended recipient(s). Any disclosure, copying, distribution, or other use of this information is strictly prohibited. If you have received this e-mail in error, please notify the sender by return e-mail and delete this message. -----Original Message----- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Mark Post Sent: Tuesday, June 29, 2010 2:54 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: PSW 000A0000 00000100 >>> On 6/29/2010 at 01:15 PM, <karlkings...@ongov.net> wrote: > Was trying to look at the Bugzilla report for this and get an access > denied???? Am I not allowed to see the report? No, it's been restricted to the reporter and Novell employees. What I can tell you is that the bug is fixed in the SLES10 SP3 series of s390-tools. Since SLES10 SP2 and earlier are out of support, there will be no fix provided for them. The patch description, which will eventually end up on IBM's developerWorks web site, shows this: Description: zipl: handle status during ipl Symptom: You encounter an error during IPL with "disabled wait" message. Problem: During the IPL sequence the subchannel of the IPL device has to be enabled. If there is a status pending or busy condition on the subchannel the IPL code abborts the IPL and goes into disabled wait. Solution: To resolve the problem the IPL code accepts the status pending or busy condition on the subchannel and does up to 256 retries. Problem-ID: 57775 If you download the source RPM for the SLES10 SP3 s390-tools, you'll also be to see the same description in the s390-tools-sles10-zipl-handle-status-during-ipl.patch file included there (typos and all). Mark Post ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/ ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/ ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/ ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/ ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
