-STOP ACCEL command (Db2)

The Db2 command STOP ACCEL causes the Db2 subsystem to stop using the specified accelerator servers.

Environment

This command can be issued from a z/OS® console, a DSN session under TSO, a DB2I panel (DB2 COMMANDS), an IMS or CICS® terminal, or a program that uses the instrumentation facility interface (IFI).

Data sharing scope: Group or member

Authorization

To execute this command, you must use a privilege set of the process that includes one of the following authorities:
  • SYSOPR authority
  • SYSCTRL authority
  • SYSADM authority

Db2 commands that are issued from a logged-on z/OS console or TSO SDSF can be checked by Db2 authorization using primary and secondary authorization IDs. Start of changeA logged-on z/OS user ID must be defined in RACF or a similar security server.End of change

Syntax

Read syntax diagramSkip visual syntax diagramSTOP ACCEL(*)(, accelerator-name)MODE(QUIESCEFORCE)SCOPE(LOCALGROUP)MEMBER( member-name)

Option descriptions

(accelerator-name)
The accelerator server name. This option limits the stop command to the specified accelerator server.
(*)
Indicates that the stop command applies to all accelerator servers.
MODE
Indicates whether currently executing active accelerator threads are allowed to complete. Valid values are:
(QUIESCE)
Allows active accelerator threads to complete normally and terminates only inactive accelerator threads.
(FORCE)
Terminates all currently executing accelerator threads. Db2 reverts to baseline processing for the originating threads.
SCOPE
Specifies the scope of the command. In a non-data-sharing environment, the option is ignored. Valid values are:
(LOCAL)
Stops the current data sharing member from using the specified accelerator servers. This is the default.
(GROUP)
Stops the data sharing group from using the specified accelerator servers.
MEMBER
Stops specific members of the data sharing group from using the specified accelerator servers. The default behavior is to stop accelerator servers on the local member. This option is not supported in non-data sharing environments.

Usage notes

Specifying SCOPE(GLOBAL) with MEMBER(member-name)
If you specify both SCOPE(GLOBAL) and MEMBER(member-name), the command will be executed only on the specified members of the data sharing group.
Trace information for commands issued with group scope
If this command is issued with options that specify group scope in a Db2 data sharing member, it also runs on all other active members. IFICID 090 trace records for other group members can show that the same command was issued by the SYSOPR authorization ID from the 016.TLPKN5F correlation ID, in addition to the trace records from the member where the original command was issued. See Command scope in Db2 data sharing.

Example

The following command is used to stop the current data sharing member from using all accelerators, and to terminate only inactive accelerator threads.
-STOP ACCEL(*) MODE(QUIESCE) SCOPE(LOCAL)

Sample results follow:

Start of change
DSNX863I ) DSNX8STO STOP ACCELERATOR INITIATED FOR BLINK1
DSNX863I ) DSNX8STO STOP ACCELERATOR INITIATED FOR BLINK2
DSNX861I ) DSNX8CXA ALL OTHER ACCELERATORS STOPPED
DSN9022I ) DSNX8CMD '-STOP ACCEL' NORMAL COMPLETION
DSNX870I ) DSNX8EKG ACCELERATOR BLINK1 IS NOT ONLINE
DSNX860I ) DSNX8EKG STOP ACCELERATOR SUCCESSFUL FOR BLINK1
DSNX870I ) DSNX8EKG ACCELERATOR BLINK2 IS NOT ONLINE
DSNX860I ) DSNX8EKG STOP ACCELERATOR SUCCESSFUL FOR BLINK2
End of change