Broadcom Mainframe Software Community

 View Only

 IRRSEQ00 (R_admin) returns a warning although ACF2 OMVS segment is created successfully

Himani Pathak's profile image
Himani Pathak posted Jun 29, 2026 04:21 AM

Hi Team,

We are investigating an issue with the mainframe security API IRRSEQ00 (R_admin) while working with ACF2.

The sequence is as follows:

1. We create the base user account.

This completes successfully with RC=0.

2. We then issue an INSERT request through IRRSEQ00 to create the OMVS segment.

This request returns RC/RSN = 8/16/4 WARNING Even though OMVS segment is created successfully.

The user's OMVS segment is created correctly, and a manual LIST PROFILE(ALL) confirms that the OMVS segment exists with the expected UID, HOME, and OMVSPGM values.

As part of our investigation, we have also verified that this is not caused by stale data in our application. We manually cleared the memory blocks and zeroed out the safRC and acf2fRC variables before each API call, but the behavior remains unchanged.

Has anyone encountered a situation where IRRSEQ00 (R_admin) returns a failure or warning status even though the INSERT operation is successfully committed to the security database?

If so:

  • Is this expected behavior under certain conditions?
  • Is there any known APAR or documentation describing this behavior?
  • Which return code and reason code should be considered authoritative in this scenario?

Any insights would be greatly appreciated.

snippest of my log

caacf2Adm: ACF returned ACF0A005

DTL:26/05/15 03:18:29 Thread:000004 issueRadmin duplicate output returned 130

DBG:26/05/15 03:18:29 Thread:000004 issueRadmin: safRC = 8, acf2fRC = 16, Reason = 4, returning rc = 4

 

Any insights would be greatly appreciated.

Thanks.

Asim Zaidi's profile image
Broadcom Employee Asim Zaidi

If you have verified that the OMVS segment was created successfully 
(e.g., by issuing LIST or SHOW OMVS in ACF2), you can safely ignore the 8/16/4 warning. 
It is a byproduct of how the SAF R_admin interface translates ACF2's success/informational messages.

    To verify the segment native to ACF2:  SET PROFILE(USER) DIV(OMVS) LIST logonid
    Note: If you are seeing this in a report like ACFRPTOM, it is considered an 
          "expected" non-zero return code for many USS-related administrative tasks.

When the IRRSEQ00 (R_admin) callable service returns SAF RC=8, Reason=16 (0x10), and Warning=4 (0x04), 
it indicates that the command was processed by the External Security Manager (ACF2), 
but it completed with informational messages or warnings. 
***

Himani Pathak's profile image
Himani Pathak

Hi Asim Zaidi,

Thank you for your confirmation and time.
But I have one more question if it is warning by product then why for other I'm seeing 

safRC = 0, acf2RC = 0, Reason = 0, returning rc = 0
for other ??

 

Thankyou,
Himani