×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On 9/28/21 4:15 PM, Frank Kolmann wrote:
I am guessing you did an exfmt.
That was the problem.
Last night, I thought of switching to a WRITE before I start looping for
a response, then a READ at the top of the loop, and another WRITE before
the call to QMHSNDPM.
I think it was while I was sitting in my subscription seat at Hollywood
Bowl (Section E, Row 1, Seat 1; nearly half the boxes are further away
from the stage), while Dudamel conducted the LAPhil in an all-Mozart
program.
I finally got around to trying the idea (after trying "*NOTIFY" in the
unaltered code, for the sake of completeness; that gave me another break
message) just now, and (in combination with going back to "*STATUS") it
solved the problem.
Apparently the QMHSNDPM writes to the record that's already on the
display, and so the WRITE that's part of the EXFMT overwrites the one
that QMHSNDPM had just done.
--
JHHL
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
