I was happy at your first post to check our values for comparison, but you have not said (up to now) where 'RECOVERY' is specified. I find none of the values you cite in PARMLIB, so we may be taking all defaults. I’m not the I/O guy but have access to most everything on the mainframe proper. IF RECOVERY is specified in the Brocade itself, I have colleagues could check there for reference. In order to get a good answer, you have start with a good question.
As for the chaos caused by failing hardware, I've seen many instances over the years. What amazes me today is the resilience that z/OS exhibits. There's lots of cacophony and confusion, but MVS tends to ride it out with minimal if any effect on applications. That was not always the case. One problem is that is that if a device cannot be reached, IOS waits for the Missing Interrupt Handler interval to expire before moving on the next device. For a few devices this is not a major problem. For hundreds or thousands of devices, it can extend the agony for a lonnnng time. Getting an offending chpid offline as quickly as possible is by far the best response. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of James Peddycord Sent: Thursday, December 29, 2016 6:57 AM To: [email protected] Subject: (External):Re: Recommendations for RECOVERY options NTAC:3NS-20 Thanks for the suggestion. I will repeat the question in a couple of weeks. Jim -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Elardus Engelbrecht Sent: Thursday, December 29, 2016 8:14 AM To: [email protected] Subject: Re: Recommendations for RECOVERY options James Peddycord wrote: >In this forum with so many people who have so many opinions, I can't believe that nobody is offering suggestions for the RECOVERY parameter when asked. Perhaps these persons with that specific hardware combination are still on holiday. Or if someone has this specific combination like yours indeed reads your message, but never experieneced this specific bad cable problem and perhaps can't contribute. Others like me are working on other things like RACF (myself), general z/OS + JES2 + TSO/ISPF matters (also myself). There are programmers in various languages also active here. Now and then you get some one with problems with a specific product like DFDSS, DFSORT, CICS, DB2 etc. Please note: I was previously responsible for storage (SMS/HSM) and managing hardware (3380 and later 3390, 3490 tapes and Magstar, etc.). I have some experience with ESCON, but not with Ficon, but I do read ALL posts on IBM, except those from a madman earlier this month. I humbly suggest that you repeat your question in second week of January 2017 when most are then hopefully back from their holidays. Good luck in finding a good solution. Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
