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*
SYSNAME: ZOSB
DUPLEXING: STAGING DATA SET
GROUP: PRODUCTION
ATR.CTSPLEX.DELAYED.UR *DASDONLY*
SYSNAME: ZOSB
DUPLEXING: STAGING DATA SET
GROUP: PRODUCTION
ATR.CTSPLEX.MAIN.UR *DASDONLY*
SYSNAME: ZOSB
DUPLEXING: STAGING DATA SET
DUPLEXING: STAGING DATA SET
GROUP: PRODUCTION
ATR.CTSPLEX.RESTART *DASDONLY*
SYSNAME: ZOSB
DUPLEXING: STAGING DATA SET
GROUP: PRODUCTION
ATR.CTSPLEX.RM.DATA *DASDONLY*
SYSNAME: ZOSB
DUPLEXING: STAGING DATA SET
GROUP: PRODUCTION
BBO.WAS.ERROR.LOG *DASDONLY*
SYSNAME: ZOSB
DUPLEXING: STAGING DATA SET
GROUP: PRODUCTION
CICSTS31.CICSVR.DFHLGLOG *DASDONLY*
CICSTS31.LOG.MODEL *DASDONLY*
CICSUSER.CICS2.DFHLOG *DASDONLY*
CICSUSER.CICS2.DFHSHUNT *DASDONLY*
CICSUSER.CICS2.DFHSHUNT *DASDONLY*
CICS1USR.CICS1.DFHLOG *DASDONLY*
SYSNAME: ZOSB
DUPLEXING: STAGING DATA SET
GROUP: PRODUCTION
CICS1USR.CICS1.DFHSHUNT *DASDONLY*
SYSNAME: ZOSB
DUPLEXING: STAGING DATA SET
GROUP: PRODUCTION
IBMUSER.CICS1.DFHLOG *DASDONLY*
IBMUSER.CICS1.DFHSHUNT *DASDONLY*
SYSPLEX.LOGREC.ALLRECS *DASDONLY*
SYSNAME: ZOSB
DUPLEXING: STAGING DATA SET
GROUP: PRODUCTION
SYSPLEX.OPERLOG *DASDONLY*
SYSNAME: ZOSB
DUPLEXING: STAGING DATA SET
DUPLEXING: STAGING DATA SET
GROUP: PRODUCTION
ZOSB.DFHLOG.MODEL *DASDONLY*
ZOSB.DFHSHUNT.MODEL *DASDONLY*
NUMBER OF LOGSTREAMS: 000018
Do we have any luck on stopping this error.
Regards,
Jags
On Tue, Apr 5, 2011 at 11:54 AM, Barbara Nitz <[email protected]> wrote:
> >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 stream. You also
> neglected to provide the error you're getting in sdsf when you try to
> access
> operlog and/or syslog.
>
> From your wording ("we are having a trouble in accessing the SYSLOG"), I
> also assume that you have a problem with SDSF, not with operlog. There
> shouldn't be any problem with issuing the commands in SDSF.U (the user
> log),
> as that doesn't access the hardcopy log for display.
>
> Barbara Nitz
>
> ----------------------------------------------------------------------
> 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
