Information

This site will undergo a brief period of maintenance on Friday, 18 December at 12:30 AM Central/12:00 PM IST. During a 30 minute window, site availability may be intermittent.

Information
Space announcement We are no longer updating this space, and you cannot comment on this space. The IMAGE COPY PLUS component is now documented in BMC AMI Backup and Recovery for IMS.

DDN keyword


The DDN keyword is used in two ways: on function control statements, and on STACK and CHKPT control statements.

DDN keyword on function control statements

You can use the DDN keyword on function control statements (IC and AIC, OIC and AOIC, CIC and ACIC, IIC and AIIC, REC and AREC, and TRACE) to specify the ddname associated with the data set group to be processed.

The DDN keyword is valid only for full-function databases (including HALDBs); for DEDBs, specify the AREA keyword.

For full-function, non-HALDB databases, the value of the DDN keyword is the ddname associated with a data set group in the database definition. If the DDN keyword is omitted on control statements where it is optional and the database contains more than one data set group, you are implicitly requesting processing of each data set group that is defined in the database. The output image copies must be dynamically allocated. For the CIC, ACIC, IIC and AIIC functions, the input image copy data sets must be dynamically allocated. If the database contains only one data set group, you can omit the DDN keyword.

For HALDBs, the following considerations apply to the use of the DDN keyword:

  • To process all data set groups in all partitions in a HALDB implicitly, omit the DDN keyword and specify the DBALLOC(Y) keyword on the GLBL control statement.
  • To process all data set groups within a partition implicitly, specify the partition name with the DDN keyword.
  • To process individual data set groups within a partition, specify the data set group name with the DDN keyword.

DDN keyword on STACK and CHKPT control statements

The DDN keyword is required on STACK control statements and optional on CHKPT control statements.

You use it to specify the ddname to use for the stack or checkpoint data set or to specify a dynamic allocation model to use for dynamic allocation of the stack or checkpoint data set. If you do not specify it on a CHKPT control statement, the default name ICPCHKPT is used.

Uses

Required on the following control statements:

  • REC and AREC
  • TRACE (only when processing a full-function database)
  • STACK

Optional on the following control statements:

  • IC and AIC
  • OIC and AOIC
  • CIC and ACIC
  • IIC and AIIC
  • CHKPT

Related keywords

Refer also to the following keyword:

Syntax

DDN(value)

Values

If you are specifying this keyword on a function control statement, you must specify the ddname (1-8 alphanumeric characters) for the value.

If you are specifying this keyword on the STACK control statement, you can specify one or more specific ddnames for the value, or you can specify one or more dynamic allocation model names. Use the following syntax:

DDN(ddname,ddname,ddname, . . )

or

DDN((*,modelname),(*,modelname),(*,modelname), . . ).

If you are specifying this keyword on the CHKPT control statement, you can specify a ddname for the value, or you can specify a dynamic allocation model name. Use the following syntax:

DDN(ddname)

or

DDN((*,modelname)).

If you specify any dynamic allocation models for a control statement keyword, all specifications on that keyword must use models or explicit allocation. For example, the specification DDN(*,(*,modelname)) is invalid. The specification DDN( ddname,(*,modelname)) is valid.

Default

No default value on function control statements and STACK control statements; ICPCHKPT on CHKPT control statements.


Related topic


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

IMAGE COPY PLUS 5.1