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
 

 

Loading a VSAM file alters the primary space allocation

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

New User


Joined: 02 Nov 2006
Posts: 28

PostPosted: Fri Jan 20, 2012 9:20 pm    Post subject: Loading a VSAM file alters the primary space allocation
Reply with quote

Hi,

I have a cluster define listed below:

DEFINE CLUSTER-
(NAME(dataset) -
REUSE -
SPEED -
SHAREOPTIONS(2) -
NOERASE -
INDEXED -
KEYS(32 0) -
NOREPLICATE -
RECORDSIZE(500 1000) -
FREESPACE(20 30) -
OWNER(ME)) -
DATA -
(NAME(dataset.DATA) -
CYL(600 200) -
CISZ(16384)) -
INDEX -
(NAME(dataset.INDEX) -
CYL(25 5) -
CISZ(2048))

As you can see the initial allocation is for a primary of 600 CYL. When I actually load the data (IDCAMS REPRO) the primary jumps to 3000 cylinders with 21 extents. We are under an operating system of zOS 1.11.

I've never seen the primary allocation get altered like this before. Any answers?

Thanks.
Back to top
View user's profile Send private message

Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 7931
Location: Bellevue, IA

PostPosted: Fri Jan 20, 2012 9:45 pm    Post subject:
Reply with quote

Post the LISTCAT output using the Code button to preserve spacing.
Back to top
View user's profile Send private message
f8ful

New User


Joined: 02 Nov 2006
Posts: 28

PostPosted: Fri Jan 20, 2012 9:57 pm    Post subject:
Reply with quote

I lost the listcat for the 3000 allocation, but I tried again this morning and got a 1200 CYL allocation on the primary. That LISTCAT is below,,,,only down to the 3rd extent.

Code:
DATA ----------
dataset                                         
     IN-CAT --- cat                                                     
     HISTORY                                                                   
       DATASET-OWNER-----(NULL)     CREATION--------2012.020                   
       RELEASE----------------2     EXPIRATION------0000.000                   
       ACCOUNT-INFO-----------------------------------(NULL)                   
     PROTECTION-PSWD-----(NULL)     RACF----------------(NO)                   
     ASSOCIATIONS                                                               
       CLUSTER--dataset                                               
     ATTRIBUTES                                                                 
       KEYLEN----------------32     AVGLRECL-------------500     BUFSPACE-----------34816     CISIZE-------------16384

       RKP--------------------0     MAXLRECL------------1000     EXCPEXIT----------(NULL)     CI/CA-----------------45

       SHROPTNS(2,3)      SPEED     UNIQUE           NOERASE     INDEXED       NOWRITECHK     NOIMBED       NOREPLICAT

       UNORDERED          REUSE     NONSPANNED                                 
     STATISTICS                                                                 
       REC-TOTAL--------5578028     SPLITS-CI--------------0     EXCPS--------------17400

       REC-DELETED------------0     SPLITS-CA--------------0     EXTENTS---------------35

       REC-INSERTED-----------0     FREESPACE-%CI---------20     SYSTEM-TIMESTAM
       REC-UPDATED------------0     FREESPACE-%CA---------30          X'C90074554A4AD704'

       REC-RETRIEVED----------0     FREESPC-------1239973888                   
     ALLOCATION                                                               
   SPACE-TYPE------CYLINDER     HI-A-RBA------4276224000                   
  SPACE-PRI------------600     HI-U-RBA------4270325760                   
  SPACE-SEC------------200                                                 
VOLUME                                                                     
  VOLSER------------SMHS34     PHYREC-SIZE--------16384     HI-A-RBA------2654208000     EXTENT-NUMBER---------28

  DEVTYPE------X'3010200F'     PHYRECS/TRK------------3     HI-U-RBA------2654208000     EXTENT-TYPE--------X'40'

  VOLFLAG------------PRIME     TRACKS/CA-------------15                   
  EXTENTS:                                                                 
  LOW-CCHH-----X'22140000'     LOW-RBA----------------0     TRACKS-------------18000

  HIGH-CCHH----X'26C3000E'     HIGH-RBA-------884735999                   
  LOW-CCHH-----X'10980000'     LOW-RBA--------884736000     TRACKS--------------3000

  HIGH-CCHH----X'115F000E'     HIGH-RBA------1032191999                   
  LOW-CCHH-----X'11C40000'     LOW-RBA-------1032192000     TRACKS--------------3000

  HIGH-CCHH----X'128B000E'     HIGH-RBA------1179647999                   
  LOW-CCHH-----X'163D0000'     LOW-RBA-------1179648000     TRACKS--------------3000

  HIGH-CCHH----X'1704000E'     HIGH-RBA------1327103999                   

Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 7931
Location: Bellevue, IA

PostPosted: Fri Jan 20, 2012 10:09 pm    Post subject:
Reply with quote

What you show does NOT indicate the primary space allocation was changed. If you think it was changed, then either (1) the DELETE / DEFINE was run from a library other than what you think, or (2) possibly an SMS parameter changed the value (although I haven't looked to see if this is even possible to change this for a VSAM file).
Back to top
View user's profile Send private message
f8ful

New User


Joined: 02 Nov 2006
Posts: 28

PostPosted: Fri Jan 20, 2012 10:24 pm    Post subject:
Reply with quote

The primary allocation shows 600 CYL. On this storage device there are 15 TRKS per CYL. You can see the primary tracks are 18000.

18000 / 15 = 1200 CYL's

Here is another view from ISPF[/code] Data Set Information

Data Set Name . . . . : dataset.DATA

General Data Current Allocation
Management class . . : **None** Allocated cylinders : 5,800
Storage class . . . : **None** Allocated extents . : 41
Volume serial . . . : DISK01 +
Device type . . . . : 3390
Data class . . . . . : **None**
Organization . . . : VS Current Utilization
Record format . . . : ? Used cylinders . . : ?
Record length . . . : ? Used extents . . . : ?
Block size . . . . : ?
1st extent cylinders: 1200
Secondary cylinders : 200 Dates
Data set name type : Creation date . . . : 2012/01/20
Referenced date . . : 2012/01/20
Expiration date . . : ***None***

To display multiple volumes press Enter or enter Cancel to Exit.
Back to top
View user's profile Send private message
tampakenny

New User


Joined: 15 Feb 2006
Posts: 11
Location: Tampa, FL

PostPosted: Sat Jan 28, 2012 3:27 am    Post subject: Reply to: Loading a VSAM file alters the primary space alloc
Reply with quote

Is it possible that the 18000 number you are seeing is not just for the primary, but rather for the entire VSAM, including extents? In this case, you have 3 extents. Counting your primary of 600 cyl, that's 9000 tracks. Adding your 3 extents at 200 cyl (3000 tracks) each, that's 9000 more tracks, for a grand total of 18000 tracks allocated.
Back to top
View user's profile Send private message
f8ful

New User


Joined: 02 Nov 2006
Posts: 28

PostPosted: Tue Jan 31, 2012 7:23 pm    Post subject:
Reply with quote

I don't think so. If you look at the ISPF Dataset Infor mation page, you see that the total allocation for the file is 5800 CYL and it consists of 41 extents. I did not list the entire LISTCAT output showing the 41 extents. Only the first three showed on the first LISTCAT page.
Back to top
View user's profile Send private message
enrico-sorichetti

Global Moderator


Joined: 14 Mar 2007
Posts: 10210
Location: italy

PostPosted: Tue Jan 31, 2012 9:50 pm    Post subject: Reply to: Loading a VSAM file alters the primary space alloc
Reply with quote

did You ever hear of VSAM extent consolidation ...

from some IBM pubblication ...
Quote:
Extent consolidation
z/OS consolidates adjacent extents for VSAM SMS managed data sets when extending on the same volume. VSAM extent consolidation is automatic and requires no action on your part. If the extents are adjacent, the new extent is incorporated into the previous extent. This means that first extent tracks as seen on ISPF 3.4 Data set level listing shows allocations larger than the primary when extents are adjacent to the primary (Figure 7 on page 13 and Figure 8 on page 14).


IIRC since zOS 1.5

here is a link to the official IBM manual
z/OS V1R11 DFSMS Using Data Sets
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/DGT2D480/CCONTENTS?SHELF=DGT2BK91&DN=SC26-7410-09&DT=20090522090215
and the exact page
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/dgt2d480/2.2.2.4.6?ACTION=MATCHES&REQUEST=consolidation&TYPE=FUZZY&SHELF=DGT2BK91&DT=20090522090215&CASE=&searchTopic=TOPIC&searchText=TEXT&searchIndex=INDEX&rank=RANK&ScrollTOP=FIRSTHIT#FIRSTHIT
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 SORTJOIN - Copy Matched and Unmatched... Steve Ironmonger DFSORT/ICETOOL 5 Tue Jan 17, 2017 4:26 pm
No new posts how to recover an uncataloged VSAM da... archanamuthukrishnan All Other Mainframe Topics 3 Wed Jan 11, 2017 6:18 pm
No new posts Underlying DB2 VSAM LDS - SMF recording vasanthz All Other Mainframe Topics 6 Thu Jan 05, 2017 4:20 am
No new posts Copy RECFM =VB TO FB file with RECL =... sahil41352 DFSORT/ICETOOL 3 Wed Dec 28, 2016 11:29 pm
No new posts REXX DB2: Dynamic allocation of DB2.D... BHAS CLIST & REXX 3 Mon Dec 19, 2016 8:26 pm


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