Checking ZTDSELS across multiple screens

[gm333]

I have working Dialog Manager examples of how to process multiple line command selections on a single dialog manager screen by checking the value of ZTDSELS, and doing repeated display commands without specifying a panel name. What I have not been able to find is an example of processing multiple line command selection over multiple screens. ISPF option 3.4 is an example of this. You can select multiple 'B' (browse) line commands on one screen, hit PF8 to see more files, and enter more line commands on the second screen. When you stop hitting PF7 or PF8, and just hit ENTER, only then does it process all of the line commands you selected. Problem with using option 3.4 as a coding example is that you can't see the code because it's been compiled into a load module. I'd like to see an example of how to process those line commands across multiple screens. Can someone point me to such an example? Thanks.

 

[rexxhead]

Sounds pretty easy.

As the REXX routine gets control of the screen, just "do ztdsels", acquire the action code and the row-key, and queue them into the stack. When the proper key is pushed, "ENTER" or whatever, process the stack.

do queued()
   pull action tblkey .
   "TBGET" ...
   /* perform requested action */
end      /* queued */

Frank Clarke
--America's source for adverse opinions since 1943.

 

[stevexff]

I normally set a flag on the table itself, then just iterate over the table to process them when 'END' is pressed, but Frank's solution using the stack is equally valid...

Steve

[small]"Every program can be reduced by one instruction, and every program has at least one bug. Therefore, any program can be reduced to one instruction which doesn't work." (Object:erlDesignPatterns)[/small]