Reason:
CA Deployment Service is issuing a Mount command for a USS file system.
Action:
No action is required. This message is informational.
Reason:
The USS file system has been successfully mounted.
Action:
No action is required. This message is informational.
Reason:
CA Deployment service is starting MSMDUTIL to unpack the GIMZIP files.
Action:
No action is required. This message is informational.
Reason:
GIMUNZIP invoked to unpack the GIMZIP package has failed. All relevant failure information has been returned to the CA CSM host for diagnostics.
Action:
Information only. No action is required, until the cause of the failure has been determined.
Reason:
GIMUNZIP was used to unpack the GIMZIP package has completed successfully. This is an informational message indicating the deployable unit has been successfully deployed.
Action:
No action is required. This message is informational.
Reason:
This message indicates that the files used by MSMDUTIL is being dynamically deallocated.
Action:
No action is required. This message is informational.
Reason:
This message indicates that the files used by MSMDUTIL have been successfully deallocated.
Action:
No action is required. This message is informational.
Reason:
This message indicates that the USS file system is being unmounted.
Action:
No action is required. This message is informational.
Reason:
This message indicates that the clean-up of USS environment failed. Remote Deployment Service continues with normal task termination.
Action:
No action is required. This message is informational.
Reason:
This message indicates that the clean-up of USS environment completed. The resources were thread-related.
Action:
No action is required. This message is informational.
Reason:
This message indicates that the clean-up of USS environment completed. The resources were process-related.
Action:
No action is required. This message is informational.
Reason:
BPX1SDD failed to set default as DUBPROCESS.
Action:
No action is required. This message is informational.
Reason:
This message indicates that the UTILITY ATTACH EXECUTOR been entered to attach a UTILITY to perform Deployment Action.
Action:
No action is required. This message is informational.
Reason:
This message indicates that EXCUTOR is attaching the UTITILY. All messages until the MSMD5176I message is the result of the UTILITY invoked.
Action:
No action is required. This message is informational.
Reason:
This message indicates that the UTILITY has completed and return to the ATTACH EXECUTOR with zero return code. Detail information from the UTITULY will be captured and returned to CA CSM.
Action:
No action is required. This message is informational.
Reason:
UTILITY SERVICE completed with non-zero return code..
Action:
No action is required. This message is informational.
Reason:
This message indicates that the attached UTILITY has ABENDED. The ATTACH EXECUTOR will DETACH the SUBTASK
Action:
No action is required. This message is informational. The retrieved output should be reviewed.
Reason:
The loading of CA CSM Deployment Service Unmount service program has failed. The USS file system will not be unmounted. CA CSM host system has been informed of same.
Action:
Make sure that the load module library (LOADLIB) containing MSMDUMFS is in the LNKLST.
Reason:
The loading of CA CSM Deployment Service Mount service program has failed. The required USS file system cannot be mounted. CA CSM Deployment service cannot continue. CA CSM host system has been informed of same.
Action:
Make sure the load module library (LOADLIB) containing MSMDMTFS is in the LNKLST.
Reason:
This message indicates a dynamic allocation failure. Review relevant failure IKJ or IGD prefixed message issued prior to this message.
Action:
Use either the STC JES message log or SYSLOG to review additional diagnostics messages, especially those starting with IKJ or IGD.
If unable to resolve the problem, save and report this message to CA Support.
Reason:
This message is issued in conjunction with message MSMD5200I.
Action:
Determine the cause of previous dynamic allocation failure before starting your next deployment action.
Reason:
This is an informational message indicating that one of the reasons for not able to send the results structure back to the CA CSM host.
Action:
Contact CA Support when diagnosing deployment related error conditions.
Reason:
A GETMAIN request for local work area failed. Deployment service cannot continue.
Action:
Make sure there are a minimum of 56K of storage is available.
Reason:
The load of MSMDALOC, dynamic allocation service module failed. Deployment service cannot continue.
Action:
Make sure the load module library (LOADLIB) containing MSMDALOC is in the LNKLST.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|