A fix is available
APAR status
Closed as program error.
Error description
When during GROUP dynamic ADD to the current plan a LOOP is detected, the message EQQM355W is issued correctly telling that "Some selected occurrences could not be added", in Panel EQQMAMOL the application that causes the loop is marked with the string 'McpError', but the mentioned application is in reality added, the dependency causing the LOOP is omitted and ignored. This leads to the fact that this application is released immediately and started before its predecessors and run out of sequence. The problem here is not the detected LOOP and thus the dependency is ignored but the fact that the message EQQM355W is saying that "Some selected occurrences could not be added" but in reality the application causing the LOOP is added. It is added is such cases without dependencies so it gets started immediately after ALL ADD and before ALL RELEASE so that the TWSz dialog user does not have any chance to prevent this application from starting.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All TWS for z/OS users: * * FUNCTION = MCP * **************************************************************** * PROBLEM DESCRIPTION: When, during GROUP dynamic ADD to the * * current plan, a LOOP is detected, the * * message EQQM355W is issued and on the * * Panel EQQMAMOL the application that * * causes the loop is marked with the * * string 'McpError', but the mentioned * * application is added. * **************************************************************** * RECOMMENDATION: APPLY THE PTF FIXING THIS APAR * **************************************************************** When during GROUP dynamic ADD to the current plan a LOOP is detected, the message EQQM355W is issued correctly telling that "Some selected occurrences could not be added". In panel EQQMAMOL, the application, that causes the loop, is marked with the string 'McpError', but the mentioned application is added.
Problem conclusion
In this scenario the occurrence that causes the loop is not released. On the panel EQQMAMOL the short message "DEP LOOP IN GROUP" is issued followed by the long message "EQQM358W Dep loop detected, not all deps resolved...". 502Y 512Y 602Y 912Y 922Y 932Y EQQMC0EX EQQMC0RH
Temporary fix
Comments
APAR Information
APAR number
PI43008
Reported component name
TIV WRKLD SCHD
Reported component ID
5697WSZ01
Reported release
512
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-06-15
Closed date
2015-08-28
Last modified date
2016-04-27
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI30651 UI30652 UI30653 UI30654 UI30655 UI30656
Modules/Macros
EQQMC0EX EQQMC0RH
Fix information
Fixed component name
TIV WRKLD SCHD
Fixed component ID
5697WSZ01
Applicable component levels
R502 PSY UI30651
UP15/12/17 P F512
R512 PSY UI30652
UP15/12/17 P F512
R602 PSY UI30653
UP15/12/17 P F512
R912 PSY UI30654
UP15/12/17 P F512
R922 PSY UI30655
UP15/12/17 P F512
R932 PSY UI30656
UP15/12/17 P F512
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSRULV","label":"IBM Workload Scheduler for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"512","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"512","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
27 April 2016