I did a quick search and didn't see anything, so I thought i'd ask here. Can a
rexx program being executed in Netview write data to a logstream?
Mark Jacobs
Sent from [ProtonMail](https://protonmail.com), Swiss-based encrypted email.
GPG Public Key -
Long ago (2005) we had one of the largest generators of SMF data on
record and continued to use MAN datasets using a couple of techniques
to carry the load.
Environment: four CECS, all in the same SYSPLEX. four on UK time,
ten on US time. Extensive use of CICSPLEX and transaction routine
W dniu 02.08.2022 o 19:41, Steve Beaver pisze:
Has anyone ever created a LOGSTREAM on an M54 of 65000 cylinders.
I have a very, very busy CICS and DB2 on the same LPAR
No, never, even close to such huge size. I'm talking about very busy and
overloaded CICS region with DB2 on same LPAR
You might consider splitting the data into multiple logstreams.
Michael
At 12:41 PM 8/2/2022, Steve Beaver wrote:
Has anyone ever created a LOGSTREAM on an M54 of 65000 cylinders.
I have a very, very busy CICS and DB2 on the same LPAR
Thanks
Has anyone ever created a LOGSTREAM on an M54 of 65000 cylinders.
I have a very, very busy CICS and DB2 on the same LPAR
Thanks
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to
well. I found anther SMF logstream which is a PLEX wide complete SMF
logstream, totaling 22,223 CYLS
Carmen
=
On 7/15/2022 9:12 AM, Steve Beaver wrote:
For those using Logstreams.
What is your largest Logstream in cylinders? And are you using SMS EF?
TIA
the largest LS we have defined is for SMF, allocated in tracks, but I
calculated to 5,098 CYLS
Carmen
On 7/15/2022 9:12 AM, Steve Beaver wrote:
For those using Logstreams.
What is your largest Logstream in cylinders? And are you using SMS EF?
TIA
For those using Logstreams.
What is your largest Logstream in cylinders? And are you using SMS EF?
TIA
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu
Does "56+ kbytes per track" help?
What are those numbers? Kilobytes?
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Steve Beaver
Sent: Friday, June 3, 2022 12:08 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Logst
Has anyone figured out how to compute the number of cylinders for
STG_SIZE(119880)
LS_SIZE(119880)
Thanks
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with
On Thu, 26 May 2022 10:10:24 -0500, Steve Beaver wrote:
>I have a friend whose systems produces BILLIONS of SMF records per month and
>
>He is basically using the following DEFINE for his DEFAULT LOGSTREAM.
>
>
>
>I will tell you simply that I have no IDEA if the NUMBERS for STG_SIZE and
I have a friend whose systems produces BILLIONS of SMF records per month and
He is basically using the following DEFINE for his DEFAULT LOGSTREAM.
I will tell you simply that I have no IDEA if the NUMBERS for STG_SIZE and
LS_SIZE
Are crazy or inline. I know those numbers can be revised on
On Wed, 25 May 2022 15:12:34 -0500, Scott Barry wrote:
>For SMF Logstreams, there is no "I SMF" -- instead, only option is IFASMFDL
>(batch) invocation to offload any given / named SMF LOGSTREAM. And consider
>staggering the individual START command invocations, that is
data sets, then allow DFHSM to
archive and manage then. Thought ought to reduce your archival storage needs.
Michael
At 02:46 PM 5/25/2022, Steve Beaver wrote:
I have learned more about SYSTEM Logstreams that I ever wanted to know.
I have friend that produces BILLIONS of SMF/Logstream records
On Wed, 25 May 2022 14:46:20 -0500, Steve Beaver wrote:
>I have learned more about SYSTEM Logstreams that I ever wanted to know.
>
>
>
>I have friend that produces BILLIONS of SMF/Logstream records per month,
>
>And has RETPD of 120 (ten years' worth). And each S
I have learned more about SYSTEM Logstreams that I ever wanted to know.
I have friend that produces BILLIONS of SMF/Logstream records per month,
And has RETPD of 120 (ten years' worth). And each STAGE file is migrated
Of within 24 hours.
I am going to split this mess into DB2(100,101,102
Logstreams are a bit befuddling
Trouble will start below
DATA TYPE(LOGR) REPORT(YES)
DEFINE LOGSTREAM NAME(IFASMF.)
DASDONLY(YES)
STG_SIZE(50)
STG_DATACLAS(MVSLOGR)
LS_DATACLAS(MVSLOGR
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
Here's a RedBook that might help you set it up. It's a little easier on a z15
(might also be true on a z14 too), since the hardware is incorporated on the
processor itself and not as a separate PCIe processor card. It still is a price
z/OS feature though.
Thanks for that. And if you have not yet set up zEDC compression, where is a
good place to start?
Jim Horne
NOTICE: All information in and attached to the e-mails below may be
proprietary, confidential, privileged and otherwise protected from improper or
‐‐‐
On Wednesday, February 10th, 2021 at 11:12 AM, Horne, Jim
wrote:
> Can you point to documentation on how to set up zEDC compression, especially
> for SMF logstreams?
>
> Jim Horne
>
> NOTICE: All information in and attached to the e-mails below may be
> proprietary, con
L r01,psaaold-psa
L r01,ascbassb-assb(,r01)
L r01,assbjsab-iazjsab(,r01)
Regards, Pierre.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu
Can you point to documentation on how to set up zEDC compression, especially
for SMF logstreams?
Jim Horne
NOTICE: All information in and attached to the e-mails below may be
proprietary, confidential, privileged and otherwise protected from improper
If you have zEDC compression available it's very worthwhile to compress the SMF
data before writing it to the logstream/staging datasets.
Mark Jacobs
Sent from ProtonMail, Swiss-based encrypted email.
GPG Public Key -
https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com
An advantage of log streams is that you can set up a log stream so type1
goes to one log stream and type2 goes to another log stream. If type1
produces too much data type2 is not affected.
If you log to disk you process the data set to extract/process the type1
and type2 records. If type1
Thank you Gadi and Jim,
For us, using DASD-only logstream is the preferred way and I already set it up
on a test system and played with it a little bit.
I set up a RETPD of 10 days. this works fine and I understand that this is the
prefered way and not period of years, I just wanted to check
Ron,
You definitely want to go to logstreams. We went to CF logstreams 10 years ago
and have never regretted it. And that is the first question you need to answer:
coupling facility, which is sysplex-wide, or DASD-only? That will affect all
your other decisions.
The next thing you need
Hi,
We write SMF to logstreams.
Every day at midnight we copy the data for the previous day to dasd.
Every week we create a weekly smf dataset from the previous weeks daily
datasets.
Gadi
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Ron
Burg
Sent: Wednesday
Hello,
I'm trying to figure out the best-practice for collecting SMF data
with Logstream instead of MAN datasets. There are few points I seem to
miss and I hope to get some advice from those who used it for a while.
I can see the benefits in storing the SMF on logstream only, for
example I can
; Anyway, I pro-actively defined all LOGSTREAMs that we would be requiring
> for production, well ahead of when we would actually require them.
>
> Sometime later but before we installed out application change we ran a
> Disaster Recovery test event.
> When the DR event ran, there was
LOGSTREAM.
I know very little about this. We simply requested the LOGSTREAM to be made
available to our CICS Regions, and our IBM resources waved their magic
wands and it was there.
Anyway, I pro-actively defined all LOGSTREAMs that we would be requiring
for production, well ahead of when we would
Gadi Ben-Avi wrote:
>I would like to prevent a user from accessing the SMF log
>streams
>Is there anything else that I need to define?
To add to earlier replies, it's prudent to encrypt your log stream data
sets so that you're fully blocking unauthorized user access, even from
storage
Probably
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
David Spiegel
Sent: Monday, April 29, 2019 11:46 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Access to SMF logstreams
Hi Gadi,
I think that you meant "discrete" instead of "discreet".
Sh
Hi Gadi,
I think that you meant "discrete" instead of "discreet".
Shalom,
David
On 2019-04-29 01:34, Gadi Ben-Avi wrote:
> Hi,
> I would like to prevent a user from accessing the SMF log streams.
> Class is active and there are discreet profiles for each of the
Subject: Re: Access to SMF logstreams
Gadi
You should be good. Remember to grant the user associated with the SMF address
space UPDATE access to the profiles.
If you haven't already done so, take a look at this redbook:
SMF Logstream Mode <http://www.redbooks.ibm.com/redbooks/pdfs/sg247919.
Mike
On Mon, 29 Apr 2019 at 08:34, Gadi Ben-Avi wrote:
> Hi,
> I would like to prevent a user from accessing the SMF log streams.
> Class is active and there are discreet profiles for each of the SMF
> logstreams.
> The user in question does not have access to the profiles.
>
Hi,
I would like to prevent a user from accessing the SMF log streams.
Class is active and there are discreet profiles for each of the SMF logstreams.
The user in question does not have access to the profiles.
Is there anything else that I need to define?
Thanks
Gadi
It sounds as though you only have one CF? At least two is the recommended
config. In that case you move the structures from one CF to the other then
work on the “empty” one.
You can always revert to using SMF datasets while working on the CF.
On Thu, May 17, 2018 at 4:40 PM Kenneth J. Kripke
Hello;
I wish to get some input on handling outages for the coupling
facilities when it comes to such activities as an IML to
Expand the Coupling facility sizes. We had an episode where the Partition
was reconfigured for more storage which disrupted recording of
The SMF data. The data
Based on my first-hand experience, the CA SMF DIRECTOR solution is nothing like
any predecessor - has not been for nearly 10 years, possibly more. Any sizable
z/OS site looking at SMF Logstreams should consider this solution, as an
opportunity to help with easing migration and also going
o:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Scott Barry
Sent: Friday, February 09, 2018 10:27 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: SMF advice on additional logstreams
Also, for consideration, might there also be "frequency of reference", such as
security (ACF2, RACF, etc.) and/or DB2
aintaining separate SMF recording/offloading by SMF type provides the
opportunity for SMS-managed historical data-capture, as a retention-limit.
For a client/site we support, SMF Logstreams are defined/managed by CA SMF
DIRECTOR using zEDC (8-to-1 compression typical) with DFHSM-managed historical
On Feb 9, 2018, at 7:16 AM, Richards, Robert B. <robert.richa...@opm.gov> wrote:
>
> At what point or percentage (records written/space used) would it be
> advisable to split out 92s, 99s, 120s into their own logstreams? Right now
> they are all in Default. A coworker test
Scott,
I am the OP.
I definitely appreciate your comments (and everyone else's too), but no one was
commented on the other half of my questions.
At what point or percentage (records written/space used) would it be advisable
to split out 92s, 99s, 120s into their own logstreams? Right now
Remember when looking at SMF volume, record counts are interesting, but the
bigger issue is the number of bytes written.
We (Peter Enrico and myself) recommend collecting at least 99 subtypes 6, 10,
11, 12, and 14.
6 is especially important as it's the summary service class period
List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Allan Staller
Sent: Thursday, February 08, 2018 11:18 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: SMF advice on additional logstreams
Not sure about SMF92, but SMF99 are "WLM decision records".
Yes they are large volume, bu
iew the installation
requirements.
Bob
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Rob Scott
Sent: Thursday, February 08, 2018 11:05 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: SMF advice on additional logstreams
I have always thought of SM
MAIN@LISTSERV.UA.EDU
Subject: Re: SMF advice on additional logstreams
I have always thought of SMF92 and SMF99 as data of interest primarily for
monitoring products - do you have them enabled because of ISV requirements?
If there is ISV software that needs to read this SMF data in real
for these types, perhaps
the vendor (or you) could create a simple IEFU8x to suppress these records from
being hardened to MANx datasets or logstreams.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Richards, Robert B.
Sent: Thursday, February 8
It was recently noticed that SMF TYPES 92 and 99 are creating a very high
percentage of our overall SMF records. Seems to coincide with the
implementation of z/OS 2.2, but that is speculative at the moment.
Has anyone considered (or implemented) making one or both into their own
logstream(s)?
stallation
> >
> >
> >
> >
> > You will find what you need.
> >
> > Lizette
> >
> >
> >> -Original Message-
> >> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> On
> >> Behalf Of Mohamed Gomaa
&g
gstream define installation
>
>
>
>
> You will find what you need.
>
> Lizette
>
>
>> -Original Message-
>> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
>> Behalf Of Mohamed Gomaa
>> Sent: Sunday, Jul
f Mohamed Gomaa
> Sent: Sunday, July 16, 2017 9:50 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: CICS Logstreams
>
> I am locking for setting CICS log stream using structure in sysplex and for
> recovery purpose we want to use staging dataset.
> I am locking for policy s
I am locking for setting CICS log stream using structure in sysplex and for
recovery purpose we want to use staging dataset.
I am locking for policy sample to define it
Thanks
Mohamed Juma
--
For IBM-MAIN subscribe / signoff /
LOGREC=IGNORE was introduced in MVS/ESA SP5.2.0 (around 1994)
as part of the logrec to logstreams line item.
Jim Mulder z/OS Diagnosis, Design, Development, Test IBM Corp.
Poughkeepsie NY
John Eells/Poughkeepsie/IBM@IBMUS wrote on 06/30/2017 09:26:31 AM:
> From: John Eells/Poughkeepsie/
data set; also with
no functioning OPERLOG. In fact this happens to us every time we bring up our
DR systems for the first time--without any defined logstreams. You can create a
logstream only on the exploiting system. So we IPL, then run the log stream
creation jobs for SMF, OPERLOG, and RRS
-715-0595 Mobile
626-543-6132 Office ⇐=== NEW
robin...@sce.com
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Skeldum, William
Sent: Thursday, June 29, 2017 9:50 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: Logstreams
We
any defined logstreams. You can create a
logstream only on the exploiting system. So we IPL, then run the log stream
creation jobs for SMF, OPERLOG, and RRS.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626
It will come up with LOGREC full :)
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> On Behalf Of Bill Wilkie
> Sent: Thursday, June 29, 2017 9:17 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Logstreams
>
> Thank
Thanks, that's nice to KnowBill
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of
Skeldum, William <william.skel...@efirstbank.com>
Sent: Thursday, June 29, 2017 4:49 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Logstr
We use logstreams, including for logrec and do not have any SYS1.LOGREC
datasets defined. Our IEASYSxx parmlib specifies LOGREC=LOGSTREAM. We have no
issues IPLing. Early in the IPL we receive message:
IFB085I LOGREC RECORDING TO LOG STREAM SYSPLEX.LOGREC.ALLRECS
Bill Skeldum
-Original
als and about to read the Logstream Redbook.
>
>
> I was just trying to figure out who was using logstreams and why.
>
>
> Thanks
>
> Bill
>
>
>
> From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf
> of L
Lizette:
I am trying to understand the purpose of the logstream vs Logrec. I am just
finishing the Logrec manuals and about to read the Logstream Redbook.
I was just trying to figure out who was using logstreams and why.
Thanks
Bill
From: IBM Mainframe
what I can gather so far about Logstreams, it just holds a bunch of
different logs like Operlog, LOGREC, etc. but the data is still in it's
original form as if it were read directly from the original data set.
Bill
From: IBM Mainframe Discussion List <IBM-M
Office ⇐=== NEW
robin...@sce.com
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Lizette Koehler
Sent: Thursday, June 29, 2017 7:51 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: Logstreams
So does this mean the problem you
So does this mean the problem you are trying to solve by asking about
logstreams is
Can I prevent my system from not IPL'ing if someone deletes SYS1.LOGREC? Will
the logstream still allow me to IPL eve if SYS1.LOGREC is gone?
Lizette
> -Original Message-
> From: IBM Mai
Lizette:
I am not using logstreams yet. I am just looking into it.
The SYS1.LOGREC data set got deleted on our test system so we couldn't IPL it.
We ran a job from our other system to create a new one and it IPL'd OK.
Thanks
Bill
From: IBM Mainframe
3:03 PM
Subject: Re: Logstreams
We don't run regularly with logrec logstream, but I believe that you still need
to maintain SYS1.LOGREC in order to capture IPL time records that are cut
before logger gets running. If that's still true...
.
.
J.O.Skip Robinson
Southern California Edison C
M-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Bill Wilkie
> Sent: Thursday, June 29, 2017 2:32 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Logstreams
>
> We accidentally deleted Logrec on one system, and couldn't IPL. Not sure if
> logstream being available would have made
.@sce.com>
Sent: Wednesday, June 28, 2017 8:23 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Logstreams
We don't run regularly with logrec logstream, but I believe that you still need
to maintain SYS1.LOGREC in order to capture IPL time records that are cut
before logger gets running. If that'
Just so. We start up our systems on SYS1.LOGREC and convert to logstream once
logger services are available (SETLOGRC command issued via automation).
I converted both SMF and SYSLOG to logstreams with no dramas. This site had
syslogs stored by system-id, so I modified SAMPLIB(IEAMDBLG
: (External):Re: Logstreams
On Jun 28, 2017, at 2:07 PM, Bill Wilkie <billwil...@hotmail.com> wrote:
>
> Is anyone running from logstreams instead just running logrec? Using
> logstreams for other reports? How used? Problems?
I switched SMF, LOGREC, and OPERLOG to logstreams a few ye
On Jun 28, 2017, at 2:07 PM, Bill Wilkie <billwil...@hotmail.com> wrote:
>
> Is anyone running from logstreams instead just running logrec? Using
> logstreams for other reports? How used? Problems?
I switched SMF, LOGREC, and OPERLOG to logstreams a few years ago. It all
as it if I was using SYS1.LOGREC
Carmen
- Original Message -
From: "Bill Wilkie" <billwil...@hotmail.com>
To: IBM-MAIN@LISTSERV.UA.EDU
Sent: Wednesday, June 28, 2017 2:07:02 PM
Subject: Logstreams
Is anyone running from logstreams instead just running logrec? Using logst
Is anyone running from logstreams instead just running logrec? Using logstreams
for other reports? How used? Problems?
Thanks
Bill
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists
What was the solution?
Thanks,
Greg Shirey
Ben E. Keith Company
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Jonathan Miller
Sent: Tuesday, May 20, 2014 9:59 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: SMF Logstreams
I found
How do i extract smf data that has already been marked for delete from a
logstream? We use the archive feature and had a problem and one of the
archived tapes was delete.
--
For IBM-MAIN subscribe / signoff / archive access
I found the solution to this problem so no need repsond. Thanks
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
78 matches
Mail list logo
