|
Thanks Vern. There was some problem with naming convention I guess, as you mentioned. Thanks, -s Sudha Ramanujan SunGard Futures Systems sramanujan@xxxxxxxxxxxxxxxxxx (312) 577 6179 (312) 577 6101 - Fax -----Original Message----- From: Vern Hamberg [mailto:vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx] Sent: Thursday, May 13, 2004 6:14 PM To: Midrange Systems Technical Discussion Subject: Re: Table_name in views Hi, Sudha What is keeping you from using Table_Name? What message are you getting? If your table name has spaces in it, try surrounding it with quotation marks. Now, to have a good system view name, make sure you keep the table name to 10 characters and that it have no spaces and that it does not start with a numeral. There are some other rules - basically make it like a standard AS/400 object name. There must be something in the SQL Reference on naming with long names. HTH Vern At 01:31 PM 5/13/2004, you wrote: >HI all, >I am trying to a jdbc java call to a view, a view that was created in >AS/400. I am not able to use the Table_Name instead have to use the >System_View_name (from the sysviews), that is generated by IBM default >view definers. I don't have any standard to these names. Is there >anyway I could use Table_Name or create my view with meaigful >System_view_names? >Thanks for your help, >Sudha > >Sudha Ramanujan >SunGard Futures Systems >sramanujan@xxxxxxxxxxxxxxxxxx >(312) 577 6179 >(312) 577 6101 - Fax _______________________________________________ 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.