|
why? Carl Galgano EDI Consulting Services, Inc. 540 Powder Springs Street Suite C19 Marietta, GA 30064 770-422-2995 mailto: cgalgano@ediconsulting.com http://www.ediconsulting.com EDI, Communications and AS400 Technical Consulting -----Original Message----- From: Kevin Watkins <kevinw@hurtcompanies.com> To: MIDRANGE-L@midrange.com <MIDRANGE-L@midrange.com> Date: Friday, March 05, 1999 3:48 PM Subject: Re: Error Indicator on Write >how about using SETLL instead? > >-----Original Message----- >From: Karl lauritzen <klauritzen@mail2.texnet.net> >To: MIDRANGE-L@midrange.com <MIDRANGE-L@midrange.com> >Date: Friday, March 05, 1999 1:45 PM >Subject: Re: Error Indicator on Write > > >>Why don't you chain to file first before write and then if the indicator is >>on the record does not exist so you can write to it. >> >> Key Chain Rec 99 >> If *in99 >> Write rec >> Endif >> >> >>-----Original Message----- >>From: Balaji.Rao@smed.com <Balaji.Rao@smed.com> >>To: MIDRANGE-L@midrange.com <MIDRANGE-L@midrange.com> >>Date: Friday, March 05, 1999 12:15 PM >>Subject: Error Indicator on Write >> >> >>> >>> >>>Hi EveryBody, >>>I have a problem with Write Opcode. I have a Write to a Unique keyed file >& >>>I give LO Indicator to stop it from erring out when a duplicate record >>>write occurs. >>>I experienced that some times the Write writes a record(data wasn't >>>duplicate) to the file & still sets on the LO Indicator. Could somebody >>>tell me Why??? Am I missing something??? >>>Your help will be greatly appreciated, >>>Prakash. >>> >>> >>>+--- >>>| This is the Midrange System Mailing List! >>>| To submit a new message, send your mail to MIDRANGE-L@midrange.com. >>>| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. >>>| To unsubscribe from this list send email to >>MIDRANGE-L-UNSUB@midrange.com. >>>| Questions should be directed to the list owner/operator: >>david@midrange.com >>>+--- >>> >> >>+--- >>| This is the Midrange System Mailing List! >>| To submit a new message, send your mail to MIDRANGE-L@midrange.com. >>| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. >>| To unsubscribe from this list send email to >MIDRANGE-L-UNSUB@midrange.com. >>| Questions should be directed to the list owner/operator: >david@midrange.com >>+--- > >+--- >| This is the Midrange System Mailing List! >| To submit a new message, send your mail to MIDRANGE-L@midrange.com. >| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. >| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. >| Questions should be directed to the list owner/operator: david@midrange.com >+--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.