Continuous Delivery is a method of getting new function into the market
in a more timely manner than the 3 year release cycle of a new version
of Db2. In Db2 V12 it uses function level to indicate a grouping of
new function. Db2 V12 at NFM or New Function Mode is Function Level
V12R1M500. To update the Function Level to higher level the ACTIVATE
command is used. This can be done through console command or by running
job DSNTIJAF. The code for new functions is delivered in the normal PTF
fashion and then must be activated in order to be used. There is a
ZPARM parameter and bind parameter that goes along with Function Level,
APPLCOMPAT. The APPLCOMPAT in the ZPARM covers the default for BIND and
can be overridden by the parameter APPLCOMPAT in the bind. So, you can
test your application packages by binding with the APPLCOMPAT of the new
Function Level before making the ZPARM APPLCOMPAT change.
***********************************************************************
LATEST LEVEL V12R1M510
***********************************************************************
== ==
== *** WARNING BEFORE ACTIVATING V12R1M510 *** ==
== ==
== SPECIAL INSTRUCTIONS TO ACTIVATE FUNCTION LEVEL (V12R1M510) ==
== USING IBMUSER THERE ARE 5 JOBS TO RUN IN THIS ORDER: ==
== 1. DSNC10.SVSC.HOLDCNTL(DL9TIJTC) ==
== 2. DSNC10.SVSC.HOLDCNTL(DL9TIJAF) ==
== 3. DSNC10.SVSC.HOLDCNTL(DL9TIJUZ) ==
== 4. DSNC10.SVSC.HOLDCNTL(DSNTIJOZ) ==
== 5. DSNC10.SVSC.HOLDCNTL(DL9TIJUA) ==
== ==
== Activating FUNCTION LEVEL V12R1M510 is required before migrating ==
== your Db2 12 environment to the next Db2 release. It does not ==
== introduce any new features, capabilities, or catalog changes. ==
== ==
== To reduce unforseen SQL incompatibilites with the newly ==
== introduced APPLCOMPAT, it is recommended to test your ==
== plans/packages with each APPLCOMPAT prior to V12R1M510 to ==
== ensure no incompatibilities are met when a new APPLCOMPAT is ==
== introduced. ==
== ==
== For example, if the plans/packages currently have an APPLCOMPAT ==
== of V12R1M508 and if you want them to be at APPLCOMPAT V12R1M510 ==
== test the plans/packages at V12R1M509, then if there are no ==
== incompatibilites, test at V12R1M510. ==
== ==
== *** It is recommended to leave NULLID packages (ie. SYSSTAT, ==
== SYSLN*,SYSLH*) at V12R1M500. ==
== ==
***********************************************************************
* After you have run all 5 jobs, this display command should give *
* these results. *
* *
* -DBCG DISPLAY GROUP DETAIL *
* DSN7100I -DBCG DSN7GCMD 260 *
* *** BEGIN DISPLAY OF GROUP(........) CATALOG LEVEL(V12R1M509) *
* CURRENT FUNCTION LEVEL(V12R1M510) *
* HIGHEST ACTIVATED FUNCTION LEVEL(V12R1M510) *
* HIGHEST POSSIBLE FUNCTION LEVEL(V12R1M510) *
* PROTOCOL LEVEL(2) *
* GROUP ATTACH NAME(....) *
* ---------------------------------------------------------------------
* DB2 SUB DB2 SYSTEM IRLM
* MEMBER ID SYS CMDPREF STATUS LVL NAME SUBSYS IRLMPROC
* -------- --- ---- -------- -------- ------ -------- ---- --------
* ........ 0 DBCG -DBCG ACTIVE 121510 S0W1 DJCG DBCGIRLM
* ---------------------------------------------------------------------
* SPT01 INLINE LENGTH: 32138 *
* *** END DISPLAY OF GROUP(........) *
* DSN9022I -DBCG DSN7GCMD 'DISPLAY GROUP ' NORMAL COMPLETION *
* *
***********************************************************************
== ==
== When using the Db2 Admin Tool after activating FUNCTION LEVEL ==
== 510 and run into a SQLCODE=-805, please follow the instructions ==
== below to BIND the ADBL packages/plans. ==
== 1. Run 'DBCGUTIL.SVSC.HOLDCNTL(DJ8COPY1)' using userid ==
== IBMUSER. ==
== 2. Run 'DBCGUTIL.SVSC.ADBC10.JOBS(A5BINDAB)' using userid ==
== IBMUSER. ==
== 3. Run 'DBCGUTIL.SVSC.ADBC10.JOBS(A6PLANAB)' using userid ==
== IBMUSER. ==
== ==
== For more information about FUNCTION LEVEL 510 please go to: ==
== https://www.ibm.com/support/knowledgecenter/SSEPEK_12.0.0/wnew/ ==
== src/tpc/db2z_fl_v12r1m510.html ==
== ==
***********************************************************************
PREVIOUS LEVEL V12R1M509
***********************************************************************
== ==
== *** WARNING BEFORE ACTIVATING V12R1M509 *** ==
== ==
== SPECIAL INSTRUCTIONS TO ACTIVATE FUNCTION LEVEL (V12R1M509) ==
== USING IBMUSER THERE ARE 5 JOBS TO RUN IN THIS ORDER: ==
== 1. DSNC10.SVSC.HOLDCNTL(DL3TIJTC) ==
== 2. DSNC10.SVSC.HOLDCNTL(DL3TIJAF) ==
== 3. DSNC10.SVSC.HOLDCNTL(DL3TIJUZ) ==
== 4. DSNC10.SVSC.HOLDCNTL(DSNTIJOZ) ==
== 5. DSNC10.SVSC.HOLDCNTL(DL3TIJUA) ==
== ==
== After activating FUNCTION LEVEL V12R1M509 and want to adopt ==
== the new features that are introduced with the new function ==
== level, you must REBIND the desired packages to APPLCOMPAT ==
== V12R1M509 to utilize new functionality. ==
== ==
== To reduce unforseen SQL incompatibilites with the newly ==
== introduced APPLCOMPAT, it is recommended to test your ==
== plans/packages with each APPLCOMPAT prior to V12R1M509 to ==
== ensure no incompatibilities are met when a new APPLCOMPAT is ==
== introduced. ==
== ==
== For example, if the plans/packages currently have an APPLCOMPAT ==
== of V12R1M507 and if you want them to be at APPLCOMPAT V12R1M509 ==
== test the plans/packages at V12R1M508, then if there are no ==
== incompatibilites, test at V12R1M509. ==
== ==
== *** It is recommended to leave NULLID packages (ie. SYSSTAT, ==
== SYSLN*,SYSLH*) at V12R1M500. ==
== ==
***********************************************************************
* After you have run all 5 jobs, this display command should give *
* these results. *
* *
* -DBCG DISPLAY GROUP DETAIL *
* DSN7100I -DBCG DSN7GCMD 260 *
* *** BEGIN DISPLAY OF GROUP(........) CATALOG LEVEL(V12R1M509) *
* CURRENT FUNCTION LEVEL(V12R1M509) *
* HIGHEST ACTIVATED FUNCTION LEVEL(V12R1M509) *
* HIGHEST POSSIBLE FUNCTION LEVEL(V12R1M509) *
* PROTOCOL LEVEL(2) *
* GROUP ATTACH NAME(....) *
* ---------------------------------------------------------------------
* DB2 SUB DB2 SYSTEM IRLM
* MEMBER ID SYS CMDPREF STATUS LVL NAME SUBSYS IRLMPROC
* -------- --- ---- -------- -------- ------ -------- ---- --------
* ........ 0 DBCG -DBCG ACTIVE 121509 S0W1 DJCG DBCGIRLM
* ---------------------------------------------------------------------
* SPT01 INLINE LENGTH: 32138 *
* *** END DISPLAY OF GROUP(........) *
* DSN9022I -DBCG DSN7GCMD 'DISPLAY GROUP ' NORMAL COMPLETION *
* *
***********************************************************************
== ==
== When using the Db2 Admin Tool after activating FUNCTION LEVEL ==
== 509 and run into a SQLCODE=-805, please follow the instructions ==
== below to BIND the ADBL packages/plans. ==
== 1. Run 'DBCGUTIL.SVSC.HOLDCNTL(DJ8COPY1)' using userid ==
== IBMUSER. ==
== 2. Run 'DBCGUTIL.SVSC.ADBC10.JOBS(A5BINDAB)' using userid ==
== IBMUSER. ==
== 3. Run 'DBCGUTIL.SVSC.ADBC10.JOBS(A6PLANAB)' using userid ==
== IBMUSER. ==
== ==
== For more information about the new features FUNCTION LEVEL 509 ==
== adds, please go to: ==
== https://www.ibm.com/support/knowledgecenter/SSEPEK_12.0.0/wnew/ ==
== src/tpc/db2z_fl_v12r1m509.html ==
== ==
***********************************************************************
PREVIOUS LEVEL V12R1M508
***********************************************************************
== ==
== *** WARNING BEFORE ACTIVATING V12R1M508 *** ==
== ==
== SPECIAL INSTRUCTIONS TO ACTIVATE FUNCTION LEVEL (V12R1M508) ==
== USING IBMUSER THERE ARE 5 JOBS TO RUN IN THIS ORDER: ==
== 1. DSNC10.SVSC.HOLDCNTL(DKBTIJTC) ==
== 2. DSNC10.SVSC.HOLDCNTL(DKBTIJAF) ==
== 3. DSNC10.SVSC.HOLDCNTL(DKBTIJUZ) ==
== 4. DSNC10.SVSC.HOLDCNTL(DSNTIJOZ) ==
== 5. DSNC10.SVSC.HOLDCNTL(DKBTIJUA) ==
== ==
== After activating FUNCTION LEVEL V12R1M508 and want to adopt ==
== the new features that are introduced with the new function ==
== level, you must REBIND the desired packages to APPLCOMPAT ==
== V12R1M508 to utilize new functionality. ==
== ==
== To reduce unforseen SQL incompatibilites with the newly ==
== introduced APPLCOMPAT, it is recommended to test your ==
== plans/packages with each APPLCOMPAT prior to V12R1M508 to ==
== ensure no incompatibilities are met when a new APPLCOMPAT is ==
== introduced. ==
== ==
== For example, if the plans/packages currently have an APPLCOMPAT ==
== of V12R1M506 and if you want them to be at APPLCOMPAT V12R1M508 ==
== test the plans/packages at V12R1M507, then if there are no ==
== incompatibilites, test at V12R1M508. ==
== ==
== *** It is recommended to leave NULLID packages (ie. SYSSTAT, ==
== SYSLN*,SYSLH*) at V12R1M500. ==
== ==
***********************************************************************
* After you have run all 5 jobs, this display command should give *
* these results. *
* *
* -DBCG DISPLAY GROUP DETAIL *
* DSN7100I -DBCG DSN7GCMD 260 *
* *** BEGIN DISPLAY OF GROUP(........) CATALOG LEVEL(V12R1M507) *
* CURRENT FUNCTION LEVEL(V12R1M508) *
* HIGHEST ACTIVATED FUNCTION LEVEL(V12R1M508) *
* HIGHEST POSSIBLE FUNCTION LEVEL(V12R1M508) *
* PROTOCOL LEVEL(2) *
* GROUP ATTACH NAME(....) *
* ---------------------------------------------------------------------
* DB2 SUB DB2 SYSTEM IRLM
* MEMBER ID SYS CMDPREF STATUS LVL NAME SUBSYS IRLMPROC
* -------- --- ---- -------- -------- ------ -------- ---- --------
* ........ 0 DBCG -DBCG ACTIVE 121508 S0W1 DJCG DBCGIRLM
* ---------------------------------------------------------------------
* SPT01 INLINE LENGTH: 32138 *
* *** END DISPLAY OF GROUP(........) *
* DSN9022I -DBCG DSN7GCMD 'DISPLAY GROUP ' NORMAL COMPLETION *
* *
***********************************************************************
== ==
== When using the Db2 Admin Tool after activating FUNCTION LEVEL ==
== 508 and run into a SQLCODE=-805, please follow the instructions ==
== below to BIND the ADBL packages/plans. ==
== 1. Run 'DBCGUTIL.SVSC.HOLDCNTL(DJ8COPY1)' using userid ==
== IBMUSER. ==
== 2. Run 'DBCGUTIL.SVSC.ADBC10.JOBS(A5BINDAB)' using userid ==
== IBMUSER. ==
== 3. Run 'DBCGUTIL.SVSC.ADBC10.JOBS(A6PLANAB)' using userid ==
== IBMUSER. ==
== ==
== For more information about the new features FUNCTION LEVEL 508 ==
== adds, please go to: ==
== https://www.ibm.com/support/knowledgecenter/SSEPEK_12.0.0/wnew/ ==
== src/tpc/db2z_fl_v12r1m508.html ==
== ==
***********************************************************************
PREVIOUS LEVEL V12R1M507
***********************************************************************
== ==
== *** WARNING BEFORE ACTIVATING V12R1M507 *** ==
== ==
== SPECIAL INSTRUCTIONS TO ACTIVATE FUNCTION LEVEL (V12R1M507) ==
== USING IBMUSER THERE ARE 5 JOBS TO RUN IN THIS ORDER: ==
== 1. DSNC10.SVSC.HOLDCNTL(DK7TIJTC) ==
== 2. DSNC10.SVSC.HOLDCNTL(DK7TIJAF) ==
== 3. DSNC10.SVSC.HOLDCNTL(DK7TIJUZ) ==
== 4. DSNC10.SVSC.HOLDCNTL(DK7TIJOZ) ==
== 5. DSNC10.SVSC.HOLDCNTL(DK7TIJUA) ==
== ==
== After activating FUNCTION LEVEL V12R1M507 and want to adopt ==
== the new features that are introduced with the new function ==
== level, you must REBIND the desired packages to APPLCOMPAT ==
== V12R1M507 to utilize new functionality. ==
== ==
== To reduce unforseen SQL incompatibilites with the newly ==
== introduced APPLCOMPAT, it is recommended to test your ==
== plans/packages with each APPLCOMPAT prior to V12R1M507 to ==
== ensure no incompatibilities are met when a new APPLCOMPAT is ==
== introduced. ==
== ==
== For example, if the plans/packages currently have an APPLCOMPAT ==
== of V12R1M505 and if you want them to be at APPLCOMPAT V12R1M507 ==
== test the plans/packages at V12R1M506, then if there are no ==
== incompatibilites, test at V12R1M507. ==
== ==
== *** It is recommended to leave NULLID packages (ie. SYSSTAT, ==
== SYSLN*,SYSLH*) at V12R1M500. ==
== ==
***********************************************************************
* After you have run all 5 jobs, this display command should give *
* these results. *
* *
* -DBCG DISPLAY GROUP DETAIL *
* DSN7100I -DBCG DSN7GCMD 260 *
* *** BEGIN DISPLAY OF GROUP(........) CATALOG LEVEL(V12R1M507) *
* CURRENT FUNCTION LEVEL(V12R1M507) *
* HIGHEST ACTIVATED FUNCTION LEVEL(V12R1M507) *
* HIGHEST POSSIBLE FUNCTION LEVEL(V12R1M507) *
* PROTOCOL LEVEL(2) *
* GROUP ATTACH NAME(....) *
* ---------------------------------------------------------------------
* DB2 SUB DB2 SYSTEM IRLM
* MEMBER ID SYS CMDPREF STATUS LVL NAME SUBSYS IRLMPROC
* -------- --- ---- -------- -------- ------ -------- ---- --------
* ........ 0 DBCG -DBCG ACTIVE 121507 S0W1 DJCG DBCGIRLM
* ---------------------------------------------------------------------
* SPT01 INLINE LENGTH: 32138 *
* *** END DISPLAY OF GROUP(........) *
* DSN9022I -DBCG DSN7GCMD 'DISPLAY GROUP ' NORMAL COMPLETION *
* *
***********************************************************************
== ==
== When using the Db2 Admin Tool after activating FUNCTION LEVEL ==
== 507 and run into a SQLCODE=-805, please follow the instructions ==
== below to BIND the ADBL packages/plans. ==
== 1. Run 'DBCGUTIL.SVSC.HOLDCNTL(DJ8COPY1)' using userid ==
== IBMUSER. ==
== 2. Run 'DBCGUTIL.SVSC.ADBC10.JOBS(A5BINDAB)' using userid ==
== IBMUSER. ==
== 3. Run 'DBCGUTIL.SVSC.ADBC10.JOBS(A6PLANAB)' using userid ==
== IBMUSER. ==
== ==
== For more information about the new features FUNCTION LEVEL 507 ==
== adds, please go to: ==
== https://www.ibm.com/support/knowledgecenter/SSEPEK_12.0.0/wnew/ ==
== src/tpc/db2z_fl_v12r1m507.html ==
== ==
***********************************************************************
PREVIOUS LEVEL V12R1M506
***********************************************************************
== ==
== *** WARNING BEFORE ACTIVATING V12R1M506 *** ==
== ==
== SPECIAL INSTRUCTIONS TO ACTIVATE FUNCTION LEVEL (V12R1M506) ==
== USING IBMUSER THERE ARE 5 JOBS TO RUN IN THIS ORDER: ==
== 1. DSNC10.SVSC.HOLDCNTL(DK3TIJTC) ==
== 2. DSNC10.SVSC.HOLDCNTL(DK3TIJAF) ==
== 3. DSNC10.SVSC.HOLDCNTL(DK3TIJUZ) ==
== 4. DSNC10.SVSC.HOLDCNTL(DK3TIJOZ) ==
== 5. DSNC10.SVSC.HOLDCNTL(DK3TIJUA) ==
== ==
== After activating FUNCTION LEVEL V12R1M506 and want to adopt ==
== the new features that are introduced with the new function ==
== level, you must REBIND the desired packages to APPLCOMPAT ==
== V12R1M506 to utilize new functionality. ==
== ==
== To reduce unforseen SQL incompatibilites with the newly ==
== introduced APPLCOMPAT, it is recommended to test your ==
== plans/packages with each APPLCOMPAT prior to V12R1M506 to ==
== ensure no incompatibilities are met when a new APPLCOMPAT is ==
== introduced. ==
== ==
== For example, if the plans/packages currently have an APPLCOMPAT ==
== of V12R1M504 and if you want them to be at APPLCOMPAT V12R1M506 ==
== test the plans/packages at V12R1M505, then if there are no ==
== incompatibilites, test at V12R1M506. ==
== ==
== *** It is recommended to leave NULLID packages (ie. SYSSTAT, ==
== SYSLN*,SYSLH*) at V12R1M500. ==
== ==
***********************************************************************
* After you have run all 5 jobs, this display command should give *
* these results. *
* *
* -DBCG DISPLAY GROUP DETAIL *
* DSN7100I -DBCG DSN7GCMD 260 *
* *** BEGIN DISPLAY OF GROUP(........) CATALOG LEVEL(V12R1M505) *
* CURRENT FUNCTION LEVEL(V12R1M506) *
* HIGHEST ACTIVATED FUNCTION LEVEL(V12R1M506) *
* HIGHEST POSSIBLE FUNCTION LEVEL(V12R1M506) *
* PROTOCOL LEVEL(2) *
* GROUP ATTACH NAME(....) *
* ---------------------------------------------------------------------
* DB2 SUB DB2 SYSTEM IRLM
* MEMBER ID SYS CMDPREF STATUS LVL NAME SUBSYS IRLMPROC
* -------- --- ---- -------- -------- ------ -------- ---- --------
* ........ 0 DBCG -DBCG ACTIVE 121506 S0W1 DJCG DBCGIRLM
* ---------------------------------------------------------------------
* SPT01 INLINE LENGTH: 32138 *
* *** END DISPLAY OF GROUP(........) *
* DSN9022I -DBCG DSN7GCMD 'DISPLAY GROUP ' NORMAL COMPLETION *
* *
***********************************************************************
== ==
== When using the Db2 Admin Tool after activating FUNCTION LEVEL ==
== 506 and run into a SQLCODE=-805, please follow the instructions ==
== below to BIND the ADBL packages/plans. ==
== 1. Run 'DBCGUTIL.SVSC.HOLDCNTL(DJ8COPY1)' using userid ==
== IBMUSER. ==
== 2. Run 'DBCGUTIL.SVSC.ADBC10.JOBS(A5BINDAB)' using userid ==
== IBMUSER. ==
== 3. Run 'DBCGUTIL.SVSC.ADBC10.JOBS(A6PLANAB)' using userid ==
== IBMUSER. ==
== ==
== For more information about the new features FUNCTION LEVEL 506 ==
== adds, please go to: ==
== https://www.ibm.com/support/knowledgecenter/SSEPEK_12.0.0/wnew/ ==
== src/tpc/db2z_fl_v12r1m506.html ==
== ==
***********************************************************************
PREVIOUS LEVEL V12R1M505
***********************************************************************
== ==
== *** WARNING BEFORE ACTIVATING V12R1M505 *** ==
== ==
== SPECIAL INSTRUCTIONS TO ACTIVATE FUNCTION LEVEL (V12R1M505) ==
== USING IBMUSER THERE ARE 5 JOBS TO RUN IN THIS ORDER: ==
== 1. DSNC10.SVSC.HOLDCNTL(DK2TIJTC) ==
== 2. DSNC10.SVSC.HOLDCNTL(DK2TIJAF) ==
== 3. DSNC10.SVSC.HOLDCNTL(DK2TIJUZ) ==
== 4. DSNC10.SVSC.HOLDCNTL(DK2TIJOZ) ==
== 5. DSNC10.SVSC.HOLDCNTL(DK2TIJUA) ==
== ==
== After activating FUNCTION LEVEL V12R1M505 and want to adopt ==
== the new features that are introduced with the new function ==
== level, you must REBIND the desired packages to APPLCOMPAT ==
== V12R1M505 to utilize new functionality. ==
== ==
== To reduce unforseen SQL incompatibilites with the newly ==
== introduced APPLCOMPAT, it is recommended to test your ==
== plans/packages with each APPLCOMPAT prior to V12R1M505 to ==
== ensure no incompatibilities are met when a new APPLCOMPAT is ==
== introduced. ==
== ==
== For example, if the plans/packages currently have an APPLCOMPAT ==
== of V12R1M503 and if you want them to be at APPLCOMPAT V12R1M505 ==
== test the plans/packages at V12R1M504, then if there are no ==
== incompatibilites, test at V12R1M505. ==
== ==
== *** It is recommended to leave NULLID packages (ie. SYSSTAT, ==
== SYSLN*,SYSLH*) at V12R1M500. ==
== ==
***********************************************************************
* After you have run all 5 jobs, this display command should give *
* these results. *
* *
* -DBCG DISPLAY GROUP DETAIL *
* DSN7100I -DBCG DSN7GCMD 260 *
* *** BEGIN DISPLAY OF GROUP(........) CATALOG LEVEL(V12R1M505) *
* CURRENT FUNCTION LEVEL(V12R1M505) *
* HIGHEST ACTIVATED FUNCTION LEVEL(V12R1M505) *
* HIGHEST POSSIBLE FUNCTION LEVEL(V12R1M506) *
* PROTOCOL LEVEL(2) *
* GROUP ATTACH NAME(....) *
* ---------------------------------------------------------------------
* DB2 SUB DB2 SYSTEM IRLM
* MEMBER ID SYS CMDPREF STATUS LVL NAME SUBSYS IRLMPROC
* -------- --- ---- -------- -------- ------ -------- ---- --------
* ........ 0 DBCG -DBCG ACTIVE 121506 S0W1 DJCG DBCGIRLM
* ---------------------------------------------------------------------
* SPT01 INLINE LENGTH: 32138 *
* *** END DISPLAY OF GROUP(........) *
* DSN9022I -DBCG DSN7GCMD 'DISPLAY GROUP ' NORMAL COMPLETION *
* *
***********************************************************************
== ==
== When using the Db2 Admin Tool after activating FUNCTION LEVEL ==
== 505 and run into a SQLCODE=-805, please follow the instructions ==
== below to BIND the ADBL packages/plans. ==
== 1. Run 'DBCGUTIL.SVSC.HOLDCNTL(DJ8COPY1)' using userid ==
== IBMUSER. ==
== 2. Run 'DBCGUTIL.SVSC.ADBC10.JOBS(A5BINDAB)' using userid ==
== IBMUSER. ==
== 3. Run 'DBCGUTIL.SVSC.ADBC10.JOBS(A6PLANAB)' using userid ==
== IBMUSER. ==
== ==
== For more information about the new features FUNCTION LEVEL 505 ==
== adds, please go to: ==
== https://www.ibm.com/support/knowledgecenter/SSEPEK_12.0.0/wnew/ ==
== src/tpc/db2z_fl_v12r1m505.html ==
== ==
***********************************************************************
PREVIOUS LEVEL V12R1M504
***********************************************************************
==* *** WARNING BEFORE ACTIVATING V12R1M504 *** *==
==* *==
==* Before running the jobs to ACTIVATE V12R1M504 run this *==
==* query with SPUFI using IBMUSER: *==
==* DSNC10.SVSC.HOLDCNTL(DJ7SQL1) *==
==* Follow the instructions, if there are any rows returned. *==
==* *==
==* CREATE TABLESPACE statements that previously created non-UTS *==
==* segmented or partitioned table spaces, now always create *==
==* partition-by-growth or partition-by-range table spaces. *==
==* The following SQL statements now return errors: *==
==* CREATE SYNONYM statements *==
==* CREATE TABLE statements that specify existing non-UTS *==
==* table spaces *==
==* CREATE TABLE and ALTER TABLE statements that specify *==
==* ORGANIZE BY HASH *==
==* *==
==* SPECIAL INSTRUCTIONS TO ACTIVATE FUNCTION LEVEL (V12R1M504) *==
==* USING IBMUSER THERE ARE 5 JOBS TO RUN IN THIS ORDER: *==
==* 1. DSNC10.SVSC.HOLDCNTL(DJ7TIJTC) *==
==* 2. DSNC10.SVSC.HOLDCNTL(DJ7TIJAF) *==
==* 3. DSNC10.SVSC.HOLDCNTL(DJ7TIJUA) *==
==* 4. DSNC10.SVSC.HOLDCNTL(DJ7TIJUZ) *==
==* 5. DSNC10.SVSC.HOLDCNTL(DJ7TIJOZ) *==
==* *==
***********************************************************************
* *
* After you have run all 5 jobs, this display command should give *
* these results. *
* *
* -DBCG DISPLAY GROUP DETAIL *
* DSN7100I -DBCG DSN7GCMD 260 *
* *** BEGIN DISPLAY OF GROUP(........) CATALOG LEVEL(V12R1M503) *
* CURRENT FUNCTION LEVEL(V12R1M504) *
* HIGHEST ACTIVATED FUNCTION LEVEL(V12R1M504) *
* HIGHEST POSSIBLE FUNCTION LEVEL(V12R1M504) *
* PROTOCOL LEVEL(2) *
* GROUP ATTACH NAME(....) *
* ---------------------------------------------------------------------
* DB2 SUB DB2 SYSTEM IRLM
* MEMBER ID SYS CMDPREF STATUS LVL NAME SUBSYS IRLMPROC
* -------- --- ---- -------- -------- ------ -------- ---- --------
* ........ 0 DBCG -DBCG ACTIVE 121504 S0W1 DJCG DBCGIRLM
* ---------------------------------------------------------------------
* SPT01 INLINE LENGTH: 32138 *
* *** END DISPLAY OF GROUP(........) *
* DSN9022I -DBCG DSN7GCMD 'DISPLAY GROUP ' NORMAL COMPLETION *
* *
***********************************************************************
PREVIOUS LEVEL V12R1M502
***********************************************************************
==* *==
==* SPECIAL INSTRUCTIONS TO ACTIVATE FUNCTION LEVEL (V12R1M502) *==
==* USING IBMUSER THERE ARE 5 JOBS TO RUN IN THIS ORDER: *==
==* 1. DSNC10.SVSC.HOLDCNTL(DSNTIJTC) *==
==* 2. DSNC10.SVSC.HOLDCNTL(DSNTIJAF) *==
==* 3. DSNC10.SVSC.HOLDCNTL(DSNTIJUA) *==
==* 4. DSNC10.SVSC.HOLDCNTL(DSNTIJUZ) *==
==* 5. DSNC10.SVSC.HOLDCNTL(DSNTIJOZ) *==
==* *==
***********************************************************************
* *
* After you have run all 5 jobs, this display command should give *
* these results. *
* *
* -DBCG DISPLAY GROUP DETAIL *
* DSN7100I -DBCG DSN7GCMD *
* *** BEGIN DISPLAY OF GROUP(........) CATALOG LEVEL(V12R1M502) *
* CURRENT FUNCTION LEVEL(V12R1M502) *
* HIGHEST ACTIVATED FUNCTION LEVEL(V12R1M502) *
* HIGHEST POSSIBLE FUNCTION LEVEL(V12R1M502) *
* PROTOCOL LEVEL(2) *
* GROUP ATTACH NAME(....) *
* ---------------------------------------------------------------------
* DB2 SUB DB2 SYSTEM IRLM
* MEMBER ID SYS CMDPREF STATUS LVL NAME SUBSYS IRLMPROC
* -------- --- ---- -------- -------- ------ -------- ---- --------
* ........ 0 DBCG -DBCG ACTIVE 121502 S0W1 DJCG DBCGIRLM
* ---------------------------------------------------------------------
* SPT01 INLINE LENGTH: 32138 *
* *** END DISPLAY OF GROUP(........) *
* DSN9022I -DBCG DSN7GCMD 'DISPLAY GROUP ' NORMAL COMPLETION *
* *
***********************************************************************
PREVIOUS LEVEL V12R1M501
***********************************************************************
==* *==
==* SPECIAL INSTRUCTIONS TO ACTIVATE FUNCTION LEVEL (V12R1M501) *==
==* USING IBMUSER FROM SD.LOG. *==
==* ENTER / *==
==* ON THE NEXT SCREEN YOU CAN ISSUE THIS COMMAND *==
==* -DBCG ACTIVATE FUNCTION LEVEL (V12R1M501) TEST *==
==* YOU SHOULD SEE MEMBER IS ELIGIBLE, THEN ENTER / AGAIN *==
==* -DBCG ACTIVATE FUNCTION LEVEL (V12R1M501) *==
==* YOU SHOULD SEE THE OUTPUT BELOW: *==
==* *==
***********************************************************************
* *
* -DBCG ACTIVATE FUNCTION LEVEL (V12R1M501) *
* DSNU757I -DBCG DSNUGCCA 132 *
* *** BEGIN ACTIVATE FUNCTION LEVEL (V12R1M501) *
* FUNCTION LEVEL (V12R1M501) SUCCESSFULLY ACTIVATED *
* *
* CATALOG LEVEL(V12R1M500) *
* CURRENT FUNCTION LEVEL(V12R1M501) *
* HIGHEST ACTIVATED FUNCTION LEVEL(V12R1M501) *
* HIGHEST POSSIBLE FUNCTION LEVEL(V12R1M501) *
* *
* DSN9022I -DBCG DSNZACMD '-ACTIVATE FUNC' NORMAL COMPLETION *
* *
***********************************************************************
***********************************************************************
==* *==
==* YOU CAN USE THIS COMMAND TO DISPLAY INFORMATION ABOUT DBCG: *==
==* /-DBCG DISPLAY GROUP *==
==* *==
***********************************************************************
***********************************************************************
==* *==
==* Function Level V12R1M501 adds SQL Builtin function LISTAGG. *==
==* Here is an example of its use: *==
==* *==
==* SELECT WORKDEPT, *==
==* LISTAGG(LASTNAME, ', ') WITHIN GROUP(ORDER BY LASTNAME) *==
==* AS EMPLOYEES *==
==* FROM EMP *==
==* GROUP BY WORKDEPT ; *==
==* *==
==* If you want to run this example you will need to run this job *==
==* from IBMUSER DSNC10.SVSC.HOLDCNTL(BINDSPFI) to bind SPUFI *==
==* with APPLCOMPAT(V12R1M501) in order to make the LISTAGG *==
==* available to SPUFI. *==
==* *==
***********************************************************************
***********************************************************************
==* *==
==* The APPLCOMPAT=V12R1M500, is still set in DSNTIJUZ you MUST *==
==* test your PACKAGES by binding with APPLCOMPAT(V12R1M501) *==
==* BEFORE changing DSNTIJUZ to APPLCOMPAT=V12R1M500, to default *==
==* all BIND packages to V12R1M501 FUNCTION LEVEL. *==
==* *==
==* WARNING: WE WILL BE CHANGING TO APPLCOMPAT=V12R1M500, IN THE *==
==* BASE COPY DSNTIJUZ IN THE NEAR FUTURE. *==
==* *==
==* Manuals and information can be found at the url listed below: *==
==* *==
https://www-01.ibm.com/support/docview.wss?uid=swg27047206#db2z12new
==* *==
***********************************************************************