Repository navigation
Add guarded RCB availability and selected-RCB SCL export - #32
Merged
Merged
Conversation
masarray
marked this pull request as ready for review
July 19, 2026 14:03
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds engine-owned, read-only RCB availability inspection and object-model selected-RCB SCL export for legacy SAS workflows.
RCB availability
DatSet,RptID,ConfRev,RptEna,Resv/ResvTmsand best-effortOwnerwithout writing or reserving an RCB;Available,InUse,UsedByCaller,Unknown, missing DataSet, empty DataSet, and unreadable DataSet;SCL selected-RCB export
RptEnabled maxto one instance and can rename the exported block to the exact runtime RCB name;Legacy SAS CID exporter
Validation
Safety boundary
The availability workflow is read-only. It does not write
RptEna,Resv,ResvTms,Owner, orDatSet, and it does not claim conformance or universal vendor interoperability.