Re: Which H-specs CTL-OPT do you use?

Hello Daniel,

Am 10.08.2025 um 17:20 schrieb Daniel Gross <daniel@xxxxxxxx>:

Usually, for production, I change the COPYRIGHT line to reflect the last changed date of the source member.

That's not really necessary as the compiler binds the last source change date into the module. You can see it e.g. with the BOUND_MODULE_INFO view - or with DSPPGM.

Good to know. Thanks for the hint!

Another reason I change this value is that most of my projects are kept in cvs, or (increasingly) git repositories.

OPTIMIZE(*FULL) is a mixed bag - on one side, you really speed things up - on the other side, those program objects are nearly impossible to debug.

I'm aware. On my 150, I want to get all the speed I can get. :-)

On the other hand, I have never accumulated enough patience to learn how to use the interactive debugger. So far, I got along surprisingly well without it.

From experience, development of code for me has three stages within the edit-compile-run loop:
- Fix errors the compiler barfs about — compiler logs help
- Fix crashes during program start or usage — debug output helps somewhat
- Fix unexpected program behavior during usage — careful studying the code helps but is rather tedious

It's very important that most of my programs are considerably small, eventough they're mostly self-contained.

We only do OPTIMIZE(*FULL) for very good tested programs where speed is absolutely crucial.

Comprehensible.

Just be careful with it.

I'm not. ;-) But I know that optimization and debuggers aren't friends. This isn't limited to IBM i.

:wq! PoC