where to find compile listing of the production program soc7

student_mf · New User Joined: 15 Jun 2007 Posts: 23 Location: pune

hi

program abended with a soc7 in batch and i can see only SAR pages i got the offset from there but where to to find complie listion for that job or program i dont know can you please help me out here.

thanks

Robert Sample · Posted: Fri Jul 17, 2009 8:38 pm

Some sites specify to save the production compile listing; others do not. You will need to find out from someone at your site whether or not the compile listings are saved and if so, where.

Anuj Dhawan · Posted: Mon Jul 20, 2009 6:34 pm

Other alternative, which I use at my shop -- take the component in some package (we use change man as version control tool) from "base line" and just stage/compile it without any change. Now go through the compile-listing which are just generated...

Hope this helps.

Bill O'Boyle · Posted: Mon Jul 20, 2009 7:04 pm

It would probably be best if you specify the compile options LIST,NOOFFSET to expand the Assembler code generated by the compiler.

Place the following on line one, above the ENVIRONMENT DIVISION -

CBL LIST,NOOFFSET

student_mf · New User Joined: 15 Jun 2007 Posts: 23 Location: pune

Robert Sample · Posted: Thu Jul 23, 2009 7:58 pm

You can recompile the program into a test library and save the compile output to use in your analysis (use LIST,NOOFFSET options in your compile so you get the full pseudo-assembler listing). Assuming the compiler hasn't been changed since the production version was compiled, the offset for the S0C7 should not have changed so you can then identify the statement and variable causing the problem.

Anuj Dhawan · Posted: Fri Jul 24, 2009 6:15 pm

Even if you not have any version control tool (though in 21st century it's hard to believe for me) you must be using some means to compile your source (COBOL) program, use that method and recompile the program into a test library as Robert has said.

PS. With the information which has been provided to Forum that's maximum, I believe, which can be suggested.

mmwife · Super Moderator Joined: 30 May 2003 Posts: 1592

It sounds like you'll have to use Robert's suggestion to get a compile listing of the prod code to help you debug the Abend.

If you do make, sure that your compile JCL uses the same compiler options as the prod compile JCL, because some compiler options may generate more or less code than others and that will change the pgm offsets.

However, the LIST,NOOFF option will not change the pgm code generated.

t5590ag · Posted: Tue Sep 08, 2009 12:50 pm

Hi, I was just going through the post and i tried using this- List,nooffset-

Robert Sample · Posted: Tue Sep 08, 2009 3:07 pm

EJECT and CBL are compiler directives, they are not COBOL keywords. The SOURCE-COMPUTER statement has been commented out, so it has no COBOL keywords. As far as the ENVIRONMENT DIVISION and CONFIGURATION SECTION, whether or not they will be highlighted depends probably upon what is doing the highlighting. Since you didn't mention that, we cannot provide any real answer to you.

t5590ag · Posted: Tue Sep 08, 2009 3:58 pm

Am using HI COB to highlight the cobol keywords, can we highlight compiler directives as well ?

Robert Sample · Posted: Tue Sep 08, 2009 4:46 pm

My ISPF highlights ENVIRONMENT DIVISION as well as CONFIGURATION SECTION but does nothing for the CBL directive. I do not see any option to highlight the compiler directives.