On Wed, 4 Oct 2006 05:28:22 -0400, ben.powell@CLA.CO.UK wrote:

>Thanks for the suggestions - I've resorted to proc printto for this >particular case. Will look again if logs become an issue. > >Rgds, > >Ben.

Ben

It may be too late, but I just spotted a note that seems relevant. On some regular housekeeping run initiated by desktop services/administrators

'\\SIM0130\LONDON$\SMSPKG\SGS00931' CMD.EXE was started with the above path as the current directory. UNC paths are not supported. Defaulting to Windows directory.

C:\WINDOWS>"C:\Program Files\Desktop inventory scanner\DTv9w32.exe"

It may be you were starting batch sas in a window addressed by the server name rather than by a drive letter.

That sounds like it may be a significant restriction on our assumptions about start-up folders

Good Luck

Peter