Delete Object (QLIDLTO) API


  Required Parameter Group:



  Default Public Authority: *USE

  Threadsafe: Conditional; see Usage Notes.

The Delete Object (QLIDLTO) API is used to delete objects of an object type listed in the description of the object type parameter. Many, but not all, of the library-based external object types on the system can be deleted using this API. You can use the corresponding Delete (DLTxxx) command to delete an object of most types that are not supported by this API although there are some object types for which there is no delete command (for example: *EXITRG, *JOBSCD, *PRDAVL, *RCT). You can also use the corresponding DLTxxx command (if one exists) to delete an object of a type that is supported by this API. A few of the DLTxxx commands for supported object types allow an additional parameter to be specified in addition to the object name and library name. For those object types, this API does not allow you to specify those additional parameters and uses documented values for those parameters. The notes column in Supported External Object Types shows those values as command keywords and values. If those values do not meet your requirements, you will need to use the DLTxxx command specifying the desired additional parameters to delete the objects, rather than this API.


Restrictions

  1. All restrictions that apply to the Delete object (DLTxxx) command for each supported object type also apply to this API.
  2. See Supported External Object Types for more information.

Authorities and Locks

Auxiliary Storage Pool (ASP) Device Authority
Use (*USE)

Library Authority
Execute (*EXECUTE). Additional library authority requirements may be listed for some object types in Supported External Object Types.

Object Authority
See Supported External Object Types for the authorities required for each object type.

Library Lock
*EXCL if deleting a library; otherwise *SHRUPD

Object Lock
*EXCL

Required Parameter Group

Object and library name
INPUT; CHAR(20)

The objects which you want to delete and the library or libraries from which the objects are to be deleted. The first 10 characters contain a simple object name, a generic object name, or *ALL and the second 10 characters contain the library name or one of several special values.

A generic name is a character string that contains one or more characters (the prefix) followed by an asterisk (*). When a generic name is specified, all objects of the specified object type that have names with the same prefix as the generic name are deleted from the specified library or libraries. When *ALL is specified for the object name, all objects of the specified object type are deleted from the specified library. When *ALL is specified for the object name, the library name must be a specific library name (it cannot be a special value.)

Note: When an object name of *ALL is specified, there are no restrictions for the name of the library. System library names such as library QSYS are allowed, but be very careful about specifying a system library name.

When *ALL is not specified for the object name, you can use these special values for the library name or use a specific library name:

Object type
INPUT; CHAR(10)

The type of object which you want to delete. You can only delete objects of one type with each invocation of this API. For a list of the supported object types, see Supported external object types. You must include an asterisk (*) as the first character of the object type.

Auxiliary storage pool (ASP) device
Input; CHAR(10)

The name of an auxiliary storage pool (ASP) device in which storage is allocated for the library that contains the object. The ASP device must have a status of 'Available'. This field must be an asterisk (*) when *CURLIB, *LIBL, or *USRLIBL is specified for the library name in the object and library name parameter. You can use one of the following special values or use a specific ASP device name:

Remove message
INPUT; CHAR(1)

Whether or not to remove completion and informational messages related to the deletion of objects from the job log. Messages are only removed if the object was successfully deleted. Diagnostic and escape messages are not removed for objects that could not be deleted. The following values can be specified:


Error code
I/O; CHAR(*)

The structure in which to return error information. For the format of the structure, see Error code parameter. If this parameter is omitted, diagnostic and escape messages are issued to the application.


Supported External Object Types

The following table lists the object types supported by this API. It also shows the values used when the equivalent Delete (DLTxxx) command allows an additional parameter to be specified. Note that this API does not use the DLTxxx commands and therefore changes made to the defaults or to the authority for those commands will not affect the operation of this API. Additional information related to the object type is also shown.



Usage Notes

This API is conditionally threadsafe. For multithreaded jobs, see the restrictions in the corresponding Delete (DLTxxx) command.

In addition to the following error messages, additional CPFxxxx messages can be returned. See the messages in the corresponding Delete (DLTxxx) command.


Error Messages




API introduced: V6R1

[ Back to top | Object APIs | APIs by category ]