Oh, well, it's likely REXX either way for me. Can't take more'n about a dozen lines. It's kinda to bad that neither sort product can take variable action depending on the data in any given record. But, I guess that'd make them programming languages :)
> -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On > Behalf Of Edward Jaffe > Sent: Wednesday, September 10, 2008 5:02 PM > To: [email protected] > Subject: Stable Interfaces (Was: SMP/E GIM44402W) > > Gibney, Dave wrote: > > I have sort pulling ADATA type x'0062' records, but it looks like I > > need to move to REXX to deal with the variable length macro names in the > > ADATA records. I also have considered parsing the assembler listing, but > > that would be prone to failure as they change HLASM. I would hope ADATA > > to remain more stable. > > > > Funny you say that. IBM changed the ADATA format significantly in HLASM > 1.5. There is an IBM-supplied exit routine that can generate the old > HLASM 1.4 ADATA for programs that can't handle the new format. That exit > didn't work well for a long time. But, now it's been fixed. > > -- > Edward E Jaffe > Phoenix Software International, Inc > 5200 W Century Blvd, Suite 800 > Los Angeles, CA 90045 > 310-338-0400 x318 > [EMAIL PROTECTED] > http://www.phoenixsoftware.com/ > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO > Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
