APAR status
Closed as fixed if next.
Error description
When a TWSz-scheduled job defined with SUBMIT=NO is submitted outside of TWSz, it may be incorrectly tracked twice, against two separate scheduled occurrences, under the following conditions: 1. An occurrence of the application containing this job is in the current plan in READY status 2. A CP EXTEND process starts 3. While the CP EXTEND is running, the job is submitted. 4. The CP EXTEND adds another occurrence of the same application with a LATEST START TIME *EARLIER* than the pre-existing occurrence. 5. The original application occurrence must not complete before the new current plan is brought into production. When this happens, the job is tracked "real time" against the originally scheduled occurrence, allowing that operation's SUCCESSORS to start. But then, when the new plan is brought into production and is brought up to date by applying the updates logged in the JTLogs while the CP was being created, the re- apply of JT events incorrectly associates the job with the NEWLY SCHEDULED occurrence. . The problem can be avoided by making certain that the LATEST START TIMES for operations tracking externally submitted jobs are always in INPUT ARRIVAL sequence. This can most easily be accomplished by assigning a valid operation-level deadline to the operation. . JT REAPPLY TURNOVER CATCHUP This problem is being addressed in APAR PM77745
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: ALL TWS for z/OS USERs * * FUNCTION=MCP * **************************************************************** * PROBLEM DESCRIPTION: Externally submitted job incorrectly * * tracked in particular situation * **************************************************************** * RECOMMENDATION: APPLY THE PTF FIXING THIS APAR * **************************************************************** Following is the scenario: 1. Add to the CP an occurrence for an application having an operation in Ready/Arriving status with submit=NO and an externally submit job. 2. Run an EXTEND of the plan for one day so that another occurrence of the same application will be added but with the affected operation having a Latest Start Time earlier of the already present one and being in Ready/Arriving status as well 3. While the CP extend is running, but before the new occurrence will be added, submit the external job The original operation must not complete before the new current plan is brought into production (job event split in turnover phase) 4. At turnover phase the processing for the first operation will be blocked and all the events will apply to the new added operation that will be completed.
Problem conclusion
Temporary fix
Comments
The problem was due to the fact that the IJ1 (submit event) is missing for job externally submitted. The IJ1 event contains the key needed to do the match to the operation in the plan to start. Since it is missing the operation chosen is that having the earlier latest start time. In this scenario a new occurrence is generated in the plan while the first occurrence started. Internally a new DOA is generated and put at the head of the DOA chain since it has an earlier Latest Start Time At the turnover phase all events are reapplied to this new DOA since it is the first in the chain The problem can be fixed handling a new trl record that substitutes the missing IJ1 and that indicates which occurrence the A1/B1 event is tracked against.
APAR Information
APAR number
PM56377
Reported component name
TIV WRKLD SCHD
Reported component ID
5697WSZ01
Reported release
512
Status
CLOSED FIN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2012-01-19
Closed date
2012-01-30
Last modified date
2016-04-22
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
R512 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":"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:
22 April 2016