RE: Mainframe Interactive Programming

["Paul Nelson" <nelsonp@xxxxxxxxxxxxx>]

Waffles? We used to keep pizza warm on top of ours.

Paul Nelson
Cell 708-670-6978
Office 409-267-4027
nelsonp@xxxxxxxxxxxxx


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Joe
Pluta
Sent: Friday, June 08, 2018 7:55 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Mainframe Interactive Programming

On 6/7/2018 2:52 PM, dlclark@xxxxxxxxxxxxxxxx wrote:
>          So, for psuedo-conversational programming (as it's called), you
> simply keep all the important stuff in your own communication area (which
> is in-memory) and this maintains state.  Of course, you can also keep
> (hidden) things on the screen (as you can on the IBM i) but in the 3270
> world this takes up screen real estate.  So, not recommended.  But, you
> can keep all screen-type information in a temp storage queue so that it is
> available across screen interactions, too.
>
>   

I just had a serious 40-year flashback to NEP-MRT programming on the 
System/3 model 15D.  Get a session ID from the screen and use that to 
restore all your session variables.

Here's a picture of one: http://www.ibmsystem3.nl/stories/Jenny_C.html. ; 
I am now officially old.