|
> -----Original Message----- > From: midrange-l-bounces@xxxxxxxxxxxx / James H. H. Lampert > Sent: Sunday, September 19, 2004 9:36 PM > > If anybody's interested, I ended up copying UIM *PNLGRP source out of > the manuals into a terminal emulation session (our emulator, of > course!), and calling the appropriate UIM APIs directly from CL, and the > result works beautifully. > > It was a total <female canid> to get the *PNLGRP to compile, though, and > a pain in the <equus asinius> to figure out how to make F3, F12, and > <ENTER> all get one out of the list. A serious question: Now that you have done it, would you say that you would have been better off just writing the RPG program? My experience with UIM is one application, a WRKSPLF clone, written by Mike Cravitz back in '96. I modified it to better suit my needs, and even that was a pain in the <horse's arse>. There's still some behavioral characteristics that I haven't been able to duplicate like IBM's Work With UIMs. For example, in my version of LSTSPLF, option 9 is CPYSPLF. Usually, I like to type some of the parameters on the command line, especially if I'm using the option on multiple entries. Unfortunately, if you do that *and* press F4 to prompt CPYSPLF, the parameters you typed on the command line don't "carry forward" into the command prompt. Little crud like that "encouraged" me to waste hours of time on a dead end. Maybe it's better now, but I remember being frustrated at the lack of useful UIM documentation. In the end, I had (and still have) a working application but, IMNSHO, UIM is just too much of a pain to work with. Maybe if it came with an SDA-like developer tool it could be easier to work with. db
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.