Define Application Logical Subsystems

On the application - Db2 Administration Options panel, choose option 1 Logical and press Enter to display the Db2 Logical Subsystems panel:

CMNLD2LN                Db2 Logical Subsystems                  Row 1 to 3 of 3 
Command ===> _________________________________________________ Scroll ===> CSR

Line commands:
   P     Specify miscellaneous parameters
   T B   Bind plan/pkg process named(T) and general(B) templates
   Q G   SQL process named(Q) and general(G) templates
   V H   Bind service process named(V) and general(H) templates

        Logical     Db2 
        name       subsys      Site          Description
        SERT6       C105       SERT6         SERT6 D/P INSTANCE
        SERT6P1     C105       SERT6         SERT6 PROMOTION SITE #1
        SERT6P2     C105       SERT6         SERT6 PROMOTION SITE #2
****************************** Bottom of data *********************************

This table describes fields on the Db2 Logical Subsystems panel:

Field	Explanation
Line Command	Type a line command to the left of a panel row.
	I Insert a blank row. R Repeat an existing row.
	D Delete an existing row.
	P Specify miscellaneous processing parameters
	T Specify BIND process named variable templates B Specify BIND process general token variable templates
	Q Specify SQL process named variable templates
	G Specify SQL process general token variable templates
	V Specify BIND SERVICE command named parameter templates
	H Specify BIND SERVICE command general token templates
Logical name	Type a 1-8 character mnemonic for this logical Db2 subsystem. Db2 logical subsystem names must be unique across all physical subsystems. The Logical Name is also called “Db2 nickname” in this manual.
Db2 subsys	Type the Db2 physical subsystem where the parameters and templates in this logical subsystem will be used.
Site	Type the site where the Db2 physical subsystem runs.
Description	Type a 30-character description for the logical subsystem.

On the Db2 Logical Subsystem panel, type I in the line command of a row below which you want to add a physical subsystem and press Enter.
Type * in the line command for the new row, and the Db2 Logical Subsystem List panel is displayed.
Select a global Db2 logical subsystem from the Db2 Logical Subsystem List and press Enter. The logical subsystem is added to the Db2 Logical Subsystem panel.

On the Db2 Logical Subsystems panel, type P on the Line Command for a logical subsystem row and press Enter. The Db2 Logical SubsystemnicknameSettings panel (CMNGD2PM) is displayed:

CMNGD2PM          Db2 Logical Subsystem SERT6 Settings       
Command ===> _________________________________________________

Preferred Libtypes: 
DBRM . . . . . . . . . . . . . . 
Plan bind parameters . . . . . .
Package bind parameters . . . . . 
Service grants            . . . .

General Parameters:
Enter "/" to select option 
  _ Bind Failure is significant 
  / Recycle Stored Procedures where WLM Environment is . . 
  / Maintain Trigger Sequence 
  _ Use Db2 versioning for Native-SQL Stored Procedures

This panel defines BIND command templating that is performed for this Db2 logical subsystem.

This table describes fields on the Db2 Logical Subsystem nickname Settings panel:

Field	Description
Bind Failure is significant	Select to stop promote or demote processing if a Db2 bind fails in this logical subsystem.
	Omit to continue promote or demote processing if a bind fails in this logical subsystem.
Recycle Stored Procedures	Select to issue Db2 command VARY WLM...REFRESH to refresh a stored procedure or external user defined function that has changed in this logical subsystem.
	Omit this field to prevent automatically refreshing a stored procedure or external user defined function that has changed in this logical subsystem.
Where WLM Environment Is	If stored procedures are executed in one or more WLM-managed address spaces, type the name (or pattern) for the target WLM environment. The value of this field restricts the refresh of stored procedures to those environments that match the name or pattern you specify.
	You can wildcard this field by typing an asterisk at the end to specify a pattern for matching WLM environments. For example, C102* targets all WLM-managed environments whose names begin with the characters C102.
Use Db2 versioning for Native SQL Stored Procedures	Select this to use Db2 versioning for Native SQL stored procedures. Instructs ZMF to keep track of active versions during Native SQL Stored Procedure deployment. Resets the active version during demote/backout instead of re-presenting the prior version of the SP definition.
	If not selected, then do not use Db2 versioning for Native SQL stored procedures.
Maintain Trigger Sequence	Select to drop and recreate all triggers for an event/table combination when one trigger is changed. To use this facility you must arrange for the 'comment on' value for the trigger to start with CMNFIRE#nn. Triggers are then ordered according to the nn in this text. When more than one trigger is defined for a particular event/table combination, the triggers will 'fire' in the order in which they were created. When we change a trigger definition we drop and then recreate it thereby altering the execution sequence. If this parameter is set to '/' then we will drop and recreate, without change, all the other trigger definitions for this event/table combination in order to maintain the required firing sequence.
	Omit this field to not drop and recreate other triggers for an event/ table combination when one trigger is changed. The modified trigger will execute last.
Preferred Libtypes	These fields are not used unless:
	1. You assign Db2 subtypes B (BIND PLAN) or P (BIND PACKAGE) or R (DBRM) to more than one library type in this application. See Define Application Db2 Library Subtypes
	2. You customize promotion, demotion, and installation skeletons to use the library types entered in these fields. The data in these fields is available in ISPF variables NTDBR, NTDBB and NTDBP in tables CMNDB2NN and CMNDB2N.
	3. The service grant libtype is only used when automating BIND SERVICE commands.

Set parameters, then press Enter to accept panel entries.

Note

The entries on this panel are not restricted by entries on the Db2 Logical Subsystem nickname Parameter Settings at the global level. The entries at the global level are only a model for applications.

On the Db2 Logical Subsystems panel, type T on the Line Command for a logical subsystem row and press Enter. The Db2 Logical Subsystem nickname Bind Process Templates panel is displayed:

CMNGD2L2     Db2 Logical Subsystem PROD BIND Process Templates       
Command ===> _________________________________________________

 Templates       Target               Source               Insert 
General: 
 Qualifier . . . PROD¬¬¬¬¬¬¬¬¬¬¬¬    + ______________     + PROD             +
Owner . . . . .  SERD¬¬¬¬¬¬¬¬¬¬¬¬    + ______________     + SERD             + 

Plan: 
 Name . . . . .  __________            __________

Package: 
 Location . . .  ________________    + _______________    + _______________
 Collection . .  ________________    + _______________    + _______________

This panel defines BIND command and schema templating that is performed for this Db2 logical subsystem.

How you use the fields on this panel to achieve the templating that you need is explained by example in Templating Examples. For an introduction to templating, see Templates.

The two tables that follow explain the field names at the left of the panel and the templating names at the top of the panel.

Note

All data fields on this panel, except for Plan Name, exceed the length of the displayed panel fields. See topic "Working with Long Fields" in the ZMF User's Guide for instructions on how to enter, update, and erase data in long panel fields.

This first table defines the field names at the left of the Db2 Logical Subsystem nickname BIND Process Templates panel:

Syntax of the BIND PLAN and BIND PACKAGE commands referred to in this table:

BIND PLAN(plan-name) PKLIST(location-name.collection-id.package-id)
    -  OWNER(authorization-id) QUALIFIER(qualifier-name)...

BIND PACKAGE(location-name.collection-id)
    -  OWNER(authorization-id) QUALIFIER(qualifier-name)...

Field	Description
Qualifier	Template or insert value for qualifier-name in BIND PLAN commands and BIND PACKAGE commands. Qualifier may be up to 128 characters long.
Bind Owner	Template or insert value for authorization-id in BIND PLAN and BIND PACKAGE commands. Bind Owner may be up to 128 characters long.
Plan Name	Template for plan-name in BIND PLAN commands. Plan name may be up to 8 characters long.
Package Location	Template for location-name in BIND PACKAGE commands. If the PKLTEMPLATE control statement is input to plan lookup program CMNDB2PL, then the template is also applied to the location-name in the PKLIST parameter of BIND PLAN commands. See the PKLTEMPLATE table entry in the Program Level Control Statements section under CMNDB2PL - BIND Utility. Package Location may be up to 128 characters long.
Package Collection	Template for collection-id in BIND PACKAGE commands. If the PKLTEMPLATE control statement is input to plan lookup program CMNDB2PL, then the template is also applied to the collection-id in the PKLIST parameter of BIND PLAN commands. See the PKLTEMPLATE table entry in the Program Level Control Statements section under CMNDB2PL - BIND Utility. Package Collection may be up to 128 characters long.

This second table defines templating fields Target, Source, and Insert on the Db2 Logical Subsystem nickname BIND Process Templates panel in terms of the kind of templating that is performed.

Template Type	Field	Description
Replace characters at an offset	Target	Placeholder ? characters define the offset for replacement characters.
		Example: ???S?T replaces the fourth character of a seven-character value with S and the sixth character with T.
	Source	Blank
	Insert	Blank
Add characters at end	Target	Placeholder ? characters define a field that is as long or longer than the actual data, followed by characters to be appended to the parameter value.
		Example: ???S?T adds ST to the end of a three-character value.
	Source	Blank
	Insert	Blank
Replace characters at end	Target	Character * (asterisk) indicates the start of a literal string n characters long that will replace the last n characters of the parameter value.
		Example: *ST replaces the last two characters with ST.
	Source	Blank
	Insert	Blank
Delete characters at end	Target	Character ¬ (not) indicates a field character that will be replaced with a space. Since embedded spaces are invalid in a parameter value, use ¬ to delete characters at the end of a value.
		Example: ????¬¬ deletes the last two characters of a six character value or the last character of a five character value.
	Source	Blank
	Insert	Blank
Replace character string	Target	Literal string that will replace the first occurrence of the string matching the value in the Source field. The matching string and replacing string can be different lengths.
	Source	Literal string to search for.
	Insert	Blank
Add an OWNER parameter	Target	Blank
	Source	Blank
	Insert	Value for the OWNER parameter.
		Note: There must be no OWNER in the input BIND command, and the following control statement must be input to the plan lookup program CMNDB2PL: AUTHORITY=OWNER,INSERT
Add a QUALIFIER parameter	Target	Blank
	Source	Blank
	Insert	Value for the QUALIFIER parameter.
		Note: There must be no QUALIFIER in the input BIND command, and the following control statement must be input to the plan lookup program CMNDB2PL: INSERTQUAL

Note

The entries on this panel are not restricted by entries on the Db2 Logical Subsystem nickname Bind Process Templates at the global level. The entries at the global level are only a model for applications.

Define templates, then press Enter to accept panel entries.

Create a logical subsystem for every promotion level and production environment in the application where the Db2 Option will manage Db2 components.

On the Db2 Logical Subsystems panel, type B on the Line Command for a logical subsystem row and press Enter.

The Db2 Logical Subsystem nickname Bind General Templates panel CMNLD2L5 is displayed.

Note

This facility is not part of the Core Db2 option. Only named templates are available if you choose to use the Core option.

CMNLD2L5 Db2 Logical Subsystem QAD1 Bind General Templates   Row 1 to 13 of 13
Command ===>                                                  Scroll ===> CSR

     Token name          + Target template        + Source template     +
____ ______________________ ______________________ ______________________
____ ______________________ ______________________ ______________________
____ ______________________ ______________________ ______________________
____ ______________________ ______________________ ______________________
____ ______________________ ______________________ ______________________
____ ______________________ ______________________ ______________________
____ ______________________ ______________________ ______________________
____ ______________________ ______________________ ______________________
____ ______________________ ______________________ ______________________
____ ______________________ ______________________ ______________________

On the Db2 Logical Subsystems panel, type Q on the Line Command for a logical subsystem row and press Enter. The Db2 Logical Subsystem nickname SQL Templates (Named) panel CMNGD2L3 is displayed:

CMNGD2L3 Db2 Logical Subsystem PROD SQL Process Templates (Named)      
Command ===> _________________________________________________

 Templates       Target               Source               Deploy 

 Schema . . . .  PROD¬¬¬¬¬¬¬¬¬¬¬¬    + ______________     +                  
 Collection . .  ________________    + ______________     + 
 WLM . . . . . . ________________    + ______________     +   

 Location . . .                      +                    + _______________
 Qualifier . .   PROD¬¬¬¬¬¬¬¬¬¬¬¬    + _______________    + PROD
 Owner . . . . . SERD¬¬¬¬¬¬¬¬¬¬¬¬    + _______________    + SERD

On the Db2 Logical Subsystems panel, type G on the Line Command for a logical subsystem row and press Enter. The Db2 Logical Subsystem nickname SQL Process Templates (General) panel is displayed:

CMNGD2L4 B2 Logical Subsys PROD SQL Process Templates (Ge Row 1 to 21 of 21  
Command ===> _____________________________________________ Scroll ===> CSR

          Token name           Target template      Source template

 ____     ________________   + ________________   + ________________   +
 ____     ________________   + ________________   + ________________   +
 ____     ________________   + ________________   + ________________   +
 ____     ________________   + ________________   + ________________   +
 ...
 ____     ________________   + ________________   + ________________   +
 ____     ________________   + ________________   + ________________   +
****************************** Bottom of data *****************************

Refer to the explanation of the Global equivalent for these - CMNGD2L4 B2 Logical Subsystem PROD SQL Process Templates (Ge Row 1 to 21 of 21).

On the Db2 Logical Subsystems panel, type V on the Line Command for a logical subsystem row and press Enter. The Db2 Logical Subsystem nickname Bind Service Named Templates panel CMNGD2L6 is displayed:
```
CMNGD2L6 Db2 Logical Subsystem QAD1 Bind Service Named Templates
Command ===>

Templates       Target            Source

Collection  . . ________________ +__________________ +
Qualifier . . . ________________ +__________________ +
Owner . . . . . ________________ +__________________ +
```
These three named parameters are templated in the same way as for package/plan binds (see section 6 above). The underlying processes are different.

On the Db2 Logical Subsystems panel, type H on the line command for a logical subsystem row and press ENTER. The Db2 Logical Subsystem nickname BIND Service General Templates panel CMNLD2L7 is displayed, from which the BIND Service process general tokens for that particular logical subsystem can be specified:

CMNLD2L7 Db2 Logical Subsystem QAD1 Bind Service General Temp Row 1 to 13 of 13
Command ===>                                                   Scroll ===> CSR

     Token name           + Target template      + Source template      +
____ ______________________ ______________________ ______________________
____ ______________________ ______________________ ______________________
____ ______________________ ______________________ ______________________
____ ______________________ ______________________ ______________________
____ ______________________ ______________________ ______________________
____ ______________________ ______________________ ______________________
____ ______________________ ______________________ ______________________
____ ______________________ ______________________ ______________________
____ ______________________ ______________________ ______________________

This general token processing is described in step 7 above. However, there are some extra features which are applicable only to Bind Service processing.

When a grant SQL component is associated with the bind service process and the token name is >GRANTEE< , the template is applied to the list of grantee userids/groups on the grant SQL supplied to the process.

Also, if you enclose the source template in single quotes, the target template is only used if the value to be replaced exactly matches the source template value.

Define Application Active Libraries

Automated Db2 Option functions are activated when libraries managed by ChangeMan ZMF are changed in promotion and production environments. These libraries are defined as active libraries in the Db2 Option. See Active Libraries for details.

Note

For stored procedures, user defined functions, and triggers, use production libraries instead of baseline libraries for Db2 active libraries at installation.

Follow these steps to define active libraries in your Db2 application:

On the application - Db2 Administration Options panel, choose option 2 Library and press Enter to display the Db2 Active Library List panel:

CMNLD2AL                Db2 Active Library List               Row 1 to 10 of 10   
Command ===> _________________________________________________ Scroll ===> CSR

      Logical     Bind 
      name        /SQL     Db2 active library name 
 ____ SERT6        B       CMNTP.S6.V810.PROD.DBB
 ____ SERT6        B       CMNTP.S6.V810.PROD.DBR
 ____ SERT6        B       CMNTP.S6.V810.PROD.LOD
 ____ SERT6        B       CMNTP.S6.V810.PROD.PKG
 ____ SERT6        S       CMNTP.S6.V810.PROD.SPD
 ____ SERT6        S       CMNTP.S6.V810.PROD.SPN
 ____ SERT6        S       CMNTP.S6.V810.PROD.SPQ
 ____ SERT6        S       CMNTP.S6.V810.PROD.STL
 ____ SERT6        S       CMNTP.S6.V810.PROD.TRG
 ____ SERT6        S       CMNTP.S6.V810.PROD.UDF 
 ____ SERT6        V       /cmntp/S6/V810/Prod00/BSG
 ____ SERT6        V       /cmntp/S6/V810/Prod00/BSZ
 ****************************** Bottom of data ********************************

The following table describes fields on the Db2 Active Library List panel:

Field	Description
Line Command	Type a line command to the left of a panel row.
	I Insert a blank row.
	R Repeat an existing row.
	D Delete an existing row.
Logical name	Type a Db2 logical subsystem, or connector, name that is already defined in Db2 application administration.
	Type * to see the Db2 Logical Subsystem List panel from which you may select a logical subsystem name. The Logical Name is also called Db2 nickname in this manual.
Type	Type an indicator for the kind of processing invoked when the active library is updated: B Activate Db2 bind processing. S Activate stored procedure processing, which includes stored procedures, user defined functions, and triggers. V Activate Db2 Bind Service processing.
Db2 active library name	Type the fully qualified data set name of a library or zFS directory name, that is monitored for change and will invoke Db2 Option bind, stored procedure, or bind service processing. Library types and subtypes that should be coded as active libraries:
	Bind processing - BIND PLAN command library, BIND PACKAGE command library, Load module library, and DBRM libraries
	Stored procedure processing - Stored procedure library. See the table below.
	Bind service processing - BIND SERVICE command library GRANT authority to service DDL library

This table shows you how the BND/SQL/SERVICE field relates to library types and other Db2 Option parameters. BND/SQL/SERVICE values are shown in bold.

Db2 Component	Like	Target Type	Sel Opt	Sub Typ	BIND/ SQL/ Service
Db2 Application Program Source	S	Db2 Program Load
Db2 Application Program Load	L				**B
DBRM	P		D	R	**B
BIND PLAN Command	P		D	B	**B
BIND PACKAGE Command	P		D	P	**B
External Stored Procedure Source	S	Stored Procedure Load
External SQL Stored Procedure Source	S	Stored Procedure Load	D	Q	**S
External Stored Procedure Load	L		D	S	**B & S
Native SQL Stored Procedure	P		D	N	**S
General DDL (e.g. CREATE PROCEDURE for external SP)	P		D	D	**S
User Defined Function Definition	P		D	D	**S
Trigger Definition	P		D	T	**S
BIND Service command	P		D	V	**V
Service GRANT command	P		D	V	**V

* Db2 Active Library specification for BIND plan/pkg (B), Process SQL (S), and Bind Service (V).

Define Application Db2 Library Subtypes

Db2 library subtypes invoke special processing for Db2 components. When you defined the Application Library Types for these components, you coded D in the Selectable Option field. Here you assign a Db2 Sub Type to each of those library types.

On the application - Db2 Administration Option panel, choose option 3 Libtypes and press Enter. The application - Db2 Library Types panel (CMNDLLT0) is displayed:

CMNDLLT0                STEV - Db2 Library Types              Row 1 to 12 of 12
Command ===> _________________________________________________ Scroll ===> CSR

Lib                                                       Sub    End SQL 
type   Description                                        type   sentence
DBR    Db2 DBRM's                                          R        _
DBP    Db2 Bind Package Commands                           P        _
PKG    Db2 Package Bind Control                            P        _
DBB    Db2 Bind Plan Commands                              B        _
STL    Db2 External Stored Procedure Load                  S        _
XPQ    Db2 External SQL stored proc Source                 D        #
SPD    Db2 Stored Procedure Definition                     D        #
NSQ    Native SQL Stored Procedures                        N        #
DDL    Data Definition Language                            D        @
BSP    Bind Service PDSE based components                  V        _
BSZ    Bind Service zFS based components                   V        _
BSG    Bind Service Grant components                       V        _
****************************** Bottom of data *********************************

This table describes the fields on the application - Db2 Library Types panel:

Field	Description
Lib type	Displays the library types from the Global Library Type definition that are defined with a Selectable Option of D.
Description	Displays the definition from the global library type.
Sub type	Type the Db2 Sub Type for special Db2 Option processing. Sub type processing is described in the next table below.
	B BIND PLAN command
	D CREATE statements for stored procedures, external user defined functions.
	N Native SQL stored procedure
	P BIND PACKAGE command
	S External SQL stored procedure load modules, REXX stored procedures
	T Trigger definition source
	V BIND SERVICE command or associated GRANT DDL.
End SQL sentence	Type an alternate SQL statement terminator. If the components in this library type include SQL that uses the semicolon (;) as a statement terminator, specify an alternate terminator for the stored procedure or function so that the semicolon is passed through to the server.
	You can specify any character except the following:
	- comma
	- underscore
	- single quote
	- double quote
	- left hand parenthesis
	- right hand parenthesis
	If you leave this field blank, the default alternate SQL statement terminator is semicolon (;).

Define the Db2 sub types, then press Enter to accept panel entries.

This table shows the processing assigned by Db2 Option library sub types:

Sub Type	Description	Modified Process	Sub Type Processing Description
B	BIND PLAN command	Promote Demote Install Backout	Process with plan lookup program CMNDB2PL to template BIND parameters for the target Db2 subsystem.
D	CREATE statements for stored procedures, external user defined functions.	Promote Demote Install Backout	Process with utility program CMNDB2DD to register the object in the Db2 catalog. Issue a DROP before the CREATE.
N	Native SQL stored procedures	Promote Demote Install Backout	Process with utility program CMNDB2DD to register the stored procedure in the Db2 catalog.
P	BIND PACKAGE command	Promote Demote Install Backout	Process with plan lookup program CMNDB2PL to find applicable BIND PLAN members and template parameters for the target Db2 subsystem.
Q	SQL stored procedure source	Promote Demote Install Backout	Process with utility program CMNDB2DQ to remove SQL procedural code, then process the CREATE with utility program CMNDB2DD to register the stored procedure in the Db2 catalog.
R	DBRM		Process with plan lookup program CMNDB2PL to find applicable BIND PACKAGE and BIND PLAN members and template BIND parameters for the target Db2 subsystem.
S	Stored procedure load modules, REXX stored procedures	Promote Demote Install Backout	If the Recycle Stored Procedure field is YES, issue Db2 command VARY WLM...REFRESH in the WLM-managed address space to refresh the executable.
T	Trigger definition source	Promote Demote Install Backout	Process with utility program CMNDB2DD to extract the table/event/time combinations. If Maintain Trigger Sequence YES, query SYSIBM.SYSTRIGGERS with utility program CMNDB2TR to find multiple triggers defined for the same table/event/time combination, then drop and recreate those triggers to maintain the original firing order.
V	BIND SERVICE command and associated GRANT SQL	Promote Demote Install Backout	Process with CMNDB2SV to apply templates to incoming BIND SERVICE and GRANT components. The templated BIND SERVICE command is passed to an IKJEFT01 step for processing. Any templated GRANT DDL is passed to CMNDB2GR for action.

Note

If you create a change package and then change an existing library type definition, the new library type behavior is not expressed in the package. If you create a change package and then define a new library type, the library type behavior in the package is set when the first component is checked out in that library type.

This table shows you how the Db2 Option sub types relate to library types and other Db2 Option parameters. Sub types are shown in bold.

Db2 Component	Like	Target Type	Sel Opt	Sub Typ	BIND/ SQL
Db2 Application Program Source	S	Db2 Program Load
Db2 Application Program Load	L				B
DBRM	P		D	**R	B
BIND PLAN Command	P		D	**B	B
BIND PACKAGE Command	P		D	**P	B
External Stored Procedure Source	S	Stored Procedure Load
External SQL Stored Procedure Source	S	Stored Procedure Load	D	**Q	S
External Stored Procedure Load	L		D	**S	B & S
Native SQL Stored Procedure	P		D	**N	S
General DDL (e.g. CREATE PROCEDURE for external SP)	P		D	**D	S
User Defined Function Definition	P		D	**D	S
Trigger Definition	P		D	**T	S
BIND Service command	P		D	**V	V
Service GRANT command	P		D	**V	V

* Db2 Active Library specification for BIND plan/pkg (B), Process SQL (S), and Bind Service (V).

Define Source/Target Connector

The BIND DEPLOY mechanism for distributing Native SQL stored procedures requires both a source and a target Db2 environment. This option is used to "connect" a source logical subsystem to a target logical subsystem.

It is not part of the "core" Db2 option functionality.

On the application - Db2 Administration Option panel, choose option 4 Connector and press Enter. The application - Db2 Logical Subsystem Connectors panel (CMNLD2CL) is displayed:

CMNLD2CL       Logical Subsystem Connectors for Appl - STEV     Row 1 to 1 of 1
Command ===>                                                   Scroll ===> CSR

        Connector     Source         Target
        name          name           name        Description
        ABC           PRODLCL1       PRODLCL2    TEST
******************************* Bottom of data ********************************

The connector definition must already exist at the global level. You can enter an asterisk in the line command to get a list of pre-defined connectors from which you can select.

Values from the source logical subsystem are used to identify the stored procedure that will be deployed. Values from the target logical subsystem are used to specify the name and related attributes of the stored procedure when it is deployed to the target.

If you wish to see which values will be used for your choice of source and target, select the row once any update has been saved.

To invoke the BIND DEPLOY mechanism based on a specific connector name, make the connector name the subsystem name associated with the relevant SQL active library.

This table describes the fields on the application - Db2 Logical Subsystem Connectors panel:

Field	Description
Connector Name	The 8 character name by which this connector definition will be referenced. It must be unique within connector and logical subsystem names.
Source Name	An existing logical subsystem name describing the source location of the required bind deploy command.
Target Name	An existing logical subsystem name describing the target location of the required bind deploy command.
Description	Free form text describing this connector definition.

Define Secondary Bind Requirements

This option is used to allow the administrator to associate secondary bind logical subsystem names with those of primary bind logical subsystems.

The secondary names will be added to a secondary bind logical subsystem ISPF table (CMNDB22N) from which additional bind steps may be created each time binds are generated for the primary logical subsystem.

On the application - Db2 Administration Option panel, choose option 5 Secondary and press Enter. The application - Db2 Secondary Binding panel (CMNLD2LB) is displayed:

CMNLD2LB                 Db2 Secondary Binding                  Row 1 to 5 of 5
Command ===>                                                   Scroll ===> CSR

Enter END command to save changes or CANCEL to exit without saving changes.
Enter * in either name field for local DB2 logical subsystem list.

     Primary    Secondary     Promotion
     Logical    Logical      Level Name       Active Description (Secondary)
     Name       Name
     PRODUCTN   QA            30    QA          Y     QA           (2NDARY BINDS)
     PRODUCTN   SYSTEST       20    SYSTEST     Y     SYSTEM       (2NDARY BINDS)
     PRODUCTN   UNIT          10    UNIT        Y     UNIT         (2NDARY BINDS)
     QA         SYSTEST       20    SYSTEST     Y     SYSTEM       (2NDARY BINDS)
     QA         UNIT          10    UNIT        Y     UNIT         (2NDARY BINDS)
******************************* Bottom of data ********************************

This table describes the fields on the application - Db2 Secondary Binding panel:

Field	Description
Primary Logical Name	A pre-existing logical subsystem name where the primary bind, for this definition, will take place. You can enter an asterisk in this field to get a list of existing logical subsystem names.
Secondary Logical Name	A pre-existing logical subsystem name where the secondary binds, for this definition, will take place. You can enter an asterisk in this field to get a list of existing logical subsystem names.
Promotion Level	This is the promotion level you wish to be associated with the secondary logical subsystem for this secondary bind. This will be used, via the relevant skeleton, to create an appropriate library concatenation for DBRMLIB (etc.). You can enter an asterisk in this field to get a list of allowed promotion levels for the remote site associated with the secondary logical subsystem.
Promotion Name	This is the nickname associated with this promotion level (display field only).
Active	This definition will only be acted on if this field is set to Y.
Description	The description associated with the secondary logical subsystem name (display field only).

Specify Application Db2 General Parameters

Set options for processing Db2 components.

On the application - Db2 Administration Options panel, choose option G General and press Enter to display the application - Db2 General Parameters panel (CMNLDPM0):

CMNLDPM0             ACTP - Db2 General Parameters      
Command ===> _________________________________________________

Enter "/" to select option 
  _ Use package name in Db2 PC version 
  _ Force package name in Db2 PC version

This table describes the options and values on the application - Db2 General Parameters panel.

Field	Description
Use Package Name in Db2 PC version	Select with / to determine whether the VERSION field on the Db2 Physical Subsystems panel (CMNSTG18) is initialized to the package ID in stage and recompile.
	When selected, initializes the VERSION field on the Db2 Physical Subsystems panel to the package ID.
	When not selected, initializes the VERSION field on the Db2 Physical Subsystems panel to blank.
Force Pkg Name in Db2 PC version	Select this to determine whether the Package ID must be used for the VERSION parameter for the Db2 precompiler in stage and recompile. This option must be blank if the “Use Package Name in Db2 PC version” field is blank.
	If selected, then display the VERSION field in browse mode on the Db2 Physical Subsystems panel (CMNSTG18) in stage and recompile so that the field cannot be changed.
	If not selected, then display the VERSION field on the Db2 Physical Subsystem panel in edit mode so it can be changed.

Type your choices for the general parameters, then press Enter to accept panel entries.

Press PF3 to return to the application - Db2 Options Administration panel.