RE: Please check your communications path to the AS/400

["Gary Kuznitz " <docfxit@xxxxxxxxxxx>]

On 13 Dec 2000, at 15:18, Eric Sundell PMI wrote:
> Try reconfiguring the connection in 'My AS400 Connections' and do a
> 'Verify' or CWBPING, perhaps one or more of the CA servers are not
> up...
Thanks for the suggestions.  I disconnected the connection in OpsNav and 
ran Verify.  It said Verify completed Successfully.  I ran CWBPING and the 
results are:
Microsoft wsock32.dll, ver2.2, 32bit of Apr 22 1999, at 20:29:32.
Address 192.168.1.1 used to connect to system .
Successfully connected to AS/400 server mapper
Successfully connected to server application telnet
Successfully connected to server application as-netprt
Successfully connected to server application as-database
Successfully connected to server application as-rmtcmd
Successfully connected to server application as-dtaq
Successfully connected to server application as-file
Successfully connected to server application as-central
Successfully connected to server application as-signon
Connection verified

In WRKACTJOB it shows:
QSERVER              QSYS             SBS   
   QPWFSERVSD          QUSER            BCH  
   QSERVER             QPGMR            ASJ  
   QZDASRVSD           QUSER            BCH  
   QZLSFILE            QUSER            PJ   
   QZLSSERVER          QPGMR            BCH  

I re-IPL'd the 400 and I get the same thing.  Am I missing something?

Thanks,

Gary Kuznitz


> 
> Eric Sundell
> AS400/PC Specialist 
> 
> -----Original Message-----
> From: Gary Kuznitz [mailto:docfxit@thegrid.net]
> Sent: Tuesday, December 12, 2000 6:40 PM
> To: MIDRANGE-L@midrange.com
> Subject: Please check your communications path to the AS/400
> 
> 
> Hi,
> 
> I'm getting an error from Operations Navigator when I click on File
> Systems saying " An error occurred while retrieving directories and
> files.  
>  Please check your communications path to the AS/400."
> 
> I have been looking every place to try to figure out where this 
> communications path is .  I can't find any reason for this error.  I'm
> using CA v3r2m0 at service pack SF59923.  I have File Systems loaded. 
> I'm signed onto the PC with *SECADM and  *ALLOBJ.  I have looked
> through the help  the manuals and the Midrange.com archives under
> "File Systems" and "communications path" and found nothing.  I'm
> running V4R4 with the latest CUM and Hypers. Normally I would prefer
> people not to be able to look at the files through OpsNav but I need
> to get in according to the instructions on setting up DNS.
> 
> Does anybody have any ideas as to what might be causing this error?
> 
> TIA,
> 
> Gary Kuznitz



+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---