Conference iosg::all-in-1_v30

    Any key can be segmented. What is your problem? In the FDL you
    specify the segments. In the call to the file via a DSR you must still
    use a symbol that is the concantenated value of all the segments, just
    like for segmented primaries.
    
    Rick

    Rick,
    
    Thanks for the reply.  I was confident that I was missing something,
    and being sometimes slow, I still am.  On page 8-4 of the 2.4 Guide it
    says, "If the segmented key is also an alternate key, then the key of
    reference is required.  The key of reference must be a concatenation of
    all segments of the key."  It then goes on discussing how to build this
    KOR and gives an example.  But unless I'm missing something, in the
    example it shows how to build the key not the KOR.  (I think it says,
    "key of reference," when it really means, "key".
    
    So what does the KOR look like?  Is it the name of the segmented key as
    specified by the FDL, or is it a concatenation of the field names which
    make up the segmented key, or something else?
    
    Thanks for the help,
    
    Joe

Hi,

It looks like they've (unfortunately IMVHO) trimmed down the amount of detail
on this subject.  In my V2.3 books, chapter 4 of the AP Guide implies that
the KOR should be the name of the segmented key as defined in the FDL file.
Note that upper case should be used for the key name in the FDL, as ALL-IN-1
converts the KOR to upper case.

However, in the V3.0 books I can't find the information any more.  Maybe it's
just moved somewhere even more obscure....

Scott

>>>    So what does the KOR look like?  Is it the name of the segmented key as
>>>    specified by the FDL, or is it a concatenation of the field names which
>>>    make up the segmented key, or something else?
    
	Your first assumption is correct, as KOR you have to use the
	RMS name of the key of interest:

	example:	KEY1
				CHANGES			yes
				DATA_FILL		.
				.			.
		--->		NAME			"KEN_OLSEN"
				.			.
				SEG0_LENGTH   		.
				.			.


	A DSR using this KEY1 reads:

		GET #first_key1_value = dsab:ken_olsen.%next[""]


	M_ichael_G