Re: RDi Not recognizing the end of table data

Hmm, I rarely use CTDATA, but I seem to recall that any local procs in
that source are actually placed AFTER the table data (CTDATA goes after
O-specs, before P-spec). I prefer Jerry's suggestion to define data in
the D-spec.

-Eric

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Kevin Bucknum
Sent: Friday, April 09, 2010 11:39 AM
To: Rational Developer for IBM i / Websphere Development Studio
ClientforSystem i & iSeries
Cc: BBateman@xxxxxxxx
Subject: Re: [WDSCI-L] RDi Not recognizing the end of table data

Table data must always be the last thing in a program. After the first
**, everything else is table data.

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of DLee@xxxxxxxx
Sent: Friday, April 09, 2010 11:18 AM
To: wdsci-l@xxxxxxxxxxxx
Cc: BBateman@xxxxxxxx
Subject: [WDSCI-L] RDi Not recognizing the end of table data

Hi

Could use some help on understanding what's happening;

Below is the code for defining a table and it's related table data:

DaRowDesc 17a DIM(4) PERRCD(01) CTDATA
**CTDATA aRowDesc
Net Premium
Earned Premium
Paid Claims
Earned Commission

After putting this code in all the code below such as calculations were
changed from there respective colors such as Operation codes in (RED)
etc... they were all turned to GREEN like RDI thinks it is part of the
Table Data.

Appreciate any help you can provide

Darrell

Regards,



SWBC
9311 San Pedro Ave., Suite 600
San Antonio, TX 78216

Visit our website at www.swbc.com



Kevin Bucknum
Senior Programmer Analyst
MEDDATA/MEDTRON
Tel: 985-893-2550