|
Seeing as I wouldn't hold my breath waiting for IBM to do anything with this, even if you submitted a proper request, I'd suggest another way. There are ways for one job to access another job's QTEMP library. This gets under the covers a bit and I'm not certain whether the technique uses supported APIs. But I have seen the MI guys talking about this. So, assuming you can get access to another job's QTEMP, you *should* be able to accomplish pretty much what you're asking for. Not as easy as a Systems-Request thingy, but more flexible, as you'd be able to use this in batch jobs as well. HTH, Dan --- Albert York wrote: > >The System/36 used to have an option on the system request menu > which was > >called something like 'Set latch flag'. All it did was turn on an > indicator > >that you could test in your program. Then your program could take > the > >appropriate action. I used it for ending long searches for example. > I would > >really like to see something like that on the AS/400. Right now the > only > >choice we have is to end the whole program, which is pretty heavy > handed. > > > >Here is what I suggest. > > > >1. In your program, create a data area in QTEMP with a name > like > >QSYSRQSOPT. It would be 51 bytes long. The first 50 bytes would > contain a > >description (i.e. 'End Search'). > >2. When the user presses System Request the description is > displayed as > >an option. > >3. If the option is taken then the last byte of the data area > is set to > >'1'. > >4. Your program could check the data area periodically. If the > flag is > >set then it is time to cancel what it is doing. > > > >It seems like this wouldn't be too difficult to implement. > > > >Albert York __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.