On Thu, 4 Dec 2014 13:24:43 +0530, Mainframe Mainframe wrote:
Yes. Both volume are part of same storage group . Also I am allocating HFS
dataset, so aggrgrow= on parameter doesn't matter here.
Any other clue to define HFS dataset with bigger space more then 4000MB.
Messages from your first
I believe you are thinking of The Code Breakers. Danger UXB was about bomb
disposal, and played around 1987 in the US, if I remember. You might also
check out The Betchley Circle, about four women who, 5 years after the war,
solve crimes in post-war England applying methods they learnt during
Good day to all,
Just curious, if you don't mind please.
One of my colleagues wants to change a job output class (column S) in 'JOB DATA
SET DISPLAY' in ST screen in SDSF.
Ie, you enter a ? next to the job, press enter and see lines of different Job
Datasets. Nothing on that screen is
It works for me on H, but not on ST. Running z/OS 2.01, JES2 2.1, ISPF 7.1.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
edgould1...@comcast.net (Ed Gould) wrote:
Derrick:
*myself* I would never put multiple page DS's from multiple systems on
the same drive.
The rule I have observed for 40+ years. Nor would I place multiple page
ds's on the same drive from one system.
Dedicate a drive for each page ds.
...and,
You still didn't provide the D SMS commands oupput. However I also notice that
on Ispf allocate screen you had specified storage class TESTSC but the sms
error message ICG17290I had storage classs TESTSG.
Storage class . . . . TESTSC
IGD17290I THERE WERE 1 CANDIDATE
In 8675686473977785.wa.peterteneyckfarmfamily@listserv.ua.edu,
on 12/03/2014
at 01:51 PM, Peter Ten Eyck peter_tene...@farmfamily.com said:
It would seem that coding SYSUDUMP in the JCL and running LE with
something like TERMTHDACT(UADUMP,,96) would be the way to go.
SYSUDUMP is fine as
In
caajsdjigfmpcacjfeyy+dt_hoaagxv97zjtayee3y6h_hq5...@mail.gmail.com,
on 12/03/2014
at 01:36 PM, John McKown john.archie.mck...@gmail.com said:
I must somewhat disagree, or perhaps just partially. IPCS is great.
I really like it. But for batch cycle jobs, I would strongly
recommend a product
Hi Derrick,
We are using flash express on our z/EC12's but have not changed our paging
confiquration because of dr considerations. May not apply to you but something
to consider.
Doug
On Wed, 3 Dec 2014 15:00:06 -0600, Derrick Haugan dhau...@metlife.com wrote:
We are preparing to use flash
Are you using ISFPARMS or the SDSF Server?
Did you convert the fields to RACF (Or your SAF product)?
I seem to remember that the ISFPARMS provide a mechanism for controlling what
groups have over typeable fields.
Lizette
-Original Message-
From: IBM Mainframe Discussion List
This is just my mind wandering around loose again. You kind indulgence is
appreciated.
But I've been thinking about the z/OS syslog for some reason lately. Given
what it was originally designed for, review by a human, it is a decent
design. But is it really as helpful as it could be in today's
Lizette Koehler wrote:
Are you using ISFPARMS or the SDSF Server?
SDSF Server. Each LPAR has its own SDSF Server, but sharing a single ISFPARM.
Did you convert the fields to RACF (Or your SAF product)?
RACF. I let ISFPARM to be used where RACF can't make up its mind. ;-)
I seem to
Have the user having the issue the WHO command and it should give you a
starting point.
Lizette
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Elardus Engelbrecht
Sent: Thursday, December 04, 2014 7:30 AM
To:
Hi John,
While I am sure this not exactly what you are dreaming about we do run IBM's
z/Aware with does consume operlogs and provides an api that uses xml.
http://www-01.ibm.com/support/docview.wss?uid=isg24f9114255d7d1f3285257a6a0077c2ca
Doug
On Thu, 4 Dec 2014 08:06:33 -0600, John McKown
John McKown wrote:
This is just my mind wandering around loose again.
Catch it! Catch it! ;-)
( There is an old Afrikaans song 'Catch it!' which says how difficult is it to
catch chicken/pig/sheep/etc. ;-D )
But I've been thinking about the z/OS syslog for some reason lately. Given
what it
Lizette Koehler wrote:
Have the user having the issue the WHO command and it should give you a
starting point.
Been there, done that. ISFSPROG, just the same as mine. This and RACF profiles
are the main reason for previous post.
Groete / Greetings
Elardus Engelbrecht
Thanks for the tip, yes it definitely applies to us, we added the flash feature
to our DR site EC12's also, as what we do in the main site we also want
available at DR
--
For IBM-MAIN subscribe / signoff / archive access
We have zos1.13 zos http server running with no SSL configured. In the PKI
Services guide (sa22-7693-13) I think there is conflict about SSL requirement.
Below is text from the guide, first one states required, second one says at
least non-ssl. Does anyone know for sure? I may not go through
I cannot clear up the confusion, other than to tell you to open a QA PMR with
IBM asking them, however I will tell you we are using SSL(HTTPS).
Maybe some the confusion comes because it uses both. We have sslmode turned
on, and a SSL port assigned, and the redirects in httpd.conf all use
Thanks Dave, I'll probably decide to go SSL at the end of the day.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Jousma, David
Sent: Thursday, December 04, 2014 10:33 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: PKI Services for
Thanks. But what's a 'volume' these days anyway? We use IBM 8870s with raid-5,
and then on top of that, we use DS800 extent pool striping. So the bits bytes
of the paging 'volumes' are scattered like the stars throughout the DASD
subsystem.
Lizette Koehler wrote:
Did you convert the fields to RACF (Or your SAF product)?
I seem to remember that the ISFPARMS provide a mechanism for controlling what
groups have over typeable fields.
Ok. I have review RACF (SDSF Class), ISFPRMxx member and looked at ISFPARMS
module (as supplied
What things are built in a Sysplex by the first LPAR brought up in the Sysplex
that would impact subsequent LPARs brought up in the Sysplex?
Some possible examples... WLM, GRS, SMS etc.
I am asking this question to elevate the need to maintain/preserve LPAR IPL
order in a Sysplex and identify
This book has been suggested:
SG24-2079-01
IBM z/OS Parallel Sysplex Operational Scenarios
It has an excellent chapter (chapter 3) on IPL order.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to
Elardus,
Entering the ? command displays the JOB DATA SET DISPLAY screen, as you note.
Pressing F1 should display the HELP panel, option 3 will list the fields on the
panel - there are 8 panels of fields to display. Panel 2 on my z/OS 1.13
system says this:
Access for fields marked with
From Chapter 4. Columns on the SDSF panels
In the tables that follow, an X in the Delay column indicates that obtaining
the data may require an I/O operation. These columns are typically in the
alternate field list. I/O operations are performed only when the columns are
visible on the screen
On Thu, Dec 4, 2014 at 8:44 AM, Elardus Engelbrecht
elardus.engelbre...@sita.co.za wrote:
snip
And I will admit that my mind has been corrupted by using Linux too much
lately. grin/
Please refresh my mind about how is Linux version of log(s) working?
Well, the normal UNIX syslogd data
While conceptually XML sounds nice, the problem would seem to be the
extreme volume of data involved, millions of messages daily for large
installations. Uncompressed XML is incredibly inefficient in storage
requirements, and compressing/uncompressing XML has processing costs.
From my viewpoint I
With current emulated DASD and PAVs, performance is probably no longer
an issue, but I believe multiple page data sets on one volume is still a
potential availability issue: You wouldn't want failure of a single
emulated drive to compromise two different systems at the same time, and
I seem to
I've run into a situation where we have a parm that expands to more than 100
characters (sound like a familiar problem?).
So, I've tried to use the PARMDD EXEC Keyword. And sure enough it points over
to the specified DDName.
So I have it coded like this:
// EXPORT SYMLIST=*
:
Doubtful regarding your high availability question. True, you are no longer
bound to an ESCON pair of type CTC/CNC. FICON has superior features, but if I
understand your configuration correctly, I am not sure how much you are gaining
as your CTCs still appear to be just two channels.
Are you
With current emulated DASD and PAVs, performance is probably no longer an
issue, but I believe multiple page data sets on one volume is still a
potential availability issue: You wouldn't want failure of a single
emulated drive to compromise two different systems at the same time, and I
Commenting just on the issue of Syslog (in the 'nix sense) structure.
No, RFC 5424 is not widely observed.
Syslog epitomizes the aphorism about God loves standards -- that's why he
created so many of them. About the only Syslog standard that everyone almost
follows is RFC 3164, and even that
A couple of recent threads indicated the 30% rule is still valid No info
on z/Flash as yet..
snip
It may be time to revisit old paging ROTs. Does anyone have a double or triple
digit paging rate anymore? Is the 30% rule still valid? (We completely ignore
it). Does zFlash obviate the old
You may have put the EXPORT statement at the wrong point in the JCL. Try
putting it right after the JOB statement.
On Thu, 4 Dec 2014 18:40:03 +, Steve Thompson sthompso...@humana.com
wrote:
I've run into a situation where we have a parm that expands to more than 100
characters (sound
On Thu, 4 Dec 2014 18:46:38 +, Bob Shannon wrote:
Unless the recommendation has changed, there should only be one page dataset
per MVS volume. IIRC MVS remembers the last head position and performance
suffers when the head has moved.
That apparently all changed with the demise of the
W dniu 2014-12-04 o 19:28, Joel Ewing pisze:
With current emulated DASD and PAVs, performance is probably no longer
an issue, but I believe multiple page data sets on one volume is still a
potential availability issue: You wouldn't want failure of a single
emulated drive to compromise two
Date: Thu, 4 Dec 2014 12:56:53 -0600
From: Peter X. DeFabritus pxdef...@gmail.com
You may have put the EXPORT statement at the wrong point in the JCL. Try
putting it right after the JOB statement.
SNIPPAGE
Sorry, it behaved the same whether it was just after the JOB card or just
before the
My €0.02
The idea of structured logging smells like WIndows Event Log which I
hate deeply.
JSON ans XML are the format which I like in similar manner like the above.
For human and script-powered review we have syslog. Of structured
logging we have SMF which can be exported to XML if someone
On 2014-12-04 12:35, Steve Thompson wrote:
So, if you need to your parm line (string), think about how you do the split.
Because the next line read is concatenated to the prior line ignoring the
right side spaces (at least that's what I have experienced). If you need a
space between
On 12/04/2014 03:04 PM, Paul Gilmartin wrote:
On 2014-12-04 12:35, Steve Thompson wrote:
SNIP
Like, what's the most efficient way to clear a register?
-- gil
SNIP
Well, mine is to pull the power plug. I don't have to write code,
I don't have to deal with MAKE, BINDER, or anything else.
The following definitely works, tested on V2.1 system today. HTH.
//YOURJOBX JOB (0,0). . . == Supply your own
//*
//* DOC: EXPERIMENT WITH INSTREAM SYMBOL SUBSTITUTION.
//*
And I should have mentioned that SHOWPARM is just a local utility to display
the PARM as a WTO. Any equivalent local program will do.
Peter
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Farley, Peter x23353
Sent: Thursday,
On 12/04/2014 04:15 PM, Farley, Peter x23353 wrote:
The following definitely works, tested on V2.1 system today. HTH.
SNIPPAGE
Yeah I'm having a Rod Serling afternoon.
I have two JOBs now where I am using this. One works, the other
does not.
The one that does not work does pass to
A suggestion then: Specify a SYMBOLS logging DD, as I did in my example. It
*should* tell you what substitutions were actually made.
Paul Gilmartin had a thread about this a while back (not sure if here or
TSO-REXX or where), from which my example was taken and subsequently modified.
The
Every MVS volume I have seen in the last two decades is on an emulated
3390 drive, although no doubt somewhere people are still running real
3380s or 3390s. From MVS's viewpoint, it thinks every DASD unit
address is a physical DASD drive even though the DASD Subsystem is only
emulating the
W dniu 2014-12-04 o 23:23, Joel Ewing pisze:
Every MVS volume I have seen in the last two decades is on an emulated
3390 drive, although no doubt somewhere people are still running real
3380s or 3390s.
I doubt it. Even if someone is really using real 3380s, it's completely
irrelevant, because
Joel Ewing wrote:
Every MVS volume I have seen in the last two decades is on an emulated
3390 drive, ...
Me too - until just a few days ago when I happened upon a number of
3380's defined at a client site. All I can guess is these were still
real 3380's at the time they needed to be moved
If the first system IPLed is not the last system brought down, you may have to
reply I to initialize the sysplex. This is because the last system leaves no
compatriot behind to do final cleanup of the couple data set(s). In the
last-down/first-up sequence, the system recognizes his own body
Crikey - we replaced 3380K's with 3390-2's back in 1990. We then had to
replace the whole lot again soon after with 3390-3's, but thats a whole
other story...
On 4 December 2014 at 23:31, Tom Brennan t...@tombrennansoftware.com wrote:
Joel Ewing wrote:
Every MVS volume I have seen in the
t...@tombrennansoftware.com (Tom Brennan) writes:
Me too - until just a few days ago when I happened upon a number of
3380's defined at a client site. All I can guess is these were still
real 3380's at the time they needed to be moved to a DS8000. TASID
shows them as 3380-TC3 (whatever that
I really like some of the new centralized logging systems like
http://logstash.net/. It can handle loads of different sources and sinks
and when you throw in the full power of elasticsearch searching for
interesting data is an order of magnitude
more powerful then what we currently have on
Anne Lynn Wheeler wrote:
http://www.bitsavers.org/pdf/ibm/dasd/reference_summary/GX26-1678-0_3380_Reference_Summary_Feb83.pdf
I just found some of those in my old reference card collection -
http://www.mildredbrennan.com/mvs/disk_summaries.jpg
... one is tempted to believe that the 3380j
On Fri, 5 Dec 2014 11:15:58 +0800, David Crayford dcrayf...@gmail.com wrote:
I really like some of the new centralized logging systems like
http://logstash.net/. It can handle loads of different sources and sinks
and when you throw in the full power of elasticsearch searching for
interesting data
On 5/12/2014 2:30 PM, Shane Ginnane wrote:
Yeah, but how do you get it there ?. Sysadmins want everything*now*. Not
tomorrow after syslog has been archived off.
Takes us back to the tail syslog thread last month. Surely the Netview (or
whatever) developers must be able to knock up code to push
55 matches
Mail list logo
