Re: Can not snapshot volume on zOS

[Schuh, Richard]

If it contains the user directory, it should have a minimal VTOC. An ICKDSF 
FORMAT CPVOL (or simply a CPFMTXA) should place a 2 or 3 record VTOC 
immediately following the volume label (which is at cyl 0, track 0, record 3). 
Can you do a DDR TYPE or PRINT of that track to see what is really there?


Regards,
Richard Schuh

 -Original Message-
From:   The IBM z/VM Operating System [mailto:[EMAIL PROTECTED]  On Behalf Of 
Jon Brock
Sent:   Friday, May 26, 2006 12:10 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject:Can not snapshot volume on zOS

I have another little issue that has cropped up.  My normal backup 
procedure for right now is to vary the DASD online to z/OS, then use 
FDR/Instant to snapshot them and back them up.  I have created a new guest and 
loaded RHEL onto it.  I can back up all of the volumes except for one; the 
snapshot for that one fails with a message "I/O ERROR READING THE VTOC."  No 
snapshot means no backup.  This volume is part of a volume group that contains 
the /usr directory.
Is there a way I could recreate a VTOC on this volume without having to 
redo the logical volume?


Thanks,
Jon

Can not snapshot volume on zOS

[Jon Brock]

I have another little issue that has cropped up.  My normal backup 
procedure for right now is to vary the DASD online to z/OS, then use 
FDR/Instant to snapshot them and back them up.  I have created a new guest and 
loaded RHEL onto it.  I can back up all of the volumes except for one; the 
snapshot for that one fails with a message "I/O ERROR READING THE VTOC."  No 
snapshot means no backup.  This volume is part of a volume group that contains 
the /usr directory.
Is there a way I could recreate a VTOC on this volume without having to 
redo the logical volume?


Thanks,
Jon

Re: This may interest some.

[Ray Mullins]

Those copyright statements are in LE modules.  Since C under z/OS is
LE-enabled, it establishes an LE environment, which includes abend
intercepts, etc.

I just did a test on z/OS 1.7, and there are only 2 copyrights, in CEESTART
and CEEBINIT.  

Of course, since the example is actually a subroutine, I tried it with
changing TEST to main.  Then I get 5 copyrights, all in LE routines.

Interestingly, there is a #pragma comment copyright where you can insert
your own copyright text in the object code generated by the compiler.

Later,
Ray 



-- 
M. Ray Mullins 
Roseville, CA, USA 
http://www.catherdersoftware.com/
http://www.mrmullins.big-bear-city.ca.us/ 
http://www.the-bus-stops-here.org/ 

German is essentially a form of assembly language consisting entirely of far
calls heavily accented with throaty guttural sounds. 

--ilvi 



 

Re: z/VM 5.2 and the S disk

[Steve Gentry]

No, they don't HAVE to go on the S disk, but every site has a unique setup.  SYSPROF and the two home grown EXECs  control how users
logon and what they are given access to.  All of this is imbed into how the rest of the system interacts.  I'm planning on converting to 5.2 this
weekend and I don't want to introduce this type of change.  I'm sure I'll have a few "opportunities"  come Tuesday when users return from
3 days off and forgetting their passwords,  ad  infinitum
Besides, Chuckie hasn't said anything about it, so I figure I can't get myself into  too much trouble.
You all have a good weekend, I know where I'll be.  8-\
Steve

"We've thought of everything, what could possibly go wrong."







Rich Greenberg <[EMAIL PROTECTED]>
Sent by: The IBM z/VM Operating System 
05/26/2006 12:59 PM
Please respond to The IBM z/VM Operating System

        
        To:        IBMVM@LISTSERV.UARK.EDU
        cc:        
        Subject:        Re: z/VM 5.2  and the S disk


On: Fri, May 26, 2006 at 09:59:17AM -0500,Steve Gentry Wrote:

} Thanks all for the response.  I needed to change the mode from S1  to S2.

Steve, fine but do these files HAVE to be on the S-Disk?  By convention
(and Mother's rules) only IBM things go on the S disk.  User things
normally go on the Y disk.

-- 
Rich Greenberg  N Ft Myers, FL, USA richgr atsign panix.com  + 1 239 543 1353
Eastern time.  N6LRT  I speak for myself & my dogs only.    VM'er since CP-67
Canines:Val, Red & Shasta (RIP),Red, Zero & Casey, Siberians  Owner:Chinook-L
Atlanta Siberian Husky Rescue. www.panix.com/~richgr/   Asst Owner:Sibernet-L

Re: z/VM 5.2 and the S disk

[Rich Greenberg]

On: Fri, May 26, 2006 at 09:59:17AM -0500,Steve Gentry Wrote:

} Thanks all for the response.  I needed to change the mode from S1  to S2.

Steve, fine but do these files HAVE to be on the S-Disk?  By convention
(and Mother's rules) only IBM things go on the S disk.  User things
normally go on the Y disk.

-- 
Rich Greenberg  N Ft Myers, FL, USA richgr atsign panix.com  + 1 239 543 1353
Eastern time.  N6LRT  I speak for myself & my dogs only.VM'er since CP-67
Canines:Val, Red & Shasta (RIP),Red, Zero & Casey, Siberians  Owner:Chinook-L
Atlanta Siberian Husky Rescue. www.panix.com/~richgr/   Asst Owner:Sibernet-L

Re: Upgrading zVM 5.1 to 5.2

[Jon Brock]

Thanks for the reply, Alan.  I have reordered z/VM 5.2 (I think).  I am sure I 
will have loads more questions when it gets here and I get a chance to work on 
it.

And my favorite editor is probably Gene Weingarten, although I think he's a 
columnist now.


Thanks,
Jon




It's worth pointing out that there is nothing that upgrades your 5.1 
system to a 5.2 system, per se.  Rather, you perform a fresh 5.2 install 
on another set of packs and either bring your 5.1 configuration to your 
5.2 system (implemented by the 5.2 migration utilitites), or you take the 
5.2 components over to your 5.1 system.  The 5.2 version of the Automated 
Installation book comes when you order the z/VM 5.2 product (not service).

(And I would rather discuss the subjective nature of reality, religion, 
global warming, sex education in public schools, stem cell research, the 
influence of math on science and engineering, conservative vs. liberal 
politics, and, if pushed to the limit of discretion, even which text 
editior is the best, before talking about which of those two migration 
philosophies is "best".  But, everyone, PLEASE don't use this post as an 
excuse to talk about your fave editor!)

Re: EMC disk on z9 with z/VM

[Romanowski, John (OFT)]

We use some EMC dasd (3390-mod3 and 3390-mod1) on a Z9 with VM5.1 and
VM5.2 without problems unless you use 3390-mod1's (and maybe 3380's? we
don't) 
Don't know if EMC officially supports the Z9/EMC combo.

If you use mod1's in the EMC and then you put on the very recent
new-function PTF for  apar VM63854 which added support for ESS D/T2105,
DS6000 ( D/T1750) , and DS8000 (D/T2107)  disk subsystems in their
native control unit modes then VM will likely complain with msg
HCPCPN6290I that your mod1  is "unsupported" disk when you try to vary
the disk online.

The PTF updates the table of supported controller/dasd models and
doesn't list a 3390-mod1 as supported in a 2105 ESS controller. EMC lets
you define a mod1 in their ESS, IBM doesn't.

Apar VM64017 (no PTF yet as of today) will add native support for
3390mod1's in some EMC controllers. 




This e-mail, including any attachments, may be confidential, privileged or 
otherwise legally protected. It is intended only for the addressee. If you 
received this e-mail in error or from someone who was not authorized to send it 
to you, do not disseminate, copy or otherwise use this e-mail or its 
attachments.  Please notify the sender immediately by reply e-mail and delete 
the e-mail from your system.


-Original Message-

From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Jim Elliott <[EMAIL PROTECTED]>
Sent: Friday, May 26, 2006 10:01 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: EMC disk on z9 with z/VM

I have a customer looking at a z9 for z/VM, but EMC only
"qualifies" the z9 for z/OS (per their web site at
http://www.emc.com/interoperability/index.jsp). Is anyone on this
list using EMC disk on a z9 with z/VM? Were you able to get a
statement of support from EMC?

Jim

Re: EMC disk on z9 with z/VM

[Schuh, Richard]

Jim,

We are using EMC on a z990. Their dasd, at least at this level, can run without 
any mods so long as you are not running Shadow Copy on VM. Pardon me if the 
name Shadow Copy is incorrect - we also have HDS and IBM dasd and I seldom 
remember which name goes with which vendor. The HDS version has similar (to 
EMC) requirements. The modifications are for CCW op codes that would fail in 
CCW translation on an unmodified CP. 

The mods are really straight forward and IBM was kind to the other vendors in 
the transition from 4.4 to 5.2. The modules being modified were not 
resequenced, at least not anywhere near the areas being modified. The 4.4 mods 
fit the 5.2 system unchanged.

Regards,
Richard Schuh

 -Original Message-
From:   The IBM z/VM Operating System [mailto:[EMAIL PROTECTED]  On Behalf Of 
Jim Elliott <[EMAIL PROTECTED]>
Sent:   Friday, May 26, 2006 7:01 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject:EMC disk on z9 with z/VM

I have a customer looking at a z9 for z/VM, but EMC only
"qualifies" the z9 for z/OS (per their web site at
http://www.emc.com/interoperability/index.jsp). Is anyone on this
list using EMC disk on a z9 with z/VM? Were you able to get a
statement of support from EMC?

Jim

Re: z/VM 5.2 and the S disk

[Jim Bohnsack]

Whaddya mean "What about  SYSTEM  NETID  ?"

Yes, use the same procedure to replace SYSTEM NETID as mode 2 if that's 
what you are asking about.  The same for the SYSTEM SEGID.  Neither of them 
go into the INSTSEG, so don't worry about that.


If you are wondering what it's used for, it's used by the CMS IDENTIFY 
command as well as NOTE and SENDFILE.  It associates your cpuid with your 
node name and the userid of the RSCS machine.


Jim

At 12:36 PM 5/26/2006, you wrote:

This is a multipart message in MIME format.
--=_alternative 005B3F3A0525717A_=
Content-Type: text/plain; charset="us-ascii"

What about  SYSTEM  NETID  ?





Rob van der Heij <[EMAIL PROTECTED]>
Sent by: The IBM z/VM Operating System 
05/26/2006 10:00 AM
Please respond to The IBM z/VM Operating System


To: IBMVM@LISTSERV.UARK.EDU
cc:
Subject:Re: z/VM 5.2 and the S disk


On 5/26/06, Jim Bohnsack <[EMAIL PROTECTED]> wrote:

> Steve--I'm not on 5.2 yet, but the procedure that I've used for many
years
> is to save the execs or whatever you need on the 190 disk as filemode
> 2.  That's important.  Then using the SAMPNSS EXEC that typically is
> shipped on the MAINT 493 disk, create a new NSS (Named Saved System)
> skeleton by entering "SAMPNSS CMS".  At that point, having remembered to
> relink 190 as RR, enter "I 190 CLEAR PARM SAVESYS CMS".  That will write
> out the directory information for 190 and 19E in the new CMS NSS.  When
you
> IPL CMS, you'll be seeing the new execs.

You need to rebuild the CMS nucleus because the directory of the
S-disk is part of the nucleus. But you also need to be aware of
INSTSEG that holds copies of S-disk programs in storage. If you would
modify one of the programs on the S-disk it would not work. So to make
such changes you would need to log a local mod to the file, build it,
rebuild INSTSEG, etc.

Rob
--
Rob van der Heij
Velocity Software, Inc
http://velocitysoftware.com/



--=_alternative 005B3F3A0525717A_=
Content-Type: text/html; charset="us-ascii"


What about  SYSTEM  NETID 
 ?








Rob van der Heij 
<[EMAIL PROTECTED]>
Sent by: The IBM z/VM Operating System 


05/26/2006 10:00 AM
Please respond to The IBM z/VM 
Operating System


        
        To:   
     IBMVM@LISTSERV.UARK.EDU
        cc:   
     
        Subject: 
       Re: z/VM 5.2 and the S disk



On 5/26/06, Jim Bohnsack 
<[EMAIL PROTECTED]> wrote:


> Steve--I'm not on 5.2 yet, but the procedure that I've used for many 
years

> is to save the execs or whatever you need on the 190 disk as filemode
> 2.  That's important.  Then using the SAMPNSS EXEC that 
typically is

> shipped on the MAINT 493 disk, create a new NSS (Named Saved System)
> skeleton by entering "SAMPNSS CMS".  At that point, 
having remembered to
> relink 190 as RR, enter "I 190 CLEAR PARM SAVESYS CMS". 
 That will write
> out the directory information for 190 and 19E in the new CMS NSS. 
 When you

> IPL CMS, you'll be seeing the new execs.

You need to rebuild the CMS nucleus because the directory of the
S-disk is part of the nucleus. But you also need to be aware of
INSTSEG that holds copies of S-disk programs in storage. If you would
modify one of the programs on the S-disk it would not work. So to make
such changes you would need to log a local mod to the file, build it,
rebuild INSTSEG, etc.

Rob
-- 
Rob van der Heij
Velocity Software, Inc
http://velocitysoftware.com/



--=_alternative 005B3F3A0525717A_=--


Jim Bohnsack
Cornell Univ.
(607) 255-1760

Re: z/VM 5.2 and the S disk

[Schuh, Richard]

I echo
Mike’s sentiment about keeping the S-disk as clean as possible. It is
guaranteed to change with the release of VM. We have a tools repository disk
that is accessed for our users by SYSPROF magic (we have created some exit
points to call our routines.) That is where we place the bulk of the tools that
are of general interest. It is similar to Mike’s 19C, except that most of the
tools are supported by their creators or their creators’ groups.

 

Regards,

Richard Schuh

 

-Original
Message-
From: The IBM z/VM Operating
System [mailto:[EMAIL PROTECTED]On
Behalf Of Mike Walter
Sent: Friday, May 26, 2006 7:10 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: z/VM 5.2 and the S
disk

 


Steve (G.), 

Others have properly alerted you to
the filemode-2 requirement (that goes for public files on the Y-disk, too!).  The
S and Y-disks are accessed to only show files with filemode 2 (e.g.
"ACCESS 19E Y/S * * Y2"). 

You didn't say why you were adding files to the S-disk.  In
my 29 years working on VM there have been very, very few reasons to add files
the S-disk (190).  Other than updating the "SYSTEM NETID S2" and
"SYSTEM SEGID S2" on our z/VM 5.2 system we didn't update *any* files
on S-disk.  The only things placed on our S-disk are files IBM places
there (sometimes during maintenance). 

The Y-disk (19E) is where we place
Independent Software Vendor and other system-wide shared, supported local
files.  Way, way back, IBM used to place their Licensed Products on
MAINT's 319 disk (we didn't want to give up another filemode for that, and
moved them to the 19E disk).   

We do (personal choice) have a MAINT
19C disk, where we place various "lesser-supported" local and public
domain tools (many from the IBM VM Download page or VM Workshop tapes).  That
MAINT 19C disk is clearly documented as being supported on a best-effort-basis
and should not be used for production-quality applications.     

Mike Walter 
Hewitt Associates 
The opinions expressed herein are
mine alone, not my employer's. 

In reply to: 









From: The IBM z/VM Operating
System [mailto:[EMAIL PROTECTED] On
Behalf Of Steve Gentry
Sent: Friday, May 26, 2006 10:10 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: z/VM 5.2 and the S disk


Hello.  I am installing 5.2 and need to add a couple of EXEC's to the S
disk (mdisk MAINT 190)   I've accessed  190 
as another mode, added my two execs and rebuilt the CMS saved segment.  Logged
off of the user, logged

back on.  When I do a  FILELIST  on the S drive, the EXEC's
don't show up, but when I access 190 in another mode 
they are there.  Therefore, I don't think they are being executed.  What
do I need to do to get these EXEC's 
to show up on the S drive? 
Thanks, 
Steve G. 


The information contained in this e-mail and any accompanying documents may
contain information that is confidential or otherwise protected from
disclosure. If you are not the intended recipient of this message, or if this
message has been addressed to you in error, please immediately alert the sender
by reply e-mail and then delete this message, including any attachments. Any
dissemination, distribution or other use of the contents of this message by
anyone other than the intended recipient is strictly prohibited.

Re: z/VM 5.2 and the S disk

[Steve Gentry]

What about  SYSTEM  NETID  ?







Rob van der Heij <[EMAIL PROTECTED]>
Sent by: The IBM z/VM Operating System 
05/26/2006 10:00 AM
Please respond to The IBM z/VM Operating System

        
        To:        IBMVM@LISTSERV.UARK.EDU
        cc:        
        Subject:        Re: z/VM 5.2 and the S disk


On 5/26/06, Jim Bohnsack <[EMAIL PROTECTED]> wrote:

> Steve--I'm not on 5.2 yet, but the procedure that I've used for many years
> is to save the execs or whatever you need on the 190 disk as filemode
> 2.  That's important.  Then using the SAMPNSS EXEC that typically is
> shipped on the MAINT 493 disk, create a new NSS (Named Saved System)
> skeleton by entering "SAMPNSS CMS".  At that point, having remembered to
> relink 190 as RR, enter "I 190 CLEAR PARM SAVESYS CMS".  That will write
> out the directory information for 190 and 19E in the new CMS NSS.  When you
> IPL CMS, you'll be seeing the new execs.

You need to rebuild the CMS nucleus because the directory of the
S-disk is part of the nucleus. But you also need to be aware of
INSTSEG that holds copies of S-disk programs in storage. If you would
modify one of the programs on the S-disk it would not work. So to make
such changes you would need to log a local mod to the file, build it,
rebuild INSTSEG, etc.

Rob
-- 
Rob van der Heij
Velocity Software, Inc
http://velocitysoftware.com/

Tcp/IP

[P. L. Lovely]

With a STATE of SYN-RECEIVED for a INTCLIEN connection.
In z/VM TCPIP - can/should you increase QUEUE for half-open connections?
   

Re: z/VM 5.2 and the S disk

[Steve Gentry]

I was afraid of that, because that is what seems to be happening, i.e., the changes aren't working.
I have the instructions on how to do local mods.







Rob van der Heij <[EMAIL PROTECTED]>
Sent by: The IBM z/VM Operating System 
05/26/2006 10:00 AM
Please respond to The IBM z/VM Operating System

        
        To:        IBMVM@LISTSERV.UARK.EDU
        cc:        
        Subject:        Re: z/VM 5.2 and the S disk


On 5/26/06, Jim Bohnsack <[EMAIL PROTECTED]> wrote:

> Steve--I'm not on 5.2 yet, but the procedure that I've used for many years
> is to save the execs or whatever you need on the 190 disk as filemode
> 2.  That's important.  Then using the SAMPNSS EXEC that typically is
> shipped on the MAINT 493 disk, create a new NSS (Named Saved System)
> skeleton by entering "SAMPNSS CMS".  At that point, having remembered to
> relink 190 as RR, enter "I 190 CLEAR PARM SAVESYS CMS".  That will write
> out the directory information for 190 and 19E in the new CMS NSS.  When you
> IPL CMS, you'll be seeing the new execs.

You need to rebuild the CMS nucleus because the directory of the
S-disk is part of the nucleus. But you also need to be aware of
INSTSEG that holds copies of S-disk programs in storage. If you would
modify one of the programs on the S-disk it would not work. So to make
such changes you would need to log a local mod to the file, build it,
rebuild INSTSEG, etc.

Rob
-- 
Rob van der Heij
Velocity Software, Inc
http://velocitysoftware.com/

Re: z/VM 5.2 and the S disk

[Rob van der Heij]

On 5/26/06, Jim Bohnsack <[EMAIL PROTECTED]> wrote:


Steve--I'm not on 5.2 yet, but the procedure that I've used for many years
is to save the execs or whatever you need on the 190 disk as filemode
2.  That's important.  Then using the SAMPNSS EXEC that typically is
shipped on the MAINT 493 disk, create a new NSS (Named Saved System)
skeleton by entering "SAMPNSS CMS".  At that point, having remembered to
relink 190 as RR, enter "I 190 CLEAR PARM SAVESYS CMS".  That will write
out the directory information for 190 and 19E in the new CMS NSS.  When you
IPL CMS, you'll be seeing the new execs.


You need to rebuild the CMS nucleus because the directory of the
S-disk is part of the nucleus. But you also need to be aware of
INSTSEG that holds copies of S-disk programs in storage. If you would
modify one of the programs on the S-disk it would not work. So to make
such changes you would need to log a local mod to the file, build it,
rebuild INSTSEG, etc.

Rob
--
Rob van der Heij
Velocity Software, Inc
http://velocitysoftware.com/

Re: VSWITCH failover woes

[Mary Ellen Carollo]

VM APAR VM64021 has been opened to address this problem. 
Mary Ellen Carollo
z/VM Development
IBM Endicott

On Wed, 10 May 2006 11:23:02 -0500, Brian Nielsen 
<[EMAIL PROTECTED]> wrote:

>This morning the LAN team was performing maintenance on the external 
CISCO 
>box that my OSA's connect to.  The logs shows the VSWITCH controllers 

>dutifully failing over between the 2 OSA cards each time the CISCO was 

>rebooted.  After several failover iterations I get HCPSWU2832E messages 

>and it never does anything after that.  The log shows this at the end:
>
>
>05:55:36 HCPSWU2830I VSWITCH SYSTEM SWITCH02 status is devices attached.

>HCPSWU2830I DTCVSW1 is VSWITCH controller.
>05:55:36 HCPSWU2832E The connection for VSWITCH SYSTEM SWITCH02 is not 

>active.
>HCPSWU2832E None of the RDEVs are available working QDIO OSA Express 
>devices.
>05:55:36 OSA 0500 DETACHED DTCVSW1 0500 BY DTCVSW1
>05:55:36 OSA 0501 DETACHED DTCVSW1 0501 BY DTCVSW1
>05:55:36 HCPSWU2832E The connection for VSWITCH SYSTEM SWITCH02 is not 

>active.
>HCPSWU2832E None of the RDEVs are available working QDIO OSA Express 
>devices.
>05:55:36 OSA 0502 DETACHED DTCVSW1 0502 BY DTCVSW1
>
>
>Doing Q VSWITCH showed that there was no longer a controller associated 

>with the VSWITCHes and that the devices were in "Error: Detached" status
.
>
>I had to do a SET VSWITCH SWITCH02 CONNECT to bring it back into working
 
>order.
>
>So, my questions are:
>
>1) What conditions in the OSA cause CP to think the RDEVs are no 
>longer "working QDIO OSA Express devices"?
>
>2) Is there anything I can do on the VM side to make this recover more 

>reliably when the LAN team messes with their CISCO box?  I'm not 
currently 
>running PROP, and would prefer not to start just for this.
>
>I'll probably open up a problem with the support center, but wanted to 

>check in here first.
>
>Brian Nielsen
>
=
===

Re: z/VM 5.2 and the S disk

[Mike Walter]

Steve (G.),

Others have properly alerted you to
the filemode-2 requirement (that goes for public files on the Y-disk, too!).
 The S and Y-disks are accessed to only show files with filemode 2
(e.g. "ACCESS 19E Y/S * * Y2").

You didn't say why you were adding
files to the S-disk.  In my 29 years working on VM there have been
very, very few reasons to add files the S-disk (190).  Other than
updating the "SYSTEM NETID S2" and "SYSTEM SEGID S2"
on our z/VM 5.2 system we didn't update *any* files on S-disk.  The
only things placed on our S-disk are files IBM places there (sometimes
during maintenance).

The Y-disk (19E) is where we place Independent
Software Vendor and other system-wide shared, supported local files.  Way,
way back, IBM used to place their Licensed Products on MAINT's 319 disk
(we didn't want to give up another filemode for that, and moved them to
the 19E disk).  

We do (personal choice) have a MAINT
19C disk, where we place various "lesser-supported" local and
public domain tools (many from the IBM VM Download page or VM Workshop
tapes).  That MAINT 19C disk is clearly documented as being supported
on a best-effort-basis and should not be used for production-quality applications.
   

Mike Walter
Hewitt Associates
The opinions expressed herein are mine
alone, not my employer's.

In reply to:

From: The IBM z/VM Operating System
[mailto:[EMAIL PROTECTED] On Behalf Of Steve Gentry
Sent: Friday, May 26, 2006 10:10 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: z/VM 5.2 and the S disk


Hello.  I am installing 5.2 and need to add a couple of EXEC's to
the S disk (mdisk MAINT 190)   I've accessed  190 
as another mode, added my two execs and rebuilt the CMS saved segment.
 Logged off of the user, logged 
back on.  When I do a  FILELIST  on the S drive, the EXEC's
don't show up, but when I access 190 in another mode

they are there.  Therefore, I don't think they are being executed.
 What do I need to do to get these EXEC's 
to show up on the S drive? 
Thanks, 
Steve G.

 
The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited.

Re: EMC disk on z9 with z/VM

[Stracka, James (GTI)]

Yes to the first.  I dunno to the second.  

-Original Message-
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Jim Elliott <[EMAIL PROTECTED]>
Sent: Friday, May 26, 2006 10:01 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: EMC disk on z9 with z/VM


I have a customer looking at a z9 for z/VM, but EMC only "qualifies" the
z9 for z/OS (per their web site at
http://www.emc.com/interoperability/index.jsp). Is anyone on this list
using EMC disk on a z9 with z/VM? Were you able to get a statement of
support from EMC?

Jim


If you are not an intended recipient of this e-mail, please notify the sender, 
delete it and do not read, act upon, print, disclose, copy, retain or 
redistribute it. Click here for important additional terms relating to this 
e-mail. http://www.ml.com/email_terms/

EMC disk on z9 with z/VM

[Jim Elliott <[EMAIL PROTECTED]>]

I have a customer looking at a z9 for z/VM, but EMC only
"qualifies" the z9 for z/OS (per their web site at
http://www.emc.com/interoperability/index.jsp). Is anyone on this
list using EMC disk on a z9 with z/VM? Were you able to get a
statement of support from EMC?

Jim

Re: z/VM 5.2 and the S disk

[Steve Gentry]

Thanks all for the response.  I needed to change the mode from S1  to   S2.
Steve G.

Honor super omnia

Re: A question on VM/LINUX/DFDSS(MVS)

[Charlie Crochet]

Mace,

Add the COPYVOLID parameter.

COPYVOLID specifies that the volser of the original source volume will be
 
copied to the target volume.  If you don't specify COPYVOLID, the target 

volume volser will remain the same as it was before the restore.
  
Charlie
State of Wyoming

Re: z/VM 5.2 and the S disk

[Hughes, Jim - OIT]

Make sure the
execs have a mode number of 2 as in “S2”.

 



___
Jim Hughes
603-271-5586
"Impossible is just an opinion."













From: The IBM z/VM Operating System
[mailto:[EMAIL PROTECTED] On Behalf Of
Steve Gentry
Sent: Friday, May 26, 2006 10:10
AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: z/VM 5.2 and the S disk



 


Hello.  I am installing 5.2 and need to add a
couple of EXEC's to the S disk (mdisk MAINT 190)   I've accessed  190

as
another mode, added my two execs and rebuilt the CMS saved segment.  Logged
off of the user, logged 
back
on.  When I do a  FILELIST  on the S drive, the EXEC's don't
show up, but when I access 190 in another mode 
they
are there.  Therefore, I don't think they are being executed.  What
do I need to do to get these EXEC's 
to
show up on the S drive? 
Thanks,

Steve
G.

Re: z/VM 5.2 and the S disk

[Jim Bohnsack]

Steve--I'm not on 5.2 yet, but the procedure that I've used for many years 
is to save the execs or whatever you need on the 190 disk as filemode 
2.  That's important.  Then using the SAMPNSS EXEC that typically is 
shipped on the MAINT 493 disk, create a new NSS (Named Saved System) 
skeleton by entering "SAMPNSS CMS".  At that point, having remembered to 
relink 190 as RR, enter "I 190 CLEAR PARM SAVESYS CMS".  That will write 
out the directory information for 190 and 19E in the new CMS NSS.  When you 
IPL CMS, you'll be seeing the new execs.

Jim

At 10:09 AM 5/26/2006, you wrote:

This is a multipart message in MIME format.
--=_alternative 004DC7B60525717A_=
Content-Type: text/plain; charset="us-ascii"

Hello.  I am installing 5.2 and need to add a couple of EXEC's to the S
disk (mdisk MAINT 190)   I've accessed  190
as another mode, added my two execs and rebuilt the CMS saved segment.
Logged off of the user, logged
back on.  When I do a  FILELIST  on the S drive, the EXEC's don't show up,
but when I access 190 in another mode
they are there.  Therefore, I don't think they are being executed.  What
do I need to do to get these EXEC's
to show up on the S drive?
Thanks,
Steve G.
--=_alternative 004DC7B60525717A_=
Content-Type: text/html; charset="us-ascii"


Hello.  I am installing 5.2 and 
need to add a couple of EXEC's to the S disk (mdisk MAINT 190)   I've 
accessed  190 
as another mode, added my two execs and 
rebuilt the CMS saved segment.  Logged off of the user, logged
back on.  When I do a 
 FILELIST  on the S drive, the EXEC's don't show up, but when I 
access 190 in another mode
they are there.  Therefore, I 
don't think they are being executed.  What do I need to do to get 
these EXEC's 

to show up on the S drive?
Thanks,
Steve G.
--=_alternative 004DC7B60525717A_=--


Jim Bohnsack
Cornell Univ.
(607) 255-1760

Re: z/VM 5.2 and the S disk

[Imler, Steven J]

Steve,
 
You need to be sure the FileMode is S2 (not S1) or the materials will not show 
up.
 

JR (Steven) 
Imler
CA
Senior Software Engineer
Tel:  +1 703 708 
3479
Fax:  +1 703 708 
3267
[EMAIL PROTECTED]


From: The IBM z/VM Operating System 
[mailto:[EMAIL PROTECTED] On Behalf Of Steve 
GentrySent: Friday, May 26, 2006 10:10 AMTo: 
IBMVM@LISTSERV.UARK.EDUSubject: z/VM 5.2 and the S 
disk
Hello.  I am installing 5.2 and 
need to add a couple of EXEC's to the S disk (mdisk MAINT 190)   I've 
accessed  190 as another mode, 
added my two execs and rebuilt the CMS saved segment.  Logged off of the 
user, logged back on.  When I do a 
 FILELIST  on the S drive, the EXEC's don't show up, but when I access 
190 in another mode they are there. 
 Therefore, I don't think they are being executed.  What do I need to 
do to get these EXEC's to show up on the 
S drive? Thanks, Steve G.

Re: This may interest some.

[Gary Eheman]

On Thu, 25 May 2006 09:31:45 -0500, Lucius, Leland
<[EMAIL PROTECTED]> wrote:


>Oh well.  I guess IBM owns everything...  :-)  Actually, since no copyri
ght was
>attached to the article, I guess Alfred was within his rights to use it 
freely,
>but to claim ownership  That just seems wrong.
>
>Leland
>

I laughed when I read this. It appears they assert (repeatedly) copyright
 on
nothing, too.

Someone shared with me once that a load module on z/OS for this C program

contains not fewer than 10 IBM copyright statements.

int TEST( void )
{  return(0); }

Probably the same on VM.
--
Gary Eheman

Re: z/VM 5.2 and the S disk

[David Kreuter]

What EXECs are you adding to the S disk? Executables should only be 
added to this disk through CMS installing or servicing.


Your problem technically may be that fm number is 1, which will not show 
up on fm letter S as the disk is access fm  number 2.

David
Steve Gentry wrote:



Hello.  I am installing 5.2 and need to add a couple of EXEC's to the 
S disk (mdisk MAINT 190)   I've accessed  190
as another mode, added my two execs and rebuilt the CMS saved segment. 
 Logged off of the user, logged
back on.  When I do a  FILELIST  on the S drive, the EXEC's don't show 
up, but when I access 190 in another mode
they are there.  Therefore, I don't think they are being executed. 
 What do I need to do to get these EXEC's

to show up on the S drive?
Thanks,
Steve G.



No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.394 / Virus Database: 268.7.1/348 - Release Date: 25/05/2006
 

z/VM 5.2 and the S disk

[Steve Gentry]

Hello.  I am installing 5.2 and need to add a couple of EXEC's to the S disk (mdisk MAINT 190)   I've accessed  190 
as another mode, added my two execs and rebuilt the CMS saved segment.  Logged off of the user, logged
back on.  When I do a  FILELIST  on the S drive, the EXEC's don't show up, but when I access 190 in another mode
they are there.  Therefore, I don't think they are being executed.  What do I need to do to get these EXEC's 
to show up on the S drive?
Thanks,
Steve G.

Re: Broadcast storms on OSD with TCP/IP under z/VM 5.2 an PROXYARP to VSE/ESA

[Peter . Webb]

Why are you using PROXYARP? It is a way to
get around routing restrictions, it is not a solution with long-term viability.

 

-Original
Message-
From: The IBM z/VM Operating
System [mailto:[EMAIL PROTECTED] On
Behalf Of Ronald A. Hammer
Sent: May 26, 2006 08:07
To: IBMVM@LISTSERV.UARK.EDU
Subject: Broadcast storms on OSD
with TCP/IP under z/VM 5.2 an PROXYARP to VSE/ESA

 

Hi @ all,



 





we've done change in
our TCP/IP network (changing IP Addresses from 10.1.1.0 to 10.1.120.0).
With in that change we also migrated from routing between z/VM and VSE/ESA to
PROXYARP.





 





Now we have the extensive broadcast
storms on out network.





 





If we plug put the Ethernet
connection from our OSD the broadcast storms end, after replugin the OSD the
broadcast storms raise again.





 





Does anyone have any idea where that
com from.





 





For informational purpose I attached
the OSD configuration an TCP/IP definitions.





 





Thanks for any answers,





 





 





Ronald







The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material.  Any review, retransmission, dissemination or other use of or taking of any action in reliance upon, this information by persons or entities other than the intended recipient or delegate is strictly prohibited.  If you received this in error, please contact the sender and delete the material from any computer.  The integrity and security of this message cannot by guaranteed on the Internet.  The Sender accepts no liability for the content of this e-mail, or for the consequences of any actions taken on basis of the information provided.  The recipient should check this e-mail and any attachments for the presence of viruses.  The sender accepts no liability for any damage caused by any virus transmitted by this e-mail.  This disclaimer is the property of the TTC and must not be altered or circumvented in any manner.

Re: Moving a guest to new DASD

[Paul Raulerson]

.. and somewhat along the same lines...Does anyone have any idea how to retireve the data off an LVM which has had one of it's volumes mistakenly formatted in z/VM while the instance was down?  Yes, I know, the best way to handle this type of situation is never to be there...The data I need slipped between our backup windows.  -Paul
--- Begin Message ---
Alan Altmark <[EMAIL PROTECTED]> wrote:
>dasdfmt should work reliably without any dependence on prior format.  I 
>notice in the dasdfmt code commentary (on Developerworks) that it doesn't
>format track 0.  Maybe that's ok, maybe not.

>Or maybe it's the dasd device driver causing the problem.

On at least some kernel levels, with at least some DASD device drivers, 
never-formatted DASD won't come ACTIVE -- it stays READY forever (yes, those 
states seem backwards: ACTIVE is "better" than READY).  Hence, I suspect, the 
original admonition.

...phsiii


--- End Message ---

Re: Moving a guest to new DASD

[Phil Smith III]

Alan Altmark <[EMAIL PROTECTED]> wrote:
>dasdfmt should work reliably without any dependence on prior format.  I 
>notice in the dasdfmt code commentary (on Developerworks) that it doesn't 
>format track 0.  Maybe that's ok, maybe not.

>Or maybe it's the dasd device driver causing the problem.

On at least some kernel levels, with at least some DASD device drivers, 
never-formatted DASD won't come ACTIVE -- it stays READY forever (yes, those 
states seem backwards: ACTIVE is "better" than READY).  Hence, I suspect, the 
original admonition.

...phsiii