PI61638: NEW OBJECT TYPE VERIFICATION EXITS IN MASKING.

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• New object type verification exits in masking.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of the DB2 Administration Tool for     *
  *                 z/OS.                                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: 1 - User wants to be able to verify     *
  *                      that the catalog values for objects     *
  *                      being compared are valid on their       *
  *                      system.                                 *
  *                                                              *
  *                      2 - User wants any incorrect            *
  *                      input that will impact catalog          *
  *                      columns to be reported and              *
  *                      the process stopped if errors are       *
  *                      found.                                  *
  *                                                              *
  *                      3. - User wants to use the new          *
  *                      verification mask format when           *
  *                      performing the abovementioned           *
  *                      actions.                                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Currently, there is no provision in DB2 Admin Tool and DB2
  Object Comparison Tool to have an object type level mask that
  would allow a user to verify all columns that are in that
  object type's catalog table  ( e.g.  SYSTABLESPACE, SYSTABLES).
  The capability of specifying object type level masks that
  would allow a user to use a REXX exit to verify the values
  in the catalog table for that object has been added.  These
  masks will only be triggered at the CREATE object level for
  all objects that are not constraints.
  
  New syntax for the masking function to support this
  object type masking is as follows:
  
  VER,xx;REXX(exitname,arg1,arg2....)
  
  Where xx is object type: SG,DB,TB,TS,IX,VW,SY,AL
  SP,TG,FU,DT,SQ,GV and for constraints objtype: FK,
  PK, UQ or CK.  arg1 ...etc are catalog column names
  based on respective catalog record and object type.
  Catalog columns that are LOB or XML columns are not
  supported.
  
  For example, for a TB object type:
  
  VER,TB:REXX(exitname,TYPE,NAME,
  CREATOR)
  
  SYSTABLES catalog record information will be passed
  to a REXX exit called exitname where TYPE, NAME,
  and CREATOR are DB2 catalog values for SYSTABLES
  for any table object being compared.
  
  The object type codes and their corresponding object
  type and catalog record is listed here:
  
  Object      Object
  type code   type                 Catalog record
  
  SG          Storage group        SYSSTOGROUP
  DB          Database             SYSDATABASE
  TS          Table Space          SYSTABLESPACE
  TB          Table                SYSTABLES
  IX          Index                SYSINDEXES
  TG          Trigger              SYSTRIGGERS
  FK          Foreign Key          SYSRELS
  PK          Primary key          SYSTABCONST
  CK          Check Constraint     SYSCHECKS
  UQ          Unique Constraint    SYSTABCONST
  DT          Data type            SYSDATATYPES
  FU          Function             SYSROUTINES
  SP          Procedure            SYSROUTINES
  SQ          Sequence             SYSSEQUENCES
  SY          Synonyms             SYSSYNONYMS
  VW          View                 SYSVIEWS
  GV          Global variable      SYSVARIABLES
  AL          Alias                SYSTABLES
  
  Like the other verification masks that use REXX exit,
  a user creates their own REXX code to do the verification
  and then returns a string with the format RC:msg
  where RC is a two byte return code ( valid values are
  00,04,06,08,12), and msg is the message that will go
  into the VALOUT dataset.  If the RC value is not one of
  the valid values, a new error message, ADB3352E /
  msgadb3352e will be issued and the processing will stop:
  
  ADB3352E: The return code from the verification
  mask REXX exit is incorrect.  return code =  rc
  
  Explanation:The return code returned from the REXX
  exit for verification mask checking was not a valid
  return code.  Only 0,4,6,8,12 are allowed.
  User action: Correct the REXX exit to pass return
  code in the first 2 bytes of message
  System action: Processing stops.
  
  A new message, ADB3349E / msgadb3349e will be issued
  if the new object type masks are used without a REXX exit:
  
  ADB3349E:  The following mask type has to be used
  as a verification mask that uses a REXX exit.
  Mask type:   mask_type
  
  Explanation:  The mask type used has to be a
  verification mask using a REXX exit for verification.
  User action: Correct the mask request by using
  verification mask syntax with REXX exit.
  System action:Processing stops.
  
  If a catalog column being requested is blank,  it will
  be changed to a period (.), so that the PARSE ARG
  parameters will line up correctly.  The user will have
  to perform a check on the catalog columns that can
  be blank and check for the period instead.
  
  If a catalog column being requested cannot be found
  a minus (-) will be passed.
  
  The message length for the message that goes into VALOUT can
  be up to 1024 characters.
  
  To create line breaks in the message passed by the REXX exit
  to the VALOUT data set, a user can add a hex '15'X character
  in the message where the user wants to have the message go
  to the next line.
  
  Verification masking is only allowed with compare process
  and GEN, in all other areas, verification masks are ignored.
  

Problem conclusion

Temporary fix

Comments

• Enhancements have been delivered.
  

APAR Information

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

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

  UI39392

Modules/Macros

• ADBCCM   ADBCDTS  ADBCEXP  ADBCP    ADBCRCM  ADBCRSP  ADBCVOC
  ADBC31   ADBHC2L  ADBIRXF  ADB2CID  ADB2CME  ADB2CMF  ADB2CMM
  ADB2CMO  ADB2CMP  ADB2CMR  ADB2CMS  ADB2CMT  ADB2CMU  ADB2CM1
  ADB2CM2  ADB2CM3  ADB2C2L  ADB2C21  ADB2DEP  ADB2MASK ADB2MSK
  ADB2MSQ  ADB2RE   ADB2REE  ADB2REG  ADB2REH  ADB2REM  ADB2REP
  ADB2RER  ADB2RES  ADB2RET  ADB2REU  ADB2REZ  ADB2RGC  ADB2RS
  ADB2WCL  ADB2WVL  ADB28MC  ADB28MM  ADB3000
  

Fix information

• Fixed component name

  DB2 ADMIN TOOL

• Fixed component ID

  568851500

Applicable component levels

• RB20 PSY UI39392

     UP16/07/16 P F607

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.