Branch-entry WTO is fine for limited output; however, you will find that the system doesn't tag such messages with a job ID (in my experience... idk if there's a way to make it do so).
For more serious output, you might consider writing a print subtask, and a queuing mechanism that SRBs and tasks can send their output to. That should either be a good exercise to develop multi-tasking skillz, or not that hard. sas On Mon, Oct 2, 2017 at 6:10 PM, Charles Mills <[email protected]> wrote: > Aha! Missed that. That should work. Thanks, > > Charles > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Mike LaMartina > Sent: Monday, October 2, 2017 2:58 PM > To: [email protected] > Subject: Re: How "print debug messages" from an SRB? > > How about WTO LINKAGE=BRANCH? > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Charles Mills > Sent: Monday, October 02, 2017 2:56 PM > To: [email protected] > Subject: How "print debug messages" from an SRB? > > Those of you who write code that runs on an SRB, what do you do in > development about debug messages? I assume there is no wonderful > customer-quality solution other than passing the results off to the "parent" > TCB process for it to log or display. But what do you do in debugging? You > call an MVS service and get a non-zero return code, probably because of > stupid, one-time programmer error. It's the sort of thing where you might > put out a quick WTO in TCB mode. But what do people do in SRB mode? > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN -- sas ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
