Forum

Hi Zefrim,

I don’t know about DECP810 or DECP910 as constant value in DSNZPARM/DSNDECP – this may be a locally used specific output name.

But you could check for existence of new ZPARMS values. Or you could check the esxistence of new DB2 catalog columns or tables.

Much more easier is to execute a -DISPLAY DB2 command and to examine its output

-DISPLAY GROUP [DETAIL] provides (as an example) the DB2 catalog level ….
in V10:
[tt]DSN7100I -DB1A DSN7GCMD
*** BEGIN DISPLAY OF GROUP(DSNDB10 ) CATALOG LEVEL(101) MODE(C   )
           PROTOCOL LEVEL(2)  GROUP ATTACH NAME(DB10)
[/tt]
in V9:
[tt]DSN7100I -DB1A DSN7GCMD
*** BEGIN DISPLAY OF GROUP(DSNDB10 ) CATALOG LEVEL(910) MODE(C )
           PROTOCOL LEVEL(2)  GROUP ATTACH NAME(DB10)[/tt]
in V8
[tt]DSN7100I -DB1A DSN7GCMD
*** BEGIN DISPLAY OF GROUP(DSNCAT1) GROUPLEVEL(810) |MODE(E)
           PROTOCOL LEVEL(2)  GROUP ATTACH NAME(CAT1)[/tt]

And as an side effect you’ll get the MODE your DB2 currently operates:
MODE (here: V8)
    Indicates the catalog mode, as follows:
        C indicates compatibility mode.
        E indicates enabling new function mode.
        N indicates DB2 Version 8 new-function mode or later.
    MODE is displayed only when you specify the DETAIL option.

If you want to compare system parameters you should not miss the page https://ruban.de/976/codezos/rexx-procedures-to-call-dsnwzo-stored-procedure-dsnzparms/. This is an REXX sample procedure which calls SYSPROC.ADMIN_INFO_SYSPARM. It works fine for V9 and V10 and is also available in V8 (I did no tests on V8).

Gernot