BeginnerTrouble
My change did not take effect
The code is fixed, the job ran, and the behaviour is unchanged.
Check each of these
- Did the compile actually succeed? Return code 8 or higher may still leave an old load module in place.
- Did the bind write to the library the job actually uses? Read the STEPLIB in JESJCL, in order.
- Is an older copy of the module earlier in the STEPLIB concatenation? First match wins.
- For a dynamic CALL, is the called module in the search order at run time as well as at bind time?
- For CICS, has a NEWCOPY or PHASEIN been done? CICS keeps the loaded copy until told otherwise.
- For DB2, was the package rebound? An unbound change leaves the old SQL running.
- Did you change the member you think? Check you were not editing a copy in your own library.
Stuck on something else?
Ask the community or search the full course.