|
Thanks for your reply Vernon
First the bad news - we DON'T have RDi
Now the good news - after MUCH cajoling, pleading, groveling, crying,
swearing - on my part - we are finally getting RDi
Just have to wait for the red tape etc.
This has nothing to do with my original question as I have
resigned/accepted that I need to do an external print file and am capable
of doing so with PDM
What DID catch my eye in your e-mail, was the link for the RDi tutorials
I haven't had a chance to look at this link, yet
But I appreciate you passing this on
Alan Shore
E-mail : ASHORE@xxxxxxxx
Phone [O] : (631) 200-5019
Phone [C] : (631) 880-8640
'If you're going through hell, keep going.'
Winston Churchill
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf
Of Vernon Hamberg
Sent: Thursday, July 25, 2019 12:20 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: [EXTERNAL] Re: Free form for a printer and o specs
Hi Alan
SImple or not, I strongly concur with the suggestions to use a PRTF -
would you ever write display code the way it was done on the 36? And
probably still can be on the IBM i?
PRTFs are also very easy, and there is a nice designer in RDi. There are
tutorials for RDi at http://ibm.biz/rdi_labs - Lab 09 deals with Report
Designer.
If you're using PDM, there is always RLU, which can do well enough.
Good luck!
Vern
On 7/25/2019 8:23 AM, Alan Shore via MIDRANGE-L wrote:
Thanks Robanything other than the most basic of reporting. For a "quick and dirty"
Its just a small report - nothing fancy
Alan Shore
E-mail : ASHORE@xxxxxxxx
Phone [O] : (631) 200-5019
Phone [C] : (631) 880-8640
'If you're going through hell, keep going.'
Winston Churchill
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On
Behalf Of Rob Berendt
Sent: Thursday, July 25, 2019 9:07 AM
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: [EXTERNAL] RE: Free form for a printer and o specs
Use of O specs, even in fixed form, have a very limited use when using
they may be acceptable. But look at creating a printer file with DDS.
Then in RPG you write to that instead of using O specs, etc.
Mail to: 2505 Dekko Drive
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600
Garrett, IN 46738click links or open attachments unless you recognize the sender and know
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Justin Taylor
Sent: Thursday, July 25, 2019 9:01 AM
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: Free form for a printer and o specs
CAUTION: This email originated from outside of the organization. Do not
the content is safe.
externally-described print file. Alternatively, you can use an /INCLUDE
You can't do O-specs (or I-specs) in **FREE. You should probably use an
compiler directive to put the fixed-format O-specs in a different source
member.
could THAT be due to what I am searching for?
-----Original Message-----
From: Alan Shore via MIDRANGE-L [mailto:midrange-l@xxxxxxxxxxxxxxxxxx]
Sent: Thursday, July 25, 2019 7:56 AM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Cc: Alan Shore <ashore@xxxxxxxx>
Subject: Free form for a printer and o specs
Hi everyone
We are on V7r3
Its been a while since I wrote a new program that produces a spool
file
With free-form, you declare a printer like
dcl-f SLSRPT0055 Printer OflInd(pageFull);
However - did anything replace the o-specs?
Ive done a google search and haven't really found anything - but then -
https://archive.midrange.com/midrange-l.
As always - all answers gratefully accepted
Alan Shore
E-mail : ASHORE@xxxxxxxx
Phone [O] : (631) 200-5019
Phone [C] : (631) 880-8640
'If you're going through hell, keep going.'
Winston Churchill
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
questions.
Please contact support@xxxxxxxxxxxx for any subscription related
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
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.