SEND messages are incorrectly sent to the TSO ID assigned to the started task , when promotion of certain library types fails and is then attempted again. DBR, MPC and LST are examples. The SEND message is being sent to the ID stamped on ISPF stats in the promotion dataset, which is also listed on the overlay warning screen as shown below
A customer encountered the following abend restarting one of their P-site started tasks after housekeeping had run while the task was down: 04.33.58 S0732751 SER0953E Task abnormally terminated: Comp=S0C7 Function=MASTER/ENDREQ NSI=157296EA 04.34.32 S0732751 IEA995I SYMPTOM DUMP OUTPUT 896
A customer is encountering problems whereby many concurrent compile jobs running for components in the same package become stuck in the SUCCESS step and their associated started task appears to be looping. The started task needs to be stopped and restarted to resolve the error. The started task shows many banks of the following type of error message: 2009/09/28 03:32:39.96
This is usually caused by the execution of the new 7.QC options 2 & 3 from the ERO panels requesting excessive amounts of storage within the started task . That is the following panel options:
