|
On Thu, Apr 18, 2019 at 12:06 PM Robert Rogerson--
<rogersonra@xxxxxxxxx>
wrote:
Sam, I read your article but the problem I still see is identifyingLooking at the macro language, I *think* you might be able to do a
the job which is started for a particular session.
macro that runs at login and does:
- WRKJOB to get the info
- Screen scrape the info
- Print it to a Windows virtual printfile
- Parse it from there.
Alternatively, you maybe could write a startup program for that user
profile that:
- writes the job info to a spooled file
- prints the spoolfile to ifs text
- scp the ifs text to your windows box
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.