[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | DB Integrator Public Conference |
| Notice: | Database Integration - today! Kit/Doc info see note 36 |
| Moderator: | BROKE::ABUGOV |
|
| Created: | Mon Sep 21 1992 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 1171 |
| Total number of notes: | 5187 |
Subject:
log
Date:
Thu, 14 Nov 1996 15:02:58 +0200
From:
[email protected]
To:
[email protected]
Hi,
We have a customer that is trying to access a DB2 databse and is
getting the following error:
attach 'fil/TYPE=DB2/config=NDBC$dcl:selma.dat/table=a212.pessoal';
%SQL-F-ERRATTDEC, Error attaching to database
/TYPE=DB2/config=NDBC$dcl:selma.dat/table=a212.pessoal
-RDB-E-BAD_DB_FORMAT,/ACCESS_NAME=VIDA/APPLICATION_NAME=RJAACICS/COLLATE=
E/CONFIG_FILE=NDBC$dcl:selma.dat/DBKEY_DEFAULT_MODE=READ_ONLY/LOGON_MODE=
XL622048/NOAUTOCOMMIT/NODE=G60000/NOENFORCE_ALL_TXN/PASSWORD=/SERVER_LOG=
N/TABLES=A212.PESSOAL/TIDCS=DC20/TX
-LDRV-E-BAD_META_QUERY, An error occurred executing a metadata query:
Table/Column Procedure
-LDRV-E-GNL_SRVR_ERROR, server software terminated abnormally
-LDRV-E-LU62_SUPP, %SNALU62-E-DEABPR, deallocate abend program
-LDRV-E-LU62_SUPP, -SNALU62-E-HOSTERR, error returned from host,
DFHAC2206 10:58:40 RJAACICS TRANSACTION DC20 HAS FAILED WITH
ABEND ASRA.
RESOURCE BACKOUT WAS SUCCESSFUL.
He is running version 3.1 and happens with any connection. He
says it worked fine up to yesterday. When trying to connect
from another system that runs version 2.0 it works fine.
I've asked him to define the logicals to get the logfile..
Any hints???
Thanks
Claudia
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1103.1 | | ORAREP::EDSCLU::WHITE | | Thu Nov 14 1996 14:49 | 14 |
| Well, it's not a known problem if that's a hint you were hoping for.
An ASRA is a CICS version of an access violation. As far as I know, there has
only ever been one ASRA associated with the DB2 server and it got fixed
in the V2 Server (I think). I doubt it's your problem anyway since
it had to do with /TABLES having more than 10 table names.
The quickest thing to do is see what changed on the mainframe 'yesterday'.
I can't imagine what would stop a V3 client but still allow
a V2 client to work. You might want to look at the CICS definition
of transaction DC20 to make sure it's really running the server.
If that doesn't work then I suggest opening a formal problem report and
getting the CICS dump submitted.
|