CORBA::Exception [UNKNOWN] when attempting to SctApiServer::modifyABCDChipVar(mid=65537, chip=0, typ=3, var=0) in UCID:0.0 in /var/pcce/userb/sctrod/lester/SctRodDaq/SctApiIPC/SctApiServer.cc at line 901.  Something has gone wrong!  It might be that this is a warning you can ignore, which has arisen from modifyABCDChipVar failing when sent to crates NOT contianing the specified module.  At present 30/5/2005 this does happen when the line 'if(rx0 < getRodInfo(label).minLink) {' in SctApi::cacheModuleConfig of SctApi.cxx calls getRodInfo for an off crate rod "label". This cayses getRidInfo to throw an SctApiException("Bad ROD") (see also SctApiMulti.cxx) which SctApi::cacheModuleConfig doesn't attempt to trap .  CGL is awaiting info from BG to determine whether how best to proceed -- whether to only send modification requests to the correct crates (complicated by off crate redundancy!) or whether to make SctApi::cacheModuleConfig more tolerant ...
CORBA::Exception [UNKNOWN] when attempting to SctApiServer::modifyABCDChipVar(mid=65537, chip=1, typ=3, var=0) in UCID:0.0 in /var/pcce/userb/sctrod/lester/SctRodDaq/SctApiIPC/SctApiServer.cc at line 901.  Something has gone wrong!  It might be that this is a warning you can ignore, which has arisen from modifyABCDChipVar failing when sent to crates NOT contianing the specified module.  At present 30/5/2005 this does happen when the line 'if(rx0 < getRodInfo(label).minLink) {' in SctApi::cacheModuleConfig of SctApi.cxx calls getRodInfo for an off crate rod "label". This cayses getRidInfo to throw an SctApiException("Bad ROD") (see also SctApiMulti.cxx) which SctApi::cacheModuleConfig doesn't attempt to trap .  CGL is awaiting info from BG to determine whether how best to proceed -- whether to only send modification requests to the correct crates (complicated by off crate redundancy!) or whether to make SctApi::cacheModuleConfig more tolerant ...
CORBA::Exception [UNKNOWN] when attempting to SctApiServer::modifyABCDChipVar(mid=65537, chip=2, typ=3, var=0) in UCID:0.0 in /var/pcce/userb/sctrod/lester/SctRodDaq/SctApiIPC/SctApiServer.cc at line 901.  Something has gone wrong!  It might be that this is a warning you can ignore, which has arisen from modifyABCDChipVar failing when sent to crates NOT contianing the specified module.  At present 30/5/2005 this does happen when the line 'if(rx0 < getRodInfo(label).minLink) {' in SctApi::cacheModuleConfig of SctApi.cxx calls getRodInfo for an off crate rod "label". This cayses getRidInfo to throw an SctApiException("Bad ROD") (see also SctApiMulti.cxx) which SctApi::cacheModuleConfig doesn't attempt to trap .  CGL is awaiting info from BG to determine whether how best to proceed -- whether to only send modification requests to the correct crates (complicated by off crate redundancy!) or whether to make SctApi::cacheModuleConfig more tolerant ...
CORBA::Exception [UNKNOWN] when attempting to SctApiServer::modifyABCDChipVar(mid=65537, chip=3, typ=3, var=0) in UCID:0.0 in /var/pcce/userb/sctrod/lester/SctRodDaq/SctApiIPC/SctApiServer.cc at line 901.  Something has gone wrong!  It might be that this is a warning you can ignore, which has arisen from modifyABCDChipVar failing when sent to crates NOT contianing the specified module.  At present 30/5/2005 this does happen when the line 'if(rx0 < getRodInfo(label).minLink) {' in SctApi::cacheModuleConfig of SctApi.cxx calls getRodInfo for an off crate rod "label". This cayses getRidInfo to throw an SctApiException("Bad ROD") (see also SctApiMulti.cxx) which SctApi::cacheModuleConfig doesn't attempt to trap .  CGL is awaiting info from BG to determine whether how best to proceed -- whether to only send modification requests to the correct crates (complicated by off crate redundancy!) or whether to make SctApi::cacheModuleConfig more tolerant ...
CORBA::Exception [UNKNOWN] when attempting to SctApiServer::modifyABCDChipVar(mid=65537, chip=4, typ=3, var=0) in UCID:0.0 in /var/pcce/userb/sctrod/lester/SctRodDaq/SctApiIPC/SctApiServer.cc at line 901.  Something has gone wrong!  It might be that this is a warning you can ignore, which has arisen from modifyABCDChipVar failing when sent to crates NOT contianing the specified module.  At present 30/5/2005 this does happen when the line 'if(rx0 < getRodInfo(label).minLink) {' in SctApi::cacheModuleConfig of SctApi.cxx calls getRodInfo for an off crate rod "label". This cayses getRidInfo to throw an SctApiException("Bad ROD") (see also SctApiMulti.cxx) which SctApi::cacheModuleConfig doesn't attempt to trap .  CGL is awaiting info from BG to determine whether how best to proceed -- whether to only send modification requests to the correct crates (complicated by off crate redundancy!) or whether to make SctApi::cacheModuleConfig more tolerant ...
CORBA::Exception [UNKNOWN] when attempting to SctApiServer::modifyABCDChipVar(mid=65537, chip=5, typ=3, var=0) in UCID:0.0 in /var/pcce/userb/sctrod/lester/SctRodDaq/SctApiIPC/SctApiServer.cc at line 901.  Something has gone wrong!  It might be that this is a warning you can ignore, which has arisen from modifyABCDChipVar failing when sent to crates NOT contianing the specified module.  At present 30/5/2005 this does happen when the line 'if(rx0 < getRodInfo(label).minLink) {' in SctApi::cacheModuleConfig of SctApi.cxx calls getRodInfo for an off crate rod "label". This cayses getRidInfo to throw an SctApiException("Bad ROD") (see also SctApiMulti.cxx) which SctApi::cacheModuleConfig doesn't attempt to trap .  CGL is awaiting info from BG to determine whether how best to proceed -- whether to only send modification requests to the correct crates (complicated by off crate redundancy!) or whether to make SctApi::cacheModuleConfig more tolerant ...
CORBA::Exception [UNKNOWN] when attempting to SctApiServer::modifyABCDChipVar(mid=65537, chip=6, typ=3, var=0) in UCID:0.0 in /var/pcce/userb/sctrod/lester/SctRodDaq/SctApiIPC/SctApiServer.cc at line 901.  Something has gone wrong!  It might be that this is a warning you can ignore, which has arisen from modifyABCDChipVar failing when sent to crates NOT contianing the specified module.  At present 30/5/2005 this does happen when the line 'if(rx0 < getRodInfo(label).minLink) {' in SctApi::cacheModuleConfig of SctApi.cxx calls getRodInfo for an off crate rod "label". This cayses getRidInfo to throw an SctApiException("Bad ROD") (see also SctApiMulti.cxx) which SctApi::cacheModuleConfig doesn't attempt to trap .  CGL is awaiting info from BG to determine whether how best to proceed -- whether to only send modification requests to the correct crates (complicated by off crate redundancy!) or whether to make SctApi::cacheModuleConfig more tolerant ...
CORBA::Exception [UNKNOWN] when attempting to SctApiServer::modifyABCDChipVar(mid=65537, chip=7, typ=3, var=0) in UCID:0.0 in /var/pcce/userb/sctrod/lester/SctRodDaq/SctApiIPC/SctApiServer.cc at line 901.  Something has gone wrong!  It might be that this is a warning you can ignore, which has arisen from modifyABCDChipVar failing when sent to crates NOT contianing the specified module.  At present 30/5/2005 this does happen when the line 'if(rx0 < getRodInfo(label).minLink) {' in SctApi::cacheModuleConfig of SctApi.cxx calls getRodInfo for an off crate rod "label". This cayses getRidInfo to throw an SctApiException("Bad ROD") (see also SctApiMulti.cxx) which SctApi::cacheModuleConfig doesn't attempt to trap .  CGL is awaiting info from BG to determine whether how best to proceed -- whether to only send modification requests to the correct crates (complicated by off crate redundancy!) or whether to make SctApi::cacheModuleConfig more tolerant ...
CORBA::Exception [UNKNOWN] when attempting to SctApiServer::modifyABCDChipVar(mid=65537, chip=8, typ=3, var=0) in UCID:0.0 in /var/pcce/userb/sctrod/lester/SctRodDaq/SctApiIPC/SctApiServer.cc at line 901.  Something has gone wrong!  It might be that this is a warning you can ignore, which has arisen from modifyABCDChipVar failing when sent to crates NOT contianing the specified module.  At present 30/5/2005 this does happen when the line 'if(rx0 < getRodInfo(label).minLink) {' in SctApi::cacheModuleConfig of SctApi.cxx calls getRodInfo for an off crate rod "label". This cayses getRidInfo to throw an SctApiException("Bad ROD") (see also SctApiMulti.cxx) which SctApi::cacheModuleConfig doesn't attempt to trap .  CGL is awaiting info from BG to determine whether how best to proceed -- whether to only send modification requests to the correct crates (complicated by off crate redundancy!) or whether to make SctApi::cacheModuleConfig more tolerant ...
The following message is the last of its type which I am going to send to MRS as there seem to be too many for MRS to cope with!  They will still go to the SctApiServer stdout, though.  Message is: CORBA::Exception [UNKNOWN] when attempting to SctApiServer::modifyABCDChipVar(mid=65537, chip=9, typ=3, var=0) in UCID:0.0 in /var/pcce/userb/sctrod/lester/SctRodDaq/SctApiIPC/SctApiServer.cc at line 901.  Something has gone wrong!  It might be that this is a warning you can ignore, which has arisen from modifyABCDChipVar failing when sent to crates NOT contianing the specified module.  At present 30/5/2005 this does happen when the line 'if(rx0 < getRodInfo(label).minLink) {' in SctApi::cacheModuleConfig of SctApi.cxx calls getRodInfo for an off crate rod "label". This cayses getRidInfo to throw an SctApiException("Bad ROD") (see also SctApiMulti.cxx) which SctApi::cacheModuleConfig doesn't attempt to trap .  CGL is awaiting info from BG to determine whether how best to proceed -- whether to only send modification requests to the correct crates (complicated by off crate redundancy!) or whether to make SctApi::cacheModuleConfig more tolerant ...
Multicrate issue pending further information.  CORBA::Exception [UNKNOWN] was caught at line 841 of /var/pcce/userb/sctrod/lester/SctRodDaq/SctApiIPC/SctApiServer.cc in func virtual void SctApiServer::modifyABCDTrims(long unsigned int, const Sct_SctApi::CharBlock&)    At the moment 30/5/2005 it is thought that this is the same sort of an issue as is described in more detail in SctApiServer::modifyABCDChipVar of the same file.  For the moment, we just carry on and hope for the best.  This EXACT message will only be printed once.
Multicrate issue pending further information.  CORBA::Exception [UNKNOWN] was caught at line 828 of /var/pcce/userb/sctrod/lester/SctRodDaq/SctApiIPC/SctApiServer.cc in func virtual void SctApiServer::modifyABCDMask(long unsigned int, const Sct_SctApi::DataBlock&)    At the moment 30/5/2005 it is thought that this is the same sort of an issue as is described in more detail in SctApiServer::modifyABCDChipVar of the same file.  For the moment, we just carry on and hope for the best.  This EXACT message will only be printed once.