$client = new Tuxedo::Admin::ud32
              (
                'TUXDIR'    => $self->{'TUXDIR'},
                'TUXCONFIG' => $self->{'TUXCONFIG'},
                'BDMCONFIG' => $self->{'BDMCONFIG'},
                'APP_PW'    => $self->{'APP_PW'}
              );

  $input_buffer{'TA_OPERATION'} = [ 'GET' ];
  $input_buffer{'TA_CLASS'}     = [ 'T_SERVER' ];

  ($error, %output_buffer) = $client->tpcall('.TMIB', \%input_buffer);

  die($client->status() . "\n") if ($error < 0);

Provides a Tuxedo client based on the ud32 utility that comes with Tuxedo. ud32 is a command-line native client that sends and receives FML32 buffers.

FML32 buffers are represented as a hash of arrays. Each hash entry is the name of an FML32 field and each hash value is an array where each element is an occurrence of that field.

The 'new' method is the object constructor. The following parameters must be provided:

TUXDIR

The directory where the Tuxedo installation is located.

TUXCONFIG

The full path to the binary application configuration file (as generated by tmloadcf).

BDMCONFIG

The full path to the binary domains configuration file (as generated by dmloadcf).

In addition the APP_PW parameter may need to be specified if the Tuxedo application requires that an application password be used.

The 'tpcall' method is used to make synchronous calls. It takes as input the name of a service and a reference to a hash of arrays that represents the input FML32 buffer. It returns an indication of whether or not the call succeeded and the output FML buffer (again represented as a hash of arrays):

  $input_buffer{'TA_OPERATION'} = [ 'GET' ];
  $input_buffer{'TA_CLASS'}     = [ 'T_SERVER' ];

  ($error, %output_buffer) = $client->tpcall('.TMIB', \%input_buffer);

If $error is negative this indicates that an error has occurred. The status() method may be used to obtain a description of the error that occurred.

Returns a description of the result of the most recent tpcall() method call.

Given an error code as input, returns a description of the error.

Below are the error codes with their corresponsing descriptions:

-1 "TAEAPP - Application component error during MIB processing"

-2 "TAECONFIG - Operating system error"

-3 "TAEINVAL - Invalid argument"

-4 "TAEOS - Operating system error"

-5 "TAEPERM - Permission error"

-6 "TAEPREIMAGE - Preimage does not match current image"

-7 "TAEPROTO - MIB specific protocol error"

-8 "TAEREQUIRED - Field value required but not present"

-9 "TAESUPPORT - Documented but unsupported feature"

-10 "TAESYSTEM - Internal System /T error"

-11 "TAEUNIQ - SET did not specify unique class instance"

0 "TAOK - Succeeded"

1 "TAUPDATED - Succeeded and updated a record"

2 "TAPARTIAL - Succeeded at master; failed elsewhere"

Keith Burdis <keith@rucus.ru.ac.za>