WebSphere MQ Workflow 3.4 Generic C API Test / Prototyping Tool

[prev][next][parent][TOC]

Running the Tool

The tool runs as a "console" application on all available platforms.
To run the tool, select one of the following command-line interfaces: See also:

Invocation Mode 1, see the following command-line help:
fmctjca1 <[path]tc fn> <[path]log fn>
or
fmctjca1 <[path]tc fn>  NoOutput
or
fmctjca1 Syntax <FileSpec>
or
fmctjca1 ApiRCs <FileSpec>
or
fmctjca1 ToolRCs <FileSpec>
or
fmctjca1 ApiMethods <FileSpec>
Abbreviations:
 tc           test case
 log          result
 fn           file name
 path         e.g. d:\data\
 FileSpec     e.g. d:\data\syntax.txt
 [...]        optional
 If no test case file name extension is specified, an extension "dat" is expected.
 If no result file name extension is specified, the tool will create an extension "log".
Invocation Example of the Test Tool as MQ Workflow Client Application :
 
fmctjca1 d:\testcase\tc01 d:\result\tc01
Invocation Example to retrieve the Test Tool Syntax:
 
fmctjca1 syntax d:\testcase\syntax.txt


Invocation Mode 2, see the following command-line help:

Note: Only for version 3.2.1 Service Pack 2 or higher.

Usage:
fmctjca1 [-option [argument] ...]

Valid option and argument combinations:
  fmctjca1 -i <> -o <> [-u <>] [-p <>] [-g <>] [-s <>] [-y <>] [-e <>] [-d]
  fmctjca1 -i <> -o nooutput [-u <>] [-p <>] [-g <>] [-s <>] [-y <>] [-e <>] [-d]
  fmctjca1 -x <>
  fmctjca1 -r <>
  fmctjca1 -a <>
  fmctjca1 -h

  The following options are valid:
  -i <TestCase>         test case input file name
  -o <Result>           test case output file name
  -u <UserID>           user id
  -p <Password>         password
  -s <System>           system name
  -g <SystemGroup>      system group name
  -y <ConfigurationID>  configuration identifier
  -e <SessionID>        session identifier
  -h                    help (this help)
  -d                    dump arguments
  -x <Syntax>           syntax output file name
  -a <ApiRc>            api rc output file
  -r <ToolRc>           tool rc output file
If you use API parameters (for example -uADMIN), also refer to the tool syntax on how to use them within an API template (Keyword: <CL-VALUE>) and see also example API parameter via command line.

NOTE: Flag -e is a not feature of the tool for MQ Workflow 3.2.2.

Invocation Example of the Tool as MQ Workflow Client Application :
 

fmctjca1 -id:\testcase\tc01.dat -od:\result\tc01.log -d


Running Parallel Tool Applications:
CAUTION :
When you invoke the Test Tool to carry out test cases in parallel, use different parameters to specify the test cases that are to be run under each invocation.
e.g.   fmctjca1 tc01a tc01a       (application A)
       fmctjca1 tc01b tc01b       (application B)


The application ends with one of the following console messages:
====== Test case ended normally ============================================
or
====== Test case ended with error(s) === +++ERROR+++ =======================
or
====== Test case break due to error(s) === +++ERROR+++ =====================
Return values:

Depending on the error type, the tool returns the following return values:
 

Error type                Return value
--------------------------------------
no error                             0
usage error                          4
error                                8
severe error                        12
user defined return code           int