Martin, First remark: Operlog does not manage the staging dataset, System Logger does. Operlog is only a user of System Logger.
If you can suffer the loss of data, you can delete the logstream and structure (and the remaining staging datasets) and recreate them. Kees. Ps. This newsgroup is a mirror of a listserver. Subscribe to the listserver to address the entire Ibm-main population. See the info attached automagically at the bottom. Kees. "martin" <[EMAIL PROTECTED]> wrote in message news:<[EMAIL PROTECTED]> ... > We are having problems getting our OPERLOG staging datasets back 'in > sync' after a 2 day DR test - stopping and starting OPERLOG, > deallocating and reallocating the structure and even structure > rebuilds have had no effect. We've been sysplexed since God was a boy > (in fact we were one of the first UK sites to go sysplex) but this > one's got us stumped! > > Documentation on how OPERLOG manages its staging datasets, or how we > can override what generations it uses, is nonexistent as far as we can > see. If anyone can shed any light on how we sort this we'd be very > grateful - we are still on OS/390 2.10 (its a long story, don't ask) > so any 'official' IBM support has long since ceased to exist! > details follow..... > > > Martin Jackson > Mainframe team manager > Vertex IT Operate > Grove House, Dawson House, Great Sankey > Warrington WA5 3LW > Tel: 01925 233599 / int 33599 > mailto:[EMAIL PROTECTED] > > > --------------------------------------------- > > IXCMIAPU reports OPERLOG is using gen A0017374 of the staging dataset, > status 'pending delete', even though the dataset didn't exist. We have > tried creating the dataset so OPERLOG can delete it and clear the > 'pending' but what happens is it deletes it but still leaves it as the > current log stream in 'delete pending' state. It then abends next time > it tries to delete it. Its creating new generations of the staging > dataset but they are LOWER gen. numbers than the one it thinks its > using and IXCMIAPU lists them as 'orphans' > > IXCMIAPU output is :- > LOG STREAM CONNECTION INFO: > > SYSTEMS CONNECTED: 1 > > SYSTEM STRUCTURE CON CONNECTION CONNECTION > NAME VERSION ID VERSION STATE > -------- ---------------- -- ---------- ---------- > PRD1 C2B1DE6E418155C0 01 00010128 Active > > > LOG STREAM DATA SET INFO: > > DATA SET NAMES IN USE: LOGGER.SYSPLEX.OPERLOG.<SEQ#> > > Ext. <SEQ#> Lowest Blockid Highest GMT Highest > Local Status > ----- -------- ---------------- ----------------- > ----------------- ---- > *00001 A0017374 00000004B6C59819 07/05/08 09:52:51 07/05/08 > 10:52:51 DELETE PENDING > > NUMBER OF DATA SETS IN LOG STREAM: 1 > > > POSSIBLE ORPHANED LOG STREAM DATA SETS: > DATA SET NAMES: > -------------------------------------------- > LOGGER.SYSPLEX.OPERLOG.A0017215 > LOGGER.SYSPLEX.OPERLOG.A0017253 > > NUMBER OF POSSIBLE ORPHANED LOG STREAM DATA SETS: 2 > > > Our structure definition is :- > > . DEFINE STRUCTURE NAME(LOGGER_OPERLOG) > LOGSNUM(1) > MAXBUFSIZE(4096) > AVGBUFSIZE(535) > EFFECTIVE > AVERAGE > BUFFER > SIZE(535) > > DEFINE LOGSTREAM NAME(SYSPLEX.OPERLOG) > STRUCTNAME(LOGGER_OPERLOG) > LS_DATACLAS(DCLOGGER) > LS_MGMTCLAS() > LS_STORCLAS(SCSTAND) > HLQ(LOGGER) > MODEL(NO) > LS_SIZE(1000) > STG_MGMTCLAS() > STG_STORCLAS(SCSTAND) > STG_DATACLAS(DCLOGGER) > STG_SIZE(0) > LOWOFFLOAD(20) > HIGHOFFLOAD(80) > STG_DUPLEX(YES) > DUPLEXMODE(COND) > RMNAME() > DESCRIPTION() > RETPD(0) > AUTODELETE(NO) > DASDONLY(NO) > > Error from IXGLOGR when it tries deleting the (nonexistent) gen > A0017374 of the staging dataset is :- > > IXG251I IKJ56228I DATA SET LOGGER.SYSPLEX.OPERLOG.A0017374 NOT IN > CATALOG OR CATALOG CAN NOT BE ACCESSED > IXG063I LOGGER ABENDED AND REQUESTED AN SVC DUMP WHILE PROCESSING 450 > LOGSTREAM: SYSPLEX.OPERLOG > STRUCTURE: **UNKNOWN** > MODULE=IXGI3DSC,ABEND=S01C5,REASON=0009000C > IXG301I SYSTEM LOGGER FAILED TO OFFLOAD DATA FOR LOG STREAM 451 > SYSPLEX.OPERLOG IN STRUCTURE LOGGER_OPERLOG. RETURN CODE: 0000000C > REASON CODE: 00000000 DIAG1: 0000001C DIAG2: 17080002 DIAG3: > 0107001B DIAG4: 00000000 > > > ---------------------------------------------------------- ********************************************************************** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 ********************************************************************** ---------------------------------------------------------------------- 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
