Resetting health status

This information describes how to reset the health status to 100 and also to 0.

Communication problems can cause the health status to drop. If the status drops to 0, it might have to be reset before the load balancer will send any new connections to the affected Gateway daemon. The health status can be reset regardless of the current health status value; you do not have to wait until the status drops to 0.

The health status can recover without intervention in some circumstances. For example, if a Java™ client application has 21 established connections to the Gateway daemon, and an ECI request is sent across each of the first 20 connections and fails with ECI_ERR_NO_CICS, health drops to 0. No new connections can be established, but because the Java client application still holds an existing connection to the Gateway, a successful request sent over that connection will cause the health to recover.

Log on to TSO and navigate to the SDSF console.
Enter the following command:
```
/F <JOB>,APPL=HEALTH,RESET
```
where <JOB> is the JCL jobname of the Gateway daemon. A message tells you whether the command completed successfully.

In HA environment, if shutdown is initiated for one of the CICS® TG instance, that CICS TG instance might receive few transactions during the shutdown phase from IBM® z/OS® Workload Manager (WLM). This might result failure of those transactions. Avoid such failures by invoking reset the gateway health to zero command and then initiate the shutdown of the gateway. To reset the health to zero, follow these steps:

Log on to TSO and navigate to the SDSF console.
Enter the following command:
```
/F <JOB>,APPL=HEALTH,RESETZERO
```
where <JOB> is the JCL jobname of the Gateway daemon to reset the gateway health to zero. A message tells you whether the command completed successfully.