Configuring named angels

Configuring multiple angel processes in an LPAR.

1. Define SERVER SAF profiles and grant permissions to the SAF user ID that the IBM z/OS Connect server is running under, by issuing the following commands:
   For example, if the angel process is started with a name of PRODUCTION, then a SAF SERVER profile for this name, BBG.ANGEL.PRODUCTION must be defined and the IBM z/OS Connect server that is running under identity USER1 must be given READ access as in the following definition.

   
   RDEFINE SERVER BBG.ANGEL.PRODUCTION UACC(NONE) OWNER(SYS1) 
   PERMIT BBG.ANGEL.PRODUCTION CLASS(SERVER) ACCESS(READ) ID(USER1) 
   SETROPTS RACLIST(SERVER) REFRESH

   Tip: You can use generic profiles such as BBG.ANGEL.* to grant a user ID access to multiple named angels.

   The SETROPTS command is issued to refresh the profiles.

2. Restart IBM z/OS Connect to use the new profile.
3. Define a named angel by coding the NAME parameter of the operator START command.
   The angel name can be 1 - 54 characters in length, and must use only the following characters: 0-9 A-Z ! # $ + - / : < > = ? @ [ ] ^ _ ` { } | ~ The angel name must be unique on the LPAR. Two angels with the same name cannot be running concurrently on the LPAR. You can have a maximum of 4092 named angels on an LPAR.

The following steps are required only if you run IBM z/OS Connect as a stand-alone server.

If you run IBM z/OS Connect embedded in CICS®, you must add these directives to the JVMServer profile that is configured for the IBM z/OS Connect server.

Choose one of the following methods to configure the server for named angels. Choose either JVM_OPTIONS or bootstrap properties.

4. Optional: Use JVM_OPTIONS to configure the server for named angels.
   1. Create a file called <name>.options in the IBM z/OS Connect Liberty server configuration directory.
      This file defines the Java™ system properties com.ibm.ws.zos.core.angelName and com.ibm.ws.zos.core.angelRequired. In this example, the angel name is PRODUCTION. The angel name is case-sensitive and must be all uppercase. For example,

      
      -Dcom.ibm.ws.zos.core.angelName=PRODUCTION
      -Dcom.ibm.ws.zos.core.angelRequired=true 

   2. Edit the JVM_OPTIONS parameter of the STDENV JCL procedure to add a reference to this options file.

      
       //STDENV   DD   *                                                      
       _BPX_SHAREAS=YES                                                       
       JAVA_HOME=/usr/lpp/java/J8.0_64/                                       
       WLP_USER_DIR=/var/zosconnect                                           
       JVM_OPTIONS=-Xoptionsfile=/var/zosconnect/servers/<serverName>/<name>.options  
       //*   

5. Optional: Use bootstrap properties file to configure the server for named angels.
   1. Edit the bootstrap.properties file in the server configuration.
      If you do not already have a file called bootstrap.properties in the IBM z/OS Connect server configuration directory, create one now. The file can be in ASCII or EBCDIC. This file defines the properties com.ibm.ws.zos.core.angelName and com.ibm.ws.zos.core.angelRequired. The angel name is case-sensitive and must be all uppercase.
      For example, if the angel name is PRODUCTION, then the bootstrap.properties file would contain the following statements,

      
      com.ibm.ws.zos.core.angelName=PRODUCTION
      com.ibm.ws.zos.core.angelRequired=true 

6. Optional: Restrict the z/OS authorized services required by the IBM z/OS Connect server.
   Modify the property com.ibm.ws.zos.core.angelRequiredServices in the bootstrap.properties file as described in Configuring the Liberty Angel process and z/OS authorized services.