The DCB attributes of the SYSUT2 data set seem to me to be very unusual. I do not believe I've ever encountered a printing device that would really accept 12879 byte records, though printer datasets using "Advanced Function Printing" input might want extremely long logical records since each logical record should be a page or a binary image of some sort. The use of an explicit BLKSIZE like this is not usually advised, though I regard the odds that IBM will ever introduce a disk device with a different track geometry than the 3390 as extremely low. Still, to cover this chance I'd specify DCB=(LRECL=12884,RECFM=VBM,DSORG=PS), which I believe will generate the same DCB attributes on a 3390 as the DCB in the JCL.
I have to admit when I read the initial post I, too, thought PDS was an error, but since it was explicitly mentioned I decided to take the post as it stood.
As dick scherrer mentioned, the use of DISP=(SHR,CATLG,CATLG) for the SYSUT1 DD statement appears to me to be strange. If the dataset is not actually cataloged, the JCL as shown won't work. so there is no dataset to catalog, unless the DD statement is overridden with a UNIT= and VOL=SER parameter. If this is done DISP=(SHR,CATLG,CATLG) should be in the override, not in the base JCL; the base JCL should specify DISP=(SHR,KEEP) or just DISP=SHR.
As has been mentioned before, there is no JCL parameter to explicitly prevent a dataset from being extended to a second volume, though UNIT=(SPROD,1) might work if UNIT=SPROD allocates only a disk device since modern disk devices cannot be unloaded.