Using the Compare program works fine with DASD, but results in a truncated message when specifying tape output.

Document ID : KB000006144
Last Modified Date : 14/02/2018
Show Technical Document Details
Issue:

The user runs a COMPARE with his SYSUT3 going to tape with RECFM=VB,LRECL=2048 and it seems to work (no truncation) with this method.

If RECFM=FB,LRECL=324 works ok with DASD but it is necessary that the SYSUT3 be VB and 2048 or larger for TAPE?

Resolution:

If one uses an OLDFILE and NEWFILE with RECFM=FB,LRECL=324 and an output TAPE file to contain the CHANGED & INSERTED records with RECFM=FB,BLKSIZE=0,LRECL=324 just like the client did, then the COMPARE job will end with RC=0004 and with message CAWA2109W.

The following is reported at the end of the job output: 

*** CAWA2100I DDNAME SYSUT1 opened for DSN=VANER02.FMMVS.OLDFILE 

File is NonVSAM LRECL=324,BLKSIZE=27864,RECFM=FB,Mode=PS 

*** CAWA2100I DDNAME SYSUT1N opened for DSN=VANER02.FMMVS.NEWFILE 

File is NonVSAM LRECL=324,BLKSIZE=27864,RECFM=FB,Mode=PS 

*** CAWA2100I DDNAME SYSUT3 opened for DSN=VANER02.FMMVS.RESFILE 

File is NonVSAM LRECL=0,BLKSIZE=0,RECFM=F,Mode=PS 

The problem is that the LRECL of the TAPE file is considered being 0 and by this you get the truncation message because the input record with size 324 doesn't fit into the output record with size 0.

 RO94242 created to resolve this problem.