Jack,

That does provide the information needed, however I was hoping to have a program that could loop through all the remote journals on the system without having to process a bunch of spool files. The API gets me there, I just need to construct the call in CL to it. Since most of my clients are still at V5R4 and are only now starting to move to V7 I'll have to be doing it at V5R4.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 11/21/2011 8:38 AM, Jack Kingsley wrote:
Might this work:
WRKJRNA JRN(XXXXXX) OUTPUT(*PRINT) DETAIL(*RMTJRN)

On Mon, Nov 21, 2011 at 9:29 AM, Jim Oberholtzer<midrangel@xxxxxxxxxx>wrote:

> Gary,
>
> Good thought but I don't need to ask the remote systems to send me
> anything, the local (main) system has all the information needed. The
> API Retrieve Journal Information will retrieve everything. Getting a
> list of the journal receivers is as easy as you suggest.
>
> Since my target audience for this function are administrators, most of
> whom have little or no experience in RPG of any flavor I was hoping to
> do the entire process in CL. (This is also partly due to my own
> extraordinarily rusty RPG skills) At this moment it looks doable. And
> before the chorus starts, yes, it would much faster and better to manage
> in RPG with subfiles and all, even better in COBOL but the concept of
> getting in done in CL is just appealing to me, so let's not have a
> discussion about the better place to do it.
>
> Now, does anyone have an example of calling the Remote Journal
> Information API in CL?
>
> Once I get the project done, I'll post to open source.
>
>
> Jim Oberholtzer
> Chief Technical Architect
> Agile Technology Architects
>
>
> On 11/18/2011 3:46 PM, Monnier, Gary wrote:
> > Jim,
> >
> >
> >
> > Can you can use a series of SBMRMTCMD/RUNRMTCMD commands to run
> > something like the following?
> >
> >
> >
> > CRTLIB LIB(MYTMPLIB)
> >
> > DSPOBJD OBJ(*ALL/*ALL) OBJTYPE(*JRN) OUTPUT(*OUTFILE)
> > OUTFILE(MYTMPLIB/JOURNALS)
> >
> > Run a command or call a program that utilizes the
> > Retrieve Journal Information (QjoRetrieveJournalInformation) API and
> > puts the info
> >
> > into a table (MYTMPLIB/RMTJRNINFO). You will probably have to have this
> > installed. SNTNETF of a save file might do the trick.
> >
> > SNDNETF FILE(MYTMPLIB/RMTJRNINFO) TOUSRID((SOMEID
> > SOMEADR))
> >
> > DLTLIB LIB(MYTMPLIB)
> >
> >
> >
> > So now you have a list of all the remote journals and their attributes
> > on the remote system.
> >
> >
> >
> > An idea anyway.
> >
> >
> >
> > Gary
> >
> >
> >
> >
> >
> > -----Original Message-----
> > From:midrange-l-bounces+gary.monnier=terex.com@xxxxxxxxxxxx
> > [mailto:midrange-l-bounces+gary.monnier=terex.com@xxxxxxxxxxxx] On
> > Behalf Of Jim Oberholtzer
> > Sent: Friday, November 18, 2011 12:20 PM
> > To: Midrange Systems Technical Discussion
> > Subject: List remote journals and the status
> >
> >
> >
> > Does any have a program (green screen) or know of a way to list all the
> > remote journals and their status on the remote system in one panel. I
> > know I can display each ones attributes and use the appropriate F key to
> >
> >
> > get there but I was hoping for a more time effective solution. Must be
> >
> >
> > V5R4 at this point.
> >
> > Thanks!
> >
> >
> >
> > --
> >
> > Jim Oberholtzer
> >
> > Chief Technical Architect
> >
> > Agile Technology Architects
> >
> >
> >
> > --
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email:MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit:http://lists.midrange.com/mailman/listinfo/midrange-l
> or email:MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> athttp://archive.midrange.com/midrange-l.
>
>
--

As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.