[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference ilbbak::ibi_focus

Title:FOCUS, from INFORMATION BUILDERS
Moderator:ZAYIUS::BROUILLETTE
Created:Thu Feb 19 1987
Last Modified:Mon May 05 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:615
Total number of notes:1779

390.0. "ERROR FOC(1043)" by WMOIS::J_MARENGO () Tue Jan 22 1991 08:00

Hi,

Have you ever seen the following error, and what does it mean:

(FOC1043) INVALID COMBINATION OF 'TO' FILED FORMATS: ASUBMSN/CAL_DT

ASUBMSN and CAL_DT are both date fields in the yymmdd.  ASUBMSN is from a .RDB
file, and CAL_DT is from a HOLD file.  This error occurs when I am trying to
join the two files.  I can join ASUBMSN to CAL_DT if I use the original file 
that CAL_DT comes from, but I can't if I use a HOLD file.  Any help would be
appreciated.

Regards,
	Jim Marengo
T.RTitleUserPersonal
Name
DateLines
390.1CUCKOO::OTTENUmbrellas, Minds, and systemsTue Jan 22 1991 11:368
I Presume that they're stored in different formats..
The RDB Dates in RDB format, and the FOCUS Date in an
Internal FOCUS Format.

What to do about it, I don't know.


David
390.2A little more info...WMOIS::J_MARENGOTue Jan 22 1991 15:158
    The format of ASUBMSN (from the RDB file) is I6YMD.  CAL_DT is I6. 
    When I define a new field from CAL_DT that has a format of I6YMD, it
    makes no difference.  Also, CAL_DT is an original field from a file
    called FISCAL.RDB which I include in my hold file.  I *can* join
    ASUBMSN to CAL_DT in FISCAL.RDB but not the hold file.
    
    Thanks,
    	   JAM
390.3Can't JOIN on alternative keyMASALA::SACAMPBELLToo Fast to Live, Too Young to Die !!Thu Oct 10 1991 10:01103
  This is not any reference to the previous reply but I am encountering the same
error.

  I am trying to join two files together. One file is a hold file the other is
an external file.

  The external file has an alternative key which I am trying to join to but am 
receiving a (FOC1043) Invalid Combination of 'TO' Field Formats. If I try to 
JOIN using the primary key then there is no JOIN error but when I try to 
RTO_YIELD, its value is zero. Don't Understand.

This is getting kinda urgent so any help would be greatfully appreciated.


    Thanx,

        Stuart.


Here is a listing of the FEX I am trying to use :

FILEDEF PSUMFILE DISK COMETS$PRODUCTION:SQFAB1SUM.CMT
FILEDEF RTOFILE DISK COMETS$PRODUCTION:RTOFILE.DAT
DEFINE FILE PSUMFILE
  DAILY_FPY/I4 = P_1OUTS - P_1REWOUTS;
  WTD_FPY/I5 = P_2OUTS - P_2REWOUTS;
  FACILITY/A6 = 'SQFAB1';
  ALPHA_OPER/A4 = EDIT(P_OPER);
  PSUMKEY/A20 = FACILITY | P_ROUTE | ALPHA_OPER;
END
TABLE FILE PSUMFILE
  SUM DAILY_FPY WTD_FPY
  BY P_ROUTE
  BY P_OPER
  IF P_ROUTE EQ 'CMOS3' OR 'B/END_F' OR 'B/END_NF' OR 'BACK GRIND' OR
         'ALLOY' OR 'FUSE'
  IF P_OWNER EQ 'PROD' OR 'PROCESS' OR 'SEGPROTO'
  ON TABLE HOLD
END

JOIN PSUMKEY IN HOLD TO RTO_ALT_KEY IN RTOFILE

TABLE FILE HOLD
SUM WTD_FPY
IF RTO_YIELD LT 1
END


Here is a list of the master file def :

FILENAME=RTOFILE,SUFFIX=ISAM
$
$  This file is the rpx route-oper file which
$  is produced by RPX752.EXE in COMETS.  It lists the
$  route-operations in each facility.
$
$  The COBOL layout for this file is contained in RTOFILECF.LIB
$
$  The standard prefix for fields in this file is "RTO_"
$
$ *********************************************************************
$  MAY 16, 1989. AB.
$  Changes for V5.1 : addition of 2 fields
$  RTO-PUPT-HOURS               PIC 9(6)V9(3)
$  RTO-IN-NS-BLOCK              PIC X.
$
$  AUG 29, 1991. Stuart Campbell
$  Changes for Focus V6.1
$  Modified ALIAS name of RTO_ALT_KEY to KEY1 (Used to be KEY)
$ *********************************************************************
$
SEGNAME=RTOSEG
 GROUP=RTO_PRIM_KEY, ALIAS=KEY ,FORMAT=A20      ,ACTUAL=A20   ,FIELDTYPE=I ,$
  FIELDNAME=RTO_FACILITY, ,FORMAT=A6       ,ACTUAL=A6    ,$
  FIELDNAME=RTO_ROUTE   , ,FORMAT=A10      ,ACTUAL=A10   ,$
  FIELDNAME=RTO_SEQ_NUM , ,FORMAT=A4       ,ACTUAL=A4    ,$
 GROUP=RTO_ALT_KEY,  ALIAS=KEY1 ,FORMAT=A20      ,ACTUAL=A20   ,FIELDTYPE=I ,$
  FIELDNAME=RTO_ALT_FAC , ,FORMAT=A6       ,ACTUAL=A6    ,$
  FIELDNAME=RTO_ALT_RTE , ,FORMAT=A10      ,ACTUAL=A10   ,$
  FIELDNAME=RTO_ALT_OPER, ,FORMAT=I4       ,ACTUAL=Z4    ,$
  FIELDNAME=RTO-PUPT-HRS, ,FORMAT=P10.3    ,ACTUAL=Z9.3  ,$
  FIELDNAME=RTO-IN-NSBLK, ,FORMAT=A1       ,ACTUAL=A1    ,$
  FIELDNAME=RTO_CUM_YLD , ,FORMAT=P9.4     ,ACTUAL=Z8.4  ,$
  FIELDNAME=RTO_PLAN_CYD, ,FORMAT=P9.4     ,ACTUAL=Z8.4  ,$
  FIELDNAME=RTO_CUM_CT  , ,FORMAT=P8.3     ,ACTUAL=Z7.3  ,$
  FIELDNAME=RTO_YIELD   , ,FORMAT=P9.4     ,ACTUAL=Z8.4  ,$
  FIELDNAME=RTO_PLAN_YLD, ,FORMAT=P9.4     ,ACTUAL=Z8.4  ,$
  FIELDNAME=RTO_CYC_TIME, ,FORMAT=P8.3     ,ACTUAL=Z7.3  ,$
  FIELDNAME=RTO_FAST_CT , ,FORMAT=P7.3     ,ACTUAL=Z6.3  ,$
  FIELDNAME=RTO_RWK_FACT, ,FORMAT=P5.3     ,ACTUAL=Z4.3  ,$
  FIELDNAME=RTO_OGROUP_1, ,FORMAT=A12      ,ACTUAL=A12   ,$
  FIELDNAME=RTO_OGROUP_2, ,FORMAT=A12      ,ACTUAL=A12   ,$
  FIELDNAME=RTO_OGROUP_3, ,FORMAT=A12      ,ACTUAL=A12   ,$
  FIELDNAME=RTO_SHT_DESC, ,FORMAT=A10      ,ACTUAL=A10   ,$
  FIELDNAME=RTO_UNIT_1  , ,FORMAT=A6       ,ACTUAL=A6    ,$
  FIELDNAME=RTO_UNIT_2  , ,FORMAT=A6       ,ACTUAL=A6    ,$
  FIELDNAME=RTO_UNIT_3  , ,FORMAT=A6       ,ACTUAL=A6    ,$
  FIELDNAME=RTO_MILESTNE, ,FORMAT=A1       ,ACTUAL=A1    ,$
  FIELDNAME=RTO_ALT_RTEF, ,FORMAT=A1       ,ACTUAL=A1    ,$
  FIELDNAME=RTO_ALT_RTEG, ,FORMAT=A12      ,ACTUAL=A12   ,$
  FIELDNAME=RTO_SCRIPTID, ,FORMAT=A12      ,ACTUAL=A12   ,$
  FIELDNAME=RTO_QUEUE_CT, ,FORMAT=P8.3     ,ACTUAL=Z7.3  ,$
390.4Segmented KeyEVTDD1::CARRIEREJean-Claude CarriereThu Oct 10 1991 13:0019
Hello Stuart,

	This look like a problem joining to secondary segmented key.

	One thing you can try for the purpose of this specific report
	is to use a different master file where the key is define as
	a single field with A20 Actual format

 GROUP=RTO_ALT_KEY,  ALIAS=KEY1 ,FORMAT=A20      ,ACTUAL=A20   ,FIELDTYPE=I ,$
  FIELDNAME=RTO_ALT_KEY , ,FORMAT=A20      ,ACTUAL=A20   ,$

	This should probably bypass FOCUS checking and since you do
	not reference any of the field in the key for target file you
	might be able to produce this report.

	Not nice having a to maintain two files but might be the fastest
	work-around.

Jean-Claude