For a truly first class solution--at a first class price--there's Connect Direct (formerly NDM). Connect Direct offers guaranteed delivery even across IPL outages. It also works between z/OS and UNIX. The product has to be functional at both ends, likely increasing the cost further.
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
626-543-6132 Office ⇐=== NEW
From: IBM Mainframe Discussion List [mailto:IBM-***@LISTSERV.UA.EDU] On Behalf Of Lizette Koehler
Sent: Saturday, May 20, 2017 10:19 AM
Subject: (External):Re: Sample JCL for file transfer using NJE/TCPIP
TRSMAIN and TSO XMIT both take the input file and build it into fixed length records. The output file contains the information needed to reconstruct the file in its original format. So LRECL, BLKSIZE, DSORG, RECFM, etc... which it will use to restore the file to its original state.
So some tools that can be used to set-up a file to be transmitted
The SEQ and PDS or PDSE files are easy enough to work with
VB, VBS files or SVC Dump datasets (for example) provide more of a challenge
The preferred method for transmitting files from mainframe to another location will depend on your shop's standards.
When I need to move SMF or SVC Dumps, I will sometimes TRSMAIN the file. Then I can use FTP or other transmission product to send the file where it needs to go. When it lands on another Mainframe host, I can run TRSMAIN again to unterse it. Note: TRSMAIN has pack and super-pack options
If I have a PDS/PDSE/SEQ file, I will sometimes use TSO XMIT. The file is written to an output dataset. Then the output dataset it transmitted to a new host and RECEIVEd.
Once the file resides on your target system, it can remain in the TRSMAIN or TSO XMIT form until you need it. Then you will need to run a process to restore the file. TRSMAIN is UNPACK, TSO XMIT is RECEIVE.
TSO XMIT (Transmit) takes a file and compresses it (if possible)
You can transmit the file and place it on JES2 SPOOL. Or you can XMIT node.id filename OUTDSN('output file name')
The OUTDSN can then be transmitted with FTP or other transmission products.
It is used as a way to transport files between z/OS systems. Even when there is a non-mainframe in the middle.
So like TRSMAIN, it can provide a transport file.
Note: Some shops restrict the number or amount of data that can be XMIT'd via Spool. So using OUTDSN is preferred mechanism
Here is a nice write up of TRSMAIN
Here is some helpful tips on VSAM
If this does not help clarify the concepts, let us know what else you need to know.
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:IBM-***@LISTSERV.UA.EDU]
> On Behalf Of Nathan Astle
> Sent: Saturday, May 20, 2017 3:54 AM
> To: IBM-***@LISTSERV.UA.EDU
> Subject: Re: Sample JCL for file transfer using NJE/TCPIP
> Hi Ed
> I was trying to understand if XMIT is used versus FTP then I will
> have to run a TSO RECEIVE command from the target LPAR to ensure the
> file is available in Target LPAR
> On May 20, 2017 2:38 PM, "Edward Finnell" < 0000000248cce9f3-dmarc-
> ***@listserv.ua.edu> wrote:
> > What have you tried?
> > //JOBCARD JOB
> > //STEP1 EXEC PGM=IKJEFT01,REGION=4096K,DYNAMNBR=16
> > //SYSTSPRT DD SYSOUT=A
> > //SYSTSIN DD *
> > TRANSMIT nodename.userid DSN('my.big.honkin.smf')
> > //*
> > In a message dated 5/20/2017 1:38:12 A.M. Central Daylight Time,
> > ***@GMAIL.COM writes:
> > Could someone please help me with the sample JCL for transferring a
> > file(SMF) Using NJE TCPIP link.
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN