search cancel

About Datacom/AD ENF Plan in Common Services fallback from 15.0 to 14.1

book

Article ID: 133581

calendar_today

Updated On:

Products

CIS COMMON SERVICES FOR Z/OS 90S SERVICES DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS COMMON PRODUCT SERVICES COMPONENT Common Services Datacom/AD CA ECOMETER SERVER COMPONENT FOC EASYTRIEVE REPORT GENERATOR FOR COMMON SERVICES INFOCAI MAINTENANCE IPC UNICENTER JCLCHECK COMMON COMPONENT LDAP SERVER FOR Z/OS 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 MF - MISC OLD CODES SERVICE ASSURE GENERIC UNISERVICE FOR CICS GENERIC UNISERVICE II Output Management Web Viewer

Issue/Introduction

During the upgrade of CA Common Services from14.1 to 15.0, it is necessary to submit the job CAW0JCL(AW1IMPRT) to import the new ENF Plan into Datacom/AD.

What to do in case of fallback to CA Common Services 14.1 from 15.0 in regard to this new Datacom/AD ENF Plan?

 

Environment

Release : 15.0

Component : CCS390 - CA COMMON SERVICES FOR Z/OS

Resolution

Looking at CAW0JCL(AW1IMPRT) member of ENF 15.0, it can be verified that the Plan name is 'CAS9ENFS.TRAN$ENF#[email protected]', which is different from the Plan name of ENF 14.1, that is 'CAS9ENFS.TRAN$ENF#[email protected]'.

This means that the 2 Plans can co-exist at the same time in the same Datacom/AD environment, even because only the load library used by ENF task will determine which of them will be the one used by the task. In this case if a fallback will be necessary, the old Plan is still present and the old load library will point and use it.