Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

Data compression and CPU consumption when running a job

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL & VSAM
View previous topic :: :: View next topic  
Author Message
balajipradeep

New User


Joined: 12 Mar 2009
Posts: 21
Location: chennai

PostPosted: Thu Mar 12, 2009 11:25 pm    Post subject: Data compression and CPU consumption when running a job
Reply with quote

Hi,

I tried to run a job with SMS compressible option = Yes for the output file.

When the Data is compressed in a job step, the CPU consumption is more, say for example 8 minutes.

When I run a job with SMS compressible = No, the CPU consumption is very less, say for example 1 minues.

Any significance between Data compression and CPU consumption when running a job?
Back to top
View user's profile Send private message

dick scherrer

Site Director


Joined: 23 Nov 2006
Posts: 19270
Location: Inside the Matrix

PostPosted: Thu Mar 12, 2009 11:30 pm    Post subject:
Reply with quote

Hello and welcome to the forum,

When you have a question is it best to start a new topic for your question rather than posting a reply to some existing topic.

Yes, compression (done on the mainframe) will increase cpu utilization. The tradeoff is that the compressed data will require less storage space.

Which is "better" would be determined by the storage and/or capacity management people for your system.
Back to top
View user's profile Send private message
paul_seth55

New User


Joined: 09 Mar 2009
Posts: 3
Location: New York

PostPosted: Thu Mar 12, 2009 11:51 pm    Post subject:
Reply with quote

Balaji,

Obviously we have significance in both the cases! Data compression save the stroge space and CPU time have much more significance towards running cost. In most installation's DASD cost per year is nothing compared to the CPU cost. For us 1 MIPS is $237 w.r.t. DASD cost of $5 per annum.

We should select between the two based on the frequency of the job and volume of data.

If the job doesn't run in daily basis and the volume is huge Compress would be the best option otherwise high CPU time everyday on yearly basis might bump up the YTD cost. Trade-off should be made based on the buisness requirement.

Everyone,

I have sent a mail to my Storage management team! But i am quite not sure if i will get a response before i contract ends ;)

So came up with another design were i commented the first step which compress the complete data. Used DATACLAS=COMPRESS only for delta copied from VSAM file. Used the 0th version to append to +1st version. Estimated savings is 50K per annum.

Thanks for everyones input.
Back to top
View user's profile Send private message
balajipradeep

New User


Joined: 12 Mar 2009
Posts: 21
Location: chennai

PostPosted: Fri Mar 13, 2009 6:18 pm    Post subject:
Reply with quote

Thanks a lot for your input!!!
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL & VSAM All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts copying data without knowing location arunsoods DFSORT/ICETOOL 6 Thu Jul 20, 2017 1:03 pm
This topic is locked: you cannot edit posts or make replies. Fetching data from BAI File arunsoods JCL & VSAM 1 Wed Jul 19, 2017 4:28 pm
No new posts Loading data to table gives wrong for... Raghu navaikulam DB2 19 Thu Jul 13, 2017 2:11 pm
No new posts SQL - select data available in index Nileshkul DB2 3 Mon Jun 26, 2017 1:30 am
No new posts NDM syntax checking without actually ... GAPX1 All Other Mainframe Topics 0 Wed Jun 07, 2017 2:36 am


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us