CWWKB0062E message indicates that the z/OS Angel process is ALREADY running, CWWKB0063I Active Angel ASID 1ce JOBNAME IZUANG1' indicates that the Liberty JVM Server connected to and will use, the existing Angel process. So from a configuration perspective, there is nothing you have to do to have the products connect to use an existing Angel process.

But it is possible to start two Angel processes (say ANGEL1 and ANGEL2), so that two different instances of Liberty can be associated with their own distinct Angel processes via a bootstrap property (com.ibm.ws.zos.core.angelName=).

Here's a couple of links to the WebSphere Application Server for z/OS Liberty documentation about how to do this :

• Named Angel

• Enabling z/OS authorized services on Liberty for z/OS

I'd also like to share the inner-workings of this with you as follows:

The angel needs to be running for both zOSMF and Liberty Servers if system services are required. Angel runs in an authorized key so that it can load and access system services such as SAF, WLM, dump servies and WOLA on behalf of Liberty or zOSMF.

If the two products are to share an Angel process, and the zOS Connect NAME variable is left blank in the PROC to start the Angel process for zOS Connect, then one of the PROCs to start the Angel Process will fail, depending on what product is started first. If the PROC to start zOSMF is executed, the PROC to start the angel process will also be executed. Later, when the zOS Connect PROC is executed, z/OS Connect will discover the 'already running' Angel process, but the PROC to start the zOS Connect angel will get a warning saying that 'an' Angel process is already started.

If you want a different Angel process for each, then use the NAME variable in the zOS Connect PROC to distinquish the zOS Connect Angel process from the zOSMF default angel process.