Skip to content

DB2 Development and Administration

Serena XML supports the following DB2 database tasks for general use:

  • DB2 Active Libraries for Application - DB2ADMIN APL_ACTV LIST

  • DB2 Logical Subsystems for Application - DB2ADMIN APL_LOGL LIST

  • DB2 Global Physical Subsystems - DB2ADMIN GBL_PHYS LIST

  • DB2 Global Logical Subsystems - DB2ADMIN GBL_LOGL LIST

DB2 Active Libraries for Application - DB2ADMIN APL_ACTV LIST

This function lists two kinds of DB2 "active" libraries for an application:

  • Bind Active Libraries — Promotion and production libraries defined in the DB2 Option to execute DB2 binds at promote, demote, install, and backout.

  • Stored Procedure Active Libraries — Promotion and production libraries defined in the DB2 Option to invoke special processing after changes to stored procedures, triggers, and user-defined functions.

Values returned for these libraries include the physical dataset name, the DB2 logical subsystem ID, and the DB2 entity type. If no DB2 active libraries are defined for an application, no results are returned.

The Serena XML service/scope/message tags and attributes for messages to list active DB2 libraries for an application are:

<service name="DB2ADMIN">
<scope name="APL_ACTV"> 
<message name="LIST">

These tags appear in both requests and replies.

To display the same information using ChangeMan ZMF, if you have the required access, you can go to the Selectable Options panel (CMNGBSOP).

DB2ADMIN APL_ACTV LIST — Requests

Serena XML supports two kinds of DB2 active library list requests for an application:

  • Comprehensive List — Enter the name of the desired application in the <applName> tag to list all DB2 active libraries for that application.

  • Single Logical Subsystem — Name the desired application in the <applName> tag and the DB2 logical subsystem ID of interest in the <db2LogicalName> tag. Information is returned for the named DB2 subsystem only.

Example XML — DB2ADMIN APL_ACTV LIST Request

<?xml version="1.0"?>
<service name="DB2ADMIN">
    <scope name="APL_ACTV">
        <message name="LIST">
            <header>
                <subsys>8</subsys>
                <product>CMN</product>
            </header>
            <request>
                <applName>CISQ</applName>
            </request>
        </message>
    </scope>
</service>

Data structure details for the <request> tag appear in Exhibit 9-13.

Exhibit 9-13 DB2ADMIN APL_ACTV LIST <request> Data Structure

Subtag Use Occurs Data Type & Length Values & Dependencies
<applName> Required 1 String (4), variable ZMF application name.
NOTE: OK to omit trailing blanks.
<db2LogicalName> Optional 0 - 1 String (8), variable DB2 logical subsystem ID of interest.
NOTE: Use asterisk (*) wildcard or omit tag to request all DB2 subsystems for named application.

DB2ADMIN APL_ACTV LIST — Replies

The reply message for this function returns zero to many <result> data elements. Each <result> describes one active DB2 library associated with the application named in the request. If no active DB2 libraries are defined for the application using the DB2 Option of ChangeMan ZMF, no <result> tags are returned in the reply message.

The standard <response> data element follows any <result> tags in the reply and indicates the success or failure of the list request. Successful requests have a return code of 00. Unsuccessful requests have a return code of 04 or higher. Because it is the final data element in the XML reply message, the <response> tag serves as an end-of-list marker.

Example XML — DB2ADMIN APL_ACTV LIST Reply

<?xml version="1.0"?>
<service name="DB2ADMIN">
    <scope name="APL_ACTV">
        <message name="LIST">
            <result>
                <applName>CISQ</applName>
                <db2LogicalName>PROM810</db2LogicalName>
                <db2Lib>CMNTP.SERT8.PROM.CISQ.C001AUT.DBR</db2Lib>
                <db2LibType>B</db2LibType>
            </result>
            <result>
                <applName>CISQ</applName>
                <db2LogicalName>PROM810</db2LogicalName>
                <db2Lib>CMNTP.SERT8.PROM.CISQ.C001AUT.DBB</db2Lib>
                <db2LibType>B</db2LibType>
            </result>
            <result>
                <applName>CISQ</applName>
                <db2LogicalName>PROM810</db2LogicalName>
                <db2Lib>CMNTP.SERT8.PROM.CISQ.C001AQA.DBR</db2Lib>
                <db2LibType>B</db2LibType>
            </result>
            <result>
                <applName>CISQ</applName>
                <db2LogicalName>PROM810</db2LogicalName> <db2Lib>CMNTP.SERT8.PROM.CISQ.C001AQA.DBB</db2Lib>
                <db2LibType>B</db2LibType>
            </result>
            <response>
                <statusMessage>CMN8700I - LIST service completed</statusMessage>
                <statusReturnCode>00</statusReturnCode>
                <statusReasonCode>8700</statusReasonCode>
            </response>
        </message>
    </scope>
</service>

Data structure details for the <result> tag appear in Exhibit 9-14.

Exhibit 9-14 DB2ADMIN APL_ACTV LIST <result>

Subtag Use Occurs Data Type & Length Values & Dependencies
<applName> Required 1 String (4), variable ZMF name of application.
<db2Lib> Optional 0 - 1 String (44), variable Fully qualified dataset name of DB2 active library.
<db2LibType> Optional 0 -1 String (1) Code for DB2 entity type. Values:
B = DBB bind control
S = Stored procedure load/REXX
<db2LogicalName> Optional 0 -1 String (8), variable DB2 logical subsystem ID (or partition) defined for the active library.

DB2 Logical Subsystems for Application - DB2ADMIN APL_LOGL LIST

This function lists specifications for the DB2 logical subsystems defined for an application. An application name is required in the request. Returned values include DB2 logical and physical subsystem IDs and description, the site where the DB2 subsystem runs, and application-level configuration settings. DB2 subsystems must be properly configured in both DB2 and ChangeMan ZMF prior to running this service, or unexpected results may occur.

The Serena XML service/scope/message tags and attributes for messages to list DB2 logical subsystems for an application are:

<service name="DB2ADMIN">
<scope name="APL_LOGL"> 
<message name="LIST">

These tags appear in both requests and replies.

DB2ADMIN APL_LOGL LIST — Requests

Serena XML supports the following options for listing DB2 logical subsystem at the application level:

  • Comprehensive List — Name the desired application in the <applName> tag to list all logical subsystems defined for the application.

  • Selected Site List — Name the desired application in the <applName> tag and the DB2 site of interest in the <db2SiteName> tag to list all DB2 logical subsystems for the named application at the selected site.

  • Selected Physical Subsystem List — Name the desired application in the <applName> tag. In the <db2SubSystemId> tag, identify the DB2 physical subsystem where the parameters and templates of the logical subsystem(s) will be used. All logical subsystems defined for that physical subsystem in the named application are returned in the reply.

  • Single Logical Subsystem — Name the desired application in the <applName> tag. Identify the DB2 logical subsystem of interest in the <db2LogicalName> tag.

Application-level specifications for the requested subsystem are returned in the reply.

Example XML — DB2ADMIN APL_LOGL LIST Request

<?xml version="1.0"?>
<service name="DB2ADMIN">
    <scope name="APL_LOGL">
        <message name="LIST">
            <header>
                <subsys>8</subsys>
                <product>CMN</product>
            </header>
            <request>
                <applName>CISQ</applName>
            </request>
        </message>
    </scope>
</service>

Data structure details for the <request> tag appear in Exhibit 9-15.

Exhibit 9-15 DB2ADMIN APL_LOGL LIST <request>

Subtag Use Occurs Data Type & Length Values & Dependencies
<applName> Required 1 String (4), variable ZMF application name.
NOTE: OK to omit trailing blanks.
<db2LogicalName> Optional 0 - 1 String (8), variable DB2 logical subsystem ID (or partition) of interest.
NOTE: Use asterisk (*) wildcard or omit tag to request all DB2 logical subsystems for application.
<db2SiteName> Optional 0 - 1 String (8), variable ZMF name of remote site where DB2 physical subsystem runs.
NOTE: Use asterisk (*) wildcard or omit tag to request all sites.
<db2SubSystemId> Optional 0 - 1 String (4), variable DB2 physical subsystem ID of interest.
NOTE: Use asterisk (*) wildcard or omit tag to request all DB2 physical subsystems for application.

DB2ADMIN APL_LOGL LIST — Replies

The reply message for this function returns zero to many <result> data elements. Each <result> contains application-level specifications for one DB2 logical subsystem. If no DB2 logical subsystems are defined for the application, no <result> tags are returned in the reply message.

The standard <response> data element follows any <result> tags in the reply and indicates the success or failure of the list request. Successful requests have a return code of 00. Unsuccessful requests have a return code of 04 or higher. Because it is the final data element in the XML reply message, the <response> tag serves as an end-of-list marker.

Example XML — DB2ADMIN APL_LOGL LIST Reply

<?xml version="1.0"?>
<service name="DB2ADMIN">
    <scope name="APL_LOGL">
        <message name="LIST">
            <result>
                <applName>CISQ</applName>
                <db2SubSystemId>C105</db2SubSystemId>
                <db2LogicalName>PROD</db2LogicalName>
                <db2SiteName>SERT8</db2SiteName>
                <bindOwnerInsert>PROD</bindOwnerInsert>
                <packageTargetPattern>???7</packageTargetPattern>
                <bindQualifierTargetPattern>?????T</bindQualifierTargetPattern>
                <logicalSubSysBindFailFlag>Y</logicalSubSysBindFailFlag>
                <recycleStoredProcs>Y</recycleStoredProcs>
                <keepTriggerSequence>Y</keepTriggerSequence>
            </result>
            <result>
                <applName>CISQ</applName>
                <db2SubSystemId>C105</db2SubSystemId>
                <db2LogicalName>PROM810</db2LogicalName>
                <db2SiteName>SERT8</db2SiteName>
                <logicalSubSysBindFailFlag>Y</logicalSubSysBindFailFlag>
                <recycleStoredProcs>Y</recycleStoredProcs>
                <keepTriggerSequence>Y</keepTriggerSequence>
            </result>
            <response> 
                <statusMessage>CMN8700I - LIST service completed</statusMessage>
                <statusReturnCode>00</statusReturnCode>
                <statusReasonCode>8700</statusReasonCode>
            </response>
        </message>
    </scope>
</service>

Data structure details for the <result> tag appear in Exhibit 9-16.

Exhibit 9-16 Application-Level DB2 Logical Subsystem List <result>

Subtag Use Occurs Data Type & Length Values & Dependencies
<applName> Required 1 String (4), variable ZMF name of application.
<bindOwnerInsert> Optional 0 - 1 String (128), variable TSO ID of default bind owner to be inserted into DB2 templates.
<bindOwnerSourcePattern> Optional 0 - 1 String (128), variable Pattern or template for DB2 source bind owner.
<bindOwnerTargetPattern> Optional 0 - 1 String (128), variable Pattern or template for DB2 target bind owner.
<bindQualifierInsert> Optional 0 - 1 String (128), variable Default high-level qualifier for DB2 datasets in bind plan commands, bind package commands, and create trigger definitions.
<bindQualifierSourcePattern> Optional 0 - 1 String (128), variable Pattern or template for high-level qualifier name for DB2 source subsystem bind commands.
<bindQualifierTargetPattern> Optional 0 - 1 String (128), variable Pattern or template for high-level qualifier name for DB2 target subsystem bind commands.
<db2LogicalName> Optional 0 - 1 String (8), variable DB2 logical subsystem ID (or partition) returned.
<db2SiteName> Optional 0 - 1 String (8), variable ZMF name of remote site where DB2 physical subsystem runs.
<db2SubsystemID> Optional 0 - 1 String (4), variable DB2 physical subsystem ID where logical subsystem templates run.
<keepTriggerSequence> Optional 0 - 1 String (1) Y = Yes, rebuild all triggers to preserve trigger sequence for table/event if a trigger changes.
N = No, don’t preserve trigger sequence if change occurs; instead move changed trigger to end.
<locationSourcePattern> Optional 0 - 1 String (128), variable Pattern or template for location ID for DB2 source subsystem.
<locationTargetPattern> Optional 0 - 1 String (128), variable Pattern or template for location ID for DB2 target subsystem.
<logicalSubSysBindFailFlag> Optional 0 - 1 String (1) Y = Yes, bind failure is significant; stop promote/demote processing if DB2 bind fails.
N = No, bind failure not significant; continue promote/demote process.
<logicalSubSystemComment> Optional 0 - 1 String (30), variable Free-format text description of DB2 logical subsystem (or partition).
<packageSourcePattern> Optional 0 - 1 String (128), variable Pattern or template for bind package name for DB2 source subsystem.
<packageTargetPattern> Optional 0 - 1 String (128), variable Pattern or template for bind package name for DB2 target subsystem.
<planNameSourcePattern> Optional 0 - 1 String (24), variable Pattern or template for bind plan name for DB2 source subsystem.
<planNameTargetPattern> Optional 0 - 1 String (24), variable Pattern or template for bind plan name for DB2 target subsystem.
<recycleStoredProcs> Optional 0 - 1 String (1) Y = Yes, automatically refresh stored procedures & external user-defined functions in DB2 if change occurs.
N = No, don’t automatically refresh stored procedures & user-defined functions in DB2.
<schemaSourcePattern> Optional 0 - 1 String (128), variable Pattern or template for explicit schema in procedure-name, function-name, or trigger-name in CREATE command for DB2 source subsystem.
<schemaTargetPattern> Optional 0 - 1 String (128), variable Pattern or template for explicit schema in procedure-name, function-name, or trigger-name in CREATE command for DB2 target subsystem.
<wlmEnvMask> Optional 0 - 1 String (54), variable Default mask for WLM address space containing stored procedures.
<wlmEnvSourcePattern> Optional 0 - 1 String (54), variable Pattern or template for name of WLM address space containing stored procedures for source DB2 subsystem.
<wlmEnvTargetPattern> Optional 0 - 1 String (54), variable Pattern or template for name of WLM address space containing stored procedures for target DB2 subsystem.

DB2 Global Physical Subsystems - DB2ADMIN GBL_PHYS LIST

This function lists the DB2 physical subsystems defined at the global level for a given

ChangeMan ZMF started task. The request message may contain an empty <request> data element or a selection of optional subtags. Returned values include the physical subsystem ID, the logical subsystem ID, the fully qualified dataset name of the associated DB2 system load library, and predefined job cards for data binding in the DB2 production environment. Physical DB2 subsystems must be defined both in DB2 and in the DB2 Option for ChangeMan ZMF prior to running the DB2 physical subsystems list service.

The Serena XML service/scope/message tags and attributes for messages to list globally defined DB2 physical subsystems are:

<service name="DB2ADMIN"> 
<scope name="GBL_PHYS"> 
<message name="LIST">

These tags appear in both requests and replies.

DB2ADMIN GBL_PHYS LIST — Requests

Serena XML supports three options for DB2 physical subsystem lists at the global level:

  • Comprehensive List — Submit an empty <request/> data element (that is, one that contains no subtags) in the XML request message. The <request> tag itself is required in the message to distinguish a request from a reply. All DB2 physical subsystems defined at the global level for the ChangeMan ZMF started task are returned in the reply message.

    Note

    XML syntax allows both a long form and a short form for empty tags. An empty <request> tag can therefore be coded in one of two ways.

    Long form: 

    <request>
</request>
    Equivalent short form: 
    <request\>

    • Selected Site List — Name a desired site in the <db2SiteName> tag to request a list of all DB2 physical subsystems that reside at that site.

  • Single Physical Subsystem — Name the DB2 physical subsystem of interest in the <db2SubSystemId> tag to list global specifications for the named site.

Example XML — DB2ADMIN GBL_PHYS LIST Request

<?xml version="1.0"?>
<service name="DB2ADMIN">
    <scope name="GBL_PHYS">
        <message name="LIST">
            <header>
                <subsys>8</subsys>
                <product>CMN</product>
            </header>
            <request>
            </request>
        </message>
    </scope>
</service>

Data structure details for the <request> tag appear in Exhibit 9-17.

Exhibit 9-17 DB2ADMIN GBL_PHYS LIST <request> Data Structure

Subtag Use Occurs Data Type & Length Values & Dependencies
<db2SiteName> Optional 0 - 1 String (8), variable ZMF site name where DB2 subsystem resides.
NOTE: Use asterisk (*) wildcard or omit tag to list subsystems at all sites.
<db2SubsystemID> Optional 0 - 1 String (4), variable DB2 physical subsystem ID of interest.
NOTE: Use asterisk (*) wildcard or omit tag to list all physical subsystems.

DB2ADMIN GBL_PHYS LIST — Replies

The reply message for this function returns zero to many <result> data elements. Each <result> contains global specifications for one DB2 physical subsystem known to the ChangeMan ZMF started task that received the XML request message. If no DB2 subsystems are defined using the DB2 Option of ChangeMan ZMF, no <result> tags appear in the reply message.

The standard <response> data element follows any <result> tags in the reply and indicates the success or failure of the list request. Successful requests have a return code of 00. Unsuccessful requests have a return code of 04 or higher. Because it is the final data element in the XML reply message, the <response> tag serves as an end-of-list marker.

Example XML — DB2ADMIN GBL_PHYS LIST Reply

<?xml version="1.0"?>
<service name="DB2ADMIN">
    <scope name="GBL_PHYS">
        <message name="LIST">
            <result>
                <db2SubSystemId>C101</db2SubSystemId>
                <db2SiteName>SERT8</db2SiteName>
                <db2SystemLoadLib>SYS2.DB2810.SDSNLOAD</db2SystemLoadLib>
                <db2ProdBindJobCards>//USER35A JOB ,ACCOUNT INFORMATION</db2ProdBindJobCards>
                <db2ProdBindJobCards>//*</db2ProdBindJobCards>
                <db2ProdBindJobCards>//*</db2ProdBindJobCards>
                <db2ProdBindJobCards>//*</db2ProdBindJobCards>
                <db2ProdBindJobCard01>//USER35A JOB ,ACCOUNT INFORMATION</db2ProdBindJobCard01>
                <db2ProdBindJobCard02>//*</db2ProdBindJobCard02>
                <db2ProdBindJobCard03>//*</db2ProdBindJobCard03> 
                <db2ProdBindJobCard04>//*</db2ProdBindJobCard04>
            </result>
            <result>
                <db2SubSystemId>C105</db2SubSystemId>
                <db2SiteName>SERT8</db2SiteName>
                <db2SystemLoadLib>SYS2.DB2810.SDSNLOAD</db2SystemLoadLib>
                <db2ProdBindJobCards>//SERT8 JOB (AMW,000),&apos;C105&apos;,MSGCLASS=Y,</ db2ProdBindJobCards>
                <db2ProdBindJobCards>// TIME=(,10),USER=USER24,NOTIFY=USER24</ db2ProdBindJobCards>
                <db2ProdBindJobCards>//*</db2ProdBindJobCards>
                <db2ProdBindJobCards>//*</db2ProdBindJobCards>
                <db2ProdBindJobCard01>//SERT8 JOB (AMW,000),&apos;C105&apos;,MSGCLASS=Y,</ db2ProdBindJobCard01>
                <db2ProdBindJobCard02>// TIME=(,10),USER=USER24,NOTIFY=USER24</ db2ProdBindJobCard02>
                <db2ProdBindJobCard03>//*</db2ProdBindJobCard03>
                <db2ProdBindJobCard04>//*</db2ProdBindJobCard04>
            </result>
            <response>
                <statusMessage>CMN8700I - DB2 Admin service completed</statusMessage>
                <statusReturnCode>00</statusReturnCode> 
                <statusReasonCode>8700</statusReasonCode>
            </response> 
        </message> 
    </scope>
</service>

Data structure details for the <result> tag appear in Exhibit 9-18.

Exhibit 9-18 DB2ADMIN GBL_PHYS LIST <result> Data Structure

Subtag Use Occurs Data Type & Length Values & Dependencies
<db2ProdBindJobCard01> Optional 0 - 1 String (72), variable First of up to four default JCL job cards used in DB2 production bind jobs for this subsystem.
<db2ProdBindJobCard02> Optional 0 - 1 String (72), variable Second of up to four default JCL job cards used in DB2 production bind jobs for this subsystem.
<db2ProdBindJobCard03> Optional 0 - 1 String (72), variable Third of up to four default JCL job cards used in DB2 production bind jobs for this subsystem.
<db2ProdBindJobCard04> Optional 0 - 1 String (72), variable Fourth of up to four default JCL job cards used in DB2 production bind jobs for this subsystem.
<db2ProdBindJobCards> Optional 0 - 1 String (72), variable Use tags db2ProdBindJobCards01 - 04 instead.
<db2SiteName> Optional 0 - 1 String (8), variable ZMF remote site nickname associated with DB2 subsystem.
<db2SubsystemID> Optional 0 - 1 String (4), variable DB2 physical subsystem ID assigned by ZMF administrator.
<db2SystemLoadLib> Optional 0 - 1 String (44), variable Physical data set name of DB2 load library for this subsystem.

DB2 Global Logical Subsystems - DB2ADMIN GBL_LOGL LIST

This function lists the global defaults for DB2 logical subsystem settings for a given ChangeMan ZMF started task. The request message may contain an empty <request> data element or a selection of optional subtags. Returned values include DB2 logical and physical subsystem IDs and description, the site where the DB2 subsystem runs, and global configuration settings. DB2 subsystems must be properly configured in both DB2 and ChangeMan ZMF prior to running this service, or unexpected results may occur.

The Serena XML service/scope/message tags and attributes for messages to list globally defined DB2 logical subsystems are:

<service name="DB2ADMIN">
<scope name="GBL_LOGL"> 
<message name="LIST">

These tags appear in both requests and replies.

DB2ADMIN GBL_LOGL LIST — Requests

Serena XML supports the following options for listing DB2 logical subsystems defined at the global level:

  • Comprehensive List — Submit an empty <request> data element (that is, one that contains no subtags) in the XML request message. The <request> tag itself is required in the message to distinguish a request from a reply. All DB2 physical subsystems defined at the global level for the ChangeMan ZMF started task are returned in the reply message.

    Note

    XML syntax allows both a long form and a short form for empty tags. An empty <request> tag can therefore be coded in one of two ways.

    Long form: 

    <request>
</request>

    Equivalent short form:

    <request/>

  • Selected Site List — Name the site of interest in the <db2SiteName> tag to list all DB2 logical subsystems for selected site.

  • Selected Physical Subsystem List — In the <db2SubSystemId> tag, identify the DB2 physical subsystem where the parameters and templates of the logical subsystem(s) will be used. All logical subsystems defined for that physical subsystem are returned.

  • Single Logical Subsystem — Name the DB2 logical subsystem of interest in the <db2LogicalName> tag. Global default specifications for the requested subsystem are returned in the reply.

Example XML — DB2ADMIN GBL_LOGL LIST Request

<?xml version="1.0"?>
<service name="DB2ADMIN">
    <scope name="GBL_LOGL">
        <message name="LIST">
            <header>
                <subsys>8</subsys>
                <product>CMN</product>
            </header>
            <request>
            </request>
        </message>
    </scope>
</service>

Data structure details for the <request> tag appear in Exhibit 9-19.

Exhibit 9-19 DB2ADMIN GBL_LOGL LIST <request> Data Structure

Subtag Use Occurs Data Type & Length Values & Dependencies
<db2LogicalName> Optional 0 - 1 String (8), variable DB2 logical subsystem ID (or partition) of interest.
NOTE: Use asterisk (*) wildcard or omit tag to request all DB2 logical subsystems for application.
<db2SiteName> Optional 0 - 1 String (8), variable ZMF name of remote site where DB2 physical subsystem runs.
NOTE: Use asterisk (*) wildcard or omit tag to request all sites.
<db2SubSystemId> Optional 0 - 1 String (4), variable DB2 physical subsystem ID of interest.
NOTE: Use asterisk (*) wildcard or omit tag to request all DB2 physical subsystems for application.

DB2ADMIN GBL_LOGL LIST — Replies

The reply message for this function returns zero to many <result> data elements. Each <result> tag contains global specifications for one DB2 logical subsystem associated with the ChangeMan ZMF started task that received the XML request message.

The standard <response> data element follows any <result> tags in the reply and indicates the success or failure of the list request. Successful requests have a return code of 00. Unsuccessful requests have a return code of 04 or higher. Because it is the final data element in the XML reply message, the <response> tag serves as an end-of-list marker.

Example XML — DB2ADMIN GBL_LOGL LIST Reply

<?xml version="1.0"?>
<service name="DB2ADMIN">
    <scope name="GBL_LOGL">
        <message name="LIST">
            <result>
                <db2SubSystemId>C105</db2SubSystemId>
                <db2LogicalName>PROD</db2LogicalName>
                <db2SiteName>SERT8</db2SiteName>
                <bindOwnerInsert>PROD</bindOwnerInsert>
                <packageTargetPattern>???7</packageTargetPattern>
                <bindQualifierTargetPattern>?????T</bindQualifierTargetPattern>
                <logicalSubSysBindFailFlag>Y</logicalSubSysBindFailFlag>
                <recycleStoredProcs>Y</recycleStoredProcs>
                <keepTriggerSequence>Y</keepTriggerSequence>
            </result>
            <result>
                <db2SubSystemId>C105</db2SubSystemId>
                <db2LogicalName>PROM810</db2LogicalName>
                <db2SiteName>SERT8</db2SiteName>
                <logicalSubSysBindFailFlag>Y</logicalSubSysBindFailFlag>
                <recycleStoredProcs>Y</recycleStoredProcs>
                <keepTriggerSequence>Y</keepTriggerSequence>
            </result>
            <response>
                <statusMessage>CMN8700I - DB2 Admin service completed</statusMessage>
                <statusReturnCode>00</statusReturnCode>
                <statusReasonCode>8700</statusReasonCode>
            </response>
        </message>
    </scope> 
</service>

Data structure details for the <result> tag appear in Exhibit 9-20.

Exhibit 9-20 DB2ADMIN GBL_LOGL LIST <result> Data Structure

Subtag Use Occurs Data Type & Length Values & Dependencies
<bindOwnerInsert> Optional 0 - 1 String (128), variable TSO ID of default bind owner to be inserted into DB2 templates.
<bindOwnerSourcePattern> Optional 0 - 1 String (128), variable Pattern or template for DB2 source bind owner.
<bindOwnerTargetPattern> Optional 0 - 1 String (128), variable Pattern or template for DB2 target bind owner.
<bindQualifierInsert> Optional 0 - 1 String (128), variable Default high-level qualifier for DB2 datasets in bind plan commands, bind package commands, and create trigger definitions.
<bindQualifierSourcePattern> Optional 0 - 1 String (128), variable Pattern or template for high-level qualifier name for DB2 source subsystem bind commands.
<bindQualifierTargetPattern> Optional 0 - 1 String (128), variable Pattern or template for high-level qualifier name for DB2 target subsystem bind commands.
<db2LogicalName> Optional 0 - 1 String (8), variable DB2 logical subsystem ID (or partition) returned.
<db2SiteName> Optional 0 - 1 String (8), variable ZMF name of remote site where DB2 physical subsystem runs.
<db2SubsystemID> Optional 0 - 1 String (4), variable DB2 physical subsystem ID where logical subsystem templates run.
<keepTriggerSequence> Optional 0 - 1 String (1) Y = Yes, rebuild all triggers to preserve trigger sequence for table/event if a trigger changes.
N = No, don’t preserve trigger sequence if change occurs; instead move changed trigger to end.
<locationSourcePattern> Optional 0 - 1 String (128), variable Pattern or template for location ID for DB2 source subsystem.
<locationTargetPattern> Optional 0 - 1 String (128), variable Pattern or template for location ID for DB2 target subsystem.
<logicalSubSysBindFailFlag> Optional 0 - 1 String (1) Y = Yes, bind failure is significant; stop promote/demote processing if DB2 bind fails.
N = No, bind failure not significant; continue promote/demote process.
<logicalSubSystemComment> Optional 0 - 1 String (30), variable Free-format text description of DB2 logical subsystem (or partition).
<packageSourcePattern> Optional 0 - 1 String (128), variable Pattern or template for bind package name for DB2 source subsystem.
<packageTargetPattern> Optional 0 - 1 String (128), variable Pattern or template for bind package name for DB2 target subsystem.
<planNameSourcePattern> Optional 0 - 1 String (24), variable Pattern or template for bind plan name for DB2 source subsystem.
<planNameTargetPattern> Optional 0 - 1 String (24), variable Pattern or template for bind plan name for DB2 target subsystem.
<recycleStoredProcs> Optional 0 - 1 String (1) Y = Yes, automatically refresh stored procedures & external user-defined functions in DB2 if change occurs.
N = No, don’t automatically refresh stored procedures & user-defined functions in DB2.
<schemaSourcePattern> Optional 0 - 1 String (128), variable Pattern or template for explicit schema in procedure-name, function-name, or trigger-name in CREATE command for DB2 source subsystem.
<schemaTargetPattern> Optional 0 - 1 String (128), variable Pattern or template for explicit schema in procedure-name, function-name, or trigger-name in CREATE command for DB2 target subsystem.
<wlmEnvMask> Optional 0 - 1 String (54), variable Default mask for WLM address space containing stored procedures.
<wlmEnvSourcePattern> Optional 0 - 1 String (54), variable Pattern or template for name of WLM address space containing stored procedures for source DB2 subsystem.
<wlmEnvTargetPattern> Optional 0 - 1 String (54), variable Pattern or template for name of WLM address space containing stored procedures for target DB2 subsystem.