PJ16168 - TRAP 000D,EIP=000017EB,CSLIM=2E4B TRAP IS IN COM.SYS AND USUALLY OCCURS WHEN TERMINATING APPLICATIONS. SAME PROBLEM AS PJ14545

Last updated: 30th November, 1994
 

APAR Identifier ...... PJ16168
 TRAP 000D,EIP=000017EB,CSLIM=2E4B TRAP IS IN COM.SYS AND USUALLY
 OCCURS WHEN TERMINATING APPLICATIONS.  SAME PROBLEM AS PJ14545
 
 Symptom ...... HL MKBCMAPAR         Status ........... OPEN
 Severity ................... 1      Date Closed .........
 Component .......... 562260100      Duplicate of .........
 Reported Release ......... 300      Fixed Release ............
 Component Name OS/2 WARP V3         Special Types ..
 Current Target Date ..              Type of Relief ..Not Available
 SCP ................... OS/2        Platform ............ OS/2
 
 Status Detail: Not Available
 
 PE PTF List:
 
 PTF List:
 
 
 Parent APAR:
 Child APAR list:
 
 
 ERROR DESCRIPTION:
 ********************* TRAP 32-bit ***********************
   TRAP =000D ERRCD=0000 ERACC=**** ERLIM=********
   EAX  =00000488 EBX  =00036004 ECX  =0000FFFF EDX  =0000FFFF
   ESI  =FDFF0000 EDI  =000007B2 EBP  =00004EAE FLG  =00012097
   CS:EIP=0A10:000017EB CSACC=009B CSLIM=00002E4B
   SS:ESP=0030:00004EA6 SSACC=1097 SSLIM=0000409F
   DS   =0000 DSACC=**** DSLIM=******** CR0  =8001001B
   ES   =0488 ESACC=0093 ESLIM=000008D1 CR2  =1B5D9066
   FS   =0000 FSACC=**** FSLIM=********
   GS   =0000 GSACC=**** GSLIM=********
   ERROR AT LOCATION # 0160:FFF5C34C - 000D:A34C
       60000, 9084
       048600B4
   INTERNAL REVISION  8.162      94/09/19
   Failure Mode : OS/2
 ***************** end TRAP 32-bit ***********************
 .
 PMCOMM (version 2.11) will sometimes cause this trap to occur
 when a REXX script file is used.  This problem is identical to
 APAR PJ14545 which occurred in the OS/2 2.11 environment.
 .
 Only customers which match the EIP and CSLIM values should be
 added to the IP list of the APAR.
 
 
 LOCAL FIX:
 The trap is random and there is no known work around.  The
 suspect area in COM.SYS is the DosClose code. Customer's
 should try to terminate communications (i.e. hang up the modem)
 before closing the application.
 


Source

IBM's OS/2 Warp APAR List - Part 1

If you need up to date information about the status of this problem, contact IBM and quote the APAR identifier.


See also