I have taken a synonym file (.mas) with its .acx cohort and changed the name of a segment containing 3 fields.

I changed 1 of the field names, but not its format, changed one of the original fields and its format (from A36V to P9).

I did this by copying original mas and acx code from dev. and pasting into notepad.

Beforehand, I made copies of each dev. file with names like *_old.mas and *_old.acx.

I am new to this synonym and acx file stuff, and I can't find much documentation about GUI_PARAMS..

After I pasted my new .mas and .acx files into my dev. environment I ran a simple TABLE request against the synonym.

Error:

(FOC1141) NO DEFAULT KEYWORD FOR VALUE 804. NEW_CASH_FLOWS LN 21
--------------------vvv
GUI_PARAMS=0,100,804,148,852,278,160', KEYS=1, $

FOC1141) NO DEFAULT KEYWORD FOR VALUE 154. NEW_CASH_FLOWS LN 24
--------------------vvv
GUI_PARAMS=0,306,154,354,202,278,160', KEYS=1, $
(FOC1354) ACCESS FILE RECORD ABSENT, WRONG OR INCOMPLETE FOR SEGMENT :
ACCESS_GROUP

Can anyone provide any insight into what might be going on here?

Thanks,

This message has been edited. Last edited by: Tomsweb,

Tomsweb,

GUI_PARAMS is used for drawing the dialog boxes. Do you get an error if you remove it?

Fernando

The GUI_PARAMS I am talking about is in the access file which accompanies a synonym master file.

For example:

Access file layout:

SEGNAME=CASH_FLOW, TABLENAME=TRS_SAM.CASH_FLOW, CONNECTION=SAM,
GUI_PARAMS='0,100,24,148,72,278,160', KEYS=2, $
SEGNAME=CASH_FLOW_VERSION, TABLENAME=TRS_SAM.CASH_FLOW_VERSION,
CONNECTION=SAM, KEYFLD=CASH_FLOW_ID, IXFLD=FK_CASH_FLOW_ID,
GUI_PARAMS='0,100,154,148,202,278,160', KEYS=2, $

Synonym file layout:

FILENAME=cash_flows, SUFFIX=SQLORA , $
SEGMENT=CASH_FLOW, SEGTYPE=S0, $
FIELDNAME=FK_ACCESS_GROUP_ID, ALIAS=FK_ACCESS_GROUP_ID, USAGE=P11, ACTUAL=P6, $
FIELDNAME=CASH_FLOW_ID, ALIAS=CASH_FLOW_ID, USAGE=P11, ACTUAL=P6, $
FIELDNAME=RDCF_NAME, ALIAS=NAME, USAGE=A30, ACTUAL=A30, $
FIELDNAME=FK_SYSTEM_TYPE_ID, ALIAS=FK_SYSTEM_TYPE_ID, USAGE=P11, ACTUAL=P6, $
FIELDNAME=UPDATE_SEQ_NR, ALIAS=UPDATE_SEQ_NR, USAGE=P16, ACTUAL=P8, $
SEGMENT=CASH_FLOW_VERSION, SEGTYPE=S0, PARENT=CASH_FLOW, CRJOINTYPE=INNER, $
FIELDNAME=FK_CASH_FLOW_ID, ALIAS=FK_CASH_FLOW_ID, USAGE=P11, ACTUAL=P6, $
FIELDNAME=VERSION_NR, ALIAS=VERSION_NR, USAGE=P6, ACTUAL=P3, $
FIELDNAME=CASH_FLOW_VERSION_ID, ALIAS=CASH_FLOW_VERSION_ID, USAGE=P11, ACTUAL=P6, $
FIELDNAME=DESCRIPTION, ALIAS=DESCRIPTION, USAGE=A255V, ACTUAL=A255V,
MISSING=ON, $
FIELDNAME=EFFECTIVE_DT, ALIAS=EFFECTIVE_DT, USAGE=HYYMDS, ACTUAL=HYYMDS, $
FIELDNAME=END_DT, ALIAS=END_DT, USAGE=HYYMDS, ACTUAL=HYYMDS,
MISSING=ON, $

and so on...

I believe if you change a synonym field name for a relational table, the ALIAS must still contain the real name of the DB column - or maybe I have it backwards: you can change the ALIAS name but the FIELDNAME must reflect the real column name. Secondly, you can't change A36V to P9 unless the Oracle column is in fact a packed decimal.

Dan,

Just to confirm, it is the ALIAS that must match the actual column name.

T

Thanks Tony and Dan. Sometimes this forum provides better insight than the documentation,
because people are speaking from experience!

Amen.

FYI - back when IBI started accessing DB2, they used the ALIAS for the real field name and if the name was too long, it could be put in the access file. It then didn't disrupt the column headings and other things based on fieldname.

When I have to do a MFD(master file) by hand, I avoid using ALIAS, unless I have to.