×
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 10-Feb-2015 13:21 -0600, Adam Driver wrote:
Would anyone have any examples of using RTVJRNE to retrieve specific
records from a journal? We have three records we need, the receivers
on production have been deleted but we have the entries in a remote
journal on a DR system.
The CL program does not have a direct ability to insert the retrieved
data, so using the Retrieve Journal Entry (RTVJRNE) as a front-end for
that purpose is probably a poor choice. Use of the command vs an API
also has many limitations that may not be able to be overcome if not
using the Retrieve Journal Entries (QjoRetrieveJournalEntries) API to
retrieve the entries; the Return Variable For The Journal Entry for
example is limited to a binary-character CL variable data type of the
maximum (¿9999?) length and no support for the data types that require
pointers to access the data.
If the journal entries are on the remote system, then the Display
Journal (DSPJRN) command supports an Output (OUTPUT) parameter
specification of *OUTFILE to request directing the entries to a named
Output File (OUTFILE) using a specified Output File Format (OUTFILFMT)
similar to the Entry Format (ENTFMT) specification of the RTVJRNE
command to define the layout of the Entry Data.
Once the data exists as rows in a file of the journal entry output,
that data can be copied\inserted into the target file. The /copy/ is
not direct and simple, minimally there are the extra columns but there
is also the issue with the null indicator and specifications of how to
expose those. There are some tools [talked about in the archives] that
can help to effect the copy more directly, but depending on the
[complexity of the layout of and the data itself in the] individual
scenario and if the request is a /one-off/ vs something that must be
done periodically, the specific steps to achieve the desired results
could probably be explained in scripted actions for a particular
setup\scenario.
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.