Start of change

COMMONQUEUE (DUMP(MASTERSCHEDULERCANDIDATE)): Specifying whether the host is a master scheduler candidate for grouped function of dump

Explanation: DUMP(MASTERSCHEDULERCANDIDATE)) is an optional subparameter of the COMMONQUEUE parameter. This specifies whether the host is a master scheduler candidate for the common dump queue.

Subsequent SETSYS commands after a CONNECT can be issued to change the MASTERSCHEDULERCANDIDATE state of this member of the dump group. A specification of MSC(NO) will remove this member as a master scheduler candidate, and if the member was currently active as the master scheduler, it will be stopped. The system will reassign the master scheduler to another dump group member that was defined as a candidate, if one is available. New incoming work will be assigned to run in this new master scheduler member. Active and queued work will be allowed to complete. A specification of MSC(YES) will allow this member to become the master scheduler if needed by the dump group. This stand-alone MSC specification will have no effect until the host is connected to the group.

If it is known at startup that a system is not a candidate for being the master scheduler, but the system needs to be a member of the dump group, the MSC(NO) and CONNECT(basename) subparameters should be specified together in the DUMP keyword.

SMS relationship: Not applicable.

SETSYS default: None.

DFSMShsm default: MASTERSCHEDULERCANDIDATE(Y), but will have no effect until a SETSYS CQUEUE(DUMP(CONNECT(basename))) command is issued.

For more information: Refer to Common dump queue.

End of change