× 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 06:42, Flensburg, Carsten wrote:

The DMPJOB method worked nicely:

OBJ- QSYSRPYL CONTEXT- QSYS
TYPE- 19 SUBTYPE-D8
OBJECT TYPE- SPACE *SYSRPYL
NAME- QSYSRPYL TYPE- 19 SUBTYPE- D8
LIBRARY- QSYS TYPE- 04 SUBTYPE- 01


Thanks. That means DMPSYSOBJ QSYSRPYL QSYS 19 D8 dumps the object and DMPSYSOBJ QSYSRPYL QSYS TYPE(19) SUBTYPE(D8) SPACE(*) will dump the data in that space. FWiW the OBJTYPE(*SYSRPYL) specification is apparently not supported, else I would have originally suggested OBJ(*ALL) on a DMPSYSOBJ instead of using DMPJOB; I guess could have mentioned the symbolic type name.

Any API\feature that provides access to that data, e.g. WRKRPYLE, would resolve to that x/19D8 system-domain space object and set a space pointer from the system pointer to access the object's space. As a system domain object, only a system state program would be allowed to perform the latter instruction. That would remain the implementation until that *SYSRPYL object as implementation-object for the feature similarly remains [unchanged]. And not to imply there would be any value when able to access the object directly... but any caching of the data [e.g. in a final-form] could probably be based upon the modification timestamp materialized from the object [system pointer]; saved for comparison on future invocations of whatever code is presenting those entries. That would probably be relevant however, if someone were to implement their own API-like DSPRPYLE OUTPUT(*OUTFILE) capability, perhaps more preferable as a SQL UDTF, to enable avoiding the overhead of WRKRPYLE OUTPUT(*PRINT) to get the data without worries for direct access to the internal object.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.