Skip to content

Explicitly identify when a dataset is cataloged but does not exist #175

Open
@bohns

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.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions