CICS

CICS

CICS

The world's leading application server software for IBM Z

 View Only

  • 1.  CICS - logger errors at startup after z/OS upgrade

    Posted Fri October 18, 2024 10:15 AM

    We are upgrading z/OS from 2.4 to 3.1 and when I start CICS regions up on the new z/OS version the regions are getting logger errors like this:

    +DFHLG0772 YCICSTS1  546                                              
     An error has occurred during z/OS logger operation IXGBRWSE START for
     log stream YCICSTS1.YCICSTS1.DFHLOG. z/OS logger codes: X'00000008', 
     X'0000084A'.

    I can resolve this by starting up as initial.  Does anyone know if CICS typically requires an initial start after z/OS upgrades?  Or some other special startup processes following an OS upgrade?  Any suggested documentation to review related to this?

    Thank you!



    ------------------------------
    Tracy Ison
    ------------------------------


  • 2.  RE: CICS - logger errors at startup after z/OS upgrade

    Posted Mon October 21, 2024 06:46 AM

    Greetings Tracy,

    Immediate answer is no, CICS should not require an initial start after a z/OS upgrade. I've not looked up that combination of response and reason codes but my immediate wonder is whether as part of the upgrade, the logstreams were redefined in some way or the off load data sets were no longer available?



    ------------------------------
    Andy Clifton
    CICS Test and Consolidated Service Test
    IBM Hursley Park
    ------------------------------

    Original Message


  • 3.  RE: CICS - logger errors at startup after z/OS upgrade

    Posted Mon October 21, 2024 09:24 AM

    Hi Andy,

    Thank you for confirming my thinking that an initial start should not be required.  I found that due to naming conventions (we are using DASD only log streams) the log stream datasets were not ending up in our z/OS 3.1 catalog.  So, after the upgrade to z/OS 3.1 (new master catalog), the log stream datasets used at shutdown were not found, same if we tried to fall back to z/OS 2.4.  Somehow our CICS regions started using the default journal models for dfhlog and dfhshunt instead of our custom / standard journal model definitions.

    I believe to resolve this issue and proceed with our z/OS upgrade without needing to start CICS with an initial start, I'll need to update the logstream(s) our CICS regions are using for dfhlog and dfhshunt to conform to our naming conventions.  I suspect this defect may have been introduced with the last CICS upgrade and was not discovered until the z/OS upgrade now.

    Seems like to resolve this I will require an initial start once to update the log stream definition being used.  Thus far I'm not clear why CICS is not picking up our standard journal model definition that is later in our group list(s) than the default definition when doing an intial start.  I would have thought that restarting as initial once would have resolved this issue but thus far it seems to persist when we upgrade to z/OS 3.1 or fall back to z/OS 2.4.

    I'm continuing to investigate.  I will update here when I resolve this or if I have further questions.  Really appreciate your confirmation, Andy!

    Thank you again!!

    Tracy



    ------------------------------
    Tracy Ison
    ------------------------------

    Original Message


  • 4.  RE: CICS - logger errors at startup after z/OS upgrade

    Posted Wed October 23, 2024 09:43 AM

    Hi Tracy,

    It's not uncommon to encounter some issues like this when upgrading your z/OS, especially with something as integral as CICS regions. Starting up as initial can often help, as it resets the system to a clean state. Regarding CICS typically requiring an initial start after an OS upgrade, it isn't always necessary, but it can help avoid complications like the logger errors you're experiencing.

    I would recommend checking IBM's documentation specific to upgrading z/OS, particularly sections that discuss compatibility and startup procedures post-upgrade. IBM's Knowledge Center or CICS documentation would be great places to start. If the issue persists, reaching out to IBM support or checking with other IBM community forums might also provide more targeted insights.

    Hope this helps and your upgrade goes smoothly from here!



    ------------------------------
    Yusuf K
    ------------------------------

    Original Message


  • 5.  RE: CICS - logger errors at startup after z/OS upgrade

    Posted Wed October 23, 2024 09:44 AM

    Hey Tracy,

    It's quite common to encounter issues like this when upgrading z/OS, especially with CICS regions due to dependencies and changes in the environment settings. Starting up as initial can indeed resolve some of these conflicts as it resets the system to a clean state. It's generally a good practice to perform an initial start of CICS regions after a major OS upgrade to ensure all components are correctly initialized.

    For documentation and best practices on handling CICS regions during z/OS upgrades, I'd recommend checking IBM's official documentation specific to CICS and z/OS compatibility and migration guides. Also, consulting the IBM Redbooks related to z/OS upgrades might provide detailed insights and recommended procedures.

    Hope this helps, and good luck with your upgrade!



    ------------------------------
    Yusuf K
    ------------------------------

    Original Message


Related Content