Timeout while waiting for Ndc Server Reply and NAT3148 Error

Hi - I have installed Adabas and Natural One using the Docker and also the Eclipse Natural One developer environment. Docker Version version is 4.21.1 (114176). NaturalOne Version 9.2.1.
I am using this environment to refresh my Natural skills as I was a mainframe coder some 20 years ago! So I am not used to working on a PC with Natural but this is great!

I have set up a new DDM and it has compile correctly and am just testing it out with some simple code - storing and reading etc. The program stows correctly. However when I run the program I get two errors that I cannot seem to get rid of.

The first error say Error Map Environment Timeout Occurred While Waiting for the Ndv server reply.

Following this a second error appears stating:

NAT3148 Database 12 Not active. Subc. 0

I suspect the two errors are related.

Can anyone assist?

Thank you.

Freyja

PS I Enabled the console and this is the output

[20:05:17.196] Natural Runtime proxy started
[20:05:17.209] session parameters:
[20:05:27.321] Logon to Library FLIB
[20:05:27.365] pass server configuration (natparm):
[20:05:27.367] SF=1 IM=D
[20:05:27.367] LT=99999999 MCPU=60 PAGEDATASET=50
[20:05:27.368] ZP=ON FCDP=ON DFOUT=S DFSTACK=S DFTITLE=S PM=R DTFORM=I MAXYEAR=2699
[20:05:27.369] CF=% DC=. IA== ID=, THSEPCH=,
[20:05:27.370] ZD=ON REINP=ON
[20:05:27.371] SM=ON SYMGEN=ON GFID=ON MAXPREC=7 TQMARK=ON
[20:05:27.372] EDTBPSIZE=1048575
[20:05:27.372] Codepage=ISO_8859-1:1987
[20:05:27.375] pass server configuration (sysvar):
[20:05:27.378] language (ULANG)= 1
[20:05:27.386] Ndv server Web I/O version 4020101
[20:05:27.387] new connection to Ndv Server (localhost - 2700 id=901554871) established
[20:05:27.388] Application starting…
[20:05:48.792] execute command R1
[20:05:48.792] throws PalResultException
[20:05:48.793] R1 0017 NAT3148 Database 12 not active. Subc 0.
[20:05:48.794] disconnect from server
[20:05:48.816] Natural Runtime Error: R1 0017 NAT3148 Database 12 not active. Subc 0.
[20:05:55.361] Natural Runtime proxy terminated

The NATURAL programs actually run on the NDV server. While you edit and compile locally the execution is on the server which must have access to Database files as well as having programs uploaded.

Eugene (Gene) Miklovich

ADABAS/NATURAL Systems Support and DBA

Cell: 916-202-7047

Normal Hours: 8am-4pm E.T.

Please call or text if assistance needed outside these hours.

Freyja - Please check your installation for “Adabas Manager” (a browser based Database Administration Tool) and use that to start your database 12.

Hi Douglas,

Thank you so much for your help. OK I managers to start adabas manager and I can see the container in the docker. The following report was in the docker:

2023-07-31 23:43:15 /opt/softwareag/AdabasManager/bin/entrypoint.sh: line 82: find: command not found
2023-07-31 23:43:15 AMNINST_DIR /opt/softwareag
2023-07-31 23:43:15 Replacing the text of installed directory to /opt/softwareag/ in current directory: /opt/softwareag
2023-07-31 23:43:15 You accepted the license agreement
2023-07-31 23:43:16 Checking user admin / manage in auth.config file
2023-07-31 23:43:16 Adding new user
2023-07-31 23:43:16 User “admin” added successfully.
2023-07-31 23:43:16 user admin is found or created in auth.config file.
2023-07-31 23:43:16
2023-07-31 23:43:16 start AMN Runtime server at default port 4990
2023-07-31 23:43:20 keepday 30
2023-07-31 23:43:20 New Log File Path: /opt/softwareag/AdabasManager/logs/amn-2023-7-31.log

I then accesses the manager through the URL of my browser and go into it fine. I then followed this instruction in the manual that states:

Please add the corresponding Adabas REST Server Hostname in Adabas Manager with port 8190 of
your running Adabas Community Edition container. You can see the steps in the following
illustrations

See attached for the image of what I did following these instructions called step 1.

I then hit an error. I could not see any Database 12 in the list.

The attached error kept appearing. See error 1.

So I am making inch by inch progress.

Thank you for your help!

Best

Freyja

Thank you Eugene.

Hi Eugene,

Thank you for your reply.

It looks like the demo data base has been started correctly.

I have this information

Database ID : 12
Database Name : GENERAL_DATABASE
Version : 7.1
Config. file : /data/db012/DB012.INI
Status : active
TCP-Port : 60001
TCP-SSL-Port : Not enabled

However when I go into the ADABAS Manager

I am following instructions as specified on page 20 of the installation guide https://softwareag-usa.s3.amazonaws.com/Adanat_Docker/AN+Community+Edition+Guide.pdf

I have entered the host configuration as instructed but I get the following error and there is no listing for database 12 showing at all.

[db] [500_ADA_REST_ERR]

adabas-db

/API/adabas/database: 500 Internal Server Error

Thu Aug 03 2023 22:18:25 GMT+0100 (British Summer Time)

Is it possible to speak with someone who can walk me through this?

Kind Regards,

Freyja

Hi Douglas,

Thank you for your reply.

It looks like the demo data base has been started correctly.

I have this information

Database ID : 12
Database Name : GENERAL_DATABASE
Version : 7.1
Config. file : /data/db012/DB012.INI
Status : active
TCP-Port : 60001
TCP-SSL-Port : Not enabled

However when I go into the ADABAS Manager

I am following instructions as specified on page 20 of the installation guide https://softwareag-usa.s3.amazonaws.com/Adanat_Docker/AN+Community+Edition+Guide.pdf

I have entered the host configuration as instructed but I get the following error and there is no listing for database 12 showing at all.

[db] [500_ADA_REST_ERR]

adabas-db

/API/adabas/database: 500 Internal Server Error

Thu Aug 03 2023 22:18:25 GMT+0100 (British Summer Time)

Is it possible to speak with someone who can walk me through this?

Kind Regards,

Freyja

Hi Freyja,

i had the same problem but i figured it out.
Use the command “docker network list” to get your network list for Docker. After that you should inspect each of the networks like “docker network inspect ” in my case it was “docker network inspect bridge”.
The result of this command should look like this:

“Containers”: {
“18457c9422a04b09dd1bfd3ec172be1cce5b705a6b245612a145b13c963d95ca”: {
“Name”: “adabas-db”,
“EndpointID”: “8102cff14d2ff8c6572633f277675ba88ac541b03dad67d830aef1e9495d9d2b”,
“MacAddress”: “02:42:ac:11:00:02”,
“IPv4Address”: “172.17.0.2/16”,
“IPv6Address”: “”
},
“392f643707d8009757a1550c39f3df0f8eedeb951c7da9ee8c180502be7cb019”: {
“Name”: “natural-ce”,
“EndpointID”: “a1fd720d34e7707c7d6fd3cde83bedcab7c6707733a31cb524fa112f483add4d”,
“MacAddress”: “02:42:ac:11:00:04”,
“IPv4Address”: “172.17.0.4/16”,
“IPv6Address”: “”
},
“cda3ea4f98d3cdd347b25aa4c870363f5911bd331e96fab396ec166223d025dd”: {
“Name”: “adabas-manager”,
“EndpointID”: “acffac213bf94ac91d9b8e78fc8c70ceb7d338119529d582f7fd41a94da36b5a”,
“MacAddress”: “02:42:ac:11:00:03”,
“IPv4Address”: “172.17.0.3/16”,
“IPv6Address”: “”
}
},

I used the command “docker run -d -p 2700:2700 --add-host adabas-db:127.0.0.1 -e ACCEPT_EULA=Y --name natural-ce softwareag/natural-ce:9.2.1” before, what caused that problem.

After i changed it to “docker run -d -p 2700:2700 --add-host adabas-db:172.17.0.2 -e ACCEPT_EULA=Y --name natural-ce softwareag/natural-ce:9.2.1” it worked fine. Before you can use that command, you need to delete the container that already exists with the command “docker rm -f <CONTAINER_ID>”.
That solved it for me!

Have a nice day

Kind Regards,

Erkan

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.