On Mon, 30 Aug 2010 08:10:54 -0500, Fran Hernandez wrote:
>
>
>/ / EXEC PGM = TRSMAIN STEP0010, PARM = UNPACK
>/ / SYSPRINT DD SYSOUT =*, RECFM = FBA, LRECL = 133
>/ / INFILE DD DSN = NOSMS.FILE.PDS, DISP = SHR
>/ / OUTFILE DD DSN = FILE.PDS.CPU2, DISP = (NEW, CATLG, DELETE)
>/ / UNIT = SYSDA, SPACE = (CYL, (10,10), RLSE)
>/ / *
>
>The result is the following:
>
>**** STARTING TERS 8/30/10 14:45:55 DECODE UNPACK 4.14 ****
>FOR INPUT - DDNAME: INFILE DSNAME: NOSMS.FILE.PDS
>** ERROR: THIS IS NOT A TERS Recognize DATASET.
>FINISHED **** TERS 8/30/10 14:45:55 DECODE UNPACK 4.14 ****
>RETURN CODE: 8
>
Where did all the blanks come from? If the same process corrupts
your TERSEd file, you have no end of problems.
(The newer form of TRSMAIN is AMATERSE. At least you can get
IBM support for it.)
For verification, I suggest that you try on both the originating
and receiving systems:
cp -B data.set.name /dev/fd/1 | cksum
and verify that the checksum and byte counts are identical. I don't
know any compatible checksum facility readily available on Windows.
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
