PARMLIB(IEASYSxx)
LOGREC parameter

On Wed, 15 May 2019 at 15:35, Gadi Ben-Avi <[email protected]> wrote:

> Thanks
> Where do I define the name of the logstream for LOGREC?
> Gadi
>
> -----Original Message-----
> From: IBM Mainframe Discussion List <[email protected]> On Behalf
> Of Mike Shorkend
> Sent: Wednesday, May 15, 2019 3:29 PM
> To: [email protected]
> 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/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 the
> &SYSNAME. system symbol as part of the name to make things easier.
>
> HTH
>
> Mike
>
>
>
>
>
> On Wed, 15 May 2019 at 14:57, Gadi Ben-Avi <[email protected]> wrote:
>
> > Hi,
> > We have a basic sysplex with two members.
> > There is no coupling facility.
> >
> >
> > 1.       Is it possible to use the same logrec logstream
> > (SYSPLEX.LOGREC.ALLRECS) for both systems.
> >
> > 2.       If not, how do I specify different a logstream for each system?
> >
> > We are using z/OS v2.3
> >
> > Gadi
> >
> >
> > ----------------------------------------------------------------------
> > For IBM-MAIN subscribe / signoff / archive access instructions, send
> > email to [email protected] with the message: INFO IBM-MAIN
> >
>
>
> --
> Mike Shorkend
> [email protected]
> www.shorkend.com
> Tel: +972524208743
> Fax: +97239772196
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions, send email
> to [email protected] with the message: INFO IBM-MAIN
>


-- 
Mike Shorkend
[email protected]
www.shorkend.com
Tel: +972524208743
Fax: +97239772196

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to