|
Jim, Try DSPMSGD CPF5029. > -----Original Message----- > From: owner-rpg400-l@midrange.com [mailto:owner-rpg400-l@midrange.com]On > Behalf Of Jim > Sent: Tuesday, July 06, 1999 3:23 PM > To: RPG400-L@midrange.com > Subject: Re: I/O error CF5029 > > > RAVI, > > could you please tell me how you got that information? Is it a book? > if so, which one? I have never been able to find that info! > > Date sent: Tue, 06 Jul 1999 15:08:19 -0500 > From: Ravi Viswanathan <ravi@spacestar.com> > To: RPG400-L@midrange.com > Subject: Re: I/O error CF5029 > Send reply to: RPG400-L@midrange.com > > Silvio, > > CPF5029 is not an authority problem. > The error message description is as follows, which should give > you an idea of where the problem > might be..... > > Message . . . . : Data mapping error on member &4. > Cause . . . . . : A data mapping error occurred on member &4 file &2 in > library &3, because the data fields in record number &6, > record format &7, > member number &8 are in error. > Recovery . . . : If the record number is zero, the error > occurred on an > attempt to put or update a record through a logical file, or the error > occurred on a group by operation, or the error was caused by a default > value, or the error was caused by a null value in the record. See > previously listed message CPF5035 or CPD5036 to determine > which fields are > in error. Change the fields that are in error and try the > operation again. > > Silvio Santos wrote: > > > I have a pgm thats is doing a chain to a file (PF). But when it > arrives that instrution > > it always returns a I/O error CPF5029. I had check if I have > authority to the file and there > > is no problem, I can use the SQL the RUNQRY; I dont know what > can be the problem ? > > Does anybody have a solution for this, > > > > TIA, > > Silvio. > > * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * > * * * * * > > * This is the RPG/400 Discussion Mailing List! To submit a new > * > > * message, send your mail to "RPG400-L@midrange.com". To > unsubscribe * > > * from this list send email to MAJORDOMO@midrange.com and > specify * > > * 'unsubscribe RPG400-L' in the body of your message. > Questions should * > > * be directed to the list owner / operator: david@midrange.com > * > > * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * > * * * * * > > * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * > * This is the RPG/400 Discussion Mailing List! To submit a new * > * message, send your mail to "RPG400-L@midrange.com". To unsubscribe * > * from this list send email to MAJORDOMO@midrange.com and specify * > * 'unsubscribe RPG400-L' in the body of your message. Questions should * > * be directed to the list owner / operator: david@midrange.com * > * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * > * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * > * This is the RPG/400 Discussion Mailing List! To submit a new * > * message, send your mail to "RPG400-L@midrange.com". To unsubscribe * > * from this list send email to MAJORDOMO@midrange.com and specify * > * 'unsubscribe RPG400-L' in the body of your message. Questions should * > * be directed to the list owner / operator: david@midrange.com * > * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * > * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * This is the RPG/400 Discussion Mailing List! To submit a new * * message, send your mail to "RPG400-L@midrange.com". To unsubscribe * * from this list send email to MAJORDOMO@midrange.com and specify * * 'unsubscribe RPG400-L' in the body of your message. 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.