Enterprise COBOL AZUTC007 sample test case (for BZUPLAY runner)

The ZUnit Enterprise COBOL AZUTC007 sample is a COBOL source file for generating and running a test case with imported batch program data. This sample file demonstrates how to test a COBOL batch application program on Dynamic Test Runner (BZUPLAY).

Before using this sample file:
  1. Verify that you have access to the following resources:
    • A z/OS® system with the XML Toolkit for z/OS installed.
    • Developer for z/OS version 14.2.4 or later installed on Windows™.
    • Developer for z/OS version 14.2.4 or later data sets FEL.SFELSAMP and FEL.SFELLOAD installed on z/OS.
    • A connection to a z/OS system that is defined in the Remote Systems view.
  2. Verify that procedure FEL.SFELSAMP(AZUZUNIT) was customized according to the instructions in xUnit support for Enterprise COBOL and PL/I.
  3. Verify file mappings for the test data generation, configuration, and results files, and the test data schema XSD files.
    Open the z/OS File System Mapping view and look for the following entries:
    Mapping Criterion Workstation File Extension Transfer Mode Host Code Page Local Code Page
    **AZUCFG azucfg binary UTF-8 UTF-8
    **AZUGEN xml binary UTF-8 UTF-8
    **AZURES azures binary UTF-8 UTF-8
    **AZUSCH xsd binary UTF-8 UTF-8
    **AZUTDT xml binary UTF-8 UTF-8
    **BZUCFG bzucfg binary UTF-8 UTF-8
    **BZURES bzures binary UTF-8 UTF-8
    If these entries do not exist, do one of these steps:
    • Create a workspace. Workspaces created by version 14.2.4 or later include these mappings.
    • Add mappings with these characteristics to your current workspace. For instructions for creating file mappings, see Mapping data sets and partitioned data set members.
    • If push-to-client support is enabled on the remote system, you can add these mappings to the z/OS file system mapping configuration files so that they are downloaded to each client when it connects to the remote system. For more information about push-to-client, see Distribution of updates by using push-to-client.
By using these sample files, you can accomplish these tasks:
  1. Generate a test case from the CALL02.cbl sample COBOL program.
  2. Record test data for the CALL02 sample COBOL batch application and import the recorded data to the test case.
  3. Create/modify a test case for CALL02 and a stub program for SUB02A and SUB02B.
  4. Build and run the test case for CALL02.
  5. Create a test case from the SUB02A.cbl sample COBOL program.
  6. Record test data for the CALL02 sample COBOL batch application and import the recorded data to the test case for SUB02A.
  7. Create/modify a test case for SUB02A.
  8. Build and run the test case for SUB02A.