Separate names with a comma.
Post in 'New Forum Hints and your Questions & Suggestions!' started by flyingcow, Mar 25, 2012.
Helpful Sponsor Ads!
TTY originally with APRANET and also the RJE station we used with the IBM 370/158. We were big time there. One of the first places in the Southwest with disk drives on the mainframe and DOS/VS. Around 1975-1976. We were thrilled when we upgraded main memory to 16K. We could run payroll and accounts payable at one time. Our fastest comm link was the lady who carried the decks of punched cards from the keypunch area to the computer room. Guess you could call it JackieNet.
So yeah, hearth.com looks mighty fast to me.
the problems i (and others) were/(are?) having (are?)/were real.
at least now for myself, i can report the site is working properly.
no hesitation getting into threads like since the changeover.
and i know it wasn't my computer or connection because i haven't had any problems on any other site.
but yeah. i'm no longer having the same slowness i was getting here before.
as always, thank you for this terrific site.
So what did you do there?
I was known to play with what this actually produced instead of what the vendor had originally provided.
* $$ JOB JNM=GENSUP3,USER='BEAR',CLASS=0,DISP=D
* $$ LST LST=00E,FNO=0001,CLASS=S,DISP=D
* $$ PUN PUN=00D,FNO=CARD,CLASS=S,DISP=D
// JOB GENSUP3
// ASSGN SYSLST,X'00E'
// ASSGN SYS001,SYSRES,SHR
// ASSGN SYS002,SYSRES,SHR
// ASSGN SYS003,SYSRES,SHR
// ASSGN SYSLNK,SYSRES,SHR
// OPTION CATAL
// EXEC PGM=ASSEMBLY
TITLE 'DOS/VS SUPERVISOR F,SYSRES=3350,MOD=138,NPARTS=5' 00420034
PHO=YES, REQUIRED FOR POWER/VS X00850033
POWER=YES, 'P O W E R / V S' X00900033
DASDFP=(2,2), (TO ALLOW SYSRES ON CHANNELS 1-4) X01650033
ECPREAL=YES, REQUIRED FOR POWER/VS X01750033
PFIX=YES, REQUIRED FOR POWER/VS X02300033
RELLDR=YES, REQUIRED FOR POWER/VS X02400033
F1=172K, POWER/VS (RJE) X03450033
NRES=10 REQUIRED FOR VSAM II 04350033
ASSGN SYSLOG,X'01F' 05700033
ASSGN SYSREC,X'240' 05750033
ASSGN SYSCAT,X'240' VSAM MASTER CATALOG 05800033
// EXEC LNKEDT
* $$ EOJ
Groan. I swore in retirement I would never look at JCL again. So much for that! Thanks just a whole bunch.
Night operator on the 370. If I had a buck for every time I typed "G OOE" I could have retired at 25. Or fixed somebody's busted JCL because you did not want to have to wake up a drunk programmer.
I don't believe that anyone here said there weren't issues for some of the folks using the forum.
Actually not having any problems on any other sites is not an indication of your computer or connection being fine and dandy or this forum misbehaving.
I can over the course of a month have problems not related to any site or my computer but somewhere in the path between a site and my computer, frequently only one of the sites appears to be slow and all others appear to be fine.
Upon closer look a piece of hardware in between goes pfft or gets blocked due to many reasons, this can happen in the weirdest of ways and sometimes it is caused by the folks that run the network operations centers in response to various events taking place.
All it takes is for some duffus to run a DOS attack against any of the network devices between you and the site you are trying to get to. Most major hosting companies have to deal with this on an ongoing basis. The effect you generally see is vastly inconsistent response times. If you are on a Satellite system various weather events can cause issues.
Lots of things to look at, lots of possibilities, plenty of places in between to be in the way. More than most people realize.
Being drunk and on call was a firing offense at every place I worked. I also have stuff for the OS/MVS, and VM side of the ledger and can actually IPL and run a number of the old systems.
We have jacked Craig's thread enough. We will have to do a good old days PM sometime.
but that people in different regions describe the same type of problems make an individual event on my specific chain of connection seem the far less likely explanation.
and there were a few comments that did indeed imply that these issues were to do with the user's connection or equipment.
as well as more reasonable folks saying that indeed there seemed to be issues.
so. just for those couple of comments that were of the "it's fine for me so your equipment is junk or you connection sucks" nature, i say that's a typical and easy reply.
in any event, i am still pleased to relate that all is well now.
and reiterate my thanks for this great site.