View previous topic :: View next topic
|
Author |
Message |
pramodg
New User
Joined: 04 Sep 2012 Posts: 5 Location: India
|
|
|
|
I am working on a COBOL performance optimization assignment. The strobe report points to a offset in a COBOL program. At my earlier company I was used to locate all the procedure division offsets near the end of the compile listing. But in current case I am not able to locate where they are listed in the compile listing. The program seems to be compiled with OFFSET (YES) and LIST(YES) options. I see this message on the first page of the compile listing -
IGYOS4022-W The "OFFSET" option was discarded due to option conflict resolution. The "L option from "PROCESS/CBL"IST"
statement took precedence.
Attached the program...........
Attachment removed. |
|
Back to top |
|
|
pramodg
New User
Joined: 04 Sep 2012 Posts: 5 Location: India
|
|
|
|
[quote="pramodg"]I am working on a COBOL performance optimization assignment. The strobe report points to a offset in a COBOL program. At my earlier company I was used to locate all the procedure division offsets near the end of the compile listing. But in current case I am not able to locate where they are listed in the compile listing. The program seems to be compiled with OFFSET (YES) and LIST(YES) options. I see this message on the first page of the compile listing -
IGYOS4022-W The "OFFSET" option was discarded due to option conflict resolution. The "L option from "PROCESS/CBL"IST"
statement took precedence.
Attached the program...
I am looking for the offset - 00144E. |
|
Back to top |
|
|
Bill Woodger
Moderator Emeritus
Joined: 09 Mar 2011 Posts: 7309 Location: Inside the Matrix
|
|
|
|
Did you try a FIND on the compile listing? You have option LIST, so you have the detail of everything there is... |
|
Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006 Posts: 6966 Location: porcelain throne
|
|
|
|
maybe, if you recompile with the proper options,
you can get your offset. |
|
Back to top |
|
|
pramodg
New User
Joined: 04 Sep 2012 Posts: 5 Location: India
|
|
|
|
Thanks Bil & dick
Unfortunately I am not able to locate the complete listing. May be I do not know where to look for. I scanned the entire compile listing file.
As there are most of such cases it will be difficult to get them to recompile all such programs.
Before complaining, just wanted to re-confirm that there is no way we can locate the offset with the compile listing provided. The module map shows offset 0 to 6348 for the concerned program. So I assume the offset 144E lies within its range. Let me know my understaning is not correct.
Code: |
SECTION CLASS ------- SOURCE --------
OFFSET OFFSET NAME TYPE LENGTH DDNAME SEQ MEMBER
0 MBM227D CSECT 6348 SYSLIN 01 **NULL** |
Your post has been Code'd and the ridiculously small text size removed. |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8697 Location: Dubuque, Iowa, USA
|
|
|
|
Unless you recompile this program, preferably with VBREF,NOOFFSET,LIST options, you cannot determine the statement having the problem. The compile listing has no offset information included. |
|
Back to top |
|
|
pramodg
New User
Joined: 04 Sep 2012 Posts: 5 Location: India
|
|
|
|
Thanks for the reply Robert. Seems I have no option but to go back to the application owner and ask for recompilation. |
|
Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006 Posts: 6966 Location: porcelain throne
|
|
|
|
do you have a resource management tool (changeman/endevor/panvalet?)
or does everybody just do what they want?
i do not understand an organization
that does not require adequate procedures to be followed
when generating production code.
how does anyone debug a problem
when there is a S0Cwhatever
and an offset is provided? |
|
Back to top |
|
|
Bill Woodger
Moderator Emeritus
Joined: 09 Mar 2011 Posts: 7309 Location: Inside the Matrix
|
|
|
|
Something is unusual. LIST requires NOOFFSET. OFFSET has been discarded. LIST is specified. Yet no LIST output.
The diagnostic message has some "garbling" in it.
If everything is compiled this way, you have no indication of any offsets in your compile listings, either through LIST or OFFSET.
It is unusual to specify everything as CBL cards. Usually you take the installation defaults plus any necessary overrides. Something is messed-up. |
|
Back to top |
|
|
|