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 00000290 S MYPROC
12:54:21.41 00000090 IRR813I NO PROFILE WAS FOUND IN THE STARTED
507 00000090 MYPROC WITH JOBNAME MYPROC. RACF
12:54:21.43 STC00383 00000291 $HASP100 MYPROC ON STCINRDR
12:54:21.48 STC00383 00000290 IEF695I START MYPROC WITH JOBNAME MYPROC
, GROUP DFLTSTC
12:54:21.48 STC00383 00000090 $HASP373 MYPROC STARTED
12:54:21.48 STC00383 00000090 IEF403I MYPROC - STARTED - TIME=12.54.21
12:54:21.60 STC00383 00000090 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:[email protected]] On Behalf
Of Patrick Lyon
Sent: Wednesday, September 08, 2010 10:00 AM
To: [email protected]
Subject: Re: NO RESPONSE RECEIVED
On Wed, 8 Sep 2010 09:53:37 -0700, Charles Mills <[email protected]>
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 [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html