>You seem to have a sandbox available to you so I would like to suggest some >more tests.
Yes, but only as time permits - I am working on those tests, but felt you should know I haven't dropped the discussion. >Note that there's not too much point in checking the TN3270 implementation >with "@"-based variables since the only possibly difficult one is @HOSTNET, >having only one "@" character. It's highly unlikely someone would use an SBA ending with x'7C', the '@' character, and immediately follow that with the character string, '@PRT', resulting in the text '@@PRT' but, 'highly unlikely' is just the type of open pit someone eventually falls into. It's also 'highly unlikely' someone would turn off the main power to the data center, but I've seen it happen twice. >Which reminds me I got something wrong regarding the MDT in a previous> >post. Recall that the "&" character when used as an attribute byte implies >an "unprotected", "input", field. I suggested it was unlikely without the MDT >bit. I'm not sure most people know the difference. I believe the ampersand (x'50') is representative of the unprotected numeric field without the MDT and with normal intensity, not light-pen detectable. It's 'highly unlikely' and even slightly absurd to follow this with a non-numeric string like 'SYSNAME'. (Defining a numeric input field and filling it with non-numerics). ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
