I's like a COMMIT for CICS. When your program updates recoverable resources (files, recoverable temporary storage, IMS databases, DB2 databases and such), the updates aren't made permanent until your transaction either ends sucessfully, or does a SYNCPOINT. So if your program updates a few things and then gets an S0C7 abend, the changes all get backed out, leaving your resources in a consistent state. It's unusual to need to do a SYNCPOINT half way through a CICS transaction, but there are cases where it is appropriate. Think carefully before you decide to use it.