Thanks everyone,
Gadi
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Allan Staller
Sent: Wednesday, May 15, 2019 3:39 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Logrec Logstream name
In the logger policy, and IIRC, in LOGREC= in IEASYS00.
HTH,
-Original
In the logger policy, and IIRC, in LOGREC= in IEASYS00.
HTH,
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Gadi Ben-Avi
Sent: Wednesday, May 15, 2019 7:35 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Logrec Logstream name
Thanks
Where do I define the name of the
With no coupling facility, you are limited to DASD-Only logstreams.
DASD-only logstreams *CAN NOT* be shared.
It is (IMO) not worth the effort to convert to logstreams for EREP when DASD
only.
EREP, these days, is pretty much limited to software records, and thus there is
limited value to a logs
esday, May 15, 2019 3:29 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Logrec Logstream name
>
> Gadi
> If you do not have a coupling facility, them the logstream has to be DASD-
> only and can not be shared between LPARS. See here:
>
>
> https://www.ibm.com/suppo
Thanks
Where do I define the name of the logstream for LOGREC?
Gadi
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Mike Shorkend
Sent: Wednesday, May 15, 2019 3:29 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Logrec Logstream name
Gadi
If you do not have a coupling
Gadi
If you do not have a coupling facility, them the logstream has to be DASD-
only and can not be shared between LPARS. See here:
https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.ieag200/cfod.htm
You will need to use a unique name for each logstream. You could use th
