Re: Automation of the TSO RECEIVE command

2022-08-31 Thread Paul Gilmartin
On Thu, 1 Sep 2022 08:47:39 +0800, Peter Van Dyke wrote: > >Here's an example of the JCL for the job: >/*... >//* >//XMIT01 DD DATA,DLM='@%' >*- Data created by XMIT for data set 1 -* > How do you ensure that the XMIT data does not contain '@%' in columns 1-2? Long ago, I experi

Re: Automation of the TSO RECEIVE command

2022-08-31 Thread Peter Van Dyke
Mainframe Discussion List On Behalf > Of Paul Gilmartin > Sent: 31 August 2022 13:56 > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Automation of the TSO RECEIVE command > > On Wed, 31 Aug 2022 11:12:12 +0100, Lennie Dymoke-Bradshaw wrote: > > >The TSO commands TRANSMIT and

Re: Automation of the TSO RECEIVE command

2022-08-31 Thread Lennie Dymoke-Bradshaw
-MAIN@LISTSERV.UA.EDU Subject: Re: Automation of the TSO RECEIVE command On Wed, 31 Aug 2022 11:12:12 +0100, Lennie Dymoke-Bradshaw wrote: >The TSO commands TRANSMIT and RECEIVE are very useful for moving data >around, particularly as TRANSMIT produces an 80-byte LRECL which works >easily with

Re: Automation of the TSO RECEIVE command

2022-08-31 Thread Matthew Stitt
Interesting The next line was there when I copied it: PROFILE NOPROMPT NOPREFIX RECEIVE INDA('MSTITT.IBM.HHOP850.F1.BIN') DATASET('MSTITT.HHOP850.F1') Matthew On Wed, 31 Aug 2022 13:43:22 -0500, Paul Gilmartin wrote: >On Wed, 31 Aug 2022 13:22:28 -0500,

Re: Automation of the TSO RECEIVE command

2022-08-31 Thread Tony Harminc
On Wed, 31 Aug 2022 at 06:14, Lennie Dymoke-Bradshaw < 032fff1be9b4-dmarc-requ...@listserv.ua.edu> wrote: > The TSO commands TRANSMIT and RECEIVE are very useful for moving data > around, particularly as TRANSMIT produces an 80-byte LRECL which works > easily with in-stream JCL. > > But has an

Re: Automation of the TSO RECEIVE command

2022-08-31 Thread Willy Jensen
You can pull the information from the XMIT dataset and then either present it to the user in a dialog, or act upon it directly. Here is a snippet that 'says' the original datasetname and user.. /* get xmit datasetname */ arg inda

Re: Automation of the TSO RECEIVE command

2022-08-31 Thread Paul Gilmartin
On Wed, 31 Aug 2022 13:22:28 -0500, Matthew Stitt wrote: >Here is a snippet from my JCL: > >//TSO EXEC PGM=IKJEFT01,DYNAMNBR=20 >//SYSTSPRT DD SYSOUT=* >//SYSPROC DD DSN=MSTITT.CLIST,DISP=SHR >//SYSTSIN DD * >PROFILE NOPROMPT NOPREFIX

Re: Automation of the TSO RECEIVE command

2022-08-31 Thread Paul Gilmartin
On Wed, 31 Aug 2022 12:26:11 -0500, Steve Horein wrote: > >> > >It's safer if you use "DATA,DLM='U5ZMw0Di'", for example in JES2. In JES3, >> you're SOL. >> >> ( I used "head -c6 /dev/random | uuencode -m x".) > >What leads you to believe DATA or DLM is unacceptable with JES3? >I use it quite ext

Re: Automation of the TSO RECEIVE command

2022-08-31 Thread Matthew Stitt
>From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of >Lennie Dymoke-Bradshaw [032fff1be9b4-dmarc-requ...@listserv.ua.edu] >Sent: Wednesday, August 31, 2022 6:12 AM >To: IBM-MAIN@LISTSERV.UA.EDU >Subject: Automation of the TSO RECEIVE comma

Re: Automation of the TSO RECEIVE command

2022-08-31 Thread Seymour J Metz
-Bradshaw [032fff1be9b4-dmarc-requ...@listserv.ua.edu] Sent: Wednesday, August 31, 2022 6:12 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Automation of the TSO RECEIVE command The TSO commands TRANSMIT and RECEIVE are very useful for moving data around, particularly as TRANSMIT produces an 80-byte

Re: Automation of the TSO RECEIVE command

2022-08-31 Thread Steve Horein
On Wed, Aug 31, 2022 at 7:56 AM Paul Gilmartin < 042bfe9c879d-dmarc-requ...@listserv.ua.edu> wrote: > It's safer if you use "DATA,DLM='U5ZMw0Di'", for example in JES2. In JES3, > you're SOL. > > ( I used "head -c6 /dev/random | uuencode -m x".) > > -- > gil > What leads you to believe DAT

Re: Automation of the TSO RECEIVE command

2022-08-31 Thread Paul Gilmartin
On Wed, 31 Aug 2022 11:12:12 +0100, Lennie Dymoke-Bradshaw wrote: >The TSO commands TRANSMIT and RECEIVE are very useful for moving data >around, particularly as TRANSMIT produces an 80-byte LRECL which works >easily with in-stream JCL. > But there's a hazard. The encoded data might by happensta

Re: Automation of the TSO RECEIVE command

2022-08-31 Thread Robin Atwood
August 2022 17:12 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Automation of the TSO RECEIVE command The TSO commands TRANSMIT and RECEIVE are very useful for moving data around, particularly as TRANSMIT produces an 80-byte LRECL which works easily with in-stream JCL. But has anyone worked out a reliable me

Re: Automation of the TSO RECEIVE command

2022-08-31 Thread Peter Vels
Just put the response on the next line of the input: RECEIVE INDSN('bla.XMIT') DATASET('bla.LOAD') On Wed, 31 Aug 2022, 20:19 Lennie Dymoke-Bradshaw, < 032fff1be9b4-dmarc-requ...@listserv.ua.edu> wrote: > The TSO commands TRANSMIT and RECEIVE are very useful for moving data > around, partic

Automation of the TSO RECEIVE command

2022-08-31 Thread Lennie Dymoke-Bradshaw
The TSO commands TRANSMIT and RECEIVE are very useful for moving data around, particularly as TRANSMIT produces an 80-byte LRECL which works easily with in-stream JCL. But has anyone worked out a reliable mechanism to automate the use of the RECEIVE command? It always issues queries to the user.