What is stopping you from using the reason code from the SRB? For example :
SRB RC=x’00000008’ SRB RSN=x’00000801’ Dataspace create failed SRB RSN=x’00000802’ ALESERV failed SRB RSN=X’00000803’ etc etc If you are after more diagnostic fields (eg the *actual* RC from an IBM service) then you could design a structure that could be passed as part of the SRB parms or maybe in the header block for any returned data. Another small point – do you really want to write “new“ code using dataspaces? There are lots of really good 64-bit alternatives these days. Rob From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Joseph Reichman Sent: Tuesday, August 4, 2020 12:40 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SRB routine return code EXTERNAL EMAIL Thats what I was trying to say if something went wrong from a z/os point of view SYNCOMPADDR would contain a return code SYNCRSNADDR would be the reason code As an example I am creating a dataspace in the target address space if that fails and I would like to let the invoker of the IEAMSCHED macro know of that there doesn’t seem to be a parm on the IEAMSCHED macro for that Scenario Thanks > On Aug 4, 2020, at 4:42 AM, Rob Scott > <rsc...@rocketsoftware.com<mailto:rsc...@rocketsoftware.com>> wrote: > > Joseph > > I am not sure what you are asking as your question seemed slightly garbled, > however the following might help : > > IEAMSCHD has a variety of return and reason code fields, including getting > feedback from the dispatch and the scheduling of the SRB. > > Considering the following : > > WA_DISPATCH_RC_ADDR contains the address of fullword WA_DISPATCH_RC > WA_SRB_RC_ADDR contains the address of fullword WA_SRB_RC > WA_SRB_RSN_ADDR contains the address of fullword WA_SRB_RSN > > Coding IEAMSCHD with the following keywords : > > SYNCHCOMPADDR=WA_DISPATCH_RC_ADDR, > SYNCHCODEADDR=WA_SRB_RC_ADDR, > SYNCHRSNADDR=WA_SRB_RSN_ADDR, > RETCODE=WA_SCHEDULE_RC, > > Assuming that the SRB completes normally (or it has abended and your FRR has > recovered successfully), the WA_SRB_RC and WA_SRB_RSN fields will contain the > contains of R15 and R0 on exit from your SRB routine (ie the return and > reason code). > > Any problems in the scheduling or dispatching of the SRB is indicated in the > values in WA_DISPATCH_RC and WA_SCHEDULE_RC and the contents of WA_SRB_RC and > WA_SRB_RSN will contain further diagnostic values as indicated in the > IEAMSCHD documentation. > > Rob Scott > Rocket Software > > > > > -----Original Message----- > From: IBM Mainframe Discussion List > <IBM-MAIN@LISTSERV.UA.EDU<mailto:IBM-MAIN@LISTSERV.UA.EDU>> On Behalf Of > Joseph Reichman > Sent: Tuesday, August 4, 2020 12:50 AM > To: IBM-MAIN@LISTSERV.UA.EDU<mailto:IBM-MAIN@LISTSERV.UA.EDU> > Subject: SRB routine return code > > EXTERNAL EMAIL > > > > > > Is there a way for the a SRB routine to communicate to the invoker a return > code SYNCHCOMPADDR has to do if the SRB completed normally > > > > thanks > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send email to > lists...@listserv.ua.edu<mailto:lists...@listserv.ua.edu> 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<https://my.rocketsoftware.com/RocketCommunity/RCEmailSupport> > Unsubscribe from Marketing Messages/Manage Your Subscription Preferences - > http://www.rocketsoftware.com/manage-your-email-preferences<http://www.rocketsoftware.com/manage-your-email-preferences> > Privacy Policy - > http://www.rocketsoftware.com/company/legal/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 lists...@listserv.ua.edu<mailto:lists...@listserv.ua.edu> with > the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu<mailto:lists...@listserv.ua.edu> with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
