RE: *ISO Date fieldin ILE from CLLE

CLLE passes the date 8S0 as a packed field.  Send it as an 8 character field
or define it as packed in your second procedure.

Christopher K. Bipes     mailto:ChrisB@Cross-Check.com
Sr. Programmer/Analyst   mailto:Chris_Bipes@Yahoo.com
CrossCheck, Inc.         http://www.cross-check.com
6119 State Farm Drive    Phone: 707 586-0551 x 1102
Rohnert Park CA  94928 Fax: 707 586-1884

*Note to Recruiters
Neither I, nor anyone that I know of, is interested in any new and/or
exciting positions. Please do not contact me.


-----Original Message-----
From: Jeff Crosby [mailto:jlcrosby@fwi.com]
Sent: Tuesday, February 22, 2000 6:57 AM
To: RPG400-L@midrange.com
Subject: *ISO Date fieldin ILE from CLLE


I've done some testing and searching and can't get the following to
work, so I must be missing something somewhere, so hopefully one of you
can help me out.

The Setup
=========

     D IsRchStrD8      PR            
1A                                                    
     D  TestDate8                     8S 0 Const

and the procedure interface is:

     P IsRchStrD8      B                   Export 
     D IsRchStrD8      PI             1A          
     D   TestDate8                    8S 0 Const  

This subprocedure simply converts the input date to an *ISO field (which
happens to be a call to another service program that does these types of
conversions), then calls IsRchStrDt with the converted date.  Now, I
thought, I'll pass an 8-character field like "20000306".  Still no
work.  Tried defining the field in the CLLE program as *DEC length 8. 
Still no work.

What am I missing?  Within the subprocedure, do I need to move the input
parm to another field first?
Thanks for any help.
+---
| 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
+---