REFRESH VS NEWCOPY

book

Article ID: 51468

calendar_today

Updated On:

Products

CA Datacom - DB CA Datacom CA Datacom - AD CA Datacom - Server CA Ideal CA CIS CA Common Services for z/OS CA 90s Services CA Database Management Solutions for DB2 for z/OS CA Common Product Services Component CA Common Services CA Datacom/AD CA ecoMeter Server Component FOC CA Easytrieve Report Generator for Common Services CA Infocai Maintenance CA IPC Unicenter CA-JCLCheck Common Component CA Mainframe VM Product Manager CA Chorus Software Manager CA On Demand Portal CA Service Desk Manager - Unified Self Service CA PAM Client for Linux for zSeries CA Mainframe Connector for Linux on System z CA Graphical Management Interface CA Web Administrator for Top Secret CA CA- Xpertware

Issue/Introduction

Description:

REFRESH PGM gives message IDADRLDP08 Module module-name has a different compile date/time than DD.

Solution:

The REFRESH command does PHASEIN instead of NEWCOPY. This means that if a module is in use, it will not be replaced immediately. CICS continues to use the old copy for all currently running transactions until they have finished (RESCOUNT equal to zero). CICS loads the new version either from the DFHRPL or dynamic LIBRARY concatenation, or uses an LPA-resident version, depending on the PRIVATE or SHARED options. PRIVATE is the default setting. Sites that are going to use the REFRESH command should first DISABLE the application, issue the REFRESH command, then issue the ENABLE command.

Information regarding Disabling and Enabling an application can be found in the CA Ideal r11 Administration Guide. The actual DISABLE/ENABLE command can be found in the CA Ideal r11 Command Reference Guide.

Environment

Release:
Component: IDEAL