1)   Workorder - noted that order of cars on the Workorder was not the same on the subsequent Train-Consist ("switchlist")

One issue was that the program had an assumption of "one Yd yard".  If the train was at another Yd yard, the Workorder would be blocked in the context of the train's location, rather than the Workorder's location.   Now the workorder "knows" that the train may be at another Yd yard.

Another issue was the circumstances under which the yard-pickups were blocked; now pickups are blocked properly.

2)  Changing the conductor for a train - from the "Preview" train consist.

The issue was an interaction with the locomotive consist number.   Conductor data is now save properly.

3)  Annulled trains - at the Daily Summary are now reset properly.   

4)  For trains run "job extra", the symbol is reset properly.

5)  Train consist - ordering of blocks-of-cars after reporting at a new location were being flipped.   This has to do with train-consists printed (post caboose) style, in locomotive -> EOT (caboose) order.   The "classification" routines now know to classify the cars remaining in the train in "locomotive -> caboose" order.

6)  "Held setoffs"    When a train is reported at a Yd yard there is an option to hold the setoffs to be worked later, allowing the train to advance immediately.   (This is different from the "Hold train" option.)   The noted problem was that not all cars in the setoff block would appear on the subsequent Cut List.

There were 3 issues: cars re-assigned to the same train, cars that would be assigned to a (local service train that had run) and cars with no valid route of any sort - cars with no routing of some sort would be not assigned to the cut-list data.    The cutlist needed a valid routing for assignment.

The first case - assigned to same train - required a minor change.

The second case - local service train has run - required a significant modification, in that the cars are now assigned as extra cars to the local service train - a routing is now found.   This change affects both Held Setoffs and >and< any car that would be assigned to a local service train that has run.   

The third case - no valid routing of any sort - the car is assigned to the Cut List data as a "Held" car (no ConnXns) for the yardmaster to figure out what to do.

                        Jim