MVSFORUMS.com Forum Index MVSFORUMS.com
A Community of and for MVS Professionals
 
 FAQFAQ   SearchSearch   Quick Manuals   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Storing Data on IMS DC screen

 
Post new topic   Reply to topic   printer-friendly view    MVSFORUMS.com Forum Index -> IMS
View previous topic :: View next topic  
Author Message
lokesh_taks
Beginner


Joined: 10 Dec 2004
Posts: 4
Topics: 2

PostPosted: Sat Dec 11, 2004 9:18 am    Post subject: Storing Data on IMS DC screen Reply with quote

Hi All,
I have a 4 btye COMP data, which i want to store it on the IMSDC screen as a 2 byte field. I have moved the required data into a working storage field and redefined the same into a 2 byte Alphanumeric data.
When I display for the data storage before the ISRT message call, the values displayed are correct. But on the screen the data stored in the FIRST BYTE is spaces.

Please could anybody let me know reason why i am not able to store COMP data on the screen?.

Regards,
Lokesh
Back to top
View user's profile Send private message
kolusu
Site Admin
Site Admin


Joined: 26 Nov 2002
Posts: 12378
Topics: 75
Location: San Jose

PostPosted: Mon Dec 13, 2004 5:09 am    Post subject: Reply with quote

lokesh_taks,

Did you know that both COMP & COMP-3 data are not visible to the eye. you need to set HEX on to view the data. why would you even want to do that on a screen ? How would the user the know what data he is looking as he cannot issue a HEX on a IMS DC screen

Kolusu
_________________
Kolusu
www.linkedin.com/in/kolusu
Back to top
View user's profile Send private message Send e-mail Visit poster's website
lokesh_taks
Beginner


Joined: 10 Dec 2004
Posts: 4
Topics: 2

PostPosted: Mon Dec 13, 2004 9:59 am    Post subject: Reply with quote

Kolusu,
I storing the data on the screen in a NODISP attribute set on the field. USER will not be using the field. I am storing the data on the screen, so that i can use the data for my next transaction processing.
I know we can interpret the COMP & COMP-3 data only in HEX mode. But my concerns is , when I move the COMP data to a 2 byte screen field which as NODISP attribute set, the first byte as spaces at all cases.
But when i move a ALPHANUMERIC data like "AB" into the same field, the data is correctly stored and given back to the program.

Please could you let me know the reason and any solution for the same

Regards,
Lokesh
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic   printer-friendly view    MVSFORUMS.com Forum Index -> IMS All times are GMT - 5 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


MVSFORUMS
Powered by phpBB © 2001, 2005 phpBB Group