I have written an OpenVMS socket based communication package to interface with our proprietary database and have observed behavior that I would like clarified if possible.
After connecting to the DT81 and sending an unload request for data from a 1 minute schedule's most current data (details omitted), I then read my socket and found "host computer return data" that continued to be sent for all schedules as they executed.
I corrected the problem by assigning the "NR" option to all of the variables in the schedules. I chose this method because I read on page 86 of the dataTaker User's Manual that the return, echo, error message, and alarm message switches were disabled during unloads.
Is the documentation referring to disabling by the unload command or by the vendor software that explicitly sends "/r/e/m/z". My assumption is the latter. The "practical" reason that I ask is that I would prefer to send the switches myself and maintain the ability to return these messages to other connections.
I have written an OpenVMS socket based communication package to interface with our proprietary database and have observed behavior that I would like clarified if possible.
After connecting to the DT81 and sending an unload request for data from a 1 minute schedule's most current data (details omitted), I then read my socket and found "host computer return data" that continued to be sent for all schedules as they executed.
I corrected the problem by assigning the "NR" option to all of the variables in the schedules. I chose this method because I read on page 86 of the dataTaker User's Manual that the return, echo, error message, and alarm message switches were disabled during unloads.
Is the documentation referring to disabling by the unload command or by the vendor software that explicitly sends "/r/e/m/z". My assumption is the latter. The "practical" reason that I ask is that I would prefer to send the switches myself and maintain the ability to return these messages to other connections.