× 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: lp5250d problem?
  • From: Jose <jsanchez@xxxxxxxxxxxxx>
  • Date: Wed, 09 Aug 2000 21:53:44 -0700
  • Organization: I ain't got no stinkin' organization!

Sean Porterfield wrote:

Hello Sean,

> Maybe I don't understand your question, but why not just assign each terminal 
>to
> a specific AS/400 workstation?  Then you'll always know which is which.
> I prefer this to using the random virtual devices - when a user is having a
> problem, I already know which terminal to look at.

Well, I'm not much of an AS/400 guy, but apparently the solutiong was to change 
the
subsystem to something called STORES and to disallow logins for certain times. 
What
happens then is that if tn5250 is run, all they get is a blinking cursor on the
upper left hand corner and the 5250 string plus 001/001 at the lower right hand
corner. Pressing enter gives a message of "Assertion failed" and exits the 
tn5250
program.

Now to another question: I was able to solve my problem of printing to a Win9x
system by using pdq for the local printer (/dev/lp0) and lpr for the SMB 
printer.
This works great, as long as you're in the same subnetwork. For example, our 
AS/400
has an IP addy of 10.100.10.1, whereas our test Linux box has an address of
10.100.10.6. 10.100.10.5 is the Win9x box that has a printer (RPT0000) while the
local printer on the Linux box is APP0000. We also have a Linux box at 
10.100.57.2
(LOC0057) and another Win9x box at 10.100.57.1 (DRJ0057), which connect to the
AS/400 via a leased line using two Cisco 16xx routers. Connecting the 3151's at
LOC0057 to the AS/400 is not a problem, and neither is trying to create new 
printing
devices (RPT0057 and APP0057) But when we send something to lp5250d, nothing 
prints
out. Today, due to other problems at DRJ0057, I was not able to run a 
tracefile, but
I'm thinking that maybe I need some other program to be able to remotely print 
at
LOC0057 from the AS/400?

Any help would be greatly appreciated. Again, using tn5250/lp5250d 0.15.8. The
command I'm issuing are: /usr/local/bin/lp5250d -s RPT0057 -T '*EPLX810' -P
'/usr/local/bin/scs2ascii | lpr' 10.100.10.1 and a similar one with '-s 
APP0057' and
'| pdq' replaced accordingly.

Once again, thanks in advance...

Jose S.

+---
| This is the LINUX5250 Mailing List!
| To submit a new message, send your mail to LINUX5250@midrange.com.
| To subscribe to this list send email to LINUX5250-SUB@midrange.com.
| To unsubscribe from this list send email to LINUX5250-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 ...

Follow-Ups:
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.