Adding DASD Volumes to VSE

[r***@sungard.com]

I run VSE as a guest under VM. I need to add some volumes to my VSE system
for my database. Can I add the volumes
without an IPL? What command can I issue?

[Mike Myrick]

if the addresses are already in an add statement, you can place them online.
if not, it would require an ipl.

-----Original Message-----
From: ***@sungard.com [mailto:***@sungard.com]
Sent: Tuesday, September 30, 2003 4:45 PM
To: VSE Discussion List
Subject: Adding DASD Volumes to VSE


I run VSE as a guest under VM. I need to add some volumes to my VSE system
for my database. Can I add the volumes
without an IPL? What command can I issue?

[r***@sungard.com]

There is an add already. But they don't show up with a VOLUME Name I need.
Do I have to reformat them?

AR 0015 565 6E 3380-K BAS565 UNUSED SHARED 2654
CYL
AR 0015 566 6E 3380-K BAS566 USED SHARED 2654
CYL
AR 0015 567 6C 3380 UNUSED SHARED DOWN 885
CYL
AR 0015 568 6C 3380 UNUSED SHARED DOWN 885
CYL




"Mike Myrick"
<***@lafayett To: "VSE Discussion List" <vse-***@Lehigh.EDU>
egov.net> cc:
Sent by: Subject: RE: Adding DASD Volumes to VSE
owner-vse-***@Lehig
h.EDU


09/30/2003 05:59
PM
Please respond to
vse-l






if the addresses are already in an add statement, you can place them
online.
if not, it would require an ipl.

-----Original Message-----
From: ***@sungard.com [mailto:***@sungard.com]
Sent: Tuesday, September 30, 2003 4:45 PM
To: VSE Discussion List
Subject: Adding DASD Volumes to VSE


I run VSE as a guest under VM. I need to add some volumes to my VSE system
for my database. Can I add the volumes
without an IPL? What command can I issue?

[Roland Chung]

Hi Robert, assuming 567, 568 the CUU you want to add the new DASDs as.

First of all, you have to make sure that the new MDSIKs have been
1) added to the VM Direct for this VSE ID and placed online;
2) ICKDSF formatted with a DOSVTOC;

Then, you can issue the DVCUP JCC command to bring them online to your
VSE machine:
r rdr,pausebg
0 dvcup 567
0 dvcup 568
After that, you should see the volume name of these 2 DASDs from the
VOLUME AR command.
You do not require an IPL.

I hope this helps. Regards,

***@sungard.com wrote:

>There is an add already. But they don't show up with a VOLUME Name I need.
>Do I have to reformat them?
>
>AR 0015 565 6E 3380-K BAS565 UNUSED SHARED 2654 CYL
>AR 0015 566 6E 3380-K BAS566 USED SHARED 2654 CYL
>AR 0015 567 6C 3380 UNUSED SHARED DOWN 885 CYL
>AR 0015 568 6C 3380 UNUSED SHARED DOWN 885 CYL
>
>
>
>
> "Mike Myrick"
> <***@lafayett To: "VSE Discussion List" <vse-***@Lehigh.EDU>
> egov.net> cc:
> Sent by: Subject: RE: Adding DASD Volumes to VSE
> owner-vse-***@Lehig
> h.EDU
>
>
> 09/30/2003 05:59
> PM
> Please respond to
> vse-l
>
>
>
>
>
>
>if the addresses are already in an add statement, you can place them
>online.
>if not, it would require an ipl.
>
>-----Original Message-----
>From: ***@sungard.com [mailto:***@sungard.com]
>Sent: Tuesday, September 30, 2003 4:45 PM
>To: VSE Discussion List
>Subject: Adding DASD Volumes to VSE
>
>
>I run VSE as a guest under VM. I need to add some volumes to my VSE system
>for my database. Can I add the volumes
>without an IPL? What command can I issue?
>
>
>
>
>
>
>
>
>
>
>

--
...Roland Chung
Senior Technical Specialist (S/390,VM/VSE,DB2/VSE&VM)
MAXC Consultants Inc.

<< Check my website for sports memorabilia at:
http://www.signaturestars.com/14317 >>
** Wanta earn some extra cash, check this out:
http://www.signaturestars.com/a/14317 **

[D***@aol.com]

In a message dated 9/30/2003 7:40:56 PM Eastern Daylight Time,
***@DowlingAssoc.com writes:


> Issue the following commands at the console
>
> r rdr,pausebg
>
> online Cuu
> 0 dvcup cuu
>
> for each dasd Cuu.

You also might need to do a LINK o the DASD if you have not attached them to
the VSE machine. This should be done BEFORE the VSE console commands above.

David Wakser
Mnemotech

[Dan Askew]

Issue the following commands at the console

r rdr,pausebg

online Cuu
0 dvcup cuu

for each dasd Cuu.

-----Original Message-----
From: ***@sungard.com
To: VSE Discussion List
Sent: 9/30/03 5:59 PM
Subject: RE: Adding DASD Volumes to VSE


There is an add already. But they don't show up with a VOLUME Name I
need.
Do I have to reformat them?

AR 0015 565 6E 3380-K BAS565 UNUSED SHARED
2654
CYL
AR 0015 566 6E 3380-K BAS566 USED SHARED
2654
CYL
AR 0015 567 6C 3380 UNUSED SHARED DOWN
885
CYL
AR 0015 568 6C 3380 UNUSED SHARED DOWN
885
CYL





"Mike Myrick"

<***@lafayett To: "VSE Discussion
List" <vse-***@Lehigh.EDU>
egov.net> cc:

Sent by: Subject: RE: Adding DASD
Volumes to VSE
owner-vse-***@Lehig

h.EDU





09/30/2003 05:59

PM

Please respond to

vse-l









if the addresses are already in an add statement, you can place them
online.
if not, it would require an ipl.

-----Original Message-----
From: ***@sungard.com [mailto:***@sungard.com]
Sent: Tuesday, September 30, 2003 4:45 PM
To: VSE Discussion List
Subject: Adding DASD Volumes to VSE


I run VSE as a guest under VM. I need to add some volumes to my VSE
system
for my database. Can I add the volumes
without an IPL? What command can I issue?

[Patrick Sonnek]

***@sungard.com wrote:

> There is an add already. But they don't show up with a VOLUME Name I
> need.
> Do I have to reformat them?
>
> AR 0015 565 6E 3380-K BAS565 UNUSED SHARED 2654
> CYL
> AR 0015 566 6E 3380-K BAS566 USED SHARED 2654
> CYL
> AR 0015 567 6C 3380 UNUSED SHARED DOWN 885
> CYL
> AR 0015 568 6C 3380 UNUSED SHARED DOWN 885
> CYL
>
>
>
>
>
from the VSE Guest console

#CP ATT cuu * 567 (assuming in the VM directory for the VSE all your
DASD is dedicated.)

From the VSE console
R RDR,PAUSEBG
0 DVCUP 567

You should be good to go.

--
For good laugh at computer security, go to
http://www.vseasy.com/Security_Humor.html

[r***@sungard.com]

Thanks for Info. Using ICKDSF how can I make sure the VTOC size is the
same as the other volumes? Also on my VM system the volume shows as ESA40D,
on VSE system I need it as Volume BAS567. What would my INIT statement
look like?

Bob Bailey

[Roland Chung]

Hi Robert,

It depends on how the DASDs are being defined to the VSE machine.
- using MDISK statement?
If the MDISK is being defined on a real 3380 with 885 cylinders, then
you can only allocate from cylinder 1 for 884 cylinders to your VSE
machine. CP must have cylinder 0. So, no matter what VOLID you put on
the MDISK using ICKDSF, you always see 2 VOLIDs. One from VM and the
other from VSE. Note: you only see 884 cylinders from VSE.

- using DEDICATE statement? (or using CP ATTACH command)
VSE machine owns all cylinders. Once you have initialized the disk with
ICKDSF, VM and VSE sees the same VOLID.

You do not have to make sure the VTOC size is the same as other volumes.
It depends on your planned usage for that disk. Traditionally, most
people use 15 tracks. Or 14 tracks if put it on cylinder 0 because
cylinder 0 track 0 is for the hardware. I would use only 4 tracks on a
3380 if I planned to put a few files on it. Such as use the whole disk
for VSAM space.

The sample ICKDSF INIT statement using only 4 track for VTOC is as follow:
init unit(567) nomap nvfy dvtoc(0,1,4) volid(bas567)

I hope this helps. Regards,

***@sungard.com wrote:

>Thanks for Info. Using ICKDSF how can I make sure the VTOC size is the
>same as the other volumes? Also on my VM system the volume shows as ESA40D,
>on VSE system I need it as Volume BAS567. What would my INIT statement
>look like?
>
>Bob Bailey
>
>
>
>
>

--
...Roland Chung
Senior Technical Specialist (S/390,VM/VSE,DB2/VSE&VM)
MAXC Consultants Inc.

<< Check my website for sports memorabilia at:
http://www.signaturestars.com/14317 >>
** Wanta earn some extra cash, check this out:
http://www.signaturestars.com/a/14317 **

[i***@dapsco.com]

> I would use only 4 tracks on a 3380 if I planned to put a
> few files on it. Such as use the whole disk for VSAM space.

Why 4 tracks? If using the entire volume for VSAM space, I only use 1
track (because the VSAM space only requires a single file entry in the
VTOC).

// ASSGN SYS001,DISK,TEMP,VOL=IDD113,SHR
// EXEC PGM=ICKDSF,SIZE=AUTO
INIT SYSNAME(SYS001) VERIFY(IDD113) VOLID(IDD113) -
VSEVTOC(0,1,1) NOCHK NOMAP PURGE
/* EOD

The following is for our 3390's but the same concept applies to 3380:

VTOC DISPLAY FOR VOLUME: IDD113 DATE: 10/01/2003 TIME: 14:42:24
TYPE: 3390-0A ECKD XT NBR. OF FILE -- STARTING ---
FILE ID SQ TRACKS TYPE CCCC.HH TRACK
-------------------------------------- -- ------- ---- ---------------
*** VOL1 AND IPL *** 1 SYST 0.00 0
*** VTOC EXTENT *** 1 SYST 0.01 1
Z9999992.VSAMDSPC.TB9D0FF0.TAB36EED 50083 VSAM 0.02 2

TOTAL AMOUNT OF FREE-SPACE ON THIS VOLUME: 0 TRACKS

Sincerely,

Dave Clark
***@dapsco.com

DAPSCO Information Systems
3110 Kettering Boulevard
Dayton, Ohio 45439
[phone]

[Rich Smrcina]

...I would put that track at the end of a cylinder...

...VSEVTOC(0,14,1)...

On Wed, 2003-10-01 at 13:48, ***@dapsco.com wrote:
>
>
> > I would use only 4 tracks on a 3380 if I planned to put a
> > few files on it. Such as use the whole disk for VSAM space.
>
> Why 4 tracks? If using the entire volume for VSAM space, I only use 1
> track (because the VSAM space only requires a single file entry in the
> VTOC).
>
> // ASSGN SYS001,DISK,TEMP,VOL=IDD113,SHR
> // EXEC PGM=ICKDSF,SIZE=AUTO
> INIT SYSNAME(SYS001) VERIFY(IDD113) VOLID(IDD113) -
> VSEVTOC(0,1,1) NOCHK NOMAP PURGE
> /* EOD
>
> The following is for our 3390's but the same concept applies to 3380:
>
> VTOC DISPLAY FOR VOLUME: IDD113 DATE: 10/01/2003 TIME: 14:42:24
> TYPE: 3390-0A ECKD XT NBR. OF FILE -- STARTING ---
> FILE ID SQ TRACKS TYPE CCCC.HH TRACK
> -------------------------------------- -- ------- ---- ---------------
> *** VOL1 AND IPL *** 1 SYST 0.00 0
> *** VTOC EXTENT *** 1 SYST 0.01 1
> Z9999992.VSAMDSPC.TB9D0FF0.TAB36EED 50083 VSAM 0.02 2
>
> TOTAL AMOUNT OF FREE-SPACE ON THIS VOLUME: 0 TRACKS
>
> Sincerely,
>
> Dave Clark
> ***@dapsco.com
>
> DAPSCO Information Systems
> 3110 Kettering Boulevard
> Dayton, Ohio 45439
> [phone]
--
Rich Smrcina
Sr. Systems Engineer
Sytek Services - A Division of DSG
Milwaukee, WI
rsmrcina at wi.rr.com
rsmrcina at dsgroup.com

Catch the WAVV! Stay for requirements and the free-for-all.
Update your zSeries skills in 4 days for a very reasonable price.
WAVV 2004 in Chattanooga, TN
April 30-May 4, 2004
For details see http://www.wavv.org

[i***@dapsco.com]

> ...I would put that track at the end of a cylinder...

For what real and beneficial purpose in this case? If the volume is fully
occupied by VSAM space, I see no reason to have the VTOC end on a cylinder
boundary. No additional files can be added to the VTOC. I don't see what
performance or access issues there can be for a volume layout as I have
demonstrated. Naturally, other volume layouts have additional
considerations -- but I don't see any for the specific case of a volume
that is dedicated entirely to suballocated VSAM space. Please enlighten me
of any issues that might pertain to this specific case.

Sincerely,

Dave Clark
***@dapsco.com

DAPSCO Information Systems
3110 Kettering Boulevard
Dayton, Ohio 45439
[phone]

[Rich Smrcina]

Even a single track VTOC can have dozens of files in it and a VSAM
catalog will easily fit. Putting the VTOC at the end saves the need for
the VTOC handler to read the rest of the cylinder where the VTOC is. If
the VTOC is at the end only one track is read. If it is at the
beginning all 15 tracks are read.

On Wed, 2003-10-01 at 15:02, ***@dapsco.com wrote:
>
>
> > ...I would put that track at the end of a cylinder...
>
> For what real and beneficial purpose in this case? If the volume is fully
> occupied by VSAM space, I see no reason to have the VTOC end on a cylinder
> boundary. No additional files can be added to the VTOC. I don't see what
> performance or access issues there can be for a volume layout as I have
> demonstrated. Naturally, other volume layouts have additional
> considerations -- but I don't see any for the specific case of a volume
> that is dedicated entirely to suballocated VSAM space. Please enlighten me
> of any issues that might pertain to this specific case.
>
> Sincerely,
>
> Dave Clark
> ***@dapsco.com
>
> DAPSCO Information Systems
> 3110 Kettering Boulevard
> Dayton, Ohio 45439
> [phone]
--
Rich Smrcina
Sr. Systems Engineer
Sytek Services - A Division of DSG
Milwaukee, WI
rsmrcina at wi.rr.com
rsmrcina at dsgroup.com

Catch the WAVV! Stay for requirements and the free-for-all.
Update your zSeries skills in 4 days for a very reasonable price.
WAVV 2004 in Chattanooga, TN
April 30-May 4, 2004
For details see http://www.wavv.org

[i***@dapsco.com]

> Even a single track VTOC can have dozens of files in it...

Well, you ignored my most basic premise but, oh well... ;-)

Sincerely,

Dave Clark
***@dapsco.com

DAPSCO Information Systems
3110 Kettering Boulevard
Dayton, Ohio 45439
[phone]

[Steve Huggins]

Rich,

I thought it was our old friend SEARCH, from the old quartet
SEEK/SEARCH/TIC/READ.
On not found conditions it would SEARCH to the end of cylinder.
Do you have any figures on this?
I thought with our new friend ECKD on 3390s we had a DEF EXTENT that took
care of that.

Steve

At 03:17 PM 10/1/2003 -0500, you wrote:
>Even a single track VTOC can have dozens of files in it and a VSAM
>catalog will easily fit. Putting the VTOC at the end saves the need for
>the VTOC handler to read the rest of the cylinder where the VTOC is. If
>the VTOC is at the end only one track is read. If it is at the
>beginning all 15 tracks are read.
>
>On Wed, 2003-10-01 at 15:02, ***@dapsco.com wrote:
> >
> > > ...I would put that track at the end of a cylinder...
> >
> > Please enlighten me
> > of any issues that might pertain to this specific case.

[Rich Smrcina]

No figures, per se. Just fond memories of presentations by Wolfgang
Kraemer and Dan Janda.

On Wed, 2003-10-01 at 15:47, Steve Huggins wrote:
> Rich,
>
> I thought it was our old friend SEARCH, from the old quartet
> SEEK/SEARCH/TIC/READ.
> On not found conditions it would SEARCH to the end of cylinder.
> Do you have any figures on this?
> I thought with our new friend ECKD on 3390s we had a DEF EXTENT that took
> care of that.
>
> Steve
>
> At 03:17 PM 10/1/2003 -0500, you wrote:
> >Even a single track VTOC can have dozens of files in it and a VSAM
> >catalog will easily fit. Putting the VTOC at the end saves the need for
> >the VTOC handler to read the rest of the cylinder where the VTOC is. If
> >the VTOC is at the end only one track is read. If it is at the
> >beginning all 15 tracks are read.
> >
> >On Wed, 2003-10-01 at 15:02, ***@dapsco.com wrote:
> > >
> > > > ...I would put that track at the end of a cylinder...
> > >
> > > Please enlighten me
> > > of any issues that might pertain to this specific case.
--
Rich Smrcina
Sr. Systems Engineer
Sytek Services - A Division of DSG
Milwaukee, WI
rsmrcina at wi.rr.com
rsmrcina at dsgroup.com

Catch the WAVV! Stay for requirements and the free-for-all.
Update your zSeries skills in 4 days for a very reasonable price.
WAVV 2004 in Chattanooga, TN
April 30-May 4, 2004
For details see http://www.wavv.org

[Stephen Frazier]

The SEARCH command that is used to find the DSN has 2 options. Search
one track only or search to the end of the cylinder. If the VTOC is ONE
track in length then it doesn't mater where the VTOC is located. Only
one track is searched by one I/O command. If the VTOC is larger than 1
track but less than one cylinder it should end on a cylinder boundary.
The search to end of cylinder form will be used and a again only one I/O
command is needed to find the DSN. If the VTOC is larger than one
cylinder then multiple I/O commands are needed to find the DSN in the
VTOC. If the volume will only have a few files in the VTOC you will get
fastest access with a 1 track VTOC no mater where it is placed. You
should not allocate more than 1 track to the VTOC unless you expect that
you will have more files defined in the VTOC than can fit in one track.
If you allocate a 2 track (or larger) VTOC when it is not needed then
you are forcing the system to use the search until end of cylinder form
which runs longer than the search one track form. The worst performance
is when you have a VTOC that is smaller than one cylinder and crosses a
cylinder boundary because that forces the system to issues multiple I/O
commands.

***@wi.rr.com wrote:

> Even a single track VTOC can have dozens of files in it and a VSAM
> catalog will easily fit. Putting the VTOC at the end saves the need for
> the VTOC handler to read the rest of the cylinder where the VTOC is. If
> the VTOC is at the end only one track is read. If it is at the
> beginning all 15 tracks are read.
>

--
Stephen Frazier
Information Technology Unit
Oklahoma Department of Corrections
3400 Martin Luther King
Oklahoma City, Ok, 73111-4298
Tel.: [phone]
Fax: [phone]
Pager: [phone]
email: stevef%doc.state.ok.us

[Rich Smrcina]

I'm going to guess that Steven has some intimate knowledge of VTOC
handling to spout that off... (nice explanation).

Where's the Swami when you need him? (I know, Russia).

On Wed, 2003-10-01 at 17:01, Stephen Frazier wrote:
> The SEARCH command that is used to find the DSN has 2 options. Search
> one track only or search to the end of the cylinder. If the VTOC is ONE
> track in length then it doesn't mater where the VTOC is located. Only
> one track is searched by one I/O command. If the VTOC is larger than 1
> track but less than one cylinder it should end on a cylinder boundary.
> The search to end of cylinder form will be used and a again only one I/O
> command is needed to find the DSN. If the VTOC is larger than one
> cylinder then multiple I/O commands are needed to find the DSN in the
> VTOC. If the volume will only have a few files in the VTOC you will get
> fastest access with a 1 track VTOC no mater where it is placed. You
> should not allocate more than 1 track to the VTOC unless you expect that
> you will have more files defined in the VTOC than can fit in one track.
> If you allocate a 2 track (or larger) VTOC when it is not needed then
> you are forcing the system to use the search until end of cylinder form
> which runs longer than the search one track form. The worst performance
> is when you have a VTOC that is smaller than one cylinder and crosses a
> cylinder boundary because that forces the system to issues multiple I/O
> commands.
>
> ***@wi.rr.com wrote:
>
> > Even a single track VTOC can have dozens of files in it and a VSAM
> > catalog will easily fit. Putting the VTOC at the end saves the need for
> > the VTOC handler to read the rest of the cylinder where the VTOC is. If
> > the VTOC is at the end only one track is read. If it is at the
> > beginning all 15 tracks are read.
> >
--
Rich Smrcina
Sr. Systems Engineer
Sytek Services - A Division of DSG
Milwaukee, WI
rsmrcina at wi.rr.com
rsmrcina at dsgroup.com

Catch the WAVV! Stay for requirements and the free-for-all.
Update your zSeries skills in 4 days for a very reasonable price.
WAVV 2004 in Chattanooga, TN
April 30-May 4, 2004
For details see http://www.wavv.org

[Roland Chung]

Dave, 1 track is running a risk. 4 tracks gives me a more comforting
feeling. :-)


***@dapsco.com wrote:

>
>
>
>
>>I would use only 4 tracks on a 3380 if I planned to put a
>>few files on it. Such as use the whole disk for VSAM space.
>>
>>
>
>Why 4 tracks? If using the entire volume for VSAM space, I only use 1
>track (because the VSAM space only requires a single file entry in the
>VTOC).
>
>// ASSGN SYS001,DISK,TEMP,VOL=IDD113,SHR
>// EXEC PGM=ICKDSF,SIZE=AUTO
> INIT SYSNAME(SYS001) VERIFY(IDD113) VOLID(IDD113) -
> VSEVTOC(0,1,1) NOCHK NOMAP PURGE
>/* EOD
>
>The following is for our 3390's but the same concept applies to 3380:
>
> VTOC DISPLAY FOR VOLUME: IDD113 DATE: 10/01/2003 TIME: 14:42:24
> TYPE: 3390-0A ECKD XT NBR. OF FILE -- STARTING ---
> FILE ID SQ TRACKS TYPE CCCC.HH TRACK
> -------------------------------------- -- ------- ---- ---------------
> *** VOL1 AND IPL *** 1 SYST 0.00 0
> *** VTOC EXTENT *** 1 SYST 0.01 1
> Z9999992.VSAMDSPC.TB9D0FF0.TAB36EED 50083 VSAM 0.02 2
>
> TOTAL AMOUNT OF FREE-SPACE ON THIS VOLUME: 0 TRACKS
>
>Sincerely,
>
>Dave Clark
>***@dapsco.com
>
>DAPSCO Information Systems
>3110 Kettering Boulevard
>Dayton, Ohio 45439
>[phone]
>

>
>Rich Smrcina wrote:
>
>
>
>
>...I would put that track at the end of a cylinder...
>
>...VSEVTOC(0,14,1)...
>
>
>
Then Rich, what are you going to put on tracks from (0,1) to (0,13), huh?

--
...Roland Chung
Senior Technical Specialist (S/390,VM/VSE,DB2/VSE&VM)
MAXC Consultants Inc.

<< Check my website for sports memorabilia at:
http://www.signaturestars.com/14317 >>
** Wanta earn some extra cash, check this out:
http://www.signaturestars.com/a/14317 **

[i***@dapsco.com]

> Dave, 1 track is running a risk. 4 tracks gives me
> a more comforting feeling. :-)

Except that I specifically stated that this was ONLY for the case of a
volume that is ENTIRELY dedicated to suballocated VSAM space. In this
case, there is NO risk. ;-)

Sincerely,

Dave Clark
***@dapsco.com

DAPSCO Information Systems
3110 Kettering Boulevard
Dayton, Ohio 45439
[phone]

[Rich Smrcina]

They're either sacrificed to the bit bucket or used for really small
files.

On Wed, 2003-10-01 at 15:49, Roland Chung wrote:
> Dave, 1 track is running a risk. 4 tracks gives me a more comforting
> feeling. :-)
>
>
> ***@dapsco.com wrote:
>
> >
> >
> >
> >
> >>I would use only 4 tracks on a 3380 if I planned to put a
> >>few files on it. Such as use the whole disk for VSAM space.
> >>
> >>
> >
> >Why 4 tracks? If using the entire volume for VSAM space, I only use 1
> >track (because the VSAM space only requires a single file entry in the
> >VTOC).
> >
> >// ASSGN SYS001,DISK,TEMP,VOL=IDD113,SHR
> >// EXEC PGM=ICKDSF,SIZE=AUTO
> > INIT SYSNAME(SYS001) VERIFY(IDD113) VOLID(IDD113) -
> > VSEVTOC(0,1,1) NOCHK NOMAP PURGE
> >/* EOD
> >
> >The following is for our 3390's but the same concept applies to 3380:
> >
> > VTOC DISPLAY FOR VOLUME: IDD113 DATE: 10/01/2003 TIME: 14:42:24
> > TYPE: 3390-0A ECKD XT NBR. OF FILE -- STARTING ---
> > FILE ID SQ TRACKS TYPE CCCC.HH TRACK
> > -------------------------------------- -- ------- ---- ---------------
> > *** VOL1 AND IPL *** 1 SYST 0.00 0
> > *** VTOC EXTENT *** 1 SYST 0.01 1
> > Z9999992.VSAMDSPC.TB9D0FF0.TAB36EED 50083 VSAM 0.02 2
> >
> > TOTAL AMOUNT OF FREE-SPACE ON THIS VOLUME: 0 TRACKS
> >
> >Sincerely,
> >
> >Dave Clark
> >***@dapsco.com
> >
> >DAPSCO Information Systems
> >3110 Kettering Boulevard
> >Dayton, Ohio 45439
> >[phone]
> >
>
> >
> >Rich Smrcina wrote:
> >
> >
> >
> >
> >...I would put that track at the end of a cylinder...
> >
> >...VSEVTOC(0,14,1)...
> >
> >
> >
> Then Rich, what are you going to put on tracks from (0,1) to (0,13), huh?
--
Rich Smrcina
Sr. Systems Engineer
Sytek Services - A Division of DSG
Milwaukee, WI
rsmrcina at wi.rr.com
rsmrcina at dsgroup.com

Catch the WAVV! Stay for requirements and the free-for-all.
Update your zSeries skills in 4 days for a very reasonable price.
WAVV 2004 in Chattanooga, TN
April 30-May 4, 2004
For details see http://www.wavv.org

[Silver]

Bob,


init unit(cuu) volid(BAS567) nvfy dvtoc(cyl,track,length/end)
If you specify DVTOC(END) The Vtoc is the last Cylinder at the end of the
volume. Elsewhere you can specify the exactly location in Cyl (started by
zero) track & length:
0,14,1 caused vtoc to be placed at cylinder track 14 length 1 track, at the
end of the first cylinder and of the minimum size, suitable for VSAM. For
Sequential Files I suggest
0,1,14 Note that on 0,0,1 there is the ID of Volume.
On VM you need to vary off/on the device after the ICKDSF IN Virtual machine
so the CP read the new VOLume ID, or assign to SYSTEM.

Silver Ravaioli
Cassa dei Risparmi di Forlì S.p.A.
Italy
----- Original Message -----
From: <***@sungard.com>
To: "VSE Discussion List" <vse-***@Lehigh.EDU>
Sent: Wednesday, October 01, 2003 5:47 PM
Subject: Re: Adding DASD Volumes to VSE


>
> Thanks for Info. Using ICKDSF how can I make sure the VTOC size is the
> same as the other volumes? Also on my VM system the volume shows as
ESA40D,
> on VSE system I need it as Volume BAS567. What would my INIT statement
> look like?
>
> Bob Bailey
>
>

[R***@aol.com]

<<...I would put that track at the end of a cylinder...>>

I agree. BTW, A one track VTOC will hold about 50 VTOC entries on a 3380.

[Tom Duerbusch]

I don't know how this plays out in the real world of RAID, but back in
the old days....

When you opened a vtoc entry, a hardware scan was issued against the
VTOC to find the DSN. If the DSN wasn't found, the scan came back when
it reached the end of the cylinder. If the DSN was found, it came back
much quicker. However, it had to search again to see if the DSN had a
second extent.

So, you always put the VTOC at the end of a cylinder to prevent the
hardware scans from running all 15 tracks, even if the VTOC was only 1
track.

Great for regular datasets. I just don't know if the VTOC entry for a
VSAM dataspace is actually ever opened (other then when the define space
was done).

I always put the VTOC on Cylinder 0 (except for DOSRES/SYSWK1) because
the VOLUME record (occupying the first 2-3 tracks) garbaged up that
cylinder anyway. So I use the bottom part of the cylinder for the VTOC.
Also, back in the old days, the volid wasn't cached by VSE. So when an
ASSGN SYSXXX,DISK,VOL=YYYYYYY,SHR was encountered, VSE scanned all the
dasd in the pub table looking for the volume. Once it found it, and the
disk heads were now on cylinder 0 anyway, it could look for the vtoc
while it was there.

But things may be different now.

Tom Duerbusch
THD Consulting

>>> ***@dapsco.com 10/01/03 03:02PM >>>




> ...I would put that track at the end of a cylinder...

For what real and beneficial purpose in this case? If the volume is
fully
occupied by VSAM space, I see no reason to have the VTOC end on a
cylinder
boundary. No additional files can be added to the VTOC. I don't see
what
performance or access issues there can be for a volume layout as I
have
demonstrated. Naturally, other volume layouts have additional
considerations -- but I don't see any for the specific case of a
volume
that is dedicated entirely to suballocated VSAM space. Please
enlighten me
of any issues that might pertain to this specific case.

Sincerely,

Dave Clark
***@dapsco.com

DAPSCO Information Systems
3110 Kettering Boulevard
Dayton, Ohio 45439
[phone]

[i***@dapsco.com]

owner-vse-***@Lehigh.EDU wrote on 10/01/2003 04:57:40 PM:
> Dave,
>
> <<Please enlighten me of any issues that might pertain to this
> specific case.>>
>
> I believe this is still the case. When VSE reads the VTOC the entire
> cylinder is read. So, if it starts at the beginning of a cylinder
> you'll read 14 tracks more than you needed to.
>
> Bob Botsis

Except that I don't think that is a major consideration for a volume
that is entirely dedicated to suballocated VSAM space ... which was my most
basic premise for making my statement in the first place. In this
scenario, there will be no (or very, very little) call for scanning the
VTOC. No other datasets will be on the volume and VSAM itself does not use
the VTOC for its operations.

Feel free to correct me if I am wrong in this.

Sincerely,

Dave Clark
***@dapsco.com

DAPSCO Information Systems
3110 Kettering Boulevard
Dayton, Ohio 45439
[phone]

[R***@aol.com]

Dave,


<<Please enlighten me of any issues that might pertain to this specific
case.>>

I believe this is still the case. When VSE reads the VTOC the entire cylinder
is read. So, if it starts at the beginning of a cylinder you'll read 14
tracks more than you needed to.


Bob Botsis
Kroger Company
513.745.5487
***@aol.com
(I read and I remember,
I do and I understand)

[Steve Huggins]

Dave,

If you have a disk space management package, I would exclude that volume
from the pool of volumes that are searched for datasets!

Steve

At 05:06 PM 10/1/2003 -0400, you wrote:
>owner-vse-***@Lehigh.EDU wrote on 10/01/2003 04:57:40 PM:
> > Dave,
> > <<Please enlighten me of any issues that might pertain to this
> > specific case.>>

[i***@dapsco.com]

owner-vse-***@Lehigh.EDU wrote on 10/01/2003 05:14:25 PM:
> Dave,

> If you have a disk space management package, I would exclude that volume
> from the pool of volumes that are searched for datasets!

> Steve

I would think that an exclusion wouldn't be required since I would
expect the norm to be that only those volumes that *were* to be searched by
a space management package would be listed as such (i.e., the default would
*not* be to search all volumes) -- at least, that is the way that I have
done it in other shops.

However, here, we use only VSAM Managed-SAM in that capacity -- no
DYNAM, EPIC or otherwise. Of 62 3390-0A volumes, we have 48 of them
defined as entirely dedicated to suballocated VSAM space. Those 48 have
single-track VTOCs while the other 14 have full-cylinder VTOCs.

Sincerely,

Dave Clark
***@dapsco.com

DAPSCO Information Systems
3110 Kettering Boulevard
Dayton, Ohio 45439
[phone]

[Tony Thigpen]

Dynam, for one, by default, will scan all drives in a system trying to find
a file once the file is not found in the pool volumes.

Tony Thigpen.
Thigpen Enterprises, Inc.
Developers of VSE2PDF
http://www.vse2pdf.com


-----Original Message-----
From: owner-vse-***@Lehigh.EDU [mailto:owner-vse-***@Lehigh.EDU]On Behalf Of
***@dapsco.com
Sent: Wednesday, October 01, 2003 5:28 PM
To: VSE Discussion List
Subject: Re: Adding DASD Volumes to VSE






owner-vse-***@Lehigh.EDU wrote on 10/01/2003 05:14:25 PM:
> Dave,

> If you have a disk space management package, I would exclude that volume
> from the pool of volumes that are searched for datasets!

> Steve

I would think that an exclusion wouldn't be required since I would
expect the norm to be that only those volumes that *were* to be searched by
a space management package would be listed as such (i.e., the default would
*not* be to search all volumes) -- at least, that is the way that I have
done it in other shops.

However, here, we use only VSAM Managed-SAM in that capacity -- no
DYNAM, EPIC or otherwise. Of 62 3390-0A volumes, we have 48 of them
defined as entirely dedicated to suballocated VSAM space. Those 48 have
single-track VTOCs while the other 14 have full-cylinder VTOCs.

Sincerely,

Dave Clark
***@dapsco.com

DAPSCO Information Systems
3110 Kettering Boulevard
Dayton, Ohio 45439
[phone]

[R***@aol.com]

Dave,


<<Feel free to correct me if I am wrong in this.>>

I can't cuz I dunno what VSAM does. And there's also Steve's point. Don't get
me wrong. I too create one track VTOC's for volumes that are going to be
totally dedicated to VSAM. It's just that I create them at the back of the
cylinder probably cuz THAT'S THE WAY I LEARNT. If VSAM doesn't bother accessing the
VTOC then it won't matter. If VSE uses DEF EXTENT then it won't matter.


Bob Botsis
Kroger Company
513.745.5487
***@aol.com
(I read and I remember,
I do and I understand)

[r***@sungard.com]

Hi Roland,

Thanks for the INFO. Here's a picture of the dasd I would like to make 567
look like. What would my INIT card to be for 567? WE do our INIT on the VM
system.

VOL=BAS565(565) --- BIM-FAQS/ASO ON-LINE VTOC DISPLAY --- 02654-15
*** SORTED BY EXTENT *** START ENDING NUMBER FIL
--DATES--
-------- FILE NAME -------- CCCCC-HH CCCCC-HH
TRACKS TYP CRE EXP
*** LABEL AREA *** 00000-00 00000-00
1
*** FREE SPACE *** 00000-01 00000-14
14
TESTDEMO.ADABAS.WORK 00001-00 00400-14 6000
DA 01086 99365
TESTDEMO.ADABAS.TEMP 00401-00 00800-14 6000
DA 01086 99365
TESTDEMO.ADABAS.SORT 00801-00 01200-14 6000
DA 01086 99365
*** FREE SPACE *** 01201-00 01224-14
360
BIM.AUD.DMP 01225-00 01248-14
360 SD 03271 03271E
TEST.ADABAS.SORT 01249-00 02648-14
21000 DA 03067 99365
*** FREE SPACE *** 02649-00 02652-14
60
*** VTOC EXTENT *** 02653-00 02653-14
15




Roland Chung
<***@rogers.co To: "VSE Discussion List" <vse-***@Lehigh.EDU>
m> cc:
Sent by: Subject: Re: Adding DASD Volumes to VSE
owner-vse-***@Lehig
h.EDU


10/01/2003 01:48
PM
Please respond to
vse-l






Hi Robert,

It depends on how the DASDs are being defined to the VSE machine.
- using MDISK statement?
If the MDISK is being defined on a real 3380 with 885 cylinders, then
you can only allocate from cylinder 1 for 884 cylinders to your VSE
machine. CP must have cylinder 0. So, no matter what VOLID you put on
the MDISK using ICKDSF, you always see 2 VOLIDs. One from VM and the
other from VSE. Note: you only see 884 cylinders from VSE.

- using DEDICATE statement? (or using CP ATTACH command)
VSE machine owns all cylinders. Once you have initialized the disk with
ICKDSF, VM and VSE sees the same VOLID.

You do not have to make sure the VTOC size is the same as other volumes.
It depends on your planned usage for that disk. Traditionally, most
people use 15 tracks. Or 14 tracks if put it on cylinder 0 because
cylinder 0 track 0 is for the hardware. I would use only 4 tracks on a
3380 if I planned to put a few files on it. Such as use the whole disk
for VSAM space.

The sample ICKDSF INIT statement using only 4 track for VTOC is as follow:
init unit(567) nomap nvfy dvtoc(0,1,4) volid(bas567)

I hope this helps. Regards,

***@sungard.com wrote:

>Thanks for Info. Using ICKDSF how can I make sure the VTOC size is the
>same as the other volumes? Also on my VM system the volume shows as
ESA40D,
>on VSE system I need it as Volume BAS567. What would my INIT statement
>look like?
>
>Bob Bailey
>
>
>
>
>

--
...Roland Chung
Senior Technical Specialist (S/390,VM/VSE,DB2/VSE&VM)
MAXC Consultants Inc.

<< Check my website for sports memorabilia at:
http://www.signaturestars.com/14317 >>
** Wanta earn some extra cash, check this out:
http://www.signaturestars.com/a/14317 **

[Stephen Frazier]

Your INIT card is:

init unit(567) nomap nvfy dvtoc(2653,0,15) volid(bas567)

***@sungard.com wrote:

> Hi Roland,
>
> Thanks for the INFO. Here's a picture of the dasd I would like to make 567
> look like. What would my INIT card to be for 567? WE do our INIT on the VM
> system.
>
> VOL=BAS565(565) --- BIM-FAQS/ASO ON-LINE VTOC DISPLAY --- 02654-15
> *** SORTED BY EXTENT *** START ENDING NUMBER FIL
> --DATES--
> -------- FILE NAME -------- CCCCC-HH CCCCC-HH
> TRACKS TYP CRE EXP

> *** VTOC EXTENT *** 02653-00 02653-14
> 15
>
>


--
Stephen Frazier
Information Technology Unit
Oklahoma Department of Corrections
3400 Martin Luther King
Oklahoma City, Ok, 73111-4298
Tel.: [phone]
Fax: [phone]
Pager: [phone]
email: stevef%doc.state.ok.us

[Roland Chung]

Hi Robert, looks like 567 is a Mdisk with 2654 cylinders. CP owns
cylinders 0. Therefore, after ICKDSF, you would see 2 VOLIDs.

OK, your INIT statement would look like:

init unit(567) nomap nvfy dvtoc(bas567) dvtoc(2653,0,14)

Regards,

***@sungard.com wrote:

>Hi Roland,
>
>Thanks for the INFO. Here's a picture of the dasd I would like to make 567
>look like. What would my INIT card to be for 567? WE do our INIT on the VM
>system.
>
>VOL=BAS565(565) --- BIM-FAQS/ASO ON-LINE VTOC DISPLAY --- 02654-15
> *** SORTED BY EXTENT *** START ENDING NUMBER FIL
>--DATES--
>-------- FILE NAME -------- CCCCC-HH CCCCC-HH
>TRACKS TYP CRE EXP
> *** LABEL AREA *** 00000-00 00000-00
>1
>---- snipped ---
> *** FREE SPACE *** 02649-00 02652-14
>60
> *** VTOC EXTENT *** 02653-00 02653-14
>15
>
>
>
>

--
...Roland Chung
Senior Technical Specialist (S/390,VM/VSE,DB2/VSE&VM)
MAXC Consultants Inc.

<< Check my website for sports memorabilia at:
http://www.signaturestars.com/14317 >>
** Wanta earn some extra cash, check this out:
http://www.signaturestars.com/a/14317 **

[Silver]

Hi all,

It's NOT necessary to dedicate cylinder 0 to CP in VM/VSE!
Here we define Full pack Minidisk (mdisk ... 0000 end ....) to our VSE.
So we have only one VOLID and one VTOC and we can see it with normal CP
command Q DASD from VM.
The volume(s) can be formatted with ICKDSF from CMS withe the DVTOC
parameter as in VSE, but without possibilty of destroy dasd that are
working!

Silver Ravaioli
Cassa dei Risparmi di Forl S.p.A.
Italy
----- Original Message -----
From: "Roland Chung" <***@rogers.com>
Newsgroups: bit.listserv.vse-l
Sent: Thursday, October 02, 2003 2:05 AM
Subject: Re: Adding DASD Volumes to VSE


> Hi Robert, looks like 567 is a Mdisk with 2654 cylinders. CP owns
> cylinders 0. Therefore, after ICKDSF, you would see 2 VOLIDs.
>
> OK, your INIT statement would look like:
>
> init unit(567) nomap nvfy dvtoc(bas567) dvtoc(2653,0,14)
>
> Regards,
>
> ***@sungard.com wrote:
>
> >Hi Roland,
> >
> >Thanks for the INFO. Here's a picture of the dasd I would like to make
567
> >look like. What would my INIT card to be for 567? WE do our INIT on the
VM
> >system.
> >
> >VOL=BAS565(565) --- BIM-FAQS/ASO ON-LINE VTOC DISPLAY ---
02654-15
> > *** SORTED BY EXTENT *** START ENDING NUMBER
FIL
> >--DATES--
> >-------- FILE NAME -------- CCCCC-HH CCCCC-HH
> >TRACKS TYP CRE EXP
> > *** LABEL AREA *** 00000-00 00000-00
> >1
> >---- snipped ---
> > *** FREE SPACE *** 02649-00 02652-14
> >60
> > *** VTOC EXTENT *** 02653-00 02653-14
> >15
> >
> >
> >
> >
>
> --
> ...Roland Chung
> Senior Technical Specialist (S/390,VM/VSE,DB2/VSE&VM)
> MAXC Consultants Inc.
>
> << Check my website for sports memorabilia at:
> http://www.signaturestars.com/14317 >>
> ** Wanta earn some extra cash, check this out:
> http://www.signaturestars.com/a/14317 **
>
>
>

[Roland Chung]

Hi Silver, you are right, it is not necessary to dedicate cylinder 0 to
CP especially it is a full pack minidisk. I was just stating what I
found from Robert's DITTO DVT display.

Personnally, I prefer MDISK vs DEDICATE for the flexibility that gives
me. That is it - personnally.

I do not quite understood your last statement: "....but without
possibilty of destroy dasd that are working!". Could you please
elaborate it? Thanks.

Regards,

Silver wrote:

>Hi all,
>
>It's NOT necessary to dedicate cylinder 0 to CP in VM/VSE!
>Here we define Full pack Minidisk (mdisk ... 0000 end ....) to our VSE.
>So we have only one VOLID and one VTOC and we can see it with normal CP
>command Q DASD from VM.
>The volume(s) can be formatted with ICKDSF from CMS withe the DVTOC
>parameter as in VSE, but without possibilty of destroy dasd that are
>working!
>
>Silver Ravaioli
>Cassa dei Risparmi di Forl S.p.A.
>Italy
>
>

--
...Roland Chung
Senior Technical Specialist (S/390,VM/VSE,DB2/VSE&VM)
MAXC Consultants Inc.

<< Check my website for sports memorabilia at:
http://www.signaturestars.com/14317 >>
** Wanta earn some extra cash, check this out:
http://www.signaturestars.com/a/14317 **

[Silver]

Hi Roland.

> "....but without possibilty of destroy dasd that are working!". Could you
please
> elaborate it? Thanks.
It's easy. If I run ickdsf in a VSE whith a lot of DASD if I mistake address
I can destroy a good dasd! When I work in CMS ICKDSF require that the dasd
was ATTACHED. To do an attach the dasd mut be detached from SYSTEM, without
link. In my CMS, with write permission, there are only this DASD. So if I
don't change the address of ICKDSF I get an error message not the
distruction of a good dasd.
In my shop MDISK is a "Strategic choice" why we work with 5 VSE like if they
were one everyone share all dasd.
----- Original Message -----
From: "Roland Chung" <***@rogers.com>
To: "VSE Discussion List" <vse-***@Lehigh.EDU>
Sent: Thursday, October 02, 2003 5:04 PM
Subject: Re: Adding DASD Volumes to VSE


> Hi Silver, you are right, it is not necessary to dedicate cylinder 0 to
> CP especially it is a full pack minidisk. I was just stating what I
> found from Robert's DITTO DVT display.
>
> Personnally, I prefer MDISK vs DEDICATE for the flexibility that gives
> me. That is it - personnally.
>
> I do not quite understood your last statement: "....but without
> possibilty of destroy dasd that are working!". Could you please
> elaborate it? Thanks.
>
> Regards,
>
> Silver wrote:
>
> >Hi all,
> >
> >It's NOT necessary to dedicate cylinder 0 to CP in VM/VSE!
> >Here we define Full pack Minidisk (mdisk ... 0000 end ....) to our VSE.
> >So we have only one VOLID and one VTOC and we can see it with normal CP
> >command Q DASD from VM.
> >The volume(s) can be formatted with ICKDSF from CMS withe the DVTOC
> >parameter as in VSE, but without possibilty of destroy dasd that are
> >working!
> >
> >Silver Ravaioli
> >Cassa dei Risparmi di Forl S.p.A.
> >Italy
> >
> >
>
> --
> ...Roland Chung
> Senior Technical Specialist (S/390,VM/VSE,DB2/VSE&VM)
> MAXC Consultants Inc.
>
> << Check my website for sports memorabilia at:
> http://www.signaturestars.com/14317 >>
> ** Wanta earn some extra cash, check this out:
> http://www.signaturestars.com/a/14317 **
>
>
>

[Ed Martin]

Hello EVeryone,

I agree with Dave. You only need one track if the entire volume is going
to be VSAM. But I have a question, I was always told that you should out
the vtoc so that it ended on a cylinder boundry because VSE would read until
the end of the Cylinder no matter what.

Is this still true? And for a one track vtoc is would be a small thing
anyway, but I was just wondering.

Ed Martin
Dowling Consulting Group

-----Original Message-----
From: ***@dapsco.com
To: VSE Discussion List
Sent: 10/1/03 2:48 PM
Subject: Re: Adding DASD Volumes to VSE





> I would use only 4 tracks on a 3380 if I planned to put a
> few files on it. Such as use the whole disk for VSAM space.

Why 4 tracks? If using the entire volume for VSAM space, I only use 1
track (because the VSAM space only requires a single file entry in the
VTOC).

// ASSGN SYS001,DISK,TEMP,VOL=IDD113,SHR
// EXEC PGM=ICKDSF,SIZE=AUTO
INIT SYSNAME(SYS001) VERIFY(IDD113) VOLID(IDD113) -
VSEVTOC(0,1,1) NOCHK NOMAP PURGE
/* EOD

The following is for our 3390's but the same concept applies to 3380:

VTOC DISPLAY FOR VOLUME: IDD113 DATE: 10/01/2003 TIME: 14:42:24
TYPE: 3390-0A ECKD XT NBR. OF FILE -- STARTING ---
FILE ID SQ TRACKS TYPE CCCC.HH TRACK
-------------------------------------- -- ------- ---- ---------------
*** VOL1 AND IPL *** 1 SYST 0.00 0
*** VTOC EXTENT *** 1 SYST 0.01 1
Z9999992.VSAMDSPC.TB9D0FF0.TAB36EED 50083 VSAM 0.02 2

TOTAL AMOUNT OF FREE-SPACE ON THIS VOLUME: 0 TRACKS

Sincerely,

Dave Clark
***@dapsco.com

DAPSCO Information Systems
3110 Kettering Boulevard
Dayton, Ohio 45439
[phone]

[i***@dapsco.com]

owner-vse-***@Lehigh.EDU wrote on 10/02/2003 12:01:03 PM:
> I agree with Dave. You only need one track if the entire volume is going
> to be VSAM. But I have a question, ... Is this still true?

I think Stephen Frazier summed it up pretty well for releases of VSE/ESA:

owner-vse-***@Lehigh.EDU wrote on 10/01/2003 06:01:54 PM:
> The SEARCH command that is used to find the DSN has 2 options. Search
> one track only or search to the end of the cylinder. If the VTOC is ONE
> track in length then it doesn't mater where the VTOC is located. Only
> one track is searched by one I/O command. If the VTOC is larger than 1
> track but less than one cylinder it should end on a cylinder boundary.
> The search to end of cylinder form will be used and a again only one I/O
> command is needed to find the DSN. If the VTOC is larger than one
> cylinder then multiple I/O commands are needed to find the DSN in the
> VTOC. If the volume will only have a few files in the VTOC you will get
> fastest access with a 1 track VTOC no mater where it is placed. You
> should not allocate more than 1 track to the VTOC unless you expect that
> you will have more files defined in the VTOC than can fit in one track.
> If you allocate a 2 track (or larger) VTOC when it is not needed then
> you are forcing the system to use the search until end of cylinder form
> which runs longer than the search one track form. The worst performance
> is when you have a VTOC that is smaller than one cylinder and crosses a
> cylinder boundary because that forces the system to issues multiple I/O
> commands.

Sincerely,

Dave Clark
***@dapsco.com

DAPSCO Information Systems
3110 Kettering Boulevard
Dayton, Ohio 45439
[phone]

[r***@sungard.com]

Hi Roland,

Thanks for the info on the init. I ran it on our VM system , then IPLed the
VSE system. But there is no volid.
The volume command on VSE
shows:

AR 0015 CUU CODE DEV.-TYP VOLID USAGE SHARED STATUS CAPACITY
AR 0015 566 6E 3380-K BAS566 USED SHARED
2654 CYL
AR 0015 567 6E 3380-K *NONE* USED SHARED
2654 CYL <<<<<<<<<<<<
AR 0015 568 6E 3380-K *NONE* UNUSED SHARED
2654 CYL <<<<<<<<<<<<

Regards
Bob

[A***@avon.com]

// JOB ICKDSF
// PAUSE EOB TO INITIALIZE ADDRESS xxx
// ASSGN SYS111,your addrs here
// EXEC ICKDSF
INIT SYSNAME(SYS111) NOMAP PURGE DOSVTOC(END) VOLID(xxxxxx) NVFY
/*
/&

will put vtoc at end of pack




***@sun
gard.com To: "VSE Discussion List" <vse-***@Lehigh.EDU>
Sent by: cc:
owner-vse-***@Lehig Subject: Re: Adding DASD Volumes to VSE
h.EDU


10/06/2003 11:55
AM
Please respond to
vse-l







Hi Roland,

Thanks for the info on the init. I ran it on our VM system , then IPLed the
VSE system. But there is no volid.
The volume command on VSE
shows:

AR 0015 CUU CODE DEV.-TYP VOLID USAGE SHARED STATUS CAPACITY
AR 0015 566 6E 3380-K BAS566 USED SHARED
2654 CYL
AR 0015 567 6E 3380-K *NONE* USED SHARED
2654 CYL <<<<<<<<<<<<
AR 0015 568 6E 3380-K *NONE* UNUSED SHARED
2654 CYL <<<<<<<<<<<<

Regards
Bob

[Roland Chung]

Hi Robert, it is funny. Have you captured the console when you performed
the ICKDSF? If you have, could you post it.

What do you see when you use DITTO DVT on 567 & 568? Could you post it,
please.

As August suggested, you can inititalze the DASD using VSE.

Could you also post the MDISK statements for 567 & 568. Thanks.



***@avon.com wrote:

>// JOB ICKDSF
>// PAUSE EOB TO INITIALIZE ADDRESS xxx
>// ASSGN SYS111,your addrs here
>// EXEC ICKDSF
> INIT SYSNAME(SYS111) NOMAP PURGE DOSVTOC(END) VOLID(xxxxxx) NVFY
>/*
>/&
>
>will put vtoc at end of pack
>
>
>
>
> ***@sun
> gard.com To: "VSE Discussion List" <vse-***@Lehigh.EDU>
> Sent by: cc:
> owner-vse-***@Lehig Subject: Re: Adding DASD Volumes to VSE
> h.EDU
>
>
> 10/06/2003 11:55
> AM
> Please respond to
> vse-l
>
>
>
>
>
>
>
>Hi Roland,
>
>Thanks for the info on the init. I ran it on our VM system , then IPLed the
>VSE system. But there is no volid.
>The volume command on VSE
>shows:
>
>AR 0015 CUU CODE DEV.-TYP VOLID USAGE SHARED STATUS CAPACITY
>AR 0015 566 6E 3380-K BAS566 USED SHARED
>2654 CYL
>AR 0015 567 6E 3380-K *NONE* USED SHARED
>2654 CYL <<<<<<<<<<<<
>AR 0015 568 6E 3380-K *NONE* UNUSED SHARED
>2654 CYL <<<<<<<<<<<<
>
>Regards
>Bob
>
>
>
>
>
>
>
>
>
>
>

--
...Roland Chung
Senior Technical Specialist (S/390,VM/VSE,DB2/VSE&VM)
MAXC Consultants Inc.

<< Check my website for sports memorabilia at:
http://www.signaturestars.com/14317 >>
** Wanta earn some extra cash, check this out:
http://www.signaturestars.com/a/14317 **

[Ed Martin]

Hello Robert and Roland,

I am just picking up on this. So You have a dasd that you want to
change the name and add it to VSE. You have done the ICKDSF. Added it via
either a VSE Console link or Attach command.
After you have done the DVCUP command, did you do a ONLINE AR command?

ONLINE xxx

I have a z/VM 4.3 system and we had the same problem. I was not
there but the ONLINE command did the trick.

Edward M. Martin
Dowling Consulting Group
1295 Corporate Drive
Hudson, Ohio 44236
330-656-1136
330-650-0172 (fax)



-----Original Message-----
From: Roland Chung [mailto:***@rogers.com]
Sent: Monday, October 06, 2003 1:41 PM
To: VSE Discussion List
Subject: Re: Adding DASD Volumes to VSE


Hi Robert, it is funny. Have you captured the console when you performed
the ICKDSF? If you have, could you post it.

What do you see when you use DITTO DVT on 567 & 568? Could you post it,
please.

As August suggested, you can inititalze the DASD using VSE.

Could you also post the MDISK statements for 567 & 568. Thanks.



***@avon.com wrote:

>// JOB ICKDSF
>// PAUSE EOB TO INITIALIZE ADDRESS xxx
>// ASSGN SYS111,your addrs here
>// EXEC ICKDSF
> INIT SYSNAME(SYS111) NOMAP PURGE DOSVTOC(END) VOLID(xxxxxx) NVFY
>/*
>/&
>
>will put vtoc at end of pack
>
>
>
>

> ***@sun

> gard.com To: "VSE Discussion
List" <vse-***@Lehigh.EDU>
> Sent by: cc:

> owner-vse-***@Lehig Subject: Re: Adding DASD
Volumes to VSE
> h.EDU

>

>

> 10/06/2003 11:55

> AM

> Please respond to

> vse-l

>

>

>
>
>
>
>
>Hi Roland,
>
>Thanks for the info on the init. I ran it on our VM system , then IPLed the
>VSE system. But there is no volid.
>The volume command on VSE
>shows:
>
>AR 0015 CUU CODE DEV.-TYP VOLID USAGE SHARED STATUS CAPACITY
>AR 0015 566 6E 3380-K BAS566 USED SHARED
>2654 CYL
>AR 0015 567 6E 3380-K *NONE* USED SHARED
>2654 CYL <<<<<<<<<<<<
>AR 0015 568 6E 3380-K *NONE* UNUSED SHARED
>2654 CYL <<<<<<<<<<<<
>
>Regards
>Bob
>
>
>
>
>
>
>
>
>
>
>

--
...Roland Chung
Senior Technical Specialist (S/390,VM/VSE,DB2/VSE&VM)
MAXC Consultants Inc.

<< Check my website for sports memorabilia at:
http://www.signaturestars.com/14317 >>
** Wanta earn some extra cash, check this out:
http://www.signaturestars.com/a/14317 **

[Roland Chung]

Hi Ed, I Thought about that. But, Robert said he did an IPL of the VSE
machine. The DASDs should have been treated as ONLINE. That is why I
said "funny".

I asked for the DITTO DVT and the MDISK statement because I kinda
suspect the misalignment of the MDISK statement. ;-)

Ed Martin wrote:

>Hello Robert and Roland,
>
> I am just picking up on this. So You have a dasd that you want to
>change the name and add it to VSE. You have done the ICKDSF. Added it via
>either a VSE Console link or Attach command.
>After you have done the DVCUP command, did you do a ONLINE AR command?
>
> ONLINE xxx
>
> I have a z/VM 4.3 system and we had the same problem. I was not
>there but the ONLINE command did the trick.
>
>Edward M. Martin
>Dowling Consulting Group
>1295 Corporate Drive
>Hudson, Ohio 44236
>330-656-1136
>330-650-0172 (fax)
>
>
>
>-----Original Message-----
>From: Roland Chung [mailto:***@rogers.com]
>Sent: Monday, October 06, 2003 1:41 PM
>To: VSE Discussion List
>Subject: Re: Adding DASD Volumes to VSE
>
>
>Hi Robert, it is funny. Have you captured the console when you performed
>the ICKDSF? If you have, could you post it.
>
>What do you see when you use DITTO DVT on 567 & 568? Could you post it,
>please.
>
>As August suggested, you can inititalze the DASD using VSE.
>
>Could you also post the MDISK statements for 567 & 568. Thanks.
>
>
>
>***@avon.com wrote:
>
>
>
>>// JOB ICKDSF
>>// PAUSE EOB TO INITIALIZE ADDRESS xxx
>>// ASSGN SYS111,your addrs here
>>// EXEC ICKDSF
>>INIT SYSNAME(SYS111) NOMAP PURGE DOSVTOC(END) VOLID(xxxxxx) NVFY
>>/*
>>/&
>>
>>will put vtoc at end of pack
>>
>>
>>
>>
>>
>>
>
>
>
>> ***@sun
>>
>>
>
>
>
>> gard.com To: "VSE Discussion
>>
>>
>List" <vse-***@Lehigh.EDU>
>
>
>> Sent by: cc:
>>
>>
>
>
>
>> owner-vse-***@Lehig Subject: Re: Adding DASD
>>
>>
>Volumes to VSE
>
>
>> h.EDU
>>
>>
>
>
>
>
>
>
>
>
>
>> 10/06/2003 11:55
>>
>>
>
>
>
>> AM
>>
>>
>
>
>
>> Please respond to
>>
>>
>
>
>
>> vse-l
>>
>>
>
>
>
>
>
>
>
>
>
>>
>>
>>
>>Hi Roland,
>>
>>Thanks for the info on the init. I ran it on our VM system , then IPLed the
>>VSE system. But there is no volid.
>>The volume command on VSE
>>shows:
>>
>>AR 0015 CUU CODE DEV.-TYP VOLID USAGE SHARED STATUS CAPACITY
>>AR 0015 566 6E 3380-K BAS566 USED SHARED
>>2654 CYL
>>AR 0015 567 6E 3380-K *NONE* USED SHARED
>>2654 CYL <<<<<<<<<<<<
>>AR 0015 568 6E 3380-K *NONE* UNUSED SHARED
>>2654 CYL <<<<<<<<<<<<
>>
>>Regards
>>Bob
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
>
>

--
...Roland Chung
Senior Technical Specialist (S/390,VM/VSE,DB2/VSE&VM)
MAXC Consultants Inc.

<< Check my website for sports memorabilia at:
http://www.signaturestars.com/14317 >>
** Wanta earn some extra cash, check this out:
http://www.signaturestars.com/a/14317 **

[A***@avon.com]

is it defined as a full pack mdisk
is it linked or dedicated




Roland Chung
<***@rogers.co To: "VSE Discussion List" <vse-***@Lehigh.EDU>
m> cc:
Sent by: Subject: Re: Adding DASD Volumes to VSE
owner-vse-***@Lehig
h.EDU


10/06/2003 02:12
PM
Please respond to
vse-l






Hi Ed, I Thought about that. But, Robert said he did an IPL of the VSE
machine. The DASDs should have been treated as ONLINE. That is why I
said "funny".

I asked for the DITTO DVT and the MDISK statement because I kinda
suspect the misalignment of the MDISK statement. ;-)

Ed Martin wrote:

>Hello Robert and Roland,
>
> I am just picking up on this. So You have a dasd that you
want to
>change the name and add it to VSE. You have done the ICKDSF. Added it
via
>either a VSE Console link or Attach command.
>After you have done the DVCUP command, did you do a ONLINE AR command?
>
> ONLINE xxx
>
> I have a z/VM 4.3 system and we had the same problem. I was
not
>there but the ONLINE command did the trick.
>
>Edward M. Martin
>Dowling Consulting Group
>1295 Corporate Drive
>Hudson, Ohio 44236
>330-656-1136
>330-650-0172 (fax)
>
>
>
>-----Original Message-----
>From: Roland Chung [mailto:***@rogers.com]
>Sent: Monday, October 06, 2003 1:41 PM
>To: VSE Discussion List
>Subject: Re: Adding DASD Volumes to VSE
>
>
>Hi Robert, it is funny. Have you captured the console when you performed
>the ICKDSF? If you have, could you post it.
>
>What do you see when you use DITTO DVT on 567 & 568? Could you post it,
>please.
>
>As August suggested, you can inititalze the DASD using VSE.
>
>Could you also post the MDISK statements for 567 & 568. Thanks.
>
>
>
>***@avon.com wrote:
>
>
>
>>// JOB ICKDSF
>>// PAUSE EOB TO INITIALIZE ADDRESS xxx
>>// ASSGN SYS111,your addrs here
>>// EXEC ICKDSF
>>INIT SYSNAME(SYS111) NOMAP PURGE DOSVTOC(END) VOLID(xxxxxx) NVFY
>>/*
>>/&
>>
>>will put vtoc at end of pack
>>
>>
>>
>>
>>
>>
>
>
>
>> ***@sun
>>
>>
>
>
>
>> gard.com To: "VSE Discussion
>>
>>
>List" <vse-***@Lehigh.EDU>
>
>
>> Sent by: cc:
>>
>>
>
>
>
>> owner-vse-***@Lehig Subject: Re: Adding DASD
>>
>>
>Volumes to VSE
>
>
>> h.EDU
>>
>>
>
>
>
>
>
>
>
>
>
>> 10/06/2003 11:55
>>
>>
>
>
>
>> AM
>>
>>
>
>
>
>> Please respond to
>>
>>
>
>
>
>> vse-l
>>
>>
>
>
>
>
>
>
>
>
>
>>
>>
>>
>>Hi Roland,
>>
>>Thanks for the info on the init. I ran it on our VM system , then IPLed
the
>>VSE system. But there is no volid.
>>The volume command on VSE
>>shows:
>>
>>AR 0015 CUU CODE DEV.-TYP VOLID USAGE SHARED STATUS CAPACITY
>>AR 0015 566 6E 3380-K BAS566 USED SHARED
>>2654 CYL
>>AR 0015 567 6E 3380-K *NONE* USED SHARED
>>2654 CYL <<<<<<<<<<<<
>>AR 0015 568 6E 3380-K *NONE* UNUSED SHARED
>>2654 CYL <<<<<<<<<<<<
>>
>>Regards
>>Bob
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
>
>

--
...Roland Chung
Senior Technical Specialist (S/390,VM/VSE,DB2/VSE&VM)
MAXC Consultants Inc.

<< Check my website for sports memorabilia at:
http://www.signaturestars.com/14317 >>
** Wanta earn some extra cash, check this out:
http://www.signaturestars.com/a/14317 **