CISCOMMON SERVICES FOR Z/OS90S SERVICESDATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OSCOMMON PRODUCT SERVICES COMPONENTCommon ServicesDATACOM - ADCA ECOMETER SERVER COMPONENT FOCEasytrieve Report Generator for Common ServicesINFOCAI MAINTENANCEIPCUNICENTER JCLCHECK COMMON COMPONENTLDAP SERVER FOR Z/OSMainframe VM Product ManagerCHORUS SOFTWARE MANAGERCA ON DEMAND PORTALCA Service Desk Manager - Unified Self ServicePAM CLIENT FOR LINUX ON MAINFRAMEMAINFRAME CONNECTOR FOR LINUX ON MAINFRAMEGRAPHICAL MANAGEMENT INTERFACEWEB ADMINISTRATOR FOR TOP SECRETXpertwareMF - MISC OLD CODESSERVICE ASSUREGENERIC UNISERVICE FOR CICSGENERIC UNISERVICE IIOutput Management Web Viewer
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.
Common Services CAIRIM (CAS9) executing on the same system with in house defined "CAS" application.
In-house application beginning with "CAS" being charged whenever CAS9 proc is executed.
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
Reference the Common Services documentation that discusses CAIRIM