Mainframe Path Start learning free
BeginnerTrouble

My change did not take effect

The code is fixed, the job ran, and the behaviour is unchanged.

Check each of these

  1. Did the compile actually succeed? Return code 8 or higher may still leave an old load module in place.
  2. Did the bind write to the library the job actually uses? Read the STEPLIB in JESJCL, in order.
  3. Is an older copy of the module earlier in the STEPLIB concatenation? First match wins.
  4. For a dynamic CALL, is the called module in the search order at run time as well as at bind time?
  5. For CICS, has a NEWCOPY or PHASEIN been done? CICS keeps the loaded copy until told otherwise.
  6. For DB2, was the package rebound? An unbound change leaves the old SQL running.
  7. 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.

Ask a question