If tape is shared... Then use IEBGENER ( ICEGENER ) to copy the XMIT dataset to
tape... and restore that DSN from tape to feed RECEIVE
FTP is horrible to use ... too much latencies ... Using TERSE in there adds
verification that the data is intact ...
---
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
rpinion865
Sent: Wednesday, December 14, 2022 10:10 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [Public] RE: EXTERNAL: Re: Transmitting SMF records
Like I said earlier, you can TERSE to a tape dataset. I use that method all of
SMF data is usually VBS format, Variable Block Span. Physical blocks 4K but
records can be much larger.
First question: Are the two z/OS machines connected via TCP/IP ? if so TERSE
XMIT to the 2nd machine, RECEIVE, DETERSE else
Second: Is the data VB or still VBS?
Using TERSE and then XMIT
Like I said earlier, you can TERSE to a tape dataset. I use that method all of
the time, for transferring mainframe data between mainframe systems, that have
an intervening non-mainframe repository.
Sent with Proton Mail secure email.
--- Original Message ---
On Wednesday, December
Be aware that your installation may have a limit on the size of a Transmit
(XMIT) file. Issue TSO PARMLIB and look for the OUTLIM value - if too small
you may want to increase it - the same for OUTWARN which reports every
increment of the XMIT file.
Using TERSE is probably the better solution
