Ben,

There is a switch in the start command that will let you do this. This works in Windows NT and Windows 95. The switch is '/wait' and can be shortened to '/w'. When you specify this switch, windows wait until the command has completed before it starts the next command. Here's a example:

start /w a_batch_file_or_other_program.bat start /w the_next_step_waits_for_the_previous.exe exit

Also, there are some other switches you can specify with start. Enter a 'start /?' at a DOS prompt to see the options.

Hope this helps, Alan

---------- From: Ben Conner[SMTP:ben@WEBWORLDINC.COM] Sent: Monday, October 07, 1996 1:31 PM To: Multiple recipients of list SAS-L Subject: Batch SAS execution in Win 95

Subject: Batch SAS execution in Win 95 To: Multiple recipients of list SAS-L <SAS-L@UGA.CC.UGA.EDU> X-UIDL: 636d1a2576e0319a9fb9369300bf1f94

Hi,

I'm not sure if this is a SAS problem or not, but thought I'd throw it out to the crowd...

I have a batch execution of SAS 6.11 in a Windows 95 environment. After SAS executes the program the batch file continues and relies on the creation of the files produced in the SAS program. Not too complicated.

Problem is when the batch file gets to the SAS step it launches SAS -but continues on immediately- with the batch file(!). Since the next step relies on the completion of the SAS program, the next steps fail as the program hasn't finished yet. Is there something I'm missing in the SAS configuration or perhaps in Win 95?

Thanks much!

--Ben Conner +------------------------------------------------------------------------- -+ + Ben Conner ben@webworldinc.com + + Web World, Inc. (714) 639-0595 voice + + PO Box 6548-107 (714) 744-4825 fax + + Orange, Ca 92863 + +------------------------------------------------------------------------- -+