Not all datasets are created equal. E.g. DCB and VSAM don't work together. E.g. IEBGENER doesn't support VSAM. I suspect that AMATERSE won't either. So the answer is these dataset types are not supported by AMATERSE which truly is WAD. UNIX or VSAM file support would be a new feature request (no fix required). The message displayed is incorrect so you could request a fix for that (it says unsupported device instead of unsupported dataset organization).
I've never read "USING DATA SETS" so I can't tell you whether it's correct. IBM support telling you that Unix files are not datasets sounds like an error on their part but who among has never made a mistake. Regardless, the correct answer to your problem will still result in WAD. . As for concatenating an MVS dataset before the UNIX file isn't as ironic as it seem's. This actually occurs more often than you think. The classic example is specifying a block size on the first dataset that is larger than it's block size. That is exactly what is happening with the UNIX file. UNIX files don't support an RECFM, LRECL or BLKSIZE so specifying them on the DD results in them being ignored. When the first DD specifies a dataset that supports RECFM, LRECL and BLKSIZE, AMATERSE now has information it needs. Secondary DD's are not scrutinized as much as the first dataset in a concatenation. Maybe GIMZIP (from SMP/E) or zip from the UNIX utilities page might help. Jon Perryman. >________________________________ > From: Paul Gilmartin <[email protected]> > > > >In other words, should I ask them whether the information in >"Using Data Sets" is correct? > >> Can you give us some context? Why is this important or even relavent? >> >AMATERSE. I, like many others, find it easier to FTP a >TERSEd archive to my desktop than to the z. And I have >a directory NFS mounted to both the desktop and the z. So: > >********************************* TOP OF DATA >*********************************************** >** AMA572I STARTING TERSE DECODE UNPACK 20:08:51 11/07/2013 **** >** AMA527I INPUT - DDNAME : SYSUT1 DSNAME: ...PATH=.SPECIFIED... >** AMA583E INPUT DEVICE TYPE IS UNSUPPORTED >** AMA573I TERSE COMPLETE DECODE UNPACK 20:08:51 11/07/2013 **** >** AMA504I RETURN CODE: 32 >******************************** BOTTOM OF DATA >********************************************* > >Ironically, this: > >//* ========================================================= >//* Temporary DS followed by UNIX file! >//* >//TESTB EXEC UNPACK >//SYSUT1 DD UNIT=SYSALLDA,SPACE=(1,00000),&ATTRS,DSORG=PS >// DD PATHOPTS=ORDONLY,PATH='&PATH',&ATTRS >//* >//* ========================================================= > >... succeeds: > >********************************* TOP OF DATA >*********************************************** >** AMA572I STARTING TERSE DECODE UNPACK 20:08:50 11/07/2013 **** >** AMA527I INPUT - DDNAME : SYSUT1 DSNAME: >SYS13311.T200847.RA000.TERSEHFS.R0165256 >** AMA528I OUTPUT - DDNAME : SYSUT2 DSNAME: >SYS13311.T200847.RA000.TERSEHFS.R0165255 >** AMA555I THE VALUES ARE: BLKSIZE= 3120 LRECL=80 PACKTYPE=SPACK >RECFM=FIXED >** AMA583I INPUT DATASET SIZE IN BYTES: 4096 OUTPUT DATASET SIZE IN BYTES: >15360 COMPRESSION RATIO: 26% >** AMA573I TERSE COMPLETE DECODE UNPACK 20:08:50 11/07/2013 **** >** AMA504I RETURN CODE: 0 >******************************** BOTTOM OF DATA >********************************************* > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
