During the initialization phase of CA Vantage 12.6 or 14.0 randomly the DFSMShsm Interface is not correctly started and the below messages are returned:
VAN0760I DFSMShsm Real Time Message Collection Hook:No HSM task is active. CVTHSM
VAN0711E DFSMShsm Message Collection Initialization Failed, RC=36
so that the Real Time Message Monitoring and Collection is affected by this error.
How to bypass the problem?
CA Vantage 12.6 and 14.0
This is the description of the messages from the CA Vantage SRM 12.6 and 14.0 Message Reference Guide:
DFSMShsm Real Time Message Collection Hook: %30S
If the system parameter HSMTABSZ is specified with a non-zero value, this message appears at subsystem startup and shutdown.
The message also appears if the command ACT,HSMTAB or DEACT,HSMTAB is issued.
? At startup or as a result of an ACT command %3S can be normally substituted with:
– VERIFY CHECK OK, NOW HOOKED
– HOOKED BY OTHER VANTAGE
– ALREADY HOOKED BY THIS VANTAGE
If it is substituted with one of the following:
– ARCILOG VERSION CHECK FAILED
– HOOK VERIFY CHECK FAILED
Then the version of DFSMShsm that you are running is currently not supported by Realtime Automation. A Snap Dump is dynamically spooled off to DD-card SNAPHSM and should be forwarded to CA Support. The dump will be used to support your version of DFSMShsm.
? If HSM is not active or HSM logging is disabled, one of the following messages is displayed:
– NO HSM, CVTHSM=0
– HSM NOT ACTIVE
– HSM IS IN SHUTDOWN
– HSM LOGGING IS DISABLED
? At shutdown or as a result of a DEACT command, %3S can be normally substituted with:
– HOOK REMOVED
– NO HOOK, NOTHING TO REMOVE
%17S Collection Initialization Failed, RC=%2S
Initialization of console message or DFSMShsm message collection failed. An RC=8 on a F SAM,ACT,WTOTAB or F SAM,ACT,HSMTAB means that message collection has already been initialized.
If other return codes than 8 are given then they should be reported to CA Support.
In this case:
1. the VAN0760I reason is ‘HSM NOT ACTIVE ‘
2. the VAN0711E RC is 36
From these error messages, it results that the DFSMShsm task is not running when CA Vantage is started. If this is the case, the error message is a normal behavior of CA Vantage but it is possible to recover it.
The ability to monitor real-time HSM messages is not started by default and it is part of the CA Vantage SRM Automation Option, which is enabled setting COMP=AUTO in CONFIG member on PARMLIB.
It allows you to select specific HSM messages that are of particular interest to you and route only those messages to CA Vantage SRM where they can be accumulated for easy viewing and analysis. This will save you from searching through the HSM logs for certain messages; CA Vantage SRM can do it for you. It also allows the CA Vantage SRM automation functions to detect and respond to the critical HSM messages in real-time.
In CA Vantage SRM 12.6 or 14.0 chapter 8 ‘Configuring CA Vantage SRM Automation Option’ we provide details about how to customize and activate it.
To detect and hook HSM hosts that are started after CA Vantage SRM, you must implement a Message Automation script (distributed as member HSMDTECT in the CCTUSAMP library) that traps the HSM startup message and issues the command:
This command causes CA Vantage SRM to find the newly started HSM host and begin routing its messages to the SAMS address space, such that all HSM messages continue to be monitored.
To customize the HSMDTECT script
1. If the HSMDTECT script is not in your Automation Script Library as specified in the AUTOSCR sysparm, copy it from the CCTUSAMP library.
2. Customize the script by following the comments in the beginning of the script.
3. Ensure your HSMTRIGS member allows message ARC0008I to be routed to CA Vantage SRM.
In any other situation, please open a Case to CA Support as suggested by the message action.