search cancel

How does cairim manage expiry date?

book

Article ID: 15269

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

I just wanted to check how the CAIRIM program handles changes to license key.

If we ran CAIRIM with keys with a later expiry date it updates these expiry dates (viewing from CAILMP in SYSVIEW).

If we then rerun against the old keys with a closer expiry date it says it accepts the key for the cpu but when viewing
in SYSVIEW, the date is not altered and stays as the date most in the future?

So from what I am seeing if the current date is further in the future then running CAIRIM with a date close to today
current date is accepted by CAIRIM but doesn't alter the expiry date.

Is this how it should be ?



When we rerun against the old keys with a closer expiry date it says it accepts the key for the cpu but when viewing
in SYSVIEW, the date is not altered and stays as the date most in the future?

Environment

CA Common Services R14.1 - Supported z/OS versions -

Resolution

It is the way CAIRIM program handles changes to license keys.

LMP will keep the key with the later expiration date.