This is a result of the way drive letter mappings are managed in Windows. See the Network Access for Jobs help topic for more information.

You should  use UNC paths rather than drive letters. If you don't want to hard-code paths in the batch file, use Job Variables/Environment Variables so you can define the path in adTempus and have the batch file use it.

If you must use a mapped drive letter the mapping has to be done on the Resources tab of the job. But note that this will fail if you try to use a drive letter that's already in use outside adTempus. For example you won't be able to create a mapping for L:. You would need to use a drive letter that's not already mapped.

So... Mapped drives which appear to a program run from the command prompt are invisible to a program run under adTempus. Is that right?

The following script shows several drives mapped when run from a cmd.exe shell. However, the driveMap.length is zero (0) when run under adTempus. Is that what I should expect to see?

===

set wshNetwork = WScript.CreateObject("WScript.Network")
set driveMap = wshNetwork.EnumNetworkDrives

wscript.echo driveMap.length

for i = 0 to (driveMap.length-2) step 2
    wscript.echo "drive letter " & i &" = " & driveMap.item(i+1)

    if (StrComp("\\" & hostname & "\" & sharename, driveMap.item(i+1), 1) = 0) then
        driveletter = driveMap.item(i)
    end if
next

The only drive mappings available to anything you run in adTempus are the mappings that you add on the Resources page of the job. Anything mapped outside of the job does not exist as far as your program is concerned.

Thank you for your help, Bill. I am a bit surprised that I have used adTempus this long and never come to know about this. It is working now.