steve-myers wrote:Actually, none of your ideas would work. The SYSOUT data set created by XMIT belongs to the job/TSO session that created the data set. Even if you know you have a data set the RECEIVE command will get, finding it in SDSF is not so easy unless you know who sent it. If the job/TSO session is still active when you try to find it in SDSF, the queue names you posted should work. If the job/TSO session has ended, the job/TSO session is in the JES2 "hardcopy" queue.
Your "transmission or spool offload" queue, more properly, is just the SPOOL offload queue; it has nothing to do with data being sent by the XMIT command. Jobs in the SPOOL offload queue are processed by offload job transmitter and SYSOUT transmitter tasks in JES2.
Working in a very large mainframe environment currently on multiple systems/LPARs and here are some more notes on Transmit (Xmit) and Receive. When you/someone else transmits a file or message to anoter NODEid (NODEid=z/OS system or LPAR) ...a JES message will be displayed on sending NODEid
20.22.21
TSU10354 $HASP546 RSILVER(TSU49776 from TSO03) SYSTEM OUTPUT RECEIVED AT
TSO09 CN(INTERNAL)
The red Highlight above will show up in SDSF on receiving
TSO09 in SDSF/ST with
JOBNAME (RSILVER) JOBID(TSU10354) QUEUE(PRINT) DEST(RSILVER).
. And the jobs will have DDNAMES as SYS##### were the XMIT is located in IEBCOPY format. On Fandezhi because there is only 1 NODEid N1 you wont see the JES messages. Also, remember in SDSF/ST make sure you have JOBID filter set to
FILTER JOBID EQ *. This will show both TSU (TSO jobs) and JOB (batch jobs).
If you want to try on Fandezhi, you can see the TRANSMITs under your TSU sessions as SYS#####. These are in IEBCOPY format and cannot be easily read. Transmit and Receive use IEBCOPY to send and receive datasets and messages.
- Code: Select all
NP DDNAME StepName ProcStep DSID Owner C Dest
JESMSGLG JES2 2 RSILVER K
JESJCL JES2 3 RSILVER K
JESYSMSG JES2 4 RSILVER K
SYS00043 SYSUSER SYSUSER 101 RSILVER B RSILVER
SYS00046 SYSUSER SYSUSER 102 RSILVER B RSILVER
All the information about TRANSMITs and RECEIVEs are maintained in a system data set named USERID.LOG.MISC
- Code: Select all
VIEW RSILVER.LOG.MISC Columns 00001 00072
Command ===> Scroll ===> 0005
=COLS> ----+----1----+----2----+----3----+----4----+----5----+----6----+----7--
****** ***************************** Top of Data ******************************
000001 ------------------------------------------------------------------------
000002 TRANSMIT RSILVER.EXEC 08 DEC 201
000003 TO: N1 RSILVER
000004 MEMBERS: LAMBO
000005 ------------------------------------------------------------------------
000006 TRANSMIT **MESSAGE** 08 DEC 201
000007 TO: N1 RSILVER
000008 This is a test
000009 This is a test
000010 This is a test
000011 This is a test
000012 This is a test
000013 This is a test
TRANSMIT (Xmit) and Receive have been around a long time...based I believe on IBM SNA. I know working in a multiple platform environment AS/400 (iSeries, IBM system I) has similar commands WRKNETF, RCVNETF, and SNDNETF as does VM that was mentioned on this post. But, in lots of shops this has been replaced with NDM (Connect/Direct) or FTP. I believe the whole ideal behind using XMIT NODE.USERID was not to use a password and send across networks which made it a whole lot safer then FTP....
On Fandezhi, the TSO HELP PDS is not allocated to DD SYSHELP...so if you type TSO HELP TRANSMIT...you will get message
IKJ56802I HELP NOT AVAILABLE+.View the 'SYS1.HELP' PDS and you can read about TRANSMIT 'SYS1.HELP(TRANSMIT)
' and RECEIVE 'SYS1.HELP(RECEIVE)'.