SAS Data Integration Studio jobs that are executed in batch incorrectly complete with a nonzero return code under the following conditions:

• The job contains a Loop transformation.
• Iterations within the Loop transformation processing are being executed in parallel.
• During code execution at least one sign-on attempt fails, but a subsequent attempt to sign on succeeds.
• The job completes without any errors.

Scheduling tools (for example, Platform LSF, or OS Host Scheduler) interpret this nonzero return code as a job failure. This results in the termination of any remaining processing that depends on successful job completion.

The incorrect return code is caused by the following events:

• When a signon attempt fails, the SYSSC automatic macro variable is set to a nonzero value.

  Note: the SYSCC automatic macro variable contains the condition code that SAS^® returns to the operating system upon job completion and termination.

• When a subsequent attempt to sign on succeeds, the job continues to process. However, SYSCC still contains a nonzero value from the earlier failure. The result is a nonzero job return code.

One workaround for this problem is to insert the following SAS code in the Postcode panel under Job Properties on the Precode and Postcode tab. This code checks the job return code (job_rc) and resets SYSCC to 0 if there were no errors during job execution:

Click the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

A fix for this issue for SAS Data Integration Studio 4.21_M2 is available at: