Creating a z/OS data set definition

Create a data set definition to describe the partitioned data set (PDS) that your build will reference.

Before you begin

This topic describes how to create a z/OS® data set definition.

Before you begin this task, you must create a System z® project area.

Restriction: Before you can create, modify, or delete a data set definition, you must have permission to make these modifications. You can manage these permissions from the Project Configuration node on the Process Configuration tab in the Project Area editor.

About this task

You can create a data set definition one of two ways:
  • Expand these nodes in the Team Artifacts navigator: Enterprise Extensions > System Definitions > z/OS > Data Set Definitions.
  • From the main menu, select File > New > Other > Enterprise Extensions > z/OS > Data Set Definition.

The following steps describe how to create a new data set definition from the Data Set Definitions node in the Team Artifacts navigator.

Procedure

  1. From the Team Artifacts view, select your repository connection and log in.
  2. Expand your team project node.
  3. Expand the Enterprise Extensions > System Definitions > z/OS nodes. Right-click the Data Set Definitions node and select New Data Set Definition. The Data Set Definition editor opens with two tabs: General and History.
  4. In the Name field, give your data set definition a name.
    Note: When running on z/OS V2R2, you can enter system symbols of up to 16 characters in the Name field. For more information on the symbols, see Chapter 2 of the MVS Initialization and Tuning Reference manual.
  5. On the General tab, specify the following attributes:
    1. Optional: In the Description field, briefly describe your new data set definition.
    2. In the Usage section, select the option that describes how you want your data set definition to be used. If you select Existing data set used for build, the Data Set Characteristics section is disabled except for the Volume serial and Generic unit fields. The Member field (under the Usage section) is also enabled.
    3. In the Data set name field, list the name of the z/OS data set described by this definition. For information about valid data set names, see z/OS data set naming rules.
      Note: If you select Add data set prefix from build definition to data set name, the prefix that you specified in the build definition will be added to the data set name.
    4. Select Compact outputs to compact the log files produced during builds. When the log file is a physical PDS, the log file is compressed to save space.
      Note: Compacted log files in the PDS can be decompressed in TSO using the BLZCMD API. For more information, refer to BLZCMD API Interface.
      When uploaded to a build result, trailing whitespace in the log file is removed.
    5. If you made changes to this data set definition that do not require a full analysis of buildable files, click the Ignore changes to this system definition for dependency builds check box. For more information about analysis of buildable files, see Running dependency builds on z/OS and IBM i systems.
    6. In the Data Set Characteristics section, specify your data set definition characteristics. Characteristics include:
      • Data class
      • Storage class
      • Management class
      • Volume serial
      • Generic unit
      • Space units
      • Primary quantity
      • Secondary quantity
      • Directory blocks
      • Record format
      • Record length
      • Block size
      • Additional parameters. Sometimes, additional allocation parameters might be necessary. For example, when you allocate a VSAM file as an existing data set used in a build, you might want to specify the BUFNO parm. When the build runs, the additional parameters are added to the parameters in the BPXWDYN interface, which allocates data sets.
        Note: The Additional parameters field is free format. You must know the format for BPXWDYN to enter parameters in the field correctly. For example, a parameter in JCL or TSO Allocate is sometimes different from the parameter in BPXWDYN.
      • A data set type. This can be either a partitioned data set extended (PDSE), a partitioned data set (PDS), a sequential data set, or in the case of a temporary data set, unspecified.
      Remember: If you select Existing data set used for build in the Usage field, only Volume serial and Generic unit are enabled.
      Note: You can use a build property to set a value for certain parameters at build time. For example, in the Volume serial field enter ${volser} to use the build property volser at build time. The following parameters support using a build property:
      • Data class
      • Storage class
      • Management class
      • Volume serial
      • Generic unit
  6. On the History tab, you can see all changes made over time by different users to the data set definition. You can review the state of the data set definition at any point in time, which is useful for debugging and fixing dependency build problems.
  7. Click Save.

What to do next

You can also duplicate any data set definition. To do this, perform the following steps:
  1. Open the Team Artifacts view.
  2. Expand the Data Set Definitions node.
  3. Right-click the data set definition you want to duplicate.
  4. Select Duplicate. The Duplicate system definition window opens.
  5. Give your duplicate system definition a name.
  6. Click OK to duplicate the data set definition or Cancel to stop.
  7. Your new duplicate data set definition should be displayed under the Data Set Definitions node. If it does not, refresh the view.

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