Hi, Its a MonoPlex. The Logger storage group volume Loger01 was fully exhausted and we deleted some orphaned Log datasets and this Error message has stopped popping. On Wed, Apr 6, 2011 at 7:04 PM, Nick Jones <[email protected]> wrote:
> Hi Jags, > > I see: > > >SYSPLEX.OPERLOG *DASDONLY* > > SYSNAME: ZOSB > > DUPLEXING: STAGING DATA SET > > DUPLEXING: STAGING DATA SET > > GROUP: PRODUCTION > > When you configure Operlog as a dasdonly log stream, you can only access it > from > one system in your sysplex at a time. Is operlog connected on system ZOSB > and > you are trying to use it on another system in your plex, perhaps ZOSA? > > -Nick Jones > Logger L3 > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: GET IBM-MAIN INFO > Search the archives at http://bama.ua.edu/archives/ibm-main.html > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
