Filter
Top Products
The sections that follow contain examples of commands to update these tables
for DB2 Universal Database for OS/390. Work with your DB2 Administrator
to determine the updates required for your DB2 Universal Database for
OS/390 system. For more information on the DB2 Universal Database for
OS/390 Communications Database tables, refer to the DB2 Universal Database
for OS/390 SQL Reference.
Updating SYSIBM.LUNAMES
To permit database connection requests to be accepted from any incoming
DB2 Connect LU, just insert a blank row. Use an SQL similar to the following:
INSERT INTO SYSIBM.LUNAMES (LUNAME) VALUES (' ')
Alternatively, if you want to restrict access by LU name, you can use an SQL
command similar to the following to update this table:
INSERT INTO SYSIBM.LUNAMES (LUNAME,
SECURITY_OUT,
ENCRYPTPSWDS,
USERNAMES)
VALUES('NYX1GW01','P','N','O');
Result:
COLUMN EXAMPLE REMARK
====== ======= ======
LUNAME NYX1GW01 Name of the DB2 Connect LU
SECURITY_OUT P
ENCRYPTPSWDS N
USERNAMES O
Updating SYSIBM.IPNAMES
If you want to permit inbound database connection requests for TCP/IP
nodes, you can use an SQL command such as the following to update this
table:
INSERT INTO SYSIBM.IPNAMES (LINKNAME) VALUES(' ')
Configuring DB2 for MVS/ESA
Before you can use the DB2 Connect connection, your DB2 for MVS/ESA
Administrator must configure DB2 for MVS/ESA to permit connections from
the DB2 Connect workstation. To configure DB2 for MVS/ESA, the following
tables need to be updated:
v SYSIBM.SYSUSERNAMES
v SYSIBM.SYSLUNAMES
v SYSIBM.SYSLUMODES
Chapter 5. Configuring Host and AS/400 Databases for DB2 Connect 45