Data Sharing Naming Conventions

 <  Day Day Up  >  

It is imperative that appropriate naming conventions are developed for data sharing constructs. This is important to enable effective management of the data sharing environment. Data sharing naming conventions fall into two categories:

  • Group-level names for structures owned by the data sharing group . These names are shared by all members of the data sharing group. Group-level names that must be created include the following:

    DB2 group name ” The name that is used to define the DB2 data sharing group to MVS. The group name can be no longer than characters and can be comprised of the characters A-Z , 0-9 , $ , # , and @ . The group name must begin with an alphabetic character.

    Catalog alias ” The name of the MVS catalog alias. This catalog alias can be up to 8 characters long. The DB2 group name should be used for the catalog alias name.

    IRLM group name ” The name used to define the IRLM to the data sharing group.

    Location name ” Each data sharing group has one DDF location name. This location is used by remote requests to indicate the data sharing group. This name can be up to 16 characters long.

    Generic LU name ” This name allows remote requesters to configure their systems to treat the data sharing group as a single LU. The generic LU name can be up to 8 characters in length.

    Group attach name ” A generic four character name that is used by applications using TSO or CALL ATTACH. This enables the application to attach to any DB2 member that is contained in the data sharing group.

    Coupling facility structure names ” Names are required for the lock structure, SCA, and group buffer pools. These names are predefined by DB2 as shown in Table 19.2. In place of the groupname, substitute the actual DB2 group name. For group buffer pools, the only difference is the prefix "G" added to the buffer pool name.

  • Member-level names for structures owned by each DB2 data sharing member. Member-level names that must be created include:

    DB2 member name ” The name that is used to identify the individual DB2 subsystem to OS/390 for inclusion into the data sharing group. Like the data sharing group name, this name can be no longer than 8 characters and can be comprised of the characters A-Z , 0-9 , $ , # , and @ . The DB2 member name is used by DB2 to form its OS/390 cross-system coupling facility (XCF) member name.

    Subsystem name ” The name can be up to four characters long and is used by all attachment interfaces.

    LU name ” Must be unique within the data sharing group and the network.

    Work file database name ” Each data sharing member must have its own work file database. The work file database in the non-data sharing environment is known as DSNDB07 . The work file database name can be up to eight characters long.

    Command prefix ” Up to eight-character prefix used for DB2 command execution.

    IRLM subsystem name ” Defines the IRLM subsystem.

    IRLM procedure name ” Defines the IRLM startup procedure.

    ZPARM name ” Each member of a data sharing group has its own DSNZPARM load module.

Table 19.2. Coupling Facility Structure Naming Conventions

Structure Type

Naming Standard

Lock Structure

groupname _LOCK1

SCA

groupname _SCA

Group Buffer Pools

groupname _G bufferpool


 <  Day Day Up  >  


DB2 Developers Guide
DB2 Developers Guide (5th Edition)
ISBN: 0672326132
EAN: 2147483647
Year: 2004
Pages: 388

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net