|
|
| Author |
Message |
dhanashreeakhade
New User
Joined: 11 Mar 2008
Posts: 8
Location: pune
|
|
|
|
Hi,
I am reviewing a JCL that has 3 steps. All are ICETOOL only.
The steps are not much complex and we can merge those into a single one.
I have asked the developer to do the same, but he says that he has splitted it so that it will be easy to understand.
I need to give him a valid reason for why to go for single step execution.
I still think that those should be merged in a single step and for clarity/understanding purpose we can have comment wherever possible. Could you please let me know if there are any other reasons because of which we should prefer 1 step? ... I am not sure whether it will be affecting performance of JCL. If it is affecting, how?
Any kind of help will be appreciated.
Thanks,
Dhanashree. |
|
| Back to top |
|
 |
References
|
 Posted: Tue Apr 29, 2008 5:36 pm Post subject: Re: executing ICETOOL... |
|
|
|
|
CICS Guy
Senior Member
Joined: 18 Jul 2007
Posts: 1128
Location: At my desk
|
|
|
|
| How about posting the three steps? |
|
| Back to top |
|
|
dick scherrer
Global Moderator
Joined: 23 Nov 2006
Posts: 7470
Location: 221 B Baker St
|
|
|
|
Hello,
| Quote: |
I need to give him a valid reason for why to go for single step execution.
I still think that those should be merged in a single step |
Why do you think this should be one step rather than 3? Is there some business reason? There is something to be said for ease of understanding - it surely makes maintenance and problem resolution easier.
Depending on what is being done, it may use less concurrent dasd if this is done in 3 steps (disp= only happens at step start and step end). Is the data to be processed large or small (your choice as to what is large/small)? |
|
| Back to top |
|
|
|
|
