Name field

When specified, code a ddname as follows:
  • Each ddname should be unique within the job step. If duplicate ddnames appear in a job step, processing is as follows:
    • In a JES2 system: The system performs device and space allocation and disposition processing for both DD statements; however, it directs all references to the first DD statement in the step.
    • In a JES3 system: If both DD statements request JES3 or jointly-managed devices, the system cancels the job during JES3 interpretation. If only one or neither DD statement requests a JES3 or jointly-managed device, the system performs device and space allocation processing for both DD statements; however, it directs all references to the first DD statement in the step.
  • The ddname must begin in column 3.
  • The ddname is 1 through 8 alphanumeric or national ($, #, @) characters.
  • The first character must be alphabetic or national ($, #, @).
  • The ddname must be followed by at least one blank.
Omitting the ddname: Do not code a ddname when the DD statement defines a data set that is concatenated to the data set of the preceding DD statement. You can code PATH or DSNAME in either or both of the DD statements if your program uses BSAM, QSAM or BPAM.
Note: Prior to z/OS® V1R7 you could define indexed sequential data sets using DSORG=IS and a DD statement without a name.
Name field when overriding a procedure DD statement: Code the following in the name field of a DD statement that is to override a procedure DD statement:
  1. The name of the procedure step that contains the DD statement to be overridden
  2. Followed by a period
  3. Followed by the ddname of the procedure DD statement that is to be overridden.
Name field when adding a DD statement to a procedure: Code the following in the name field of a DD statement that is to be added to a procedure:
  1. The name of the procedure step to which the DD statement is to be added
  2. Followed by a period
  3. Followed by a ddname of your choosing.
For example: 
   //PROCSTP1.DDA DD parameters
Name field when adding a DD statement to a program: When you code a DD statement with a ddname of procstepname.ddname within a program step, the system:
  1. Checks the syntax of both the procstepname qualifier and the ddname qualifier
  2. Uses only the ddname qualifier as the statement ddname
  3. Adds the DD statement to the program step that contains the statement
  4. Issues an informational message because procstepname is coded outside of a procedure.

Special ddnames: Use the following special ddnames only when you want to use the facilities these names represent to the system. These facilities are explained in Special DD statements.

JOBLIB
STEPLIB
SYSABEND
SYSCKEOV
SYSMDUMP
SYSUDUMP

Do not use the following ddnames. They are reserved for compatibility with the prior releases of MVS.

JOBAT
STEPCAT

Do not use the following ddnames on a DD statement in a JES2 system. They have special meaning to JES2.

JESJCLIN
JESJCL
JESMSGLG
JESYSMSG

The following ddnames have special meaning to JES3; do not use them on a DD statement in a JES3 system.

JCBIN
JCBLOCK
JCBTAB
JESJCLIN
JESInnnn
JESJCL
JESMSGLG
JOURNAL
JST
JESYSMSG
JES3CATLG
J3JBINFO
J3SCINFO
J3STINFO
STCINRDR
TSOINRDR
Parent topic: Description