Re: Re: Mainframe Interactive Programming

I learned early on . . .

S/3 Model 10. I didn't compile from the card decks. The "OCL" copied the
contents of the card deck to a library source member, then compiled from
said source member.

If I dropped a deck (not often), I punched out a new one.


On Fri, Jun 8, 2018 at 9:47 AM, Winchester Terry <
terry.winchester@xxxxxxxxxxxxxxx> wrote:

LMAO...BTDT!

Always had the keypunch gals put a number in the card so
if anyone dropped the program deck, we could run it thru
the sorter to get it back in sequence again.


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Musselman, Paul
Sent: Friday, June 08, 2018 9:42 AM
To: Midrange Systems Technical Discussion
Subject: [EXTERNAL] 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_computerhistoryarchivesproject_1_univac-2D1050&d=DwIGaQ&c=
usKnhNfiA3SpEGkR2TubeV6I5jE5rze8vzZE7OpWXXY&r=
LD1savGZ6Gc4gIcG9yLPnyfe5Wy5IgPnRmF3qDwpJN4&m=
vDkxxFAohQpUGhsNutm8EK36UYh10--3AvB7eC_PmC8&s=rPTqZ4v4yBo88va0xEm_
Bi31eS6efhqWLvoBeRqQOzo&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_stories_Jenny-5FC.html&d=DwIGaQ&c=
usKnhNfiA3SpEGkR2TubeV6I5jE5rze8vzZE7OpWXXY&r=
LD1savGZ6Gc4gIcG9yLPnyfe5Wy5IgPnRmF3qDwpJN4&m=
ppXaucfJrjR0h3v28mpSOEwQXNnjwLScqZ6WCAvxmpc&s=ILqz0e-
e16cpnpuepifZhZnyQFeAluQmyKqXA3GeG6o&e=.

I am now officially old.


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

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.
midrange.com_mailman_listinfo_midrange-2Dl&d=DwIGaQ&c=
usKnhNfiA3SpEGkR2TubeV6I5jE5rze8vzZE7OpWXXY&r=
LD1savGZ6Gc4gIcG9yLPnyfe5Wy5IgPnRmF3qDwpJN4&m=L_
qdBkm9jG9E12KKVNtqtfVCobk2yOXcJgRHTq4U2hg&s=OLCD6Y-qcWgGpsxuwBo5o_
cr9pnNO5ZPAqOn9boc0J8&e=
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://urldefense.proofpoint.com/v2/url?u=https-3A__
archive.midrange.com_midrange-2Dl&d=DwIGaQ&c=
usKnhNfiA3SpEGkR2TubeV6I5jE5rze8vzZE7OpWXXY&r=
LD1savGZ6Gc4gIcG9yLPnyfe5Wy5IgPnRmF3qDwpJN4&m=L_
qdBkm9jG9E12KKVNtqtfVCobk2yOXcJgRHTq4U2hg&s=TqeKuyyzsaGGYtID-3bLH_
8cQnJ4vBITdADjbUwxcmo&e=.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://urldefense.proofpoint.com/v2/url?u=http-3A__amzn.to_
2dEadiD&d=DwIGaQ&c=usKnhNfiA3SpEGkR2TubeV6I5jE5rze8vzZE7OpWXXY&r=
LD1savGZ6Gc4gIcG9yLPnyfe5Wy5IgPnRmF3qDwpJN4&m=L_
qdBkm9jG9E12KKVNtqtfVCobk2yOXcJgRHTq4U2hg&s=ZtAEMut1QgrUJrU5EVxQHlzLclUXEv
s02cpyqkvXSF0&e=

----------------------------------------------------------------------
Confidentiality Notice: The preceding e-mail message (including any
attachments) contains information that may be confidential, protected by
applicable legal privileges, or constitute non-public information. It is
intended to be conveyed only to the designated recipient(s). If you are not
an intended recipient of this message, please notify the sender by replying
to this message and then delete it from your system. Use, dissemination,
distribution or reproduction of this message by unintended recipients is
not authorized and may be unlawful.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD