× 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.


  1.  Home
  2. MIDRANGE-L
  3. July 1998

RE: Client Access crashes

  • Subject: RE: Client Access crashes
  • From: Neil Palmer <npalmer@xxxxxxxxxxx>
  • Date: Mon, 20 Jul 1998 16:06:22 -0500
 
There are several flakey problems with V3R1M3 at Service Pack SF48155.
You may want to drop back to the previous Service Pack SF46891.

One known problem is where PC5250 won't connect via TCP/IP if it takes a
long while for the remote system to reply (say over 800 milliseconds on
a ping).  Yet you can connect OK with Graphical Access, Operations
Navigator, Data Transfer, etc.
Apparently this doesn't occur on SF46891.

Another nasty problem - in a PC5250 session connect to your 400 (note
this problem only occured when connecting to a V4R1 system, if I
connected to a V3R1 machine it worked fine, to a V3R2 system it drops
the session - and leaves it active on the 400 - and goes back to a
signion display).  Now (without first doing STRPASTHR or TELNET to
another system) go to the System Request menu.  You'll notice option 11
- Transfer to previous system.  Now on a twinax screen you wouldn't see
that if you hadn't done a STRPASTHR or TELNET to another machine.  Now,
should you happen to try to run that option 11 it will crash your
session.  CPF5063 Data sent to device xxxxx invalid.
This is particularly nasty when you HAVE done STRPASTHR or TELNET to
another machine, then done SysReq 11 to go back to your original system,
then you forget which one you're on and do a SysReq 11 (instead of
SysReq 1) to go back to the target system.  Bye bye session !  I don't
know if this problem just started with SF48155 or if it existed
previously.



Neil Palmer                                AS/400~~~~~      
NxTrend Technology - Canada   ____________          ___  ~     
Thornhill, Ontario,  Canada   |OOOOOOOOOO| ________  o|__||=   
Phone: (905) 731-9000  x238   |__________|_|______|_|______)   
Cell.: (416) 565-1682  x238    oo      oo   oo  oo   OOOo=o\   
Fax:   (905) 731-9202       ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
mailto:NPalmer@NxTrend.com    AS/400  The Ultimate Business Server      
http://www.NxTrend.com

> -----Original Message-----
> From: Gary Lehman [SMTP:Gary_Lehman@mail.mchcp.org]
> Sent: Monday, July 20, 1998 3:53 PM
> To:   'MIDRANGE-L@midrange.com'
> Subject:      Client Access crashes
> 
> Hi,
> 
> I'm using the latest and greatest Client Access V3M1R3 with the latest
> service pack and I seem to be having some trouble.  I just want to
> know if
> anyone on this list has had some crazy things happen like your machine
> rebooting whenever you click on an AS/400 session to bring it up.
> I've also
> had other quirky things like a command shell not wanting to shut down
> when I
> shut down the PC and errors with RUN32.DLL.  These things weren't
> happening
> until Client Access was installed.  If anyone has had any problems
> like
> these let me know.
> 
> Thanks,
> 
> Gary Lehman
> Programmer Analyst
> Missouri Consolidated Health Care Plan
> 
>               -----Original Message-----
>               From:   Buck Calabro [mailto:mcalabro@commsoft.net]
>               Sent:   Thursday, July 16, 1998 9:47 AM
>               To:     'MIDRANGE-L@midrange.com'
>               Subject:        RE: RUNRMTCMD
> 
>               On Thursday, July 16, 1998 8:25 AM, Gary Lehman 
>               [SMTP:Gary_Lehman@mail.mchcp.org] wrote:
>               > Yes the daemon is running on the PC.  However, I have
> to
> do it manually
>               > and
>               > the commands I'm trying to run don't seem to execute,
> even
> though it
>               > tells
>               > me the command ran successfully.
> 
>               Gary,
>                 Any output from the command will be put into a spooled
> file on the 400. 
>                Also, the daemon window will have a record of what
> happened.  Here are 
>               the exact steps I take to run commands on my PC from my
> 400:
> 
>               1. Open a DOS window from W95
>               2. cwbrxd
>               The daemon window (this one) shows:
>               IBM AS/400 Client Access for Windows 95/NT
>               Version 3  Release 1  Level 3
>               TCP/IP Remote Command Server
>               (C) Copyright IBM Corporation and Others 1984, 1995.
> All
> rights reserved.
>               U.S. Government Users Restricted Rights - Use,
> duplication
> or disclosure
>                 restricted by GSA ADP Schedule Contract with IBM Corp.
>               Licensed Materials - Property of IBM
> 
>               CWBAR1007 - Client Access CWBRXD has been started.
> 
>               3. On the AS/400, RUNRMTCMD CMD(DIR)
>                         RMTLOCNAME(BUCK *IP)
>                         RMTUSER(BUCK)
>                         RMTPWD(MyW95Password)
>                  Note that my PC is in the AS/400 host table as BUCK.
> CFGTCP, option 
>               10.
>                  The PC daemon window shows:
> 
>               Ran the following remote command from user BUCK on
> system
> AS400COM: 'DIR'
> 
>               4. On the AS/400, WRKSPLF.  I have a spooled file named
> QSYSPRT that 
>               contains the directory listing.  The first few lines
> are:
> 
>                Volume in drive C has no label
>                Volume Serial Number is 3A39-1205
>                Directory of C:\WINDOWS
>               .              <DIR>        04-13-98 11:12a .
>               ..             <DIR>        04-13-98 11:12a ..
>               SYSTEM         <DIR>        04-13-98 11:12a SYSTEM
>               COMMAND        <DIR>        04-13-98 11:12a COMMAND
>               HELP           <DIR>        04-13-98 11:12a HELP
>               MSBATCH  INF         1,209  12-17-97 11:03a MSBATCH.INF
>               NETDET   INI         7,885  08-24-96 11:11a NETDET.INI
> 
>               5. When I'm all done, I open another DOS window from W95
>               6. CWBRXDSD
>                  The daemon window shows
>               CWBAR1008 - Client Access CWBRXD is shutting down.
>               7. EXIT from the daemon window
>               8. EXIT from the stop daemon window
> 
>               I am running Client Access V3R1M3, service pack level
> SF46891 on a TCP/IP 
>               connection to a 620 running V4R2 at PFT level 98140.
> 
>               Buck Calabro
> | 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
> +---
+---
| 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
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
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.