On Fri, Apr 28, 2023 at 11:18:43AM -0500, Pierre Fichaud wrote: > I set DCBOFPPC before the OPEN. > DCB after open > 000224D8 00000000 00000000 01D00000 00F43026 002FE5A2 05025C70 > 00004000 00027E08 *........ }...4 . Vs * .. .. = * > 000224F8 02010580 50000000 00A44848 008C4064 1AE30E68 00CA99F8 > 0A018240 020903E8 * &....u . T . r8 b Y* > 00022518 30013030 00027E78 00000000 00000000 000000C8 00000000 > 00000000 80E37A58 * . = ...........H........ T: * > > DCBOFLGS is at X'30'. > At x'30', the value is x'1A'. The value of DCBOFPPC is X'08'. > This means that the bit is on.
Oh, I mistook the x'30' for the value of DCBOFLGS not the offset. OK, so DCBOPPC is set. So an alternate theory is that the unlike concatenation is working as designed in that EOV is doing the close/open but open isn't getting the new LRECL and BLKSIZE. An indication of this is that your DCB open exit is getting control. What does your source DCB look like? Does it include LRECL and/or BLKSIZE? Values coded for LRECL/BLKKSiZE in the DCB macro do NOT in general get changed by open, unspecified values get set from the JCL/JFCB or the DSCB (dataset attributes). ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
