Board index » DB2

All times are UTC



 DB2 OS/390 crashing after connection via DB2 Connect 
Author Message
Michael Taylo
#1 / 6
 DB2 OS/390 crashing after connection via DB2 Connect

We are getting UDB crashing after a connection (via DB2 Connect on AIX).
The manuals don't help in pinpointing the error.

The console shows the following messages:

00000281  IEA989I SLIP TRAP ID=X33E MATCHED.  JOBNAME=*UNAVAIL, ASID=004F.    
00000090  DSNL027I - SERVER DISTRIBUTED AGENT WITH 176                        
00000090             LUWID=CB02CB79.O16D.000504070227=10                      
00000090             THREAD-INFO=P390:*:P390:DB2BP.EXE                        
00000090             RECEIVED ABEND=04E                                      
00000090             FOR REASON=00D31011                                      
00000090  DSNL028I - CB02CB79.O16D.000504070227=10 177                        
00000090             ACCESSING DATA FOR                                      
00000090               LOCATION 203.2.203.121                                
00000090               IPADDR 203.2.203.121                                  
00000090 *DSNV086E - DB2 ABNORMAL TERMINATION REASON=00E50702                
00000090  IEA794I SVC DUMP HAS CAPTURED: 179                                  
00000090  DUMPID=002 REQUESTED BY JOB (DSN1DIST)                              
00000090  DUMP TITLE=DSN1,ABND=04E-00D3111C,U=P390    ,C=XYR00.610.LOCN=2    
00000090             03.2.203.121      ,LOC=DSNLILLM.DSNLIDDC:0003            
00000081  IEA995I SYMPTOM DUMP OUTPUT 180                                    
00000081  SYSTEM COMPLETION CODE=0D7  REASON CODE=00000025                    
00000081   TIME=11.20.11  SEQ=00680  CPU=0000  ASID=0049                      
00000081   PSW AT TIME OF ERROR  070C1000   876EF3E2  ILC 4  INTC 25          
00000081     NO ACTIVE MODULE FOUND                                          
00000081     NAME=UNKNOWN                                                    
00000081     DATA AT PSW  076EF3DC - AA1350B0  8120B225  00B05820            
00000081     GPR  0-3  00000001  076D70F8  000B3FF1  C78DC418                
00000081     GPR  4-7  0000011E  0762DC78  07138418  0775D280                
00000081     GPR  8-11 7F2A1778  876EDC3A  076EEC39  00000032                
00000081     GPR 12-15 882F316C  7F2A1778  876EE4D2  876EE4C0                
00000081   END OF SYMPTOM DUMP                                                
00000281  IEA989I SLIP TRAP ID=X13E MATCHED.  JOBNAME=DSN1DIST, ASID=0026.    
00000281  IEA989I SLIP TRAP ID=X13E MATCHED.  JOBNAME=DSN1MSTR, ASID=0032.    

--
Regards,
Mick

Michael Taylor
Senior Technical Specialist
Search Software America
PO Box 22, Braddon
Canberra, ACT 2612, Australia


http://www.***.com/



Tue, 22 Oct 2002 03:00:00 GMT
Frank Allan Rasmuss
#2 / 6
 DB2 OS/390 crashing after connection via DB2 Connect

On Fri, 05 May 2000 11:21:14 +1100, Michael Taylor

Quote:

>We are getting UDB crashing after a connection (via DB2 Connect on AIX).
>The manuals don't help in pinpointing the error.

Check PQ07441, sound like it could be it.

Frank Allan Rasmussen
Systemsprogrammer
Fyns Amts EDB-central



Tue, 22 Oct 2002 03:00:00 GMT
Byron Schulk
#3 / 6
 DB2 OS/390 crashing after connection via DB2 Connect
Hi:
If running version 6.1 UDB for OS/390 check for maintenance. APARs PQ31299
and/or PQ33473 may fix it.
Quote:

> We are getting UDB crashing after a connection (via DB2 Connect on AIX).
> The manuals don't help in pinpointing the error.

> The console shows the following messages:

> 00000281  IEA989I SLIP TRAP ID=X33E MATCHED.  JOBNAME=*UNAVAIL, ASID=004F.
> 00000090  DSNL027I - SERVER DISTRIBUTED AGENT WITH 176
> 00000090             LUWID=CB02CB79.O16D.000504070227=10
> 00000090             THREAD-INFO=P390:*:P390:DB2BP.EXE
> 00000090             RECEIVED ABEND=04E
> 00000090             FOR REASON=00D31011
> 00000090  DSNL028I - CB02CB79.O16D.000504070227=10 177
> 00000090             ACCESSING DATA FOR
> 00000090               LOCATION 203.2.203.121
> 00000090               IPADDR 203.2.203.121
> 00000090 *DSNV086E - DB2 ABNORMAL TERMINATION REASON=00E50702
> 00000090  IEA794I SVC DUMP HAS CAPTURED: 179
> 00000090  DUMPID=002 REQUESTED BY JOB (DSN1DIST)
> 00000090  DUMP TITLE=DSN1,ABND=04E-00D3111C,U=P390    ,C=XYR00.610.LOCN=2
> 00000090             03.2.203.121      ,LOC=DSNLILLM.DSNLIDDC:0003
> 00000081  IEA995I SYMPTOM DUMP OUTPUT 180
> 00000081  SYSTEM COMPLETION CODE=0D7  REASON CODE=00000025
> 00000081   TIME=11.20.11  SEQ=00680  CPU=0000  ASID=0049
> 00000081   PSW AT TIME OF ERROR  070C1000   876EF3E2  ILC 4  INTC 25
> 00000081     NO ACTIVE MODULE FOUND
> 00000081     NAME=UNKNOWN
> 00000081     DATA AT PSW  076EF3DC - AA1350B0  8120B225  00B05820
> 00000081     GPR  0-3  00000001  076D70F8  000B3FF1  C78DC418
> 00000081     GPR  4-7  0000011E  0762DC78  07138418  0775D280
> 00000081     GPR  8-11 7F2A1778  876EDC3A  076EEC39  00000032
> 00000081     GPR 12-15 882F316C  7F2A1778  876EE4D2  876EE4C0
> 00000081   END OF SYMPTOM DUMP
> 00000281  IEA989I SLIP TRAP ID=X13E MATCHED.  JOBNAME=DSN1DIST, ASID=0026.
> 00000281  IEA989I SLIP TRAP ID=X13E MATCHED.  JOBNAME=DSN1MSTR, ASID=0032.

> --
> Regards,
> Mick

> Michael Taylor
> Senior Technical Specialist
> Search Software America
> PO Box 22, Braddon
> Canberra, ACT 2612, Australia


> http://www.searchsoftware.com



Tue, 22 Oct 2002 03:00:00 GMT
Michael Taylo
#4 / 6
 DB2 OS/390 crashing after connection via DB2 Connect
Thanks.

I have now found the APAR search for OS/390 and there are a few TCPIP<->DB2
problems listed on there. I will see if the 6.1 refresh is an option.

Quote:

> Hi:
> If running version 6.1 UDB for OS/390 check for maintenance. APARs PQ31299
> and/or PQ33473 may fix it.


> > We are getting UDB crashing after a connection (via DB2 Connect on AIX).
> > The manuals don't help in pinpointing the error.

> > The console shows the following messages:

> > 00000281  IEA989I SLIP TRAP ID=X33E MATCHED.  JOBNAME=*UNAVAIL, ASID=004F.
> > 00000090  DSNL027I - SERVER DISTRIBUTED AGENT WITH 176
> > 00000090             LUWID=CB02CB79.O16D.000504070227=10
> > 00000090             THREAD-INFO=P390:*:P390:DB2BP.EXE
> > 00000090             RECEIVED ABEND=04E
> > 00000090             FOR REASON=00D31011
> > 00000090  DSNL028I - CB02CB79.O16D.000504070227=10 177
> > 00000090             ACCESSING DATA FOR
> > 00000090               LOCATION 203.2.203.121
> > 00000090               IPADDR 203.2.203.121
> > 00000090 *DSNV086E - DB2 ABNORMAL TERMINATION REASON=00E50702
> > 00000090  IEA794I SVC DUMP HAS CAPTURED: 179
> > 00000090  DUMPID=002 REQUESTED BY JOB (DSN1DIST)
> > 00000090  DUMP TITLE=DSN1,ABND=04E-00D3111C,U=P390    ,C=XYR00.610.LOCN=2
> > 00000090             03.2.203.121      ,LOC=DSNLILLM.DSNLIDDC:0003
> > 00000081  IEA995I SYMPTOM DUMP OUTPUT 180
> > 00000081  SYSTEM COMPLETION CODE=0D7  REASON CODE=00000025
> > 00000081   TIME=11.20.11  SEQ=00680  CPU=0000  ASID=0049
> > 00000081   PSW AT TIME OF ERROR  070C1000   876EF3E2  ILC 4  INTC 25
> > 00000081     NO ACTIVE MODULE FOUND
> > 00000081     NAME=UNKNOWN
> > 00000081     DATA AT PSW  076EF3DC - AA1350B0  8120B225  00B05820
> > 00000081     GPR  0-3  00000001  076D70F8  000B3FF1  C78DC418
> > 00000081     GPR  4-7  0000011E  0762DC78  07138418  0775D280
> > 00000081     GPR  8-11 7F2A1778  876EDC3A  076EEC39  00000032
> > 00000081     GPR 12-15 882F316C  7F2A1778  876EE4D2  876EE4C0
> > 00000081   END OF SYMPTOM DUMP
> > 00000281  IEA989I SLIP TRAP ID=X13E MATCHED.  JOBNAME=DSN1DIST, ASID=0026.
> > 00000281  IEA989I SLIP TRAP ID=X13E MATCHED.  JOBNAME=DSN1MSTR, ASID=0032.

> > --
> > Regards,
> > Mick

> > Michael Taylor
> > Senior Technical Specialist
> > Search Software America
> > PO Box 22, Braddon
> > Canberra, ACT 2612, Australia


> > http://www.searchsoftware.com

--
Regards,
Mick

Michael Taylor
Senior Technical Specialist
Search Software America
PO Box 22, Braddon
Canberra, ACT 2612, Australia


http://www.searchsoftware.com



Fri, 25 Oct 2002 03:00:00 GMT
nywalke
#5 / 6
 DB2 OS/390 crashing after connection via DB2 Connect
Where can I get a copy of db2 connect.  we have db2 v5 in
production, v6 in test and I want to connect via odbc to the db2
tables from my workstation.
i could not find it in the ibm download folders.

thank you

* Sent from RemarQ http://www.remarq.com The Internet's Discussion Network *
The fastest and easiest way to search and participate in Usenet - Free!



Mon, 28 Oct 2002 03:00:00 GMT
cur..
#6 / 6
 DB2 OS/390 crashing after connection via DB2 Connect
For DB2 for OS/390 problems in TCPIP area check info APAR II11164 TCPIP
APARS for DB2/OS390 V51 DDF DISTRIBUTED FACILITY
Regards,

Sent via Deja.com http://www.deja.com/
Before you buy.



Fri, 01 Nov 2002 03:00:00 GMT
 
 Page 1 of 1
  [ 6 post ] 

 Relevant Pages 

1. Access to DB2 for OS/390 via DB2 Connect

2. Table Limit with DB2 Connect to DB2 for OS/390

3. Import DELimited File Format Files to DB2 for OS/390 Tables with DB2 Connect

4. Frontpage with DB2 Connect to OS/390 DB2 ?

5. MTS and DB2 Connect to DB2 OS/390

6. Accesing DB2 on 0S/390 via DB2 Connect

7. desire to move data from OS 390 DB2 to AS/400 DB2 using DTS

8. Load data from DB2 in NT to DB2 in OS/390

9. Creating DB2 SQL Procedures in DB2 version 6 on OS/390 (June 2000 PUT)

10. DB2 Conenct & DB2 on OS/390

11. Trigger working in DB2 for NT but not in DB2 on an OS/390-machine

12. DB2 for OS/390 REXX Language Support for DB2 V5.1

 
Powered by phpBB® Forum Software