RE: End Request not allowed (how does this work?) -- MIDRANGE-L

David,

Close, but I'll bet your thinking of the message that says the end
request was temporarily delayed. In Ravi's case, the end request was
simply not allowed. 

Ravi,

Your on the right track with the "request processing program" question.
Take another look at the program stack four your two jobs. The stack
when you call QCMD should have a request level on the left hand side,
the JDE stack won't. (Column will be there, but no numbers.) The ENDRQS
command (what sysrqs-2 calls) drops back to the last request processing
program (RPP). QCMD, may or may not be a RPP depending on how it is
called. When you see the QCMD screen on your display QCMD will be an RPP
and hence ENDRQS will work, but when used in a routing entry, QCMD will
not be a RPP. When you called QCMD from the JDE menu you started QCMD as
a RPP and thus ENDRQS worked.

Creating a RPP is very simple, all you have to do is send and receive a
*Request message (via CL or APIs) and your a RPP. The lack of an RPP is
a common method used in menus to disable sysrqs-2 so the user can't kill
a process half-way through. 

HTH,
-Walden

-----Original Message-----
From: Murphy, David [mailto:murphy_d@OSCAR.OSSC.STATE.OR.US]
Sent: Wednesday, July 22, 1998 2:57 PM
To: 'MIDRANGE-L@midrange.com'
Subject: RE: End Request not allowed (how does this work?)


The behavior you describe appears to occur (in my experience) when the
system is building an index for the query or sql. The only difference I
see between your two scenarios is that in the first one you let the
query run a bit, but in the second one it sounds as if you cancelled it
right after starting it. So perhaps it didn't have a chance to start
building an index (or maybe it used the one it had already built?).

-----Original Message-----
From:   owner-midrange-l@midrange.com  On Behalf Of Ravi
Sent:   Tuesday, July 21, 1998 9:46 AM
To:     MIDRANGE-L@midrange.com
Subject:        End Request not allowed (how does this work?)

Hello all,

Can someone explain how "end request works" in the following scenarios:

1)
I was in the JDE menu system which has a command line at the bottom and
got into ISQL by typing STRSQL. I ran a query which took a while to run,
so I got into the System Request menu and took option 2, to end previous
request. I got a message "End Request not allowed" (CPF7121).
The call stack entries were: 

 QCMD      
 J98INITA  
 J98INITV  
 P00MENU   
 J00CMDA   
 QCMDEXC   
 QSQIMAIN  
 QSQISE    
 QWSGET    
 QT3REQIO  
           
          
2)
In trying to ivestigate this further, from the menu system, I got into
the command entry screen by "call qcmd", got into ISQL by typing STRSQL,
ran the same query, got into the system request menu, took option 2
which worked and got out of ISQL. 
Call stack entries were:
 QCMD     
 J98INITA 
 J98INITV 
 P00MENU  
 J00CMDA  
 QCMDEXC  
 QCMD     
 QSQIMAIN 
 QSQISE   
 QWSGET   
 QT3REQIO 
          

How is that "end request" worked in the 2nd scenario and not the 1st? 
Would the menu system somehow control this? I am on V4R2M0 if that makes
a difference. How does one create a "request processing program" as
mentioned in the message description of CPF7121?

Thanks in advance.

Ravi
Systems group, Inc
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---