What are the steps to remove an old/unwanted Gen Host Encyclopedia (HE).
The instructions assume that the Host Encyclopedia (HE) to be removed uses DB2 databases that are completely separate from any other HE that is still in use. It is assumed that all models are already moved to a new Host Encyclopedia (if necessary) and are no longer needed.
The HE comprises the software in the installation datasets plus its DB2 database(s).
The recommendation is to do the following before performing the database removal steps:
These instructions apply to Gen 8.x Host Encyclopedias. For earlier releases, determine the information that was used to create the environment from the installation jobs and TIUGLOB clist.
This information is displayed in the Environment Specification – Display System Information panel – option 5.5 from Main Menu:
Select option 1 for Host Encyclopedia Variables to determine the plan prefix and encyclopedia dataset prefix:
Select option 3 for Host Encyclopedia DB2 variables to determine the DB2 subsystem, secondary authorization ID, DB2 collection ID, Runtime collection ID, Schema DB name, Data DB name, Public Interface DB name:
Alternatively, this information can be found in the TILPARMS members (TIUHE and TIUHE2) or the JCL for the HE installation jobs.
The Host Encyclopedia databases to drop will be the Schema DB name, Data DB name and Public Interface DB name found via option 5.5.3 for the Host Encyclopedia DB2 variables.
The drop of the database will remove all DB2 objects for Gen. It will also drop the tables and table spaces.
NOTE: When running SPUFI, be sure and set the default DB2 name to the correct DB2 subsystem. May also want to consider running SPUFI in batch after thoroughly checking out the statements. Otherwise, SPUFI under TSO could be locked up for a long time due to table locks.
Run this SQL to drop a database:
DROP DATABASE 'yyyyyyyy'.'xxxxxxxx'; where yyyyyyyy is the secondary authorization id and xxxxxxxx is the database name.
Run this SQL to drop a tablespace:
DROP TABLESPACE 'yyyyyyyy'.'xxxxxxxx'; where yyyyyyyy is the secondary authorization id and xxxxxxxx is the tablespace name.
If it exists drop the RPROF database.
Make sure it is not still used by any generated applications or z/OS Implementation Toolset environments. If so, do not drop the RPROF database.
To find the name of the RPROF database, refer to the RPROFDB SQL member used in the installation BLDRPROF job.
Drop any z/OS Implementation Toolset database that is no longer used. Take a backup of the DB2 database first.
To find the z/OS Implementation Toolset database name, refer to TIXSDATA variable in the TIUIT2 TILPARMS member.
Also, make note of the collection IDs (TIXECOLL and TIXERTCO), DB2 authorization IDs (TIXAUTH1, TIXAUTH2), DB2 subsystem (TIXEDB2I), and installation dataset prefix (TIZAPREF).
Run SQL to find all binds where ‘xxxx’ is the bind prefix:
SELECT * FROM SYSIBM.SYSPLAN
WHERE NAME LIKE 'xxxx%_%';
Confirm the bind plans match the environment. Crosscheck with those listed in the clist used to create the binds.
Run SQL to find all the packages where ‘xxxxxxxx’ is the secondary authorization ID:
SELECT COLLID, NAME, VERSION, PDSNAME
WHERE OWNER = 'xxxxxxxx';
Confirm the collection ID and packages match the environment. Crosscheck with those listed in the clist used to create the package binds.
Use the SPUFI panel to do this with unique identifiers such as the plan prefix.
Use the SPUFI panel to do this with unique identifiers such as the collection ID.