Modifying FDT modules for multiple-system environments

Summary: In this task, you will modify the installation so that multiple systems reference the  appropriate VSAM files.

Before you begin

Before you begin this task, complete the following steps:

• Install ULTRAOPT. For more information, see the Installation System.

• Complete the Define VSAM Option File and Print File step when customizing ULTRAOPT. For more information, see Customizing-ULTRAOPT.
• Choose one of the following methods for using VSAM options and print files on multiple systems:

1. 
   
   1. Share VSAM options and print files.
   2. Use separate VSAM options and print files.

To share VSAM options and print files

1. Access the Product Customization Steps panel.

2. Select the Define VSAM Option File and Print File step. The Define VSAM Files panel (Define VSAM Files Panel) is displayed.

   MAINVIEW VTAM ------------- DEFINE VSAM FILES ------------------- CUSTOMIZATION COMMAND ===>
   The MainView for VTAM ULTRAOPT Address Space requires VSAM files.
   Do you need to create VSAM files ? ===> YES (YES or NO)
   
   
   * YES assists you in creating the files.
   * NO bypasses this step.
   
   
   In the PROCEDURE LIBRARY field enter the library name to contain the procedure.
   In the PROC MEMBER NAME enter the name for the procedure.
   
   
   PROCEDURE LIBRARY      ===> ’hilevel.UBBSAMP’
   PASSWORD               ===> (If password protected)
   PROC MEMBER NAME       ===> SOPVSAM (Enter a name for the startup procedure)
   REPLACE MEMBER?        ===> NO (If duplicate member in PROCEDURE LIBRARY)
   SMF ID ?               ===> xxxx (SMF ID of system running ULTRAOPT)
   
   
   When you press ENTER, jcl are created and you are placed
   in an edit session to make further changes, if necessary.
   
   
   Press ENTER to continue, HELP for more information, or END to exit.

3. Change the name of the startup procedure that is displayed in the PROC MEMBER NAME field. For example, SOPVSAM2.

   Note

   Copying the FDT modules in the SOPVSAM file and changing the FDT module names does not change the internal VSAM file references. Both systems use the same options and print to the same file. Changing an option in one system changes it in the other system.

4. Type NO in the REPLACE MEMBER? field.
5. In the SMF ID ? field type the SMF ID of the system where you are running ULTRAOPT. For example, SYSB.
6. Press Enter.
7. Modify the JCL as necessary and submit the job.
   The job creates FDT module SOPFSYSB, deletes existing VSAM files, and redefines VSAM options files and print files.

To share VSAM options and print files by copying an FDT module

By using the TSO copy utility, copy FDT module SOPFxxxx. Name the module SOPFxxxn. For example, copy SOPFSYSA and name it SOPFSYSB.

Illustration

Multiple-System Files Using Same VSAM Files shows an example of the VSAM files that are referenced in the SOPFxxxx modules in the hilevel.BBLINK library for a system where ULTRAOPT is installed on two CPUs.

In this example, the FDT modules, SOPFSYSA and SOPFSYSB, contain the same data set name references to VSAM options and print files. hilevel.SOPOPT is the data set name of the ULTRAOPT options file, and hilevel.SOPPRINT is the data set name of the ULTRAOPT print file.

Multiple-System Files Using Same VSAM Files

To use separate VSAM options and print files

1. Access the Product Customization Steps panel.
2. Select the Define VSAM Option File and Print File step. The Define VSAM Files panel (Define VSAM Files Panel) is displayed.
3. Change the name of the startup procedure that is displayed in the PROC MEMBER NAME field. For example, SOPVSAM2.
4. Type NO in the REPLACE MEMBER? field.
5.  In the SMF ID ? field type the SMF ID of the system where you are running ULTRAOPT. For example, SYSB.

6. Press Enter.
   JCL that is created by the AutoCustomization utility is displayed. A sample of the JCL that is created follows:

   000033 //SYSIN    DD     *
   ==CHG>       DELETE RCHRWB.MV22F.SOPOPT CLUSTER
   ==CHG>       DEFINE CLUSTER (NAME(hilevel.SOPOPT) -
   000036              VOLUMES(111111) /* <--------------- CHANGE */ -
   000037              FILE(SOPOPT) -
   000038              RECORDS(10,5) -
   000039              NUMBERED -
   000040              UNIQUE -
   000041              RECORDSIZE(4084,4084)) -
7. Modify the JCL as necessary. You must change the cluster name (for example, from hilevel.SOPOPT to hilevel.SYSB).
8. Submit the job. The job creates FDT module SOPFSYSB and new VSAM options files and print files.
9. Perform one of the following steps:

• 
  
  • If you are using permanent product authorization passwords, add a new password to the product authorization security module.
  • If you are using a bypass password for a product, you do not need to process another password. All systems that share the load library containing the security module with the bypass password can use that product.

Enabling two systems to use separate VSAM options and print files is more involved that enabling two systems to share VSAM options and print files. Multiple-System Files Using Separate VSAM Files shows an example of the VSAM files that are referenced in the SOPFxxxx modules in the hilevel.BBLINK library for a system where ULTRAOPT is installed on two CPUs.

In this example, the FDT modules, SOPFSYSA and SOPFSYSB, contain different data set name references to VSAM options and print files. hilevel.SOPOPT is the data set name of the ULTRAOPT options file, and hilevel.SOPPRINT is the data set name of the ULTRAOPT print file.

Multiple-System Files Using Separate VSAM Files