IIRC the (pseudo) eof is only written for SMS managed PS datasets, so a PO dataset could well be allocated over old data which will then be readable. Can you force the problem PO dataset to anther place by making sure the space for the 66000 dataset is still in use when the problem PO dataset is allocated.
Kees. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of DASDBILL2 Sent: Thursday, September 19, 2013 14:17 To: [email protected] Subject: Re: Allocation test It sounds as if one of the allocation routines is getting some temporary storage but not zeroing all of it out, and the storage it happens to get contains residual data from whoever used some of that storage previously. Bill Fairchild Franklin, TN ----- Original Message ----- From: "[email protected]" <[email protected]> To: [email protected] Sent: Thursday, September 19, 2013 4:33:11 AM Subject: Allocation test Can someone please run this iefbr14 job and tell me what the space allocation is (number of directory blocks) on your system? // EXEC PGM=IEFBR14 //DD1 DD DISP=(,CATLG),DSN=TEST, // SPACE=(TRK,(1,0,0)),RECFM=F,LRECL=20,DSORG=PO Note that I deliberately request DSORG=PO but do not provide a directory space number. In my case the job ends with rc=0, the data set is allocated, but ISPF gets an I/O error when I use an "i" line command in front of it. The data set is allocated as PDS. When I change the space allocation to (TRK,(10000,0,0)), the job still ends with rc=0, the data set is still a PDS, but now it is allocated with 66000 "maximum directory blocks" displayed using the ISPF line command "i". In case you're wondering, the last PO data set allocated successfully using a batch job had 66000 directory blocks, and in my opinion that number is (invalidly) used for this batch job. Certainly the allocation behaviour is not consistent. Can anyone confirm the same behaviour or is this just another quirk on our system? Thanks in advance, Barbara ---------------------------------------------------------------------- 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 information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 ******************************************************** ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
