s tlm qi installation guide

8/10/2019 s Tlm Qi Installation Guide

1/32

TLM Reconciliations Version 2 . 7 SP1

STLMQI In stallation Guide


2/32


3/32

Contents iii

Contents About this guide .................................................................................. 1

Who should read this guide? .................................................... ..................................... 1 About STLMQI .................................................................................................... ........ 1 How is this guide organised? ................................................... ..................................... 1 Conventions used in this guide ................................................................... .................. 2

Prerequis ites ........................................................................................ 3

UNIX requirements ................................... ........................................................... ........ 3

Windows requirements .................................................. ............................................... 3

Running STLMQI on the client .................................................................. .................. 4 Configuring queue access .................................................... ........................... 4

Running STLMQI on the server ......................................................... .......................... 5 Configuring queue manager access on UNIX ....................................................... ........ 5

Solaris UNIX configurations .......................................................................... 5 STLMQI Working folder set ...................................................................... .................. 7 Potential Issues ..................................................................................................... ........ 7

Instal ling STLMQI................................................................................. 9

Installing on Unix ....................................................................................... .................. 9 Pre TLM 2.5 ................................................................................................... 9 Potential Issues ......................................................... .................................... 10

TLM 2.5 Onwards ............................................................................ .......................... 10 Installing on Windows .................................................. .............................................. 11

Pre TLM 2.5 ................................................................................................. 11 TLM 2.5 Onwards ........................................................................................ 11

Appl ying the STLMQC Configuration Tool ...................................... 13

Running STLMQI ................................................................................ 15

MODE PUT ......................................................... ....................................................... 15 MODE GET ........................................................ ........................................................ 15 Running MODE GET and Report Matcher (STELINK Only) ................................... 16

On Unix ........................................................... ............................................. 16

On Windows .................................................... ............................................. 16 Potential Issues ..................................................................................................... ...... 17

Appendix A - Install ing the STLMQI Cli ent ...................................... 19

Appendix B - SYST Sett ings For STLMQI ........................................ 21

STLMQI_MODE definitions .................................................. .................................... 21 STLMQI_MODE mappings .................................................... ................................... 21

Appendix C - Test ing MQ Connectivi ty On MQ cl ient ..................... 25

Software Support ............................................................................... 27 Calling SmartStream Technologies Support ......................................................... ...... 27


4/32

iv Contents

Before you call... .................................................. ....................................................... 28


5/32

About this guide 1

About this guide

Welcome to the STLMQI Installation Guide.

Who should read this guide?This guide is aimed at users responsible for installing the STLMQI Interface toIBM MQ.

About STLMQISTLMQI is the SmartStream interface to IBM MQ. It uses the standard loggingfunctions employed by existing SmartStream server engines and retrieves itsreference data from the SYST table.

Depending on the modes defined by the SYST Settings, the server performs thefollowing operations:

Obtains files dependent on mask or extension, that contain multiplemessages from a specified folder. The messages from these files are placedon individual message queues and then validated to ensure that they are onthe correct queue.

Retrieves messages from specified queues the messages retrieved are then built into files containing a specified number of messages, to a locationdefined in the SYST table.

Requests PAN (Positive Acknowledgment) or NAN (NegativeAcknowledgment) messages and reconciles these with the messages sent areport containing this information is then sent to a specified MQ reportqueue.

It is always assumed that all messages have a known termination character orstring and that they can be offered to STLMQI within files of a specificextension.

How is this guide organised?This guide describes the standard installation of STLMQI and is divided into thefollowing sections:

Pre-requisites (p 3) describes the conditions that must be met beforeinstalling STLMQI on Windows or UNIX, and how to configure the IBMMQ client.

Installing STLMQI (p 9) describes how to install STLMQI and provides alist of known installation issues and how they are resolved.

STLMQC describes the STLMQI configuration tool and how it is run.

Running STLMQI (p 15) describes how to run STLMQI and the utilities process flow.


6/32

2 Conventions used in this guide

Appendix A - Installing a client (p 19) describes how to install anSTLMQI Client on a separate machine from the server.

Appendix B - SYST settings for STLMQI (p 21) describes the SYSTsettings required by STLMQI.

Appendix C - Testing MQ connectivity on the MQ client (p 23) describesthe MQ connectivity testing process.

Software Support (p 27) includes contact details for SmartStreamTechnologies Support.

Conventions used in this guideThis guide uses the following conventions for menus and shortcuts:Example Describes

Pressing the Enter key

Holding down the Control key and pressing the Home

keyCurrent View > Orientation> Horizontal

Choosing the Horizontal option from the Orientationsubmenu of the Current View option

Click Clicking the left mouse button

Right-click Clicking the right mouse button

Double-click Clicking the left mouse button twice in rapid succession

Click [Cancel] Clicking the Cancel button displayed in the window

Replace the chevrons and italicised text with the realdatabase name.


7/32

Prerequisites 3

Prerequisites

The following sections describe the prerequisites that must be met before youcan install STLMQI on UNIX and Windows, and how to configure the MQCHANNEL required by STLMQI to access queues.

You must ensure that MQ is configured with at least one queue managercontaining at least two queues, before starting the STLMQI installation process.

In the examples used in this guide, the queue manager is called QM_STLMQIand the queues are called INPUT and OUTPUT. If you use names other thanthese, you must ensure that you replace the names in the examples with the ones

you have specified.

UNIX requirementsThe conditions required for installing STLMQI on UNIX depend on the versionof TLM you are running.

Requirements f or Pre TLM 2.5

A standard STL winaenv Unix build environment with IBM MQSeries(WebSphere MQ) version 5.2 or later installed.

Access to the STL Product database. Suitable access rights to the build environment to enable you to copy the

source and build files to their appropriate directories and modify files asnecessary.

Requirements for TLM 2.5 Onwards

A standard STL Unix install environment with IBM MQSeries (WebSphereMQ) version 6.0 or later installed.

Access to the STL Product database.

Suitable access rights to copy the binaries to their appropriate directories

and to execute them.

Windows requirementsThe conditions required for installing STLMQI on Windows depend on theversion of TLM you are running.

Requirements for pr e TLM 2.5

A standard STL Windows install environment with the environmentvariable SSRDIR set up.

IBM MQSeries (WebSphere MQ) Version 5.2 or later and access to theSTL Product database.


8/32

4 Running STLMQI on the client

Suitable access rights to copy the applications to their appropriatedirectories and execute them.

Requirements for TLM 2.5 Onwards

A standard STL Windows install environment with the environment

variable TLM_HOME set up. IBM MQSeries (WebSphere MQ) Version 6.0 or later and access to the

STL Product database.

Suitable access rights to copy the applications to their appropriatedirectories and execute them.

Running STLMQI on the clientIf you want to run STLMQI on the client machine, you must first ensure thatIBM MQSERIES is installed (p 19) and that it has access to at least one queuemanager that contains one or more queues.

Configuring queue accessYou can grant STLMQI access to queues via an MQ CHANNEL, that isspecified in the MQSERVER environment variable.

The MQSERVER variable requires the following information:

The server connection channel

Connection type, for example TCP/IP

Host name or IP Address

Listener port required unless the MQ listener port is the default (1414), inwhich case it does not need to be included in the environment variable.

To configure MQSERVER for UNIX

Specify the following configuration from the command line:export

/ < connection type >/ < host name /IP >( < listener port >)

For example:expor t MQSERVER=SYST. TLM. SVRCONN/ TCP/ gser ver ( 16500)

It is recommended that you add this line to a start-up file such as the .profilefile on UNIX.

To conf igure MQSERVER for Windows

Specify the following configuration from the command line:set MQSERVER=/ / ( )

For example:set MQSERVER=SYST. TLM. SVRCONN/ TCP/ gser ver ( 16500)


9/32

Prerequisites 5

Running STLMQI on the serverTo run the standard configuration of STLMQI on the server, you must installSTLMQI on the same machine as the MQ Server Manager it is accessing.

Configuring queue manager access on UNIX

Solaris UNIX configurationsFor SOLARIS UNIX configurations only, STLMQI requires authorisation toaccess the queue manager.

The following sections summarise the authorisations required to get started withIBM MQ. For further information, refer to the MQ User Manuals.

Configuring the STLMQI User

The run user for STLMQI must be a member of the mqm user group and isusually the user responsible for installing or administering IBM MQ, forexample, the. mqm user.

Configuring basic access contro lFor basic access control to a given queue manager, the following entries may berequired:

setmqaut m QM_STLMQI t qmgr g mqm +all. For example:

setmqaut m QM_STLMQI n INPUT t q g mqm +all

setmqaut m QM_STLMQI n OUTPUT t q g mqm +all

The parameters are as follows: -m - the Queue Manager Name.

-n - the Queue Name.

-t - the Object Type (qmgr Queue Manager, q Queue).

-g - the Group to assign the Auth Rights to.

+all - the Auth Rights (+all gives all rights, -all would remove all rights).


10/32

6 Configuring queue manager access on UNIX

Displaying the authorisation settingsYou can display the current authorisation settings by entering the followingcommands (shown with example output for a QMgr and Queues with AuthRights set to all):

Command Authorisations settingdspmqaut -m QM_STLMQI -t qmgr -g mqm inq

set

connect

altusr

crt

dlt

chg

dsp

setid

setalldspmqaut -m QM_STLMQI -n INPUT -t q -g mqm get

browse

put

inq

set

crt

dlt

chg

dsp

passid passall

setid

setall

clr

dspmqaut -m QM_STLMQI -n OUTPUT -t q -g mqm get

browse

put

inq

set

crtdlt

chg

dsp

passid

passall

setid

setall

clr


11/32

Prerequisites 7

STLMQI Working folder setThe table below outlines the directory structure required for STLMQI, where is the path as entered into the SYST table entry.

See Applying the STLMQC Configuration Tool (p13) and Appendix B - SYST

Settings For STLMQI (p21) for further information.

Directory Use Additional Info

/swift_in Messages files to be put on the MQQUEUE_OUT

Used byPUT

process

/messages_in Temporary workingdirectory

DO NOTUSE

/messages_out Temporary workingdirectory

DO NOTUSE

/swift_out Message files createdfrom the messages

collected from the MQQUEUE_IN

Used byGET

process

/sent Copies of messages being put on the MQQUEUE_OUT

Used byPUT

process

/used Copies of the messagefiles being put on theMQ QUEUE_OUT

Used byPUT

process

You must configure a different working folder directory for each instance ofSTLMQI that you want to run, to prevent any potential conflicts.

Potential IssuesAll Queue Manager and Queues must be created on MQ with upper case namesand entered into the STLMQI configuration in upper case. This is due toinconsistencies across platforms with the IBM MQ (WebSphere MQ) SeriesMQCONN API Call.

Issues might also arise when running multiple instances of STLMQI that areconfigured to use the same workfolders. As such, you must ensure that youconfigure a different working folder set for each instance of STLMQI.


12/32

8 Potential Issues


13/32

Installing STLMQI 9

Installing STLMQI

The following sections describe how to install STLMQI. The installation processvaries depending on which operating system and version of TLM you arerunning.

Installing on UnixThe instructions in this section describe how to install STLMQI on UNIX. This

process varies depending on which version of TLM you are running.

Pre TLM 2.5This section describes how to install STLMQI on UNIX for versions of TLM

prior to 2.5.

To ins tall STLMQI

1. Stop any existing instances of STLMQI.

2. Backup the original source files, as follows:mv $WI NAREL/ bui l d/ i ncl ude/ st l mqi . h$WI NAREL/ bui l d/ i ncl ude/ st l mqi _ol d. h

mv $WI NAREL/ bui l d/ t ool box/ sr c/ st l mql . sc$WI NAREL/ t ool box/ sr c/ st l mql _ol d. sc

mv $WI NAREL/ bui l d/ pr g/ sr c/ st l mqi _s. sc$WI NAREL/ bui l d/ pr g/ sr c/ st l mqi _s_ol d. sc

mv $WI NAREL/ bui l d/ pr g/ sr c/ st l mqc. sc$WI NAREL/ bui l d/ pr g/ sr cst l mqc_ol d. sc

3. Copy the new code to its required locations. For example:mv . / st l mqi . h $WI NAREL/ bui l d/ i ncl ude/ st l mqi . h

mv . / st l mql . sc $WI NAREL/ t ool box/ sr c/ st l mql . sc

mv . / st l mqi _s. sc $WI NAREL/ bui l d/ pr g/ sr c/ st l mqi _s. sc

mv . / st l mqc. sc $WI NAREL/ bui l d/ pr g/ sr cst l mqc. sc

4. Check that the build configuration file buildcfg contains the entriesnecessary to build stlmqi.

If this is not the first time that stlmqi has been built on this machine thismight not be necessary.

5. Check that the IBM MQ library paths are correctly set as required in thewinaenv file.

6. Build both the config tool stlmqc, and the appropriate engine, stlmqi_s forserver MQ installs, or stlmqi_c for client MQ installs. For example:


14/32

10 TLM 2.5 Onwards

bui l d t ool box st l mql i b

bui l d st l mqc

bui l d st l mqi _s

7. Check that the STLMQI folder set has been created as shown in STLMQIWorking folder set (p7).

8. Restart STLMQI after making any required configuration changes.

Potential IssuesWhen installing STLMQI, a link error has been known to occur, which can causethe following error message to be displayed:

l d: f at al : f i l e/ app/ or a101/ pr oduct/ 10. 1. 0/ db_1/ l i b/ l i bcl nt sh. so: wr ong ELFcl ass: ELFCLASS64

Link Errors are caused by attempting to link to a mix of 32 bit and 64 bitlibraries. As such, if either the database or MQ are 32 bit then you can fix thisissue by ensuring that the build only links to 32 bit libraries.

TLM 2.5 OnwardsThis section describes how to install STLMQI on UNIX for TLM 2.5 onwards.

To ins tall STLMQI

1. Stop any instances of STLMQI if necessary.

2. Backup the original binaries if they exist:

mv $TLM_HOME/ bi n/ st l mqc $TLM_HOME/ bi n/ st l mqc_ol d

mv $TLM_HOME/ bi n/ st l mqi _s $TLM_HOME/ bi n/ st l mqi _s _ ol d

mv $TLM_HOME/ bi n/ st l mqi _c $TLM_HOME/ bi n/ st l mqi _c_ ol d

3. Copy the new binaries to their required location:

mv . / st l mqc $TLM_HOME/ bi n/ st l mqc

mv . / st l mqi _s $TLM_HOME/ bi n/ st l mqi _s

mv . / st l mqi _c $TLM_HOME/ bi n/ st l mqi _c

4. Check that the IBM MQ library paths are correctly set so that stlmqi canfind the appropriate library, libmqm.so for Server MQ installs andlibmqic.so for Client MQ installs. For TLM 2.5 onwards only 64 bit librariesmay be used.

5. Ensure that the STLMQI folder set has been created as shown in the sectionSTLMQI Working folder set (p7).

6. Restart STLMQI after making any required configuration changes.


15/32

Installing STLMQI 11

Installing on WindowsThe instructions in this section describe how to install STLMQI on Windows.This process varies depending on which version of TLM you are running.

Pre TLM 2.5This section describes how to install STLMQI on Windows for versions of TLM

prior to 2.5.

To ins tall STLMQI

1. Stop any existing instances of STLMQI.

2. Backup any existing instances of stlmqc.exe and stlmqi_s.exe in the%SSRDIR%\Release\Bin directory.

3. Copy the executable files into %SSRDIR%\Release\Bin.

4. After making any necessary configuration changes, restart stlmqi.

TLM 2.5 Onwards1. Stop any existing instances of stlmqi.

2. Backup any existing instances of stlmqc.exe, stlmqi_s.exe and stlmqi_c.exein the %TLM_HOME%\Release\Bin directory.

3. Copy the executable files into the %TLM_HOME%\Release\Bin directory.

4. After making any necessary configuration changes, restart stlmqi.


16/32


17/32

Applying the STLMQC Configuration Tool 13

Applying the STLMQC ConfigurationTool

Once you have installed STLMQI, you can create a new server instance usingthe STLMQC configuration tool. This tool is launched from the command lineand contains a number of settings which you must configure.

To create a new server instance

1. To start STLMQC, open a command prompt and enter the following:st l mqc

The system prompts you for your database user name and password.

2. Enter your username and password to proceed.

The Main Menu is displayed:

STLMQI Conf i gurat i on.

Mai n Menu

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

1 - Add i nst ance.2 - Remove i nst ance.

3 - Modi f y i nst ance.

4 - Show al l .

5 - Wr i t e t o f i l e.

6 - Exi t .

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

Ent er opt i on and hi t ent er:

3. From the main menu, enter 1 to add an instance.A set of configuration settings are displayed. For example:

NAME : MQ_UNI T_ OF_WORK

DESCRI PTI ON : MQI : Uni t of work wi t hi n a tr ansact i on.

TYPE : I nt eger

4. Edit the values of the settings as required, or where required, leave thedefault values in place.

5. Press .

If there are more settings to configure, then the next set of settings isdisplayed.

6. Repeats steps 4-5 until you have configured all the settings.


18/32

14 Installing on Windows

When you have configured the last set of settings, the main menu isdisplayed.

7. From the main menu, select Option 4 Show all.

8. The settings that you have configured are displayed. For example:Show Al l

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

I NSTANCE 1 MODE PUT Ser ver ( 1000)

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

MQ_UNI T_OF_ WORK = 10 MQ_CAT_ MSG_NUM = 0

MQ_DI RECT_SUBMI T = 0 MQ_FI LE_FI LTER = ' dat '

MQ_GET_QUEUE_PRI = 0 MQ_GET_SWI FT_ PRI = 20

MQ_LOAD_FLAT_FI LES = 0 MQ_LOAD_MESSAGE_FEED = ' EMPTY'

MQ_LOAD_SERVER_ENG = ' EMPTY' MQ_LOAD_SERVER_I NST = 0

MQ_MSGTERM = ' - }' MQ_PUT_QUEUE_PRI = 20

MQ_PUT_SWI FT_PRI = 0 MQ_PRI ORI TY = 5

MQ_SLEEP_BUSY = 2 MQ_SLEEP_I DLE = 20

MQ_QUEUE_MANAGER = ' QM_STLMQI ' MQ_QUEUE_NAME_I N = ' EMPTY'

MQ_QUEUE_NAME_OUT = ' OUTPUT' MQ_QUEUE_WORKDI R = ' c: \ st l mqi '

MQ_LAST_SEQUENCE = 0

more ( hi t ent er) . . .

You can press the key to view the next set of settings configured.

9. If required, do the following to write this information to a file:

1. Enter 5

The Enter filename prompt is displayed.

2. Enter the name of the file and directory in which you want to write theinformation, in the format of \. For example:Ent er f i l ename : c: \ t emp\ st l mqc. l og

10. If you want to change the configuration for an instance number, enter theremove command.

This leaves an empty setting that you will be filled next time a server isadded.

11. You can enter the Modify command in the same way. This command provides the current values as defaults so that if no text is entered for anoption then the previous value is used.


19/32

Running STLMQI 15

Running STLMQI

The following diagrams show the flow of processing when running STLMQI.

MODE PUTThe following diagram displays the flow of message files in swift_in for theMODE PUT and Report Requester (STELINK Only).

MQ Queue Mgr

swift_in

stlmqi_s QUEUE_OUT

Message files

sent Individual messages Individual messages

Copies of message files

used

Figure 1: Message files in swift_in

MODE GETThe following diagram shows the flow of messages in the Input queue, forMODE GET and Report Matcher (STELINK Only).

Figure 2: Messages in Input Queue


20/32


21/32

Running STLMQI 17

Potential IssuesThe table below lists some of the possible issues that may arise and suggestionsas to how they can be resolved. If you discover any issues that are not listed here,

please report them to SmartStream Support (p 27) so they may be added to thelist.

Issue Potential Resolution

ERROR: Could not Connect to QManager Reason: 2035

Check that the user running the STLMQIApplication is in the MQM group or has suitableaccess rights to connect to an MQ Series QueueManager.

stlmqi_s: fatal: libmqm.so: openfailed: No such file or directory

Ensure that the user running the STLMQIApplication has the STL environment configuredcorrectly, especially the PATH for the MQLibraries.

ERROR: OPEN Comp 2 - Reason2085 (normally in conjunction withERROR: CLOSE Comp 2 -Reason 2019)

Ensure that the Queue Manager and Queues have been created with upper case names in MQ Seriesand the names have been in upper case using theSTLMQI configuration tool.

ERROR: Could not Connect to QManager Reason: 2059

Ensure that the queue manager has been started. Ifthe connection is from a client application, checkthe channel definitions.


22/32


23/32

Appendix A - Installing the STLMQI Client 19

Appendix A - Installing the STLMQIClient

This section describes how to install the STLMQI Client on a separate machinefrom the server.

When you install MQSeries (WebSphere MQ), a check is made for any existingMQSeries configuration files (MQS.INI). If any are located, the configurationinformation is automatically migrated to the Windows NT registry.

Otherwise, MQSeries automatically puts its configuration information directlyinto the Windows NT registry.

If you want to install the MQSeries client for Windows NT, you must first belogged on to Windows NT as an administrator.

To install MQSeries on a non-server machine

1. Start the IBM WebSphere MQ installation.

2. At theWebSphere MQ Installation Launchpad, ensure Software & NetworkPrerequisites are satisfied then select Launch WebSphere MQ Installer.

The WebSphere MQ Setup Wizard is displayed.3. Follow the prompts, ensuring that you configure the following pages asdescribed below:

License Agreement page - if you want to change the language settings,you can do so by clicking [Change Language] and selecting theappropriate language from the list displayed.

On the Setup Type page, ensure that Custom is selected then [Next].

On the Destination Folder page you may change the folder to install the program files to by selecting Change.

On the Destination Folders page you may change the folder to installthe data files to by selecting Change.

You can also change the folder to install the log files to by selectingChange.

On the Features page, ensure the appropriate features are selected /deselected as shown:


24/32

20 Potential Issues

When you have reached the end of the configuration pages, the Ready To

Install page is displayed, and lists the selected configuration options.4. Check your configuration settings to ensure they are as expected, and click

[Install] to proceed.

If you want to change a configuration setting, you can do so by clicking[Back].

The progress indicator shows which components are being copied and the percentage of copying completed. When the selected components have beeninstalled, the Setup Complete window is displayed.

5. Click [Finish] or press [Enter] to close the window.

6. If you want to view the release notes, you can do so by selecting [Launch Notepad.

The installation of the MQSeries client is now complete.


25/32

Appendix B - SYST Settings For STLMQI 21

Appendix B - SYST Settings ForSTLMQI

The tables in this section describe the SYST settings used by STLMQI and theirrespective values.

STLMQI_MODE definitionsThe table below summarises the STLMQI_MODE ranges and meanings:

Operation(s) SystOccurrence

Range ( Syst Value )

PUT < server no > 1000 to 1999

GET < server no > 2000 to 2999

PUTREQREP Put request feedback < server no > 3000 to 3999

GETREP Get the reports.(Replaces REPORT MODE in

previous versions).

< server no > 4000 to 4999

Important: The mode range of this version of STLMQI has been improved from10 per mode to 1000 per mode. As such, if you are upgrading from a previousversion of STLMQI, you must remove the previous SYST settings and recreatethem using the configuration program.

STLMQI_MODE mappingsSyst Name Syst Occurrence Syst String Syst Value

MQ_CAT_MSG_NUM The max number ofmessages joined as output.

MQ_DIRECT_SUBMIT Determines whether thisinstance puts entries onVQUE.

MQ_FILE_FILTER File extension to look for.For example SWF orFAX.

MQ_GET_QUEUE_PRI A value representing thenumber of times STLMQIwill pick up messages shouldany exist on the queue.

MQ_GET_SWIFT_PRI A value representing the


26/32

22 STLMQI_MODE mappings

Syst Name Syst Occurrence Syst String Syst Valuenumber of times STLMQIwill break input files intoindividual messages.

MQ_LAST_SEQUENCE (STELINK) The lastsequence number used. Valid

for the range 1 to 999999.MQ_LOAD_FLAT_FILES Removes intermediate

column headers for flat filefeeds.

MQ_LOAD_MESSAGE_FEED (VQUE) The name of thefeed. If it is a SWIFT formatfeed then leave blank,otherwise use the GEMSKB feed template name.However, if this is replacingthe fetchit process, this will

be the template namedefined for the fetchit

process, for the particularmessage type. For exampleif the message type is a flatfile securities position itcould be loaded using KBFeed Template FD_SOP.On Windows NT this may

be found using the ServerManager Fetchit FeedsDefinition. On UNIX this isspecified in the Fetchitscript. If this is a full newinstall / new message typethat is not SWIFT standard,then the feed templates willneed to be defined.

MQ_LOAD_SERVER_ENG (VQUE) The name of theserver application to be usedfor loading the entries. Forexample GEMS.

MQ_LOAD_SERVER_INST (VQUE) The instance of theserver application thatshould be used for loadingthe entries.

MQ_MSGTERM The (SWIFT) messageterminator. For example .HEX03 is used for Ctrl-C.

MQ_PUT_QUEUE_PRI The number of timesSTLMQI will attempt to place any remainingmessages on the outputqueue.

MQ_PUT_SWIFT_PRI The number of timesSTLMQI will concatenatemessages read from thequeue into files ofMQ_CAT_MSG_NUMmessages.

MQ_PRIORITY The priority of this instance.If greater than zero thensleep time is multiplied by

priority to get the actualsleep time. Default value is


27/32

23

Syst Name Syst Occurrence Syst String Syst Value0.

MQ_SLEEP_BUSY Sleep time (secs) to be usedwhen busy. If priority isgreater than zero then thisvalue is multiplied by

priority to calculate actualsleep time. Default value is1.

MQ_SLEEP_IDLE Sleep time (secs) to be usedwhen idle. If the priority isgreater than zero then thisvalue is multiplied by

priority to calculate theactual sleep time. Defaultvalue is 60.

MQ_QUEUE_MANAGER The MQ Queue Manager Name

MQ_QUEUE_NAME_IN The MQ Queue Name from

which STLMQI will getdatagrams

MQ_QUEUE_NAME_OUT The Queue Name whereSTLMQI will placedatagrams

MQ_QUEUE_WORKDIR The root of the MQworkfolders .You must specify a differentroot directory for eachinstance of STLMQI thatyou want to run.

MQ_UNIT_OF_WORK The unit of work within atransaction.

Important: In any of the priority settings above, whatever the priority of the task,the full number of iterations will only be executed if there is work left for it todo. For example messages waiting on the queue or in the workfolders.


28/32


29/32

Appendix C - Testing MQ Connectivity On MQ client 25

Appendix C - Testing MQConnectivity On MQ client

You can test the connection with the MQ Client by ensuring that the MQServerenvironment variable is correctly set. You can also use the IBM sample

programs provided to test the MQ Client in both directions by sending andretrieving some test messages.

To test the MQ Connectivity on MQ Client

1. On the client host, open a command prompt and enter the followingcommand to ensure that the MQSERVER environment variable is setcorrectly:

echo $MQSERVER

If MQSERVER is set correctly, the following line is displayed:

MQSERVER = < server connection channel > / < connection type > / < hostname / ip address >(< mq listener port> )

For example:

MQSERVER=SYST. TLM. SVRCONN/ TCP/ gser ver ( 16500)

2. If the MQSERVER environment is not displayed, or is incorrect, you willneed to go through the steps detailed in the section Pre-requisites - STLMQIrunning on the client .

For this example we'll get these same messages from the put queue that we have just written to the server. Normally these queues will be different.

To test the connection using IBM sample programs

1. In a command prompt, navigate to the /opt/mqm/samp/bin/ directory.

2. Enter the following command to put test messages to MQ server on serverhost:

. / amqsput c TLMEXM. DTG. SYS. CQ SYSDTGU0

The following message is output:

Sampl e AMQSPUT0 st ar t

t ar get queue i s TLMEXM. DTG. SYS. CQ

3. Enter the following command, where 'Test message 1' can be any text: Test mess age 1

Test mess age 2


30/32

26 STLMQI_MODE mappings

The following message is displayed and the application exits back to thecommand prompt:

Sampl e AMQSPUT0 end

4. Enter the following command to get test messages from MQ server on theother host:

. / amqsget c TLMEXM. DTG. SYS. CQ SYSDTGU0

The following messages are output before the sample program exits back to thecommand prompt:

Sampl e AMQSGET0 st ar t

message

message

no mor e messages

Sampl e AMQSGET0 end

This proves MQ client works in both directions.


31/32

Software Support 27

Software Support

More information about SmartStream Technologies software can be found in theother documentation supplied with the product. If you are unable to find theanswer to your question in any of these resources, contact SmartStreamTechnologies Support. Details are given below.

Calling SmartStream Technologies SupportBefore you call, you should consult the checklist given below, to ensure that youhave all relevant information to hand.Area Postal Address Contact Details

Europe SmartStreamTechnologies Ltd1690 Park AveAztec WestAlmondsburyBristol, BS32 4RAUK

tel: +44 (0) 1454 888485fax: +44 (0) 1454 888486email: [email protected]

North and SouthAmerica

SmartStreamTechnologies Ltd

61 BroadwaySuite 2824 New York NY 10006USA

tel: +1 212 763 6505tel (US internal): 877 215 8227

fax: +1 212 763 6501email: [email protected]

Australia and Asia SmartStreamTechnologies Ltd70 Anson Road26-01, Apex TowerSingapore079905

tel: +65 6224 7689fax: +65 6222 4039email: [email protected]


32/32

28 Before you call...

Before you call...You will be asked... Notes

Your name and yourcompany name

You must have already been registered with SmartStreamTechnologies Support Desk by your main supportcontact, otherwise the call will not be accepted

Software type: test or production?

If this is a test issue, it will be treated as a chargeable callunless a software bug is proven.

Software version number Can be found by selecting Help > About from thesoftware menu.

RDBMS Type & Version Confirm RDBMS Type (Sybase/Oracle/SQLServer) andVersion.

Server Operating System Type & Version

Confirm operating system (UNIX, Linux or Windows)and Version.

Priority of call (1 to 4) Based on business criticality.1 Unable to process any transactions.2 Partially inoperable transactions restricted3 Operational but functionally impaired4 Cosmetic problem or enquiry

Full description of problem being experienced

Please provide as much detail as possible Any supportingscreen shots, reports or server logs that may help identifyyour problem This information should be sent to yournearest support centre as listed above. Please ensure thatthe Heat call reference that you will be provided with isclearly indicated on any emails and faxes.

Can you reproduce the

problem?

Yes or No.

Has this problem occurred before?

Yes or No.

Customer Call ref.(optional)

Please provide us with your own call reference if youhave one.

s tlm qi installation guide

Documents