|
View previous topic :: View next topic
|
| Author |
Message |
neoarvind
New User
Joined: 28 Oct 2006
Posts: 6
|
|
|
|
It is bit long but please have a look....
I have a map with set od UNPROT fields. i am validation the user input to update the CWA variables. To do that, i have set all attributes of the map input variables to FSET so that the value retuned will be exactly the same as in the map variable. But after that i came to know that since FSET is used, it taking input from all the screen varibles regardless of the user input. At one point (for some display purpose), i need to check the udpated screen varibles alone. I have checked using Input > spaces and length = low-values and spaces. None is working out. Since FSET is used, the length is always = 0 for all the variables. Plz help me out :roll: |
|
| Back to top |
|
 |
dineshness
New User
Joined: 25 Dec 2006
Posts: 63
Location: Perambalur
|
|
|
|
In that case, may be no field has been changed by the user.... 
| Quote: |
| But after that i came to know that since FSET is used, it taking input from all the screen varibles regardless of the user input. |
It should not be, as according to the manual...
Setting the FSET for a field would result in the value of the field to be transmitted only when it is changed.
Dinesh. |
|
| Back to top |
|
|
Mickeydusaor
Active User
Joined: 24 May 2006
Posts: 258
Location: Salem, Oregon
|
|
|
|
I will disagree with that. If I FSET a field it is always returned on the
receive map even if the user has not changed the field. That is why
I have EDIT Routines in my programs to check the fields to see if
they have been changed from the original data displayed. If you do
not FSET the fields then you need to CHECK the MAP FIELD Length
MAPFIELD1L for a X'80', which will tell you that the field has been
modified. |
|
| Back to top |
|
|
dineshness
New User
Joined: 25 Dec 2006
Posts: 63
Location: Perambalur
|
|
|
|
Huh...Thats right Mickey.
I wrote the reply with an offhandedly blocked mind between FSET and FRSET.... 
It should be FRSET.
If you use FRSET, then you dont have to check for the changed fields.
But the problem is if no field is changed by the user, then recieving the map will result in MAP FAIL condition.
May be trying to define the map with FRSET and atleast one of the input fields with FSET could solve the problem. But you need to check for that FSET field value always in the program to find out whether it is modified or not.
Atleast this reduces the no.of fields to be checked.. 
Dinesh. |
|
| Back to top |
|
|
|
|
