I have a client app that calls an RPG program to view images. When I
click on the CMD key in HATS, it tells me it's getting the image and
then the HATS screen never updates. However, on the host terminal, the
green screen changes to say it can't find the image, and then boots me
back to the originating screen (where I pressed the CMD key). Meanwhile,
HATS is still hanging on the "getting image" page. I can use the browser
refresh button and it will come back to the current screen.

I am guessing that HATS needs some sort of a listener that will notice
the green screen has changed? I am at wits end, and I am not sure how to
fix this. Any help would be greatly appreciated.

-Dee M

[ Post a follow-up to this message ]

Might want to try the enabling the refresh applet



> I have a client app that calls an RPG program to view images. When I
> click on the CMD key in HATS, it tells me it's getting the image and
> then the HATS screen never updates. However, on the host terminal,
> the green screen changes to say it can't find the image, and then
> boots me back to the originating screen (where I pressed the CMD
> key). Meanwhile, HATS is still hanging on the "getting image" page. I
> can use the browser refresh button and it will come back to the
> current screen.
>
> I am guessing that HATS needs some sort of a listener that will
> notice the green screen has changed? I am at wits end, and I am not
> sure how to fix this. Any help would be greatly appreciated.
>
> -Dee M

[ Post a follow-up to this message ]

To know if you need the refresh applet, add the HATS keypad to the page and
hit the "refresh" button.  HATS should then render the new screen it now
sees in the presentation space (terminal), without sending any host keys or
data.  This should be your error message screen.

This all relates to screen settling, which hasn't been well documented until
now.  Check the online V6 info center on this topic.  The applet is part of
the story, but so are the screen settling algorithms.

BTW: Settling is all about solving the problem of presenting a changable
terminal screen (ie. the host can update the screen at any time) out to a
stateless web world.

"Jackson Brown" <brownee@hotmail.com> wrote in message
news:d1nfa0$54ba$1@news.boulder.ibm.com...
> Might want to try the enabling the refresh applet
>
>
> 
>

[ Post a follow-up to this message ]

This did work, but the response time needed is making all of the screens
render way too slow.

David Smart wrote:
> To know if you need the refresh applet, add the HATS keypad to the page an
d
> hit the "refresh" button.  HATS should then render the new screen it now
> sees in the presentation space (terminal), without sending any host keys o
r
> data.  This should be your error message screen.
>
> This all relates to screen settling, which hasn't been well documented unt
il
> now.  Check the online V6 info center on this topic.  The applet is part o
f
> the story, but so are the screen settling algorithms.
>
> BTW: Settling is all about solving the problem of presenting a changable
> terminal screen (ie. the host can update the screen at any time) out to a
> stateless web world.
>
> "Jackson Brown" <brownee@hotmail.com> wrote in message
> news:d1nfa0$54ba$1@news.boulder.ibm.com...
> 
>
>

[ Post a follow-up to this message ]

This problem can be solved without the applet enabled.  The customization
must wait until the screen settles.  I have code to handle this.  Contact me
for details. dougpiner@yahoo.com .

Doug

"Dee M" <dmcwhorter@cgcsolutionsgroup.comNOSPAM> wrote in message
news:d1vilg$vre$1@news.boulder.ibm.com...[vbcol=seagreen]
> This did work, but the response time needed is making all of the screens
> render way too slow.
>
> David Smart wrote: 
and[vbcol=seagreen] 
or[vbcol=seagreen] 
until[vbcol=seagreen] 
of[vbcol=seagreen] 
a[vbcol=seagreen] 

[ Post a follow-up to this message ]