Ray,
Here is the combination that works (but requires a file definition which
is not okay).
I give it a 0 on OPEN (result: the file is opened)
I will get now only WRITE calls (not exactly what documentation says)
- and I can extract my data
I get a final CLOSE call.
What I think is wrong- the
I must correct parts of my last stmt-
I said:
I will get now only WRITE calls (not exactly what documentation says)
Correct is:
It does pass control to the PROCESS exit (when 0 at OPEN is given) and
honors the RC given at return of PROCESS (just as the manual says).
BUT what is left is the
I've had a peek at the HLASM source code (now that we have it
here at Hursley). I see that the VSE version of the Assembler
appears to have a bug in the ADATA open support, in that code in
ASMA00V for PQ26966 (from 1999) causes a spurious check on
whether the SYSADAT DTF was opened correctly when
Jonathan,
now that makes sense- Thank you
here is my detailed answer:
From a quick glance, I cannot see any similar problem in the
code for other platforms, so I suspect it is VSE-specific.
My guess as well.
As for question 2, my VSE knowledge is so rusty that it's
actually DOS/VS
John,
Three sample ADATA exits are provided with the HLASM ASMASAMP library --
Only in z/OS (and the z/OS, I can use, did not restore the ASMASAMP)
you might be able to use them as models for the ADATA exit you are
writing.
I am done testing (with the restriction that I need a file as the
On 2012-04-20 11:53, Martin Truebner wrote in ASSEMBLER-LIST:
Did you ever try to copy code from a PDF? As and idea: a funny char
aside of the space (in col 1) and an other one in col 10 and col 16
would make it a easy to rebuild source from a (PDF-)printed manual.
1) There's another good
