Configure a separate z/OSMF server instance

To set up a separate z/OSMF server instance, you must configure it as described in this topic. You can then deploy an application, like a z/OSMF plugin, on this separate server so that it will not be impacted or impact other z/OSMF plugins. This is especially useful if your application is more complex and requires more resources such as CPU, memory, and network bandwidth.

Setup a separate z/OSMF server by reusing existing z/OSMF security setup

If you already have z/OSMF Server running on your system, this means your z/OSMF Configuration has already been set up. In this case, follow these steps to configure and start a separate z/OSMF server.

  1. Run job IZUMKFS to create the z/OSMF user file system.

    1. This step is the same as Step 2: Run job IZUMKFS to create the z/OSMF user file system except you need to modify IZUMKFS to ensure that the new file system is mounted to the other mount point like /var/zosmf, not /global/zosmf. This is because /global/zosmf is supposed to be the mount point of your primary z/OSMF server’s user file system, which is already being used.

  2. Make a copy of your current z/OSMF server’s PARMLIB and change the port number, and remove the unnecessary plugins in the PARMLIB.

    1. For example, if the z/OSMF server you are currently running is using IZUPRM00, you can make a copy of IZUPRM00 and name it IZUPRM01. You can then change the HTTP_SSL_PORT statement in IZUPRM01 to ensure that the new separate z/OSMF server uses a port that is not yet being used.

      For more information, see IZUPRMxx reference information.

  3. Start this separate z/OSMF server.

    1. This step is the same as Step 4: Start the z/OSMF server, except you don’t need to start the angel process. This is because the new separate z/OSMF server uses the same angel process that is running from your current running z/OSMF server.

    2. Start this separate z/OSMF server with the following command: S IZUSVR1 JOBNAME=<job name>,IZUPRM=<parmlib suffix>,USERDIR=<user directory>, SERVER=STANDALONE

      JOBNAME should be a different name than your current running z/OSMF server job name, for example, IZUSVR2.

      IZUPRM should be the new PARMLIB created in Step 2, for example, 01.

      USERDIR should be the mount point that you mounted your new z/OSMF user file system that is created in Step 1.

      This z/OSMF server should be a stand-alone z/OSMF server. This means the separate server would not be a server of your autostart group. For more information about z/OSMF Autostart concepts, see Autostart concepts in z/OSMF.

      For more information about these parameters, see IZUSVR reference information.

    3. Here is an example command to start a separate server: S IZUSVR1 jobname=izusvr2,izuprm=01,userdir='/var/zosmf', SERVER=STANDALONE

  4. Log in to z/OSMF.

    1. This is the same step as Step 5: Log in to z/OSMF, except you use the new port number.

      When you log in to z/OSMF, the desktop interface is displayed. Only the options you are authorized to use are displayed.

  5. Enable z/OSMF service with these steps:
    1. Open the z/OSMF General Settings task.
    2. "Enable" the services that you are interested in.
    3. Restart the z/OSMF server.

Setup a separate z/OSMF server with new security configuration

In this case, it would be the same process as setting up your z/OSMF system for the first time. For more information about setting up a z/OSMF server for your specific needs, see Faster set-up with a z/OSMF Lite configuration.