Date:         Fri, 6 Oct 1995 05:08:27 -0700
Reply-To:     The NOMAD2 Discussion List
Sender:       The NOMAD2 Discussion List
From:         Michael Dow
Subject:      Re: Duplicated records in master with externalfile
In-Reply-To:  "Mail dated 95/10/06 12:04:04 UT from (NOMAD2-L) The NOMAD2
              Discussion List"

Or... Use fixed record length?  Works like a charm for me.. :-)
Actually, using RECFM F will 'force' the logical addition of
the extra character(s) in the CMS file system spoken about below.

>___Original Letter _______________________________________
>Date: 05 Oct 1995 10:07:27 -0700
>Sender:   The NOMAD2 Discussion List           (NOMAD2-L)
>From:     Don DeCosta                          (DOND)
>To:       Multiple recipients of list NOMAD2-L (NOMAD2-L)
>Reply-To: The NOMAD2 Discussion List           (NOMAD2-L)
>Subject: Re: Duplicated records in master with externalfile
>
>> - when listing or dbediting the master, each record followed by an empty line
> in
>> the external file is duplicated in the Nomad2 master.
>
>Actually what's happening is when reading an external file with
>varying record lengths, NOMAD will fill a short record with the data
>from the previous record. For example if you have two records:
>
>FIRST LONG RECORD
>the short record
>
>NOMAD will list the second record as "the short recordCORD"
>
>Either insure that your external report file has all records the same
>length (like force a char in column (reportwidth+1) and declare an A1
>DUMMY item at the end)
>
>Or,  change your external schema to
>
>ITEM REPORTCHARS(0) AS A1;
>DEFINE REPORTLINE AS A255 = STRING(REPORTCHARS);
>
>This will only work if you are treating each record as a single item,
>of course doing the above in an interim create is a good way of
>getting a char in column (reportwidth+1) and then use the first
>solution above.
>
>Good Luck!
>Don DeCosta
>DonD@crl.com
>___End of Original Letter_________________________________
back to index