OSHELL is a TSO command. So you continue it using TSO conventions. Yes, I
have done this. Example:
//SYSTSIN DD *
OSHELL cd /some/directory; +
some-command file-in-some-directory
/*
//
I don't remember the maximum length for a TSO command. Oh, and I only use
column 1-72 . I don't remember if TSO allow sequence numbers in 73-80 or
not.
On Mon, Aug 19, 2013 at 7:16 PM, [email protected] <[email protected]> wrote:
> Last week there was a thread that discussed copying USS files in batch
> mode.
> One of the examples posted was:
> >
> >//OSHELL JOB CLASS=A,MSGCLASS=A
> >//UNIXIVP EXEC PGM=IKJEFT1B,DYNAMNBR=20
> >//SYSPROC DD DISP=SHR,DSN=SYS1.CLIST
> >//SYSTSIN DD DATA,DLM=$$
> > oshell cp -p /service1/ABC* /service2/testdir/
> >$$
> >//SYSTSPRT DD SYSOUT=*
> >//SYSOUT DD SYSOUT=*
> >//SYSPRINT DD SYSOUT=*
> >//SYSIN DD DUMMY
> >//
>
>
> My question is what is the proper method to continue a command across
> input lines when hhe command itself exceeds the physical length of the input
>
> If I specify
> oshell cp -p /usr/lpp/cics_test/utill/
> /usr/lpp/cics_prod/utill/
>
>
> How do I properly continue the copy statement when it wraps the length of
> the 80 position input ?
>
> Is there a continuation character ?
>
>
> Paul D'Angelo
> *********************************************
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN
>
--
As of next week, passwords will be entered in Morse code.
Maranatha! <><
John McKown
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
