Refer to “Administering the SNA Components” in the
Oracle Tuxedo Mainframe Adapter for SNA CRM Administration Guide for information about the following CRM administration commands:
addumap -d <local domain ID> -R <
remote domain ID> -p <
local principal name> -u <
remote username>
addumap can only be executed as a subcommand of
dmadmin(1). The purpose of this page is to describe options for the subcommand and to show examples.
The dmadmin addumap subcommand exits with a return code of 0 upon successful completion.
addusr -d <local domain ID> -R <
remote domain ID> -u <
remote username>
[-w ]
addusr can only be executed as a subcommand of
dmadmin(1). The purpose of this page is to describe options for the subcommand and to show an example.
The dmadmin addusr subcommand exits with a return code of 0 upon successful completion.
addusr -d tux -R cics -u CICSUSR /*adds remote user CICSUSR
to
cics domain’s user and
password file. The
administrator is prompted for
a password*/
delumap -d <local domain ID> -R <
remote domain ID> -p <
local principal name> -u <
remote username>
delumap can only be executed as a subcommand of
dmadmin(1). The purpose of this page is to describe options for the subcommand and to show examples.
The dmadmin delumap subcommand exits with a return code of 0 upon successful completion.
delusr -d <local domain> -R <
remote domain> -u <
remote username>
delusr can only be executed as a subcommand of
dmadmin(1). The purpose of this page is to describe options for the subcommand and to show an example.
The dmadmin delusr subcommand exits with a return code of 0 upon successful completion.
DMADM SRVGRP = “identifier”
SRVID = “
number”
REPLYQ = “
N”
The /DOMAIN administrative server (DMADM) is a Tuxedo-supplied server that provides run-time access to the binary domain configuration file (
BDMCONFIG file). When
DMADM is booted, the
BDMCONFIG environment variable should be set to the pathname of the file containing the binary version of the
DMCONFIG file.
DMADM is described in the SERVERS section of the
UBBCONFIG file as a server running within a group, e.g.,
DMADMGRP. There should be only one instance of the
DMADM running in this group and it must not have a reply queue (
REPLYQ must be set to “N”).
DMADM is supported as a Tuxedo-supplied server on UNIX System and Windows NT operating systems.
dmadmin(1),
tmboot(1),
dmconfig(5),
GWADM(5),
servopts(5),
ubbconfig(5)
The dmadmin interactive command interpreter is used for the administration of domain gateway groups defined for a particular Tuxedo System/T application. The interpreter can operate in two modes: administration mode and configuration mode.
The dmadmin command interpreter enters
administration mode when called with no parameters. This is the default. In this mode,
dmadmin can be run on any active node (excluding workstations) within an active application. Application administrators can use this mode to obtain or change parameters on any active domain gateway group. Application administrators may also use this mode to create, destroy, or re-initialize the
DMTLOG for a particular local domain. In this case, the domain gateway group associated with that local domain must not be active, and
dmadmin must be run on the machine assigned to the corresponding gateway group.
The dmadmin command interpreter enters
configuration mode when it is invoked with the
-c option or when the
config subcommand is invoked. Application administrators can use this mode to update or add new configuration information to the binary version of the domain configuration file (
BDMCONFIG).
The dmadmin command interpreter requires the use of the
DOMAIN administrative server (
DMADM) for the administration of the
BDMCONFIG file and the gateway administrative server (
GWADM) for the re-configuration of active
DOMAIN gateway groups (there is one
GWADM per gateway group).
Once dmadmin has been invoked, commands may be entered at the prompt (“>”) according to the following syntax:
Output from dmadmin commands is paginated according to the pagination command in use (see the paginate subcommand below).
If the default command is entered with no arguments, the current default values are printed.
Destroy the domain transaction log for the named local domain on the current machine (that is, the machine where dmadmin is running). An error is returned if a
DMTLOG is not defined for this local domain, if the local domain is active, or if outstanding transaction records exist in the log. The term outstanding transactions means that a global transaction has been committed but an end-of-transaction has not yet been written. This command prompts for confirmation before proceeding unless the
-y option is specified.
dsdmlog is not supported for SNA-type gateways.
Print help messages. If command is specified, the abbreviation, arguments, and description for that command are printed. Omitting all arguments causes the syntax of all commands to be displayed.
Activate (on), deactivate (
off), or reset (
reset) statistics gathering for the named local domain. If no option is given, then the current setting will be toggled between the values
on and
off, and the new setting will be printed. The initial setting is
off.
The dmadmin command enters configuration mode when executed with the
-c option or when the
config subcommand is used. In this mode,
dmadmin allows run-time updates to the
BDMCONFIG file.
dmadmin manages a buffer that contains input field values to be added or retrieved, and displays output field values and status after each operation completes. The user can update the input buffer using any available text editor.
The dmadmin command first prompts for the desired section followed by a prompt for the desired operation.
dmadmin then prompts for the desired operation.
dmadmin then prompts whether or not to edit the input buffer.
Entering a value of y will put the input buffer into a temporary file and execute the text editor. The environment variable
EDITOR is used to determine which editor to be used; the default is “
ed”. The input format is in field name/field value pairs and is described in the
CONFIGURATION INPUT FORMAT section below. The field names associated with each
DMCONFIG section are listed in tables in the subsections below. The semantics of the fields and associated ranges, default values, restrictions, etc., are described in
dmconfig(5). In most cases, the field name is the same as the
KEYWORD in the
DMCONFIG file, prefixed with “TA_”. When the user completes editing the input buffer,
dmadmin reads it. If more than one line occurs for a particular field name, the first occurrence is used and other occurrences are ignored. If any errors occur, a syntax error will be printed and dmadmin prompts whether or not to correct the problem.
Finally, dmadmin asks if the operation should be done.
When “QUIT” is selected,
dmadmin prompts for authorization to create a backup ASCII version of the configuration:
On success, dmadmin indicates that a backup was created, otherwise an error is printed.
If the domain identifier (TA_LDOM) is a local domain identifier, then the
TA_NWADDR field can be updated if the gateway group representing that local domain is not running.
If the domain identifier (TA_LDOM) is a local domain identifier, then the other fields in this table can be updated if the gateway group representing that local domain is not running.
The TA_LPWD and
TA_RPWD show the existence of a defined password for the local and/or the remote domain. Passwords are not displayed. If an
UPDATE operation is selected, the value of the corresponding field must be set to
U. The program will then prompt with echo turned off for the corresponding passwords.
dmadmin fails if it cannot allocate an FML typed buffer, if it cannot determine the
/etc/passwd entry for the user, or if it cannot reset the environment variables
FIELDTBLS or
FLDTBLDIR.
The return value printed by dmadmin after each operation completes indicates the status of the requested operation. There are three classes of return values.
The calling process specified an ADD,
UPDATE, or
DELETE operation but it is not running as the System/T administrator. Update operations must be run by the administrator (that is, the user specified in the
UID attribute of the RESOURCES section of the
TUXCONFIG file).
When using dmunloadcf to print entries in the configuration, optional field values are not printed if they are not set (for strings) or 0 (for integers). These fields will always appear in the output buffer when using
dmadmin. In this way, it makes it easier for the administrator to retrieve an entry and update a field that previously was not set. The entry will have the field name followed by a tab but no field value.
If dmadmin is run with the application administrator’s
UID, it assumes a trusted user and Security is bypassed. If
dmadmin is run with another user ID, and if the security option is enabled in the TUXCONFIG file, then the corresponding application password is required to start the
dmadmin program. If standard input is a terminal, then
dmadmin will prompt the user for the password with echo turned off. If standard input is not a terminal, the password is retrieved from the environment variable,
APP_PW. If this environment variable is not specified and an application password is required, then
dmadmin will fail to start.
The dmadmin command resets the
FIELDTBLS and
FLDTBLDIR environment variables to pick up the ${TUXDIR}/udataobj/dmadmin field table. Hence, the
TUXDIR environment variable should be set correctly.
The TUXCONFIG environment variable should be set to the pathname of the Tuxedo System/T configuration file.
If the dmadmin command is entered before the system has been booted, the following message is displayed:
dmadmin then prompts for the corresponding commands.
dmadmin for /SNA must be installed on Tuxedo System/T R6.5. Other nodes in the same domain with an R6.5 gateway may be Tuxedo System/T R4.2.2 or later.
dmloadcf(1),
tmadmin(1),
dmconfig(5),
DMADM(5),
addusr(5),
delusr(5)
dmconfig is the ASCII version of a Tuxedo System/Domain domain configuration file; it is also referred to by its environmental variable name:
DMCONFIG. The
dmconfig file is parsed and loaded into a binary version by the
dmloadcf utility. The binary configuration file, called the
BDMCONFIG file, contains information used by domain gateways to initialize the context required for communications with other domains.
dmadmin uses the binary file (or a copy of it) in its monitoring activity. There will be one
BDMCONFIG file for each Tuxedo System/Domain application that uses the /Domain feature.
A DMCONFIG file, and its binary
BDMCONFIG counterpart, are analogous to the
UBBCONFIG and
TUXCONFIG files of a non-/Domain System/T application. The
DMCONFIG file extends the definition of a non-/Domain System/T application so that the application becomes a domain.
A Tuxedo System/Domain Application is defined as the environment described in a single
TUXCONFIG file. A System/T Application can communicate with another System/T Application or with another TP Application via a domain gateway group. In “Tuxedo System/Domain” terms, an
Application is the same as a
TP Domain.
A Gateway Group is a collection of domain gateway processes that provide communication services with a specific type of TP Domain.
A Domain Gateway is a Tuxedo System/Domain process that relays requests and replies to another TP Domain.
A Local Domain characterizes a part of the application (set or subset of services) that is made available to other domains. A Local Domain is always represented by a Domain Gateway Group, and both terms are used as synonyms.
A Remote Domain is a remote application that is accessed through a Gateway Group. The remote application may be another Tuxedo System/Domain application or an application running under another TP system.
A Remote Service is a service provided by a remote domain that is made available to the local application through a Gateway Group.
A Local Service is a service of a local domain that is made available to remote domains through a Gateway Group.
•
|
The file is made up of eight possible specification sections. Lines beginning with an asterisk (∗) indicate the beginning of a specification section. Each such line contains the name of the section immediately following the ∗. Allowable section names are: DM_LOCAL_DOMAINS, DM_REMOTE_DOMAINS, DM_SNACRM, DM_SNASTACKS, DM_SNALINKS, DM_LOCAL_SERVICES, DM_REMOTE_SERVICES, DM_ROUTING, DM_ACCESS_CONTROL,DM_OSITP, and DM_TDOMAIN. The DM_LOCAL_DOMAINS section must precede the DM_REMOTE_DOMAINS /.
|
•
|
Parameters are generally specified by: KEYWORD = value. This sets KEYWORD to value. Valid keywords are described below within each section. KEYWORDs are reserved; they cannot be used as values unless they are quoted.
|
Lines beginning with the reserved word, DEFAULT:, contain parameter specifications that apply to any lines that follow them in the section in which they appear. Default specifications can be used in all sections. They can appear more than once in the same section. The format for these lines is:
DEFAULT: [ KEYWORD1 =
value1 [
KEYWORD2 =
value2 [...]]]
The values set on this line remain in effect until reset by another DEFAULT: line, or until the end of the section is reached. These values can also be overridden on non-
DEFAULT: lines by placing the optional parameter setting on the line. If on a non-
DEFAULT: line, the parameter setting is valid for that line only; lines that follow revert to the default setting. If
DEFAULT: appears on a line by itself, all previously set defaults are cleared and their values revert to the system defaults.
If a value is numeric, standard C notation is used to denote the base (that is, 0x prefix for base 16 (hexadecimal), 0 prefix for base 8 (octal), and no prefix for base 10 (decimal)). The range of values acceptable for a numeric parameter are given under the description of that parameter.
If a value is an identifier, standard C rules are used. An
identifier must start with an alphabetic character or underscore and contain only alphanumeric characters or underscores. The maximum allowable length of an identifier is 30 (not including the terminating null). An identifier cannot be the same as any
KEYWORD.
•
|
“#” introduces a comment. A newline ends a comment.
|
where string_value can be any value. The field is not checked by the software; it is provided simply as a place where the customer can enter a string that may have some documentation value to the application.
LDOM required parameters [optional parameters]
where LDOM is an
identifier value used to name each local domain.
LDOM must be unique within a particular configuration. As you will see in the description of the DM_LOCAL_SERVICES section,
LDOM is the identifier that connects local services with a particular gateway group.
Is used for grouping local domain into classes. TYPE can be set to one of the following values:
TDOMAIN,
OSITP or
SNAX. The
TDOMAIN value indicates that this local domain can only communicate with another Tuxedo System/Domain. The
OSITP value indicates that this local domain communicates with another TP Domain via the OSI-TP protocol. The
SNA value indicates that this local domain communicates with an MVS/CICS region via the LU6.2 protocol. Domain types must be defined in the
$TUXDIR/udataobj/DMTYPE file.
Is used to identify the local domain. DOMAINID must be unique across both local and remote domains. The value of
string can be a sequence of characters (for example, "BA.CENTRAL01"), or a sequence of hexadecimal digits preceded by “0x” (for example, “0x0002FF98C0000B9D6”).
DOMAINID must be 32 octets or fewer in length. If the value is a string, it must be 32 characters or fewer (counting the trailing null).
Specifies the Tuxedo file system that contains the Domain transaction log (DMTLOG) for this machine. The
DMTLOG is stored as a Tuxedo System VTOC table on the device. If this parameter is not specified (and it should not be specified if
TYPE=SNADOM), the domain gateway group is not allowed to process requests in transaction mode. Local domains running on the same machine can share the same
DMTLOGDEV file system, but each local domain must have its own log (a table in the
DMTLOGDEV) named as specified by the
DMTLOGNAME keyword (see below).
Specifies the maximum wait time allowed for a blocking call. The value sets a multiplier of the SCANUNIT parameters specified in the
TUXCONFIG file. The value
SCANUNIT * BLOCKTIME must be greater than or equal to
SCANUNIT and less than 32,768 seconds. If this parameter is not specified, the default value is set to the value of the
BLOCKTIME parameter specified in the
TUXCONFIG file. A time-out always implies a failure of the affected request. Notice that the time-out specified for transactions in the
TUXCONFIG will always be used when the request is issued within a transaction.
•
|
When the DM_LOCAL_DOMAINS Security parameter is set to NONE or APP_PW, no action is taken by the Oracle Tuxedo Mainframe Adapter for SNA gateway with regard to security.
|
•
|
However, when the UBBCONFIG file Security parameter is set to APP_PW, the application password is validated by an AUTHSVC when clients join the application. The AUTHSVC is provided by the user application.
|
•
|
UBBCONFIG file Security parameter must be set to one of: USER_AUTH, ACL, or MANDATORY_ACL
|
•
|
DMCONFIG file DM_LOCAL_DOMAINS section Security parameter must be set to DM_USER_PW
|
•
|
DM_SNALINKS Security parameter must be set to IDENTIFY or VERIFY
|
•
|
UBBCONFIG file Security parameter must be set to one o: USER_AUTH, ACL, or MANDATORY_ACL
|
•
|
DMCONFIG file DM_LOCAL_DOMAINS section Security parameter must be set to DM_USER_PW
|
•
|
DM_SNALINKS Security parameter must be set to IDENTIFY or VERIFY
|
Therefore, if the ATTACHSEC level for the connection definition in the host system is
Identify or
Verify, the
DMCONFIG SECURITY parameter must be set to
DM_USER_PW so that a userid and a password are sent on the conversation start-up requests.
RDOM required parameters
[optional parameters]
where RDOM is an
identifier value used to identify each remote domain known to this configuration.
RDOM must be unique within the configuration.
Is used for grouping remote domain into classes. TYPE can be set to one of the following values:
TDOMAIN,
OSITP or
SNAX. The
TDOMAIN value indicates that this remote domain can only communicate with another Tuxedo System/Domain. The
OSITP value indicates that this remote domain communicates with another TP domain via the OSI-TP protocol. The
SNAX value indicates that this remote domain communicates with an MVS/CICS region via the LU6.2 protocol.
Is used to identify a remote domain. DOMAINID must be 32 octets or fewer in length. If the value is a string, it must be 32 characters or fewer (counting the trailing null).
DOMAINID must be unique across remote domains. The value of
string can be a sequence of characters or a sequence of hexadecimal digits preceded by “
0x”.
DOM required parameters [optional parameters]
where DOM is an
identifier value used to identify either a local domain (
LDOM) or a remote domain (
RDOM) in the DM_LOCAL_DOMAINS section or in the DM_REMOTE_DOMAINS section. The
DOM identifier must match a previously defined
LDOM in the DM_LOCAL_DOMAINS sections or
RDOM in the DM_REMOTE_DOMAINS section.
DOM required parameters [optional parameters]
where DOM is an
identifier value used to identify a local domain (LDOM) or a remote domain (RDOM) in the DM_LOCAL_DOMAINS section or in the DM_REMOTE_DOMAINS section. The
DOM identifier must match a previously defined
LDOM in the DM_LOCAL_DOMAINS sections or
RDOM in the DM_REMOTE_DOMAINS section.
This parameter specifies the OSI TP profile used by this domain and is used to determine the required OSI TP functional units. PROFILE can be set to one of the following values:
ATP11,
ATP21,
ATP31,
ATP12,
ATP22, and
ATP32. The UDT ASE application context allows the use of any of these profiles. The XATMI-ASE application context only allows profiles
ATP11,
ATP21 and
ATP31. Profiles
ATP11,
ATP21 and
ATP31 use the Dialogue, Polarized Control and Handshake functional units. Profiles
ATP12,
ATP22 and
ATP32 use the Dialogue, Shared Control, and Handshake functional units. Profiles
ATP11 and
ATP12 do not use OSI TP transactions (the Commit functional unit is not used). Profiles
ATP21 and
ATP22 require the Commit, Unchained Transactions, and Recovery functional units. Profiles
ATP31 and
ATP32 require the Commit, Chained Transactions, and Recovery functional units. By default, the
ATP21 profile is always selected.
LDOM associates this SNACRM with a defined local domain. <LocalDomainName> is the reference to an entry in the DM_LOCAL_DOMAINS section. This name is an ASCII string 1 to 30 characters in length. This parameter is required. This parameter has no default.
Therefore if the SNACRM was running on a machine with an IP address of 206.189.43.13, and we wanted to use port 6000 for the
SNACRM then SNACMADDR would be:
Where LINK is an
identifier value used to identify a connection between a local domain (LDOM) and a remote domain (RDOM). The
RDOM identifier must match a previously defined
RDOM in the DM_REMOTE_DOMAINS section.
Outbound ATMI tpcall() as a CICS distributed program link request with the semantics of SYNCONRETURN.
Outbound ATMI tpcall() as a CICS distributed program link request with full two phase commit transaction semantics using
tpcommit().
Outbound ATMI tpconnect() as APPC or CPIC distributed transaction processing with full two phase commit transaction semantics using
tpcommit().
ACL_NAME required parameters
where ACL_NAME is a (
identifier) name used to identify a particular access control list; it must be 15 characters or less in length.
where an ACLIST is composed of one or more remote domain names (
RDOM) separated by commas. The wildcard character (*) can be used to specify that all the remote domains defined in the DM_REMOTE_DOMAINS section can access a local domain.
service [optional parameters]
where service is the (
identifier) local name of the exported service, and it must be 1-15 characters in length. This name corresponds to a name advertised by one or more servers running with the local Tuxedo System/Domain application. Notice that exported services inherit the default or special properties specified for the service in an entry in the
SERVICES section of the
TUXCONFIG file. Some of these parameters are:
LOAD,
PRIO,
AUTOTRAN,
ROUTING,
BUFTYPE, and
TRANTIME.
Specifies whether (Y) or not (
N) the local service is a conversational service. The default value is N.
The RNAME option is the local-service name imported from a remote CICS/ESA region. This name is used by the CRM to select a local service.
When the RNAME specifies an alternate mirror transaction identifier for explicit attachment for inbound DPL requests, it must be a combination of the alternate mirror
TRANSID and a CICS/ESA program name in the following format:
service [optional parameters]
where service is the (
identifier) name used by the local Tuxedo System/Domain application for a particular remote service. Remote services are associated with a particular remote domain.
Specifies whether (Y) or not (
N) the remote service is a conversational service. The default value is N.
The RNAME option is the name of the host TP_NAME. For non-CICS systems, this name can be up to 64 characters in length. For CICS systems, this name is the trans-id name for APPC-defined requests and the program name for DPL requests. CICS trans-id names cannot exceed four characters and CICS program names cannot exceed eight characters. The RNAME option must observe these requirements.
When the RNAME specifies an alternate mirror transaction identifier for explicit attachment to outbound DPL requests, it must be a combination of the alternate mirror
TRANSID and an advertised remote CICS/ESA program name in the following format:
CRITERION_NAME required parameters
where CRITERION_NAME is the (
identifier) name of the routing entry that was specified on the services entry.
CRITERION_NAME must be 15 characters or less in length.
A range is either a single value (signed numeric value or character string in single quotes), or a range of the form “lower - upper” (where lower and upper are both signed numeric values or character strings in single quotes). Note that “lower” must be less than or equal to “upper”. To embed a single quote in a character string value (as in O’Brien, for example), the single quote must be preceded by two backslashes (
’O\\’Brien’). The value MIN can be used to indicate the minimum value for the data type of the associated
FIELD; for strings and arrays, it is the null string; for character fields, it is 0; for numeric values, it is the minimum numeric value that can be stored in the field. The value
MAX can be used to indicate the maximum value for the data type of the associated
FIELD; for strings and arrays, it is effectively an unlimited string of octal-255 characters; for a character field, it is a single octal-255 character; for numeric values, it is the maximum numeric value that can be stored in the field. Thus, “
MIN - -5” is all numbers less than or equal to –5 and “6
- MAX” is all numbers greater than or equal to 6. The meta-character “*’’ (wild-card) in the position of a range indicates any values not covered by the other ranges previously seen in the entry; only one wild-card range is allowed per entry and it should be last (ranges following it will be ignored).
BUFTYPE = ~type1[:subtype1[,subtype2 . . . ]][;type2[:subtype3[, . . . ]]] . . .~
Is a list of types and subtypes of data buffers for which this routing entry is valid. The types are restricted to be either FML,
VIEW,
X_C_TYPE, or
X_COMMON. No subtype can be specified for type
FML and subtypes are required for the other types (“*” is not allowed). Duplicate type/subtype pairs can not be specified for the same routing criterion name; more than one routing entry can have the same criterion name as long as the type/subtype pairs are unique. This parameter is required. If multiple buffer types are specified for a single routing entry, the data types of the routing field for each buffer type must be the same.
If the field value is not set (for FML buffers), or does not match any specific range and a wild-card range has not been specified, an error is returned to the application process that requested the execution of the remote service.
The BDMCONFIG environment variable is used to find the BDMCONFIG configuration file.
#================================================================
# DMCONFIG
# Application Domain Gateway Test Configuration
#
# See also
# See $(TOP)/Makefile for more information.
#
# @(#)SNA Devel apps/simpsna DMCONFIG 1.6 98/03/03 15:35:29
# Copyright 1997, BEA Systems, Inc., all rights reserved.
#----------------------------------------------------------------
*DM_LOCAL_DOMAINS
simpsnad
GWGRP=GROUP2
TYPE=SNAX
DOMAINID="simpsnad"
BLOB_SHM_SIZE=1000000
DMTLOGDEV=<your Tuxedo filesystem device and name for
DMTLOG>
#example DMTLOGDEV="/home/me/bin/DMTLOG"
*DM_REMOTE_DOMAINS
SIMPSNAG TYPE=SNAX DOMAINID="SIMPSNAG"
*DM_SNACRM
simpcrm SNACRMADDR="<your Host Socket Listen Address>"
LDOM="simpsnad"
#example SNACRMADDR="0x00021770cfbd2b0d" INET family 0x0002 port 6000 host 207.189.43.13 or SNACRMADDR=//207.189.43.13:6000
*DM_SNASTACKS
simpstk
SNACRM="simpcrm"
STACKTYPE=<SNACRM Stack Library Named Token>
LOCALLU=<Local LU definition specified in
stack product>
LTPNAME="*"
STACKPARMS=<Parameters passed to Stack
Product>
#example STACKTYPE="VT210"
# LOCALLU="BEAAPPL1"
# STACKPARMS="testhp" Name of the host machine
*DM_SNALINKS
simplk1 STACKREF="simpstk"
RDOM="SIMPSNAG"
LSYSID=<Connection ID of remote (CICS)
region>
RSYSID=<SYSID of remote (CICS) region>
RLUNAME=<Alias of Applid for remote region>
MODENAME=<Mode name VTAM mode entry>
SECURITY="LOCAL"
STARTTYPE="COLD"
MAXSESS=<Total Session number>
MINWIN=<Session Local Winners>
MAXSYNCLVL=<0|1|2 Maximum Syncpoint Level>
#example LSYSID="BEA"
# RSYSID="TEST"
# RLUNAME="CICSTEST"
# MODENAME="SMSNA100"
# MAXSESS=10
# MINWIN=5
# MAXSYNCLVL=2
*DM_LOCAL_SERVICES
MIRROR LDOM="simpsnad"
CONV=N
RNAME="MIRRORSERV"
INBUFTYPE="STRING"
OUTBUFTYPE="STRING"
API="ATMI"
*DM_REMOTE_SERVICES
SIMPDPL AUTOTRAN=N
LDOM="simpsnad"
RDOM=SIMPSNAG
CONV=N
RNAME="TOUPDPLS"
INBUFTYPE="STRING"
OUTBUFTYPE="STRING"
API="ATMI"
FUNCTION="DPL"
SIMPDTP AUTOTRAN=N
LDOM="simpsnad"
RDOM=SIMPSNAG
CONV=N
RNAME="DTPS"
INBUFTYPE="STRING"
OUTBUFTYPE="STRING"
API="ATMI"
FUNCTION="APPC"
build_dgw(1),
dmadmin(1),
tmboot(1),
tmshutdown(1),
dmloadcf(1),
dmunloadcf(1)
Parse a DMCONFIG file and load binary
BDMCONFIG configuration file.
dmloadcf [-c] [-n] [-y] [-b blocks] {
dmconfig_file | - }
dmloadcf reads a file or the standard input that is in
DMCONFIG syntax, checks the syntax, and optionally loads a binary
BDMCONFIG configuration file. The
BDMCONFIG environment variable points to the path name of the
BDMCONFIG file where the information should be stored.
dmloadcf prints an error message if it finds any required section of the
DMCONFIG file missing. If a syntax error is found while parsing the input file,
dmloadcf exits without performing any updates to the
BDMCONFIG file.
dmloadcf requires the existence of the
$TUXDIR/udataobj/DMTYPE file. This file defines the valid domain types. If this file does not exist,
dmloadcf exits without performing any updates to the
BDMCONFIG file.
The -c option to
dmloadcf causes the program to print minimum IPC resources needed for each local domain (gateway group) in this configuration. The
BDMCONFIG file is not updated.
The -n option to
dmloadcf causes the program to do only syntax checking of the ASCII
DMCONFIG file without actually updating the
BDMCONFIG file.
After syntax checking, dmloadcf checks to see if the file pointed to by
BDMCONFIG exists, is a valid Tuxedo System file system, and contains
BDMCONFIG tables. If these conditions are not true, the user is prompted to create and initialize the file with
where path is the complete file name of the
BDMCONFIG file. Prompting is suppressed if the standard input or output are not terminals, or if the
-y option is specified on the command line. Any response other than “
y” or “
Y” will cause
dmloadcf to exit without creating the configuration file.
If the BDMCONFIG file is not properly initialized, and the user has given the go-ahead,
dmloadcf creates the Tuxedo file system and then creates the
BDMCONFIG tables. If the
-b option is specified on the command line, its argument is used as the number of blocks for the device when creating the Tuxedo file system. If the value of the
-b option is large enough to hold the new
BDMCONFIG tables,
dmloadcf will use the specified value to create the new file system; otherwise,
dmloadcf will print an error message and exit. If the
-b option is not specified,
dmloadcf will create a new file system large enough to hold the
BDMCONFIG tables. The
-b option is ignored if the file system already exists. The
-b option is highly recommended if
BDMCONFIG is a raw device (that has not been initialized) and should be set to the number of blocks on the raw device. The
-b option is not recommended if
BDMCONFIG is a regular UNIX file.
If the BDMCONFIG file is determined to already have been initialized,
dmloadcf ensures that the local domain described by that
BDMCONFIG file is not running. If a local domain is running,
dmloadcf prints an error message and exits. Otherwise,
dmloadcf, to confirm that the file should be overwritten, prompts the user with:
If the SECURITY parameter is specified in the
RESOURCES section of the
TUXCONFIG file, then
dmloadcf will flush the standard input, turn off terminal echo and prompt the user for an application password as follows:
The password is truncated to 8 characters. The option to load the ASCII DMCONFIG file via the standard input (rather than a file) cannot be used when this
SECURITY parameter is turned on. If the standard input is not a terminal, that is, if the user cannot be prompted for a password (as with a
here file, for example), then the environment variable
APP_PW is accessed to set the application password. If the environment variable
APP_PW is not set with the standard input not a terminal, then
dmloadcf will print an error message, generate a log message and fail to load the
BDMCONFIG file.
The environment variable APP_PW must be set for applications that require security (the
SECURITY parameter in the
TUXCONFIG file is set to
APP_PW) and
dmloadcf is run with something other than a terminal as the standard input.
The BDMCONFIG environment variable should point to the BDMCONFIG file.
If dmloadcf is run on an active node, the following error message is displayed:
If dmloadcf is run by a person whose effective user identifier doesn’t match the
UID specified in the
TUXCONFIG file, the following error message is displayed:
Upon successful completion, dmloadcf exits with exit code 0. If the
BDMCONFIG file is updated, a
userlog message is generated to record this event.
dmunloadcf translates the
BDMCONFIG configuration file from the binary representation into ASCII. This translation is useful for transporting the file in a compact way between machines with different byte ordering and backing up a copy of the file in a compact form for reliability. The ASCII format is the same as is described in
dmconfig(5).
dmunloadcf reads values from the
BDMCONFIG file pointed to by the
BDMCONFIG environment variable and writes them to its standard output.
dmunloadcf checks that the file pointed to by the
BDMCONFIG environment variable exists, is a valid Tuxedo file system, and contains
BDMCONFIG tables. If any of these conditions is not met,
dmunloadcf prints an error message and exits with error code 1. Upon successful completion,
dmunloadcf exits with exit code 0.
GWADM SRVGRP = “identifier” SRVID = “
number” REPLYQ = “N”
CLOPT = “-A -- [-a {
on |
off } ] [-s
services ]
[-t {
on |
off } ]“
The CLOPT option is a string of command line options that is passed to the GWADM when it is booted. This string has the following format:
This option turns off or
on the audit log feature for this local domain. The default is
off. The
dmadmin program can be used to change this setting while the gateway group is running (see
dmadmin(1)).
Specifies the remote services that should be initially offered by the domain gateway. The specifications for these services are found in the DMCONFIG file. For example, the specification
This option turns off or
on the statistics gathering feature for the local domain. The default is
off. The
dmadmin program can be used to change this setting while the gateway group is running (see
dmadmin(1)).
dmconfig(5),
DMADM(5),
servopts(5),
ubbconfig(5)
GWSNAX should be defined in the SERVERS section of the UBBCONFIG file as a server running within a particular gateway group; that is, SRVGRP must be set to the corresponding GRPNAME tag specified in the GROUPS section. The SVRID parameter is also required and its value must consider the maximum number of gateways allowed within the gateway group. The GWSNAX definition must not precede its associated CRM server definition in the
UBBCONFIG file.
The CLOPT option is a string of command line options that is passed to the GWSNAX when it is booted. This string has the following format:
Establishes that encryption is in effect for this client process. type is the encryption type. Currently, the only valid entry is GPE. The min and max values designate the minimum and maximum number of bits to be used for encryption. This level is used during the negotiation between the CRM and client process. Any number is acceptable, but the negotiated values resolve to 0, 56, or 128.
min designates the minimum number of bits to be used for encryption. This level is used during the negotiation between the CRM and GWSNAX. Any number is acceptable, but the negotiated values resolve to 0, 56, or 128. The level specified must be supported by the security add-on package used.
max designates the maximum number of bits to be used for encryption. This level is used during the negotiation between the CRM and GWSNAX. Any number is acceptable, but the negotiated values resolve to 0, 56, or 128.
Alternatively, for ARTDPL, -N can be omitted as well if non-aligned view file is used instead of common aligned view file. For example, on Linux, non-aligned view file can be generated as following:
dmconfig(5),
DMADM(5),
servopts(5),
ubbconfig(5)
modusr -d <local domain> ID -R <
remote domain ID> -u <
remote username>
modusr can only be executed as a subcommand of
dmadmin(1). The purpose of this page is to describe options for the subcommand and to show an example.
The dmadmin modusr subcommand exits with a return code of 0 upon successful completion.