CA MICS

New CICS regions getting rejected with MICS - not defined in CICOPS?

  • 1.  New CICS regions getting rejected with MICS - not defined in CICOPS?

    Posted 05-12-2015 12:46 PM

    If you have any new CICS regions getting rejected because they not defined in your CICOPS member, don't blame the CICS SYSPROGs.  Remember, any new region needs to have its CICOPTS statement (and most important the VTAM APPLID) added so that the input data is not rejected.

     

    Instead have a look at implementing the MICS CICS component's USRSCID exit for auto-identification of new, incoming CICS regions' data.  Why stress over needing to pay attention to the MICS DAY040 (CICS component) daily MICSLOG in order to be sure no new systems are being rejected.

     

    And also with a recently added MICS CICS component feature, you can ensure any new-version of CICS data being input will not just be rejected resulting in that data being lost -- instead, look at adding the VERIFY RELEASE statement to your CICOPS so that MICS will force an ABEND on a new-version input condition.  Check the MICS CICS component documentation in Chapter 7 for the details.

     

    Scott Barry

    SBBWorks, Inc.