Re: InformationWeek survey

2009-05-08 Thread Mike Walter
Sure... go ahead... reduce the odds of my winning a touch iPod by sharing 
this with the whole world (at least the whole world that MATTERS!)  ;-)

Mike Walter



"Glenn Knickerbocker"  

Sent by: "The IBM z/VM Operating System" 
05/08/2009 01:25 PM
Please respond to
"The IBM z/VM Operating System" 



To
IBMVM@LISTSERV.UARK.EDU
cc

Subject
InformationWeek survey






In case you haven't seen it, System z suggests you might want to take a
few minutes to participate in this survey:

  http://informationweek.mainframes.sgizmo.com/

Somewhere around 40 questions about your use of mainframes, and a
drawing for a free iPod Touch.

¬R






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. All messages 
sent to and from this e-mail address may be monitored as permitted by 
applicable law and regulations to ensure compliance with our internal policies 
and to protect our business. E-mails are not secure and cannot be guaranteed to 
be error free as they can be intercepted, amended, lost or destroyed, or 
contain viruses. You are deemed to have accepted these risks if you communicate 
with us by e-mail. 


Re: Location of MINIOPT in directory

2009-05-08 Thread Shedlock, George
Thank you.

George Shedlock Jr
AEGON Information Technology
AEGON USA
502-560-3541
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf 
Of Bill Munson
Sent: Friday, May 08, 2009 2:29 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Location of MINIOPT in directory


George,

The MINIOPT statement is an extension to the MDISK statement and must 
immediately follow an MDISK statement that defines a non-full-pack minidisk

Bill Munson
Sr. z/VM Systems Programmer
Brown Brothers Harriman & CO.
525 Washington Blvd.
Jersey City, NJ 07310
201-418-7588



"Shedlock, George" 
Sent by: The IBM z/VM Operating System 

05/08/2009 02:23 PM
Please respond to
The IBM z/VM Operating System 


To

IBMVM@LISTSERV.UARK.EDU

cc

Subject

Location of MINIOPT in directory







Is there any specific location for a MINIOPT directory statement?

For example, I have the following statements in my user directory:

 MDISK 0B00 ...
 MINIOPT PAV FB00
 MDISK 0B01 ...
 MINIOPT PAV FB01

Do I need to maintain that order of statements? Can I group all of the MDISK 
statements together and all of the MINIOPT statements separately?

George Shedlock Jr
AEGON Information Technology
AEGON USA
502-560-3541


*** IMPORTANT NOTE * The 
opinions expressed in this message and/or any attachments are those of the 
author and not necessarily those of Brown Brothers Harriman & Co., its 
subsidiaries and affiliates BBH. There is no guarantee that this message is 
either private or confidential, and it may have been altered by unauthorized 
sources without your or our knowledge. Nothing in the message is capable or 
intended to create any legally binding obligations on either party and it is 
not intended to provide legal advice. BBH accepts no responsibility for loss or 
damage from its use, including damage from virus. 
***


InformationWeek survey

2009-05-08 Thread Glenn Knickerbocker
In case you haven't seen it, System z suggests you might want to take a
few minutes to participate in this survey:

  http://informationweek.mainframes.sgizmo.com/

Somewhere around 40 questions about your use of mainframes, and a
drawing for a free iPod Touch.

¬R


Re: Location of MINIOPT in directory

2009-05-08 Thread Demeritt, Yvonne
The MINIOPT statement must immediately follow the MDISK statement it
goes with. It's looked at as an extension of the MDISK statement. 

So yes, the order must be maintained.

Yvonne


Yvonne DeMeritt
CA
 

-Original Message-
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On
Behalf Of Shedlock, George
Sent: Friday, May 08, 2009 2:23 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Location of MINIOPT in directory

Is there any specific location for a MINIOPT directory statement?

For example, I have the following statements in my user directory:

  MDISK 0B00 ...
  MINIOPT PAV FB00  
  MDISK 0B01 ...
  MINIOPT PAV FB01

Do I need to maintain that order of statements? Can I group all of the
MDISK statements together and all of the MINIOPT statements separately?


George Shedlock Jr
AEGON Information Technology
AEGON USA
502-560-3541


Re: Location of MINIOPT in directory

2009-05-08 Thread Bill Munson
George,

The MINIOPT statement is an extension to the MDISK statement and must 
immediately follow an MDISK statement that defines a non-full-pack 
minidisk

Bill Munson 
Sr. z/VM Systems Programmer 
Brown Brothers Harriman & CO.
525 Washington Blvd. 
Jersey City, NJ 07310 
201-418-7588





"Shedlock, George"  
Sent by: The IBM z/VM Operating System 
05/08/2009 02:23 PM
Please respond to
The IBM z/VM Operating System 


To
IBMVM@LISTSERV.UARK.EDU
cc

Subject
Location of MINIOPT in directory






Is there any specific location for a MINIOPT directory statement?

For example, I have the following statements in my user directory:

  MDISK 0B00 ...
  MINIOPT PAV FB00 
  MDISK 0B01 ...
  MINIOPT PAV FB01

Do I need to maintain that order of statements? Can I group all of the 
MDISK statements together and all of the MINIOPT statements separately?  

George Shedlock Jr
AEGON Information Technology
AEGON USA
502-560-3541



*** IMPORTANT
NOTE* The opinions expressed in this
message and/or any attachments are those of the author and not
necessarily those of Brown Brothers Harriman & Co., its
subsidiaries and affiliates ("BBH"). There is no guarantee that
this message is either private or confidential, and it may have
been altered by unauthorized sources without your or our knowledge.
Nothing in the message is capable or intended to create any legally
binding obligations on either party and it is not intended to
provide legal advice. BBH accepts no responsibility for loss or
damage from its use, including damage from virus.


Location of MINIOPT in directory

2009-05-08 Thread Shedlock, George
Is there any specific location for a MINIOPT directory statement?

For example, I have the following statements in my user directory:

  MDISK 0B00 ...
  MINIOPT PAV FB00  
  MDISK 0B01 ...
  MINIOPT PAV FB01

Do I need to maintain that order of statements? Can I group all of the MDISK 
statements together and all of the MINIOPT statements separately? 

George Shedlock Jr
AEGON Information Technology
AEGON USA
502-560-3541


Re: Virtual Software Systems Inc. VTAPE product

2009-05-08 Thread Shiminsky, Gary
Thank you.

Gary

Gary L. Shiminsky

"I'm going to move you baby!"
Captain, USS Titanic
Legend of the USS Titanic - Jamie Brockett

Systems & Communications Sciences, Inc
At TSG, DoIT Services Data Center
State of New Hampshire
(603) 271-1509
 

-Original Message-
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On
Behalf Of Schuh, Richard
Sent: Friday, May 08, 2009 2:11 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Virtual Software Systems Inc. VTAPE product

Ah, now the mud has been washed away from my eyes. VSSLTAPE isn't the
easiest to pick apart. I'll send you a sample of an updated EXEC.

 

Regards, 
Richard Schuh 

 

> -Original Message-
> From: The IBM z/VM Operating System 
> [mailto:ib...@listserv.uark.edu] On Behalf Of Shiminsky, Gary
> Sent: Friday, May 08, 2009 10:01 AM
> To: IBMVM@LISTSERV.UARK.EDU
> Subject: Re: Virtual Software Systems Inc. VTAPE product
> 
> I'm sorry I was not more clear on what we needed. We were not 
> planning to use CA's VM:Backup/HiDRO to backup VTAPE's 
> library volumes.
> 
> We would like to have VTAPE's VTBKUP and VTREST commands 
> interface thru the VSSLTAPE EXEC to CA's Dynam/T/VM where we 
> manage our tapes (days retention, number of gens, offsite 
> vaulting and of course scratching tapes).
> 
> The driving force behind this is we would like to retire our 
> 3490 tape drives because of ever increasing maintenance costs 
> (and eventually our 3590 tape drive) and get new tape 
> technology (which means much larger capacity tape cartridges 
> along with much larger costs).
> 
> Gary
> 
> Gary L. Shiminsky
> 
> "I'm going to move you baby!"
> Captain, USS Titanic
> Legend of the USS Titanic - Jamie Brockett
> 
> Systems & Communications Sciences, Inc
> At TSG, DoIT Services Data Center
> State of New Hampshire
> (603) 271-1509
>  
> 
> -Original Message-
> From: The IBM z/VM Operating System 
> [mailto:ib...@listserv.uark.edu] On Behalf Of Schuh, Richard
> Sent: Friday, May 08, 2009 12:34 PM
> To: IBMVM@LISTSERV.UARK.EDU
> Subject: Re: Virtual Software Systems Inc. VTAPE product
> 
> Do not lose track of the fact that VSSLTAPE is an 
> application/TMS interface, not-VTAPE-system code/TMS. You 
> might be able to create a tape pool that includes the 
> potential volumes in your VTAPE library. That is only the 
> easy piece. If you look at the sample VSSLTAPE, you will see 
> that it is not trivial. It was designed to be used by two 
> very specific applications. Those applications intercept the 
> I/O interrupts occurring on specific real tape drives and all 
> OPEN and CLOSE macros and call VSSLTAPE as required, simply 
> to get real tapes mounted. What you are asking is the 
> complimentary action. You want something that monitors for 
> VTAPE requests and handles them for the Hidro-Dynam/T 
> environment. I doubt that Hidro has such exits.
> 
> Also, do not forget about the need for logical backup of the 
> VTAPE library. If you use Hidro to do a physical backup while 
> the library is closed, you will not be able to restore a 
> single VTAPE, you will have to restore the entire library. 
> You could, of course, create a second library, restore to it, 
> then copy the tape in question to your real (pun
> intended) VTAPE library.
>   
> 
> Regards,
> Richard Schuh 
> 
>  
> 
> > -Original Message-
> > From: The IBM z/VM Operating System
> > [mailto:ib...@listserv.uark.edu] On Behalf Of Phil Smith III
> > Sent: Friday, May 08, 2009 2:55 AM
> > To: IBMVM@LISTSERV.UARK.EDU
> > Subject: Re: Virtual Software Systems Inc. VTAPE product
> > 
> > "Shiminsky, Gary" wrote:
> > >We use the other VMBACKUP product - HiDRO which does have an
> > interface
> > >with Dynam/T/VM.  HiDRO does a good job of backing up our 
> CMS & SFS 
> > >material except for Byte File System (BFS) directories in SFS.
> > 
> > It's been a while, but I remember that DYNAM/T wasn't that hard to 
> > interface with. It did have a nasty habit of losing threads 
> (per the 
> > then-DYNAM/T dev team), but hopefully that's been fixed by now.
> > 
> > ...phsiii
> > 
> 


Re: Virtual Software Systems Inc. VTAPE product

2009-05-08 Thread Schuh, Richard
Ah, now the mud has been washed away from my eyes. VSSLTAPE isn't the easiest 
to pick apart. I'll send you a sample of an updated EXEC.

 

Regards, 
Richard Schuh 

 

> -Original Message-
> From: The IBM z/VM Operating System 
> [mailto:ib...@listserv.uark.edu] On Behalf Of Shiminsky, Gary
> Sent: Friday, May 08, 2009 10:01 AM
> To: IBMVM@LISTSERV.UARK.EDU
> Subject: Re: Virtual Software Systems Inc. VTAPE product
> 
> I'm sorry I was not more clear on what we needed. We were not 
> planning to use CA's VM:Backup/HiDRO to backup VTAPE's 
> library volumes.
> 
> We would like to have VTAPE's VTBKUP and VTREST commands 
> interface thru the VSSLTAPE EXEC to CA's Dynam/T/VM where we 
> manage our tapes (days retention, number of gens, offsite 
> vaulting and of course scratching tapes).
> 
> The driving force behind this is we would like to retire our 
> 3490 tape drives because of ever increasing maintenance costs 
> (and eventually our 3590 tape drive) and get new tape 
> technology (which means much larger capacity tape cartridges 
> along with much larger costs).
> 
> Gary
> 
> Gary L. Shiminsky
> 
> "I'm going to move you baby!"
> Captain, USS Titanic
> Legend of the USS Titanic - Jamie Brockett
> 
> Systems & Communications Sciences, Inc
> At TSG, DoIT Services Data Center
> State of New Hampshire
> (603) 271-1509
>  
> 
> -Original Message-
> From: The IBM z/VM Operating System 
> [mailto:ib...@listserv.uark.edu] On Behalf Of Schuh, Richard
> Sent: Friday, May 08, 2009 12:34 PM
> To: IBMVM@LISTSERV.UARK.EDU
> Subject: Re: Virtual Software Systems Inc. VTAPE product
> 
> Do not lose track of the fact that VSSLTAPE is an 
> application/TMS interface, not-VTAPE-system code/TMS. You 
> might be able to create a tape pool that includes the 
> potential volumes in your VTAPE library. That is only the 
> easy piece. If you look at the sample VSSLTAPE, you will see 
> that it is not trivial. It was designed to be used by two 
> very specific applications. Those applications intercept the 
> I/O interrupts occurring on specific real tape drives and all 
> OPEN and CLOSE macros and call VSSLTAPE as required, simply 
> to get real tapes mounted. What you are asking is the 
> complimentary action. You want something that monitors for 
> VTAPE requests and handles them for the Hidro-Dynam/T 
> environment. I doubt that Hidro has such exits.
> 
> Also, do not forget about the need for logical backup of the 
> VTAPE library. If you use Hidro to do a physical backup while 
> the library is closed, you will not be able to restore a 
> single VTAPE, you will have to restore the entire library. 
> You could, of course, create a second library, restore to it, 
> then copy the tape in question to your real (pun
> intended) VTAPE library.
>   
> 
> Regards,
> Richard Schuh 
> 
>  
> 
> > -Original Message-
> > From: The IBM z/VM Operating System
> > [mailto:ib...@listserv.uark.edu] On Behalf Of Phil Smith III
> > Sent: Friday, May 08, 2009 2:55 AM
> > To: IBMVM@LISTSERV.UARK.EDU
> > Subject: Re: Virtual Software Systems Inc. VTAPE product
> > 
> > "Shiminsky, Gary" wrote:
> > >We use the other VMBACKUP product - HiDRO which does have an
> > interface
> > >with Dynam/T/VM.  HiDRO does a good job of backing up our 
> CMS & SFS 
> > >material except for Byte File System (BFS) directories in SFS.
> > 
> > It's been a while, but I remember that DYNAM/T wasn't that hard to 
> > interface with. It did have a nasty habit of losing threads 
> (per the 
> > then-DYNAM/T dev team), but hopefully that's been fixed by now.
> > 
> > ...phsiii
> > 
> 

Re: Virtual Software Systems Inc. VTAPE product

2009-05-08 Thread Shiminsky, Gary
I'm sorry I was not more clear on what we needed. We were not planning
to use CA's VM:Backup/HiDRO to backup VTAPE's library volumes.

We would like to have VTAPE's VTBKUP and VTREST commands interface thru
the VSSLTAPE EXEC to CA's Dynam/T/VM where we manage our tapes (days
retention, number of gens, offsite vaulting and of course scratching
tapes).

The driving force behind this is we would like to retire our 3490 tape
drives because of ever increasing maintenance costs (and eventually our
3590 tape drive) and get new tape technology (which means much larger
capacity tape cartridges along with much larger costs).

Gary

Gary L. Shiminsky

"I'm going to move you baby!"
Captain, USS Titanic
Legend of the USS Titanic - Jamie Brockett

Systems & Communications Sciences, Inc
At TSG, DoIT Services Data Center
State of New Hampshire
(603) 271-1509
 

-Original Message-
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On
Behalf Of Schuh, Richard
Sent: Friday, May 08, 2009 12:34 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Virtual Software Systems Inc. VTAPE product

Do not lose track of the fact that VSSLTAPE is an application/TMS
interface, not-VTAPE-system code/TMS. You might be able to create a tape
pool that includes the potential volumes in your VTAPE library. That is
only the easy piece. If you look at the sample VSSLTAPE, you will see
that it is not trivial. It was designed to be used by two very specific
applications. Those applications intercept the I/O interrupts occurring
on specific real tape drives and all OPEN and CLOSE macros and call
VSSLTAPE as required, simply to get real tapes mounted. What you are
asking is the complimentary action. You want something that monitors for
VTAPE requests and handles them for the Hidro-Dynam/T environment. I
doubt that Hidro has such exits.

Also, do not forget about the need for logical backup of the VTAPE
library. If you use Hidro to do a physical backup while the library is
closed, you will not be able to restore a single VTAPE, you will have to
restore the entire library. You could, of course, create a second
library, restore to it, then copy the tape in question to your real (pun
intended) VTAPE library.
  

Regards, 
Richard Schuh 

 

> -Original Message-
> From: The IBM z/VM Operating System 
> [mailto:ib...@listserv.uark.edu] On Behalf Of Phil Smith III
> Sent: Friday, May 08, 2009 2:55 AM
> To: IBMVM@LISTSERV.UARK.EDU
> Subject: Re: Virtual Software Systems Inc. VTAPE product
> 
> "Shiminsky, Gary" wrote:
> >We use the other VMBACKUP product - HiDRO which does have an 
> interface 
> >with Dynam/T/VM.  HiDRO does a good job of backing up our CMS & SFS 
> >material except for Byte File System (BFS) directories in SFS.
> 
> It's been a while, but I remember that DYNAM/T wasn't that 
> hard to interface with. It did have a nasty habit of losing 
> threads (per the then-DYNAM/T dev team), but hopefully that's 
> been fixed by now.
> 
> ...phsiii
> 


Re: Virtual Software Systems Inc. VTAPE product

2009-05-08 Thread Schuh, Richard
Do not lose track of the fact that VSSLTAPE is an application/TMS interface, 
not-VTAPE-system code/TMS. You might be able to create a tape pool that 
includes the potential volumes in your VTAPE library. That is only the easy 
piece. If you look at the sample VSSLTAPE, you will see that it is not trivial. 
It was designed to be used by two very specific applications. Those 
applications intercept the I/O interrupts occurring on specific real tape 
drives and all OPEN and CLOSE macros and call VSSLTAPE as required, simply to 
get real tapes mounted. What you are asking is the complimentary action. You 
want something that monitors for VTAPE requests and handles them for the 
Hidro-Dynam/T environment. I doubt that Hidro has such exits.

Also, do not forget about the need for logical backup of the VTAPE library. If 
you use Hidro to do a physical backup while the library is closed, you will not 
be able to restore a single VTAPE, you will have to restore the entire library. 
You could, of course, create a second library, restore to it, then copy the 
tape in question to your real (pun intended) VTAPE library.
  

Regards, 
Richard Schuh 

 

> -Original Message-
> From: The IBM z/VM Operating System 
> [mailto:ib...@listserv.uark.edu] On Behalf Of Phil Smith III
> Sent: Friday, May 08, 2009 2:55 AM
> To: IBMVM@LISTSERV.UARK.EDU
> Subject: Re: Virtual Software Systems Inc. VTAPE product
> 
> "Shiminsky, Gary" wrote:
> >We use the other VMBACKUP product - HiDRO which does have an 
> interface 
> >with Dynam/T/VM.  HiDRO does a good job of backing up our CMS & SFS 
> >material except for Byte File System (BFS) directories in SFS.
> 
> It's been a while, but I remember that DYNAM/T wasn't that 
> hard to interface with. It did have a nasty habit of losing 
> threads (per the then-DYNAM/T dev team), but hopefully that's 
> been fixed by now.
> 
> ...phsiii
> 

Re: Virtual Software Systems Inc. VTAPE product

2009-05-08 Thread Phil Smith III
"Shiminsky, Gary" wrote:
>We use the other VMBACKUP product - HiDRO which does have an interface
>with Dynam/T/VM.  HiDRO does a good job of backing up our CMS & SFS
>material except for Byte File System (BFS) directories in SFS.

It's been a while, but I remember that DYNAM/T wasn't that hard to interface 
with. It did have a nasty habit of losing threads (per the then-DYNAM/T dev 
team), but hopefully that's been fixed by now.

...phsiii


AUTO: Susan Lindsay/Poughkeepsie/IBM is out of the office until 5/11/2009 (returning 05/11/2009)

2009-05-08 Thread Susan Lindsay


I am out of the office until 05/11/2009.

I'll be out of the office until Mon. May 11th.


Note: This is an automated response to your message  "IBMVM Digest - 6 May
2009 to 7 May 2009 (#2009-126)" sent on 5/8/09 1:01:45.

This is the only notification you will receive while this person is away.