Step 1: Running the customization script

Edit online

Run the customization script to allocate the product libraries and VSAM files and to perform basic editing tasks. This customization step is required.

Procedure

  1. From the ISPF command shell (ISPF Option 6), run the GTOINST EXEC that is in the SGTOEXEC target library by specifying the following statement: 
    EXEC 'target_HLQ.SGTOEXEC(GTOINST)' 'runtime_HLQ target_HLQ'

    where target_HLQ is the high-level qualifier that you specified at installation for the SMP/E target libraries and runtime_HLQ is the high-level qualifier that you want to use for the run-time libraries. For example, you could use userid.GTO as the runtime_HLQ.

    While the script is running, informational messages regarding the progress of the customization process are displayed.

    When the script finishes, the default names of the product run-time data sets are listed.
  2. At the prompt Are these names OK?, indicate whether you want to accept the default names of the product run-time data sets, as follows:
    • Type Y (for Yes) if you want to accept the default names (recommended).
    • Type N (for No) if you want to specify other names. Tape Optimizer will prompt you to edit the customization script.
  3. If Tape Optimizer prompts you to edit the customization script (because you specified N in step 2), perform these substeps:
    1. Exit customization.
    2. Edit the following portion of the customization script. In the left column, replace the default names for the product run-time libraries and files with the names that you want to use.
      Ensure that your values are enclosed in double quotation marks.
      Tip: To perform this task, you should be familiar with the REXX programming language.
      /* >>>>>>>>>>>>>>>>>>>>  note <<<<<<<<<<<<<<<<<<<<<<<<< */ 
/* If you want to change the default names of the       */ 
/* run-time data sets, then specify the names here.     */ 
/* >>>>>>>>>>>>>>>>>>>>  note <<<<<<<<<<<<<<<<<<<<<<<<< */ 
/* set run-time dataset constants                       */ 
loadnam = "LOAD"           /* Executables     */
isppnam = "ISPPLIB"        /* Panels          */ 
ispmnam = "ISPMLIB"        /* Messages        */ 
ispsnam = "ISPSLIB"        /* JCL Skeletons   */ 
joblnam = "JOBLIB"         /* Copy JOB JCL    */ 
cntlnam = "CNTL"           /* Sample Jobs     */ 
execnam = "EXEC"           /* Rexx EXECS      */ 
fildnam = "FILEDEFS"       /* File Definition */
rmmvnam = "RMMVARS"        /* RMM MetaData    */
    3. Save your changes.
      Your new names will be used as the last qualifier of the run-time data set names.
    4. Restart the customization script.
  4. At the prompt OK to delete product files?, indicate whether you want the customization script to delete files from a previous installation of the product (for example, files for a previous product version), as follows:
    • Type Y (for Yes) if you want the customization script to delete the files from a previous product installation and then continue.
    • Type N (for No) if you want the customization script to terminate so that you can back up or rename the files from a previous product installation. After you back up or rename the files, you will need to restart the customization script.
  5. At the prompt Do you want to allocate the product VSAM files from the script (Y) or from batch (N)?, indicate how you want the VSAM files that the product uses to be allocated:
    • Type Y to have the customization script automatically allocate the VSAM files by using the system defaults. (recommended)
    • Type N to prevent the VSAM files from being automatically allocated and to end the customization script. You will need to manually allocate the VSAM files by running the JCL in the GTOVSAM member of the runtime_HLQ.CNTL library. (For more information, see Manually allocating the product’s VSAM files.) You might want to choose this option if you need to allocate the files by means of a batch job or customize how the files are allocated in some way.