MCP SUCCESSOR dependency conditions: .

APPLICATION#1 has an I/A APP#1 OPERATION CPU1 010 APP#1 OPERATION CPU1 030

resolution may fail under the following

of 20:05 has no explicit I/A has an OPERATION I/A of 23:00 has APPL#1 OPERATION CPU1 010 as an INT PRED has APPL#2 OPERATION CPU1 020 as an EXT PRED APPLICATION#2 has an I/A of 20:06 APP#2 OPERATION CPU1 020 has no explicit I/A has APPL#1 OPERATION CPU1 010 as an EXT PRED . APPLICATION#1 is added to the CP with RESOLVE REQUIRED = N Then APPLICATION#2 is added to the CP with RESOLVE=Y and RESOLVE REQUIRED=Y . APP#2 CPU1 020 I/A = 20:06 (SUCC) APP#1 CPU1 010 I/A = 20:05 (PRED) -- PREDECESSOR IS RESOLVED CORRECTLY. . APP#1 CPU1 030 I/A = 23:00 (SUCC) APP#2 CPU1 020 I/A = 20:06 (PRED) -- PREDECESSOR WHOULD BE RESOLVED IN CP EXTEND, BUT IS NOT RESOLVED IN MCP . MCP processing considers only the APPLICATION I/A TIME of the SUCCESSOR OPERATION, not the OPERATION I/A as is done by CP BATCH. Further, the RESOLVE REQUIRED flag on panel EQQMADDP applies only to PREDECESSOR resolution... NOT SUCCESSORS. . These differences between CP BATCH and the MCP processing should be clearly documented.
Local fix

Problem summary

**************************************************************** * USERS AFFECTED: ALL OPC/V2 USERs * * FUNCTION=MCP Modify Current Plan * **************************************************************** * PROBLEM DESCRIPTION: Both the manual and the help panel * * EQQMADD3 do not mention that RESOLVE * * REQUIRED=Y apply only to the * * PREDECESSORS resolution. * ****************************************************************

* RECOMMENDATION: APPLY THE PTF FIXING THIS APAR * **************************************************************** Both the manual and the help panel EQQMADD3 do not mention that RESOLVE REQUIRED=Y apply only to the PREDECESSORS resolution.
Problem conclusion

The help panel has been corrected. THE FOLLOWING OPC/ESA PUBLICATION WILL BE UPDATED: - - +--------------------------------------------------------------+ | | |TITLE: OPC Controlling and Monitoring the Workload 2.3.0 | | SH19437702 | | | |PAGE: 50 SUBJECT: Including Dependencies defined ..| | Change the text, which starts with "When you request", in the| | following way: | | "When you request that dependencies be considered for | | individual occurrences, you can also specify if the | | PREDECESSOR dependencies MUST be resolved. If you specify | | RESOLVE REQUIRED=Y, OPC issues a message if ANY PREDECESSOR | | dependency defined in the application cannot be resolved. If| | this happens, OPC does not add the application occurrence | | into the current plan until you enter DEP and delete the | | unresolved dependency." | +--------------------------------------------------------------+