I interpreted Gilmartin's explanation that AMATERSE was failing because it did not support LRECL and BLKSIZE from the DD statement. That his workaround was to add a DD before the UNIX file. It turns out that the message from AMATERSE was correct "Unsupported device type". It looks like AMATERSE uses the DEVTYPE macro which is not suitable for UNIX files.
Jon Perryman. >________________________________ > From: Shmuel Metz (Seymour J.) <shmuel+ibm-m...@patriot.net> > > >In <1383936555.77181.yahoomail...@web181006.mail.ne1.yahoo.com>, on >11/08/2013 > at 10:49 AM, Jon Perryman <jperr...@pacbell.net> said: > >>I admit I don't re-read JCL and I mostly use existing JCL. But that >>doesn't make my statement false. For LRECL, it clearly states "LRECL >>applies to data sets with the BPAM, BSAM, EXCP, QISAM, QSAM, and TCAM >>access methods, and with SMS, to VSAM data sets.". Just because UNIX >>files are implemented thru one of these, doesn't mean UNIX files are >>that access method. > >Then why does z/OS DFSMS Macro Instructions for Data Sets describe >considertationa for using BSAM and QSAM with Unix files? Why does z/OS >DFSMS Using Data Sets include this? > >1.1.2.9 Access to z/OS UNIX Files > > Programs can access the information in UNIX files through z/OS > UNIX System Services (z/OS UNIX) calls, such as open(pathname), > read(file descriptor), and write(file descriptor). Programs can > also access the information in UNIX files through the BSAM, > BPAM, QSAM, and VSAM access methods. When you use BSAM or QSAM, > a UNIX file is simulated as a single-volume sequential data > set. When you use VSAM, a UNIX file is simulated as an ESDS. > When you use BPAM, a UNIX directory and its files are simulated > as a partitioned data set directory and its members. > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
