Absolutely. Today is the first day of my new career as an IEFU8x consultant.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of David Crayford
Sent: Tuesday, October 8, 2019 9:27 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re:
On 2019-10-09 9:55 AM, Charles Mills wrote:
No, I retired from the SMF exit business on March 31.
Of course, you have a wealth of expertise in this area from your
Correlog days. I might ping you off list if I have any questions if
that's alright? ;)
If I were writing the product today
Should have written > 255, of course.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Charles Mills
Sent: Tuesday, October 8, 2019 6:56 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: SMF exit IEFU086 work area size
No, I
No, I retired from the SMF exit business on March 31.
If I were writing the product today there is no question I would use it: only
one exit point to maintain, handles the new > 127 SMF records whenever they
come, and the work area is a plus. I used a cell pool for work areas in my exit
so it
Hi Charles,
Yes, it is!
SMXP_WORKAREA_LENGTH_V1 EQU 1024
This IEFU086 exit is great! Have you used it?
David
On 2019-10-08 10:27 PM, Charles Mills wrote:
It's not defined in IFAEXITP?
Charles
-Original Message-
From: IBM Mainframe Discussion List
Use PGM=ADRDSSU to backup your *complete* SMP/E product environment to a
new GDG entry (e.g. on tape/cart), and keep a note of the GDG entry
containing the backup so that you can restore your previous SMP/E etc.
from there if necessary.
E.g. something like:
//STEP1 EXEC PGM=ADRDSSU
And to completely close the loop, I did hear from IBM and they pointed me to
this page, which is more or less what I ended up doing.
https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.bpxb200/crusfs.htm
Charles
-Original Message-
From: IBM Mainframe
Unless all jobs updating the PDS with DISP=SHR use the same serialization
protocol, you are going to periodically lose data. I concur with the suggestion
to use the ISPF convention.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM
On 2019-10-08 13:10, ITschak Mugzach wrote:
Jhon, It should be enterprise linux. Centos is an option as well.
For the current zPDT release...
Linux levels used to build and test zPDT release. (The “official” levels.):
- RHEL 7.5, SLES 12 SP3, Ubuntu 18.04 LTS
Informally tested Linux levels:
And a potential solution is just as old. Allocate a zero space "dummy" dataset.
Pdsname.ENQUEUE. Add a DISP=OLD DD against this to the jobs. This only works it
the updating job/step is fairly fast, but it will prevent simultaneous
accesses.
> -Original Message-
> From: IBM Mainframe
In article <2000189509316059.wa.paulgboulderaim@listserv.ua.edu> you wrote:
> On Tue, 8 Oct 2019 16:28:30 +, Jesse 1 Robinson wrote:
> >This is a classic problem endemic to traditional PDS since the dawn of MVS.
> >IBM's solution to this problem is PDSE. If you convert the data set to
>
The z/OSMF Workflow is a framework that supports z/OS System Programmers
(Workflow provider) to define a guided flow (workflow) through steps to
accomplish a system management or configuration task. System programmers can
organize the tasks they perform for day to day operation in a workflow
On 10/7/2019 4:10 PM, Juergen Kehr wrote:
we just started a project to upgrade from z/OS V2.2 to V2.4. Now, late enough,
we find out that with z/OS V2.4 PMA is removed. Up to now we used at least one
of the tables (BCNFMDS) and one of the EXECs (BCN2APRR) to get a description of
the installed
I need to dynamically activate NETMONITOR SMFS in TCPIP using obey command.
Seems pretty harmless but I'd like to ask if there any concerns when turning on
these services? Any gotcha's to be aware of? Does it cause additional SMF
records to be written?
Thanks,
Matt Dazzo
On Tue, 8 Oct 2019 16:28:30 +, Jesse 1 Robinson wrote:
>This is a classic problem endemic to traditional PDS since the dawn of MVS.
>IBM's solution to this problem is PDSE. If you convert the data set to Library
>(PDSE) you may reduce problem occurrence to negligible. OTOH PDSE may
Jhon, It should be enterprise linux. Centos is an option as well.
ITschak
On Tue, Oct 8, 2019 at 7:27 PM John McKown
wrote:
> On Tue, Oct 8, 2019 at 10:47 AM Gord Tomlin <
> gt.ibm.li...@actionsoftware.com>
> wrote:
>
> > On 2019-10-08 00:20, Peter wrote:
> > > Hi All
> > >
> > > Is there
Thanks all.
What I am trying to do is to install a vendor product. (The vendor is one you
all know and love who is not famous for customer hand-holding.) But I did find
in one of the myriad supplied PDFs a cookbook for accomplishing this. It seems
to be under control.
Charles
>PDSE data sets and members can be shared. If allocated with DISP=SHR, the
>PDSE directory can be shared by multiple writers and readers, and each PDSE
>member can be shared by a single writer or multiple readers. Any number of
>systems can have the same PDSE open for input. If one system has a
On Tue, 8 Oct 2019 16:15:38 +, Pesce, Andy wrote:
>I have "JOBA" that executes a COBOL program to update a particular member in a
>PDS. Within the program, it calls an internal utility that someone
>wrote years ago that puts an enqueue on the dataset and its member that it is
>updating.
On Tue, Oct 8, 2019 at 11:16 AM Pesce, Andy wrote:
> I am looking for an explanation and this may be one of those
> "unpredictable results" may occur.
>
> I have "JOBA" that executes a COBOL program to update a particular member
> in a PDS. Within the program, it calls an internal utility that
This is a classic problem endemic to traditional PDS since the dawn of MVS.
IBM's solution to this problem is PDSE. If you convert the data set to Library
(PDSE) you may reduce problem occurrence to negligible. OTOH PDSE may introduce
its own set of problems, chief of which is the inability to
On Tue, Oct 8, 2019 at 10:47 AM Gord Tomlin
wrote:
> On 2019-10-08 00:20, Peter wrote:
> > Hi All
> >
> > Is there anyone in the group who had Mainframe on AWS space ?
> >
> > I Would like to a set a one using my AWS account. Any pointers would be
> > appreciated.
> >
> > Peter
>
> If you are an
I am looking for an explanation and this may be one of those "unpredictable
results" may occur.
I have "JOBA" that executes a COBOL program to update a particular member in a
PDS. Within the program, it calls an internal utility that someone
wrote years ago that puts an enqueue on the dataset
On 2019-10-08 00:20, Peter wrote:
Hi All
Is there anyone in the group who had Mainframe on AWS space ?
I Would like to a set a one using my AWS account. Any pointers would be
appreciated.
Peter
If you are an ISV, have a look at Chapter 8 of the zPDT Redbook:
Yes, but that is MVS3.8J on Hercules mainframe emulator in S/370 mode, not z/OS.
AFAIK, no IBM hardware is available in AWS, only x86 hardware, so no, you can't
do that.
Peter
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Mike Schwab
Sent: Tuesday, October 8,
It's not defined in IFAEXITP?
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of David Crayford
Sent: Tuesday, October 8, 2019 5:52 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: SMF exit IEFU086 work area size
z/OS 2.3 introduced
Thank you Larre!
This looks definitive :)
On 2019-10-08 9:42 PM, Larre Shiller wrote:
David -
Based on some ESP notes that I have from our z/OS 2.3 install, it looks like
the work area size is 1024 bytes. The parameter list is mapped by
MACLIB(IFAEXITP). I see no evidence to indicate that
David -
Based on some ESP notes that I have from our z/OS 2.3 install, it looks like
the work area size is 1024 bytes. The parameter list is mapped by
MACLIB(IFAEXITP). I see no evidence to indicate that the length can be
set/modified by the installation.
Larre
US Social Security
David,
I guess you will use a mapping for your work area in your program. So you can
always have code which compares the length needed with the length available. I
just don't know what you do when your needs are greater than they supply!
Issue a message? Yes, but how many messages will you
Thank you Lennie,
You make some very good observations. I think the salient point of the
work area is so the exit routine doesn't need to allocate any storage
for obvious reasons (performance). I'm leery of using an exit with a
work area without knowing it's length!
On 2019-10-08 9:13 PM,
When I look in the System Exits manual I see a structure passed as a parameter
list which has an offset to the work area, and a length specified for it.
Assuming the length is specified in bytes it must fit in a halfword. So max
would be 65536 bytes.
I agree it would be sensible for IBM to
z/OS 2.3 introduced the new IEFU086 SMF exit which is passed a work area
which is great.
I can't find any documentation in KC on how to customize the size of the
workarea in SMPRMxx or what the minimum size of the area is.
Can anybody shed any light on this?
https://www.youtube.com/watch?v=fhdFPEHdwCg
On Tue, Oct 8, 2019 at 4:20 AM Peter wrote:
>
> Hi All
>
> Is there anyone in the group who had Mainframe on AWS space ?
>
> I Would like to a set a one using my AWS account. Any pointers would be
> appreciated.
>
> Peter
>
>
33 matches
Mail list logo
