We installed our first Domino server on iSeries.Installed as 5.0.10, then upgraded to 6.0.
Then we decided to add a second Domino partition. The install failed because the first install did not include partitioning. We added partitioning to the first Domino partition and successfully installed the second partition.
Since the second install, the first partition stays in the “Starting” state. The second partition always goes to “Started”.
Both servers seem to function properly - fully accessible and always able to stop them.
While this seems to not have an operational impact, we don’t like the server being in this state and would like to resolve it before putting these Domino servers into production.
iSeries 820 v5r2 (PTF’s very current)
Domino 6.0
Domino00
Ports=MEDTCP
MEDTCP_TcpIpAddress=0,10.100.1.39:1352
MEDTCP=TCP,0,15,0,12288
Domino02
Ports=MEDTCP
MEDTCP_TcpIpAddress=0,10.100.1.38:1352
MEDTCP=TCP,0,15,0,12288
Subject: Domino partition on iSeries never goes to Started
Check if there is a joblog in the SERVER job of your first DOMINO partition.
Subject: RE: Domino partition on iSeries never goes to Started
I checked the log which pointed to QNNINAPI , reason code 5. Did a search on this and have come up with nothing.
Subject: RE: Domino partition on iSeries never goes to Started
QNNINAPI with error code 5 indicates a possibility that the server couldn’t find the data directory. Check this file to see if the data directory path and the partition number are specified correctly:/qibm/userdata/lotus/LOTUS_SERVERS
For your environment, you should see there are at least two SERVER= entries there.
Subject: RE: Domino partition on iSeries never goes to Started
Thank you for your help. My issue has been resolved.I located the LOTUS_SERVERS file and found an incorrect Server= entry.
This is how it happened: This iSeries server was originally installed and configured in an isolated network for testing reasons. It will replace an active production server by the same name - MED01. Following some testing, we decided to bring this server into the production environment with,of course, a different name - MED03. All references in the INI file to MED01 were changed to MED03 and the server ID for MED03 was placed appropriately on the iSeries server. Cfgdomsvr was never used for
the MED03 server so the Servers= line for this partition in the LOTUS_SERVERS file is still MED01. When I make all the appropriate INI changes and start this partition as the MED01 server, the wrkdomsvr displays correctly - Started. I am 11 days from going live with this server, so I am not re-configuring for this issue.
Thanks for the help. As an iSeries newbie I had no knowledge of the LOTUS_SERVERS file.