Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expand validation on different allocation parameters that depend on LRECL #227

Open
KUGDev opened this issue Jan 31, 2025 · 0 comments
Open
Labels
priority-low Will be resolved when no other critical things ongoing

Comments

@KUGDev
Copy link
Contributor

KUGDev commented Jan 31, 2025

https://www.ibm.com/docs/en/zos/2.4.0?topic=options-record-length-lrecl

  1. For fixed-length unblocked records, LRECL must equal BLKSIZE:
    "blockSize": 80,
    "logicalRecordLength": 80,
    "recordFormat": "F",
    "dataSetOrganization": "PS"
    (то есть lrecl == blksize)
  2. For PDSEs or compressed-format data sets with fixed-length blocked records, LRECL must be specified when the data set is opened for output - not sure, need to check with experienced z/OS programmers to see what exactly this means
  3. For the extended logical record interface (XLRI) for ISO/ANSI variable spanned records, LRECL must be specified as LRECL=0K or LRECL=nK:
    "blockSize": 32760, - 32760 bytes (maximum size for block records in VBS format).
    "logicalRecordLength": 0,
    "recordFormat": "VBS",
    "dataSetOrganization": "PS"
    OR
    "blockSize": 32760,
    "logicalRecordLength": 4096, == 4K
    "recordFormat": "VBS",
    "dataSetOrganization": "PS"

It is worth considering the option of adding presets for these types of datasets.

@KUGDev KUGDev added the priority-low Will be resolved when no other critical things ongoing label Jan 31, 2025
@KUGDev KUGDev moved this from New to Backlog in Zowe IntelliJ Squad Feb 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority-low Will be resolved when no other critical things ongoing
Projects
Status: Backlog
Development

No branches or pull requests

1 participant