Re: DSM example (was Using a timeout with display files)

If you are really using the Dynamic Screen Manager APIs and you need a good source for it then take a look at Thomas Raddatz website tools400.de. He has a very nice service program which wraps the pretty low level API from IBM. http://tools400.de/English/Freeware/Service_Programs/DSM/dsm.html

DSM APIs can be a real PITA to use so the service program helped me a lot.

Mihael


On 18.08.22 01:54, Frank Kolmann wrote:

Hi Patrik

DSM example program. DSMFD.

I have this code on GITHUB.  (Is it just me or is GITHUB so very very difficult to use?)
https://github.com/FrankKolmann/FranksRPG

It is a program that shows on a screen what a DDS file looks like using the compiled object.
It uses DSM to show.  Also there is a progam that uses the QDFDRTVFD api to get the DDS info.

Regards
Frank



On 16/08/2022 7:07 pm, Patrik Schindler wrote:

Hello Javier,

Am 16.08.2021 um 00:04 schrieb Javier Sanchez <javiersanchezbarquero@xxxxxxxxx>:

I've been dealing with the DSM documentation, but this is barely the API prototypes and the several data structures and constant values that these use. There are no significant examples and what I've found on the Web is also poor material.

So it's not just me. :-) Good to know!

I'll have to wrap up my sleeves and try.

I'd love to see some DSM examples somewhen, if you're willing to share your insights!

Since the input buffer is still there, that's the right moment to invoke the *QsnReadImm* API which is a non-AID-generating read input from the screen, and that should probably bring me the data that I'm expecting: the one the user may have typed in.

This proves (in a twisted way) my guts feeling of "there must be a possibility to do this". You know, the OS can set the message waiting indicator on a terminal at any time, without intervention from the currently running application. This made me think there *must* be an asynchronous way to obtain data from the terminal without any read or write in the usual way.

:wq! PoC