DSNTYPE=LARGE and COMPRESS parameters



JES, JES2, JCL utilities, IDCAMS, Compile & Run JCLs, PROCs etc...

DSNTYPE=LARGE and COMPRESS parameters

Postby samb01 » Mon Jun 01, 2015 2:43 pm

Hello,

i would like to know if it's possible to compress datasets large format sequential ?

I can't find this information.

Than'k for your help.

Fianley, i would like to know if it's better to use these parameters (in the datacass : COMPRA):


Data Set Name Type . . . . . : EXTENDED
If Extended . . . . . . . . : REQUIRED
Extended Addressability . . : NO
Record Access Bias . . . . : USER
RMODE31 . . . . . . . . . . :
Space Constraint Relief . . . : YES
Reduce Space Up To (%) . . : 50
Dynamic Volume Count . . . :

Compaction . . . . . . . . . : YES
Spanned / Nonspanned . . . . :



for a very big dataset :

//     DISP=(,CATLG,DELETE),DATACLAS=COMPRA,           
//         SPACE=(CYL,(650,300),RLSE),VOL=(,,,59),     
//         DCB=(RECFM=VB,LRECL=27994,BLKSIZE=27998)     



This aalocation generated this error :

IEC032I E37-04,IFG0554P,EVRDAFMR,S10,BABEP,B55F,PDUMC1, 294
B.EVRDAFM.BABEP.G0027V00




or is it better to use this allocation :

SPACE=(CYL,(650,300),RLSE),VOL=(,,,59),   
DSNTYPE=LARGE                             



Be cause with this allocation, it works with these messages :

VAM0096 SECONDARY REDUCED FROM 300 CYL TO 73 CYL
VAM0096 DOES IT FIT SUPPORT REDUCE TO FIT OPERATION STARTING
VAM0096 EPRSAUMR,S10,BABEP,B.EVRDAFM.BABEP.G0027V00
VAM0096 REDUCE TO FIT OPERATION SUCCESSFUL FOR
VAM0096 EPRSAUMR,S10,BABEP,B.EVRDAFM.BABEP.G0027V00
VAM0096 SECONDARY REDUCED FROM 300 CYL TO 12 CYL
VAM0096 DOES IT FIT SUPPORT REDUCE TO FIT OPERATION STARTING
VAM0096 EPRSAUMR,S10,BABEP,B.EVRDAFM.BABEP.G0027V00
VAM0096 REDUCE TO FIT OPERATION SUCCESSFUL FOR
VAM0096 EPRSAUMR,S10,BABEP,B.EVRDAFM.BABEP.G0027V00
VAM0096 SECONDARY REDUCED FROM 300 CYL TO 3 CYL
VAM0096 DOES IT FIT SUPPORT REDUCE TO FIT OPERATION STARTING
VAM0096 EPRSAUMR,S10,BABEP,B.EVRDAFM.BABEP.G0027V00
VAM0096 DOES IT FIT SUPPORT REDUCE TO FIT OPERATION STARTING
VAM0096 EPRSAUMR,S10,BABEP,B.EVRDAFM.BABEP.G0027V00
VAM0096 REDUCE TO FIT OPERATION SUCCESSFUL FOR
VAM0096 EPRSAUMR,S10,BABEP,B.EVRDAFM.BABEP.G0027V00
VAM0096 SECONDARY REDUCED FROM 300 CYL TO 179 CYL



But the inconvenient is that the fianl dataset is really big because there is not compression parameters.

Have a look in this message :

IGD17163I
COMPRESSION
REQUEST NOT HONORED FOR DATA SET
B.EVRDAFM.BABEP.G0027V00 BECAUSE DATA SET
CHARACTERISTICS DO NOT MEET COMPRESSION CRITERIA, ALLOCATION CONTINUES
IGD101I SMS ALLOCATED TO DDNAME (SAVEP )
DSN (B.EVRDAFM.BABEP.G0027V00 )
STORCLAS (SCDBDUM) MGMTCLAS ( ) DATACLAS (DCKOMP1)
VOL SER NOS= PDUM48,PDUM46,PDUM76,PDUMC5,PDUMA9,PDUM68,PDUM38,PD
PDUMB1,PDUM57,PDUM60,PDUM09,PDUM32,PDUMA0,PDUM52,PD
PDUMD7,PDUMC9,PDUME5,PDUM10,PDUM54,PDUMA5,PDUM27,PD
PDUM53,PDUM49,PDUMD3,PDUM71,PDUMA3,PDUM86,PDUM70,PD
PDUMH5,PDUME4,PDUMB4,PDUM04,PDUMH6,PDUM94,PDUM56,PD
PDUM92,PDUMA6,PDUM80,PDUMD4,PDUMC2,PDUM91,PDUMH2,PD
IGD17271I ALLOCATION HAS BEEN ALLOWED TO PROCEED FOR DATA SET
PROBPR.EPRSAUM.FINDPA.G0027V00
ALTHOUGH VOLUME COUNT REQUIREMENTS COULD NOT BE MET
IGD101I SMS ALLOCATED TO DDNAME (FICINDPA)



And because of this, the size of the dataset is huges :

1146885 tracks


but previously, with this allocation :

//     DISP=(,CATLG,DELETE),DATACLAS=COMPRA,           
//         SPACE=(CYL,(650,300),RLSE),VOL=(,,,59),     
//         DCB=(RECFM=VB,LRECL=27994,BLKSIZE=27998)     



the size was about : 828360 tracks because of the parameters compress.
samb01
 
Posts: 236
Joined: Mon Nov 16, 2009 7:24 pm
Has thanked: 0 time
Been thanked: 0 time

Re: DSNTYPE=LARGE and COMPRESS parameters

 

Return to JCL

 


  • Related topics
    Replies
    Views
    Last post