CA Datacom NEWCOPY Console command to replace a load module to the active Multi-User (MUF).

Products

• Datacom
• DATACOM - AD
• CIS
• COMMON SERVICES FOR Z/OS
• 90S SERVICES
• DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS
• COMMON PRODUCT SERVICES COMPONENT
• Common Services
• CA ECOMETER SERVER COMPONENT FOC
• Easytrieve Report Generator for Common Services
• INFOCAI MAINTENANCE
• IPC
• UNICENTER JCLCHECK COMMON COMPONENT
• Mainframe VM Product Manager
• CHORUS SOFTWARE MANAGER
• CA ON DEMAND PORTAL
• CA Service Desk Manager - Unified Self Service
• PAM CLIENT FOR LINUX ON MAINFRAME
• MAINFRAME CONNECTOR FOR LINUX ON MAINFRAME
• GRAPHICAL MANAGEMENT INTERFACE
• WEB ADMINISTRATOR FOR TOP SECRET
• Xpertware

Issue/Introduction

Introduction: 

The CA Datacom NEWCOPY console command allows procedures or modules to be replaced within the CA Datacom Multi-User (MUF) without recycling the MUF.

This means that critical solutions can be applied to a working system without any downtime.

 

Instructions: 

 

In z/OS, the NEWCOPY process first looks to see if the MUF has a DD statement for //NEWCOPY DD to load the module from.

If //NEWCOPY DD is not present, the load will occur using the STEPLIB or JOBLIB. Using STEPLIB or JOBLIB is usually not a problem.

However, if the module replacement into STEPLIB or JOBLIB causes the library data set to be extended, the NEWCOPY load would fail since the STEPLIB or JOBLIB would have been already opened at MUF job execution and NEWCOPY would not have access to a new extent.

 

It is therefore recommended that every MUF execution JCL include a //NEWCOPY DD statement that points to the library that contains every module that is eligible for NEWCOPY.

 

??? NEWCOPY ? name ?????????????????????????????????????????????????????????????

name

(Required) Specify a procedure name or a module name.

- The NEWCOPY console command does not delete the old version of the procedure, and this can cause memory to be wasted if many NEWCOPY commands are issued.

- The NEWCOPY console command works with most modules (see the list given in the valid entries that follow). NEWCOPY alters the operating system load list of modules, replacing the final blank in the eight-character name with a ? (question mark). A load then brings in a fresh copy of the module. All new requests for the module use the newly loaded copy. All current requests logically in the middle of the previous version of the module continue to use that copy. The old copy remains in memory until the MUF is ended.

- Valid Entries: A valid procedure name, or one of the following module names:

DBACMPR, DBACRPR, DBAFNPR, DBBFLPR, DBBFMPR, DBBFWPR, DBCAPPR, DBCFMPR, DBCL1PR, DBCMPPR, DBCOMPR, DBCPLPR DBDSMPR, DBDSTPR, DBDS2PR, DBDS3PR, DBDVCPR, DBEIPPR, DBFABPR, DBHSTPR,DBIDSPR, DBIDXPR, DBID3PR, DBIOCPR, DBIOMPR, DBLOGPR, DBMEMPR, DBMPLPR, DBMPXPR, DBMSMPR, DBOP1PR, DBREDPR, DBREXPR, DBR0PPR, DBRPFPR, DBRPSPR, DBRPTPR, DBRQPPR, DBSMNPR, DBSPLPR, DBSQMPR, DBSRPPR, DBSUBPR, DBTXBPR, DBUPDPR, DBUPXPR, DBUTMPR, DBXNFPR. 

 

Additional Information:  

- More can be found in CA Datacom/DB System and Administration Guide Version 14.0 and above..

 

 

 

Environment

Release:
Component: DB