How is resource expiration handled?

[SV]

Has any one seen documentation on how the resource expiration is done in CMOD.

[Justin Derrick]

I would imagine it's no different than other expiration processes -- if all the documents that use that resource have expired, it gets deleted.

Are you seeing strange behavior?  How does what you're seeing differ from what you expected?

-JD.

[SV]

I have not seen any issue or analyzed if do have one. With that said, just wondering on any documentation in general how resource expiration is handled?

I was asked to document this at my work, so curious.
What happens when the resource is reused. How the resource expiration happens when HOLD is removed? Is there any scenario that would cause orphaned resources that may not be expiring and taking space?

[Justin Derrick]

I don't think there's any specific documentation on that, and the only people who can answer that are the people who write the source code for CMOD. 

In the absence of any evidence to the contrary, I'd suggest that resources expire in the fashion I've described.

As for how resources are re-used...   When a new resource is loaded, it's assigned a number (in the arsres table) and stored in the cache or TSM named only by that number.  However, there's a "Resource Comparisons" field in the Application definition.  If a file is loaded into CMOD, and the resources for the file being loaded match any of the resources within the last X (where X is the number in the Resource Comparisons field) resources, then the existing resource(s) are re-used (by pointing to the matching resources already stored). 

If you need an official answer from IBM, open a PMR and request clarification -- hopefully they'll post a technote or include the response in the next release of the documentation.

-JD.