The only thing that has changed is the wording, before 2.3 (i.e. 2.2) it stated:
The IEASYSxx LFAREA parameter specifies the amount of real storage to be made
available for 1 MB and 2 GB large pages.
after 2.3 (i.e. 2.3 and 2.4) it now says:
The IEASYSxx LFAREA parameter specifies the maximum a
On Sat, 27 Mar 2021 00:01:36 +, Farley, Peter x23353 wrote:
>Then they really ought to donate it to the open source community (CBT?) and
>let the community upgrade it should they choose to do so.
>
>Laziness or "resource constraints" are no good excuse. If IBM don’t think
>they can make mon
Then they really ought to donate it to the open source community (CBT?) and let
the community upgrade it should they choose to do so.
Laziness or "resource constraints" are no good excuse. If IBM don’t think they
can make money from it, they should donate it and take the tax deduction (if
the
The stated reason for dropping WSA is that it uses an unsecured connection
and IBM doesn’t want to upgrade it.
On Fri, Mar 26, 2021 at 06:28 Radoslaw Skorupka
wrote:
> W dniu 25.03.2021 o 23:14, Paul Gilmartin pisze:
> > On Thu, 25 Mar 2021 14:33:34 -0700, Ed Jaffe wrote:
> >
> >> On 3/25/2021 2
I don't know about your experience, but the industry in which I work in has
some legal and some client-initiated retention rules that require retaining
records for as long as 7 calendar years, so we have GDG's for all such
"permanent" files and can usually go back to select appropriate data to
There are both legal and operational issues with programmer access to live
data, e.g., HIPPA, ENQ.
Further, once you have successfully reproduced a bug, best practice requires
that the corrected code produce the correct answer with the data that the
previous version failed on. Doing so requires
Your interpretation of QWHSRN is correct. It is the same place and format
through all recent and current versions AFAIK.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Pierre Fichaud
Sent: Friday, March 26, 2021 1:22 PM
To:
According to the documentation, after z/OS 2.3 the LFAREA parameter no longer
reserves real memory for large frames at IPL. Instead, it's a limit on the
number of fixed 1M frames.
Since it's now a limit is there any harm in leaving LFAREA too high as long as
you keep an eye on large fixed fram
Given an SMF record for DB2 (100-102), I'd like to find the DB2 version/release.
In the product section, I see QWHSRN and QWHSSUBV.
The first is the release "indicator number" in hex.
The second is the "subversion for the base release".
I downloaded SMF 9.1 data from IBM's secure site. That's what
Hello,
In past when we used CA-TLMS we have CA-COPYCAT utility that help in tape
duplication among other things.
Control-M/Tape has something similar to CA-Copycat?
Thanks
Carlos Bodra
IBM zEnterprise Certified
São Paulo SP Brazil
---
Bill our DB2 guy installed all of the Omegamon products, now that we're moving
to BMC MV for Z,CICS,DB2 and MQ, he will be installing the suite of tools for
the site, for us it just makes sense
Carmen Vitullo
-Original Message-
From: Bill
To: IBM-MAIN
Date: Friday, 26 Marc
We use BMC Mainview for z/OS, CICS, DB2 and Performance Reporter for DB2. These
related but separate products that BMC put under one SMPe FMID.
The issue we have is that one person does the z/os, cics part and I do the DB2
part. And this causes us to step on each other in terms of maintenance. Wh
At the IRS we are given courses in UNAX ( unauthorized access) for those who
have access to production data to be very careful
Making a mistake can lead to anywhere from loss of job to possible Jail
> On Mar 26, 2021, at 1:47 PM, Farley, Peter x23353
> <031df298a9da-dmarc-requ...@listserv
Jeremy,
I have to disagree with you here about access to read (not modify) production
data by application developers. Full read access to production data
(especially when the quantities are very large and cannot easily be copied to
"test" disk pools which are usually much smaller than producti
You are welcome Joe!
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Joseph Reichman
Sent: Friday, March 26, 2021 12:00 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Dataset contention
[External Email. Exercise caution when clicking links or opening attachments.]
Ric
On Fri, 26 Mar 2021 15:17:06 +, Jeremy Nicoll wrote:
>On Fri, 26 Mar 2021, at 14:06, Joseph Reichman wrote:
>> I open the file extend
>What?
Perhaps Python jargon. "append"? "DISP=MOD"?
>...
>> number of files on the off chance that 2 jobs write to the duke
>Duke?
Duplicate?
>Surely yo
Richard was the one who resolved by problem I allocated the datasets in rexx
and did a submit
The contention was between the batch jobs and my TSO session IKJEFT01
When I did the FREE FI problem was resolved
Thank you Richard
> On Mar 26, 2021, at 11:18 AM, Jeremy Nicoll
> wrote:
>
>
On Fri, 26 Mar 2021, at 14:06, Joseph Reichman wrote:
> I open the file extend
What?
> I have been tasked with finding data there are
> certain cases that are not easily found so I have to search a large
> number of files on the off chance that 2 jobs write to the duke
Duke?
You seem to have
I open the file extend I have been tasked with finding data there are certain
cases that are not easily found so I have to search a large number of files on
the off chance that 2 jobs write to the duke if it’s corrupted I can run it
again it won’t happen and like I said it’s not production if i
On Fri, 26 Mar 2021 09:21:59 -0400, Joseph Reichman wrote:
>The chances of two jobs writing to the file are slim and none I am searching
>a large number of files because I cannot find the data
>
https://en.wikipedia.org/wiki/Murphy%27s_law
> And most importantly it is NOT a production job
>
It
The chances of two jobs writing to the file are slim and none I am searching
a large number of files because I cannot find the data
And most importantly it is NOT a production job
thanks
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Jeremy Nicoll
Sent: Friday, Ma
On Fri, 26 Mar 2021, at 12:38, Joseph Reichman wrote:
> The output file is shared among multiple jobs whenever I get
> an equal condition I open put and close
That won't work if two jobs simultaneously try to write to the file.
You might not destroy the file, but you will lose the information
This abend is not about a separate started task that uses LXRES in its
creation of an XM environment, and then subsequent jobs or started tasks
"connect".
The description for this abend is this: LXRES is issued but a
cross-memory-resource-owning jobstep task has already terminated in the
home
It seems long past time that we could document:
-- you may assume that run-length-encoding is available
-- you may assume that that approach requires no workarea.
Thus (especially once documented) there is no need to use CSRCESRV
SERVICE=QUERY.
Should some alternate algorithm be implemented, it
Richard
Thank you I see 2 jobs running now without contention messages
> On Mar 26, 2021, at 8:38 AM, Joseph Reichman wrote:
>
> I am doing a file search over 2000 files looking for specfic data since
> there are so
> Many files I broke them up in to multiple
> Jobs
> The rexx exec call
I am doing a file search over 2000 files looking for specfic data since there
are so
Many files I broke them up in to multiple
Jobs
The rexx exec calls the catalog search program IGGCSI00 for the input files
They are VB files
The output file is shared among multiple jobs whenever I get an equ
On Fri, 26 Mar 2021, at 12:07, Joseph Reichman wrote:
> I have a dataset that is allocated to multiple jobs but with a disp=shr
>
> And I am getting contention messages MIM1039I I was always under the
> impression
> That if the dataset was allocated with disp=shr
> It could be used among multipl
Thanks
I create the file from a Rexx exec and do a TSO submit maybe before the submit
I’ll do I free that might me be it
Let me give it a try
> On Mar 26, 2021, at 8:14 AM, PINION, RICHARD W.
> wrote:
>
> Do you know if the dataset is being held by something other than your
> batch jobs,
Do you know if the dataset is being held by something other than your
batch jobs, with DISP=OLD? You should be able to use the ISPF DDLIST
command to find out who is holding the enqueue.
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Joseph Reichman
Sent: Friday, Ma
Hi
I have a dataset that is allocated to multiple jobs but with a disp=shr
And I am getting contention messages MIM1039I I was always under the impression
That if the dataset was allocated with disp=shr
It could be used among multiple jobs
Without problems
Thanks
--
W dniu 25.03.2021 o 23:14, Paul Gilmartin pisze:
On Thu, 25 Mar 2021 14:33:34 -0700, Ed Jaffe wrote:
On 3/25/2021 2:22 PM, Don Leahy wrote:
WSA is another possibility. It is part of ISPF (for now), so should be
available to all. Once you have wsa.exe running on your desktop you can
set u
Gary
From the description of the abend, if your user code runs as a jobstep in
something like a JES initiator, you will always be at risk from a prior batch
job performing an LXRES for PC-ss (without an initiator restart).
Admittedly this is rare as LXRES-issuing code normally runs as a started
32 matches
Mail list logo
