×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On 30 Nov 2012 09:13, Mark S Waterbury wrote:
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
Actually the output via the printer file changes on every release,
but the *SYSRPYL implementation object likely remains unchanged over
many releases. I would not be surprised if the object layout has been
unchanged since the S/38. Of course the changes to the spooled data is
likely to be only the information that which matches the service OIR,
i.e. feature identifiers, and V#R#M# values, plus the GA date of the
release. When not spooling directly to a database file, the biggest
differences are across languages and SBCS vs DBCS specifications of the
PRTF; the latter detail I recall may affect layout in a database file,
but I do not recall if only when using CPYSPLF or if also for directing
output to a database file.
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
