A SAS Data Integration Studio parallel
iterative job does not indicate failure when an inner loop process fails unless status handling
is defined. This problem occurs because a SAS Data Integration Studio iterative
job that is set to run in parallel spawns a separate SAS session for each iteration of
the loop.
By default, each session, including the calling job, contains its own job status information.
However, none of this information is shared
among processes. As a result, the calling program might indicate that the job completed
successfully even though one or more of the spawned processes failed. The only way
to force the calling job to indicate failure when a spawned process fails is to set
up status handling in the Loop transformation.