Compile error

[Ron Thomas]

Hello

We are trying to compile a very old cobol/db2 program and getting the below error . Could someone let me know how to get this fixed ?

00210 77 SQL-TEMP PIC X(128).
00211 77 DSN-TEMP PIC S9(9) COMP-4.
00212 77 DSN-TMP2 PIC S9(18) COMP-3.
00213 77 DSNNROWS PIC S9(9) COMP-4.
00214 77 DSNNTYPE PIC S9(4) COMP-4.
00215 77 DSNNLEN PIC S9(4) COMP-4.
00216 77 SQL-NULL PIC S9(9) COMP-4 VALUE +0.
00217 77 SQL-INIT-FLAG PIC S9(4) COMP-4 VALUE +0.
00218 88 SQL-INIT-DONE VALUE +1.
00219 77 SQL-FILE-READ PIC S9(9) COMP-4 VALUE +2.
00220 77 SQL-FILE-CREATE PIC S9(9) COMP-4 VALUE +8.
00221 77 SQL-FILE-OVERWRITE PIC S9(9) COMP-4 VALUE +16.
00222 77 SQL-FILE-APPEND PIC S9(9) COMP-4 VALUE +32.
00223 01 SQL-PLIST5.
00224 05 SQL-PLIST-CON PIC S9(9) COMP-4 VALUE +4195328.
00225 05 SQL-CALLTYPE PIC S9(4) COMP-4 VALUE +30.
00226 05 SQL-PROG-NAME PIC X(8) VALUE X'5453533530305020'.
00227 05 SQL-TIMESTAMP-1 PIC S9(9) COMP-4 VALUE +436568894.
00228 05 SQL-TIMESTAMP-2 PIC S9(9) COMP-4 VALUE +473023280.
00229 05 SQL-SECTION PIC S9(4) COMP-4 VALUE +1.
00230 05 SQL-CODEPTR PIC S9(9) COMP-4.
00231 05 SQL-VPARMPTR PIC S9(9) COMP-4 VALUE +0.
00232 05 SQL-APARMPTR PIC S9(9) COMP-4 VALUE +0.
00233 05 FILLER PIC S9(4) COMP-4 VALUE +1208.
00234 05 SQL-STMT-TYPE PIC S9(4) COMP-4 VALUE +231.
00235 05 SQL-STMT-NUM PIC S9(9) COMP-4 VALUE +239.
00236 05 SQL-PLIST-FLG PIC S9(4) COMP-4 VALUE +0.
00237 05 FILLER PIC X(18) VALUE
00238 X'000000000000000000000000000000000000'.
00239 05 SQL-AVAR-LIST5.
00240 10 PRE-SQLDAID PIC X(8) VALUE 'SQLDA '.
00241 10 PRE-SQLDABC PIC S9(9) COMP-4 VALUE +104.
00242 10 PRE-SQLN PIC S9(4) COMP-4 VALUE +2.
0243 10 PRE-SQLLD PIC S9(4) COMP-4 VALUE +2.
0244 10 PRE-SQLVAR.
0245 12 SQLVAR-BASE1.
0246 15 SQL-AVAR-TYPE1 PIC S9(4) COMP-4 VALUE +452.
0247 15 SQL-AVAR-LEN1 PIC S9(4) COMP-4 VALUE +8.
0248 15 SQL-AVAR-ADDRS1.
0249 20 SQL-AVAR-ADDR1 PIC S9(9) COMP-4.
0250 20 SQL-AVAR-IND1 PIC S9(9) COMP-4.
0251 15 SQL-AVAR-NAME1.
0252 20 SQL-AVAR-NAMEL1 PIC S9(4) COMP-4 VALUE +0.
0253 20 SQL-AVAR-NAMEC1 PIC X(30) VALUE ' '.
0254 12 SQLVAR-BASE2.
0255 15 SQL-AVAR-TYPE2 PIC S9(4) COMP-4 VALUE +500.
0256 15 SQL-AVAR-LEN2 PIC S9(4) COMP-4 VALUE +2.
0257 15 SQL-AVAR-ADDRS2.
0258 20 SQL-AVAR-ADDR2 PIC S9(9) COMP-4.
0259 20 SQL-AVAR-IND2 PIC S9(9) COMP-4.
00260 15 SQL-AVAR-NAME2.
00261 20 SQL-AVAR-NAMEL2 PIC S9(4) COMP-4 VALUE +0.
00262 20 SQL-AVAR-NAMEC2 PIC X(30) VALUE ' '.
00263 01 SQL-PLIST6.
00264 05 SQL-PLIST-CON PIC S9(9) COMP-4 VALUE +4195328.
00265 05 SQL-CALLTYPE PIC S9(4) COMP-4 VALUE +30.
8 TSS500P 10.15.24 JAN 19,1916
00266 05 SQL-PROG-NAME PIC X(8) VALUE X'5453533530305020'.
00267 05 SQL-TIMESTAMP-1 PIC S9(9) COMP-4 VALUE +436568894.
00268 05 SQL-TIMESTAMP-2 PIC S9(9) COMP-4 VALUE +473023280.
00269 05 SQL-SECTION PIC S9(4) COMP-4 VALUE +2.
00270 05 SQL-CODEPTR PIC S9(9) COMP-4.
00271 05 SQL-VPARMPTR PIC S9(9) COMP-4 VALUE +0.
00272 05 SQL-APARMPTR PIC S9(9) COMP-4 VALUE +0.
00273 05 FILLER PIC S9(4) COMP-4 VALUE +1208.
00274 05 SQL-STMT-TYPE PIC S9(4) COMP-4 VALUE +231.
00275 05 SQL-STMT-NUM PIC S9(9) COMP-4 VALUE +260.




226 IKF1007I-W X NOT PRECEDED BY A SPACE. ASSUME SPACE.
226 IKF1017I-E X INVALID IN VALUE CLAUSE. SKIPPING TO NEXT CLAUSE.
238 IKF1007I-W X NOT PRECEDED BY A SPACE. ASSUME SPACE.
238 IKF1017I-E X INVALID IN VALUE CLAUSE. SKIPPING TO NEXT CLAUSE.
266 IKF1007I-W X NOT PRECEDED BY A SPACE. ASSUME SPACE.
266 IKF1017I-E X INVALID IN VALUE CLAUSE. SKIPPING TO NEXT CLAUSE.
278 IKF1007I-W X NOT PRECEDED BY A SPACE. ASSUME SPACE.
278 IKF1017I-E X INVALID IN VALUE CLAUSE. SKIPPING TO NEXT CLAUSE.
297 IKF1007I-W X NOT PRECEDED BY A SPACE. ASSUME SPACE.
297 IKF1017I-E X INVALID IN VALUE CLAUSE. SKIPPING TO NEXT CLAUSE.
309 IKF1007I-W X NOT PRECEDED BY A SPACE. ASSUME SPACE.
309 IKF1017I-E X INVALID IN VALUE CLAUSE. SKIPPING TO NEXT CLAUSE.
328 IKF1007I-W X NOT PRECEDED BY A SPACE. ASSUME SPACE.
328 IKF1017I-E X INVALID IN VALUE CLAUSE. SKIPPING TO NEXT CLAUSE.
340 IKF1007I-W X NOT PRECEDED BY A SPACE. ASSUME SPACE.

Thanks
Ron T

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to list...@listserv.ua.edu with the message: INFO IBM-MAIN

[Lizette Koehler]

What platform are you running this on? This does not appear to be COBOL compiler on z/OS

An internet search on IKF1017I appears to be Hercules390 compiler? z/OS Cobol is IGY typically.

Lizette

[John McKown]

What compiler are you using? The code looks OK for a _modern_ COBOL
compiler. I.e. for Enterprise COBOL (IGYCRCTL), but not for the older
IKJCBL00 compiler. The older compiler did not have hex literals. eg: X'00'

--
Werner Heisenberg is driving down the autobahn. A police officer pulls
him over. The officer says, "Excuse me, sir, do you know how fast you
were going?"
"No," replies Dr. Heisenberg, "but I know where I am."

Computer Science is the only discipline in which we view adding a new wing
to a building as being maintenance -- Jim Horning

Schrodinger's backup: The condition of any backup is unknown until a
restore is attempted.

He's about as useful as a wax frying pan.

Maranatha! <><
John McKown

[Rugen, Len]

Quote vs. apost option?

Len Rugen

Metrics and Automation – umdoit...@missouri.edu

[Clark Morris]

On 19 Jan 2016 07:23:57 -0800, in bit.listserv.ibm-main Ron Thomas
wrote:

As others have pointed out the IKF messages are from an OS/VS compiler
(or another compiler set to the OS/VS mode). This compiler does not
recognize hexadecimal values. I'm surprised it isn't complaining
about the COMP-4 usages.

Clark Morris

[Pinnacle]

The IKF messages indicate a COBOL compiler circa 1980. Perhaps a
21st-century compiler would yield better results.

Regards,
Tom Conley

[Lizette Koehler]

It has been so long since I had a VS COBOL Manual, I did not recognize it.
So it seems what everyone is saying is

Fix would be to use a more current compiler.

Lizette

-----Original Message-----
>From: Pinnacle <pinn...@ROCHESTER.RR.COM>
>Sent: Jan 19, 2016 10:55 AM
>To: IBM-...@LISTSERV.UA.EDU
>Subject: Re: Compile error
>

[Jon Butler]

Let me also suggest you do not use the stand-alone external DB2 translator, but use the SQL compiler option. Then any errors will be included in-line and it will be easier to debug. Likewise the CICS compiler option vs the translator.

Also today, all the DB2 artifacts are GLOBAL such as the SQLCA, so you can use nested (internal) subroutines...although if the code is from VS/COBOL, I doubt there will be any.

[Charles Mills]

The OP says "COBOL/DB2 program." I would wonder about DB2 support for the older compilers.

Charles

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-...@LISTSERV.UA.EDU] On Behalf Of Lizette Koehler

[Ron Thomas]

I looked at the endevor processor group setting and it is showing the program that is used is PGM=IKFCBL00. is this won't work ? Thanks!

[John McKown]

Correct. That's a very old COBOL compiler. Today's compiler is IGYCRCTL.

--
Werner Heisenberg is driving down the autobahn. A police officer pulls
him over. The officer says, "Excuse me, sir, do you know how fast you
were going?"
"No," replies Dr. Heisenberg, "but I know where I am."

Computer Science is the only discipline in which we view adding a new wing
to a building as being maintenance -- Jim Horning

Schrodinger's backup: The condition of any backup is unknown until a
restore is attempted.

He's about as useful as a wax frying pan.

Maranatha! <><
John McKown

[Charles Mills]

All of the recent COBOLs starting I think with COBOL for OS/390 have had an entry point of IGYCRCTL.

IKFCBL00 is the entry point for VS COBOL I, often called CB1. The IBM program number is 5740-CB1. It is a pre-LE product.

Compilers between CB1 and OS/390 *might* have also used IKFCBL00. If someone *really* needs to know I know where I can look it up.

Charles

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-...@LISTSERV.UA.EDU] On Behalf Of Ron Thomas
Sent: Tuesday, January 19, 2016 10:58 AM
To: IBM-...@LISTSERV.UA.EDU
Subject: Re: Compile error

[Pinnacle]

IKFCBL00 is VS/COBOL. It is not Y2K compliant. IGYCRCTL is the current
compiler. Are you sure you're picking up the correct Endevor processor?
That compiler is at least 30 years old.

Regards,
Tom Conley

[Skip Robinson]

I had the same question. Like maybe the JCL containing the ancient compiler name was pulled from the same archive as the source. But others have pointed out that hex literals were not allowed in the OS/VS compiler, so this particular combination of source and JCL could never have worked.

.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
323-715-0595 Mobile
JO.Skip....@att.net
JO.Skip....@gmail.com

> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:IBM-...@LISTSERV.UA.EDU]

[Charles Mills]

"(c) International Business Machines Corporation 1974, 1976, 1981"

35 to 42 years old!

Charles

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-...@LISTSERV.UA.EDU] On Behalf Of Pinnacle
Sent: Tuesday, January 19, 2016 12:14 PM
To: IBM-...@LISTSERV.UA.EDU

[Dale R. Smith]

On Tue, 19 Jan 2016 12:33:44 -0800, Charles Mills <char...@MCN.ORG> wrote:

>"(c) International Business Machines Corporation 1974, 1976, 1981"
>
>35 to 42 years old!
>
>Charles

The last supported release of the OS/VS COBOL Compiler and Library was V1.2.4. It was withdrawn from marketing in June 1992 and withdrawn from support in June 1994, so not quite that old! EOS does not mean it doesn't still work and can create code that can still execute on a modern mainframe. (Of course the source must not contain anything that OS/VS COBOL doesn't support!) Not sure if it's still shipping as part of z/OS or if it was just left around on the OP's system. We still have OS/VS COBOL programs that are running on VM/CMS, (none on z/OS).

--
Dale R. Smith

[Charles Mills]

It does not ship with z/OS. It is withdrawn from marketing, my understanding of which is "you can't order it."

Charles

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-...@LISTSERV.UA.EDU] On Behalf Of Dale R. Smith
Sent: Tuesday, January 19, 2016 6:12 PM
To: IBM-...@LISTSERV.UA.EDU
Subject: Re: Compile error

On Tue, 19 Jan 2016 12:33:44 -0800, Charles Mills <char...@MCN.ORG> wrote:

>"(c) International Business Machines Corporation 1974, 1976, 1981"
>
>35 to 42 years old!
>
>Charles

The last supported release of the OS/VS COBOL Compiler and Library was V1.2.4. It was withdrawn from marketing in June 1992 and withdrawn from support in June 1994, so not quite that old! EOS does not mean it doesn't still work and can create code that can still execute on a modern mainframe. (Of course the source must not contain anything that OS/VS COBOL doesn't support!) Not sure if it's still shipping as part of z/OS or if it was just left around on the OP's system. We still have OS/VS COBOL programs that are running on VM/CMS, (none on z/OS).

[Ed Gould]

On Jan 19, 2016, at 8:11 PM, Dale R. Smith wrote:

> On Tue, 19 Jan 2016 12:33:44 -0800, Charles Mills
> <char...@MCN.ORG> wrote:
>
>> "(c) International Business Machines Corporation 1974, 1976, 1981"
>>
>> 35 to 42 years old!
>>
>> Charles
>
> The last supported release of the OS/VS COBOL Compiler and Library
> was V1.2.4. It was withdrawn from marketing in June 1992 and
> withdrawn from support in June 1994, so not quite that old! EOS
> does not mean it doesn't still work and can create code that can
> still execute on a modern mainframe. (Of course the source must
> not contain anything that OS/VS COBOL doesn't support!) Not sure
> if it's still shipping as part of z/OS or if it was just left
> around on the OP's system. We still have OS/VS COBOL programs that
> are running on VM/CMS, (none on z/OS).
>
> --
> Dale R. Smith

Dale:

In our environment we have production cobol code from the early 1980's

Ed

[R.S.]

W dniu 2016-01-20 o 03:11, Dale R. Smith pisze:

> On Tue, 19 Jan 2016 12:33:44 -0800, Charles Mills <char...@MCN.ORG> wrote:
>
>> "(c) International Business Machines Corporation 1974, 1976, 1981"
>>
>> 35 to 42 years old!
>>
>> Charles
> The last supported release of the OS/VS COBOL Compiler and Library was V1.2.4. It was withdrawn from marketing in June 1992 and withdrawn from support in June 1994, so not quite that old! EOS does not mean it doesn't still work and can create code that can still execute on a modern mainframe. (Of course the source must not contain anything that OS/VS COBOL doesn't support!) Not sure if it's still shipping as part of z/OS or if it was just left around on the OP's system. We still have OS/VS COBOL programs that are running on VM/CMS, (none on z/OS).

Well, it has been unable to be ordered for almost 24 years (and replaced
by some newer version even earlier).
24 years in IT. If it's not old, then what actually is old?

--
Radoslaw Skorupka
Lodz, Poland






--
Treść tej wiadomości może zawierać informacje prawnie chronione Banku przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może być jedynie jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli nie jesteś adresatem niniejszej wiadomości lub pracownikiem upoważnionym do jej przekazania adresatowi, informujemy, że jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne działanie o podobnym charakterze jest prawnie zabronione i może być karalne. Jeżeli otrzymałeś tę wiadomość omyłkowo, prosimy niezwłocznie zawiadomić nadawcę wysyłając odpowiedź oraz trwale usunąć tę wiadomość włączając w to wszelkie jej kopie wydrukowane lub zapisane na dysku.

This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorized to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive.

mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa, www.mBank.pl, e-mail: kon...@mBank.pl
Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, nr rejestru przedsiębiorców KRS 0000025237, NIP: 526-021-50-88. Według stanu na dzień 01.01.2016 r. kapitał zakładowy mBanku S.A. (w całości wpłacony) wynosi 168.955.696 złotych.

[Chris Bowen]

. . . "But others have pointed out that hex literals were not allowed in the OS/VS compiler, so this particular combination of source and JCL could never have worked. "

For clarity:

The problem code was almost certainly inserted by the DB2 pre-compiler. With a level of DB2 contemporary with the COBOL compiler it would have worked - different code would have been inserted.

The OP is using on old version of COBOL (accidentally or intentionally) with a more recent version of DB2 for the pre-compile. That process inserts code which more modern compilers can handle.

Chris Bowen

[Tony Harminc]

On 21 January 2016 at 12:31, Chris Bowen <chris...@macro4.com> wrote:
> For clarity:
> The problem code was almost certainly inserted by the DB2 pre-compiler. With a level of DB2 contemporary
> with the COBOL compiler it would have worked - different code would have been inserted.

The last copyright date on the compiler seems to be 1981. Did DB2
exist as a product in 1981? I was at a shop that used SQL/DS (on VM)
very early in the game, and that was1984, and I'm pretty sure DB2 came
out after SQL/DS. Was there ever a DB2 that was contemporary with this
COBOL compiler?

Tony H.

[Charles Mills]

"The name DB2, or IBM Database 2, was first given to the Database Management System or DBMS in 1983 when IBM released DB2 on its MVS mainframe platform." -- Wikipedia, citing an IBM manual as authority.

I think the question is irrelevant however. The program may *never* have been compiled (at least in anything resembling its current form) by 5740-CB1. The program may not have existed in 1981 or 1983. The OP simply latched onto some old JCL or Endevor control statements.

Also, DB2 "version one" may have come after 5740-CB1 -- nonetheless its inserted statements were probably compatible with then-existing COBOL.

Charles

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-...@LISTSERV.UA.EDU] On Behalf Of Tony Harminc
Sent: Thursday, January 21, 2016 3:10 PM
To: IBM-...@LISTSERV.UA.EDU
Subject: Re: Compile error

On 21 January 2016 at 12:31, Chris Bowen <chris...@macro4.com> wrote:
> For clarity:
> The problem code was almost certainly inserted by the DB2
> pre-compiler. With a level of DB2 contemporary with the COBOL compiler it would have worked - different code would have been inserted.

The last copyright date on the compiler seems to be 1981. Did DB2 exist as a product in 1981? I was at a shop that used SQL/DS (on VM) very early in the game, and that was1984, and I'm pretty sure DB2 came out after SQL/DS. Was there ever a DB2 that was contemporary with this COBOL compiler?

[Savor, Thomas , Alpharetta]

>"The name DB2, or IBM Database 2, was first given to the Database Management System or DBMS in 1983 when IBM >released DB2 on its MVS mainframe platform." -- Wikipedia, citing an IBM manual as authority.

All these years, I've have only known of DB2. The name seems to have stuck.

Was there ever a DB1 ??
Will there ever be a DB3 ??

Thanks,
Tom

[Anne & Lynn Wheeler]

Thomas...@FISERV.COM (Savor, Thomas , Alpharetta) writes:
> Management System or DBMS in 1983 when IBM >released DB2 on its MVS
> mainframe platform." -- Wikipedia, citing an IBM manual as authority.
>
> All these years, I've have only known of DB2. The name seems to have stuck.
>
> Was there ever a DB1 ??
> Will there ever be a DB3 ??

The original sql/relational implementation was at SJR (bldg. 28 on main
plant site, using modified vm/370 on 370/145), System/R. History/Reunion:
http://www.mcjones.org/System_R/
wiki
https://en.wikipedia.org/wiki/IBM_System_R
and another history
http://www.theregister.co.uk/2013/11/20/ibm_system_r_making_relational_really_real/
and
http://www.cs.ubc.ca/~rap/teaching/504/2010/readings/history-of-system-r.pdf

The official new DBMS project was EAGLE .... with the corporation
focused on EAGLE it was possible to get System/R out the door
as SQL/DS (under the radar).

When EAGLE imploded, there was a request about how fast would it take to
port System/R to MVS ... eventually released as DB2 (originally for
analytical & decision support *only*).

past posts mentioning System/R
http://www.garlic.com/~lynn/submain.html#systemr
also referenced here
http://www.mcjones.org/System_R/citations.html

The Birth of SQL
http://www.mcjones.org/System_R/SQL_Reunion_95/sqlr95-The.html

Some discussion of EAGLE and then DB2
http://www.mcjones.org/System_R/SQL_Reunion_95/sqlr95-DB2.html

I periodically reference this post about Jan1992 meeting in Ellison's
conference room
http://www.garlic.com/~lynn/95.html#13

one of the people in the meeting would tell how he was responsible for
the majority of the tech transfer into the Santa Teresa Lab (now silicon
valley lab) for DB2.

Jim Gray departs for Tandem palming off some number of things on me
... old email ref:
http://www.garlic.com/~lynn/2007.html#email801016

Eventually IBM Toronto starts RDBMS for IBM/PC ... implemented in C ..
which is made available on other platforms and is also called DB2
... even though it is totally different code base from the mainframe
implementation.

SQL/DS is also eventually renamed DB2
https://en.wikipedia.org/wiki/IBM_SQL/DS

--
virtualization experience starting Jan1968, online at home since Mar1970

[Skip Robinson]

The name 'DB2' seems to have followed the 1980s tradition of what I call
'name bloat', the practice of inflating a moniker in one way or another to
make a product look more mature or more elegant. The paragon in my mind was
dBASE II from Ashton-Tate. There never was a plain old dBASE. The roman
numeral was added from the get-go to make the product seem new and improved.
Moreover, there was never an 'Ashton'. That name was invented because, gosh
darn it, it sounded good hyphenated with Tate, a real person.

Before DB2 there was precedent for name bloat within IBM. There never was a
plain old 'JES'. The product emerged from the cocoon as JES2. There had been
a predecessor product called 'HASP', which may or may not have been an
acronym for Houston Automatic Spooling Priority, but the name 'J-E-S' was
born complete with suffix.

Meanwhile there did emerge a 'JES3', but it was not an evolutionary
descendant of JES2. Both products have coexisted, albeit uneasily, for
decades. We used to imagine a JES5 or JES6 (depending on one's arithmetic
proclivity) that would somehow combine the best features of both products,
but it's almost certainly DOA. Likewise, the prospects for a 'DB3' are as
dim as a distant star.

.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
323-715-0595 Mobile
JO.Skip....@att.net
JO.Skip....@gmail.com

> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:IBM-...@LISTSERV.UA.EDU]

> On Behalf Of Anne & Lynn Wheeler
> Sent: Thursday, January 21, 2016 10:53 PM
> To: IBM-...@LISTSERV.UA.EDU
> Subject: [Bulk] Re: Compile error
>

[Richard Pinion]

JES2 was a half ASP project, just a little play on words :)



--- JO.Skip....@ATT.NET wrote:

From: Skip Robinson <JO.Skip....@ATT.NET>
To: IBM-...@LISTSERV.UA.EDU
Subject: Re: Compile error

_____________________________________________________________
Netscape. Just the Net You Need.

[Staller, Allan]

<snip>
Meanwhile there did emerge a 'JES3', but it was not an evolutionary descendant of JES2. Both products have coexisted, albeit uneasily, for decades. We used to imagine a JES5 or JES6 (depending on one's arithmetic proclivity) that would somehow combine the best features of both products, but it's almost certainly DOA. ....
</snip>

Actually this seems to be happening. Witness the recent merging of JES3 and JES2 capabilities. 8 char job classes in JES2, JES2/JES3 using common SAPI. SDSF (formerly JES only) obtaining JES3 capabilities.
Dependent Job Control language in JES2 (2.2).

And I am sure there are others. It looks like IBM is attempting to create "THE JES" from the capabilities of JES2 and JES3.

Just my $0.02 USD worth...

This email – including attachments – may contain confidential information. If you are not the intended recipient, do not copy, distribute or act on it. Instead, notify the sender immediately and delete the message.

[Pommier, Rex]

Probably just an old fairy tale, but I was told long ago that DB2 came about as a name because IBM already had IMS so the 2 in DB2 was to distinguish it as being IBM's second DBMS offering.

Rex

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-...@LISTSERV.UA.EDU] On Behalf Of Skip Robinson
Sent: Friday, January 22, 2016 10:51 AM
To: IBM-...@LISTSERV.UA.EDU
Subject: Re: Compile error

The information contained in this message is confidential, protected from disclosure and may be legally privileged. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any disclosure, distribution, copying, or any action taken or action omitted in reliance on it, is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and destroy the material in its entirety, whether in electronic or hard copy format. Thank you.

[Skip Robinson]

As we saw in the recent thread on converting from JES3 to JES2, JES3 from
the beginning provided function--especially in the area of data device
control--that was never envisioned for JES2. I think that most of the recent
convergence of function in the two products mostly involves what we think of
as classic 'job control'. And the motivation for much of that convergence is
to 'elevate' function from JES to the BCP so that code has to be developed
only once. JES3's historic foray into disk and tape control, while useful
for shops that make use of it, has little to do with 'controlling jobs' in
the original sense.

.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
323-715-0595 Mobile
JO.Skip....@att.net
JO.Skip....@gmail.com

> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:IBM-...@LISTSERV.UA.EDU]

> On Behalf Of Staller, Allan
> Sent: Friday, January 22, 2016 09:02 AM
> To: IBM-...@LISTSERV.UA.EDU
> Subject: [Bulk] Re: Compile error
>

> <snip>

> Meanwhile there did emerge a 'JES3', but it was not an evolutionary
> descendant of JES2. Both products have coexisted, albeit uneasily, for
decades.
> We used to imagine a JES5 or JES6 (depending on one's arithmetic
proclivity)
> that would somehow combine the best features of both products, but it's

> almost certainly DOA. ....
> </snip>
>
> Actually this seems to be happening. Witness the recent merging of JES3
and
> JES2 capabilities. 8 char job classes in JES2, JES2/JES3 using common
SAPI.
> SDSF (formerly JES only) obtaining JES3 capabilities.
> Dependent Job Control language in JES2 (2.2).
>
> And I am sure there are others. It looks like IBM is attempting to create
"THE
> JES" from the capabilities of JES2 and JES3.

[Gibney, David Allen,Jr]

I've never worked with JES3. What does it offer in "disk and tape control" that DFSMS doesn't? Or, are we talking a different kind of control?

> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:IBM-...@LISTSERV.UA.EDU]

> On Behalf Of Skip Robinson
> Sent: Friday, January 22, 2016 9:45 AM
> To: IBM-...@LISTSERV.UA.EDU
> Subject: Re: Compile error
>

[Skip Robinson]

It's Friday, right? After the release of Mel Brooks' History of the World
Part I, he was often asked when we could expect to see Part II. He claimed
never to have intended a Part II. Then why call it Part I? Because that
qualifier is almost never used. The first one is called Name; the next one
is Name II or Name Part 2. If you think about our biz, we do the same thing.
We name all sorts of elements and components such that the first one gets a
vanilla name; the next one--usually not contemplated in the original
design--gets various kinds of qualifications. The idea of naming the very
first one with a 'two' is fallout from modern marketing obfuscation, where
ordinary logic is irrelevant or downright inimical.

.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
323-715-0595 Mobile
JO.Skip....@att.net
JO.Skip....@gmail.com


> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:IBM-...@LISTSERV.UA.EDU]
> On Behalf Of Pommier, Rex
> Sent: Friday, January 22, 2016 09:05 AM
> To: IBM-...@LISTSERV.UA.EDU
> Subject: [Bulk] Re: Compile error
>

> Probably just an old fairy tale, but I was told long ago that DB2 came
about as a
> name because IBM already had IMS so the 2 in DB2 was to distinguish it as
> being IBM's second DBMS offering.
>
> Rex
>

> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:IBM-...@LISTSERV.UA.EDU]
> On Behalf Of Skip Robinson
> Sent: Friday, January 22, 2016 10:51 AM
> To: IBM-...@LISTSERV.UA.EDU
> Subject: Re: Compile error
>

> The name 'DB2' seems to have followed the 1980s tradition of what I call
'name
> bloat', the practice of inflating a moniker in one way or another to make
a
> product look more mature or more elegant. The paragon in my mind was
> dBASE II from Ashton-Tate. There never was a plain old dBASE. The roman
> numeral was added from the get-go to make the product seem new and
> improved.
> Moreover, there was never an 'Ashton'. That name was invented because,
gosh
> darn it, it sounded good hyphenated with Tate, a real person.
>
> Before DB2 there was precedent for name bloat within IBM. There never was
a
> plain old 'JES'. The product emerged from the cocoon as JES2. There had
been a
> predecessor product called 'HASP', which may or may not have been an
> acronym for Houston Automatic Spooling Priority, but the name 'J-E-S' was
> born complete with suffix.
>

> Meanwhile there did emerge a 'JES3', but it was not an evolutionary
> descendant of JES2. Both products have coexisted, albeit uneasily, for
decades.
> We used to imagine a JES5 or JES6 (depending on one's arithmetic
> proclivity) that would somehow combine the best features of both products,

> but it's almost certainly DOA. Likewise, the prospects for a 'DB3' are as
dim as a
> distant star.

[Anne & Lynn Wheeler]

JO.Skip....@ATT.NET (Skip Robinson) writes:
> The name 'DB2' seems to have followed the 1980s tradition of what I call
> 'name bloat', the practice of inflating a moniker in one way or another to
> make a product look more mature or more elegant. The paragon in my mind was
> dBASE II from Ashton-Tate. There never was a plain old dBASE. The roman
> numeral was added from the get-go to make the product seem new and improved.
> Moreover, there was never an 'Ashton'. That name was invented because, gosh
> darn it, it sounded good hyphenated with Tate, a real person.
>
> Before DB2 there was precedent for name bloat within IBM. There never was a
> plain old 'JES'. The product emerged from the cocoon as JES2. There had been
> a predecessor product called 'HASP', which may or may not have been an
> acronym for Houston Automatic Spooling Priority, but the name 'J-E-S' was
> born complete with suffix.
>
> Meanwhile there did emerge a 'JES3', but it was not an evolutionary
> descendant of JES2. Both products have coexisted, albeit uneasily, for
> decades. We used to imagine a JES5 or JES6 (depending on one's arithmetic
> proclivity) that would somehow combine the best features of both products,
> but it's almost certainly DOA. Likewise, the prospects for a 'DB3' are as
> dim as a distant star.

note that VS1 had JES1 (Job Entry Subsystem 1)
https://en.wikipedia.org/wiki/OS/VS1

The official names were OS/VS1 and OS/VS2 ... so JES2 originally may
have originally been to designate it was for OS/VS2.

Long ago and far away, my wife was in the GBURG JES group and was part
of the catchers for ASP turning into JES3. She was then co-author of
JESUS (JES UNIFIED SYSTEM) document ... which merged the features in
JES2 and JES3 that respective customers couldn't live w/o ... for
various reasons never saw the light of day.

A Fascinating History of JES2
http://www.share.org/p/bl/et/blogid=9&blogaid=238

For the truth we must go back to the mid 1960's. IBM's OS/360 was in
trouble. The spooling (wonder where that name came from) support was
slow and the overhead was high. Many programming groups independently
attacked the problem. ASP, loosely based upon the tightly coupled IBM
7090/7094 DCS, held the lead in the OS/360 spooling sweepstakes. ASP's
need for at least two CPU's fit well with IBM Marketing's plans for the
System/360. Meanwhile, a group of IBM SE's, located in Houston,
developed a different product of which they were justifiably proud.
They wanted to popularize it, as they correctly suspected it would be
the balm for OS/360 users, increasing the usability and popularity of
the operating system, and, not incidentally, furthering their careers.
All they needed was the right name! A name which was easy to remember,
a name which would draw attention to their product, and a name to
distract from the ASP publicity. That name was Half-ASP, or HASP.
Naturally, if HASP and ASP were products of two different companies, the
FTC would have stepped in to stop such a predatory product name.
Regulatory action was prevented, however, because IBM is "one big happy
family", believed by many to be larger than the Government.

... snip ...

of course officially, the "H" stands for "Houston"
https://en.wikipedia.org/wiki/Houston_Automatic_Spooling_Priority

then my wife was con'ed into going to POK to be responsible for
loosely-coupled architecture ... where she "peer-coupled shared data
architecture" ... which saw very little uptake (except for IMS
hot-standby) until SYSPLEX & Parallel SYSPLEX ... contributing to her
not remaining long in POK (along with the ongoing periodic battles with
the communication group trying to force her into using SNA/VTAM for
loosely-coupled operation). some past posts
http://www.garlic.com/~lynn/submain.html#shareddata

as undergraduate in the 60s, I got to make a lot of HASP modifications
(I had also been hired fulltime by the university to be responsible for
production mainframe systems) ... including implementing terminal
support and conversational editor in HASP for a form of CRJE.
https://en.wikipedia.org/wiki/Remote_job_entry

DB2 may have been because some had hopes that the official new DBMS
"EAGLE" might still be able to rise from its ashes ... or it was to
designate the OS/VS2 (aka MVS) version of System/R as opposed to the
earlier SQL/DS version of System/R (that ran on VM370, VS1, DOS/VSE).

trivia: one of the problems with the System/R tech transfer to Endicott
for SQL/DS ... was that several enhancements to vm370 had been made to
make System/R much more efficient. For various reasons, the Endicott
people didn't want to make SQL/DS release dependent on getting
enhancements into VM370 ... and so that had to be dropped.

[Anne & Lynn Wheeler]

other trivia from ibm jargon:

MVM - n. Multiple Virtual Memory. The original name for MVS (q.v.),
which fell foul of the fashion of changing memory to storage.

MVS - n. Multiple Virtual Storage, an alternate name for OS/VS2
(Release 2), and hence a direct descendent of OS. OS/VS2 (Release 1)
was in fact the last release of OS MVT, to which paging had been
added; it was known by some as SVS (Single Virtual Storage). MVS is
one of the big two operating systems for System/370 computers (the
other being VM (q.v.)). n. Man Versus System.

... snip ...

as part of the "Man Versus System" theme ... it had become significantly
much easier to work out lots of computer concepts and design on
vm370/cms ... and then later port the implementation to MVS ... than
trying to start on an MVS base.

some time ago, I got a request about the history of adding virtual
memory to all 370s ... old post with exchange from IBMer involved (who
recently passed) with references of os/v2, future systems, hasp/asp,
etc
http://www.garlic.com/~lynn/2011d.html#73

other parts of the thread
http://www.garlic.com/~lynn/2011d.html#71
http://www.garlic.com/~lynn/2011d.html#72
http://www.garlic.com/~lynn/2011d.html#74

[Rugen, Len]

I ran OS/VS1 on a 4341 and later I think on a 4381. We also ran VM, OS/VS1 had a VM "Assist" mode where it didn't page, but let VM page for it. I think OS/VS1 ran JES, just JES, no 2 or 3 after it, but it looked a lot like JES2.

[Rick Troth]

On 01/22/2016 01:40 PM, Anne & Lynn Wheeler wrote:
> other trivia from ibm jargon:
>
> MVM - n. Multiple Virtual Memory. The original name for MVS (q.v.),
> which fell foul of the fashion of changing memory to storage.
>
> MVS - n. Multiple Virtual Storage, an alternate name for OS/VS2
> (Release 2), and hence a direct descendent of OS. OS/VS2 (Release 1)
> was in fact the last release of OS MVT, to which paging had been
> added; it was known by some as SVS (Single Virtual Storage). MVS is
> one of the big two operating systems for System/370 computers (the
> other being VM (q.v.)). n. Man Versus System.

Helpful, because I am preparing yet another MF intro,
where the acronyms seem to be what confuse non-mainframers more than
anything else.

Where do you place VSE? (since it's not one of "the big two")

Lineage of TPF would also be interesting.

> as part of the "Man Versus System" theme ... it had become significantly
> much easier to work out lots of computer concepts and design on
> vm370/cms ... and then later port the implementation to MVS ... than
> trying to start on an MVS base.
>
> some time ago, I got a request about the history of adding virtual
> memory to all 370s ... old post with exchange from IBMer involved (who
> recently passed) with references of os/v2, future systems, hasp/asp,
> etc
> http://www.garlic.com/~lynn/2011d.html#73
>
> other parts of the thread
> http://www.garlic.com/~lynn/2011d.html#71
> http://www.garlic.com/~lynn/2011d.html#72
> http://www.garlic.com/~lynn/2011d.html#74

Got into some discussion with Alan Altmark about VOL1 on IBMVM.
Track-and-record formatting is common with MVS, though VSE and VM (both
CP and CMS) have less need of it. (Well ... until SSI in the VM world
got an artificial dependency.)
Linux doesn't care, and actually works better (for a Linux/Unix person)
when storage is just blocks.
(Track and record boundaries are discarded.)

So things like DASD labeling are software artifacts that give the
illusion of being hardware feature, adding yet more kon-foo-zhun to the
newcomers.

-- R; <><

[John McKown]

On Fri, Jan 22, 2016 at 1:12 PM, Rick Troth <tro...@gmail.com> wrote:

> Helpful, because I am preparing yet another MF intro,
> where the acronyms seem to be what confuse non-mainframers more than
> anything else.
>
> Where do you place VSE? (since it's not one of "the big two")
>

​Descended from DOS.​
https://en.wikipedia.org/wiki/DOS/360_and_successors

>
> Lineage of TPF would also be interesting.
>

​Descended from ACP (Airline Control Program).
https://en.wikipedia.org/wiki/IBM_Airline_Control_Program​

I worked at Braniff Airways before it went under. The reservation system
ran ACP on a 2 Meg 3033. The thing would IPL in about 5 seconds. The ACP
systems people were a bit strange. They had the source and modified it. I
remember the CE complaining that the ACP attached tapes (3420s) would just
die with "no warnings at all" whereas the MVT (yes MVT on a 3033) and, a
bit later MVS and VM would show temp errors. The ACP people then told the
CE that they had removed all logging of temporary errors to speed up
processing. Not just on the tapes, but on the 3344 disks as well. IIRC, the
3344s on ACP actually used "software duplexing" for reliability.

--
Werner Heisenberg is driving down the autobahn. A police officer pulls
him over. The officer says, "Excuse me, sir, do you know how fast you
were going?"
"No," replies Dr. Heisenberg, "but I know where I am."

Computer Science is the only discipline in which we view adding a new wing
to a building as being maintenance -- Jim Horning

Schrodinger's backup: The condition of any backup is unknown until a
restore is attempted.

He's about as useful as a wax frying pan.

Maranatha! <><
John McKown

[Anne & Lynn Wheeler]

john.arch...@GMAIL.COM (John McKown) writes:
> ​Descended from ACP (Airline Control Program).
> https://en.wikipedia.org/wiki/IBM_Airline_Control_Program​
>
> I worked at Braniff Airways before it went under. The reservation system
> ran ACP on a 2 Meg 3033. The thing would IPL in about 5 seconds. The ACP
> systems people were a bit strange. They had the source and modified it. I
> remember the CE complaining that the ACP attached tapes (3420s) would just
> die with "no warnings at all" whereas the MVT (yes MVT on a 3033) and, a
> bit later MVS and VM would show temp errors. The ACP people then told the
> CE that they had removed all logging of temporary errors to speed up
> processing. Not just on the tapes, but on the 3344 disks as well. IIRC, the
> 3344s on ACP actually used "software duplexing" for reliability.

there was big problem with 3081 ... which originally was going to be
multiprocessor only ... and ACP/TPF didn't have multiprocessor support
(they were afraid that the whole market would move to clone processors
which were building newer single processor machines). An an interim they
shipped some number of releases of VM370 with very unnatural things done
to it specifically for running ACP/TPF on multiprocessors (but degraded
performance for all other customers). Eventually they shipped 3083 ...
which was a 3081 box with one of the processors removed (minor trivia,
simplest would be to remove the 2nd processor which was in the middle of
the box ... but that would have made the box dangerously top-heavy, they
had to rewrire "processor 0" to processor in the middle and remove the
processor at the top of the box). other issues with 308x
... highlighting that it was warmed over FS technology
http://www.jfsowa.com/computer/memo125.htm

later in the 80s, my wife did temporary stint as chief architect for
Amedeus (euro res system based on old eastern "system one") ... the
communication group got her replaced because she backed x.25 (instead of
sna/vtam) ... it didn't do them much good because amedeus went with x.25
anyway.

later in the mid-90s, we were asked to look at re-engineering some of
the largest airline res system in the world ... starting with ROUTES
(about 25% of total mainframe processing load) addressing the ten
impossible things that they couldn't do. I went away and two months
later came back with totally different ROUTES implementation that ran
about hundred times faster and did all ten impossible things
... including ten RS/6000 990s being able to handle every ROUTES
transaction for every airline in the world. The issue was much of
ACP/TPF implementation was dictated by technology trade-offs made in the
60s ... it was possible to start from scratch 30yrs later and make
totally different trade-offs (and a decade later, cellphone processors
had processing capacity of those ten 990s).

It was fun because they provided me with tape of the full OAG ...
including record for every scheduled airline flt in the world.

--
virtualization experience starting Jan1968, online at home since Mar1970

[Mike Schwab]

On Fri, Jan 22, 2016 at 11:54 AM, Gibney, David Allen,Jr <gib...@wsu.edu> wrote:
> I've never worked with JES3. What does it offer in "disk and tape control" that DFSMS doesn't? Or, are we talking a different kind of control?

It doesn't start until the dataset names / tape volumes are not in use
and there is sufficient free space on disk. JES2 would start the job
then wait for them to be available. Or the job could abend for lack
of space.

--
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?

[Gibney, David Allen,Jr]

> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:IBM-...@LISTSERV.UA.EDU]
> On Behalf Of Mike Schwab
> Sent: Friday, January 22, 2016 12:32 PM
> To: IBM-...@LISTSERV.UA.EDU
> Subject: Re: Compile error
>

> On Fri, Jan 22, 2016 at 11:54 AM, Gibney, David Allen,Jr <gib...@wsu.edu>
> wrote:
> > I've never worked with JES3. What does it offer in "disk and tape control"
> that DFSMS doesn't? Or, are we talking a different kind of control?
>
> It doesn't start until the dataset names / tape volumes are not in use and
> there is sufficient free space on disk. JES2 would start the job then wait for
> them to be available. Or the job could abend for lack of space.
>

So, still scheduling, not really DASD or TAPE management.

[Phil Smith III]

John McKown wrote, re TPF:

>I worked at Braniff Airways before it went under. The reservation system

>ran ACP on a 2 Meg 3033. The thing would IPL in about 5 seconds. The ACP

>systems people were a bit strange. They had the source and modified it. I

>remember the CE complaining that the ACP attached tapes (3420s) would just

>die with "no warnings at all" whereas the MVT (yes MVT on a 3033) and, a

>bit later MVS and VM would show temp errors. The ACP people then told the

>CE that they had removed all logging of temporary errors to speed up

>processing. Not just on the tapes, but on the 3344 disks as well. IIRC, the

>3344s on ACP actually used "software duplexing" for reliability.

My favorite TPF story, from Sabre, circa 1988:

Someone started a TPF transaction without proper testing, and it clipped
something like 1,000 packs. MVS and TPF were quite unhappy about it.



While the MVS and TPF guys were moaning, Mike Roegner (now retired) quietly
went over to the VM system and wrote a small Rexx program to attach, ICKDSF
(or whatever the equivalent was-this would have been pre-XA, and I forget!),
and detach, and started relabeling the packs.



Meanwhile, they were down for several hours, at a reported cost of
$20,000/minute. And of course neither Mike nor VM got the credit they
deserved for saving the day. The outage did make ComputerWorld, however. (Of
course it did-would ComputerWorld ever forego the opportunity to run a
negative story?)



.phsiii

[Robert A. Rosenberg]

At 08:50 -0800 on 01/22/2016, Skip Robinson wrote about Re: Compile error:

>There never was a plain old 'JES'.

I thought the spooling subsystem in OS/VS1 was called JES.

[Robert A. Rosenberg]

JES3 does device allocation before the job is allowed to run. For
tape drives it grabs the needed number of drives so you do not run
into "Waiting for a Drive" issues. It did the same back in the
mountable DASD days. I think it also tracks Tape Volumes so you do
not run into "I need Volume X" but another job is current using it
issues. IOW: It insures that once a job is allowed to start, there
will be no delays to gain access to the devices and files it needs.

At 17:54 +0000 on 01/22/2016, Gibney, David Allen,Jr wrote about Re:
Compile error:

[Robert A. Rosenberg]

And then there was Star Wars (AKA: A New Hope [which was added when
the film was rereleased as part of the release of The Empire Strikes
Back]) which opened with a crawl saying Episode 4". That was just
because they were emulating the old serials where each segment was a
numbered Chapter with its own title (which often reflected the
cliffhanger being resolved or the plot point of that chapter).

[Ed Finnell]

Not nearly as unhappy as the Ops Mgr that found out they had replied "u"
all 1000 times.


In a message dated 1/22/2016 3:51:48 P.M. Central Standard Time,

li...@AKPHS.COM writes:

MVS and TPF were quite unhappy about it.

[Frank Swarbrick]

In the opening crawl for the original release of Star Wars not only did not say "A New Hope", it also did not say Episode IV.

See it here:
https://www.youtube.com/watch?v=UKRIUiyF0N4

Frank

> Date: Fri, 22 Jan 2016 16:52:01 -0500
> From: hal...@PANIX.COM
> Subject: Re: Compile error
> To: IBM-...@LISTSERV.UA.EDU

[Larry Chenevert]

From: Robert A. Rosenberg

>There never was a plain old 'JES'.

"I thought the spooling subsystem in OS/VS1 was called JES."

You are correct: JES

Did that (VS1/JES) through a lot of of the '70's.
Then VS1 under VM, then SVS, then DOS, VS1, and MVS under VM (different
place), then finally MVS.

[Larry Chenevert]

At 08:50 -0800 on 01/22/2016, Skip Robinson wrote about Re: Compile error:

>There never was a plain old 'JES'.

"I thought the spooling subsystem in OS/VS1 was called JES."

You are correct: JES (for VS1).

Through most of the '70's did VS1, VS1 under VM/370, SVS,
then at a different place, DOS/VSE and VS1 and MVS 3.8J under VM/370, and
finally MVS with other combinations to get to Man Versus Machine.

[Anne & Lynn Wheeler]

hal...@PANIX.COM (Robert A. Rosenberg) writes:
> And then there was Star Wars (AKA: A New Hope [which was added when
> the film was rereleased as part of the release of The Empire Strikes
> Back]) which opened with a crawl saying Episode 4". That was just
> because they were emulating the old serials where each segment was a
> numbered Chapter with its own title (which often reflected the
> cliffhanger being resolved or the plot point of that chapter).

co-worker at IBM would talk about Lucas attending San Jose Astronomy
club meetings and bringing draft outlines for all 8 episodes (for
members to review) More recent interviews with Lucas says that the first
episode he chose to do, was the one most likely for getting funding.

--
virtualization experience starting Jan1968, online at home since Mar1970

[Scott Ford]

Guys,

Great articles, I learned BAL on a BPS360/20...

Brings back a lot of memories..

Scott

On Friday, January 22, 2016, Ed Finnell <

0000000248cce9f...@listserv.ua.edu> wrote:

> Not nearly as unhappy as the Ops Mgr that found out they had replied "u"
> all 1000 times.
>
>
> In a message dated 1/22/2016 3:51:48 P.M. Central Standard Time,

> li...@AKPHS.COM <javascript:;> writes:
>
> MVS and TPF were quite unhappy about it.
>
>
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,

> send email to list...@listserv.ua.edu <javascript:;> with the message: