NEWCOPY
The CICS action that makes a region load the latest version of a program, after the program has been changed and link-edited.
Also written PHASEIN, SET PROGRAM NEWCOPY, new copy
When a CICS program is changed, compiled and link-edited, the running CICS region does not notice by itself. It keeps using the copy of the program it already loaded. NEWCOPY tells it to load the new version.
The usual command is CEMT SET PROGRAM(ACCTINQ) NEWCOPY. The next task that uses ACCTINQ gets the new version. NEWCOPY only works when the program is not in use at that moment. PHASEIN is the alternative for busy programs: tasks already running finish with the old copy, and new tasks get the new one.
At a site with several regions, the program may need a new copy in each region that runs it, which is where tools like CICSPlex SM help. In production, NEWCOPY is part of the change process, often run by automation as the last step of a promotion.
A classic puzzle in testing is "I changed the program but nothing happened". Usually the change was link-edited correctly, but no NEWCOPY was done, so CICS is still running the old version.
Where can I learn this hands-on?
Right here, at ZedBank. You take a junior job at a simulated bank and learn each part of the work by doing it, with Zed beside you. There's nothing to install.
Start at ZedBankRelated
- CEMTThe CICS transaction used to see and change what is running in a region, enquiring on resources and acting on them.
- CICS regionOne running copy of CICS, with its own programs, files and users. A site typically runs several.
- Load moduleThe runnable form of a program, stored in a library, which JCL executes by name.
- Link-editCombining compiled object code with the other modules it needs into a single runnable program.
- Change controlThe process every change goes through before reaching production: reviewed, approved, scheduled and reversible.