Converting to z/OS Connect (OpenAPI 2) Unlimited

You can convert your existing z/OS Connect (OpenAPI 2) server to z/OS Connect (OpenAPI 2) Unlimited.

Note: You must have z/OS Connect (OpenAPI 2) V3.0.28 or later installed to convert.

There are two methods that you can use to convert from z/OS Connect (OpenAPI 2) to z/OS Connect (OpenAPI 2) Unlimited. The preferred solution is to create a new installation with new SMP/E zones. The alternative solution is to modify an existing z/OS Connect (OpenAPI 2) installation. Creating a new installation has no impact to an existing z/OS Connect (OpenAPI 2) installation, and logically separates the two products. By using this method, you can perform a staged conversion of your servers and, if required, an easy way to revert to your existing installation.

Preferred method

The preferred method is to install z/OS Connect (OpenAPI 2) Unlimited into new SMP/E zones by following the instructions in the z/OS Connect Program Directory. You can continue to use your existing z/OS Connect (OpenAPI 2) servers (including configuration and artifacts) that are stored in /var/zosconnect as these are unaffected by the installation of z/OS Connect (OpenAPI 2) Unlimited. After you install z/OS Connect (OpenAPI 2) Unlimited, update your JCL to use the new data sets and z/OS UNIX System Services paths from the z/OS Connect (OpenAPI 2) Unlimited installation, such as started tasks for your servers and the Angel to point to the new installation.

Alternative method

If you choose to install z/OS Connect (OpenAPI 2) Unlimited into existing z/OS Connect (OpenAPI 2) SMP/E zones, you must customize your BAQURCV or BAQURCVE job to use the z/OS Connect (OpenAPI 2) Unlimited RELFILES and SMPMCS data set (as described in more detail in the following steps).

In the following procedure, hlq.zcee is used as the high-level qualifier for data sets used by the existing z/OS Connect (OpenAPI 2) installation jobs, while hlq.unlimited is used as the high level qualifier for the new z/OS Connect (OpenAPI 2) Unlimited installation jobs. Use these instructions with the z/OS Connect Program Directory.

Procedure

  1. Copy the jobs from the hlq.unlimited.IBM.JZC3003.F2 RELFILE to a work data set for editing and submission.
  2. Allocate data sets for z/OS Connect (OpenAPI 2) Unlimited.
    1. Customize the sample job BAQUALOC in hlq.unlimited.IBM.JZC3003.F2 RELFILE. Set @hlq@ for your existing z/OS Connect (OpenAPI 2) installation.
    2. Submit the sample job. A return code of 0 indicates success.
  3. Define DDDEFs for z/OS Connect (OpenAPI 2) Unlimited
    1. Customize the sample job BAQUDDEF in hlq.unlimited.IBM.JZC3003.F2 RELFILE. Set @hlqgzone@, @tname@, @hlq@, and @dname@ for your existing z/OS Connect (OpenAPI 2) installation.
    2. Submit the sample job. A return code of 0 indicates success.
  4. Receive z/OS Connect (OpenAPI 2) Unlimited into the existing z/OS Connect (OpenAPI 2) Global Zone.
    1. Customize the sample job, BAQURCV or BAQURCVE, in hlq.unlimited.IBM.JZC3003.F2 RELFILE. Set @hlqgzone@ and @smpeoptions@ for your existing z/OS Connect (OpenAPI 2) installation.
    2. IMPORTANT: You must set @downhlq@ to the hlq.unlimited RELFILES and SMPMCS data set on the SMPCNTL and SMPPTFIN statements to receive the contents of z/OS Connect (OpenAPI 2) Unlimited.
    3. Submit the sample job BAQURCV or BAQURCVE. A return code of 0 indicates success.
  5. Apply z/OS Connect (OpenAPI 2) Unlimited.
    1. Customize the sample job BAQUAPLY in hlq.unlimited.IBM.JZC3003.F2 RELFILE. Set the @hlqgzone@, @tname@, and @smpeoptions@ for your existing z/OS Connect (OpenAPI 2) installation.
    2. IMPORTANT: In the SMPCNTL command, ensure that the SELECT attribute includes any z/OS Connect (OpenAPI 2) Unlimited maintenance PTFs in addition to JZC3003.
    3. Submit the sample job twice, first with CHECK, then without. A return code of 0 indicates success.
  6. Optional: Accept z/OS Connect (OpenAPI 2) Unlimited.
    1. Customize the sample job BAQUACPT in hlq.unlimited.IBM.JZC3003.F2 RELFILE. Set the @hlqgzone@, @dname@, and @smpeoptions@ for your existing z/OS Connect (OpenAPI 2) installation.
    2. Submit the sample job twice, first with CHECK, then without. A return code of 0 indicates success.