• Subject: End Request not allowed (how does this work?)
  • From: Ravi <ravi@xxxxxxxxxxxxx>
  • Date: Tue, 21 Jul 1998 11:46:23 -0500

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 thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].