Table Values, Kill/Continue Dispositions,

[Duy Nguyen]

I have a table of UPINS for providers.  If a provider’s UPIN is listed on the table, I provide a “CONTINUE” and a default of “KILL” otherwise.

I’m using a TCL proc to do a table lookup.  I’ve recently added a UPIN to the table but somehow, my engine tells me it’s KILLING it even though the value is valid in the table!  I’ve bounced the inbound (source) thread already.  Do I need to bounce the outbound thread as well?

Can you guys offer any insight as to what may be happening here?

Thanks!

Topic

[John Hamilton]

Depending on where you are running your code you may have to stop and start the process. If it is pre-xlt kind of thing.   I’m not sure if you purge the caches on the prcocess that may work. I have always just killed and restarted the process to reload everything.

Know all you true experts can speak up correct me and tell us the correct way to reload a table.

[James Cobane]

John/Duy,

You should be able to just ‘purge cache’ on the effected process to invoke the change to the table.

Hope this helps.

Jim Cobane

Henry Ford Health

[Duy Nguyen]

I will give that a shot guys.   🙂

[Author]

Replies