DB2 Server for VSE & VM: Operation

Forcing DB2 Server for VSE Remote Users to End Their Work

The FORCE RMTUSER operator command can be used to force remote (DRDA) DB2 Server for VSE users. The command can force users whether they have real agents or not. Also, the real agent may not be in a logical unit of work when the FORCE RMTUSER is initiated.

The FORCE RMTUSER operator command can also be used to free up the control structure for a remote connection. This will then allow other remote users to access the server.

Note:

The FORCE RMTUSER command will roll back the current LUW and will cause the conversation to end on the next request.

The FORCE RMTUSER operator command has the following syntax:

>>-FORCE RMTUSER--rmtuser ID-----------------------------------><

Before entering the FORCE RMTUSER command, a SHOW CONNECT must be entered to verify the remote user identifier (rmtuser ID). The output display of the SHOW CONNECT command will identify each remote user by a unique rmtuser ID, for example:

+--------------------------------------------------------------------------------+
|:
·
·
·
                                                                            |
|F4 004    User Agent:   5   User-ID: SQLUDAY1 SQL-ID: SQLUDAY1                  |
|F4 004       is R/O  APPL  14729                                                |
|F4 004       Agent is processing and is in communication  wait.                 |
|F4 004             State started: 1996-10-21  14:23:08                          |
|F4 004             Conversation started: 1996-10-21  14:22:57                   |
|F4 004             CPU time: 00:00:01                                           |
|F4 004             LUWID: CAIBMOML.OECGW001.A679B3B27B1E.0001                   |
|F4 004             EXTNAM: SQLUDAY1.1                                           |
|F4 004             Requester: SQLDS/VM  V3.3.0   at TOIVMLB6                    |
|F4 004             Rmtuser ID: 2                                                |
|F4 004             LU name: OMPGW001                                            |
|F4 004             Task no.: 0000046                                            |
|F4 004             Protocol: DRDA                                               |
|:
·
·
·
                                                                            |
+--------------------------------------------------------------------------------+

Use of this information will help prevent an operator from mistakenly forcing the wrong remote user from the system.

Note:

If the operator FORCE command does not stop the remote user successfully, the conversation can be ended by using the CICS master operator transaction (CEMT) which ends the APPC-to-XPCC Exchange Transaction (AXE) of the remote user. Forced ending of an AXE transaction by using the CEMT Terminate Task will result in a de-allocate abend to the application requester and an XPCC abnormal disconnect to the application server. For information on the use of the CEMT command, refer to the CICS/VSE CICS-Supplied Transactions manual.

VM/ESA FORCE Enhancements for CRR

It could occur that during resynchronization initialization or resynchronization recovery, the database manager waits indefinitly for a response from the CRR recovery server. If this is the case, the following command may be used to terminate resynchronization initialization processing:

>>-FORCE----+-RINIT-+------------------------------------------>< '-RREC--'

If "FORCE RINIT" is entered, resynchronization initialization processing is terminated and the SYNCPNT parameter is changed from Y to N. If "FORCE RREC" is entered, resynchronization recovery is terminated and deallocate (abend) is performed to terminate the conversation with the CRR recovery server.

Notes:

1. The operator must issue the SHOW ACTIVE, SHOW CONNECT or SHOW SYSTEM command prior to the FORCE RINIT/RREC command. Otherwise, the following message is issued:

    ARI0225E System operator must issue SHOW ACTIVE, SHOW CONNECT or
             SHOW SYSTEM command prior to FORCE command.
   

   and FORCE processing terminates.

2. If the database is not performing resynchronization initialization when the FORCE RINIT command is entered, then the following message is displayed:

    ARI2040E FORCE RINIT may only be entered when Resychronization
             Initialization is active.
   

   and FORCE processing terminates.

3. If the database is not performing resynchronization recovery when the FORCE RREC command is entered, then the following message is displayed:

    ARI2040E FORCE RREC may only be entered when Resychronization
             Recovery is active.
   

   and FORCE processing terminates.

4. If the FORCE RINIT command was already issued, the following message is displayed:

    ARI2041E FORCE RINIT is already scheduled.
   

   and FORCE processing terminates. (Note that the scheduled FORCE command remains!)

5. If the FORCE RREC command was already issued, the following message is displayed:

    ARI2041E FORCE RREC is already scheduled.
   

   and FORCE processing terminates. (Note that the scheduled FORCE command remains!)

6. If extra parameters are entered after "FORCE RINIT/RREC", then the following message is displayed:

    ARI0229E Too many FORCE command input parameters
   

   and FORCE processing terminates.