It may be a bad idea. And actually I agree. But, my z9-L03 capped at 16 MSU doesn't have an ICF or any resources to fire up GRS in ring mode, let alone star. Since I am the only user in one sandbox and one of two sysprogs in the other, we get by. :) The message does not occur with z/OS 1.11 with the same mix of monoplexes.
> -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Skip Robinson > Sent: Friday, April 25, 2014 12:40 PM > To: [email protected] > Subject: Re: ISPF Log error > > True dat. Bad idea. > > . > . > 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 12:36 PM > Subject: ISPF Log error > Sent by: IBM Mainframe Discussion List <[email protected]> > > > > 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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
