### Example Output of Supported Platforms

Source: https://docs.oracle.com/cd/E12531_01/index.htm/msgq50/mqscinst/1inst

An example of the list of supported operating systems and machine/processor types displayed during the installation script execution.

```text
01) aix41/rs6000     02) aix42/rs6000     03) aix43/rs6000
04) hpux10/hppa      05) sol251/sparc     06) sol26/sparc
```

--------------------------------

### Execute MessageQ Installation Script (Lowercase)

Source: https://docs.oracle.com/cd/E12531_01/index.htm/msgq50/unixic/3one

Run this command to start the MessageQ client installation process if the installation script file name is in lowercase (install.sh). Ensure you are in the correct directory.

```Shell
sh ./install.sh
```

--------------------------------

### FTP Connection to MVS System Example

Source: https://docs.oracle.com/cd/E12531_01/index.htm/msgq50/mvsinst/1install

Illustrates the initial steps of establishing an FTP connection to an MVS system, including entering the hostname, username, and password for authentication.

```FTP
% ftp mvs-node-name
Connected to mvs-node-name.
Name (mvs-node-name:unix-id): tso-id
331 Send password please.
Password: tso-password
230 tso-id is logged on.
Remote system type is OS/MVS.
```

--------------------------------

### VMSINSTAL Product Processing Confirmation and Start

Source: https://docs.oracle.com/cd/E12531_01/index.htm/msgq50/lu62inst/chap1

Shows the VMSINSTAL messages confirming the specific product (MQLU62VAXA V4.0) that will be installed, the timestamp for the beginning of the installation, and the informational message indicating the restoration of the product saveset.

```OpenVMS DCL Output
The following products will be processed:
  MQLU62VAXA V4.0

        Beginning installation of MQLU62VAXA V4.0 at 10:48

%VMSINSTAL-I-RESTORE, Restoring product saveset A ...
```

--------------------------------

### Interactive Installation Prompts for Solaris

Source: https://docs.oracle.com/cd/E12531_01/index.htm/tma_ositp91/ositpig/instal

This snippet captures the full interactive transcript of the `install.sh` script during a Solaris installation. It demonstrates the prompts for platform selection, installation directory, package selection, and the final confirmation of successful installation. Users must respond to these prompts to complete the setup.

```Shell
[lcsol13]:/nfs/vol1/homes1/tkumar/TMAOSITP9/unix>sh install.sh

01) hp/hpux1123      02) ibm/aix53        03) sun5x/sol10

Install which platform's files? [01-       3, q to quit, l for list]: 3

** You have chosen to install from sun5x/sol10 **

BEA Tuxedo Mainframe Adapter OSI TP 9.1

This directory contains BEA Tuxedo Mainframe Adapter TMA OSI TP 9.1 for
SunOS 5.10 (Solaris) on SPARC.

Is this correct? [y,n,q]: y

To terminate the installation at any time
press the interrupt key,
typically <del>, <break>, or <ctrl+c>.

The following packages are available:

	1     ositp           BEA Tuxedo Mainframe Adapter TMA OSI TP 9.1

Select the package(s) you wish to install (default: 1) [?,??,q]: 1

BEA Tuxedo Mainframe Adapter TMA  OSI TP 9.1
(sparc) Release 9.1
Copyright (c) 2006 BEA Systems, Inc.
All Rights Reserved.

BEA is a registered trademark of BEA Systems, Inc.

Directory where OSI TP files are to be installed

(Enter your Tuxedo directory path) [?,q]:
/nfs/vol1/homes1/tkumar/tux91/sol9/tux
edo9.1

Using /nfs/vol1/homes1/tkumar/tux91/sol9/tuxedo9.1 as the OSI TP base
directory
PREREQ_SFX = T91

Determining if sufficient space is available ...
10544 blocks are required
421303040 blocks are available to
/nfs/vol1/homes1/tkumar/tux91/sol9/tuxedo9.1

Unloading /nfs/vol1/homes1/tkumar/TMAOSITP9/unix/sun5x/sol10/ositp/OSITPT91.Z ..

TMA/osi/samples/simpapp/dmconfig
TMA/osi/samples/simpapp/tailor.txt
TMA/osi/samples/simpapp/ubbsimple
bin/GWOSITP
bin/getulogpfx
bin/lic.sh
bin/osiadmin
bin/osiltmain
bin/portproxy
bin/prdebuginfo
bin/setPROXYpriv
lib/libgwo.so
lib/libnwunisys.so
lib/libtasn1.so
locale/C/LIBGWO.text
locale/C/LIBGWO_CAT
locale/C/libnwunisys.cat
udataobj/gbebc2u.fld
udataobj/jbis82u.fld
udataobj/ksc2u.fld
udataobj/u2gbebc.fld
udataobj/u2jbis8.fld
udataobj/u2ksc.fld
10370 blocks

... finished

The $TUXDIR/bin/portproxy executable listens on privileged ports (< 1024)
on behalf of GWOSITP. The script $TUXDIR/bin/setPROXYpriv is used to
set the appropriate permissions.

If you know the root password, you may run setPROXYpriv now.
Run the setPROXYpriv script? [y/n]: n
Remember to run $TUXDIR/bin/setPROXYpriv later.

Changing file permissions...
... finished

Installation of BEA Tuxedo Mainframe Adapter TMA OSI TP 9.1 was successful.

Please don't forget to fill out and send in your registration card
```

--------------------------------

### Install BEA MessageQ Online Documentation

Source: https://docs.oracle.com/cd/E12531_01/index.htm/msgq50/unixic/3one

Outlines the steps for installing the online documentation for BEA MessageQ 5.0. This includes confirming the documentation's copyright, specifying its installation directory, and monitoring the installation progress.

```Console
BEA MessageQ Online Documentation
(alpha) Release 5.0
Copyright (c) 1998 BEA Systems, Inc.
Portions * Copyright 1986-1998 RSA Data Security, Inc.
All Rights Reserved.
```

```Console
Base directory for documentation installation (default: /opt/messageq) [?,q]:
```

```Console
Determining if sufficient space is available ...
27810 blocks are required
6186632 blocks are available to /opt/messageq
```

```Console
Using /opt/messageq for the documentation base directory
```

```Console
Installing documentation...
```

```Console
Changing file permissions...
... finished
```

```Console
Installation of BEA MessageQ Online Documentation was successful
```

```Console
Please don't forget to fill out and send in your registration card
```

--------------------------------

### Installer Launch and Preparation Output

Source: https://docs.oracle.com/cd/E12531_01/index.htm/salt20/install/instcon

Displays the initial console output from the InstallAnywhere installer as it launches and prepares for the console mode installation process.

```Shell
Launching installer...

Preparing CONSOLE Mode Installation...
```

--------------------------------

### Selecting MessageQ Installation Type (Client/Server)

Source: https://docs.oracle.com/cd/E12531_01/index.htm/msgq50/unixcli/2install

This snippet details the interactive choice between installing BEA MessageQ as a server and client, or as a client-only setup. The user specifies the desired installation environment.

```CLI
The following installation options are available:

  1     both            Server and client
  2     client          Client only
```

```CLI
Select an option (default: both) [?,??,q]: 2
```

--------------------------------

### Select BEA MessageQ Installation Platform

Source: https://docs.oracle.com/cd/E12531_01/index.htm/msgq50/unixic/3one

Guides the user through selecting the target operating system and hardware platform for BEA MessageQ 5.0 installation. The process involves choosing from a list of supported platforms and confirming the selection.

```Console
Install which platform's files? [01-    12, q to quit, l for list]: 4
```

```Console
** You have chosen to install from dux/alpha **
```

```Console
BEA MessageQ 5.0
```

```Console
This directory contains the BEA MessageQ Core System for
Digital Unix 4.0 on DEC Alpha.
```

```Console
Is this correct? [y,n,q]: y
```

--------------------------------

### Select Installation Platform for BEA MQ Series Connection

Source: https://docs.oracle.com/cd/E12531_01/index.htm/msgq50/mqscinst/1inst

Guides the user through selecting the target operating system and hardware architecture for the BEA MQ Series Connection installation, confirming the choice before proceeding.

```Console
Install which platform's files? [01-    6, q to quit, l for list]: 5
```

```Console
** You have chosen to install from sol251/sparc **
```

```Console
BEA MQ Series Connection 5.0
```

```Console
This directory contains the BEA MQ Series Connection for
Solaris on Sparc.
```

```Console
Is this correct? [y,n,q]: y
```

--------------------------------

### Example MessageQ Installation Path for System PATH

Source: https://docs.oracle.com/cd/E12531_01/index.htm/msgq50/wntic/1instal

This snippet illustrates the format for the MessageQ installation's 'bin' directory, which needs to be appended to the Windows NT system's PATH environment variable. This ensures that MessageQ executable images are discoverable by the system.

```System Configuration
drive:\\installation directory\\bin
```

--------------------------------

### Manually Start Secure Simpapp Server Application

Source: https://docs.oracle.com/cd/E12531_01/index.htm/tuxedo100/security/samples

Commands to manually start the server component of the Secure Simpapp sample application using the `tmboot` utility. This is an alternative to the automated `runme` command for specific testing or debugging scenarios.

```Windows Batch
prompt>tmboot -y
```

```UNIX Shell
ksh prompt>tmboot -y
```

--------------------------------

### Secure Simpapp Environment Variable Definitions and Examples

Source: https://docs.oracle.com/cd/E12531_01/index.htm/tuxedo100/security/samples

Defines the required environment variables for the Secure Simpapp application, providing descriptions and example values for both Windows 2003 and UNIX operating systems.

```APIDOC
Environment Variables for Secure Simpapp:
  - Name: APPDIR
    Description: The directory path where you copied the sample application files.
    Examples:
      Windows 2003: c:\work\simpappSSL
      UNIX: /usr/work/simpappSSL
  - Name: TUXCONFIG
    Description: The directory path and name of the configuration file.
    Examples:
      Windows 2003: c:\work\simpappSSL\tuxconfig
      UNIX: /usr/work/simpappSSL/tuxconfig
  - Name: TOBJADDR
    Description: The host name and port number of the IIOP Listener/Handler. The port number must be defined as a port for SSL communications.
    Examples:
      Windows 2003: trixie::1111
      UNIX: trixie::1111
  - Name: RESULTSDIR
    Description: A subdirectory of APPDIR where files that are created as a result of executing the runme command are stored.
    Examples:
      Windows 2003: c:\workdirectory\
      UNIX: /usr/local/workdirectory/
```

--------------------------------

### Install BEA MQ Series Connection Online Documentation

Source: https://docs.oracle.com/cd/E12531_01/index.htm/msgq50/mqscinst/1inst

Details the process of installing the online documentation, including copyright display, directory selection, space availability checks, and file installation progress.

```Console
BEA MQ Series Connection Online Documentation
(sparc) Release 5.0
Copyright (c) 1998 BEA Systems, Inc.
Portions * Copyright 1986-1998 RSA Data Security, Inc.
All Rights Reserved.
MessageQ is a registered trademark of BEA Systems, Inc.
TUXEDO is a registered trademark.
```

```Console
Base directory for documentation installation (default: /usr/kits) [?,q]:
```

```Console
Determining if sufficient space is available ...
530 blocks are required
249948 blocks are available to /usr/kits
```

```Console
Using /usr/kits for the documentation base directory
```

```Console
Installing documentation...
.
.
.
Changing file permissions...
... finished
```

```Console
Installation of BEA MQ Series Connection Online Documentation was successful
```

```Console
Please don't forget to fill out and send in your registration card
```

--------------------------------

### Choose BEA MessageQ Software Packages

Source: https://docs.oracle.com/cd/E12531_01/index.htm/msgq50/unixic/3one

Illustrates the process of selecting which components of BEA MessageQ to install, such as the core system or online documentation. The user can choose specific packages or install all available components.

```Console
   1   msgq          BEA MessageQ
   2   msgqdoc       BEA MessageQ Online Documentation

```

```Console
Select the package(s) you wish to install (or 'all' to install
all packages) (default: all) [?,??,q]: all
```

--------------------------------

### JRLY Windows 2003 Installation and Configuration Examples

Source: https://docs.oracle.com/cd/E12531_01/index.htm/tuxedo100/jdg/dvconfig

Practical examples demonstrating how to install and configure JRLY services on Windows 2003 using the command line, showing both default and named instance operations.

```Shell
jrly -install
jrly -install MASTER
jrly -set -f c:\\tux71\\udataobj\\jolt\\jrly.con
jrly -set -d MASTER -f c:\\tuxdir\\udataobj\\jolt\\master.con
```

--------------------------------

### Choose BEA MQ Series Connection Packages

Source: https://docs.oracle.com/cd/E12531_01/index.htm/msgq50/mqscinst/1inst

Presents a list of available software packages (main application and documentation) and prompts the user to select which ones to install, with an option to install all.

```Console
1   mqsc          BEA MQ Series Connection
2   mqscdoc       BEA MQ Series Connection Online Documentation

```

```Console
Select the package(s) you wish to install (or 'all' to install
all packages) (default: all) [?,??,q]: all
```

--------------------------------

### MessageQ Installation Options

Source: https://docs.oracle.com/cd/E12531_01/index.htm/msgq50/unixcli/2install

This section describes the different installation subsets for MessageQ, outlining whether to install both client and server components for development/running applications, or just the Client Library for remote client access.

```APIDOC
Table 2-3 MessageQ Installation Options:
  - Both client and server: Installed on licensed systems for developing or running MessageQ applications. Includes Client Library Server, include files, and examples.
  - Client Library: Provides remote client applications access to message queuing using MessageQ for UNIX. Also installs MessageQ include files.
```

--------------------------------

### Execute Uppercase Installation Script

Source: https://docs.oracle.com/cd/E12531_01/index.htm/msgq50/mqscinst/1inst

Command to run the installation script when its name is found to be in uppercase (INSTALL.SH). This initiates the software installation process.

```shell
% sh ./INSTALL.SH
```

--------------------------------

### Execute Lowercase Installation Script

Source: https://docs.oracle.com/cd/E12531_01/index.htm/msgq50/mqscinst/1inst

Command to run the installation script when its name is found to be in lowercase (install.sh). This initiates the software installation process.

```shell
% sh ./install.sh
```

--------------------------------

### Locate Secure Simpapp Sample Application Files

Source: https://docs.oracle.com/cd/E12531_01/index.htm/tuxedo100/security/samples

These paths indicate the default installation locations for the Secure Simpapp sample application files on Windows 2003 and UNIX systems within the TUXdir directory structure.

```Text
Windows 2003:
drive:\TUXdir\samples\corba\simpappSSL

UNIX:
/usr/local/TUXdir\samples\corba\simpappSSL
```

--------------------------------

### Execute MessageQ Installation Script

Source: https://docs.oracle.com/cd/E12531_01/index.htm/msgq50/unixcli/2install

These shell commands demonstrate how to run the MessageQ installation script, accounting for both lowercase and uppercase variations of the script name depending on how the CD-ROM was mounted.

```Shell
sh ./install.sh
```

```Shell
sh ./INSTALL.SH
```

--------------------------------

### Execute MessageQ Installation Script (Uppercase)

Source: https://docs.oracle.com/cd/E12531_01/index.htm/msgq50/unixic/3one

Use this command to initiate the MessageQ client installation if the installation script file name is in uppercase (INSTALL.SH). Verify your current directory before execution.

```Shell
sh ./INSTALL.SH
```

--------------------------------

### Select BEA MessageQ Client/Server Installation Type

Source: https://docs.oracle.com/cd/E12531_01/index.htm/msgq50/unixic/3one

Explains how to choose between installing BEA MessageQ as a server and client, or as a client-only component, based on the deployment requirements.

```Console
The following installation options are available:
```

```Console
  1     both            Server and client
  2     client          Client only

Select an option (default: both) [?,??,q]: both
```

--------------------------------

### Build Jolt EJB Example (Windows)

Source: https://docs.oracle.com/cd/E12531_01/index.htm/tuxedo100/Jolt_wls/EJB_example

Command to build the Jolt EJB example on Windows 2003 using the default build script provided by BEA Jolt.

```Shell
$ build
```

--------------------------------

### List Directory Contents to Find Installation Script

Source: https://docs.oracle.com/cd/E12531_01/index.htm/msgq50/mqscinst/1inst

Command to list the contents of the current directory. This helps in determining whether the installation script (install.sh or INSTALL.SH) is in lowercase or uppercase.

```shell
%ls
```

--------------------------------

### Build Sample Application on Windows

Source: https://docs.oracle.com/cd/E12531_01/index.htm/tuxedo100/notify/int_samp

Instructions for building the sample application on Microsoft Windows using the `nmake` utility with provided makefiles.

```Batch
nmake
```

--------------------------------

### Files in Introductory C++ Sample Directory

Source: https://docs.oracle.com/cd/E12531_01/index.htm/tuxedo100/notify/int_samp

Lists the key files located in the `introductory_sample_c++` directory, including source code, build scripts, and environment setup files for both Windows and UNIX.

```APIDOC
File: Readme.txt
  Description: Describes the Introductory sample application and provides instructions for setting up the environment and building and running the application.
File: setenv.cmd
  Description: Sets the environment for Microsoft Windows systems.
File: setenv.ksh
  Description: Sets the environment for UNIX systems.
File: makefile.nt
  Description: Makefile for Microsoft Windows systems.
File: makefile.mk
  Description: Makefile for UNIX systems.
File: makefile.inc
  Description: Common makefile used by the `makefile.nt` and the `makefile.mk` files.
File: Reporter.cpp
  Description: Code for the reporter.
File: Subscriber.cpp
  Description: Code for the subscriber.
File: NewsConsumer_i.h and NewsConsumer.cpp
  Description: The callback servant class that subscribers use to receive news events. (For the Subscriber application.)
```

--------------------------------

### Build Sample Application on UNIX

Source: https://docs.oracle.com/cd/E12531_01/index.htm/tuxedo100/notify/int_samp

Instructions for building the sample application on UNIX using the `make` utility with provided makefiles.

```Shell
make
```

--------------------------------

### Convert BEA MessageQ Example Programs on MVS using TSO RECEIVE

Source: https://docs.oracle.com/cd/E12531_01/index.htm/msgq50/mvsinst/1install

This snippet demonstrates the TSO RECEIVE command used on an MVS system to convert transferred example programs (X@GET and X@BASIC) from a sequential unload format back into their original mainframe load module formats. It includes the interactive prompts and required user input.

```TSO
READY
RECEIVE INDSN('DMQ.V5R0.PROC(X@GET)')
INMR901I Dataset DMQ.V5R0.PROC from
INMR902I Members: X@GET
INMR906A Enter restore parameters or 'DELETE' or 'END' +
DATASET ('DMQ.V5R0.LOAD(X@GET)')
```

```TSO
READY

RECEIVE INDSN('DMQ.V5R0.PROC(X@BASIC)')

INMR901I Dataset DMQ.V5R0.PROC from
INMR902I Members: X@BASIC
INMR906A Enter restore parameters or 'DELETE' or 'END' +

DATASET ('DMQ.V5R0.LOAD(X@BASIC)')
```

--------------------------------

### Set Up Environment on UNIX

Source: https://docs.oracle.com/cd/E12531_01/index.htm/tuxedo100/notify/int_samp

Command to source the `setenv.ksh` script to configure the environment for the sample application on UNIX.

```Shell
. ./setenv.ksh
```

--------------------------------

### Set Temporary Directory for UNIX Installation

Source: https://docs.oracle.com/cd/E12531_01/index.htm/tuxedo100/install/inspre

To allocate an alternate temporary directory for the BEA Tuxedo installation on UNIX systems, set the `IATEMPDIR` environment variable to the desired directory path before starting the installation program. This ensures adequate temporary space for the installer.

```Shell
export IATEMPDIR=tmpdirname
```

--------------------------------

### Sample Windows Silent Installation Template File

Source: https://docs.oracle.com/cd/E12531_01/index.htm/salt20/install/instsil

Example configuration for a silent installation template file on a Windows system. It sets the installation mode to 'silent', specifies the BEA Home directory path, and includes the overwrite option.

```Batch
INSTALLER_UI=silent
### BEA Home Directory ###
### NOTE: backslashes must be escaped. ###
BEAHOME=C:\\bea
### Overwite Option###
OVERWRITE=yes|no
```

--------------------------------

### Set Up Environment on Windows

Source: https://docs.oracle.com/cd/E12531_01/index.htm/tuxedo100/notify/int_samp

Command to execute the `setenv.cmd` script to configure the environment for the sample application on Windows.

```Batch
.\setenv.cmd
```

--------------------------------

### Build Introductory Sample Application

Source: https://docs.oracle.com/cd/E12531_01/index.htm/tuxedo100/notify/int_samp

Commands to compile and build the Introductory Sample Application using platform-specific makefiles. This process requires `nmake` on Microsoft Windows and `make` on UNIX systems.

```Shell
nmake -f makefile.nt
```

```Shell
make -f makefile.mk
```

--------------------------------

### Sample UNIX Silent Installation Template File

Source: https://docs.oracle.com/cd/E12531_01/index.htm/salt20/install/instsil

Example configuration for a silent installation template file on a UNIX system. It specifies the installation mode as 'silent', defines the BEA Home directory path, and includes the overwrite option.

```Shell
INSTALLER_UI=silent
### BEA Home Directory ###
### NOTE: backslashes must be escaped. ###
BEAHOME=/home/user/bea
### Overwite Option###
OVERWRITE=yes|no
```

--------------------------------

### Example: Starting CRM Links with crmlkon

Source: https://docs.oracle.com/cd/E12531_01/index.htm/tma_sna91/crm/chap2

A practical example demonstrating how to use the `crmlkon` command to start specific CRM links. This snippet shows how to target a CRM server on a particular host and port, and then specify multiple link names to be activated.

```Shell
crmlkon -n mach1:5000 link2 cicstest
```

--------------------------------

### Example: Setting up a Queue with qmadmin

Source: https://docs.oracle.com/cd/E12531_01/index.htm/tuxedo100/rfcm/rfcmd

This example demonstrates a sequence of `qmadmin` commands to set up a queue space. It includes initializing `qmadmin`, creating device lists (`crdl`), listing device lists (`lidl`), and preparing to create a queue space.

```Shell
$ QMCONFIG=/dev/rawfs qmadmin
qmadmin - Copyright (c) 1987 ATT; 1991 USL. All rights reserved.
QMCONFIG=/dev/rawfs
# create the list of devices on which the queue space
# can exist;  specify two devices, 80000 and 600
# blocks, respectively
# NOTE: the first one will actually contain the device list
#
# create first device on a raw slice
#
> crdl /dev/rawfs 0 80000
Created device /dev/rawfs, offset 0, size 80000 on /dev/rawfs
#
# create another device on a UNIX file
#
> crdl /home/queues/FS    0    600
Created device /home/queues/FS, offset 0, size 600 on /dev/rawfs
#
# if you want a list of the device list
#
> v  Verbose mode is now on

> lidl
universal device index. 0:
       name: /dev/rawfs
       start: 0
       size: 20000
       free space map(1 entry used 47 available):
              size[1]: 79974 addr[1]: 26
universal device index. 1:
       name: /home/queues/FS
       start: 0
       size: 600
       free space map(1 entry used 47 available):
              size[1]: 600  addr[1]: 0
#
# create  a queue space
```

--------------------------------

### Start Specific CRM Links on a Remote Server

Source: https://docs.oracle.com/cd/E12531_01/index.htm/tma_sna91/crm/appa

This example demonstrates how to use `crmlkon` to start `link2` and `cicstest` on a CRM server running on `mach1` at port `5000`.

```shell
crmlkon -n mach1:5000 link2 cicstest
```

--------------------------------

### Default Installation Path for MessageQ Sample Programs

Source: https://docs.oracle.com/cd/E12531_01/index.htm/msgq50/wincli/4using

Provides the typical default installation path for MessageQ client sample application programs. These examples are distributed with the client and demonstrate various features of the MessageQ API, serving as valuable references for developers.

```Shell
c:\\...\\BEA Systems\\BEA MessageQ\\examples\\x
```

--------------------------------

### Invoke dmqsetup and View Initial Menu

Source: https://docs.oracle.com/cd/E12531_01/index.htm/msgq50/unixic/5three

This snippet demonstrates how to launch the `dmqsetup` utility from the command line. Upon execution, it displays the utility's welcome message and its main interactive menu, allowing users to begin configuring MessageQ for UNIX.

```Shell
# dmqsetup
MessageQ for UNIX: Setup
1. Profile
2. Links
3. Routes
4. Queues
5. Names
6. Create standard group initialization
7. Save
8. Help
9. Exit
```

--------------------------------

### Execute runme Command for Secure Simpapp Sample Application

Source: https://docs.oracle.com/cd/E12531_01/index.htm/tuxedo100/security/samples

Instructions for building and running the Secure Simpapp sample application using the automated `runme` command. This command handles environment setup, compilation, and application startup/shutdown. Users will be prompted for a password during execution.

```Windows Batch
prompt>cd workdirectory
prompt>runme
```

```UNIX Shell
ksh prompt>cd workdirectory
ksh prompt>./runme.ksh
```

--------------------------------

### Start CRM with Output Redirection

Source: https://docs.oracle.com/cd/E12531_01/index.htm/tma_sna91/crm/appa

This example demonstrates how to start the CRM command with specific parameters, redirecting standard output to `std.out` and standard error to `std.err`, and running it in the background.

```shell
CRM -t 0 //myhost:5587 GROUP2 /dev/null>std.out 2>std.err &
```

--------------------------------

### Start BEA TSAM Manager

Source: https://docs.oracle.com/cd/E12531_01/index.htm/tsam11/deployment/deploy

These commands provide the steps to start the BEA TSAM Manager application on both UNIX and Windows operating systems. They involve navigating to the TSAM installation directory and executing the appropriate startup script.

```Shell
cd <TSAMDIR>
. ./tsam.env
cd <TSAMDIR>/bin
./startup.sh
```

```Batch
cd <TSAMDIR>\bin
startup.cmd
```

--------------------------------

### VMSINSTAL Initial Welcome and Backup Prompt

Source: https://docs.oracle.com/cd/E12531_01/index.htm/msgq50/lu62inst/chap1

Displays the initial output from the VMSINSTAL utility, including the product installation procedure version, current date/time, and a crucial prompt asking for confirmation of system disk backup before proceeding with the installation.

```OpenVMS DCL Output
OpenVMS VAX Software Product Installation Procedure V6.2

 It is 06-JAN-1999 at 10:45.
 Enter a question mark (?) at any time for help.

* Are you satisfied with the backup of your system disk [YES]?
```

--------------------------------

### Example tuxwsvr.ini Initialization File for BEA Tuxedo

Source: https://docs.oracle.com/cd/E12531_01/index.htm/tuxedo100/install/insadm

This snippet provides an example of the tuxwsvr.ini file, which configures the tuxwsvr web server. It maps virtual paths (CGI, HTML) to physical directories on the file system, directing where the server should find its content. While typically generated by the installer, it can be manually edited for custom setups.

```Configuration
# tuxwsvr initialization file.
# Created Sep 12, 2004 2:02:07 PM by BEA software installation program.
#
CGI   /cgi-bin    C:\bea\tuxedo10.0/udataobj/webgui/cgi-bin
HTML  /java    C:\bea\tuxedo10.0/udataobj/webgui/java
HTML  /doc     C:\bea\tuxedo10.0/help
HTML  /        C:\bea\tuxedo10.0/udataobj/webgui
```

--------------------------------

### Other Files Used by Introductory Sample Application

Source: https://docs.oracle.com/cd/E12531_01/index.htm/tuxedo100/notify/int_samp

Details additional files required by the sample application, including common makefile symbols, exception utilities, and OMG IDL definitions for CORBA services.

```APIDOC
Files located in the common directory:
  File: common.nt
    Description: Makefile symbols for Microsoft Windows systems.
  File: common.mk
    Description: Makefile symbols for UNIX systems.
  File: introductory.inc
    Description: Makefile for administrative targets.
  File: ex.h
    Description: Utilities to print exceptions. (For C++ only.)
  File: client_ex.h
    Description: Client utilities to handle exceptions. (For C++ only.)
Files located in the \tuxdir\include directory:
  File: CosEventComm.idl
    Description: The OMG IDL code that declares the CosEventComm module.
  File: CosNotification.idl
    Description: The OMG IDL code that declares the CosNotification module.
  File: CosNotifyComm.idl
    Description: The OMG IDL code that declares the CosNotifyComm module.
  File: Tobj_Events.idl
    Description: The OMG IDL code that declares the Tobj_Events module.
  File: Tobj_SimpleEvents.idl
    Description: The OMG IDL code that declares the Tobj_SimpleEvents module. (Needed only for BEA Simple Events API applications.)
Files needed only for CosNotification Service API applications:
  File: CosEventChannelAdmin.idl
    Description: The OMG IDL code that declares the CosEventChannelAdmin module.
  File: CosNotifyFilter.idl
    Description: The OMG IDL code that declares the CosNotifyFilter module.
  File: CosNotifyChannelAdmin.idl
    Description: The OMG IDL code that declares the CosNotifyChannelAdmin module.
  File: Tobj_Notification.idl
    Description: The OMG IDL code that declares the Tobj_Notification module.
```

--------------------------------

### Prepare and Navigate for Gateway Installation on UNIX

Source: https://docs.oracle.com/cd/E12531_01/index.htm/tma_sna91/eamig/eamig2

This sequence of shell commands guides the user through the initial setup steps for installing the Tuxedo Mainframe Adapter for SNA Gateway. It includes logging in as the root user, mounting the installation CD-ROM, changing the directory to the mounted media, and listing its contents to identify the installer binary. Specific mount commands may vary by system.

```Shell
$ su -\nPassword:
```

```Shell
# mount -r -F cdfs /dev/cdrom/c1b0t0l0 /mnt
```

```Shell
# cd /mnt/
```

```Shell
# ls
```

--------------------------------

### Start Alternate Network Driver (Windows Batch)

Source: https://docs.oracle.com/cd/E12531_01/index.htm/msgq50/wincli/4using

This command line example shows how to start an alternate network driver, `ewrk3.com`, typically by adding it to a batch file like `lanwp.bat` after installing LAN Workplace on Novell networks. This is necessary if the driver was not provided by LAN Workplace directly.

```Batch
c:\net\nwclient\ewrk3.com
```

--------------------------------

### Locating and Copying Transactions Sample Application Files

Source: https://docs.oracle.com/cd/E12531_01/index.htm/tuxedo100/usamples/transactions

Instructions on where to find the Transactions sample application files on Windows and UNIX systems, and the requirement to copy them along with the 'utils' directory to a designated work directory for setup.

```cmd
drive:\TUXDIR\samples\corba\university\transaction
```

```bash
/usr/TUXDIR/samples/corba/university/transaction
```

--------------------------------

### Basic corbaloc and corbalocs URL Examples

Source: https://docs.oracle.com/cd/E12531_01/index.htm/tuxedo100/CORBA_ref/boot

Examples demonstrating the basic structure of `corbaloc` and `corbalocs` URLs, including multiple host and port combinations for specifying IIOP Listener/Handler locations.

```URL Syntax
corbaloc://curly:1024,larry:1022,joe:1999
corbalocs://host1:1024,{host2:1022|host3:1999}
```

--------------------------------

### Start and Stop CORBA Server Application

Source: https://docs.oracle.com/cd/E12531_01/index.htm/tuxedo100/usamples/transactions

Manages the lifecycle of the CORBA server application and its associated system processes (e.g., TMSYSEVT, TMFFNAME, TMIFSRVR, univt_server, ISL) using `tmboot` to start and `tmshutdown` to stop. These commands control the entire server environment for the Transactions sample.

```Shell
tmboot -y
```

```Shell
tmshutdown
```

--------------------------------

### Initialize University Database for Wrapper Sample Application

Source: https://docs.oracle.com/cd/E12531_01/index.htm/tuxedo100/usamples/wrapper

This snippet shows the commands to initialize the University database used by the Wrapper sample application. The process differs slightly between Windows (using nmake) and UNIX (using make).

```Batch
nmake -f makefilew.nt initdb
```

```Shell
make -f makefilew.mk initdb
```

--------------------------------

### Start CRM with Detailed Tracing and APPC Stack API Tracing on UNIX

Source: https://docs.oracle.com/cd/E12531_01/index.htm/tma_sna91/crm/chap2

Shows a command-line example for starting the `CRM` process on UNIX with detailed tracing (level 2) and APPC Stack API tracing enabled. The command specifies the host and port address for the CRM.

```Shell
CRM -t 2 -s //myhost:5587
```

--------------------------------

### Initializing University Database for Transactions Sample Application

Source: https://docs.oracle.com/cd/E12531_01/index.htm/tuxedo100/usamples/transactions

Commands to initialize the University database that is used by the Transactions sample application, with specific instructions for both Windows (using nmake) and UNIX (using make).

```cmd
nmake -f makefilet.nt initdb
```

```bash
make -f makefilet.mk initdb
```

--------------------------------

### Example Server Startup Options from tmboot

Source: https://docs.oracle.com/cd/E12531_01/index.htm/tuxedo100/pgc/pgerr

Shows an example of command-line options passed to a server's `main()` by the `tmboot` command. These options are crucial for manually running a server under `dbx`.

```Shell
exec server -g 1 -i 1 -u sfmax -U /tuxdir/appdir/ULOG -m 0 -A
```

--------------------------------

### Install MessageQ LU6.2 Services on OpenVMS Alpha

Source: https://docs.oracle.com/cd/E12531_01/index.htm/msgq50/lu62inst/chap1

This snippet illustrates a complete interactive installation session for MessageQ LU6.2 Services on an OpenVMS Alpha system. It includes initial setup commands, running the VMSINSTAL utility, and responding to various prompts for system backup, file purging, IVP execution, directory tree location, and MessageQ queue numbers for user callback and port server.

```DCL
$ @dka300:[dmq$v40.exe]dmq$set_lnm_table 30 444

%DMQ-S-SETLNM, Set to MessageQ LNM table DMQ$LNM_0030_00444
$ @sys$update:vmsinstal MQLU62AXPA040

 OpenVMS ALPHA Software Product Installation Procedure V6.2

It is 06-JAN-1999 at 14:43.

Enter a question mark (?) at any time for help.
* Are you satisfied with the backup of your system disk [YES]?
The following products will be processed:

  MQLU62AXPA V4.0

 Beginning installation of MQLU62AXPA V4.0 at 14:43

%VMSINSTAL-I-RESTORE, Restoring product save set A ...
%VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.

     **************************************************************
     *                                                            *
     *     BEA MessageQ for OpenVMS AXP LU6.2 Services V4.0A      *
     *                                                            *
     *                                                            *
     *                   Installation Procedure                   *
     *                                                            *
     *                                                            *
     *               Copyright BEA System, Inc., 1999.            *
     *                   All rights reserved.                     *
     *                                                            *
     *                                                            *
     * Restricted Rights: Use, duplication, or disclosure by the  *
     * U.S. Government is subject to restrictions as set forth in *
     * subparagraph (c)(1)(ii) of DFARS 252.227-7013, or in FAR   *
     * 52.227-19, or in FAR 52.227-14 Alt. III, as applicable.    *
     *                                                            *
     * This software is proprietary to and embodies the           *
     * confidential technology of BEA Systems, Inc.               *


     *                                                            *
     **************************************************************

%MQLU62AXPA-I-DMQOK, MessageQ is present on this system
* Do you want to purge files replaced by this installation [YES]?
* Do you want to run the IVP after the installation [YES]?
* Where do you want the MessageQ LU6.2 Directory Tree built [DMQ$DISK:]: 

    MessageQ LU6.2 is installed by default at Queue Number 62.
    This may not be acceptable at your site.

* Queue Number for the MessageQ LU6.2 User Callback [62]: 

    The MessageQ LU6.2 Port Server is installed by default at Queue
    Number 63.  This may not be acceptable at your site.

* Queue Number for the MessageQ LU6.2 Port Server [63]: 

  A MessageQ Customized User Area has been found in the
  current MessageQ Group

* Do you want to add the MessageQ LU6.2 Definitions to this Group [Y]?
%MQLU62AXPA-I-CHECKLU62, Checking for previous MessageQ LU6.2 installation...
%MQLU62AXPA-I-CHECKLU62, ...ignore any SEARCH-I-NOMATCH messages.
%SEARCH-I-NOMATCHES, no strings matched

     =======================================================================
     All questions regarding the installation of MessageQ for OpenVMS AXP
     LU6.2 Services have now been asked.  The installation will continue for
     approximately 5-10 minutes, depending on load, CPU type and kit media.
     =======================================================================

*
* MessageQ for OpenVMS LU6.2 Services
*
PAMS_LU62               62 1000000 1000 None   .    .
```

--------------------------------

### Secure Simpapp Sample Application File Components Overview

Source: https://docs.oracle.com/cd/E12531_01/index.htm/tuxedo100/security/samples

This section provides an overview of the core files included in the Secure Simpapp sample application, detailing their purpose, associated programming languages, and build system relevance.

```APIDOC
File Components:
  Simple.idl: The OMG IDL code that declares the Simple and SimpleFactory interfaces.
  Simples.cpp: The C++ source code that overrides the default Server::initialize and Server::release methods.
  Simplec.cpp: The source code for the CORBA C++ client application in the Secure Simpapp sample application.
  Simple_i.cpp: The C++ source code that implements the Simple and SimpleFactory methods.
  Simple_i.h: The C++ header file that defines the implementation of the Simple and SimpleFactory methods.
  Readme.html: This file provides the latest information about building and running the Secure Simpapp sample application.
  runme.cmd: The Windows 2003 batch file that builds and runs the Secure Simpapp sample application.
  runme.ksh: The UNIX Korn shell script that builds and executes the Secure Simpapp sample application.
  makefile.mk: The makefile for the Secure Simpapp sample application on the UNIX operating system. This file is used to manually build the Secure Simpapp sample application. Refer to the Readme.html file for information about manually building the Secure Simpapp sample application. The UNIX make command needs to be in the path of your machine.
  makefiles.nt: The makefile for the Secure Simpapp sample application on the Windows 2003 operating system. This makefile can be used directly by the Visual C++ nmake command. This file is used to manually build the Secure Simpapp sample application. Refer to the Readme.html file for information about manually building the Secure Simpapp sample application. The Windows 2003 nmake command needs to be in the path of your machine.
```

--------------------------------

### Start CORBA C++ Client Application

Source: https://docs.oracle.com/cd/E12531_01/index.htm/tuxedo100/usamples/transactions

Launches the CORBA C++ client application for the Transactions sample. Upon execution, the client will prompt the user for a student ID and a domain password to proceed with interaction.

```Shell
univt_client
```

--------------------------------

### Selecting BEA MessageQ Packages to Install

Source: https://docs.oracle.com/cd/E12531_01/index.htm/msgq50/unixcli/2install

This section shows the interactive process of selecting which components of BEA MessageQ 5.0 to install. The system lists available packages, and the user inputs their choice, typically '1' for the core MessageQ system.

```CLI
  1    msgq           BEA MessageQ
  2     msgqdoc         BEA MessageQ Online Documentation
```

```CLI
Select the package(s) you wish to install (or 'all' to install
all packages) (default: all) [?,??,q]: 1
```

--------------------------------

### Windows Sample Application File Paths

Source: https://docs.oracle.com/cd/E12531_01/index.htm/tuxedo100/notify/int_samp

Specifies the directory paths for the C++ Introductory sample application and common files on Windows systems, which need to be copied to a local work directory.

```Batch
drive:\tuxdir\samples\corba\notification\introductory_simple_cxx
```

```Batch
drive:\tuxdir\samples\corba\notification\common
```

--------------------------------

### UNIX CD-ROM Device Listing and Output

Source: https://docs.oracle.com/cd/E12531_01/index.htm/tma_tcp91/install/insttux

Command to list details of the CD-ROM device on a UNIX system, along with an example of the expected output, to identify the correct device path for mounting.

```Shell
> ls -l /dev/cdrom
```

```Text
total 0
brw-rw-rw-     1 root     sys     22,   0 July 1 10:55 c1b0t010
```

--------------------------------

### Message Recovery Services (MRS) Configuration Prompt Example

Source: https://docs.oracle.com/cd/E12531_01/index.htm/msgq50/vmscli/3config

Illustrates an interactive command-line interface (CLI) prompt for configuring Message Recovery Services (MRS) in the BEA MessageQ Client. This example shows various options like journal file directory, size, and block cycling, along with their default values, guiding the user through the setup process.

```Configuration
MRS Configuration
  MRS Enabled (yes/no) [yes]:
  Journal File Directory []:
  Journal File Size (bytes) [48000]:
  Cycle Journal File Blocks (yes/no) [yes]: n
  Fixed Size Journal File (yes/no) [yes]:
  Preallocate Journal File (yes/no) [yes]:
```

--------------------------------

### Start Introductory Reporter Application

Source: https://docs.oracle.com/cd/E12531_01/index.htm/tuxedo100/notify/int_samp

Command to launch the C++-based Reporter application. This application is responsible for posting events to the Tuxedo system, making them available for subscribers.

```Shell
is_reporter
```

--------------------------------

### Specify BEA MessageQ Installation Path and Verify Disk Space

Source: https://docs.oracle.com/cd/E12531_01/index.htm/msgq50/unixic/3one

Guides the user in specifying the desired installation directory for BEA MessageQ files. The system then automatically checks for sufficient disk space and proceeds with file creation and permission setting.

```Console
Directory where BEA M3 files are installed [?,q]: /opt/messageq
Creating /opt/messageq
```

```Console
Determining if sufficient space is available ...
11794 blocks are required
6186634 blocks are available to /opt/messageq
```

```Console
Using /opt/messageq as the installation base directory
.
.
.
Changing file permissions...
.. finished
```

--------------------------------

### Build BEA MessageQ MQSeries Examples on Windows NT

Source: https://docs.oracle.com/cd/E12531_01/index.htm/msgq50/mqscgde/aprog

Instructions to compile the BEA MessageQ MQSeries Connection programming examples on Windows NT systems using the `nmake` utility and the provided makefile. This command should be executed from the example directory.

```Shell
nmake -f mqsc.mak
```

--------------------------------

### Boot BEA Tuxedo System

Source: https://docs.oracle.com/cd/E12531_01/index.htm/tuxedo100/notify/int_samp

Command to start the BEA Tuxedo system, which initializes essential server processes such as `TMSUSREVT`, `TMNTS`, `TMNTSFWD_T`, and `ISL` for event handling and IIOP communication.

```Shell
tmboot -y
```

--------------------------------

### BEA SALT Console Uninstallation Process Example (UNIX)

Source: https://docs.oracle.com/cd/E12531_01/index.htm/salt20/install/instpost

Displays a typical interactive console output during the uninstallation of BEA SALT 2.0 on a UNIX system. It shows the prompts, progress indicators, and the final completion message.

```Console Output
Preparing CONSOLE Uninstall...
=================================================================

About to uninstall...

SALT 2.0 for Tuxedo 9.1

This will remove features installed by InstallAnywhere.  It will not remove files and folders created after the installation.

PRESS <ENTER> TO BEGIN THE UNINSTALL, OR 'QUIT' TO EXIT THE UNINSTALLER: <ENTER>
=================================================================

Uninstalling...
---------------

...*
*
*************************
*************************
*************************
************************
...*

Uninstall Complete
------------------

All items were successfully uninstalled.

PRESS <ENTER> TO EXIT THE UNINSTALLER: <ENTER>
```

--------------------------------

### VMSINSTAL Initial Installation Output

Source: https://docs.oracle.com/cd/E12531_01/index.htm/msgq50/vmsinst/chap2

This output shows the initial messages displayed by VMSINSTAL when it begins the installation process. It confirms the product being processed, the start time, and indicates the restoration of product save sets and relocation of release notes.

```VMS Console Output
The following products will be processed:

  MQAXP V5.0

 	Beginning installation of MQAXP V5.0 at 14:45

%VMSINSTAL-I-RESTORE, Restoring product save set A ...
%VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP
```

--------------------------------

### Start BEA SALT Console Uninstaller (UNIX)

Source: https://docs.oracle.com/cd/E12531_01/index.htm/salt20/install/instpost

Executes the BEA SALT 2.0 uninstallation program in interactive console mode on a UNIX system. The `-i console` flag specifies the console interface for the uninstallation process.

```UNIX Shell
<bea/home> sh Uninstall_SALT_2.0_for_Tuxedo_9.1 -i console
```

--------------------------------

### Example: Starting SNMP Integrator with Specific IP Binding

Source: https://docs.oracle.com/cd/E12531_01/index.htm/tuxedo100/snmpadmin/8agincom

An example demonstrating how to start the `snmp_integrator` command, binding it to a specific IP address to monitor incoming SNMP requests only from that address.

```Shell
snmp_integrator -b 130.86.23.1
```

--------------------------------

### HP-UX Tuxedo 9.1 Required Patches Warning

Source: https://docs.oracle.com/cd/E12531_01/index.htm/tma_ositp91/ositpig/instal

This warning message may appear during installation on HP machines if required patches for Tuxedo 9.1 are missing. It advises the user to refer to the Tuxedo 9.1 Installation Guide or a specific URL for more information. Users should exit the installation if this warning appears and address the patch requirements.

```Shell
===================================================
You do NOT HAVE required HP Patches for Tuxedo 9.1
Please refer to the Tuxedo 9.1 Installation Guide
or http://edocs.bea.com/tuxedo/tux90/install/inspds.htm#1318335
for more information.

Continue Installation? [y/n]:
```

--------------------------------

### BEA Tuxedo CORBA Application Development Process Steps

Source: https://docs.oracle.com/cd/E12531_01/index.htm/tuxedo100/getstart/build

This outlines the sequential steps required to develop, compile, and deploy BEA Tuxedo CORBA applications, from IDL definition to application startup. It serves as a high-level process guide for developers.

```APIDOC
Development Process for BEA Tuxedo CORBA Applications:
  1. Write the Object Management Group (OMG) Interface Definition Language (IDL) code for each CORBA interface you want to use in your BEA Tuxedo application.
  2. Generate the CORBA client stubs and the skeletons.
  3. Write the CORBA server application.
  4. Write the CORBA client application.
  5. Create an XA resource manager.
  6. Create a configuration file.
  7. Create a TUXCONFIG file.
  8. Compile the CORBA server application.
  9. Compile the CORBA client application.
  10. Start the BEA Tuxedo CORBA application.
```

--------------------------------

### UNIX Sample Application File Paths

Source: https://docs.oracle.com/cd/E12531_01/index.htm/tuxedo100/notify/int_samp

Specifies the directory paths for the C++ Introductory sample application and common files on UNIX systems, which need to be copied to a local work directory.

```Shell
/usr/local/tuxdir/samples/corba/notification/introductory_simple_cxx
```

```Shell
/usr/local/tuxdir/samples/corba/notification/common
```

--------------------------------

### Example corbaloc and corbalocs URLs

Source: https://docs.oracle.com/cd/E12531_01/index.htm/tuxedo100/CORBA_ref/boot

Illustrative examples demonstrating the construction and usage of corbaloc and corbalocs URLs, including variations with multiple addresses, versioning, and IP addresses.

```URL
corbaloc::555xyz.com:1024,555backup.com:1022,555last.com:1999
corbalocs::555xyz.com:1024,{555backup.com:1022|555last.com:1999}
corbaloc::1.2@555xyz.com:1111
corbalocs::1.1@24.128.122.32:1011,1.0@24.128.122.34
```

--------------------------------

### Build Xerces-C++ Samples on Unix

Source: https://docs.oracle.com/cd/E12531_01/index.htm/tuxedo100/xmlparser/html/build-winunix

This snippet outlines the standard procedure to compile the Xerces-C++ samples on a Unix-like system. It involves navigating to the samples directory, executing the `runConfigure` script with platform and compiler specifications, and then initiating the build process using `gmake`.

```bash
cd xerces-c2_5_0-linux/samples
./runConfigure -p<platform> -c<C_compiler> -x<C++_compiler>
gmake
```

--------------------------------

### Verify TUXCONFIG File Creation

Source: https://docs.oracle.com/cd/E12531_01/index.htm/tuxedo100/tutor/tutsi

Shows how to use the `ls -l` command to verify that the `tuxconfig` file has been created after loading the `ubbsimple` configuration. This confirms the successful setup of the BEA Tuxedo system file.

```shell
$ ls -l
total 216
-rwxr-x--x 1 usrid grpid 313091    May 28 15:41 simpcl
-rw-r----- 1 usrid grpid   1064    May 28 07:51 simpcl.c
-rwxr-x--x 1 usrid grpid 358369    May 29 09:00 simpserv
-rw-r----- 1 usrid grpid    275    May 28 08:57 simpserv.c
-rw-r----- 1 usrid grpid 106496    May 29 09:27 tuxconfig
-rw-r----- 1 usrid grpid    382    May 29 09:26 ubbsimple
```

--------------------------------

### Execute SALT 2.0 Console Mode Installer

Source: https://docs.oracle.com/cd/E12531_01/index.htm/salt20/install/instcon

Initiates the SALT 2.0 for Tuxedo 9.1 installation in console mode on a HPUX 11 PA system using the provided installer binary.

```Shell
sh salt20_tux91_32_hpux_11_pa.bin -i console
```