Copyright © Cloud Software Group, Inc. All Rights Reserved
Copyright © Cloud Software Group, Inc. All Rights Reserved


Chapter 18 Monitoring and Controlling the TIBCO Object Service Broker Environment : Administration Controls
Administration Controls
1. In-Doubt Transactions
Function
Option 1, IN-DOUBT TRANSACTIONS, displays a list of transactions involving service providers that could not be fully completed for some reason.
* 
If the system is recycled before an in-doubt transaction is resolved, TIBCO Object Service Broker automatically reacquires the logical locks for the transaction during the restart process.
In-Doubt Transaction List Screen
 
S6BADM11 S6DCDOBA IN-DOUBT TRANSACTIONS LIST 2008JUL09 06:13:38
 
LOCAL ORIGINATING
TRK DATE TIME STAGE STATUS LOCK ID USER ID LOCK ID NODE NAME
1 2008JUL09 05:05 CONTNGT IN-DOUBT 0000023F CLARKD
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
                 PLACE CURSOR ON DESIRED TRACK AND HIT PF2 TO ZOOM
 
Screen Headings
 
TRK
Track Number — Identifies the contingency log entry.
DATE and TIME
The date and time when the commit was first saved on the contingency log.
STAGE
Stage or phase within the commit cycle that is currently being processed:
PHASE 1 — Prepare-to-commit stage of a two-phase commit.
PHASE 2 — Commit stage of a two-phase commit.
CONTINGT (Contingent) — TDS updates are held pending confirmation of the service provider’s update status.
STATUS
Identifies the current status of the contingency log
PROGRESS — The commit cycle is continuing.
M-COMMIT — The commit continues because of manual intervention.
M-ABORT — The commit is aborted because of manual intervention.
P-ABORT — The commit coordinator determined that the commit cycle should abort; however, either all resources have not been informed, or have not confirmed their aborts.
HELD — The local TDS concerns of a commit are done; however, there are service provider commit or cleanup confirmations outstanding.
CHECKING — The commit coordinator is currently attempting to resolve an in-doubt transaction.
IN-DOUBT — A service provider is lost during the commit cycle; it is undetermined if the commit should continue.
LOCAL LOCK ID
A reference number generated by the Data Object Broker to relate concerns within an identifiable transaction.
USERID
An 8 character identifier used by TIBCO Object Service Broker security to determine access privileges.
ORIGINATING LOCK
ID and NODE NAME
If the contingency log is created as a result of a commit coordinated by a different TIBCO Object Service Broker, the lock ID and node name displayed identify the transaction on the named TIBCO Object Service Broker node.
Other Available Screens
From the IN-DOUBT TRANSACTIONS LIST screen, you can display the following nested screens:
•
The IN-DOUBT TRANSACTION DISPLAY screen
•
The IN-DOUBT TDS DETAIL screen
These screens are described below.
In-Doubt Transaction Display Screen
Function
The IN-DOUBT TRANSACTION DISPLAY screen displays a detailed list of all resources involved in in-doubt transactions.
To Display
Place the cursor on the desired track in the IN-DOUBT TRANSACTIONS LIST screen and press PF2. A screen similar to the following appears:
 
S6BADM12 S6DCDOBA IN-DOUBT TRANSACTIONS DISPLAY 2008JUL09 06:13:38
 
LOCAL ORIGINATING
TRK DATE TIME STAGE STATUS LOCK ID USER ID LOCK ID NODE NAME
1 2008JUL09 05:05 CONTNGT IN-DOUBT 0000023F CLARKD
 
 
 
 
TRANSACTION RESOURCE LIST
 
CONFIGURED PROCESSING ACCESS REMOTE
TYPE SERVER ID F.S. LEVEL F.S. LEVEL NODE ID TRACK
TDS LOCAL
HRN S6DCDOBB FAIL SAFE 2 FAIL SAFE 1 S6DCDOBB DAB00003
 
 
 
 
PF2-TDS DETAIL PF4-IN-DOUBT LIST PF9-DELETE PF10-COMMIT PF11-ABORT
 
Key Commands
PF1
Display help information about the current screen.
PF2
Display the TDS DETAIL screen.
PF3
Return to the main menu.
PF4
Redisplay the IN-DOUBT LIST screen.
PF6
Print the current screen.
PF9
Manually delete the transaction from this system, if authorized.
PF10
Manually commit the transaction, if authorized.
PF11
Abort the transaction, if authorized.
PF12
Exit from the Administration menu.
In-Doubt TDS Detail Screen
Function
The IN-DOUBT TDS DETAIL screen displays TDS concerns for the contingency log Entry shown on the IN-DOUBT TRANSACTION DISPLAY screen.
To Display
Press PF2 from the IN-DOUBT TRANSACTION DISPLAY screen.
 
S6BADM13 S6DCDOBA IN-DOUBT TDS DETAIL 2008JUL09 06:14:16
LOCAL ORIGINATING
TRK DATE TIME STAGE STATUS LOCK ID USER ID LOCK ID NODE NAME
1 2008JUL09 05:05 CONTNGT IN-DOUBT 0000023F CLARKD
 
TDS PENDING TDS PENDING
TABLE NAME INST DELT REPL TABLE NAME INST DELT REPL
CLXWRITE DJC_PEER 1 0 0
 
 
 
 
 
 
 
 
 
 
 
 
PF2-IN-DOUBT DISPLAY PF4-IN-DOUBT LIST
 
2. Operator Functions
Function
Option 2, OPERATOR FUNCTIONS, displays the most recent log messages.
Message Log Display Screen
 
S6BADM21 S6H1DOBB MESSAGE LOG DISPLAY 2006NOV29 14:22:31
13:18:07 S6BKC017L-V50 DBA LOGGED OFF #=000041 TYPE=TSO USER COMM=XMS SO
13:18:07 S6BKC017L-V50 @OP008D0 LOGGED OFF #=000040 TYPE=OPERATOR COMM=XMS SO
13:28:40 S6BKC017L-V50 USR00 LOGGED OFF #=000039 TYPE=TSO USER COMM=XMS SO
13:28:40 S6BKC017L-V50 @OP00CE0 LOGGED OFF #=000038 TYPE=OPERATOR COMM=XMS SO
14:11:00 S6BKC017L-V50 USERP    LOGGED OFF #=000033 TYPE=OPERATOR COMM=XMS SO
14:14:51 S6BKC016L-V50 USERP    CONNECTED  #=000033 TYPE=OPERATOR COMM=XMS SOU
14:17:08 S6BKC017L-V50 USR00 LOGGED OFF #=000036 TYPE=TSO USER COMM=XMS SO
14:17:08 S6BKC017L-V50 @OP01090 LOGGED OFF #=000035 TYPE=OPERATOR COMM=XMS SO
14:18:45 S6BKC017L-V50 USERP    LOGGED OFF #=000033 TYPE=OPERATOR COMM=XMS SO
14:19:00 S6BKP005L-V50 MODIFY S6H1DOBB SPINS=I
14:19:00 S6BKP006I-V50 MODIFY COMMAND ACCEPTED
14:19:00 S6BKX051L-V50 START CHECKPOINT - 822 14:19:00 LOCAL
14:19:01 S6BKX052L-V50 END CHECKPOINT - 822 14:19:00 LOCAL COUNT= 77
14:19:01 S6BKX008A-V50 JOURNAL 002 SPIN IN PROCESS
14:19:02 S6BKC016L-V50 OSBBSTC CONNECTED #=000033 TYPE=OPERATOR COMM=XMS SOU
14:19:02 S6BKX009A-V50 JRNL 002 SPIN:JOB=JOB04871 PG= 255 STATUS=00-00 DUR
14:19:02 S6BKC017L-V50 OSBBSTC LOGGED OFF #=000033 TYPE=OPERATOR COMM=XMS SO
14:19:02 S6BDB090I-V50 OPEN S6B.VTH.JRNL2
14:19:17 S6BKC016L-V50 USERP    CONNECTED #=000033 TYPE=OPERATOR COMM=XMS SOU
 
ENTER-REFRESH PF2-COMMAND LIST
 
Issuing Operator Commands
Press PF2 to display a list of operator commands for the Data Object Broker. To issue a command:
•
Press Tab to place the cursor on the desired command and press Enter.
•
Type a command on the input line and press PF10 to issue the command.
You are prompted to press PF11 to confirm the command.
Illustration of the Operator Commands Screen
 
S6BADM22 S6DCDOBA OPERATOR COMMANDS 2011JAN07 03:06:58
 
BWOSTATUS CANCELTERMID (I) CANCELUSER (I)
CHECKPOINT COMRESTART CRSTATUS
CS N/A DBJRNLOFF (B) DBJRNLON (B)
DBOFFLINE (B) DBONLINE (B) DBREADONLY (B)
DBREADWRITE (B) DBSEGMENTSTAT (B) FORCEUSER (I)
FREEZE GTFSTATUS JOURNALOFF N/A
JOURNALON N/A JOURNALSTATUS MEMBERLIST
NETSTART NOTRACE (I) PARAMETER N/A
PEERCANCEL N/A QUIESCE RESUME
SHUTDOWN SPINENABLE N/A SPINLOADJCL N/A
SPINSUBMIT=N SPINSUBMIT=I SPINSUBMIT=C
STARTPEER N/A STOPSERVER (E) SWEEPACTION N/A
SWEEPLIMIT N/A SWITCH N/A TIMESTAMP
TRACEID (I) UNFREEZE USERCOUNT (I)
USERLIST (I) USERMAX N/A WTOPRINT
 
 
 
INPUT COMMAND: __________________________________________________
 
ENTER-ISSUE SELECTED COMMAND PF10-ISSUE INPUT COMMAND
 
3. Resource Management
Function
Option 3, RESOURCE MANAGEMENT, lists the TIBCO Object Service Broker resources you can manage with the Administration menu. To update TIBCO Object Service Broker resources through the Resource Management facility, you must have TIBCO Object Service Broker Administrator or Operator authority.
What is a TIBCO Object Service Broker Resource?
A TIBCO Object Service Broker resource is an interface to an environment managed by the Data Object Broker. For example:
•
A connection to or from another Data Object Broker
•
A connection to an external DBMS from the Data Object Broker
•
A connection to a peer server or a Service Gateway for Files
Data Object Broker Parameters and Resource Management
The following Data Object Broker parameters affect the processing of resource management data:
DYNAMICRESOURCE
Specifies whether to allow resource entries to be created dynamically.
MAXNODES
Maximum number of peer nodes.
MAXRESOURCES
Maximum number of resources.
RSCSCHEDULES
Average number of schedule entries for each resource. Each line in a schedule entry counts as an entry when estimating a value for RSCSCHEDULES.
Refer to TIBCO Object Service Broker Parameters for more information about these parameters.
RESOURCE File
The data needed for resource management is stored in a standard VSAM Keyed Sequenced Data Set (KSDS) referred to as a repository. Its record size is 128. It can be created, backed up, and reorganized using IDCAMS when the Data Object Broker is offline. It must be defined in the DBDLIB.
Resource Types
Resources are identified by a 3‑character code:
Code
Resource Type
Table type (for example, ADA, DAT, DB2)
External database server.
API
•
Remote peer servers that provide rules access on a remote TIBCO Object Service Broker node.
•
Service Gateway for Files
HIN
Inbound Data Object Broker communications, identifying connections from a remote TIBCO Object Service Broker node to a local TIBCO Object Service Broker node.
HRN
Outbound Data Object Broker communications, identifying connections from a local TIBCO Object Service Broker node to a remote TIBCO Object Service Broker node.
The RESOURCE TYPE LIST screen displays all the available resource types. The Resource Manager supports up to 32 different resource types.
Peer server and external database server resources are established by running batch jobs or started tasks. Use the Resource Manager to schedule when these resources are available. The Resource Manager does not start these tasks for you.
Inbound (HIN) and outbound (HRN) resources defined for peer TIBCO Object Service Broker communications must be defined at both ends of the connection.
Resource Groups
Connections within each resource type can be grouped into connections that have the same characteristics and are functionally equivalent to each other. Up to 512 connections can be defined within a single group.
The combined resource type and the resource group are referred to as the resource name used for scheduling resources or displaying their details. For example, an inbound connection (HIN resource type) in the resource group called OSTARSRV1 would have the resource name of HINOSTARSRV1.
The RESOURCE GROUP LIST screen displays all the available resource groups.
Use resource groups to define common characteristics for connections. For example, you should define a group of resources for each server ID in an external database server. To enable connections between Data Object Brokers, define a resource group for each Data Object Broker.
Wildcard Processing
The value “????????” is a reserved resource group. If you specify this value, the Resource Manager generates a definition for a resource at connection time, using dynamic resource naming.
Resource Type List Screen
Function
The RESOURCE TYPE LIST screen shows the available resource types.
Illustration of the Resource Type List Screen
 
S6BADM31 S6H1DOBB RESOURCE TYPE LIST 2006NOV29 14:35:55
 
 
ADA API DAT DB2
 
HIN HRN IDM IMS
 
 
 
 
 
 
 
TYPE ___ GROUP ________
 
 
ENTER-GROUPS PF2-DETAIL PF4-NODES PF5-ADD PF9-TURNAROUND PF10-SCHED PF11-STOP
 
Key Commands
Enter
Display the groups within a selected resource type. Select a resource type by entering its name or positioning the cursor on the name. In some emulators, you can also place the mouse pointer over the type name and use the right mouse button to select a type.
PF1
Display help information about the current screen.
PF2
Display details about the selected resource. Enter a valid TYPE and GROUP to display the RESOURCE DETAIL screen.
PF3
Return to the main Administration menu.
PF4
Display all TIBCO Object Service Broker node names known to the Resource Manager. The NODE NAME LIST screen appears.
PF5
Add a new entry in the resource detail list. The RESOURCE DETAIL screen appears in input mode. If no resources are defined when selecting RESOURCE MANAGEMENT from the main Administration menu, the RESOURCE DETAIL screen appears in input mode.
PF9
Display a summary profile of message turnaround times for various resource types. The MESSAGE TURNAROUND TIME screen appears.
PF10
Display a list of all defined schedule names known to the Resource Manager. The DEFINED SCHEDULE LIST screen appears.
PF11
Stop all connections of all paths within a selected resource type. You are prompted to confirm the request.
PF12
Exit from the Administration menu.
Managing TIBCO Object Service Broker Resources
From the RESOURCE TYPE LIST screen, you use the following screens to manage TIBCO Object Service Broker resources:
•
Resource Group List Screen
•
Resource Detail Screen
•
Node Name List Screen
•
Message Turnaround Time Screen
•
Defined Schedule List Screen
The sections below describe these screens.
Resource Group List Screen
Function
The RESOURCE GROUP LIST screen shows the available resource groups within a selected type.
To Display
•
From the RESOURCE TYPE LIST screen, select a resource type and press Enter.
•
From the RESOURCE DETAIL SCREEN or the PATH LIST SCREEN, press PF4.
If more than 133 groups are defined within a type, 28 rows of data appear on a model 3 display, and 39 rows of data appear on a model 4 display.
Illustration of the Resource Group List Screen
 
S6BADM32 S6H1DOBB RESOURCE GROUP LIST FOR TYPE = API 2006NOV29 14:38:08
 
DEFAULT0 FILEGATE GEORGETN PICTON
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
INPUT GROUP ________ ENTER-DETAIL PF4-TYPE LIST PF5-ADD GROUP PF11-STOP GROUP
NO MORE DATA TO BE DISPLAYED
 
Key Commands
Enter
Display the resource detail for a selected resource group. Select a resource group by entering its name or positioning the cursor on the name. In some emulators, you can also place the mouse pointer over the group name and use the right mouse button to select a group.
PF1
Display help information about the current screen.
PF3
Return to the main Administration menu.
PF4
Return to the RESOURCE TYPE LIST.
PF5
Add a group. The RESOURCE DETAIL screen appears in input mode. The type is set to the resource type displayed in the RESOURCE GROUP LIST screen. If no resources are defined when selecting RESOURCE MANAGEMENT from the main Administration menu, the RESOURCE DETAIL screen appears in input mode.
PF11
Stop all connections within a selected resource group. You are prompted to confirm the stop request.
PF12
Exit from the Administration menu.
Resource Detail Screen
Function
The RESOURCE DETAIL screen displays the following resource information:
•
Defined characteristics of the resource: for example, resource type and group, commit level, in-doubt transactions, node name
•
Configuration of the online and common connection paths
•
Statistics by access type: how many paths are in use and the number of transactions against them
•
The resource schedule that applies to those paths
To Display
•
From the NODE NAME LIST screen, place the cursor on the desired node name. Press Enter for outbound paths (HRN resource type) and press PF2 for inbound paths (HIN resource type).
•
From the RESOURCE TYPE LIST, select a resource type and a resource group and press PF2.
•
From the RESOURCE GROUP LIST, select a resource group and press Enter.
•
From the PATH LIST SCREEN, press PF5.
•
From the DEFINED SCHEDULE LIST, select a schedule and press PF2.
•
From the RESOURCE SCHEDULE screen, or the USERS OF SCHEDULE screen, press Enter.
Illustration of the Resource Detail Screen
 
S6BADM33 S6H1DOBB RESOURCE DETAIL FOR API DEFAULT0 2006NOV29 14:38:08
 
INTERMEDIATE ROLLBK Y EARLY RELEASE Y LAST USER REUSE Y COMMIT LEVEL 2
RETRY INTERVAL 0 TP NAME USER ID PREFIX FAILURES 0
NODE AMDSDCTHURON INDOUBTS N MONITOR/SMF N
 
CONNECTIONS IN-USE TRX MESSAGE
CUR MAX LMT CUR MAX COUNT COUNT
ONLINE 0 0 0 0 0 0 0
COMMON 10 10 10 0 0 0 0
 
SCHEDULE NAME COMMON
 
APPLICABLE DAYS EXCEPTION START ONLINE CONNECTIONS
MON TUE WED THR FRI SAT SUN DATE TIME ONLY MAX
Y Y Y Y Y Y Y 00:00 N 10
 
 
 
 
 
 
ENTER-PATHS PF2-TYPE PF4-GROUP PF5-PEER PF9-START PF10-SCHEDULES PF11-UPDATE
NO MORE DATA TO BE DISPLAYED
 
Use the RESOURCE DETAIL screen to monitor resource path connections.
The top section of the screen presents the defined characteristics of the resource. The middle section shows statistics by access type. The lower portion displays the current schedule of connection limits.
Resource Characteristics
The characteristics section of the screen displays the following fields:
INTERMEDIATE ROLLBK
This flag indicates whether this resource expects to receive a “sync” message following a rollback request to terminate a transaction.
The setting of this value is specific to each resource type. Refer to the manual for the server to determine what it should be.
Valid values are “Y” (yes), “N” (no), and “?” (wildcard). A wildcard indicates that the resource takes on the characteristic of the connection. We recommend that you not use the wildcard setting for this characteristic under normal conditions.
EARLY RELEASE
The early release feature enables resources that were not updated to be released early in the commit cycle. The early release shortens the duration of the commit cycle by reducing the number of contributors. It also releases the resource path so that it can be reassigned sooner.
Note  EARLY RELEASE should not be used with paths that are generated for specific batch jobs or when there is only one path available. Valid values are “Y” (yes), “N” (no), and “?” (wildcard).
LAST USER REUSE
This features gives selection preference to paths that were most recently used by the current user. Some resources can bypass part of the security processing if the same user processes a subsequent transaction. Valid values are “Y” (yes), “N” (no), and “?” (wildcard).
COMMIT LEVEL
The commit level indicator identifies the highest commit level a resource is capable of supporting.
The three levels are “0” (serial), “1” (contingent or Fail Safe 1), and “2” (two phased or Fail Safe 2). DBMS resources should be set to “1” and peer Data Object Brokers and peer rules servers to “2”.
Note  To retain data integrity in a commit group with more than 1 update location, level “0” should not be used.
The following group of characteristics are used only for the resources for which the Data Object Broker generates connections.
RETRY INTERVAL
If the connection fails and there are no active connections to the target the retry interval specifies a wait time in minutes (1-60) until the connect attempt is retried. If “0”, there is no retry attempt.
TP NAME
When multiple Data Object Brokers are running on a non-z/OS platform a TP Name must be supplied so the communications subsystem can differentiate between them.
USER ID PREFIX
The generated unique user ID of the path. To avoid conflicts and enhance identification it is recommended that the user ID prefix be unique throughout the configuration.
FAILURES
The number of transactions that failed because there were no paths available for the resource. That is, you did not have enough resources to meet the demand. To diagnose a remote access failure, check for local failures under HRN and remote failures under API.
NODE
Specifies the logical node name (up to 16 bytes) of peer TIBCO Object Service Broker resources. The Node is required input for all “HRN” and “HIN” type resources. It must be unique throughout the configuration.
INDOUBT
Indicates whether there are in-doubt transactions against the displayed resource.
MONITOR/SMF
If the SMFRECORD and SMF28INTERVAL Data Object Broker parameters are set, to capture interval server usage statistics, set the monitor/smf value to “Y”. By default, the statistics are not collected.
Monitoring Path Connections
The statistics displayed for the resource are identified as either online or common, where:
Online resources
Can be used only by transactions run from a terminal.
Common resources
Can be accessed by batch jobs or terminal-based transactions.
The following path usage statistics appear:
CONNECTIONS
The current, maximum concurrent, and limit connection counts.
IN-USE
The MAX column shows how many paths were used in the life of the current Data Object Broker. The CUR field shows the number of paths currently in use.
TRX COUNT
The number of transactions associated with the resource.
MESSAGE COUNT
The total number of messages sent to the resource.
You should review the CONNECTIONS and IN USE counters regularly to ensure the appropriate number of connections are scheduled to meet the demand.
Updating Resource Entries
Press PF11 on the RESOURCE DETAIL screen to update or delete the resource entry. You are prompted to confirm your changes. You can edit these fields in input mode:
Resource Type
Specifies the kind of connection on this resource to the remote component. Valid values are:
HRN — For an outbound connection to a peer Data Object Broker
HIN — For an inbound connection to a peer Data Object Broker
API — For a connection from a peer server or a Service Gateway for Files
DB2, IDM, and so on — For connections to external database servers. This field usually has the same value as the TIBCO Object Service Broker table type.
An outbound connection is used if the local Data Object Broker issues data access requests to the remote peer. Inversely, an inbound connection is for data access requests coming from a remote peer. If the same remote peer requires both outbound and inbound connections, two resource detail entries are required.
Resource Group
The name of the resource group.
INTERMEDIATE ROLLBK
Indicates whether the resource expects to receive a sync message following a rollback request.
Valid values are Y or N. You should not use the wildcard (?) character under normal conditions.
EARLY RELEASE
When a service provider is released at the end of a transaction, it is released either in series or in parallel. Early release is recommended.
The early release option causes external resources that were not updated within the transaction to be released simultaneously, that is, in parallel. This decreases turnaround time and improves response time performance for interactive users because the effective commit group is reduced.
If early release is selected, the slight delay in server release can potentially increase server-not-available failures if there are too few servers connected. It usually takes longer for server release and acknowledgment to be processed than for TIBCO Object Service Broker to turn around the user transaction end (that is, the user application could be ready for the next transaction before the server is again generally available for it).
LAST USER REUSE
With some external database management systems, it is more efficient if the same server is used to process consecutive transactions from the same user. With DB2, for example, the server permits bypassing of some processing related to security when a new transaction is initiated via a server whose immediate previous user was the same as the current one.
Other servers, however, could be unaffected by such reuse. Enabling this facility for such servers yields no benefit, and, in fact, results in slightly reduced efficiency.
COMMIT LEVEL
This indicator specifies the highest commit protocol level that an external resource can support. Valid values are:
2 — Two-phase commit protocol. Recommended for use with other Data Object Brokers and with peer servers
1 — Contingent commit. Recommended for external database servers.
0 — Serial Commit. Not recommended for any connection. Use only if the external resource is unable to support Fail Safe levels 1 or 2.
RETRY INTERVAL
If a connection fails and there are no active connections to the target, RETRY INTERVAL specifies the wait time in minutes (1-60) before retrying a connection. A setting of 0 indicates no attempt to retry. Used only for the resources that the Data Object Broker generates connections for (resource type HRN).
TP NAME
Identifies a Data Object Broker on a non-z/OS platform running multiple Data Object Brokers.
USER ID PREFIX
When a connection request is generated to a remote resource, a user ID is generated to identify the connection. The user ID is prefixed by these three characters.
When a connection to a resource is generated by the Data Object Broker, the user ID associated with that connection must be unique. The actual user ID contains a five-digit sequence number appended to the specified three-character prefix; for example, T2P00001.
NODE
The logical node name, up to 16 bytes, of a peer TIBCO Object Service Broker resource. A node name is required for outbound (HRN) and inbound (HIN) resources. TIBCO Object Service Broker rules use the node name to indicate a target Data Object Broker, for example GET TABLE (’nodename’);. It must be unique throughout the configuration.
SCHEDULE NAME
Name of a resource schedule that controls connection limits. The name can be up to 11 characters. It can be different from the resource name, and if a schedule is specific to a resource, make the schedule name the same as the resource name. For example, an inbound connection (HIN resource type) in the resource group called OSTARSRV1 would have the resource name of HINOSTARSRV1.
To reduce maintenance effort, you should use generic schedule names (for example, WEEKDAYS05, WEEKEND06) and define shared schedules where possible.
DELETE
Appears when the RESOURCE DETAIL screen is in input mode. To delete the resource detail entry, set to Y. The DELETE field is not visible in browse mode.
Key Commands
Enter
Display the connected paths within a named resource.
PF1
Display help information about the current screen.
PF2
Return to the RESOURCE TYPE LIST screen.
PF3
Return to the main Administration menu.
PF4
Display the RESOURCE GROUP LIST screens.
PF5
Display the NODE NAME LIST screen.
PF9
Start a connection to another outbound peer if the current connection count for online or common accesses is below the maximum connection limit.
PF10
Display a list of all defined schedule names known to the Resource Manager. The DEFINED SCHEDULE LIST screen appears.
PF11
Toggle browse and input mode of the RESOURCE DETAIL screen for the selected resource. In input mode, the DELETE field appears where you can delete the resource detail entry.
PF12
Exit from the Administration menu.
See Also
The appropriate TIBCO Service Gateway manual for proper settings for intermediate rollback.
Node Name List Screen
Function
The NODE NAME LIST displays the node names of the available Data Object Brokers.
To Display
•
From the RESOURCE TYPE LIST screen, press PF4.
•
From the RESOURCE DETAIL screen, press PF5.
Illustration of Node Name List Screen
 
S6BADM35 S6H1DOBB NODE NAME LIST 2006NOV29 14:45:32
 
AMDSDCPHURON AMDSDCTHUR31 AMDSDCTHUR32 AMDSDCTHUR40
AMDSDCTHUR41 CASPER CASPER00 GEORGETOWN
V4R1
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
ENTER-OUTBOUND DETAIL PF2-INBOUND DETAIL PF4-TYPE LIST PF5-PROCESS
NO MORE DATA TO BE DISPLAYED
 
Key Commands
Enter
Display RESOURCE DETAIL screen for outbound paths (HRN resource type). Place your cursor beside the desired NODE NAME and press Enter.
PF1
Display help information about the current screen.
PF2
Display RESOURCE DETAIL screen for inbound paths (HIN resource type). Place your cursor beside the desired NODE NAME and press PF2.
PF3
Return to the main menu.
PF4
Display the RESOURCE TYPE LIST screen.
PF5
Access the selected node
All subsequent commands in the Administration menu apply to the chosen node until you exit from the menu or use the NODE NAME LIST option to choose another node.
The local node appears by default whenever you select the NODENAME LIST option, regardless of any previous node processing.
Note  Remote administration is supported only for Data Object Brokers at the same release level.
PF12
Exit from the Administration menu.
Path List Screen
Function
Lists all the connected paths within the resource identified in the screen title. It also shows the job name under which the Execution Environment is running, the status of the path, and its utilization.
To Display
From the RESOURCE DETAIL screen, press Enter.
Illustration of the Path List Screen
 
S6BADM34 S6H1DOBB PATH LIST FOR API DEFAULT0 2006NOV29 14:52:04
 
CURRENT JOB LAST TIMES MESSAGE LAST
ID USER NAME STATUS MSG USED COUNT PARTNER USER
T00E6000 IDLE 0 0 U00E6000
T00E6001 IDLE 0 0 U00E6001
T00E6002 IDLE 0 0 U00E6002
T00E6003 IDLE 0 0 U00E6003
T00E6004 IDLE 0 0 U00E6004
T00E6005 IDLE 0 0 U00E6005
T00E6006 IDLE 0 0 U00E6006
T00E6007 IDLE 0 0 U00E6007
T00E6008 IDLE 0 0 U00E6008
T00E6009 IDLE 0 0 U00E6009
 
 
 
 
 
 
 
 
ENTER-REFRESH PF2-TYPE LIST PF4-GROUP LIST PF5-DETAIL PF11-STOP SERVER
NO MORE DATA TO BE DISPLAYED
 
Key Commands
Enter
Refresh the display.
PF1
Display help information about the current screen.
PF2
Display the RESOURCE TYPE LIST screen.
PF3
Return to the main Administration menu.
PF4
Display the RESOURCE GROUP LIST screen.
PF5
Return to the RESOURCE DETAIL screen for the current resource.
PF11
Stop a selected path. You are prompted to confirm the stop request.
PF12
Exit from the Administration menu.
Message Turnaround Time Screen
Function
Displays a summary of message response times for all resource types.
To Display
From the RESOURCE TYPE LIST screen, press PF9.
Illustration of the Message Turnaround Time Screen
 
S6BADM36 S6H1DOBB MESSAGE TURNAROUND TIME BY TYPE 2006NOV29 15:01:42
DELTA
ALL PERCENTAGE OF TOTAL MESSAGES
128ms 256 512 1024 2048 4096 8192 >8192 TOTAL DELTA
ADA 0 0 0 0 0 0 0 0 0
API 0 0 0 0 0 0 0 0 0
DAT 0 0 0 0 0 0 0 0 0
DB2 0 0 0 0 0 0 0 0 0
HRN 0 0 0 0 0 0 0 0 0
IDM 19 15 6 10 19 15 6 10 48
IMS 0 0 0 0 0 0 0 0 0
 
 
 
 
 
 
 
 
 
 
 
ENTER-REFRESH PF2-ONLINE ONLY PF4-COMMON ONLY PF5-COMBINED PF9-TYPE LIST
NO MORE DATA TO BE DISPLAYED
 
Understanding Message Turnaround Times
The Message Turnaround Time By Type screen presents a matrix by resource type of the message turnaround times. Each column shows the percentage of messages for that resource that fall in the millisecond range indicated.
At the right, the two columns show the total number of messages for that resource and the change in number of messages since the last refresh. When the screen is refreshed, the time elapsed since the previous refresh could appear beside the word “DELTA” in the top right corner of the screen.
The data displayed is indicated by the value at the top left corner of the matrix:
Report Type
Pertains to data from
ONLINE
Online paths only, available to terminal-based transactions that tend to run at a higher priority.
COMMON
General access, used perhaps by batch or terminal-based transactions, excluding values from online-only paths.
ALL
Contains both the ONLINE and COMMON accumulated values. This is the default display.
Key Commands
Enter
Defined Schedule List Screen
Function
Use the DEFINED SCHEDULE LIST screen to view a list of existing schedules. From this screen you can select a schedule to edit, or define new schedules. You can display the resource details of a schedule and the resources associated with it. Normally for most resources, you should not need more than two or three schedules.
To Display
From the RESOURCE TYPE LIST screen or the RESOURCE DETAIL screen, press PF10.
Illustration of the Defined Schedule List Screen
 
S6BADM38 S6H1DOBB DEFINED SCHEDULE LIST 2006NOV29 15:02:58
 
COMMON SCHEDULE1
 
ENTER-SCHEDULE PF2-DETAIL PF4-TYPE LIST PF5-NEW SCHEDULE PF9-ASSOCIATES
DISPLAY FROM TOP OF DATA
 
Key Commands
Enter
Display the resource schedule for the selected schedule name.
PF1
Display help information about the current screen.
PF2
Display the RESOURCE DETAIL for the selected schedule.
PF3
Return to the main Administration menu.
PF4
Display the RESOURCE TYPE LIST screens.
PF5
Define a new schedule.
PF9
Display the resources associated with the selected schedule.
PF12
Exit from the Administration menu.
Resource Schedule Screen
Function
Use the RESOURCE SCHEDULE screen to view the schedule for a specific resource in the same format as it is presented on the RESOURCE DETAIL SCREEN. Create a copy of the schedule, create new schedules, or delete or update existing schedules from this screen.
To Display
•
From the DEFINED SCHEDULE LIST screen, select a schedule name and press ENTER.
•
From the USERS OF SCHEDULE screen, press PF2.
Illustration of the Resource Schedule Screen
 
S6BADM37 S6H1DOBB RESOURCE SCHEDULE COMMON 2006NOV29 15:04:40
 
ACT APPLICABLE DAYS EXCEPTION START ONLINE CONNECTIONS
MON TUE WED THR FRI SAT SUN DATE TIME ONLY MAX
Y Y Y Y Y Y Y 00:00 N 10
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
TARGET RESOURCE ___ ________
ENTER-DETAIL PF2-SCH IX PF4-COPY PF5-ASSOCIATE PF9-NEW PF10-UPDATE PF11-DELETE
DISPLAY FROM TOP OF DATA
 
Key Commands
Enter
Display the Resource Detail for the schedule.
PF1
Display help information about the current screen.
PF2
Display the DEFINED SCHEDULE LIST screen.
PF3
Return to the main Administration menu.
PF4
Copy the schedule to a new schedule.
PF5
Associate the schedule with a named resource.
PF9
Create a new schedule.
PF10
Update the displayed schedule.
PF11
Delete the displayed schedule when it is no longer needed.
PF12
Exit from the Administration menu.
How to Use Schedules
Resources are scheduled based on when they are available and how many of them are to be made available. Normally, each resource has only one or two schedule entries associated with it.
On the RESOURCE SCHEDULE screen, use the Target Resource field at the bottom of the screen when you copy a schedule or when associating a schedule with a resource group.
Using Exception Entries
When you define exception dates for a schedule, any exception records are automatically removed from the schedule file at the end of the day they expire. Dates are in the format CCYYMMMDDD, and an asterisk (*) indicates the current day. Exception entries always override the normal settings for the schedule. A typical schedule consists of one line showing the normal settings, and one or more lines for days when the normal settings do not apply.
To set up a new schedule:
1.
Select a resource group and press PF10 to see a list of available schedules.
The DEFINED SCHEDULE LIST appears.
2.
Press PF5 to display an empty resource schedule screen in input mode.
You can also press PF9 from the RESOURCE SCHEDULE SCREEN to display an empty resource schedule screen in input mode.
3.
Complete as many lines as you need and press PF10 to save the new schedule.
The first line of the new schedule should be the normal settings for that schedule. Subsequent lines define exceptions to or variations on this schedule.
4.
Press PF5 to associate the schedule with a resource group.
Illustration of the Resource Schedule Screen in Input Mode
 
S6BADM37 S6H1DOBB RESOURCE SCHEDULE COMMON 2006NOV29 15:04:40
 
ACT APPLICABLE DAYS EXCEPTION START ONLINE CONNECTIONS
MON TUE WED THR FRI SAT SUN DATE TIME ONLY MAX
Y Y Y Y Y Y Y _________ 00:00 N 10
_ _ _ _ _ _ _ _ _________ __:__ _ ___
_ _ _ _ _ _ _ _ _________ __:__ _ ___
_ _ _ _ _ _ _ _ _________ __:__ _ ___
_ _ _ _ _ _ _ _ _________ __:__ _ ___
_ _ _ _ _ _ _ _ _________ __:__ _ ___
_ _ _ _ _ _ _ _ _________ __:__ _ ___
_ _ _ _ _ _ _ _ _________ __:__ _ ___
_ _ _ _ _ _ _ _ _________ __:__ _ ___
_ _ _ _ _ _ _ _ _________ __:__ _ ___
_ _ _ _ _ _ _ _ _________ __:__ _ ___
_ _ _ _ _ _ _ _ _________ __:__ _ ___
_ _ _ _ _ _ _ _ _________ __:__ _ ___
_ _ _ _ _ _ _ _ _________ __:__ _ ___
_ _ _ _ _ _ _ _ _________ __:__ _ ___
_ _ _ _ _ _ _ _ _________ __:__ _ ___
 
TARGET RESOURCE ___ ________
ENTER-DETAIL PF2-SCH IX PF4-COPY PF5-ASSOCIATE PF9-NEW PF10-UPDATE PF11-DELETE
DISPLAY FROM TOP OF DATA
 
Users of Schedule Screen
Function
Use this screen to display a list of all resources that use a specified schedule.
To Display
From the DEFINED SCHEDULE LIST screen, press PF9.
Illustration of the Users of Schedule Screen
 
S6BADM39 S6H1DOBB USERS OF SCHEDULE COMMON 2006NOV29 15:07:13
 
ADAADAFSLV1 ADATESTC APIDEFAULT0 APIFILEGATE
APIGEORGETN APILESSMITH DATDATACOM0 DATDATACOM1
DATIMPSRVR DB2DB2PUT01 DB2DB2PUT04 DB2DB2SRVR
DB2DB2SRVR2 DB2DCOM2DB2 DB2RFSDB21 DB2RFSDB22
HINCASPER HINCASPER00 HINGEORGETN IDMRFSIDMS
IDMRFSIDMS1 IMSIMSDRA IMSRFSIMS IMSRFSIMS41
 
 
 
 
 
 
 
 
 
 
 
 
 
 
ENTER-DETAIL PF2-SCHEDULE PF4-TYPE LIST PF5-SCHEDULE INDEX
DISPLAY FROM TOP OF DATA
 
Key Commands
Enter
Display the RESOURCE DETAIL screen for the named schedule.
PF1
Display help information about the current screen.
PF2
Display the RESOURCE SCHEDULE for the named schedule.
PF3
Return to the main Administration menu.
PF4
Display the RESOURCE TYPE LIST screen.
PF5
Display the DEFINED SCHEDULE LIST screen.
PF12
Exit from the Administration menu.
 
Copyright © Cloud Software Group, Inc. All Rights Reserved
Copyright © Cloud Software Group, Inc. All Rights Reserved