The sections that follow contain examples of commands to update these
tables. Work with your DB2 Administrator to determine the options required
for your DB2 for MVS/ESA system.
Updating SYSIBM.SYSUSERNAMES
If you want to use secondary authorization IDs, you can use the following
SQL command to update this table:
INSERT INTO SYSIBM.SYSUSERNAMES VALUES('I','ADBUSER','NYX1GW01',' ',' ');
Result:
COLUMN EXAMPLE REMARK
====== ======= ======
Type I
Authid ADBUSER
LU Name NYX1GW01 Name of the DB2 Connect LU
NewAuthID (blank)
Password (blank)
USERNAME types are: O (outbound translation), I (inbound translation), B
(both inbound and outbound) and blank (no authorization ids are translated,
and no passwords are sent to the server).
Updating SYSIBM.SYSLUNAMES
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.SYSLUNAMES VALUES('NYX1GW01','IBMRDB','A','N',' ','I');
Result:
COLUMN EXAMPLE REMARK
====== ======= ======
LUNAME NYX1GW01 Name of the DB2 Connect LU
SYSMODENAME IBMRDB
USERSECURITY A
ENCRYPTPSWDS N
MODESELECT
USERNAMES I
Alternatively, just insert a blank row, and this will allow any incoming DB2
Connect LUs to be accepted.
Updating SYSIBM.SYSLUMODES
You can use an SQL command such as the following to update this table:
INSERT INTO SYSIBM.SYSLUMODES VALUES ('NYX1 ', 'IBMRDB', 150, 'Y');
46 Quick Beginnings