RE: Running batch jobs in Qinter

Henrik:

I too would prefer a routing program, though for the original question it 
probably doesn't need to do anything except retrieve the job type to see if 
it's batch or interactive, end the job with an error message for batch jobs and 
TFRCTL to QCMD otherwise. No need to examine the *RQS message at all in this 
case.

But in more robust cases such as yours, I'm curious about why you'd use CMD() 
over RQSDTA(). I can understand why you'd avoid a length of 256, but a length 
of 3000 is what RQSDTA() will accept as a maximum and CMD() must accommodate 
the same length anyway, AFAIK.

Tom Liotta

midrange-l-request@midrange.com wrote:

>   9. RE: Running batch jobs in Qinter (Henrik Krebs)
>
>
>a better way to execute a command than using QCMDEXC is to re-send the &RQS=
>DTA to *EXT type *RQS and give it over to original request processor by TFR=
>CTL to QCMD.
>
>I used that once to do things to CRTxxx like processing in-source embedded =
>commands (OVRDBF before compile etc), build xref etc. In that way I managed=
> to be able to recompile entire production source files (a good guarantee t=
>hat your system is solid and source/object consistent).
>
>btw-1: VAR(&RQSDTA) LEN(256) will give you troubles. I often have use comma=
>nds.

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


__________________________________________________________________
The NEW Netscape 7.0 browser is now available. Upgrade now! 
http://channels.netscape.com/ns/browsers/download.jsp

Get your own FREE, personal Netscape Mail account today at 
http://webmail.netscape.com/