DB2 installation on AIX   

My guess is that your environment is not set up.

I use this in my .profile (provided by DB2 install, assuming your instance owner had a .profile when the instance is created)

1. The following three lines have been added by UDB DB2.

if -f <instance owner home dir>/sqllib/db2profile ; then
. <instance owner home dir>/sqllib/db2profile
fi

If for some reason, you don't want it in the .profile you can source the db2profile which will set it up.

I think the "1390" message is:

SQL1390C The environment variable DB2INSTANCE is not defined or is
invalid.

Explanation:

The environment variable DB2INSTANCE is not defined or is not set to a
valid instance owner.

User response:

Set the DB2INSTANCE environment variable to the name of the instance to
use. If you do not know the name of the instance to use or how to set
the DB2INSTANCE environment variable to the instance name, refer to the
Administration Guide.

Federated system users: refer to the Federated Systems Guide for
DB2INSTANCE information.

Ensure your PATH environment variable contains the sqllib/adm path in
the home directory of the instance you want to use (for example,
/u/instance/sqllib/adm, where /u/instance is the home directory of the
instance owner on a UNIX system).

You may not have created an instance as part of the install or as a post installation step.

To confirm, run <db2 install path>/instance/db2ilist

That will let you know if you created one or not. If not, you will need to create one with <db2 install path>/instance/db2icrt.

Check the install docs for more information on this step.

Hope it helps!
Pete

ok.

when I run db2ilist

in case of root there is an error: ksh: db2ilist: not found
(I also use chmod 777 for this directory)

and

in case of db2inst1 no any output, only #.

I have some clarifications in your question. Are you sure the DB2 installation went fine ? You can verify the DB2 installation from the DB2 server using this. (NOT FROM THE DB2 CLIENT). Make sure you are verifying this in the DB2 server
for DB2 V8.1 or V8.2 - lslpp -l | grep db2 (u should see DB2 components as committed)

for DB2 v9 and more = db2ls

Once this verification is done. Try to login to the instance in the DB2 server and type db2. If you are able to enter the command prompt then its good. Or please check the .profile in the instance home directory /home/<instancename>.
Then add these lines in the .profile and execute it.

if -f /db2home/<instancename>/sqllib/db2profile ; then
. /db2home/<instancename>/sqllib/db2profile
fi

Where instancename=your instance name
then execute the .profile with this command
. .profile
Then you may exit out of the instance login back and check it should work.
After this we may proceed to remote client connection which involves cataloging of the database.

Hope this helps

thanks