APAR status
Closed as documentation error.
Error description
BATCH OPTIMIZER utilities such as BMC BATCH OPTIMIZER DATA OPTIMIZER and MAINVIEW BATCH OPTIMIZER prevent correct communication between the OPC CONTROLLER and CP/LTP BATCH PLANNING JOBS. OPC logic depends on an exchange of ENQUEUES and REAL-TIME updates of several sequential datasets to pass information back and forth between the CONTROLLER STC and the CP/LTP BATCH PLANNING JOBS. These optimizers hold I/O from the batch jobs until END OF STEP or END OF JOB, then preventing the required communication from occurring. . When these sorts of utilities are allowed to "manage" I/O for the OPC CP or LTP batch planning jobs, communication between the jobs and the OPC CONTROLLER is disrupted resulting in many hard to diagnose problems. Most commonly, the OPC CURRENT PLAN EXTEND or REPLAN jobs will run to normal completion, an NCP dataset will be successfully created, but the OPC CONTROLLER will not automatically take the new plan into production until forced to do so via a CURRPLAN(NEW) restart of the CONTROLLER. . In other cases, customers have reported CP EXTEND/REPLAN jobs do not clear the EQQJTARC dataset as they should. . APAR PQ27179, in May of 1999, documented a similar problem with SMARTBATCH DATA ACCELERATOR (SMARTBATCH DA). . Use of BATCHPIPES with these OPC batch planning jobs will result in the same sorts of problems. . TWSz 5697WSZ01 . MARCH 2006: TIVOLI ALLOCATION OPTIMIZER has been observed to cause similar problems.
Local fix
EXEMPT all OPC BATCH PLANNING JOBS (LTP EXTEND, LTP MODIFY ALL, LTP MODIFY ONE, LTP TRIAL, CP EXTEND, CP REPLAN, CP TRIAL) from processing by these or any similar products.
Problem summary
**************************************************************** * USERS AFFECTED: All OPC users, * * FUNCTION=LTP,DP * **************************************************************** * PROBLEM DESCRIPTION: BATCH OPTIMIZER utilities such as BMC * * BATCH OPTIMIZER DATA OPTIMIZER and * * MAINVIEW BATCH OPTIMIZER prevent * * correct communication between the * * OPC CONTROLLER and CP/LTP BATCH * * PLANNING JOBS. * **************************************************************** * RECOMMENDATION: APPLY THE PTF FIXING THIS APAR * **************************************************************** BATCH OPTIMIZER utilities such as BMC BATCH OPTIMIZER DATA OPTIMIZER and MAINVIEW BATCH OPTIMIZER prevent correct communication between the OPC CONTROLLER and CP/LTP BATCH PLANNING JOBS. OPC logic depends on an exchange of ENQUEUES and REAL-TIME updates of several sequential datasets to pass information back and forth between the CONTROLLER STC and the CP/LTP BATCH PLANNING JOBS. These optimizers hold I/O from the batch jobs until END OF STEP or END OF JOB, then preventing the required communication from occurring. When these sorts of utilities are allowed to "manage" I/O for the OPC CP or LTP batch planning jobs, communication between the jobs and the OPC CONTROLLER is disrupted resulting in many hard to diagnose problems. Most commonly, the OPC CURRENT PLAN EXTEND or REPLAN jobs will run to normal completion, an NCP dataset will be successfully created, but the OPC CONTROLLER will not automatically take the new plan into production until forced to do so via a CURRPLAN(NEW) restart of the CONTROLLER. Use of BATCHPIPES with these OPC batch planning jobs will result in the same sorts of problems.
Problem conclusion
- - - THE FOLLOWING OPC PUBLICATION(S) WILL BE UPDATED: - - - +--------------------------------------------------------------+ | | |TITLE: INSTALLATION GUIDE, SH19-4379-00 | | | |CHAPTER: 1 | | | |TOPIC: "Relationship between TME 10 OPC and MVS/ESA | | | | The following text has to be added at the end of the | | paragraph after the sentence: | | "As a result, even if the PLAN JOBS run successfully, | | the NCP is not taken into production by the CONTROLLER | | unless a CURRPLAN(NEW) restart is performed." added by | | APAR PQ27179. | | | | BATCH OPTIMIZER utilities such as BMC BATCH OPTIMIZER DATA | | OPTIMIZER and MAINVIEW BATCH OPTIMIZER prevent correct | | communication between the OPC CONTROLLER and CP/LTP BATCH | | PLANNING JOBS. OPC logic depends on an exchange of ENQUEUES | | and REAL-TIME updates of several sequential datasets to pass| | information back and forth between the CONTROLLER STC and | | the CP/LTP BATCH PLANNING JOBS. These optimizers hold I/O | | from the batch jobs until END OF STEP or END OF JOB, then | | preventing the required communication from occurring. | | When these sorts of utilities are allowed to "manage" I/O | | for the OPC CP or LTP batch planning jobs, communication | | between the jobs and the OPC CONTROLLER is disrupted | | resulting in many hard to diagnose problems. Most commonly,| | the OPC CURRENT PLAN EXTEND or REPLAN jobs will run to | | normal completion, an NCP dataset will be successfully | | created, but the OPC CONTROLLER will not automatically take | | the new plan into production until forced to do so via a | | CURRPLAN(NEW) restart of the CONTROLLER. | | Use of BATCHPIPES with these OPC batch planning jobs will | | result in the same sorts of problems. | +--------------------------------------------------------------+ +--------------------------------------------------------------+ | | |TITLE: PLANNING AND SCHEDULING THE WORKLOAD, SH19-4376-00 | | | |CHAPTER: 11 | | | |TOPIC: "Creating and Activating the NCP" | | | | The following text has to be added at the end of the | | paragraph, as a note, after the sentence: | | "As a result, even if the PLAN JOBS run successfully, | | the NCP is not taken into production by the CONTROLLER | | unless a CURRPLAN(NEW) restart is performed." added by | | APAR PQ27179. | | | | BATCH OPTIMIZER utilities such as BMC BATCH OPTIMIZER DATA | | OPTIMIZER and MAINVIEW BATCH OPTIMIZER prevent correct | | communication between the OPC CONTROLLER and CP/LTP BATCH | | PLANNING JOBS. OPC logic depends on an exchange of ENQUEUES | | and REAL-TIME updates of several sequential datasets to pass| | information back and forth between the CONTROLLER STC and | | the CP/LTP BATCH PLANNING JOBS. These optimizers hold I/O | | from the batch jobs until END OF STEP or END OF JOB, then | | preventing the required communication from occurring. | | When these sorts of utilities are allowed to "manage" I/O | | for the OPC CP or LTP batch planning jobs, communication | | between the jobs and the OPC CONTROLLER is disrupted | | resulting in many hard to diagnose problems. Most commonly,| | the OPC CURRENT PLAN EXTEND or REPLAN jobs will run to | | normal completion, an NCP dataset will be successfully | | created, but the OPC CONTROLLER will not automatically take | | the new plan into production until forced to do so via a | | CURRPLAN(NEW) restart of the CONTROLLER. | | Use of BATCHPIPES with these OPC batch planning jobs will | | result in the same sorts of problems. | +--------------------------------------------------------------+ +--------------------------------------------------------------+ | | |TITLE: INSTALLATION GUIDE, SH19-4379-01 | | | |CHAPTER: 1 | | | |TOPIC: "Relationship between TME 10 OPC and MVS/ESA | | | | The following text has to be added at the end of the | | paragraph after the sentence: | | "As a result, even if the PLAN JOBS run successfully, | | the NCP is not taken into production by the CONTROLLER | | unless a CURRPLAN(NEW) restart is performed." added by | | APAR PQ27179. | | | | BATCH OPTIMIZER utilities such as BMC BATCH OPTIMIZER DATA | | OPTIMIZER and MAINVIEW BATCH OPTIMIZER prevent correct | | communication between the OPC CONTROLLER and CP/LTP BATCH | | PLANNING JOBS. OPC logic depends on an exchange of ENQUEUES | | and REAL-TIME updates of several sequential datasets to pass| | information back and forth between the CONTROLLER STC and | | the CP/LTP BATCH PLANNING JOBS. These optimizers hold I/O | | from the batch jobs until END OF STEP or END OF JOB, then | | preventing the required communication from occurring. | | When these sorts of utilities are allowed to "manage" I/O | | for the OPC CP or LTP batch planning jobs, communication | | between the jobs and the OPC CONTROLLER is disrupted | | resulting in many hard to diagnose problems. Most commonly,| | the OPC CURRENT PLAN EXTEND or REPLAN jobs will run to | | normal completion, an NCP dataset will be successfully | | created, but the OPC CONTROLLER will not automatically take | | the new plan into production until forced to do so via a | | CURRPLAN(NEW) restart of the CONTROLLER. | | Use of BATCHPIPES with these OPC batch planning jobs will | | result in the same sorts of problems. | +--------------------------------------------------------------+ +--------------------------------------------------------------+ | | |TITLE: PLANNING AND SCHEDULING THE WORKLOAD, SH19-4376-01 | | | |CHAPTER: 11 | | | |TOPIC: "Creating and Activating the NCP" | | | | The following text has to be added at the end of the | | paragraph, as a note, after the sentence: | | "As a result, even if the PLAN JOBS run successfully, | | the NCP is not taken into production by the CONTROLLER | | unless a CURRPLAN(NEW) restart is performed." added by | | APAR PQ27179. | | | | BATCH OPTIMIZER utilities such as BMC BATCH OPTIMIZER DATA | | OPTIMIZER and MAINVIEW BATCH OPTIMIZER prevent correct | | communication between the OPC CONTROLLER and CP/LTP BATCH | | PLANNING JOBS. OPC logic depends on an exchange of ENQUEUES | | and REAL-TIME updates of several sequential datasets to pass| | information back and forth between the CONTROLLER STC and | | the CP/LTP BATCH PLANNING JOBS. These optimizers hold I/O | | from the batch jobs until END OF STEP or END OF JOB, then | | preventing the required communication from occurring. | | When these sorts of utilities are allowed to "manage" I/O | | for the OPC CP or LTP batch planning jobs, communication | | between the jobs and the OPC CONTROLLER is disrupted | | resulting in many hard to diagnose problems. Most commonly,| | the OPC CURRENT PLAN EXTEND or REPLAN jobs will run to | | normal completion, an NCP dataset will be successfully | | created, but the OPC CONTROLLER will not automatically take | | the new plan into production until forced to do so via a | | CURRPLAN(NEW) restart of the CONTROLLER. | | Use of BATCHPIPES with these OPC batch planning jobs will | | result in the same sorts of problems. | +--------------------------------------------------------------+ +--------------------------------------------------------------+ | | |TITLE: INSTALLATION GUIDE, SH19-4379-02 | | | |CHAPTER: 1 | | | |TOPIC: "Relationship between TIVOLI OPC and MVS/ESA | | | | The following text has to be added at the end of the | | paragraph: | | | | BATCH OPTIMIZER utilities such as BMC BATCH OPTIMIZER DATA | | OPTIMIZER and MAINVIEW BATCH OPTIMIZER prevent correct | | communication between the OPC CONTROLLER and CP/LTP BATCH | | PLANNING JOBS. OPC logic depends on an exchange of ENQUEUES | | and REAL-TIME updates of several sequential datasets to pass| | information back and forth between the CONTROLLER STC and | | the CP/LTP BATCH PLANNING JOBS. These optimizers hold I/O | | from the batch jobs until END OF STEP or END OF JOB, then | | preventing the required communication from occurring. | | When these sorts of utilities are allowed to "manage" I/O | | for the OPC CP or LTP batch planning jobs, communication | | between the jobs and the OPC CONTROLLER is disrupted | | resulting in many hard to diagnose problems. Most commonly,| | the OPC CURRENT PLAN EXTEND or REPLAN jobs will run to | | normal completion, an NCP dataset will be successfully | | created, but the OPC CONTROLLER will not automatically take | | the new plan into production until forced to do so via a | | CURRPLAN(NEW) restart of the CONTROLLER. | | Use of BATCHPIPES with these OPC batch planning jobs will | | result in the same sorts of problems. | +--------------------------------------------------------------+ +--------------------------------------------------------------+ | | |TITLE: PLANNING AND SCHEDULING THE WORKLOAD, SH19-4376-02 | | | |CHAPTER: 11 | | | |TOPIC: "Creating and Activating the NCP" | | | | The following text has to be added at the end of the | | paragraph, as a note, after the sentence: | | "As a result, even if the PLAN JOBS run successfully, | | the NCP is not taken into production by the CONTROLLER | | unless a CURRPLAN(NEW) restart is performed." added by | | APAR PQ27179. | | | | BATCH OPTIMIZER utilities such as BMC BATCH OPTIMIZER DATA | | OPTIMIZER and MAINVIEW BATCH OPTIMIZER prevent correct | | communication between the OPC CONTROLLER and CP/LTP BATCH | | PLANNING JOBS. OPC logic depends on an exchange of ENQUEUES | | and REAL-TIME updates of several sequential datasets to pass| | information back and forth between the CONTROLLER STC and | | the CP/LTP BATCH PLANNING JOBS. These optimizers hold I/O | | from the batch jobs until END OF STEP or END OF JOB, then | | preventing the required communication from occurring. | | When these sorts of utilities are allowed to "manage" I/O | | for the OPC CP or LTP batch planning jobs, communication | | between the jobs and the OPC CONTROLLER is disrupted | | resulting in many hard to diagnose problems. Most commonly,| | the OPC CURRENT PLAN EXTEND or REPLAN jobs will run to | | normal completion, an NCP dataset will be successfully | | created, but the OPC CONTROLLER will not automatically take | | the new plan into production until forced to do so via a | | CURRPLAN(NEW) restart of the CONTROLLER. | | Use of BATCHPIPES with these OPC batch planning jobs will | | result in the same sorts of problems. | +--------------------------------------------------------------+
Temporary fix
Comments
APAR Information
APAR number
PQ56634
Reported component name
TME 10 OPC V2 R
Reported component ID
5697OPC01
Reported release
302
Status
CLOSED DOC
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2002-01-14
Closed date
2002-01-28
Last modified date
2006-03-13
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
| SH19437900 | SH19437901 | SH19437902 | SH19437600 | SH19437901 |
| SH19437902 |
Fix information
Applicable component levels
[{"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":"302","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
13 March 2006