HP NonStop G-Series - Manual (Page 100)

Developing a Tandem Program to Create UMS Messages
Using DDE Hot and Warm Data Links
7–4 110838 Tandem Computers Incorporated
Considerations
You should put the data to be forwarded by the Tandem DDE Gateway to your client
application here.
For compatibility with most client applications and tools, the user data should be
ANSI (ISO 8859/1) characters with no imbedded binary numbers or other non-
printable data. For English language data, ANSI is effectively the same as ASCII.
Most tools require a terminating byte of binary zeros. If your client application is
written in the C language, you can send binary data but you must do all necessary
data conversion in the client application. It is best to use only ANSI characters when
possible.
Reply Message Example If your application on the Tandem system sends a UMS message to the RSC TDP with
a writeread operation, the reply message will be as follows:
01 RSC-UMS-TDP-REC.
03 RSC-HEADER.
05 N-CODE NATIVE-2.
05 U-VERSION NATIVE-2.
88 RSC-C30 VALUE 17182.
05 AC-TERMINAL-NAME PIC X(10).
05 AC-ALIAS PIC X(32).
05 U-ALIAS-TYPE PIC 9(4) COMP.
88 RSC-GROUP-ALIAS VALUE 1.
88 RSC-SESSION-ALIAS VALUE 2.
03 UMS-REPLY.
03 DDE-ERROR-RETURN NATIVE-2.
03 DDE-NUM-TIMES-DELIVERED NATIVE-2.
Considerations
DDE-ERROR-RETURN is zero if no error was encountered by the Tandem DDE
Gateway, or it is one of the following values:
300 UMS message too short
301 MESSAGE-VERSION not 1
302 DDE-ITEM-NAME has no byte of binary zeros
303 Invalid DDE-ITEM-NAME
304 Tandem DDE Gateway internal error
305 Workstation too low on memory to deliver data
306 DDE protocol error communicating with client application
307 Client rejected data because it was busy
308 Client rejected data
309 Client timed out while accepting data
310 Client program ended without ending the DDE conversation
311 Workstation out of system timers
312 Message rejected by User Hook Library as an error
313 Message skipped by User Hook Library