Thank you.
I had a response started with the SQL as Alan asked although before I added the eval statements to load the print line fields, the SQL worked fine.
But Paul's answer fixed it.
I was verifying before I added the write statement and got involved in whether I had set up the F spec correctly.
Thank you all. My mind must have started vacation before I can leave the office.
HTH,
TIA,
Thanks,
Whichever applies
Dave B
Sometimes I get the feeling the whole world is against me, but deep down I know that's not true. Some of the smaller countries are neutral. -- Robert Orben (comedy writer)
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of paul therrien
Sent: Thursday, January 05, 2012 2:46 PM
To: 'RPG programming on the IBM i / System i'
Subject: RE: SQL Report Program
Do you have a write statement to the output record format?
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Dave Boettcher
Sent: Thursday, January 05, 2012 2:12 PM
To: RPG programming on the IBM i / System i
Subject: SQL Report Program
For the last few hours I have been struggling to make sense of an SQLRPGLE
program I'm writing.
All of the input is through SQL and I want to produce a report that I've
defined as an external print file.
F specs:
fkcmunibk if e k disk
FTAX012P O E PRINTER oflind(*in89)
F infds(Prtds)
Everything looked good until I tried to use the fields I had defined in the
print file.
A R PAYDTL
A PXENTY R 2REFFLD(PXREC1/PXENTY TAPADT)
A PXPROP R 7REFFLD(PXREC1/PXPROP TAPADT)
A PXTAXP R 25REFFLD(PXREC1/PXTAXP TAPADT)
A PXDSCP R 41REFFLD(PXREC1/PXDSCP TAPADT)
A PXPENP R 55REFFLD(PXREC1/PXPENP TAPADT)
A PXINTP R 69REFFLD(PXREC1/PXINTP TAPADT)
A SPACEA(1)
A 2'Receipt Date:'
A PXDATE R + 1
A REFFLD(PXREC1/PXDATE TAPADT)
A 29'Receipt Number:'
A PXREC# R + 1
A REFFLD(PXREC1/PXREC# TAPADT)
No matter what I have changed, I can't get past that the verifier and the
compiler do not recognize the fields defined in the print file.
I get this error for all the print file fields:
PXDATE = T1.PXDATE;
RNF7030: The name or indicator PXDATE is not defined.
There must be something that I'm missing but so far I haven't seen it.
Do I have to define these fields somewhere else because they only exist at
output time or is it something else?
Any ideas?
TIA,
Thanks,
Whichever applies
Dave B
Sometimes I get the feeling the whole world is against me, but deep down I
know that's not true. Some of the smaller countries are neutral. -- Robert
Orben (comedy writer)
________________________________
The information in this e-mail message (including any information contained
in attachments hereto) is intended only for use of the addressee. This
e-mail message may contain confidential or privileged information. If you
receive this e-mail message unintentionally, please notify the sender
immediately and then delete this message. E-mail transmission is not
guaranteed to be secured or error free. The sender is not liable for any
errors or omissions in the content of this e-mail message, which may arise
as a result of e-mail transmission. E-mails, text messages, and other
electronic communications made or received in connection with the
transaction of public business, the expenditure of public funds, or the
administration of public property are subject to the Wisconsin Public
Records Law.
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/rpg400-l.
The information in this e-mail message (including any information contained in attachments hereto) is intended only for use of the addressee. This e-mail message may contain confidential or privileged information. If you receive this e-mail message unintentionally, please notify the sender immediately and then delete this message. E-mail transmission is not guaranteed to be secured or error free. The sender is not liable for any errors or omissions in the content of this e-mail message, which may arise as a result of e-mail transmission. E-mails, text messages, and other electronic communications made or received in connection with the transaction of public business, the expenditure of public funds, or the administration of public property are subject to the Wisconsin Public Records Law.
midrange.com
