This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. -- [ Picked text/plain from multipart/alternative ] Barbara, Thanks for the clarification. Regards, Jon A. Erickson Sr. Programmer Analyst 800.COM Inc. 1516 NW Thurman St Portland, OR 97209-2517 Direct: 503.944.3613 Fax: 503.943.9313 Web: http://www.800.com -----Original Message----- From: firstname.lastname@example.org [mailto:email@example.com] Sent: Monday, December 17, 2001 8:08 AM To: firstname.lastname@example.org Subject: Alarm: *nopass vs *omit (was RE: Retrieving and formatting current time in RPGLE) >From: email@example.com >Date: Fri, 14 Dec 2001 13:45:55 -0800 > ... >But I have to add a warning to it,... without the Omissible Feedback >Parameter (*Nopass) defined in the prototypes, and a couple of changes to PR >field definitions, (10U 0 -> 10I 0), other defined fields in the >program/memory became corrupted, or at least they did for me, (imagine me >reading a manual). Thus resulting in the following code: > ... It should be options(*omit). In the API documentation, "optional" means *NOPASS, "omissible" means *OMIT. Rule to live by: Never use OPTIONS(*NOPASS) with CEE APIs. Barbara Morris _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-Lfirstname.lastname@example.org Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.