< Previous | Next >

Lesson 4: Creating data set definitions

A data set definition is a container for information about a data set on the z/OS® system. All data sets referenced by a build process must have a corresponding data set definition.

About this task

Tip: You can use the system definitions generator to automate the tasks described in Lessons 4 through 9, instead of using an editor to create each one manually. See z/OS system definitions generator for more information about automating the creation of data set definitions, translators, and language definitions.
Create data set definitions for each of the data sets that will be referenced by your build. The following table describes the data set definitions that are required for this tutorial:
Table 1. Required data set definitions
Name Type Allocation Parameters Description
COBOL Destination data set for a zFolder RECFM(F,B) LRECL(80) SPACE(1,1) CYL Data set for COBOL source files
LINK Destination data set for a zFolder RECFM(F,B) LRECL(80) SPACE(1,1) CYL Data set for link-edit source files
OBJ Build output data set (created if it does not exist) RECFM(F,B) LRECL(80) SPACE(1,1) CYL Data set for object decks
LOAD Build output data set (created if it does not exist) RECFM(U) LRECL(0) SPACE(1,1) CYL Data set for program objects
TEMPFILE Temporary data set used for build SPACE(5,5) TRACKS UNIT(SYSALLDA) Temporary data sets required by the COBOL compiler
IGYCRCTL Existing data set used for build   COBOL compiler module
IEWBLINK Existing data set used for build   Link-editor module
SCEELKED Existing data set used for build   Data set containing the link-edit stubs for C/C++, PL/I, COBOL, and Fortran languages and Language Environment-provided routines

Procedure

  1. Create a data set definition that corresponds to the PDSE (partitioned data set extended) that will contain COBOL source code on the build machine.
    1. In the Team Artifacts view, expand your project area node, and then these nodes: Enterprise Extensions > System Definitions > z/OS. Right-click the Data Set Definitions node to show the menu, then click New Data Set Definition.
    2. Name the data definition COBOL.
  2. In the General section, specify the following parameters:
    • Usage: Destination data set for a zFolder. This specifies that the new data set definition corresponds to a zFolder contained within a zComponent Project.
    • Data set name: COBOL. This is the name that will be used on your z/OS system after you create this data set.
  3. For data set characteristics, specify the following parameters:
    • Space Units: Cylinders
    • Primary Quantity: 1
    • Secondary Quantity: 1
    • Directory Blocks: 0
    • Record Format: FB
    • Record Length: 80
    • Block Size: 0
  4. Click Save.
  5. Repeat steps 1-4 to create and save a new data set definition named LINK, as described in the previous table.
  6. Create a data set definition for OBJ.
  7. In the General section, specify the following parameter:
    • Usage: Build output data set (created if it does not exist) . This specifies that the new data set definition refers to an output data set that will be used by the build process. In this tutorial, the OBJ data set will be used to hold the object decks produced by the COBOL compiler. If this data set does not exist, it will be allocated during the build.
  8. Select Add data set prefix from build definition to data set name. This indicates that this data set should be prepended with the data set high-level qualifier associated with the build request.
  9. For data set characteristics, specify the following parameters:
    • Space Units: Cylinders
    • Primary Quantity: 1
    • Secondary Quantity: 1
    • Directory Blocks: 0
    • Record Format: FB
    • Record Length: 80
    • Block Size: 0
    • Data Set Type: Library (PDSE)
  10. Create a data set definition for a data set named LOAD, which will store the program object that the build creates.
  11. In the General section, specify the following parameter:
    • Usage: Build output data set (created if it does not exist). This specifies that the new data set definition refers to an output data set that will be used by the build. In this tutorial, the LOAD data set will be used to hold the program object produced by the link-editor. If this data set does not exist, it will be allocated during the build process.
  12. Select Add data set prefix from build definition to data set name. This indicates that this data set should be prepended with the high-level qualifier associated with the build request.
  13. For data set characteristics, specify the following parameters:
    • Space Units: Cylinders
    • Primary Quantity: 1
    • Secondary Quantity: 1
    • Directory Blocks: 0
    • Record Format: U
    • Record Length: 0
    • Block Size: 32720
    • Data Set Type: Library (PDSE)
  14. Create a data set definition named TEMPFILE.
  15. In the General section, specify the following parameter:
    • Temporary data set used for build. This indicates that this data set will be allocated as a temporary file to be used by the build process.
  16. For data set characteristics, specify the following parameters:
    • Generic unit: SYSALLDA
      Tip: For better performance, if you can use VIO (virtual input/output) with your operating system, specify VIO for temporary data sets instead of SYSALLDA.
    • Space units: Tracks
    • Primary quantity: 5
    • Secondary quantity: 5
    • Data set type: Unspecified
    • All other fields: Accept the default values.
  17. Create a data set definition named IGYCRCTL. This data set definition describes the characteristics of the IBM® COBOL for z/OS compiler.
  18. In the General section, specify the following parameters:
    • Usage: Existing data set used for build.
    • Data set name: The name of the data set that contains the IGYCRCTL module; for example, IGY.V4R1M0.SIGYCOMP.
    • Member: IGYCRCTL
  19. Clear the Add data set prefix from build definition to data set name box.
  20. Create a data set definition named IEWBLINK. This data set definition describes the IEWBLINK module that is used to bind a program and store it in a program library.
  21. In the General section, specify the following parameters:
    • Usage: Existing data set used for build.
    • Data set name: Leave blank.
    • Member: IEWBLINK
  22. Clear the Add data set prefix from build definition to data set name box.
  23. Create a data set definition named SCEELKED. This should be the name of the data set on the build machine that contains the COBOL and LE link-edit stubs, generally named CEE.SCEELKED.
  24. In the General section, specify the following parameters:
    • Usage: Existing data set used for build.
    • Data set name: CEE.SCEELKED, or whatever is the name of the equivalent data set on your system.
    • Member: Leave blank.
  25. Clear the Add data set prefix from build definition to data set name box.
< Previous | Next >

video icon Video

Jazz.net channel
Software Education channel

learn icon Courses

IoT Academy
Skills Gateway

ask icon Community

Jazz.net
Jazz.net forums
Jazz.net library

support icon Support

IBM Support Community
Deployment wiki