Focal Point
Data comes in garbled due to master file config changes

This topic can be found at:
https://forums.informationbuilders.com/eve/forums/a/tpc/f/7971057331/m/9541096302

December 27, 2006, 07:25 PM
Viral
Data comes in garbled due to master file config changes
Hello,

Uses WebFocus Server 7.1 and OS -WIN2003.
I have two master file exactly same in two projects and sharing the same focus file which is residing at one of the project. Data was coming fine in the both the projects .
Now I have reload the focus file, master file also got updated in that project where focus file.
Data comes fine in the project where I have the focus and master file, but the other project where master file still old config - data comes garbled.
Only difference I found between master files
Master file where data comes fine - which got updated. for example
FIELD=LINECODE, FORMAT=A2,
Other project where master file still has old config
FIELD=LINECODE, USAGE=A2,
I have checked everything no field attributes got changed, only changes instead of USAGE now it says FORMAT.
Tell me if you have face this kind of issues before and how to deal with it.
Thanks in advance for your inputs.


WF 7.6.2/ OS WIN2003.
DM 7.6.2
January 05, 2007, 01:51 PM
Viral
Hi Kerry,

As suggested here is the two master files.

1)
FILE=rv_FabLotMoves_etl, SUFFIX=FOC, DATASET='D:\ibi-qa\ibi\apps_srv\rv_bus_objects\rv_FabLotMoves_etl.foc'
SEGNAME=SEG01, SEGTYPE=S1, $
FIELD=FOCLIST, ALIAS=E01, FORMAT=I9, $
FIELD=CUTOFFDATE, ALIAS=E02, FORMAT=I8YYMD, $
FIELD=LINECODE, ALIAS=E03, FORMAT=A2, FIELDTYPE=I, $
FIELD=LOTNUMBER, ALIAS=E04, FORMAT=A12, FIELDTYPE=I, $
FIELD=MAJORSTEPCODE, ALIAS=E04, FORMAT=A3, $
FIELD=MINORSTEPCODE, ALIAS=E06, FORMAT=A3, $


2) FILE=fablotmoves, SUFFIX=FOC, REMARK='Fab Lot Moves (Finishes) for the past 35 days', DATASET='D:\ibi-qa\ibi\apps_srv\RV_Bus_Objects\rv_fablotmoves_etl.foc'
SEGNAME=SEG01, SEGTYPE=S1, $
FIELD=FOCLIST, ALIAS=FOCLIST, USAGE=I5, DESCRIPTION='Focus Unique Record Identifier', ACCESS_PROPERTY=(INTERNAL), $
FIELD=CUTOFFDATE, ALIAS=E02, USAGE=I8YYMD, ACCESS_PROPERTY=(INTERNAL), $
FIELD=LINECODE, ALIAS='Line Code', USAGE=A2, FIELDTYPE=I, DESCRIPTION='Line Code', $
FIELD=LOTNUMBER, ALIAS='Lot Number', USAGE=A12, FIELDTYPE=I, DESCRIPTION='Lot Number', $
FIELD=MAJORSTEPCODE, ALIAS='Major Step', USAGE=A3, DESCRIPTION='Major Step', $
FIELD=MINORSTEPCODE, ALIAS='Minor Step', USAGE=A3, DESCRIPTION='Minor Step', $

Let me know if it helps, otherwise I will try to create as CAR files and upload it.


WF 7.6.2/ OS WIN2003.
DM 7.6.2
January 05, 2007, 02:15 PM
susannah
dude, look at your very first field
one is I5, one is I9
Use the command CHECK
CHECK FILE mastername
against each of the masters.




In Focus since 1979///7706m/5 ;wintel 2008/64;OAM security; Oracle db, ///MRE/BID
January 05, 2007, 02:22 PM
Viral
quote:
CHECK FILE mastername

Thanks susannah ! for quick reply.

Let make the change to use I9 for both master files and let you know results.
Quick questions if the total length comes different in master files using CHECK command then data comes garbled?

Once agains thanks !


WF 7.6.2/ OS WIN2003.
DM 7.6.2
January 06, 2007, 02:53 PM
susannah
yes, you've got it, that's exactly right.
one master is expecting 9 postions, the other master is expecting 5. So one of the 'maps' is whacky...the master which actually creates the file would be the real format




In Focus since 1979///7706m/5 ;wintel 2008/64;OAM security; Oracle db, ///MRE/BID