The CA Allocate team recently received a request for a list of messages that could be included in a system message automation tool, such as CA OPS/MVS® Event Management and Automation.
CA Allocate DASD Space and Placement has already defined a set of mesages which it can route to the existing CA Service Desk interface, if you have chosen to include CA Service Desk supportas part of your CA Allocate configuration. If you have not activated the Service Desk Support, then please review the Activate CA Service Desk Support task for the list of messages that it processes. That list can be used as a starting point for configuring your message automation tool to process CA Allocate messages.
In addition, the CA Health Checker Interface provides notification on conditions which affect CA Allocate while it is active.
CA Allocate also provides its own Message Control Facility which can control whether messages go to TSO users, JCL listings, or the operator console. It can also be used to route selected messages to CA Vantage.
The following list of additional messages, which are not part of the Service Desk list or the Health Check list, is aimed at identifying conditions in CA Allocate which still allow the task to start or end successfully, but it may not be operating as expected.
We are aware that the legacy messages in CA Allocate DASD Space and Placement do not end with severity indicators (I, W, E, S, or T). We would like to know if this affects your operations, or if changing the messages to add the suffix would be disruptive to automated operations that you already have in place. We are interested in your feedback. Please use the comments section of this article to continue the discussion on this topic.
The following list of messages are automation candidates which are not listed as part of the Service Desk support or Health Checker Support:
Incomplete installation or removal. An incomplete removal may also cause abandoned memory in CSA or SQA
VAM0060 UNABLE TO INSTALL SVC 32 (DADSM) HOOK RC = xx
VAM0062 IGGDAC02 HOOK CAN ONLY BE REMOVED BY LOADLIB THAT INSTALLED IT
VAM0071 DAC02-STUB FOUND INSTALLED. 'xxxx' WITH EARLIER LOADLIB NOT PERMITTED.
Messages which indicate you may be unintentionally running with default values
VAM0075 OPTIONAL PLSPRGDS MEMBER KEYDSN NOT FOUND
VAM0082 DOCUMENTED DEFAULT NAME OF VKGPARMS USED FOR OPTIONAL SYSPARM OVERRIDE MEMBER
VAM0089 OPTIONAL CONFIG MEMBER <member> NOT FOUND
VAM0090 OVERRIDE VALUE SUPPLIED FOR SYSPARM <sysparm> IGNORED BECAUSE IT IS INVALID
Messages which can affect the problem program address space
VAM0020 CANNOT GET MEMORY FOR mmmmmmmm
VAM0200 BAD INSTRUCTION CODE IN PROGRAM
VAM0201 PROGRAM STACK IS TOO SMALL
VAM0307 CA Allocate DASD Space and Placement POST-EXIT CANNOT GET MEMORY
VAM5005 ALLOCATION PROCEEDING WITH CA Allocate DASD Space and Placement FEATURES DISABLED FOR DSN=ddd
VAM5036 UNABLE TO DELETE NVR FOR DATA SET dsname, RC=rc
VAM7000 LSPACE FAILURE RC(nnnnnnnn)
Storage management issues
VAM0039M Indicates insufficient space for primary allocation.
VAM0039O Indicates that there was no room in the VTOC or VTOC index on a volume.
Unused memory not freed
VAM0382 FREEMAIN OF {PRIVATE/CSA} QUOTA TABLE FAILED, RC = xx
VAM0410 ddname ALLOCATION FAILED RC=nnnnnnnn FOR mmm in dsn
These Health Checker messages indicate a need for further action
VAMHC006 Your CA Allocate DASD Space and Placement system failed to initialize End-of-Volume Support.
VAMHC007 The last REFRESH to your CA Allocate DASD Space and Placement system failed to activate a new Allocation Selection Routine (ASR).