Steve -

Attached is an extract of a dialog I had with the vendor on this some time ago 
which you may find useful. We have not as yet implemented their solution.

========================================================================================

VENDOR-SUPPLIED INFORMATION:
Attached is the most current release of our Virtuent User's Guide which 
discusses the Tape-on-Disk application (Virtuent) used in all of our MDL 
products.

Scratch Synonyms are discussed beginning on page 19.  An example on page 20 
shows how different synonyms can be assigned to a specific range of volume 
serial numbers within the Virtuent (MDL) configuration. 

There is a z/OS user exit that allows you to modify the load display CCW before 
it is sent to a tape drive.   Since scratch synonyms can be up to 8 characters 
in length, one approach you could consider would be to define scratch synonyms 
equal to the LPAR IDs (which are 8 characters long).  Then using the load 
display user exit, replace the scratch request (SCRTCH or PRIVAT, for example) 
with the LPAR ID.   As long as the scratch synonyms were properly configured, 
the MDL would recognize the LPAR ID as a request for a scratch and assign a 
VOLSER from the range assigned to that synonym (LPAR ID).

========================================================================================

MY COMMENTARY TO MGMT ON LOCAL USAGE IN OUR ENVIRONMENT:
The exit he refers to is IGXMSGEX where we could change SCRTCH and PRIVAT in 
the mount message to a value which reflects the LPAR/system/sysplex. That value 
is then equated to a volser prefix(es) in their Scratch Synonym mechanism to 
satify a scratch request from within the proper volser range for that system. 
As an example, for PROD1, we could set SYSPROD1 in the message text in IGXMSGEX 
and define a scratch synonym of  SYSPROD1=J . This would cause only a volser 
with a prefix of  'J'  to be mounted in response to a scratch request on PROD1.
 
========================================================================================

We have a need to keep volser ranges isolated to particular system images hence 
the dissertation. An adjustment of this logic may suit your needs.

Hope you find this helpful.

Frank.


> From: Steve Dover <[email protected]>
> To: [email protected]
> Date: 11/08/2011 01:22 PM
> Subject: Bustech Virtual Tape Appliance
> Sent by: IBM Mainframe Discussion List <[email protected]>
> 
> We have recently purchased an EMC/Bustech MDL 1000 virtual tape 
> appliance, backed by EMC/Data Domain DD670 open systems storage 
> appliance.  We are going to migrate from a tape based DR recovery 
> plan to data replication to a hot site.  We are going to remove all 
> mainframe tape from our footprint.  We (read management) did not 
> purchase any services for this and have thrown me under the bus.  I 
> have to convert our tape processing from real tape to virtual tape. 
> OK, that part is already done.  The hard part, which is the bus 
> part, is splitting our tape data into classes (at least it is hard 
> for me).  Bustech says we can have 'scratch synonyms' for our tape 
> mounts, so the data can be written onto the Data Domain in different
> folders, where can control replication.  This will allow us to 
> replicate our DR tapes, but not worry about the local, non-offsite 
> tapes.  As far as I can tell, I need our z/OS system to ask for 
> something besides a PRIVAT or SCRTCH tape.  And please don't tel!
>  l me to RFM, I have read about 10 so far to no avail.  But if you 
> can't point me to a manual that will help me, I will be forever in your 
debt.
> 
> Thanks,
> Steve
> 
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: GET IBM-MAIN INFO
> Search the archives at http://bama.ua.edu/archives/ibm-main.html


This e-mail message and all attachments transmitted with it may
contain legally privileged and/or confidential information intended
solely for the use of the addressee(s). If the reader of this
message is not the intended recipient, you are hereby notified that
any reading, dissemination, distribution, copying, forwarding or
other use of this message or its attachments is strictly
prohibited. If you have received this message in error, please
notify the sender immediately and delete this message and all
copies and backups thereof. Thank you.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to