LesK

From what little I know about Object programming, you should be able to put your method in it's own file and share it using the PUBLIC keyword and use the ::REQUIRES directive in both programs to tell the ooRexx interpreter where it is. Consult the ooRexx docs and examples. For the second problem, why not just pass the directory names and then simply reaccess the directories when you get control back?

What OS and what version of THE are you using?

It's not fair to directly compare old 32K/64K mainframe systems, where we worked directly with Assembler and managed our own memory, with a modern pc that uses some variant of C and depends on garbage collection to help manage memory. I vividly recall writing 4K diagnostic segments for TP equipment (2701 RPQ's) as my first 'test the waters' programming assignment. Just the design phase back then was dramatically different than what a pc programmer would do now with C.

I would guess that RV=1 tells you that the scroll succeeded. Wouldn't you want to know that, just in case your calculations were wrong? Les On 6/12/2018 3:06 AM, Norbert wrote: Hello world, I hope for an answer for my question: What can I do to avoid the return value 1 from the scroll method of a list view control? In my application, there is a list view control with several hundred data lines. One function of the application is to locate on a certain data line automatically depending on some other...

The problem is not with running ooRexx on the VM mainframe, since that will probably never happen except under a Linux cpu. The problem, as you have discovered, is that the VM programmer moving to a pc running ooRexx under the impression that the statement from the About ooRexx page: Upwardly compatible with classic Rexx means that his code will run unchanged under ooRexx. Yours is just one of many surprises awaiting such a novice.

This is just one of the many incompatibilities between ooRexx and Classic Rexx on the VM mainframe, where Rexx was invented. The behavior of: a= is different, and there are others as well. Note that Rexx on VM also has not been upgraded to the ANSI standard, to the best of my knowledge.

I'm quite sure that if ooRexx attempted to share a RXQUEUE between userids that zOS would raise a security exception!

say windows_version('oorexx') should give you what you're expecting.