Description: Prior to z/OS V1R13, a DOWN response to message IXC102A issued for a JES3 local processor required operations to enter the *S main,FLUSH command. Without the *S main,FLUSH command, jobs on the local were held up until the local processor was reconnected.
Starting in z/OS V1R13, JES3 flushes the active jobs on the local processor automatically as soon as the operator responds to message IXC102A. This automatic flush eliminates the step of issuing the command and reduces the time gap between the local processor being removed from the sysplex and job recovery actions.
In z/OS V1R13 JES3 and later releases, if you run the *S main,FLUSH command in response to the XCF messages, the command will have no effect because the affected jobs will have already been flushed by the new automatic processing.
| Element or feature: | z/OS JES3. |
| When change was introduced: | z/OS V1R13. |
| Applies to migration from: | z/OS V1R12 |
| Timing: | Before the first IPL of z/OS V2R1. |
| Is the migration action required? | No, but recommended to avoid redundant *S main,FLUSH commands. |
| Target system hardware requirements: | None. |
| Target system software requirements: | None. |
| Other system (coexistence or fallback) requirements: | None. |
| Restrictions: | None. |
| System impacts: | None. |
| Related IBM Health Checker for z/OS check: | None. |
Steps to take: If you want to avoid redundant *S main,FLUSH commands, remove the *S main,FLUSH command from all automated procedures or operating procedures.
Reference information: For more information, see z/OS JES3 Messages and z/OS JES3 Commands.