That's it! We recover only one member of a two member sysplex. Normally we use operlog, but the logstream did not get created on this IPL, so SDSF has to use syslog. I can now create the problem at will with 'SYSID missing-sys'. SYSID 'recovered-sys' goes right into syslog with no problem.
Do I sniff an APAR here? Or does all this go away in z/OS 2.2? . . . 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 [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Andy Higgins Sent: Monday, April 11, 2016 6:36 AM To: [email protected] Subject: (External):Re: SDSF Mystery Skip, I've noticed that SDSF will try to allocate HASPINDX if you invoke LOG SYSLOG with SYSID set to a system that's an inactive member of the MAS. hth Andy On Sat, 9 Apr 2016 20:24:18 +0000, Jesse 1 Robinson <[email protected]> wrote: >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 >[email protected] ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
