How to Promote a Test System › Review Required Changes

Review Required Changes

General

The following items must be changed if the test and product system are on the same LPAR:

• High-level qualifier (HLQ) for the deployed libraries
• UNIX System Services (USS) Runtime Home
• CHORNTSF, CHORTSFB, or CHORTSFR instances running on the same LPAR
  • By design, CHORNTSF, CHORTSFB, and CHORTSFR communicate across two LPARs and require the same SUFFIX. However, within a single LPAR, multiple CHORNTSF, CHORTSFB, or CHORTSFR instances cannot share a SUFFIX.
  • By default, the suffix is PROD. For a second TSF instance on the same LPAR, you need a new suffix. The commands to make this change appear later in this scenario.

Maintenance

Confirm that CA Chorus, its disciplines, and back-end systems have all current maintenance applied.

Port range

CA Chorus has the following port requirements for the CA Chorus Application Server and Time Series Facility (TSF) components:

• Thirteen consecutive ports for the CA DSI server and CA Chorus Application server. The CA Chorus Application Server ports consist of one DSI two-way (connecting and listening) port, and 12 server (listening) ports.
• Two ports for the TSF Server. These ports are server (listening) ports similar to the 12 CA Chorus Application Server ports that are noted in the previous bullet.
• One one-way port for the TSF Bridge. (This port does not need to be consecutive with the 13 ports for the CA DSI server and CA Chorus Application Server.) You can specify an actual value (port number), or you can omit the value to let the TSF Bridge dynamically assign a port number.

  Note: If the TSF Bridge instances are being used on a remote LPAR, one more one-way port is required to receive data from a relay. You must specify an actual value; dynamic assignment is not supported.

• One one-way port for the TSF Relay. (This port does not need to be consecutive with the 13 ports for the CA DSI server and CA Chorus Application Server.) You can specify an actual value (port number), or you can omit the value to let the TSF Bridge dynamically assign a port number.

  Note: The TSF Remote Relay uses an additional port for monitoring the connection from the TSF relay to the TCP/IP stack. By default, this port is dynamically allocated. To specify this port value instead of having it dynamically allocated, edit the MONPORT parameter in the TSFRPRMS member in your_chorus_hlq.CETJOPTN.

To confirm that the ports you intend to use are available, consult your network management team.

H2 Database

Do not copy the H2 database (profile database) into a new environment. When you configure the new environment, the CA Chorus Application server creates an H2 database.

User Documentation

Evaluate any user documentation that has been indexed. Following the promotion, you can index this content in the new environment.

Important! Do not share the user doc file systems between two CA Chorus systems because you cannot mount a file system at two locations.

Started task names

Identify which of the follow uses cases matches your site:

• If the systems are running on a different LPAR, you can use the same Started Task Names. If you do so, place the procs for the started tasks in a separate proclib from the original location.
• If the systems are on the same LPAR, the started task names must be different. The procs can be in the same proclib.

Back-end system

You may want to access a different back-end system for some disciplines. For the instructions to establish access to the back-end systems, see the applicable Site Preparation Guide.