Re: DFSMS for VM Exit FSRMDEV

2008-01-31 Thread Romanowski, John (OFT)
Horst,

I can send you assembler and VMSES instructions for a working DFSMS exit 
FSMRMSHR (RMS Library Partitioning).

FSMRMSHR calls a Rexx EXEC to do its actual work. 

 

 You would have to adjust a few assembler lines and names to convert  it into 
your desired FSMRMDEV exit that calls a Rexx EXEC. 

The main effort is the 2 exits have different parameters but  should be easy 
for adventurous, novice assembler to adjust the parameter references. The 
parameter types of FSMRMDEV are a subset of the types used by FSMRMSHR except 
for FSMRMDEV's 'Real dev address' bit(16) input parameter for which an example 
is probably in the 'z/Vm Application Dev Guide for Assembler'.

 

John (Novice assembler)

 



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.





From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of 
Rempel, Horst
Sent: Wednesday, January 30, 2008 7:23 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: DFSMS for VM Exit FSRMDEV

 

Hello VMers, 

we have a problem with DFSMS/RMS for VM and our IBM 3494 TapeLibrary with 
mixxed tapedrives 2 x 3490 and 4 x 3590. 
When we do mount requests without specifying a real device RMS will try to use 
the first available device nevertheless its

a 3490 or a 3590. 

So the recommandation from IBM to solve our problem is to modify the exit 
FSMRMDEV. 
The exit should be written as a assembler program that calls a REXX-procedure 
where the logic resides. 

I found the following text in the redbook 'Guide to Sharing and Partitioning 
IBM Tape Library Dataservers'  SG24-4409-02 

 FSMRMDEV 
The real-device-selection exit, FSMRMDEV, can select a device when a real 
device address is not specified in the incoming request. Users can provide 
their 
own device selection algorithm. The product default processing selects the 
first 
available (unattached) library tape device that can be located. The request 
fails 
if no devices are available. 
Note: This exit becomes highly interesting in an environment of mixed drive 
types where getting the correct media-drive match is critical. A 
sophisticated exit may be required here, to match a selected device type 
to a particular scratch pool being requested, or a volume serial number 
within a customer-defined range that represents a certain media type. 

Has anyone modified this exit ? I am looking for a sample how to do it ? 
I am familar with REXX but not really with assembler. I appreciate any sample. 

Kind regards, 

Horst Rempel 
Berufsgenossenschafthttp://www.bgchemie.de 
der chemischen Industriee-mail [EMAIL PROTECTED] 
Abteilung EDV/DV-ORG 
Kurfürstenanlage 62 
69115 Heidelberg


Re: DFSMS for VM Exit FSRMDEV

2008-01-30 Thread Tracy Dean
On Wed, 30 Jan 2008 13:23:17 +0100, Rempel, Horst [EMAIL PROTECTED] 

wrote:

Hello VMers,

we have a problem with DFSMS/RMS for VM and our IBM 3494 TapeLibrary wit
h 
mixxed tapedrives 2 x 3490 and 4 x 3590.
When we do mount requests without specifying a real device RMS will try 
to 
use the first available device nevertheless its
a 3490 or a 3590.

So the recommandation from IBM to solve our problem is to modify the exi
t 
FSMRMDEV.

product promotion on

Or you could use a tape management product (such as IBM Tape Manager for 

z/VM) to manage your tapes and the devices in the ATL.  Once you've 
specified the types of tapes you have and the types of devices you have, 

Tape Manager will request the correct device for a specific tape.  And of
 
course you get the additional benefits of tape management such as access 

control, expiration processing, etc.

product promotion off

Tracy Dean, IBM