I hope others agree that this is of general interest. I found Glenn's
help enlightening. Thanks, Glenn.

>----------
>From:  Glenn Cole[SMTP:[log in to unmask]]
>Sent:  Monday, August 25, 1997 9:35 PM
>To:    Stigers, Gregory - ANDOVER
>Subject:       Re: COBOL copylib
>
>> >Looks like a CM KSAM copylib is being converted to NM KSAM.
>
>> What is making this happen? Does COBEDIT make CM KSAMs, and FCopy reads
>> the CM but writes an NM KSAM?
>
>Yes, COBEDIT makes CM KSAMs.
>
>FCOPY is writing to NM KSAM because that is what it was told to do.
>The syntax for the TO= parm says that if a SINGLE filename is inside
>the parens
>
>    :FCOPY...;TO=( filename )
>
>then the destination file is an NM KSAM file.
>However, if *two* filenames are in parens
>
>    :FCOPY...;TO=( file1, file2 )
>
>then the destination is a CM KSAM file (one is the key and the other
>is the data; I don't recall which is which).
>
>> Is there any reason that I could not just
>> BUILD the silly thing as an NM in the true target group, then?
>
>This should be fine, as long as you get the parms right.
>(On the NM target from the fcopy, use :LISTFILE filename,UNIQUE
>to see the KSAM-specific info.)
>
>> This is news to me. Do you think that this might be of general interest
>> to the group?
>
>To me, ANY time an on-topic query does not receive several replies
>in short order, it's a good topic for the list. :)
>
>(I know SIGCOBOL maintains a list as well, but it's a pain to
>monitor more than one.)
>
>--Glenn
>  [log in to unmask]
>