Agreed on all points. That's what I was trying to say with "no wonderful customer-quality solution other than passing the results off to the "parent" TCB process for it to log or display. But ... stupid, one-time programmer error ... where you might put out a quick WTO."
On the job ID issue, IBM sez "If an SRB-mode or cross-memory mode caller issues WTO without the JOBID or JOBNAME parameter, the resulting message may not contain a job ID or job name" so that implies both the restriction and a possible solution. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Steve Smith Sent: Tuesday, October 3, 2017 7:17 AM To: [email protected] Subject: Re: How "print debug messages" from an SRB? 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. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
