The osiadmin processor provides the following features:
•
|
Imports configurations from eLink OSI TP 1.3 (DMCONFIG, OSITP configuration, and ULS configuration) and creates a comparable configuration in proper format for eLink OSI TP 4.x or Oracle Tuxedo Mainframe Adapter for OSI TP 8.1 or 9.1.
|
•
|
Exports the dmconfig file and creates the correct format of the config-in.txt file needed for the UNISYS ClearPath systems.
|
The osiadmin processor can be initiated in interactive, script, or batch mode. The
OSIRUNDIR environment variable must be set in order to run the
osiadmin utility. Refer to Setting Environment Variables for more information.
The local domain name (LDOM) may be specified at
osiadmin execution time. The
LDOM is the
LDOM identifier specified in the
Local_Domains section of the
DMCONFIG file.
Note:
|
The LDOM identifier is case sensitive.
|
where BA.CENTRAL01 is the
LDOM.
The LDOM is necessary for
CONNECTIONSTATUS,
DUMP,
TRACE,
TESTCONNECTION, and
LISTRDOM commands. If the
LDOM is not specified on the command line, the user must enter an
LDOM command before using any of these commands.
where input_script_name is the name of a script file that you created with a series of one or more commands you wish to execute. If the script file is in a different directory, you must also enter the directory path. The script file is a text file that you can create with any text editor. Following is an example run of a script that might be used with
osiadmin:
The "-b" option initiates the osiadmin in batch mode with the following conditions: the menu of commands that is normally displayed upon startup of
osiadmin is not printed, pagination is set to off, command echo is set to on, and interactive prompts (for example, "Overwrite file, Y or N") are suppressed.
When you initiate osiadmin or enter any of the other commands in interactive mode, the command executes if the syntax is correct. If the syntax is incorrect, an error message displays showing the correct syntax. When the command executes, results are printed to the screen. If the result is more than one page and
PAGINATE=ON (which is the default), the prompt,
“CONTINUE? Y or N” displays. Select
Y to continue displaying another 20 lines or
N to discontinue displaying the results.
When you initiate osiadmin and enter commands using a script, the commands execute in order and the results are printed to the screen as the commands execute.
All osiadmin commands are initiated through interactive mode or through a script containing one or more commands. The following sections explain how to get Help for
osiadmin commands and provide descriptions for each command in detail.
where command is any of the valid commands.
Exports TMA OSI TP configuration information from the DMCONFIG file and creates configuration files readable by OSI-TP on UNISYS ClearPath servers. The names of the files produced are
<output directory>TAILOR-IN.TXT and
<output directory>CONFIG-IN.TXT. The output directory is optional. The current directory is the default if none is specified.
Note:
|
OSITP-CONFIGFILE is the source configuration file and not the current.cfg file that was required for older versions of Oracle Tuxedo Mainframe Adapter for OSI TP.
|
Sets the local domain name. The LDOM must be set for the
DUMP, CONNECTIONSTATUS, TRACE, TESTCONNECTION, and
LISTRDOM commands. The
LDOM can also be specified as an argument when executing the
osiadmin.
Retrieves and displays a list of all RDOMs. The list indicates if the
RDOMs are offline or online, indicates if the online
RDOMs are currently available, and indicates that communications with unavailable
RDOMs are not operational. TMA OSI TP will try to establish communications until successful.
Resets RDOM configured to be offline at startup to online. Once an RDOM is set OFFLINE, it must be manually reset to ONLINE before communications with the peer can continue. All remote services associated with the
RDOM will be advertised.