![]() |
![]() |
![]() |
![]() |
![]() |
Note:
•
•
•
•
•
•
•
• Figure 4‑1 shows a sample domain menu listing the simple domain.Figure 4‑1 Sample Domain MenuTable 4‑1 describes the other Domain menu options.
Table 4‑1 The Other Domain Menu Options Creates a new domain. Use this option if the domain you want is not listed on the menu. After clicking on New, enter the pathname of the tuxconfig file for your domain. The GUI will then invoke the specified domain and add its name to the menu for future reference. Opens and displays the domain called simple in the tree view.To create a new domain, select Domain—>New from the menu bar to display the Create New Object window as shown in Figure 4‑2. (You can also select an existing domain in the tree and select Quick Menu—>New.)Figure 4‑2 Create New Object Window for a DomainAnywhere within the interface, fields that take an address in decimal format can also be specified in hexadecimal format when preceded by the characters 0x. Each character after the initial 0x is a number between 0 and 9 or a letter between A and F (not case sensitive). The hexadecimal format is useful for arbitrary binary network addresses such as IPX/SPX or TCP/IP. For example:0002 is the first part of a TCP/IP address and 091E is the port number 2334 translated into a hexadecimal number. The rest of the line contains hexadecimal numbers that are translations of the elements of the IP address 155.2.193.12: 155 becomes 9B, 2 becomes 02, and so on.A string of 0 to 30 characters. The default is NoName; this name is used only for display purposes in the GUI; it is not recorded as a value in the MIB.The name of the master machine, which is the node on which the master copy of the configuration file (TUXCONFIG) for your application is located. In a multiprocessor environment, this machine is also the one that should run the DBBL.Each logical machine identifier (LMID) contains a maximum of 30 characters. The name of the master machine (LMID1) must correspond to the local machine for inactive applications. For a single-machine application, you cannot specify a backup machine.A master machine name is required; specifying a backup machine is optional. For more information about using a Master and Backup machine to swap machines, refer to the section, Setting up Master and Backup Machines. If you specify a backup machine, it will be used as an alternate location (for the TUXCONFIG file and the DBBL) during process relocation and booting.The Application Configuration File field is equivalent to the MIB attribute TA_TUXCONFIG. TUXCONFIG is also the name of an environment variable that is used to compile the configuration file and activate the application. This internal entry is used by the Oracle Tuxedo system software after the application is activated.The local name for the address of the machine on which the bridge resides.The TCP port number or name at which the bridge will listen for incoming requests. The value of port_number can be either a number (between 0 and 65535) or a name. If port_number is a name, then it must be found in the network services database on your local machine.In the first format, the bridge finds an address for hostname using the local name resolution facilities (usually DNS). hostname must unambiguously resolve to the address of the machine on which the bridge resides.In the second format, the #.#.#.# is in dotted decimal format. Each # is a number from 0 to 255. This dotted decimal number represents the IP address of the local machine.A local machine on which a TDomain is being run is using TCP/IP addressing and is named backup.company.com, with address 155.2.193.18. The port number at which the TDomain should accept requests is 2334; this port number has been added to the network services database under the name bankapp-bridge. The address can be specified in any of the following five formats:This field specifies the network address used by the UNIX tlisten(1) process servicing the network on the node identified by the LMID.tmloadcf(1) prints an error if you do not enter a value in this field for most machines. If you do not enter a value in this field for the MASTER LMID, tmloadcf prints a warning, and tmadmin(1) will not be able to run in administrator mode on remote machines; it will be limited to read-only operations. This also means that the backup site will be unable to reboot the master site after failure./dev/provider_nameFor STARLAN this is /dev/starlan. In a multiprocessor configuration, the value takes the form /dev/starlanN, where N is the PE number.
•
• An integer greater than or equal to 0 (up to the limits imposed by your operating system). The default is the effective user ID of the person running the tmloadcf command. Specify 0 for Windows 2000 systems.An integer greater than or equal to 0 (up to the limits imposed by your operating system). The default is the effective group ID of the person running the tmloadcf command. Specify 0 for Windows 2000 systems.Any of the methods presented in the drop-down menu. The available possibilities are shown in Table 4‑2.
Table 4‑2 The Available Possibilities
Note: A string of 0 to 127 characters, one of the following values as specified in Security (TA_SECURITY): USER_AUTH, ACL, or MANDATORY_ACL.For upward compatibility, setting both APP_PW and AUTHSVC implies USER_AUTH. If you make those two specifications in Security (TA_SECURITY), service_name will be set, without notification, to USER_AUTH no matter what specification you make here.If you selected the ACL or MANDATORY_ACL security method in Security (TA_SECURITY), then service_name must be.AUTHSVC; this name will be used no matter what specification you make here.If you selected the USER_AUTH in Security (TA_SECURITY), then the default for service_name is AUTHSVC.A value in this field is not required if you selected no security (NONE) or APP_PW in Security (TA_SECURITY).A string of 0 to 8 characters. This field is not required if you selected no security (NONE) in Security (TA_SECURITY).Initial setting of the TP_COMMIT_CONTROL characteristic for all client and server processes in a Oracle Tuxedo application.For details about setting this characteristic, refer to the description of the tpscmt(3) function in the BEA Tuxedo ATMI C Function Reference manual.An integer in the range 0 to 32767. You do not need to include system administration processes, such as the BBL and the tmadmin command, when calculating this number. The default is 50.Maximum amount of string pool space to be accommodated in the bulletin board string pool table. Strings and carrays specified in the Max Routing Ranges (TA_MAXRFT) are stored in the string pool. (A carray, character array, is a typed buffer format in which the data is an array of uninterpreted bytes; it always requires an associated length value.) Additional space should be allocated to allow for run-time growth.Displays an integer in the range 1to 16384. The default is 16384. The maximum group identifier that can be defined is 1 less than max_aclgroups.An integer in the range 0 to 32767. The default is 0. This attribute value should be set to at least twice scan_unit (the value specified in the Basic Time Unit for Sanity Checks (TA_SCANUNIT)). The default is an integer number that is approximately equal to 300 divided by scan_unit.
Table 4‑3 The Available Choices Specifies that by default, notification messages are to be ignored by application clients. This is appropriate in applications that specify that only clients requesting notification at tpinit(3) time should receive unsolicited messagesOnce unsolicited messages are detected, they are made available to the application through the unsolicited message handling routine that has been defined by the application and identified by the UNIX tpsetunsol(3) function.) This default value can be overridden on a per-client basis using the appropriate tpinit(3) flag value.
Table 4‑4 The Available Choices Only the ACCSTATS option can be set or reset in an active application.
Table 4‑5 The Available Choices The default is FASTPATH.This field displays the maximum string pool space accommodated in the bulletin board string pool table. Strings and carrays specified in the Routing Table Ranges field (on the General tab for the Routing Tables class) are stored in the string pool. Additional space should be allocated to allow for run-time growth.For UNIX users: The value of Machine Name is the node name returned when you run the uname -a command on this machine.You have the option of assigning a logical name to a backup machine in case the first machine fails.TUXDIR is the absolute pathname of the directory (on this machine) in which the Oracle Tuxedo software resides.A string of 0 to 78 characters. This directory should not be on a remote filesystem. The default is $APPDIR/ULOG.
•
• An integer in the range 0 to 2147483647. The default is the value entered in the User ID field on the Security tab for the Application Resources (T_DOMAIN) class). Administrative commands such as tmboot(1), tmshutdown(1), and tmadmin(1) must be run, on this machine, by the owner of this ID. Application and administrative servers on this machine will be started as this user. IPC structures created for the bulletin board are associated with this ID.UNIX system group identifier for the Oracle Tuxedo application administrator on this machine. (The administrator for this machine is the owner of the user ID, as defined by the value you entered in the User ID (TA_UID).)
Table 4‑6 The Available Choices
Note:
Table 4‑7 The Available Choices An integer in the range 0 to 32767. You do not need to include system administration processes, such as the BBL, when calculating this number, but all application servers, clients, and TMS servers should be counted. If the application is activating workstation listeners on this site, then both the listeners and the potential number of workstation handlers that may be activated should be counted. The default is the value entered in the Max Accessors (TA_MAXACCESSORS) on the Limits 1 Tab tab for Application Resources (T_DOMAIN).An integer in the range 1 to 32767. The default is the value you specified in the Max Conversations (TA_MAXCONV) on the Limits 1 Tab tab for Application Resources (T_DOMAIN).This field is active only when the WorkStation feature is being used. The number specified here takes a portion of the total accesser slots specified with the value entered in the Max Accessors (TA_MAXACCESSORS). The appropriate setting of this parameter helps to conserve IPC resources since Workstation client access to the system is multiplexed through a Oracle Tuxedo supplied surrogate, the workstation handler.The value of this field must be less than the value of the Max Accessors (TA_MAXACCESSORS); setting this field to a greater value is an error.An integer in the range 1 to 32767. The default is the value you specified in the Max Global Transactions (MAXGTT) on the Limits 2 Tab tab for Application Resources (T_DOMAIN).An integer greater than or equal to 0. The default is 0. A value of 0 indicates that the spin count built into the delivered binary should be used. If set, this parameter causes the TMSPINCOUNT environment variable to be ignored. This behavior varies from platform to platform.Default values are built into the Oracle Tuxedo binaries on each machine. These defaults can be overridden at run time for tuning purposes using this attribute. The spin count can be reset to the default built-in value for the site by resetting this attribute value to 0. The system uses the TMSPINCOUNT environment variable if the value is not set here or in the ubbconfig file.The values of remote and local can be either nonnegative numeric values or the string MAXLONG, which is dynamically translated to the maximum long setting for the machine. The default is MAXLONG,MAXLONG.Number of entries in the cache used for ACL entries when TA_SECURITY is set to ACL or MANDATORY_ACL. The appropriate setting of this parameter helps to conserve shared memory resources and yet reduce the number of disk access needed to perform ACL checking.If more than one DTP transaction log (or TLOG) exists on the same TLOG device (TLOG Device (TA_TLOGDEVICE)), they must have unique names. The name you specify in this field must not match any other name in any other table in the configuration in which the TLOG table is created.You can specify the same value that you entered (for this machine) in the Tuxedo Root Directory (Full Path) (TA_TUXDIR) on the General tab for the Machines class. If no TLOG device exists for a given machine, the associated LMID cannot be used by server groups that participate in distributed transactions.Number of tpconnect(3) operations performed from this machine since Oracle Tuxedo was booted (or since you reset this field).Number of tpdequeue(3) operations performed from this machine since Oracle Tuxedo was booted (or since you reset this field).Number of tpenqueue(3) operations performed from this machine since Oracle Tuxedo was booted (or since you reset this field).Number of tppost(3) operations performed from this machine since Oracle Tuxedo was booted (or since you reset this field).Number of tpacall(3) or tpcall(3) operations performed from this machine since Oracle Tuxedo was booted (or since you reset this field).The number of transactions initiated (with tpbegin(3)) from this machine since Oracle Tuxedo was booted (or since you reset this field).The number of transactions aborted (tpabort(3)) from this machine since Oracle Tuxedo was booted (or since you reset this field).The number of transactions committed (with tpcommit(3)) from this machine since Oracle Tuxedo was booted (or since you reset this field).
Note: If the T_DOMAIN:TA_LDBAL attribute is N or the T_DOMAIN:TA_MODEL attribute is MP, then an FML32 NULL value is returned (0).The number of tpsubscribe(3) operations performed from this machine since Oracle Tuxedo was booted (or since you reset this field).This field displays the size (in pages) of the offset between the beginning of the device and the beginning of the Oracle Tuxedo filesystem that contains the TUXCONFIG file for this machine. (If the offset is greater than 0, then it is placed in the environment of all servers booted on a machine.)
Table 4‑8 Machine Role For more information about using a Master and Backup machine to swap machines, refer to the section, Setting up Master and Backup Machines.This field displays the transaction identifier as returned from tx_info(3) mapped to a string representation. The data in this field should not be interpreted directly by the user except for equality comparison.This field displays the transaction identifier as returned from tpsuspend(3) mapped to a string representation. The data in this field should not be interpreted directly by the user except for equality comparison.
•
•
•
• This field displays the index of the first group specific attribute values (TA_GRPNO and TA_GSTATE) corresponding to this object.This field displays time left, in seconds, before the transaction will time out on the retrieval site. This attribute value is returned only when the transaction state (TA_STATE) is ACTIVE.
•
•
•
•
•
•
• The group name cannot contain an asterisk, a comma, or a colon. The group name must be unique among all group names in the Groups class and all values entered in the Logical Machine Name (TA_LMID) for objects in the Machines class.This name is used as the value of the SRVGRP parameter in two places: in the Servers tabs (to identify a server as a part of this group), and the Services tab (to identify an instance of a service with its occurrences in the group).Primary logical machine identifier for this server group (LMID1) and optional secondary logical machine identifier (LMID2).
•
•
•
• Name of the transaction manager server a.out file associated with this group. This file is executed by tmboot when you boot this server group.A string of 0 to 78 characters. The value TMS is reserved to indicate use of the null XA interface. The default is no entry, that is, the null string.You must enter a value in this field for any group that includes servers that will participate in distributed transactions. (A distributed transaction is a transaction executed across multiple resource managers, and possibly machines, that are started with tpbegin(3), and ended with a tpcommit(3) or tpabort(3) call.)If you specify a nonempty value other than TMS, then you must also specify a TLOG device for the one or more machines associated with the primary and secondary logical machines for this group.Number of transaction manager servers to be started for the associated group, if you have specified a value for the TMS Name (TA_TMSNAME).tmscount is an integer in the range 2 to 10. The default is 3. If you have not specified a value for the TMS Name (TA_TMSNAME), then this field is ignored.
Table 4‑9 Subfield TUXEDO/D for Oracle Tuxedo System/D databases.
TUXEDO/SQL for Oracle Tuxedo System/SQL databases.
TUXEDO/QM for Oracle Tuxedo /Q databases.
Note: The /D and /SQL databases are only used by the sample applications provided with Oracle Tuxedo (for example, bankapp) and are not supported for use with the application code.The Open Information format depends on the requirements of the resource manager vendor. The string required by the vendor must be prefixed by rm_name, which is the published name of the vendor’s transaction (XA) interface, followed immediately by a colon.This field is ignored if you have not specified a name in the TMS Name (TA_TMSNAME) or if you have specified it as TMS. If you have specified a value for the TMS name but you have not done so for the Open Information field, it means that a resource manager exists for this group but does not require any information for executing an open operation.
Table 4‑10 Subfield On Windows 2000 and NetWare machine, semicolons are used instead of the colons after fsconfig and dbname.The Close Information format depends on the requirements of the resource manager vendor. The string required by the vendor must be prefixed by rm_name, which is the published name of the vendor’s transaction (XA) interface, followed immediately by a colon.This field is ignored if you have not specified a name in the TMS Name (TA_TMSNAME) or if you have specified it as TMS. If you have specified a value for the TMS name but you have not done so for the Close Information field, it means that a resource manager exists for this group but does not require any information for executing a close operation.If multiple instances of servers are desired, do not use consecutive numbers. Instead, leave enough room for the system to assign additional server IDs up to the number specified in the Max Servers Activated (TA_MAX) field.A string of 1 to 78 characters. The server identified in this field will run on the machines specified in the Logical Machine Name, Backup (TA_LMID) for the Groups class to which this server belongs. If you specify a relative pathname, a search will be done for the executable file in the following order:
2.
3.
4.
5. The pathname specified as the first PATH= entry in the machine environment file (if one exists).
• This field displays the name of the file that defines the environment in which the a.out file is executed by tmboot.
•
•
•
• An integer in the range 0 to 2147483647. The default is 86400 (the number of seconds in 24 hours. The Automatic Restart (TA_RESTART) must be set to Yes. The equation used to calculate the grace period is:where MAXGEN is set in the Max Generations (TA_MAXGEN). As soon as one grace period ends, the next one begins. Thus setting the value of this field to 0 removes all limitations. The server can then be restarted an unlimited number of times.If you have specified a value in the Request Queue (TA_RQADDR) and the Min Servers Activated value is greater than 1, then an MSSQ set is formed.The maximum number of times this server can be started within the period specified in the Grace Period (TA_GRACE).
Table 4‑11 The Available Choices Servers sharing a request queue (that is, equal values in the Request Queue (TA_RQADDR) on the System Parameters tab) should have equal values for this attribute. If they do not, then the first server activated will establish the run-time value associated with all servers on the queue.The default is No. You must specify Yes in this field if server migration has been specified for this server group in the following manner: You selected MIGRATE in the Options (TA_OPTIONS) of the General tab for Configuring Domain Resources (T_DOMAIN Class), and you designated an alternate site in the Logical Machine Name, Backup (TA_LMID) of the General tab in the Groups class.Servers sharing a request queue (that is, equal values in the Request Queue (TA_RQADDR) on the System Parameters tab) should have equal values for this attribute. If they do not, then the first server activated will establish the run-time value associated with all servers on the queue.A string of 0 to 30 characters. The default is GRPNO.SRVID, where:
• GRPNO is the value specified in the Group Number (TA_GRPNO) of the General tab for the Groups class.
• SRVID is the value specified in the Server ID (TA_SRVID) of the General tab for the Servers class).Multiple Server, Single Queue (MSSQ) sets are established by using the same symbolic name for more than one server or by specifying the Min Servers Activated (TA_MIN) to be greater than 1. All members of an MSSQ set must offer an identical set of services and must be in the same server group.The default is Yes.If you specify Yes, the server is a member of a Multiple Server, Single Queue (MSSQ) set and contains services programmed to receive reply messages. This ensures that the individual reply queue is created for this server. If this is not done, the reply is sent to the request queue shared by all servers of the MSSQ set, and there is no way of assuring that it will be picked up by the server waiting for it. It should be standard practice to specify Yes for all member servers of an MSSQ set if replies are anticipated. Servers in an MSSQ set must have identical service offerings, so it is reasonable to expect that if one server in the set expects replies, any server in the set may do likewise.If you specify No, only one server uses the request queue. Replies are then picked up from the request queue without difficulty.A four-digit octal number (of which the first character is always 0) in the range 0001 to 0777 that represents the UNIX system read and write permissions (as defined by the UNIX system) that you set for the request queue for this server. For example, the value 0666 signifies that permission to read and write (6) has been given to the designated user, the designated group, and any other user. The default is 0666. If you do not enter a value in this field, the permissions of the bulletin board, as specified by the Permission (TA_PERM) on the Security tab for the Application Resources class (T_DOMAIN), are implemented.A four-digit octal number, in the range 0001 to 0777, as described under Request Queue Perm (TA_RQPERM). The default is the value you entered for this field in the Permission (TA_PERM) on the Security tab for the Application Resources class (T_DOMAIN).This field displays the UNIX system message queue identifier for the server’s reply queue. If a separate reply queue is not allocated (the Reply Queue (TA_REPLYQ) specified No), then this attribute will be the same as the value of the Request Message Queue ID (TA_RQID).This field displays the UNIX system message queue identifier for the server’s request queue. If a separate queue is not allocated (the Reply Queue (TA_REPLYQ) specified No), then this attribute will be the same as the value of the Reply Message Queue ID (TA_RPID).This field causes the number of conversations initiated through this server by tpconnect(3) since Oracle Tuxedo was booted (or you reset the counter) to be displayed in the Number of Conversations (TA_NUMCONV).This field displays the number of tpconnect(3) conversations initiated by this server since Oracle Tuxedo was booted (or you reset the counter).This field displays the number of tpdequeue(3) operations initiated by this server since Oracle Tuxedo was booted (or since you reset the counter).This field displays the number of tpenqueue(3) operations performed from this machine since Oracle Tuxedo was booted (or since you reset the counter).This field displays the number of tppost(3) operations performed from this machine since Oracle Tuxedo was booted (or you reset the counter).This field displays the number of tpacall(3) or tpcall(3) operations performed from this machine since Oracle Tuxedo was booted (or since you reset the counter).An integer greater than or equal to 0, representing the seconds since 00:00:00 UTC, January 1, 1970, as returned by the time(2) system call on the machine identified in the Current Logical Machine Name (TA_LMID). This value shows when the server was last started or restarted.An integer greater than or equal to 0, representing the seconds since 00:00:00 UTC, January 1, 1970, as returned by the time(2) system call on the machine identified in the Current Logical Machine Name (TA_LMID). This value shows when the server was first started.Restarts of the server do not reset this value; however, if the value entered in the Max Generations (TA_MAXGEN) on the Args tab and the amount of time specified in the Grace Period (TA_GRACE) on the Args tab has expired, the value in this field (Starting Time) will be reset to the time of the restart.An integer greater than or equal to 0, the number of subscriptions made by this server with tpsubscribe(3) since Oracle Tuxedo was booted (or you reset the counter).This field displays the number of transactions begun by this server since its last start or restart.This field displays the setting of the TP_COMMIT_CONTROL characteristic for this server. For details about setting this characteristic, refer to the description of the tpscmt(3) function in the BEA Tuxedo ATMI C Function Reference manual, and the Default Commit Control (TA_CMTRET) in the File Formats, Data Descriptions, MIBs, and System Processes manual.Number of tpconnect(3) conversations initiated by this server that are still active.This field displays the number of requests that have been initiated by this server with tpcall(3) that are still active.This field displays the current time (in seconds) since 00:00:00 UTC, January 1, 1970, as returned by the time(2) system call on the machine identified in the Current Logical Machine Name (TA_LMID). This attribute can be used to compute elapsed time from the Starting Time (TA_TIMESTART) and Restarting Time (TA_TIMERESTART) attribute values.This field displays the server group number (as shown in the Group Number (TA_GRPNO)) of the last service request made or conversation initiated from this server outward.
•
•
•
•
• No subtype can be specified for the FML type. Subtypes are required for VIEW, X_C_TYPE, and X_COMMON. (The wildcard character, *, is not allowed.)This field is assumed to be an FML buffer or view field name that is identified in an FML field table (using the FLDTBLDIR and FIELDTBLS environment variables) or an FML view table (using the VIEWDIR and VIEWFILES environment variables), respectively. This information is used to get the associated field value for data-dependent routing during the sending of a message.
Table 4‑12 Valid Values The values MIN and MAX can be used to indicate the minimum and maximum values for the data type of the associated field on the machine. The asterisk, a wildcard character, is a metacharacter that, when used in the position of a range, indicates any values not covered by any previous ranges. Only one wildcard range is allowed per entry and it should be listed last, since ranges following it will be ignored.String range values for string, carray, and character field types must be delimited by single quotes and cannot be preceded by a sign. (To embed a single quotation mark in a character string value, precede it with two backslashes.) Short and long integer values are a string of digits, optionally preceded by a plus or minus sign. Floating point numbers are of the window accepted by the C compiler or atof(3):
• In the following example, entries in the range 60,000 to 69,999 are routed to BANKB2, those in the range 70,000 to 79,999 to BANKB3, and the rest to BANKB4.This field displays the name of the routing criteria table specified in the Routing Table Name (TA_ROUTINGNAME) of the Create New Object window.rctable is a string of 1 to 15 characters.If multiple entries exist for the same service name but with different SRVGRP (see Group Name (TA_SRVGRP)) parameters, the Routing Table Name parameter must be the same for all of these entries.
• FML (for FML buffers)
•
•
• X_COMMON (for FML views)
• STRING (for null-terminated character arrays)
• CARRAY or X_OCTET (for a character array that is neither encoded nor decoded during transmission)
• Of these types, only VIEW, X_C_TYPE, and X_COMMON have subtypes. A view subtype gives the name of the particular view expected by the service. Application types and subtypes can also be added (see the UNIX manpage on tuxtypes(5)). For a type that has subtypes, an asterisk can be specified for the subtype to indicate that the service accepts all subtypes for the associated type.A single service can interpret only a fixed number of buffer types, namely those found in its buffer type switch (see the UNIX manpage on tuxtypes(5)). If this parameter is set to ALL, that service will accept all buffer types found in its buffer type switch. Leaving this field blank is equivalent to setting it to ALL. If multiple entries exist for the same service name but with different SRVGRP parameters, this parameter must be the same for all of these entries.The default is ALL.
•
• Service loads are used for load balancing purposes; that is, queues with higher enqueued workloads are less likely to be chosen for a new request. Service loads have meaning only if the value of the Load Balancing Enabled (TA_LDBAL) for the domain class is Yes.(Transactions are started automatically when a request not in transaction mode is received and the value for the service (in the Auto Transaction Mode (TA_AUTOTRAN) is Yes.
Table 4‑13 Valid Values A string of 1 to 127 characters. The default is the value you entered in the Service Name (TA_SERVICENAME).On a SET request, this server must be able to map the function name to a function using its symbol table to successfully advertise the service. In some situations (for example, direct calls to tpadvertise(3) by the server), the function name for an active service object will not be known and a question mark will be returned as the attribute value.
•
• A string of 2 to 64 characters. The default is the pathname entered in the Full Path to Device (TA_CFGDEVICE).The offset between the beginning of this device and the point at which the space on this device is reserved for use by the Oracle Tuxedo VTOC specified by the value you entered in the Full Path to Device (TA_CFGDEVICE).The offset at which space on this device begins for use within the Oracle Tuxedo VTOC specified in the Device Name (Full Path) (TA_DEVICE) on this tab.A string of 2 to 64 characters. The default is the pathname entered in the Full Path to Device (TA_CFGDEVICE).This field displays the client name associated with the client at tpinit(3) by the cltname element of the TPINIT structure.This field displays the username associated with the client at tpinit(3) time by the usrname element of the TPINIT structure.This field displays the Workstation client. If this attribute is set to Yes, then the indicated client is logged in to the application from a remote workstation.This field displays the workstation handler. If this attribute is set to Yes, then the indicated client is a workstation handler process.This field displays the network address of a Workstation client. Network addresses with unprintable characters are converted to the Hexadecimal Addresses format. If the address is a TCP/IP address, then it is returned in the dotted decimal format with appended port number, as described under Network Address (TA_NADDR).
•
• This field displays the server group with which the client is associated. This information is set by the grpname element of the TPINIT structure at tpinit(3) time.This field displays the time (specified in seconds) since the client joined the application (as reported by the time(2) system call on the machine identified in the Logical Machine Name, Backup (TA_LMID).This field displays the approximate amount of time (in seconds) since this client last interacted with the system through an ATMI call. This value is accurate to within the value the scan units, as described in Basic Time Unit for Sanity Checks (TA_SCANUNIT).
• Number of tpconnect(3) conversations initiated by this client since Oracle Tuxedo was booted.Number of tpconnect(3) conversations initiated by this client that are still active.Number of tpdequeue(3) operations initiated by this client since Oracle Tuxedo was booted.Number of tpenqueue(3) operations performed from this client since Oracle Tuxedo was booted (or since you reset the counter).Number of tppost(3) operations performed from this client since Oracle Tuxedo was booted.This field displays the number of tpacall(3) or tpcall(3) operations performed from this client since Oracle Tuxedo was booted.An integer greater than or equal to 0, the number of subscriptions made by this server with tpsubscribe(3) since Oracle Tuxedo was booted (or you reset the counter).This field displays the number of transactions begun by this client since its last start or restart.This field displays the source logical machine identifier (LMID1) and optionally, the destination logical machine identifier (LMID2) for network connection.
•
•