|
View previous topic :: View next topic
|
| Author |
Message |
jontyjun
New User
.jpg)
Joined: 12 Sep 2006
Posts: 12
Location: India
|
|
|
|
Hi,
We are using DB2 8.1 & DB2 7.1 in one of our Lpars in the Z/Os mainframe.
Recently we got an error message while accessing the Spufi region. There is a conflict between the CCSIDs(Terminal & Spufi). The error is as follows:
DSNESP06
DSNE345I WARNING: DB2 DATA CORRUPTION CAN RESULT
FROM THIS SPUFI SESSION BECAUSE THE
CCSID USED BY THE TERMINAL IS NOT THE
SAME AS THE CCSID USED BY SPUFI
- TERMINAL CCSID: 00037
- SPUFI CCSID:
NOTIFY THE DB2 SYSTEM ADMINISTRATOR.
PRESS: ENTER to continue
END to return
In case we run the the Bind Step of the DSNTIJSG job against DB2 8.1, the error gets corrected in DB2 8.1 while the error still exists in DB2 7.1
Running the Bind step DSNTIJSG job against DB2 7.1 does not correct the error.
Please let me know a way to proceed.
Regards,
Arjun. |
|
| Back to top |
|
 |
wanderer
Active User
Joined: 05 Feb 2007
Posts: 199
Location: Sri Lanka
|
|
|
|
Not sure if this will help. But,
CCSID from V7 to V8 was an issue. One of the conversion step was to rebind SPUFI etc with ENCODING(37) in V7 before upgrade.
You might try the rebind with encoding option in V7 if you haven't done so already. |
|
| Back to top |
|
|
jontyjun
New User
Joined: 12 Sep 2006
Posts: 12
Location: India
|
|
|
|
The ENCODING(EBCDIC) in the Bind Step of the job DSNTIJSG corresponds to 37. We had tried this earlier itself but in vain.  |
|
| Back to top |
|
|
|
|
