Re: SMF exit IEFU086 work area size

[Charles Mills]

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: SMF exit IEFU086 work area size

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 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 was pretty efficient, but "free" is even better.
>
> BTW, IEFU86, right? No 0?

My bad :)

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: SMF exit IEFU086 work area size

[David Crayford]

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 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 was pretty efficient, but 
"free" is even better.

BTW, IEFU86, right? No 0?


My bad :)




Charles


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of David Crayford
Sent: Tuesday, October 8, 2019 6:27 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: SMF exit IEFU086 work area size

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 [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 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?

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: SMF exit IEFU086 work area size

[Charles Mills]

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 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 was pretty efficient, but "free" is even better.

BTW, IEFU86, right? No 0?

Charles


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of David Crayford
Sent: Tuesday, October 8, 2019 6:27 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: SMF exit IEFU086 work area size

Hi Charles,

Yes, it is!

SMXP_WORKAREA_LENGTH_V1 EQU 1024

This IEFU086 exit is great! Have you used it?

David

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: SMF exit IEFU086 work area size

[Charles Mills]

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 was pretty efficient, but "free" is even better.

BTW, IEFU86, right? No 0?

Charles


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of David Crayford
Sent: Tuesday, October 8, 2019 6:27 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: SMF exit IEFU086 work area size

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 [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 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?
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: SMF exit IEFU086 work area size

[David Crayford]

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 [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 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?

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: SMPe CSI maintenance levels

[CM Poncelet]

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
//SYSPRINT  DD  SYSOUT=*
//OUTDD1 DD DSN=(+1),
// DCB=(,
// BLKSIZE=32760),
// DISP=(NEW,CATLG,DELETE),
// UNIT=CART
//FILTERDS DD    *
 INCLUDE( -
        -
     -
                        -
 )
//SYSIN    DD    *
 DUMP DATASET(FILTERDD(FILTERDS)) -
  OUTDDNAME( -
    OUTDD1 -
   ) -
  CANCELERROR -
  INCAT() -
  OPTIMIZE(4) -
  WAIT(2,2)
//*

 

Chris Poncelet (retired sysprog)



On 07/10/2019 19:37, Kurt Quackenbush wrote:
> On 10/7/2019 11:29 AM, Bill Giannelli wrote:
>> I apologize if this is a dumb question, I have 3 zones, global,
>> target and dlib, so if I had an "x y and z" as in your example, would
>> I then have 9 zones? x global target dlib, y global target dlib, z
>> gobal target dlib?
> Using Lizette's example, yes, 9 zones.  Although I assert you don't
> need to copy your global zone, just the target and dlib.  So really
> you have 3 target and dlib zones (6), all hanging off a single global
> zone (1) for a total of 7.
>
> Kurt Quackenbush -- IBM, SMP/E Development
> Chuck Norris never uses CHECK when he applies PTFs.
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> .
>


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Add space to OMVS filesystem?

[Charles Mills]

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 Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Charles Mills
Sent: Tuesday, October 8, 2019 10:06 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Add space to OMVS filesystem?

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

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: PDS Member updating via COBOL Program

[Seymour J Metz]

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 Mainframe Discussion List  on behalf of 
Pesce, Andy 
Sent: Tuesday, October 8, 2019 12:15 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: PDS Member updating via COBOL Program

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 and its member that it is 
updating.  The dd associated with the parmlib uses DISP=SHR.

I have "JOBB" that executes a COBOL program to do the same thing, but it is a 
different member within the same dataset as "JOBA".It is coded
to open the dataset as I/O.  After it reads the member, it then does a REWRITE. 
   It doesn't follow the rules as above and use the internal utility.
The dd associated with the parmlib also uses DISP=SHR.

Here is the issue.   Occasionally the member in "JOBA" is becoming "empty", 
while the member in JOBB is always OK.I have looked at SMF
records and I see these jobs run at the same time.  And it is usually the same 
down to the hundreds of seconds.

My suggestion was that JOBB needs to be fixed to use the "enqueue and dequeue" 
utility, since it is using DISP-SHR.   This parmlib is
used heavily and extensively by applications, and no way to get it DISP=OLD.  
Any thoughts or explanation would truly be appreciated.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Mainframe environment on AWS

[Gord Tomlin]

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:

- RHEL 7.0, 7.1, 7.2, 7.3, 7.4 (do not use 6.x)openSUSE 13.1, Leap42.3, 
Leap 15.0, Fedora 27, 28, CentOS 7.0, 7.4,Ubuntu 16.04.5 LTS, 18.04.1


Most definitely the annual cost per seat for ZD is pretty hefty, and 
you can infer from this that the offering is not aimed at hobbyists.



--

Regards, Gord Tomlin
Action Software International
(a division of Mazda Computer Corporation)
Tel: (905) 470-7113, Fax: (905) 470-6507
Support: https://actionsoftware.com/support/

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: PDS Member updating via COBOL Program

[Gibney, Dave]

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 Discussion List  On
> Behalf Of Don Poitras
> Sent: Tuesday, October 08, 2019 10:55 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: PDS Member updating via COBOL Program
> 
> 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
> 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 
> share
> the data set across sysplex boundaries. If that restriction is unacceptable, 
> you
> might try adding in your RYO enqueue program as you suggest. Be aware,
> however, that DISP=SHR is unlikely to provide much if any protection against
> concurrent update.
> > >
> > I have used ISPF LM services for this purpose.  But that requires a
> > TSO environment.  Otherwise, you may simulate the ISPF technique, as in:
> >
> > https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__www.ibm.com_suppo
> > rt_knowledgecenter_en_SSLTBW-
> 5F2.4.0_com.ibm.zos.v2r4.f54pc00_isppcmmn
> > amen.htm=DwIBAg=C3yme8gMkxg_ihJNXS06ZyWk4EJm8LdrrvxQb-
> Je7sw=u9g8
> > rUevBoyCPAdo5sWE9w=-
> UJtuL7ygnoO_jSZKwoqXZkKxYZabHfW2DHliI3IKU8=St_
> > eOtwpm5WRFX6EOtYceBdAAOXHTO-FbL_MpcX4_mQ=
> > Whatever you do, all players must follow the same rules.  Any
> > nonconformists must be re-coded.
> > I have tested using LMPUT to write multiple members concurrently.
> > It works, but only within a single job because ISPF LMPUT reqiuires
> > ENQ EXC on the DSN.
> > -- gil
> 
> If you do the ENQ as shown in the link above, be sure to also issue the
> RESERVE which is documented just before this. (ISPF Data set integrity
> enqueue).
> 
> --
> Don Poitras - SAS Development  -  SAS Institute Inc. - SAS Campus Drive
> sas...@sas.com   (919) 531-5637Cary, NC 27513
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send email to
> lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: PDS Member updating via COBOL Program

[Don Poitras]

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 
> >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 
> >share the data set across sysplex boundaries. If that restriction is 
> >unacceptable, you might try adding in your RYO enqueue program as you 
> >suggest. Be aware, however, that DISP=SHR is unlikely to provide much if any 
> >protection against concurrent update. 
> > 
> I have used ISPF LM services for this purpose.  But that requires a TSO
> environment.  Otherwise, you may simulate the ISPF technique, as in:
> 
> https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.4.0/com.ibm.zos.v2r4.f54pc00/isppcmmnamen.htm
> Whatever you do, all players must follow the same rules.  Any
> nonconformists must be re-coded.
> I have tested using LMPUT to write multiple members concurrently.
> It works, but only within a single job because ISPF LMPUT reqiuires
> ENQ EXC on the DSN.
> -- gil

If you do the ENQ as shown in the link above, be sure to also issue the
RESERVE which is documented just before this. (ISPF Data set integrity
enqueue).

-- 
Don Poitras - SAS Development  -  SAS Institute Inc. - SAS Campus Drive
sas...@sas.com   (919) 531-5637Cary, NC 27513

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

zorow - open source community for z/OSMF workflows

[Hiren Shah]

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 format. 
Workflow can be then automated or performed manually. z/OSMF workflow also 
supports faster on boarding of newer generation of system programmers. 

Recently Open Mainframe Project announced ‘Zorow’ (Z Open Respository Of 
Workflows) Project to help customers to collaborate with z/OSMF workflow. More 
information about zorow project can be found at following link. Please consider 
joining the community to learn about z/OSMF workflow and collaborate with each 
other. 
https://www.openmainframeproject.org/projects/zorow

Sign up to the Zorow email lists
User List:
https://lists.openmainframeproject.org/g/zorow-user/
Developer List:
https://lists.openmainframeproject.org/g/zorow-dev/

Join Slack channel.
https://slack.openmainframeproject.org
Channel: #zorow

View the code and contribute workflows
https://github.com/openmainframeproject/zorow
Contribution Guidelines at
https://github.com/openmainframeproject/zorow/blob/master/CONTRIBUTING.md

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Removal of Planning and Migration Assistant with z/OS V2.4

[Kurt Quackenbush]

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 FMIDs (We built some EXECs to send ++HOLD infos to the 
responsible colleagues, depending on the FMID. In these files also we print the 
FMID Description from BCNFMDS) and to create some handy reports about the 
installed software (with some additional infos like program number etc.) for a 
given CSI.

My question now is how to get this infos in future. Can anyone give us some 
hints?


You can use the View -> Products, Features, and FMIDs action for a 
software instance defined to z/OSMF Software Management instead of the 
PMA Products Applied report.  It contains the same information.


FMIDs and descriptions you can get from your CSI.  Try using the GIMAPI 
program interface to query SYSMOD entries from your target zones and 
return their DESCRIPTION subentries.


Kurt Quackenbush -- IBM, SMP/E Development
Chuck Norris never uses CHECK when he applies PTFs.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

TCPIP NETMONITOR Parm

[Dazzo, Matt]

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


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: PDS Member updating via COBOL Program

[Paul Gilmartin]

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 
>introduce its own set of problems, chief of which is the inability to share 
>the data set across sysplex boundaries. If that restriction is unacceptable, 
>you might try adding in your RYO enqueue program as you suggest. Be aware, 
>however, that DISP=SHR is unlikely to provide much if any protection against 
>concurrent update. 
> 
I have used ISPF LM services for this purpose.  But that requires a TSO
environment.  Otherwise, you may simulate the ISPF technique, as in:

https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.4.0/com.ibm.zos.v2r4.f54pc00/isppcmmnamen.htm

Whatever you do, all players must follow the same rules.  Any
nonconformists must be re-coded.

I have tested using LMPUT to write multiple members concurrently.
It works, but only within a single job because ISPF LMPUT reqiuires
ENQ EXC on the DSN.

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Mainframe environment on AWS

[ITschak Mugzach]

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 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:
> > http://www.redbooks.ibm.com/abstracts/sg248205.html?Open
> >
> > There is an option for using a remote license server. I haven't tried it
> > myself, but have read other people's reports that they have been
> > successful.
> >
> > I don't know whether the zD offering for non-ISVs supports a remote
> > license server. Here is the forum for that offering:
> >
> >
> >
> https://www.ibm.com/developerworks/community/forums/html/forum?id=----2283
>
>
> $5,070 per user per year. OUCH! And you supply the PC hardware running a
> supported Linux distro (or maybe any Linux).
>
>
>
> >
> >
> > --
> >
> > Regards, Gord Tomlin
> > Action Software International
> > (a division of Mazda Computer Corporation)
> > Tel: (905) 470-7113, Fax: (905) 470-6507
> > Support: https://actionsoftware.com/support/
> >
>
> --
> I find television very educational. The minute somebody turns it on, I go
> into the library and read a good book
> -- Groucho Marx
>
> Maranatha! <><
> John McKown
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>


-- 
ITschak Mugzach
*|** IronSphere Platform* *|* *Information Security Contiguous Monitoring
for Legacy **|  *

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Add space to OMVS filesystem?

[Charles Mills]

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

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: PDS Member updating via COBOL Program

[Tabari Alexander]

>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 PDSE
>open for output (to create or replace members), that PDSE can be opened on
>other systems only if the systems are using the PDSE extended sharing
>protocol. The storage administrator can establish PDSE extended sharing
>protocol by using the PDSESHARING keyword in the IGDSMS*xx* member of
>SYS1.PARMLIB as described in z/OS DFSMSdfp Storage Administration
>
>.

One thing that I might add here is that if JOBA is really updating the member, 
as in opening the member for UPDATE, the PDSE sharing capabilities are 
diminished as opening a member for UPDATE requires the system to have exclusive 
access to the data set even if extended sharing is enabled. With that being 
said, the PDSE can still be shared in this scenario within the same system.

---
Tabari Alexander

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: PDS Member updating via COBOL Program

[Tom Marchant]

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.  The dd associated with the parmlib uses DISP=SHR.
>
>I have "JOBB" that executes a COBOL program to do the same thing, but it is a 
>different member within the same dataset as "JOBA".It is coded
>to open the dataset as I/O.  After it reads the member, it then does a 
>REWRITE.It doesn't follow the rules as above and use the internal utility.
>The dd associated with the parmlib also uses DISP=SHR.
>
>Here is the issue.   Occasionally the member in "JOBA" is becoming "empty", 
>while the member in JOBB is always OK.I have looked at SMF
>records and I see these jobs run at the same time.  And it is usually the same 
>down to the hundreds of seconds.
>
>My suggestion was that JOBB needs to be fixed to use the "enqueue and dequeue" 
>utility, since it is using DISP-SHR.   This parmlib is
>used heavily and extensively by applications, and no way to get it DISP=OLD.  
>Any thoughts or explanation would truly be appreciated.

Your ENQ on DSNAME+member will not help you when the two jobs are updating a 
different member.

-- 
Tom Marchant

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: PDS Member updating via COBOL Program

[John McKown]

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 someone
> wrote years ago that puts an enqueue on the dataset and its member that it
> is updating.  The dd associated with the parmlib uses DISP=SHR.
>
> I have "JOBB" that executes a COBOL program to do the same thing, but it
> is a different member within the same dataset as "JOBA".It is coded
> to open the dataset as I/O.  After it reads the member, it then does a
> REWRITE.It doesn't follow the rules as above and use the internal
> utility.
> The dd associated with the parmlib also uses DISP=SHR.
>
> Here is the issue.   Occasionally the member in "JOBA" is becoming
> "empty", while the member in JOBB is always OK.I have looked at SMF
> records and I see these jobs run at the same time.  And it is usually the
> same down to the hundreds of seconds.
>
> My suggestion was that JOBB needs to be fixed to use the "enqueue and
> dequeue" utility, since it is using DISP-SHR.   This parmlib is
> used heavily and extensively by applications, and no way to get it
> DISP=OLD.  Any thoughts or explanation would truly be appreciated.
>
>
I agree. You should use the same ENQs as ISPF just for safety's sake. An
vague possibility, but not as good, is to convert from a PDS to a PDS/E.
ref:
https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.4.0/com.ibm.zos.v2r4.idad400/shr.htm

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 PDSE
open for output (to create or replace members), that PDSE can be opened on
other systems only if the systems are using the PDSE extended sharing
protocol. The storage administrator can establish PDSE extended sharing
protocol by using the PDSESHARING keyword in the IGDSMS*xx* member of
SYS1.PARMLIB as described in z/OS DFSMSdfp Storage Administration

.

-- 
I find television very educational. The minute somebody turns it on, I go
into the library and read a good book
-- Groucho Marx

Maranatha! <><
John McKown

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: PDS Member updating via COBOL Program

[Jesse 1 Robinson]

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 share the data set 
across sysplex boundaries. If that restriction is unacceptable, you might try 
adding in your RYO enqueue program as you suggest. Be aware, however, that 
DISP=SHR is unlikely to provide much if any protection against concurrent 
update. 

.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-543-6132 Office ⇐=== NEW
robin...@sce.com

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Pesce, Andy
Sent: Tuesday, October 8, 2019 9:16 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):PDS Member updating via COBOL Program

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 and its member that it is 
updating.  The dd associated with the parmlib uses DISP=SHR.

I have "JOBB" that executes a COBOL program to do the same thing, but it is a 
different member within the same dataset as "JOBA".It is coded
to open the dataset as I/O.  After it reads the member, it then does a REWRITE. 
   It doesn't follow the rules as above and use the internal utility.
The dd associated with the parmlib also uses DISP=SHR.

Here is the issue.   Occasionally the member in "JOBA" is becoming "empty", 
while the member in JOBB is always OK.I have looked at SMF
records and I see these jobs run at the same time.  And it is usually the same 
down to the hundreds of seconds.

My suggestion was that JOBB needs to be fixed to use the "enqueue and dequeue" 
utility, since it is using DISP-SHR.   This parmlib is
used heavily and extensively by applications, and no way to get it DISP=OLD.  
Any thoughts or explanation would truly be appreciated.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Mainframe environment on AWS

[John McKown]

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 ISV, have a look at Chapter 8 of the zPDT Redbook:
> http://www.redbooks.ibm.com/abstracts/sg248205.html?Open
>
> There is an option for using a remote license server. I haven't tried it
> myself, but have read other people's reports that they have been
> successful.
>
> I don't know whether the zD offering for non-ISVs supports a remote
> license server. Here is the forum for that offering:
>
>
> https://www.ibm.com/developerworks/community/forums/html/forum?id=----2283


$5,070 per user per year. OUCH! And you supply the PC hardware running a
supported Linux distro (or maybe any Linux).



>
>
> --
>
> Regards, Gord Tomlin
> Action Software International
> (a division of Mazda Computer Corporation)
> Tel: (905) 470-7113, Fax: (905) 470-6507
> Support: https://actionsoftware.com/support/
>

-- 
I find television very educational. The minute somebody turns it on, I go
into the library and read a good book
-- Groucho Marx

Maranatha! <><
John McKown

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

PDS Member updating via COBOL Program

[Pesce, Andy]

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 and its member that it is 
updating.  The dd associated with the parmlib uses DISP=SHR.

I have "JOBB" that executes a COBOL program to do the same thing, but it is a 
different member within the same dataset as "JOBA".It is coded
to open the dataset as I/O.  After it reads the member, it then does a REWRITE. 
   It doesn't follow the rules as above and use the internal utility.
The dd associated with the parmlib also uses DISP=SHR.

Here is the issue.   Occasionally the member in "JOBA" is becoming "empty", 
while the member in JOBB is always OK.I have looked at SMF
records and I see these jobs run at the same time.  And it is usually the same 
down to the hundreds of seconds.

My suggestion was that JOBB needs to be fixed to use the "enqueue and dequeue" 
utility, since it is using DISP-SHR.   This parmlib is
used heavily and extensively by applications, and no way to get it DISP=OLD.  
Any thoughts or explanation would truly be appreciated.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Mainframe environment on AWS

[Gord Tomlin]

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:
http://www.redbooks.ibm.com/abstracts/sg248205.html?Open

There is an option for using a remote license server. I haven't tried it 
myself, but have read other people's reports that they have been successful.


I don't know whether the zD offering for non-ISVs supports a remote 
license server. Here is the forum for that offering:


https://www.ibm.com/developerworks/community/forums/html/forum?id=----2283

--

Regards, Gord Tomlin
Action Software International
(a division of Mazda Computer Corporation)
Tel: (905) 470-7113, Fax: (905) 470-6507
Support: https://actionsoftware.com/support/

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Mainframe environment on AWS

[Farley, Peter x23353]

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, 2019 3:41 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Mainframe environment on AWS

EXTERNAL EMAIL

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
--


This message and any attachments are intended only for the use of the addressee 
and may contain information that is privileged and confidential. If the reader 
of the message is not the intended recipient or an authorized representative of 
the intended recipient, you are hereby notified that any dissemination of this 
communication is strictly prohibited. If you have received this communication 
in error, please notify us immediately by e-mail and delete the message and any 
attachments from your system.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: SMF exit IEFU086 work area size

[Charles Mills]

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 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?

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: SMF exit IEFU086 work area size

[David Crayford]

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 the length can be 
set/modified by the installation.

Larre
US Social Security Administration

"The opinions expressed in this e-mail are mine personally and do not necessarily 
reflect the opinion of the US Social Security Administration and/or the US 
Government."

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: SMF exit IEFU086 work area size

[Larre Shiller]

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 Administration

"The opinions expressed in this e-mail are mine personally and do not 
necessarily reflect the opinion of the US Social Security Administration and/or 
the US Government."

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: SMF exit IEFU086 work area size

[Lennie Dymoke-Bradshaw]

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 get? (Ans: Millions!)
Give up without a message? Not very useful at all.
Assuming this is a dynamic exit, you could issue a message and then deactivate 
the exit.

None of these is very satisfactory.

I suspect the length is always the same, but IBM reserve the right to increase 
it. 
Come on IBM. Give us the answer!

Lennie Dymoke-Bradshaw | Security Lead | RSM Partners Ltd  
Web:  www.rsmpartners.com
‘Dance like no one is watching. Encrypt like everyone is.’

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
David Crayford
Sent: 08 October 2019 14:22
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: [IBM-MAIN] SMF exit IEFU086 work area size

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, Lennie Dymoke-Bradshaw wrote:
> 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 give an indication of how much there 
> is. Without that one could be reduced to getting ones own work area .
>
> Can you dump out the parameter list to see what is passed? Can we have any 
> indication from IBM of a minimum size?
>
> Lennie Dymoke-Bradshaw | Security Lead | RSM Partners Ltd

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: SMF exit IEFU086 work area size

[David Crayford]

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, Lennie Dymoke-Bradshaw wrote:

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 give an indication of how much there 
is. Without that one could be reduced to getting ones own work area .

Can you dump out the parameter list to see what is passed? Can we have any 
indication from IBM of a minimum size?

Lennie Dymoke-Bradshaw | Security Lead | RSM Partners Ltd


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: SMF exit IEFU086 work area size

[Lennie Dymoke-Bradshaw]

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 give an indication of how much there 
is. Without that one could be reduced to getting ones own work area .

Can you dump out the parameter list to see what is passed? Can we have any 
indication from IBM of a minimum size?

Lennie Dymoke-Bradshaw | Security Lead | RSM Partners Ltd  

Web:  www.rsmpartners.com
‘Dance like no one is watching. Encrypt like everyone is.’

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
David Crayford
Sent: 08 October 2019 13:52
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [IBM-MAIN] SMF exit IEFU086 work area size

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?

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

SMF exit IEFU086 work area size

[David Crayford]

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?

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Mainframe environment on AWS

[Mike Schwab]

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
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN



-- 
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN