IBM Mainframe Forum

Posted: **Mon Sep 14, 2009 11:46 pm**

In my JCL there are multiple IEBCOPY step, will there be any performance improvement if i combine all the IEBCOPY into one step with multiple COPY control statement in the sysin :?:

. Will there be any adverse effect in doing so :!:

.

Posted: **Tue Sep 15, 2009 1:10 am**

Hello,

Without seeing what is currently being done, i can't even make a guess. . .

Why are there multiple steps now?

Any adverse effects would more likely be logistics rather than performance. Are there different condition code tests for any of the current steps?

Posted: **Tue Sep 15, 2009 11:10 pm**

Hi,
The job is for copying components to a test region and created by a tool. The steps are to copy SOURCE, Batch Load, Online load etc separately using different IEBCOPY some time the no of component are large and take a lot of time so we were thinking to optimize the job

Select all

//COPYSRC EXEC PGM=IEBCOPY
//STGSRC DD DSN=x.srclib
//TSTSRC DD DSN=y.srclib
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
COPY INDD=((STGSRC,R)),OUTDD=TSTSRC
/*
//COPYBAT EXEC PGM=IEBCOPY
//STGBAT DD DSN=x.batch.load
//TSTBAT DD DSN=y.batch.load
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
COPY INDD=((STGBAT,R)),OUTDD=TSTBAT
/*
//COPYONL EXEC PGM=IEBCOPY
//STGONL DD DSN=x.online.load
//TSTONL DD DSN=y.online.load
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
COPY INDD=((STGONL,R)),OUTDD=TSTONL
/*

If we have only one IEBCOPY to copy all the type of components will it be more efficient? If yes how much more efficient?

Select all

//COPYSRC EXEC PGM=IEBCOPY
//STGSRC DD DSN=x.srclib
//TSTSRC DD DSN=y.srclib
//STGBAT DD DSN=x.batch.load
//TSTBAT DD DSN=y.batch.load
//STGONL DD DSN=x.online.load
//TSTONL DD DSN=y.online.load
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
COPY INDD=((STGSRC,R)),OUTDD=TSTSRC
COPY INDD=((STGBAT,R)),OUTDD=TSTBAT
COPY INDD=((STGONL,R)),OUTDD=TSTONL
/*

Posted: **Wed Sep 16, 2009 12:24 am**

Hello,

If yes how much more efficient?

Probably not enough to measure. . . .

There is no difference in the amount of work to do and no "extra" dataset allocations due to the multiple steps. The only difference would be the 2 step initiations/terminations that would be eliminated.

Posted: **Sat Sep 19, 2009 6:52 pm**

Hi dick,

Thanks for the responding.
We didn't made changes to the JCL, as in out testing we only found very small gain in EXCP count, no gain in CPU time and elapse time.

Regards,
Rajith

Posted: **Mon Sep 21, 2009 2:35 am**

You're welcome - thanks for posting your results

d

IBM Mainframe Forum

Combining Multiple IEBCOPY step into one

Combining Multiple IEBCOPY step into one

Re: Combining Multiple IEBCOPY step into one

Re: Combining Multiple IEBCOPY step into one

Re: Combining Multiple IEBCOPY step into one

Re: Combining Multiple IEBCOPY step into one

Re: Combining Multiple IEBCOPY step into one