OSI/MHS Configuration and Management Manual

Troubleshooting Your OSI/MHS Subsystem
OSI/MHS Configuration and Management Manual—424827-003
9-10
Problem Examples
OSI/MHS is the initiator of an association. For example, the above display indicates
190 unsuccessful attempts by OSI/MHS to initiate an association. The counters are
described in detail in the OSI/MHS SCF Reference Manual.
RTS Process Abend Problem
OSI/MHS RTS processes can abend under certain conditions when attempting to
communicate with OSI/MHS MTA processes. These conditions are as follows:
1. The TRANSFER entry-manager process EMSERV has been restarted and has
been attempting to write a message to its outlog file reporting that the queue file
was a pre-enlightened queue file.
2. EMSERV could not write to the outlog file because the outlog file is a terminal
running a TACL process (that is, it is in read-only mode).
3. EMSERV has hung waiting to write to the outlog file.
4. The OSI/MHS MTA process hangs because EMSERV does not respond.
5. The OSI/MHS RTS process abends while waiting to communicate with the MTA
To resolve this problem, ensure that the EMSERV process is configured to write to a
valid outlog file.
Problem Examples
The following example illustrates a connection rejection due to an invalid remote NSAP
(REM-NSAP-1) in the definition of an adjacent MTA. In the example, two MTAs are
configured, each on a different system. The two systems are connected by a packet-
switching network. One route has been defined between these MTAs; no alternate
routes are involved. These example configurations are similar to those in Appendix A,
Examples of Configuration Files.