| Date: | Mon, 14 Apr 1997 16:15:18 PDT |
|---|
| Reply-To: | TWB2%Rates%FAR@GO50.COMP.PGE.COM |
|---|
| Sender: | "SAS(r) Discussion" <SAS-L@UGA.CC.UGA.EDU> |
|---|
| From: | TWB2%Rates%FAR@GO50.COMP.PGE.COM |
|---|
| Subject: | Re: SUBMIT vs. IKJEFT01 TSO in Batch |
|---|
Tim, SUBMIT may be a special case, or your site may have a cataloged PROC for
SUBMIT, but valid TSO commands are not normally valid cataloged PROC's.
IKJEFT01 is the batch version of TSO, so it can process SUBMIT just as TSO
would.
Tim Berryhill - Contract Programmer and General Wizard
TWB2@PGE.COM or http://www.aartwolf.com/twb.html
Frequently at Pacific Gas & Electric Co., San Francisco
The correlation coefficient between their views and
my postings is slightly less than 0
----------------------[Reply - Original Message]----------------------
Sent by:Tim Latendress <TIM.LATENDRESS@LATENT62.CUSTOMS.SPRINT.COM>
"Connolly, Roger" <rconn@ACCX.GHC.ORG> suggested:
<SNIP>
> 5) Easier than the above, add a job step that does this:
>
> //LASTSTEP EXEC PGM=IKJEFT01
> //SYSTSPRT DD SYSOUT=*
> //SYSTSIN DD DATA,DLM='@@'
> SUBMIT 'pds name(membername)'
How is that different from:
//LASTSTEP EXEC SUBMIT,DSN='pds.name(membername)'
Does your approach get around some barriers?
| 
