How can we handle multiple DB environments with SQL which likes hardcode libraries or just uses the *curlib. In other words, testing and production, using the same SQL program. In the past we have been able to use *libl without anything in the programs pointing to a specific file.
I would use overrides in a CL overriding the file at the *JOB level. In my testing, it appears to work just fine.
MORE INFORMATION ON THIS TOPIC
The Best Web Links: tips, tutorials and more.
Ask your programming questions--or help out your peers by answering them--in our live discussion forums.
Dig Deeper on iSeries COBOL programming
Related Q&A from John Brandt
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.