IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

CICS invalid data stream


IBM Mainframe Forums -> CICS
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
Carla LeGree

New User


Joined: 02 Jun 2008
Posts: 3
Location: Ohio

PostPosted: Tue Jun 03, 2008 2:14 am
Reply with quote

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
View user's profile Send private message
CICS Guy

Senior Member


Joined: 18 Jul 2007
Posts: 2146
Location: At my coffee table

PostPosted: Tue Jun 03, 2008 2:41 am
Reply with quote

Did you initialize the dsect to binary zeros prior to moving in your data fields?
Back to top
View user's profile Send private message
Carla LeGree

New User


Joined: 02 Jun 2008
Posts: 3
Location: Ohio

PostPosted: Wed Jun 04, 2008 8:35 pm
Reply with quote

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
View user's profile Send private message
CICS Guy

Senior Member


Joined: 18 Jul 2007
Posts: 2146
Location: At my coffee table

PostPosted: Wed Jun 04, 2008 9:57 pm
Reply with quote

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....... icon_lol.gif
Back to top
View user's profile Send private message
Carla LeGree

New User


Joined: 02 Jun 2008
Posts: 3
Location: Ohio

PostPosted: Thu Jun 05, 2008 12:38 am
Reply with quote

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
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> CICS

 


Similar Topics
Topic Forum Replies
No new posts Store the data for fixed length COBOL Programming 1
No new posts Using API Gateway from CICS program CICS 0
No new posts Data set Rec-Cnt and Byte-Cnt Testing & Performance 2
No new posts SCOPE PENDING option -check data DB2 2
No new posts Check data with Exception Table DB2 0
Search our Forums:

Back to Top