Issue with field length while modifying

Infosphere's Quality Product

Moderators: chulett, rschirm

Post Reply
csc.datastage
Premium Member
Premium Member
Posts: 23
Joined: Wed Sep 10, 2008 4:46 pm
Location: USA

Issue with field length while modifying

Post by csc.datastage »

Hello,

I am new to QualityStage (QS). Right now using for Address standardization, Area and Name as well. The existing QS dictionary files are working fine without having any issues. Now, the requirement is to use extend the existing field lengths. Currently I am using MNS stage for address and name standardization. Trying to modify the NAME field length and ADDRESS field length from DIC files but the result file is not giving the expected result. Example the address (MNPREP) standardization purpose, using AD1.DIC as input and AD2.DIC as output. For AREA standardization, AD2.DIC as input and AD3.DIC as output. For MNNAME, standardization, AD3.DIC as input and AD4.DIC as output file. The final result file AD4.DIC data is processing into DataStage.

Able to modify the AD1.DIC file so the result AD2.DIC file is giving as expected. From AD2.DIC onwards the resultant data is not correct as expected where I am using built-in AREA standardization. What would like to know is,
1) Are they any limitations while modifying the field length in QS?
2) Possible to modify the AREA related .DIC and .STN files for MNNAME and MNPREP?
3) As of I modified only .DIC/.DCT/.STN files only. Is there any other format files have to modify of these length changes?

AD1.DIC (Current)
-------------------
;;QualityStage v7.0
RECORD 832
FILE ${DATAA}
CODEPAGE DEFAULT
FILEFORMAT FIXEDTERM
VAR LOADDAT 1 20 S A
.
.
.
VAR NAME 57 80 S A
VAR ADDRES1 137 80 S A
.
.

AD1.DIC (New)
--------------------
;;QualityStage v7.0
RECORD 1253
FILE ${DATAA}
CODEPAGE DEFAULT
FILEFORMAT FIXEDTERM
VAR LOADDAT 1 20 S A
.
.
.
VAR NAME 78 280 S A
VAR ADDRES1 358 80 S A
.
.
.

AD2.DIC (Current)
---------------------
;;QualityStage v7.0
RECORD 485
FILE ${DATAA}
CODEPAGE DEFAULT
FILEFORMAT FIXEDTERM
VAR NAMNPRE 1 100 S A
.
.
.
VAR LOADDAT 403 20 S A
.
.
.

AD2.DIC (New)
-----------------
;;QualityStage v7.0
RECORD 906
FILE ${DATAA}
CODEPAGE DEFAULT
FILEFORMAT FIXEDTERM
VAR NAMNPRE 1 300 S A
.
.
.
VAR LOADDAT 803 20 S A
.
.
.

AD3.DIC (Current)
---------------------
;;QualityStage v7.0
RECORD 1091
FILE ${DATAA}
CODEPAGE DEFAULT
FILEFORMAT FIXEDTERM
.
.
.
VAR NAMNPRE 607 100 S A
.
.
.
VAR LOADDAT 1009 20 S A
.
.
.

AD3.DIC (New)
----------------
;;QualityStage v7.0
RECORD 1512
FILE ${DATAA}
CODEPAGE DEFAULT
FILEFORMAT FIXEDTERM
.
.
.
VAR NAMNPRE 607 300 S A
.
.
.
VAR LOADDAT 1409 20 S A

AD4.DIC (Current)
--------------------
;;QualityStage v7.0
RECORD 637
FILE ${DATAA}
CODEPAGE DEFAULT
FILEFORMAT FIXEDTERM
.
.
.
VAR LNMNNAM 73 50 S A
.
.
.
VAR ADMNPRE 455 100 S A
VAR LOADDAT 555 20 S A
.
.
.

AD4.DIC (New)
----------------
;;QualityStage v7.0
RECORD 903
FILE ${DATAA}
CODEPAGE DEFAULT
FILEFORMAT FIXEDTERM
.
.
.
VAR LNMNNAM 73 95 S A
.
.
.
VAR ADMNPRE 500 300 S A
VAR LOADDAT 800 20 S A
.
.
.
Focus on ABC: Audit , Balance and Control..
rjdickson
Participant
Posts: 378
Joined: Mon Jun 16, 2003 5:28 am
Location: Chicago, USA
Contact:

Post by rjdickson »

I would strongly suggest you open a PMR with IBM to get their help with all the artificats that need to be changed.
Regards,
Robert
Post Reply