>I just got an MNOTE on a nIARV64 macro assembly. I
It would have been helpful to have seen the actual invocation and the
actual MNOTE,
as well as information about what kind of memory object you were actually
trying to detach.
None of the following invocations gets an MNOTE:
iarv64 request=DETACH,memobjstart=(2)
iarv64 request=DETACH,memobjstart=(2),affinity=LOCAL
iarv64 request=DETACH,memobjstart=(2),affinity=LOCAL,owner=NO
iarv64 request=DETACH,memobjstart=(2),affinity=LOCAL,owner=YES
iarv64 request=DETACH,memobjstart=(2),affinity=LOCAL,owner=YES*
,ttoken=(4)
iarv64 request=DETACH,memobjstart=(2),affinity=SYSTEM, *
v64common=NO
iarv64 request=DETACH,memobjstart=(2),affinity=SYSTEM, *
v64common=YES
Nor did anything else that I tried with syntactically correct use of the
other operands of request=DETACH.
In general, I'm quite sure that your suggested update is wrong. You do not
syntactically always need to specify AFFINITY=SYSTEM on REQUEST=DETACH.
I would not be surprised if semantically there are such cases (but those
would be represented by return/reason codes or abend/abendreason codes
from the service, not by MNOTEs from the macro).
So perhaps you could start over with what went wrong?
Peter Relson
z/OS Core Technology Design
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
