Same code but different outcome

[robin24]

Hello Everyone !!!

Please share your experience and possible solution for below concern. 

Using PROC IMSTAT: A code is written to DELETE records from a LASR server table on a specified condition

and then APPENDS records from another table consisting of latest data.

Issue: 

Case 1. When code executed in SAS EG manually, LASR server tables get updated with exact values as required. 

Case 2. But when executed through scheduled SAS DI Job,  LASR server table gives missing numeric values for couple of columns, where as remaining numerical column values matches exactly with source tables.

Note: Total records at the end matches to source table in both the cases.

Please suggest why such difference and how same can be removed. 

Regards,

Robin Sharma

[Reeza · Accepted solution]

Any notes/errors in the logs that differ?
Does this process include the import of any data, especially from a text file?

[SASKiwi]

AFAIK any table used in SAS DI must also be registered in SAS metadata so one possible cause of your symptom is the metadata registration does not match the actual table attributes. I suggest you update the VA load table metadata registration to see if that fixes your problem.