search cancel

Per RO95587, is there a need to define an additional ZFS?

book

Article ID: 14890

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 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 Compress Data Compression for MVS Compress Data Compression for Fujitsu

Issue/Introduction

Users do not want to create a new ZFS file (as specified in ++HOLD for RO95587).



We currently have two zfs files already defined for CA COMMON SERVICES (TOMCAT and MAINFRAME CONNECTOR).

Are we required to create a new ZFS (++HOLD APAR # RO95587), or can we use one of the existing ones?

 

 

Environment

z/OS, CA COMMON SERVICES 14.1

Resolution

The file system introduced by RO95587 belongs to the CAIRIM component, which is separate from the Tomcat and Mainframe Connector components. Therefore, it is required to define an additional ZFS file, since we must keep the file systems separate.