Deleting a report

You can use the UNLOAD function of the ARSADMIN program to delete the index data and documents that the ARSLOAD program stored in the system during a load process. To use the UNLOAD function, you must specify the Load ID that the ARSLOAD program generated during the load process. The Load ID represents the index data that was added to the database and the storage objects that were copied to cache storage and archive storage. The Load ID can be found in the message log that the ARSLOAD program saved in the System Log.

When you use the UNLOAD function, you must specify the name of the application group and the Load ID. You can obtain the Load ID from the message log that the ARSLOAD program generated during the load process. If there is more than one Load ID listed in the message log, then you should use the last Load ID listed in the log. Storage locations include cache storage, the primary storage node, and the secondary storage node. The UNLOAD function deletes the storage objects associated with the Load ID. The UNLOAD function also deletes the rows of index data that were added to the database during the original load process.

The following shows an example of the program, path, and required parameter values to run the ARSADMIN program from the TSO OMVS command line on a z/OS® server to delete a load process from all of the storage locations: 
     /opt/IBM/ondemand/V10.5/bin/arsadmin unload -g 'Credit' -L 1220-1-0-8FAA-5538-5673

When the ARSADMIN program completes, you should open the System Log folder to view the messages that were generated during the UNLOAD process.

Note:
  1. The Content Manager OnDemand server program (ARSSOCKD or ARSOBJD) must be running, otherwise the ARSADMIN program will fail.
  2. See ARSADMIN for more information about the ARSADMIN program and the parameters that you can specify to UNLOAD data from the system.
  3. See Commands overview for information about running the Content Manager OnDemand programs as commands (under the TSO OMVS command), specifying JCL to run the Content Manager OnDemand programs from jobs and started tasks, and examples of how to specify parameters to the Content Manager OnDemand programs.