Current Topaz for Total Test Virtualized Test Limitations

COBOL Limitations

The following COBOL language constructs are not supported:

• Occurs Depending On when the "depending on" value is outside of the structure, i.e. when it's part of some other program argument or field.
• Stubbing of COBOL EXTERNAL files.
• Stubbing of COBOL EXTERNAL storage, unless it is already an argument of the program call.
• Editing of DBCS and Unicode data in Topaz for Total Test Stub Editors.
• The number of target program arguments is limited to 2500.
• AMODE 24 target programs.
• Programs using object-oriented (OO) COBOL Features.
• Nested COBOL programs.
  
• Recursive COBOL programs.
• EJECT, SKIP1, SKIP2, SKIP3, TITLE in COBOL copybooks.
• Print file carriage control characters are not asserted.
• Limited support for PIC N and USAGE NATIONAL.
• Compile options LIST and TEST must be used with programs compiled with OPTIMIZED(1) or OPTIMIZED(2) in order to record test cases. It is strongly recommended to use sub-parameters TEST(NOEJPD,NOSOURCE,NODWARF) to prevent excessively inflating the size of the executable module.
• Limited long name support:
  • Long names for target program names and entry points are supported; requires recording the test cases with Xpediter SET ABBREV ON.
  • Not supported:
    • Long names for stubbed subprograms. 
    • COBOL compile options PGMNAME(LONGMIXED) for stubbed subprograms, statically linked.
    • Long name tokens used for DDIO source members.
    • CICS long names can be a maximum of 16 characters.
• These file status keys are not yet supported:
  • 02 - WRITE, REWRITE for KSDS AIX NONUNIQUEKEY
  • 22 - WRITE, REWRITE for KSDS AIX UNIQUEKEY
  • 44 - WRITE, REWRITE of wrong length record; partially supported
• Certain rarely encountered file status keys are not supported. Among these are those that result from environmental factors, external to the COBOL program. These are not expected to occur when recording a unit test. Examples are:
  • 30 - Read boundary violation, data check parity error, or transmission error
  • 95 - Corrupt or incomplete file

VSAM Limitations

One unusual case is not supported:

• VSAM KSDS file defined with "NOUPGRADE" that uses an alternate index and has a WRITE, REWRITE, or DELETE operation performed upon it.

Db2 Limitations

• No CLOB, BLOB, DBCLOB data type support.
• Test data collection is not supported for all Db2 Special Registers.
• Limited support of Db2 DDL: Create Table, Declare Table, and Drop Table are supported.
• Db2 Stored Procedures: "Live Db2" (no stubs) execution for running test cases is not supported.
• No support for Dynamic SQL.
• Limited support for DBCS in Db2.

IMS Limitations

• BMP and DL/I Batch Programs Live Execution:
  • Only testing of main program is supported.
  • Sub-program stubbing is not supported.

• Can’t collect data for IMS BMP Programs running on COPE systems.
• MPP Programs Live Execution is not supported.
• Topaz for Total Test currently only captures the first MPP transaction during Unit Test generation.
• Can’t collect data from Pseudo-Wait for Input MPP Programs.
• IMS interfaces not supported:
  • IMS ODBA Interface.
  • IMS AERTDLI (ODBA) Interface.

CICS Limitations

• Stubbing out Db2 Stored Procedures in a CICS program is not currently supported.
• IMS Database stubbing is not yet supported under CICS (no support for DBCTL).
• CICS Transaction Gateway programs cannot be tested.
• CICS Java programs cannot be tested.

Miscellaneous Limitations

• No Hogan File support.
• No IDMS support
• No Datacom/DB support