Direct link to fix
APAR status
Closed as program error.
Error description
When you run the BPM Undeploy command and the business-level application is already in an undeployed state, you see the following error: BPMUndeploy failed due to: The snapshot should be deactivated first and then stopped before it can be undeployed. Use BPMDeactivate to deactivate snapshot and BPMStop to stop snapshot and then try BPMUndeploy.
Local fix
Check business-level application status in the WebSphere administrative console and, if the application is not there, ignore the message that the application must be stopped first.
Problem summary
When the BPM Undeploy command is run, it first checks that the business-level application status is not inactive. If the business-level application is in an undeployed state, you see the same error as when the application is in an active state. PRODUCTS AFFECTED IBM Business Automation Workflow
Problem conclusion
A fix will be included in a future release of Business Automation Workflow that returns a message that indicates the snapshot is already undeployed rather than the message currently returned.
Temporary fix
Comments
APAR Information
APAR number
JR61204
Reported component name
BUS AUTO WORKFL
Reported component ID
5737H4100
Reported release
I00
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2019-06-12
Closed date
2019-08-21
Last modified date
2019-08-21
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
BUS AUTO WORKFL
Fixed component ID
5737H4100
Applicable component levels
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS8JB4","label":"IBM Business Automation Workflow"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"18.0.0.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
21 August 2019