Re: Vanishing OUTLINKS

[goodrich@noao.edu (Bret Goodrich)]

Which is the problem, the CAD or the CAR record?  You said the "CAD"
produced the error, but the database you gave shows only a longout
and a "CAR" record.

I have run the test problem on 3.12.2 without any error.  I get:

        -> dbpf "mc:dir_0.TPRO", "1"
        DBR_UCHAR:          1         0x1                 
        value = 0 = 0x0
        -> dbpf "mc:move.TPRO", "1"
        DBR_UCHAR:          1         0x1                 
        value = 0 = 0x0
        -> dbgf "mc:dir_0.LSET"
        DBR_SHORT:          1         0x1                 
        value = 0 = 0x0
        -> dbgf "mc:move.LSET"
        DBR_SHORT:          1         0x1                 
        value = 0 = 0x0
        -> dbpf "mc:dir_0.PROC", "1"
        process:   mc:dir_0
        process:   mc:move
        DBR_UCHAR:          1         0x1                 
        value = 0 = 0x0
        -> dbpf "mc:move.PROC", "1"
        process:   mc:move
        DBR_UCHAR:          1         0x1                 
        value = 0 = 0x0
        -> dbpf "mc:dir_0.PROC", "1"
        process:   mc:dir_0
        process:   mc:move
        DBR_UCHAR:          1         0x1                 
        value = 0 = 0x0
        
        
The dir_0 record is a longout with .OUT as a PP/NMS link to move.DIR.
Processing dir_0, move, and then dir_0 again works fine.

bret
--------------------  
Bret Goodrich, Gemini 8 Meter Telescopes Project, Tucson, Arizona, USA
Internet: goodrich@gemini.edu     SPAN/HEPNET: noao::goodrich
Phonenet: 1.520.318.8522          Snailnet:    PO Box 26732, Tucson, AZ 85726