We’ve been using a shared Natural nucleus (DDN826SH) and have the environment-dependent non-re-entrant nucleus (DDN826BA) for normal batch and a re-entrant nucleus (DDR826BA) for Natural RPC Servers that both reference the shared nucleus. All this is working fine.
Now I am trying to figure out this Natural Development Server which seems to use a similar setup as Natural RPC Servers using re-entrant batch Natural nucleus and additionally what seems to be a redundant different re-entrant nucleus serving as a “front-end” (DDR826SV) which references the other re-entrant nucleus (DDR826BA) which references the shared nucleus (DDN826SH). That alone has me completely confused!
However, attempts to start the NDV server fail with:
NAT9903 NATSTUB NOT LINKED TO NATURAL NUCLEUS DDR826BA.
NATSTUB not linked to Natural nucleus :1:.
Either the module NATSTUB is not linked to the Natural nucleus; or
the shared nucleus :1: has been loaded; but NATSTUB is not defined
as its entry point.
Link the module NATSTUB to the Natural nucleus. If a shared nucleus
is used, specify CMSTUB as its entry point in the link job.
What I don’t want to do is break what works now with normal batch Natural and the Natural RPC Servers.
How do I untangle all this? I feel it is probably incorrect to need both DDR826SV and DDR826BA… can’t DDR826SV just reference the shared nucleus?
How should I include the NATSTUB? Do I add a line anywhere in the linkedit of DDR826SV like:
…or are there rules as to order or should this go into DDR826BA instead (as the error message is indicating)?
How do I change the shared nucleus DDN826SH to specify CMSTUB as its entry point, and will that break existing batch Natural (normal and re-entrant RPC nukes both)? Or do I need a different shared nucleus just for NDV use separate from the shared nucleus I use for everything else?
Please advise… thanks in advance!