Barry
I connection with possible problems from "moved" VTAMLST members, I used to
do the following:
But first I need to explain the environment. I used to have a number of test
MVS systems running on the same VM system. There was also a "production" MVS
system also running on the same VM system from which I could access all the
volumes used to support the test systems.
I was very often playing around with VTAM and making very frequent changes
to VTAMLST members - as one does with test systems. Whenever I felt I may be
getting near to the capacity of a VTAMLST data set, I ran a "z" on it from a
TSO ISPF session running in the production MVS system. I was actually
somewhat paranoid about running out of space so I probably "z"ed far more
often than I really needed to.
I recall having no problems ever - in getting on for 20 years - over a
"moved" VTAMLST member.
Chris Mason
----- Original Message -----
From: "Schwarz, Barry A" <[EMAIL PROTECTED]>
Newsgroups: bit.listserv.ibm-main
To: <IBM-MAIN@BAMA.UA.EDU>
Sent: Monday, March 12, 2007 7:44 PM
Subject: Re: Renaming SYS1.VTAMLST
...
You can compress the dataset in batch with IEBCOPY and DISP=SHR but you
run the risk of active tasks having problems if any open member is
relocated.
----------------------------------------------------------------------
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
