🚀 go-pugleaf

I have just finished setting up SAA v2 and Hostprint v1.1 and it works ok. 


I did have problems similar to yours initially.  I was trying to get the
SAA server (running Netware 4.1) to reference bindery print queues on an
existing Netware 3.11 server.  Basically I could not get this config to
work at all.  When I created NDS print queues on the SAA gateway server it
worked fine.

Our SAA gateway is setup to run through a Token Ring card.  The mainframe
is connected to another ring and comms are established using source route
bridging.  I don't know what a SLU problem is, so cannot help there.

Hope this helps.  Email me if you want further info.

Mark Fuller
Communications Analyst
BHP Iron Ore

M. Paradise <terror@newrock.com> wrote in article
<320FD01C.7270@newrock.com>...
> Cliff Jones wrote:
> > 
> > Problem
> > I'm having problems with SAA 2.0 and Hostprint 1.1. The mainframe side
> > cannot send jobs to the print queues I've established.
> > 
> > Symptoms
> > The SAA gatetway runs properly.  Hostprint NLM runs properly.  The SAA
> > gateway shows the dedicated LUs connected to the mainframe, but no
> > print jobs. The mainframe folks says it a "SLU" problems meaning the
> > their side is has communications problems with the SAA gateway. Has
> > anyone else experienced these types of problems ??  Can anyone else
> > shared their SAA hostprint installation experiences ???? A sample
> > profiles of an active server with SAA gateway and Hostprint would be
> > veryyyy helpful.
> > 
> > CJ
> 
> Haven't loaded them up yet but we where told that there is a major
problem getting 
> SAA2.0 to work with HOSTPRT1.x.  Our contractors tell us that we must
upgrade to the 
> latest version of HOSTPRT.  Don't know what that is off hand but we are
in the budget 
> battles trying to get the upgrade.
> 
> MP
>