This session provides practical experience with LANDP's PIN pad support. During the session, you will customize a simple LANDP workgroup consisting of a single workstation attached to a PIN pad device. You will be shown how to perform some basic PIN pad operations.
In this example we will be using an IBM 4778 PIN pad device on a Windows NT platform. Please ensure you have an IBM 4778 PIN pad device attached to your computer's first serial port (COM1).
In order for the LANDP PIN pad server to communicate with the PIN pad device, you need to install the appropriate driver software.
To install the IBM 4778 PIN pad driver, do the following:
Platform | Windows NT/2000/XP | OS/2 | DOS |
Driver to download. | 47nt95dd/47NT95DD.EXE | 47os2dd/47OS2DD.EXE | 47dosdd/4777DD.EXE |
Driver files to copy | WNT78PIN.DLL WNT78MSR.DLL WNT7XPDD.DLL |
FIO.MSG FIOH.MSG FIOSERDD.SYS PINCALLS.DLL PINMSR.DLL |
IBM4778M.SYS IBM4778P.SYS |
Destination |
If you have a DOS or OS/2 workstation, you must also modify the CONFIG.SYS file with an entry for the PIN pad device driver. See Preparing LANDP platforms on page 85 of the LANDP Installation and Customization manual for more information.
In this section the LANDP configuration files are written to specify a LANDP workstation that provides PIN pad services. The steps required during customization are outlined below.
Read more about creating LANDP common definitions.
The table 'Vectors - a quick reference', on page 44 of the LANDP Installation and Customization manual, shows that LANDP does not need any common data for the PINP47## server, but we do need to specify some SOFTPACK vectors for the SVPCPRB program.
SOFTPACK  | PACKNAME=CONFTEST, FILENAME=EHCXLATE.DLL, |
SOFTPACK  | PACKNAME=CONFTEST, FILENAME=SVPCPRBN.EXE, |
SOFTPACK  | PACKNAME=CONFTEST, FILENAME=SVPCPRBN.HLP, |
A brief overview about creating LANDP workgroup definitions is available.
We will specify a single workstation providing PIN pad services in a workgroup called "PINP". We will also specify that the workstation will be used as a client for the PIN pad device.
LANCONF  | NAME=PINP, WSNAMES=(P1) |
LWSCONF | NAME=P1, TYPE=NT, SERVER=(PINP47P1), PAR&PINP=(4778,1,Y), CLIENT=(PINP47P1,P1), SOFTPACK=CONFTEST |
The COMMON.SPC and LANCONF.SPC must now be validated to ensure they have been entered correcly. A brief overview of the validation stage is available, as well as the VALSPEC utility on page 55 of the LANDP Installation and Customization manual.
C:\
CD C:\EHC\EHCCUS\
VALSPEC COMMON
VALSPEC LAN \PINP
Once the configuration has been validated, the LANDP files to be installed on each workstation can now be generated and copied. This is the distribution stage.
GENRUN \PINP
GETTING \PINP WS=P1 C:\PINP\
The LANDP files are now installed in the directory C:\PINP\.
The final stage is to start the LANDP services on the workstations.
CD \PINP
AUTOFBSS
The LANDP services should now have started. To view a list of the running LANDP services, type EHCINFO at the command prompt. You are now ready to begin using the LANDP PIN pad support.
Testing of LANDP servers is done using the SVPCPRB program. For more information on the SVPCPRB program and it's capabilities, see page 107 of the LANDP Programming Guide.
Communication with LANDP services is done by sending CPRB messages. The first message we must send is an IN command to the LANDP Supervisor server.
If the CPRB message was recieved successfully, the Server Return Code shown in the Output panel should read "OK". If the return code is different, refer to the Problem Determination manual for more information.
Next we must open the PIN pad for use by our client. This is done by sending an OP message to the PIN pad server:
The next step is to arm the PIN pad for reading from the keypad. This is done as follows. The N flag means you are arming the PIN pad in non-encrypted mode. There are many different ways to arm the PIN pad. See the LANDP Programming Reference for more information.
Once the PIN pad is armed, an arrow will appear on the display. Enter a 5 digit number on the keypad and press END.
To read the information entered into the PIN pad, the RD command is used. Issue an RD to the PIN pad server as follows:
The result of the RD command will appear in the reply data area.
Once you have finished with the PIN pad server, you must issue a CL command to close the device. Issue a CL command as follows:
Model 1 and model 3 PIN pads have a magnetic card reader built in to them. The PIN pad server allows you to make use of this functionality.
To read a magnetic card using the PIN pad, send an OP command to open the PIN pad server for mag-stripe use as follows:
Now arm the PIN pad for reading a magnetic card as follows. An arrow will appear on the display indicating that a card should be swiped.
Swipe a magnetic card through the card slot. The MSRE server hands on is useful for creating a suitable card for this example. If the swipe was successful the arrow on the display will disappear.
To read the data read from the magnetic card, issue a RD command as follows:
The KL command is useful if you arm the device and want to cancel the operation without typing on the key pad or swiping a magnetic card. A KL command is sent as follows:
You can write messages to the PIN pad display using the WD command. First open the PIN pad device for use of the keypad using the OP command, and issue a WD command as follows:
The specified message will be displayed on the PIN pad LCD display. Finally, close the PIN pad using the CL command.
The parameters of the PIN pad device can be read or set using the DV command. For more information about this function, see page 223 of the LANDP Programming Reference.
Open the PIN pad for use of the keypad using the OP command as before, and send a DV to read the device parameters as follows:
The result, placed in the reply data area, is numerical, and should be read by pressing the HEX button to the right of the SVPCPRB window. The meaning of the parameter block is explained on page 236 of the LANDP Programming Reference.
When you have finished with LANDP and the PIN pad server, issue a CL command to the PIN pad server to close the device, and issue an EJ command to disconnect from LANDP as follows: