Do you have a compile listing of the production program?
No. In production compile job, compressed lsiting is populated in a temporary library, but the temp library is not copied to permanent lib down the line.
Quote:
Did you get the source from a production library?
Yes.
Quote:
Have you checked compile and link time, like Robert suggested?
In the loadmodule, the time is 24 June 1998. But in panvalet for the same module i can see two timestamp -
LMAINT LACCESS
-------- --------
06/24/98 04/29/03
I am not sure of the significance of LACCESS.
Quote:
Did you find an answer for Dick's question about where the SYSOUT is actually routed?
I haven't talked to support for this, as they are not very good people to talk to, if you have technical question which a developer should himself know. But i have talked to other seniors and they say, it should direct to spool itself.
And I was looking for logic to reset the internal return code in the program. Before there logic there is a display, which is not getting displayed in production, but when i run the same load module in test, i can see the display.
Joined: 09 Mar 2011 Posts: 7309 Location: Inside the Matrix
Remember you have the EXHIBIT NAMED. I think you can track it to that.
Are you saying you didn't see the SYNCSORT either in production?
Check out what the STAN stuff means. I think you'll find it squirelled away somewhere. Talk to "production support" or whoever it is responsible for production JCL.
Joined: 06 Jun 2008 Posts: 8696 Location: Dubuque, Iowa, USA
IIRC, that display is generated by OS/VS COBOL -- possibly as a result of a compiler option or EXHIBIT? -- to indicate variable values at a particular line of the program.