APAR status
Closed as program error.
Error description
After PTF UQ23378/9 are applied, OPC CP BATCH PROCESSING may incorrectly remove special resource records from the CX dataset. Resources which were *not* dynamically added... that is, which are defined in the RD database... may be deleted even tho there are operations in the CP which require those resources, and even though the resource status does not match the RD definition. . This occurs most consistantly when BATCHOPT keyword parameter DYNAMICDEL() is set to NO. This APAR is the SysRoute of Apar PQ27305.
Local fix
Until a fix is available for this PTF, it is recommended that users set DYNAMICDEL(Y).
Problem summary
**************************************************************** * USERS AFFECTED: ALL OPC/ESA USERS. * * FUNCTION=DP Daily Plan * **************************************************************** * PROBLEM DESCRIPTION: The APAR PQ27941 had the objective to * * help the customers in the deletion of * * the SR from the CP, taking into * * consideration the fact that in many * * scenarios SR dynamically added to the * * CP are stored with values which do not * * satisfy the criteria to be considered * * eligible for deletion: for this * * purpose it created the parameter * * DYNAMICDEL. Specifying DYNAMICDEL(YES) * * a SR dynamically added should have been * * considered eligible for deletion, * * without any further check, while * * specifying DYNAMICDEL(NO) or omitting * * the new parameter, no change with the * * previous process should have happened. * * Unfortunately the implementation of * * that APAR was wrong and caused in both * * cases in some scenarios incorrect * * results. * **************************************************************** * RECOMMENDATION: APPLY THE PTF FIXING THIS APAR * **************************************************************** The APAR PQ27941 had the objective to help the customers in the deletion of the SR from the CP, taking into consideration the fact that in many scenarios SR dynamically added to the CP are stored with values which do not satisfy the criteria to be considered eligible for deletion: for this purpose it created the parameter DYNAMICDEL. Specifying DYNAMICDEL(YES) a SR dynamically added should have been considered eligible for deletion, without any further check, while specifying DYNAMICDEL(NO) or omitting the new parameter, no change with the previous process should have happened. Unfortunately the implementation of that APAR was wrong and caused in both cases in some scenarios incorrect results.
Problem conclusion
This is a corrective fix. Now the new parameter DYNAMICDEL works correctly and special resources, dynamically added after the installation of this APAR, are considered eligible for deletion if DYNAMICDEL(YES) is specified, while, if DYNAMICDEL is omitted or DYNAMICDEL(NO) is specified, each SR (independently if it was dynamically added or not) will be considered eligible for deletion only if satisfies the old criteria. Problem is fixed. - - - THE FOLLOWING OPC/ESA PUBLICATION(S) WILL BE UPDATED: - - - +--------------------------------------------------------------+ | | |TITLE: OPC/ESA CUSTOMIZATION AND TUNING, SH19-4380-00 | | | |PAGES: 16-18 | |CHAPTER: 1 | |PARAGRAPH: "Other initialization statements" | |TOPIC: BATCHOPT | | | | add a new keyword: | | | |DYNAMICDEL(NO/YES) (no is the default) | |DYNAMICDEL determines if a special resource, that has been | |dynamically added to the current plan, has to be considered | |eligible for deletion at the next replan or CP extension, | |without checking the normal conditions listed in the | |section "Setting the global values" of the PSW manual. | | | |Specify YES if OPC/ESA should consider any SR dynamically | |added as eligible for deletion, without any further check. | | | |Specify NO if OPC/ESA should not make any difference between | |SR dynamically added and other SR as far as concerns their | |evaluation as eligible for deletion. | | | +--------------------------------------------------------------+ +--------------------------------------------------------------+ | | |TITLE: OPC/ESA PLANNING AND SCHEDULING | | THE WORKLOAD, SH19437600 | | | |PAGES: 52 | |CHAPTER: 3 | |PARAGRAPH: Creating special resources | |TOPIC: "Creating missing resources during Batch Planning" | | | |ADD THE FOLLOWING: ( after "Use the DYNAMICADD..." paragraph) | | | |Use the DYNAMICDEL keyword of the BATCHOPT initialization | |statement to specify whether, at the extension or rerun | |of the Current Plan, OPC/ESA should consider eligible | |for deletion those resources that have been previously | |dynamically added. Refer to | |Customization and Tuning for details of BATCHOPT. | | | |PAGES: 53 | |CHAPTER: 3 | |PARAGRAPH: Creating special resources | |TOPIC: "Setting the Global Values" | | | |ADD THE FOLLOWING: (Before "To make a resource eligible for | | deletion" ) | |A SR is considered eligible for deletion if all the following | |conditions are satisfied: | |- the global quantity is not set | |- the global availability is not set | |- the deviation is not set | |- no intervals modified | |- RODM Availability, Quantity and Deviation are set to N. | | | |ADD THE FOLLOWING at the end of the section: | |WARNING: There are many cases in which SR dynamically added | |are stored with values which do not satisfy the criteria to | |be considered eligible for deletion. It is possible to avoid | |the work to manually modify them and still be able to delete | |them: it is necessary to run a daily planning REPLAN or EXTEND| |with DYNAMICDEL(YES). In this case an SR dynamically added | |(except those added by the DP extension or rerun itself and | |those added before the installation of the APAR PQ27941) | |is always considered eligible for deletion without any | |condition. | | | +--------------------------------------------------------------+ +--------------------------------------------------------------+ | | |TITLE: OPC/ESA CUSTOMIZATION AND TUNING, SH19-4380-01 | | | |PAGES: 17-20 | |CHAPTER: 1 | |PARAGRAPH: "Other initialization statements" | |TOPIC: BATCHOPT | | | | add a new keyword: | | | |DYNAMICDEL(NO/YES) (no is the default) | |DYNAMICDEL determines if a special resource, that has been | |dynamically added to the current plan, has to be considered | |eligible for deletion at the next replan or CP extension, | |without checking the normal conditions listed in the | |section "Setting the global values" of the PSW manual. | | | |Specify YES if OPC/ESA should consider any SR dynamically | |added as eligible for deletion, without any further check. | | | |Specify NO if OPC/ESA should not make any difference between | |SR dynamically added and other SR as far as concerns their | |evaluation as eligible for deletion. | | | +--------------------------------------------------------------+ +--------------------------------------------------------------+ | | |TITLE: OPC/ESA PLANNING AND SCHEDULING | | THE WORKLOAD, SH19437601 | | | |PAGES: 54 | |CHAPTER: 3 | |PARAGRAPH: Creating special resources | |TOPIC: "Creating missing resources during Batch Planning" | | | |ADD THE FOLLOWING: ( after "Use the DYNAMICADD..." paragraph) | | | |Use the DYNAMICDEL keyword of the BATCHOPT initialization | |statement to specify whether, at the extension or rerun | |of the Current Plan, OPC/ESA should consider eligible | |for deletion those resources that have been previously | |dynamically added. Refer to | |Customization and Tuning for details of BATCHOPT. | | | |PAGES: 55 | |CHAPTER: 3 | |PARAGRAPH: Creating special resources | |TOPIC: "Setting the Global Values" | | | |ADD THE FOLLOWING: (Before "To make a resource eligible for | | deletion" ) | |A SR is considered eligible for deletion if all the following | |conditions are satisfied: | |- the global quantity is not set | |- the global availability is not set | |- the deviation is not set | |- no intervals modified | |- RODM Availability, Quantity and Deviation are set to N. | | | |ADD THE FOLLOWING at the end of the section: | |WARNING: There are many cases in which SR dynamically added | |are stored with values which do not satisfy the criteria to | |be considered eligible for deletion. It is possible to avoid | |the work to manually modify them and still be able to delete | |them: it is necessary to run a daily planning REPLAN or EXTEND| |with DYNAMICDEL(YES). In this case an SR dynamically added | |(except those added by the DP extension or rerun itself and | |those added before the installation of the APAR PQ27941) | |is always considered eligible for deletion without any | |condition. | | | +--------------------------------------------------------------+ 100N 102Y 200N 202Y DCLBOPT DCLDPCOM EQQBOPTX EQQDNTOP EQQDPQAC EQQDPQAR EQQDPQCX EQQDRTOP EQQQQDYN
Temporary fix
A fix is already available.
Comments
APAR Information
APAR number
PQ27941
Reported component name
TME 10 OPC V2 R
Reported component ID
5697OPC01
Reported release
202
Status
CLOSED PER
PE
YesPE
HIPER
YesHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
1999-06-18
Closed date
1999-11-29
Last modified date
2000-01-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UQ37743 UQ37744 UQ37745 UQ37746
Modules/Macros
DCLBOPT DCLDPCOM EQQBOPTX EQQDNTOP EQQDPQAC EQQDPQAR EQQDPQCX EQQDRTOP EQQQQDYN
| SH19438000 | SH19437600 | SH19438001 | SH19437601 |
Fix information
Fixed component name
TME 10 OPC V2 R
Fixed component ID
5697OPC01
Applicable component levels
R102 PSY UQ37745
UP99/12/17 P F912 «
R202 PSY UQ37746
UP99/12/21 P F912 «
R100 PSN
UP
R200 PSN
UP
[{"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":"202","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
04 January 2000