Okay, Ive followed the examples in the documentation and cant get this to work right.
I have the following dictionaries:
PART_NO
1 = D
2 = 42
3 =
4 = PART_NO
5 = 15L
6 = M
QTY
1 = D
2 = 43
3 =
4 = QTY
5 = 4R
6 = M
When I import the universe table definition, I check the box about metadata supporting multivalue fields. I set the Position for PART_NO to 42, the type to M, and the Association to PART_NO. For QTY, I set position to 43, type to M and Assocation to PART_NO.
When I create a job and load the columns, then normalize on PART_NO, then click view data, it separates the PART_NO into separate rows, but not the QTY. What am I doing wrong?
Thanks,
Mike Roosa
Universe multivalues to SQL
Perhaps because your association name PART_NO is the same as your field name. Try a different association name.
----- Original Message -----
From: "Roosa, Mike"
To:
Sent: Friday, August 04, 2000 8:41 AM
Subject: Universe multivalues to SQL
> Okay, Ive followed the examples in the documentation and cant get
> this
to
> work right.
>
> I have the following dictionaries:
> PART_NO
> 1 = D
> 2 = 42
> 3 =
> 4 = PART_NO
> 5 = 15L
> 6 = M
>
> QTY
> 1 = D
> 2 = 43
> 3 =
> 4 = QTY
> 5 = 4R
> 6 = M
>
> When I import the universe table definition, I check the box about
metadata
> supporting multivalue fields. I set the Position for PART_NO to 42,
> the type to M, and the Association to PART_NO. For QTY, I set
> position to 43, type to M and Assocation to PART_NO.
>
> When I create a job and load the columns, then normalize on PART_NO,
> then click view data, it separates the PART_NO into separate rows, but
> not the QTY. What am I doing wrong?
>
> Thanks,
> Mike Roosa
>
----- Original Message -----
From: "Roosa, Mike"
To:
Sent: Friday, August 04, 2000 8:41 AM
Subject: Universe multivalues to SQL
> Okay, Ive followed the examples in the documentation and cant get
> this
to
> work right.
>
> I have the following dictionaries:
> PART_NO
> 1 = D
> 2 = 42
> 3 =
> 4 = PART_NO
> 5 = 15L
> 6 = M
>
> QTY
> 1 = D
> 2 = 43
> 3 =
> 4 = QTY
> 5 = 4R
> 6 = M
>
> When I import the universe table definition, I check the box about
metadata
> supporting multivalue fields. I set the Position for PART_NO to 42,
> the type to M, and the Association to PART_NO. For QTY, I set
> position to 43, type to M and Assocation to PART_NO.
>
> When I create a job and load the columns, then normalize on PART_NO,
> then click view data, it separates the PART_NO into separate rows, but
> not the QTY. What am I doing wrong?
>
> Thanks,
> Mike Roosa
>
Tried calling it PARTS, but when I normalize on PARTS, then click View Data, I get the following error:
Invalid association operation. Column or association name "PARTS" does not exist in dict file of FSR. Do I need to do something to the dict?
-----Original Message-----
From: Jerry P Banker [mailto:j_banker@affiliated.org]
Sent: Friday, August 04, 2000 10:12 AM
To: informix-datastage@oliver.com
Subject: Re: Universe multivalues to SQL
Perhaps because your association name PART_NO is the same as your field name. Try a different association name.
----- Original Message -----
From: "Roosa, Mike"
To:
Sent: Friday, August 04, 2000 8:41 AM
Subject: Universe multivalues to SQL
> Okay, Ive followed the examples in the documentation and cant get
> this
to
> work right.
>
> I have the following dictionaries:
> PART_NO
> 1 = D
> 2 = 42
> 3 =
> 4 = PART_NO
> 5 = 15L
> 6 = M
>
> QTY
> 1 = D
> 2 = 43
> 3 =
> 4 = QTY
> 5 = 4R
> 6 = M
>
> When I import the universe table definition, I check the box about
metadata
> supporting multivalue fields. I set the Position for PART_NO to 42,
> the type to M, and the Association to PART_NO. For QTY, I set
> position to 43, type to M and Assocation to PART_NO.
>
> When I create a job and load the columns, then normalize on PART_NO,
> then click view data, it separates the PART_NO into separate rows, but
> not the QTY. What am I doing wrong?
>
> Thanks,
> Mike Roosa
>
Invalid association operation. Column or association name "PARTS" does not exist in dict file of FSR. Do I need to do something to the dict?
-----Original Message-----
From: Jerry P Banker [mailto:j_banker@affiliated.org]
Sent: Friday, August 04, 2000 10:12 AM
To: informix-datastage@oliver.com
Subject: Re: Universe multivalues to SQL
Perhaps because your association name PART_NO is the same as your field name. Try a different association name.
----- Original Message -----
From: "Roosa, Mike"
To:
Sent: Friday, August 04, 2000 8:41 AM
Subject: Universe multivalues to SQL
> Okay, Ive followed the examples in the documentation and cant get
> this
to
> work right.
>
> I have the following dictionaries:
> PART_NO
> 1 = D
> 2 = 42
> 3 =
> 4 = PART_NO
> 5 = 15L
> 6 = M
>
> QTY
> 1 = D
> 2 = 43
> 3 =
> 4 = QTY
> 5 = 4R
> 6 = M
>
> When I import the universe table definition, I check the box about
metadata
> supporting multivalue fields. I set the Position for PART_NO to 42,
> the type to M, and the Association to PART_NO. For QTY, I set
> position to 43, type to M and Assocation to PART_NO.
>
> When I create a job and load the columns, then normalize on PART_NO,
> then click view data, it separates the PART_NO into separate rows, but
> not the QTY. What am I doing wrong?
>
> Thanks,
> Mike Roosa
>
Mike:
You need to have an association defined that groups the various multivalued fields together so that DataStage knows to normalize them as a set. Add an association name to field 7 of each of the dictionary records you want to group as a set (e.g., called PARTS), then create an association phrase grouping these, e.g.:
PARTS
001 PH
002 PART_NO QTY
The phrase name should exist in all of the dictionary records referenced by the phrase and vice versa.
-----Original Message-----
From: Roosa, Mike [mailto:Mike.Roosa@getronics.com]
Sent: Friday, August 04, 2000 7:24 AM
To: informix-datastage@oliver.com
Subject: RE: Universe multivalues to SQL
Tried calling it PARTS, but when I normalize on PARTS, then click View Data, I get the following error:
Invalid association operation. Column or association name "PARTS" does not exist in dict file of FSR. Do I need to do something to the dict?
-----Original Message-----
From: Jerry P Banker [mailto:j_banker@affiliated.org]
Sent: Friday, August 04, 2000 10:12 AM
To: informix-datastage@oliver.com
Subject: Re: Universe multivalues to SQL
Perhaps because your association name PART_NO is the same as your field name. Try a different association name.
----- Original Message -----
From: "Roosa, Mike"
To:
Sent: Friday, August 04, 2000 8:41 AM
Subject: Universe multivalues to SQL
> Okay, Ive followed the examples in the documentation and cant get
> this
to
> work right.
>
> I have the following dictionaries:
> PART_NO
> 1 = D
> 2 = 42
> 3 =
> 4 = PART_NO
> 5 = 15L
> 6 = M
>
> QTY
> 1 = D
> 2 = 43
> 3 =
> 4 = QTY
> 5 = 4R
> 6 = M
>
> When I import the universe table definition, I check the box about
metadata
> supporting multivalue fields. I set the Position for PART_NO to 42,
> the type to M, and the Association to PART_NO. For QTY, I set
> position to 43, type to M and Assocation to PART_NO.
>
> When I create a job and load the columns, then normalize on PART_NO,
> then click view data, it separates the PART_NO into separate rows, but
> not the QTY. What am I doing wrong?
>
> Thanks,
> Mike Roosa
>
You need to have an association defined that groups the various multivalued fields together so that DataStage knows to normalize them as a set. Add an association name to field 7 of each of the dictionary records you want to group as a set (e.g., called PARTS), then create an association phrase grouping these, e.g.:
PARTS
001 PH
002 PART_NO QTY
The phrase name should exist in all of the dictionary records referenced by the phrase and vice versa.
-----Original Message-----
From: Roosa, Mike [mailto:Mike.Roosa@getronics.com]
Sent: Friday, August 04, 2000 7:24 AM
To: informix-datastage@oliver.com
Subject: RE: Universe multivalues to SQL
Tried calling it PARTS, but when I normalize on PARTS, then click View Data, I get the following error:
Invalid association operation. Column or association name "PARTS" does not exist in dict file of FSR. Do I need to do something to the dict?
-----Original Message-----
From: Jerry P Banker [mailto:j_banker@affiliated.org]
Sent: Friday, August 04, 2000 10:12 AM
To: informix-datastage@oliver.com
Subject: Re: Universe multivalues to SQL
Perhaps because your association name PART_NO is the same as your field name. Try a different association name.
----- Original Message -----
From: "Roosa, Mike"
To:
Sent: Friday, August 04, 2000 8:41 AM
Subject: Universe multivalues to SQL
> Okay, Ive followed the examples in the documentation and cant get
> this
to
> work right.
>
> I have the following dictionaries:
> PART_NO
> 1 = D
> 2 = 42
> 3 =
> 4 = PART_NO
> 5 = 15L
> 6 = M
>
> QTY
> 1 = D
> 2 = 43
> 3 =
> 4 = QTY
> 5 = 4R
> 6 = M
>
> When I import the universe table definition, I check the box about
metadata
> supporting multivalue fields. I set the Position for PART_NO to 42,
> the type to M, and the Association to PART_NO. For QTY, I set
> position to 43, type to M and Assocation to PART_NO.
>
> When I create a job and load the columns, then normalize on PART_NO,
> then click view data, it separates the PART_NO into separate rows, but
> not the QTY. What am I doing wrong?
>
> Thanks,
> Mike Roosa
>