Problem Note 46851: Errors occur when you perform tasks that require a reread of a DB2 table
Errors are likely to occur when all of the following are attempted:
- A remote session to z/OS is created through SAS/CONNECT®
- A LIBNAME statement using SAS/ACCESS® Interface to DB2 and an RSUBMIT statement are submitted to the remote session
- In the local SAS session, a LIBNAME statement is allocated to the remote DB2 library via Remote Library Services (RLS)
- One of the DB2 tables is opened via VIEWTABLE
- Within VIEWTABLE, the mode is changed to Edit
- An observation from the DB2 table is deleted
- Within VIEWTABLE, the mode is changed back to Browse
When all of the above are performed, your SAS session might seem unresponsive or delayed, and the row(s) that you attempted to delete still exist in the DB2 table. Eventually, errors similar to those shown below appear in the SAS log. The only workaround is to not change the mode back to Browse before exiting out of VIEWTABLE.
REMOTE(S390DEVA): IEA995I SYMPTOM DUMP OUTPUT
REMOTE(S390DEVA): SYSTEM COMPLETION CODE=04E REASON CODE=00E7000C
REMOTE(S390DEVA): TIME=11.55.42 SEQ=39179 CPU=0080 ASID=0101
REMOTE(S390DEVA): PSW AT TIME OF ERROR 077C1001 A3C45166 ILC 2 INTC 0D
ERROR: An exception has been encountered.
Please contact technical support and provide them with the following traceback
information:
The SAS task name is [ViewTable Window]
Exception occurred at (4B781335)
Task Traceback
Address Frame (DBGHELP API Version 4.0 rev 5)
4B781335 0A9BBB64 tknlssb:tknlssb+0x335
6795AA7A 0A9BBBDC saswzx:tkvercn1+0x19A3A
6795A6F3 0A9BBC54 saswzx:tkvercn1+0x196B3
667A871B 0A9BBCC4 sasyoio:tkvercn1+0x76DB
667A4405 0A9BBDA4 sasyoio:tkvercn1+0x33C5
5C718ADA 0A9BBE54 sasgdat:tkvercn1+0x17A9A
5C701799 0A9BBFFC sasgdat:tkvercn1+0x759
571BA543 0A9BC040 saspos:tkvercn1+0x19503
571B52F1 0A9BC434 saspos:tkvercn1+0x142B1
571BFB4D 0A9BC4E8 saspos:tkvercn1+0x1EB0D
5C6A4DB8 0A9BC9C0 sasgfsv:tkvercn1+0x23D78
571BA543 0A9BCA04 saspos:tkvercn1+0x19503
571B52F1 0A9BCDF8 saspos:tkvercn1+0x142B1
571BFB4D 0A9BCEAC saspos:tkvercn1+0x1EB0D
0999E49B 0A9BD458 sasoted:tkvercn1+0xD45B
0999D661 0A9BD550 sasoted:tkvercn1+0xC621
099C5EDA 0A9BD6C8 sasoted:tkvercn1+0x34E9A
099C23E4 0A9BD71C sasoted:tkvercn1+0x313A4
09992D23 0A9BD73C sasoted:tkvercn1+0x1CE3
606FA131 0A9BD82C sasrm:tkvercn1+0x190F1
606F11B0 0A9BD8E8 sasrm:tkvercn1+0x10170
6071E860 0A9BD930 sasrm:tkvercn1+0x3D820
60716B06 0A9BD954 sasrm:tkvercn1+0x35AC6
60716AEC 0A9BD96C sasrm:tkvercn1+0x35AAC
65C3726B 0A9BDC44 sasabld:tkvercn1+0x622B
606E6034 0A9BDDDC sasrm:tkvercn1+0x4FF4
60712C40 0A9BDEE8 sasrm:tkvercn1+0x31C00
65AF212C 0A9BDF30 sasf03:tkvercn1+0x210EC
65BE8423 0A9BDF68 sasaf:tkvercn1+0x73E3
65BF0372 0A9BDFB8 sasaf:tkvercn1+0xF332
65BF06F1 0A9BE14C sasaf:tkvercn1+0xF6B1
570FC1C7 0A9BE49C saspxq:tkvercn1+0x2B187
570FBA75 0A9BE4B0 saspxq:tkvercn1+0x2AA35
570D6C54 0A9BE598 saspxq:tkvercn1+0x5C14
570DE6D7 0A9BE8E8 saspxq:tkvercn1+0xD697
570DA5A7 0A9BEB58 saspxq:tkvercn1+0x9567
65BE21B2 0A9BEE30 sasaf:tkvercn1+0x1172
65BE4480 0A9BF0A0 sasaf:tkvercn1+0x3440
65A71975 0A9BFF54 saszaf:tkvercn1+0x935
00B92DB4 0A9BFFA0 sashost:Main+0xCF84
00C86038 0A9BFFB4 sashost:Main+0x100208
7C80B713 0A9BFFEC kernel32:GetModuleFileNameA+0x1B4
REMOTE(S390DEVA): ACTIVE LOAD MODULE ADDRESS=99999999
OFFSET=0A2AB7CD
REMOTE(S390DEVA): NAME=rrrrrrrr
REMOTE(S390DEVA): DATA AT PSW IS UNAVAILABLE AT THIS TIME
REMOTE(S390DEVA): GR 0: 00000000_80000000 1: 00000000_8004E000
REMOTE(S390DEVA): 2: 00000000_00000010 3: 00000048_B27FC894
REMOTE(S390DEVA): 4: 00000000_00000002 5: 00000000_00000080
REMOTE(S390DEVA): 6: 00000000_18996C48 7: 00000000_00000000
REMOTE(S390DEVA): 8: 00000000_22D3E4B0 9: 00000000_7A28D1F4
REMOTE(S390DEVA): A: 00000000_18996BA0 B: 00000000_18996BA0
REMOTE(S390DEVA): C: 00000000_23C4EFE0 D: 00000000_7A4AB938
REMOTE(S390DEVA): E: 00000000_7A747908 F: 00000000_00E7000C
REMOTE(S390DEVA): END OF SYMPTOM DUMP
ERROR: INTERNAL ERROR - YP UNABLE TO FORMAT MESSAGE.
ERROR: Generic critical error.
Operating System and Release Information
SAS System | SAS/ACCESS Interface to DB2 | z/OS | 9.2 TS2M3 | 9.4 TS1M0 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Type: | Problem Note |
Priority: | high |
Date Modified: | 2012-06-22 14:19:56 |
Date Created: | 2012-06-20 10:22:25 |