Displays to standard output information about applications
that are connected to host databases via DB2 Connect™ Enterprise Edition.
Authorization
One of the following:
- sysadm
- sysctrl
- sysmaint
- sysmon
Required connection
Instance. To list
the DCS applications at a remote instance, it is necessary to first
attach to that instance.
Command syntax
>>-LIST DCS APPLICATIONS--+-------------+----------------------><
+-SHOW DETAIL-+
'-EXTENDED----'
Command parameters
- LIST DCS APPLICATIONS
- The default application information includes:
- Host authorization ID (username)
- Application program name
- Application handle
- Outbound application ID (luwid).
- SHOW DETAIL
- Specifies that output include the following additional information:
- Client application ID
- Client sequence number
- Client database alias
- Client node name (nname)
- Client release level
- Client code page
- Outbound sequence number
- Host database name
- Host release level.
- EXTENDED
- Generates an extended report. This report includes all of the
fields that are listed when the SHOW DETAIL option is specified, plus
the following additional fields:
- DCS application status
- Status change time
- Client platform
- Client protocol
- Client code page
- Process ID of the client application
- Host coded character set ID (CCSID).
Note: - The application status field contains one of the following values:
- connect pending - outbound
- Denotes that the request to connect to a host database has been
issued, and that DB2 Connect is
waiting for the connection to be established.
- waiting for request
- Denotes that the connection to the host database has been established,
and that DB2 Connect is
waiting for an SQL statement from the client application.
- waiting for reply
- Denotes that the SQL statement has been sent to the host database.
- The status change time is shown only if the System Monitor UOW
switch was turned on during processing. Otherwise, Not Collected is
shown.
Usage notes
The database administrator
can use this command to match client application connections to the
gateway with corresponding host connections from the gateway.
The
database administrator can also use agent ID information to force
specified applications off a DB2
Connect server.