RE: asynRecord immutable fields

["Mark Rivers" <rivers@cars.uchicago.edu>]

If the TIME field is changing when the gensub record processes, then
something is causing the asyn record to process.

I wonder if having the links for TMOD and NOWT =PP is causing your
problem.  Perhaps when it goes to write those values the asyn record is
already processing (PACT=1) and so it won't write the values.  Try
changing those links to NPP.

Mark
 

> -----Original Message-----
> From: Eric Williams [mailto:ECWilliams@lbl.gov] 
> Sent: Wednesday, January 23, 2008 2:43 PM
> To: Mark Rivers
> Cc: tech-talk@aps.anl.gov
> Subject: Re: asynRecord immutable fields
> 
> Mark Rivers wrote:
> >> When I process the genSub record, which triggers
> >> the write to those fields, the TIME field of the asynRec 
> is updated.
> >>     
> >  
> > That is incorrect behavior, writing to the TMOD or NOWT 
> fields should NOT cause the TIME field to update, because 
> those fields are not defined as PP (Process Passive).  When I 
> test modifying those fields with dbpf the TIME field does NOT update:
> Since I didn't say TIME changed with dbpf, I'm not surprised at your 
> results.
> > I suspect that perhaps you have the attribute PP on your 
> gensub links for the TMOD and NOWT fields, while those should 
> actually be NPP.  But I still don't understand why the fields 
> would not update.
> Yes, the links from the genSub record are PP.  That may be 
> unnecessary, 
> but, as you say, it doesn't explain why the fields won't update.  If 
> there were a bug in my genSub processing routine, then when I re-link 
> the output to a longin record instead of NOWT it should also 
> fail.  Yet 
> it succeeds.  Very puzzling.
>