× 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[2]: CA Windows 95<
  • From: John Swartzendruber <johnbs@xxxxxxxxxxxxxx>
  • Date: Fri, 25 Apr 1997 12:50:52 -0000
  • Comments: Routed through 'Mailcoach V2.10 for Win95/NT'

The first 2 messages jive with ones I see in the job log on my system as well, I
believe it has to do with not having IPX setup as a protocol on the AS/400.  The
third message MCH3402 looks like a problem.  It appears that something is
missing or misplaced, but it was not obvious to me what.

____________________Reply Separator____________________
Subject:    Re: CA Windows 95<
Author: Alan Pruitt
Date:       4/25/97 9:08 AM

<  Pete, Neil, Guy and Tim responds:

< I assume that since you are working with IBM, you have already made sure that
< you have run STRHOSTSVR.  What does the joblog of QZDASRVSD say?  


Thank for the responses, It appears that the setup is correct.  
The routing entries are correct for subsystem qserver.
STRHOSTSVR *ALL has been ran.  Quser profile is okay and not expired.
I am running the V3R1M2 version. I have done a netstat and everything appears
okay.  I ran   CWBPING on the client and it came back okay.


The job log when QZDASRVSD ends:

I get this message: Which is CPE3448
                      
10    04/24/97   10:25:02   QZBSCOMM       QSYS        *STMT    QZBSCOMM   
  From module . . . . . . . . :   QZBSCOMM                                 
  From procedure  . . . . . . :   SndErrnoMsg__FPc                         
  Statement . . . . . . . . . :   923                                      
  To module . . . . . . . . . :   QZBSCOMM                                 
  To procedure  . . . . . . . :   SndErrnoMsg__FPc                         
  Statement . . . . . . . . . :   923                                      
  Message . . . . :   The protocol required to support the specified addres
    family is not available at this time.                                  


Then this message: Which is CPIAD08

40    04/24/97   10:25:02   QZBSCOMM       QSYS        *STMT    QZBSCOMM   
  From module . . . . . . . . :   QZBSCOMM                                 
  From procedure  . . . . . . :   SndCPIAD08__FiN21                        
  Statement . . . . . . . . . :   907                                      
  To module . . . . . . . . . :   QZBSCOMM                                 
 To procedure  . . . . . . . :   
SndCPIAD08__FiN21                              
Statement . . . . . . . . . :   907                                            
Message . . . . :   HOST SERVER COMMUNICATIONS ERROR OCCURRED ON SOCKET() -    
  SPX FAMILY.                                                                  
CAUSE . . . . . :   ERROR CODE 3448 WAS RECEIVED WHILE PROCESSING THE SOCKET() 
  - SPX FAMILY FUNCTION FOR THE HOST SERVER COMMUNICATIONS. RECOVERY  . . . :  
   SEE ANY PREVIOUSLY LISTED MESSAGE(S) TO DETERMINE THE CAUSE OF THE ERROR;   
  IF NECESSARY, CORRECT THE ERROR AND ISSUE THE REQUEST AGAIN.                 
    04/24/97   10:51:06   01BCE2019AB0               2030     QSOKERN3     QSY 

Then the MCH3402:
To module . . . . . . . . . :   QSODRVRS                                       
To procedure  . . . . . . . :   qso_open_driver__FiN31PP7qso_scbPc             
Statement . . . . . . . . . :   740                                            
Message . . . . :   Tried to refer to all or part of an object that no longer  
  exists.                                                                      
Cause . . . . . :   The most common cause is that a stored address to an       
  object is no longer correct because that object was deleted or part of the   

Thanks for any help, still have not found a solution.

Original Question:

<< I am attempting to install CA/95.  I am on V3R1, with current PTF tape and
<< latest Service Pack and also PTF SF38543.  I am using native Windows 95 TCP 
<< Winsock 1.1 stack.  PC5250 works and I can send remote commands from the 
<< client and it works.  Basically everything seems okay until I try to
<< transfer a file from the As/400 to the client.  I get a message on the 
client that
<< says  Unable to start database server.  On the As/400 the QZDASRVSD running 
in 
<< QSERVER ends.
 
<< Has anyone ran across this problem and came to a resolution ?  I've been 
<< working with IBM Service for 2 days but have not come to a resolve.  

I assume that since you are working with IBM, you have already made sure that
you have run STRHOSTSVR.  What does the joblog of QZDASRVSD say?  


* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* 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   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.