OSI/MHS Management Programming Manual
Event Messages
OSI/MHS Management Programming Manual—424824-001
6-143
38: ZMHS-EVT-ACCT-ROS-ASSOC-OP
ZMHS-TKN-OR-TLTX-ORGANIZ
is the teletex organization name component of an O/R name. It is an optional token 
that is supplied if it is present in the X.400 O/R name. The maximum length is 64 
bytes.
ZMHS-TKN-OR-TLTX-COMMON-NAME
is the teletex common name component of an O/R name. It is an optional token that 
is supplied if it is present in the X.400 O/R name. The maximum length is 64 bytes.
ZMHS-TKN-OR-TLTX-PNAME-SUR
is the teletex personal surname component of an O/R name. It is an optional token 
that is supplied if it is present in the X.400 O/R name. The maximum length is 
40 bytes.
ZMHS-TKN-OR-TLTX-PNAME-GIVEN
is the teletex personal given-name component of an O/R name. It is an optional 
token that is supplied if it is present in the X.400 O/R name. The maximum length 
is 16 bytes.
ZMHS-TKN-OR-TLTX PNAME-INIT
is the teletex personal initials component of an O/R name. It is an optional token 
that is supplied if it is present in the X.400 O/R name. The maximum length is 
5 bytes.
ZMHS-TKN-OR-TLTX PNAME-GENQ
is the teletex personal generation qualifier component of an O/R name. It is an 
optional token that is supplied if it is present in the X.400 O/R name. The maximum 
length is 3 bytes.
ZMHS-TKN-OR-TLTX-ORG-UNIT-1...4
is the teletex organizational unit name component of an O/R name. It is an optional 
token that is supplied if it is present in the X.400 O/R name. The maximum length 
is 32 bytes.
ZMHS-TKN-OR-TLTX-DD-TYPE-1...4
is the teletex domain-defined attribute type component of an O/R name. It is an 
optional token that is supplied if it is present in the X.400 O/R name. The maximum 
length is 8 bytes.
Cause. This accounting message indicates a successful or unsuccessful association 
establishment with a remote user agent. 
Recovery. If the remote service (RS) process association is accepted, no corrective 
action is needed.  If the RS process association is rejected, follow this procedure: 
•
Examine the surrounding messages in the message log to obtain more information. 










