My best guess, seeing there is not a lot of information to go on: the VOLID as seen by z/VSE is not correct. What does a VTOC of VSE6AF on z/VSE show?
David Wakser
From: vse-l-bounces+david.wakser=wipr...@lists.lehigh.edu [mailto:vse-l-bounces+david.wakser=wipr...@lists.lehigh.edu] On Behalf Of Coffman, Wallace R NAF (US)
Sent: Monday, March 12, 2012 5:00 AM
To: vs...@lehigh.edu
Subject: define vsam dataset (UNCLASSIFIED)
Classification: UNCLASSIFIED
Caveats: NONE
I am trying to define vsam dataset for a specific dasd in a test catalog. I can define space in the vse1 system but not in the vse2 or vse3 systems. The vse 4.2 systems are running as guests in z/vm 5.4. The 6af device is a mdisk in vse1, vse2 and vse3 link to it. I defined the space;
// EXEC IDCAMS,SIZE=AUTO
DEFINE SPACE -
( -
VOLUME(VSE6AF) -
DEDICATE -
) -
CATALOG (RMV.DEV.CATALOG)
I have the 6af device in the directory and in the ipl. I am at a loss as to why I can’t define a vsam dataset, the error;
DEFINE CLUSTER(NAME(TEST.FILE) -
RECORDS (150 30) -
TO (99366) -
REUSE -
NONINDEXED -
SHR(1) -
RECORDSIZE(100 1000) -
CISZ(4096) -
VOLUMES (VSE6AF)) -
CATALOG (RMV.DEV.CATALOG)
IDC3014I CATALOG ERROR
IDC3009I ** VSAM CATALOG RETURN CODE IS 240 - REASON CODE IS IGG0CLAM-8
Indicates that there is a error in the dlbl or extent.
Wallace Coffman
RMV
PSC 10 Box 951
APO AE 09142
DSN 496-4624
CIV 06302-67-4624
U.S. +49-6302-67-4624
Classification: UNCLASSIFIED
Caveats: NONE
Confidentiality Note: This e-mail, including any attachment to it, may contain material that is confidential, proprietary, privileged and/or "Protected Health Information," within the meaning of the regulations under the Health Insurance Portability & Accountability Act as amended. If it is not clear that you are the intended recipient, you are hereby notified that you have received this transmittal in error, and any review, dissemination, distribution or copying of this e-mail, including any attachment to it, is strictly prohibited. If you have received this e-mail in error, please immediately return it to the sender and delete it from your system. Thank you.
Hello Wallace Coffman,
The RC of 240 and reason code indicate the device type is incorrect or the extents are not correct.
Would you run an IDCAMS with the SPACE ALL to show what space is available on VSE6AF?
I would stay away from using DEDICATE.
To add space I recommend:
* $$ JOB JNM=EXPANDEF,DISP=D,PRI=3,CLASS=0
* $$ PUN CLASS=K,DISP=D
* $$ LST CLASS=Z,DISP=L,DEST=*
// JOB EXPANDEF
// LOG
// EXEC IDCAMS,SIZE=AUTO
DEFINE SPACE ( -
ORIGIN( 15735 ) -
TRK( 2115 ) -
VOLUMES(SYSWK1)) -
CAT( VSESP.USER.CATALOG )
IF LASTCC = 0 -
THEN -
LISTC ALL -
CATALOG( VSESP.USER.CATALOG )
/*
/&
// EXEC LISTLOG
* $$ EOJ
Even better is to define a catalog and give it the whole pack (with 6 or more cyls for the catalog itself).
* $$ JOB JNM=UCCOLL,DISP=D,PRI=3,CLASS=0
* $$ LST CLASS=Z,DISP=L
// JOB UCCOLL
// LOG
// DLBL IJSYSUC,'VSAM.MASTER.CATALOG',,VSAM
// EXEC IDCAMS,SIZE=AUTO
DEFINE UCAT -
( -
NAME ( COLL.USER.CATALOG) -
NRVBL -
VOL(VSM101) -
ORIGIN(1 ) -
TRK(50069) -
) -
DATA (CYL( 6 1 ) )
LISTC CATALOG ( COLL.USER.CATALOG)
/*
/&
// EXEC LISTLOG
* $$ EOJ
Elaborate. Thanks.
Frank M. Ramaekers Jr. |
|
I thought DEDICATE was one of those VSAM parameters that was on its way out. Like IMBED and REPLICATE.
I misspoke. DEDICATE is not going away any time soon.
I just think it is better to explicitly provide the ORIGIN and TRACKS of your VSAM spaces. I never liked that the VSAM people decided to call the parameter “DEDICATE”. Everyone knows that DEDICATE is a vintage VM term.