IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

SYSADATA interpretation


IBM Mainframe Forums -> PL/I & Assembler
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
ganasrinivasan

New User


Joined: 06 Nov 2006
Posts: 27
Location: Montreal

PostPosted: Fri Jun 05, 2015 11:45 am
Reply with quote

Hi,

I am trying to interpret SYSADATA output from assembler compilation.

Can someone please help/direct me to right place? I had looked in to HLASM programming guide, but the layout in SYSADATA is not matching with guide.

I am missing something? Is there any easy way to interpret. I am trying to create some tools using this.

Thanks in advance!
Back to top
View user's profile Send private message
enrico-sorichetti

Superior Member


Joined: 14 Mar 2007
Posts: 10872
Location: italy

PostPosted: Fri Jun 05, 2015 12:00 pm
Reply with quote

hard to believe ( unless You are looking at a manual for a different hlasm version )

anyway You can find the layout looking at
Code:
HLA.SASMMAC1(ASMADATA)

substitute HLA with whatever qualifier is used in Your system
Back to top
View user's profile Send private message
Bill Woodger

Moderator Emeritus


Joined: 09 Mar 2011
Posts: 7309
Location: Inside the Matrix

PostPosted: Fri Jun 05, 2015 12:02 pm
Reply with quote

I've never looked, but I don't see how the SYSADATA from an Assembler program would differ from how it is documented in the Programmer's Guide. Ensure that you have the manual for your release of the Assembler, but I doubt there has been any change in the general format of the SYSADATA anyway.

It''l be "easy" to read once you know how, and not so until you do.
Back to top
View user's profile Send private message
steve-myers

Active Member


Joined: 30 Nov 2013
Posts: 917
Location: The Universe

PostPosted: Fri Jun 05, 2015 5:34 pm
Reply with quote

As Mr. Sorrichetti says, use the macro in SASMAC1.

I have a program that scans SYSADATA. From time to time IBM alters the contents of SYSADATA; the update would break my program. I think the update from V1R4 to V1R5 broke my program, but V1R5 to V1R6 was OK. Unfortunately, it's been a long time since I ran it and I can't find the source.
Back to top
View user's profile Send private message
steve-myers

Active Member


Joined: 30 Nov 2013
Posts: 917
Location: The Universe

PostPosted: Mon Jun 08, 2015 7:47 pm
Reply with quote

I am recreating the program from 15 or 20 years ago that disappeared. This program uses the SYM and XREF records. I found two problems in XREF on the way.

Comment -
Code:
ADXREF_SYM_OFF      DS    FL4        Offset of Symbol/Literal name
ADXREF_SYM_LEN      DS    FL4        Offset of Symbol/Literal name
The comment on ADXREF_SYM_LEN is obviously wrong. It's actually a length, as implied by the symbol name.

Value -
Code:
ADXREF_REFS_OFF     DS    FL4        Offset to first reference
In data with variable length records an offset usually means it includes the RDW for the record. This offset does not include the RDW.

In the program I used ADXREF_SYM_NAME rather than ADXREF_SYM_OFF so I can't comment on its accuracy.

I also looked at the record descriptions in the manual. Like you, I found them to be fairly useless.
Back to top
View user's profile Send private message
ganasrinivasan

New User


Joined: 06 Nov 2006
Posts: 27
Location: Montreal

PostPosted: Thu Jun 25, 2015 12:57 pm
Reply with quote

Hi All,

Now i am able to interpret the details in manual to SYSADATA file (Initially i was referring to a wrong version).

Thanks for your inputs. Additionally i would like to know your thoughts on using compiler listing or sysadata to create some tools (like cross reference, some specific source parser tool etc).

Note:
I know that there is a tool kit which provides the cross reference etc.. but thought of creating a tool which is very specific to our need.
Back to top
View user's profile Send private message
ganasrinivasan

New User


Joined: 06 Nov 2006
Posts: 27
Location: Montreal

PostPosted: Thu Jun 25, 2015 12:59 pm
Reply with quote

To be more clear, I would like to know which one (compiler listing or SYSADATA) will be more appropriate to create some cross reference tools.
Back to top
View user's profile Send private message
Nic Clouston

Global Moderator


Joined: 10 May 2007
Posts: 2455
Location: Hampshire, UK

PostPosted: Thu Jun 25, 2015 3:17 pm
Reply with quote

That is a different subject and, as you said this would be tightly tailored to your site and it depends on what you want your cross-reference to look like and what data it is to hold then you should fo the analysis and see which dataset is appropriate to your needs.
Back to top
View user's profile Send private message
steve-myers

Active Member


Joined: 30 Nov 2013
Posts: 917
Location: The Universe

PostPosted: Thu Jun 25, 2015 9:22 pm
Reply with quote

The tool I mentioned from long ago was a cross reference tool. It was tailored for JES2, but it can be considered a general purpose tool.

A typical output line is

$AFTOFF HASPCNVT *HASPCOMM HASPNUC

Symbol $AFTOFF is used in the listed modules, and modified in HASPCOMM.

I'm thinking about sending the reworked tool to CBT, but its doc and packaging needs more work before I can do that.

Is this something like you're think about?
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> PL/I & Assembler

 


Similar Topics
Topic Forum Replies
No new posts SYSADATA - COBOL - Structure displace... COBOL Programming 3
No new posts Zoned Decimal DFSORT - interpretation DFSORT/ICETOOL 2
No new posts CPU TIME interpretation in joblogs JCL & VSAM 1
Search our Forums:

Back to Top