Bob's approach is much cleaner and used by several of us. Personally, I
review the output in BROWSE by default rather than VIEW and switch to VIEW only
if I need to use EXCLUDE and FIND commands to work through a really long
trace (I usually go to batch for those anyway and use SDSF SE on the SYSTSPRT
SYSOUT).
TSO Session Manager had some interesting features, but overall, the impact
on ISPF dialogs is somewhat painful. I thought the coolest was the side by
side display of TSO output streams (line mode). I was using it in the mid-80's
for a while and finally gave up. You had to alter the TSO LOGON PROC and
use a different initial PGM other than IKJEFT01. You get some new behaviors
that you have to code around (like coding many extra CONTROL DISPLAY REFRESH
commands) and not all application are written to be tolerant of Session
Manager. Today, with the approach Bob described and 3270 emulators under Windows
you can scroll forwards and backwards through your traces and run 2 emulator
sessions side by side to see 2 versions of code or traces or whatever.
Rob
In a message dated 8/26/2007 10:43:11 AM US Mountain Standard Time,
***@ATTGLOBAL.NET writes:
I don't pay much attention to the session manager at any site I'm on,
Michael -- mostly it's just another step to log on, since mostly on the
mainframe I live in TSO -- so I can't comment on that part of it. I have
seen IBM's session manager more recently than 25 years ago, but not (I
think) as recently as 3 years ago.
About following a trace interactively, though: I often do just what
associate does, turn on tracing and follow it in line mode. I have become
aware of the advantages of doing it in batch, though, and recently I
started doing the same thing in the foreground by using a routine many of
us have written.
My version is called DISP; others here use a different name, but they all
do essentially the same thing, ie use OUTTRAP to trap the output from a TSO
command and display it in a scrollable form. In my version instead of
saying, for example, TSO HELP XMIT, I say TSO DISP HELP XMIT, and voilà! I
get the Help file in a View session so I can do a FIND on the part of the
file I want but can't remember. I do the same thing for the ACF2 CLASMAP,
the RACF SETROPTS and pretty much anything else I take it into my head to
use it for. Recently it's becoming more clear to me that instead of
working my way through a long TRACE in line mode I can use it on my own
commands-in-development -- so instead of typing TSO X I just type TSO DISP
X and the trace comes out in View. That's assuming I know the TRACE is
going to come to an end, of course, but if in the middle of a long loop the
routine has been bombing with a complaint that a Boolean flag isn't 0 or 1
and I can't immediately see why not, I can use this to trace the problem,
jump to the bottom of the listing and work my way back up to get to the
source of the problem.
Not, it should be understood, that any of these problems are due to
mistakes of my own. No, someone must have changed the code while I wasn’t
looking.
I imagine you either have such a routine yourself already or can see how it
would be written, but just in case, here's the salient portion of my
version:
vx=sysvar('SYSWTERM') /* use the terminal width */
ddn=tempdd('DISP') /* get a temporary DD name */
'ALLOCATE DDN('ddn') NEW REUSE LRECL('vx')'
'EXECIO * DISKW 'ddn' (STEM OP. FINIS'
'ISPEXEC LMINIT DATAID(OP) DDNAME('ddn')'
'ISPEXEC VIEW DATAID('op')'
'FREE DDN('ddn')'
This displays the date in a temporary DS; that way I don't have to worry
about making up a DSN each time.
---
Bob Bridges, ***@attglobal.net, cell 336 382-7313
***@westfieldgrp.com, 330 791-6576
/* It is often stated that of all the theories proposed in this century,
the silliest is quantum theory. In fact, some say that the only thing that
quantum theory has going for it is that it is unquestionably correct.
-from "Hyperspace" by Michio Kaku */
-----Original Message-----
From: Michael Bradley
Sent: Monday, August 20, 2007 08:39
This note is cross-posted to IBM-MAIN & TSO-REXX
Does anyone find the TSO Session Manager of use when tracing execs executed
in ISPF? (Or anything else?)
I test almost all my code in TSOBATCH using trace, and I feel productive
doing this; I can scroll backwards and forwards. But I have an associate
who develops a lot of dialogs, and is always viewing the output in a
non-scrollable uni-directional manner. Session Manager has always appealed
to me as a solution for this kind of behavior, but I haven't seen it for
maybe 25 years. It used to be a chargeable product, but I don't know what
its status is today. I see mention of it in IBM pubs as considerations in
certain situations, or how to test for its availability, etc.
I'd be interested in learning of anyone using Session Manager in this way,
or any tips on viewing Trace output when the exec is inovked interactively.
************************************** Get a sneak peek of the all-new AOL at
http://discover.aol.com/memed/aolcom30tour
----------------------------------------------------------------------
For TSO-REXX subscribe / signoff / archive access instructions,
send email to ***@VM.MARIST.EDU with the message: INFO TSO-REXX