Hi!!!

I've made a new table with a reference to tcmcs010. Now, when I use to fill the tabel via my Session, I get the BW Message:

---------------------------------------------------------------------------------------

>> Error: Unknown Reference from 'llsls010.ccty' to 'tcmcs010'
>> Error: found 1 errors during scanning/parsing .. Stopped.
>> Fatal error: Error 301 (Query not correct) on SELECT
>> Fatal error: Can not continue in llsls0110m000 in DLL: ottstpstandard()

---------------------------------------------------------------------------------------

I controlled my query and it's correct (it's a a BaaN-generated Session and script via Session ttadv1135m000). May I have to look to the tcmcs010-table?
Does anybody know, what I have to do???

Is your llsls010 table new? If so, did you run a create runtime data dictionary (ttadv5210m000) on tcmcs010, too? I've found that sometimes this is necessary if you have created a reference in another table (sometimes, it seems to be taken care of by using a wide open convert to runtime (ttadv5215m000).

I tried it and now it works. I thought I already made it, but I don't!!!

Thanx!!!

I'm running into the same problem.. and tried Ed's solution, but did not work...
any other ideas?
I'm referencing in a new table the tiitm001.item field and after adding a new record on my new session and trying to tab to the second field I get the same error message..
I'm almost convinced to do a manual query to bring the item description.. but it should work..
Any help will be appreciated.

Thanks


Daniel
NAI

Did you create runtime on both the new table and tiitm001? You might also want to make sure that tiitm001 is not in shared memory, if so stop and restart shared memory - not an app manager so I am not sure if this is possible. Also do not forget to logout of Baan, then back into Baan.

Mark

mark_h,
thanks it was the shared memory reboot what I was missing

thanks again

Daniel

So that you don't need to reboot shared memory as whole, you can remove just the referenced table by itself using the shared memory manager.

ed

So what is it exactly? Is it rebooting the shared Memory through BW or through Unix ? Or by either of them as it doesnt matter?

It's the shared memory on the server - essentially the table definition is still loaded there until you remove it and so you will continue to get the error 301 until you undertake that task.

It's the shared memory on the server - essentially the table definition is still loaded there until you remove it and so you will continue to get the error 301 until you undertake that task.

So how does the system admin operate the shared memory manager, Through BW or through the OS ?

Dont know in practise about Shared Memory Manager much. Havent used it .:confused:

So how does the system admin operate the shared memory manager, Through BW or through the OS ?

Dont know in practise about Shared Memory Manager much. Havent used it .

Refer to the latest -
Infor Enterprise Server Administration Guide
Document code U8854O US
Release 10.4
Publication date December 12, 2014
Chapter 19 Shared Memory
The shared memory is a part of physical memory intended for common use. Programs communicate with each other through shared memory. Shared memory results in faster access to the components loaded in shared memory. To enhance the performance of your LN system, you can load program objects and report objects into the shared memory. Before you set up and initialize shared memory, you should verify that the hardware and internal memory is sufficient.

Our system is quite old (and soon to be retired as we are moving to a different ERP product) being Baan IV on Windows, the shared memory manager is inside a server component called Baan NT Manager. Inside that the tool is Shared Memory Manager.
You can unload domain & table definitions using that instead of having to stop the service as a whole.