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

Just did a test:
- wrote a program that reads a primary file for update

- 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.