KNG0627D Several Object Not Licensed
search cancel

KNG0627D Several Object Not Licensed

book

Article ID: 426138

calendar_today

Updated On:

Products

Vantage Storage Resource Manager

Issue/Introduction

We have been making the initial test with z/OS v3.1 migrating from z/OS v2.5.  Everything worked fine after several test, however we got this message below: 

KNG0627D Object CATACSIA Not Licensed            
KNG0627D Object DMSINDEX Not Licensed            
KNG0627D Object DTOC4SYS Not Licensed            
KNG0627D Object EXTFILT  Not Licensed            
KNG0627D Object GENDELTA Not Licensed            
KNG0627D Object GENSUMSL Not Licensed            
KNG0627D Object JOINSTAT Not Licensed            
KNG0627D Object LSPACEPO Not Licensed            
KNG0627D Object MAILBOX  Not Licensed            
KNG0627D Object MEMORYSE Not Licensed            
KNG0627D Object MVDSNS   Not Licensed            
KNG0627D Object OBJECTRL Not Licensed            
KNG0627D Object OBJ10181 Not Licensed            
KNG0627D Object PDSMEMX  Not Licensed            
KNG0627D Object POOLGRP  Not Licensed            
KNG0627D Object POOLS    Not Licensed            
KNG0627D Object POOLS    Not Licensed
KNG0627D Object POOLS    Not Licensed
KNG0627D Object RCVB     Not Licensed            
KNG0627D Object SECURITY Not Licensed            
KNG0627D Object SMFCONF  Not Licensed            
KNG0627D Object STMON    Not Licensed            
KNG0627D Object VISTCFG  Not Licensed            
KNG0627D Object VISTMCD  Not Licensed
KNG0627D Object VISTMCM  Not Licensed
KNG0627D Object VKGPARMS Not Licensed         
KNG0627D Object XREFPV   Not Licensed           

Cause

That means something probably goes wrong during the IPL sequence initialization.

Resolution

In such case, you need to check when CAIRIM (CAS9) initialized the LMP keys for the Broadcom Products and when Vantage here starts.

You will probably notice that CAS9 was in process to install the LMP keys and unfortunately Vantage started before its corresponding LMP keys were loaded in to memory.

The best solution to avoid this problem with Broadcom products in general is to use the CAIRIM AUTOCMD way to start the Broadcom products at the end of CAIRIM processes. So you will be never get any LMP key initialization problems.