Quote:
Originally Posted by Dngrsone
My goodness... I don't even remember. Let's see, Vulcan was a basic OS; the Machine itself was 24-bit mainframe with I think 512KB RAM. We used two HP7906 or 7907 hard drives (the 7906 had 18" platters, one fixed, one removable, total storage, a whopping 20MB; the 7907 went down to 8" platters, same capacity, IIRC). I think we calculated teh clock speed at something like 3MHz...
Job Control Language (JCL) ran on top of Vulcan, though we spent most of our time in Test Executive, which ran in the JCL shell.
|
The first machine I dealt with, back in the 80's, was an IBM 370 compatible. It ran OS/VS1, later converted to OS/MVS. The original machine had 2MB RAM and 16MB virtual memory, and supported about 500 remote 3270 terminals under CICS, when it worked. The area of the bank I worked in had brought in a complete IBM mainframe data center for just under $1 million, but to do so they went third-party and plug compatible, and because it wasn't genuine IBM kit, they couldn't run the latest IBM software. Outages were frequent.
I had a cartoon from Datamation in my cube, with a field engineer walking into a site asking "System been down long?", and addressing the question to a skeleton in a chair coated in cobwebs. Some made a copy of it, and put it up on the inside of the door to the VP of IT's office. He was not amused. He came up through the ranks, having started as a COBOL programmer. There was still a COBOL module on the system he maintained to keep his hand in. He sat down at the terminal do do a little work on "his" program, and Lo! The system was down. The systems programmer turned purple and sputtered when I told him about it.
Midway through my tenure, they upgraded to two IBM 4341s loosely coupled under JES2, and reliability soared. Around the time I left, the bank decided to centralize everything back at Division level and close the Region's data center. The Region had built out its own capacity in the first place to get out from under the two year backlog at Division, and it was hitting its stride and doing good stuff, but corporate had different ideas...
I was amused by IBM JCL. All of eight statements in the language, but it was a black art, and everyone used someone else's canned procs instead of trying to write their own. I got yelled at at one point because I tweaked the JCL on a job to boost it's prioriy, and got a "Don't
do that!" reprimand from the VP of Applications Development. I'm not sure whether he was more upset that I'd done it, or that I
wasn't a member of the IT staff. (I actually worked for Finance, and was their interface with IT.)
Access was via IBM's TSO. The original "GUI" was a third party product called ACEP, intended to be a substitute for IBM's SPF. When the bank upgraded to "real" SPF, I thought it a step backward.
Quote:
I've got a crappy Motorola NVG510 that AT&T insists I use for U-verse. The built-in firewall is basic. I have an old gaming server with Smoothwall on it: CLAMAV and content filtering, usage restrictions and monitoring, etc... I can even set up a separate network for a server, if the son decides he wants to host a Minecraft server.
Problem is, I can't get the NVG510 to go into true bridge mode for my external firewall to work; hence the hacking part.
|
This might help:
https://forums.att.com/t5/Third-Part...y/td-p/3434307
Quote:
|
It's either that or try and get AT&T to admit that there are other (perhaps even better?) modems that will work on their lines.
|
There probably are. The question is whether AT&T would notice if you substituted one and what they would do if you did.
______
Dennis