After some work, I could find a few solutions. One of these, I’d call Serialisation.
So, we start of two Parallel path –let’s say A and B – under a Common Parent.
Help to MultiPath we can extract a file (Mono Segment) that contains
1) Fields of the Parent
2) Fields of the A Path (Including Data that’ll prove the ‘Missing’ of the nth A son)
3) Fields of the B Path (Including Data that’ll prove the ‘Missing’ of the nth B son)
The idea is to Build a two characters Field let’s say ZON_CHAPTER
1) The 1st character will be ‘A’ if A Data are present and, otherwise, will be ‘ ‘.
2) The 2nd character will be ‘B’ if B Data are present and, otherwise, will be ‘ ‘.
Then to save the created master and add a serialization level that re defines ZON_CHAPTER
SEGNAME=PSEUCHAP,Parent=MONOSEG,Position=ZON_CHAPTER,OCCURS=2,$
FIELD=CHAPTER,ALIAS=CHAPITRE, A001, A001,$
FIELD=INDCHAP,ALIAS=ORDER , I004, I004 ,$
With this (classical) Trick, you allow Focus to ‘access’ twice the same Line (We call it Multiplicative effect)
We Can Reject the meaningless lines with IF CHAPTER EQ ‘A’ OR ‘B’
We need to be clever enough as to Define , at the Chapter level, fields with a Format Common to Path A or B and Which Content is A or B Oriented :
Ex : Common_Lib/A32 = IF CHAPTER EQ ‘A’ THEN LIB_IN_THE_A_PATH
ELSE IF CHAPTER EQ ‘B’ THEN LIB_IN_THE_B_PATH
ELSE ‘STUPID, FILTER ON A OR B, PLEASE’ ;
Of Course, as ever with Focus, there are many other Ways to serialize parallel information.
But, Obviously, I'm no longer (if I ever was) in touch with Focus Community, sniff...
If on my side, I'm such a bad communicant, aren't you too much 'Focus for Nulls' oriented ?
I exclude some great signatures who are witty, tricky and know Focus far better than I.
I really laugh when they come to be brilliant
Cordially, Focusely, and a bit sadly
Focus Mainframe 7.6.11
Dev Studio 7.6.11 and !!!
PC Focus, Focus for OS/2, FFW Six, MSO