We use logstreams, including for logrec and do not have any SYS1.LOGREC datasets defined. Our IEASYSxx parmlib specifies LOGREC=LOGSTREAM. We have no issues IPLing. Early in the IPL we receive message: IFB085I LOGREC RECORDING TO LOG STREAM SYSPLEX.LOGREC.ALLRECS Bill Skeldum
-----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Bill Wilkie Sent: Thursday, June 29, 2017 10:17 AM To: [email protected] Subject: Re: Logstreams Thanks, and yes, It does fail without sys1.logrec. I can't believe the system can't come up without LOGREC. I would think it should issue messages but at least let you IPL. Once you're up you can allocate a new one. Maybe Z/os could even dynamically allocate one and just keep going. From what I can gather so far about Logstreams, it just holds a bunch of different logs like Operlog, LOGREC, etc. but the data is still in it's original form as if it were read directly from the original data set. Bill ________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Jesse 1 Robinson <[email protected]> Sent: Thursday, June 29, 2017 3:45 PM To: [email protected] Subject: Re: Logstreams Logstream cannot substitute for the LOGREC data set at IPL, which others suggest is required. I checked our MSTJCLxx, but LOGREC is not named there. It is however named in IEASYSxx, where we have coded LOGREC=SYS1.LOGREC.$SYS&SYSCLONE ever since we moved to sysplex in the mid-90s. I cannot recall trying to IPL without LOGREC, but I imagine it would fail. There are good reasons for moving to logstream, but the ability to IPL is not one of them. . . 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 Lizette Koehler Sent: Thursday, June 29, 2017 7:51 AM To: [email protected] Subject: (External):Re: Logstreams So does this mean the problem you are trying to solve by asking about logstreams is Can I prevent my system from not IPL'ing if someone deletes SYS1.LOGREC? Will the logstream still allow me to IPL eve if SYS1.LOGREC is gone? Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Bill Wilkie > Sent: Thursday, June 29, 2017 5:51 AM > To: [email protected] > Subject: Re: Logstreams > > Lizette: > > > I am not using logstreams yet. I am just looking into it. > > > The SYS1.LOGREC data set got deleted on our test system so we couldn't > IPL it. We ran a job from our other system to create a new one and it IPL'd > OK. > > > Thanks > > Bill > > > ________________________________ > From: IBM Mainframe Discussion List <[email protected]> on > behalf of Lizette Koehler <[email protected]> > Sent: Thursday, June 29, 2017 12:45 PM > To: [email protected] > Subject: Re: Logstreams > > When you say you deleted a logstream - which one? > > If it is for Logrec, did you have the SYS1.LOGREC dataset still > cataloged and on the system? > > What was the corrective action that allowed you to IPL > > Lizette > > > > -----Original Message----- > > From: IBM Mainframe Discussion List > > [mailto:[email protected]] On Behalf Of Bill Wilkie > > Sent: Thursday, June 29, 2017 2:32 AM > > To: [email protected] > > Subject: Re: Logstreams > > > > We accidentally deleted Logrec on one system, and couldn't IPL. Not > > sure if logstream being available would have made a difference. > > > > > > Bill > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN The information contained in this electronic communication and any document attached hereto or transmitted herewith is confidential and intended for the exclusive use of the individual or entity named above. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any examination, use, dissemination, distribution or copying of this communication or any part thereof is strictly prohibited. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy this communication. Thank you. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
