Aend 0C4000 hex



IBM's flagship relational database management system

Aend 0C4000 hex

Postby sri_mf » Fri Feb 26, 2016 5:27 pm

while executing select query on d2 sample table getting an aend error

select * from DSN8910.EMP;
sri_mf
 
Posts: 8
Joined: Thu Feb 04, 2016 1:54 pm
Has thanked: 0 time
Been thanked: 0 time

Re: Aend 0C4000 hex

 

Re: Aend 0C4000 hex

Postby NicC » Fri Feb 26, 2016 8:19 pm

So? Good for you! Hope you managed to read up about it and fix it.

In other words - explain a lot more! We are not mind-readers. What is the data? What is the query? How is the query being executed - SPUFI or program? If a program what language? Show the relevant bits of code.
The problem I have is that people can explain things quickly but I can only comprehend slowly.
Regards
Nic
NicC
Global moderator
 
Posts: 2568
Joined: Sun Jul 04, 2010 12:13 am
Location: Down on the pig farm
Has thanked: 4 times
Been thanked: 90 times

Re: Aend 0C4000 hex

Postby sri_mf » Sat Feb 27, 2016 7:34 am

tried thru SPUFI and QMF

result was same
sri_mf
 
Posts: 8
Joined: Thu Feb 04, 2016 1:54 pm
Has thanked: 0 time
Been thanked: 0 time

Re: Aend 0C4000 hex

Postby sri_mf » Sat Feb 27, 2016 11:40 am

hope this post will give more clarity on my question

while i was trying to retrieve data from a table of an exixsting db2 sample database

select * from DSN8910.EMP;

its giving an error Aend 0C4000 hex

similar error occurred on spufi aswell as QMF

but if i retrieve only empno its giving results(select empno from DSN8A10.EMP)

table discription

CREATE TABLE DSN8A10.EMP
      (EMPNO     CHAR(6)                          NOT NULL,
       FIRSTNME  VARCHAR(12)                      NOT NULL,
       MIDINIT   CHAR(1)                          NOT NULL,
       LASTNAME  VARCHAR(15)                      NOT NULL,
       WORKDEPT  CHAR(3)                                  ,
       PHONENO   CHAR(4)         CONSTRAINT NUMBER CHECK
                 (PHONENO >= '0000' AND
                  PHONENO <= '9999')                      ,
       HIREDATE  DATE                                     ,
       JOB       CHAR(8)                                  ,
       EDLEVEL   SMALLINT                                 ,
       SEX       CHAR(1)                                  ,
       BIRTHDATE DATE                                     ,
       SALARY    DECIMAL(9,2)                             ,
       BONUS     DECIMAL(9,2)                             ,
       COMM      DECIMAL(9,2)                             ,
       PRIMARY KEY (EMPNO)                                ,
       FOREIGN KEY RED (WORKDEPT) REFERENCES DSN8A10.DEPT
                 ON DELETE SET NULL                       )
  EDITPROC  DSN8EAE1
  IN DSN8D10A.DSN8S10E
  CCSID EBCDIC;
sri_mf
 
Posts: 8
Joined: Thu Feb 04, 2016 1:54 pm
Has thanked: 0 time
Been thanked: 0 time

Re: Aend 0C4000 hex

Postby NicC » Sat Feb 27, 2016 7:08 pm

Try retrieving the numeric columns - one at a time. Possibly someone has updated the table with invalid information so you may have to reload it (or jave someone reload it for you). These sample tables are used the world over and only you seem to have the problem so it is probably your table that is corrupt. You would need to speak to the DB2 DBA once you have discovered which column is corrupted.

p.s. it is abend (ABnormal END) - not aend.
The problem I have is that people can explain things quickly but I can only comprehend slowly.
Regards
Nic
NicC
Global moderator
 
Posts: 2568
Joined: Sun Jul 04, 2010 12:13 am
Location: Down on the pig farm
Has thanked: 4 times
Been thanked: 90 times


Return to DB2

 


  • Related topics
    Replies
    Views
    Last post