Re: ARC0734i rc=20 reason=98
You might look at SMF record 65's (catalogue delete) to find out what process is messing with your GDG's. Ant. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Hervey Martinez Sent: Tuesday, 21 November 2017 6:35 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ARC0734i rc=20 reason=98 The MC is set to EXPIRE. And that's the other strange thing, not all GDGs that share the MC have the same problem. Hervey From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of Allan Staller <allan.stal...@hcl.com> Sent: Monday, November 20, 2017 3:36 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ARC0734i rc=20 reason=98 GDS=EXPIRED vs GDS=MIGRATE in the SMS management class? -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Hervey Martinez Sent: Monday, November 20, 2017 1:59 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ARC0734i rc=20 reason=98 Well, all files that I've seen are GDG files. This is very puzzling. There are a few of these errors that happen every so often but have no idea what is causing them. Hervey From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of Allan Staller <allan.stal...@hcl.com> Sent: Monday, November 20, 2017 2:34 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ARC0734i rc=20 reason=98 Non-symetric aliases? i.e. alias A in MCATA, but not in MCATB See message arc1220I RC=98 for explanation. Basically get down to one copy of the dataset (whether it is the migrated copy or the "real" dataset). This will resolve the issue. As to why, there are too many variables to spend a great deal of time speculating. HTH, -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Hervey Martinez Sent: Monday, November 20, 2017 1:28 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: ARC0734i rc=20 reason=98 We have several datasets that show up in HSM's miglog file. I know the problem is that the file is not cataloged and is the reason for the error. My question is: What causes these files to become uncataloged? I've read a few other posts about the HSM address space being cancelled due to errors and causing this sort of error. We only recycle HSM during maintenance on the weekends and many of these errors happen during the week which does not coincide with the recycling of the HSM task. Any ideas? -- 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 -- 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.e
Re: ARC0734i rc=20 reason=98
There has always been a general restriction that SMS managed data sets must be cataloged. If you try to uncatalog an SMS data set, it will (should?) fail. In our shop, tape data sets are not SMS managed, so we can (and do) keep some uncataloged data sets indefinitely. CA-1 made that fairly easy. RMM was initially quite unhappy with uncataloged data sets but has since negotiated an uneasy peace. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Paul Gilmartin Sent: Monday, November 20, 2017 1:05 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: ARC0734i rc=20 reason=98 On Mon, 20 Nov 2017 14:03:15 -0600, John McKown wrote: > >Oh, I've had that problem. Look at the GDG base in the catalog. Make >sure that it says "SCRATCH". Otherwise the GDG data set entry will "roll off" >the GDG, but the data set will not be scratched from the volume. I had >a big problem with this when programmers were allowed to create their >own GDGs and they _never_ put the SCRATCH parameter on the DEFINE GDG. >Why the bleeding IBM made the default NOSCRATCH is a mystery >know to none at this point. > It appears that the GDG designers, the SMS designers, and the catalog designers don't coordinate very well with each other. Otherwise, SMS strives mightily to avoid orphaned 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: ARC0734i rc=20 reason=98
On Mon, 20 Nov 2017 14:03:15 -0600, John McKown wrote: > >Oh, I've had that problem. Look at the GDG base in the catalog. Make sure >that it says "SCRATCH". Otherwise the GDG data set entry will "roll off" >the GDG, but the data set will not be scratched from the volume. I had a >big problem with this when programmers were allowed to create their own >GDGs and they _never_ put the SCRATCH parameter on the DEFINE GDG. Why the >bleeding IBM made the default NOSCRATCH is a mystery know to none >at this point. > It appears that the GDG designers, the SMS designers, and the catalog designers don't coordinate very well with each other. Otherwise, SMS strives mightily to avoid orphaned 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: ARC0734i rc=20 reason=98
The MC is set to EXPIRE. And that's the other strange thing, not all GDGs that share the MC have the same problem. Hervey From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of Allan Staller <allan.stal...@hcl.com> Sent: Monday, November 20, 2017 3:36 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ARC0734i rc=20 reason=98 GDS=EXPIRED vs GDS=MIGRATE in the SMS management class? -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Hervey Martinez Sent: Monday, November 20, 2017 1:59 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ARC0734i rc=20 reason=98 Well, all files that I've seen are GDG files. This is very puzzling. There are a few of these errors that happen every so often but have no idea what is causing them. Hervey From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of Allan Staller <allan.stal...@hcl.com> Sent: Monday, November 20, 2017 2:34 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ARC0734i rc=20 reason=98 Non-symetric aliases? i.e. alias A in MCATA, but not in MCATB See message arc1220I RC=98 for explanation. Basically get down to one copy of the dataset (whether it is the migrated copy or the "real" dataset). This will resolve the issue. As to why, there are too many variables to spend a great deal of time speculating. HTH, -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Hervey Martinez Sent: Monday, November 20, 2017 1:28 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: ARC0734i rc=20 reason=98 We have several datasets that show up in HSM's miglog file. I know the problem is that the file is not cataloged and is the reason for the error. My question is: What causes these files to become uncataloged? I've read a few other posts about the HSM address space being cancelled due to errors and causing this sort of error. We only recycle HSM during maintenance on the weekends and many of these errors happen during the week which does not coincide with the recycling of the HSM task. Any ideas? -- 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 -- 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: ARC0734i rc=20 reason=98
Yes, that was my initial thought but all GDGs that I've seen have the SCRATCH parm. From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of John McKown <john.archie.mck...@gmail.com> Sent: Monday, November 20, 2017 3:03 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ARC0734i rc=20 reason=98 On Mon, Nov 20, 2017 at 1:59 PM, Hervey Martinez <hervey...@hotmail.com> wrote: > Well, all files that I've seen are GDG files. This is very puzzling. There > are a few of these errors that happen every so often but have no idea what > is causing them. > Oh, I've had that problem. Look at the GDG base in the catalog. Make sure that it says "SCRATCH". Otherwise the GDG data set entry will "roll off" the GDG, but the data set will not be scratched from the volume. I had a big problem with this when programmers were allowed to create their own GDGs and they _never_ put the SCRATCH parameter on the DEFINE GDG. Why the bleeding IBM made the default NOSCRATCH is a mystery know to none at this point. > > > Hervey > > > > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf > of Allan Staller <allan.stal...@hcl.com> > Sent: Monday, November 20, 2017 2:34 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: ARC0734i rc=20 reason=98 > > Non-symetric aliases? i.e. alias A in MCATA, but not in MCATB > > See message arc1220I RC=98 for explanation. > > Basically get down to one copy of the dataset (whether it is the migrated > copy or the "real" dataset). > This will resolve the issue. > > As to why, there are too many variables to spend a great deal of time > speculating. > > HTH, > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Hervey Martinez > Sent: Monday, November 20, 2017 1:28 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: ARC0734i rc=20 reason=98 > > We have several datasets that show up in HSM's miglog file. I know the > problem is that the file is not cataloged and is the reason for the error. > My question is: What causes these files to become uncataloged? > > I've read a few other posts about the HSM address space being cancelled > due to errors and causing this sort of error. We only recycle HSM during > maintenance on the weekends and many of these errors happen during the week > which does not coincide with the recycling of the HSM task. > > Any ideas? > > -- > 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 > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- I have a theory that it's impossible to prove anything, but I can't prove it. Maranatha! <>< John McKown
Re: ARC0734i rc=20 reason=98
GDS=EXPIRED vs GDS=MIGRATE in the SMS management class? -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Hervey Martinez Sent: Monday, November 20, 2017 1:59 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ARC0734i rc=20 reason=98 Well, all files that I've seen are GDG files. This is very puzzling. There are a few of these errors that happen every so often but have no idea what is causing them. Hervey From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of Allan Staller <allan.stal...@hcl.com> Sent: Monday, November 20, 2017 2:34 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ARC0734i rc=20 reason=98 Non-symetric aliases? i.e. alias A in MCATA, but not in MCATB See message arc1220I RC=98 for explanation. Basically get down to one copy of the dataset (whether it is the migrated copy or the "real" dataset). This will resolve the issue. As to why, there are too many variables to spend a great deal of time speculating. HTH, -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Hervey Martinez Sent: Monday, November 20, 2017 1:28 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: ARC0734i rc=20 reason=98 We have several datasets that show up in HSM's miglog file. I know the problem is that the file is not cataloged and is the reason for the error. My question is: What causes these files to become uncataloged? I've read a few other posts about the HSM address space being cancelled due to errors and causing this sort of error. We only recycle HSM during maintenance on the weekends and many of these errors happen during the week which does not coincide with the recycling of the HSM task. Any ideas? -- 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 -- 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: ARC0734i rc=20 reason=98
On Mon, Nov 20, 2017 at 1:59 PM, Hervey Martinez <hervey...@hotmail.com> wrote: > Well, all files that I've seen are GDG files. This is very puzzling. There > are a few of these errors that happen every so often but have no idea what > is causing them. > Oh, I've had that problem. Look at the GDG base in the catalog. Make sure that it says "SCRATCH". Otherwise the GDG data set entry will "roll off" the GDG, but the data set will not be scratched from the volume. I had a big problem with this when programmers were allowed to create their own GDGs and they _never_ put the SCRATCH parameter on the DEFINE GDG. Why the bleeding IBM made the default NOSCRATCH is a mystery know to none at this point. > > > Hervey > > > > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf > of Allan Staller <allan.stal...@hcl.com> > Sent: Monday, November 20, 2017 2:34 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: ARC0734i rc=20 reason=98 > > Non-symetric aliases? i.e. alias A in MCATA, but not in MCATB > > See message arc1220I RC=98 for explanation. > > Basically get down to one copy of the dataset (whether it is the migrated > copy or the "real" dataset). > This will resolve the issue. > > As to why, there are too many variables to spend a great deal of time > speculating. > > HTH, > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Hervey Martinez > Sent: Monday, November 20, 2017 1:28 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: ARC0734i rc=20 reason=98 > > We have several datasets that show up in HSM's miglog file. I know the > problem is that the file is not cataloged and is the reason for the error. > My question is: What causes these files to become uncataloged? > > I've read a few other posts about the HSM address space being cancelled > due to errors and causing this sort of error. We only recycle HSM during > maintenance on the weekends and many of these errors happen during the week > which does not coincide with the recycling of the HSM task. > > Any ideas? > > -- > 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 > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- I have a theory that it's impossible to prove anything, but I can't prove it. Maranatha! <>< John McKown -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ARC0734i rc=20 reason=98
Well, all files that I've seen are GDG files. This is very puzzling. There are a few of these errors that happen every so often but have no idea what is causing them. Hervey From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of Allan Staller <allan.stal...@hcl.com> Sent: Monday, November 20, 2017 2:34 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ARC0734i rc=20 reason=98 Non-symetric aliases? i.e. alias A in MCATA, but not in MCATB See message arc1220I RC=98 for explanation. Basically get down to one copy of the dataset (whether it is the migrated copy or the "real" dataset). This will resolve the issue. As to why, there are too many variables to spend a great deal of time speculating. HTH, -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Hervey Martinez Sent: Monday, November 20, 2017 1:28 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: ARC0734i rc=20 reason=98 We have several datasets that show up in HSM's miglog file. I know the problem is that the file is not cataloged and is the reason for the error. My question is: What causes these files to become uncataloged? I've read a few other posts about the HSM address space being cancelled due to errors and causing this sort of error. We only recycle HSM during maintenance on the weekends and many of these errors happen during the week which does not coincide with the recycling of the HSM task. Any ideas? -- 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 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ARC0734i rc=20 reason=98
Non-symetric aliases? i.e. alias A in MCATA, but not in MCATB See message arc1220I RC=98 for explanation. Basically get down to one copy of the dataset (whether it is the migrated copy or the "real" dataset). This will resolve the issue. As to why, there are too many variables to spend a great deal of time speculating. HTH, -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Hervey Martinez Sent: Monday, November 20, 2017 1:28 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: ARC0734i rc=20 reason=98 We have several datasets that show up in HSM's miglog file. I know the problem is that the file is not cataloged and is the reason for the error. My question is: What causes these files to become uncataloged? I've read a few other posts about the HSM address space being cancelled due to errors and causing this sort of error. We only recycle HSM during maintenance on the weekends and many of these errors happen during the week which does not coincide with the recycling of the HSM task. Any ideas? -- 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
ARC0734i rc=20 reason=98
We have several datasets that show up in HSM's miglog file. I know the problem is that the file is not cataloged and is the reason for the error. My question is: What causes these files to become uncataloged? I've read a few other posts about the HSM address space being cancelled due to errors and causing this sort of error. We only recycle HSM during maintenance on the weekends and many of these errors happen during the week which does not coincide with the recycling of the HSM task. Any ideas? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
