Re: Window in 2nd pgm?

[Mark Waterbury <mark.s.waterbury@xxxxxxxxxxxxx>]

Justin,

The QSN APIs are part of DSM the Dynamic Screen Manager -- DSM APIs operate at the level of 5250 data streams, below the level of any "display file."   The DSM has no knowledge of "display files" at all.

This DSM API actually queries the device (a 5250-family terminal or emulator session) to learn what screen size is currently in use.

I hope this explanation helps aid your understanding of what is going on -- or what it is doing, and why that works..

Mark S. Waterbury

> On Thursday, August 28, 2025 at 02:01:26 PM EDT, Justin Taylor <jtaylor.0ab@xxxxxxxxx> wrote:

It looks like I was wrong.  The QsnRtvMod API does work to detect the
screen size from  the calling program.

Thanks guys!

On Thu, Aug 28, 2025 at 8:22 AM Charles Wilt <charles.wilt@xxxxxxxxx> wrote:

> Yes the code Mark linked to shows the check being called from the popup
> window.
>
> TLDR;
> The key to making our popup window display in the correct mode requires the
> following steps:
>
>
>     1. The (popup) display file should be user open (UsrOpn on the F spec)
>     so that we can set the size mode before the file is opened
>     2. Detect the current screen mode size by using the Screen_SizeIs27x132
>     functio
>     3. Set the display mode size of our popup window program to the current
>     mode
>     4. Open the display file
>     5. Display the popup screen
>
> Ignore what's being done in the test driver.
>
> The QsnRtvMod API mentioned by another poster won't work, it simply tells
> you if a display supports 27x132.
> I've used that to display a message asking the user to call the help desk
> to get their session reconfigured as I had a new application that only
> worked on 27x132.
>
> HTH,
> Charles