>(2nd reply, fixed typing error)
>First of all, thanks for your reply, I'm great appreciated.
>
>Let me brief you what actually the requirement in PC site.
>The PC is responsible for one major task only, which is talk to an external device (security PIN pad, a smart card reader) and send the response back to mainframe. The scenario is when mainframe received a payment instruction from their client in EDIFACT format, it need to authenticate the message, so the mainframe will send a so-called digital signature which is derived from the EDIFACT message to PC for verification purposes, and PC will pass the digital signature to the smart card reader, get the response and send back to mainframe. It's on line. The PC program must keep listening to the incomming messages and response it respectively.
>
>The PC will be one of the workstation in their local network (SNA), the mainframe people dictated using 3270 as the communication bridge. They suggested put the string (messages) in a file and transfer the file using 3270 terminal emulation program. This is something back to ten years ago, most important, this method will not solve the problem, and inefficient if it's on line. I've done a project several years ago, using 3270 terminal emulation as a file transfer utility, which is in DOS environment, there are a few utilities come with 3270 for PC, something similar to FTP, there are programs, run directly from DOS prompt, our program have to run the 'command.com' to execute it, and we wouldn't know what's happenning to the process when the control is pass to the external program, the only stupid way is wait for the external program finish, and check the predefined path if any files available.
>

Attachmate is available for the environment; you can use the MVS or VM/CMS tools for handling the transfer, or if you're ambitious, APPC. You can access the AttachMate API, and the last time I looked, there was an ActiveX controla vailable as well.

>Now the smart card reader come only with 32bit DLL for windows. PC program have to be developed using one of the Windows development tools. So is your suggestion?
>

Well, VFP probably isn't thew right tool for the job as you've outlined it, since it isn't data-centric, and it's not as easy to access APIs from VFP. OTOH, API_APPRUN could handle the firing of the command-line tools from within Win9x, so yuou could use that to construct coomand lines and fire them. Much as I'm not a big fan, VB might well be an easier environment to develop the application in, and you'll find more tools readily available.

>
>>>Sorry, this question is not suppose to be here, but I coundn't find it elsewhere, my client is chasing me.
>>>
>>>I'd like to a send a string to IBM mainframe and vice-versa, any idea?
>>>such as:
>>
>>It's going to depend entirely on how you connect the PC to the mainframe (LAN, dial-up, any of several specialized serial conections) the operating system run on the mainframe, and the capability of the software on both the mainframe and PC. One rather ubiquitous package is AttachMate; you might look into that, but regardless, the mainframe site management people will dictate just about everything related to the connection and capabilities their system will support. You need to talk in detail to the client's technical people to determine what they'll let you do and specify the details of the connection.
>>