× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: Non-keyable input field
  • From: "Alex A Moore" <alexm@xxxxxxxxxxxxxxxx>
  • Date: Fri, 27 Jul 2001 06:31:33 -0400
  • Importance: Normal

A wedge can be configured to only accept input from the port that the
scanner/bar code reader is attached to.  The better ones even allow you to
conditionally pass the input on to the terminal/PC based on where the input
came from (keyboard or other input port).


Alex

-----Original Message-----
From: owner-midrange-l@midrange.com
[mailto:owner-midrange-l@midrange.com]On Behalf Of Douglas Handy
Sent: Friday, July 27, 2001 12:23 AM
To: MIDRANGE-L@midrange.com
Subject: Re: Non-keyable input field


Mark,

>I would like to know if there is some mechanism that
>would allow barcode entry, but not keyboard entry.

Seems like this would be contingent on how the barcode scanner was attached.
If
it hooks up as a keyboard wedge, it seems unlikely to accomplish.

>  My initial thought was to somehow tap into the badge reader
>capability.  Is that still supported?

Yes, via DSPATR(OID) in the DSPF's DDS.

>If yes, are there any products on
>the market that would make the barcode reader look like a badge reader to
>the system?

I have no idea.

>Does anyone have any other suggestions?

I think it will depend on whether dumb terminals are involved and keyboard
wedges, or whether you can use a PC.  If you can use a PC, then you can make
the
input field protected on the DSPF.  Use a scanner which does not use a
keyboard
wedge, but has a serial port or USB connection or whatever.  Use CA or
whatever
as the foreground task so it gets normal keyboard activity.  Have a PC
program
(eg VB) monitor the bar code scanner, and when it sees a scan have it update
the
display buffer of the emulation session.  All it has to do is stuff the
barcode
data into the right positions in the screen buffer -- the cursor location
does
not matter and the field can be protected.  (I'd put a series of non-display
characters at a known location for a signature check for the VB program to
examine to make sure the proper DSPF format was on the screen.)

When the operator presses Enter, the "protected" field's contents will be
returned to the program.  This is along the lines of how I used to interface
some devices to a S/34 or S/36 by using IBM's DOS-based 5250 emulation and
APIs
to manipulate buffers and automate keystroke processing.  But now it is a
different series of API's used.

Doug

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.