Installing Other vendor products, the client got sporadic S0C4 abends:
*TSS9999E CA-TSS SECURITY SVC ABEND S0C4 IN TSSKERNL+25940
*TSS9999E ABENDING JOB=XXXXXX ACID=RW132 FUNCTION=I
*TSS9999E CA-TSS SECURITY SVC ABEND S0C4 IN TSSRSVCS+F33
The nature of the abend suggests that the product may be swapping ACEEs at the address space level.
The design of our MULTIUSER processing depends on the address space ACEE remaining constant for the live of the address space.
If this abend really is being caused by ACEE swapping, the facility will have to be set to SUAS to let us know that the product is doing something incompatible with MULTIUSER.
This will lose profile sharing, cleanup of ACEEs at address termination, and the SIGN(S) restriction if it is in use. But it may be necessary to prevent the abends.
The facility can be set to SUAS, as the following:
Setting the facility to SUAS by the following in the startup parms:
This can also be issued after startup as F TSS,FAC(Vendor-facility=SUAS) from a console or TSS MODIFY(FAC(Vendor-facility=SUAS)) from TSO.
This recommendation will resolve this case.