Space announcement This documentation space provides the same content as before, but the organization of the content has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

Upgrading

This topic provides detailed tasks that you need to perform to upgrade from earlier versions of ECC.


Important

Role involved: z/OS Systems Programmer

Earlier releases of ECCwhich comprises of a suite of products, must migrate some artifacts to be compatible with ECC 17.02. Use the following table to determine which tasks need to be completed based on the release of ECC from which you are upgrading.

Determine which instructions to follow to upgrade to 17.02 and proceed accordingly:

ECC Release

Instructions to follow

Comments

pre-16.05

Use conversion utility to create PARMLIB members. Refresh of product libraries required.

16.05

Refresh of product libraries required.

Task 1: Upgrading from versions earlier than 16.05 to 17.02

This task assists you in upgrading your existing pre-release 16.05 ECC software to the current release of ECC.

LMS changes

  1. Starting with ECC release 16.05, LMS runs in the CMSC address space. The initialization jobs no longer run independently.
  2. ECC requires the use of BMC PARMLIB. You should copy your pre-16.05 LMS parameters from member LMINPARM in library SLMSCNTL to member LMCL00 in the BMC PARMLIB data set.
  3. You must delete the pre-16.05 LMS subsystem before you start the CMSC for the current LMS release. To delete the earlier LMS subsystem, specify FUNCTION(DELETE) in the LMS client PARMLIB member. This must be accomplished using the job LMSINIT from your pre-16.05 LMS library using the specified SYSIN PARMLIB, possibly located in member LMINPARM from library SLMSCNTL.

  4. For testing ECC 17.02, after upgrading from LMS 4.0, you can override the installation of LMS 4.0 by changing the DEFAULT parameter in ECC 17.02 from DEFAULT=YES to DEFAULT=FORCE. You will also need to change the LMS subsystem name, checkpoint data set, and exit PROC. If during testing of ECC 17.02 you encounter any issues, stop ECC 17.02 and reissue the UPDATE for LMS 4.0. 

    Important

    Any products that were checked out or running when the earlier LMS’s subsystem was deleted should be shutdown and restarted. Also, any products that are started between the time the earlier LMS’s subsystem was deleted and LMS is started in the CMSC will fail with a license error.

  5. Add the LICENSE_DSNAME parameter to the newly created LMCL00 PARMLIB member. Set the value for the parameter to the name of the current license file. This parameter setting will avoid an enqueue reserve on the license file when attempting to update a license.

 HCI changes

  1. If you are upgrading from HCI 3.0 to ECC 17.02, BMC provides a migration utility that converts HCI 3.0 XML parameters and their associated CSS TP configuration parameters into a PARMLIB member for use with ECC 17.02.
    Modify the sample JCL member HCIJMGRT, located in the SLCXCNTL library, to execute the migration utility. The utility writes its output into the specified PARMLIB member, for example HCI00, replacing any data in the member. The output includes the parameters and their values.
    1. Update the JCL:
      1. Add a job card.
      2. On the HCIXML DD statement, specify the HCI 3.0 member that contains the HCI XML parameters to be converted.
      3. On the TPCONFIG DD statement, specify the CSS 9.0 library that contains the TP configuration members.
      4. On the HCIPARM DD statement, specify the pre-allocated PARMLIB data set and the member to which we will write the converted data.
      5. On the SYSTSIN DD statement, specify the library member HCIRMGRT in the EXEC statement that contains the REXX EXEC that performs the migration.
    2.  Submit the job and review the output PARMLIB member.

    3. Make any additional changes to the new PARMLIB member according to your site’s requirements for the current release of ECC.

      Important

      If you are upgrading from an HCI release 2.1 and prior, you will have to manually update the PARMLIB member with your site’s values.

Abend-AID changes

  1. Prior to ECC 16.05, Base Services was part of Abend-AID Common Components. Base Services was removed from BMC AMI DevX Abend-AID 16.05 and became part of ECC beginning with release 16.05. If you are upgrading to ECC 17.02, but not upgrading BMC AMI DevX Abend-AID to release 16.05 or 17.02, then the following procedures must be implemented to allow your existing BMC AMI DevX Abend-AID installation to function correctly with ECC 17.02.

    You may continue to use BMC AMI DevX Abend-AID 12.4 (and below) with your prior version of CSS. However, if you want to change existing BMC AMI DevX Abend-AID servers to use the ECC 17.02 load libraries then these changes will be needed:


    1. BDCAS – in the step that executes program FDBMMPLU:
      1. Add the ECC 17.02 SLCXAUTH library as the first library on the STEPLIB DD statement.
      2. Add the ECC 17.02 SLCXLOAD library as the first library on the FDBDRPL DD statement.

      3. Remove the existing SLCXLOAD library from the FDBDRPL DD statement.

        Important

        If you have steps to execute program FDBASUBS to start or stop an BMC AMI DevX Abend-AID subsystem, update the STEPLIB DD statement to remove the BMC AMI DevX Abend-AID Common library SKAZAUTH and replace it with the ECC 17.02 SLCXAUTH library.

    2. TDCAS – in the step that executes program FDBMMPLU:
      1. Add the ECC 17.02 SLCXAUTH library as the first library on the STEPLIB DD statement.
      2. Remove the HCI library SLHCAUTH library from the STEPLIB DD statement.
      3. Add the ECC 17.02 SLCXLOAD library as the first library on the FDBDRPL DD statement.
      4. Remove the existing SLCXLOAD library from the FDBDRPL DD statement.

      5. Remove the HCI SLHCLOAD library from the FDBDRPL DD statement.

        Important

        If you have steps to execute program FDBASUBS to start or stop an BMC AMI DevX Abend-AID subsystem, update the STEPLIB DD statement to remove the BMC AMI DevX Abend-AID Common library SKAZAUTH and replace it with the ECC 17.02 SLCXAUTH library.

    3.  VIEWING SERVER – in the step that executes program FDBMMPLU:
      1. Add the ECC 17.02 SLCXAUTH library as the first library on the STEPLIB DD statement.
      2. Remove the HCI library SLHCAUTH library from the STEPLIB DD statement.
      3. Add the ECC 17.02 SLCXLOAD library as the first library on the FDBDRPL DD statement.
      4. Remove the existing SLCXLOAD library from the FDBDRPL DD statement.
      5. Remove the HCI SLHCLOAD library from the FDBDRPL DD statement.

 2. If you have steps to execute program FDBASUBS to start or stop an BMC AMI DevX Abend-AID subsystem, update the STEPLIB DD statement to remove the BMC AMI DevX Abend-AID Common library SKAZAUTH and replace it with the ECC 17.02 SLCXAUTH library.

CSS changes

  1. If you installed CSS with your ECC pre-16.05 release, copy your existing CSS Compile Information Table to the ECC 17.02 library. The Compile Information Table is member AAUTCTBL in library SLCXTABL.
  2. Review and modify started tasks (PROCs) or batch jobs to use 17.02 libraries.
    1. HCIPROC
    2. LMSEXIT
    3. CXSS0000
    4. CXSSAS
    5. Any others that may have older ECC library names.
  3. Since your ECC pre-16.05 release did not include the CMSC component, you must complete Configuring-CMSC-for-a-new-install to finish the upgrade.


Task 2: Upgrading from 16.05 to 17.02

This task will assist you to upgrade your existing ECC software, release 16.05, to the current release of ECC.

  1. Modify started tasks (PROCS) or batch jobs to use 17.02 libraries.
    1. CMSC
    2. HCIPROC (only if using the HCI)
    3. LMSEXIT
    4. CXSS0000
    5. CXSSAS
  2. Remove CWLF0000 DD statement in CMSC started task.
  3. Authorize the 17.02 SLCXAUTH library.
  4. Run the LMSPREP CLIST to update the CWLMA CLIST to use the 17.02 libraries. Copy the CWLMA CLIST to an appropriate CLIST system library, if desired.
  5. Update the LMCLxx PARMLIB member:
    1. Change DEFAULT parameter value to FORCE.
    2. Change CHKPT_DSNAME value to a new library name.
    3. Change EXIT_PROC value to the name of the new PROC.
    4. Add LICENSE_DSNAME parameter with the value of the current license file, to avoid enqueue reserve on license file when attempting to update a license.
  6. Delete the existing LMS subsystem:
    1. Update LMCLxx parameter FUNCTION to DELETE.

    2. Refresh the LMCLxx PARMLIB member in storage.

      f cmsc,parmlib

      refresh LMCLxx where cmsc is the CMSC started task name (if modified) and xx is the suffix for the PARMLIB member (default is LMCL00).

    3. Shutdown the LMS subsystem.

      f cmsc,lmshut client
  7. Add the 17.02 LMS subsystem:
    1. Update LMCLxx parameter FUNCTION to UPDATE.

    2. Refresh the LMCLxx PARMLIB member in storage.

      f cmsc,parmlib refresh LMCLxx

    3. Shutdown the LMS subsystem.

      f cmsc,shutdown immed

    4. Restart the CMSC

      s cmsc
  8. If your HCI is controlled by the CMSC, then shutdown the HCIPROC and restart the CMSC. This will prompt LMS to load your BMC licenses into storage and will start the HCIPROC. Otherwise, stop and restart your HCI started task or batch job.
  9.  Copy your existing CSS Compile Information Table (member AAUTCTBL) from the 16.05 SLCXTABL library to the 17.02 SLCXTABL library.

Important

Base Services require no customization for an upgrade other than the refresh to the current release libraries.

Task 3: Configuring CMSC

If CMSC is not installed on your system, configure it and perform the following steps for Simple Deploy Users:

  1. Copy the DDSN00 sample from hlq.SLCXCNTL(DDSN00) into the CPWR common PARMLIB data set.
  2. Uncomment the DD_INFO blocks for products that are installed or will be installed.

  3. Update the DSNAME parm in the DD_INFO block to match the actual data set names on your LPAR.

    Tip

    You can use System Symbols so that CMSC will resolve the names.

Task 4: Verifying

This task is used to verify that your LMS subsystem lists your BMC License Certificates and the HCIPROC is started.

  1. Verification of LMS subsystem
    1. Modify the sample JCL member LMLFCRPT, located in library SLCXCNTL, to list the contents of the LMS License File.
      1. Add a job card.
      2. On the IMPORT step’s STEPLIB DD statement, update the SLCXAUTH library to your installation’s fully qualified data set name.
      3. Modify ‘CPWR.LICENSE.FILE’ to the name of your LMS License File.
      4. Submit the job and review the output to verify successful completion. Also, verify that all your BMC License Certificates are listed.
  2. Verification of HCI
    1. Modify the sample JCL member HCITEST, located in library SLCXCNTL, to execute the verification job. The job will attempt to ping the HCI to validate the connection.
      1. Add a job card.
      2. On the IVP step’s STEPLIB DD statement, update the SLCXLOAD library to your installation’s fully qualified data set name.
      3. On the IVP step’s SYSIN DD for both the HOSTIP and PORT:
        1. HOSTIP – Must contain the value of the host address in which the HCI is executing. It can be the host DNS name or the host IP address.
        2. PORT – Must represent the port on which the HCI is listening.
      4. Submit the job and review the output.

      5. If a connection gets established, the output should resemble:

        BMC AMI HCI TP Connection Verification Report

        Control statement specification:
        HOSTIP=MVS1.XYZCORP.COM
        PORT=16196

        OPEN connection     RC = 00, ERRNO=00000
        SEND data           RC = 00, ERRNO=00000
        RECV data           RC = 00, ERRNO=00000
        SEND data           RC = 00, ERRNO=00000
        RECV data           RC = 00, ERRNO=00000

        Connection to the port was successfully validated.
        Valid BMC mainframe product license verified.

Task 5: Post upgrade considerations

After verification, the ECC upgrade is complete. 

If you plan to integrate with BMC AMI DevX Workbench for Eclipse, you should proceed directly to Configuring-BMC-AMI-DevX-Workbench-for-Eclipse.

If you do not want to integrate with Workbench for Eclipse, you should proceed directly to Deploying-ECC-to-another-LPAR.

 

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