Re: *CNZ4201E OPERLOG HAS FAILED

2011-04-07 Thread Nick Jones
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. Hi Jags, For a case of data set storage exhaustion, I would expect to see messages IXG310, IXG311, IXG312 highlighting an offload

Re: *CNZ4201E OPERLOG HAS FAILED

2011-04-06 Thread Nick Jones
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

Re: *CNZ4201E OPERLOG HAS FAILED

2011-04-06 Thread jagadishan perumal
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 nrjo...@us.ibm.com wrote: Hi Jags, I see: SYSPLEX.OPERLOG*DASDONLY*

Re: *CNZ4201E OPERLOG HAS FAILED

2011-04-06 Thread chen lucky
Hi Nick, in this case If want to access operlog from ZOSA, how to switch? 2011/4/6 Nick Jones nrjo...@us.ibm.com Hi Jags, I see: SYSPLEX.OPERLOG*DASDONLY* SYSNAME: ZOSB DUPLEXING: STAGING DATA SET DUPLEXING: STAGING DATA SET GROUP: PRODUCTION When you

Re: *CNZ4201E OPERLOG HAS FAILED

2011-04-05 Thread jagadishan perumal
Hi, Output of the command : D C,HC : RESPONSE=ZOSB IEE889I 11.26.51 CONSOLE DISPLAY 468 MSG: CURR=0LIM=1500 RPLY:CURR=1LIM=20 SYS=ZOSB PFK=00 CONSOLEID --- SPECIFICATIONS --- SYSLOG COND=H AUTH=CMDS NBUF=N/A

Re: *CNZ4201E OPERLOG HAS FAILED

2011-04-05 Thread Barbara Nitz
2) OS Version is : 1.8 The message id might have changed since then, as 1.8 is out of service. In any case, the D C,HC putput clearly shows that you still have a syslog and hence a hardcopy log. 3) Ouput of command : /D LOGGER,LOGSTREAM. You neglected to provide the status of the OPERLOG log

Re: *CNZ4201E OPERLOG HAS FAILED

2011-04-05 Thread jagadishan perumal
Hi, Apology for not being more precise. Ouput for the command : /D LOGGER,LOGSTREAM. D LOGGER,LOGSTREAM IXG601I 12.20.54 LOGGER DISPLAY 02 INVENTORY INFORMATION BY LOGSTREAM LOGSTREAM STRUCTURE - - ATR.CTSPLEX.ARCHIVE*DASDONLY*

Re: *CNZ4201E OPERLOG HAS FAILED

2011-04-05 Thread Ravi Gaur
Please hit below commands and put output.. ( D EMCS ) ( D C,KEY=OPERLOG ) ( D GRS,RES=(SYSZCNZ,*) ) Also check if there has been any Plex defined system Ipled for upgrade if yes with what version... I see no Operlog structure in your output..since not connected...

*CNZ4201E OPERLOG HAS FAILED

2011-04-04 Thread jagadishan perumal
Hi, We are getting the below error message in our SR queue, for the given below message we gave the command : * /v operlog,hardcpy but no luck. *CNZ4201E OPERLOG HAS FAILED Could anyone please guide me on. Regards, Jags

Re: *CNZ4201E OPERLOG HAS FAILED

2011-04-04 Thread Barbara Nitz
*CNZ4201E OPERLOG HAS FAILED /v operlog,hardcpy but no luck. What message exactly are you getting in response to that command? Did operlog work before? Are you using a CF log stream or a DASD-only logstream? What is the status of the operlog logstream? Were there any messages prefixed IXG

Re: *CNZ4201E OPERLOG HAS FAILED

2011-04-04 Thread jagadishan perumal
, Barbara Nitz nitz-...@gmx.net wrote: *CNZ4201E OPERLOG HAS FAILED /v operlog,hardcpy but no luck. What message exactly are you getting in response to that command? Did operlog work before? Are you using a CF log stream or a DASD-only logstream? What is the status of the operlog logstream

Re: *CNZ4201E OPERLOG HAS FAILED

2011-04-04 Thread Barbara Nitz
Also we are not able to access the LOG option from SDSF panel. What error message are you getting in SDSF? The response to a v operlog,hardcpy command is a CNZ4100I message issued in response to the internal command D C,HC: CNZ4100I 07.47.57 CONSOLE DISPLAY 041