Create workload when first target AOR region joins

CICSPlex SM needs to allow the creation of the workload as soon as an AOR connects to a CMAS where the target region is named in the AORSCOPE of any workload. The workload does not get created until the first router region is activated. This method makes it difficult for automated processes to administer the workload.

The user created a process to dynamically activate or quiesce target regions from WLMAWAOR workload. The process browses the WLMAWORK table and issues the quiesce/activate commands against each WLMAWAOR entry as needed.

This is done via both CICS PLT startup or transaction entered via terminal; if we want to quiesce/activate after startup.

When the AOR targets start up, it looks like the WLMAWORK entry is not being created when the target region is registered to CPSM; I can see the region in the CICSRGN view. Once the router region is registered to CPSM, then the WLMAWORK entry is created.

The problem is that when the CICS TARGET regions start, there is no
entry found in the WLMAWORK table; therefore no QUIESCE is issued
because the WLMAWAOR entry does not yet exist. After all the targets start the TOR then starts, building the WLMAWAOR entry for each of the
targets; all the targets are in ACTIVE status (which is what we don't want)

The CPSM manual says "A workload is active within a CICSplex as long as:
A CICS system that is acting as a routing OR TARGET region and is
participating in the workload is connected to that CICSplex."

If I shut down the router region, the WLMAWAOR still exists with on the AOR TARGET, which is what I'd expect. Router count=0.

What I did not expect is that the WLMAWAOR not being created when started and defined to the workload. We want to have a stable base of CICS TARGET regions before we introduce the TOR at startup.