Another JDBC (and by extension, JDBCR4) meta-data retrieval question

Given a test PF defined in good-old-fashioned DDS as follows (extra spaces squeezed out):

A UNIQUE
A R TEST04AP13
A PACKED 5P 0
A FLOAT1 7F 0
A DOUBLEFLT1 15F 0 FLTPCN(*DOUBLE)
A FLOAT2 7F 2
A DOUBLEFLT2 15F 7 FLTPCN(*DOUBLE)
A FLOAT3 7F 6
A DOUBLEFLT3 15F14 FLTPCN(*DOUBLE)
A K PACKED

Notice that the floating point fields have "preferred" number of decimal places defined.

If I get the meta-data the old-fashioned way, via the system APIs, then I can get the preferred number of decimal places, and QuestView pays attention to that, and displays them thusly:

PACKED . . . : 12345
FLOAT1 . . . : 1234500.E-002
DOUBLEFLT1 . : 123456789000000.E-005
FLOAT2 . . . : 12345.00E+000
DOUBLEFLT2 . : 12345678.9000000E+002
FLOAT3 . . . : 1.234500E+004
DOUBLEFLT3 . : 1.23456789000000E+009

But if I get the meta-data through a JDBC connection, then getScale() always returns zero, meaning that I have to arbitrarily decide the preferred number of decimal places to show.

Unless there's another way of getting that value via JDBC?

****
While I'm at it: I note that if I use a view name instead of a table name, I don't see the table's primary key, and neither do I see any indexes. So apparently, I need to have the table name in order to get primary key and index information.

Can anybody point me in the right direction on how to get from a view to its based-on table(s) via JDBC, so I can look up the keys? (And yes, I know, views that aren't DDS LFs don't have their own indexes built in.)

--
JHHL