Elardus > Ok. What about the ISPF attribute field, HILITE(BLINK)? I think if the OP wants blinking inside ISPF, he could use that?
I am not a specialist in programming ISPF - although I've done a wee bit of it in my time. Actually just one panel[1] and I happen to have preserved it. I note I did set up some extended attributes but I used them only at the *field* level - and I don't know whether or not it is possible in ISPF to set attributes at the character level. What you could do using field attributes is make the blinking character a field but then you would need to allow for three apparent or logical blanks between each word in your message which might be a bit of a limitation. > Interesting. According to my Ref Summary the x'3F' is 'SUB' and x'40' is > 'SP'. I wonder what is 'SUB'? I know SP is SPACE. Don't get hung up over the specific character, just try it. You could equally well use "@", for example, or "!" or "*" or anything that has the effect of drawing attention to the text you want read without causing any ambiguity if it happened to be read together with the text either side. >> According to the Communications Server SNA Messages manual, USS stands for Unformatted *Session* Services - ho hum! > What version? The V1R12 manual has the same text in the same place as the V1R11 manual I had downloaded already.[2] <quote> 17.0 Chapter 17. USS messages This chapter provides information on unformatted session services (USS) messages that are sent to the VTAM operator or a program operator, and USS messages that are sent to terminal users. For information on translating USS messages, see "User-selected message changes" in topic 1.7. </quote> Given that USS applies not only to assisting human operators initiate sessions but also to the customisation of any VTAM message, the word "session" is not sufficiently broad. - [1] Not counting one, ICQASE00, which is not displayed and is used for "seeding" APPC/MVS variables. [2] Thanks for the reminder to download *all* the V1R12 manuals before the end of the month since I still have some "volume" left in my ISP's monthly quota. - Chris Mason On Fri, 29 Apr 2011 07:02:03 -0500, Elardus Engelbrecht <[email protected]> wrote: >Chris Mason wrote: > >>This trick has nothing whatsoever at all to do with the content of mode tables >or any alteration of the "standard environment". This is purely a matter of >support for characters in the 3270 data stream implementation. Casting my >mind back, I think the old 3279 may have imagined it was rendering a solid >circle but it ended up the shape that requires skill to execute a "drop kick". > >[ ... rest of very good educational notes snipped for brevity ... ] > >Ok. What about the ISPF attribute field, HILITE(BLINK)? I think if the OP wants >blinking inside ISPF, he could use that? > >>You just need to put X'3F' into your data stream and make sure no busy- body >programming which thinks it knows better does anything to mess with it. > >Interesting. According to my Ref Summary the x'3F' is 'SUB' and x'40' is 'SP'. >I >wonder what is 'SUB'? I know SP is SPACE. > >>[1] According to the Communications Server SNA Messages manual, USS >stands for Unformatted *Session* Services - ho hum! > >:-D What version? > >My 1.10 SNA Messages does not show that, but I saw that ho-hum definition >too in 'z/OS Communications Server SNA Diagnosis Volume 2: FFST Dumps and >the VIT v1.10'! > >Ho-hum... ;-D > >Groete / Greetings >Elardus Engelbrecht ---------------------------------------------------------------------- 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
