×

Good News Everybody!

A new search engine is coming soon.

As a stop gap measure, we are using Google's custom search engine service.




Those fields are not in QADBIFLD. As for SYSCOLUMNS, these are really meant for 
SQL, and SQL does not use the idea of reference fields as DDS does. I believe 
the reference information is coming from somewhere other than the QADB* files.

Sorry

-------------- Original message -------------- 

> Thanks Rob. 
> I originally looked at QSYS2/SYSCOLUMNS but couldn't find the field. 
> Perhaps I've missed something? None of the field text values seem to 
> refer to the same field as in QDSPFFD. The fields in the record format 
> of QADBIFLD that I need are: 
> 
> WHRFIL QADSPFFD Reference file 
> WHRLIB QADSPFFD Reference library 
> WHRFMT QADSPFFD Reference record format 
> WHRFLD QADSPFFD Reference field 
> 
> I can't see any of these in SYSCOLUMNS. None of the fields in SYSCOLUMNS 
> seem to have these field texts. 
> 
> I tried building my own view over the physical but ran into the same 
> authority problems. 
> 
> -----Original Message----- 
> From: midrange-l-bounces@xxxxxxxxxxxx 
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx 
> Sent: Thursday, May 26, 2005 11:05 PM 
> To: Midrange Systems Technical Discussion 
> Subject: Re: QADBIFLD Question 
> 
> 
> Do you have access to SYSCOLUMNS? It's in QSYS2 but that should be in 
> your library list. It's a logical built over the physical. There are 
> ways to lock a person out of the physical but let them access it via the 
> 
> logical. 
> 
> If you are able to see the structure, then that should be all you need. 
> You aren't trying to open it with a utility that needs update access are 
> 
> you? I think that is your problem. 
> 
> DSPOBJAUT... 
> Object 
> User Group Authority 
> *PUBLIC USER DEF 
> QSYS *ALL 
> 
> Object ----------Object----------- 
> User Group Authority Opr Mgt Exist Alter Ref 
> *PUBLIC USER DEF 
> QSYS *ALL X X X X X 
> 
> Object ---------------Data--------------- 
> User Group Authority Read Add Update Delete Execute 
> *PUBLIC USER DEF X 
> QSYS *ALL X X X X X 
> 
> Rob Berendt 
> -- 
> Group Dekko Services, LLC 
> Dept 01.073 
> PO Box 2000 
> Dock 108 
> 6928N 400E 
> Kendallville, IN 46755 
> http://www.dekko.com 
> 
> 
> 
> 
> 
> "Mike Pantzopoulos - \(H/O\)" 
> Sent by: midrange-l-bounces@xxxxxxxxxxxx 
> 05/25/2005 06:11 PM 
> Please respond to 
> Midrange Systems Technical Discussion 
> 
> 
> To 
> 
> cc 
> 
> Subject 
> QADBIFLD Question 
> 
> 
> 
> 
> 
> 
> I've been looking for the reference field attribute in the SQL catalog. 
> 
> This value is obtainable from the DSPFFD command and I presumed it would 
> also be available through the SQL interface. I seem to recall seeing it 
> in the QSYS/QADBIFLD file but I don't have authority to that file. I'm 
> trying to do an audit of our system and would dearly love to have access 
> to this information through the SQL catalog rather than the more 
> circuitous methods. 
> 
> I have been able to see the structure of the QADBIFLD format and it 
> looks exactly like the DSPFFD output format. 
> 
> Is there anyway of getting access to this attribute through SQL? Either 
> directly from the file or via a view? I've had a look at what's 
> available through the catalog vews but can't seem to find the reference. 
> 
> Thanks. 
> 
> Mike Pantzopoulos 
> 
> EIG-Ansvar Limited 
> Tel : 61 (3) 9614 3535 
> Fax: 61 (3) 9614 2740 
> 
> 
> 
> ************************************************************************ 
> ********************************* 
> This email and any files transmitted with it are confidential and 
> intended 
> solely for the use of the individual or entity to whom they are 
> addressed. 
> If you are not the intended recipient, any use, disclosure or copying of 
> 
> this message is unauthorised. If you have received this message in 
> error, 
> please reply using the sender's email address. 
> 
> This footnote confirms that this email message has been scanned for 
> computer viruses. EIG-Ansvar Limited does not accept liability for any 
> loss or damage, whether caused by our own negligence or not, that 
> results 
> from a computer virus or defect in the transmission of this email or any 
> 
> attached file. 
> EIG-Ansvar Limited - Australia (A.B.N. 21 007 216 506) 
> Email : insure@xxxxxxxxxxxxxxxx 
> 
> Eig-Ansvar Limited - New Zealand 
> Email : insure@xxxxxxxxxxxxxxxx 
> 
> ************************************************************************ 
> ********************************* 
> 
> -- 
> 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. 
> 
> 
> -- 
> 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 thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2026 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.