Originally posted by: SystemAdmin

Windows Server 2003
Mercator 6.7.1

Does anyone have any idea why a program (Expedite Base for Windows)
that runs fine when called from a batch script called from a map rule
in Mercator map running under the Event Server under Windows NT on
old hardware fails to even execute under Windows Server 2003 on
newer, much faster hardware. All pieces work independently. That
is, I can execute the map, the script, or the external program and,
in each case, connect to GXS successfully. But the external program
fails to even execute under the Event Server on the new system.

I have confirmed that the .MSD, .ini, .bat, .mmc files are identical
on both the old & new systems.

Map rule call:
GET("BAT", "C:\expedite_out\ExpediteOUT.bat " + Generic Field [1]:SendToVan )

ExpediteOUT.bat Batch Script: (The called map fails as IF2 is missing due to the
failure of iebase.exe to execute.)

@ECHO OFF


 cd\expedite_out


 iebase.exe


 C:\Mercator6.7\mercnt.exe C:\IAA_EDI\VAN_CommMaps\StatChk_ReformatOUT.mmc -IF1 C:\CommMgr_MailOUT\Mail_out.new -IF2 C:\expedite_out\baseout.msg -B


 move baseout.msg c:\ExpediteTrace\PUT\PUT_%1.txt


 Echo Complete

The batch trace file:
Mercator Batch File Adapter, Version 6.7(306)
Copyright © 1997-2000, TSI International Software, DBA Mercator Software
Built for WIN32 - INTEL on Jun 25 2003 at 20:38:31 by bocabuild.
Retry Count is 0. Retry Interval is 0. OnFailure is Rollback.
Fetch Unit is 0. Card Mode is Integral.
Will process 9 bytes of data.
Run Started at 13:21:49.387 on 07/11/08.
Options used: cmd,trace,name
Poll Count is 0. Timeout Interval is 0.
Will receive data from standard output pipe.
Executing Command: C:\expedite_out\ExpediteOUT.bat
Window Style is SW_HIDE (0).
Getting standard input handle.
Standard input handle is 000003b8.
Process 1852 Created.
Reading from Standard Error...
stdin reading is being processed by thread 3800.
...0 bytes read from Standard Error.
Reading from Standard Output...
...282 bytes read from Standard Output.
Reading from Standard Error...
...0 bytes read from Standard Error.
Reading from Standard Output...
...0 bytes read from Standard Output.
Reading from Standard Error...
...44 bytes read from Standard Error.
Reading from Standard Output...
...111 bytes read from Standard Output.
Reading from Standard Error...
...0 bytes read from Standard Error.
Reading from Standard Output...
Command Executed Successfully.
Read 393 bytes from standard output pipe.
Run Completed at 13:21:51.902 on 07/11/08.
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: GerryCullen

Thoughts:

• Is C:\Mercator6.7 in your PATH?
• Are you running from a single hard drive? That is, will there be any problems with doing a "cd" if you're on a separate drive that would be resolved using a "pushd" instead.
• You might try using something like this for your batch file to see if you can capture any more details. In your case, the results will be in %TEMP%\ExpediteOUT.log.

@echo off
set LOGFILE=%temp%\%~n0.log
echo %0: %date% %time%: Start: Current directory is %CD% > %LOGFILE% 2>&1
PATH >> %LOGFILE% 2>&1
cd\expedite_out >> %LOGFILE% 2>&1
iebase.exe >> %LOGFILE% 2>&1
C:\Mercator6.7\mercnt.exe C:\IAA_EDI\VAN_CommMaps\StatChk_ReformatOUT.mmc -IF1 C:\CommMgr_MailOUT\Mail_out.new -IF2 C:\expedite_out\baseout.msg -B >> %LOGFILE% 2>&1
move baseout.msg c:\ExpediteTrace\PUT\PUT_%1.txt >> %LOGFILE% 2>&1
echo %0: %date% %time%: Complete >> %LOGFILE% 2>&1
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: SystemAdmin

Thanks, Jerry. You got me pointed in the right direction. I suspected a Path issue but failed to find it. I elaborated on your debugging code and trapped the return codes which helped. It turns out that when Expedite Base for Windows installs, it creates a local PATH variable to a directory containing some required DLLs. Unfortunately, this wasn't documented in the installation instructions in the Expedite Base for Windows Programmer's Guide as far as I could tell.

Since the Mercator Event Server is running as a system service under a User ID different from that used to install the software, the iebase.exe program failed and Windows reported an ErrorLevel 128. In discussions with GXS Support, the TSR pointed out the required PATH variable.

I resolved the missing path issue by right-clicking on My Computer and selecting Properties->Advanced->Environmental Variables and adding the required path under System Variables. Now any user an execute iebase.exe succesfully including the Mercator Event Server.

Thanks again, Jim
#DataExchange
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender

Originally posted by: janhess

Jim,
I didn't think 6.7.1 was certified for Windows 2003 server. Does everything run ok?
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: SystemAdmin

So far most things work. I have one issue remaining but I believe it's a data issue uand that the process and maps are working as expected. I hadn't considered whether or not 6.7.1 was certified for Windows 2003 Server. I hope it is not an issue. A move to 8.2 is the next step. I had wanted to move directly to 8.2 but it was thought the move to the new hardware/OS platform would be an easy and riskless first step and I didn't disagree. It's turned out to be more work than thought and perhaps the effort might have been better made working on the 8.2 upgrade.
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange