IBM Mainframe Forum

Let me ask this question, Can I define/create a VSAM-E file that is non-sms managed?
If yes, then how can I get this done.
Thanx in advance.

Jerry

From the VSAM Demystified redbook, SG24-6105:

Extended format data sets must be system-managed. A system-managed data
set must have an associated storage class and reside in a system-managed
volume. Extended format data sets are described in the catalog as striped data
sets with a stripe count of one. When a data set is allocated as an extended
format data set, the data and index are extended format. Any alternate indexes
related to an extended format cluster are also extended format.

This is where I am at today.

DataClass

CDS Name . . . : SYS1.SCDS
Data Class Name : VSAMEXT

Description : TEST DATACLASS

Recfm . . . . . . . . . :
Lrecl . . . . . . . . . :
Override Space . . . . . : NO
Space Avgrec . . . . . . :
Avg Value . . . . :
Primary . . . . . :
Secondary . . . . :
Directory . . . . :
Retpd Or Expdt . . . . . :
Volume Count . . . . . . : 1
Add'l Volume Amount . . :
CDS Name . . . . . : SYS1.SCDS
Data Class Name . . : VSAMEXT

Data Set Name Type . . . . . : EXTENDED
If Extended . . . . . . . . : REQUIRED
Extended Addressability . . : NO
Record Access Bias . . . . : USER
Space Constraint Relief . . . : NO
Reduce Space Up To (%) . . :
Dynamic Volume Count . . . :
Compaction . . . . . . . . . :
Spanned / Nonspanned . . . . :
Media Interchange
Media Type . . . . . . . . :
Recording Technology . . . :
Performance Scaling . . . . :
Performance Segmentation . :

Control DataSet
CDS Name . : SYS1.SCDS
CDS Status : VALID

Description : BASE CONFIGURATION FOR HFS
==> . . . . :
Default Management Class : STANDEF Default Device Geometry :
Default Unit . . . . . . : SYSDA Bytes/track . . . . . : 474
Tracks/cylinder . . . : 15
DS Separation Profile :
System: ADCD



Sysgrp:
VALIDATION RESULTS

VALIDATION RESULT: VALIDATION SUCCESSFUL - WARNINGS DETECTED
SCDS NAME: SYS1.SCDS
ACS ROUTINE TYPE: *
DATE OF VALIDATION: 2011/03/07
TIME OF VALIDATION: 15:34

IGD06023I STORAGE GROUP HFSCLASS IS NOT REFERENCED BY THE STORAGE GROUP ACS ROUT
===================================================
JCL:
//VKSDCRT1 EXEC PGM=IDCAMS,REGION=4096K
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DEFINE CLUSTER ( -
NAME(QA.VSUM.R50B.PERSNL.DATA1.VSAMEXT) -
VOLUME(OS3H8A) -
DATACLAS(VSAMEXT) -
TRACKS(5 1) -
RECORDSIZE(150 1500) -
KEYS(5 9) -
INDEXED -
) -
DATA ( -
NAME(QA.VSUM.R50B.PERSNL.DATA1.VSAMEXT.DATA) -
) -
INDEX ( -
NAME(QA.VSUM.R50B.PERSNL.DATA1.VSAMEXT.IDX) -
)
=========================================================
IDC3014I CATALOG ERROR
IDC3009I ** VSAM CATALOG RETURN CODE IS 48 - REASON CODE IS IGG0CLAT-80
IDC3003I FUNCTION TERMINATED. CONDITION CODE IS 12

IDC0002I IDCAMS PROCESSING COMPLETE. MAXIMUM CONDITION CODE WAS 12

can anyone give me an idea of the problem.

The Messages and Codes manual for IDC3009I, RC48, gives

80 Explanation: Define data set with extended format information is not valid for a non-SMS data set.

Hello,

As you had already asked and been told extended vsam has to be managed by sms, why try to create one that is not?

Why might you believe that the rules would change and you could "get away with it"?

d

My understanding that to create an VSAM-E dataset, you had to define the file with a DataClass
that has Extended Addressability. I.E.

Data Set Name Type . . . . . : EXTENDED
If Extended . . . . . . . . : REQUIRED
Extended Addressability . . : YES

If I do not need a DataClass, then how does it get done then?

Jerry

From my earlier post:

From the VSAM Demystified redbook, SG24-6105:Extended format data sets must be system-managed. A system-managed data
set must have an associated storage class and reside in a system-managed
volume. Extended format data sets are described in the catalog as striped data
sets with a stripe count of one. When a data set is allocated as an extended
format data set, the data and index are extended format. Any alternate indexes
related to an extended format cluster are also extended format.

Note the Redbook says an extended format VSAM file must:
1. have an associated storage class
2. reside on a system-managed volume

The data class is a necessary but far from sufficient condition to allocate an extended format VSAM file. You must make sure you define a storage class in your ACS routines that will cover the data set you are attempting to allocate, and you must make sure you are allocating on a system-managed volume (that is, when ICKDSF is run to initialize the volume, the keyword SG must be present as one of the initialization parameters). Furthermore, the presence of this message from your post is a red flag that you have work to do:

IGD06023I STORAGE GROUP HFSCLASS IS NOT REFERENCED BY THE STORAGE GROUP ACS ROUT

Remember that I said this would take at least a week of your time? You did post a lot of information, but not enough. Your ACS routines (one for the DC, MC, SC, SG) determine if a data set is SMS managed or not. That is why it is important to have a concept, otherwise you will have a problem with those routines because they will become totally confusing. We use the LLQ and the HLQ to determine if a data set is SMS managed or not. If your data set has a SC assigned to it from the ACS routines then it will be a SMS data set. A data set goes through the DC ACS first, then SC which determines if SMS or not, then it continues with the MC and SG. The SG determines which volume pool will be used. Hope this helps you some.