Re: How to easily render a system unIPLable/IPLable
It depends on how far you want the hardware/software to get before if fails. For example: - If you have access to the HMC, rename the IMAGE profile of the LPAR your sandbox system runs in. Then De-activate that LPAR. If someone attempts to IPL that LPAR, it will fail, LPAR not activated. If someone attempts to activate that LPAR, the activate will fail because the IMAGE profile does not exist. Change the load address on your image to a non-RES volume ??? The IPL will fail with a NO IPL TEXT message or something like that. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
How to easily render a system unIPLable/IPLable
I am running some SMP/E jobs to apply maintenance to our sandbox. It is currently down. I have emailed everybody that it needs to say down while I do my maintenance. Yes, I generally trust them. However, since I have the sandbox OMVS files mounted in order to directly put the maintenance on them, I was wondering if there is a simple, easy to reverse, way to render a system unIPLable? I don't really want to AMASPZAP the IPL text or anything weird like that. I don't want to rename any libraries (such as SYS1.NUCLEUS) because that would mess up my DDDEFs. And, just to be weird, I really love the result to be a hard wait with a code of 0xDEADBEEF. That would amuse me greatly. -- John McKown Senior Systems Programmer UICI Insurance Center Information Technology This message (including any attachments) contains confidential information intended for a specific individual and purpose, and its' content is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this transmission, or taking any action based on it, is strictly prohibited. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: How to easily render a system unIPLable/IPLable
-Original Message- From: IBM Mainframe Discussion List On Behalf Of McKown, John I am running some SMP/E jobs to apply maintenance to our sandbox. It is currently down. I have emailed everybody that it needs to say down while I do my maintenance. Yes, I generally trust them. However, since I have the sandbox OMVS files mounted in order to directly put the maintenance on them, I was wondering if there is a simple, easy to reverse, way to render a system unIPLable? Create a bogus IPLPARM? -jc- -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: How to easily render a system unIPLable/IPLable
What does happen if IPL process does not find right LOADxx member ? Marian On 8/22/05, McKown, John [EMAIL PROTECTED] wrote: I am running some SMP/E jobs to apply maintenance to our sandbox. It is currently down. I have emailed everybody that it needs to say down while I do my maintenance. Yes, I generally trust them. However, since I have the sandbox OMVS files mounted in order to directly put the maintenance on them, I was wondering if there is a simple, easy to reverse, way to render a system unIPLable? I don't really want to AMASPZAP the IPL text or anything weird like that. I don't want to rename any libraries (such as SYS1.NUCLEUS) because that would mess up my DDDEFs. And, just to be weird, I really love the result to be a hard wait with a code of 0xDEADBEEF. That would amuse me greatly. -- John McKown Senior Systems Programmer UICI Insurance Center Information Technology This message (including any attachments) contains confidential information intended for a specific individual and purpose, and its' content is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this transmission, or taking any action based on it, is strictly prohibited. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: How to easily render a system unIPLable/IPLable
Specifying an IODF that doesn't exist will put you in a wait state when you ipl. So a simple member edit should suffice. Alan Schwartz Assurant Shared Business Services Lead Systems Programmer Phone: 651-361-4758 Fax: 651-361-5625 McKown, John [EMAIL PROTECTED] Sent by: IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU 08/22/2005 12:01 PM Please respond to IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU To IBM-MAIN@BAMA.UA.EDU cc Subject How to easily render a system unIPLable/IPLable I am running some SMP/E jobs to apply maintenance to our sandbox. It is currently down. I have emailed everybody that it needs to say down while I do my maintenance. Yes, I generally trust them. However, since I have the sandbox OMVS files mounted in order to directly put the maintenance on them, I was wondering if there is a simple, easy to reverse, way to render a system unIPLable? I don't really want to AMASPZAP the IPL text or anything weird like that. I don't want to rename any libraries (such as SYS1.NUCLEUS) because that would mess up my DDDEFs. And, just to be weird, I really love the result to be a hard wait with a code of 0xDEADBEEF. That would amuse me greatly. -- John McKown Senior Systems Programmer UICI Insurance Center Information Technology ** This e-mail message and all attachments transmitted with it may contain legally privileged and/or confidential information intended solely for the use of the addressee(s). If the reader of this message is not the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, forwarding or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately and delete this message and all copies and backups thereof. Thank you. ** -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: How to easily render a system unIPLable/IPLable
-Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Alan Schwartz Sent: Monday, August 22, 2005 12:09 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: How to easily render a system unIPLable/IPLable Specifying an IODF that doesn't exist will put you in a wait state when you ipl. So a simple member edit should suffice. Alan Schwartz Yeah, I finally figured that out. Simple. Too bad it doesn't give my the 0xDEADBEEF wait state. I don't know where my mind is today. It seems to have checked out over the weekend and left no forwarding address. -- John McKown Senior Systems Programmer UICI Insurance Center Information Technology This message (including any attachments) contains confidential information intended for a specific individual and purpose, and its' content is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this transmission, or taking any action based on it, is strictly prohibited. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: How to easily render a system unIPLable/IPLable
On Mon, Aug 22, 2005 at 12:37:31PM -0500, McKown, John wrote: Yeah, I finally figured that out. Simple. Too bad it doesn't give my the 0xDEADBEEF wait state. If you want dead beef, you'll have to go to a steakhouse or write custom IPL text. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: How to easily render a system unIPLable/IPLable
John, It depends on how far you want the hardware/software to get before if fails. For example: - If you have access to the HMC, rename the IMAGE profile of the LPAR your sandbox system runs in. Then De-activate that LPAR. If someone attempts to IPL that LPAR, it will fail, LPAR not activated. If someone attempts to activate that LPAR, the activate will fail because the IMAGE profile does not exist. Once you finish with your maintenance, rename the IMAGE profile of that LPAR back to its original name. NOTE: The HMC Application does not have a rename function. I circumvent this 'editing' ( the customize function ) the profile I want to rename, change the Profile Name on the 1st customization screen, Save the 'new' Profile, then delete the 'original' Profile. - Use the NOBOOTSTRAP parameter of the ICKDSF REFORMAT command against the Sysres volume you're working on. CAUTION: DO NOT use INIT command. Once you finish with your maintenance, perform ICKDSF REFORMAT command with BOOTSTRAP IPLDD parameters to 're-install' the correct z/OS IPL text. - The other suggestions regarding the LOADxx member are good. However, if you don't want your Sysres volume to be access, these may not meet your requirement. HTH Glenn Miller --- This message (including any attachments) is confidential and may be privileged. If you have received it by mistake please notify the sender by return e-mail and delete this message from your system. Any unauthorised use or dissemination of this message in whole or in part is strictly prohibited. Please note that e-mails are susceptible to change. ABN AMRO Bank N.V. (including its group companies) shall not be liable for the improper or incomplete transmission of the information contained in this communication nor for any delay in its receipt or damage to your system. ABN AMRO Bank N.V. (or its group companies) does not guarantee that the integrity of this communication has been maintained nor that this communication is free of viruses, interceptions or interference. --- -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: How to easily render a system unIPLable/IPLable
Just write over the boot record and then put it back later. The Dead Beef part is tough unless you decide to mess with the second boot record and program. -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of McKown, John Sent: Monday, August 22, 2005 1:02 PM To: IBM-MAIN@BAMA.UA.EDU Subject: How to easily render a system unIPLable/IPLable I am running some SMP/E jobs to apply maintenance to our sandbox. It is currently down. I have emailed everybody that it needs to say down while I do my maintenance. Yes, I generally trust them. However, since I have the sandbox OMVS files mounted in order to directly put the maintenance on them, I was wondering if there is a simple, easy to reverse, way to render a system unIPLable? I don't really want to AMASPZAP the IPL text or anything weird like that. I don't want to rename any libraries (such as SYS1.NUCLEUS) because that would mess up my DDDEFs. And, just to be weird, I really love the result to be a hard wait with a code of 0xDEADBEEF. That would amuse me greatly. -- John McKown Senior Systems Programmer UICI Insurance Center Information Technology This message (including any attachments) contains confidential information intended for a specific individual and purpose, and its' content is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this transmission, or taking any action based on it, is strictly prohibited. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: How to easily render a system unIPLable/IPLable
Specifying an IODF that doesn't exist will put you in a wait state when you ipl. So a simple member edit should suffice. BORING ! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: How to easily render a system unIPLable/IPLable
If the Dead Beef is important to you than don't let it go ! It's not that hard to do. I can tell you've got what it takes. Pot a coffee and a few snickers bars and you'll have the dead beef wait state by morning. Yeah, I finally figured that out. Simple. Too bad it doesn't give my the 0xDEADBEEF wait state. I don't know where my mind is today. It seems to have checked out over the weekend and left no forwarding address. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
