On Wed, 29 Jun 2016 13:00:10 -0500, John McKown <[email protected]> wrote:
. . . >Now, with JES2 (or UNIX output), what happens? Well, it's more like a data >base. You still have two DCBs, but the actual write sends the data to JES2 >and tells it to place it in the SPOOL file. So JES2 is accepting and >interleaving the data for you. . . . I'm not so sure about the extent of that. A long time ago I had to sort out a problem in a multi-tasking utility, which could have several tasks, each with their own DCB, writing to the same DD, which was invariably allocated to JES2 SYSOUT (I don't recall trying pointing it to a DASD data set). One of the symptoms of the problems was that SDSF would very occasionally get ABEND0C4 when browsing the SYSOUT from this utility. Later, perhaps after some JES2 enhancement, I think there were very occasional ABEND02As. The solution was to wrap ENQ/DEQ around the writes to the DD in question. I have no idea whether Java would provide any serialization. It is also possible that something has changed in JES2 since I encountered this issue (although I see one of the listed reasons for ABEND02A is "HASP access method detected a serialization error for a spool data set.") ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
