|
Assuming you can somehow avoid the MCH6801 that will result from
trying to use a pointer to a system domain object to examine the
internals of an IBM-defined object, this approach seems far more
likely to be subject to change from release to release than relying
on the layout of spool file records, e.g. using the output of the
WRKRPYLE *PRINT command. :-o
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.