>>IXG014E LOGSTREAM SYSPLEX.OPERLOG IS CURRENTLY IN USE >>IXG002E LOGR POLICY PROCESSING ENDED WITH RETCODE=00000008 RSNCODE=00000810
If IXCMIAPU tells you that IxgRsnCodeStreamInuse then you're not looking at the right definitions, either via command or in the IXCMIAPU job. When I had to redefine operlog logstream, the things I did were: 1. Check if any TSO user was stuck in SDSF-operlog. Cancel them mercilessly. 2. ro *ALL,V OPERLOG,HARDCPY,OFF Check via D C (better route this to all systems in the sysplex, too) that all systems complied and got rid of operlog. My LOGR policy is set up in such a way that I first delete the log stream, then the structure definition and then redefine them (first structure, then log stream). If the delete doesn't go through, *something* is still using the log stream. Bring out all the D logger commands to check again. But SDSF users were the only culprits in my experience. (Oh, and once things are redefined, v operlog back on.) Best regards, Barbara ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
