Can the CAS9 proc be renamed?

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

We have a retiring application with the 3 character code of CAS and our chargeback system cannot distinguish between the app and the product proc, so they are being charged everytime we execute this proc.  

Environment

Common Services CAIRIM (CAS9) executing on the same system with in house defined "CAS" application.    

Cause

In-house application beginning with "CAS" being charged whenever CAS9 proc is executed.

Resolution

It is possible to rename the proc.  

•  Ensure that the name is changed to correspond to any automated processes that may execute CAS9
• Any console commands also need to reflect the new name
• ie, S CAS9,,,LMPKEYS                

Additional Information

Reference the Common Services documentation that discusses CAIRIM