TPFCS maintenance and diagnostic tool enhancements

TPFUG_Req_Number: D08005S
ORIGIN DATE: March 25th, 2008
REQUIREMENT ABSTRACT : Provide additional maintenance, investigative and diagnostic tools for TPFCS. Since the TPF file system is subject to a higher level of management and has its own utility functions, these requirements do not apply to TPF file system collections.


REQUIREMENT DESCRIPTION :
• Provide a function to display the PIDs and any associated browser names of all collections in a datastore
o DS_INVENTORY is optional and is not guaranteed to be complete. Browser names may not be defined for all collections in a datastore. This means there is currently no reliable means of identifying all collections
o 'All collections in a datastore' may need to mean 'all collections in a datastore that recoup can locate'
o Providing PID and any associated browser name avoids the need for a subsequent ZBROW NAME DISP ALL entry and the manual process of matching PIDs and browser names from the result of the two displays.
o The display function should be able to provide a 'tree' representation of the collections, with any associated browser names, so the relationship between embedded collections can be easily identified.
• ZBROW DISP FA should display any associated browser name with the owning collection.
• Provide the ability to capture a datastore and restore (restore or import) ALL or SELECTIVE collections captured.
o Latest support provides capture support for a list of collections but not the ability to capture or restore all collections so multiple capture requests would be required for datastores with large numbers of user collections. This would be error-prone and should not be necessary.
o Capture of a datastore includes capture of the system collections required to retain datastore integrity on any restore.
o The ability to capture all collections should not require the user to create browser names for all the collections at the time of capture.
o Any browser name requirements should be managed by the restore (restore or import) function.
o Any embedded PIDs in restored collections should be automatically replaced as part of the restore if new PIDs for that collection are allocated by the restore.
o Provide the ability to interrogate the capture tape(s) used in a full datastore capture to provide a 'tree' display of the collections captured and other captured collections that reference them.
o Procedures for using the capture/restore capability should be provided to ensure restored collections are fully available to applications that need to use the restored (restored or imported) collections (e.g. browser name setup, recoup index setup requirements). This is especially important if a restored collection is allocated a different PID from the captured collection. The procedures for any restore should be made as simple as is programmatically possible.




CRITICAL SUCCESS FACTORS


ALTERNATIVE SOLUTIONS

N/A

SOLUTION CONSIDERATIONS (required)