Explicitly identify when a dataset is cataloged but does not exist
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 6
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Is your feature request related to a problem? Please describe.
If zOSMF ds operation encounters a z/OS dataset that is cataloged but doesn't exist on disk, it returns the following:
{"dsname":"IBMUSER.SYSPLEX.JCL","catnm":"CATALOG.Z24B.MASTER","dev":"3390","migr":"NO","mvol":"N","vol":"WORK01"}
... which the Zowe data-sets API maps to:
{"name":"IBMUSER.SYSPLEX.JCL","deviceType":"3390","migrated":false,"catalogName":"CATALOG.Z24B.MASTER"}
User code must check to see if the volumeSerial attribute is missing in order to detect this condition.
The API should explicitly indicate that the dataset is cataloged but does not exist on the specified disk.
Describe the solution you'd like
I suggest adding an attribute mapping of "datasetExists" (True/False) and include this in the API result.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the data-sets API mapping that converts the z/OSMF dataset response into the API result. Trace how the missing volumeSerial case is represented, then add the datasetExists result and verify that cataloged datasets missing from disk are explicitly distinguished from existing datasets.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100