Run DSQ3EDBI, the database installation job, for each SQL database that you are connecting to QMF.
Skip this procedure if you have a DB2 guest sharing environment and have installed QMF for VM. Under these conditions, you can continue with Tailor QMF for NLF, if you have an NLF to install, or skip to Link-edit jobs for QMF for a base installation.
DSQ3EDBI
ch /..*/*/ *
// SETPARM STEP1=YES -- CREATE QMF CONTROL TABLES IN SQL DB // SETPARM STEP2=YES -- LOAD QMF PACKAGES INTO SQL DB // SETPARM STEP3=YES -- LOAD QMF SAMPLES INTO SQL DB
For subsequent installations, or under error conditions, some of the job steps might need to be set to NO. Changing the setparm to NO will skip the step.
// SETPARM DBNAME=SQLDSparameter and verify or change SQLDS to the name of the database that you are using. DBNAME is the database name that is specified in the SQL DBNAME directory.
If an earlier version is installed, located the following statement and change the value from NO to Version 3.3, Version 6.1, or Version 7.1:
// SETPARM MIGRATE=NO //
Using this parameter will prevent duplicate control tables from being created.
The QMF installation procedures assume that the password for SQLDBA is set to SQLDBAPW. IF the password is set to anything else, DSQ3SETQ.A must be updated and re-cataloged into the QMF installation library.
To update DSQ3SETQ.A:
CONNECT SQLDBA IDENTIFIED BY 'new-SQLDBAPW'
To install QMF into additional DB2 databases, repeat the procedure for each database, starting with step 3.