Date:         Mon, 17 May 2004 13:57:52 -0400
Reply-To:     "Richard A. DeVenezia" <radevenz@IX.NETCOM.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         "Richard A. DeVenezia" <radevenz@IX.NETCOM.COM>
Subject:      Re: Executing external DOS programs with %sysexec

Doug Rohde wrote:
>snip
> The problem is that my DOS shell screen seems to briefly flash on the
> screen, but disappears right away, and I can't see what's happening.
>snip

You can try redirecting STDOUT and STDIN (if bcp uses them).  Also if bcp
has a -option for debugging/diagnostics/logging, use that also.
%sysexec (dos-command 2>stderr.log >stdout.log)

stderr example, in cmd windows:
> dir /_beef_to_fish_ 2>err.log
> type err.log

Worst case, write a batch file with a pause command at the end, and sysexec
the batch file.
If bcp forks itself off into another process, this trick doesn't work.

You might want to invoke bcp via that START nt command.  Why ? Start lets
you set the priority of what gets started.

--
Richard A. DeVenezia
http://www.devenezia.com/downloads/sas/samples