RE: PROGMAN GPF in Client Access Enh. for Win 3.1

Paul,

Read through this, see if thge symptoms match, and follow the
circumvention.



Item SA70096

  APAR Identifier ...... SA70096       Last Changed..98/02/18  
  CA400WIN-PC5250 CANNOT OPEN PC5250 SESSION USING SNA
  CONNECTION TYPE
 
  Symptom ...... IN INCORROUT         Status ........... CLOSED  PRS
  Severity ................... 1      Date Closed ......... 98/02/17
  Component .......... 5763SS100      Duplicate of ........
  Reported Release ......... 310      Fixed Release ............
  Component Name 5763 OS/400 ROC      Special Notice
  Current Target Date ..97/12/17      Flags
  SCP ...................
  Platform ............
 
  Status Detail: APARCLOSURE - APAR is being closed.
 
  PE PTF List:
 
  PTF List:
 
 
  Parent APAR:
  Child APAR list:
 
 
  ERROR DESCRIPTION:
  User cannot open PC5250 session under APPC or ANYNET connection.
  (APPC connection is used for both connection type). User gets
  above messages :
          Application error
  PCSCM caused error on segment loading in module PCSTQ.DLL in
  003:25B0
            then after clicking on OK button
          Application error
  PROGMAN cause GPF in module PCSTQ.DLL in 003:22EF
  Then PC is frozen.
  Another symptom is that when customer execute 'start/configure
  session' icon of personal communication then choose 'APPC
  connection' and then click on 'link configuration', 'NETWORK
  SERVICES' window is partially displayed and cannot choose
  as400 system name
 
 
  LOCAL FIX:
 
 
  PROBLEM SUMMARY:
  User cannot open PC5250 session under APPC or ANYNET connection.
  (APPC connection is used for both connection type).  User gets
  above messages :
          Application error
  PCSCM caused error on segment loading in module PCSTQ.DLL in
  003:25B0
            then after clicking on OK button
          Application error
  PROGMAN cause GPF in module PCSTQ.DLL in 003:22EF Then PC is
  frozen.  Another symptom is that when customer execute
  'start/configure session' icon of personal communication then
  choose 'APPC connection' and then click on 'link configuration',
  'NETWORK SERVICES' window is partially displayed and cannot
  choose as400 system name
 
 
  PROBLEM CONCLUSION:
  PTF 5763XK1-SF42934 was partially overwritten during the PTF
  package build.
 
  The build procedure has been fixed.  Future packages that come
  out after the C8013410 level will not be exposed to this
  problem.
 
   TEMPORARY FIX:
 
   COMMENTS:
 
  MODULES/MACROS:   NONE
  
  SRLS:      NONE
  
  RTN CODES:
 
  CIRCUMVENTION:
  Permanently remove PTF 5763XK1-SF42934.  Order the same PTF from
  ECS, load it from *SERVICE, and temporarily apply it.
 
 
  MESSAGE TO SUBMITTER:



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: Paul [SMTP:kdcma@ix.netcom.com]
> Sent: Tuesday, March 17, 1998 8:43 AM
> To:   MIDRANGE-L@midrange.com
> Subject:      Re: PROGMAN GPF in Client Access Enh. for Win 3.1
> 
> Is no one else having this problem then??
> 
> Paul wrote:
> 
> > Hi everyone,
> >
> > I've got a VERY CONSISTENT problem with Client Access Enhanced for
> Win
> > 3.1. As far as I can tell, I am at the latest patch levels but the
> > following errors occur on every workstation with 100%
> reproducability:
> >
> > 1) User runs client access under Windows 3.1
> > 2) User has no problem while client access is running.
> > 3) User logs off the system & exits client access
> > 4) The next thing the user tries to run, regardless of what it is,
> > causes a GPF in PROGMAN.
> >
> > Has anyone run into this or seen anything on it?
> >
> > Thank You,
> >
> > Paul
> >
> >
+---
| 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 MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---