James: On Thu, 20 December 2001, "James W. Kilgore" wrote: > I'm thinking that I would write an interactive "requester" that sits on a data > queue to lock the workstation, does the SBMJOB and each step feeds back it's > particular point in time back to the requester which displays the progress >bar. Sounds very reasonable. You could have a single *dtaq to handle everything or individual *dtaqs per menu option or other possibilities. Keyed *dtaqs could use the submitting job's job name as part of the key for a single or multiple *dtaqs. Another part of the key could be menu option number or similar identifier. You could create a single, generic, "Submitted job progress monitor" that could be used for this or any number of other functions and have any number of workstations running it at once. Not bad at all. One issue might be recreating the *dtaq(s) at a later date if size becomes an issue and you aren't at a release level that can help handle it for you; another would be clearing old entries after problems arose. Tom Liotta -- Tom Liotta The PowerTech Group, Inc. 19426 68th Avenue South Kent, WA 98032 Phone 253-872-7788 Fax 253-872-7904 http://www.400Security.com ___________________________________________________ The ALL NEW CS2000 from CompuServe Better! Faster! More Powerful! 250 FREE hours! Sign-on Now! http://www.compuserve.com/trycsrv/cs2000/webmail/
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.