View previous topic :: View next topic
|
Author |
Message |
Carla LeGree
New User
Joined: 02 Jun 2008 Posts: 3 Location: Ohio
|
|
|
|
After a z/OS 1.7 upgrade one of my online applications that uses extended data streaming began displaying corrupted data on some of it screen displays. My optimizer software shows an invalid outbound SFE data stream when displaying extended highlighting and foreground color after and exec cics send.
The invalid data is x'4140' and x'4240' before the upgrade the data stream displayed x'41F4' and x'42F4'.
I've exhausted every conceivable change to my CICS TYPETERM. Any suggestions on what could change a data stream after an operating system upgrade? |
|
Back to top |
|
|
CICS Guy
Senior Member
Joined: 18 Jul 2007 Posts: 2146 Location: At my coffee table
|
|
|
|
Did you initialize the dsect to binary zeros prior to moving in your data fields? |
|
Back to top |
|
|
Carla LeGree
New User
Joined: 02 Jun 2008 Posts: 3 Location: Ohio
|
|
|
|
I found the problem. An LE runtime parameter had to be changed. the default was STORAGE=((NONE,NONE,NONE,0K),OVR). I changed it to
STORAGE=((00,NONE,NONE,0K),OVR) which clears WS in COBOL and everything works fine now.
Thanks for your help. |
|
Back to top |
|
|
CICS Guy
Senior Member
Joined: 18 Jul 2007 Posts: 2146 Location: At my coffee table
|
|
|
|
Carla LeGree wrote: |
I found the problem. An LE runtime parameter had to be changed. the default was STORAGE=((NONE,NONE,NONE,0K),OVR). I changed it to
STORAGE=((00,NONE,NONE,0K),OVR) which clears WS in COBOL and everything works fine now. |
That would have been my guess, but I figured you had already checked that....... |
|
Back to top |
|
|
Carla LeGree
New User
Joined: 02 Jun 2008 Posts: 3 Location: Ohio
|
|
|
|
My MVS group assured me that the LE runtime parms were the same on both z/OS 1.4 and the z/OS 1.7, and I took them for their word. When I recieved your feed back about clearing the DSECT it made me think about LE options. I ran the CLER transaction on both systems and saw the problem right away.
Your response triggered the fix THANKS!!!! |
|
Back to top |
|
|
|