DB2 TOOLS APPLCOMPAT(V12R1M507) OPTION IS NOT SUPPORTED

book

Article ID: 241474

calendar_today

Updated On:

Products

Detector for DB2 for z/OS Database Management for DB2 for z/OS - Administration Suite Database Management for DB2 for z/OS - Performance Suite Database Management for DB2 for z/OS - Recovery Suite Database Management for DB2 for z/OS - SQL Performance Suite Database Management for DB2 for z/OS - Utilities Suite

Issue/Introduction

The Bind job generated by the SSID0002 job failed with the following message:

BIND PACKAGE ( PTT3RCMA_ALLPKGS )                                        MEMBER     ( RMA#DBSP )
                     OWNER(OS1BOC)       CURRENTDATA ( NO   )                                           APPLCOMPAT  ( V12R1M507 )
    VALIDATE   ( RUN     )       ISOLATION  ( CS      )       FLAG       ( I       )       RELEASE    ( COMMIT  )       DBPROTOCOL (
 DRDA    )       ENCODING   ( EBCDIC  )       EXPLAIN    ( NO      ) ;
 DSNT225I  -D2DY BIND ERROR FOR PACKAGE
 B1001D02G.PTT3RCMA_ALLPKGS.RMA#DBSP
            APPLCOMPAT(V12R1M507) OPTION IS NOT SUPPORTED
 DSNT233I  -D2DY UNSUCCESSFUL BIND FOR
            PACKAGE =
 B1001D02G.PTT3RCMA_ALLPKGS.RMA#DBSP.(CAD200_2019-03-15-07.14.10)

 

Environment

Release : 20.0

Component : General Services for DB2

Resolution

This is an expected behavior. The APPLCOMPAT value is taken from SSIDVERF. Unless the applcompat is changed, Most packages will always stay on V12R1M500. There is a set of packages however:'BPASQL8' , BPASQLB1', 'BPASQL','RMA#DBTB', 'BPAFE08', 'BPAFE09', RMA#DBSP', SQA$CSYN','[email protected]','[email protected]','[email protected]' that are always bound with the function level of the SSID. Since the tools don't migrate to UTS objects in PTDB for some packages  the applcompat must be lower than 504 otherwise multi table T won't be allowed to be created. IN General the V12R1M500 is de facto baseline.