CL Programming
You can use the Retrieve Object Description (RTVOBJD) command to return the
descriptions of a specific object to a CL procedure. Variables are used
to return the descriptions. You can use these descriptions to help you
detect unused objects on the system.
The command can return the following descriptions as variables for an
object:
- The name of the library that contains the object
- Any extended attribute of an object (such as program or file type)
- User-defined attribute
- Text description of the object
- Name of the object owner's user profile
- Name of the primary group for the object
- Object ASP number
- Library ASP number
- Object ASP device
- Library ASP device
- Indication of whether or not the object overflowed the ASP in which it
resides
- Date and time the object was created
- Date and time the object was last changed
- Date and time the object was last saved
- Date and time the object was last saved during a SAVACT (*LIB, *SYSDFN, or
*YES) save operation
- Date and time the object was last restored
- Name of the object creator's user profile
- System the object was created on
- Object domain
- Digitally signed system-trusted source
- Digitally signed multiple signatures
- Whether or not usage data was collected
- Date the object was last used
- Count (number) of days the object was used
- Date the use count was last reset
- Storage status of the object data
- Compression status of the object
- Size of the object in bytes
- Size of the object in bytes of storage at the time of the last save
- Command used to save the object
- Tape sequence number generated when the object was saved on tape
- Tape or diskette volumes used for saving the object
- Type of the device the object was last saved to
- Name of the save file if the object was saved to a save file
- Name of the library that contains the save file if the object was saved to
a save file
- File label used when the object was saved
- Name of the source file that was used to create the object
- Name of the library that contains the source file that was used to create
the object
- Name of the member in the source file
- Date and time the member in the source file was last updated
- Level of the operating system when the object was created
- Licensed program identifier, release level, and modification level of the
compiler
- Object control level for the created object
- Information about whether or not the object can be changed by the Change
Object Description (QLICOBJDD) API
- Indication of whether or not the object has been modified with the Change
Object Description (QLICOBJD) API
- Information about whether or not the program was changed by the user
- Name, release level, and modification level of the licensed program if the
retrieved object is part of a licensed program
- Program Temporary Fix (PTF) number that resulted in the creation of the
retrieved object
- Authorized Program Analysis Report (APAR) identification
- Type of auditing for the object
- Whether or not the object is digitally signed
- Current journal status for the object
- Current or last journal
- Journal image information
- Journal entries to be omitted information
- The date and time that journaling was last started
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]
(C) Copyright IBM Corporation 1992, 2005. All Rights Reserved.