Re: SMP/E oddity?

If you try to RESTORE bar it will fail unless either foo is also restored at the same time or foo has been accepted. -- Tom Marchant On Wed, 30 Nov 2022 14:49:42 +, Seymour J Metz wrote: >Partial restore is a can of worms. What happens if foo has a PE, bar >supersedes the associated

Re: Computers

Reminds me of all of those movies and TV shows that had shots of sorters or spinning reels on tape drive. Silly wabbit, trits are for kids. From: IBM Mainframe Discussion List on behalf of Tom Brennan Sent: Tuesday, November 29, 2022 10:00 PM To:

Re: Computers

Are the ones we remember forever :) Matt Hogstrom m...@hogstrom.org +1-919-656-0564 PGP Key: 0x90ECB270 Facebook LinkedIn Twitter “It may be cognitive, but, it ain’t intuitive." — Hogstrom >

Re: Computers

LOL, I'm not convinced I won't think the very same thing, when I'm 500 years old, about some of the games and projects that hold my interest now. Personal growth goes on. --- Bob Bridges, robhbrid...@gmail.com, cell 336 382-7313 /* It is a good sign in a nation when things are done badly. It

Re: Computers

Reminds me of staying up all night in the computer lab at college playing 3d TicTacToe (4x4x4) against an IBM 1620 computer until I finally beat it by playing its own moves back at it. Wasted a whole box of console paper (not to mention failing to do my Calculus and other homework that night)

Re: Computers

In college we had an IBM 1130 in the computer lab. Those of us working in the lab discovered an AM radio placed near the console switches made odd noises when you ran Fortran programs and set the radio to a specific "station". Further investigation revealed you could change the tone of the

Re: DASD I/O response time affects CICS transaction MIPS, why?

PPRC synchronous completes the I/O when the result is posted to the secondary dasd. PPRC asynchronous completes the I/O when the result is posted to the primary dasd. During busy times you might get multiple updates to a track before the last update is sent. On Wed, Nov 30, 2022 at 2:33 AM

Re: Computers

Wow. Reminds me of the times when some people spelled it "computor" instead of "computer" :-) Roops On Wed, 30 Nov 2022, 05:37 Phil Smith III, wrote: > Tom Brennan wrote: > >I never knew each section of a computer had its own distinct sound. > >https://www.youtube.com/watch?v=ukyHECjKDoQ > >

Re: Origin of the name of sample programs DSNTEP2/4?

A long time ago I wrote a cobol equivalent because the site didn't have a PL/I compiler and the program was distributed in source only. Lacking the necessary naming expertise I simply called it CSNTEP2 with the first character indicating the language used :). It might still be available at IDUG

Re: SMP/E oddity?

https://www.ibm.com/docs/en/zos-basic-skills?topic=maintenance-zos-software - Is a good 500' level discussion. In general, never delete anything from a target system outside of SMP/E. -- For IBM-MAIN subscribe / signoff /

Re: SMP/E oddity?

> > SMP/E is a complex tool to manage your z/OS system, but it does the job it > is intended to do. > Indeed so. It's quite complex, but so is the job it's designed to do, and if you understand it, you can maintain your system as it was intended to be maintained. Whenever I hear Linux geeks

Re: SMP/E oddity?

With all the issues with SMP and SMP/E themselves over the years, I always backup ALL SMPE related datasets, including the CSIs, before I start any SMPE work. No source/object management systems are perfect and the extra time to secure a check point of the state of the SMP/E environment is

Re: [EXTERNAL] Re: SMP/E oddity?

Thanks for the clarification, Kurt. I didn't think RESTORE processing had changed. Rex -Original Message- From: IBM Mainframe Discussion List On Behalf Of Kurt J. Quackenbush Sent: Wednesday, November 30, 2022 9:35 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: [EXTERNAL] Re: SMP/E

Re: SMP/E oddity?

Well, like I said, this all demands that a sysprog know what the hell he's doing...and clearly I don't. :-) In my defense, it's been 30 years since I wrangled SMP/E... On Wed, Nov 30, 2022 at 9:35 AM Kurt J. Quackenbush wrote: > >> RESTORE does behave the same as APPLY in this respect. > > >

Re: SMP/E oddity?

>> RESTORE does behave the same as APPLY in this respect. > RESTORE no longer requires that other maintenance to the involved elements be > ACCEPTed? > It can rebuild the load modules using APPLYed-only elements? No, no, no, that's not it at all. This discussion was solely about building

Re: Computers

I had all of them on mine while playing this video. Agreed with how great it is. On a funny timing note, today's version would just show a cloud :-) On Wed, Nov 30, 2022 at 12:38 AM Phil Smith III wrote: > Tom Brennan wrote: > >I never knew each section of a computer had its own distinct

Re: [EXTERNAL] Re: SMP/E oddity?

That's not the way I am reading it from the SMP/E commands manual. Here's what I see. The RESTORE command replaces the affected elements in the target libraries with the unchanged versions from the distribution libraries. (As a result, once you have accepted a SYSMOD into the distribution

Re: SMP/E oddity?

There is no right answer to this one: SMP/E cannot differentiate between this scenario and the one where foo is OK and bar is broken, or where foo has a PE that's relatively benign but bar has an issue that's worse than the problem with foo. The sysprog who's doing this has to know what he's

Re: SMP/E oddity?

Partial restore is a can of worms. What happens if foo has a PE, bar supersedes the associated APAR, the APPLY only installed foo because bar had been received and you now restore bar?. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM

Re: SMP/E oddity?

I'd always understood that RESTORE could do this, but it required a lot more work on the part of SMP/E, and the purpose of ACCEPT was to make RESTORE work much faster. Every shop I ever worked at didn't ACCEPT anything (except for those very rare SYSMODs that needed it for sysgen processing) until

Re: DASD I/O response time affects CICS transaction MIPS, why?

Johnny, you are watching a very normal behavior. There is no unlimited supply of anything. Once the OP-sys is full (whatever resource you look at) the next level will have queues that build up. And maintaining these queues takes time. Very simple model: Once your I/O rate is higher than

DASD I/O response time affects CICS transaction MIPS, why?

Hi, Several months ago we conducted two tests on our system. In the first test, when cics transaction rate reached 9000, response time deteriorated badly. So we stopped the PPRC and repeated the test. As expected, we got very good response time. Surprisingly, however, our transaction cpu time