ADSM-L

Re: control over tape data set names

2015-10-04 18:14:04
Subject: Re: control over tape data set names
From: Jerry Lawson at TISDMAIL
From: INTERNET.OWNERAD at SNADGATE
To: higmx.oas at SNADGATE
To: Jerry Lawson at TISDMAIL
Date: 8/15/96 12:21PM
Date: 8/15/96 8:57AM
I am confused by your comments below - I am now at 2.1.0.7 of my MVS server,
and I am also setting up a disaster recovery copypool.  I did a DEFINE
DEVCLASS and set the highlevel qualifier to ADSM.BK.  Needless to say, it
seems to be working - I am getting tapes created with the name of ADSM.BK.BFS.

I would also note that While the tapes seem to be ok, two of the tapes are
marked in TMS as having abended - but I did not see any abend.  I did have
cause to cancel one process as it was at reel change time - it was looking for
a econd tape drive, and my test system only had one available.  I would not
have expected this to mark the tape as abended, though.  I did have a
situation where the tapes were run on a back level server (level 3 or 4, not
sure which) due to an unusual testing request from the security dept.  But
that's another story....

Jerry Lawson
jlawson AT itthartford DOT com
________________________Forward Header________________________
Author: INTERNET.OWNERAD
Subject: Re: control over tape data set names
08-15-96 08:57 AM

>I am new to ADSM, and doing initial planning of MVS server, prior to
>installation.  What controls are there for tape names?  The devclass prefix
>parameter implies that it only dictates the high-level qualifier?  I would
>like, ideally, to specify a unique ADSM HLQ and multiple second levels on a
>devclasses to conform to our naming standards and provide unique DSN's for
>our CA1 TMS to control vault movement (offsite copy storage pool).

>My understanding from book-  default is always ADSM.BFS and can only be
>changed to USERHLQ.BFS ??  Are copy group storage group tapes also
>ADSM.BFS, or do they generate different 2nd level, ADSM.CFS for ex.?

A PTF has enabled the use of multiple qualifiers in the PREFIX setting of
the devclass... with one caveat: you are still limited to a maximum of 8
characters in the prefix field, including the dots. Thus you can define a
devclass with a prefix like ADSM.OFF, ADSM.LOC, ADSM.A.B, etc. But you can't
have a prefix of ADSM.OFFSITE or ADSM.LOCAL because these exceed 8 characters.

The latest PTF level for MVS is V2 R1 L0.9. The PTF numbers are UN91696,
UN91697, UN91698, UN91699, and UN91700.

Andy Raibeck
ADSM Level 2 Support
<Prev in Thread] Current Thread [Next in Thread>