Just too crazy. It's behaving like an old version. Removed our file name from ISFPRMxx, then it wanted ancient default ISF.HASPINDX. Put in a new name and created one with that name. Now LOG works, but none of this makes any sense. To reiterate, this is a totally mirrored environment. There is no discernable difference from production except unit addresses for like-named volumes. I will probably reIPL and watch more closely how the system comes up. . . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-302-7535 Office robin...@sce.com
-----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Field, Alan Sent: Saturday, April 09, 2016 6:22 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: SDSF Mystery Skip, I think HASPINDX is obsolete since about 1.12. We have a number of lpars where I deleted it and everything works. Try deleting it. Perhaps if it isn't there it will work better than being migrated/ -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jesse 1 Robinson Sent: Saturday, April 09, 2016 3:24 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: SDSF Mystery IPLed a system in DR mode. Exact mirrored copy of prod. SDSF log won't work in DR because HASPINDX shows migrated to tape, inaccessible in DR. But function works fine in prod. I can't find any difference. System is 2.1. How can log work in prod without HASP INDEX but fail in DR? . . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-302-7535 Office robin...@sce.com ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
