WebSphere MQ Workflow 3.4 Generic C API Test / Prototyping Tool

[prev][parent][TOC]

Error handling

The tool generates error messages. Most error messages are written to the result file. Some messages are also sent to stderr. The explanations of the messages and suggested actions are listed in the table below.

CAUTION:
Some of the test tool errors will cause a test tool application to terminate via an exit( ). When the test tool application is a DLL and an exit( ) occurs, then the calling application (e. g. PEA) will also be terminated.

When several error messages within one scenario occur, analyze the first message before checking any subsequent error messages. In many cases, the first error is the cause of all subsequent errors.
 
 
 
Tool Error No Explanation Suggested Action
TC0001 Cannot open input file (test case file) Check:
a) file name
b) drive letter
c) path
TC0002 Cannot open output file (result file) Check:
a) file name
b) drive letter
c) path
TC0003 Cannot open input file (file with persistent handle(s)) Check:
a) file name
b) drive letter
c) path
TC0004 Cannot open output file (persitent handle(s) result file) Check:
a) file name
b) drive letter
c) path
TC0005 Input file (test case file) is empty Check file contents
TC0006 API keyword or test tool method keyword within a test case file cannot be interpreted. Check for typos in API keyword
(see TOOL Syntax)
TC0007 Parameter value within a test case file cannot be interpreted. Check for typos (see TOOL Syntax)
TC0008 A parameter is missing within a test case file. Check for completeness of an API section (see TOOL Syntax)
TC0009 The combination of the parameters within a API section is not allowed. See TOOL Syntax
TC0010 Parameter keyword within a test case file can not be interpreted Check for typos (see TOOL Syntax)
TC0012 Invalid enumeration parameter keyword Check for typos (see TOOL Syntax)
TC0013 Invalid process ID (PID) index See method TestTool_DosExecPgm or TestTool_DosKillProcess (OS/2 only): 
Choose a lower user defined index number (IdxPID)
TC0014 ExecFlag of method TestTool_DosExecPgm is missing, invalid or ActionFlag of method TestTool_DosKillProcess is invalid or missing. See method TestTool_DosExecPgm (OS/2 only).
Check: Parameter value of ExecFlag 
or
see method TestTool_DosKillProcess (OS/2 only). 
Check: Parameter value of ActionFlag.
TC0015 The user defined handle number exceeds the limit. See TOOL Syntax for handle limits.
TC0016 Parameter "ALL" represented by "...VectorHdl" is invalid in this context. See TOOL syntax, check for valid options.
TC0017 The object cannot be processed, because it is invalid. Check object attributes.
TC0018 Length of BINARY data is not specified. Invoke Fmcj...BinaryLength() API before.
TC0020 An expected double quote (") as string delimiter is missing. Check string parameter of the API method within a test case file for a missing double quote.
TC0022 Comment END "*/" not found. Check for typos (see TOOL Syntax)
TC0023 Out of resources Check values of parameter "BufferLength" of the API calls:
If requested buffer size was 0 bytes use a number > 0.
If requested buffer size was > 0 bytes check system resources.
TC0024 If statement error See Syntax Introduction for
TestTool_IF    or
TestTool_Then  or
TestTool_Else  or
TestTool_End.
 
TC0031 Hex string ends with a half byte. Change the hex string and look for a even string length.
TC0032 Hex string contains a unknown char. See valid chars: 
0123456789aAbBcCdDeEfF