>From what little I understand, the TMP invoked via ADDRESS TSO is like the >"batch version" of TSO. The "batch version" of TSO cannot do terminal I/O. And >does not appear, to me, to implement things like "terminal interrupts" (aka >ATTN'ing out of a command). To do ISPF "interactive" work via an emulated 3270 >would require your program to implement and script a TN3270 session and do a >3270s scripted LOGON to TSO like an end user would do. This would also mean >"only one session". Because "interactive" TSO uses an ENQ on SYSIKJUA <userid> >to "single thread". I have a memory of an option from the TSO pre-prompt exit >to turn off this ENQ. But reviewing the current documentation, I don't see it. >So either my memory is bad (ECC checks are common), or IBM has removed that >option.
-- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * [email protected] * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM > -----Original Message----- > From: IBM Mainframe Discussion List > [mailto:[email protected]] On Behalf Of Paul Gilmartin > Sent: Thursday, February 16, 2012 6:55 PM > To: [email protected] > Subject: Re: Authorized functions > > On Thu, 16 Feb 2012 15:40:40 -0600, Chris Craddock wrote: > > >On Thu, Feb 16, 2012 at 3:33 PM, Scott Ford wrote: > >> > >> I dont want to knock IBM but for us developers this is UGLY ... > >> Maybe the problem is they never intended for it to be > called that way ... > > > >Yes, exactly right on both counts. Don't forget that TSO is > older than > >dirt and all subsequent efforts to graft on functionality > are limited by > >its original design assumptions. Modern it ain't. > > > Actually, I suspect the roots go deeper than that. The original > design assumptions of OS/360 never included the requirement to > support TSO; TSO was designed within the resulting constraints, > and so on ... > > John M's BPXWUNIX -> address TSO is the seed of a good idea. > If only each of several concurrent BPXWUNIces addressing TSO > could run ISPF attached to its own (emulated) 3270. Ah, for > something like the DIAL command in VM! > > -- gil > > ---------------------------------------------------------------------- > 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
