Virtual Terminals and Data Queues

M

Hello,

Does any one (IBM lurkers prefereably) know why the Virtual Terminal APIs 
ignore the SENDERID 
attribute on a data queue?

Background:
===========
A data queue is named on the Open Virual Terminal API.  If the this data queue 
is created with 
SENDERID(*NO) then all is fine.  If the data queue is created with 
SENDERID(*YES) then things 
are __not__ fine.  What is __supposed__ to happen is that the enqueued message 
is offset by 36 
bytes allowing sender information to appear in those bytes.  What actually 
happens is that the 
VT APIs simply enqueue the message at offset 0 and ignore the sender 
information.

The problem is that the Receive Data Queue API, which is the method for getting 
the queue entry, 
__does__ respect the SENDERID attribute and will think the first 36 bytes 
contains sender 
information and so does not return the enqueued message properly.

Regards,
Simon Coulter.

«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»
«» FlyByNight Software         AS/400 Technical Specialists       «»
«» Eclipse the competition - run your business on an IBM AS/400.  «»
«»                                                                «»
«» Phone: +61 3 9419 0175      Mobile: +61 0411 091 400           «»
«» Fax:   +61 3 9419 0175      mailto: shc@flybynight.com.au      «»
«»                                                                «»
«» Windoze should not be open at Warp speed.                      «»
«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---