It is my understanding of CICS with VSAM LSR pools, that the buffer is "written" to DASD at task completion or at a EXEC CICS SYNCPOINT.
as far as HURBA, in VSE we used TCLOSE, and it looks like on ZOS the VERIFY MACRO does almost the same thing: https://www.ibm.com/docs/en/zos/2.1.0?topic=examples-verify-synchronize-end-data VERIFY RPL=address,ACTION=REFRESH Note this warning about it use: After verifying a data set, positioning must be established with a POINT macro for sequential processing or with a GET macro with RPL OPTCD=DIR. so for KSDS file, you will need to save current positioning for the VSAM Placeholder PLH, and after the VERIFY MACRO, issues a POINT RPL=address. in CICS when you do a EXEC STARTBR, CICS acquires a VSWA control block for your task, the first x4c bytes of the VSWA is the VSAM RPL used by CICS to make VSAM requests. this field in the VSWA, hold the address of your tasks PlaceHolder: VSWAPLHP I think if you do it the way below, you don't need to worry about positioning, or or creating a VSAM RPL: EXEC CICS STARTBR L R1,VSWA-address VERIFY RPL=address,ACTION=REFRESH EXEC CICS ENDBR ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
