The development environment is the IBM Dallas Innovation Center. My other 
console is a VM session. (That should be a bumper sticker.)

I wonder how that affects things. Anyone have a clue?

Charles


-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
Of Jesse 1 Robinson
Sent: Wednesday, June 26, 2019 4:21 PM
To: [email protected]
Subject: Re: WTO for message that will require explicit deletion?

Charles, if you're spear-heading this project, I suggest you wheedle your 
systems guys/gals into setting you up with SMCS. It's a native VTAM console 
application that comes as close to emulating a classic 3270 console as any 
software I've seen. There is no cost involved, but it requires some 
configuration. If your shop is already set up for it, they just need to add 
your userid to the mix. Simple editing. If starting from scratch, they need to 
do some prep work. 

Once you have it working, you will know--for better or worse--the effect of 
every little tweak and fiddle you perform. 

.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-543-6132 Office ⇐=== NEW
[email protected]

-----Original Message-----
From: IBM Mainframe Discussion List <[email protected]> On Behalf Of 
Charles Mills
Sent: Wednesday, June 26, 2019 4:07 PM
To: [email protected]
Subject: (External):Re: WTO for message that will require explicit deletion?

Okay, anyone have any clues as to how to align the stars?

My "console" experience is with SDSF LOG, not a real console, so my perception 
of where messages hang is a little skewed I guess.

Charles


-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
Of Jesse 1 Robinson
Sent: Wednesday, June 26, 2019 3:54 PM
To: [email protected]
Subject: Re: WTO for message that will require explicit deletion?

Non-rolling (no delete) messages do not hang 'at the bottom'. They hang as high 
as they can based on any other non-rolling messages that preceded them. A 
non-rolling message that stays toward the bottom is there only because a lot of 
other non-rolling messages are preventing it from rolling higher. 

Getting the attributes right for a non-rolling message can be tricky, including 
the status of the task that issued it. If the stars are aligned, a message can 
'stay on the screen' indefinitely as long as console mode is RD and the task 
that issued it is still active. 


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to