Previous Topic Next topic Print topic


DLBL

Associates a DD name with a dataset.

Syntax:

      *---------------------------------------------------------------
      *--- DLBL OPERANDS
      *--- // DLBL filename
      *---          file-id
      *---          date
      *---          codes
      *---          DSF
      *---          BLKSIZE
      *---          BUFND
      *---          BUFNI
      *---          BUFSP
      *---          CAT
      *- --         CISZ
      *- --         DISP
      *---          RECORDS
      *---          RECSIZE
      *---------------------------------------------------------------

Where:

Operand Description
filename   DD name
file-id   A unique name which identifies a dataset in the system catalog

DSNs that start with a $$$ prefix are treated as temporary ones - for example:

// DLBL filename, '$$$.xxx.yyyy'
date   Retention period in days (0 to 9999) or Julian date
codes Parsed but not processed* VSAM SD or DA
DSF Parsed but not processed* A data-secured file
BLKSIZE   Block size
BUFND Parsed but not processed* Number of I/O buffers
BUFNI Parsed but not processed* Number of index buffers
BUFSP Parsed but not processed* Number of bytes allocated for buffer space.
CAT Parsed but not processed* Catalog name; single system catalog in MF
CISZ Parsed but not processed* Control Interval size
DISP   Disposition opened, after normal step end, after abnormal step end
RECORDS Parsed but not processed* Number of records for primary and secondary space allocation
RECSIZE   Average record length
Note: The command and operand combinations listed in these topics are supported unless indicated as "parsed but not processed". Where indicated, this means:
  • Parsed but not processed - indicates that the command and the operand are not supported, however, Enterprise Developer parses it and, if it fails validation, a JCL error is generated.
  • Parsed but not processed* - indicates that a number of the operands for JCL and POWER commands (for example, any tape or volume-specific operands) do not apply in the Micro Focus Enterprise Developer environment. See General Differences.
Previous Topic Next topic Print topic