Step 12. Specify external files


Important

If the selected product(s) do not require external files, then this step will be bypassed.

The screen shown in the following figure is displayed after you press Enter the last time in the previous step. Default names for external files related to the product(s) being installed are displayed and can be edited to match your site's values. Make any necessary edits.

The actual display of the following figure will only include the external files required for the products you selected in the Product installation selection—Sample screen showing all products selected figure.

Specifying external files - Example

                            BMC Installer
Command ===> __________________________________________________ Scroll ===> PAGE
Enter the following information for: External Files


Press Enter to continue or PF3 to return to previous panel.

C++ base routine lib              CEE.SCEECPP
                    File Status:  OK
ECC (HCI) load library(SLCXLOAD)  CPWR.SLCXLOAD
                    File Status:  OK
ISPF load library                 ISP.SISPLOAD
                    File Status:  OK
LE link-edit lib 2                CEE.SCEELKEX
                    File Status:  DATASET NOT FOUND
LE link-edit library              CEE.SCEELKED
                    File Status:  OK
LE run library                    CEE.SCEERUN
                    File Status:  OK
LE Side-Deck lib                  CEE.SCEELIB
                    File Status:  OK
LE Xplink lib                     CEE.XXXXBND2
                    File Status:  Verify DSName is intended file

The File Status field shows the results of checking whether the listed library exists or not. Some of the External Files are additionally checked whether they contain specific members or not. If the file does not contain the required member, status Verify DSName is intended file is displayed. This indicates that the DSName entered may not be the desired data set.

Important

The File Status not equal to 'OK' does not stop the dialog as the generated JCL could be planned for execution on a different LPAR than where it is generated and the DSName entered might be valid on that LPAR.


  1.  Update the names of the following libraries as they are defined at your installation:
    C++ base routine lib

    Specifies the Language Environment C++ base routine library (for example, CEE.SCEECPP).

    ECC (HCI) load library(SLCXLOAD)

    Specifies the ECC load library which includes BMC AMI Host Communications Interface (HCI) (for example, cpwr.SLCXLOAD).

    ISPF load library

    Specifies the ISPF load library (e.g., ISP.SISPLOAD).

    LE link-edit lib 2

    Specifies the Language Environment link-edit library 2. This library contains the LE resident routines which include those for callable services, initialization, and termination. (for example, CEE.SCEELKEX).

    LE link-edit library

    Specifies the Language Environment link-edit library. LE transient or base libraries at link- edit. If LE370 support is requested enter the LE370 link edit Library (for example, CEE.SCEELKED).

    LE run library

    Specifies the Language Environment object library. This data set is used to execute LE programs at your site. If LE370 support is requested enter the LE370 Execution time Library (for example, CEE.SCEERUN).

    LE Side-Deck lib

    Specifies the Language Environment side-deck library (for example, CEE.SCEELIB).

    LE Xplink lib

    Specifies the Language Environment Xplink LP64 library (for example, CEE.SCEEBND2).

    System USS Library

    Specifies the z/OS UNIX System Services (USS) library (for example, SYS1.CSSLIB).

    TCPIP loadlib (SEZACMTX)

    Specifies the generic socket library (for example, TCPIP.SEZACMTX).

    TCPIP loadlib (SEZARNT1)

    Specifies the reentrant C socket library (for example, TCPIP.SEZARNT1).

    TCPIP loadlib (SEZATCP)

    Specifies the TCP/IP executable load library (for example, TCPIP.SEZATCP).

  2. Check the File Status for each library. It should be OK for each library, unless you intend to execute the generated JCL on a different LPAR. In that case, verify that the libraries are valid on that LPAR.
  3. Press Enter.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*