|
>I have situations where I may have a device failure >and the program is attempting to recover on it's own. >When it doesn't I will get a job that loops. While >pursuing the issue of why it won't recover I want to >be able to control the looping job - specifically I want >to end the job. > >I will know the name of the device in question, but not >necessarily the job name. Other than working with >locks (I'm concerned there may not be any..), what is >the easiest way to say I have device DSPMINE and want >to end whatever job is xxxxxx/YYYYYYYYYY/DSPMINE? You can get the complete job information from the program status data structure. In old fashioned RPG, the columns are: I* I SDS I *PROGRAM PGNAME I *STATUS STATUS I 244 253 TMNAME I 254 263 USRNAM I 264 2690JOBNBR Hope this helps... Buck Calabro Commsoft, Albany, NY +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to "MIDRANGE-L@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 +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.