Re: Relaying a (not) passed parm to another proc

Thanks to both Scott Klement and Roger Mackie (for the perfect answer for Scott's *NOPASS issue).

Scott, I think, if I understood your answer correctly, that you meant to say "so long as the procedure you call also has options(*OMIT)", not *NOPASS. Right?
"As long as you really mean options(*OMIT) and NOT options *NOPASS, then
you shouldn't have a problem, so long as the procedure you call also has
options(*NOPASS)."

Arthur J. Marino
Southern Container Corporation
(631) 297 - 2276
________________________________
This message, including its attachments, constitutes an electronic communication within the meaning of the Electronic Communications Privacy Act, 18 U.S.C. Section 2510. This message is the confidential property of Rock-Tenn Company, and disclosure is strictly limited to recipients intended by the sender. Unless previously authorized in writing, this message does not constitute an offer, acceptance, or agreement of any kind. This message may contain confidential attorney-client privileged information and attorney work product. If you are not the intended recipient, or responsible for delivering e-mail to the intended recipient, you are advised that use, dissemination, forwarding, printing, or copying of this message is STRICTLY PROHIBITED. If you receive this message in error, please notify the sender immediately by return e-mail and delete the message entirely from your system. Sender is not liable for damage caused by viruses transmitted with this message, or errors or omissions in content caused by transmission.
(c) Rock-Tenn Company, Norcross, GA.