Skip to content

ISPF Tables and Variables

The following pages describe ISPF Dialog Manager tables and variables used in the ChangeMan ZMF Db2 Option.

ISPF Tables

This section lists the ISPF tables used in file tailoring to create Db2 processing steps in jobs for promote, demote, install, backout, baseline ripple, and reverse baseline ripple.

For the list of variables in each of these tables, search for the table name in member #VARLIST in the CMNZMF SKELS library.

Caution

ZMF skeletons do not use these ISPF tables consistently across different package processes such as promotion and installation. Before you apply Db2 Option customization designed for one package process to skeletons for a different package process, examine the delivered skeletons to see that you are using the appropriate ISPF tables.

CMNDB2S1 - Db2 Physical Subsystem Table

Each row in table CMNDB2S1 describes a physical subsystem defined for the ZMF instance. All physical subsystems for the ZMF instance are included in this table.

Values for the ISPF variables in this table are set on global administration panels for the Db2 option. These panels include:

  • Db2 Physical Subsystems - Part 1 of 2 (CMNGD2S0)

  • Db2 Physical Subsystems - Part 2 of 2 (CMNGD2S1)

CMNDB2SS - Db2 Physical Subsystem Table for BIND

Table CMNDB2SS contains only those physical subsystems where Db2 BIND processing is required by the current action. Each row is initially formed from equivalent rows in CMNDB2S1. That is, when a component will be copied into a library that is listed in the Db2 BIND active library table CMNDB2AL, the logical subsystem listed for the active library is used to get a logical subsystem definition, which contains a physical subsystem that is used to copy a row from CMNDB2S1 to CMNDB2SS.

However, information about bind failure significance is also gathered from these logical subsystems. The "bind failure significance" variable (STBINDF) forms a key for this table so that you may have up to two rows for each physical subsystem. (STBINDF can be "YES" or "NO.")

This structure allows CMNDB2SS to be used in the skeletons to generate zero, one, or two CMNDB2PL/BIND step couplets for each physical subsystem, depending on whether:

  • No logical subsystems active in this promote/demote target this physical subsystem (zero).

  • All such logical subsystems have the same setting for bind failure significance (one).

  • There is a mix of bind failure significance settings (two).

CMNDB2S2 - Db2 Physical Subsystem Table (With Bind Failure)

This table has the same global scope as CMNDB2S1 but it is constructed with "bind failure" information (STBINDF), in a similar way to CMNDB2SS.

There are currently no delivered skeletons which make use of this table but it is available for use. CMNDB2S2 has been chosen so as not to upset the existing use of CMNDB2S1.

CMNDB2N1 - Db2 Logical Subsystem Table

Each row in table CMNDB2N1 describes a logical subsystem defined in the application that is being processed in file tailoring. All logical subsystems for the application are included in this table.

Values for the ISPF variables in this table are set on application administration panels for the Db2 option. These panels include:

  • Db2 Logical Subsystems (CMNLD2LN)

  • Db2 Logical Subsystem logical subsys Parameter Settings (CMNGD2PM)

  • Db2 Logical Subsystem logical subsys Templates (CMNGD2L2)

CMNDB2NN - Db2 Logical Subsystem Table for BIND

Table CMNDB2NN contains a subset of the rows in table CMNDB2N1. The information for a logical subsystem is identical in both tables, but CMNDB2NN contains only those logical subsystems where Db2 BIND processing is required.

When a component will be copied into a library that is listed in the Db2 BIND active library table CMNDB2AL, the logical subsystem listed for the active library is used to copy a row from table CMNDB2N1 into table CMNDB2NN.

CMNDB22N - Db2 Logical Subsystem Table for Secondary BIND

Table CMNDB22N contains rows describing secondary bind requirements for this action. These requirements are defined using application admin in the ZMF Db2 option.

The primary bind logical subsystem is assigned when a component will be copied into a library that is listed in the Db2 BIND active library table CMNDB2AL.

If there are one or more secondary bind definitions linking the primary bind logical subsystem to other logical subsystems then a row will be written to this table for each such association.

The table is similar to CMNDB2NN in content but has added fields for the secondary bind process (see list below).

In the sample skeletons this table is used during file tailoring to generate CMNDB2PL/ BIND steps to address secondary bind requirements in the same job as the primary bind.

TABLE NAME: CMNDB22N DESCRIPTION: Secondary binds for plan/pkg

   NOTE: The field values are those that apply to the secondary
         logical
              subsystem. This table can be used to drive binds for the
              secondary logical subsystem if binds have already been
             generated for the primary logical subsystem.

TABLE   VARIABLE    VARIABLE    VARIABLE
COLUMN  NAME        LENGTH      DESCRIPTION
------  --------    --------    -------------------------
01      NT2NAM      08          Primary logical subsystem name
02      NT2COLT     128         Primary Pkg ID target template
03      NT2COLS     128         Primary Pkg ID source template
04      NTNNAM      08          Secondary logical subsys name
05      NTSSYS      04          Db2 logical subsystem ID
06      NTPLVL      02          Associated promotion level
07      NTPNME      08          Associated promotion name
08      NTBDID      128         Db2 insert bind owner ID
09      NTTOTPT     128         Db2 owner target template
10      NTSOTPT     128         Db2 owner source template
11      NTTMPT      24          Db2 PLAN target template
12      NTSTMPT     24          Db2 PLAN source template
13      NTPTMP      128         Db2 PKG ID target template
14      NTSPTMP     128         Db2 PKG ID source template
15      NTTLTPT     128         Db2 location ID target template
16      NTSLTPT     128         Db2 location ID source template
17      NTQUAL      128         Db2 qualifier
18      NTSQTPT     128         Db2 qualifier source template
19      NTTQTPT     128         Db2 qualifier target template
20      NTBINDF     03          Fail action if bind fails
21      NTREMT      08          Db2 logical remote site
22      NTPRMLV     02          Associated promotion level
23      NTPRMNM     08          Associated promotion name
24      NTDBR       03          Preferred DBRM libtype

CMNDB2NQ - Db2 Logical Subsystem Table for SQL/Stored Procedure

Table CMNDB2NQ contains a subset of the rows in table CMNDB2N1. The information for a logical subsystem is identical in both tables, but CMNDB2NQ contains only those logical subsystems where SQL/stored procedure processing is required.

When a component will be copied into a library that is listed in the SQL/stored procedure active library table CMNSQLAL, the logical subsystem listed for the active library is used to copy a row from table CMNDB2N1 into table CMNDB2NQ.

CMNDB2AL - Db2 BIND Active Library Table

This table lists the Db2 Option active libraries for BIND processing in the application being processed in file tailoring.

Values for the ISPF variables in this table are set in application administration for the Db2 Option on the Db2 Active Library List panel (CMNLD2AL). Table CMNDB2AL contains only those active libraries where the BIND/SQL field is set to B.

CMNSQLAL - Db2 SQL/Stored Procedure Active Library Table

This table lists the Db2 Option active libraries for SQL/stored procedure processing in the application being processed in file tailoring.

Values for the ISPF variables in this table are set in application administration for the Db2 Option on the Db2 Active Library List panel (CMNLD2AL). Table CMNSQLAL contains only those active libraries where the BIND/SQL field is set to S.

CMNSQLTK - Db2 General Token Table for SQL/DDL operations

This table lists the token name (64), token source template (128) and token target template (128).