|
So in debug, at line 19 of the CL, what's the value of &MBR? Does that member exist in the REPAIRS file that's found in the library list? On 5/30/06, steema@xxxxxxxxxxxxx <steema@xxxxxxxxxxxxx> wrote:
The CL is here: 0007.00 PGM PARM(&MBR &COMM1 &COMM2 &COMM3 &COMM4 &COMM5) 0008.00 0009.00 DCL VAR(&MBR) TYPE(*CHAR) LEN(7) 0010.00 DCL VAR(&COMM1) TYPE(*CHAR) LEN(80) 0011.00 DCL VAR(&COMM2) TYPE(*CHAR) LEN(80) 0012.00 DCL VAR(&COMM3) TYPE(*CHAR) LEN(80) 0013.00 DCL VAR(&COMM4) TYPE(*CHAR) LEN(80) 0014.00 DCL VAR(&COMM5) TYPE(*CHAR) LEN(80) 0015.00 0016.00 OVRDBF FILE(REPAIRS) MBR(&MBR) 0019.00 CALL PGM(OERRPRM) PARM(&COMM1 &COMM2 &COMM3 + 0020.00 &COMM4 &COMM5 THE RPG: 0009.00 Frepairs if e disk 0010.00 c* 0011.00 c *entry plist 0012.00 c parm comm1 80 0013.00 c parm comm2 80 0014.00 c parm comm3 80 0015.00 c parm comm4 80 0016.00 c parm comm5 80 > Show the complete OVRDBF and the complete File spec. > > On 5/30/06, steema@xxxxxxxxxxxxx <steema@xxxxxxxxxxxxx> wrote: >> >> Peter, I didn't make it Usropn, bec. I am simply passing the member name >> from the main program. However, I will try this idea as well. >> Thanks, >> Steve Merer >> > Did you make the file UsrOpn? >> > >> > if not, and the ExtMbr variable is blanks, you might get this error >> > (haven't checked but my gut feeling suggests it) >> > >> > Also the "implicit" open suggests that your file is opened >> automagically >> > when the program is started, whereas a UsrOpn file will be >> "explicitly" >> > opened. >> > >> > HTH, >> > >> > Peter Colpaert >> > Application Developer >> > PLI - IT - Kontich, Belgium >> > ----- >> > Yoda of Borg are we. Futile is resistance, assimilated will you be. >> > ----- >> > >> > >> > >> > steema@xxxxxxxxxxxxx >> > Sent by: rpg400-l-bounces@xxxxxxxxxxxx >> > 30/05/2006 15:16 >> > Please respond to >> > RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx> >> > >> > >> > To >> > "RPG programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx> >> > cc >> > >> > Subject >> > Re: Problem w/ calling a multi-members file >> > >> > >> > >> > >> > >> > >> > Yes but the file does exist. The issue is that the member does not >> exist, >> > I think. >> > >> > this is the called program error >> > >> > >> > Message ID . . . . . . : CPF9C32 Severity . . . . . . . : 40 >> > Message type . . . . . : Diagnostic >> > Date sent . . . . . . : 05/30/06 Time sent . . . . . . : >> 09:05:19 >> > >> > Message . . . . : Unmonitored exception at line 1 >> > Cause . . . . . : An unmonitored exception occurred in module >> OERRPRM >> in >> > program OERRPRM in library MYLIB. The exception occurred at line 1 >> in >> > view >> > "ILE RPG Source View". >> > Recovery . . . : See the job log to view the exception. >> > Technical description . . . . . . . . : The program is stopped in >> line >> 1 >> > of >> > view "ILE RPG Source View". >> > >> > >> >> It's a file not found error - check your file name. If you're >> specifying >> > a >> >> variable for the file name, make sure it's correct. If it's a hard >> coded >> >> file name, check your F spec. >> >> >> >> On 5/30/06, steema@xxxxxxxxxxxxx <steema@xxxxxxxxxxxxx> wrote: >> >>> >> >>> HI if you recall, I have to find the comments for a repair in a file >> >>> that >> >>> is multi - member. the name of the member, is the invoice number, >> which >> >>> I >> >>> can get from the main file or via the subfile. what is very strange >> is >> >>> that the called program, seems to kick off w/out any logic. I have a >> >>> debug >> >>> break on the call statement, but it still kicks off w/ this error >> >>> message: >> >>> >> >>> Perhaps someone has seen this before. >> >>> >> >>> >> >>> Message ID . . . . . . : RNX1216 Severity . . . . . . . : >> 99 >> >>> Message type . . . . . : Diagnostic >> >>> Date sent . . . . . . : 05/30/06 Time sent . . . . . . : >> >>> 09:05:19 >> >>> >> >>> Message . . . . : Error message CPF4102 appeared during OPEN for >> file >> >>> REPAIRS. >> >>> Cause . . . . . : RPG procedure OERRPRM in program MYLIB/OERRPRM >> >>> received >> >>> the message CPF4102 while performing an implicit OPEN operation on >> >>> file >> >>> REPAIRS. The actual file is REPAIRS. >> >>> Recovery . . . : Check the job log for a complete description of >> >>> message >> >>> CPF4102, and contact the person responsible for program >> maintenance. >> > >> > >> > >> > -- >> > This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing >> list >> > To post a message email: RPG400-L@xxxxxxxxxxxx >> > To subscribe, unsubscribe, or change list options, >> > visit: http://lists.midrange.com/mailman/listinfo/rpg400-l >> > or email: RPG400-L-request@xxxxxxxxxxxx >> > Before posting, please take a moment to review the archives >> > at http://archive.midrange.com/rpg400-l. >> > >> > >> >> -- >> This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing >> list >> To post a message email: RPG400-L@xxxxxxxxxxxx >> To subscribe, unsubscribe, or change list options, >> visit: http://lists.midrange.com/mailman/listinfo/rpg400-l >> or email: RPG400-L-request@xxxxxxxxxxxx >> Before posting, please take a moment to review the archives >> at http://archive.midrange.com/rpg400-l. >> >> > -- > This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list > To post a message email: RPG400-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/rpg400-l > or email: RPG400-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/rpg400-l. > > -- This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/rpg400-l or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.
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.