RE: Exit Point When Opening a Source Member with RDP ?

Or EDTF what ? :-)

Regards,
Richard Schoen
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site: http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT


-----Original Message-----

message: 8
date: Fri, 18 Jan 2013 08:16:46 -0500
from: rob@xxxxxxxxx
subject: RE: Exit Point When Opening a Source Member with RDP ?

or EDTF?


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: Richard Schoen <richard@xxxxxxxxxxxxxxx>
To: "'midrange-l@xxxxxxxxxxxx'" <midrange-l@xxxxxxxxxxxx>,
Date: 01/18/2013 08:12 AM
Subject: RE: Exit Point When Opening a Source Member with RDP ?
Sent by: midrange-l-bounces@xxxxxxxxxxxx



Answered my own question again :)

Was able to trap an SEU change request and also an RDP object lock
request.

Now this will work all the way back to V5R1 since we have a mix of
machines internally.

My goal was to be able to create a passive mechanism for the developer
which will detect source changes on the I and archive a copy before
editing whether using SEU or RDP.

Regards,
Richard Schoen
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business
Intelligence
Email: richard@xxxxxxxxxxxxxxx<mailto:richard@xxxxxxxxxxxxxxx>
Web Site: http://www.rjssoftware.com<http://www.rjssoftware.com/>
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT