PR 2563: dopterr complains it doesn't have the semaphore

When running dopterr ( the TCC's pointing model data acquisition program ), 
it complains it doesn't have the semaphore.  This is after the telescope has 
been slewed via telrun and is currently tracking.  If you then issue an axis 
init in the telrun session, then reissue the dopterr command, it works 
without complaint.  What follows is the response in the telrun session to 
running dopterr as first described.

0 0 : Text="pointing error log file opened"
0 0 > Started; Cmd='Track/Wait -47.75, 42.25 Mount'
0 0 W Text="some axes will not be slewed"; AxisNoSlew="FFT"
0 0 I TCCStatus="TTT","NNN"; TCCPos=86.21,64.32,71.71; AxePos=86.21,64.33,71.71
0 0 I ObjNetPos = -47.750000, 0.000000, 4504129548.01000, 42.250000, 0.000000, 4504129548.01000
0 0 I ObjInstAng = NaN, NaN, NaN
0 0 I SpiderInstAng = NaN, NaN, NaN
0 0 F Modu="prt_ReadReplySet"; Text="too many replies on port LTA19:"
0 0 I Modu="prt_ReadReplySet"; Text="the following replies were read:"
0 0 I Modu="prt_ReadReplySet"; Text="ERR: I don't have the semCmdPort semaphore"
0 0 F Modu="prt_ReadReplySet"; Text="too many replies on port LTA19:"
0 0 I Modu="prt_ReadReplySet"; Text="the following replies were read:"
0 0 I Modu="prt_ReadReplySet"; Text="ERR: I don't have the semCmdPort semaphore"
0 0 F Modu="prt_ReadReplySet"; Text="too many replies on port LTA19:"
0 0 I Modu="prt_ReadReplySet"; Text="the following replies were read:"
0 0 I Modu="prt_ReadReplySet"; Text="ERR: I don't have the semCmdPort semaphore"
0 0 F Modu="axe_o_NoAbsRefCorr"; Text="could not disable absolute encoder correction for AZ , ALT, ROT"
0 0 W AxisNoTrack="TTT"
0 0 I AxisStop="TTT"
0 0 F Text="move failed; axes halted"
0 0 > Started; Cmd='Pterr Close'
0 0 I Modu="exe_DoPtErr"; Text="Pointing data collection ends"
0 0 : Text="pointing error log file closed"


This happened shortly before getclock  997412787 or about 21:05 local time.

I leave it to Russell and Robert to determine if this is a TCC or MCP bug.  
It isn't a show-stopper in any way, but a minor nuisance, and a curious bug.

This has happened each of the three times I have issued a dopterr command 
during this shakedown.