On Tue, 1 Dec 2009 14:46:09 -0500, Don Leahy wrote: >I am not sure why it works, we did not do any extensive testing but I >do know that we haven't had any problems for a long time. We use >ICEGENER to do the copying. > >Caveat: we rarely have more than 2 compiles running at the same time >(small shop), so your mileage may vary. > Sounds risky to me. A safe technique I use is LMCOPY (but ICEGENER may be smart enough to use the same ENQ as ISPF).
Or, allocate DRMLIB to a Unix directory. >On Tue, Dec 1, 2009 at 14:04, Frank Swarbrick wrote: >> A later step in the same job? Does this solve the issue because the copy >> uses different serialization than the actual creating of the DBRM member? >> >> On 12/1/2009 at 11:58 AM, in message >> <[email protected]>, Don Leahy >> wrote: >>> This is a perennial problem. >>> >>> Our local solution was to allocate DBRMLIB to a temporary data set. >>> >>> //DBRMLIB DD DSN=&DBRMLB(&MR),DISP=(,PASS), >>> // UNIT=SYSDA,SPACE=(TRK,(15,5,5)), >>> // DCB=(RECFM=FB,LRECL=80,BLKSIZE=6160) >>> >>> A later step copies the DBRM to a permanent library. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
