Well, shucks. Our motivation is to implement operlog in order to manage three closely related systems. We have always had shared console in place, but that combined view is not reflected syslog. ;-(
. . 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 robin...@sce.com -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Allan Staller Sent: Tuesday, April 9, 2019 5:11 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: DASD-only logging YES. It is a hard restriction. -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Jesse 1 Robinson Sent: Monday, April 8, 2019 10:37 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: DASD-only logging After 20+ years of heavy duty parallel sysplex, we'd finally like to dip our toe into DASD-only logging. We have one multi-system sysplex with no possible CF. According to https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ibm.com%2Fsupport%2Fknowledgecenter%2Fen%2FSSLTBW_2.2.0%2Fcom.ibm.zos.v2r2.ieaa600%2Fdasdy.htm&data=02%7C01%7Callan.staller%40HCL.COM%7C4362c828b272487ce15f08d6bc9cbf5c%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C636903778770312461&sdata=BnOJydu2xJFN%2F5%2FaWngs%2Bejs9HUiC2DruP1%2B3UmaqnQ%3D&reserved=0 "...a DASD-only log stream is single-system in scope - only one system may write to a DASD-only log stream." That's a major bummer. Is it really a hard restriction? Does anyone have a way around it? . . 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 robin...@sce.com<mailto:robin...@sce.com> ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
