We're experiencing an abend S0D5 that occurs at only one site. We have an authorized program that issues a DSPSERV CREATE SCOPE=ALL to establish a dataspace. It initializes several of the blocks in the dataspace but does not touch the rest of the blocks. It then issues SYSEVENT TRANSWAP and WAITs for the ECB to be posted (unless it was already non-swappable). Then it publishes the availability of the dataspace in CSA and WAITs for a MVS STOP command.
Later we run a problem state program that invokes a proprietary PC to acquire the dataspace ALET (ALESERV) and then accesses the dataspace blocks. It runs fine until it tries to access a block that was not referenced by the dataspace creating program. It then abends S0D5. Are there conditions under which a non-swappable address space can become logically swapped out? Gary Weinhold Senior Application Architect DATAKINETICS | Data Performance & Optimization Phone: +1.613.523.5500 x216<tel:+1.613.523.5500%20x216> Email: weinh...@dkl.com<mailto:weinh...@dkl.com> [http://www.dkl.com/wp-content/uploads/2015/07/dkl_logo.png]<http://www.dkl.com/> Visit us online at www.DKL.com<http://www.dkl.com/> [http://www.dkl.com/wp-content/uploads/2015/08/banner.png]<http://www.dkl.com/mailsig> E-mail Notification: The information contained in this email and any attachments is confidential and may be subject to copyright or other intellectual property protection. If you are not the intended recipient, you are not authorized to use or disclose this information, and we request that you notify us by reply mail or telephone and delete the original message from your mail system. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
