Virtual Terminals and Data Queues

[bvining@xxxxxxxxxxxx]

Simon,

I discovered this problem a few years back and thought it had been
fixed.  But I guess not...

What's happening is that the SenderId information is actually tacked
on to the *DTAQ message by the data queue APIs prior to the actual ENQ
instruction.  The Virtual Terminal support is using ENQ directly and so
the API logic never gets into the picture.

I would suggest submitting an APAR on this situation.

Bruce Vining

>
>Hello,
>
>Does any one (IBM lurkers prefereably) know why the Virtual Terminal APIs ignor
>attribute on a data queue?
>
>Background:
>===========
>A data queue is named on the Open Virual Terminal API.  If the this data queue
>SENDERID(*NO) then all is fine.  If the data queue is created with SENDERID(*YE
>are __not__ fine.  What is __supposed__ to happen is that the enqueued message
>bytes allowing sender information to appear in those bytes.  What actually happ
>VT APIs simply enqueue the message at offset 0 and ignore the sender informatio
>
>The problem is that the Receive Data Queue API, which is the method for getting
>__does__ respect the SENDERID attribute and will think the first 36 bytes conta
>information and so does not return the enqueued message properly.
>
>Regards,
>Simon Coulter.
>


+---
| 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
+---