|
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 -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Vern Hamberg Sent: Tuesday, September 02, 2003 9:21 PM To: Midrange Systems Technical Discussion Subject: Re: Does SST does not support Variable length field in logical ? Unfortunately, there are no fixed length fields for these things in this file, as far as I can tell. Could you redefine the fields as character in the logical, then SST those new fields? This would be like a logical that redefines packed fields as zoned. BTW, is there a reason not to use the already-existing view in QSYS2? Of course, that means using SQL, more than likely, and it also has the VARCHAR fields. Vengoal, can you say more about the need for getting this information? Will you be reading it in a program, or creating a report from it? If the latter, I strongly suggest using QM forms and QM queries. If the former, RPG can use variable length fields, or you could use SQL in the program easily. An odd thing about the file in question is the use of allocated length. The varchar fields for file and library have an allocation of 10, which makes sense. But the fields for program and library have allocation of "None" - is that the same as 0? But maybe there's no point in worrying about this when there are many other fields with no allocation, because that already forces reading the auxiliary space where variable data is held. Also, there are a couple CLOBs, thousands of bytes long, for some path names, best as I can tell on short notice. Regards Vern 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 > >also, you could use the fixed length system fields in that table for >the library and file names, then you could substring them. Since the >system names are 10 max, you should not have to use the variable length >names unless you ARE using SQL already. > > >=========================================================== >R. Bruce Hoffman, Jr. > -- IBM Certified Specialist - iSeries Administrator > -- IBM Certified Specialist - RPG IV Developer > >"When I die, I want to die like my grandmother who died peacefully > in her sleep. Not screaming like all the passengers in her car." > > - Author Unknown > >----- Original Message ----- >From: "Vengoal Chang" <vengoal@xxxxxxxxxxx> >To: "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx> >Sent: Monday, September 01, 2003 11:10 PM >Subject: Does SST does not support Variable length field in logical ? > > > > Dear folks, > > 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. > > > > Best regards, > > > > Vengoal _______________________________________________ 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.
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.