|
I think program SFC100D2 will loop and copy notes until the file is full if the same operation number (PNOPN), and note sequence number (PNSEQ) exist. It will simply copy this one line over and over. Use DFU or some other utility to correct the problem. The sequence number (PNSEQ) must be unique for a given item's operation (PNOPN) in the MPN file. Hope this helps. Dwight Slessman -----Original Message----- From: oludare [SMTP:oludare@ix.netcom.com] Sent: Thursday, November 04, 1999 9:01 AM To: Beepics BPCS Usergroup Subject: : RE: Duplicate notes created by SFC100 in MPN during copy Yes some of the source routing have duplicate notes. Some of the dups are inactive. ----- Original Message ----- From: Dwight Slessman <dslessman@nationalelectrical.com> To: <BPCS-L@midrange.com> Sent: Tuesday, November 02, 1999 4:52 PM Subject: RE: Duplicate notes created by SFC100 in MPN during copy > Does the source routing operation have duplicate notes on it? > > -----Original Message----- > From: oludare [SMTP:oludare@ix.netcom.com] > Sent: Tuesday, November 02, 1999 2:41 PM > To: Beepics BPCS Usergroup > Cc: Peter Smolens > Subject: Duplicate notes created by SFC100 in MPN during copy > > Hello guys, > > I'm on BPCS 6.00.02 Jan Cum OS400 V37M0 > > I need some help with SFC100. Record duplication occurs when users try to > create a routing notes by copying from an old note. The old note is then > created until the note file, MPN, is filled to its maximum. This seems > strange, is there a known problem with this PGM or is it possible that the > users are generating these new records by mistake of what they do or don't > do. I will appreciate anyone with similar experience, knowledge, or > experience with this event to educate me on this issue. > > Thank you for your help in advance. > > Oludare > > +--- > | This is the BPCS Users Mailing List! > | To submit a new message, send your mail to BPCS-L@midrange.com. > | To subscribe to this list send email to BPCS-L-SUB@midrange.com. > | To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com. > | Questions should be directed to the list owner: dasmussen@aol.com > +--- > +--- > | This is the BPCS Users Mailing List! > | To submit a new message, send your mail to BPCS-L@midrange.com. > | To subscribe to this list send email to BPCS-L-SUB@midrange.com. > | To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com. > | Questions should be directed to the list owner: dasmussen@aol.com > +--- +--- | This is the BPCS Users Mailing List! | To submit a new message, send your mail to BPCS-L@midrange.com. | To subscribe to this list send email to BPCS-L-SUB@midrange.com. | To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com. | Questions should be directed to the list owner: dasmussen@aol.com +--- +--- | This is the BPCS Users Mailing List! | To submit a new message, send your mail to BPCS-L@midrange.com. | To subscribe to this list send email to BPCS-L-SUB@midrange.com. | To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com. | Questions should be directed to the list owner: dasmussen@aol.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.