OSI/MHS Configuration and Management Manual

Troubleshooting Your OSI/MHS Subsystem
OSI/MHS Configuration and Management Manual—424827-003
9-21
Problem Examples
TSEL : 52
NSAP : 52
Initiator : 0 Turn : 0 Checkpoint size : 1 Window size : 3
Safe store window : 2 Application Protocol : 88 Abstract syntax id : 0
Dialogue mode : 0
Local MTA name :
Local Password :
Remote MTA name : 4D544131
Remote Password : 4D544132
Recovery time : 600 Recovery expiry : 0 Delay time : 60 Delay expiry
: 0 PCD List size : 3 PCID : 3
Current session connection id
User ref : 040751515A4B312030 Common ref :
170D3933303630323139323034355A Add ref : 140135
Activity id :
Initial session connection id :
User reference : Common ref : Add ref :
Activity id :
Activity number : 0
Original session connection id
User reference : 040751515A4B312030 Common ref :
170D3933303630323139323034355A Add ref : 140135
SpTx : 0 SpRx : 0 SpAckTx : 0 SpAckRx : 0
PDU Id= 0 0-0-0-0-0
Offset : 0 Transfer time : 0 Transfer Expiry : 0 Size : 0
Completed flag : 0
Roll back index : 0 Roll back overflow : 0
The RTS receives the RTORQ (RTS open request) APDU from the initiating RTS, as
shown in trace record number 9. The RTS then passes the open request to the MR
process for validation. (There is no trace record for the interaction between the RTS
and MR processes because interlayer tracing was not enabled.) The next trace record
(number 12) shows a RT-OPres- (RTS open response) with a refusal reason of 3
(rejected).
Refusal reason is an OSI/MHS internal error code that represents the refusal reason
code. Refusal reason code 3 means that the OSI address is invalid. The refusal
reason codes are mapped to CCITT RTSE refusal reasons. Table 9-5 lists possible
values of the internal refusal reasons mapped to the CCITT RTSE refusal reason code.
Table 9-5. RTS Refusal Code Mapping (page1of2)
No. Internal Name
CCITT RTSE
(Refuse reason) Meaning
1 BAD_MODE unacceptable
dialogue mode
The specified mode is not
MONOLOGUE.
2 AUTH_FAIL validation failure MTA passwords do not match.
3 BAD_OSI_ADDRESS validation failure The OSI address does not
exist in an MTA object.
4 BAD_PROTOCOL validation failure The supplied protocol is not
MTS-TRANSFER, MTS-
TRANSFER-PROTOCOL, or
MTS-TRANSFER-
PROTOCOL-1984.