Re: Possible Automated Troubleshooting on RECORD LOCK

Any chance you have access to Jim Sloan's TAATOOL stuff?
In the free version years ago he had CLP that could be used
called TAADBFFC. You would do your RPG chain and on error
call that program and it would push up the user with options to
retry etc.
Just a thought. I don't know if TAATOOLS is still available for
free anymore.







From: dlclark@xxxxxxxxxxxxxxxx
To: "RPG programming on the IBM i \(AS/400 and iSeries\)"
<rpg400-l@xxxxxxxxxxxx>
Date: 04/01/2016 11:57 AM
Subject: Re: Possible Automated Troubleshooting on RECORD LOCK
Sent by: "RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxx>



"RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxx> wrote on 04/01/2016 12:32:26
PM:

Secondly this lock manifests by a field that holds the user id, in order

to

clear, our program, reads and clears that field, but in recent case I

noted

that when I tried to manually clear that field, i see this message in my
dspjoblog on my pc:

Record 5858274 in use by job 427038/NINAM/XT09DD0B10.

So my question is, can the RPG be able to discern the above message?

Yes, the following is a rough example of something like what you
want to do:

MONITOR; // trap file errors
CHAIN MYKEY MYFILE
ON-ERROR 01218; // already locked
// PSDS fields EXCP_MSGID and EXCP_DATA identify specific error and job
user
ON-ERROR *ALL; // all other errors
// some processing
ENDMON;


Sincerely,

Dave Clark
int.ext: 91078
direct: (937) 531-6378
home: (937) 751-3300

Winsupply Group Services
3110 Kettering Boulevard
Dayton, Ohio 45439 USA
(937) 294-5331

--
This is the RPG programming on the IBM i (AS/400 and iSeries)
(RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related

questions.


*********************************************************************************************
This email message and any attachments is for use only by the named
addressee(s) and may contain confidential, privileged and/or proprietary
information. If you have received this message in error, please
immediately notify the sender and delete and destroy the message and all
copies. All unauthorized direct or indirect use or disclosure of this
message is strictly prohibited. No right to confidentiality or privilege
is waived or lost by any error in transmission.
*********************************************************************************************