IBM Books

Application ID


Snapshot Information Level
Application
DCS Application
Lock


API Structure(s)
sqlm_appl_id_info
sqlm_dcs_applinfo
sqlm_appl_lock


Monitor Group
Basic
Basic
Basic


Resettable


No


 


Event Information Level
Connection
 
Statement
 
Transaction
Deadlock


API Structure(s)
sqlm_conn_event
sqlm_connheader_event
sqlm_stmt_event
sqlm_stmttext_event
sqlm_xaction_event
sqlm_dlconn_event


 


API Element Name
Element Type


appl_id
information

 

Description: This identifier is generated when the application connects to the database at the database manager or when DDCS receives a request to connect to a DRDA database.

Usage: This ID is known on both the client and server, so you can use it to correlate the client and server parts of the application. For DDCS applications, you will also need to use "Outbound Application ID". to correlate the client and server parts of the application.

This identifier is unique across the network. There are different formats for the application ID, which are dependent on the communication protocol between the client and the server machine on which the database manager and/or DDCS are running. Each of the formats consists of three parts separated by periods.

  1. APPC

    Format
    Network.LU Name.Application instance

    Example
    CAIBMTOR.OSFDBX0.930131194520

    Details
    This application ID is the displayable format of an actual SNA LUWID (Logical Unit-of-Work ID) that flows on the network when an APPC conversation is allocated. APPC-generated application IDs are made up by concatenating the network name, the LU name, and the LUWID instance number, which create a unique label for the client/server application. The network name and LU name can each be a maximum of 8 characters. The application instance corresponds to the 12-decimal-character LUWID instance number.

  2. TCP/IP

    Format
    *TCPIP.IPAddr.Application instance

    Example
    *TCPIP.A12CF9E8.930131214645

    Details
    A TCP/IP-generated application ID is made up by concatenating the string "*TCPIP", the IP address in hexadecimal characters, and a unique identifier for the instance of this application. The IP address is a 32-bit number displayed as a maximum of 8 hexadecimal characters.

  3. IPX/SPX

    Format
    Netid.nodeid.Application instance

    Example
    C11A8E5C.400011528250.0131214645

    Details
    An IPX/SPX-generated application ID is made up by concatenating a character network ID (8 hexadecimal characters), a node id (12 hexadecimal characters), and a unique identifier for the instance of the application. The application instance corresponds to a 10-decimal-character time stamp of the form MMDDHHMMSS.

  4. NetBIOS

    Format
    *NETBIOS.nname.Application instance

    Example
    *NETBIOS.SBOIVIN.930131214645

    Details
    A NetBIOS application ID is made up by concatenating the string "*NETBIOS", the nname defined in the client's database configuration file, and a unique identifier for the instance of this application.

  5. Local Applications

    Format
    *LOCAL.DB2 instance.Application instance

    Example
    *LOCAL.DB2INST1.930131235945

    Details
    The application ID generated for a local application is made up by concatenating the string *LOCAL, the name of the DB2 instance, and a unique identifier for the instance of this application.

Use "Client Communication Protocol" to determine which communications protocol the connection is using and, as a result, the format of the application ID;.

[ Top of Page | Table of Contents | Glossary | Index ]

[ DB2 List of Books | Search the DB2 Books ]