Conference orarep::nomahs::dbintegrator_public_public

    Hi Martti,
    
    Can you provide a little more information please?  Is MAKSULAJIN_TUNNIS
    another structure?
    
    Thanks,
    Don

Hi,
	Here are two records definitions used in rms files.
	I was too lazy to write the whole record of finnish 
	field names...-:)
	Sorry but couln't get the info about MAKSULAJIN_TUNNUS
	from the cust.
	Hope this helps
Martti




define record lar025.
lar025_lasku_structure.
lar025_lasku_avain structure.
lar025_yritysnumero structure.
lar025_yritysno			copy from yritysno.
lar025_tulosyksikon_nro		copy from tulosyksikon_nro.
END lar025_yritysnumero structure.
lar025_lainanumero		copy from laino
lar025_erapvm			copy from vvvkkpp.
end lar025_lasku_avain structure.
lar025_laskunro structure.
lar025_vuosi 		datatype is unsigned numeric size is 2 digits.
lar025_kirjenro         datatype is unsigned numeric size is 5 digits.
END lar025_laskunro structure.
lar025_tieto structure.
lar025_laskun_tilan_tun		copy from laskun_tilan_tun.
lar025_laskut_muist_pvm		copy from vvvkkpp.
lar025_laskun_maara		copy from rahamq.
lar025_laskurivi_lkm		copy from indeksi.
lar025_laskurivi structure occurs 1 to 30 times
				depending on lar025_laskurivi_lkm.
lar025_laskurivi_avain structure.
lar025_laskurivin_tunnus	copy from maksulajin_tunnus.
lar025_korkovalin_alkupvm	copy from vvvvkkpp.
lar025_korkovalin_loppupvm	copy from vvvvkkpp.
END lar025_laskurivi_avain structure.
lar025_koron_paaoma		copy from rahamq.
lar025_korko_pros		copy from korkopro.
lar025_vakuus_pro		copy from korkopro.
lar025_osit_maksun_osoitin	copy from osit_maksun_osoitin.
lar025_laskurivin_mitat_oso	copy from mitatoinnin_osoitin.
lar025_laskurivin_maara		copy from rahamq.
END lar025_laskurivi structure.
END lar025_tieto structure.
END lar025_lasku_structure.
END lar025 record.

********************************************
define record lar060.
lar060_korkokannat structure.
lar060_korkokanta_avain structure.
lar060_sovellustunnus		copy from korkoluokan_tunnus.
lar060_sovellustunnus		copy from sovellustunnus.
lar060_lainanumero		copy from laino.
END lar060_korkokanta_avain structure.
lar060_tieto structure.
lar060_korkoluokan_nimi		datatype is text size is 20 characters.
lar060_korko_lkm		copy from indeksi.
lar060_korkokanta structure occurs 1 to 20 
				depending on lar060_korko_lkm.
lar060_koron_voimaantulopvm	copy from vvvkkpp.
lar060_korko_pros		copy from korkopro.
lar060_vakuus_pros		copy from korkopro.
END lar060_korkokanta structure.
END lar060_tieto structure.
END lar060_korkokannat structure.
END lar060 record.

Martti,

I am assuming that things like, "yritysno" and "tulosyksikon_nro" are records or
structures that are defined elsewhere in the dictionary and on that basis I
believe the answer to your question is a qualified yes. The definition you have
shown will not work "as is".

1) When I tried to run a test using the syntax you have provided the CDD 
   doesn't seem to like the "copy from" construct.

2) I did run a couple of tests with the CDD and CDO Reader metadata drivers.
   Using the CDO file:




! NESTED_RECORD.CDO
! This CDO file is used to execise the metadata drivers using nested records.
!
set verify
set def nsds01:[daf.code.tom.nested.dict]

define field f1
  description  is "Normal field"
  datatype is TEXT 5.
define field f2
  description  is "Normal field"
  datatype is TEXT 5.
define field f3
  description  is "Normal field"
  datatype is TEXT 5.
define field f4
  description  is "Normal field"
  datatype is TEXT 5.

define record r1.
  f1.
  f2.
  end r1 record.

define record r2.
  f2.
  f3.
  end r2 record.

define record r3.
  f1.
  r2.
  f4.
  end r3 record.

define rms_database rms_db_1
  description is "This is the RMS database definition".
  record r3.
    file_definition
    organization SEQUENTIAL
    format FIXED.
  end rms_db_1 rms_database.

define database db_1
  description is "This is the database definition"
  using rms_db_1 on
  nsds01:[daf.code.tom.nested]nested_1.dat.  

----- end CDO file

A show table give the following result:

SQL> show table db_1
Information for table DB_1

Comment on table DB_1:
This is the database definition

Columns for table DB_1:
Column Name                     Data Type        Domain
-----------                     ---------        ------
F1                              CHAR(5)          F1
 Comment:       Normal field
 Query Header:  F1
F2                              CHAR(5)          F2
 Comment:       Normal field
 Query Header:  F2
F3                              CHAR(5)          F3
 Comment:       Normal field
 Query Header:  F3
F4                              CHAR(5)          F4
 Comment:       Normal field
 Query Header:  F4

Constraints referencing table DB_1:
No constraints found

Indexes on table DB_1:
No indexes found

Triggers on table DB_1:
No triggers found

SQL> exit ;

So I guess if the question is, "Can NSDS utilize nested records and structures?"
then the answer is yes. If the question is, "Can NSDS utilize nested records and
structures using the CDO syntax provided?" then the answer is no, because this
doesn't appear to be valid CDO syntax. Finally, if the question is, "Can NSDS
provide some specific field/record/structure naming convention indicated by the
provided CDO syntax?" then the answer is probably not.

					Tom

Tom,

Thank you for your testing and answer!
The question was "Can NSDS utilize nested records and structures?" 
None of those 'copy from' are structures or records, just normal fields/domains.

-Martti