Re: Anyone with TLMS: please help !
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 wrote: >Pierre, > >Try specifying DBLTIME=24 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:IBM-MAIN@bama.ua.edu] On Behalf Of Vernooij, CP - SPLXM >Sent: Tuesday, April 12, 2011 1:41 AM >To: IBM-MAIN@bama.ua.edu >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" wrote in message news:<2d518eb7-6410-4e6e-b18f-b5c1e45f4...@1g2000yqq.googlegroups.com>... > >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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Anyone with TLMS: please help !
The job name that you submitted must match the jobname in the VMF record. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Anyone with TLMS: please help !
Thank you both for your replies. My TLMSIPO's DBLTIME is 24, and tests with SPACE=(1,(1,3)) did nothing more. Bob, should I understand that the phrase "same job" also applies to "other job with the same jobname" ? In other words, was DBLTIME implemented by comparing the current JOBNAME to XCREJOB from the VMF ? P. On Tue, 12 Apr 2011 12:51:37 -0500, Bob Van Horn wrote: >CA TLMS automatically prevents "double opens" of an output data set to the >same volume by the same job without first being closed. However, if you want >to re-create a data set on the same volume on which it was originally created, >you must set this option to a value greater than zero. This option determines >the time interval (after creation) during which CA TLMS will allow a double >open of the same tape data set by the same job. > >-- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO >Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Anyone with TLMS: please help !
CA TLMS automatically prevents "double opens" of an output data set to the same volume by the same job without first being closed. However, if you want to re-create a data set on the same volume on which it was originally created, you must set this option to a value greater than zero. This option determines the time interval (after creation) during which CA TLMS will allow a double open of the same tape data set by the same job. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Anyone with TLMS: please help !
Pierre, Try specifying DBLTIME=24 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:IBM-MAIN@bama.ua.edu] On Behalf Of Vernooij, CP - SPLXM Sent: Tuesday, April 12, 2011 1:41 AM To: IBM-MAIN@bama.ua.edu 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" wrote in message news:<2d518eb7-6410-4e6e-b18f-b5c1e45f4...@1g2000yqq.googlegroups.com>... 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 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
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" wrote in message news:<2d518eb7-6410-4e6e-b18f-b5c1e45f4...@1g2000yqq.googlegroups.com>... 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 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
