× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I've been a proponent of externally-defined PRTFs since working at Help Systems around 1990 - they used to have a product called PrintCoder that was a much better designer than RLU, but they decided to sell it and concentrate on automated operations, not diffuse their energies in other areas. I think it is out there under another name - maybe Gumbo's product.

I did learn to use RLU, although it's always a few minutes to get back to it, as we don't use PRTFs much here. Somehow it never seemed all that different to use PRTFs vs O-specs, just different keywords. But the Code Designer is cool.

Vern

At 07:47 AM 8/31/2007, you wrote:

I did the same thing, Tom: Internally-defined printer files. The only
way to define externally-described printer files was either manually,
which can be painful, or RLU, which is more painful. When WDSc came
bundled, though, and included Code Designer, my life changed
(hallelujah!). I still wind up fine-tuning the DDS manually upon
occasion, but by then it's just a matter of adding a keyword (HIGHLIGHT,
UNDERLINE, or such) here and there.

Is EXCPT even recognized by RSE as a free-form op-code? Since switching
to externally-described printer files, I haven't had to use it, so I
wouldn't know.


* Jerry C. Adams
*IBM System i Programmer/Analyst
B&W Wholesale Distributors, Inc.* *
voice
615.995.7024
fax
615.995.1201
email
jerry@xxxxxxxxxxxxxxx <mailto:jerry@xxxxxxxxxxxxxxx>


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.