Norbert Friemel wrote:
On Sat, 21 Apr 2007 17:57:18 +0200, R.S. wrote:
RACF Security Administrator's Guide says:
You cannot RACF-protect nonlabeled tapes that have a volume serial
number of "Lnnnnn".
Why ?
Just curious
Lnnnnn is a special serial number (like SCRTCH and PRIVAT) used in mount
messages.
<http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IEA2M771/3.357?SHELF=EZ2MZ801&DT=20070122113857&CASE=>
SER= subparameter
<http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IEA2B661/12.63.2?SHELF=IEA2BK71&DT=20060125042105&CASE=>
Norbert Friemel
I'm assuming that the "Lnnnnn" designation must be some convention that
is assigned by placing the volume into an automated tape library of some
kind. If that is the case, then I would expect that volser association
to be a temporary one, as there would be nothing written in tape
labels to force consistent use of the same volser if the volume is
removed and later reinserted into the tape library, or used outside of
the tape library.
Outside of an automated library, an unlabeled tape can be designated in
JCL with any arbitrary volser and any arbitrary dataset name as long as
you can convince an Operator to mount the intended tape, since there are
no recorded labels on the tape to contradict. There is no way in general
to protect an unlabeled tape via RACF because without label records
there is no fixed volser and no fixed dataset name that could be used as
the basis for such protection -- another of many good arguments for
avoiding use of unlabeled tapes for anything but stand-alone IPL tapes.
--
Joel C. Ewing, Fort Smith, AR [EMAIL PROTECTED]
----------------------------------------------------------------------
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
