Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 12 Starting and Shutting Down TIBCO Object Service Broker : Shutting Down the TIBCO Object Service Broker System

Shutting Down the TIBCO Object Service Broker System
Overview
To ensure an orderly shutdown, complete the following tasks:
1.
2.
3.
4.
5.
Each of these tasks is described in detail below.
 
Task A Determine Who Is Logged In to TIBCO Object Service Broker
There are several ways to determine which users are currently logged in to TIBCO Object Service Broker:
From within TIBCO Object Service Broker
From the administrator workbench, position your cursor beside the ST Statistics option and press Enter. This selection displays the TIBCO Object Service Broker Statistics main menu. You can then select the Users Logged On option and press Enter.
From the TIBCO Object Service Broker Administration Menu
Execute the S6BTLADM utility and use option I. Refer to I. User Activity for more information.
From the z/OS Operator Console
If you have access to a z/OS operator console, you can issue the following command:
MODIFY dob_jobname,USERLIST
In this command, dob_jobname is the name of the batch job or started task used to start the Data Object Broker. For more information about the forms of this command, refer to Chapter 16, Operator Commands.
From Within CICS
Use the HINQ transaction to list users currently active to the CICS Execution Environment. The HINQ transaction states whether the Execution Environment subtask is attached or detached, and lists the number of users and their user IDs.
This transaction code is issued in the following form:
HINQ USERC
This is the same as above without listing the user IDs
You can also issue the HINQ command as part of a Modify command from the z/OS operator console. For example:
Modify cics_jobname,HINQ userid
Refer to Commands to Control the CICS Execution Environment for more information about the HINQ command. For more information about issuing TIBCO Object Service Broker operator commands, refer to Chapter 16, Operator Commands.
Do not use the CICS message utility CMSG to broadcast a message telling all users to log out. CMSG overwrites the screens of CICS users who are in pseudo-conversational mode.
Task B If Necessary, Cancel Users
If you need to cancel a specific user ID, do one of the following:
From the Data Object Broker
From the z/OS operator console, issue the command:
Modify dob_jobname,Canceluser=userid
where
With the TIBCO Object Service Broker Administration Menu
Execute the S6BTLADM utility and use option I. Refer to I. User Activity for more information.
From the Execution Environment
From the z/OS operator console, issue the command:
Modify ee_jobname,HCUS userid
where
If multiple connections have the same user ID, a list of all connections for the specified user ID is presented on the console. Select the connection you require and reenter the command with the appropriate reference number extension.
From the CICS Execution Environment
Do one of the following:
HCUS userid
From the z/OS operator console, issue the HCUS (Canceluser) command as follows:
Modify cics_jobname,HCUS userid
Task C Shut Down the Servers
All users and servers are automatically logged out if they are still active when the Data Object Broker begins to shut down. The Data Object Broker also automatically issues final SMF records at this time.
You should use the STOPSERVER command to shut down any batch servers and external database servers before you initiate the Data Object Broker shutdown.
Shutting Down Servers Using the Administration Menu (S6BTLADM)
Execute the S6BTLADM utility and use option 3 to shut servers down using the Resource Management of the Administration menu. Refer to 3. Resource Management for more information.
Shutting Down Servers Using the z/OS Operator Console
If you have access to a z/OS operator console, you can issue the following command:
MODIFY dob_jobname,STOPSERVER=connection_id
In this command, dob_jobname is the name of the Data Object Broker batch job or started task addressed by this command and the connection_id is the unique identifier for the connection. For valid values for this command, refer to Chapter 16, Operator Commands.
Task D Shut Down the Execution Environments
This section describes how to shut down the various types of Execution Environments in the TIBCO Object Service Broker environment.
TSO
A TSO Execution Environment shuts down when its user logs out of TIBCO Object Service Broker.
CICS
Do one of the following:
To shut down a CICS Execution Environment without shutting CICS down, enter the transaction code HTRM from any CICS session or from the z/OS operator console.
Issue the following command from the console to delay the shutdown until active users are done:
MODIFY cics_jobname,HTRM SHUTD
Issue the following command from the console for an immediate shutdown:
MODIFY cics_jobname,HTRM SHUTI
To shut down the CICS Execution Environment automatically when you shut down CICS, define the program S6BCSTRM to the CICS shutdown PLT.
Native Execution Environment
You can shut down a Native Execution Environment by doing one of the following:
p ee_jobname
or
Modify ee_jobname,Shutdown
where
Refer to Commands to Control the Native Execution Environment.
Task E Shut Down the Data Object Broker
You can shut down the Data Object Broker by doing one of the following:
Issue the Shutdown command from the z/OS operator console:
Modify dob_jobname,Shutdown
In this example, dob_jobname is the name of the batch job or started task used to start the Data Object Broker. Active connections to the Data Object Broker are terminated when the Shutdown command is processed.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved