Hi All,
Thanks for the inputs. No TCP/IP or UDP protocols. I understand it is PEER to PEER.
The network setup in OS2 Warp currently is - " the batch system will generate a INI file in
Server which will have the Master terminal id, corresponding slave terminal id, Port number,
Device number .
Using this INI file, we can now get the common port number which is used by both Master and
Slave.
But as i said earlier, only MASTER will have the biometric device connected directly via the port.
Our main application will reside in the SERVER, which has to read the details from device.
But if SLAVE terminal requests to access the biometric device connected in MASTER via common
port, we couldn't get the response. We are struck here.
Is there any command by which From Slave terminal we can trigger directly the port number of
Master terminal?
or What are the questions which we need to understand from networking perspective and post to
the client SME's?
Appreciate your help on the above.
Thanks
Rajasekaran
Thanks for the inputs. No TCP/IP or UDP protocols. I understand it is PEER to PEER.
The network setup in OS2 Warp currently is - " the batch system will generate a INI file in
Server which will have the Master terminal id, corresponding slave terminal id, Port number,
Device number .
Using this INI file, we can now get the common port number which is used by both Master and
Slave.
But as i said earlier, only MASTER will have the biometric device connected directly via the port.
Our main application will reside in the SERVER, which has to read the details from device.
But if SLAVE terminal requests to access the biometric device connected in MASTER via common
port, we couldn't get the response. We are struck here.
Is there any command by which From Slave terminal we can trigger directly the port number of
Master terminal?
or What are the questions which we need to understand from networking perspective and post to
the client SME's?
Appreciate your help on the above.
Thanks
Rajasekaran