× 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.



Hi Chuck,

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

Cheers,
Carsten


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: 29. november 2012 21:13
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Reply list entry handling?

On 29 Nov 2012 13:03, Vernon Hamberg wrote:

I've not looked so I hope you know - is there an option in MATMATR
MI function (or some other MI function) that can be used? This one
is usable from high-level languages.

I doubt that MI instruction would produce that kind of information;
i.e. OS Message Handler component information.

Most likely I expect, although I can not verify [no access to a
system], there is an internal object type with system-domain that
implements a "System Reply List" object; probably a space object, major
type x'19', and something I have oft implied if exists should be
extended to become a "User Reply List" object. So anyhow, I doubt
anything other than a resolve system pointer and set space pointer from
system pointer would gain access the list\entries details; thus,
justifying a need for an API to avoid mucking with /spooled/ results.
Some creative use of DMPSYSOBJ [using QMH* naming?], or review for such
an object in a DMPJOB [to include object references] issued after
issuing WRKRPYLE would help to locate the object.
This communication is intended only for use by the addressee.It may contain confidential or privilegedinformation.
If you receive this communication unintentionally, please inform us immediately and delete this e-mail and any attachments.
Warning: Although we have taken reasonable precautions to ensure no viruses are present in this email, we cannot accept
responsibility for any loss or damage arising from the use of this email orattachments.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.