Unconfigured Ad Widget

Collapse

TechTip: Parameter Passing

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • MCWebsite.Staff
    Senior Member
    • Dec 2007
    • 997

    TechTip: Parameter Passing

    ** This thread discusses the article: TechTip: Parameter Passing **
    ** This thread discusses the Content article: TechTip: Parameter Passing **
    0
  • Guest.Visitor

    #2
    TechTip: Parameter Passing

    ** This thread discusses the article: TechTip: Parameter Passing **
    1. Another option would be to make it into one parm. Call pgm 'ABC123' would work fine (then just parse it in the CL program). 2. or, just make the numeric field a character field and have a leading or trailing character as U123 instead of just 123 (then just parse it in the CL program). Jim Gardner 813-282-3828 x 2403

    Comment

    • buck.calabro@commsoft.net

      #3
      TechTip: Parameter Passing

      ** This thread discusses the article: TechTip: Parameter Passing **
      A discussion of this very topic is in the FAQ at http://faq.midrange.com Search for 'garbage'. The link is at the lower left. The general consensus of several mailing lists is that specifying numeric parameters in the form x'012345f' is fine for testing, but for production, defining a command is far better. The command processing program can be either RPG or CL. It is important to recognise that this issue is not related to the command line; in fact, it is an issue in any place you use a literal as a parameter, like SBMJOB or CALL from one program to another using literals instead of variables. --buck

      Comment

      Working...
      X