INGCFL

Purpose

The INGCFL routine supports line mode for INGCF other than display capability. For further information see INGCF.

Support of the maintenance mode of a coupling facility depends on the function that is specified:

ACTIVATE, ENABLE, and POPULATE automatically handle the maintenance mode of the coupling facility. However, each command will fail when the coupling facility is in maintenance mode but the mode is not supported by SA z/OS® (see Restrictions and Limitations).
DEACTIVATE and DRAIN put the coupling facility into maintenance mode when possible. Otherwise, both functions proceed with setting the sender paths offline after the rebuild has been performed.
REBUILD does not make use of the maintenance mode capability.

Activate: Activates the coupling facility.
DEactivate: Deactivates the coupling facility after performing DRAIN.
DRain: Performs REBUILD, then puts the coupling facility into maintenance mode if possible. Otherwise, it sets the sender paths to OFFLINE.
Enable: Performs ACTIVATE, then takes the coupling facility out of maintenance mode if it is in this mode. Finally, it sets the sender paths to ONLINE.
Populate: Starts the populate process of the coupling facility after performing ENABLE.
Rebuild: Starts the rebuild process of the coupling facility.
CF_name: The name of the target coupling facility for the specified function.
RESP: Specifies whether the final result is returned synchronously as a return code or asynchronously as a message (default: synchronous response).
TARGET: Specifies the system where the command is executed (default: local system).

Note: The real activation and deactivation of a coupling facility are unavailable when running on a z/OS image that runs under z/VM®.

0: The command completed normally.
1: An initialization error occurred. Check the netlog for explanatory messages.
3: The slave routine failed. Check the netlog for explanatory messages. If you are still unable to detect the reason for failure, attempt a rerun after turning on debugging for the INGRVX92 slave routine.
4: The lock is unavailable to update the coupling facilities.
5: The authorization check failed for function. Check the netlog for explanatory messages.
6: The status of the coupling facility is not as expected for the current request. Running with GDPS debugging should provide a listing of status changes that have taken place. This return code does not necessarily indicate that the request failed.
7: The permission check has failed for the POPULATE request.

The real activation and deactivation of a coupling facility are unavailable when running on a z/OS image that runs under z/VM.