On Feb 21, 2012, at 12:07, Edward Jaffe wrote: > .... > I believe this change will instruct the assembler to fall back to its own > internal OPEN and READ processing for SYSIN (or whatever DD you're using) > which, > as you know, contains support for z/OS UNIX files. > Why is a RDJFCB required at all? I'm primarily not an assembler programmer, but I've coded a few OPENs successfully, but never a RDJFCB. I would suggest that if RDJFCB fails, let FLOWASM, not assembler, proceed with its OPEN and I/O processing.
In my understanding, the statement that "the assembler ... contains support for z/OS UNIX files" is misleading. The bulk of such support lies in the access method. IIRC, even before HLASM announced support for z/OS UNIX files, I was able to ALLOCATE SYSIN to a UNIX file and assemble it successfully. I had such a discussion a while back on IBM-MAIN where one contributor rebutted, asserting that using information in the JCFB, DSCB, UCB, etc. he was able to significantly optimize performance. If so, fine, but if the fancy stuff fails, he should fall back to good old OPEN, GET/PUT, CLOSE which will provide satisfatory operation for a greater number of users. But certainly I appreciate your generosity with the tools that you author. -- gil
