Skip to content

Conversation

@varunchennamadhava
Copy link
Collaborator

💡 Issue Reference

Issue: Include any issues related to this PR

💻 What does this address?

Details of the issue...why is this necessary?

📟 Implementation Details

How was this feature/issue implemented?

📋 Is there a test case?

Include the details of the tests that were done

Signed-off-by: varunchennamadhava <varunchennamadhava@gmail.com>
Signed-off-by: varunchennamadhava <varunchennamadhava@gmail.com>
Signed-off-by: varunchennamadhava <varunchennamadhava@gmail.com>
Signed-off-by: varunchennamadhava <varunchennamadhava@gmail.com>
Signed-off-by: varunchennamadhava <varunchennamadhava@gmail.com>
Signed-off-by: varunchennamadhava <varunchennamadhava@gmail.com>
Signed-off-by: varunchennamadhava <varunchennamadhava@gmail.com>
@lcarcaramo
Copy link
Member

lcarcaramo commented Feb 3, 2026

Since the ASXB control block is in subpool 255, it is private storage that CBXP cannot correctly access as a problem state program, meaning that we cannot extract ASXB control blocks from live storage. CBXP can only extract control blocks that reside in common storage.

@lcarcaramo lcarcaramo closed this Feb 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants