> an account no field having length of 8 bytes on a map.
> If account is universal type then account no is of full 8 byte length.
> if account is non universal, then while sending the map the first 3bytes should be protected and remaining 5 bytes should be as unprotected. Also cursor should be present at 4th byte.
You should modify the map definition and split the field in two separate fields. This gives you the flexibility to protect or unprotect the different parts of your account number as necessary with very little effort. In addition you can easily use different colors for the first field to indicate its protection mode. This would make the map more meaningful to the user. The positioning of the cursor would also be just a trivial matter.