×
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.
Actually, the RPG programs that this CL calls, though
designed to run in an interactive job, are essentially
non-interactive in nature, riding The Cycle through
various files to sweep them of orphaned records, and using
DSPLY statements to indicate when they are deleting an
orphaned record. There is no display file I/O involved.
Using DSPLY has the advantage that whatever I DSPLY gets
copied into the joblog, which is potentially useful here
(it sure was for development and debugging).
What I finally did was to move the "stage marker" messages
(announcing the various RPG program calls) from the CL
program into *INZSR routines in the RPG programs
themselves (in most of them, that's ALL that *INZSR
does!).
9 Cycle programs, all controlled by Primary Files, some of
them opening externally described files as
program-described, in order to avoid level-checks, one of
them called 25 times (with overrides in the CL) and using
the Open Feedback to determine the actual name and key
length, and NONE of them use O-specs or display files.
Interesting week.
--
JHHL
As an Amazon Associate we earn from qualifying purchases.
This thread ...
RE: SNDPGMMSG to behave exactly like RPG DSPLY?, (continued)
This mailing list archive is Copyright 1997-2025 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
