W dniu 2016-09-22 o 15:36, Joel C. Ewing pisze:
On 09/22/2016 07:30 AM, Tom Marchant wrote:
On Thu, 22 Sep 2016 13:48:42 +0200, R.S. <r.skoru...@snipped.com.pl> wrote:

PDSEs were available long before z/OS brandname was born.
Executable code could be stored in PDSE starting with MVS 4.3 in 1992.
 From the General Information manual:

Additional MVS/ESA SP 4.3 support with DFSMS/MVS allows users to store and
load executable code in a partitioned data set extended (PDSE).  Users can
create and manage loaded modules and load libraries in PDSEs with the same
data management techniques as other PDSEs.

Perhaps a better question would be when did IBM and the MVS user
community actually have enough confidence in PDSE reliability to  start
distributing products with PDSE program libraries, especially ones that
needed to go in the LNKLST concatenation.

My recollection is that PDSEs did have a  significant number of issues
for a number of years including data-loss and availability APARs.  You
had to have a strong need for some of the unique PDSE features to take
the risk in the early years.   About the only way to corrupt a PDS was
to open one improperly, and with the most common error (attributes
change) most of the damage was easily repairable.  We had a number of
cases (more than 1, less than 10, at least 2 night calls) in the early
PDSE years where access rules were not violated and an entire PDSE
became corrupted and unreadable and also at least one case where a PDSE
became hung and inaccessible until next IPL!  That would have been a
much more serious issue for us had those incidents involved a product
program library instead of just an application data library..

It was 25 years ago. Things changed. Nowadays the most popular way to destroy PDSE is to share it across sysplexes. In my shop we use PDSE from day 0 (~18 years) with no issue except very few cases of improper sharing. People who are reluctant to use PDSE have ... no choice. Many system libraries are PDSE with no option to switch to PDS (the opposite way covers 99% of system libraries). Now, COBOL v5 and v6 do require PDSE for linked binaries.

Radoslaw Skorupka
Lodz, Poland

Treść tej wiadomości może zawierać informacje prawnie chronione Banku 
przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może być jedynie 
jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli nie jesteś adresatem 
niniejszej wiadomości lub pracownikiem upoważnionym do jej przekazania 
adresatowi, informujemy, że jej rozpowszechnianie, kopiowanie, rozprowadzanie 
lub inne działanie o podobnym charakterze jest prawnie zabronione i może być 
karalne. Jeżeli otrzymałeś tę wiadomość omyłkowo, prosimy niezwłocznie 
zawiadomić nadawcę wysyłając odpowiedź oraz trwale usunąć tę wiadomość 
włączając w to wszelkie jej kopie wydrukowane lub zapisane na dysku.

This e-mail may contain legally privileged information of the Bank and is 
intended solely for business use of the addressee. This e-mail may only be 
received by the addressee and may not be disclosed to any third parties. If you 
are not the intended addressee of this e-mail or the employee authorized to 
forward it to the addressee, be advised that any dissemination, copying, 
distribution or any other similar activity is legally prohibited and may be 
punishable. If you received this e-mail by mistake please advise the sender 
immediately by using the reply facility in your e-mail software and delete 
permanently this e-mail including any copies of it either printed or saved to 
hard drive.

mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa, 
www.mBank.pl, e-mail: kont...@mbank.pl
Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru 
Sądowego, nr rejestru przedsiębiorców KRS 0000025237, NIP: 526-021-50-88. 
Według stanu na dzień 01.01.2016 r. kapitał zakładowy mBanku S.A. (w całości 
wpłacony) wynosi 168.955.696 złotych.

For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to