Gary,
In one of my first programs, I inadvertently defined a Vcon double.
It gave me exactly the result you describe. It led me to conclude that
the loader simply adds the offset to the base value.
If you define (or load) twice, the addition is performed twice as well...
Looks like you will need a lock or latch of some kind after all. Or
pre-load, maybe.
I'm sure you'll be able to determine what will work best for your product.
Success!
Abe Kornelis
==========
Gary Weinhold schreef op 21-1-2015 om 16:26:
We have a situation where it appears that a LOAD of a module may not
be resolving a VCON correctly. The first requirement for this module
in a region will cause us to issue a LOAD for the module. In a
multitasking environment we know that our code could be running on two
TCBs simultaneously, but I don't see anything in the manuals to
indicate that we have to prevent LOAD from running at the same time.
From what we can see the address that ends up in the VCON is the
displacement from the beginning of the module (the value presumably
placed their by the binder) plus twice the load point. Has anyone seen
this happen before? Is there an undocumented requirement to single
thread multiple LOADs for the same module within a region?
Gary Weinhold
Data Kinetics, Ltd.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
