Resolving The Problem

When dealing with a merged AON/SA into the same NetView, the recommendation we have is to use a different set of autotasks for SA gateways than you do for AON gateways. This will allow the two process to work independently and eliminate any chance of overlap or inconsistencies.

For example, lpar1 has combined SA/AON NetView asid (domain CNM01) and lpar2 has combined SA/AON NetView asid (domain CNM02). Following are advised gateways between these two NetView regions:
AON GATOPERs - GATNV001, GATNV002
SA GATOPERs - GATSA001, GATSA002

In the AON EZLCFG01 one defines the AON gateway operators, and in the SA PDB you define the SA gateway operators, and each can function separately from the other set of operators. One would still associate the domain related info to the correct domain (ie. Focal Point domain is CNM01 but the actual operators used for the unique AON/SA services will be different).

Not covered in this article are the related underlying definitions:
a) DSIOPF / DSIOPFU
b) CNMSCAT2 Command Authorization Table
c) SAF security (ie RACF)

The definitions in these areas will depend on the specific NetView security definitions for operator security (OPERSEC) and command level security (CMDAUTH). Each of the suggested gateway operator ids will have to be defined in these locations as appropriate for the customer environment, using standard definition formats.