[Info-vax] yet another sys$qiow question

[Richard Maher]

On 8/20/2015 9:05 PM, Bob Koehler wrote:
> In article <mr2upj$26c$2 at speranza.aioe.org>, Richard Maher <maher_rjSPAMLESS at hotmail.com> writes:
>> On 8/20/2015 1:42 AM, John Reagan wrote:
>>
>>>
>>> A lot of stuff that doesn't wrap. Reminiscent oflatent personality disorder lacking empathy.
>>
>>
>> Use COBOL, IOSB on the heap, Done!
>>
>> Stop getting your jollies by telling everyone about how cool and hip C is.
>
>     There are plenty of ways to put the IOSB on the heap in C, too.
>     That's not what volatile addresses.
>

So what do you say volatile addresses address? The COBOL compiler 
directives say our *DC VOLATILE stops the compiler using registers: -

http://h71000.www7.hp.com/doc/82final/6297/6297pro_108.html#mem_manage

When I used to call asynch services the iosb would be the first item in 
a record structure whose start address was passed as the ASTPARM or 
solely as the IOSB for those services that mandated the IOSB as the 
AST's parameter. Often I have an array of say connections or mailboxes 
that would have a private IOSB for each channel or, as was the case with 
my shmicko Tier3 Applet Uploader, just lib$get_vm a chunk of heap and 
map it however you want.

Is you iosb not aligned? Do you have atomicity or word-tearing issues or 
are you simply overtuning, prevaricating, and navel-gazing because 
you've chosen to use a language so shit it doesn't even have Strings?