This I-descriptor or EVAL should help you:
LIST VOC _
WITH EVAL "CONVERT( @AM:@VM:@SM:@TM, 'avst', @id )" # @ID _
ID.SUP EVAL "CONVERT( @AM:@VM:@SM:@TM, 'avst', @id )"
(To be rigorous, char(247 thru 250) are also treated as system
delimiters. You might test for them, too.)
Is ALLOWMARKS set to 1 or 0 in uvconfig?
My guess is "1", or at least that it used to be "1".
This means system delimiters are allowed to be embedded in IDs.
So if you have an id with a field-mark (aka attribute-mark, char(254),
@AM, @FM) in it -- let's call it ABC^254DEF -- then if that is part of
an active select list, it will be processed as ABC then DEF. That is,
2 ids that are probably not in the file at all.
Moral of the story: ALLOWMARKS 0 is better than 1.
Did you look at what NSELECT's 2 supposed ids are?
Try pinning them together with system delimIters and reading with basic
read statement.
Or LIST.ITEM VOC should show them to you., too.
I am not sure what happens if uvconfig is set to 1 after such records
are already in your files.
That param was introduced a few years ago, after many systems were
already up & running.
Another source is data ported from other MV platforms.
Has anyone seen this before? When I select everything from VOC and
immediately do a NSELECT on VOC, it returns 2 records.
:SELECT VOC
14315 records selected to list 0.
>>NSELECT VOC
2 record(s) selected.
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
