There are now very many languages and tools available to iSeries developers. Some run in PASE, some under Linux, and of course many native OS/ 400 compilers and languages to choose from.

When you have to work on a program developed by another developer (who may no longer even work at the same company), how can you tell which compiler options she/ he used when they compiled that program? And, what about that program you developed two years ago? What compile options did you use? How can you ensure that the correct compile time options will always be used whenever your applications are recompiled and moved into production?

This session will describe specific tools and methods you can use to allow you to "embed" compile time options directly into the source code for each program, where they will never get "lost" and will always be available when needed (the next time you need to recompile that program). Best of all, this session describes how this approach can be implemented so that it will even work with WDSCi!

By the end of this session, attendees will be able to:
1. Understand compile time options.
2. Learn how and why to capture these options.
3. Learn how to automate processing the options.