>controller cannot allow writes to those tracks to happen until the commit of >Step A's data is complete. Step B's unexpected delay may even lead to the >job's failure, perhaps with a S522 or S222 abend.
Huh? I think this is a bit contrived, and slightly inaccurate. What happens if STEPA updates the same track/block more than once? This can happen in a Banking App (for example), if somebody does multiple bill payments (online), or there are multiple posts/debits to the same account in a batch job. STEPA is going to 522, because of itself? I don't think so! - Too busy driving to stop for gas! ---------------------------------------------------------------------- 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
