RE: Does SST does not support Variable length field in logical ?

["Vengoal Chang" <vengoal@xxxxxxxxxxx>]

I compiled it on V5R2, still got the same error. My system have
secondary language QSYS2987, and DBCS enabled. Does some one have any
idea ?

Best regards,

Vengoal

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Wednesday, September 03, 2003 9:53 PM
To: Midrange Systems Technical Discussion
Subject: RE: Does SST does not support Variable length field in logical
?


Source code that you posted to the RPG list compiled on my V5R2 machine.

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 





Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
09/03/2003 08:47 AM
Please respond to Midrange Systems Technical Discussion
 
        To:     Midrange Systems Technical Discussion 
<midrange-l@xxxxxxxxxxxx>
        cc: 
        Fax to: 
        Subject:        RE: Does SST does not support Variable length 
field in logical ?


Well, now I'm confused - I used your source on our V5R1 machine, and it 
compiled just fine. This looks like a bogus error. I suggest you call
IBM 
support, as this is not correct.

There is no VARCHAR data type in DDS, only A for character (actually, 
alpha). This is modified with a keyword to make the field
variable-length. 

The message says the type must be A, S, H, or G in position 35. Of
course, 

we don't have the source for the file in question, but these fields ARE 
character fields, and SST did work for me. And I'm not all that special.

Maybe others have ideas why this does not work for you.

HTH

Vern

At 10:23 AM 9/3/2003 +0800, you wrote:
>Thanks your help,
>Now I am testing the Tracking Triggers  by Doug Eckersley from 
>Mcpressonline
>   http://www.mcpressonline.com/mc?1@xxxxxxxxxxxxxxxxx@.6ae73ce8 , and 
>I could not compiled LF which contain system table variable field. I 
>can test your suggestion. Do you have any other idea ?
>
>Best regards,
>
>Vengoal

<snip>

>At 07:44 AM 9/2/2003 -0400, you wrote:
> >two things, varchar is not char, as it begins with a binary value, so

> >no, sst in dds does not work but, substr in sql on a view will work

<snip>

> > > I want to retrieve some information from system file QADBXTRIGB on
> > > V5R1: I create as following statement LF, but cannot compiled. The

> > > error message is
> > > CPD7616   : Keyword ignored because of error in list of values.
> > > CPD 7964 : Field on SST keyword must be character or zoned 
> > > decimal.
> > >
> > >      A          R MXTTTR                    PFILE(QADBXTRIGB)
> > >      A            TFFILE             I      SST(DBXTBTNAME 1 10)
> > >      A            TFLIB              I      SST(DBXTBTLIB 1 10)
> > >      A            TTPGM              I      SST(DBXTBPGM 1 10)
> > >      A            TTLIB              I      SST(DBXTBPGML 1 10)
> > >
> > > And I check those fields in QADBXTRIGB all Variable length field, 
> > > if
>
> > > I changed SST to other fixed length field, compiled no problem. 
> > > Does
>
> > > SST does not support Variable length field ? Any help will be 
> > > appreciated.


_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.