Hogan BATCHPEM Test Screen – Environments Menu - Option 5

The Hogan BATCHPEM screen, shown in following figure, lets you specify the Hogan BATCHPEM environment parameters and initiate a debugging session. Batch programs that run under the Hogan umbrella and process QSAM and VSAM files can be executed in this environment.

Hogan BATCHPEM Screen

Profile: DEFAULT ---------------- HOGAN BATCHPEM (2.5) ----------------
COMMAND ===>

COMMANDS: SEtup (Display Setup Menu)
           PROFile (Display Profile List)
           SYsin (Edit SYSIN Data Set)
TEST SELECTION CRITERIA:

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

           PARM String ===>

  HOGAN SYSIN Data Set ===>

      HOGAN PEM Driver ===> BATCHPEM   ("BATCHPEM" is Default for This Test)

  File List/JCL Member ===>

   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 Hogan BATCHPEM screen are defined as follows

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 String

Optional field. Enter the parameter string to be passed to the Hogan PEM driver program. You can enter up to 100 characters in this field.

If the run-time parameter consists of several substrings separated by commas, or if it contains special characters (/, =, etc.), enclose the entire parameter in quotes (single or double).

Hogan SYSIN Data Set

A control file used by Hogan programs. Enter SYSIN on the command line to edit or create the SYSIN data set, shown in following figure.

Displaying the SYSIN Data set

EDIT ----- AXPTSO.XPEDITER.SYSINDS(HOGSYS01) - 01.00 ---------- COLUMNS 001 072
COMMAND ===> SCROLL ===> PAGE

****** *************************** TOP OF DATA *******************************
000001 1 49 904
000002 #905¬704¬1%
****** ************************** BOTTOM OF DATA *****************************

Hogan PEM Driver

The name of the Hogan driver. BATCHPEM is the default.

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. Any files or databases that are not dynamically allocated by Hogan must be allocated through this file.

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 the Using the File Allocation Utility for detailed information about the FAU.

Important

All CDMF files and databases should be allocated.

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. The default value is NO.

Plan

Enter the Db2 plan name generated during the bind process if the program executes EXEC SQL statements.

System

Enter the Db2 subsystem name. The subsystem name depends on the release level of Db2 and is assigned at the time of installation.

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