When the WFL job reinitiates a task, some of the physical files used by the new task might reflect changes made by the old task before the halt/load. When designing a program that is to be initiated by a WFL job, you must plan ahead for this possibility and provide a way for the program to produce appropriate audit trails.

A WFL task that opens a remote file might not be able to do so after a halt/load. Normally, a task equation such as the following is used to enable a WFL task to open a remote file:

RUN OBJECT/PROG;
   STATIONNAME = #MYSELF(SOURCENAME);

This task equation directs the task to open any remote files at the station that initiated the WFL job. However, the requested station might not exist after a halt/load. This is the case, for example, if the job was initiated from a pseudostation, such as a Command and Edit (CANDE) dialogue opened through the Transaction Server. This pseudostation is discarded during a halt/load and is not reestablished until you log on to the same CANDE dialogue again. The task terminates abnormally if it attempts to open a remote file at a nonexistent pseudostation.