Joined: 12 Jan 2004 Posts: 240 Topics: 48 Location: Maryland
Posted: Fri Jan 30, 2004 2:07 pm Post subject: Assembler LIST
Hi ,
I had read some place that this for a Cobol Program is created only if the CBL LIST option is used in the Program ..which can later be used for Abend analysis.
Is my understanding wrong because I am seeing that at our end this LIST is getting created even without specifying it as an option in the program.
Is it that a LIST always gets created by Default and giving CBL LIST as an Option gives some detailed listing of a different kind ??? If yes, how are these two different.
Pls. clarify.
Joined: 26 Nov 2002 Posts: 12369 Topics: 75 Location: San Jose
Posted: Fri Jan 30, 2004 3:39 pm Post subject:
Vini,
Look at the sysprint of the job when you compile a cobol program. Typically it would like this as follows. the first line is the cobol compiler version and then followed by the complier options. The listings can be obtained with options like LIST, MAP, SOURCE. However there are few differences between the options.
Joined: 12 Jan 2004 Posts: 240 Topics: 48 Location: Maryland
Posted: Fri Jan 30, 2004 4:06 pm Post subject:
kolusu,
Is there a difference between having the LIST as a Compiler Option in JCL and including the line 'CBL LIST' before the Identification Division ..or are they one and same things ?
I did not find any SYSPRINT or reference to LIST, MAP or SOURCE in the Compile JCL ..part of the reason could be because this Compile/Build Job gets trigerred by the SCLM itself when we select 'Build Archdef' (which is for compile).
Joined: 26 Nov 2002 Posts: 12369 Topics: 75 Location: San Jose
Posted: Mon Feb 02, 2004 6:12 am Post subject:
Vini,
Any compiler options specified before the ID division of the program will override the compiler options provided in the JCL. So if you provide CBL LIST in the program and the JCl also had the compiler option LIST then there is no difference.
Quote:
I did not find any SYSPRINT or reference to LIST, MAP or SOURCE in the Compile JCL ..part of the reason could be because this Compile/Build Job gets trigerred by the SCLM itself when we select 'Build Archdef' (which is for compile).
How do you check for your compiler errors when you compile a program? You must be looking at the compiler listing somewhere. Usually the sysprint will have the compiler output listing.
Joined: 12 Jan 2004 Posts: 240 Topics: 48 Location: Maryland
Posted: Mon Feb 02, 2004 5:02 pm Post subject:
kolusu,
Yes we do see the Compiler listing in the BLDLIST (part of JCL output like sysprint )..and I finally did find the MAP and SOURCE options in there like you mentioned.
Earlier I was looking for them in the JCL which apparently doesnt have any such options ..but it must be picking up from something specified in the JCL..I see lots of references to CLISTs but not to Procs (surprisingly)..and apart from that IKJEFT01 and IEBGENER are being executed . Dont have much idea about CLISTS and hence their role here .. I wanted to paste the JCL here ..but it was real long !
SCLM has always seemed elusive and obscure to me..does plenty in background but then it takes care of version control.
Joined: 26 Nov 2002 Posts: 12369 Topics: 75 Location: San Jose
Posted: Tue Feb 03, 2004 6:51 am Post subject:
vini,
There are some options which are default to the complier. So even if you don't override them(via JCL or Program), then the program will be complied with the default value. Take a look at the link provided above and see the default value of each compiler option.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
FAQ
Search
Quick Manuals
Register
Profile
Log in to check your private messages
Log in
but then it takes care of version control.