View previous topic :: View next topic
|
Author |
Message |
Machani Hanuprasad
New User
Joined: 06 Jun 2012 Posts: 11 Location: India
|
|
|
|
Hi,
i have an requirement like below:
> 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.
Please can any one look on this |
|
Back to top |
|
|
PeterHolland
Global Moderator
Joined: 27 Oct 2009 Posts: 2481 Location: Netherlands, Amstelveen
|
|
|
|
Try this :
Redefine the 8 byte field in 2 fields (3 and 5 bytes).
Then do a dynamic modification of the attributes. |
|
Back to top |
|
|
Stefan
Active User
Joined: 12 Jan 2006 Posts: 110 Location: Germany
|
|
|
|
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. |
|
Back to top |
|
|
Bill O'Boyle
CICS Moderator
Joined: 14 Jan 2008 Posts: 2501 Location: Atlanta, Georgia, USA
|
|
|
|
Try inserting X'1DF0' in the first two-bytes and see if this (at least) ASKIP's positions one and two and we'll go from there.
I'm not an advocate of doing this and don't generally promote it.... |
|
Back to top |
|
|
|