The Delete Subsystem Description (DLTSBSD) command deletes the specified subsystem descriptions (including any work entries or routing entries added to them) from the system. Job queues assigned to this subsystem by the Add Job Queue Entry (ADDJOBQE) command are not deleted. The associated subsystem must be inactive before it can be deleted.
Restrictions:
- To use this command, you must have:
- use (*USE) and object existance (*OBJEXIST) authority to the specified subsystem description and execute (*EXECUTE) authority to the library containing that subsystem description.
- This command cannot be run if an active subsystem is associated with this description.
Subsystem description (SBSD)
Specifies the name and library of the subsystem descriptions being deleted. A specific subsystem description or a generic subsystem description can be specified; either type can be qualified by a library name.
This is a required parameter.
Qualifier 1: Subsystem description
- generic-name
- Specify the generic name of the subsystem descriptions being deleted. A generic name is a character string that contains one or more characters followed by an asterisk (*). If a generic name is specified for this parameter, then all subsystem descriptions with names that have the same prefix as the generic subsystem description are deleted.
- name
- Specify the name of the subsystem description being deleted.
Qualifier 2: Library
- *LIBL
- All libraries in the thread's library list are searched until a match is found. If a specific object name is specified (instead of a generic name), only the first object found to have that name is deleted.
- *CURLIB
- The current library for the thread is used to locate the object. If no library is specified as the current library for the thread, the QGPL library is used.
- *USRLIBL
- Only the libraries listed in the user portion of the library list are searched. If a specific object name is specified (instead of a generic name), only the first object found with that name is deleted.
- *ALL
- All libraries in auxiliary storage pools (ASPs) that are currently part of the thread's library name space will be searched. This includes the system ASP (ASP 1), all defined basic user ASPs (ASPs 2-32), and, if the thread has an ASP group, the primary and secondary ASPs in the thread's ASP group. Only your own QTEMP library is searched. All objects matching the specified name and object type in all libraries in the thread's name space are deleted.
- *ALLUSR
- All user libraries are searched. All libraries with names that do not begin with the letter Q are searched except for the following:
#CGULIB #DSULIB #SEULIB
#COBLIB #RPGLIB
#DFULIB #SDALIB
Although the following Qxxx libraries are provided by IBM, they typically contain user data that changes frequently. Therefore, these libraries are considered user libraries and are also searched:
QDSNX QRCLxxxxx QUSRIJS QUSRVxRxMx
QGPL QSRVAGT QUSRINFSKR
QGPL38 QSYS2 QUSRNOTES
QMGTC QSYS2xxxxx QUSROND
QMGTC2 QS36F QUSRPOSGS
QMPGDATA QUSER38 QUSRPOSSA
QMQMDATA QUSRADSM QUSRPYMSVR
QMQMPROC QUSRBRM QUSRRDARS
QPFRDATA QUSRDIRCL QUSRSYS
QRCL QUSRDIRDB QUSRVI
- 'xxxxx' is the number of a primary auxiliary storage pool (ASP).
- A different library name, in the format QUSRVxRxMx, can be created by the user for each previous release supported by IBM to contain any user commands to be compiled in a CL program for the previous release. For the QUSRVxRxMx user library, VxRxMx is the version, release, and modification level of a previous release that IBM continues to support.
- name
- Specify the library where the subsystem description is located.