Using what language? And running under what operating system version/release?

Using RPG IV on current releases, you might code this way:

    monitor ;
       update MYFILE ;
    on-error 01221 ;
       callp  MyErrProc( 1 ) ;
    on-error *FILE ;
       callp  MyErrProc( 2 ) ;
    on-error *PROGRAM ;
       callp  MyErrProc( 3 ) ;
    on-error *ALL ;
       callp  MyErrProc( 4 ) ;
    endmon ;

That piece of code attempts to run an UPDATE against a file named MYFILE. It monitors for errors in the UPDATE and calls procedures for different possible error conditions. The error handling doesn’t have to be a CALLP — it can be EXSR, CALL or any series of statements that you want. I showed CALLP for each one with a different parm for different errors.

The first error tested is for file status code 1221, which is “UPDATE before prior READ”. You can have different ON-ERROR sections for any error status codes that you want to handle.

In order to show more details, I included the three ‘generic’ ON-ERROR conditions — *FILE, *PROGRAM and *ALL.

Any file status codes that are errors would be handled by the *FILE section. Any status codes that are errors but aren’t file status codes would be handled by the *PROGRAM section. The ON-ERROR *ALL section could be used if you didn’t have a *FILE and a *PROGRAM section.

But other languages and versions would do things differently. Even RPG IV has other ways of doing it.

Tom

When compiling a program:
CRTSQLRPG COMMIT(*HLP)

Commitment control . . . . . . . > *HLP

*CHG
*ALL
*CS
*NONE
*RR
*UR
*RS
*NC

Within the RPG program:
You can use the “SET” statement within the RPG SQL program:

Specify SET TRANSACTION Statement

Type choices, press Enter.

ISOLATION LEVEL . . . . . . . . 1=NO COMMIT (NC, NONE)
2=READ UNCOMMITTED (UR, CHG)
3=READ COMMITTED (CS)
4=REPEATABLE READ (RS, ALL)
5=SERIALIZABLE (RR)

WARNING: Journaling must be active.
Be aware of the processing overhead.
Be aware of other users if this is an active file.

Tom