× 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 agree, Edmund. One could find it in *ALL or *ALLUSR, too - but even then, it might not have the same name. I was a temp (in the 80s) at a big company here in the Twin Cities who used an S/36, and there was contractor who all of a sudden wasn't there after lunch - turned out he thought he had job security, he had used objects names that were all different from the source name!! Someone else came in eventually and hooked things up. I don't know, but I assume the objects had the source name in them - just as they do now on the IBM i.

So that brings up a thought - there's an SQL service now for object information, I think, maybe it has the source information there, too. I admit, it might be a bit slow - but maybe there's something Scott and his crew can come up with for this specific purpose.

Anyhow, just some more thoughts before lunch!

Cheers
Vern

On 6/18/2020 11:08 AM, Edmund Reinhardt wrote:
The only challenge is finding the compiled PRTF object given the PRTF
source member.  You could assume that it is in the same library or the
*CURLIB but that assumption will not always be true.
______________________________________________________________________________________

Edmund Reinhardt [1][IMG]
905-413-3125
IBM Canada Ltd   Rational Developer for i Access Client Solutions
Architect
[2]https://www.linkedin.com/in/edmundreinhardt/   [3]http://ibm.biz/rdi_hub [4]http://ibm.biz/IBMi_ACS


----- Original message -----
From: Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx>
To: Rational Developer for IBM i / Websphere Development Studio Client
for System i & iSeries <wdsci-l@xxxxxxxxxxxxxxxxxx>
Cc:
Subject: [EXTERNAL] Re: [WDSCI-L] Using RDi Report Designer on a print
file larger than 132 characters
Date: Wed, Jun 17, 2020 6:25 PM
It might not be necessary to go through all that - an existing PRTF has
the width as one of its attributes, right? Or is there a way for it not
to?

But an API exists to get what DSPFD has.

The issue, as I've been thinking it through today, is for existing
PRTFs, where wider ones are not automatically opened with their full
width. That's be the import of an RFE I submit.

Cheers, y'all!
Vern

As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.