Joe You may well be able to achieve what you want in problem state assuming that you do not use any of the authorized dynamic allocation text units.
I imagine that StopX37-like products from ISVs will, however, use non-problem state keys and services as they tend to have rules or policy statements that will be sensibly behind some sort of key0-7 requirement (maybe PC routine or SVC). Rob Scott Rocket Software ________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Joseph Reichman <[email protected]> Sent: 24 June 2026 4:06 AM To: [email protected] <[email protected]> Subject: Re: Automating fix for B37 from a recovery program EXTERNAL EMAIL I am hoping I am able to do this in problem state the x 37 software does it run completly in problem state Joe Reichman On Tue, Jun 23, 2026 at 10:58 PM Paul Feller < [email protected]> wrote: > Joe, the data in the dataset is not affected. The executing program does > not know that the X37 software stepped in to do the recovery process. If I > recall correctly with both of the different X37 software I worked with over > the years there are rules you can setup to try to handle things. > > Now these types of software do have limits. As an example they can't help > if there is not any DASD space to extend a dataset or you have reached the > limit for how many volumes a dataset can extend across. > > > Paul > > -----Original Message----- > From: IBM Mainframe Discussion List <[email protected]> On Behalf > Of Joseph Reichman > Sent: Tuesday, June 23, 2026 09:01 PM > To: [email protected] > Subject: Re: Automating fix for B37 from a recovery program > > So when get a x 37 type error what happens to the data that’s already > written to the file is it intact > > > Can you close the dataset reallocate and continue > > Doesn’t sound like it but I guess I can ask > > > > > Joe Reichman > > On Tue, Jun 23, 2026 at 9:57 PM Paul Feller < > [email protected]> wrote: > > > As Steve said that is what X37 type software does. The X37 software > > steps in to determine if it should try to help recover from a X37 > > error. Now if that type of software is not in the cards, then maybe > > looking at how datasets are allocated might be a way to help reduce X37 > errors. > > > > If SMS is in the picture, you could look at some type of general rule > > around volume count. The down side to that is it takes up room in the > > TIOT below the line. If you open/allocate lots of datasets you might > > run out of room in the TIOT. If you are pushing all TIOT stuff above > > the line then space may not be an issue. > > > > Keeping with SMS maybe look at dataset allocation stuff. It comes > > down to the size of the primary and secondary allocation. Maybe some > > datasets are better off with a large primary and small secondary. > > While other datasets might work better with a small primary and large > secondary. > > > > As far as I know SMS changes really only come into play during dataset > > allocation. Will not help with datasets already allocated. > > > > Paul > > > > -----Original Message----- > > From: IBM Mainframe Discussion List <[email protected]> On > > Behalf Of Steve Beaver > > Sent: Tuesday, June 23, 2026 07:45 PM > > To: [email protected] > > Subject: Re: Automating fix for B37 from a recovery program > > > > What you’re describing and wanting to do is exactly how the product > > stop X > > 37 works > > > > > > > > Sent from my iPhone > > > > No one said I could type with one thumb > > > > > On Jun 23, 2026, at 19:39, Joseph Reichman < > > [email protected]> wrote: > > > > > > I was able to verify what Kurtz Q told me earlier that SDWAGR02 > > > Points to the dcb in a recovery program > > > > > > That being said is it possible I guess via SVC 99 to fix I.e > > > reallocate a dataset from a recovery program > > > > > > Thanks > > > -------------------------------------------------------------------- > > > -- For IBM-MAIN subscribe / signoff / archive access instructions, > > > send email to [email protected] with the message: INFO > > > IBM-MAIN > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, send > > email to [email protected] with the message: INFO IBM-MAIN > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, send > > email to [email protected] with the message: INFO IBM-MAIN > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send email > to [email protected] with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ================================ Rocket Software, Inc. and subsidiaries ■ 77 Fourth Avenue, Waltham MA 02451 ■ Main Office Toll Free Number: +1 855.577.4323 Contact Customer Support: https://my.rocketsoftware.com/RocketCommunity/RCEmailSupport Unsubscribe from Marketing Messages/Manage Your Subscription Preferences - http://www.rocketsoftware.com/manage-your-email-preferences Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy ================================ This communication and any attachments may contain confidential information of Rocket Software, Inc. All unauthorized use, disclosure or distribution is prohibited. If you are not the intended recipient, please notify Rocket Software immediately and destroy all copies of this communication. Thank you. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
