Updates to DB2 Cloning Tool V2.2 User's Guide

Product documentation


Abstract

Updates that apply to the DB2® Cloning Tool for z/OS® V2.2 User's Guide (SC19-2549-01).

Content

The most recent update is listed first.




Update 8
Date of change: 2/22/2012
Topic: Messages
Change description: The following messages were added or changed for PM56808.

New messages:

CKZ22403I DDNAME= ddname ALLOCATED FOR DSN=datasetname
Explanation: 'ddname' has been dynamically allocated for the specified data set.
User response: None.

CKZ22405E ALLOCATION FAILED FOR DSN: datasetname
Explanation: Dynamic allocation for a data set failed. The associated z/OS messages are displayed. Processing terminates.
User response: If unable to determine the reason for the failure from the associated z/OS messages, contact IBM® Customer Support. Have available the listing containing these messages.

CKZ22405W DEALLOCATION FAILED FOR DDNAME: ddname
Explanation: Dynamic deallocation for a ddname failed. The associated z/OS messages are displayed. Processing continues.
User response: If unable to determine the reason for the failure from the associated z/OS messages, contact IBM® Customer Support. Have available the listing containing these messages.

CKZ22423E SVC 99 INFORMATION RETRIEVAL FAILED; DDNAME: ddname R15= nnnn S99INFO= X'nnnn' S99ERROR= X'nnnn'
Explanation: The SVC 99 information retrieval of the data set name of the identified DD has failed. Processing terminates.
User response: Contact IBM® Customer Support. Have available the listing containing these messages.

CKZ22424E THE DATA SET NAME OF DDNAME: ddname DOES NOT HAVE DB2 FORMAT; datasetname
Explanation: The data set name of the data set allocated to the indicated ddname does not have a DB2 data set name form. DB2UPDATE is trying to determine if there are multiple data sets for the DB2 directory LOB space SYSDBDXA that need to be processed, but cannot determine what the data set names should be. Processing terminates.
User response: Change the JCL statement for the indicated ddname to point to a DB2 directory LOB space SYSDBDXA that has a DB2 format data set name and that also has a low level qualifier of A001.

CKZ22425E THE NUMBER OF DIRECTORY DATA SETS DISCOVERED IS GREATER THAN THE EXPECTED MAXIMUM OF 254
Explanation: More than 254 DB2 directory LOB space SYSDBDXA data sets have been discovered. A maximum of 254 data sets is expected. Processing terminates.
User response: Verify the data set being used corresponds to the correct DB2 directory LOB space SYSDBDX data set. If unable to resolve problem, contact IBM® Customer Support. Have available the listing that contains this message.

Changed message:

CKZ22431I THE ENDING RBA FOR DDNAME: ddname IS: X'nnnnnnnn_nnnnnnnn'

Explanation: The ending RBA of the directory file being processed.

User response: None.




Update 7
Date of change: 02/22/2012
Topic: Messages
Change description: The following message was added for PM33056.


CKZVE251E type error; VOLSER: volser CCHHR: cccchhhhrr CCHH_LO: cccchhhh CCHH_HI: cccchhhh POST: xx Loc: lllll

Explanation: An error occurred when trying to access or process the VVDS on the indicated volume. For type of EXCP, an error was returned from a read of a VVDS block. Other types indicate an expected record was not found in the VVDS. lllll is an internal indicator of where the problem occurred.

User response: Contact IBM® Customer Support. Have available the listing that contains this message.



Update 6
Date of change: 2/22/2012
Topics: Multiple
Change description: The following changes were made in support of PM49649:

1. “Copy command syntax”

Add the IGNORE-RF-MISMATCH-IF-NO-VAR-COLS keyword to COPY command syntax:

COPY command syntax
Optional Keywords:

[ ALLOW-COPY-ON-MISMATCH( Y | N ) ]
[ ALWAYS-COPY-INDEXSPACES ( Y | N ) ]
[ AUTO-START-SOURCE-SPACE( Y | N | R ) ]
[ AUTO-START-TARGET-SPACE( Y | N ) ]
[ AUTO-STOP-TARGET-SPACE( Y | N ) ]
[ CATALOG-PREFETCH(
  [ENABLE-PREFETCH ( Y | N ) ]
  [ENABLE-SOURCE-PREFETCH ( Y | N ) ]
  [ENABLE-TARGET-PREFETCH ( Y | N ) ]
  [SOURCE-PREFETCH-DATABASE-LIST ( sourcedatabase1, sourcedatabase2,
    . . . sourcedatabasen ) ) ]
  [TARGET-PREFETCH-DATABASE-LIST ( targetdatabase1, targetdatabase2,
.   . . targetdatabasen ) ) ]
[ CHECK-DATASET-COMPATIBILITY( Y | N ) ]
[ CHECK-INDEX-KEYS( Y | N ) ]
[ COPY-IF-NO-DB2-TARGET-OBJECTS( Y | N ) ]
[ DATA-MASKING ( Y | N ) ]
[ DATA-MOVER( PGM( ADRDSSU | EMCAPI | NONE )
  [ ,CMDDDNAME( ddname ) ]
  [ ,FASTREP( PREF | REQ | NONE ) ]
  [ ,FCTOPPRCPRIMARY ] ) ]
[ DATASETS-TO-COPY-DDN( ddname ) ]
[ DSNS-PER-COPY ( numberofdatasets ) ]
[ DSS-COPY-COMMANDS ( numberofcommands )
[ FUZZY-COPY( Y | N ) ]
[ IDCAMS-DDN( ddname ) ]
[ IGNORE-RF-MISMATCH-IF-NO-VAR-COLS( Y | N ) ]
[ INCLUDE-ALL-RI ( Y | N ) ]
[ JOB-TEMPLATE( inddname1, outddname1,...[ , inddnamen, outddnamen ] ) ]
 [ OBJECT-TRANSLATE(
  DATABASE, sourcedatabase, targetdatabase
    [DATABASE, sourcedatabasen, targetdatabasen ]
  TABLESPACE, sourcetablespace1, targettablespace1 . . .
    [TABLESPACE, sourcetablespacen, targettablespacen ]
  TABLE, sourcetable1, targettable1 . . .
    [TABLE, sourcetablen, targettablen ]
  INDEXSPACE, sourceindexspace1, targetindexspace1 . . .
    [INDEXSPACE, sourceindexspacen, targetindexspacen ]
  INDEX, sourceindex1, targetindex1 . . .
    [INDEX, sourceindexn, targetindexn ]
  CREATOR, sourcecreator1, targetcreator1 . . .
    [CREATOR, sourcecreatorn, targetcreatorn ] ) ]
[ REPLACE-TARGET-DSN( Y | N ) ]
[ RESET-LOGRBA( Y | N ) ]
[ SIMULATE( A | N | Y ) ]
[ SQLOUT-DDN( ddname ) ]
[ START-SOURCE-DDN( ddname ) ]
[ STOP-SOURCE-DDN( ddname ) ]
[ STOP-TARGET-DDN( ddname ) ]
[ SYNCDB2-DDN( ddname ) ]
[ V7-MIGRATED-OBJECTS-PRESENT( Y | N ) ]
[ WARN-IF-OBJECT-NOT-TRANSLATED( Y | N ) ]
[ WARN-ON-INCOMPLETE-RI( Y | N ) ]
[ WARN-ON-SIMPLE-TABLESPACE( Y | N ) ]
[ WARN-ON-VERSIONS( Y | N ) ]
[ XMLSTRING-DDN( ddname ) ]

2. “COPY command & keyword definitions"

Add the following command to COPY command & keyword definitions:

IGNORE-RF-MISMATCH-IF-NO-VAR-COLS( Y | N )
This parameter can be used to allow copy of table spaces from source to target when there is a mismatch involving reordered row format. For example, the source may have been migrated from DB2 V8 and be in basic row format (BRF), and the target objects may have been created on DB2 V9 NFM and be in reordered row format (RRF). When IGNORE-RF-MISMATCH-IF-NO-VAR-COLS is set to Y, table spaces with no variable columns can ignore the mismatch in row format and be copied without a warning. Variable columns are VARCHAR, LONGVAR, VARG, LONGVARG, and VARBIN.

When IGNORE-RF-MISMATCH-IF-NO-VAR-COLS is N, all reordered row mismatches are treated as mismatches. A copy of mismatched spaces is only allowed when ALLOW-COPY-ON-MISMATCH(Y). If ALLOW-COPY-ON-MISMATCH(Y) and IGNORE-RF-MISMATCH-IF-NO-VAR-COLS(Y), and there are one or more variable columns, a warning is issued and the space is copied. Note that any other incompatibility will override the processing of this command and ALLOW-COPY-ON-MISMATCH will determine if the space is copied.

    Default: None
    Required: No
    Restrictions: None
    Short form: VARCL

3. “Messages”

Add the following message:

CKZ54768I: Row Format Incompatibility Bypassed per the IGNORE-RF-MISMATCH-IF-NO-VAR-COLS(Y) Command, DB= source_database , TS= source_table_space
Explanation: This message is informational. It will print once for each partition if the tablespace is partitioned.
User response: None.




Update 5
Date of change: 12/13/2011
Topics: Multiple
Change description: The following changes were made in support of PM49245:

1. Topic: “Copy command syntax”

Add the CHECK-DATASET-COMPATIBILITY keyword to COPY command syntax:

COPY command syntax
Optional Keywords:

[ ALLOW-COPY-ON-MISMATCH( Y | N ) ]
[ ALWAYS-COPY-INDEXSPACES ( Y | N ) ]
[ AUTO-START-SOURCE-SPACE( Y | N | R ) ]
[ AUTO-START-TARGET-SPACE( Y | N ) ]
[ AUTO-STOP-TARGET-SPACE( Y | N ) ]
[ CATALOG-PREFETCH(
  [ENABLE-PREFETCH ( Y | N ) ]
  [ENABLE-SOURCE-PREFETCH ( Y | N ) ]
  [ENABLE-TARGET-PREFETCH ( Y | N ) ]
  [SOURCE-PREFETCH-DATABASE-LIST ( sourcedatabase1, sourcedatabase2,
    . . . sourcedatabasen ) ) ]
  [TARGET-PREFETCH-DATABASE-LIST ( targetdatabase1, targetdatabase2,
.   . . targetdatabasen ) ) ]
[ CHECK-DATASET-COMPATIBILITY( Y | N ) ]
[ CHECK-INDEX-KEYS( Y | N ) ]
[ COPY-IF-NO-DB2-TARGET-OBJECTS( Y | N ) ]
[ DATA-MASKING ( Y | N ) ]
[ DATA-MOVER( PGM( ADRDSSU | EMCAPI | NONE )
  [ ,CMDDDNAME( ddname ) ]
  [ ,FASTREP( PREF | REQ | NONE ) ]
  [ ,FCTOPPRCPRIMARY ] ) ]
[ DATASETS-TO-COPY-DDN( ddname ) ]
[ DSNS-PER-COPY ( numberofdatasets ) ]
[ DSS-COPY-COMMANDS ( numberofcommands )
[ FUZZY-COPY( Y | N ) ]
[ IDCAMS-DDN( ddname ) ]
[ JOB-TEMPLATE( inddname1, outddname1,...[ , inddnamen, outddnamen ] ) ]
[ INCLUDE-ALL-RI ( Y | N ) ]
[ OBJECT-TRANSLATE(
  DATABASE, sourcedatabase, targetdatabase
    [DATABASE, sourcedatabasen, targetdatabasen ]
  TABLESPACE, sourcetablespace1, targettablespace1 . . .
    [TABLESPACE, sourcetablespacen, targettablespacen ]
  TABLE, sourcetable1, targettable1 . . .
    [TABLE, sourcetablen, targettablen ]
  INDEXSPACE, sourceindexspace1, targetindexspace1 . . .
    [INDEXSPACE, sourceindexspacen, targetindexspacen ]
  INDEX, sourceindex1, targetindex1 . . .
    [INDEX, sourceindexn, targetindexn ]
  CREATOR, sourcecreator1, targetcreator1 . . .
    [CREATOR, sourcecreatorn, targetcreatorn ] ) ]
[ REPLACE-TARGET-DSN( Y | N ) ]
[ RESET-LOGRBA( Y | N ) ]
[ SIMULATE( A | N | Y ) ]
[ SQLOUT-DDN( ddname ) ]
[ START-SOURCE-DDN( ddname ) ]
[ STOP-SOURCE-DDN( ddname ) ]
[ STOP-TARGET-DDN( ddname ) ]
[ SYNCDB2-DDN( ddname ) ]
[ V7-MIGRATED-OBJECTS-PRESENT( Y | N ) ]
[ WARN-IF-OBJECT-NOT-TRANSLATED( Y | N ) ]
[ WARN-ON-INCOMPLETE-RI( Y | N ) ]
[ WARN-ON-SIMPLE-TABLESPACE( Y | N ) ]
[ WARN-ON-VERSIONS( Y | N ) ]
[ XMLSTRING-DDN( ddname ) ]

2. Topic: “COPY command & keyword definitions"

Add the following commands to COPY command & keyword definitions:

CHECK-DATASET-COMPATIBILITY( Y | N )
This parameter checks several VSAM data set attributes to determine if they are compatible between the source and target subsystems. The following attributes are checked:
- If the data set is in extended format.
- If the data set was allocated using extended addressability.
- Whether the data set can be compressed
- Whether the data set is striped.
- Whether the data set can be spanned.
These attributes must be the same between the source and target subsystems.

When one or more data set incompatibilities are found, no copies are attempted and the source job ends with RC=8.

IDCAMS LISTCAT commands are issued for each data set pair (source and target). IDCAMS commands and responses are output to the CKZLOG data set.

Use PGM(NONE) to check data set compatibility. Correct the data sets found to be incompatible. Then use PGM(ADRDSSU) to make the copies.

- Default: N.
- Required: No
- Restrictions: None
- Short form: CKDSN

3. Topic: “Messages”

Add the following messages:

CKZ54759W Dataset Mismatch, Attribute data_set_attribute, Source dsname = YES |
NO Target dsname = YES | NO
Explanation: This message is a warning. The data set attribute listed in the message does not match between source and target. There is a high probability that the source data set cannot be copied to the target.
User response: Redefine one or both data sets and resubmit the job.


CKZ54770E Subtask subtask_number, IDCAMS Execute Error, RC=return_code,
RS=IDCAMS_reason_code, Text to Follow...
Explanation: This message is an internal error. Additional text may follow this message.
User response: Contact IBM® Customer Support.


CKZ54771I Subtask subtask_number, IDCAMS Messages Follow...
Explanation: This message is informational.
User response: None.




Update 4
Date of change: August 30, 2011
Topic: Multiple
Change Description: The following changes were made in support of PM20396 and PM20410:

1. Topic: “Copy command syntax”

Add the CHECK-INDEX-KEYS keyword and the WARN-ON-SIMPLE-TABLESPACE keywords to COPY command syntax:

COPY command syntax
Optional Keywords:

[ ALLOW-COPY-ON-MISMATCH( Y | N ) ]
[ ALWAYS-COPY-INDEXSPACES ( Y | N ) ]
[ AUTO-START-SOURCE-SPACE( Y | N | R ) ]
[ AUTO-START-TARGET-SPACE( Y | N ) ]
[ AUTO-STOP-TARGET-SPACE( Y | N ) ]
[ CATALOG-PREFETCH(
    [ENABLE-PREFETCH ( Y | N ) ]
    [ENABLE-SOURCE-PREFETCH ( Y | N ) ]
    [ENABLE-TARGET-PREFETCH ( Y | N ) ]
    [SOURCE-PREFETCH-DATABASE-LIST ( sourcedatabase1, sourcedatabase2,
      . . . sourcedatabasen ) ) ]
    [TARGET-PREFETCH-DATABASE-LIST ( targetdatabase1, targetdatabase2,
      . . . targetdatabasen ) ) ]
 [ CHECK-INDEX-KEYS( Y | N ) ]
 [ COPY-IF-NO-DB2-TARGET-OBJECTS( Y | N ) ]
[ DATA-MASKING ( Y | N ) ]
[ DATA-MOVER( PGM( ADRDSSU | EMCAPI | NONE )
    [ ,CMDDDNAME( ddname ) ]
    [ ,FASTREP( PREF | REQ | NONE ) ]
    [ ,FCTOPPRCPRIMARY ] ) ]
[ DATASETS-TO-COPY-DDN( ddname ) ]
[ DSNS-PER-COPY ( numberofdatasets ) ]
[ DSS-COPY-COMMANDS ( numberofcommands )
[ FUZZY-COPY( Y | N ) ]
[ IDCAMS-DDN( ddname ) ]
[ JOB-TEMPLATE( inddname1, outddname1,...[ , inddnamen, outddnamen ] ) ]
[ INCLUDE-ALL-RI ( Y | N ) ]
[ OBJECT-TRANSLATE(
      DATABASE, sourcedatabase, targetdatabase
          [DATABASE, sourcedatabasen, targetdatabasen ]
      TABLESPACE, sourcetablespace1, targettablespace1 . . .
          [TABLESPACE, sourcetablespacen, targettablespacen ]
      TABLE, sourcetable1, targettable1 . . .
          [TABLE, sourcetablen, targettablen ]
      INDEXSPACE, sourceindexspace1, targetindexspace1 . . .
          [INDEXSPACE, sourceindexspacen, targetindexspacen ]
      INDEX, sourceindex1, targetindex1 . . .
          [INDEX, sourceindexn, targetindexn ]
      CREATOR, sourcecreator1, targetcreator1 . . .
          [CREATOR, sourcecreatorn, targetcreatorn ] ) ]
[ REPLACE-TARGET-DSN( Y | N ) ]
[ RESET-LOGRBA( Y | N ) ]
[ SIMULATE( A | N | Y ) ]
[ SQLOUT-DDN( ddname ) ]
[ START-SOURCE-DDN( ddname ) ]
[ STOP-SOURCE-DDN( ddname ) ]
[ STOP-TARGET-DDN( ddname ) ]
[ SYNCDB2-DDN( ddname ) ]
[ V7-MIGRATED-OBJECTS-PRESENT( Y | N ) ]
[ WARN-IF-OBJECT-NOT-TRANSLATED( Y | N ) ]
[ WARN-ON-INCOMPLETE-RI( Y | N ) ]
[ WARN-ON-SIMPLE-TABLESPACE( Y | N ) ]
[ WARN-ON-VERSIONS( Y | N ) ]
[ XMLSTRING-DDN( ddname ) ]

2. Topic: “COPY command and keyword definitions”
Add the following commands to COPY command & keyword definitions:

CHECK-INDEX-KEYS( Y | U )
When set to Y, the CHECK-INDEX-KEYS parameter makes additional checks on index compatibility. LIMITKEY is always checked and is normally sufficient. In some cases, a mismatch is missed unless the keys are read and checked also. If using index caching, run once with CHECK-INDEX-KEYS(Y), change any indexes to correct the mismatches, and then run with CHECK-INDEX-KEYS(N) or the default. Using this command may cause performance degradation, especially when there are many indexes to copy or caching is being used to access the catalog (caching is not supported for index keys).
• Default: N.
• Required: No
• Restrictions: None
• Short form: CIXKY

WARN-ON-SIMPLE-TABLESPACE ( Y | N  )
This command allows you to be warned when simple table spaces are to be copied. When N is specified, an informational message is printed for each simple table space found on the source or target subsystem. When Y is specified, a warning message is issued.
In some cases when a simple table space is copied by DB2 Cloning Tool Table Space Cloning, the copy may have duplicate rows. This is caused by incompatibilities between table spaces migrated from an earlier DB2 version and processed using DB2 Version 9.1 or later.

When a simple table space is copied for the first time, ensure the target table space is accessible and has the correct number of rows. Once all of the simple table spaces in a job are verified, use the default N to eliminate warning messages.
• Default: N
• Required: No
• Restrictions: None
• Short form: WOSTS

3. Topic: “Messages”

CKZ54738I Simple Tablespace Found, sss, ccc, ooo
Explanation: This message is informational. A simple tablespace was found in the catalog. This message prints when COPY subcommand WARN-ON-SIMPLE-TABLESPACE is N. sss = subsystem ccc = creator of the object ooo = name of the object
User response: When copied the first time, ensure the target object is accessible

CKZ54739W Simple Tablespace Found, sss, ccc, ooo
Explanation: This message is a warning. A simple table space was found in the catalog. This message prints when COPY subcommand WARN-ON-SIMPLE-TABLESPACE is Y. sss = subsystem ccc = creator of the object vvv = name of the object
User response: When copied the first time, ensure the target object is accessible.

CKZ54740W Source Object ooo ssss.ddd.iii cannot be matched with Target Object tttt.eee.jjj, src keys=nnn, trg keys=ppp
Explanation: This message is a warning. The number of columns differ from source to target index. ooo = object type (indexspace) ssss = source subsystem ddd = source database iii = source indexspace tttt = target subsystem ddd = target database jjj = target indexspace nnn = number of source keys ppp = number of target keys
User response: Change the source or target index so that they have the same keys. Resubmit the source job.




Update 3
Date of change: June 30, 2011
Topic: Multiple
Change Description: The following SET command changes were made to support the new AREOR status for DB2 10 and later. These changes were made with DB2 Cloning Tool PTF UK62827 and PM34769.

1. Topic: “
SET command & keyword definitions
Add the following possible value to the ADVISORY-STATUS-VALUES optional keyword syntax for the DB2 Cloning Tool Table Space Cloning SET command:
  • AREOR: advisory REORG-pending (DB2 10 and later)
Also, add AREOR to the default specification:
  • Default: ARBDP, AREO*, AREOR (for DB2 10 and later), and AUXW are used if no SET ADVISORY-STATUS-VALUES command is found.

2. Topic: “ SET command defaults (ISPF interface)
For the ISPF interface, add the following bullet to the Specifying ADVISORY-STATUS-VALUES defaults topic:
  • AREOR: advisory REORG-pending (DB2 10 and later)

Also, change the last bullet under the Selecting or deselecting an advisory status section to add the AREOR status to the default list:
  • Enter D to select only the default advisory status values. The default statuses are ARBDP, AREO*, AREOR (for DB2 10 and later), and AUXW.




Update 2
Date of change: March 31, 2011
Topic: Considerations for DB2 Version 9.1 and later
Change Description: The following changes were made to this topic:
  • Clarified the “Considerations for partition-by-growth table space" topic to better explain how PBG spaces are handled
  • Added the “Considerations for reordered row format in DB2 Version 9.1 NFM and later” section


1. Topic: “Considerations for partition-by-growth table spaces”

DB2 Version 9.1 introduced partitioning according to data growth. This enables segmented tables to be partitioned as they grow. DB2 Cloning Tool Table Space Cloning can copy partition-by-growth table spaces if the number of source partitions is equal to or less than the number of target partitions. However, if the number of source partitions is greater than the number of target partitions, DB2 Cloning Tool Table Space Cloning will create a DSN on the target for each partition that does not exist, using .F0001 as a data set name qualifier. This data set, and therefore the extra partitions, will not be usable on the target. If the number of partitions is greater on the source, you must create the extra partitions(s) on the target using the DB2 UNLOAD and LOAD utilities before initiating the cloning process.

2. Topic: “ Considerations for reordered row format in DB2 Version 9.1 NFM and late r
Reordered row format (RRF) is new with DB2 Version 9.1 NFM. It results in variable-length columns being placed at the end of a row. RRF is not compatible with objects that have been migrated from DB2 V8. Those objects will be in basic row format (BRF) until a REORG or LOAD REPLACE is run on the object under DB2 Version 9.1 NFM.

Newly created table spaces under DB2 Version 9.1 NFM are put in RRF. If a source BRF table space is copied to a target RRF table space (or vice versa), in most cases the target table(s) will not be accessible. DB2 Cloning Tool Table Space Cloning will issue a warning if the row formats do not match. Thus, if running DB2 Cloning Tool Table Space Cloning on DB2 Version 9.1 NFM or later subsystem, and new objects are added to LISTDEF, run the source job using DATA-MOVER(NONE) and SIM(N). All object incompatibilities will result in warning and/or error messages. REORG the table spaces in BRF and rerun the DB2 Cloning Tool Table Space Cloning source job to ensure there are no more object incompatibilities.




Update 1
Date of change: March 18, 2011
Topic: Multiple
Change Description: The following topics and messages were added in support of APAR PM28934. This APAR provides a new DB2 Cloning Tool Table Space Cloning command that can be used to specify the data subtype value (BIT, MIXED, or SBCS) needed by data masking.
  • DB2 Cloning Tool Table Space Cloning commands (Chapter 17)
  • Messages (in Chapter 21)


1. Topic:
“Chapter 17. DB2 Cloning Tool Table Space Cloning commands”
Add the DATASUBTYPE command to Table 42, DB2 Cloning Tool Table Space Cloning commands overview.

Add the following new topic to describe the new DATASUBTYPE command:

DATASUBTYPE

The DATASUBTYPE command is optional.

DATASUBTYPE may be used to specify the data subtype value (BIT, MIXED, or SBCS) needed by data masking.

The DATASUBTYPE command is useful when you are specifying data masking for a column that has been migrated from an earlier version of DB2 and has a blank for FOREIGNKEY in SYSIBM.SYSCOLUMNS.

If a source column has data masking specified and either the source or target has a blank for the FOREIGNKEY column in SYSCOLUMNS, the non-blank value will be used by data masking. This will not be reported as an object mismatch.

If both source and target have different non-blank values, a mismatch will be reported unless the source value is overridden by a DATASUBTYPE command. The source value for FOREIGNKEY will be used to perform data masking.

If the DATASUBTYPE command is found for a column, it overrides whatever FOREIGNKEY values exist in the catalog. If the source and target catalogs have the same non-blank value, but it differs from the DATASUBTYPE command value, the DATASUBTYPE command value still is used. No warning message will be issued.

If no FOREIGNKEY value is specified in the catalog or by command, SBCS will be used.

If the column specified in the masking definition is not a string column, any DATASUBTYPE command for this table and column is ignored. String columns are defined with TYPEDEF values CHAR, VARCHAR, LONGVAR, CLOB, DBCLOB and DISTINCT where the DATATYPEID is a string type.

DATASUBTYPE command syntax

DATASUBTYPE

Required keywords:

TABLECREATOR( tblcreator  )
TABLENAME( tblname  )
COLUMNNAME( colname  )
SUBTYPE( B | M | S  )

DATASUBTYPE command & keyword definitions
Required and conditionally required keywords are described first, followed by optional keywords

DATASUBTYPE
The DATASUBTYPE command is optional. This command may be used to specify the data subtype value. This value may be needed by data masking when a column has been migrated from an earlier version of DB2 and has a blank for FOREIGNKEY in SYSIBM. SYSCOLUMNS. If the DATASUBTYPE command is found for a column, it overrides whatever FOREIGNKEY values exist in the catalog.
  • Default: None
  • Required: No
  • Restrictions: None

Required DATASUBTYPE keywords:

TABLECREATOR ( creator-id )
TABLENAME ( table-name )
COLUMNNAME ( column-name )

TABLECREATOR, TABLENAME, and COLUMNNAME identify the source column that will be masked.
  • Default: None
  • Required: Yes
  • Restrictions: None
  • Short form: TBCR, TBNM, CLNM
SUBTYPE( B | M | S )
Indicates the data subtype to be assumed as the FOREIGNKEY in SYSCOLUMNS. Valid subtypes are B for BIT, M for MIXED, or S for SBCS.
  • Default: S
  • Required: No
  • Restrictions: None
  • Short form: SUBT

2. Topic: Messages

Add the following new messages:


CKZ53901E DATASUBTYPE Command Parsing Error, RC= rrr , RS= sss

Explanation: Source job initialization has failed to read the DATASUBTYPE command. rrr = return code sss = reason code

User response: Correct the input and resubmit the job.


CKZ53902E
vvv must be 128 characters or less

Explanation: The DATASUBTYPE field must be less than 128 characters. vvv = table creator, table name or column name

User response: Correct the input and resubmit the job.


CKZ53903I DATASUBTYPE
fff=vvv

Explanation: This gives the parsed vale for the given field. fff = field vvv = value

User response: None.


CKZ53904E Illegal Syntax in DATASUBTYPE Command, Field,
fff

Explanation: The field has an invalid DB2 value. fff = field

User response: Correct the input and resubmit the job.


CKZ53905E SUBTYPE must be S, B or M


Explanation: The FOREIGNKEY value is incorrect.

User response: Correct the input and resubmit the job.


CKZ53906E
fff must be 1 character

Explanation: This DATASUBTYPE field only has one valid length.

User response: Correct the input and resubmit the job.


CKZ54746I Source table ccc.ttt , Column lll , FOREIGNKEY Override using DATASUBTYPE command, was ooo , now nnn

Explanation: This message is informational. The new FOREIGNKEY value will be used to mask data for this column. ccc = source table creator ttt = source table name lll = source column name ooo = old source FOREIGNKEY value nnn = new source FOREIGNKEY value

User response: None.


CKZ54748I Source table ccc.ttt , Column lll , Target table ddd.uuu , Column mmm, both FOREIGNKEY values blank, use Product Default, S (SBCS)

Explanation: This message is informational. Both foreign key values are blank. The product default S (SBCS) will be used to mask data for this column. ccc = source table creator ttt = source table name lll = source column name ddd = target table creator uuu = target table name mmm = target column name

User response:
None.


CKZ54749I Source Table ccc.ttt , Column lll , Target Table ddd.uuu , Column mmm, Source FOREIGNKEY value blank, use Target, vvv

Explanation: This message is informational. The source FOREIGNKEY value is blank. The target FOREIGNKEY value will be used to mask data for this column. ccc = source table creator ttt = source table name lll = source column name ddd = target table creator uuu = target table name mmm = target column name vvv = FOREIGNKEY value used to mask this column

User response: None.


CKZ54757I Source Table
ccc.ttt , Column lll , Target Table ddd.uuu , Column mmm , Target FOREIGNKEY value blank, use Source, vvv

Explanation: This message is informational. The target FOREIGNKEY value is blank. The source FOREIGNKEY value will be used to mask data for this column. ccc = source table creator ttt = source table name lll = source column name ddd = target table creator uuu = target table name mmm = target column name vvv = FOREIGNKEY value used to mask this column

User response: None.


CKZ54758W Source Table
ccc.ttt , Column lll , FOREIGNKEY vvv , Target Table ddd.uuu , Column mmm , FOREIGNKEY www , Not Compatible

Explanation: This message is a warning that the source and target columns may not be compatible. ccc = source table creator ttt = source table name lll = source column name vvv = source FOREIGNKEY value ddd = target table creator uuu = target table name mmm = target column name www = target FOREIGNKEY value

User response: None.


CKZ99087E: Subtask
nn , iconv_open() error: Reason: rrr ; From CCSID: fff ; To CCSID: ttt

Explanation
: String column data conversion error was issued. C function iconv_open() has failed.

nn = subtask number
rrr = reason code; it may be:
  • EINVAL: the conversion between encoded character sets specified is not supported
  • ECUNNOENV: a CUN_RS_N0_UNI_ENV error was issued by Unicode Conversion Services
  • ECUNNOCONV: a CUN_RS_NO_CONVERSION error was issued by Unicode Conversion Services
  • ECUNNOTALIGNED : a CUN_RS_TABLE_NOT_ALIGNED error was issued by Unicode Conversion Services
  • ECUNERR: function iconv_open() encountered an unexpected error while using Unicode Conversion Services
fff = from CCSID
ttt = to CCSID

User response: Contact IBM® Customer Support.


CKZ99088E: Subtask nn , iconv() error: Reason: rrr ; From CCSID: fff ; To CCSID: ttt

Explanation: String column data conversion error was issued. C function iconv() has failed.

nn = subtask number
rrr = reason code; it may be:
  • EBADF: conversion descriptor is not valid
  • ECUNNOENV: a CUN_RS_N0_UNI_ENV error was issued by Unicode Conversion Services
  • ECUNNOCONV: a CUN_RS_NO_CONVERSION error was issued by Unicode Conversion Services
  • ECUNNOTALIGNED: a CUN_RS_TABLE_NOT_ALIGNED error was issued by Unicode Conversion Services
  • ECUNERR: function iconv() encountered an unexpected error while using Unicode Conversion Services
  • EILSEQ: input conversion stopped due to an input byte that does not belong to the input codeset
  • EINVAL: input conversion stopped due to an incomplete character or shift sequence at the end of the input buffer
  • E2BIG: input conversion stopped due to lack of space in the output buffer
fff = from CCSID
ttt = to CCSID

User response: Contact IBM® Customer Support.

CKZ99089E Subtask nn , Unable to add rule ' mmm ' because CCSID is not defined for column ccc.ttt ( fff ). Reason: rrr

Explanation: CCSID is not defined for string column because it was created prior to Version 8. The data masking module attempted to retrieve the CCSID from SYSIBM.SYSTABLESPACE but encountered an error.

nn = subtask number
mmm = mask rule name
ccc = creator name
ttt = table name
fff = column name
rrr = reason code; it may be:
  • The string column contains binary data and does not have valid CCSID
  • The subtype of string column is not valid
  • The database was created in a DB2 release prior to Version 5

User response:
If rrr = 1 then
  1. Remove mask rule from list of mask rules
  2. Change the mask rule to another column, or to the USEREXIT mask rule
If rrr = 2 or rrr = 3, contact IBM® Customer Support.


CKZ99090E Subtask
nn , Unable to add rule ' mmm ' because string column ccc.ttt ( fff ) contains binary data

Explanation:
Unable to add defined mask rule to string column which contains binary data. nn = subtask number mmm = mask rule name ccc = creator name ttt = table name fff = column name.

User response:
Remove mask rule from list of mask rules, or change the mask rule to another column, or to the USEREXIT mask rule.

Publication number

SC19-2549-01

Copyright date

2006, 2011

Rate this page:

(0 users)Average rating

Document information


More support for:

DB2 Tools for z/OS
DB2 Cloning Tool

Software version:

2.2.0

Operating system(s):

z/OS

Reference #:

7018361

Modified date:

2012-02-22

Translate my page

Machine Translation

Content navigation