SQL login failure - using wrong DBID

Anyone got the blatantly logical reason why my login is failing.

Background
We use quite a bit of Natural to SQL and visa versa processing to update information between us and our clients. We use different alias logins to setup the
SQL_DATABASE_LOGIN=DB
SQL_DATABASE_USER=…
SQL_DATABASE_PASSWORD=…
Then inside out NATPARM we setup the DB Management assignments so that our DBID matches the database to connect to.
When we run our Natural program we access the file and evrything is pretty.

EXCEPT FOR NOW.

For some reason when we access our SQL Table from inside our natural program - the database picked up is for another SQL table.
e.g.
COY-A-TABLE DBID=100 FNR=1 (database=coya on Natparm)
COY-Z-TABLE DBID=200 FNR=1 (database=coyz on Natparm)
source
READ (1) COY-Z-TABLE …

My trace shows that I am trying to connect to connect to coya instead of coyz. And because the UserID and password are not valid on coya I get a
ERROR: 3503
DESC: Internal Natural SQL driver error.
Login failed for user ‘…’

Anyone got a clue???

My bad - always make sure the host’s ip address is correct!:oops: