A fix is available
APAR status
Closed as program error.
Error description
EVJEAC02 should ensure that TWS jobs have the status reset when the controller goes UP or a gateway connects.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All SA z/OS V3R2, V3R3 and V3R4 customers * * using TWS Automation. * **************************************************************** * PROBLEM DESCRIPTION: When a controller is started or a * * domain is reconnected EVJEAC02 should * * process this event and reset TWS status * * values, this does not always occur * * correctly. * **************************************************************** * RECOMMENDATION: * **************************************************************** TWS status values should be reset correctly when required.
Problem conclusion
Rexx routines AOFR1REQ, INGR1IGT, EVJRSACT, AOFRSGST and EVJEAC02 have been changed to ensure the TWS status values are always reset as required. Product documentation is updated as follows: +------ System Automation for z/OS Version 3 Release 2 --------+ | | |PROGRAM NUMBER: 5698-SA3 | | | |TITLE: System Automation for z/OS SC33-8269-04 | | TWS Automation Programmer's Reference and | | Operator's Guide | | | |CHAPTER: 1.0 Introducing TWS Automation | |SECTION: 1.1 Functions of TWS Automation | |SUBSECTION: 1.1.1 Basic Concepts | |TOPIC: 1.1.1.5 Defining Tivoli Workload Scheduler to SA | | z/OS | |SUBTOPIC: 1.1.1.5.1 The TWS Controller | |CHANGE: | | | | Replace the paragraph that starts "If multiple controllers | | are running..." with the following Note: | | | | Note: If multiple controllers are running on the same | | system they must share the same Controller Details (OCS) | | definitions. If more than one OCS policy object is linked | | to the same system the last is used, but the TWS controller | | can be selected by TWS common routines, as described in | | section 3.7.1 TWS Automation Common Routines, using the | | SUBSYS parameter. | | | | | |SUBSECTION: 1.1.2 Support for Multiple TWS Controllers | | | |CHANGE: | | | | Same as above... | | | | | |CHAPTER: 3.0 Programmer's Reference | |SECTION: 3.1 Installing TWS Automation | |SUBSECTION: 3.1.2 Defining System Automation Policy | |TOPIC: 3.1.2.7 Define Controller Details | | | |CHANGE: | | | | Same as above... | | | | | +--------------------------------------------------------------+ +------ System Automation for z/OS Version 3 Release 3 --------+ | | |PROGRAM NUMBER: 5698-SA3 | | | |TITLE: System Automation for z/OS SC34-2579-01 | | TWS Automation Programmer's Reference and | | Operator's Guide | | | |CHAPTER: 1.0 Introducing TWS Automation | |SECTION: 1.1 Functions of TWS Automation | |SUBSECTION: 1.1.1 Basic Concepts | |TOPIC: 1.1.1.5 Defining Tivoli Workload Scheduler to SA | | z/OS | |SUBTOPIC: 1.1.1.5.1 The TWS Controller | |CHANGE: | | | | Replace the paragraph that starts "If multiple controllers | | are running..." with the following Note: | | | | Note: If multiple controllers are running on the same | | system they must share the same Controller Details (OCS) | | definitions. If more than one OCS policy object is linked | | to the same system the last is used, but the TWS controller | | can be selected by TWS common routines, as described in | | section 3.7.1 TWS Automation Common Routines, using the | | SUBSYS parameter. | | | | | |SUBSECTION: 1.1.2 Support for Multiple TWS Controllers | | | |CHANGE: | | | | Same as above... | | | | | |CHAPTER: 3.0 Programmer's Reference | |SECTION: 3.1 Installing TWS Automation | |SUBSECTION: 3.1.2 Defining System Automation Policy | |TOPIC: 3.1.2.7 Define Controller Details | | | |CHANGE: | | | | Same as above... | | | | | +--------------------------------------------------------------+ +------ System Automation for z/OS Version 3 Release 4 --------+ | | |PROGRAM NUMBER: 5698-SA3 | | | |TITLE: System Automation for z/OS SC34-2651-00 | | TWS Automation Programmer's Reference and | | Operator's Guide | | | |CHAPTER: 1.0 Introducing TWS Automation | |SECTION: 1.1 Functions of TWS Automation | |SUBSECTION: 1.1.1 Basic Concepts | |TOPIC: 1.1.1.5 Defining Tivoli Workload Scheduler to SA | | z/OS | |SUBTOPIC: 1.1.1.5.1 The TWS Controller | |CHANGE: | | | | Replace the paragraph that starts "If multiple controllers | | are running..." with the following Note: | | | | Note: If multiple controllers are running on the same | | system they must share the same Controller Details (OCS) | | definitions. If more than one OCS policy object is linked | | to the same system the last is used, but the TWS controller | | can be selected by TWS common routines, as described in | | section 3.7.1 TWS Automation Common Routines, using the | | SUBSYS parameter. | | | | | |SUBSECTION: 1.1.2 Support for Multiple TWS Controllers | | | |CHANGE: | | | | Same as above... | | | | | |CHAPTER: 3.0 Programmer's Reference | |SECTION: 3.1 Installing TWS Automation | |SUBSECTION: 3.1.2 Defining System Automation Policy | |TOPIC: 3.1.2.7 Define Controller Details | | | |CHANGE: | | | | Same as above... | | | | | +--------------------------------------------------------------+
Temporary fix
Comments
APAR Information
APAR number
OA40809
Reported component name
SYSTEM AUTO Z/O
Reported component ID
5698SA300
Reported release
330
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-11-12
Closed date
2012-11-19
Last modified date
2012-12-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UA67251 UA67252 UA67253
Modules/Macros
AOFRSGST AOFR1REQ EVJEAC02 EVJRSACT INGR1IGT
| SC33826904 | SC34257901 | SC34265100 |
Fix information
Fixed component name
SYSTEM AUTO Z/O
Fixed component ID
5698SA300
Applicable component levels
R320 PSY UA67251
UP12/11/21 P F211
R330 PSY UA67252
UP12/11/21 P F211
R340 PSY UA67253
UP12/11/21 P F211
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.
Rate this page:
Average rating
Copyright and trademark information
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.