Skip to content

Installing a ChangeMan ZMF P Instance

This provides instructions for building a ChangeMan ZMF P instance.

Introduction

The purpose of a ChangeMan ZMF P instance (environment) is to manage the contents of a set of production libraries that are under the control of ZMF at a production site. P instances are essentially slaves of D or DP instances where development is performed and baseline libraries are maintained.

P instances may reside on the same LPAR as the D or DP instance they work with, on a different LPAR with shared DASD, on a different LPAR with separate DASD, or on a completely separate z/OS machine at a physically distant location.

Differences between a P instance and development environments such as ALL, D, and DP instances include:

  • No development activities are performed on a P instance.

  • Component history is not maintained on a P instance.

  • Impact analysis information is not maintained at a P instance.

Jobs for REXX reporting are the only JCL that is created on a P instance with ISPF skeleton file tailoring.

Note

In this chapter, "the development instance" refers to the ChangeMan ZMF D or DP instance that manages the packages and components that are installed by the P instance that we are building.

Sharing Libraries and Data Stores

If a P instance resides the same LPAR as the development instance or on a different LPAR with shared DASD, the development instance and the P instance may share some files.

This table shows which files can be shared and which cannot.

Note

The file sharing described in this table also applies to sharing between development instances.

Started Procedure DDname DSN Last Node ChangeMan ZMF File Type Share Notes
STEPLIB
ISPLLIB
ISPMLIB
ISPPLIB
ISPSLIB
ISPTLIB		 LOAD
LOAD
MESSAGES
PANELS
SKELS
TABLES		 ZMF delivered CMNZMF libraries
ZMF delivered SERCOMC libraries		 PDS Yes
STEPLIB
ISPLLIB
ISPMLIB
ISPPLIB
ISPSLIB
ISPTLIB		 LOAD
LOAD
MESSAGES
PANELS
SKELS
TABLES		 ZMF custom CMNZMF libraries
ZMF custom SERCOMC libraries		 PDS Yes Note 1
CMNPMAST CMNPMAST Package Master VSAM No
CMNCMPNT CMNCMPNT Component Master VSAM No Note 2
CMNCMPNL CMNCMPNL Long Name Component Master VSAM No Note 2
CMNRECV CMNRECV Recovery File VSAM No
CMNIMPCT IADSP Impact Analysis LDS No Note 2
CMNIALOG IALOG Impact Analysis Log (fwd. rec.) QSAM No Note 2
CMNLOG CMNLOG Activity Log VSAM No
CMNDELAY CMNDELAY Delay File VSAM No

CMNSVSM
CMNSVOM
CMNSVDM		 Staging Versions:
Site Master
Object Master
Delta Master		 VSAM No Note 2
HPSPLIB Library containing staging version parameter member PDS Note 2
Library containing SERNET keyword option member PDS Yes Note 3
SER#PARM TCPIPORT TCP/IP address/port number library PDS Yes Note 5
SERLIC SER10TY license library PDS Yes
XMLSPACE XMLSPACE XML Services data LDS LDS Yes Note 4
MAPDATA XML Services data QSAM Yes Note 4

Note 1: Custom libraries can be shared, but the customization must be designed for control by ZMF subsystem ID.

Note 2: This DDname/file is not used with P instances. The CMNIMPCT and CMNIALOG DD names are not used if using Db2 to host the I/A table.

Note 3: The DDname for this library is set with the DDNAME= execution parameter for PGM=SERVER in the started procedure.

Note 4: The content of this file must be aligned with the same version of the delivered LOAD libraries.

Note 5: The SER#PARM dataset may either be coded in the started task JCL or it may be manually updated and omitted from the started task JCL.

Installing P Instance Components

To build P instance components, execute the steps Installing ChangeMan ZMF Components with these adjustments.

  1. Review ChangeMan ZMF Libraries and Step 1: Allocate CUSTOM Libraries, then copy your delivered and custom libraries from the site of the development instance to the P site instance if one of the following is true:

    • The data set naming conventions on the P instance site are different from the naming conventions on the development site.

    • The ZMF delivered and custom libraries running the development instance are not accessible from the P instance site.

    • You want a unique set of delivered and custom libraries for each ZMF instance, as you will if you use a phased migration when you upgrade the ChangeMan ZMF software.

  2. Execute Step 2: APF Authorize Delivered and CUSTOM Load Libraries on the P instance site if one of the following is true.

    • You created a new set of ZMF delivered and custom libraries for the P instance.

    • The P instance is on a different LPAR.

    ZMF delivered and custom load libraries must be APF authorized on any LPAR where ZMF runs.

  3. Execute Step 3: Apply ChangeMan ZMF License to create licenses on the P instance site if one of these is true:

    • You use a PDS(E) to store ZMF licenses and the license library used by the development instance is not available on the P site.

    • You use CSA to store licenses and the P instance is the first ZMF instance in that LPAR.

    Note

    ChangeMan ZMF is generally licensed by LPAR. If the new P instance is the first ZMF instance on an LPAR, you may need to contact your ChangeMan ZMF account representative to obtain an additional ZMF license.

  4. Execute Step 4: Define ChangeMan ZMF VSAM Files on the P instance site with these changes.

    1. In job INITIAL1:

      • Delete job step LONGDMY.

      • In job step IDCAMS, delete DD statements:

        CMNIALOG
LONGDMY

      • In job step IDCAMS, for a P instance, these files are not deleted, only updated.

        CMNCMPNT - Component master VSAM KSDS
CMNCMPNL - Long name component master VSAM KSDS 
IADSP - Impact analysis LDS

      • Adjust VSAM space allocations as follows:

      VSAM File Unit Pri Sec
      CMNPMAST (Package Master) CYL 20 5
      CMNLOG (Log File) CYL 10 5
      CMNDELAY (Delay File) CYL 1 1
      CMNRECV (Recovery File) CYL 10 5

      Caution

      Before you submit job INITIAL1, ensure that you are using data set names that will be unique to the new P instance. Make sure that job INITIAL1 will not delete any existing data sets.

    2. In job INITIAL2:

      • Delete these job steps:

        CMPNT - Clears and initializes the component master VSAM KSDS CMPNL - Clears and initializes the long name component master VSAM KSDS

      • In job step INITPM, change the environment type in the program execution parameter for CMNINTPM to ENVTYP=P.

      • Delete job step CMNIAIN0 - Clears and initializes the impact analysis LDS

      Caution

      Before you submit job INITIAL2, ensure that you are using data set names that will be unique to the new P instance. Make sure that job INITIAL2 will not delete any existing data sets.

  5. Execute Step 5: Define XMLSPACE VSAM LDS on the P instance site.

  6. Skip Step 6: Define Staging Versions VSAM Files.

  7. Skip Step 7: Store SVPARM Control Member.

  8. If there is no SER#PARM library that is accessible from the P instance site, execute Step 8: Allocate the SER#PARM TCP/IP Address Library on the P instance site. If a SER#PARM library is accessible from the P instance, use that library for the new P instance.

  9. Verify that there is a CMNKEYS members in the TABLES library that you plan to use for the new P instance. See Step 9: Create ISPF Keylist for EXPAND.

  10. Skip Step 10: Build SERNET JCL for ChangeMan ZMF and follow these steps instead to create a started procedure for the new P instance.

    1. Copy the started procedure for the development instance to a new PDS(E) member for the P instance procedure.

    2. Delete these DD statements:

      //CMNCMPNT
//CMNCMPNL
//*CMNCMPNT
//*CMNCMALT
//*CMNCMPNL
//*CMNCLALT
//CMNIMPCT
//CMNIALOG
//HPSPLIB
//HPSIN

    3. Code these DD statements with your delivered and custom ZMF library names for the P instance:

      //STEPLIB
//ISPPLIB
//ISPMLIB
//ISPSLIB
//ISPLLIB
//ISPTLIB

    4. Change the data set name in the //XMLSPACE DD statement to match the LDS data set name you created in step 5 above.

    5. Change the data set name at the //SYSMDUMP DD statement to be unique for this started procedure. Create a GDG index for the new data set name.

    6. Change the data set names in these DD statements to match the data set names you created in step #4 above.

      DDname Last Node of File Name
      //CMNPMAST CMNPMAST
      //CMNLOG CMNLOG,
      //CMNRECV CMNRECV,
      //CMNDELAY CMNDELAY,

    7. If you use execution parameter DDNAME= for program SERVER in your started procedure, make sure that the library at the specified DD name is available at the P instance site. Copy the member containing SERNET keyword parameters for the ZMF development instance to a new member for the P instance.

    8. Update the SERNET keyword parameters with the subsystem ID and port number of the P instance.

      SUBSYS=a
CMN=nnnn

      See Passing Parameters to SERNET and Appendix D, Sernet Keyword Options for more information.

    9. Install the new SERNET started procedure in a system PROCLIB that is available at the P instance site.

    See ChangeMan ZMF P Instance for an example of a finished procedure.

  11. Skip Step 11: Build Default File Tailoring Procedure, and follow these steps instead to build a default file tailoring procedure for the new P instance.

    1. Copy the default file tailoring procedures for the ZMF development instance to a new member for the P instance.

    2. Change the library names in the concatenation at the SYSEXEC DD statement to match the delivered and custom libraries available at the P instance site.

    3. Change all other file and library names to match those in the started procedure for the new P instance.

    4. Install the file tailoring started procedure in a system PROCLIB that is available at the P instance site.

    Note

    The only skeleton file tailoring that is performed at a P instance builds JCL for REXX reporting batch jobs. You only need a default file tailoring procedure for a P instance.

  12. Skip Step 14: Build the Logon CLIST, and follow these steps instead to build a logon CLIST for the new P instance.

    1. Copy the logon CLIST for the development instance to a new member for the P instance.

    2. Change parameter SS(n) to the subsystem ID for the new P instance.

    3. Change all file and library names to match those in the started procedure for the new P instance.

    4. Copy the connect CLIST into a system CLIST library that is available at the P instance site.

  13. If the data set naming conventions on the P instance site are different from the naming conventions on the development site, execute Step 15: Modify Exit Program CMNEXINS on the P instance site.

  14. Execute Step 16: APF Authorize Other Load Libraries on the P instance site.

Configuring P Instance Security

To configure security for a P instance, execute the steps in Configuring Security with these adjustments.

  1. Skip Step 1: Customize SERLCSEC, but ensure that the ZMF custom LOAD library that will run the new P instance contains security interface program SERLCSEC. You do not need a unique version of SERLCSEC for the P instances that work with a particular development instance.

  2. If the new ZMF P instance will run under a different instance of your security system than the ZMF development instance, execute the following:

    1. Step 2: Add ChangeMan ZMF to Your Security System
    2. Step 3: Define Security Entities
    3. Step 4: Define Data Set Access
    4. Step 5: Add OMVS Segment To Use TCP/IP

Starting, Connecting, and Stopping

Review the Starting, Connecting, and Stopping chapter.

SERPRINT Message Example for P Instance

The date/time stamp at the left of each line is not shown.

SER0800I SerNet - Initialization in progress: CSA=00007000
SER0801I Execution parameters specified:
SER0801I DDNAME=ZMFOPTS
SER0801I < DDNAME: ZMFOPTS
SER0801I SUBSYS=7
SER0801I CMN=6384
SER0801I XCH=6383
SER0801I ASID=(16,60)
SER0801I SDNOTIFY=M240
SER0801I STAX=NO
SER0801I CHUNK=255
SER0801I RLLINIT=16382
SER0801I RLLTHRSH=2048
SER0801I RLLCOUNT=8192
SER0801I >
SER0804W Obsolete parameter ignored: CHUNK
SER0611I Storage protection is being used
SER0606I SEREX006 Activated
SER0604I The prefix for the dynamic allocation of log datasets is CMNSUP.INTL.MSG
LIC0010I Machine Seq: D5907 Type: 2465 Model: G99 Capacity: 558 MSU
LIC0011I LPAR ID: 18 Name: S004 Capacity: 190 MSU
LIC0012I Licensing version: 4.3 Date/Time: 2016/11/21 00:44:11 Key: 7061ae2a
LIC0045I ChangeMan ZDD licensed to SERENA SOFTWARE
LIC0010I Machine Seq: D5907 Type: 2965 Model: G03 Capacity: 58 MSU
LIC0011I LPAR ID: 18 Name: S004 Capacity: 190 MSU
LIC0012I Licensing version: 4.3 Date/Time: 2016/11/21 00:44:11 Key: 7061ae2a
LIC0045I ChangeMan ZMF licensed to SERENA SOFTWARE
SER1018I The following TCP/IP procedures are active: TCPIP
SER0660I Unix services are available
SER0821I ZDD (ChangeMan ZDD) licensed
SER0821I ECL (ChangeMan Eclipse) licensed
SER1004I XCH TCP/IP v6 socket acquired
SER1000I XCH TCP/IP environment active at 151.155.151.106..6383
SER1001I XCH TCP/IP local host name: S004
SER0835I TCB Manager active
SER0832I Address Space Manager active
SER0833I XML Data Space Manager active
SER0821I ZMF (ChangeMan ZMF) licensed
SER1004I CMN TCP/IP v6 socket acquired
SER1000I CMN TCP/IP environment active at 151.155.151.106..6384
SER1001I CMN TCP/IP local host name: S004
CMN7308I CMNSTART ZMF version: 8.1.2
CMN7350I CMNSTART *** Warning *** Missing DD Name = SYSEXEC
CMN7300I CMNSTART Initialization in progress; @TCA=15B86000
SER6414I SERXMLDB Header: SERNET XML Dsect Cross Reference. Created: 2 Sep 2016 08:41:14. Version: 813
SER7301I CMNSTART Loading CMN services; @ADR=00008000
CMN7340I CMNSTART Loading active exits:
CMN7340I CMNSTART CMNEXINS loaded
CMN7340I CMNSTART CMNEX001 loaded
...
CMN7340I CMNSTART CMNEX201 loaded
LIC0010I Machine Seq: D5907 Type: 2965 Model: G03 Capacity: 58 MSU
LIC0011I LPAR ID: 18 Name: S001 Capacity: 19 MSU
LIC0012I Licensing version: 4.3 Date/Time: 2016/11/28 02:32:08 Key: fbcdccdd
LIC0045I ChangeMan ZMF licensed to SERENA SOFTWARE
LIC0050I DB2 option licensed.
LIC0050I IMS option licensed.
LIC0050I Info Man option licensed.
LIC0050I Load Balance option licensed.
LIC0050I M+R option licensed.
LIC0050I Online Forms option licensed.
LIC0050I ERO option licensed.
CMN7800I CMNSTART Opened VSAM file CMNSUP.INTL.CMN7.CMNPMAST
CMN7800I CMNSTART Opened VSAM file CMNSUP.INTL.CMN7.CMNLOG
CMN7800I CMNSTART Opened VSAM file CMNSUP.INTL.CMN7.CMNRECV
CMN7300I CMNSTART Attach: U=CMNSTART,F1=ATTACH,F2=INFO,@TCA=1AA1F000,@TCB=8BFE88
CMN7385I CMNINFSB Attempting INFO Task Connect CMNINFSB (MVS-8.1.3) 20160729 03.01
CMN7387I CMNINFSB Soap member is undefined. 0008
CMN7399I CMNINFSB INFO Connection disabled
SER0810I SerNet server "7" initialized and ready for communications
SER0824I Attempting to load PAN#1 to determine if feature present; Please ignore any associated CSV003I message.
SER0826I PAN#1 not found
SER0824I Attempting to load LIBR to determine if feature present; Please ignore any associated CSV003I message.
SER0826I LIBR not found
SER0700I CPU ID: 00000D5907, Company: SERENA SOFTWARE
SER0704I Machine type: 2965, Model: G99, LPAR: S004 / 24
SER0701I Product: 210, Name: ChangeMan ZMF (Unlimited)
SER0701I Product: 213, Name: Client Pack Usrs=0000005
SER0702I Capacity MSU: 50-59, Hours: 1
SER0705I LPAR Capacity MSU: 190-199, Hours: 1
SER0703I Report time: 2016/11/28 02:32, Hours: 1, Key: 5B4198D6
CMN7300I CMNSTART Attach: U=CMNSTART,F1=ATTACH,F2=SERVDLAY,@TCA=1AA2A000,@TCB=8BFCF0
CMN7497I CMNSTART No active HLL exits are defined, the HLLX address space will not be started.
CMN7460I CMNDELAY - START of processing
CMN7468I CMNDELAY - Waiting for resource => qname:rname
CMN7468I CMNDELAY - CHGMAN:CMNSUP.INTL.CMN7.CMNDELAY
CMN7469I CMNDELAY - Resource obtained successfully.
CMN7800I SERS      Opened VSAM file CMNSUP.INTL.CMN7.CMNDELAY                   Exclusive
CMN7800I SERS      Closed VSAM file CMNSUP.INTL.CMN7.CMNDELAY
CMN7461I CMNDELAY - END of processing                        00000

Modifying P Instance Skeletons

The only skeleton file tailoring that is initiated by a P instance is for building REXX reporting batch jobs. Therefore, the only skeleton that must be customized for a P instance is:

  • CMN$$DSN

Ensure that the ZMF custom SKELS library that will run the new P instance contains CMN$$DSN. Check the custom skeleton to make sure it will create the JCL you want for the P instance.

Note

Most customers can use D and DP instance skeletons on a P instance by using the value of variable \&SUBSYS to select instance-specific library names and data set names.

Installing Other P Instance Facilities

Review the Installing Other Facilities chapter.

  1. Skip Installing XMLSERV. XMLSERV is a XML Services prototypingL tool that is inappropriate for a P instance.

  2. If you intend to have ChangeMan ZMF execute CICS NEWCOPY for programs that are installed by the new P instance:

    1. Review topic "CMNCICS1 - CICS NEWCOPY" in the ChangeMan ZMF Customization Guide.

    2. Execute the steps in Installing CICS NEWCOPY Support of this book to enable the ChangeMan ZMF CICS NEWCOPY facility in the CICS region that uses the production libraries managed by the new P instance.

Setting Up P Instance Housekeeping

Review the Setting Up Housekeeping chapter, especially the Introduction section. Build the batch housekeeping jobs for the new P instance that you require.

Housekeeping jobs for these files are not required because P instances do not use these files:

  • CMNCMPNT -Component Master

  • CMNCMPNL - Long Name Component Master

  • IADSP - Impact Analysis

  • CMNIALOG - Impact Analysis Log

  • CMNSVSM - Staging Versions

  • CMNSVOM - Staging Versions

  • CMNSVDM - Staging Versions