Connect to ChangeMan ZMF

This chapter tells you how to prepare an existing ChangeMan ZMF server for access through a separate ChangeMan ZDD server.

Skip this chapter if you do not license ChangeMan ZMF, or if you will not use ChangeMan ZDD to access ChangeMan ZMF.

Introduction

In the diagram on Dedicated ZDD Server, ChangeMan ZDD clients connect to ChangeMan ZMF 2 and ZMF 3 through dedicated ZDD server Sernet A.

This chapter tells you how to prepare ZMF instances like ZMF 2 and ZMF 3 in the diagram on Dedicated ZDD Server for access through ZDD.

If you want to build a Sernet started task that is dedicated as a ChangeMan ZDD server, see Build Dedicated Sernet Started Task.

If you want to configure an existing ChangeMan ZMF server to act as a ChangeMan ZDD server, see Add ChangeMan ZDD to ChangeMan ZMF.

Step 1: Verify ChangeMan ZMF Compatibility

As you connect to ChangeMan ZMF, see the release level on the pop-up panel that is displayed before the Primary Option Menu appears.

------------------------------------------------------------------------------
                        ISPF Command Shell
Enter TSO or Workstation commands below:
        +-----------------------------------------------------------------+
===> s  |                                                                 |
        |                   ChangeMan(R)                                  |
        |                  Version = 7.1.1                                |
        |                                                                 |
Place   |               Initialization in progress                        |
        |                                                                 |
=> ser  |       Copyright (C) 1985-2010 Serena Software, Inc.             |
=> ser  |           Licensed material. All rights reserved.               |
=> SER  | ChangeMan is a registered trademark of SERENA (R) Software Inc. |
=> ser  |                                                                 |
=> RAC  |                                                                 |
=> isr +-----------------------------------------------------------------+

...

=> isrddn
=>
=>
=>

See the "Compatibility" section of the ChangeMan ZDD Readme to verify that your ZMF release level is compatible with the ZDD client you want to use to access it.

Upgrade ChangeMan ZMF or ChangeMan ZDD if necessary.

Step 2: Apply ChangeMan ZDD License

Ensure that the license that enables ChangeMan ZDD on the ZDD server is available to this ZMF server, either through CSA or through a license PDS or PDSE at a SERLIC DD statement.

If you need to apply the license with SER10TY License Manager, apply the ZDD license using the SER10TY JCL that you used to apply other licenses to this ZMF server. If you cannot find that JCL, SER10TY components are included in the SERCOMC libraries running your ZMF server.

Step 3: Enable ZDD Application

Add Sernet application keyword option XCH to the started task to enable ChangeMan ZDD on this Sernet instance.

Code the option in one of these locations:

The PARM= parameter for program SERVER in the Sernet started procedure.
The data set coded at the ddname that is specified in the DDNAME=ddname keyword option in the PARM= parameter.

A port number is optional because ZDD clients will not access this Sernet instance directly. The following format is acceptable.

XCH

Step 4: Provide Port Number for ZMF

To access a ChangeMan ZMF instance from a ChangeMan ZDD server, the CMN application keyword option must include a port number.

Locate the CMN application parameter in the Sernet started task. This parameter will be coded in either:
- The PARM= parameter for program SERVER in the Sernet started procedure.
- The data set coded at the ddname that is specified in the DDNAME=ddname keyword option in the PARM= parameter.
Ensure that the CMN keyword option includes a non-zero port number. Example:
```
`CMN=60`
```

Note

Do not use the same port number for the CMN=port keyword option and the XCH=port keyword option.

Step 5: Allocate ZDDOPTS XML Parameters

You can use XML pages in a library at ddname ZDDOPTS in the ChangeMan ZMF started procedure to alter the behavior of the ChangeMan ZDD client when it accesses functions in ChangeMan ZMF 5.3.6 and higher.

See ZDDOPTS: ChangeMan ZDD XML Options for a description of the XML parameter members and for instructions for coding the XML to meet your requirements.

Execute these steps to add a ZDDOPTS library to an existing ChangeMan ZMF server

Allocate a PDS(E) for the ZDDOPTS XML page members with these characteristics:

DSN=node.SERCOMC.ZDDOPTS                * Recommended last node 
DCB=(RECFM=VB,LRECL=255,BLKSIZE=0)      * Let SMS set BLKSIZE 
SPACE=(CYL,(1,10,30))

Add a ZDDOPTS DD statement to the ChangeMan ZMF started procedure and code it with the data set name of the allocated ZDDOPTS library.
Copy these members to the ZDDOPTS library from the SERCOMC SAMPXML library unloaded from the download image or the distribution CD:
- AUDIT
- BUILD
- COMMAND
- DEMOTE
- LIBTYPE
- PKGCREAT
- PKGPROP
- PROMOTE
Use a PDS search like the ISPF Search-For Utility to find this XML comment syntax in any ZDDOPTS library member:
```
`<!--`
```

If no XML comments are found, see Translating Comments in ZDDOPTS Members for a procedure to fix XML comments in ZDDOPTS library members.

Step 6: Configure Your Security System

You may need to change some security settings in your ChangeMan ZMF instance to access it from a ChangeMan ZDD client.

Set Security Interface to SAF

A ChangeMan ZMF instance must use SAF for its security interface if you want to access it from a ChangeMan ZDD client. See SAF and Your Security System.

Execute these steps to ensure that the ChangeMan ZMF server you want to access from a ZDD server is using the SAF security interfacez:

Logon to ChangeMan ZMF with Global Administrator authority.
Go to the Global Parameters - Part 1 of 6 panel (=A.G.1) and examine the setting of the Security System field.
If the Security System field is set to RACF, ACF2, or TSS, change it to SAF, and then save your change by pressing ENTER until you are returned to the menu where you started.
If you have not customized local security routine SERLCSEC, no further action is required. Go to Define OMVS Segments For TCP/IP.
Edit local security routine SERLCSEC in your custom ASMSRC library, and search the source code for &SAF.
If &SAF is not found, Sernet is running Version 7.1.1 or later, and no further action is required. Go to Define OMVS Segments For TCP/IP.

Compare the switch settings in your customized SERCSEC source to the settings shown in this code fragment.

*--------------------------------------------------------------------
* BELOW IS WHERE THE USER CAN TAILOR THE SOURCE CODE FOR THE SHOP
*--------------------------------------------------------------------
&SAF         SETB 1     (YES)   security package - SAF
&ACF2        SETB 0     (NO)    security package - ACF2
&RACF        SETB 0     (NO)    security package - RACF
&RACFVRM     SETB 1     (1.9)   .RACF 1.9 or better (0=1.8)
&TSS         SETB 0     (NO)    security package - Top Secret
&TSSVRM      SETB 0     (4.1)   .version 4.2 or better (0=4.1)
&VERFYID     SETB 1     (YES)   SAF user ID verification

If your switch settings match the settings in the code fragment above, no changes are required. Go to Define OMVS Segments For TCP/IP.
Change the switch settings in your customized SERLCSEC source to match the code fragment above.
Assemble and link the customized SERLCSEC program source into your custom LOAD library.
Stop and start your ChangeMan ZMF instance.

Define OMVS Segments For TCP/IP

Most user IDs requiring access to TCP/IP functions must have an OMVS segment. To satisfy this requirement for the ChangeMan ZMF server, do one of the following:

Define an OMVS RACF segment for the userid assigned to the ZMF server.
Use the default OMVS segment support provided by RACF and z/OS UNIX for users and groups.

See "Requirement for an OMVS segment" in the z/OS Communications Server IP Configuration Guide.