Skip to content

Setting Up Load Balancing

The instructions in this chapter assume that you installed ChangeMan ZMF according to instructions in the ChangeMan ZMF Installation Guide.

Load Balancing Architecture

ChangeMan ZMF may be implemented in various ways, depending on your requirements:

  • One or several independent ALL sites

  • Several related DP sites

  • One or several combinations of DP and P sites

  • A mix of any of the above.

Use of the Load Balancing Option allows users and administrators to logon to a ChangeMan ZMF instance from another CPU or MVS image, but it does not change the function of any ChangeMan ZMF instance or the relationships between instances in a complex implementation.

In particular, DP and P site combinations are still required where the production environment does not share DASD and catalogs with the development environment. The ChangeMan ZMF servers that make up a DP and P site combination still communicate using the Transmission Vehicle defined in Global Administration.

Requirements

All CPUs or MVS images where ChangeMan ZMF ISPF client programs or ChangeMan ZMF server programs run must meet these requirements to use the Load Balancing Option:

  • TCP/IP started task, one per CPU or image.

  • Shared DASD and catalog. (This is required to access components in stage and baseline libraries.)

  • License for the Load Balancing Option of ChangeMan ZMF.

A SERNET started task is not required to run ChangeMan ZMF client programs.

Installation Procedures

Use these instructions for installing the Load Balancing Option.

LBO Option License

If you license the LBO Option at the same time that you license ChangeMan ZMF, the license for the option is applied when you apply the license for the base product. You do not have to take further action to enable the LBO Option.

If you license the LBO Option after you apply licenses for ChangeMan ZMF and other selectable options, use the SER10TY™ License Manager to add a license for the option. See the SER10TY User Guide for instructions on how to apply a license. The load modules, JCL, and other components that you need to run SER10TY are included in the SERCOMC libraries in the ChangeMan ZMF installer.

Installation Procedures

After you have applied a license, shut down the SERNET started task where ChangeMan ZMF runs and restart the task.

ChangeMan ZMF Server Setup

Ensure that the SERNET started procedure that runs the target ChangeMan ZMF server contains:

  1. DD statement SER#PARM. See SER#PARM DDNAME in the ChangeMan ZMF Installation Guide.

  2. Keyword parameter CMN=(,port). See SERNET Options For ChangeMan ZMF in the ChangeMan ZMF Installation Guide.

ChangeMan ZMF Client Setup

On the image where you will use the Load Balancing Option to connect to a ChangeMan ZMF server, do the following:

  1. Ensure that the logon CLIST used to connect to the target ChangeMan ZMF server contains an ALLOC DD statement for SER#PARM. See “Building the Logon CLIST” in the ChangeMan ZMF Installation Guide.

  2. Ensure that the logon CLIST contains parameter CON() or CON(T). See “Building the Logon CLIST” in the ChangeMan ZMF Installation Guide.

  3. Add an option that executes the ChangeMan ZMF logon CLIST to the appropriate ISPF menu where users wish to logon to ChangeMan ZMF.

TCP/IP Logon CLIST

You must create a special logon CLIST if the name of the TCP/IP procedure on the MVS image where you will logon to ChangeMan ZMF is different from the TCP/IP procedure on the image where the ChangeMan ZMF server runs. This CLIST will use a special parameter file for the SER#PARM ddname.

  1. Create a new parameter file and #SERx member for the SER#PARM ddname:

    1. Allocate a parameter file with the same attributes as the TCPIPORT used for the SER#PARM ddname in the SERNET procedure JCL. You should not use an existing library.

    2. Copy the #SERx member (where “x” is the subsystem ID of the ChangeMan ZMF server instance) from the server TCPIPORT file into the new library.

    3. Edit the #SERx member. Add the client site TCP/IP procedure name to the CMN record in positions 39 to 46. In this sample code, “pppppppp” is TCP/IP procedure name on the client site.

       SMFI.SUBS APP DOT.TED.DEC.MAL PORT\# TCPIPROC --Update-Time-Stamp BH3A.SER7 CMN 172.20.105.170 06190 pppppppp

    4. Save the edited #SERx member.

  2. Create a new logon CLIST:

    1. Copy the logon CLIST for the ChangeMan ZMF instance to a new CLIST member name.

    2. Edit the new CLIST and change the ALLOC statement for the SER#PARM ddname to point to the new parameter library created above.

Security

The database for your security system (RACF®, CA-ACF2®, or CA-Top Secret®) may be shared across the MVS images that you will use for ChangeMan ZMF server programs and the Load Balancing Option. If this is the case, no special security entries are required for the Load Balancing Option.

If the security database is not shared, make the following security entries on the image where Load Balancing will be used:

  1. Grant users ALTER (ALLOCATE, READ, UPDATE, DELETE) access to ChangeMan ZMF temporary data sets. High level qualifiers for ChangeMan ZMF temporary detests are set in exit program CMNEXINS.

  2. You do not need to add a resource class or any of the security entities that restrict access to ChangeMan ZMF functions. Security checking is performed by ChangeMan ZMF server programs.