× 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: CA/400 Netware for SAA File Transfer
  • From: Neil Palmer <NPalmer@xxxxxxxxxxx>
  • Date: Tue, 10 Jun 1997 20:13:14 -0400
  • Organization: NxTrend Technology - Canada

Carol Collins wrote:
> 
> 
>      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,

To expand a little on my previous reply (start the QSERVER subsystem):



Item SA56403

  APAR Identifier ...... SA56403       Last Changed..97/02/05  
  CA400WINOPT INCORROUT- MSGCWBD0053 CWBDB0048 DATA TRANSFER ERROR
  WHEN USING NOVELL SAA GATEWAY OR SNA SERVER
 
  Symptom ...... IN INCORROUT         Status ........... CLOSED  PRS
  Severity ................... 2      Date Closed ......... 96/08/19
  Component .......... 5763XD100      Duplicate of ........
  Reported Release ......... 310      Fixed Release ............
  Component Name 5763 CA400 WIN       Special Notice
  Current Target Date ..96/08/22      Flags
  SCP ...................
  Platform ............
 
  Status Detail: APARCLOSURE - APAR is being closed.
 
  PE PTF List:
 
  PTF List:
 
 
  Parent APAR:
  Child APAR list:
 
 
  ERROR DESCRIPTION:
  Windows 95 Client Access Data Transfer will fail when
  the job is run in any subsystem other then QSERVER.
  The user is able to retrieve a list of libraries
  but queries and table or field catalog requests fail.
  The PC receives the error:
  MSGCWBDB0053 - Communication error received
                 during processing (System).
  MSGCWBDB0048 - Server returned general error
  AS/400 joblog would show (depending on version and PTF):
   MSGPWS0010 or MSGPWS0008
   MSGMCH3601 Pointer not set to location referenced
   MSGCPF9999 Function Check. MCH3601 unmonitored by QZDASQL
              at statement *N and instruction X'078B'
   MSGPWS0005 Error occured in OS/400 Database Server Code.
 
   Comm Trace shows that AS/400 is sending FMH -7 when a
   Stream Fetch Request is received by the Database Server.
 
   The Database server has two entry points for SNA
   attached devices: An ICF file based program allocated
   when the attach occurs on a session bound to mode
   description QPCSUPP (or other);  The QZDAINIT job
   allocated when the session is bound to mode description
   QSERVER.  The ICF file interface does not support
   the Database Server Stream Fetch operation used
   by Data transfer.  Any such job will fail.
 
   This error is usually seen on PCs connected via
   Mircosoft NT SNA server or Novell SAA.  By default,
   both connection types use QPCSUPP mode and not QSERVER.
 
 
 
  LOCAL FIX:
   If you are NOT running over SAA or SNA gateway and are still
   receiving similar error, a QSERVER mode description needs to
   be created on the AS/400. A QSERVER modd may be created using
   this command:
 
     CRTMODD MODD(QSERVER) MAXSSN(64) MAXCNV(64) INDTACPR(*LZ10)
              OUTDTACPR(*LZ10) TEXT('QSERVER MODD FOR CA/400')
 
 
   When running under SAA or SNA gateway a QSERVER modd needs
   to be created on the gateway as well.
 
   Novell SAA 2.x users require a fix from Novell SAA
   support.
 
   For a SNA server before you can configure a mode you may need
   to assign a Local APPC LU to a server and then associate the
   QSERVER mode for both local and remote APPC LU.
 
   Consult appropriate documentation to create a QSERVER modd
   on the server/gateway.
 
 
 
 
  PROBLEM SUMMARY:
   Under Windows 95 Client Access Data Transfer will fail when
   the job is running under QCMN subsystem and/or using QPCSUPP
   mode description. An ICF file interface is used to process
   such jobs. But under ICF file interface Stream Fetch requests
   are not supported. So, any such data transfer job would
   fail.
   When PC is connected via SAA or SNA server data transfer
   job uses QPCSUPP mode and runs under QCMN. For SAA 2.0
   PC would generate this error: "CWBDB0053-Communication error
   received during processing (System)."
   AS/400 joblog would show:
     MCH3601 Pointer not set to location referenced
     CPF9999 Function Check. MCH3601 unmonitored by QZDASQL  at s
             statement *N and instruction X'078B'
   Comm Trace would show  that AS/400 is sending FMH -7 when a
   Stream Fetch Request is received by the SQL Server.
   Similar error messages may also be encountered when running
   through a MS SNA Server.
 
 
 
  PROBLEM CONCLUSION:
  In order to run Data Transfer, the QSERVER mode description
  must be defined in the PC "router", the AS/400, and any
  APPN node on the network that may route the BIND.
  If the mode description QSERVER does not exist on
  the AS/400, one may be created using this command:
 
    CRTMODD MODD(QSERVER) MAXSSN(64) MAXCNV(64) INDTACPR(*LZ10)
             OUTDTACPR(*LZ10) TEXT('QSERVER MODD FOR CA/400')
 
  When running under a Netware for SAA or Microsoft SNA gateway a
  QSERVER mode description needs to be created on the gateway as
  well.
 
  Netware for SAA requires a fix to properly handle the
  QSERVER mode.  Contact Novell SAA support, apar JR09091
  for further details.
  The Novell SAA BBS number are: 919-254-6231 and 919-254-6306.
  The Web page is www.networking.ibm.com/nsa/nsamain.htm.
  The individual fixes are:
   D347-20.ZIP ; Fixes SAA 2.0 *** MUST HAVE SAA030 APPLIED ***
   D347-21.ZIP ; Fixes SAA 2.1 ( AS/400 Edition )
   D347-22.ZIP ; Fixes SAA 2.2
 
  The fixpacks are/will be:
    SAA20032 2.0
    SAA21010 2.1
    SAA22010 2.2
  Please note that you MUST be running Novell SAA 2.0 or later.
 
  Microsoft SNA Server:
  See the SNA Server Aministration Guide, "Configuring
  Modes for LU-LU Pairs", for instructions on how to
  configure new mode descriptions.
  You may need to assign a Local APPC LU to a server and then
  associate the QSERVER mode for both local and remote APPC LU.
 
  For detailed information on how to create QSERVER mode
  descriptions on the servers, consult the appropriate server
  documentation.
 

-- 
... Neil Palmer                                      AS/400~~~~~      
... NxTrend Technology -Canada       ____________          ___  ~     
... Markham,  Ontario,  Canada       |OOOOOOOOOO| ________  o|__||=   
... Phone: (905) 731-9000 x238       |__________|_|______|_|______)   
... url:http://www.NxTrend.com        oo      oo   oo  oo   OOOo=o\   
... mailto:NPalmer@NxTrend.com     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* 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   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *


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.