Re: Question about accessing internal object *PTCSPC programmatically from my job -- MI400

Subject: Re: Question about accessing internal object *PTCSPC programmatically from my job
From: Jon Paris <jon.paris@xxxxxxxxxxxxxx>
Date: Tue, 11 May 2010 14:06:35 -0400
List-archive: <http://archive.midrange.com/mi400>
List-help: <mailto:mi400-request@midrange.com?subject=help>
List-id: MI Programming on the AS400 / iSeries <mi400.midrange.com>
List-post: <mailto:mi400@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/mi400>, <mailto:mi400-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/mi400>, <mailto:mi400-request@midrange.com?subject=unsubscribe>

On May 11, 2010, at 1:00 PM, mi400-request@xxxxxxxxxxxx wrote:

Information about the last display file is easy. See the QWSRTVOI
(Retrieve Output Operation) API.

But even easier surely would be to have the INFDS passed as a parm to the called program. This idea was fresh in my mond becuase I've just been doing it with some SPECIAL files.

Jon Paris

www.Partner400.com
www.SystemiDeveloper.com

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.