sdk(files): Return data set attributes with the correct type

[zFernand0]

Describe the bug

Extenders of the zos-files-sdk receive data set attribute values as string when some of them should be numbers.

Expected and actual results

Perform a List.DataSet operation and notice that numeric values (e.g. blksz) are returned as strings

Describe your environment

N/A: SDK-related issue

Additional context

This came up because of how extenders of the zos-files-sdk (like Zowe Explorer) may have to parse certain values to their correct types.

Relevant files

• https://github.com/zowe/zowe-cli/blob/master/packages/zosfiles/src/methods/list/doc/IZosmfListResponse.ts

[github-actions]

Thank you for creating a bug report.
We will investigate the bug and evaluate its impact on the product.
If you haven't already, please ensure you have provided steps to reproduce the bug and as much context as possible.

[traeok]

Consider adding type generic to interface (defaulting to the current string type) and then adding logic in SDK to transform according to requested type generic.

[tayvz]

Hi, I'd like to take this on if it's available.

My planned approach:

• Update IZosmfListResponse to type blksz, extx, lrecl, sizex, and used as number instead of string
• Add a coercion utility that converts these fields after z/OSMF responses are parsed in List.dataSet() and List.allMembers()
• Handle edge cases like undefined, non-numeric strings like "N/A", and values that are already numbers
• Add unit tests for the coercion logic

I noticed Copy.ts already works around this with manual parseInt() calls in generateDatasetOptions, so this fix would address the root cause.

Should I target master or is there a next/v4 branch for this since it's tagged as a breaking change?

[zFernand0]

Hey @tayvz, 👋
Thanks for showing interest in the Zowe SDKs 🙏
There is no next branch yet, but there could be ways to do this in a non-breaking fashion. 🤔
Since there is nobody assigned, feel free to open a PR and we will get to it as soon as practicable 😸