If you mean that the 'field' can actually be multiple fields, (because you want the dashes to be protected on screen) then it's more difficult.
You can define it as a big field, allow any kind of typing to be input, reformat it programatically, and then redisplay the map with the dashes in the right place. This doesn't allow for protection though.
You can set up several maps, one for the top of the page, one for the bottom, and a series of different maps for the problem field. You can then use the ACCUM on the send map to send a composite map to the screen, changing the map on the middle section according to circumstances. This at least isolates the changes and avoids you having to amend 50 maps when the user wants an enhancement later on. But you have to know what the format is going to be before you send the map, i.e. if your screen has "Enter type:" at the top and the problem field has "Enter value:", then if the format of 'value' depends on what the user keys into 'type', you are out of luck. The 3270 is a dumb terminal, and you can't reformat the display on the fly without a round trip to CICS to redraw the screen.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.