RE: Checking for a record Lock on an Update Primary.

With the ENDSR of the exception subroutine you can specify where the 
program should continue (or cancel). One of the options is *GETIN: 
'Continue at the get input record routine'. I suspect that that might get 
you the next record. To be sure: study the detailed cycle in the manual 
and/or experiment.

Joep Beckeringh






"Bruce Collins" <bruce.collins@xxxxxxxxxxxxx>
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
24-05-2006 17:27
Please respond to RPG programming on the AS400 / iSeries
 
        To:     "RPG programming on the AS400 / iSeries" 
<rpg400-l@xxxxxxxxxxxx>
        cc: 
        Fax to: 
        Subject:        RE: Checking for a record Lock on an Update 
Primary.


When you encounter that then how can you tell it to bypass that record
and try and get the next one?

Bruce "Hoss" Collins
IBM Certified Specialist - eServer i5 iSeries System Administrator V5R3
Cisco Certified Network Associate
AAA Cooper Transportation
Dothan, AL 36303
(334)793-2284 x2434

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx

[mailto:rpg400-l-bounces@xxxxxxxxxxxx]

On Behalf Of Joep Beckeringh
Sent: Wednesday, May 24, 2006 9:21 AM
To: RPG programming on the AS400 / iSeries
Subject: Re: Checking for a record Lock on an Update Primary.

Just did a test:
- wrote a program that reads a primary file for update
- coded an INFSR for the primary file (just sends an escape message

and

thus ends the program)
- run the program in debug in one session, made it break with a record
locked
- run the program in another session

Sure enough the program sent the escape message. The INFSR got

control.

Joep Beckeringh



Bruce Collins wrote:
 > Yes sorry. INFSR is what I used.
 >
 > Bruce "Hoss" Collins
 > IBM Certified Specialist - eServer i5 iSeries System Administrator

V5R3

 > Cisco Certified Network Associate
 > AAA Cooper Transportation
 > Dothan, AL 36303
 > (334)793-2284 x2434
 >
 >> -----Original Message-----
 >> From: rpg400-l-bounces@xxxxxxxxxxxx
 > [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
 >> On Behalf Of Joep Beckeringh
 >> Sent: Wednesday, May 24, 2006 3:27 AM
 >> To: RPG programming on the AS400 / iSeries
 >> Subject: Re: Checking for a record Lock on an Update Primary.
 >>
 >> Bruce,
 >>
 >> You say you've tried an INFDS, but that should have been INFSR. Is
 > that
 >> a typo?
 >>
 >> Joep Beckeringh
 >>
 >>
 >> Bruce Collins wrote:
 >>> I have looked through the archives but I have not found exactly

what

 > I
 >>> need. (I hate RPGII). We have a very very very very old RPG

program

 > that
 >>> has had the CVTRPGSRC run on it so it is a type RPGLE but the
 > contents
 >>> are still RPGII. I am needing to trap when the Primary file
 > encounters a
 >>> record lock. I have tried a INFDS but it does not trap it. I have
 >>> attempted a *PSSR but I think I have it wrong. Does some have an
 >>> example, preferably in free of how to trap a record lock on a

file

 >>> described as Update Primary.
 >>>
 >>> Thanks in Advance.



--
This is the RPG programming on the AS400 / 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.

 
<http://446360.sigclick.mailinfo.com/sigclick/04050102/06044D03/004D0510
171041.jpg>