cksum byte count different from OMVS and UNIX



Post anything related to mainframes (IBM & UNISYS) if not fit in any of the above categories

Re: cksum byte count different from OMVS and UNIX

Postby AnandAK » Thu May 03, 2012 10:58 am

Hi,
Can anyone please help me out here?
AnandAK
 
Posts: 6
Joined: Mon Mar 12, 2012 5:19 pm
Has thanked: 0 time
Been thanked: 0 time

Re: Re: cksum byte count different from OMVS and UNIX

 

Re: cksum byte count different from OMVS and UNIX

Postby bbonner » Thu May 03, 2012 9:28 pm

This is a blast from the past. I looked at your JCL and it looks essentially like what I have in place. When you FTP the file down to your other system are you making sure you have the transmission method set to binary? If you set the transmission to binary it should have the same cksum when computed, and can then be converted to ASCII or whatever format you want. That is what I remember setting up on the receiving systems ends, was a script that computed the cksum output and then converted the file.
bbonner
 
Posts: 5
Joined: Sat Dec 20, 2008 4:25 am
Has thanked: 0 time
Been thanked: 0 time

Re: cksum byte count different from OMVS and UNIX

Postby dick scherrer » Fri May 04, 2012 12:42 am

Hello,

FWIW - it has been many years since i or any client site have had "corruption" after a successful transmission. This includes thousands of PCs, hundreds of Unix and Windows servers, and many dozen mainframes. If the transmission fails, all bets are off. . .

I don't recall the last time i saw someone actually try to work with the checksum. Possibly it is not needed in this case.
Hope this helps,
d.sch.
User avatar
dick scherrer
Global moderator
 
Posts: 6304
Joined: Sat Jun 09, 2007 8:58 am
Has thanked: 3 times
Been thanked: 91 times

Re: cksum byte count different from OMVS and UNIX

Postby bbonner » Fri May 04, 2012 1:13 am

I would second what Dick said. The only reason the site I worked at wanted that comparison was for one particularly critical data transfer where the damage done by processing incorrect data was quite hard to fix. Unless there is some high cost from having the data be mangled I would say it is a very small concern.
bbonner
 
Posts: 5
Joined: Sat Dec 20, 2008 4:25 am
Has thanked: 0 time
Been thanked: 0 time

Re: cksum byte count different from OMVS and UNIX

Postby AnandAK » Fri May 04, 2012 12:24 pm

Thank you very much for your reply bbonner and Dick Scherrer. Here we have this requirement to fullfil one of our compliance requirements. Eventhough data corruption doesnt happen nowadays while file transfer, they wanted a proof for that :).

I have tried changing the file from EBCDIC to ASCII using iconv and it worked now. Please find the JCL below :

************************************************************************************************
//CKSUM011 JOB (XXXX,XXX,00000),'XXXXXXXX ',REGION=0K,
// MSGCLASS=X,
// CLASS=D,
// NOTIFY=&SYSUID
//*******************************************************
//* DELETE OUTPUT FILE IF IT EXISTS *
//*******************************************************
//STEP1 EXEC PGM=IEFBR14
//SYSPRINT DD SYSOUT=*
//LOOKHERE DD DSN=CHKSUM.OUT,
// DISP=(MOD,DELETE,DELETE),SPACE=(TRK,(1,1))
//*******************************************************
//* COPY FROM input TO file named i *
//*******************************************************
//IEBGENER EXEC PGM=IEBGENER,REGION=5M,TIME=100
//SYSPRINT DD SYSOUT=*
//SYSIN DD DUMMY
//SYSUT1 DD DSN=CHKSUM.INFILE,
// DISP=(OLD,KEEP,KEEP)
//SYSUT2 DD PATH='/tmp/i1',
// PATHOPTS=(OWRONLY,OCREAT),PATHDISP=(KEEP,DELETE),
// PATHMODE=(SIWUSR,SIXUSR,SIRUSR),
// FILEDATA=TEXT,LRECL=27994,RECFM=VB,BLKSIZE=27998
//*******************************************************
//* COPY FROM ebcdic to ascii *
//*******************************************************
//BPXBATCH EXEC PGM=BPXBATCH,
// PARM='SH iconv -f IBM-1047 -t ISO8859-1 /tmp/i1 > /tmp/i'
//SYSPRINT DD SYSOUT=*
//SYSIN DD DUMMY
//*******************************************************
//* RUN BPXBATCH TO CKSUM PASSED FILE *
//*******************************************************
//BPXBATCH EXEC PGM=BPXBATCH,
// PARM='SH cksum /tmp/i'
//STDOUT DD PATH='/tmp/cksmout.i',PATHOPTS=(OWRONLY,OCREAT),
// PATHDISP=(KEEP,DELETE),PATHMODE=(SIWUSR,SIXUSR,SIRUSR),
// FILEDATA=TEXT,LRECL=27994,RECFM=VB,BLKSIZE=27998
//*******************************************************
//* COPY FROM CKSMOUT.i TO output file *
//*******************************************************
//IEBGENER EXEC PGM=IEBGENER,REGION=5M,TIME=100
//SYSPRINT DD SYSOUT=*
//SYSIN DD DUMMY
//SYSUT1 DD PATH='/tmp/cksmout.i',PATHOPTS=(ORDONLY),
// PATHDISP=(DELETE,DELETE),
// FILEDATA=TEXT,LRECL=27994,RECFM=VB,BLKSIZE=27998
//SYSUT2 DD DSN=CHKSUM.OUT,DISP=(NEW,CATLG),
// DCB=(DSORG=PS,RECFM=U,LRECL=80),
// SPACE=(TRK,(1,1))
//*******************************************************
//* RUN BPXBATCH TO DELETE ALL .i FILES *
//*******************************************************
//BPXBATCH EXEC PGM=BPXBATCH,
// PARM='SH find /tmp/ -name "i" | xargs rm -f'
//STDOUT DD PATH='/tmp/std.out',PATHOPTS=(OWRONLY,OCREAT),
// PATHDISP=(DELETE,DELETE),PATHMODE=(SIWUSR,SIXUSR,SIRUSR)
//*******************************************************
//* RUN BPXBATCH TO DELETE ALL .i FILES *
//*******************************************************
//BPXBATCH EXEC PGM=BPXBATCH,
// PARM='SH find /tmp/ -name "*.i" | xargs rm -f'
//STDOUT DD PATH='/tmp/std.out',PATHOPTS=(OWRONLY,OCREAT),
// PATHDISP=(DELETE,DELETE),PATHMODE=(SIWUSR,SIXUSR,SIRUSR)
//*******************************************************
//* RUN BPXBATCH TO DELETE ALL .i1 FILES *
//*******************************************************
//BPXBATCH EXEC PGM=BPXBATCH,
// PARM='SH find /tmp/ -name "i1" | xargs rm -f'
//STDOUT DD PATH='/tmp/std.out',PATHOPTS=(OWRONLY,OCREAT),
// PATHDISP=(DELETE,DELETE),PATHMODE=(SIWUSR,SIXUSR,SIRUSR)
*****************************************************************************************************
AnandAK
 
Posts: 6
Joined: Mon Mar 12, 2012 5:19 pm
Has thanked: 0 time
Been thanked: 0 time

Re: cksum byte count different from OMVS and UNIX

Postby AnandAK » Fri May 04, 2012 12:31 pm

Hello bbonner,
to answer your questions, the upstream system transfers the file in Ascii mode, not binary. So I will ask them to send using Binary mode and test this once again. We are actually in the process of developing the data feeds set up . Here for testing purpose we had run the cksum command in unix , in future we will develop a script.

Thanks a lot for your reply.
AnandAK
 
Posts: 6
Joined: Mon Mar 12, 2012 5:19 pm
Has thanked: 0 time
Been thanked: 0 time

Previous

Return to All other Mainframe Topics

 


  • Related topics
    Replies
    Views
    Last post