× 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.



This feature is one part of RLU that was pretty useful - IF you used RLU to create the PRTF after editing it.

I think this would be a good thing in the Designer - this page size thing is one of the items I find a bit awkard - might just that it's different - but as I recall you have to set up a "report", where you can set this stuff - I would like it to be independent of some extra steps inside RDi myself.

So I suggest you submit an RFE for what you're looking for - and I guess I have one I should put in there!

Cheers
Vern

On 5/29/2015 11:37 AM, Terry Hertel wrote:
I don't see how that will help. I still have to look at the printer file size before entering the command. Shouldn't RDi be able to pre-fill the size when I select the Compile/Compile (Prompt) option in RDi?
------------------------------

message: 2
date: Thu, 28 May 2015 21:00:56 +0000
from: "Tyler, Matt" <matt.tyler@xxxxxxxxxxxxxx>
subject: Re: [WDSCI-L] Page size when compiling printer files

Use this command ? CRTPRTF ?*PAGESIZE(68 132) and it will appear but be locked out.

? CRTPRTF ??PAGESIZE(68 132) allows for the value to be modified.


Thanks, Matt


-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Terry Hertel
Sent: Thursday, May 28, 2015 2:57 PM
To: wdsci-l@xxxxxxxxxxxx
Subject: [WDSCI-L] Page size when compiling printer files

Thought I would run this by everyone before submitting an RFE. When we create a printer file in RDi we give it the page size (lines and columns). When I compile the printer file using the Compile (Prompt) option, the default page size values for me are 66x132. Since I have already specified the page size, would it make sense for RDi to display those values in the CRTPRTF prompt? That would be easier than looking at the header documentation or prompting the CHGPRTF command in green screen.
--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l.


------------------------------

message: 3
date: Thu, 28 May 2015 17:14:39 -0400
from: Buck Calabro <kc2hiz@xxxxxxxxx>
subject: Re: [WDSCI-L] Page size when compiling printer files

On 5/28/2015 4:56 PM, Terry Hertel wrote:
Thought I would run this by everyone before submitting an RFE. When we create a printer file in RDi we give it the page size (lines and columns). When I compile the printer file using the Compile (Prompt) option, the default page size values for me are 66x132. Since I have already specified the page size, would it make sense for RDi to display those values in the CRTPRTF prompt? That would be easier than looking at the header documentation or prompting the CHGPRTF command in green screen.
Craig Rutledge has a tool for this:
http://www.jcrcmds.com/jcrdown2.html#JCRPATTR_tag

You might also consider Alan Campin's COMPILE preprocessor but it'll
take a bit of work to add printer file support to the up front compile
command.

There may be an RFE for RDi to 'remember' the specifics for each
separate compile [i.e. member A has dbgview(*source), member B has
dbgview(*list)] but I couldn't quickly put my finger on it.



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.