Joseph, I am sure that I have advised this more than once in the past, but I will repeat myself in case you missed it.
You are working in a development environment without access to a premium debugging product like z/XDC and you seem to spend quite a lot of time guessing about what your programs are doing. I strongly suggest you "stick a pin" on where you are now with your current project and spend a month or so writing yourself a generic internal trace facility. Something that can record : (o) Registers and current PSW (o) CSECT name and offset within it (o) A sequence of trace payloads so that you can print/dump out areas of memory Write the trace data to an internal memory buffer and then author something that can expose the contents in STCK order. This could be one or more of : (o) IPCS REXX exec (o) Some form of trace print dataset (or SYSOUT) allocated to a special DD name Rob Scott Rocket Software ________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Tony Harminc <[email protected]> Sent: Wednesday, February 25, 2026 11:59 PM To: [email protected] <[email protected]> Subject: Re: Debugging multitasking applications EXTERNAL EMAIL On Wed, 25 Feb 2026 at 13:13, Joseph Reichman < [email protected]> wrote: > I am in hard loop waitting for the task to do a wait on a TCB so I keep on > looping looking for the X’80’ > I wouldn't call it a hard loop if there is an STIMER wait-a-bit in it. > What I am trying to do is make sure the subtask gets to certain point of > sitting for work > Why do you want to loop for this? Do you have something else to do while you loop? If not, just wait for your subtask to post its "I'm ready" ECB (you passed in the address in the parameter list, right?), rather than waiting for the subtask to wait. If you are concerned about the subtask failing before it posts its "I'm ready" ECB, then WAIT on the first of the "I'm ready" ECB and the ECB you specified with ECB= on the ATTACH[X]. So the code in the main task is somewhat > Checktask > TM 0(R10),x’80’ > BO. Next task > Stimer wait a bit > B checktask > Bexttask > > While waitting I due issue the stimer a few times > All of sudden I get a abend with r14 pointing to SVC 3 > What abend? Are we to guess? How can that be > A program that receives control via LINK or ATTACH will have R14 pointing to the SVC 3 in the CVT. (Under TSO TEST R14 will generally point to an SVC 97.) I think it has something to do with debugging multitasking programs > Well if you are issuing ATTACH (you've only told us about one of them so far), then it's certainly possible. Are you starting your program under TEST, or did you bring TEST into the picture only after encountering your whatever-it-is Abend? As always, more info is needed. Tony H. ---------------------------------------------------------------------- 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
