Fwd: CA/400 Netware for SAA File Transfer

Howdie! 

I found the following answer to a previous post in my extensive mail
backlog today and figured I would post it to the list even though it is
old - just in case someone needs the information.  

<cut some extraneous text> 

The netware fixes are documented in SA56403.  Netware fixed it in all
versions of 2.x.  They hardcoded the mode name in 2.0 and 2.1.  2.2 will
actually allow you to configure a mode.  This fix just became available
and is not on their web site yet. 

There are several documents on the web plus 2 info apars that all
reference this apar.  One document talks about other reasons why QCMN
may capture the mode description. 

<cut some extraneous text and routing> 

A few people have problems with this.  Most times it is fixed by doing
the subsystem startup items listed in the attached notes.  Netware users
have been different though.  Only the most recent version of Netware,
and fix packs for older versions of Netware, allow mode configuration
for QSERVER.  Older versions allowed you to configure QSERVER, but they
just ignored it and continued to use QPCSUPP mode.  Obviously, by
default, this would not route the job correctly.  These users would have
to get the fix from IBM Netware folks, apply it, delete the controllers,
and retry the operation. 

 >Date: Fri, 13 Jun 1997 16:29:59 -0500 
 >From: "Jeffrey M. Carey" <jeffreycarey@usa.net> 
 >Organization: Trase Miller Vacations 
 >To: MIDRANGE-L@midrange.com 
 >Subject: Re: CA/400 Netware for SAA File Transfer 

>Just a guess, but try manually doing STRHOSTSVR.  Sometimes  
>the server programs will crash (there is a PTF that seems to  
>fix this - it was an authority issue, we just applied them a  
>few weeks ago, but I don't have the numbers handy). 


 Mark Welte wrote: 
 > 
 > I'm having a similar problem with CA/400 V3R1M2 using file transfer. I'm 
 > using the Netsoft router as well but am connecting to the AS/400 via 
 > AnyNet. We have three machines (320, 40S, 200). The 40S and 200 came 
 > shipped with V3R7 and V3R1 respectively and they work fine. I only get 
 > the message when doing a file transfer with the 320. It was upgraded 
 > from a E70 which used to be a B70. 
 > 
 > I called IBM and they suggested a few things that got the 200 working 
 > (we changed the start of QCMN to be after the start of QSERVER) but have 
 > not been effective on the 320. We have QSERVER started and it starts 
 > before QCMN. We changed the line description of the ethernet controller 
 > to be varied off at IPL and then varied it on manually in the QSTRUP 
 > program. We even added a 30 delay between the start of QSERVER and QCMN. 
 > None of these things have gotten rid of the message that you mentioned. 
 > Any help somone can give me on this will be greatly appreciated. 


 > 
 >      Neely wrote: 
 > 
 >      >Has anyone had problems with downloading a file from the 400 via 
 >      >CA/400 V3R1M2 using NetWare for SAA as the connectivity? 
 > 
 >      >Please advise.  I have the latest service pack loaded. 
 > 
 >      Now that you mention it . . . 
 > 
 >      I have just installed CA/400 V3R1M2 (also using NetWare for SAA), 
 > and 
 >      I'm experimenting with it.  I get the initial library list, but 
 > when I 
 >      browse for a file name to download, it goes out to lunch.  On the 
 >      AS/400 side, the job log says: 
 > 
 >      "PWS0008 - The OS/400 database server cannot be run.  Cause . . : 
 >      Stream fetch is only supported through the Qserver subsystem. " 
 > 
 >      This could be a problem.  Using NetWare for SAA means we use the 
 > QCMN 
 >      subsystem instead of QSERVER.  I don't even have QSERVER active. 
 > 
 >      I'm not sure how to fix this. 
 > 
 >        -- Carol 
 > 









* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *