rename a dataset in acs routine?
Hi, I was asked a question today that I honestly don't know how to answer. The programmer has a (very large) series of jobs that generate fiche tapes that get created and have a expiration date but never are cataloged (because they all have exactly the same DSN). So over time, they ended up with about 30,000 tapes from the over 9,000 jobs that CA-1 keeps around until expiration date. Obviously, these are not the easiest datasets to use later because they need to look up the tape volser every time. The problem is that they want to know if there is a way to automatically catalog datasets at creation time, to which I told them we could, but only 1 of them because you can't catalog two datasets with the same name. But they want to have "the system" which I'm guessing is me :), dynamically rename these datasets at creation time to add a date and time, such as change HLQ.FICHE.TAPE to which I would dynamically make it HLQ.FICHE.TAPE.D091720.T1123, meaning today's date and the current time (if it was 11:23am). I can't think of a way to do that in an acs routine, or any other simple way, and I'm hoping that someone has an idea that might apply here. I think I can alter almost anything about the dataset, except the name. Is there something I am missing? Brian -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: rename a dataset in acs routine?
On 2020-09-18 5:36 PM, Brian Westerman wrote: would dynamically make it HLQ.FICHE.TAPE.D091720.T1123 I don't suppose the hard-coded data set name can be changed to include dynamic system symbols in new low-level qualifiers which would be resolved to the current date and time? Cheers, Greg -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: rename a dataset in acs routine?
Why can't his jobs generate dsns like HLQ.FICHE.TAPE.D091720.T1123 ? Can use system symbols to generate the date and time in the JCL output DD. Brian On Fri, 18 Sep 2020 at 15:36, Brian Westerman wrote: > Hi, > > I was asked a question today that I honestly don't know how to answer. > The programmer has a (very large) series of jobs that generate fiche tapes > that get created and have a expiration date but never are cataloged > (because they all have exactly the same DSN). So over time, they ended up > with about 30,000 tapes from the over 9,000 jobs that CA-1 keeps around > until expiration date. Obviously, these are not the easiest datasets to > use later because they need to look up the tape volser every time. > > The problem is that they want to know if there is a way to automatically > catalog datasets at creation time, to which I told them we could, but only > 1 of them because you can't catalog two datasets with the same name. But > they want to have "the system" which I'm guessing is me :), dynamically > rename these datasets at creation time to add a date and time, such as > change HLQ.FICHE.TAPE to which I would dynamically make it > HLQ.FICHE.TAPE.D091720.T1123, meaning today's date and the current time (if > it was 11:23am). > > I can't think of a way to do that in an acs routine, or any other simple > way, and I'm hoping that someone has an idea that might apply here. I > think I can alter almost anything about the dataset, except the name. Is > there something I am missing? > > Brian > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: rename a dataset in acs routine?
On Fri, 18 Sep 2020 17:34:17 +0800, Brian Fraser wrote: >Why can't his jobs generate dsns like HLQ.FICHE.TAPE.D091720.T1123 ? >Can use system symbols to generate the date and time in the JCL output DD. > I understand that system symbols are not supported in JCL DSNs because of o ambiguity between EXECSYS and CNVTSYS o queue latency -- the job might run at a time not matching the JCL symbols. (If the actual date and time values are important I understand they may be invalid because around midnight date and time might be fetched on different days, resulting in a 23+ hour error. Murphy says this will only be a problem when it matters. Rexx can do it right; why can't JCL?) >On Fri, 18 Sep 2020 at 15:36, Brian Westerman wrote: >... So over time, they ended up >> with about 30,000 tapes from the over 9,000 jobs that CA-1 keeps around >> until expiration date. >> >> The problem is that they want to know if there is a way to automatically >> catalog datasets at creation time, to which I told them we could, but only >> 1 of them because you can't catalog two datasets with the same name. But >> they want to have "the system" which I'm guessing is me :), dynamically >> rename these datasets at creation time to add a date and time, such as >> change HLQ.FICHE.TAPE to which I would dynamically make it >> HLQ.FICHE.TAPE.D091720.T1123, meaning today's date and the current time (if >> it was 11:23am). >> Use the seconds also, as D200917.T112359. With thousands of entries a collision is likely. And use YYMMDD for the date for easy sorting of displays. Is it possible to rename a tape data set? That would seem to require overwriting the HDR1 label, but tapes can't be updated in place. I'm imagining a sequence such as: Momentarily catalog HLQ.FICHE.TAPE DEFINE ALIAS HLQ.FICHE.TAPE.D200917.T112359 SYMBOLICRELATE HLQ.FICHE.TAPE Uncatalog HLQ.FICHE.TAPE. I understand that symbolic aliases remain when the RELATED name is uncatalogued. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: rename a dataset in acs routine?
On Fri, 18 Sep 2020 02:36:24 -0500 Brian Westerman wrote: :>I was asked a question today that I honestly don't know how to answer. The programmer has a (very large) series of jobs that generate fiche tapes that get created and have a expiration date but never are cataloged (because they all have exactly the same DSN). So over time, they ended up with about 30,000 tapes from the over 9,000 jobs that CA-1 keeps around until expiration date. Obviously, these are not the easiest datasets to use later because they need to look up the tape volser every time. :>The problem is that they want to know if there is a way to automatically catalog datasets at creation time, to which I told them we could, but only 1 of them because you can't catalog two datasets with the same name. But they want to have "the system" which I'm guessing is me :), dynamically rename these datasets at creation time to add a date and time, such as change HLQ.FICHE.TAPE to which I would dynamically make it HLQ.FICHE.TAPE.D091720.T1123, meaning today's date and the current time (if it was 11:23am). :>I can't think of a way to do that in an acs routine, or any other simple way, and I'm hoping that someone has an idea that might apply here. I think I can alter almost anything about the dataset, except the name. Is there something I am missing? That is what GDG's were built for. -- Binyamin Dissen http://www.dissensoftware.com Director, Dissen Software, Bar & Grill - Israel Should you use the mailblocks package and expect a response from me, you should preauthorize the dissensoftware.com domain. I very rarely bother responding to challenge/response systems, especially those from irresponsible companies. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: rename a dataset in acs routine?
Classification: HCL Internal Paul, That is incorrect. DYNAMIC system symbols were not supported until JES2 V2. (Z/OS 2.1+). The installation gets to define where symbols are resolved via JESPARMS STATIC system symbols have been supported for "eons". (e.g. SYSDATE, SYSIME, SYSUID). Init and Tuning ref defines the IBM supplied static symbols. HTH, -Original Message- From: IBM Mainframe Discussion List On Behalf Of Paul Gilmartin Sent: Friday, September 18, 2020 7:12 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: rename a dataset in acs routine? [CAUTION: This Email is from outside the Organization. Unless you trust the sender, Don’t click links or open attachments as it may be a Phishing email, which can steal your Information and compromise your Computer.] On Fri, 18 Sep 2020 17:34:17 +0800, Brian Fraser wrote: >Why can't his jobs generate dsns like HLQ.FICHE.TAPE.D091720.T1123 ? >Can use system symbols to generate the date and time in the JCL output DD. > I understand that system symbols are not supported in JCL DSNs because of o ambiguity between EXECSYS and CNVTSYS o queue latency -- the job might run at a time not matching the JCL symbols. (If the actual date and time values are important I understand they may be invalid because around midnight date and time might be fetched on different days, resulting in a 23+ hour error. Murphy says this will only be a problem when it matters. Rexx can do it right; why can't JCL?) >On Fri, 18 Sep 2020 at 15:36, Brian Westerman wrote: >... So over time, they ended up >> with about 30,000 tapes from the over 9,000 jobs that CA-1 keeps >> around until expiration date. >> >> The problem is that they want to know if there is a way to >> automatically catalog datasets at creation time, to which I told them >> we could, but only >> 1 of them because you can't catalog two datasets with the same name. >> But they want to have "the system" which I'm guessing is me :), >> dynamically rename these datasets at creation time to add a date and >> time, such as change HLQ.FICHE.TAPE to which I would dynamically make >> it HLQ.FICHE.TAPE.D091720.T1123, meaning today's date and the current >> time (if it was 11:23am). >> Use the seconds also, as D200917.T112359. With thousands of entries a collision is likely. And use YYMMDD for the date for easy sorting of displays. Is it possible to rename a tape data set? That would seem to require overwriting the HDR1 label, but tapes can't be updated in place. I'm imagining a sequence such as: Momentarily catalog HLQ.FICHE.TAPE DEFINE ALIAS HLQ.FICHE.TAPE.D200917.T112359 SYMBOLICRELATE HLQ.FICHE.TAPE Uncatalog HLQ.FICHE.TAPE. I understand that symbolic aliases remain when the RELATED name is uncatalogued. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ::DISCLAIMER:: The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: rename a dataset in acs routine?
Classification: HCL Internal As I am sure you know, ACS routines only apply at creation time and don’t have the power to alter the DSN anyway. ISTR a (fairly recent (z/OS 1+)) modification that will allow creation and cataloging of a 2nd dataset with the same name and avoiding the NOT CATLGD 2 jcl message. However only one dataset will be in the catalog (other ways to avoid this w/o changing the system default), It seems this is the old "its too much work to change all that JCL" (not to mention recreating all of the tapes). The only thing I can think of is to define a dataset alias pointing back to the volser. Considering this is tape I am not even sure it will work. This is not a savings in work based on the numbers below! However, it might be "automatable" via REXX or other utility, I hope this helps you formulate your response, -Original Message- From: IBM Mainframe Discussion List On Behalf Of Brian Westerman Sent: Friday, September 18, 2020 2:36 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: rename a dataset in acs routine? [CAUTION: This Email is from outside the Organization. Unless you trust the sender, Don’t click links or open attachments as it may be a Phishing email, which can steal your Information and compromise your Computer.] Hi, I was asked a question today that I honestly don't know how to answer. The programmer has a (very large) series of jobs that generate fiche tapes that get created and have a expiration date but never are cataloged (because they all have exactly the same DSN). So over time, they ended up with about 30,000 tapes from the over 9,000 jobs that CA-1 keeps around until expiration date. Obviously, these are not the easiest datasets to use later because they need to look up the tape volser every time. The problem is that they want to know if there is a way to automatically catalog datasets at creation time, to which I told them we could, but only 1 of them because you can't catalog two datasets with the same name. But they want to have "the system" which I'm guessing is me :), dynamically rename these datasets at creation time to add a date and time, such as change HLQ.FICHE.TAPE to which I would dynamically make it HLQ.FICHE.TAPE.D091720.T1123, meaning today's date and the current time (if it was 11:23am). I can't think of a way to do that in an acs routine, or any other simple way, and I'm hoping that someone has an idea that might apply here. I think I can alter almost anything about the dataset, except the name. Is there something I am missing? Brian -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ::DISCLAIMER:: The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: rename a dataset in acs routine?
On Sep 18, 2020, at 2:36 AM, Brian Westerman wrote: > > I can't think of a way to do that in an acs routine, or any other simple way, > and I'm hoping that someone has an idea that might apply here. I think I can > alter almost anything about the dataset, except the name. Is there something > I am missing? You can’t do it in the ACS routine, but it’s easy to do in JCL: //ddname DD DSN=HLQ.FICHE.TAPE.D&LYYMMDD..T&LHHMMSS -- Pew, Curtis G curtis@austin.utexas.edu -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: rename a dataset in acs routine?
>The problem is that they want to know if there is a way to automatically catalog datasets at creation time, to which I told them we could, but only 1 of them because you can't catalog two datasets with the same name. Generate the RENAME cards in the same program/JCL to rename the file from HLQ.FICHE.TAPE to HLQ.FICHE.TAPE.Yccyy.Mmm.Ddd.Thhmmss Run those rename control cards thru IDCAMS in the same JCL Thannks, Kolusu -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: rename a dataset in acs routine?
Mike designed REXX as a programming language. JCL is not and was never intended to be a programming language. This is something that should be handled in the environment that creates and submits the JCL. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Paul Gilmartin <000433f07816-dmarc-requ...@listserv.ua.edu> Sent: Friday, September 18, 2020 8:12 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: rename a dataset in acs routine? On Fri, 18 Sep 2020 17:34:17 +0800, Brian Fraser wrote: >Why can't his jobs generate dsns like HLQ.FICHE.TAPE.D091720.T1123 ? >Can use system symbols to generate the date and time in the JCL output DD. > I understand that system symbols are not supported in JCL DSNs because of o ambiguity between EXECSYS and CNVTSYS o queue latency -- the job might run at a time not matching the JCL symbols. (If the actual date and time values are important I understand they may be invalid because around midnight date and time might be fetched on different days, resulting in a 23+ hour error. Murphy says this will only be a problem when it matters. Rexx can do it right; why can't JCL?) >On Fri, 18 Sep 2020 at 15:36, Brian Westerman wrote: >... So over time, they ended up >> with about 30,000 tapes from the over 9,000 jobs that CA-1 keeps around >> until expiration date. >> >> The problem is that they want to know if there is a way to automatically >> catalog datasets at creation time, to which I told them we could, but only >> 1 of them because you can't catalog two datasets with the same name. But >> they want to have "the system" which I'm guessing is me :), dynamically >> rename these datasets at creation time to add a date and time, such as >> change HLQ.FICHE.TAPE to which I would dynamically make it >> HLQ.FICHE.TAPE.D091720.T1123, meaning today's date and the current time (if >> it was 11:23am). >> Use the seconds also, as D200917.T112359. With thousands of entries a collision is likely. And use YYMMDD for the date for easy sorting of displays. Is it possible to rename a tape data set? That would seem to require overwriting the HDR1 label, but tapes can't be updated in place. I'm imagining a sequence such as: Momentarily catalog HLQ.FICHE.TAPE DEFINE ALIAS HLQ.FICHE.TAPE.D200917.T112359 SYMBOLICRELATE HLQ.FICHE.TAPE Uncatalog HLQ.FICHE.TAPE. I understand that symbolic aliases remain when the RELATED name is uncatalogued. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: rename a dataset in acs routine?
//* //EXPORT EXPORT SYMLIST=(MNTH,DY,YR) //SETSYMBL SET MNTH=&LMON,DY=&LDAY,YR=&LYR4 //* HLQ.FICHE.TAPE.D&MNTH&DY&YR = HLQ.FICHE.TAPE.D09182020 Thank You and Please Be Safe! Len Sasso Systems Administrator Senior CSRA, A General Dynamics Information Technology Company 327 Columbia TPKE Rensselaer, NY 12144 Office Hours: M-F 7 AM - 3:45 PM Phone: (518) 257-4209 Cell: (518) 894-0879 Fax: (518) 257-4300 len.sa...@gdit.com URL: www.gdit.com From: IBM Mainframe Discussion List on behalf of Seymour J Metz Sent: Friday, September 18, 2020 12:26 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: rename a dataset in acs routine? [External: Use caution with links & attachments] Mike designed REXX as a programming language. JCL is not and was never intended to be a programming language. This is something that should be handled in the environment that creates and submits the JCL. -- Shmuel (Seymour J.) Metz https://urldefense.us/v3/__http://mason.gmu.edu/*smetz3__;fg!!JRQnnSFuzw7wjAKq6ti6!mkx1yaW-aw-3YqQyrzTWwpc4Xwrfp9G3-ZFVghxkJr8upxVCmr20Trud5LSTbQ$ From: IBM Mainframe Discussion List on behalf of Paul Gilmartin <000433f07816-dmarc-requ...@listserv.ua.edu> Sent: Friday, September 18, 2020 8:12 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: rename a dataset in acs routine? On Fri, 18 Sep 2020 17:34:17 +0800, Brian Fraser wrote: >Why can't his jobs generate dsns like HLQ.FICHE.TAPE.D091720.T1123 ? >Can use system symbols to generate the date and time in the JCL output DD. > I understand that system symbols are not supported in JCL DSNs because of o ambiguity between EXECSYS and CNVTSYS o queue latency -- the job might run at a time not matching the JCL symbols. (If the actual date and time values are important I understand they may be invalid because around midnight date and time might be fetched on different days, resulting in a 23+ hour error. Murphy says this will only be a problem when it matters. Rexx can do it right; why can't JCL?) >On Fri, 18 Sep 2020 at 15:36, Brian Westerman wrote: > ... So over time, they ended up >> with about 30,000 tapes from the over 9,000 jobs that CA-1 keeps around >> until expiration date. >> >> The problem is that they want to know if there is a way to automatically >> catalog datasets at creation time, to which I told them we could, but only >> 1 of them because you can't catalog two datasets with the same name. But >> they want to have "the system" which I'm guessing is me :), dynamically >> rename these datasets at creation time to add a date and time, such as >> change HLQ.FICHE.TAPE to which I would dynamically make it >> HLQ.FICHE.TAPE.D091720.T1123, meaning today's date and the current time (if >> it was 11:23am). >> Use the seconds also, as D200917.T112359. With thousands of entries a collision is likely. And use YYMMDD for the date for easy sorting of displays. Is it possible to rename a tape data set? That would seem to require overwriting the HDR1 label, but tapes can't be updated in place. I'm imagining a sequence such as: Momentarily catalog HLQ.FICHE.TAPE DEFINE ALIAS HLQ.FICHE.TAPE.D200917.T112359 SYMBOLICRELATE HLQ.FICHE.TAPE Uncatalog HLQ.FICHE.TAPE. I understand that symbolic aliases remain when the RELATED name is uncatalogued. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: rename a dataset in acs routine?
Well, if they want to use a chainsaw to open a bag of peanuts, you could write a JES exit, but the proper way to handle it is for the process that creates the JCL to generate a unique name. If they're using ISPF it's super easy to do it with File Tailoring, and many production control programs have similar capabilities. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Brian Westerman Sent: Friday, September 18, 2020 3:36 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: rename a dataset in acs routine? Hi, I was asked a question today that I honestly don't know how to answer. The programmer has a (very large) series of jobs that generate fiche tapes that get created and have a expiration date but never are cataloged (because they all have exactly the same DSN). So over time, they ended up with about 30,000 tapes from the over 9,000 jobs that CA-1 keeps around until expiration date. Obviously, these are not the easiest datasets to use later because they need to look up the tape volser every time. The problem is that they want to know if there is a way to automatically catalog datasets at creation time, to which I told them we could, but only 1 of them because you can't catalog two datasets with the same name. But they want to have "the system" which I'm guessing is me :), dynamically rename these datasets at creation time to add a date and time, such as change HLQ.FICHE.TAPE to which I would dynamically make it HLQ.FICHE.TAPE.D091720.T1123, meaning today's date and the current time (if it was 11:23am). I can't think of a way to do that in an acs routine, or any other simple way, and I'm hoping that someone has an idea that might apply here. I think I can alter almost anything about the dataset, except the name. Is there something I am missing? Brian -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: rename a dataset in acs routine?
Classification: HCL Internal See my earlier. IMO, the answer is Not Possible -Original Message- From: IBM Mainframe Discussion List On Behalf Of Brian Westerman Sent: Friday, September 18, 2020 2:36 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: rename a dataset in acs routine? [CAUTION: This Email is from outside the Organization. Unless you trust the sender, Don’t click links or open attachments as it may be a Phishing email, which can steal your Information and compromise your Computer.] Hi, I was asked a question today that I honestly don't know how to answer. The programmer has a (very large) series of jobs that generate fiche tapes that get created and have a expiration date but never are cataloged (because they all have exactly the same DSN). So over time, they ended up with about 30,000 tapes from the over 9,000 jobs that CA-1 keeps around until expiration date. Obviously, these are not the easiest datasets to use later because they need to look up the tape volser every time. The problem is that they want to know if there is a way to automatically catalog datasets at creation time, to which I told them we could, but only 1 of them because you can't catalog two datasets with the same name. But they want to have "the system" which I'm guessing is me :), dynamically rename these datasets at creation time to add a date and time, such as change HLQ.FICHE.TAPE to which I would dynamically make it HLQ.FICHE.TAPE.D091720.T1123, meaning today's date and the current time (if it was 11:23am). I can't think of a way to do that in an acs routine, or any other simple way, and I'm hoping that someone has an idea that might apply here. I think I can alter almost anything about the dataset, except the name. Is there something I am missing? Brian -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ::DISCLAIMER:: The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: rename a dataset in acs routine?
Renaming a tape? The last 17 characters are on the label of the tape so it must remain the same or any use will result in a Tape DSN name mismatch. You will also need to Update TMS, RMM, and any tape management system that uses the data set name. MUCH easier to just create new tape correctly and copy old tapes to the revised name and scratch the old tape. On Fri, Sep 18, 2020 at 7:12 AM Paul Gilmartin <000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > > On Fri, 18 Sep 2020 17:34:17 +0800, Brian Fraser wrote: > > >Why can't his jobs generate dsns like HLQ.FICHE.TAPE.D091720.T1123 ? > >Can use system symbols to generate the date and time in the JCL output DD. > > > I understand that system symbols are not supported in JCL DSNs because of > o ambiguity between EXECSYS and CNVTSYS > o queue latency -- the job might run at a time not matching the JCL symbols. > > (If the actual date and time values are important I understand they > may be invalid because around midnight date and time might be > fetched on different days, resulting in a 23+ hour error. Murphy > says this will only be a problem when it matters. Rexx can do it > right; why can't JCL?) > > > >On Fri, 18 Sep 2020 at 15:36, Brian Westerman wrote: > >... So over time, they ended up > >> with about 30,000 tapes from the over 9,000 jobs that CA-1 keeps around > >> until expiration date. > >> > >> The problem is that they want to know if there is a way to automatically > >> catalog datasets at creation time, to which I told them we could, but only > >> 1 of them because you can't catalog two datasets with the same name. But > >> they want to have "the system" which I'm guessing is me :), dynamically > >> rename these datasets at creation time to add a date and time, such as > >> change HLQ.FICHE.TAPE to which I would dynamically make it > >> HLQ.FICHE.TAPE.D091720.T1123, meaning today's date and the current time (if > >> it was 11:23am). > >> > Use the seconds also, as D200917.T112359. With thousands of entries > a collision is likely. And use YYMMDD for the date for easy sorting of > displays. > > Is it possible to rename a tape data set? That would seem to require > overwriting the HDR1 label, but tapes can't be updated in place. > > I'm imagining a sequence such as: > > Momentarily catalog HLQ.FICHE.TAPE > > DEFINE ALIAS HLQ.FICHE.TAPE.D200917.T112359 > SYMBOLICRELATE HLQ.FICHE.TAPE > > Uncatalog HLQ.FICHE.TAPE. I understand that symbolic aliases > remain when the RELATED name is uncatalogued. > > -- gil > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: rename a dataset in acs routine?
I'm all for editing the JCL, but they say there are far too many to do at one time, (and not screw it up) n Fri, 18 Sep 2020 19:32:01 +1000, Greg Price wrote: >On 2020-09-18 5:36 PM, Brian Westerman wrote: >> would dynamically make it HLQ.FICHE.TAPE.D091720.T1123 > >I don't suppose the hard-coded data set name can be changed to include >dynamic system symbols in new low-level qualifiers which would be >resolved to the current date and time? > >Cheers, >Greg > >-- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: rename a dataset in acs routine?
They would like an approach that didn't include editing the thousands of JCL sets. On Fri, 18 Sep 2020 17:34:17 +0800, Brian Fraser wrote: >Why can't his jobs generate dsns like HLQ.FICHE.TAPE.D091720.T1123 ? >Can use system symbols to generate the date and time in the JCL output DD. > >Brian > > >On Fri, 18 Sep 2020 at 15:36, Brian Westerman >wrote: > >> Hi, >> >> I was asked a question today that I honestly don't know how to answer. >> The programmer has a (very large) series of jobs that generate fiche tapes >> that get created and have a expiration date but never are cataloged >> (because they all have exactly the same DSN). So over time, they ended up >> with about 30,000 tapes from the over 9,000 jobs that CA-1 keeps around >> until expiration date. Obviously, these are not the easiest datasets to >> use later because they need to look up the tape volser every time. >> >> The problem is that they want to know if there is a way to automatically >> catalog datasets at creation time, to which I told them we could, but only >> 1 of them because you can't catalog two datasets with the same name. But >> they want to have "the system" which I'm guessing is me :), dynamically >> rename these datasets at creation time to add a date and time, such as >> change HLQ.FICHE.TAPE to which I would dynamically make it >> HLQ.FICHE.TAPE.D091720.T1123, meaning today's date and the current time (if >> it was 11:23am). >> >> I can't think of a way to do that in an acs routine, or any other simple >> way, and I'm hoping that someone has an idea that might apply here. I >> think I can alter almost anything about the dataset, except the name. Is >> there something I am missing? >> >> Brian >> >> -- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >> > >-- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: rename a dataset in acs routine?
dealing with the existing tapes is doable via a rexx exec that submits a series of IEBGENER, but it's the JCL that they want (preferably SMS) to deal with. On Fri, 18 Sep 2020 07:12:15 -0500, Paul Gilmartin wrote: >On Fri, 18 Sep 2020 17:34:17 +0800, Brian Fraser wrote: > >>Why can't his jobs generate dsns like HLQ.FICHE.TAPE.D091720.T1123 ? >>Can use system symbols to generate the date and time in the JCL output DD. >> >I understand that system symbols are not supported in JCL DSNs because of >o ambiguity between EXECSYS and CNVTSYS >o queue latency -- the job might run at a time not matching the JCL symbols. > >(If the actual date and time values are important I understand they >may be invalid because around midnight date and time might be >fetched on different days, resulting in a 23+ hour error. Murphy >says this will only be a problem when it matters. Rexx can do it >right; why can't JCL?) > > >>On Fri, 18 Sep 2020 at 15:36, Brian Westerman wrote: >>... So over time, they ended up >>> with about 30,000 tapes from the over 9,000 jobs that CA-1 keeps around >>> until expiration date. >>> >>> The problem is that they want to know if there is a way to automatically >>> catalog datasets at creation time, to which I told them we could, but only >>> 1 of them because you can't catalog two datasets with the same name. But >>> they want to have "the system" which I'm guessing is me :), dynamically >>> rename these datasets at creation time to add a date and time, such as >>> change HLQ.FICHE.TAPE to which I would dynamically make it >>> HLQ.FICHE.TAPE.D091720.T1123, meaning today's date and the current time (if >>> it was 11:23am). >>> >Use the seconds also, as D200917.T112359. With thousands of entries >a collision is likely. And use YYMMDD for the date for easy sorting of >displays. > >Is it possible to rename a tape data set? That would seem to require >overwriting the HDR1 label, but tapes can't be updated in place. > >I'm imagining a sequence such as: > >Momentarily catalog HLQ.FICHE.TAPE > >DEFINE ALIAS HLQ.FICHE.TAPE.D200917.T112359 >SYMBOLICRELATE HLQ.FICHE.TAPE > >Uncatalog HLQ.FICHE.TAPE. I understand that symbolic aliases >remain when the RELATED name is uncatalogued. > >-- gil > >-- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: rename a dataset in acs routine?
I agree, but that decision was made 30 years ago. On Fri, 18 Sep 2020 15:28:40 +0300, Binyamin Dissen wrote: >On Fri, 18 Sep 2020 02:36:24 -0500 Brian Westerman > wrote: > >:>I was asked a question today that I honestly don't know how to answer. The >programmer has a (very large) series of jobs that generate fiche tapes that >get created and have a expiration date but never are cataloged (because they >all have exactly the same DSN). So over time, they ended up with about 30,000 >tapes from the over 9,000 jobs that CA-1 keeps around until expiration date. >Obviously, these are not the easiest datasets to use later because they need >to look up the tape volser every time. > >:>The problem is that they want to know if there is a way to automatically >catalog datasets at creation time, to which I told them we could, but only 1 >of them because you can't catalog two datasets with the same name. But they >want to have "the system" which I'm guessing is me :), dynamically rename >these datasets at creation time to add a date and time, such as change >HLQ.FICHE.TAPE to which I would dynamically make it >HLQ.FICHE.TAPE.D091720.T1123, meaning today's date and the current time (if it >was 11:23am). > >:>I can't think of a way to do that in an acs routine, or any other simple >way, and I'm hoping that someone has an idea that might apply here. I think I >can alter almost anything about the dataset, except the name. Is there >something I am missing? > >That is what GDG's were built for. > >-- >Binyamin Dissen >http://www.dissensoftware.com > >Director, Dissen Software, Bar & Grill - Israel > > >Should you use the mailblocks package and expect a response from me, >you should preauthorize the dissensoftware.com domain. > >I very rarely bother responding to challenge/response systems, >especially those from irresponsible companies. > >-- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: rename a dataset in acs routine?
I don't see that you can do that with tapes, the hdr1 won't match the new DSN. On Fri, 18 Sep 2020 07:19:33 -0700, Sri h Kolusu wrote: >>The problem is that they want to know if there is a way to automatically >catalog datasets at creation time, to which I told them we could, but only >1 of them because you can't catalog two datasets with the same name. > >Generate the RENAME cards in the same program/JCL to rename the file from >HLQ.FICHE.TAPE to HLQ.FICHE.TAPE.Yccyy.Mmm.Ddd.Thhmmss > >Run those rename control cards thru IDCAMS in the same JCL > > >Thannks, >Kolusu > >-- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: rename a dataset in acs routine?
Changing the JCL is my preferred method, but they would like an "easier" way. Also, D09182020 is 9 characters, so would cause a JCL error. But I understand what you meant. :) Brian On Fri, 18 Sep 2020 16:37:30 +, Sasso, Len wrote: > //* //EXPORT EXPORT SYMLIST=(MNTH,DY,YR) //SETSYMBL SET MNTH=&LMON,DY=&LDAY,YR=&LYR4 //* HLQ.FICHE.TAPE.D&MNTH&DY&YR = HLQ.FICHE.TAPE.D09182020 Thank You and�Please Be Safe! Len Sasso Systems Administrator Senior CSRA, A General Dynamics Information Technology Company 327 Columbia TPKE Rensselaer, NY 12144 Office Hours: M-F� 7 AM - 3:45 PM Phone: (518) 257-4209 Cell: (518) 894-0879 Fax: (518) 257-4300 len.sa...@gdit.com URL:�www.gdit.com � � From: IBM Mainframe Discussion List on behalf of Seymour J Metz Sent: Friday, September 18, 2020 12:26 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: rename a dataset in acs routine? � �[External: Use caution with links & attachments] Mike designed REXX as a programming language. JCL is not and was never intended to be a programming language. This is something that should be handled in the environment that creates and submits the JCL. -- Shmuel (Seymour J.) Metz https://urldefense.us/v3/__http://mason.gmu.edu/*smetz3__;fg!!JRQnnSFuzw7wjAKq6ti6!mkx1yaW-aw-3YqQyrzTWwpc4Xwrfp9G3-ZFVghxkJr8upxVCmr20Trud5LSTbQ$ From: IBM Mainframe Discussion List on behalf of Paul Gilmartin <000433f07816-dmarc-requ...@listserv.ua.edu> Sent: Friday, September 18, 2020 8:12 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: rename a dataset in acs routine? On Fri, 18 Sep 2020 17:34:17 +0800, Brian Fraser wrote: >Why can't his jobs generate dsns like� HLQ.FICHE.TAPE.D091720.T1123 ? >Can use system symbols to generate the date and time in the JCL output DD. > I understand that system symbols are not supported in JCL DSNs because of o ambiguity between EXECSYS and CNVTSYS o queue latency -- the job might run at a time not matching the JCL symbols. (If the actual date and time values are important I understand they may be invalid because around midnight date and time might be fetched on different days, resulting in a 23+ hour error.� Murphy says this will only be a problem when it matters.� Rexx can do it right; why can't JCL?) >On Fri, 18 Sep 2020 at 15:36, Brian Westerman wrote: >��� ...� So over time, they ended up >> with about 30,000 tapes from the over 9,000 jobs that CA-1 keeps around >> until expiration date. >> >> The problem is that they want to know if there is a way to automatically >> catalog datasets at creation time, to which I told them we could, but only >> 1 of them because you can't catalog two datasets with the same name.� But >> they want to have "the system" which I'm guessing is me :), dynamically >> rename these datasets at creation time to add a date and time, such as >> change HLQ.FICHE.TAPE to which I would dynamically make it >> HLQ.FICHE.TAPE.D091720.T1123, meaning today's date and the current time (if >> it was 11:23am). >> Use the seconds also, as D200917.T112359.� With thousands of entries a collision is likely.� And use YYMMDD for the date for easy sorting of displays. Is it possible to rename a tape data set?� That would seem to require overwriting the HDR1 label, but tapes can't be updated in place. I'm imagining a sequence such as: Momentarily catalog HLQ.FICHE.TAPE DEFINE ALIAS HLQ.FICHE.TAPE.D200917.T112359 ��� SYMBOLICRELATE HLQ.FICHE.TAPE Uncatalog HLQ.FICHE.TAPE.� I understand that symbolic aliases remain when the RELATED name is uncatalogued. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >-- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: rename a dataset in acs routine?
Actually I'm leaning towards the JES or SMF UJI exit as well. File tailoring doesn't help in this case because most of the JCL doesn't get submitted via TSO. Brian On Fri, 18 Sep 2020 16:41:29 +, Seymour J Metz wrote: >Well, if they want to use a chainsaw to open a bag of peanuts, you could write >a JES exit, but the proper way to handle it is for the process that creates >the JCL to generate a unique name. If they're using ISPF it's super easy to do >it with File Tailoring, and many production control programs have similar >capabilities. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Brian Westerman Sent: Friday, September 18, 2020 3:36 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: rename a dataset in acs routine? Hi, I was asked a question today that I honestly don't know how to answer. The programmer has a (very large) series of jobs that generate fiche tapes that get created and have a expiration date but never are cataloged (because they all have exactly the same DSN). So over time, they ended up with about 30,000 tapes from the over 9,000 jobs that CA-1 keeps around until expiration date. Obviously, these are not the easiest datasets to use later because they need to look up the tape volser every time. The problem is that they want to know if there is a way to automatically catalog datasets at creation time, to which I told them we could, but only 1 of them because you can't catalog two datasets with the same name. But they want to have "the system" which I'm guessing is me :), dynamically rename these datasets at creation time to add a date and time, such as change HLQ.FICHE.TAPE to which I would dynamically make it HLQ.FICHE.TAPE.D091720.T1123, meaning today's date and the current time (if it was 11:23am). I can't think of a way to do that in an acs routine, or any other simple way, and I'm hoping that someone has an idea that might apply here. I think I can alter almost anything about the dataset, except the name. Is there something I am missing? Brian -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >-- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: rename a dataset in acs routine?
On Fri, 18 Sep 2020 23:05:04 -0500, Brian Westerman wrote: >They would like an approach that didn't include editing the thousands of JCL >sets. > Thousands!? Not just one with parameters!? The design is wrong. It will remain broken until it's fixed. Facing a similar requirement once, I appended a minimal data set with a unique name to each tape and catalogued that. I needed to deceive the tape management system; something like EXPDT=99000. I don't recall the details. I might have needed VOL=REF,LABEL=(1,SL) to get to the payload data sets. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: rename a dataset in acs routine?
JES exit 6 > -Original Message- > From: IBM Mainframe Discussion List On > Behalf Of Brian Westerman > Sent: Friday, September 18, 2020 9:05 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: rename a dataset in acs routine? > > They would like an approach that didn't include editing the thousands of JCL > sets. > > On Fri, 18 Sep 2020 17:34:17 +0800, Brian Fraser > wrote: > > >Why can't his jobs generate dsns like HLQ.FICHE.TAPE.D091720.T1123 ? > >Can use system symbols to generate the date and time in the JCL output > DD. > > > >Brian > > > > > >On Fri, 18 Sep 2020 at 15:36, Brian Westerman > > >wrote: > > > >> Hi, > >> > >> I was asked a question today that I honestly don't know how to answer. > >> The programmer has a (very large) series of jobs that generate fiche tapes > >> that get created and have a expiration date but never are cataloged > >> (because they all have exactly the same DSN). So over time, they ended > up > >> with about 30,000 tapes from the over 9,000 jobs that CA-1 keeps around > >> until expiration date. Obviously, these are not the easiest datasets to > >> use later because they need to look up the tape volser every time. > >> > >> The problem is that they want to know if there is a way to automatically > >> catalog datasets at creation time, to which I told them we could, but only > >> 1 of them because you can't catalog two datasets with the same name. > But > >> they want to have "the system" which I'm guessing is me :), dynamically > >> rename these datasets at creation time to add a date and time, such as > >> change HLQ.FICHE.TAPE to which I would dynamically make it > >> HLQ.FICHE.TAPE.D091720.T1123, meaning today's date and the current > time (if > >> it was 11:23am). > >> > >> I can't think of a way to do that in an acs routine, or any other simple > >> way, and I'm hoping that someone has an idea that might apply here. I > >> think I can alter almost anything about the dataset, except the name. Is > >> there something I am missing? > >> > >> Brian > >> > >> -- > >> For IBM-MAIN subscribe / signoff / archive access instructions, > >> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > >> > > > >-- > >For IBM-MAIN subscribe / signoff / archive access instructions, > >send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: rename a dataset in acs routine?
On Fri, 18 Sep 2020 23:10:24 -0500, Brian Westerman wrote: >I don't see that you can do that with tapes, the hdr1 won't match the new DSN. > So the tapes are labeled. Alas. I'm curious: how do the users access those data sets in subsequent jobs? Examine the logs of the creating jobs for allocation messages and code VOL=SER in the later jobs? Cataloging unique DSNs hardly alleviates the problem -- it might aggravate it: 3 times as many keystrokes to modify -- two DSN qualifiers versus one volser. How would you deal with DSN collisions? With "thousands" of generated names this is highly likely: https://en.wikipedia.org/wiki/Birthday_problem If you do nothing, one job with DISP=(NEW,CATLG) will wait for the other to complete; write the data set then get NOT CATALOGUED. There's a meta-process problem here. At some point programmers should have been instructed not to create thousands of uncatalogued data sets with identical names. If you adopt unique catalogued DSNs, might DASD be a medium preferable to tape? -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: rename a dataset in acs routine?
As a microfische job, it is a collection of printouts, not used for input. On Sat, Sep 19, 2020 at 8:51 AM Paul Gilmartin <000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > > On Fri, 18 Sep 2020 23:10:24 -0500, Brian Westerman wrote: > > >I don't see that you can do that with tapes, the hdr1 won't match the new > >DSN. > > > So the tapes are labeled. Alas. > > I'm curious: how do the users access those data sets in subsequent jobs? > Examine the logs of the creating jobs for allocation messages and code > VOL=SER in the later jobs? > > Cataloging unique DSNs hardly alleviates the problem -- it might > aggravate it: 3 times as many keystrokes to modify -- two DSN > qualifiers versus one volser. > > How would you deal with DSN collisions? With "thousands" of > generated names this is highly likely: > https://en.wikipedia.org/wiki/Birthday_problem > > If you do nothing, one job with DISP=(NEW,CATLG) will wait for the > other to complete; write the data set then get NOT CATALOGUED. > > There's a meta-process problem here. At some point programmers > should have been instructed not to create thousands of uncatalogued > data sets with identical names. > > If you adopt unique catalogued DSNs, might DASD be a medium > preferable to tape? > > -- gil > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: rename a dataset in acs routine?
On Sat, 19 Sep 2020 09:24:32 -0500, Mike Schwab wrote: >As a microfische job, it is a collection of printouts, not used for input. > ??? Write-only memory? Why bother? And why keep them? Would a temp DSN be suitable? >On Sat, Sep 19, 2020 at 8:51 AM Paul Gilmartin wrote: >> >> On Fri, 18 Sep 2020 23:10:24 -0500, Brian Westerman wrote: >> >> >I don't see that you can do that with tapes, the hdr1 won't match the new >> >DSN. >> > >> So the tapes are labeled. Alas. >> >> I'm curious: how do the users access those data sets in subsequent jobs? >> Examine the logs of the creating jobs for allocation messages and code >> VOL=SER in the later jobs? >> >> Cataloging unique DSNs hardly alleviates the problem -- it might >> aggravate it: 3 times as many keystrokes to modify -- two DSN >> qualifiers versus one volser. >> >> How would you deal with DSN collisions? With "thousands" of >> generated names this is highly likely: >> https://en.wikipedia.org/wiki/Birthday_problem >> >> If you do nothing, one job with DISP=(NEW,CATLG) will wait for the >> other to complete; write the data set then get NOT CATALOGUED. >> >> There's a meta-process problem here. At some point programmers >> should have been instructed not to create thousands of uncatalogued >> data sets with identical names. >> >> If you adopt unique catalogued DSNs, might DASD be a medium >> preferable to tape? -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: rename a dataset in acs routine?
Is fiche still a thing? On Sat, Sep 19, 2020 at 11:34 AM Paul Gilmartin < 000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > On Sat, 19 Sep 2020 09:24:32 -0500, Mike Schwab wrote: > > > > >As a microfische job, it is a collection of printouts, not used for input. > > > > > ??? > > Write-only memory? Why bother? And why keep them? > > Would a temp DSN be suitable? > > > > >On Sat, Sep 19, 2020 at 8:51 AM Paul Gilmartin wrote: > > >> > > >> On Fri, 18 Sep 2020 23:10:24 -0500, Brian Westerman wrote: > > >> > > >> >I don't see that you can do that with tapes, the hdr1 won't match the > new DSN. > > >> > > > >> So the tapes are labeled. Alas. > > >> > > >> I'm curious: how do the users access those data sets in subsequent jobs? > > >> Examine the logs of the creating jobs for allocation messages and code > > >> VOL=SER in the later jobs? > > >> > > >> Cataloging unique DSNs hardly alleviates the problem -- it might > > >> aggravate it: 3 times as many keystrokes to modify -- two DSN > > >> qualifiers versus one volser. > > >> > > >> How would you deal with DSN collisions? With "thousands" of > > >> generated names this is highly likely: > > >> https://en.wikipedia.org/wiki/Birthday_problem > > >> > > >> If you do nothing, one job with DISP=(NEW,CATLG) will wait for the > > >> other to complete; write the data set then get NOT CATALOGUED. > > >> > > >> There's a meta-process problem here. At some point programmers > > >> should have been instructed not to create thousands of uncatalogued > > >> data sets with identical names. > > >> > > >> If you adopt unique catalogued DSNs, might DASD be a medium > > >> preferable to tape? > > > > -- gil > > > > -- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: rename a dataset in acs routine?
They are mifrofiche tapes, and they are not sent out for processing any more. They exist only on the off chance that "someday" they might be needed to recreate something. When they are needed, they use the DSN=,VOL= to use them. On Sat, 19 Sep 2020 08:50:50 -0500, Paul Gilmartin wrote: >On Fri, 18 Sep 2020 23:10:24 -0500, Brian Westerman wrote: > >>I don't see that you can do that with tapes, the hdr1 won't match the new DSN. >> >So the tapes are labeled. Alas. > >I'm curious: how do the users access those data sets in subsequent jobs? >Examine the logs of the creating jobs for allocation messages and code >VOL=SER in the later jobs? > >Cataloging unique DSNs hardly alleviates the problem -- it might >aggravate it: 3 times as many keystrokes to modify -- two DSN >qualifiers versus one volser. > >How would you deal with DSN collisions? With "thousands" of >generated names this is highly likely: >https://en.wikipedia.org/wiki/Birthday_problem > >If you do nothing, one job with DISP=(NEW,CATLG) will wait for the >other to complete; write the data set then get NOT CATALOGUED. > >There's a meta-process problem here. At some point programmers >should have been instructed not to create thousands of uncatalogued >data sets with identical names. > >If you adopt unique catalogued DSNs, might DASD be a medium >preferable to tape? > >-- gil > >-- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: rename a dataset in acs routine?
Maybe use a database like EOS to suck up all those uncataloged tapes and index them? Hopefully, there is some kind of machine readable index data created when the fiche tape is created. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: rename a dataset in acs routine?
ITYM IEFUJV; IEFUJI doesn't have the right interfaces. I'd probably use an internal text exit. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Brian Westerman Sent: Saturday, September 19, 2020 12:14 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: rename a dataset in acs routine? Actually I'm leaning towards the JES or SMF UJI exit as well. File tailoring doesn't help in this case because most of the JCL doesn't get submitted via TSO. Brian On Fri, 18 Sep 2020 16:41:29 +, Seymour J Metz wrote: >Well, if they want to use a chainsaw to open a bag of peanuts, you could write >a JES exit, but the proper way to handle it is for the process that creates >the JCL to generate a unique name. If they're using ISPF it's super easy to do >it with File Tailoring, and many production control programs have similar >capabilities. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Brian Westerman Sent: Friday, September 18, 2020 3:36 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: rename a dataset in acs routine? Hi, I was asked a question today that I honestly don't know how to answer. The programmer has a (very large) series of jobs that generate fiche tapes that get created and have a expiration date but never are cataloged (because they all have exactly the same DSN). So over time, they ended up with about 30,000 tapes from the over 9,000 jobs that CA-1 keeps around until expiration date. Obviously, these are not the easiest datasets to use later because they need to look up the tape volser every time. The problem is that they want to know if there is a way to automatically catalog datasets at creation time, to which I told them we could, but only 1 of them because you can't catalog two datasets with the same name. But they want to have "the system" which I'm guessing is me :), dynamically rename these datasets at creation time to add a date and time, such as change HLQ.FICHE.TAPE to which I would dynamically make it HLQ.FICHE.TAPE.D091720.T1123, meaning today's date and the current time (if it was 11:23am). I can't think of a way to do that in an acs routine, or any other simple way, and I'm hoping that someone has an idea that might apply here. I think I can alter almost anything about the dataset, except the name. Is there something I am missing? Brian -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >-- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: rename a dataset in acs routine?
I apologize if this has been discussed The SYSTEM Symbols can be made available to JES2 batch jobs The shop needs to determine if they want that to happen https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1 .ieab600/jclsymstr.htm The three types of symbols that can be used for JES2 in-stream substitution are JCL Symbols, JES Symbols and System Symbols: On a JES2 JOBCLASS definition, the field SYSSYM needs to be ALLOW rather than DISALLOW If there Is scheduling software available, it is possible it might provide symbolic substitution at Submission time (I know CA Workload Manager ESP can do that) Otherwise, you might want to have something like s REXX be executed (or language of your choice) to generate the JCL then submit into the Internal Reader ACS routines cannot do this type of function. Best of luck Lizette -Original Message- From: IBM Mainframe Discussion List On Behalf Of Seymour J Metz Sent: Sunday, September 20, 2020 5:47 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: rename a dataset in acs routine? ITYM IEFUJV; IEFUJI doesn't have the right interfaces. I'd probably use an internal text exit. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Brian Westerman Sent: Saturday, September 19, 2020 12:14 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: rename a dataset in acs routine? Actually I'm leaning towards the JES or SMF UJI exit as well. File tailoring doesn't help in this case because most of the JCL doesn't get submitted via TSO. Brian On Fri, 18 Sep 2020 16:41:29 +, Seymour J Metz wrote: >Well, if they want to use a chainsaw to open a bag of peanuts, you could write a JES exit, but the proper way to handle it is for the process that creates the JCL to generate a unique name. If they're using ISPF it's super easy to do it with File Tailoring, and many production control programs have similar capabilities. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Brian Westerman Sent: Friday, September 18, 2020 3:36 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: rename a dataset in acs routine? Hi, I was asked a question today that I honestly don't know how to answer. The programmer has a (very large) series of jobs that generate fiche tapes that get created and have a expiration date but never are cataloged (because they all have exactly the same DSN). So over time, they ended up with about 30,000 tapes from the over 9,000 jobs that CA-1 keeps around until expiration date. Obviously, these are not the easiest datasets to use later because they need to look up the tape volser every time. The problem is that they want to know if there is a way to automatically catalog datasets at creation time, to which I told them we could, but only 1 of them because you can't catalog two datasets with the same name. But they want to have "the system" which I'm guessing is me :), dynamically rename these datasets at creation time to add a date and time, such as change HLQ.FICHE.TAPE to which I would dynamically make it HLQ.FICHE.TAPE.D091720.T1123, meaning today's date and the current time (if it was 11:23am). I can't think of a way to do that in an acs routine, or any other simple way, and I'm hoping that someone has an idea that might apply here. I think I can alter almost anything about the dataset, except the name. Is there something I am missing? Brian -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >-- >For IBM-MAIN subscribe / signoff / archive access instructions, send >email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: rename a dataset in acs routine?
Classification: HCL Internal Don't forget to expire the old tapes after successful copy. -Original Message- From: IBM Mainframe Discussion List On Behalf Of Brian Westerman Sent: Friday, September 18, 2020 11:07 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: rename a dataset in acs routine? [CAUTION: This Email is from outside the Organization. Unless you trust the sender, Don’t click links or open attachments as it may be a Phishing email, which can steal your Information and compromise your Computer.] dealing with the existing tapes is doable via a rexx exec that submits a series of IEBGENER, but it's the JCL that they want (preferably SMS) to deal with. On Fri, 18 Sep 2020 07:12:15 -0500, Paul Gilmartin wrote: >On Fri, 18 Sep 2020 17:34:17 +0800, Brian Fraser wrote: > >>Why can't his jobs generate dsns like HLQ.FICHE.TAPE.D091720.T1123 ? >>Can use system symbols to generate the date and time in the JCL output DD. >> >I understand that system symbols are not supported in JCL DSNs because >of o ambiguity between EXECSYS and CNVTSYS o queue latency -- the job >might run at a time not matching the JCL symbols. > >(If the actual date and time values are important I understand they may >be invalid because around midnight date and time might be fetched on >different days, resulting in a 23+ hour error. Murphy says this will >only be a problem when it matters. Rexx can do it right; why can't >JCL?) > > >>On Fri, 18 Sep 2020 at 15:36, Brian Westerman wrote: >>... So over time, they ended up >>> with about 30,000 tapes from the over 9,000 jobs that CA-1 keeps >>> around until expiration date. >>> >>> The problem is that they want to know if there is a way to >>> automatically catalog datasets at creation time, to which I told >>> them we could, but only >>> 1 of them because you can't catalog two datasets with the same name. >>> But they want to have "the system" which I'm guessing is me :), >>> dynamically rename these datasets at creation time to add a date and >>> time, such as change HLQ.FICHE.TAPE to which I would dynamically >>> make it HLQ.FICHE.TAPE.D091720.T1123, meaning today's date and the >>> current time (if it was 11:23am). >>> >Use the seconds also, as D200917.T112359. With thousands of entries a >collision is likely. And use YYMMDD for the date for easy sorting of >displays. > >Is it possible to rename a tape data set? That would seem to require >overwriting the HDR1 label, but tapes can't be updated in place. > >I'm imagining a sequence such as: > >Momentarily catalog HLQ.FICHE.TAPE > >DEFINE ALIAS HLQ.FICHE.TAPE.D200917.T112359 >SYMBOLICRELATE HLQ.FICHE.TAPE > >Uncatalog HLQ.FICHE.TAPE. I understand that symbolic aliases remain >when the RELATED name is uncatalogued. > >-- gil > >-- >For IBM-MAIN subscribe / signoff / archive access instructions, send >email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ::DISCLAIMER:: The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: rename a dataset in acs routine?
What's the down side? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Lizette Koehler Sent: Sunday, September 20, 2020 11:06 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: rename a dataset in acs routine? I apologize if this has been discussed The SYSTEM Symbols can be made available to JES2 batch jobs The shop needs to determine if they want that to happen https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1 .ieab600/jclsymstr.htm The three types of symbols that can be used for JES2 in-stream substitution are JCL Symbols, JES Symbols and System Symbols: On a JES2 JOBCLASS definition, the field SYSSYM needs to be ALLOW rather than DISALLOW If there Is scheduling software available, it is possible it might provide symbolic substitution at Submission time (I know CA Workload Manager ESP can do that) Otherwise, you might want to have something like s REXX be executed (or language of your choice) to generate the JCL then submit into the Internal Reader ACS routines cannot do this type of function. Best of luck Lizette -Original Message- From: IBM Mainframe Discussion List On Behalf Of Seymour J Metz Sent: Sunday, September 20, 2020 5:47 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: rename a dataset in acs routine? ITYM IEFUJV; IEFUJI doesn't have the right interfaces. I'd probably use an internal text exit. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Brian Westerman Sent: Saturday, September 19, 2020 12:14 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: rename a dataset in acs routine? Actually I'm leaning towards the JES or SMF UJI exit as well. File tailoring doesn't help in this case because most of the JCL doesn't get submitted via TSO. Brian On Fri, 18 Sep 2020 16:41:29 +, Seymour J Metz wrote: >Well, if they want to use a chainsaw to open a bag of peanuts, you could write a JES exit, but the proper way to handle it is for the process that creates the JCL to generate a unique name. If they're using ISPF it's super easy to do it with File Tailoring, and many production control programs have similar capabilities. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Brian Westerman Sent: Friday, September 18, 2020 3:36 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: rename a dataset in acs routine? Hi, I was asked a question today that I honestly don't know how to answer. The programmer has a (very large) series of jobs that generate fiche tapes that get created and have a expiration date but never are cataloged (because they all have exactly the same DSN). So over time, they ended up with about 30,000 tapes from the over 9,000 jobs that CA-1 keeps around until expiration date. Obviously, these are not the easiest datasets to use later because they need to look up the tape volser every time. The problem is that they want to know if there is a way to automatically catalog datasets at creation time, to which I told them we could, but only 1 of them because you can't catalog two datasets with the same name. But they want to have "the system" which I'm guessing is me :), dynamically rename these datasets at creation time to add a date and time, such as change HLQ.FICHE.TAPE to which I would dynamically make it HLQ.FICHE.TAPE.D091720.T1123, meaning today's date and the current time (if it was 11:23am). I can't think of a way to do that in an acs routine, or any other simple way, and I'm hoping that someone has an idea that might apply here. I think I can alter almost anything about the dataset, except the name. Is there something I am missing? Brian -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >-- >For IBM-MAIN subscribe / signoff / archive access instructions, send >email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: I
Re: rename a dataset in acs routine?
Jes Exit 6 seems to be the best place to do this. There is only a max of one dataset per job and it's never re-read in that same job (or any other) and we already know what the dataset(s) are called, so it's pretty simple to scan for the DSN= text object and if the supplied DSN matches one of the ones we want, we just replace it with the symbolic. Actually at that point in time I could just insert the actual date and time. The test version does just that. Of course as soon as I started writing the exit, several people came in to ask for more "features". The only thing I forgot was a way to bypass the exit in the event that I wanted to actually process one of the tapes manually (by volser), but I now have that worked out as well, I just don't have time to test it properly at this time. I also think it's possible to limit the processing to ONLY the jobs that we know will contain the fiche tapes, so I'm waiting on a programmer to tell me if that's true. Brian On Mon, 21 Sep 2020 13:11:56 +, Seymour J Metz wrote: >What's the down side? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Lizette Koehler Sent: Sunday, September 20, 2020 11:06 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: rename a dataset in acs routine? I apologize if this has been discussed The SYSTEM Symbols can be made available to JES2 batch jobs The shop needs to determine if they want that to happen https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1 .ieab600/jclsymstr.htm The three types of symbols that can be used for JES2 in-stream substitution are JCL Symbols, JES Symbols and System Symbols: On a JES2 JOBCLASS definition, the field SYSSYM needs to be ALLOW rather than DISALLOW If there Is scheduling software available, it is possible it might provide symbolic substitution at Submission time (I know CA Workload Manager ESP can do that) Otherwise, you might want to have something like s REXX be executed (or language of your choice) to generate the JCL then submit into the Internal Reader ACS routines cannot do this type of function. Best of luck Lizette -Original Message- From: IBM Mainframe Discussion List On Behalf Of Seymour J Metz Sent: Sunday, September 20, 2020 5:47 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: rename a dataset in acs routine? ITYM IEFUJV; IEFUJI doesn't have the right interfaces. I'd probably use an internal text exit. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Brian Westerman Sent: Saturday, September 19, 2020 12:14 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: rename a dataset in acs routine? Actually I'm leaning towards the JES or SMF UJI exit as well. File tailoring doesn't help in this case because most of the JCL doesn't get submitted via TSO. Brian On Fri, 18 Sep 2020 16:41:29 +, Seymour J Metz wrote: >Well, if they want to use a chainsaw to open a bag of peanuts, you could write a JES exit, but the proper way to handle it is for the process that creates the JCL to generate a unique name. If they're using ISPF it's super easy to do it with File Tailoring, and many production control programs have similar capabilities. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Brian Westerman Sent: Friday, September 18, 2020 3:36 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: rename a dataset in acs routine? Hi, I was asked a question today that I honestly don't know how to answer. The programmer has a (very large) series of jobs that generate fiche tapes that get created and have a expiration date but never are cataloged (because they all have exactly the same DSN). So over time, they ended up with about 30,000 tapes from the over 9,000 jobs that CA-1 keeps around until expiration date. Obviously, these are not the easiest datasets to use later because they need to look up the tape volser every time. The problem is that they want to know if there is a way to automatically catalog datasets at creation time, to which I told them we could, but only 1 of them because you can't catalog two datasets with the same name. But they want to have "the system" which I'm guessing is me :), dynamically rename these datasets at creation time to add a date and time, such as change HLQ.FICHE.TAPE to which I would dynamically make it HLQ.FICHE.TAPE.D091720.T1123, meaning today's date and the current time (if it was 11:23am). I can't think of a way to do that in an acs routine, or any other simple way, and I'm hoping that someone has an idea that might
Re: rename a dataset in acs routine?
If you are not allowed to fix the JCL, JES2 exit 6 certainly sounds like a reasonable way to go, as long as it isn't the camel's nose under the tent. Good luck. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Brian Westerman Sent: Monday, September 21, 2020 5:48 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: rename a dataset in acs routine? Jes Exit 6 seems to be the best place to do this. There is only a max of one dataset per job and it's never re-read in that same job (or any other) and we already know what the dataset(s) are called, so it's pretty simple to scan for the DSN= text object and if the supplied DSN matches one of the ones we want, we just replace it with the symbolic. Actually at that point in time I could just insert the actual date and time. The test version does just that. Of course as soon as I started writing the exit, several people came in to ask for more "features". The only thing I forgot was a way to bypass the exit in the event that I wanted to actually process one of the tapes manually (by volser), but I now have that worked out as well, I just don't have time to test it properly at this time. I also think it's possible to limit the processing to ONLY the jobs that we know will contain the fiche tapes, so I'm waiting on a programmer to tell me if that's true. Brian On Mon, 21 Sep 2020 13:11:56 +, Seymour J Metz wrote: >What's the down side? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Lizette Koehler Sent: Sunday, September 20, 2020 11:06 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: rename a dataset in acs routine? I apologize if this has been discussed The SYSTEM Symbols can be made available to JES2 batch jobs The shop needs to determine if they want that to happen https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1 .ieab600/jclsymstr.htm The three types of symbols that can be used for JES2 in-stream substitution are JCL Symbols, JES Symbols and System Symbols: On a JES2 JOBCLASS definition, the field SYSSYM needs to be ALLOW rather than DISALLOW If there Is scheduling software available, it is possible it might provide symbolic substitution at Submission time (I know CA Workload Manager ESP can do that) Otherwise, you might want to have something like s REXX be executed (or language of your choice) to generate the JCL then submit into the Internal Reader ACS routines cannot do this type of function. Best of luck Lizette -Original Message- From: IBM Mainframe Discussion List On Behalf Of Seymour J Metz Sent: Sunday, September 20, 2020 5:47 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: rename a dataset in acs routine? ITYM IEFUJV; IEFUJI doesn't have the right interfaces. I'd probably use an internal text exit. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Brian Westerman Sent: Saturday, September 19, 2020 12:14 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: rename a dataset in acs routine? Actually I'm leaning towards the JES or SMF UJI exit as well. File tailoring doesn't help in this case because most of the JCL doesn't get submitted via TSO. Brian On Fri, 18 Sep 2020 16:41:29 +, Seymour J Metz wrote: >Well, if they want to use a chainsaw to open a bag of peanuts, you could write a JES exit, but the proper way to handle it is for the process that creates the JCL to generate a unique name. If they're using ISPF it's super easy to do it with File Tailoring, and many production control programs have similar capabilities. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Brian Westerman Sent: Friday, September 18, 2020 3:36 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: rename a dataset in acs routine? Hi, I was asked a question today that I honestly don't know how to answer. The programmer has a (very large) series of jobs that generate fiche tapes that get created and have a expiration date but never are cataloged (because they all have exactly the same DSN). So over time, they ended up with about 30,000 tapes from the over 9,000 jobs that CA-1 keeps around until expiration date. Obviously, these are not the easiest datasets to use later because they need to look up the tape volser every time. The problem is that they want to know if there is a way to automatically catalog datasets at creation time, to which I told them we could, but only 1 of them because you can't catalog two datasets with the same name. But they want to have "the system" which I'm guess
Re: rename a dataset in acs routine?
On Sun, 20 Sep 2020 00:06:01 -0500, Brian Westerman wrote: >They are mifrofiche tapes, and they are not sent out for processing any more. >They exist only on the off chance that "someday" they might be needed to >recreate something. When they are needed, they use the DSN=,VOL= to use them. > I read your more recent ply, but I'm curious about the history. "Sent out" seems to imply they're physical tapes to go in a courier pouch. I had imagined virtual. And RETPD must be comfortably beyond the "someday they might be needed." Does/did the process depend on the DSN's being precisely hlq.FICHE.TAPE, perhaps to trigger an exit or operator action? I don't see that cataloguing unique DSNs would help much -- it leaves the chore of associating DSN rather than VOL=SER with a particular job to be retrieved. It would enable a DSLIST of all such tapes. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: rename a dataset in acs routine?
The place that process our (not his) microfiche (later CD-ROMS) wanted the same DSN name so they only had to type in the volser, and they would pick up the date and time from the data. So HLQ.Jobname8.Dyymmdd.Thhmm.FIXED.LAST.NAME17 they would see as the same. On Mon, Sep 21, 2020 at 5:43 PM Paul Gilmartin <000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > > On Sun, 20 Sep 2020 00:06:01 -0500, Brian Westerman wrote: > > >They are mifrofiche tapes, and they are not sent out for processing any > >more. They exist only on the off chance that "someday" they might be needed > >to recreate something. When they are needed, they use the DSN=,VOL= to use > >them. > > > I read your more recent ply, but I'm curious about the history. > > "Sent out" seems to imply they're physical tapes to go in a courier pouch. > I had imagined virtual. And RETPD must be comfortably beyond the > "someday they might be needed." > > Does/did the process depend on the DSN's being precisely > hlq.FICHE.TAPE, perhaps to trigger an exit or operator > action? > > I don't see that cataloguing unique DSNs would help much -- it leaves > the chore of associating DSN rather than VOL=SER with a particular > job to be retrieved. It would enable a DSLIST of all such tapes. > > -- gil > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: rename a dataset in acs routine?
The following idea/method will probably not work, but what the hell. Consider listing the needed tape files with a TMS report to disk. 1. create a PDSE to load these files into. 2. change create fiche jcl to create a new member e.g. (d092120) 3 create job to load old tape files as member names. This could be a second PDSE, if helpful. 4. change jobs to read pdse member (d051719) for example. Alternate method, after finding all these old tapes from TMS report, load each tape to disk as PS/EF with compress. They would get migrated after X days of no use. -Original Message- From: IBM Mainframe Discussion List On Behalf Of Brian Westerman Sent: Monday, September 21, 2020 5:48 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: rename a dataset in acs routine? Jes Exit 6 seems to be the best place to do this. There is only a max of one dataset per job and it's never re-read in that same job (or any other) and we already know what the dataset(s) are called, so it's pretty simple to scan for the DSN= text object and if the supplied DSN matches one of the ones we want, we just replace it with the symbolic. Actually at that point in time I could just insert the actual date and time. The test version does just that. Of course as soon as I started writing the exit, several people came in to ask for more "features". The only thing I forgot was a way to bypass the exit in the event that I wanted to actually process one of the tapes manually (by volser), but I now have that worked out as well, I just don't have time to test it properly at this time. I also think it's possible to limit the processing to ONLY the jobs that we know will contain the fiche tapes, so I'm waiting on a programmer to tell me if that's true. Brian On Mon, 21 Sep 2020 13:11:56 +, Seymour J Metz wrote: >What's the down side? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Lizette Koehler Sent: Sunday, September 20, 2020 11:06 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: rename a dataset in acs routine? I apologize if this has been discussed The SYSTEM Symbols can be made available to JES2 batch jobs The shop needs to determine if they want that to happen https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1 .ieab600/jclsymstr.htm The three types of symbols that can be used for JES2 in-stream substitution are JCL Symbols, JES Symbols and System Symbols: On a JES2 JOBCLASS definition, the field SYSSYM needs to be ALLOW rather than DISALLOW If there Is scheduling software available, it is possible it might provide symbolic substitution at Submission time (I know CA Workload Manager ESP can do that) Otherwise, you might want to have something like s REXX be executed (or language of your choice) to generate the JCL then submit into the Internal Reader ACS routines cannot do this type of function. Best of luck Lizette -Original Message- From: IBM Mainframe Discussion List On Behalf Of Seymour J Metz Sent: Sunday, September 20, 2020 5:47 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: rename a dataset in acs routine? ITYM IEFUJV; IEFUJI doesn't have the right interfaces. I'd probably use an internal text exit. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Brian Westerman Sent: Saturday, September 19, 2020 12:14 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: rename a dataset in acs routine? Actually I'm leaning towards the JES or SMF UJI exit as well. File tailoring doesn't help in this case because most of the JCL doesn't get submitted via TSO. Brian On Fri, 18 Sep 2020 16:41:29 +, Seymour J Metz wrote: >Well, if they want to use a chainsaw to open a bag of peanuts, you >could write a JES exit, but the proper way to handle it is for the process that creates the JCL to generate a unique name. If they're using ISPF it's super easy to do it with File Tailoring, and many production control programs have similar capabilities. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Brian Westerman Sent: Friday, September 18, 2020 3:36 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: rename a dataset in acs routine? Hi, I was asked a question today that I honestly don't know how to answer. The programmer has a (very large) series of jobs that generate fiche tapes that get created and have a expiration date but never are cataloged (because they all have exactly the same DSN). So over time, they ended up with about 30,000 tapes from the over 9,000 jobs that CA-1 keeps around until expiration date. Obviously, these are not the easiest datasets to use later becau
Re: rename a dataset in acs routine?
My €0.02: This is typical problem when the goal is NOT defined. Existing approach seems ridiculous, but it exists. It works. So, since it works, why to change it? What is the reason? What goal is to achieve? More ridiculous are the terms. JCL cannot be changed. WHY??? However JES2 exit6 which changes JCL "in the flight" is allowed. Why??? Datasets are important, but the chances it will be ever read are small. Uncataloged datasets are a problem, however there is no big problem with duplicate names and volser which is known after the dataset is created. My opinion: First, recognize the situation and define the problem, then define the goal. Never use tapes, especially for small datasets. Including virtual tapes. Small datasets can be written to DASD, zEDC can be used to compress it. And DFSMS MC can be used to migrate it to tape. Yes, tapes are still good for backup and ML2. Large number of datasets is not a problem, that's what are user catalogs for. Good naming convention will help with ACS routines and ICF aliases. It can be GDG or just HLQ.YEAR.SOME.NAME.Ddate, or so. I would not go to PDSE members. Member are good candidate for really big number of really small files. Note, the smallest chunk of DASD is one track. The smallest chunk of PDSE is 4kB, and for PDS is just the size of file, it can be one byte. However migrated dataset occupies zero tracks. All the revolution require ...just simple changes in JCL and few changes in DFSMS realm. I can do that for peanuts ;-) -- Radoslaw Skorupka Lodz, Poland == Jeśli nie jesteś adresatem tej wiadomości: - powiadom nas o tym w mailu zwrotnym (dziękujemy!), - usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub zapisałeś na dysku). Wiadomość ta może zawierać chronione prawem informacje, które może wykorzystać tylko adresat.Przypominamy, że każdy, kto rozpowszechnia (kopiuje, rozprowadza) tę wiadomość lub podejmuje podobne działania, narusza prawo i może podlegać karze. mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, KRS 025237, NIP: 526-021-50-88. Kapitał zakładowy (opłacony w całości) według stanu na 01.01.2020 r. wynosi 169.401.468 złotych. If you are not the addressee of this message: - let us know by replying to this e-mail (thank you!), - delete this message permanently (including all the copies which you have printed out or saved). This message may contain legally protected information, which may be used exclusively by the addressee.Please be reminded that anyone who disseminates (copies, distributes) this message or takes any similar action, violates the law and may be penalised. mBank S.A. with its registered office in Warsaw, ul. Senatorska 18, 00-950 Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. District Court for the Capital City of Warsaw, 12th Commercial Division of the National Court Register, KRS 025237, NIP: 526-021-50-88. Fully paid-up share capital amounting to PLN 169.401.468 as at 1 January 2020. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: rename a dataset in acs routine?
Unfortunately, after about 45 years of doing it "this way", the users have a lot of their own JCL, it would not be economical or feasible to train or expect thousands of them to change or even know how to change their JCL. Many of them (most) don't even know what they are editing, they just replace a VOLSER with the one from the listing they have and submit the job. In a nice little environment where you can control these things, you are probably correct, but that is not the case in this instance. Brian On Tue, 22 Sep 2020 12:55:05 +0200, R.S. wrote: >My €0.02: >This is typical problem when the goal is NOT defined. >Existing approach seems ridiculous, but it exists. It works. >So, since it works, why to change it? What is the reason? What goal is >to achieve? >More ridiculous are the terms. JCL cannot be changed. WHY??? >However JES2 exit6 which changes JCL "in the flight" is allowed. Why??? >Datasets are important, but the chances it will be ever read are small. >Uncataloged datasets are a problem, however there is no big problem with >duplicate names and volser which is known after the dataset is created. > >My opinion: >First, recognize the situation and define the problem, then define the goal. >Never use tapes, especially for small datasets. Including virtual tapes. >Small datasets can be written to DASD, zEDC can be used to compress it. >And DFSMS MC can be used to migrate it to tape. Yes, tapes are still >good for backup and ML2. >Large number of datasets is not a problem, that's what are user catalogs >for. >Good naming convention will help with ACS routines and ICF aliases. >It can be GDG or just HLQ.YEAR.SOME.NAME.Ddate, or so. I would not go to >PDSE members. Member are good candidate for really big number of really >small files. Note, the smallest chunk of DASD is one track. The smallest >chunk of PDSE is 4kB, and for PDS is just the size of file, it can be >one byte. However migrated dataset occupies zero tracks. >All the revolution require ...just simple changes in JCL and few changes >in DFSMS realm. I can do that for peanuts ;-) > >-- >Radoslaw Skorupka >Lodz, Poland > > > > > >== > >Jeśli nie jesteś adresatem tej wiadomości: > >- powiadom nas o tym w mailu zwrotnym (dziękujemy!), >- usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub >zapisałeś na dysku). >Wiadomość ta może zawierać chronione prawem informacje, które może wykorzystać >tylko adresat.Przypominamy, że każdy, kto rozpowszechnia (kopiuje, >rozprowadza) tę wiadomość lub podejmuje podobne działania, narusza prawo i >może podlegać karze. > >mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 >Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. Sąd Rejonowy dla m. st. >Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, KRS 025237, >NIP: 526-021-50-88. Kapitał zakładowy (opłacony w całości) według stanu na >01.01.2020 r. wynosi 169.401.468 złotych. > >If you are not the addressee of this message: > >- let us know by replying to this e-mail (thank you!), >- delete this message permanently (including all the copies which you have >printed out or saved). >This message may contain legally protected information, which may be used >exclusively by the addressee.Please be reminded that anyone who disseminates >(copies, distributes) this message or takes any similar action, violates the >law and may be penalised. > >mBank S.A. with its registered office in Warsaw, ul. Senatorska 18, 00-950 >Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. District Court for the >Capital City of Warsaw, 12th Commercial Division of the National Court >Register, KRS 025237, NIP: 526-021-50-88. Fully paid-up share capital >amounting to PLN 169.401.468 as at 1 January 2020. > >-- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: rename a dataset in acs routine?
They used to be physically sent out, then FTP'ed, then not sent at all, but still created for a way to fall back in case of a data loss. Mostly, they are trash, but we are stuck with them, so we would like to force them to go to DASD (as cataloged datasets) and then archived so we can manage them for 3 years and drop them. Brian On Mon, 21 Sep 2020 17:42:52 -0500, Paul Gilmartin wrote: >On Sun, 20 Sep 2020 00:06:01 -0500, Brian Westerman wrote: > >>They are mifrofiche tapes, and they are not sent out for processing any more. >> They exist only on the off chance that "someday" they might be needed to >>recreate something. When they are needed, they use the DSN=,VOL= to use them. >> >I read your more recent ply, but I'm curious about the history. > >"Sent out" seems to imply they're physical tapes to go in a courier pouch. >I had imagined virtual. And RETPD must be comfortably beyond the >"someday they might be needed." > >Does/did the process depend on the DSN's being precisely >hlq.FICHE.TAPE, perhaps to trigger an exit or operator >action? > >I don't see that cataloguing unique DSNs would help much -- it leaves >the chore of associating DSN rather than VOL=SER with a particular >job to be retrieved. It would enable a DSLIST of all such tapes. > >-- gil > >-- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: rename a dataset in acs routine?
I have a TMS listing that I wrote a rexx prog to process and it generated IEBGENER jobs that copied from the non-cataloged tape to a new disk dataset (which contained the original creation date/time in the DSN), That dataset was later migrated via HSM. Brian On Mon, 21 Sep 2020 22:49:00 -0400, David Mingee wrote: >The following idea/method will probably not work, but what the hell. >Consider listing the needed tape files with a TMS report to disk. >1. create a PDSE to load these files into. >2. change create fiche jcl to create a new member e.g. (d092120) >3 create job to load old tape files as member names. This could be a second >PDSE, if helpful. >4. change jobs to read pdse member (d051719) for example. >Alternate method, after finding all these old tapes from TMS report, load each >tape to disk as PS/EF with compress. They would get migrated after >X days of no use. > >-Original Message- >From: IBM Mainframe Discussion List On Behalf Of >Brian Westerman >Sent: Monday, September 21, 2020 5:48 PM >To: IBM-MAIN@LISTSERV.UA.EDU >Subject: Re: rename a dataset in acs routine? > >Jes Exit 6 seems to be the best place to do this. There is only a max of one >dataset per job and it's never re-read in that same job (or any other) and we >already know what the dataset(s) are called, so it's pretty simple to scan for >the DSN= text object and if the supplied DSN matches one of the ones we want, >we just replace it with the symbolic. Actually at that point in time I could >just insert the actual date and time. The test version does just that. Of >course as soon as I started writing the exit, several people came in to ask >for more "features". The only thing I forgot was a way to bypass the exit in >the event that I wanted to actually process one of the tapes manually (by >volser), but I now have that worked out as well, I just don't have time to >test it properly at this time. I also think it's possible to limit the >processing to ONLY the jobs that we know will contain the fiche tapes, so I'm >waiting on a programmer to tell me if that's true. > >Brian > > On Mon, 21 Sep 2020 13:11:56 +, Seymour J Metz wrote: > >>What's the down side? > > >-- >Shmuel (Seymour J.) Metz >http://mason.gmu.edu/~smetz3 > > >____________________ >From: IBM Mainframe Discussion List on behalf of >Lizette Koehler >Sent: Sunday, September 20, 2020 11:06 PM >To: IBM-MAIN@LISTSERV.UA.EDU >Subject: Re: rename a dataset in acs routine? > >I apologize if this has been discussed > >The SYSTEM Symbols can be made available to JES2 batch jobs The shop needs >to determine if they want that to happen > >https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1 >.ieab600/jclsymstr.htm > >The three types of symbols that can be used for JES2 in-stream substitution >are JCL Symbols, JES Symbols and System Symbols: > >On a JES2 JOBCLASS definition, the field SYSSYM needs to be ALLOW rather than >DISALLOW > > > >If there Is scheduling software available, it is possible it might provide >symbolic substitution at Submission time (I know CA Workload Manager ESP can >do that) > >Otherwise, you might want to have something like s REXX be executed (or >language of your choice) to generate the JCL then submit into the Internal >Reader > >ACS routines cannot do this type of function. > >Best of luck > >Lizette > >-Original Message- >From: IBM Mainframe Discussion List On Behalf Of >Seymour J Metz >Sent: Sunday, September 20, 2020 5:47 PM >To: IBM-MAIN@LISTSERV.UA.EDU >Subject: Re: rename a dataset in acs routine? > >ITYM IEFUJV; IEFUJI doesn't have the right interfaces. I'd probably use an >internal text exit. > > >-- >Shmuel (Seymour J.) Metz >http://mason.gmu.edu/~smetz3 > > > >From: IBM Mainframe Discussion List on behalf of >Brian Westerman >Sent: Saturday, September 19, 2020 12:14 AM >To: IBM-MAIN@LISTSERV.UA.EDU >Subject: Re: rename a dataset in acs routine? > >Actually I'm leaning towards the JES or SMF UJI exit as well. File tailoring >doesn't help in this case because most of the JCL doesn't get submitted via >TSO. > >Brian > >On Fri, 18 Sep 2020 16:41:29 +, Seymour J Metz wrote: > >>Well, if they want to use a chainsaw to open a bag of peanuts, you >>could >write a JES exit, but the proper way to handle it is for the process that >creates the JCL to generate a unique name. If they're using ISPF it's super >easy to do it with File Tailoring, and many production con
Re: rename a dataset in acs routine?
This is clou (the point). Many users, a lot o JCL jobs, people are unaware of the JCL, they can only change volser... Excuse me, but it looks like kindergarten with no teachers on board. For 45 years. It is not technical issue, this is strong organizational problem. And this should be fixed. Yes, people could be unhappy. BTW: even in this kindergarten it is feasible to identify all the job libraries and change JCL code. -- Radoslaw Skorupka Lodz, Poland W dniu 23.09.2020 o 10:42, Brian Westerman pisze: Unfortunately, after about 45 years of doing it "this way", the users have a lot of their own JCL, it would not be economical or feasible to train or expect thousands of them to change or even know how to change their JCL. Many of them (most) don't even know what they are editing, they just replace a VOLSER with the one from the listing they have and submit the job. In a nice little environment where you can control these things, you are probably correct, but that is not the case in this instance. Brian On Tue, 22 Sep 2020 12:55:05 +0200, R.S. wrote: My €0.02: This is typical problem when the goal is NOT defined. Existing approach seems ridiculous, but it exists. It works. So, since it works, why to change it? What is the reason? What goal is to achieve? More ridiculous are the terms. JCL cannot be changed. WHY??? However JES2 exit6 which changes JCL "in the flight" is allowed. Why??? Datasets are important, but the chances it will be ever read are small. Uncataloged datasets are a problem, however there is no big problem with duplicate names and volser which is known after the dataset is created. My opinion: First, recognize the situation and define the problem, then define the goal. Never use tapes, especially for small datasets. Including virtual tapes. Small datasets can be written to DASD, zEDC can be used to compress it. And DFSMS MC can be used to migrate it to tape. Yes, tapes are still good for backup and ML2. Large number of datasets is not a problem, that's what are user catalogs for. Good naming convention will help with ACS routines and ICF aliases. It can be GDG or just HLQ.YEAR.SOME.NAME.Ddate, or so. I would not go to PDSE members. Member are good candidate for really big number of really small files. Note, the smallest chunk of DASD is one track. The smallest chunk of PDSE is 4kB, and for PDS is just the size of file, it can be one byte. However migrated dataset occupies zero tracks. All the revolution require ...just simple changes in JCL and few changes in DFSMS realm. I can do that for peanuts ;-) -- Radoslaw Skorupka Lodz, Poland == Jeśli nie jesteś adresatem tej wiadomości: - powiadom nas o tym w mailu zwrotnym (dziękujemy!), - usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub zapisałeś na dysku). Wiadomość ta może zawierać chronione prawem informacje, które może wykorzystać tylko adresat.Przypominamy, że każdy, kto rozpowszechnia (kopiuje, rozprowadza) tę wiadomość lub podejmuje podobne działania, narusza prawo i może podlegać karze. mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, KRS 025237, NIP: 526-021-50-88. Kapitał zakładowy (opłacony w całości) według stanu na 01.01.2020 r. wynosi 169.401.468 złotych. If you are not the addressee of this message: - let us know by replying to this e-mail (thank you!), - delete this message permanently (including all the copies which you have printed out or saved). This message may contain legally protected information, which may be used exclusively by the addressee.Please be reminded that anyone who disseminates (copies, distributes) this message or takes any similar action, violates the law and may be penalised. mBank S.A. with its registered office in Warsaw, ul. Senatorska 18, 00-950 Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. District Court for the Capital City of Warsaw, 12th Commercial Division of the National Court Register, KRS 025237, NIP: 526-021-50-88. Fully paid-up share capital amounting to PLN 169.401.468 as at 1 January 2020. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: rename a dataset in acs routine?
On Wed, 23 Sep 2020 11:58:02 +0200, R.S. wrote: >This is clou (the point). Many users, a lot o JCL jobs, people are >unaware of the JCL, they can only change volser... >Excuse me, but it looks like kindergarten with no teachers on board. For >45 years. >It is not technical issue, this is strong organizational problem. And >this should be fixed. Yes, people could be unhappy. >BTW: even in this kindergarten it is feasible to identify all the job >libraries and change JCL code. > +1 >W dniu 23.09.2020 o 10:42, Brian Westerman pisze: >> Unfortunately, after about 45 years of doing it "this way", the users have a >> lot of their own JCL, it would not be economical or feasible to train or >> expect thousands of them to change or even know how to change their JCL. >> Many of them (most) don't even know what they are editing, they just replace >> a VOLSER with the one from the listing they have and submit the job. In a >> nice little environment where you can control these things, you are probably >> correct, but that is not the case in this instance. >> "thousands"!? But if you make your imagined change to unique catalogued DSNs those users must be educated to change their process to replace not only VOLSER but also/instead DSN and UNIT. Worse, some may be relying on handwritten logs in which they record only VOLSER, not DSN. Is there any possible dependency on serialization by EXC ENQ on hlq.FICHE.TAPE? What's the likelihood of a collision of generated DSNs during the next 45 years? How would you resolve it? How would you test that solution? The Amish have driven horses and carriages for longer than 45 years They see nothing that needs to be fixed on that account. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
