NO RESPONSE RECEIVED
When you issue an operator command from SDSF (/S proc or /D IPLINFO, for example) what determines whether SDSF displays NO RESPONSE RECEIVED in the upper right or displays the messages that result from the command's being issued? /S myproc, for example, results in WTO messages being issued within less than a tenth of second but SDSF says NO RESPONSE RECEIVED. From SDSF's point of view, what is a response? I've looked at QEDIT and CIB and I don't see a way to respond as opposed to just doing something. Thanks, Charles Mills -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: NO RESPONSE RECEIVED
On Wed, 8 Sep 2010 09:53:37 -0700, Charles Mills charl...@mcn.org wrote: When you issue an operator command from SDSF (/S proc or /D IPLINFO, for example) what determines whether SDSF displays NO RESPONSE RECEIVED in the upper right or displays the messages that result from the command's being issued? /S myproc, for example, results in WTO messages being issued within less than a tenth of second but SDSF says NO RESPONSE RECEIVED. From SDSF's point of view, what is a response? I've looked at QEDIT and CIB and I don't see a way to respond as opposed to just doing something. Thanks, Charles Mills Charles, try upping your response delay under Options/7. Set delay for responses... in SDSF. Although I am not sure if you will get a response on a start command. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: NO RESPONSE RECEIVED
It has to do with the way the WTO was issued by the command processor. Instead of issuing a simple WTO, the code that processes the command and generates the response should use MCSFLAG=RESP on the WTO. It could also have to do with a CART being used. If a CART is supplied with the command the WTO should also include CART= where matches the CART of the command. Chuck Arney illustro Systems International, LLC http://www.illustro.com Internet-enable your applications with z/Ware V2 Voice: 214-800-8900 X#5562 -- This e-mail is private and may be confidential and is for the intended recipient only. If misdirected, please notify us by telephone and confirm that it has been deleted from your system and any copies destroyed. If you are not the intended recipient you are strictly prohibited from using, printing, copying, distributing or disseminating this e-mail or any information contained in it. We use reasonable measures to virus scan all E-mails leaving illustro but no warranty is given that this E-mail and any attachments are virus free. You should ensure you have adequate measures in place for your own virus checking. -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Charles Mills Sent: Wednesday, September 08, 2010 11:54 AM To: IBM-MAIN@bama.ua.edu Subject: NO RESPONSE RECEIVED When you issue an operator command from SDSF (/S proc or /D IPLINFO, for example) what determines whether SDSF displays NO RESPONSE RECEIVED in the upper right or displays the messages that result from the command's being issued? /S myproc, for example, results in WTO messages being issued within less than a tenth of second but SDSF says NO RESPONSE RECEIVED. From SDSF's point of view, what is a response? I've looked at QEDIT and CIB and I don't see a way to respond as opposed to just doing something. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: NO RESPONSE RECEIVED
What SDSF is doing here is using the MGCRE service with the CART parameter (the CART is the command response token) to send the operator command to an EMCS console. The expectation in most cases is that the code that eventually executes in whatever ASID because of the operator command looks at the CIB and sees that there is a CART present and then uses the CART=CIBXCART specification on the WTOs that writes messages containing the operator command response. This allows the EMCS that SDSF has established to wake up and get the message(s). Not all software products use CARTs on their WTOs and there may be architectural reasons why some base z/OS components do not use CARTs either. To cater for this, SDSF must establish a timer so it can give up waiting - hence the setting in the SDSF options. Rob Scott Lead Developer Rocket Software 275 Grove Street * Newton, MA 02466-2272 * USA Tel: +1.617.614.2305 Email: rsc...@rs.com Web: www.rocketsoftware.com -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Charles Mills Sent: 08 September 2010 17:54 To: IBM-MAIN@bama.ua.edu Subject: NO RESPONSE RECEIVED When you issue an operator command from SDSF (/S proc or /D IPLINFO, for example) what determines whether SDSF displays NO RESPONSE RECEIVED in the upper right or displays the messages that result from the command's being issued? /S myproc, for example, results in WTO messages being issued within less than a tenth of second but SDSF says NO RESPONSE RECEIVED. From SDSF's point of view, what is a response? I've looked at QEDIT and CIB and I don't see a way to respond as opposed to just doing something. Thanks, Charles Mills -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: NO RESPONSE RECEIVED
Thanks, Patrick, but that does not seem to be it. I upped it from 1 to 2 seconds with no discernible effect. For my particular benchmark /S command, here are the timings 12:54:21.38 0290 S MYPROC 12:54:21.41 0090 IRR813I NO PROFILE WAS FOUND IN THE STARTED 507 0090 MYPROC WITH JOBNAME MYPROC. RACF 12:54:21.43 STC00383 0291 $HASP100 MYPROC ON STCINRDR 12:54:21.48 STC00383 0290 IEF695I START MYPROC WITH JOBNAME MYPROC , GROUP DFLTSTC 12:54:21.48 STC00383 0090 $HASP373 MYPROC STARTED 12:54:21.48 STC00383 0090 IEF403I MYPROC - STARTED - TIME=12.54.21 12:54:21.60 STC00383 0090 program issues WTO message So you can see there are a lot of responses within about a quarter of a second. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Patrick Lyon Sent: Wednesday, September 08, 2010 10:00 AM To: IBM-MAIN@bama.ua.edu Subject: Re: NO RESPONSE RECEIVED On Wed, 8 Sep 2010 09:53:37 -0700, Charles Mills charl...@mcn.org wrote: When you issue an operator command from SDSF (/S proc or /D IPLINFO, for example) what determines whether SDSF displays NO RESPONSE RECEIVED in the upper right or displays the messages that result from the command's being issued? /S myproc, for example, results in WTO messages being issued within less than a tenth of second but SDSF says NO RESPONSE RECEIVED. From SDSF's point of view, what is a response? I've looked at QEDIT and CIB and I don't see a way to respond as opposed to just doing something. Thanks, Charles Mills Charles, try upping your response delay under Options/7. Set delay for responses... in SDSF. Although I am not sure if you will get a response on a start command. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: NO RESPONSE RECEIVED
Thanks. Perfect. That's what I was looking for. I was sure I remembered something like this. Not all software products use CARTs on their WTOs Nope, but mine will. g Charles -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Rob Scott Sent: Wednesday, September 08, 2010 10:14 AM To: IBM-MAIN@bama.ua.edu Subject: Re: NO RESPONSE RECEIVED What SDSF is doing here is using the MGCRE service with the CART parameter (the CART is the command response token) to send the operator command to an EMCS console. The expectation in most cases is that the code that eventually executes in whatever ASID because of the operator command looks at the CIB and sees that there is a CART present and then uses the CART=CIBXCART specification on the WTOs that writes messages containing the operator command response. This allows the EMCS that SDSF has established to wake up and get the message(s). Not all software products use CARTs on their WTOs and there may be architectural reasons why some base z/OS components do not use CARTs either. To cater for this, SDSF must establish a timer so it can give up waiting - hence the setting in the SDSF options. Rob Scott Lead Developer Rocket Software 275 Grove Street * Newton, MA 02466-2272 * USA Tel: +1.617.614.2305 Email: rsc...@rs.com Web: www.rocketsoftware.com -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Charles Mills Sent: 08 September 2010 17:54 To: IBM-MAIN@bama.ua.edu Subject: NO RESPONSE RECEIVED When you issue an operator command from SDSF (/S proc or /D IPLINFO, for example) what determines whether SDSF displays NO RESPONSE RECEIVED in the upper right or displays the messages that result from the command's being issued? /S myproc, for example, results in WTO messages being issued within less than a tenth of second but SDSF says NO RESPONSE RECEIVED. From SDSF's point of view, what is a response? I've looked at QEDIT and CIB and I don't see a way to respond as opposed to just doing something. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: NO RESPONSE RECEIVED
In response to Charles, Rob Scott said: What SDSF is doing here is using the MGCRE service with the CART parameter (the CART is the command response token) to send the operator command to an EMCS console. The expectation in most cases is that the code that eventually executes in whatever ASID because of the operator command looks at the CIB and sees that there is a CART present and then uses the CART=CIBXCART specification on the WTOs that writes messages containing the operator command response. This allows the EMCS that SDSF has established to wake up and get the message(s). Not all software products use CARTs on their WTOs and there may be architectural reasons why some base z/OS components do not use CARTs either. To cater for this, SDSF must establish a timer so it can give up waiting - hence the setting in the SDSF options. 'es a bright lad is our Rob! Spot on. However, whether or not you see the NO RESPONSE message depends entirely on whether SDSF sees a response before that timeout occurs. So if the system is busy and/or your command takes a while to process, you may get this even when you're doing everything right with respect to the CART. BTDTGTS. As an aside, if you have more than one line of data to return in the command response you'll have to use the multi-line WTO option. Miraculously, it does work and SDSF faithfully horks up the entire multi-line response which makes it a lot easier to see which message parts belong with which responses. -- This email might be from the artist formerly known as CC (or not) You be the judge. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
