The commands that can be executed from the TestBench main menu (with the exception of Adhoc_IT) support Project and the relevant Case as parameters. These two parameters can be set to the special value of ‘*SELECT’ in all commands except Play_IT which is how the commands are issued from the TestBench main menu.

The ‘SELECT’ option allows the user to specify on the initiation screen which Project and Case to use. If the Project is named but the Case is set to ‘SELECT’, then the Project will be locked on the initiation screen but the user can still choose a Case. In Play_IT, if the required parameters are left blank a prompt screen will be displayed for each one.
Test_IT
This command interface operates in a similar fashion to Option 1 on the Work With Test Cases display. However it possesses one additional option. When a Test Case which calls a program directly is executed the Level ID of the program is checked to ensure that it has not changed since the Test Case was created. If it has changed, a message is displayed and you are forced into Test Case Maintenance to re-confirm the parameter definitions for the program. If you can be certain that the calling parameters for the program have not changed then this level check can be bypassed with the Bypass Level Check option. This also causes the initiation screens to be bypassed so that the Test_IT command can be submitted to batch.
CRTTSTCSE
Access the Test Case maintenance screens and optionally specify command parameters of Project, Test Case, Description, Program and Library. This is the equivalent to pressing F6 on the Work With Test Cases display.
WRKTSTCSE
Access the Work With Test Cases display for a specific Project and optionally provide Test Case and Program filters to further limit the view.
Play_IT
This command interface enables a Script to be replayed immediately for fast start test execution. Specify a Project, Test Case, Script Name and optionally a Run Description and Reference. If submitting the request to batch the device type must also be specified (F4 to prompt). See specific section in the Native R&P chapter for more information.
WRKTSTRUN
This provides the capability to view all Test Runs for a specified Project and Test Case, all Test Runs for a specified User or all Test Runs for a Test Run Reference. In the first mode the view can optionally be limited further by specifying a Test Run number.
WRKDTARUN
This provides the capability to view all Data Case Runs for a specified Project and Data Case or all Data Case Runs for a specified User. In the first mode the view can optionally be limited further by specifying a Data Case Run number.
WRKWRPRUN
This provides the capability to view all Warp Case Runs for a specified Project and Warp Case or all Warp Case Runs for a specified User. In the first mode the view can optionally be limited further by specifying a Warp Case Run number.
WRKCMPRUN
This provides the capability to view all Comp Case Runs for a specified Project and Comp Case or all Comp Case Runs for a specified User. In the first mode the view can optionally be limited further by specifying a Comp Case Run number.
WRKINTRUN
This provides the capability to view all Integrity Case Runs for a specified Project and Integrity Case or all Integrity Case Runs for a specified User. In the first mode the view can optionally be limited further by specifying an Integrity Case Run number.
Report_IT
This command interface operates in an identical fashion to Option 6 on the Work With Test Cases display.
Extract_IT
This command interface operates in an identical fashion to Option 1 on the Work With Data Cases display unless both a Project and a Data Case code are specified.

In this event the request will be executed immediately in the mode specified (interactive or batch) for the Data Case. Any invalid parameters will cause exception messages to be sent, which can be monitored.

It is also possible to specify a Target Library which will override that attached to the Data Case.

Note Run time values should not be set up on a data case that you want to submit using the command EXTRACT_IT, this is as there is no chance for the user to enter the selection values.

RESUMEEXT
This command is the equivalent to keying an option ‘13’ on the Work With Data Runs display. For remote Data Cases which use the media method of data transfer, the Data Run remains at ‘Medready’ status until the extracted library is manually transferred from the remote to the local system. This command resumes the extract process for the given Data Run. See the Data Extract chapter for more information.
Warp_IT
This command interface operates in an identical fashion to Option 1 on the Work With Warp Cases display unless both a Project and a Warp Case code are specified.

In this event the request will be executed immediately in the mode specified (interactive or batch) for the Warp Case. Any invalid parameters will cause exception messages to be sent, which can be monitored.

Comp_IT
This command interface operates in an identical fashion to Option 1 on the Work With Comp Cases display unless both a Project and a Comp Case code are specified.

In this event the request will be executed immediately in the mode specified (interactive or batch) for the Comp Case. Any invalid parameters will cause exception messages to be sent, which can be monitored.

Adhoc_IT
This is the only way of entering the Adhoc_IT facilities. Command parameters of Program and Library are supported.

Plan_IT
This command interface operates in a similar fashion to Option 2 on the Work With Plan Cases display. If the command is submitted to run in batch there are some additional checks that are performed:-
• If a Plan Case is being executed interactively and the Rebuild option is set to *NO, the Plan Case will is displayed. In batch, a message is sent to the job log and the operation is halted.
• If the command has been submitted and the Rebuild option is *YES but the Mode is set to *INTER, the Plan Case will be rebuilt in batch.

Inspect_IT
This command enables a previously defined Integrity Case to be executed and requires parameters of Project and Integrity Case. If these are left blank a selection screen is displayed.

Purge_IT
This command interface operates in a similar fashion to the Purge Results option on the Main Menu and is used to remove multiple Test Case, Data Case, Warp Case or Action Map results.

Scan_IT
This command interface scans a Test Environment and operates in an identical fashion to Option 1 on the Work With Test Case Environments display. It requires the Environment ID. If this is left blank when the command is issued a selection screen will be displayed.

Mark_IT
This command interface sets a Checkpoint and operates in an identical fashion to Option 2 on the Work With Checkpoints display. It requires the Environment ID and Checkpoint ID. If these are left blank when the command is issued a selection screen will be displayed for each.

Roll_IT
This command interface will issue a rollback to a Checkpoint and operates in an identical fashion to Option 7 on the Work With Checkpoints display. If these are left blank when the command is issued a selection screen will be displayed for each.

TBWAIT
Command to add as a Test Case Process which will pause the test until all of the previous jobs (processes) have ended. Optionally enter a number of seconds as a parameter. A value of 12 means that TestBench will check all previous jobs every 12 seconds for completion, no entry means that there is no time delay between checks. This can be useful when a previous process is a submitted job and a subsequent process is required to use the output from the submitted job.

Spool_IT
Command to add as a Test Case User Exit which will copy a spool file generated by a specified Test Run into a database file. This file can then be used, for example, to compare to a previously stored version of the report using Comp_IT. Unlike the CPYSPLF command, the job name is not required which is an advantage when reports are generated by batch jobs. Substitution variables enable Projects, Test Cases, Run numbers etc to be embedded in the Spool_It command and thus identify the system job. Substitution variables are supported in User Exits.

CPYMSGFTF
Command to add the contents of a message file into a physical file so that two message files can then be compared using Compare Cases. If the physical file does not exist it will be created, if it does exist it must be in the correct format to hold the message file data. Message information including the Message ID and Text is added to the physical file. Two logical files are also created to assist with the file comparison, they have the same name as the physical file but with a ‘1’ and a ‘2’ on the end. Logical 1 has the Message ID in the key, logical 2 has both the Message File and Message ID in the key.

DSPJL
Display Job Log Alternate – full information will be found in an earlier section

WrkJrnAnl
Work with Journal Analysis – full information will be found in an earlier section

WrkPF
Work with File Definition – full information will be found in an earlier section

SETTBLIB
Set TestBench Library – see Technical Information section

TBE102R
Reserved – This is for TestBench internal use only.

TBIMPORT and TBEXPORT
These two commands can be used to export TestBench information such as Data Cases into a temporary library which can then be transferred to another iSeries and imported into an alternative TestBench library, thus making it easy to share information.

Export Command

Project Specify the name of the TestBench Project from which information will be extracted.

Case Type Choose from *DATACASE (Data Cases), *TESTCASE (Test Cases), *COMPCASE (Compare Cases), *WARPCASE (Warp Cases), *ACTIONMAP (Action Maps) or *INTEGRITY (Integrity Cases). Alternatively select *ALL to extract all information within the Project.

Case Name Specify a specific Case for export or leave blank to export all Cases of the specified type. This field is case sensitive.

Source Library The name of the TestBench library from which data will be exported.

Export Library The name of the library into which data will be exported, this should be a holding library and not another TestBench database. If the library does not exist it will be created.

Copy Script If Test Cases are being exported, specify whether or not Scripts should also be included. Choose from *NONE, *ALL, *GREEN (5250 or 3270) or *GOLD (Windows or Web) scripts. This field is case sensitive.

Script Name Optionally specify the name of a specific Script to be exported.

Data Option Choose between replacing data in the export library or adding any new Cases to those which have already been exported into it.

Import Command

Import From Library The name of the temporary library into which data was exported.

Target Library The TestBench library into which the extracted data should be imported.

Data Option *REPLACE will cause all Cases which have been exported and exist in the temporary library to be deleted from the target before the import occurs. *ADD will simply add any Cases which do not already exist in the target library.