You will require the following:
- VTAM entry for db2 subsystem
- VTAM entry activated
- allocate 2 tcpip ports
- started task for DDF (xxxxDIST) xxxx=subsystem name
started task should have LE runtime library in steplib and a dd for the tcpip parm file
- racf for started task, also OMVS super user (UID=0, GID=x)
- ZPARM modification
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 record in BSDS - use program DSNJU003 (see utility guide)
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.
0 comments on more DDF notes