Conference orarep::nomahs::repository

1058.0. "About the variants definition by the Record definition . " by ORAREP::EWBV51::NAKAMURA () Wed Feb 26 1997 07:32

Hello,

There is a question about the CDD VARIANTS phrase. 

My customer is doing the following definition to CDD by the DMU format. 
And, it is used from DTR. 

[ SYSTEM INFORMATION. ]

        OpenVMS VAX       V6.2          MI-CLUSTER
        OpenVMS AXP       V6.2-1H3

        Oracle Rdb      V6.1A
        Oracle CDD/R    V6.1-ECO#2
        Datatrieve/J    V6.1

[ DDL PROCEDURE ]

DEFINE RECORD CDD$TOP.HA220ADAT_REC
    DESCRIPTION IS
        /* This record contains the field to be able to define
                        in BASIC program. */.
    HA220ADAT_REC STRUCTURE.
    VARIANTS.
     VARIANT.
      SB7       STRUCTURE.
        HDATA_ID                        DATATYPE IS TEXT SIZE IS   1 CHARACTERS.
        HKOSIN_ID                       DATATYPE IS TEXT SIZE IS   1 CHARACTERS.
                                        :
        HDUM                            DATATYPE IS TEXT SIZE IS 163 CHARACTERS.
      END SB7 STRUCTURE.
     END VARIANT.
     VARIANT.
      HENKO     STRUCTURE.
        HDATA_ID                        DATATYPE IS TEXT SIZE IS   1 CHARACTERS.
                                        :
        HDUM                            DATATYPE IS TEXT SIZE IS 184 CHARACTERS.
      END HENKO STRUCTURE.
     END VARIANT.
     VARIANT.
      SB8_1     STRUCTURE.
        HDATA_ID                        DATATYPE IS TEXT SIZE IS   1 CHARACTERS.
                                        :
                                        :
        HDUM                            DATATYPE IS TEXT SIZE IS  12 CHARACTERS.
      END KOGO STRUCTURE.
     END VARIANT.
     VARIANT.
      HA220ADAT_REC_ALL STRUCTURE.
        HA220ADAT_ALL                   DATATYPE IS TEXT SIZE IS 400 CHARACTERS.
      END STRUCTURE.
     END VARIANT.
    END VARIANTS.
    END HA220ADAT_REC STRUCTURE.
END HA220ADAT_REC.

    
The customer has the case where a correct result is not obtained when
 the processing of DTR is executed from the AXP system in the Mixed 
Architecture Cluster environment. 

I wonder whether to obtain the result as which both are the same though
 the method of specifying the VARIANT definition is different in DMU and CDO. 

Difference between DMU and CDO 

In CDO, the VARIANT definition is judged from the column value which is
        clearly. 

	EX)
	CDO> DEFINE RECORD EMPLOYEE_REC.
	cont>   FULL_NAME.
	cont>   BADGE_NO.
			:
	cont> VARIANTS.
	cont>  VARIANT EXPRESSION IS JOB_CODE IN EMPLOYEE_REC="D".
	cont>   DISMISSED.
	cont>  END VARIANT.
	cont>  VARIANT EXPRESSION IS JOB_CODE IN EMPLOYEE_REC="R".
	cont>   RETIRED.
	cont>  END VARIANT.
	cont> END VARIANTS.
	cont> END EMPLOYEE_REC RECORD.

In DMU, the VARIANT definition is judged from the entire all colume of record. 

My question 

Is it a trouble that the processing result is different by VAX and AXP which 
shares the CDD dictionary this time?
Originally, should I correctly judge the input record data only from the VARIANT
 definition defined with DMU? 
 or 
When I use the VARIANT definition, should I change to the VARIANT definition 
which uses EXPRESSION with CDO? 

best regards