DB2 related pages
Allocate TCPIP port numbers for the DRDA and RESYNC ports. Update the TCPIP profile with reservations for these numbers. This is not strictly necessary if the numbers are above 1024.
Note the TCPIP home address, from the profile.
Update the BSDS with the port numbers. (Usually done with DB2 down). PORT= for the DRDA port and RESPORT= for the RESYNC port.
Ensure that the user on the xxxxDIST job has a RACF definition for OMVS(UID(0)) and that the group has the definition OMVS(GID(n)). Note UID must be zero, whilst GID can be any number.
Add the TCPIP profile dataset to the xxxxDIST job. Also ensure the xxxxDIST job has the LE/370 runtime library in the STEPLIB.
Get the host name and address for any TCPIP hosts that will connect to this DB2. This includes other lpars and any PC’s that may be running DB2 Connect. Update the TCPIP HOSTS file with the host addresses, and run the MAKESITE utility.
Add the port numbers to the TCPIP ETC.SERVICES file, if IPNAMES (below) is to contain host names rather than host addresses.
Review the ZPARM parameters that relate to TCPIP. Initially use TCPALVER=YES to minimise problems with the first connections. It can be changed to NO later, if necessary.
Add entries to the DB2 communications database for the hosts to be defined. Entries will be required in SYSIBM.LOCATIONS and SYSIBM.IPNAMES at a minimum.
Must set up nnnnDIST and nnnnSPAS regions for each subsystem.
Must change ZPARM module to add STORPROC=nnnnSPAS and DDF=AUTO and MAXTYPE1=2. Also TCPALVER=YES to start with.
Must update the BSDS with a new DDF record with PORT= port number above and RESPORT= resync port number above. These numbers were chosen at random and are not below 1024, which are generally reserved by MVS. VTAM addresses!
In DB2 Connect use the Client Configuration Assistant to define the databases. The information above is required to set up each database system. Note the name is the local name in the subsystem. Use TCP/IP, and mark that the database is on the host. Under security select host security. After finishing the definition, it is worth going back into the properties and making sure that host security is still selected.
Using the Command Line Processor enter the commands
LIST DATABASE DIRECTORY
LIST NODE DIRECTORY
LIST DCS DIRECTORY
It is likely that the last of these will show there is no DCS directory. Define an entry with the command
CATALOG DCS DATABASE TECHDB2 AS TECHDB2
and run the LIST command again. Catalog any databases still missing from the DCS directory.
You will require the following:
started task should have LE runtime library in steplib and a dd for the tcpip parm file
DDF=AUTO or =COMMAND to allow either automatic start or manual start
CMTSTAT=number of DDF threads to allow
DB2 subsystem will have to be recycled to make this change effective
DDF LOCATION=anything,LUNAME=vtamname,PORT=ipport1,RESPORT=ipport2
LOCATION can be subsystem name, it is the database name when trying to connect via odbc
Requires DB2 subsystem to be stopped when DSNJU003 is run.
ODBC connection will require some DB2 software at the connecting location , e.g. Windows PC. This may be a suitable version of DB2 UDB for Linux, Unix, Windows, or it may have to be a copy of DB2 Connect. Depending on how DB2 for mainframe was ordered, if all the freebie products were ordered, then a copy of DB2 Connect Personal Edition (single licence) may already be available.
If you have to install DB2 Connect then we may be into some hard work. It requires some stored procedures and WLM environments (Goal mode). Also RRS is required.
For the stored procedure stuff, there should be a skeleton job DSNTIJCC in the install SDSNSAMP dataset. This should be copied to the subsystem customised SDSNSAMP dataset, customised and run. Note it names the WLM environments it expects to be there by default; these can be changed to fit in with any existing standards.