quiz parallel linkage

[Pickering, John (NORBORD)]

I had a similar issue with parallel linkage. It was solved with a workaround for bug 401877 by Mary Pilgrim at Cognos. I'm running on an HP3000 but maybe the underlying code is the same?

Try taking the explicit linkage out of the second side of the parallel linkage. As in:
ACC ACCOUNTS LINK ACCT_NUM &
TO CLIENT_NUM OF ACT_CLIENT OPT &
AND TO EXP_CLIENT OPT

This was Mary's suggestion and it solved my problem.

Regards,
JWP

From: powerh-l-bounces+john.pickering=norbord.com at lists.sowder.com [mailto:powerh-l-bounces+john.pickering=norbord.com at lists.sowder.com] On Behalf Of Lorry Litman
Sent: Thursday, March 05, 2015 9:56 AM
To: PowerHouse listserver
Subject: quiz parallel linkage


Hi,

I'm not getting the results I'm expecting from this parallel linkage.
VMS 7.3-2  PH 7.10G1
This involves 3 RMS indexed files
Accounts, Act_client, Exp_client
Act_client and Exp_client are identical files/record structure.
Acct_num and client_num are both num * 9.
Acct_num should be found in one of act_client or exp_client. Yes, it's possible in rare situations it's not found in either, but that's a different issue.

ACC ACCOUNTS LINK ACCT_NUM &
TO CLIENT_NUM OF ACT_CLIENT OPT &
AND TO CLIENT_NUM OF EXP_CLIENT OPT

If the acct_num exists in act_client info is found/reported
If acct_num exists in exp_client info is not found/reported

If I reverse the access statement and have exp_client as the first link and then act_client second I get the reverse result of the above.

If I link to each file individually it will find it.

I've tried optional on the first linkage only, the second linkage only or both and no different result.

What am I not understanding of how parallel linkage should work?


Thanx
Lorry Litman
Application Management
llitman at manitoba-ehealth.ca<mailto:llitman at manitoba-ehealth.ca>
204-926-9076

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sowder.com/pipermail/powerh-l/attachments/20150305/0a87f7bd/attachment.htm>