An SDTM variable exists as a value of QNAM in a suppqual dataset

Having an SDTM variable as a value of QNAM does not appear to trigger any violation.  We had a SUPPVS with a QNAM value of VSREASND (of course VSREASND should have been a variable in VS and not placed in SUPPVS) but OpenCDISC didn't detect this problem.  Also, we had a SUPPEG with a QMAM value of EGEVAL, and the variable EGEVAL was already a variable in EG, but OpenCDISC did not detect this problem either.  When we used WebSDM we knew such problems existed because WebSDM would have a load failure if such situations existed.  It would save sponsors manual checking on the SUPP QNAM values if OpenCDISC could check for these problems.