Modify the Started Task JCL for the ARM Wrapper

Managing High Availability › How to Implement HA Automatic Restart Management › Modify the Started Task JCL for the ARM Wrapper

Modify the Started Task JCL for the ARM Wrapper

The CHRARMW utility is used for registering and deregistering the CA Chorus started tasks with the Automatic Restart Manager (ARM).

Members of chorus_runtime_hlq.CETJJCL contain commented steps to complete the following tasks:

Register the started task with ARM before the main step execution (ARMREG).
Deregister the started task with ARM after the main step has successfully terminated (ARMDEREG).

ARM uses the following process to determine whether to restart a started task:

If the main step terminates with a non-zero condition code or abends, the ARMDEREG step does not execute.
If either option occurs, ARM automatically restarts the started task after address space termination.
The registration step specifies an element name. The default is the job name. Ensure that the element name corresponds to an element name in the ARM policy that was created in the previous step.

Note: If ARM is not enabled, you can rerun Automatic Configuration or can edit the jobs manually, as noted in this procedure. For Automatic Configuration details, see the Installation Guide.

Important! In the following content, CHORTSFB indicates the TSF Bridge started task; CHORNTSF indicates the TSF Server started task.

Follow these steps:

Edit the ARM parameters in the following members in chorus_runtime_hlq.CETJJCL as described in the member and save your changes:
- CHORJBOS member
- Each of the TSF members for the corresponding TSF tasks that you plan to use:
  - CHORNTSF member
  - CHORTSFB member
  - CHORTSFR member
The started task JCL is updated.
Copy the CHORJBOS, CHORTSFB, and CHORNTSF PROC into a specific PROCLIB for each eligible system. Edit both copies of CHORJBOS to match the configuration of the system.
Note: If a TSF Bridge (CHORTSFB) is copied to an LPAR where a TSF Relay (CHORTSFR) runs, stop the TSF Relay to let the TSF Bridge run.
If the failover system has different system values for the values in the ENV* members that are located in CETJOPTN, copy the ENV* members and reference them from the PROCLIB of each system.
(Optional) If you have TSF relays on other LPARs, update their CETJOPTN(TSFRPRMS) member to point to the new TTSFHOST.
Start the TSF Bridge:
```
S CHORTSFB
```
A message indicating that the TSF Bridge is initialized is logged.
```
N00503 *** TSF INITIALIZATION COMPLETE TSF ***
```
Start the TSF Server:
```
S CHORNTSF
```
A message indicating that the TSF Server is initialized is logged.
```
ETJTS001I *** TSF SERVER STARTUP COMPLETE ***
```
(Optional) Start the TSF Relay:
Important! This command is required if you are using a relay for remote LPARs and you are using a TSF Bridge.
```
S CHORTSFR
```
A message indicating that the TSF Relay is initialized is logged.
```
N00503 *** TSF INITIALIZATION COMPLETE TSF ***
```
Restart the CHORJBOS started task:
```
S CHORJBOS
```
The following message appears when the CA Chorus Application Server startup is complete:
```
ETJTC001I CA Chorus Startup Complete
```

You have successfully configured High Availability for CA Chorus using z/OS Automatic Restart Management.