RE: Purge saved journal receivers

Charles,

You're dead right on both points. Carsten's work is exemplary and there are
several of us that occasionally feel ignored. Sometimes folks just don't
like the answer.

That particular utility is in my toolbox that goes onto nearly every machine
Agile helps to manage.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Charles Wilt
Sent: Wednesday, May 27, 2015 7:55 AM
To: Midrange Systems Technical Discussion
Subject: Re: Purge saved journal receivers

I don't find it hard either...

But why roll my own when there's an existing utility to do it for you?
http://iprodeveloper.com/rpg-programming/apis-example-manage-journal-receive
rs

Are my emails not being seen or what? I seem to be being ignored...

Charles


On Wed, May 27, 2015 at 8:48 AM, <rob@xxxxxxxxx> wrote:

I don't think it's that hard to list journal receivers, whether or not
they are detached, and whether the last save date/time was after they
were detached.
However, many other people think that it is. Many people have a tough
time overcoming the learning curve in how to:
- handle a user space
- use a list API
- handle the error code parameter
and all that genre. Stuff that once you do it the first time isn't
all that hard. Then again, you can probably reconfigure a system from
Lan Console to HMC in your sleep.

IBM coming up with a service for this would be a huge help for that crowd.

Combined with a QCMDEXC UDF and you could simply run something like

create table qtemp.DeletedReceivers as ( select ReceiverLib,
ReceiverName,
qcmdexc('dltjrnrcv' + %trim(ReceiverLib) + '/' + ReceiverName) from
List_Journal_Receivers(...) where detachedtimestamp <
LastSavedTimestamp
)

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: "Jim Oberholtzer" <midrangel@xxxxxxxxxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date: 05/27/2015 08:27 AM
Subject: RE: Purge saved journal receivers
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Yes that service would be nice but honestly It's not that hard to list
the receivers and build a delete program that check to see if the
receiver has been saved or not. With the new RUNSQL features you can
do the entire thing in a CLLE program.

Meanwhile, assuming the tooling is in the OS would that not be the
DB/2 group to provide that service? It occurs to me this is one of the
services Scott Forstie might be interested in providing.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
rob@xxxxxxxxx
Sent: Tuesday, May 26, 2015 1:38 PM
To: Midrange Systems Technical Discussion
Subject: RE: Purge saved journal receivers

Sue Baker, we sure could use that journal receiver service...


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600
Mail
to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 05/26/2015 02:22 PM
Subject: RE: Purge saved journal receivers
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



So the answer is there's not an easy solution. <sigh>

I can do it the hard way, but it'll have to go on the to-do list.


Thanks

--
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 at
http://archive.midrange.com/midrange-l.



--
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 at
http://archive.midrange.com/midrange-l.


--
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 at
http://archive.midrange.com/midrange-l.



--
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 at
http://archive.midrange.com/midrange-l.

--
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 at http://archive.midrange.com/midrange-l.