Pierre, i wouldn't be too hasty to find an answer, rather, i'd be troubled by the existence of such jobs. Yes, it is weird.
what if some recovery is needed from that dsn=ABCD, and the only copy (on tape) was then clobbered ? what if dsn=ABCD has extended to another tape volume ? - ravi. On Tue, 12 Apr 2011 09:31:37 -0700, Starr, Alan <[email protected]> wrote: >Pierre, > >Try specifying DBLTIME=240000 in TLMSIPO or, alternatively, specify SPACE=(1,(1,3)) on the DD statement that ORIGINALLY creates DSN=ABCD with DISP=(NEW,CATLG). > >The former permits "double OPEN" of all tape datasets and the latter restricts "double OPEN" to a single tape dataset. The documentation isn't clear if "double open" is restricted to jobs having the same name. > >Hope that helps, >Alan > > >-----Original Message----- >From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Vernooij, CP - SPLXM >Sent: Tuesday, April 12, 2011 1:41 AM >To: [email protected] >Subject: Re: Anyone with TLMS: please help ! > >Pierre, > >I can't help you with TLMS. >However, this newsgroup is a mirror of the IBM-MAIN listserver and that is where the majority of the users read posts. >I sent this via the listserver, so you will probably get more answers now. >Information about joining the listserver will be attached automagically at the bottom of this post. > >Kees. > >"Pi-R" <[email protected]> wrote in message news:<[email protected]>... > >Hi, list ! It's been a long time... ! > >I have this weird situation (at least, *I* think it's weird, until proven otherwise !): > >- Job JOB1 writes file DSN=ABCD with DISP=(NEW,CATLG) on a tape unit. >Tape library is managed by CA-TLMS. > >- JOB JOB2 attempts to overwrite file DSN=ABCD with DISP=OLD and gets following error: > >CAT9040I 5V4635 ON 2BDB REJECTED BY CA TLMS CAT9041I VOLUME IS NOT A SCRATCH TAPE IEC148I 713-04,IFG0196N,JOB2,STEP1,SYSUT2,2BDB,,ABCD > >UserIdS attached to both jobs is the same, therefore, this is not a matter of security rights. > >Funnily enough, if the JOBNAME of the second job is changed to JOB1 (same as the job that created the file), it gets no error. Also, if the file is on label other than 1 (eg: LABEL=(2,SL)), it also gets no error. Finally, if JOB2 does something with DISP=MOD on the file, subsequent executions of JOB2 can overwrite the file with DISP=OLD without error. > >I am trying to figure out if this is the making of some obscure forgotten exit put there by a system programmer of a previous generation, or if it's really how TLMS behaves. I was unsuccessful in searching documentation for explanations. > >If anyone with TLMS can try this and tell me how it goes, it would really help ! > >TIA ! > >--- >Pierre >---------- ---------------------------------------------------------------------- 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
