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

Is it possible to allocate DA dataset with DSNTYPE=LARGE?


IBM Mainframe Forums -> All Other Mainframe Topics
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
evandro95

New User


Joined: 14 May 2015
Posts: 2
Location: Brazil

PostPosted: Thu Jul 22, 2021 8:40 pm
Reply with quote

Hi all,

Currently I have one DCB DSORG=DA dataset to store data, for years... and this is about to reach current file allocation size limit of 4369 cylinders and I would need to increase that, however, when I try, I get the following error, even if I specify DSNTYPE=LARGE, which seems not to be accepted by DA:
Code:
REQUESTED SPACE EXCEEDS 65,535 TRKS


And unfortunately I can't change DSORG to PS, otherwise clear verbs and processes that use/consume this dataset no longer works.
I am currently studying the possibility of changing process to accept PS files, however that's going to take long and require many application changes... so I would like to check if there are any other alternative

As reference, this is the file allocation lastly used and working:
Code:
//JSTEP1  EXEC PGM=GISAMZAP,PARM=NEW                       
//STEPLIB   DD DSN=MVSCLR.V1R1M0.LOAD,DISP=SHR             
//CLRPRINT  DD SYSOUT=*                                     
//GISAM     DD DSN=nnnnnnn,DISP=(,CATLG,DELETE),
//             UNIT=3390,VOL=SER=OSSS12,                   
//             SPACE=(CYL,(2184,2184)),
//             DCB=(KEYLEN=19,BLKSIZE=16000,DSORG=DA)       
//CLRIN     DD DUMMY                                       


Note: seems DSORG=DA is also limited to 2 extents
Note2: volume OSSS12 is dedicated to that file and has 25.000+ cylinders available

Thanks in advance!
Back to top
View user's profile Send private message
Joerg.Findeisen

Active Member


Joined: 15 Aug 2015
Posts: 618
Location: Bamberg, Germany

PostPosted: Thu Jul 22, 2021 9:09 pm
Reply with quote

Code:
DATASET LIMITS
NON-EXTENDED-FORMAT

DS Extents Max Max     Size
Type /Vol Vols Stripes Limit
DA    16  59   0       255 extents
Back to top
View user's profile Send private message
Joerg.Findeisen

Active Member


Joined: 15 Aug 2015
Posts: 618
Location: Bamberg, Germany

PostPosted: Fri Jul 23, 2021 12:00 am
Reply with quote

Whatever application that is, you can't grow a DA dataset beyond 65535 Tracks.
Back to top
View user's profile Send private message
evandro95

New User


Joined: 14 May 2015
Posts: 2
Location: Brazil

PostPosted: Wed Jul 28, 2021 12:55 am
Reply with quote

Thanks, Joerg. Do you think this is possible to convert BDAM to VSAM RRDS or other direct access structure? Would you have any tip on that if so?
I have been trying to split BDAM along volumes but it doesn't work, so I am now trying to change it to VSAM, but getting some errors.

Current BDAM details
Code:
HITTR    LLDIR     KEYLEN    NUMINDEX  BLKSIZE   BLK/TRK    CCHHR     
74D202     1         19        158      16000         3     0028000001
EMPTY BLOCK TOTAL =      0                                           
INDEX BLOCK TOTAL =    159                                           
DATA  BLOCK TOTAL =  89561                                           
UNKWN BLOCK TOTAL =      0                                           


VSAM allocated:
Code:
DEFINE                                        -
  CLUSTER                                     -
    (NAME(zzz)                                -
    RECORDSIZE(1,19)                          -       
    CYLINDERS(2200,2200)                      -
    VOLUMES(OSSS12)                           -
    NUMBERED                                  -
    REUSE )                                   -
  INDEX                                       -
    (NAME(zzz.INDEX))                         -
  DATA                                        -
    (NAME(zzz.DATA))


Error found during copy process:
Code:
  REPRO                                        -                     
  INFILE(xxx)                   -                     
IDC3201I CONSTANT 'xxx' EXCEEDS LENGTH LIMIT         
  OUTDATASET(zzz)   
Back to top
View user's profile Send private message
Joerg.Findeisen

Active Member


Joined: 15 Aug 2015
Posts: 618
Location: Bamberg, Germany

PostPosted: Wed Jul 28, 2021 9:59 pm
Reply with quote

evandro95 wrote:
Error found during copy process:
Code:
  REPRO                                        -                     
  INFILE(xxx)                   -                     
IDC3201I CONSTANT 'xxx' EXCEEDS LENGTH LIMIT         
  OUTDATASET(zzz)   

Can it be that IDS was intended but IFILE has been used instead here?
Back to top
View user's profile Send private message
steve-myers

Active Member


Joined: 30 Nov 2013
Posts: 891
Location: The Universe

PostPosted: Fri Jul 30, 2021 2:48 am
Reply with quote

Joerg.Findeisen wrote:
Whatever application that is, you can't grow a DA dataset beyond 65535 Tracks.


I, too, fear this is correct.

But, what is the complete BDAM DCB in the program, used to read and write the BDAM data set.

In BDAM, there are several ways to access a record.
  • Relative record number.
  • Record address expressed as a TTR (which is where the 64K limit comes from.
  • Record addresss expressed as cccchhhhrr
  • Record key
As you may be aware, several years ago IDMS changed over to using EXCP instead of BDAM. Because of the way IDMS defines record addresses accessing records by relative record number seemed to me to be quite logical. Since, at least in theory, converting a relative record number to a TTR is very simple, my thought at the time IDMS wanted to cut out the middleman (in BDAM), but your difficulty suggests DSNTYPE=LARGE may have been the real reason.

You do have one other option: split the data base into multiple BDAM data sets. In essence, IDMS has been doing this for a long, long time.

I think you will have a great deal of difficulty converting the application to VSAM RRDS. The records are then addressed by the record's RBA, and there is no method to calculate an RBA from a record address when the data set contains mutilple CIs The RBA jumps in unpredictable way when jumping fo one CI to the next sequential CI.
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 -> All Other Mainframe Topics

 


Similar Topics
Topic Forum Replies
No new posts Multiple find/replace on the same dat... DFSORT/ICETOOL 4
No new posts Map VSAM Dataset to a Table/Tablespace DB2 5
No new posts ADR324E-VOL/DATASET SPECIFIED BY DDNA... JCL & VSAM 6
No new posts how to list the number of backup data... JCL & VSAM 3
No new posts Copying large number of datasets to m... JCL & VSAM 17
Search our Forums:

Back to Top