IBM Mainframe Forum

by **Noice** » Wed Feb 11, 2015 7:13 pm

Hello, I was wondering if someone can help me.... In my current process I use LFTP to transfer files between my Mainframe and Linux box but the transfer is very slow. I have been doing some testing with OCOPY and I have seen substantial performance gains which makes OCOPY a potential candidate to replace LFTP but I am having Code Page problems with the data. When I review the logic in the shell script for LFTP I see that the site command is set as follows:

Select all

site sbd=(IBM-037,ISO8859-1)

So basically LFTP is doing a conversion from EBCDIC IBM-037 to ASCII whereas OCOPY does a transfer and conversion from EBCDIC IBM-1047 to ASCII. From looking at the IBM manual for OCOPY I found that you can do a OCOPY code page conversion on the mainframe from EBCDIC IBM-037 to EBCDIC IBM-1047 but I haven't been able to get results that look any different than when I do EBCDIC IBM-1047 to ASCII conversion.

Below is my JCL:

Select all

//********************************************************
//SN333010 EXEC PGM=IKJEFT01,DYNAMNBR=30,COND=(0,LT)
//SYSTSPRT DD SYSOUT=X
//MVSIN DD DSN=S333.US.CUSTDT.DOMESTIC.PAYMNT.G739,DISP=SHR
//HFSOUT DD DSN=S333.US.CUSTDT.DOMESTIC.PAYMNT.G739S,
// DISP=(NEW,CATLG,DELETE),UNIT=SYSDA,
// SPACE=(CYL,(100,25),RLSE),
// DCB=(LRECL=1704,RECFM=VB)
//SYSTSIN DD DSN=N333.DVLP.CTC(OCOPY037),DISP=SHR
//*************************************************************
//SN333015 EXEC PGM=IKJEFT01,DYNAMNBR=30,COND=(0,LT)
//SYSTSPRT DD SYSOUT=X
//MVSIN DD DSN=S333.US.CUSTDT.DOMESTIC.PAYMNT.G739S,
// DISP=SHR
//HFSOUT DD PATHOPTS=(OWRONLY,OCREAT,OTRUNC),
// PATH='/APPS/333/SVR/n333/CDP739',
// PATHMODE=(SIRUSR,SIWUSR,SIRGRP,SIWGRP,SIROTH,SIWOTH),
// PATHDISP=(KEEP,KEEP)
//SYSTSIN DD DSN=N333.DVLP.CTC(OCOPY2LX),DISP=SHR

Control Cards:
OCOPY037

Select all

OCOPY INDD(MVSIN) OUTDD(HFSOUT) TEXT CONVERT((BPXFX111)) TO1047

OCOPY2LX

Select all

OCOPY INDD(MVSIN) OUTDD(HFSOUT) TEXT CONVERT((BPXFX311)) FROM1047

On the Linux side I have been able to do HEX replaces on the bad char but I would like to have everything handle properly by the OCOPY tool.

Did I set the JCL up wrong? Does anyone have any ideas?

Thank you

IBM Mainframe Forum

OCOPY Code Page Issue

OCOPY Code Page Issue