PI96080: SCHEMA NAME WAS NOT TRANSLATED

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When running DDL generation for table space cloning,
  user-defined SQL statements that are missing spaces next to the
  following special characters: '<', '=', '>=', '<=', '<>', '!=',
  '^=', ' !< ', ' !> ' might cause the following error:
  CKZ61325W SQL Error in Module CKZ06100
  DSNT408I SQLCODE = -206, ERROR: SCHEMA.NAME IS NOT VALID IN THE
  CONTEXT WHERE IT IS USED
  CKZ54726E Fatal Generate DDL Error
  where SCHEMA is the schema of the object in the SQL statement
  and NAME is the name of the object in the SQL statement.
  After applying this fix, the DDL statements are generated
  correctly.
  

Local fix

• Use spaces around '>','<', '=', '>=', '<=', '<>', '!=', '^=',
  '!< ', ' !> 'in the source objects.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of IBM Db2 Cloning Tool z/OS.          *
  ****************************************************************
  * PROBLEM DESCRIPTION: When running DDL generation for table   *
  *                      space cloning, user-defined SQL         *
  *                      statements that are missing spaces      *
  *                      next to the following special           *
  *                      characters: '<', '=', '>=', '<=', '<>', *
  *                      '!=', ' =', ' !< ', ' !> ' might        *
  *                      cause the following error:              *
  *                      CKZ61325W SQL Error in Module CKZ06100  *
  *                      DSNT408I SQLCODE = -206, ERROR:         *
  *                       SCHEMA.NAME IS NOT VALID IN THE        *
  *                       CONTEXT WHERE IT IS USED               *
  *                      CKZ54726E Fatal Generate DDL Error      *
  *                      where SCHEMA is the schema of the       *
  *                      object in the SQL statement and NAME    *
  *                      is the name of the object in the SQL    *
  *                      statement. After applying this fix,     *
  *                      the DDL statements are generated        *
  *                      correctly.                              *
  ****************************************************************
  * RECOMMENDATION: APPLY the PTF.                               *
  ****************************************************************
  Code has been changed to correct this condition.
  

Problem conclusion

• APPLY the PTF.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

•    CKZCPLNC
  

Fix information

• Fixed component name

  DB2 CLONING TOO

• Fixed component ID

  5655N1000

Applicable component levels

• R320 PSY UI55206

     UP18/04/17 P F804

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.