Paul,
1) There's another good reason here to regret IBM's SoD to
abandon Bookie in favor of PDF.
Absolutly.
1b) I like to distribute README files containing code examples
as HTML with the code between PRE and /PRE
I do it without anything around it.
Here is code that has nothing
I am out of the office until Monday May 18th. I will not have access to email
or phone.
I like to issue a message about success
CLOSE would be nice- but documentations says:
The contents of the error buffer are ignored on CLOSE calls to the
exit, unless the exit requests immediate termination.
No- I don't want to terminate- Job complete is what I would like to
say.
Any ideas?
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
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
I am writing an ADATA Exit for HLASM
I told the invoker (ASMA90) all possible Return-code/reason code
combinations (that is 4/0 4/4 4/8), because I want to write the records
in my format. All I get is a one line nastygram:
** ASMA418C Unable to open ADATA file
Question 1: anyone succeeded
I am out of the office until Friday 4/20/2012. I will read your note, as time
permits, when I return to the office. If your e-mail is urgent and concerns a
production issue/problem, please send your note to the 'GLO-RETS zOS Content'
mailbox for attention.
Thanks!
On 2012-04-19 06:37, Martin Truebner wrote:
I am writing an ADATA Exit for HLASM
I told the invoker (ASMA90) all possible Return-code/reason code
combinations (that is 4/0 4/4 4/8), because I want to write the records
in my format. All I get is a one line nastygram:
** ASMA418C Unable to open
On 4/19/12, Martin Truebner mar...@pi-sysprog.de wrote:
Ray,
I assume you tried // ASSGN SYSADAT,IGN?
No i did not- Why would you expect VSE to know something about that
special number ADAT?
Perhaps because he looked in the HLASM Programmer's Guide, Document
Number SC26-4941-05, and there
On 2012-04-19 12:06, Martin Truebner wrote:
Ray,
I assume you tried // ASSGN SYSADAT,IGN?
No i did not- Why would you expect VSE to know something about that
special number ADAT?
But I did try // DLBL +EXTENT (pointing to SYS010) and assgn SYS010
IGN- This did not work (and this never
14 matches
Mail list logo
