IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

Data compression and CPU consumption when running a job


IBM Mainframe Forums -> JCL & VSAM
Post new topic   Reply to topic
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
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

Moderator Emeritus


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

PostPosted: Thu Mar 12, 2009 11:30 pm
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
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
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 View Bookmarks
All times are GMT + 6 Hours
Forum Index -> JCL & VSAM

 


Similar Topics
Topic Forum Replies
No new posts How to save SYSLOG as text data via P... All Other Mainframe Topics 4
No new posts Store the data for fixed length COBOL Programming 1
No new posts Running REXX through JOB CLIST & REXX 13
No new posts Data set Rec-Cnt and Byte-Cnt Testing & Performance 2
No new posts SCOPE PENDING option -check data DB2 2
Search our Forums:

Back to Top