Re: AUTOIPL SADUMP LOADPARM flag value

2017-05-15 Thread Jesse 1 Robinson
-Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Bruce Hewson Sent: Sunday, May 14, 2017 9:24 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: AUTOIPL SADUMP LOADPARM flag value Hello Skip, GDPS-PPRC - doesn't like any IPL activity

Re: AUTOIPL SADUMP LOADPARM flag value

2017-05-14 Thread Bruce Hewson
Hello Skip, GDPS-PPRC - doesn't like any IPL activity that is not performed via the GDPS panels. extract from:- https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.2.0/com.ibm.zos.v2r2.ieag300/wsat.htm Note: AutoIPL is not appropriate in a GDPS® environment. Regards Bruce

Re: AUTOIPL SADUMP LOADPARM flag value

2017-05-13 Thread Jesse 1 Robinson
@LISTSERV.UA.EDU] On Behalf Of Bruce Hewson Sent: Saturday, May 13, 2017 5:17 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: AUTOIPL SADUMP LOADPARM flag value Hi Skip, why not REIPL ? one acronym == GDPS :-) Regards Bruce Hewson

Re: AUTOIPL SADUMP LOADPARM flag value

2017-05-13 Thread Bruce Hewson
Hi Skip, why not REIPL ? one acronym == GDPS :-) Regards Bruce Hewson -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: AUTOIPL SADUMP LOADPARM flag value

2017-05-12 Thread Tom Conley
On 5/12/2017 5:18 PM, Jesse 1 Robinson wrote: It's Friday, so I can (re)tell my war story. Shortly after z/OS R13 hit our first prod system, I noticed one morning that the system had been IPLed around 05:00. Everyone denied having done it. Then I discovered a fresh SAD taken around the same

Re: AUTOIPL SADUMP LOADPARM flag value

2017-05-12 Thread Jesse 1 Robinson
@LISTSERV.UA.EDU Subject: (External):Re: AUTOIPL SADUMP LOADPARM flag value On Fri, 12 May 2017 16:18:14 +, Jesse 1 Robinson <jesse1.robin...@sce.com> wrote: >I'm curious as to why you do not want automatic reIPL after SADMP. Your >system is in a non-restartable wait state,

Re: AUTOIPL SADUMP LOADPARM flag value

2017-05-12 Thread Mark Zelden
On Fri, 12 May 2017 16:18:14 +, Jesse 1 Robinson wrote: >I'm curious as to why you do not want automatic reIPL after SADMP. Your >system is in a non-restartable wait state, after all. I view that as the >ultimate performance degradation. ;-) You have an

Re: AUTOIPL SADUMP LOADPARM flag value

2017-05-12 Thread Jesse 1 Robinson
Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Bruce Hewson Sent: Thursday, May 11, 2017 11:39 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: AUTOIPL SADUMP LOADPARM flag value Hello Jim, thank you. summary:- SADUMP treats last LOADPARM

Re: AUTOIPL SADUMP LOADPARM flag value

2017-05-12 Thread Bruce Hewson
Hello Jim, thank you. summary:- SADUMP treats last LOADPARM character as if it is a hexadecimal nibble. 1... 8 - reserved for IBM - do not use .1.. 4 - SADUMP will attempt re-ipl using stored DIAG member MVS() parameter values ..1. 2 - unassigned - do not use ...1 1

Re: AUTOIPL SADUMP LOADPARM flag value

2017-05-10 Thread Jim Mulder
Currently, "2" will be treated the same as "0" or " " (blank).There is no reason why you should have specified "2", and a good reason not to - there is a possibility that in some future release, we might assign some meaning to "2". Standalone dump treats this character as a hexadecimal

AUTOIPL SADUMP LOADPARM flag value

2017-05-10 Thread Bruce Hewson
hello, Back in 2010 I had a system coded with SADUMP(,SNSYSC2) and MVS(LAST). When a V, XCF,sysn,OFFLINE,SADUMP,REIPL command was issued, the system did take a Stand Alone Dump, and did IPL. That is my recollection. Today I have no idea why I coded the "2" in the "SSNSYSC2" loadparm,