With CA ACF2 CICS I am getting a SECN abend when a CICS user tries to connect to another CICS region via an MRO connection. What is wrong or missing?

Products

• ACF2
• ACF2 - DB2 Option
• ACF2 for zVM
• ACF2 - z/OS
• ACF2 - MISC

Issue/Introduction

Question:  

With CA ACF2 CICS I am getting a SECN abend when a CICS user tries to connect to another CICS region via an MRO connection.  What is wrong or missing?

 

Answer: 

 

The SECN abend indicates:

 

The CA ACF2 CICS MRO control blocks passed from one system to another are too long for the receiving system to process or invalid FMH protocols were found on the inbound data stream. The task abends with a dump.  

 

A common reason for this is that the mini-lid structure is different between the 2 regions that are MRO connected, or one of the regions is not using mini-lids.  

 

Ensure that the mini-lid structure is the same for each CICS region connected via MRO.  When creating (or cloning) new CICS regions, ensure that the @MUSASS (defined in the ACFFDR) specifies the desired @MLID specification for the new region.  If using GSO MUSASS records, ensure that the MUSID field specifies the logonid for the new CICS region.

 

 

Additional Information:

• CA ACF2 Messages Guide, for the SECN abend description.
• CA ACF2 CICS Support Guide, Chapter 3 (Installation) under the sections for "Review ACFFDR Values Relevant to the CICS interface" and "Review GSO MLID and MUSASS Record Values or ACFFDR Values Relevant to CA ACF2 CICS."
• CA ACF2 Administration Guide, Chapter 14 (GSO Records), under the MLID record and MUSASS record.

 

Environment

Release:
Component: ACF2MS

Resolution

-