We've added a Damaged Object Report Option to the Cozzi Tools DSPOBJLVL (Display Object Level Information) Command. In addition we've added ordering (sorting) capabilities to the generated output.
Check out the Cozzi Tools website to download or license the COZTOOLS library.
There is at least one Damaged Objects Report available online via (I believe) a Japanese website. The TAATOOL product also includes one, and now the DSPOBJLVL CL command in COZTOOLS also privides this information.
We added it to DSPOBJLVL because (A) we were already using the QGYxxxxx APIs that report Damaged Objects when generating the object list, and (B) we actually had a damaged object or two in one of our IBM i partitions (first time for us).
The Cozzi Tools has a no-charge runtime library that includes our CL commands. A lot of people seem to overlook this capability, and I know none of my nemesises ever mention it in their articles or lectures; so I'm mentioning it here.
To get a list of Damanged Objects you need (A) a paid license to Cozzi Tools, or (B) the free/no-charge runtime library. In either case, the DSPOBJLVL command can be used to produce your Damanged Objects Report. Here's how:
/* The Cozzi Tools Display Object Level Info Command */ DSPOBJLVL OBJ((MYUSRLIB/*ALL)) OBJSTS(*SELECT (*DAMAGED *PARTIAL))
The new OBJSTS (Object Status) parameter allows you to include or omit objects that are damanaged. Specify *SELECT or *OMIT for the first part of the parameter and *DAMAGED or *PARTIAL (or both) for the 2nd part of the OBJSTS parameter. This includes only those objects that are damaged or partially damaged. By default the command selects objects of any status.
When you select the above options, only damaged or partially damanged objects appear on the list. In other situations, when you are selecting objects of any status, when a damaged or partially damanged object appears, a "tic mark" appears on the generated list to the right of the text description, indicating that the object is damaged.
While it has always been rare for objects to become damaged, it is always a possability since power outages or even an abrupt power down of a virtual partition can cause an object to be damaged. Having the means to produce a list of these objects can be beneficial before you run RCLSTG to "fix" them by deleting or in some rare cases, repairing them. Generating a pre-RCLSTG list can help you recover or recreate those objects that are damaged.