On Tue, 21 Aug 2007 21:09:43 +0200, Chris Aide <(E-Mail Removed)>
wrote:
>foxidrive schrieb:
>> On Tue, 21 Aug 2007 12:33:51 +0200, Christopher Aide
>> <(E-Mail Removed)> wrote:
>>
>>> we are running a couple of batch files, that start cobol-programs (cobol
>>> = an old programing language). If the cobol program has a problem, it
>>> stops (closing the cobol window) and presents "errorlevel 1" or
>>> "errorlevel 255" to the batch file. The batch file then takes
>>> appropriate actions.
>>> If the program runs through without error, „errorlevel 0“ is presented
>>> to the batch file, ... all just as it should be!!
>>>
>>> Now our problem:
>>> When running the same batch-file on our Win2k-TerminalServer, the return
>>> value of the very same cobol-program is always „errorlevel 0“, even if
>>> the cobol program had to exit because of an error!! This of course
>>> results in our batch files not working correctly!
>>>
>>> It would be nice to hear your thoughts on this subject!
>>>
>>> Thanks in advance
>>
>> Different OS use different ways of setting 'stuff'
>> We'd need to see the code in question...
>>
>
>Hi foxidrive,
>
>thanks for answering. Would it perhaps be possible, to copy cmd.exe from
>our Win2003-Server to the Win200-TS-Server, would that work?
>
>Or: is there any other cmd.exe/dos -version I could download and install
>on our TS-Server in hopes that that new version might start presenting
>errorlevels again?
Actually I assumed it was a prior OS - I didn't cotton to the fact that you
were using W2003 ok and it didn't work in W2K.
You can try using the cmd.exe from W2003, it shouldn't hurt. Dunno if
it'll do any good though as it may be a problem with missing external
command instead.
Seeing the code is the way to tell why it fails...
|
Similar Threads
