;-) Sorry for the snarky comeback. I got carried away with my current fav 'true dat'.
I logged on to two different sysplex members. They use GRS, but I don't think that's your problem. Here's what I see: useird.$SYSX0.SPFLOGn.LIST on SYSX0 userid.$SYSX1.SPFLOGn.LIST on SYSX1 That is, my two sysplex members use different DSNs for log (and other) data sets. Each one has &SYSCLONE built into the name, so there could never be a conflict. That protects against any possible conflict whether concurrent use or ISPF level difference. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [email protected] From: "Gibney, Dave" <[email protected]> To: [email protected], Date: 04/25/2014 01:03 PM Subject: Re: ISPF Log error Sent by: IBM Mainframe Discussion List <[email protected]> Thanks, I will look at that setting. I don't remember doing anything with that when I installed 1.13, so I bet that is it. And might not be an issue in my two other LPARs (Development and Production) where the Catalogs and "stuff" aren't as broadly shared. > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Dana Mitchell > Sent: Friday, April 25, 2014 12:54 PM > To: [email protected] > Subject: Re: ISPF Log error > > Dave, > > Do you have 'Profile Sharing' turned on? IIRC that was new with 1.13. In > addition to allowing safe sharing of ISPPROF between systems, it also > provides: > > 1.3.3.2 Temporary data set names > > > The ISPF Configuration utility provides an option to specify an additional > qualifier for ISPF temporary data sets, including Log, List and temporary > control and work data sets. The use of this qualifier also includes trace > data sets from ISPVCALL, ISPDPTRC and ISPFTTRC. When Profile Sharing has > been enabled and no value has been specified for the additional qualifier, > a value of "ISP&SEQ" is used, where &SEQ is a system symbolic variable > that has the same value as defined by the ISPF dialog variable ZSEQ. > > > Dana > > > > > On Fri, 25 Apr 2014 19:35:56 +0000, Gibney, Dave <[email protected]> > wrote: > > >Since moving my sandbox LPARs to z/OS 1.13, I have been getting this error > message frequently. So for, I just pressed the Enter key and continued. It > finally irritated me enough to ask if others have this experience. It is possible > it is due to the way I have the these two LPARs sharing disk and catalogs and > "stuff" without any GRS protection. > > > >**** ISPF Log error **** > >**** ISPF will continue without log data set *** > > > >Dave Gibney > >Information Technology Services > >Washington State University ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
