Try NEW on the SYSUT2. Then it should go down the copy DCB, etc. path. With OLD, it understandably tries to verify compatibility. OLD and an output NULLFILE isn't all that logical.
> -----Original Message----- > From: IBM Mainframe Assembler List [mailto:ASSEMBLER- > [email protected]] On Behalf Of Paul Gilmartin > Sent: Tuesday, June 03, 2014 2:31 PM > To: [email protected] > Subject: Re: ADRDSSU VTOC -- also IEBCOPY > > On 2014-06-03 15:03, Dougie Lawson wrote: > > You didn't tell us it was your output file that failed. You said it > > was the input that got the error. > > > No, I said merely that the JCL sample failed, but conceded that I had changed > SYSUT1 from tape (which I assumed you verified) to DASD. > > > So we've learned that the input can either be on tape or disk. > > > (Actually, I haven't yet verified with tape.) > > > ...The output > > can't be DSN=NULLFILE because IEBCOPY does too much checking that > you're > > not trying to pull the wool over its eyes. IEB120I SYSUT2 VALIDATION > > ERROR > > > Too much checking indeed. I did try changing your "SYSUT2 DSORG=PO" > to "DSORG=PS", suspecting that BPAM might conflict with NULLFILE. > Made no difference. > > > You could try UNIT=VIO or you'll have to read the VBS dataset with a > > user program and interpret what the bits and bytes mean. > > > I trust DISP=(,DELETE),UNIT=VIO (or SYSALLDA) would work (or at least fail > with a different message). I was just hoping to avoid the superfluous I/O. > (I > also know, by experience, that "SYSUT2 DD PATH=..." doesn't work.) > > -- gil
