|
While evaluating "Alliance" from Patrick Townsend & Assoc., I've hit a problem with the way their DSM session scroller ends. It appears this "Alliance" product uses the DSM session scroller. DSPJOB OPTION(*OPNF) shows its display file is QSYS/QSN132, in its own non-shared open data path. When their DSM session scroller ends, this QSYS/QSN132 display file closes okay; but, unfortunately, so does the other open data path to QSYS/QSN132 in my job. Ouch. My application (which has worked fine for ten years) uses this display file QSYS/QSN132 in a non-shared open data path. Thus, when "Alliance" ends and control returns to my application, my display file I/O crashes with MCH3402, "Tried to refer to all or part of an object that no longer exists." Is this is a bug in the DSM session scroller? Or, can someone suggest a way that they can tear down their DSM session scroller that won't close my own open data path to QSYS/QSN132?
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.
midrange.com
