zMan,
The "mainfame" is just to remind us that some people think that "sic
transit gloria mundi" of the mainframe...
ITschak
ITschak Mugzach
*|** IronSphere Platform* *|* *Information Security Continuous Monitoring
for z/OS, x/Linux & IBM I **| z/VM coming soon *
On Thu, Feb 11, 2021 at
Good point. I was just hoping that something from a company focused on the
mainframe would do better.
On Thu, Feb 11, 2021 at 5:25 PM Seymour J Metz wrote:
> Hey, it's a classic example of Buzz Word Bingo. It's not supposed to make
> sense.
>
>
> --
> Shmuel (Seymour J.) Metz
>
Hey, it's a classic example of Buzz Word Bingo. It's not supposed to make sense.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
zMan [zedgarhoo...@gmail.com]
Sent:
Nope, paid gig. But good suggestion!
On Thu, Feb 11, 2021 at 4:31 PM Tom Brennan
wrote:
> My bet is the artist is a student who did it for free, so I give them a
> break. And if he/she is anything like my kids (both do that kind of
> work), one of the characters in the comic looks like the
My bet is the artist is a student who did it for free, so I give them a
break. And if he/she is anything like my kids (both do that kind of
work), one of the characters in the comic looks like the artist :)
On 2/11/2021 1:13 PM, zMan wrote:
https://devops.com/wp-content/uploads/2021/02/Triumph-Of-The-Mainframe.pdf
While I admire the effort, I feel compelled to point out:
- The typo “mainfame” on p.5
- The fact that the mainframe has NOTHING to do with solving the problem
in the story
- RBAC is not the opposite of “plain
A few thoughts
This is NOT purely an academic excersize - if an lpar crashed with a DS member
on it, and the LPAR COULD NOT be immediately restarted. You would NEED to bring
up the downed member on the remaining LPAR in light mode - to free any locked
threads - miake sure all the drda ports
The answer is much more related to your infrastructure than the DB2 DS Member
itself. (You can indeed run different DS members on a single LPAR) - we've done
it during a DR exercise ) The question is more about do you have shared
parmlibs/proclibs/RACF etc. etc. Some other considerations might
Are you saying you currently do not have a DB2 Data Sharing Region on LPAR2
(Non CICS?) for this DB2 Region?
Lizette
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Lizette Koehler
Sent: Thursday, February 11, 2021 11:40 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject:
Unless I am missing something.
The point of DB2 Data Sharing is there is a GROUP (Umbrella) that connects
multiple DB2 Regions.
So if you have 2 or more DB2 Data Sharing regions. One on LPAR1 one on LPAR2
Then if LPAR1 is down, then LPAR2 will take on the DB2 data sharing work.
Does that
Decisions around how long to keep SMF data in the log streams are unique per
customer installation. IBM does not make recommendations for that. For your
IFASMFDL return code concerns, implementing a post processing job log 'scraper'
world be useful to take specific actions based on the messages
I have used it extensively.
I know my MODIFY command parser would handle blanks as equivalent to commas
-- but I can assure you I never tested that. (The identical parser is used
elsewhere, where blanks are common as separators.)
Charles
-Original Message-
From: IBM Mainframe
The MODIFY command processor creates a CIB and queues it off of the relevant
CSCB. See the QEDIT macro.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Pew, Curtis G
we are being constrained due to operations limitations. We are planning to
upgrade our development environment and we need to have the development CICS
regions down. Unfortunately operations says they have difficulty going thru all
the regions and just stopping development cics. Our CICS
Bill,
Why are you wanting to do that?
A DB2 Data sharing environment has a DB2 Start on each lpar that shares the
Same DB2 information. If you have 4 LPARs, you would have one DB2 Data
Sharing region on the LPARs you want.
For example:
I have a group name of DBP2, but I have 3 DB2 regions
@Peter, the example I quoted came from
https://www.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieag100/m3modaxr.htm
. (Hope that survives the wrap.)
I was *actually* working from the V2R1 docs (because I am a stick in the mud
and prefer BookManager to the unreliable
Martin,
We develop a product that intercepts SMF records in real-time and generates a
DataBase in Open Platform. This Data can be used to generate reports and
graphics dynamically.
Best Regards
Em quinta-feira, 11 de fevereiro de 2021 11:19:39 BRT, Martin Packer
escreveu:
Subchannel
Curtis P wrote
On Feb 10, 2021, at 3:27 PM, Charles Mills wrote:
>
> I guess blanks are legal in a MODIFY command operand. I see an example
in the manual: F AXR,SYSREXX STATUS
>
> I did not know that.
>
I believe that the console address space handles modify commands by
sticking
Subchannel busy (as opposed to busy CONDITIONS) is estimated from request
rate and service time multiplied together.
I think we'd all like to know the purpose of this, though.
Cheers, Martin
Martin Packer
Systems Investigator & Performance Troubleshooter, IBM
+44-7802-245-584
email:
no I simply want to start DB2 Member1 on LPAR2.
Bill
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Colin,
Thank you very much for your time.I'll take a closer look at these SMF fields.
Best Regards
Ituriel
Em quinta-feira, 11 de fevereiro de 2021 09:55:10 BRT, Colin Paice
escreveu:
Hi,
CF level Local Coupling Facility Data Section
24 18 R744FPBC 8 l_float Number of times coupling
Hi,
CF level Local Coupling Facility Data Section
24 18 R744FPBC 8 l_float Number of times coupling facility requests fail
due to path busy.
You get data for each structure
For the Structures you get the different sorts of requests
92 5C R744SSRC 8 l_float Count of number of times for
Hi Colin,
I do need the SMF fields, not the extraction from RMF. I have to create a
database with information related to Path Busy, Service Time, Number of
subchannels, sync and async requests, etc...
And i could see similar information in several sections of SMF 74.4, which
causes me
You can get RMF to format most(all?) of these records.
What high level analysis do you want to do?
Colin
On Thu, 11 Feb 2021 at 11:56, Ituriel do Neto <
03427ec2837d-dmarc-requ...@listserv.ua.edu> wrote:
> Hi all,
> I'm trying to collect some information from SMF 74.4 and would like some
>
Hi all,
I'm trying to collect some information from SMF 74.4 and would like some
advice.I need to analyze data similar to Subchannel Activity Report does, but
i'm a little confused.
In SMF 74.4 there are several sections and, if possible, i would like to know
which one isused as the basis for
W dniu 11.02.2021 o 11:54, Bill Giannelli pisze:
Thank you for the information!
I think I was a little vague.
Let me explain further...
we have on LPAR1 DB2 Member1, on LPAR2 DB2 Member2. Both members of the same
data sharing group.
I want to be able to start DB2 Member1 on LPAR2 and
Thank you for the information!
I think I was a little vague.
Let me explain further...
we have on LPAR1 DB2 Member1, on LPAR2 DB2 Member2. Both members of the same
data sharing group.
I want to be able to start DB2 Member1 on LPAR2 and DB2 Member2 on LPAR1.
thanks
Bill
It depends ... there are many non-Db2 dependencies on things like shared
dasd (implies SMS definitions), Catalog structure, XCF signalling paths,
IRLM and your CF connectivity, etc. Unless your shop has deliberately
setup multiple lpars to be compatible, chances are they will not be. You
can
We have DB2 data sharing and I have a need to start DB2 members on any LPAR.
Aside from RACF definitions, is the only other item I need in place is the SSID
symbol in SYS1.PARMLIB(IEFSSNxx) ?
thanks
Bill
--
For IBM-MAIN
Agree that all machines are better off in a single IODF.
In a site I was at, site1 was connected to both site1dasd and site2dasd.
However, only a few volumes from site2dasd were 'live' / accessible; the rest
were PPRC targets from site1dasd.
Those site2dasd vols that were accessible from site1,
30 matches
Mail list logo
