Batch recording of I/O data

You can use IBM® z/OS® Debugger to capture linkage data for an Enterprise COBOL program at runtime and generate an XML file for the data values. You can then import the XML file into the z/OS Automated Unit Testing Framework (ZUnit) Test Case Editor.

About this task

This procedure explains how to use the batch recording feature. For information about recording test data from the Test Case Editor, see Recording test case data for CICS (test runner).

Procedure

  1. Ensure that a z/OS UNIX System Services (USS) directory exists for saving the XML file. If not, create a USS directory.
  2. Add the following statement to the GO step of the JCL for the batch job. When the job is submitted the debugger runs in the background. The generated XML file is saved to the USS directory that is specified in the command. 
    TEST
(ALL,,,*),
ENVAR("EQA_STARTUP_KEY=parm1,parm2,parm3,parm4,parm5,parm6")
    Parms Valid values Description
    parm1 LD Function code
    parm2 Program name(s) The linkage data is captured when this program is exited. The * wild card character is supported.

    *: any compilation unit name.

    ab*: the compilation unit name starts with ab, such as ab, ab1, or abc12.

    Multiple program names are supported. The format is nn,nn,nn, where nn is a program name with or without a wild card character.

    parm3 recording=both

    rec is a short version of the recording keyword.

    		 Records linkage data at program entry and exit
    parm4 output=directory

    out is a short version of the output keyword.

    		The USS directory to write the output XML file to. The file is written to the directory you specify with /testid appended.

    You must create the USS directory structure before the file is written.

    parm5 testid=alpha-numeric string

    tid is a short version of the testid keyword.

    		 The tester's user ID. This ID is appended to the output directory path when the output XML file is written.
    parm6 perm=3-digit attribute The output file permission attribute. Specify the permission attribute using the same rules as for the CHMOD command. This parameter is optional. The default value is 644. If the value is invalid, the default value is used.

    The 644 permission attribute provides read-write access to the file owner, read access to the group, and read access to all others.

Example

TEST
(ALL,,,*),
ENVAR("EQA_STARTUP_KEY=LD,*,rec=both,out=/u/userid/ztest,tid=userid")