How can I tell what version of OZI was used to generate the JCL created by the Installation System?

Version 2
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    Common Install - z/OS



    QUESTION:

    How can I find out what version of the Installation System was used to generate the JCL in my Project's JCL Data Set?


    ANSWER:

    Background:
    The BMC Installation System is often referred to as the OZI Installation System.  There are numerous references to the term “OZI” in the Installation System documentation and JCL. The OZI name was derived from an earlier version of the Installation System called the OS/390 and z/OS Installer.
     
    The BMC Installation System creates an OZI Control member in the output JCL library whenever it generates the $ JCL members during Product Installation and Customization.  This member contains information about the installation jobs generated into the Project JCL Data Set, such as Project details and dataset qualifiers.
     
    The OZI Control member also contains version and timestamp information regarding the generated JCL.  In fact, the OZI Control member name is itself generated from a timestamp.  As shown in the following example, the member name is constructed from the prefix OZI, followed by the Julian day, plus the hour, in the format OZIjjjhh (with jjj being 001 to 366, hh being 0 to 23):
     
    BROWSE    IAURXM.RM3700T5.JCL(OZI2893) - 01.00     Line 0000000000 Col 001 080
      Command ===>                                                  Scroll ===> CSR
    ********************************* Top of Data **********************************
    NAMING CONVENTION FOR OZICNTL -
    OZI2893 = OZI PLUS JULIAN DAY FROM 18/10/16 AND THE HOUR FROM 03:24
    ---------------------------------------------------
    2018/10/16                                        DATE OF INSTALL
    ---------------------------------------------------
    3.7.00                                            INSTALL VERSION USED
    EMA1PLEX                                          SYSPLEX NAME
    EMA1                                              LPAR NAME
     
    If additional JCL is generated, or existing JCL is regenerated later, another OZI Control member will be added to the JCL dataset. This creates a history of when JCL generation occurred. However, if JCL is generated in the same hour on the same Julian day (regardless of year) then the existing OZIjjjnn control member will be replaced.  For example, if the Installation JCL is generated in the same hour as the Customization JCL, then there will be only one OZI Control member. Note that the information in the OZIjjjnn control member generated by the Installation step (for the $1 jobs) is a subset of the information generated by the Customization step ($2 to $9 jobs). That is because not all information is available at the time the Installation step generates the $1 JCL members.
     
    By matching the timestamp of the OZI Control member with the $ installation jobs it is possible to determine which OZIjjjhh member contains the control information that was saved at the time the $ jobs were generated.  Below is an example showing that the timestamp for the $1 jobs matches the OZI2894 control member, and the timestamp for the $7 jobs matches the OZI2895 member:
     
        Name     Prompt          Size    Created           Changed            ID
     [OZI2894 generated members]
     . $103DWNL                   173   2018/10/16   2018/10/16 04:58:02    IAURXM
     . $104DCMP                   157   2018/10/16   2018/10/16 04:58:02    IAURXM
     . $105SMPE                  1052   2018/10/16   2018/10/16 04:58:03    IAURXM
     . $106SMPE                  1089   2018/10/16   2018/10/16 04:58:05    IAURXM
     [OZI2895 generated members]
     . $700DB2                    120   2018/10/16   2018/10/16 05:01:06    IAURXM
     . $729DOP1                   143   2018/10/16   2018/10/16 05:01:07    IAURXM
     . $730DOP2                   106   2018/10/16   2018/10/16 05:01:08    IAURXM
     . $735BNDI                   109   2018/10/16   2018/10/16 05:01:08    IAURXM
     . $740INST                   358   2018/10/16   2018/10/16 05:01:11    IAURXM
     . $741FPE                    206   2018/10/16   2018/10/16 05:01:24    IAURXM
     [OZI Control members]
     . OZI2572                    129   2018/09/14   2018/09/14 02:41:22    IAURXM
     . OZI2893                     63   2018/10/16   2018/10/16 03:24:17    IAURXM
     . OZI2894                     68   2018/10/16   2018/10/16 04:58:02    IAURXM
     . OZI2895                    134   2018/10/16   2018/10/16 05:01:54    IAURXM
       ...
     
    Note that the time may not exactly match due the sequential generation of the members by the Installation System. Once the OZIjjjhh member has been identified, look for the string INSTALL VERSION USED to identify the Installation System version.
     
    BROWSE    IAURXM.RM3700T5.JCL(OZI2895) - 01.00     Line 0000000000 Col 001 080
      Command ===>                                                  Scroll ===> CSR
    ********************************* Top of Data **********************************
    NAMING CONVENTION FOR OZICNTL -
    OZI2895 = OZI PLUS JULIAN DAY FROM 18/10/16 AND THE HOUR FROM 05:01
    ---------------------------------------------------
    2018/10/16                                        DATE OF INSTALL
    ---------------------------------------------------
    3.7.00                                            INSTALL VERSION USED
    EMA1PLEX                                          SYSPLEX NAME
    EMA1                                              LPAR NAME

     


    Article Number:

    000159800


    Article Type:

    FAQ/Procedural



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles