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.