>>> On 9/5/2009 at 7:57 AM, in message <listserv%[email protected]>, Mark Zelden <[email protected]> wrote: > On Sat, 5 Sep 2009 07:19:56 -0600, Frank Swarbrick > <[email protected]> wrote: > >>>>> On 9/4/2009 at 7:06 PM, in message >><[email protected]>, "Savor, Tom" >><[email protected]> wrote: >>>> For any (all) of you who "dislike" the file status "97" - especially >>> anyone involved in a >VSE to MVS conversion (where this seems to be a >>> medium-high priority problem), >please consider submitting a "Marketing >>> Request" >>>>to IBM and reference the existing SHARE requirement: >>> >>> >SSLNGC0413615 Optional (ISO 2002) "0x" file-status code for current >>> "97" >>> >>> Yes, it was very aggravating when status code of "97" appeared on the >>> landscape. >>> But, to be honest with you, all of our I/O routines are coded to treat >>> "00" and "97" the same. So for IBM to remove "97" as a status code will >>> no real effect. >>> >>> If this status code had just appeared, I would say "yes" it would help >>> save some needless coding, but since it's been around so long...we >>> already have coded around it. >>> And management won't spend the money to remove it...no money to get >>> gained. >> >>I would agree that there is no gain in removing it if it's already there. > But as a shop migrating from VSE where file status 97 does not occur, and > thus has never been coded for, it will take us "time and money" to make the > changes to handle status 97 now. >> >>Frank >> > > Since you have to rewrite all your JCL anyway, adding an IDCAMS VERIFY > step may be the best option and really shouldn't add much to your migration > costs in terms of time and money. If you have automated this in some > way, it shouldn't be too much trouble to add this step. You could always > go back and revisit it later if IBM ever makes a change in this area.
That is indeed one of the options I am considering. Thanks! > Just out of curiosity, how many programs are we talking about here? > A few hundred? Thousands? A few thousand, total, though likely not all that many would have the issue. As far as I can tell it only affects KSDS files that are opened for I-O (output without REUSE). So hopefully that will lessen the scope of the issue. Frank The information contained in this electronic communication and any document attached hereto or transmitted herewith is confidential and intended for the exclusive use of the individual or entity named above. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any examination, use, dissemination, distribution or copying of this communication or any part thereof is strictly prohibited. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy this communication. Thank you. -- Frank Swarbrick Applications Architect - Mainframe Applications Development FirstBank Data Corporation - Lakewood, CO USA P: 303-235-1403 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
