From Ingres Community Wiki

This is an Ingres 10.0 Connectivity project to assist system administrators in mapping the process ID back to the Communications Server(s) ID needed for netutil/iinamu.

Contents 1 References 2 Problem 3 Proposal 4 Example 'show server' command output for GCC server 5 Notes 5.1 Ingres Enhancement Number 5.2 DDS Review Summary 5.3 Test Considerations 5.4 OS Dependencies 6 Documentation

References

Ingres Community forum issue.

Problem

An Ingres System Administrator needed to quiesce an individual comms server, but could find nothing within Ingres to map the Unix process ID back to the internal communications server ID required by netutil/iinamu.

As discussed in the community forum issue, there are ways to achieve the mapping of the GCF server PID (Process ID) to the port as requested. For example, this can be achieved in several possible ways such as writing scripts using OS utilities, etc...

Proposal

Beginning with Ingres 9.1 (Ingres 2006r2), Ingres users can use the 'iimonitor' utility to monitor GCF servers to get all the info except PID which was not made available for GCF servers. It is proposed that with Ingres 10.0, the 'iimonitor' capabilities for the GCF servers be extended to include the PID information in the "Show server" command output.

Example 'show server' command output for GCC server

The aforementioned forum issue obtained the information using OS utilities and displayed it in the following format.

PID: 727648 IINAMU: 4788 TCP: 21064 GCC: II0

PID: 727118 IINAMU: 4784 TCP: 21065 GCC: II1

Beginning with Ingres 10.0 the equivalent information ( marked in bold below) can be obtained from the GCC server using 'iimonitor'. For comparison purposes it is worth mentioning here that the information pointed by label 'PID' maps to information pointed by 'Pid:' , 'IINAMU' maps to 'Server:' , 'TCP' maps to 'port', and 'GCC' maps to 'addr' in the section labeled 'Protocols' respectively.

% iinamu

Ingres NAME SERVICE MANAGEMENT UTILITY --

-- Copyright (c) 2009 Ingres Corporation

IINAMU> show servers

STAR * 32867

DASVR * 32868

COMSVR * 32871

COMSVR * 32872

COMSVR * 32873

COMSVR * 32874

INGRES * 32864 (sole server)

IUSVR * 32863

IINMSVR * 32869

IINAMU> quit

%iimonitor 32874

IIMONITOR> show server

Server: 32874

Class: COMSVR

Object: *

Pid: 25373

Connected Sessions ( includes system and admin sessions )

Current: 3

Active Sessions ( includes user sessions only )

Inbound sessions:

Current: 0

Limit: 64

Outbound sessions:

Current: 0

Limit: 64

Protocols

TCP_IP host:ingnet02 addr:MB3 port:23059

Registry Protocols

Not Enabled

IIMONITOR> quit

% iimonitor 32873

IIMONITOR> show server

Server: 32873

Class: COMSVR

Object: *

Pid: 25350

Connected Sessions ( includes system and admin sessions )

Current: 3

Active Sessions ( includes user sessions only )

Inbound sessions:

Current: 0

Limit: 64

Outbound sessions:

Current: 0

Limit: 64

Protocols

TCP_IP host:ingnet02 addr:MB2 port:23058

Registry Protocols

Not Enabled

IIMONITOR> quit

% iimonitor 32872

IIMONITOR> show server

Server: 32872

Class: COMSVR

Object: *

Pid: 25315

Connected Sessions ( includes system and admin sessions )

Current: 3

Active Sessions ( includes user sessions only ):

Inbound sessions

Current: 0

Limit: 64

Outbound sessions:

Current: 0

Limit: 64

Protocols

TCP_IP host:ingnet02 addr:MB1 port:23057

Registry Protocols

Not Enabled

IIMONITOR> quit

Notes

Ingres Enhancement Number

SIR 123621

DDS Review Summary

N/A

Test Considerations

OS Dependencies

Documentation

Process ID (PID) for GCF Servers Displayed in iimonitor

The iimonitor "show server" command output for the Communications Server (GCC), Data Access Server (GCD), and Name Server (GCN) now displays the process ID information. Also, the GCC and GCD servers display the actual symbolic port address in the "addr:" field of the "Protocols" section.

Here is an example of the iimonitor "show server" command output, with new fields shown in bold:

IIMONITOR> show server

Server: 32874

Class: COMSVR

Object: *

Pid: 25373

Connected Sessions ( includes system and admin sessions )

Current: 3

Active Sessions ( includes user sessions only )

Inbound sessions:

Current: 0

Limit: 64

Outbound sessions:

Current: 0

Limit: 64

Protocols

TCP_IP host:ingnet02 addr:MB3 port:23059

Registry Protocols

Not Enabled