Reason:
The removal of VAMPRE00, the hook at IGGPRE00, or VAMPOST0, the hook at IGGPOST0, may fail for a number of reasons. The RC identifies the specific place in the code where the message originated.
Action:
CA Allocate only attempts to uncouple itself from these intercept points during a shutdown operation when it is running with PLSOPT94 (Y). The default value is (N). When the rest of the active configuration is removed, the hooks are left in, but rendered inactive.
A shutdown operation can be initiated with one of three different Action Commands: CLEANUP, REMOVE, or STOP. The difference between these commands in how they react to unexpected error conditions encountered during a shutdown operation such as this VAM0363 condition:
CLEANUP continues with the shutdown process and then Started Task ends.
REMOVE stops the shutdown process if running with RESIDENT. The Started Task remains running, waiting for the next action command. If you run NON-RESIDENT, the Started Task ends after the shutdown process stops prematurely when it encounters the unexpected error condition. The residency of the Started Task is noted in the VAM0078 message. The message is included with the output from a STATUS request.
STOP terminates the shutdown process and ends the Started Task.
If you run with PLSOPT94 (Y), the reason the default value is (N) is that many other products also have hooks at IGGPRE00 or IGGPOST0. The VAM0363 condition occurs because one of those other products that hooks IGGPRE00 or IGGPOST0 was installed behind CA Allocate. The product was installed at one or both of those intercept points. CA Allocate uses the LIFO (last-in, first-out) methodology that requires that hooks are removed in REVERSE order from how they were installed.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|