A fix is available
Closed as program error.
In a TDI 7.0 Project with 4 Assembly lines cust is planning to run one AL as a Windows service. If cust stops this service and runs one of the other ALs manually using the TDI GUI, cust is getting a side effect: The AL assigned to the Win service starts every time the cust is running one of the other ALs fronm this project. This is because an AL has to be set as 'Startup Item' in the AutoStart tab of Log & Settings if cust wants to have it running as a Windows service. In our cust's case, AL 1 runs a timer connector in order to start its data flow every two minutes. In this data flow AL2 and AL3 are called. If cust likes to test AL2 or AL3 manually, AL1 is always starting. For testing purpuses, this is not the behavior our cust wants. For testing, there is no advantage of automated starting of an Assembly line in TDI GUI mode. ######## This behavior has been addressed in WI DI01720 BE has provided a test fix Cust has tested this fix successfully APAR created upon request in above WI Regarding the final fix, the BE states: The official fix will be available in 70 FP9. The planned delivery date of this FP is not decided yet. It might be sometime in 1st or 2nd quarter 2013.
testfix \IBM\TDI\V7.0\jars\common\diserverapi.jar Cust tested this fix successfully.
AssemblyLines in the AutoStart folder should not be automatically started when running AssemblyLines from the Config Editor.
This is a bug in the TDI code and has been fixed. The official fix will be made available in 7.0.0-TIV-TDI-FP0009. The fix will also be made available in 7.0.0-TIV-TDI-LA0013.
Reported component name
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
Fixed component ID
Applicable component levels