|
Terry, We have the same device here (only one so far) but have not run into that issue, as they use it for a short time in the AM, and then they are done - so I have not had the worry there. That said, we have a PC running 5250 emulation hooked up to a scanner in the warehouse to do barcode case counts as cases go by on the conveyor, and I did not want the AS/400 to end the job after 3 hours automatically when the line is not running. Try this solution that I worked up - Within my ile/rpg I run the following commands; chgjob brkmsg(*hold) crtdtaq dtaq(qtemp/testdq) maxlen(80) seq(*fifo) ovrdspf file(scanpickdm) dtaq(qtemp/testdq) Then I write the screen record (NOT exfmt) and instead of a read, do a call to qrcvdtaq with the wait parm set low. What does this do for you, you ask. What it does is fake out the AS/400, and I would assume the device, that screen I/O has occurred, thus keeping the session "alive". I then only need the warehouse to sign on the system once per week, as we IPL each Friday night. The change job is to alleviate any messages breaking while the program is running. If you need more code snippets - let me know. But I "think" this might help if no one else can think of a way to accomplish your goal. Mark A. Manske -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Exterior Wood Sent: Sunday, October 12, 2003 8:32 PM To: midrange-l@xxxxxxxxxxxx Subject: Keep alive problems with RF devices This is my 1st post, so it might be a little rough. I am working on a project using a couple of Falcon 325 data terminals made by PSC. I am also use software called Powenet created by ConnectRF that creates the telnet sessions (tn5250e emulation). We are using settings for a Lucent Radio modem. Our system is an Iseries 820 at R5V2. I have had limited success getting adequate help from either PSCnet or ConnectRF, but have discovered through trial and error how to make things work pretty much the way I want. I do know that these devices are used on several AS400's all over the place and supposedly they are quite successful. We currently use several other PSC devices, they just are not RF. My problem is that these devices will not be in constant use but will be expected to work whenever needed. You can log in and go directly to a program, all works fine. If they are not used within a 5 minute period, they time out. When the user comes back it looks like they are still in the program, but the press of any key will take them back to sign on and they must start all over. The people using these devices are in a manufacturing environment, normally using a scanning device, and also wearing fairly heavy gloves. These are not people who are necessarily used to using a keyboard, let alone a fairly small keypad on this type of device. The way this device reacts does not make it very user friendly and will make them not want to use it if the problem cannot be solved satisfactorily. The reason they time out is to conserve battery life, thus if the system was polling them all the time to "keep them alive", the battery would only last about 2 hours. There is supposed to be a server that ConnectRF sells that will take care of this process, obviously for a bunch more money. Has anyone discovered a way that these devices can be kept alive without going to another server and not changing the global keep alive attributes of the AS400. Changing those would cause a whole new problem to something that already works well. I am not real knowledgeable about these devices, so I may not be posing my questions correctly. If you can do a little interpreting and read between the lines, please respond. Any help will be greatly appreciated. Terry Nonamaker Exterior Wood Inc. tnonamaker@xxxxxxxxxxxxxxxx _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
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.