To start NEE with SPoD under windows there still remains only one opportunity for me :
Start NEE, invoke Natural, connect with the MF environment, log on to SYSNEE and start NEESTART. Then the Mainframe NEE-environment (Terminal emulation) appeared, I made a definition for an application, defined and executed my impacts… But after starting the according batch job the previous defined application itself had been locked. I wanted to see what had been impacted. But I couldn’t resolve this locking. A password was inquired, which I don’t know. It’s not equal to my own Natural password. :?
Sometimes before this, I tried to get NEE results in accordance to SPoD by using the Windows environment. Additionally I made the repository definition by using a dynamic LFILE assignment. But an error came up which formerly had been described in the Knowledge Database under Document ID 612886. As a solution to this error (GENSEL.ERROR LOADING LIBRARIES! 1999) a redone of the Natural INPL had been requested there. But in my test environment this had been certainly done before! :roll:
The only solution for this, which I can think of, lies in security purposes, because SYSNEE has not been defined as a steplib to any application (Natural Lib). And this may be why NEESTART can’t properly be executed :?: