So, tell me what the ADATA issues are, what you'd like to see change and
HLASM improve. Asking for ASMLANX may not be the answer.
I (believe) RFE entries can be marked private. RFEs allow us to review
requirements & understand what required by users. You can vote on RFE
items.
Go cr
I should also say:
Ed make a useful suggestion - make some of these items Share requests.
Also, John and I will be in San Francisco at the spring Share conference.
We (am taking a liberty here - I've not asked John, but I'm sure the
answer is yes) can sort out a conference room to dis
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 in
Hello Sharuff,
I think the main problem people have with ADATA is that it's so
extraordinarily verbose. That, I suppose, is why you wrote ASMLANGX for IDF.
I suppose if IBM would create user settable (and resettable) controls
in HLASM over which particular ADATA record types did and did no
Hi:
Is there a limitation on how many ADATA records can be written? For
example, when I define the ADATA file as a PDSE, and the number of records
must exceed the 64K PDSE member limit, the assembly fails and I get this
message:
IEC036I 002-AC,IGC0005E,jobname,procname,ADATA,ucb@,volser
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
at had logic build into them to honor it).
>> You could try DLBLing a "dummy" 1-track SAM-ESDS file.
As long as I do not specify an exit it does produce data.
>> I have used ADATA in the past under VSE; I created VSAM files that
It works with regular SAM as well.
--
Marti
SC26-4941-05, and there found:
"ADATA
Specifies that the assembler collect associated data and write it
to the associated data file. You define the associated data file with
the SYSADATA ddname on z/OS and CMS, or with the SYSADAT filename on
z/VSE."
--
Bob Netzlof a/k/a Sweet Old Bob
Debug Tool (which I
must correct myself - I used it rather than the IBM Debug Tool (for LE-based
languages) back in my prior life). Or, possibly, another debugging tool that I
think you are
familiar with. :D
I have used ADATA in the past under VSE; I created VSAM files that
It works with regu
Bob,
>> (citation from Prog-guide)
and the next sentence is what I cited.
Just so that everyone knows that VSE is an excellent OP_sys- here is
what happens:
4 // ASSGN SYSADAT,IGN
F4-0004 1A43D INVALID LOGICAL UNIT SPECIFICATION.
This is off-thread - but I like to share it.
Now watch this- b
return-code of 4 (with any reason) is
ignored.
Instead of passing control to the exit (WRITE or PROCESS) it passes
control to it for CLOSE and then terminates with RC=20.
Message from HLASM is:
** ASMA418C Unable to open ADATA file
(althru it is defines as without the exit or when I give it RC
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
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 knowle
Three sample ADATA exits are provided with the HLASM "ASMASAMP" library --
you might be able to use them as models for the ADATA exit you are writing.
They are described in Appendix I of the HLASM Programmer's Guide.
Regards... John
---
555 Bailey Ave, San Jose CA 951
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
On 8/31/2010 1:25 AM, paul schuster wrote:
Is there a limitation on how many ADATA records can be written? For
example, when I define the ADATA file as a PDSE, and the number of records
must exceed the 64K PDSE member limit, the assembly fails and I get this
message:
I'm confused - what
paul schuster wrote:
Hi:
Is there a limitation on how many ADATA records can be written? For
example, when I define the ADATA file as a PDSE, and the number of records
must exceed the 64K PDSE member limit, the assembly fails and I get this
message:
Just to clarify, the maximum number of
Why not use DSORG=PS? My ADATA below.
Regards,
John K
>usage
DISP UNIT RECFM LRECL BLKSIZE ALLOCTRK FREETRK SECONDARY DSORG
SHR 3390 VB32756 32760 5X 1350 110 CYL PS
>verify
END OF DATA SET
159 CHARACTERS PER AVERAGE VARIABLE LENGTH RECORD
On Tue, 31 Aug 2010 01:41:25 -0400, Gerhard Postpischil
wrote:
>On 8/31/2010 1:25 AM, paul schuster wrote:
>> Is there a limitation on how many ADATA records can be written? For
>> example, when I define the ADATA file as a PDSE, and the number of records
>> must excee
have you written ADATA output to a PDS or PDSE member that has more than
say
64K records?
Yes, I have a PDS ADATA dataset where I have a member with 164K+ records
and another member with 96K+ records.
Larry
-Original Message-
From: IBM Mainframe Assembler List
[mailto:assembler-l
On 8/31/2010 9:26 AM, paul schuster wrote:
Let me re-ask the question then:
have you written ADATA output to a PDS or PDSE member that has more than say
64K records?
I just found an ADATA member with 399103 records in a PDSE that is 3656
cylinders in size with RECFM=VB, LRECL=32756 and
On Tue, 31 Aug 2010 09:57:02 -0700, Edward Jaffe
wrote:
> On 8/31/2010 9:26 AM, paul schuster wrote:
>>
>> Let me re-ask the question then:
>>
>> have you written ADATA output to a PDS or PDSE member that has more than say
>> 64K records?
>
>I just found a
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!
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 ide
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 reas
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 and
I do it without anything around it.
Here is code that has nothing aside o
I am out of the office until Monday May 18th. I will not have access to email
or phone.
I have written an ADATA Filtering Program that z/XDC customers can
use to reduce ADATA library sizes from 50% to 90%. It is available
now via maintenance (Z1D-1302A).
For more information, please see our Facebook page at
facebook.com/colesoftware.
Dave Cole REPLY TO: dbc
Charles,
Would it be possible for you to contribute only the "intelligent ADATA dump"
code to CBT, without any of your firm's IP included? That seems to be a
notably generic utility that would be a wonderful contribution to the IBM
programming community.
Converting suc
[English text follows]
Bonjour,
Je suis absent.
Si nécessaire, je répondrai à votre message lors de mon retour le 18/02/13.
Vous pouvez envoyer les emails à l'équipe Mainframe Belgique :
teammfrb...@dexia.com
Votre message n'a pas été redirigé.
Bien à vous,
Marc Hardy.
Infrastructure Managemen
I can't really see what you want. ADATA is fairly dense, but it's much
easier to process than SMF data. All the record layouts have good DSECTs
available.
Just do it.
sas
On Sun, Jan 2, 2022 at 3:31 PM Farley, Peter x23353 <
0dc9d8785c29-dmarc-requ...@listserv.uga.edu> w
Sorry. Don't own one line of the code.
Charles
-Original Message-
From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] On
Behalf Of Farley, Peter x23353
Sent: Sunday, January 2, 2022 12:31 PM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: ADATA dump utility
Peter,
nice idea- but... have a look:
Here is my definition that defines what data structures I want (and of
course these are processed)
in the ADEXIT. If you write a stand-alone program, I imagine it is
pretty much the same logic.
ASMADATA PRINT=NOGEN,
Understood, and thanks for the reply.
Peter
-Original Message-
From: IBM Mainframe Assembler List On Behalf
Of Charles Mills
Sent: Sunday, January 2, 2022 7:19 PM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: ADATA dump utility [was: RE: Determining a group item]
Sorry. Don'
GA.EDU] On
Behalf Of Farley, Peter x23353
Sent: Monday, January 3, 2022 9:01 AM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: ADATA dump utility [was: RE: Determining a group item]
Understood, and thanks for the reply.
Peter
-Original Message-
From: IBM Mainframe Assembler List On
36 matches
Mail list logo
