Jobs in a flow are executed sequentially to support logging of individual job execution statuses to the .status file. Job #2 does not run until Job #1 finishes.
Note: This is not true for MVS, where jobs are submitted asynchronously.

For all operating systems, successive jobs are not dependent on the error code of the previous job. Flows that are scheduled to run in the past are not scheduled.

Test your job command lines prior to scheduling them. For example, bad syntax in a job command on Windows causes a dialog box to display on an ‘invisible’ desktop of the target system and wait for a response from the user of the server. Then the job suspends, and someone with appropriate authority has to manually kill the cmd.exe process that is running the script on the machine, in order to stop the hung script.

For more information, see the SAS 9.1.3 Intelligence Platform: System Administration Guide online document at:
http://support.sas.com/onlinedoc/913/getDoc/en/bisag.hlp/a003144725.htm

Operating System and Release Information