• Welcome to OS2World OLD-STATIC-BACKUP Forum.
 

News:

This is an old OS2World backup forum for reference only. IT IS READ ONLY!!!

If you need help with OS/2 - eComStation visit http://www.os2world.com/forum

Main Menu
Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - rajases6

#1
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


#2
Hi,

An external biometric device is connected to a terminal.
Another terminal which is not connected to this external bio device

tries to read this device using commom port.

Case:
The Application is triggered using the below 2 Arguments and

application's logic is to read the bio device.

1. Terminal id
2. Teller id



Relationship between Master and Slave terminal ids with port and device
type is captured in a INI file.<br>

Master will be connected to bio device and the application reads the
information. This case is working fine. <br>
Slave will also try to access the bio device connected in corresponding
Master terminal id. This is not working. <br>


In what ways, we can make the slave to access the device.
Please give the correct steps we need to change or how to make this
scenario work modifying any files in OS2 Warp server?

Thanks
Rajasekaran
#3
Hi,

An external biometric device is connected to a terminal.
Another terminal which is not connected to this external bio device tries to read this device using commom port.

Case:
The Application is triggered using the below 2 Arguments and application's logic is to read the bio device.

1. Terminal id
2. Teller id



Relationship between Master and Slave terminal ids with port and device
type is captured in a INI file.<br>

Master will be connected to bio device and the application reads the
information. This case is working fine. <br>
Slave will also try to access the bio device connected in corresponding
Master terminal id. This is not working. <br>


In what ways, we can make the slave to access the device.
Please give the correct steps we need to change or how to make this scenario work modifying any files in OS2 Warp server?

Thanks
Rajasekaran