DELETE

Edit online

Use the DELETE action to delete the runtime libraries for your runtime environment.

Before you begin

Review the following information before you use the DELETE action:

The DELETE action requires the RTE_NAME and RTE_PLIB_HILEV parameters and values.
If you are implementing a remote deployment scenario and used the KFJ_LOCAL_PLIB_HILEV parameter when creating the runtime environment, you can also specify this parameter for the DELETE action, depending on your situation. For more information, see Deleting libraries used for remote deployment.
Review details about the data sets that are deleted by the DELETE action and those that are not affected, as follows:
Data sets that are deleted by the DELETE action
The DELETE action deletes the runtime libraries created by the GENERATE action. This includes the PARMGEN libraries that the GENERATE action creates: WCONFIG, interim staging, work, and global user JCL.
The following list describes the name patterns of the data sets that are affected by the DELETE action:
- Data sets that match the following name patterns:
  
  rte_plib_hilev.rte_name.*
  
  rte_hilev.rte_name.*
  
  rte_vsam_hilev.rte_name.*
  
  By default, these are all the same pattern, because the default value for rte_hilev and rte_vsam_hilev is rte_plib_hilev.
- For the following data sets, the default values for these parameters, when not specified explicitly, include rte_name, but custom values are allowed:
  
  rte_pds_hilev.*
  
  rte_pds2_hilev.*
- Data sets that match the following product-specific name patterns, if the respective products have been configured:
  
  IBM OMEGAMON for Db2 Performance Expert on z/OS
  
  KD2_OMPE_DSHLQ.*
  
  KD2_OMPE_VSAM_DSHLQ.*
  
  IBM OMEGAMON for IMS on z/OS
  
  KI2_LOGR_EHLQ.KI2_LOGR_LS_PREFIX.*
- For remote deployment scenarios, if you used the KFJ_LOCAL_PLIB_HILEV parameter for deploying remote environments, data sets that match the following name patterns:
  
  kfj_local_plib_hilev.rte_name.*
  
  kfj_local_hilev.rte_name.*
  
  kfj_local_vsam_hilev.rte_name.*
  
  kfj_local_pds_hilev.*
  
  Note: When deploying remote environments, the rte_* parameters are for the remote runtime environments and the kfj_local_* parameters are for the local runtime environments. On a single run of the DELETE action, either rte_* parameter values or kfj_local_* parameter values are used for the high-level qualifier.
Data sets not affected by the DELETE action
The DELETE action does not affect the following data sets:
- The runtime environment definition library: rte_plib_hilev.RTEDEF
- The security exits library, defined by RTE_X_SECURITY_EXIT_LIB
- The embed overrides library, defined by RTE_X_OVERRIDE_EMBEDS_LIB
- Any other data sets, such as persistent data store data sets, that have been allocated outside the rte_name-based data set name patterns described previously
- z/OS® UNIX® System Services directories

About this task

The following list provides details about the DELETE action:

The DELETE action uses the specified information and values in the configuration members to derive the names of the data sets to be deleted.
You must perform the DELETE action on the system where the files to be deleted exist, which is significant in remote deployment scenarios.
The DELETE action requires the CONFIRM workflow variable to delete the data sets. You can also use the CONFIRM parameter to preview the data sets that will be deleted. Specify the CONFIRM parameter in the KCIVARS DD statement with one of the following values:

N

(Default) List all data sets that will be deleted. The list appears in KCIPRINT.
Important: It is recommended that you review the list of data sets that will be deleted before performing the delete.

Y

Delete the data sets. The DELETE action deletes your runtime libraries, as described in Data sets that are deleted by the DELETE action.

Procedure

Perform the following steps on the system where the files to be deleted exist:

Modify the KFJJMCM sample job in TKANSAM (see example below) to select a DELETE action.
Add the CONFIRM workflow variable and set to N, which will allow you to review the list of data sets that will be deleted.
Specify values for the required parameters RTE_NAME and RTE_PLIB_HILEV.
For remote deployment scenarios: If you are using remote deployment and want to delete data sets on the configuration system, specify the KFJ_LOCAL_PLIB_HILEV parameter and value.
Run the KFJJMCM job to display the data sets that will be deleted.
The list appears in the KCIPRINT SYSOUT data set.
Review the generated list of data sets that will be deleted.
If you are satisfied with the list of data sets that will be deleted, change the CONFIRM workflow variable to Y and run the KFJJMCM job.
The DELETE action deletes your runtime libraries.

Example

The following JCL deletes the runtime libraries for the runtime environment that is defined in the member TSOUID.MONSUITE.RTEDEF(RTE1).

Figure 1. Example JCL to perform the DELETE action

//UID#ZMCM JOB ,CLASS=A,MSGCLASS=X,NOTIFY=&SYSUID
/*JOBPARM SYSAFF=ZOS1
//S1       EXEC PGM=KCIOMEGA,REGION=0M,DYNAMNBR=256
//STEPLIB  DD DISP=SHR,DSN=MONSUITE.TKANMOD
//KCIFLOW  DD DISP=SHR,DSN=MONSUITE.TKANCUS(KFJOMEGA)
//KCIVARS  DD *                                        
ACTION            DELETE
CONFIRM           Y
RTE_NAME          RTE1
RTE_PLIB_HILEV    TSOUID.MONSUITE
/*

Note the JES2 SYSAFF that causes the job to run on LPAR ZOS1. This is required only if the RTE_NAME parameter in the TSOUID.MONSUITE.RTEDEF(RTE1) member refers to a variable whose value is LPAR-specific.