- This topic has 4 replies, 4 voices, and was last updated 18 years, 6 months ago by
.
-
Topic
-
Greetings Cloverleafer !!! V5.2 on AIX
I am trying to send a Low level ACK to Eclipsys SCM. x6 for Ack and x15 for Nak. We are having problem with that, so I turned on the “enable_all” but I did not see anything related to this low level ack, only the application level ack is there, why?
Attached are the log file and the tcl I use to send the ack.
Code:if [cequal $ack_type “AA”] {
# Build a low-level ACK
set lowACK x6
set lowAckMsg [msgcreate -type reply]
msgset $lowAckMsg $lowACK
return “{OVER $lowAckMsg} {CONTINUE $mh} {OVER $obMsg}”
} else {# Build a low-level NAK
set lowACK x15
set lowAckMsg [msgcreate -type reply]
msgset $lowAckMsg $lowACK
return “{OVER $lowAckMsg} {KILL $mh} {OVER $obMsg}”
}
Thanks for any help!
Sam 8)
-
Replies
-
-
Seems that I rember Charlie saying something about never using msgcreate because you have to populate all the metadata for the message. Charlie, does this apply in this circumstance?
(I also remember that he said that there was one instance where you have to use msgcreate… Could this be it?)
For this system-level ack, would you not want to ack any message received? I know that in ASTM messaging, you are not concerned with the data in the message when you do handshaking, you simply want to say “yeah.I got it”.
That being the case, would you not want to send the ack from the receiving PDL?
-
-
-
I for one would not recommend acking from within a pdl. It leaves a window open that could prevent the incoming message from getting into the rdb should a problem occur. Acking from the inbound tps stack assures that the message is without question in the rdb as it is put there after ther the pdl and before the tps runs. The acks should be application to application, not driver to driver or driver to application.
-
- The forum ‘Cloverleaf’ is closed to new topics and replies.
