List,
Please forgive the probably simple question but I can't see what I'm
doing wrong. I am a SMS rookie - it was set up here before I got here
and I haven't done anything with it until now, and I'm having problems.
I'm trying to define an extended-format VSAM linear dataset for
downloading z/OS 1.9. IBM says the download will be about 6.5 GB so I
need to get the extended working to get it downloaded. I have never
built any SMS definitions before so it's probably something stupid that
I am missing but here goes.
My plan is to define a new zFS dataset called OMVSBIG.SERVICE to hold
the downloaded serverpac.
I can allocate OMVSBIG.SERVICE with just a few cylinders and the system
allocates it on the correct volume, but when I try to allocate my big
dataset, the system rejects it saying the dataset will go over 4 GB but
isn't an extended attribute dataset. I can't see what I'm missing and
am asking for help. Here's the define and error.
DEF CL(NAME(OMVSBIG.SERVICE) VOL(ZB2000) LINEAR -
CISZ(4096) -
CYL(25000 1000) SHR(3))
IGD17103I CATALOG ERROR WHILE DEFINING VSAM DATA SET
OMVSBIG.SERVICE
RETURN CODE IS 140 REASON CODE IS 110 IGG0CLEV
IGD306I UNEXPECTED ERROR DURING IGG0CLEV PROCESSING
RETURN CODE 140 REASON CODE 110
THE MODULE THAT DETECTED THE ERROR IS IGDVTSCU
SMS MODULE TRACE BACK - VTSCU VTSCT VTSCH VTSCG VTSCD VTSCC VTSCR SSIRT
SYMPTOM RECORD CREATED, PROBLEM ID IS IGD00004
IGD17219I UNABLE TO CONTINUE DEFINE OF DATA SET
OMVSBIG.SERVICE
IDC3014I CATALOG ERROR
IDC3009I ** VSAM CATALOG RETURN CODE IS 140 - REASON CODE IS
IDC3009I IGG0CLEV-110
IDC3003I FUNCTION TERMINATED. CONDITION CODE IS 12
My question is "what am I missing?"
Here is what I have done so far:
I defined a new 3390 mod 27 to hold this thing, and it shows up with
30043 free cylinders. I defined it using the SG parameter in ICKDSF.
The vol-ser is ZB2000.
Next I defined a storage group called SGBIG with the following
parameters.
LINE STORGRP SG VIO VIO AUTO
OPERATOR NAME TYPE MAXSIZE UNIT MIGRATE
--(1)---- --(2)--- -------(3)------ --(4)-- (5)-
--(6)---
SGBIG POOL ------- ---- NO
Vol-ser ZB2000 is in this storage group:
CDS Name . . . . . . . : MVS.SMS.SCDSI
Storage Group Name . . : SGBIG
Volume Serial Number . : ZB2000
Physical Volume Status : ---------
MB-free : ---------
% Free : --
System/Sys SMS Vol MVS Vol SMS SG
Group Name Status Status Status
---------- ------- -------- ------
WSCP ENABLE -------- ENABLE
I then defined a data class called DCBIG with the following parameters.
DATACLAS LAST TIME EXTENDED
NAME MODIFIED DATA SET NAME TYPE ADDRESSABILITY
--(2)--- --(25)--- -------(26)------- -----(27)-----
DCBIG 14:49 EXTENDED REQUIRED YES
DCLIST 13:47 ------------------ NO
I added the following to the ACS routines in use.
To the storage class routine, I added OMVSGRP.** as a valid SMS-managed
dataset name.
To the storage group routine, I added:
FILTLIST BIG INCLUDE(OMVSBIG.**)
WHEN (&DSN EQ &BIG)
SET &STORGRP = 'SGBIG'
To the data class routine I added
FILTLIST VALID_DC INCLUDE('DCPDS',
'DCBIG',
'DCSTD',
'DCLOAD')
FILTLIST DCBIG INCLUDE('OMVSBIG')
IF (&DATACLAS EQ '' AND
&PGM NE &NOORG) THEN
SELECT (&HLQ)
WHEN (&DCBIG)
SET &DATACLAS = 'DCBIG'
END
I ran the validate and activate of the SMS "stuff" I defined above.
Running an ACS test using the following parameters, the system came back
telling me it would use the SGBIG and DCBIG and allocating a small
dataset called OMVSBIG.SERVICE correctly put it on ZB2000
Thanks.
Rex
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
