Back when there was such a thing as WSA, I ran TSO/ISPF in batch to give myself 
separate sessions and used a different profile PDS for each.

The advantage of SPLIT/SPLITV over multiple sessions is that the splits share 
data with each other. What I'd really like is a "son of WSA" using SCTP to 
communicate with multiple windows or tabs. Maybe also stealing some ideas from 
CMS and XEDIT while they're at it.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3

________________________________________
From: IBM Mainframe Discussion List [[email protected]] on behalf of 
Paul Gilmartin [[email protected]]
Sent: Tuesday, April 20, 2021 12:48 PM
To: [email protected]
Subject: Re: Is there a vertical split in ISPF?

Whom were you quoting with the ">>"?

On Tue, 20 Apr 2021 06:38:53 -0500, John McKown wrote:
>>
>> I remember, long, long ago at a shop far, far away; that I allowed a TSO
>> user to log on multiple times by using IKJEFLD1 to suppress the issuing of
>> the standard ENQ. I don't recall how I handled the ISPF profiles so that
>>
I've accomplished this by allocating the profiles to temp DSNs.  The macro
was for distribution and I wished to avoid dependencies on personal profiles.

>> there weren't any problems. I guess, today, I could use a PDSe. Anyway,
>> using this & multiple sessions is how I would have the equivalent of VSPLIT
>> today.
>>
ISPF is PDSE-ignorant.  LMPUT requires SYSDSN ENQ EXC, failing to trust PDSE
serialization and precluding some use of LM services in multiple jobs.

OTOH, within a job LMPUT's design precludes using SPFEDIT ENQ serialization,
with risk of data corruption.

Has vertical split any advantage over multiple emulator instances (in the
UNIX tradition) or a single emulator instance (in the Mac/Windows tradition)?

If ISPF were to support multiple windows in a single session (not in any
future I foresee) the benefit might be variable pool sharing.

-- 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

Reply via email to