MVSFORUMS.com

[semigeezer]

The animation problem is interesting. Are you saying that you are able to tell what PFKEY was pressed during a control display lock/display panel() loop? I didn't think ISPF set that because while a panel is displayed with control display lock, ISPF is not sitting in a TGET state and thus has no way to get the interrupt. The only way I know to terminate that type of loop through user interaction is to have a STAX macro running either in the same task or a different task. I've never gotten the latter to work, but the former works. If you are able to tell what PF key is pressed, please post the code here. I'd love to use whatever technique is available.

There is some info on STAX in this context on the google 'groups' site.

[miboy]

Anand,

The word way should work, I tested it myself, I saw it working... U might want to Use the TRACE function to see what values are set

Miboy

[semigeezer]

Ravi, please see my last update which explains why a simple Rexx based screensaver in ISPF is not possible. You can break out of a lock/display loop gracefully with a STAX macro and exit, but that requires assembler, not Rexx. Something similar MAY be possible with a CLIST ATTN exit, but I don't think it can be done easily with Rexx. You might be able to do something with Signal in Halt and a PA1 key, but I'm not sure if that will get invoked or if the ISPF task will intercept the PA1 interrupt and crash the logical screen.

Rexx will not give you the control you need for password protection either, again, because it can be interrupted by a PA1 or ATTN key so it is not a security solution. That has to come from your session controller (VTAM, NetView, SuperSession, PIE, etc).

Finally, although networks are fast these days, you probably won't make any friends among the systems programmers at your shop if you regularly run something that causes your otherwise idle TSO session to remain swapped in and active.

[miboy]

Ravi,

REXX doesn't have the capability of what u r trying to do.... Just imagine the CPU usage if u were to run a screen saver with REXX, if u use a LOCK u will have to put an loop to display the same screen over and over .If ur group is charged for the CPU usage then maybe in a month or two u might need to find a new job....