On 2020-05-26 5:04 AM, Ed Jaffe wrote:
We recently had the need to use GTF to collect SLIP IF, SVC, USR and
PI events to help diagnose a PIC 38 program check where the address
to be resolved was above the bar. Unfortunately, the trace was of
almost no use in diagnosis due to the more or less co
Hi Clark,
Not "was", is, DYL280 aka Vision:Results still exists. We run it in our
datacenter.
Rex
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Clark Morris
Sent: Friday, May 22, 2020 3:05 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [External] Re: z/OS 2.3 systems
Greetings,
A gentle reminder that the next meeting of the GSE UK Security Working Group,
will take place on Thursday 11th June 2020 (09:00 – 17:15 BST) via Webex.
The agenda and registration is available here >
https://www.gse.org.uk/events/gse-uk-security-working-group-meeting/ -
(regist
Kolusu, thank you so much for this. I hadn't thought about testing for
each node and length like that - I will hold onto this email for some
other things that are similar!
Thanks again!
Billy
-- Original Message --
From: "Sri h Kolusu"
To: IBM-MAIN@listserv.ua.edu
Sent: 5/22/2020 8:44
On 2020-05-25 17:04, Ed Jaffe wrote:
For the record, we diagnose issues using the events you've listed all
the time, no matter what the AMODE. In fact, we even have RMODE(64) code
nowadays.
There is a bug with 64-bit PTRACE formatting and we got a custom fix
from Jim Mulder for that (it will
On Sun, 24 May 2020 05:02:24 +, Seymour J Metz wrote:
>That sounds like a great use case for regexen.
>
Ob"When your favorite tool is a hammer ..."
>
>From: Billy Ashto
>Sent: Friday, May 22, 2020 3:57 PM
>
>I have an 80-byte LRECL list of filenames (st
VPH/VPA seems to be documented.
On Tue, 26 May 2020 13:52:49 -0400 Gord Tomlin
wrote:
:>On 2020-05-25 17:04, Ed Jaffe wrote:
:>> For the record, we diagnose issues using the events you've listed all
:>> the time, no matter what the AMODE. In fact, we even have RMODE(64) code
:>> nowadays.
:>>
Indeed rather a "broad brush" when the problem was only with the last
item, the "PI" record. Especially when SLIP was mentioned and I knew that
SLIP's record does contain the high halves.
For a person as experienced as the OP, the data presented really was
enough (albeit I guess not in the way
Well, in this case the hammer is the reverse function;
/\.([#$@[:upper:][:digit:]]{1,8})\n/, despite the awkward syntax, is still
cleaner.
Wasn't there a song on the 1960's, Lexity, Lex, YACCitty YACC?
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
__
https://www.youtube.com/watch?v=-cHB3Rbz1OI
Yakity Yak - The Coasters April 1958. In The Great Outdoors with John
Candy and Twins with Arnold and Danny DeVito.
On Tue, May 26, 2020 at 2:42 PM Seymour J Metz wrote:
>
> Well, in this case the hammer is the reverse function;
> /\.([#$@[:upper:][:d
I'm not a CICS jock, but at many of the installations I've worked at I've had
occasion to analyze a record of who used which CICS transactions over the past
weeks or years. The datasets have had varying formats, but I've gradually come
to believe that CICS must track such things and keep a log
I'm not advocating this practice. Just saying that we did it for 25 years
without a failure. We're now moving to totally different technology where such
action is not even in the picture.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co
CICS statistics. Make sure they are turned on.
The CICS statistics are written as SMF 110 records.
It is possible to analyze them using various tools.
>toot toot> Check CBT file 529. You will also need CBT file 527 for a
>sub-program or two.
Matthew
On Tue, 26 May 2020 16:59:28 -0400, Bob
On Tue, 26 May 2020 19:42:31 +, Seymour J Metz wrote:
>Well, in this case the hammer is the reverse function;
>/\.([#$@[:upper:][:digit:]]{1,8})\n/, despite the awkward syntax, is still
>cleaner.
>
I was more thinking of the OP's requirement for DFSORT as the hammer.
And Sri supplied a mass
> And Sri's example contained a node longer than 8 bytes.
Well, if it were up to me z/OS would support cataloged data sets with longer
index levels, but circumstances being what they are I'd rather not parse them.
Besides, they're only valid inside of apostrophes.
If the problem definition cha
AFAIK, no captures available in POSIX awk (i.e., what we get delivered with
z/OS), only in gawk-only extended matching functions like gensub() and in gawk
split() with the optional gawk-only arguments to split out parsed groups into
arrays.
Peter
-Original Message-
From: IBM Mainframe
On Tue, 26 May 2020 22:50:10 +, Seymour J Metz wrote:
>
>Well, if it were up to me z/OS would support cataloged data sets with longer
>index levels, but circumstances being what they are I'd rather not parse them.
>Besides, they're only valid inside of apostrophes.
>
DISABLE(DSNCHECK) superse
*totally different technology...*
Magic?
On Tue, May 26, 2020 at 5:11 PM Jesse 1 Robinson
wrote:
> I'm not advocating this practice. Just saying that we did it for 25 years
> without a failure. We're now moving to totally different technology where
> such action is not even in the picture.
>
>
> Empirically, I found I couldn't create a DSN starting with a period even
> within apostrophes. I don't know where this is documented.
Gil,
This works fine for me
//STEP0100 EXEC PGM=SORT
//SYSOUT DD SYSOUT=*
//SORTIN DD *
dummyrecord
//SORTOUT DD PATH='/tmp/.create.dsn.with.period',
//
PATH ¬= DSN
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Sri
h Kolusu [skol...@us.ibm.com]
Sent: Tuesday, May 26, 2020 9:49 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: R
Yackity yak, don't go back. It's after Monday Morning and it's the wrong
season for quarterbacks.
On Wed, May 27, 2020 at 1:13 PM Seymour J Metz wrote:
> PATH ¬= DSN
>
>
> --
> Shmuel (Seymour J.) Metz
> http://mason.gmu.edu/~smetz3
>
>
> From: IBM Mainfr
CICS SMF 110. You could probably use DFH$MOLS to analyse, it takes some of
the hard work out of breaking the SMF into readable stuff.
On Wed, May 27, 2020 at 7:13 AM Matthew Stitt
wrote:
> CICS statistics. Make sure they are turned on.
>
> The CICS statistics are written as SMF 110 records.
>
>
You'll need a CICS MCT entry (Monitor control table).
Sample JCL:
//DELITEXEC PGM=IDCAMS
//SYSIN DD *
DELETE SYS.CICSTS54.CICS.MNDUPREC
SET MAXCC=0
/*
//SYSPRINT DD SYSOUT=A
//MNDUPEXEC PGM=DFHMNDUP
//STEPLIB DD DSN=SYS3.CICSTS54.CICS.SDFHLOAD,DISP=SHR
//SYSUT4 DD DSN=SYS.CICSTS54.CI
Wayne,
The MCT is only required for CICS monitoring records which have a
dictionary. CICS statistics SMF 110 records are fixed.
On 2020-05-27 11:54 AM, Wayne Bickerdike wrote:
You'll need a CICS MCT entry (Monitor control table).
Sample JCL:
//DELITEXEC PGM=IDCAMS
//SYSIN DD *
DELETE
24 matches
Mail list logo
