-START CDDS command (Db2)

Environment for -START CDDS

This command can be issued from a z/OS® console, a DSN session under TSO, a DB2I panel (DB2 COMMANDS), an IMS or CICS® terminal, or a program that uses the instrumentation facility interface (IFI).

Authorization for -START CDDS

To execute this command, you must use a privilege set of the process that includes one of the following privileges or authorities:

• BSDS privilege
• SYSCTRL authority
• SYSADM authority

Db2 commands that are issued from a logged-on z/OS console or TSO SDSF can be checked by Db2 authorization using primary and secondary authorization IDs. A logged-on z/OS user ID must be defined in RACF or a similar security server.

Syntax for -START CDDS

Usage notes for -START CDDS

Trace information for data sharing members

When this command with group scope is issued in a Db2 data sharing member, it also runs on all other active members. IFICID 090 trace records for other group members can show that the same command was issued by the SYSOPR authorization ID from the 016.TLPKN5F correlation ID, in addition to the trace records from the member where the original command was issued. See Command scope in Db2 data sharing.

Examples for -START CDDS

Example: Allocating and opening the CDDS on a stand-alone Db2 subsystem

Issue this command:

-START CDDS

If the command is successful, output like this is displayed:

DSNJ375I - DSNJB101 CDDS DSNAME = cdds-name IS ACTIVE IN SOURCE_ONLY MODE.
DSN9022I - DSNJC001 'START CDDS' NORMAL COMPLETION

Example: Allocating and opening the CDDS on all members of a source data sharing group in a GDPS® Continuous Availability with zero data loss environment

Issue this command:

-START CDDS

If the command is successful, output like this is displayed:

DSNJ375I - DSNJB101 CDDS DSNAME = cdds-name IS ACTIVE IN SOURCE MODE.
DSN9022I - DSNJC001 'START CDDS' NORMAL COMPLETION