Re: ADATA dump utility [was: RE: Determining a group item]
"My firm" (and it was only a little bit mine) no longer exists. All of its IP was acquired by a large software company often referred to with three letters, under an agreement that is 189 pages long and was crafted by not one, not two, but three! legal teams. (Our firm, their inside team, their outside firm.) I may actually be in violation of the NDA for saying what I just said. Really. Trust me: it was all worth it. I LOVED the work, and I did not mind the transaction. Charles -Original Message- From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.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 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'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 [was: RE: Determining a group item] 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 such code to other languages (MetalC, HLASM, python, etc.) would then be an exercise for the rest of the community to take up. Peter -Original Message- From: IBM Mainframe Assembler List On Behalf Of Charles Mills Sent: Saturday, January 1, 2022 7:56 PM To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Subject: Re: Determining a group item I started by writing an "intelligent dump" program to display the contents of an ADATA file, and then refined that until it was producing the desired output (with the dump available as a debugging option in the finished program). Charles -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.
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 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'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 [was: RE: Determining a group item] 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 such code to other languages (MetalC, HLASM, python, etc.) would then be an exercise for the rest of the community to take up. Peter -Original Message- From: IBM Mainframe Assembler List On Behalf Of Charles Mills Sent: Saturday, January 1, 2022 7:56 PM To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Subject: Re: Determining a group item I started by writing an "intelligent dump" program to display the contents of an ADATA file, and then refined that until it was producing the desired output (with the dump available as a debugging option in the finished program). Charles -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.
Re: ADATA dump utility [was: RE: Determining a group item]
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, * AID=NO, * AOPT=NO, Options File Information * COMPUNIT=NO, Compilation Unit Start/End * DCDS=YES, DC/DS DSECT (Type X'0034') * DCX=YES, Duplication Extension DSECT(Type X'0035') * ESD=YES, ESD DSECT (Type X'0020') * JID=YES, Job Identification DSECT (Type X'') * MACH=YES, Machine Instruction DSECT (Type X'0036') * MXREF=NO, Macro and Copy Code Source Summary X'0060'* MXREFX=NO, Macro/Copy XReference DSECT (Type X'0062')* OPT=NO, Options DSECT (Type X'0010') * OUTPUT=NO, Output File DSECT (Type X'000A') * RLD=NO, RLD DSECT (Type X'0040') * RXREF=NO, Register XREFe DSECT (Type X'0045') * SOURCE=YES, Source Analysis DSECT (Type X'0030') * SRCERR=YES, Source Error DSECT (Type X'0032') * STATS=YES, Statistics DSECT (Type X'0090') * SYM=YES, Symbol DSECT (Type X'0042') * USER=NO, User Data Record DSECT (Type X'0070') * USING=YES, Using Map DSECT (Type X'0080') * XREF=NO Symbol XREF DSECT (Type X'0044') for some (i.e.SRCERR) I only take the sheer presence to abort collection of data (since a program with error during compile can not be debugged). Others there is a more elaborated routine (i.e. DCDS) I have no problem publishing initial or the handling routines of specific record- but there are in no way a complete program for any purpose. They will be snippets of a working program. They can be taken as starting point for you own routine (i.e. the parser that Charles suggested). The program gets control from the HLASM for this OPEN,CLOSE,WRITE, PROCESS I have no clue (would have to RTFM) what PROCESS is- I handle it with this message: 'we never process any records(wrong call)' The others are obvious. Almost all processing is done in the WRITE part- Once the record-type is identified it is a simple transformation of the incoming structure into what you need on the outside. My program to extract all data needed for debugging which is -the compile listing as the human sees it (=for stepping thru the code) -defined structures (DS and DC/DSECT) (=for showing structures with names+content) The information I needed was sometimes spread over multiple record-types, but no major hurdles. The ADEXIT is little under 500 cards long Hope this helps Martin
Re: ADATA dump utility [was: RE: Determining a group item]
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 [was: RE: Determining a group item] 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 such code to other languages (MetalC, HLASM, python, etc.) would then be an exercise for the rest of the community to take up. Peter -Original Message- From: IBM Mainframe Assembler List On Behalf Of Charles Mills Sent: Saturday, January 1, 2022 7:56 PM To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Subject: Re: Determining a group item I started by writing an "intelligent dump" program to display the contents of an ADATA file, and then refined that until it was producing the desired output (with the dump available as a debugging option in the finished program). Charles -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.
Re: ADATA dump utility [was: RE: Determining a group item]
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> wrote: > 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 such code to other languages (MetalC, HLASM, python, etc.) > would then be an exercise for the rest of the community to take up. > > Peter > >
ADATA dump utility [was: RE: Determining a group item]
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 such code to other languages (MetalC, HLASM, python, etc.) would then be an exercise for the rest of the community to take up. Peter -Original Message- From: IBM Mainframe Assembler List On Behalf Of Charles Mills Sent: Saturday, January 1, 2022 7:56 PM To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Subject: Re: Determining a group item I started by writing an "intelligent dump" program to display the contents of an ADATA file, and then refined that until it was producing the desired output (with the dump available as a debugging option in the finished program). Charles -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.
Automatic reply: Why ADATA is so big ? (not any more...)
[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 Management Engineering - Mainframe Belgium Dexia Technology Services Belgium -- [English text] Hello, I'm out of the office. If needed, I'll respond to your mail when I'll return on 18/02/13. You can send emails to team Mainframe Belgium: teammfrb...@dexia.com Your mail was not forwarded. Regards, Marc Hardy. Infrastructure Management Engineering - Mainframe Belgium Dexia Technology Services Belgium - Dexia disclaimer: http://www.dexia.com/maildisclaimer.htm -
ADATA
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 discuss ADATA or other topics. Sharuff Sharuff Morsa - IBM Hursley Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
Re: ADATA
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 not get generated, that would be a help. Also, many programs are constructed from numerous separately assembled elements. Generally, in such cases, there will be a control blocks definition section that is similar across all of the assemblies. It would be useful to provide a way to turn off (and later turn back on) the generation of all ADATA for selected ranges of source statements. Further, this mechanism should be nestable so that it can be safely invoked in broadly used macros. In my own case, z/XDC is built from nearly 200 separate assemblies. Each has a cblocks section that provides to its particular assembly selected cblock maps from a much larger product-wide set. Then I have one DOC assembly (similar in concept to JES2's HASPDOC) that does nothing but generate assemblies of the entire set of mapping macros used by z/XDC. If I could turn off ADATA generation across just the cblocks sections of all of my assemblies (except the DOC assembly), that would save tens of thousands of tracks of DASD space. Finally, since a lot of ADATA consists of nulls and particularly blank strings, even something so simple minded as a run length encoding compression would save significant space (PARM controlled, of course). WRT SHARE, I am not generally involved in SHARE, and in particular, I will not be attending the SFO SHARE. So I will leave it to others who (hopefully) think these are good ideas to create suitable SHARE requirements. Absent that, I will develop my own custom solutions. Thank you for your consideration of these ideas. Dave Cole REPLY TO: dbc...@colesoft.com ColeSoft Marketing WEB PAGE: http://www.colesoft.com 736 Fox Hollow RoadVOICE:540-456-8536 Afton, VA 22920FAX: 540-456-6658 At 11/7/2012 02:44 AM, Sharuff Morsa3 wrote: 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 create them. Go read http://www-01.ibm.com/support/docview.wss?uid=swg21577670 (and the usual caveats - no promises - but I do need RFEs in order to pursue user requested enhancements) Sharuff Sharuff Morsa - IBM Hursley Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU At 11/7/2012 04:47 AM, Sharuff Morsa3 wrote: 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 discuss ADATA or other topics. Sharuff Sharuff Morsa - IBM Hursley Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
Re: PDF vs. Bookie (was: ADATA Exit)
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 aside of it. Look at this: http://www.pi-sysprog.de/prod/ftpds/sampds.txt JCL-sample, ready to use without any extra processing required at all Copy the HTML; edit out the (minimal) markup and go. That would be required, if the code is part of more HTML. 2) It may depend on your PDF viewer. Some are worse than others (not to call the others better). Many trash the indention. Is there a trick to avoid trashing the indention (I use acro and foxit) or another PDF-viewer that doesn't? -- Martin Pi_cap_CPU - all you ever need around MWLC/SCRT/CMT in z/VSE more at http://www.picapcpu.de
Automatic reply: PDF vs. Bookie (was: ADATA Exit)
I am out of the office until Monday May 18th. I will not have access to email or phone.
ADATA Exit / now:niceing things up
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? -- Martin Pi_cap_CPU - all you ever need around MWLC/SCRT/CMT in z/VSE more at http://www.picapcpu.de
Re: ADATA Exit
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 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 of 0) -- Martin Pi_cap_CPU - all you ever need around MWLC/SCRT/CMT in z/VSE more at http://www.picapcpu.de
Re: ADATA Exit
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 quirk that there is no way to stop the ASAM90 from opening SYSADAT file. -- Martin Pi_cap_CPU - all you ever need around MWLC/SCRT/CMT in z/VSE more at http://www.picapcpu.de
Re: ADATA exit
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 ADATA is specified, even though the relevant OPEN is bypassed if the OPEN exit set return code 4, so this check will always fail in that case. It's not immediately obvious to me why this code was added in the first place. Martin, please can you report it through your usual IBM service channel? Some of the HLASM team follow this mailing list so it shouldn't be a surprise to them. From a quick glance, I cannot see any similar problem in the code for other platforms, so I suspect it is VSE-specific. As for question 2, my VSE knowledge is so rusty that it's actually DOS/VS knowledge. The code tests DTFFLG1 for DTFIGNOP to test whether it's assigned IGN, but I don't know to assign something other than a logical unit as IGN. Perhaps the developer copied code for other files without noticing this limitation. However, I hope that this question should become irrelevant if you can get a fix for the first one. Jonathan Scott IBM Hursley, UK
Re: ADATA exit
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 knowledge. The code tests DTFFLG1 for DTFIGNOP to test whether it's assigned IGN, but I don't know to assign something other than a logical unit as IGN. Perhaps the developer copied code for other files without noticing this limitation. The developer ment what I did- use the SYSnnn that can be designated for SYSADAT (by doing so and so) and assign it IGN. The flags signal if the SYSnumber is assigned ignore. However, I hope that this question should become irrelevant if you can get a fix for the first one. Looks like this is the case. Why would anyone have a DLBL and an EXTENT-card just to use an ASSIGN to IGN it. -- Martin Pi_cap_CPU - all you ever need around MWLC/SCRT/CMT in z/VSE more at http://www.picapcpu.de
Re: ADATA Exit
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 code is now) They are described in Appendix I of the HLASM Programmer's Guide. I have seen that and also inspected the lengthy sample printed in the PDF-manual. I decided to write from scratch: the result looks promising. All that is left is to store the resulting data (and then to further process it) 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. -- Martin Pi_cap_CPU - all you ever need around MWLC/SCRT/CMT in z/VSE more at http://www.picapcpu.de
PDF vs. Bookie (was: ADATA Exit)
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 reason here to regret IBM's SoD to abandon Bookie in favor of PDF. 1a) I did this many years ago with, IIRC, the very same example in Bookie format. Wasn't too bad. Strip the gutters and filter out the page headers. 1b) I like to distribute README files containing code examples as HTML with the code between PRE and /PRE. Copy the HTML; edit out the (minimal) markup and go. 2) It may depend on your PDF viewer. Some are worse than others (not to call the others better). Many trash the indention. Grrr/ gil
ADATA Exit
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 convincing the Assembler not to attempt open of the ADATA file - any op-sys. Question 2: I am on VSE and I do not understand this sentence (in Programmers Guide- chapter on ADATA exit processing): - Suppress the associated data output by doing this: -z/OS (okay I got this) -CMS Issue (okay I do understand this as well) -z/VSE Assign SYSADAT to IGN. The last sentence is something I have problems doing. -- Martin Pi_cap_CPU - all you ever need around MWLC/SCRT/CMT in z/VSE more at http://www.picapcpu.de
Automatic reply: ADATA Exit
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!
Re: ADATA Exit
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 ADATA file Question 1: anyone succeeded in convincing the Assembler not to attempt open of the ADATA file - any op-sys. Yes. I have used the sample exit for converting HLASM V5+ to HLASM V4 to use with the long-neglected Program Understanding Tool, under z/OS. Question 2: I am on VSE and I do not understand this sentence (in Programmers Guide- chapter on ADATA exit processing): - Suppress the associated data output by doing this: -z/OS (okay I got this) -CMS Issue (okay I do understand this as well) -z/VSE Assign SYSADAT to IGN. The last sentence is something I have problems doing. I assume you tried // ASSGN SYSADAT,IGN? Judging from the Programmer's Guide, this is supported. But I agree, that seems strange; I've never known of a SYSADAT logical unit. There are only three hits in the z/VSE documentation for SYSADAT: in messages and codes for the ASMA418C, and two in the area of the C DSECT conversion tool. These all reference DLBL. You could try DLBLing a dummy 1-track SAM-ESDS file. I have used ADATA in the past under VSE; I created VSAM files that were then fed into the appropriate utility for use in the IBM Debug Tool (since, despite my begging over the years, Dave Cole still hasn't ported z/XDC to z/VSE. (Yes, this is a joke. There are very good economic reasons why Dave has not done it. :) )) -- M. Ray Mullins Roseville, CA, USA http://www.catherdersoftware.com/ German is essentially a form of assembly language consisting entirely of far calls heavily accented with throaty guttural sounds. ---ilvi French is essentially German with messed-up pronunciation and spelling. --Robert B Wilson English is essentially French converted to 7-bit ASCII. ---Christophe Pierret [for Alain LaBonté]
Re: ADATA Exit
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 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
Re: ADATA Exit
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 worked except for very old COBOL-programs that had logic build into them to honor it). It was worth a shot. :) You could try DLBLing a dummy 1-track SAM-ESDS file. As long as I do not specify an exit it does produce data. Now that sounds like a bug. I vote for firing up the HLASM 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 regular SAM as well. I used VSAM because I didn't need to deal with EXTENTs. :) -- M. Ray Mullins Roseville, CA, USA http://www.catherdersoftware.com/ German is essentially a form of assembly language consisting entirely of far calls heavily accented with throaty guttural sounds. ---ilvi French is essentially German with messed-up pronunciation and spelling. --Robert B Wilson English is essentially French converted to 7-bit ASCII. ---Christophe Pierret [for Alain LaBonté]
ADATA size limitation ?
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,adatadsn,ADATA IEA995I SYMPTOM DUMP OUTPUT 285 SYSTEM COMPLETION CODE=002 REASON CODE=00AC TIME=23.56.48 SEQ=15258 CPU= ASID=0167 PSW AT TIME OF ERROR 075C1000 80DC0B56 ILC 2 INTC 0D ACTIVE LOAD MODULE ADDRESS=00DBF000 OFFSET=1B56 NAME=IFG0199B When I then define the ADATA file as a PDS, asssembly works ok, but ADATA file always shows 64403 records, and the last many (not sure how many, probably several hundred) records are all like this: ** * * * I/O error detected, I/O terminated * * * ** Is there some way around this limiitation? Probably an ADATA exit, but which records should be filtered? I am trying to create an ADATA file for use by the XDC MAP and DMAP commands. This is HLASM RELEASE at PTF UK57150. Or is this already fixed at a higher maintenance level for HLASM? Thank you. Paul
