|
I've encountered the same problem and i have a finding that if you sent parm which is longer than 33 char then you have to make sure you've sent full parm to the called program (char with no trailing blank character) Only in that way we could separate the two parm with no offset one in another. I've tested it in simple program which got two parms one is 40 char and one is 5 char **************************************************************** C *ENTRY PLIST C PARM VAR1 40 C PARM VAR2 5 C MOVE *BLANK VAR1 C MOVE 'HIIII' VAR2 C MOVEL'VAR1' VAR1 C MOVE *ON *INLR ****************** End of data **************************************** if i called this program with var1='123456789 ' var2='HIIII' then in the called program it would be like this '123456789 HIIII ' 'HIIII' the rest of the program will be error cause var1 affect var2 but (this is important) if i called this program with : '123456789 90' 'HIIII' then in the called program it would be like this '123456789 90' 'HIIII' and it is true the two variabel parameter is separated. you do clear on var1 and it will no effect on var2. i suggest you split the parm into 32 char or you could manipulate your input parm to have full character with no trailing char blank. I don't know how but hope this finding will be useful for u. ps:is this problem not encountered if i use callp on ILE RPG IV??? best regards, Danny Oentung. -----Original Message----- From: Silvio Santos [mailto:Silvio.Santos@brainag.com] Sent: Wednesday, July 12, 2000 6:01 PM To: RPG400-L@midrange.com Subject: RPG/400 pgm strange behaviour I have a program (RPG/400) that checks if some record exists and return. These two filds are *ENTRY parms of the PGM: MSDT$E - length 256 $RTC$E (*FOUND or *ERROR) - length 8A The condition used is like this: *IN,96 IFEQ '0' MOVEL'*FOUND' $RTC$E MOVELMSDTOH MSDT$E ELSE MOVEL'*ERROR' $RTC$E ENDIF It works fine, excepts for one thing: if the condition is true, when it moves the MSDTOH content to MSDT$E, it erases the $RTC$E field. For the other hand, when the first move is done, the '*Found' is placed in the 34th position of the field MSDT$E. Is there any restriction about entry parms lenght ? How can I resolve this? Thanks ,,,,,, (o o) -----------------------oOO--(_)--OOo------------------------ Silvio Santos BRAIN Portugal Tel: +351 252 248-120 Av. Joao Canavarro, 305 Fax: +351 252 248-111 4480-668 Vila do Conde Portugal Email: silvio.santos@brainag.com Web-Page: www.brainag.com --------------------------------------------------------------------- +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-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.