Displays communication control information about a communication-established server. This command can be used when it is necessary to determine whether processing control is on the HiRDB side or on the client side if the client stops responding during UAP operation.

(a) -a

Displays communication control information about all processes in the HiRDB system. This option can be used to determine details of communication control information.

1. Return code 0 for the pdls -d rpc command indicates normal termination, and return code 8 indicates abnormal termination.
2. When the -a option is specified and the client is connected with server type F or S, the following information is displayed:
   
   • Client's OS
   • Client's group name
   • XA interface usage status
3. When the -a option is specified and the client is connected with client type C, the following information is displayed:
   
   • Client's process ID
   • Client's IP address
   • Client's UAP identification information

(a) Default option (UAP connected)

 
 [aaaa]
  Client Information :
   PID     ADDR     NAME    OS  GROUP   XA
   bb...b  cc...c   dd...d  e    ff     g
  Server Information :
   PID    SVID   STATUS SYS_EVENT USR_EVENT CRITICAL(MASK) SERVICE SYS_CALL
   hh...h ii...i jj...j 0xkk...k  0xll...l  m(0xnn...n)    oo...o  0xtt...t
      :      :      :        :        :           :           :         :
 [aaaa]
  Client Information :
   :
 

(b) Default option (Utility connected)

 
 [aaaa]
  Server Information :
   PID    SVID   STATUS SYS_EVENT USR_EVENT CLITICAL(MASK) SERVICE SYS_CALL
   hh...h ii...i jj...j 0xkk...k  0xll...l  m(0xnn...n)    oo...o  0xtt...t
      :      :      :        :        :           :           :         :
 [aaaa]
  Server Information :
   :
 

(c) The -a option specified

 
 HOSTNAME : ss...s
 PID    SVID   STATUS SYS_EVENT USR_EVENT CLITICAL(MASK) SERVICE OS GROUP XA ...1
 hh...h ii...i jj...j 0xkk...k  0xll...l  m(0xnn...n)    oo...o  e  ff    Y  ...2
 CLTKIND SVRKIND CLTPID CLTADDR CLTNAME ACTID    SYS_CALL                    ...3
 p       q       bb...b cc...c  dd...d  0xrr...r 0xtt...t                    ...4
 :        :        :       :       :         :       :
 

Explanation

Items 1 to 4 are displayed in one line each. Items 2 and 4 are displayed repetitively for each process.

aaaa

Item number

bb...b

Process ID of the client connected to a server process (in decimal, up to 10 digits)

The process ID is not displayed in the following cases:

• The server process is not connected to the client
• The client library connected to the UAP is earlier than version 04-00
• Connection is made from a Type4 JDBC driver

cc...c

IP address of the client connected to a server process (up to 15 characters)

If the client library connected to the UAP is earlier than version 04-00, the IP address is not displayed.

dd...d

UAP identification information for the client connected to a server process (up to 30 characters)

Displays identification information about the UAP specified in the PDCLTAPNAME client environmental variable. If PDCLTAPNAME is not specified, the command displays Unknown. If the client library connected to the UAP is earlier than version 04-00, the UAP identification information is not displayed.

e

Client operating system

W

Workstation-based client

P

PC-based client

M

Mainframe-based client

If the client library connected to the UAP is earlier than version 04-00, the client's OS is not displayed.

ff

Client group name (up to 2 characters) of the client connected to a server process.

When using one character, specify a user-assigned client group name; when using two characters, specify a HiRDB-supplied client group name by client type.

The client group name is not displayed in the following cases:

• The client library connected to the UAP is earlier than version 04-00
• Connection was made with an unlimited use frame using the connection frame guarantee facility for a client group name
• The connection frame guarantee facility for a client group name is not used

Following is a list of HiRDB-supplied client group names by client type:

Client group name	Client type
XA	X/Open XA interface
PC	PC client
WS	WS client
MF	Mainframe-based client

g

Use of X/Open XA interface

Y

Used

N

Not used

If the client library connected to the UAP is earlier than version 04-00, the X/Open XA interface usage status is not displayed.

hh...h

Server process ID (up to 10 decimal digits)

ii...i

Server name (up to 8 characters)

jj...j

Process status display (up to 12 characters)

ACTIVE

currently processing

SUSPEND (QUE)

processing suspended (service wait state: queued)

SUSPEND (CLT)

processing suspended (waiting for next service)

SUSPEND (SVR)

processing suspended (waiting for other messages)

kk...k

Display of process status details (26 characters)

Displays system internal code.

ll...l

Display of process status details (8 characters)

Displays system internal code.

m:

Critical status display

Y

Critical

N

Not critical

nn...n:

Critical information display (8 hexadecimal digits)

oo...o

Service name display (up to 32 characters)

Displays internal system information.

p

Client type

C

Client

U

Utility

Blank

Other than above

q

Server type (With -a option, displays a server type only when the client type is C.)

F

Front-end server (FES)

B

Back-end server (BES)

D

Dictionary server (DIC)

S

Single server (SDS)

rr...r

Activity ID (18 characters)

This is not displayed for a process that does not have an activity ID.

ss...s

Host name (up to 32 characters)

tt...t

Internal information used by the system (8 characters)

SQL not responding

If the STATUS is ACTIVE, the server is processing.

To determine whether current control is with the client or the server:

This can be determined based on the information indicated in the STATUS display on the front-end server (single server). If the STATUS display on the front-end server is SUSPEND (CLT), control is with the client.