×
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.
> Jim T wrote:
>> runqry *n QATMADRLST
>>
> rob wrote:
That doesn't seem to be it. I ran the ADDSMTPLE twice and there's
only one row in there with no data from the ADDSMTPLE that I can see.
That RUNQRY request defaults to *LIBL for the named file, and to the
*FIRST member. DSPFD QATMADRLST *MBRLIST will show if there are other
members [that have data]. Presumably that is the name of a physical
file.... so additionally, if the program opens a logical file that is
supposed to be defined over the named file, ensure that the LF member
that was used, is based-on that PF [member]. Prior improper restore
activity for database file.member(s) into QUSRSYS could have /broken/
the installation, such that I/O to the expected file is placing data
into the wrong member. Again, a trace is a good way to find [if] a
database member is used to access or update data; then by review of its
journal, to see any actual insert or update activity that transpired.
Regards, Chuck
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
