No. There are several scenarios, as I noted on Friday, February 4, 2022 12:15
PM, and that CLIST doesn't help for any of them. You could use a GTF trace and
look at the parameters for MGCR, TPUT and WTO. The only logging that the system
does for any of the scenario is logging the SEND operator command (not the SEND
TSO command) to syslog, and that does not involve a temporary dataset. To
summarize:
SEND to available user
TPUT, no logging unless receiver is in TSD SM.
SEND to unavailable user
SEND records the message in the broadcast data set or in
the receiver's user log
SEND to console
WTO; message retained in hardcopy log
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
________________________________________
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of CM
Poncelet [000003e99a92061c-dmarc-requ...@listserv.ua.edu]
Sent: Saturday, February 5, 2022 11:03 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Is there a TSO SEND history anywhere?
FWIW No idea whether this would help finding where TSOSEND data is
logged (try a GTF + parms, if 'critically important') - but I would
suspect that the data is stored in system genned temp datasets, possibly
in VIOs, and deleted after the data I/O sent-and-displayed on
terminal screens. Perhaps displayed in the syslog. If it were
straight-forward, I would expect the IBM system savants to have posted a
resolution by now. If. HTH. Cheers etc.
Job TSOSEND:
------------
//*********************************************************************
//* NOTE: NO LINE NUMBERS IN COLS 73-80 ALLOWED, ELSE CLIST FAILS! *
//* ¯¯¯¯¯ *
//*********************************************************************
//* NOTE: 'U' => TSO USERID(S); SPECIFY LIST OF USERIDS UNDER DESTIDS *
//* ¯¯¯¯¯ 'C' -> CONSOLE; SPECIFY MASTER ETC. UNDER CONSIDS *
//* *
//* 04/01/95 CMP *
//*********************************************************************
//*
//CLIST EXEC PGM=IKJEFT01,
// REGION=512K,
//* PARM='%TSOSEND DESTIDS SYSIN USERID'
// PARM='%TSOSEND CONSIDS SYSIN CONSOLE'
//*
//SYSPROC DD DISP=SHR,DSN=<whatever>.ISPCLIB
//SYSTSIN DD DUMMY
//SYSTSPRT DD SYSOUT=*
//CONSIDS DD *
<whatever CONSOLE ID>
//*
//DESTIDS DD *
<whatever USERID1>
<whatever USERID2>
...
<whatever USERIDn>
//SYSIN DD *
Dear MVS OPS,
<whatever OPS message#1>
<whatever OPS message#2>
...
<whatever OPS message#n>
Thanks a lot.
Chris
/*
//*
//
CLIST TSOSEND:
--------------
PROC 2 DESTLIST MESSAGE DEBUG USERID CONSOLE
/*-------------------------------------------------------------------*/
/* N.B. DEFAULT IS 'NOW' */
/* 'LOGON' -> 'NOW' IF LOGGED ON, ELSE AT LOGON TIME. */
/* 'SAVE' -> ONLY AT NEXT LOGON TIME (OR LISTBC) */
/* */
/* PARMS: DESTLIST DDNAME OF USERS/CONSOLES TO WHOM MESSAGE IS TO */
/* BE SENT - DEFAULT=NONE */
/* MESSAGE: DDNAME OF MESSAGE TEXT TO BE SENT - DEFAULT=NONE */
/* DEBUG: SETS TRACE ON - DEFAULT=OFF */
/* */
/* 02/05/00 CMP - SET EXIT CODE TO 0 */
/* 13/12/94 CMP - ALLOW SENDING TO USERID(S) OR TO MVS CONSOLE(S) */
/* 17/04/89 CMP */
/*-------------------------------------------------------------------*/
CONTROL: +
CONTROL END(ENDO)
IF &DEBUG = DEBUG | &DEBUG = D THEN +
CONTROL LIST SYMLIST CONLIST MSG ASIS
ELSE +
CONTROL NOLIST NOSYMLIST NOCONLIST NOMSG ASIS
ERROR: +
ERROR DO
SET CC = &LASTCC
IF &CC = 400 THEN RETURN
ELSE DO
WRITE ERROR WITH CONDITION CODE = &CC OCCURRED : INTERRUPT AT LABEL +
'ERROR'
WRITE CLIST RUN ABANDONNED
GOTO EXIT
ENDO
ENDO
IF &USERID ¬= THEN SET TO = USER
ELSE IF &CONSOLE ¬= THEN SET TO = CN
ELSE +
WHERE: +
DO
WRITE YOU MUST SPECIFY PARAMETER 'USERID' OR 'CONSOLE'
WRITE
GOTO EXIT
ENDO WHERE
SET SENDTO =
SET K = &&K
SET USREC = &&&DESTLIST
SET MSGREC = &&&MESSAGE
SET MAXCC = 0
OPENFILE &DESTLIST INPUT
GETFILE &DESTLIST
DO I = 0 TO 99 WHILE &MAXCC = 0
SET USER = &USREC
SET J = &SYSINDEX(&STR( ),&USER,1)
SET J = &J - 1
SET USER = &SUBSTR(1:&J,&USER)
SET SENDTO = &STR(&SENDTO&USER,)
GETFILE &DESTLIST
ENDO
CLOSFILE &DESTLIST
IF &I > 0 THEN +
DO
SET LSENDTO = &LENGTH(&STR(&SENDTO)) - 1
SET SENDTO = &SUBSTR(1:&LSENDTO,&STR(&SENDTO))
SET MSG = &&MSG
SET MAXCC = 0
OPENFILE &MESSAGE INPUT
GETFILE &MESSAGE
DO J = 1 TO 99 WHILE &MAXCC = 0
SET MSG&J = &SUBSTR(1:71,&MSGREC)
SET K0 = 1
DO I = 1 TO 99 WHILE &K&EVAL(&I-1) > 0
SET K&I = &SYSINDEX(&STR('),&STR(&MSG&J),&K&EVAL(&I-1))
IF &K&I > 0 THEN SET K&I = &K&I + 1
ENDO
DO L = &I-2 TO 1 BY -1 WHILE &K&L > 0
SET MSG&J = &SUBSTR(1:&K&L-1,&STR(&MSG&J))&STR(')+
&SUBSTR(&K&L:&LENGTH(&STR(&MSG&J)),&STR(&MSG&J))
ENDO
GETFILE &MESSAGE
ENDO
SET J = &J - 1
DO I = 1 TO &J
SEND '&MSG&I' +
&TO(&STR(&SENDTO)) LOGON
ENDO
ENDO
EXIT: +
EXIT CODE(0)
On 04/02/2022 18:43, Charles Mills wrote:
> 1. I am running ISPF full screen. So once I hit Enter the message seems to
> be gone, gone, gone.
>
> 2. The particular SENDs that I am interested in is sent from a batch job
> with Rexx Address TSO "SEND ... but the question was intended to be general.
> I don't see it in SYSLOG. I do see the SENDS that JES2 uses for NOTIFY=
>
> 3. Seems to me I tried Session Manager years ago and did not like it.
>
> Charles
>
>
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Seymour J Metz
> Sent: Friday, February 4, 2022 9:15 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Is there a TSO SEND history anywhere?
>
> That depends. For an MVS SEND command, including a TSO SEND that does an MVS
> SEND, there is the syslog. For a TSO SEND that does a TPUT to another user,
> the only way that I know of requires that you be running under the TSO
> Session Monitor.
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> .
>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
