RE: Re: Mainframe Interactive Programming

How many of you youngsters still use QDKT as your default output queue?

:-)

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
Musselman, Paul
Sent: Friday, June 08, 2018 8:42 AM
To: Midrange Systems Technical Discussion
Subject: RE: Re: Mainframe Interactive Programming

It was a great day when the 3741 Key-To-Diskette (8") machines were rolled
in. No more worries about dropping an un-sequenced deck of about 800 cards
for the invoicing program!

Paul E Musselman
PaulMmn@xxxxxxxxxxxxx


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Winchester Terry
Sent: Friday, June 08, 2018 9:19 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: RE: Re: Mainframe Interactive Programming

Yep...sounds like you were "priviliged"...lol

Many of us were still punching our code onto cards back then!


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

Oh heck, Terry, we were high-tech!  I wish I still had a picture.  We
had an Apple II connecting the System/3 to a Series/1 so that we could
use state-of-the-art IBM 3101 terminals for source code entry.

Wow...40 years ago you had "tubes"? Some of us weren't so lucky...lol

https://urldefense.proofpoint.com/v2/url?u=https-3A__sites.google.com_site_c
omputerhistoryarchivesproject_1_univac-2D1050&d=DwIGaQ&c=usKnhNfiA3SpEGkR2Tu
beV6I5jE5rze8vzZE7OpWXXY&r=LD1savGZ6Gc4gIcG9yLPnyfe5Wy5IgPnRmF3qDwpJN4&m=vDk
xxFAohQpUGhsNutm8EK36UYh10--3AvB7eC_PmC8&s=rPTqZ4v4yBo88va0xEm_Bi31eS6efhqWL
voBeRqQOzo&e=

Terry


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Joe

Pluta

Sent: Friday, June 08, 2018 8:55 AM
To: midrange-l@xxxxxxxxxxxx
Subject: [EXTERNAL] 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:

https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ibmsystem3.nl_storie
s_Jenny-5FC.html&d=DwIGaQ&c=usKnhNfiA3SpEGkR2TubeV6I5jE5rze8vzZE7OpWXXY&r=LD
1savGZ6Gc4gIcG9yLPnyfe5Wy5IgPnRmF3qDwpJN4&m=ppXaucfJrjR0h3v28mpSOEwQXNnjwLSc
qZ6WCAvxmpc&s=ILqz0e-e16cpnpuepifZhZnyQFeAluQmyKqXA3GeG6o&e=.

I am now officially old.


----------------------------------------------------------------------