Re: CA/400 Netware for SAA File Transfer

I tried the STRHOSTSVR trick. I didn't solve the problem so I called
IBM. I described the problem (CA/NT file transfer starts, then a job
with my device name pops up in QCMN and has a message in its job log
which says: PWS0008 - The OS/400 database server cannot be run. CAUSE .
. : Stream fetch is only supported through the QSERVER subsystem.). He
had me disconnect my session on the PC and then at a terminal he had me
do this:

ADDCMNE SBSD(QCMN) DEV(*APPC) DFTUSR(*SYS) MODE(QSERVER) MAXACT(0)

Then vary off the *APPC device for my PC and then vary it back on. Then
the file transfer worked. He said that each *APPC device would need to
be varied off and then back on for this to take effect.

I knew it had to be something like that but I would have never guessed
exactly what to do. Thanks IBM support line!

BTW, I was not using a SAA gateway, I'm using AnyNet.

Mark Welte
Denso Manufacturing Tennessee, Inc.

 ----------
From: Jeffrey M. Carey
To: MIDRANGE-L@midrange.com
Subject: Re: CA/400 Netware for SAA File Transfer
Date: Friday, June 13, 1997 5:29PM

Just a gues, 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.
>
> Thanks,
> Mark Welte
> Denso Manufacturing Tennessee, Inc.
>
>  ----------
> From: Carol.Collins@DOEGJPO.COM
> To: 'midrange-l@midrange.com'; Neely N. Loring
> Subject: Re: CA/400 Netware for SAA File Transfer
> Date: Tuesday, June 10, 1997 11:56AM
>
>      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   *
> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
> umidr
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
*
* 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
*
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
*
umidr
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* 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   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *