Messages
Overview
Message codes issued during test execution. The message codes are printed to
• the Eclipse Error Log of the Client IDE
• DD SYSOUT on IBM z/OS
STBB (Builder)
STBB000E Error in BinaryBuilder
Explanation: Unexpected error while creating binary input data – contact Topaz for Total Test support.
STBB001E String in NAME is longer than LENGTH character
Explanation: The input value given for the text field NAME is too long. It may not exceed LENTGH characters.
STBB002E Converted number in NAME is not LENGTH bytes long
Explanation: The input value given for the numeric field NAME is too large. It may not exceed LENGTH digits.
STBB003E Given byte buffer for NAME is shorter than LENGTH character
Explanation: Internal problem – contact Compuware support.
STBB004E Unsupported Encoding.
Explanation: The requested target encoding is not supported. Check target environment settings in project properties.
STBB005E Given name of charset is null.
Explanation: Target encoding is not set. Check target environment settings in project properties.
STBB006E POS is not a valid position in a buffer of LENGTH bytes.
Explanation: Internal problem – contact Compuware support.
STBB007E Storage length of NAME is not valid (LENGTH bytes).
Explanation: Internal problem – contact Compuware support.
STBB008E File not opened for writing.
Explanation: Open failed for BININP.
STBB009E Error while writing MVS file.
Explanation: Write failed for BININP.
STBB010E FILE has invalid XML format.
Explanation: Internal problem – contact Compuware support.
STBB011W Invalid value in NAME (VALUE).
Explanation: Numeric field NAME contains a binary value of VALUE which is not a valid numeric value for the target format. Builder uses no value ("null") for this field and continues with the next field.
STBB012E Length of REDEFINES structure NAME exceeds length of its redefined counterpart
Explanation: The structure NAME redefines a shorter structure which is not currently supported. Builder continues with the next field after this structure, but this problem will probably lead to a failed execution.
STBB013W Field NAME not defined in interface definition
Explanation: Scenario uses field NAME which is not defined in the interface. This problem is probably caused by changing a structure without properly updating the interface in using it.
STBP (Parser)
STBP000E Error in BinaryParser
Explanation: Unexpected error while creating output data – contact Compuware support.
STBP001E Given byte buffer in NAME is shorter than LENGTH character.
Explanation: Internal problem – contact Compuware support.
STBP005E Storage length of NAME is not valid (LENGTH bytes).
Explanation: Internal problem – contact Compuware support.
STBP006E POS is not a valid position in a buffer of LENGTH bytes.
Explanation: Internal problem – contact Compuware support.
STBP007E Byte buffer for writing NAME is null.
Explanation: Internal problem – contact Compuware support.
STBP008E File corrupted, TARGET expected, but OTHER found.
Explanation: Problem in binary result data BINRES – contact Compuware support.
STBP009E File not opened for reading.
Explanation: Open failed for BINRES.
STBP010E File corrupted, ARGVAL expected, but OTHER found.
Explanation: Problem in binary result data BINRES – contact Compuware support.
STBP011E File corrupted, argument POS1 expected, but found argument POS2
Explanation: Problem in binary result data BINRES – contact Compuware support.
STBP012E File corrupted, RETVAL expected, but OTHER found.
Explanation: Problem in binary result data BINRES – contact Compuware support.
STBP013W No more test cases in binary file.
Explanation: Not all targets have output data – possible premature end of test execution. Also check other messages.
STBP014E Error while reading mvs file.
Explanation: Read failedfor BINRES.
STBP015W Invalid value in NAME (VALUE).
Explanation: A binary value of VALUE has been found for the numeric field NAME which is not a valid value for the target format. Parser uses no value ("null") as output value of this field and continues with the next field.
STBP016S Binary test case data do not correspond to test case
Explanation: A target has been found that does not have a corresponding test case in the test scenario. Data in BINRES do not match this test suite.
STBP017S Binary test case number of arguments (LENGTH-1) do not correspond with test case number of arguments (LENGTH-2)
Explanation: The number of argument data differ from the number of arguments as defined in the interface. Data in BINRES may refer to an outdated interface definition.
STTR (Runner)
STTR003S Unsupported number of arguments.
Explanation: A maximum of 2500 arguments is currently supported.
STTR005S Invalid record type
Explanation: Internal problem detected – contact Compuware support.
STTR006I Executing target name
Explanation: Information – target name has been executed.
STTR007I Execution failed with errors
Explanation: One or more targets have not been executed successfully. For details check preceding messages.
STTR008I All targets successfully executed
Explanation: Information – all targets have been executed as requested.
STTR010E Invalid job parameter
Explanation: Invalid parameter in EXEC PARM. Check JCL template.
STTR011I Topaz for Total Test zTargetRunner vVVRRMM YYYYMMDDhhmmssss-xxxx on YYYY-MM-DD hh:mm.ss
Explanation: Information – Version and execution time stamp.
STTR012I Options set to Options List
Explanation: Information – Options with which the Target Runner has been executed.
STTR013I Processing test suite name
Explanation: Information – Test suite name has been processed.
STTR014I Processing test scenario name
Explanation: Test scenario name has been processed.
STTR018W The repeat parameter is no longer supported; input ignored.
Explanation: Requested option REPEAT is no longer supported by TTTRUNNR. Test execution continues with the REPEAT value ignored.
STTR028I Processing test case name
Explanation: Information – Test case name has been processed.
STTR031S No binary input data found (BININP)
Explanation: Dataset containing the binary input data is empty.
STTR034S Binary Builder version not supported by zTargetRunner version: version level
Explanation: Internal problem detected – contact Compuware support.
STTR035W Max number of write stub assertions reached
Explanation: The limit of asserting 256 different files has been reached. Assertions for files beyond this limit will not be provided.
STTR036W License check finished with warnings
Explanation: License check was successful, please check the LMS output for more information.
STTR037S License check failed, product not licensed
Explanation: License check failed, please check LMS output for more information.
STTR038S License check failed for unknown reasons, contact support
Explanation: Please call Compuware Support.
STTR042S File open failed check job log and JCL. File: filename
Explanation: BININP or BINRES failed to open. Check the Test Runner job output and JCL for information about the failure.
STTR043I Initializing simulation environment for: environment
Explanation: Informational.
STTR245W -- SOURCE LISTING DATASET WARNING -
STTR245W SOME TESTS REQUIRE THE SOURCE LISTING DATASET,
STTR245W NO SOURCE LEVEL SUPPORT INFORMATION EXISTS FOR THE CURRENT PROGRAM,
STTR245W PROGRAM pgmname DATE: mm/dd/yy TIME: hh:mm:ss
Explanation: A DDIO source listing is required for test runs that use the following: Db2 SQL stubs, CICS command stubs, IMS CBLTDLI stubs, and subprogram stubs for statically linked subprogram calls. If this test does not use any of these stub types, then this message is informational only; the target program of the test will run as it should. Otherwise, the test run will terminate early with additional error messages in the job output and test result report.
If the test has terminated early because the DDIO source listing was required but not available, then follow these steps to ensure Test Runner can find it:
- Check this job's JCL step used to run Test Runner program TTTRUNNR. It may contain one or more SLSF00x DDs. Make sure the proper DDIO dataset for this target program's application is specified. If it is not, you may add its DDIO dataset on an SLSF00x DD statement. Up to eight DDIO datasets are allowed in JCL, having DD names SLSF001 through SLSF008.
- Test Runner will dynamically allocate DD SLSF009 using the DDIO dataset name found in this program's User IDR record from its load module or program object, if such an IDR record exists. When this DDIO dataset name is available, then DDs SLSF001 through SLSF008 are not needed in JCL. Use Compuware Language Processor's PROCESSOR(IDENTYES) option, which is the default, to add this User IDR record. If post-processing a program listing, be sure to specify the appropriate CWPLOAD DD or CWPDECK DD to the Language Processor job step.
- If this target program was compiled using Enterprise COBOL V5 or V6, then DDIO's Embedded Source Support is highly recommended and eliminates the need for DDIO datasets to be allocated using SLSF00x DDs in the Test Runner job. Use Compuware Language Processor's ESS(YES) option, which is not the default, to use Embedded Source Support in place of DDIO datasets. If post-processing a program listing, be sure to specify the appropriate CWPLOAD DD or CWPDECK DD to the Language Processor job step.
Refer to the Compuware Shared Services Compuware Source Support Best Practices for more information about using Compuware Language Processor options and DD statements.
If any other STTR245W messages are displayed, then an internal error may have occurred; in that case, please contact Compuware support.
STTR246W Load of module xxxxxxxx failed. Check that its PDSE or load library is specified in the Test Runner STEPLIB.
Explanation: The program being tested issued an EXEC CICS LOAD statement for the named program. If the program name is correct and its PDSE or load library is already specified in the Test Runner STEPLIB, then check the Test Runner job output for system messages.
STTR700E DB2 SQL STATEMENT STUB NOT FOUND. FOR MORE INFORMATION,
STTR700E FIND MESSAGE STTR700E IN SYSOUT FILE TTOUT.
STTR700E -- TERMINATING -- ABEND U0700 --.
Explanation: Test Runner was not able to stub a Db2 SQL statement. This may be due to the target program issuing an EXEC SQL statement that was not executed when the test case's baseline was recorded. Also, this may be due to the source listing of the target program not being found; see message STTR245W for more information.
STTR701E DB2 SQL STATEMENT TYPE NOT YET SUPPORTED. FOR MORE INFORMATION,
STTR701E FIND MESSAGE STTR701E IN SYSOUT FILE TTOUT.
STTR701E -- TERMINATING -- ABEND U0701 or U0703 --
Explanation: The target program issued an EXEC SQL call for a function that is not yet supported. Contact Compuware support and provide the TTOUT file. This function may be supported in a later release.
STTR702E DB2 SQL DATA TYPE NOT YET SUPPORTED. FOR MORE INFORMATION,
STTR702E FIND MESSAGE STTR702E IN SYSOUT FILE TTOUT.
STTR702E -- TERMINATING -- ABEND U0702 or U0703 -
Explanation: The target program used a Db2 data type that is not yet supported. Contact Compuware support and provide the TTOUT file. This data type may be supported in a later release.
STTR710E AN UNEXPECTED ERROR OCCURRED DURING DB2 SQL STUB PROCESSING. FOR
STTR710E MORE INFORMATION, FIND MESSAGE STTR710E IN SYSOUT FILE TTOUT.
STTR710E -- TERMINATING -- ABEND U0710 --
Explanation: An unexpected error occurred. Contact Compuware support.
STTR900E EXEC CICS STATEMENT STUB NOT FOUND. FOR MORE INFORMATION,
STTR900E FIND MESSAGE STTR900E IN SYSOUT FILE TTOUT.
STTR900E -- TERMINATING -- ABEND U0900 --
Explanation: Test Runner was not able to stub a CICS command. This may be due to the target program issuing an EXEC CICS statement that was not executed when the test case's baseline was recorded. Also, this may be due to the source listing of the target program not being found; see message STTR245W for more information.
STTR909E EXEC CICS COMMAND NOT YET SUPPORTED. FOR MORE INFORMATION,
STTR909E FIND MESSAGE STTR909E IN SYSOUT FILE TTOUT.
STTR909E -- TERMINATING -- ABEND U0909 --
Explanation: The target program issued an EXEC CICS call for a command that is not yet supported. Contact Compuware support and provide the TTOUT file. This command may be supported in a later release.
STTR910E AN UNEXPECTED ERROR OCCURRED DURING EXEC CICS STATEMENT STUB PROCESSING. FOR
STTR910E MORE INFORMATION, FIND MESSAGE STTR910E IN SYSOUT FILE TTOUT.
STTR910E -- TERMINATING -- ABEND U0910, U0915, or U0920 -
Explanation: An unexpected error occurred. Contact Compuware support.