RE: This is friggin' weird...

["Wills, Mike N. (TC)" <MNWills@xxxxxxxxxxxxxx>]

Title: Message

You hit the 32 char limit. See the FAQ and and archives for the information.

 

 

Mike Wills

IT Corporate Support

MNWills@taylorcorp.com

-----Original Message-----
From: tomh@simas.com [mailto:tomh@simas.com]
Sent: Thursday, July 12, 2001 5:01 PM
To: rpg400-l@midrange.com
Subject: This is friggin' weird...

I'm having a 
strange problem, and surely you guys can see what it is that I'm not 
seeing: 

WO11C (CLP): 
dcl &parms *char 39 
display prompt screen, get various parms 
combine parms into var &PARMS 
call WO11JQ0 PARM(&PARMS) 

WO11JQ0 (CLP): 
dcl &parms *char 39 
call 
WO11BWFR2 parm(&parms) 

WO11BWFR2 
(SQLRPGLE): 
fqsysprt   o   
 f   80        printer         
                  
c     *entry        plist 
                      
                
c                 
  parm                   
 parms            39 
c                 
  except    exc01             
                
c                 
  eval      *inlr = *on           
            
oqsysprt   e            exc01   
                      
          
o 
                      
                      
 '>'               
o                 
      parms               
                    
o           
                      
             '<'       
        


Let's suppose that the combined value of &parms in WO11C is 
"300000YLAAPY0620012                 
   "   (that's 20 blank trailing spaces) 

Now, here's the weird stuff: 
If I run WO11C like you see, WO11BWFR gets this for 
variable parms: "300000YLAAPY0620012             
       " 

If I 
change the call to a SBMJOB: 
SMBJOB 
CMD(CALL PGM(WO11JQ0) PARM(&PARMS)) 
BO11BWFR gets this for parms: "300000YLAAPY0620012       
       CALLf "   (that's 14 blanks before CALLf, 1 
after) 

If I change the SBMJOB to 
this: 
SBMJOB CMD(CALL PGM(WO11JQ0) 
PARM('300000YLAAPY0620012               
     ')) 
WO11BWFR gets 
the parm correctly. 

What am I 
overlooking?