Re: Command Processing -- MIDRANGE-L

Martin:

From past experience, I suspect you can go a long ways on your own with a 
simple example. I'm including two sample demo CLPs that should illustrate the 
difference.

The first, TstSbmJob, executes SBMJOB RQSDTA() and SBMJOB CMD() for what should 
appear to give exactly the same results. You should change the &CmdStr value so 
that "MyMsgQ" is replaced with the name of your *msgq. Both SBMJOBs issue CALL 
TSTSNDMSG, the second program, with parms. Under most circumstances, the 
results will be quite different. (If you have to respond to a message on 
QSYSOPR, reply with 'D' so you'll see what happened. Familiar looking problem 
perhaps.)

The difference is in what happens to the CMD() value before the job gets 
submitted. When the SBMJOB prompts are shown, just press <Enter>; don't 
actually change anything.

/*------------------------------------------------*/

TstSbmJob CLP:

TstSbmJob:  pgm                                              
                                                             
  dcl   &cmdstr   *char  64  value( 'sndmsg hi MyMsgQ' )     
  dcl   &xgarbage *char  64  value( 'who knows?????? ' )     
                                                             
  sbmjob ??rqsdta( 'call tstsndmsg parm(''' *cat &CmdStr +   
                    *cat ''' ''' *cat &XGarbage *cat ''')' ) 
                                                             
  sbmjob ??cmd( call pgm(TstSndMsg) parm(&CmdStr &XGarbage) )
                                                             
return                                                       
endpgm

/*------------------------------------------------*/

TstSndMsg CLP:

TstSndMsg:  pgm  ( +                           
                   &pCmdStr    +               
                   &pXGarbage  +               
                 )                             
                                               
   dcl   &pCmdStr    *char  64                 
   dcl   &pXGarbage  *char  64                 
                                               
   dcl   &CmdLen     *dec ( 15 5 )  value( 64 )
                                               
   call  QCmdExc   ( +                         
                     &pCmdStr  +               
                     &CmdLen   +               
                   )                           
                                               
return                                         
endpgm

/*------------------------------------------------*/

If this produces no error on your system, I'd very much like info on what PTFs, 
OS level, etc., that you've got, because it errors out everywhere I've ever 
been.

Tom Liotta

On Fri, 13 July 2001, Martin Rowe wrote:

> This has me confused (not difficult). I have always assumed that the 
> CMD() parm was added as in improvement to RQSDTA(). I can't think of 
> anmywhere at our site, other than legacy S/38 apps, that still use 
> RQSDTA. I thought I've read there's a more restrictive command length 
> limit on it too, plus all the escaping of quotes required and no 
> prompting available. What *is* the difference then, and what makes RQSDTA 
> more powerful/preferable? Pointers to the appropriate docs if you haven't 
> the time/inclination to go into detail on this would be appreciated.

-- 
Tom Liotta
The PowerTech Group, Inc.
19426 68th Avenue South
Kent, WA 98032
Phone  253-872-7788
Fax  253-872-7904
http://www.400Security.com


___________________________________________________
The ALL NEW CS2000 from CompuServe
 Better!  Faster! More Powerful!
 250 FREE hours! Sign-on Now!
 http://www.compuserve.com/trycsrv/cs2000/webmail/




+---
| 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
+---