× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: where did those zeros come from?
  • From: "James W. Kilgore" <eMail@xxxxxxxxxxxxxxxxxxx>
  • Date: Thu, 22 Mar 2001 10:59:50 -0800
  • Organization: Progressive Data Systems, Inc.

Ray,

I know that's it a matter of personal preference, but IMHO, the command
route is cleaner.

In file QCMDSRC create the following member:  (Now, I like to call my
commands the same as the CPP (Command processing Program) but it's not
necessary.)

*************** Beginning of data *************************************
             CMD        PROMPT('Wrapper for program PRR50130')         
             PARM       KWD(P01) TYPE(*CHAR) LEN(30) ALWVAR(*YES) + 
                          PROMPT('Parameter #1')                       
             PARM       KWD(P02) TYPE(*CHAR) LEN(90) ALWVAR(*YES) + 
                          PROMPT('Parameter #2')                       
             PARM       KWD(P03) TYPE(*CHAR) LEN(9)  ALWVAR(*YES) + 
                          PROMPT('Parameter #3')                       
             PARM       KWD(P04) TYPE(*CHAR) LEN(8)  ALWVAR(*YES) + 
                          PROMPT('Parameter #4')                       
             PARM       KWD(P05) TYPE(*CHAR) LEN(8)  ALWVAR(*YES) + 
                          PROMPT('Parameter #5')                       
****************** End of data ****************************************


Then compile (CRTCMD) with:

                            Create Command (CRTCMD)           
                                                              
Type choices, press Enter.                                    
                                                              
Command  . . . . . . . . . . . . CMD          > PRR50130      
  Library  . . . . . . . . . . .              >   MYLIB  
Program to process command . . . PGM          > PRR50130      
  Library  . . . . . . . . . . .              >   *LIBL       
Source file  . . . . . . . . . . SRCFILE      > QCMDSRC       
  Library  . . . . . . . . . . .              >   MYLIB  
Source member  . . . . . . . . . SRCMBR       > PRR50130      
Text 'description' . . . . . . . TEXT           *SRCMBRTXT    
                                                              
                                                              
                           Additional Parameters              
                                                              
Replace command  . . . . . . . . REPLACE      > *YES          
                                                              

The end result is that in your CL program that you have been having
problems with, the SBMJOB would look like this:

********* Beginning of data ***************************************
       SBMJOB     CMD(PRR50130 P01(&P01) P02(&P02) +         
                    P03(&P03) P04(&P04) P05(&P05)) +      
                    JOB(PRR50130XX) JOBQ(QPGMR2)                   


HTH


"Ray, Adam" wrote:
> 
> Thanks Scott. I used solution number 2, only because I am clueless as to how
> to do number 1. I would love to learn though.
>
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.