Re: Where do I start?

Ron Hudson <[email protected]>
Newsgroups gmane.comp.emulators.turnkey-mvs
Message-ID <[email protected]>
On Tue, May 25, 2010 at 12:58 PM, Rick Fochtman <[email protected]> wrote:

> ---------------------------------------<snip>-----------------------------
> Only if the user does not edit that field.. If the user edits the field
> the MDT is set for you.
>
> Right now I am trying to get underlinded fields to work - my first field
> starts underlining but it never stops to the end of the screen
>

I have progressed past this and the square bracket issue below (read 'gave
up')
but I am prefilling my fields with '.' (Periods) just to see where they are.

I wanted to delimit my fields with the bracket but the attribute byte got in
the way
so it would have had to be bracket - space - field - space - bracket.. hmm
that might
not be too bad. anyway - later for that.


> ---------------------------------------<unsnip>---------------------------
> You need to do a START FIELD with appropriate attributes, followed by a
> REPEAT-TO-ADDRESS followed by your underlining character. And make sure
> you follow the command format exactly. RTA, two-byte address, character
> to be repeated.
>
> If you're interested, I can share a pair of simple TPUT/TGET subroutines
> that are written in Assembler, designed for call from high-level
> language code.
>
>
> ---------------------------------------<snip>-----------------------------------
> Oh and is '[' Square bracket not a mainframe character?  when I try to
> place one in RPF I get a U with an accent of some sort.
>
> --------------------------------------<unsnip>----------------------------------
> Square brackets are not part of the EBCDIC character set; square
> brackets and braces are not part of the 3270 character set.
>

That was my final guess too.


>
> Rick
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.