I have another dumb question. How is it that PSF can tolerate having its PDS 
data sets moved while it is running?

-- 
Tom Marchant

On Wed, 23 Oct 2019 15:29:24 +0000, Jousma, David <[email protected]> wrote:

>David,  I guess I might have a dumb question, but if the datasets that PSF was 
>using were PDSE, then why is your re-org process trying to re-org a PDSE?   
>Seems like maybe the selection process of what gets re-org'd should be tweaked?
>
>_____________________________________________________________________________________________________
>Dave Jousma
>AVP | Manager, Systems Engineering  
>
>Fifth Third Bank  |  1830 East Paris Ave, SE  |  MD RSCB2H  |  Grand Rapids, 
>MI 49546
>616.653.8429  |  fax: 616.653.2717
>
>
>
>-----Original Message-----
>Fro : I M Mainframe Discussion List <[email protected]> On Behalf Of 
>David Purdy
>Sent: Wednesday, October 23, 2019 8:34 AM
>To: [email protected]
>Subject: Re: PDS to PDSE conversion issues
>
>**CAUTION EXTERNAL EMAIL**
>
>**DO NOT open attachments or click on links from unknown senders or unexpected 
>emails**
>
>This is within one sysplex.  We're asking ourselves the same questions.
>Dave, I will let you know the quite interesting details when the drill down is 
>complete.
>David
>
>-----Original Message-----
>From: Gibney, Dave <[email protected]>
>To: IBM-MAIN <[email protected]>
>Sent: Wed, Oct 23, 2019 12:01 AM
>Subject: Re: PDS to PDSE conversion issues
>
>
>Why would this change, between PDS and PDS/E? Unless this is yet another 
>encounter with the pitfall os trying to share PDE/E outside Sysplex.
>
>> -----Original Message-----
>> From: IBM Mainframe Discussion List <[email protected]> On 
>> Behalf Of David Purdy
>> Sent: Tuesday, October 22, 2019 2:20 PM
>> To: [email protected]
>> Subject: Re: PDS to PDSE conversion issues
>> 
>> I recently converted several PSF libraries, resulting in a problem if 
>> a dasd reorg moved the dataset while PSF tasks are up.  PSF does not 
>> issue an enqueue but has the dataset open.  The volume reorg only 
>> checks for enqueue before moving the dataset.  Short term, we configed 
>> the reorg to skip PSF datasets.  Long term, looking at setting DSI and 
>> setting a dataset close flag in a PSF exit.  Or just taking down 
>> printers before reorg in the wee morning hours.
>> David
>> -----Original Message-----
>> From: Toby Seguin <[email protected]>
>> To: IBM-MAIN <[email protected]>
>> Sent: Tue, Oct 22, 2019 03:06 PM
>> Subject: PDS to PDSE conversion issues
>> 
>> 
>> We are currently thinking about converting many of our PDS libraries to PDSE.
>> While researching the possible pitfalls to a PDSE one that concerned 
>> me the most is "Blocked Workload" that Thomas Reed discussed at SHARE in 
>> 2018.
>> 
>> This situation is said to occur when CPU is near 100% (pretty common 
>> event from time to time here) so it certainly caught my attention. 
>> Does anyone have any experience with Blocked Workload? Anything else I 
>> should be looking closer at?
>> 
>> Thanks and Regards,
>> 
>> Toby Seguin
>> 
>> ----------------------------------------------------------------------
>> For IBM-MAIN subscribe / signoff / archive access instructions, send 
>> email to [email protected] with the message: INFO IBM-MAIN
>> 
>> ----------------------------------------------------------------------
>> For IBM-MAIN subscribe / signoff / archive access instructions, send 
>> email to [email protected] with the message: INFO IBM-MAIN
>
>----------------------------------------------------------------------
>For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
>[email protected] with the message: INFO IBM-MAIN
>
>----------------------------------------------------------------------
>For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
>[email protected] with the message: INFO IBM-MAIN **CAUTION EXTERNAL 
>EMAIL**
>
>**DO NOT open attachments or click on links from unknown senders or unexpected 
>emails**
>
>This e-mail transmission contains inorrmation that is confidential and may be 
>privileged.   It is intended only for the addressee(s) named above. If you 
>receive this e-mail in error, please do not read, copy or disseminate it in 
>any manner. If you are not the intended recipient, any disclosure, copying, 
>distribution or use of the contents of this information is prohibited. Please 
>reply to the message immediately by informing the sender that the message was 
>misdirected. After replying, please erase it from your computer system. Your 
>assistance in correcting this error is appreciated.
>
>
>----------------------------------------------------------------------
>For IBM-MAIN subscribe / signoff / archive access instructions,
>send email to [email protected] with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to