Space announcement This documentation space provides the same content as before, but the organization of the content has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

Standard Test Screen – Environments Menu - Option 1

The Standard Environment Test screen (Environments Menu) shown in following figure is used to specify the standard environment parameters. Batch programs that process QSAM or VSAM files, batch programs that issue third-party database calls (IMS/DB, ADABAS, TOTAL, TIS, SUPRA, DATACOM/DB, and System 2000), and batch programs that issue EXEC SQL (Db2) statements can be executed in this environment.

Standard Environment Test Screen 

Profile: DEFAULT ------------  STANDARD (2.1)  -----------------------
COMMAND ===>

COMMANDS:  SEtup (Display Setup Menu)
           PROFile (Display Profile Selection)
TEST SELECTION CRITERIA:

               Program ===> SQL
           Entry Point ===>
           Load Module ===>

        Initial Script ===>
           Post Script ===>

  PARM  ( Caps = YES ) ===>

  File List/JCL Member ===>
        Preview Files? ===> NO
   Code Coverage Test? ===> NO   (YES, NO, TDO)  System Flow? ===> NO
   Is This a DB2 Test? ===> NO    Plan ===>            System ===>

           Press ENTER to process  or  enter END command to terminate


The fields on the Standard Environment Test screen are described as follows:

Program

Required. Enter the name of the load module.

Important

If executing other than the linked entry name, then the program name is the CSECT name and the load module name must be specified under Load Module.

Entry Point

Enter an alternate entry point if execution is to start at a point other than the link-edited entry point.

Load Module

Enter only if executing a CSECT other than the link-edited entry point of a load module, such as unit testing CSECTs within a load module.

Initial Script

Enter the member name of a test script if you want to execute a predefined command stream at the beginning of the debugging session. This member will be executed after the inclusion of the site-wide script member @@SITE@@, if defined.

Post Script

Enter the member name of a test script if you want to execute a predefined command stream at the end of the debugging session.

PARM (Caps=YES)

When this field is left blank:

If JCL PROC expansion option CONVERT is being used and the step you are testing has the PARM= or PARMDD= keyword, Code Debug TSO will use the JCL-supplied PARM value. To make Code Debug ignore the JCL-supplied PARM value, enter two consecutive single quotes ('') in this field.

When this field is non-blank:

Up to 100 characters may be specified in this field to pass parameter strings and/or run-time options to the program being tested. If the field consists of several substrings separated by commas, or if it contains special characters (/, =, etc.), enclose the entire parameter in quotes (single or double).

The Caps field can be used to designate whether or not you want the PARM string to be converted to upper case.

Important

This conversion applies only to the parameter string entered on this screen and not to any PARM values supplied in the JCL.

File List/JCL Member

Enter the data set name that contains the file list, CLIST, or JCL. The File Allocation Utility (FAU) preallocates files and databases that are processed by the program upon entry to the debugging session.

If the member name of a PDS is omitted, a member list is displayed.

If the data set contains a CLIST, Code Debug TSO immediately executes it and begins the debugging session.

If the data set contains a file list or JCL, the FAU is invoked to dynamically allocate the specified files before beginning the debugging session. See Using the File Allocation Utility for detailed information about the FAU.

Preview Files?

Enter YES to browse or edit the content of files prior to allocation. For more information, see Using the Edit File List Screens.

Code Coverage Test?

Enter YES to collect statistics without Test Data Optimization information. Enter TDO to collect statistics and TDO information. The default value is NO.

System Flow?

Enter YES to collect Code Coverage System Flow data. The default value is NO.

Important

The Code Coverage options are only available if you have purchased Code Coverage.

Is This a DB2 Test?

Enter YES if the program executes EXEC SQL statements. Code Debug TSO executes the DSN RUN command and establishes the Db2 environment upon entry to the debugging session. The default value is NO.

Plan

Enter the Db2 plan name generated during the bind process. If omitted, the plan name defaults to the name specified in the Program field.

System

Enter the Db2 subsystem name. The subsystem name depends on the release level of Db2 allocated to the DSNLOAD library specified on the Setup option.

Important

If the following conditions are met, Code Debug will search the JCL member’s SYSTSIN DD for the plan name and/or system name and use values found for the current debugging session:

  • File List/JCL Member field contains a JCL library
  • Is This a DB2 Test? field set to YES
  • Plan and/or System fields blank
  • JCL PROC expansion set to CONVERT.

If a plan name is not found in the JCL, the default will be used. If a system name is not found, an error will result. Also, if the Library keyword is used in the SYSTSIN DD, Code Debug will concatenate the data set after the user libraries that were specified on the Load Module Libraries screen.

Press Enter to initiate the debugging session. See Debugging Interactively for information on how to debug your program.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*