Was it really some ISPF/PDF function or could it have been some ad-on? FileAid/MVS does an OLD enqueue on the data set even if you're editing a member thereof. You may change this but you can easily forget to do so.-- Peter Hunkeler
Von: Lizette Koehler <[email protected]> An: [email protected] Betreff: Re: ISPF dynamically allocating dataset with DISP=OLD? Datum: 04.04.14 03:53 Did they compress the dataset in ISPF 3.4? Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Chase, John > Sent: Thursday, April 03, 2014 10:42 AM > To: [email protected] > Subject: ISPF dynamically allocating dataset with DISP=OLD? > > Hi, List, > > z/OS 1.13 at RSU1312. The other day, a user "did something" in ISPF that caused > allocation of a Production JCL library to his TSO session with DISP=OLD instead of > DISP=SHR, causing a "hiccup" in batch processing when the scheduler was > "locked out" for a few seconds. So far, we have not been able to replicate "locking > out" another user at the dataset level via any combination of manipulations using > (primarily) ISPF EDIT. > > Here's a SMF14 record formatted by DAF (Thank you, Michael J. Cleary!!): > > 014 VOL=volser DD=ISP15297 OPE=15.30.06.51 CRTDT=02045 > EXPDT=00000 DISP=Old > BUFNO=16 DSORG=PO RECFM=FB BLKSIZE=7520 LRECL=80 NVOL=1 > CTRI=CYL SQTY=50 > NTU=00582800 NTA=6000 VOL=OPER9A DEVTYPE=3390 NEX=1 > EXCP=4001 STEP=tsoproc > PGM=IKJEFT01 14XF1=192 14CIS=18090271 14TKL=58051 > > The SMF 42-006 that immediately follows: > > 042 006 JDCOD=Close DSTYP=PDS DSFL1=Non-VSAM_fixed_length_records > VOL=volser DSDEV=ccuu > DSBSZ=256 DSIOR=9 DSIOC=7 DSIOP=1 DSION=256 DSSEQ=256 > DSMXR=58 DSMXS=57 > AMSRB=4000 AMSRR=2562 > > The timestamps on those two records are identical down to hundredths of a second, > so maybe the user was running a SuperC search? We can't tell from evidence > available to us today. > > We've tried every combination we can think of with multiple users ISPF EDITing the > same dataset, and the only time we get any "conflict" is if a second user tries to > open a MEMBER for EDIT that is already opened for EDIT by another user; and we > believe that "lockout" at the member level is accomplished via an ENQ named > SPFEDIT.membername or something like that. IOW, we have been unable to > cause a dataset (PDS or PDSE) to be dynamically allocated with DISP=OLD using > any variant of ISPF EDIT. > > Is there any other way within ISPF that an existing dataset can be dynamically > allocated with DISP=OLD? If there is, we apparently have never encountered it > before. > > TIA, > > -jc- > ---------------------------------------------------------------------- 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
