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

Reply via email to