APAR status
Closed as program error.
Error description
In some cases, application processes are not completely canceled when a "Cancel" action is taken. Instead, running steps cancel, and steps following steps continue as if the canceled steps succeeded. To reproduce: 1. Create a component operational process (no version needed) with a simple shell step that sleeps for 10 seconds. (So that the component process takes more than a few seconds to run) 2. Create an application process calling that component operational process 3 times in a row. 3. In the application process, mark the edges between the operational processes as "Grey", or "Always". 4. Run the application process. 5. Immediately cancel the application process. 6. Note that while the first instance of the component process canceled correctly, the second instance of the component process may start running anyway.
Local fix
If it doesn't cancel the first time, canceling the application process via the CLI multiple times will eventually result in the application process cancelling.
Problem summary
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * In some cases, application processes are not completely * * canceled * * when a "Cancel" action is taken. Instead, running steps * * cancel, * * and steps following steps continue as if the canceled steps * * succeeded. * * * * To reproduce: * * 1. Create a component operational process (no version * * needed) * * with a simple shell step that sleeps for 10 seconds. (So * * that * * the component process takes more than a few seconds to run) * * 2. Create an application process calling that component * * operational process 3 times in a row. * * 3. In the application process, mark the edges between the * * operational processes as "Grey", or "Always". * * 4. Run the application process. * * 5. Immediately cancel the application process. * * 6. Note that while the first instance of the component * * process * * canceled correctly, the second instance of the component * * process * * may start running anyway. * **************************************************************** * RECOMMENDATION: * ****************************************************************
Problem conclusion
Fixed in 6.2.4.1
Temporary fix
Comments
APAR Information
APAR number
PI72860
Reported component name
UC RELEASE
Reported component ID
5725M5500
Reported release
621
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-11-28
Closed date
2017-05-25
Last modified date
2017-05-25
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
UC RELEASE
Fixed component ID
5725M5500
Applicable component levels
R621 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS4GCC","label":"IBM UrbanCode Release"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"621","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
25 May 2017