(E), %Error and *PSSR for file operations

[Tony Carolla <carolla@xxxxxxxxx>]

I am writing a program that creates a memo record for a customer. It accepts 
a company ID, customer ID, and the memo text. It returns an indicator, and 
the indicator is *on if the memo got created, *off if it didn't for any 
reason, including a file error.

I created a *PSSR subroutine that closes all files (if open), and returns 
*off. I placed this subroutine as all of the file spec's INFSR subroutines, 
specified USROPN, etc.

During memo creation, there is a sequence number in the memo file, and it is 
a unique key situation, the key being the company ID, customer ID and 
sequence number. Because other processes can be writing to this file at the 
same time, I use a technique (with the help of this mailing list 8-) ) that 
does the following:

- SetGT using the company ID and customer ID
- ReadPE using the company ID and customer ID
- If %Equal is off, set the seq# to 1, else add 1 to the sequence number
- Write using the (E) extender

I have conditioned the entire loop using DOU NOT %ERROR. My question is 
this: If a unique key error happens on the WRITE, will the control jump to 
my *PSSR subroutine, in spite of the (E) extender, or will it continue the 
loop, turning on the %ERROR bif? 



-- 
"Enter any 11-digit prime number to continue..."
"In Hebrew SQL, how do you use right() and left()?..." - Random Thought