Installing BMC II for z/OS on UNIX


Use the following procedures to install the BMC II for z/OS cell and console components on a UNIX operating system.

Important

If the cell and console reside on different systems, you must complete all steps in both procedures.

To install the BMC II for z/OS cell components

  1. From a command line, enter cd $MCELL_HOME to change the working directory to MCELL_HOME, the installation directory for BMC Impact Manager.
  2. At the command prompt, use File Transfer Protocol (FTP) to retrieve the files from the z/OS host system where BMC II for z/OS is installed:
    1. When prompted, enter your z/OS user ID and password.
    2. Change the directory to the hlq.TAR directory that contains the iimpkgu.tar file.
      hlq represents your high-level qualifier.
    3. Enter binary to set the transfer mode to binary.
    4. Enter get iimpkgu iimpkgu.tar to retrieve the tar file.
    5. When finished, enter quit to end the FTP session.
  3. At the command prompt, enter tar -xf iimpkgu.tar to unpack the tar file contents.
  4. Change the directory to the iimpkg directory that was created in Step 3.
  5. At the command prompt, enter su root to change to the root user ID and, when prompted, enter the root password.
  6. Use the MCSTAT command to verify the active status of the cell:
    1. Enter mcstat -n my_cell1 -r -ttimeout.
      The variable timeout is the maximum time to wait (in milliseconds) to receive a response to the register request. The deThe default value is 60000.
      The system output can be either of the following responses:
      • Running indicates that the cell exists and its service is running. If you receive this response, continue to Step 7.
      • Could not connect to Cell indicates that the cell exists and its service is stopped. If you receive this response, continue to Step 6.b.
    2. Enter mcell -n my_cell1 to start the cell.
  7.  At the command prompt, type ./InstallKB and press Enter.
    The Configuration Utility opens.

    image2018-10-22_16-26-55.png

    Important

    If you do not want to use the Configuration Utility, switch to the ManualScript subdirectory and then issue the following command at the command prompt to update the cell:

    ./updateKB cellhome cellname.

  8. In the Configuration views frame, select Local cells.
    The Configuration Utility displays the cells located on this computer in the views frame.
  9. From the list of cells in the Local cells view, select cellname.
  10. From the Actions menu, select Cell actions > Update Knowledge base.
    The Configuration Utility displays the Get updates package dialog.
    image2018-10-22_16-30-58.png
  11. From the Choose method list, select Get package from local directory.
  12. In the Directory or file path field, type the name of the directory where the files were created when the tar file was unpacked.

    Tip

    Alternatively, you can click Browse to select the directory from the File dialog.

  13. When finished, click Continue.
    The Configuration Utility completes the following actions:
    • Backs up modified files to . fileName.old before copying or editing occurs
    • Creates an updateKB.log file that contains all update activity
    • Displays messages about the progress of the update in the Log view frame at the bottom of the window

To install the BMC II for z/OS console components

Important

If the cell and console reside on the same system, skip to Step 7. If the cell and console reside on different systems, you must complete all steps in both procedures.

  1. From a command line, enter cd $BMC_PORTAL_KIT_HOME to change the working directory to BMC_PORTAL_KIT_HOME, the installation directory for the TrueSight console server.
  2. At the command prompt, use File Transfer Protocol (FTP) to retrieve the files from the z/OS host system where BMC II for z/OS is installed:
    1. When prompted, enter your z/OS user ID and password.
    2. Change the directory to the hlq.TAR directory that contains the iimpkgu.tar file.
    3. Enter binary to set the transfer mode to binary.
    4. Enter get iimpkgu iimpkgu.tar to retrieve the tar file.
    5. When finished, enter quit to end the FTP session.
  3. At the command prompt, enter tar -xf iimpkgu.tar to unpack the tar file contents.
  4. Change the directory to the iimpkg directory that was created in Step 3.
  5. At the command prompt, enter su root to change to the root user ID and, when prompted, enter the root password.
  6. At the command prompt, type ./InstallKB and press Enter.
    The Configuration Utility opens as shown in Configuration Utility main window.

    Important

    Alternatively, you can still use the same command used for installation before the Configuration Utility. Switch to the ManualScript subdirectory then issue the following command at the command prompt to update the console:

    ./updateConsole cellhome

  7. From the Actions menu, select Console actions > Update console.
    The Configuration Utility displays the Get updates package dialog (Get updates package dialog).

    Important

    If the cell and console reside on the same system and you have already updated the Knowledge Base, the Configuration Utility uses the data that you previously entered on the Get updates package dialog. When the Update TrueSight Console dialog is displayed, skip to Step 11.

  8. From the Choose method list, select Get package from local directory .
  9. In the Directory or file path field, type the directory where the files were created during the unzip process.

    Tip

    Alternatively, you can click Browse to select the directory from the File dialog.

  10. When finished, click Continue.
    The Configuration Utility displays the Update TrueSight Console dialog.


    image2020-12-11_0-24-50.png

  11. From the Choose web update type list, select Replace jar.
  12. Click Execute.The Configuration Utility executes the following actions:
    • Backs up modified files to fileName.old before copying or editing occurs.
    • Creates an updateConsole.log file that contains all update activity.
    • Displays messages about the progress of the update in the Log view frame at the bottom of the window.

 

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