Is there a fundamental reason why are you using a hiperspace? If you are trying to selectively copy SMF data from IEFU8x into somewhere that can be accessed/post-processed by another task/ASID, then using a common dataspace would be much easier and you could manage the serialization with CDS.
As mentioned before, you could also consider PC-ss into another server ASID and write the data directly to private storage. Rob Scott Lead Developer Rocket Software 275 Grove Street * Newton, MA 02466-2272 * USA Tel: +1.617.614.2305 Email: [email protected] Web: www.rocketsoftware.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Donald Likens Sent: 11 August 2011 02:45 To: [email protected] Subject: Shared Hiperspace write serialization I have looked in the manuals so if the answer is there, I could not find it. I am looking to write to a hiperspace from the IEFU8x exits. I do not see anything to stop this but I am concerned about writing to a shared hiperspace from multiple addree spaces. Do I need to be concerned? If in a middle of a write operation an interrupt occurs and then from another address space issues a write to the hiperspace, what happens? Another thing I did not see in the manual. I assume an SREAD will retrieve the data in the order it was written. True? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
