Re: SEASIK 1.0 released

Eric: On Mon, May 24, 2010 at 6:06 PM, Paul Edwards wrote: > I have just released SEASIK 1.0, which is (effectively) > a DFDSS dump of a whole lot of C products, namely: > > GCC 3.2.3 MVS 8.0 > PDPCLIB 3.00 > BISON 1.35 MVS 4.0 > BREXX 2.1.8 MVS 1.0 > BWBASIC 2.50 MVS 1.0 > DIFFUTIL 2.8.1 MVS 4.

Re: SEASIK 1.0 released

What is SEASIK? I don't think anyone ever said what it is, and if it is 1.0, it must be a new product. Please enlighten me. Eric Bielefeld Sr. Systems Programmer IBM Global Services Division Dubuque, Iowa 414-477-7259 -- Fo

Re: SEASIK 1.0 released

On Wed, 9 Jun 2010 10:48:18 -0400, Gerhard Postpischil wrote: >On 6/9/2010 5:17 AM, Paul Edwards wrote: >> Don't look at me. IBM are the ones who created ftp >> with the RDW option, and I'm not the only user of that. > >You missed one crucial step - you zip the AWS file, and then ftp >that. No

Re: SEASIK 1.0 released

In , on 06/09/2010 at 04:17 AM, Paul Edwards said: >I was programming in MVS while you >were still knee-high to a grasshopper. ITYM knee high to a 704. Gerhard was programming well before there was an MVS, or even a S/360. Don't try to play the seniority card in IBM-MAIN; there's always someo

Re: SEASIK 1.0 released

In , on 06/05/2010 at 10:41 AM, Paul Edwards said: >Are you talking about the parameter processing? Yes. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see We don't care. We don't have to care, we're Congress. (S877: Th

Re: FTP RDW (was: SEASIK 1.0 released)

Shmuel Metz (Seymour J.) wrote: In <4c0fbbd1.6090...@trainersfriend.com>, on 06/09/2010 at 10:05 AM, Steve Comstock said: Perhaps I should add a new prefix type: RDW, which would be 2-byte binary integer length followed by 2-byte binary zeros, with data starting at the fourth byte. What a

Re: FTP RDW (was: SEASIK 1.0 released)

In <4c0fbbd1.6090...@trainersfriend.com>, on 06/09/2010 at 10:05 AM, Steve Comstock said: >Perhaps I should add a new prefix type: RDW, which would be 2-byte >binary integer length followed by 2-byte binary zeros, with data >starting at the fourth byte. What about RECFM=VBS, where the second

Re: FTP RDW (was: SEASIK 1.0 released)

Paul Gilmartin wrote: On Wed, 9 Jun 2010 04:17:02 -0500, Paul Edwards wrote: Don't look at me. IBM are the ones who created ftp with the RDW option, and I'm not the only user of that. And the special utility is only required because IBM (again) neglected to provide a facility to reverse that. T

Re: SEASIK 1.0 released

On 6/9/2010 9:47 AM, J R wrote: I'm a dinosaur and I'm pretty sure I remember 7294 bytes fitting on a 2314. Where did 6233 come from? It's (sub)optimal for every disk from 2314 to 3390/9345 on Also it's the (approximate) size IBM used for its own distributions, way back when. Gerhard Pos

Re: SEASIK 1.0 released

On 6/9/2010 5:17 AM, Paul Edwards wrote: Don't look at me. IBM are the ones who created ftp with the RDW option, and I'm not the only user of that. You missed one crucial step - you zip the AWS file, and then ftp that. No worry about record format or boundaries, and a "universal" unzip is ava

Re: SEASIK 1.0 released

OK. I've had my coffee now and I understand the relevance of 6233! > Date: Wed, 9 Jun 2010 09:47:10 -0400 > From: jayare...@hotmail.com > Subject: Re: SEASIK 1.0 released > To: IBM-MAIN@bama.ua.edu > > > dinosaurs still use 3350s. And I'm no dinosaur, even

Re: SEASIK 1.0 released

e: Wed, 9 Jun 2010 04:17:02 -0500 > From: mutazi...@gmail.com > Subject: Re: SEASIK 1.0 released > To: IBM-MAIN@bama.ua.edu > > On Mon, 7 Jun 2010 03:11:20 -0400, Gerhard Postpischil > wrote: > > >There's good news and bad news > > > >I've be

FTP RDW (was: SEASIK 1.0 released)

On Wed, 9 Jun 2010 04:17:02 -0500, Paul Edwards wrote: > >Don't look at me. IBM are the ones who created ftp >with the RDW option, and I'm not the only user of that. > >And the special utility is only required because IBM (again) >neglected to provide a facility to reverse that. They will >presumab

Re: SEASIK 1.0 released

On Mon, 7 Jun 2010 03:11:20 -0400, Gerhard Postpischil wrote: >There's good news and bad news > >I've been trying to restore SEASIK since Friday, with no luck. > >1) There is a design error in DSSREST. When I added the RDW >code, I wrote the code so it only works when the block size is >equal t

Re: SEASIK 1.0 released

I uploaded a new version of DSSREST as part of the DSSDMP tape. It's still in 3350 format (I'll change it to 3390 when you change .SOURCE files to FB/80 ). It restored the SEASIK files without a hitch, using slightly less memory and time. Gerhard Postpischil Bradford, VT -

Re: SEASIK 1.0 released

There's good news and bad news I've been trying to restore SEASIK since Friday, with no luck. 1) There is a design error in DSSREST. When I added the RDW code, I wrote the code so it only works when the block size is equal to the sum of the lengths of all RDWs (+4 if there is a BDW). When I

Re: SEASIK 1.0 released

On Mon, 31 May 2010 18:07:08 -0400, Shmuel Metz (Seymour J.) wrote: >In , on 05/24/2010 > at 05:06 PM, Paul Edwards said: > >>Also GETLINE/PUTLINE are used in a TSO environment, >>so all programs automatically become command processors. > >I takes more than that to make them command processor

Re: SEASIK 1.0 released

In , on 05/25/2010 at 11:13 AM, Paul Edwards said: >No Charles, Gerhard is MVS through and through. Nonsense; he's a veteran of the one true mainstream[1] IBM[2] computer, the 7094. [1] If you count limited run then it's the 7030. ]2] I once had lust in my heart for a CDC 3600. -- S

Re: SEASIK 1.0 released

In , on 05/24/2010 at 05:06 PM, Paul Edwards said: >Also GETLINE/PUTLINE are used in a TSO environment, >so all programs automatically become command processors. I takes more than that to make them command processors. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; se

Re: SEASIK 1.0 released

Wow, what a lot of misses. > *nix humor. This is after all an environment with a utility > called grep and where processes fork in order to make children. No Charles, Gerhard is MVS through and through. Nothing to do with Unix. You're right about the SEA = C though. > Well, it's certainly memor

Re: SEASIK 1.0 released

On 5/24/2010 8:38 PM, zMan wrote: Well, it's certainly memorable. Not sure I understand where it comes from -- it looks like an acronym, but for what? Paul asked me to suggest something, and I expressed my feelings about C and related languages (except for a short stint as a ForTran programme

Re: SEASIK 1.0 released

The SEA part presumably is a pun on the C language. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of zMan Sent: Monday, May 24, 2010 5:38 PM To: IBM-MAIN@bama.ua.edu Subject: Re: SEASIK 1.0 released Well, it's certainly memo

Re: SEASIK 1.0 released

Well, it's certainly memorable. Not sure I understand where it comes from -- it looks like an acronym, but for what? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the me

Re: SEASIK 1.0 released

@bama.ua.edu Subject: Re: SEASIK 1.0 released SEASIK? Seriously?! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http

Re: SEASIK 1.0 released

- I have just released SEASIK 1.0, which is (effectively) a DFDSS dump of a whole lot of C products, namely: - Is it offered as "Mal de mer" in France or French-speaking region

Re: SEASIK 1.0 released

SEASIK? Seriously?! On Mon, May 24, 2010 at 6:06 PM, Paul Edwards wrote: > I have just released SEASIK 1.0, which is (effectively) > a DFDSS dump of a whole lot of C products, namely: > -- For IBM-MAIN subscribe / signoff / arc

SEASIK 1.0 released

I have just released SEASIK 1.0, which is (effectively) a DFDSS dump of a whole lot of C products, namely: GCC 3.2.3 MVS 8.0 PDPCLIB 3.00 BISON 1.35 MVS 4.0 BREXX 2.1.8 MVS 1.0 BWBASIC 2.50 MVS 1.0 DIFFUTIL 2.8.1 MVS 4.0 FLEX 2.5.4a MVS 4.0 M4 1.4 MVS 4.0 PATCH 2.5.4 MVS 4.0 SED 3.02 MVS 4.0 MINIZ