COPYIN and DDLDB2 not accessible after new LMP keys installed with the addition of a CP engine
search cancel

COPYIN and DDLDB2 not accessible after new LMP keys installed with the addition of a CP engine

book

Article ID: 117578

calendar_today

Updated On:

Products

Repository

Issue/Introduction

We installed another CP over the weekend and I believe that new LMP keys were installed for the CA products. We do not see any authorization messages or other licensing related messages, but now the COPYIN and DDLDB2 options are not selectable any longer in any of our Repositories. The only thing that has changed in the environment is the addition of the new keys with the addition of the CP yesterday morning. Is it possible that our licensing could have been affected by the new keys?

Environment

Release:
Component: XTR

Resolution

You must first access a dialog and a entity type before you can issue the OPTIONS.DDLDB2 or the OPTIONS.COPYIN command.  We check the DBX_DIALOG_PRIV table to see if what dialogs are associated with log privileges.   
For example, once logged in select VD RECORDS; VT RECORD