Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
get compiler options from a modul
- Thread starter hero69
- Start date
Hi H,
The link below provides pgm downloads for various system needs. I know there are pgms that provide the info you're looking for. Can't remember the pgm name offhand, but try a search on "signature bytes" along w/the more obvious args. Don't know if anyone has updated the process for eCOBOL.
If you're forced to write it yourself take a look at the eCOBOL Pgmr Guide. It should have a discussion of signature bytes.
Good luck.
Regards, Jack.
"A problem well stated is a problem half solved" -- Charles F. Kettering
The link below provides pgm downloads for various system needs. I know there are pgms that provide the info you're looking for. Can't remember the pgm name offhand, but try a search on "signature bytes" along w/the more obvious args. Don't know if anyone has updated the process for eCOBOL.
If you're forced to write it yourself take a look at the eCOBOL Pgmr Guide. It should have a discussion of signature bytes.
Good luck.
Regards, Jack.
"A problem well stated is a problem half solved" -- Charles F. Kettering
- Thread starter
- #3
Thanks Jack
that's a good Tipp! And I had tested the cobanalyser. But he don't write all compile information to sysprint.
A other Problem was, I had a program in VS Cobol II and run the cobanal over this program and got so the compilation information. That's work fine. Then I compiled the same program (same name!) with Enterprise Cobol V3.3 and run the cobanal again! But I got the wrong compilation options! What I got was the options of VS Cobol II program!
Regards,
JP
that's a good Tipp! And I had tested the cobanalyser. But he don't write all compile information to sysprint.
A other Problem was, I had a program in VS Cobol II and run the cobanal over this program and got so the compilation information. That's work fine. Then I compiled the same program (same name!) with Enterprise Cobol V3.3 and run the cobanal again! But I got the wrong compilation options! What I got was the options of VS Cobol II program!
Regards,
JP
Roland updates COBANAL medium-often (at least whenever there is a new release of IBM's COBOL). You might want to verify that you have the latest version.
Also, you may want to check your JCL to make certain that you are looking at the NEW object code (to analyze). I have never heard of it confusing VS COBOL II with Enterprise COBOL.
Finally, if you want an "officially supported" *AND* paid for product to do all of this (and more), you may want to look at the EDGE Portfolio Analyzer. See:
This would be particularly useful for shops with BOTH COBOL and PL/I
Bill Klein
Also, you may want to check your JCL to make certain that you are looking at the NEW object code (to analyze). I have never heard of it confusing VS COBOL II with Enterprise COBOL.
Finally, if you want an "officially supported" *AND* paid for product to do all of this (and more), you may want to look at the EDGE Portfolio Analyzer. See:
This would be particularly useful for shops with BOTH COBOL and PL/I
Bill Klein
- Thread starter
- #5
I had the latest version, this version includes Enterprise Cobol V3.
It was always the newest object code to analyze! I had checked this!
I wrote this only with my experiences about this tool. Maybe there is some one how need this information.
I known about the EDGE Portfolio Analyzer, thanks
It was always the newest object code to analyze! I had checked this!
I wrote this only with my experiences about this tool. Maybe there is some one how need this information.
I known about the EDGE Portfolio Analyzer, thanks
- Status
Similar threads
