I should have added to not forget to circle back around, and delete the renamed
logstream at some point.
Dave Jousma
Vice President | Director, Technology Engineering
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of
Jousma, David <000001a0403c5dc1-dmarc-requ...@listserv.ua.edu>
Date: Tuesday, April 2, 2024 at 6:38 AM
To: IBM-MAIN@LISTSERV.UA.EDU <IBM-MAIN@LISTSERV.UA.EDU>
Subject: Re: Loss of data for logstream
Mark, We’ve run into the problem before, either on a single CF sandbox system,
or when we did GDPS region swaps. Let me cut/paste a couple snippets for you
DATA TYPE(LOGR) REPORT(NO) UPDATE LOGSTREAM NAME(IFASMF. ALSSYS. DATA)
NEWSTREAMNAME(IFASMF. ALSSYS. ZATA)
Mark,
We’ve run into the problem before, either on a single CF sandbox system, or
when we did GDPS region swaps. Let me cut/paste a couple snippets for you
DATA TYPE(LOGR) REPORT(NO)
UPDATE LOGSTREAM NAME(IFASMF.ALSSYS.DATA)
NEWSTREAMNAME(IFASMF.ALSSYS.ZATA)
Then when you redefine your logstream, enable these options too. Since then,
weve never had a lost data problem.
UPDATE LOGSTREAM NAME(IFASMF.ALSSYS.DATA)
STG_DUPLEX(YES) DUPLEXMODE(UNCOND)
Dave Jousma
Vice President | Director, Technology Engineering
This e-mail transmission contains information that is confidential and may be
privileged. It is intended only for the addressee(s) named above. If you
receive this e-mail in error, please do not read, copy or disseminate it in any
manner. If you are not the intended recipient, any disclosure, copying,
distribution or use of the contents of this information is prohibited. Please
reply to the message immediately by informing the sender that the message was
misdirected. After replying, please erase it from your computer system. Your
assistance in correcting this error is appreciated.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
