View previous topic :: View next topic
|
Author |
Message |
Pradeebha
New User
Joined: 06 Jan 2006 Posts: 7
|
|
|
|
Why do we go for FSET option in DFHMDF Macro.Is there any specific reason for it?
regards
Pradeebha |
|
Back to top |
|
|
radhakrishnan82
Active User
Joined: 31 Mar 2005 Posts: 435 Location: chennai, India
|
|
|
|
FSET specifies that the modified data tag (MDT) for this field should be set when the field is sent to a terminal.
Specification of FSET causes the 3270 to treat the field as though it has been modified. On a subsequent read from the terminal, this field is read, whether or not it has been modified. The MDT remains set until the field is rewritten without ATTRB=FSET, or until an output mapping request causes the MDT to be reset.
Hope this helps. |
|
Back to top |
|
|
nagendrat
New User
Joined: 18 Jan 2006 Posts: 5
|
|
|
|
This is the Field Set. MDT is SET on so that the feild is to be sent from one terminal to the host computer regardless of whether the feild is actually modified by the user.
For Ex: When the terminal user modifies a feild on a screen, MDT will be set to "1"(0n) automatically by the terminal hardware.
I hope this is understandable for You.
---
Nagendra. |
|
Back to top |
|
|
|