INFO IBM-MAIN
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
On Thu, 14 Sep 2017 21:53:47 -0400, Joseph Reichman wrote:
>
>Don't know if this doable but I would snap dump data to a pds
>
>Looking at the snap dump DCB macros DSORG=PS,MACRF=W
>
>That would lead me to think I would have to use (if this doable) RDJFCB and
>move the member name in
>
>BSAM has a
Hi
Don't know if this doable but I would snap dump data to a pds
Looking at the snap dump DCB macros DSORG=PS,MACRF=W
That would lead me to think I would have to use (if this doable) RDJFCB and
move the member name in
BSAM has a exlst parameter and I use X'07' to get the JFCB area
Phil Smith wrote:
All good questions, and obviously you pushed some of my favorite buttons! I'll
stop now :)
Great notes Phil. Thanks!
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to
John McKown wrote:
IMO, encrypting data is a very good defense. Another good defense is
hiring competent people rather than inexpensive people and giving them the
time to design, code, and test their solutions. I don't have statistics,
but many attacks are based on coding errors such as the
On Thu, 14 Sep 2017 13:16:58 -0500, Giliad Wilf wrote:
>Yes, but no PDSE may be listed in LPALSTxx, and since LPALSTxx
>must list SYS1.LPALIB, it can't be a PDSE.
It is true that SYS1.LPALIB cannot be a PDSE, but who cares?
It isn't important. MVS has long had a mechanism to include
program
On 9/14/2017 9:53 AM, Paul Gilmartin wrote:
On Thu, 14 Sep 2017 11:17:38 -0500, Steve Beaver wrote:
You're talking it's about a change that is possible but it would be such a
shock to people from what they know he's probably going to get fired for that
one
I wonder if Ed Jaffe knows of
Depending on the one-jobname restriction was indeed a 'convenient' method of
serialization--but a method fraught with peril. Along with the one-jobname
restriction a shop would also need to run with only one internal reader because
if more than one, it's unpredictable which of two like-named
An increase in ECSA could shrink the 31 bit private area. Depending on that
shrinkage would could have issues with jobs looking for 31 bit private. You
should try to determine your 31 bit private area usage/needs before increasing
the ECSA.
I agree you should double check what is using the
210M or more.
On Thu, Sep 14, 2017 at 2:35 PM, Nai, Dean wrote:
> Hi,
>
> We have been getting messages from health checker about ECSA at 84%. We
> added another DB2 so that probably pushed us over 80%. Currently we have it
> set at CSA=(2M,200M). Any suggestions on
We have our set to CSA=(2400,320M). However, you need to review what CSA is
being used, because it is allocated on the 1M boundary. But, for ECSA, you
should have any problems increasing it without any issues.
Jerry Edgington
11450 Grooms Road | Cincinnati, Ohio 45242
Hi,
We have been getting messages from health checker about ECSA at 84%. We added
another DB2 so that probably pushed us over 80%. Currently we have it set at
CSA=(2M,200M). Any suggestions on increasing it?
Dean Nai
Senior z/OS Systems Programmer
Mainframe Technical Support Group
Yes, but no PDSE may be listed in LPALSTxx, and since LPALSTxx must list
SYS1.LPALIB, it can't be a PDSE.
On Thu, 14 Sep 2017 07:13:38 -0500, Tom Marchant
wrote:
>On Thu, 14 Sep 2017 13:02:54 +0200, Peter Hunkeler wrote:
>
>>The LPA is built as part of the IPL
Curtis G. Pew wrote:
>When I gave a presentation about encryption to our programmers a few years
>back, one thing I said was "Encryption never solves your problem. Instead, it
>transforms your problem into a different problem, which may be easier to
>solve." (I was thinking specifically about
I believe that this is possible by associating the "modified" line with
the particular NJE node.
We do something like the following:
Code the desired LINE parameters in the JES2 Initialization Parameters:
LINE(xx)JRNUM=1,JTNUM=1,SRNUM=1,STNUM=1,UNIT=SNA
On Thu, 14 Sep 2017 11:17:38 -0500, Steve Beaver wrote:
>You're talking it's about a change that is possible but it would be such a
>shock to people from what they know he's probably going to get fired for that
>one
>
I wonder if Ed Jaffe knows of anyone who got fired?
It feels as if Steve is
Steve,
I took your prior comment to mean it *IS NOT* possible, period.
IBM has supported allowing duplicate batch jobs to run for many years now.
I did not say you should. I did say you could.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
On Sep 14, 2017, at 10:43 AM, John McKown wrote:
>
> IMO, encrypting data is a very good defense. Another good defense is
> hiring competent people rather than inexpensive people and giving them the
> time to design, code, and test their solutions. I don't have
You're talking it's about a change that is possible but it would be such a
shock to people from what they know he's probably going to get fired for that
one
Sent from my iPhone
Sorry for any grammar problems
> On Sep 14, 2017, at 11:11, Allan Staller wrote:
>
> That
Dear list:
I'd like to know if there is a way to configure a line (Lx.ST1) to select
different sizes of sysouts (size in terms of lines) when starting a connection.
I know that after a connection have been stablished, you can change the options
LIMIT and WS on order to have the following:
That is no longer true. There is an option to run duplicate batch as of z/OS
2.1(?).
Might be earlier.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Steve Beaver
Sent: Thursday, September 14, 2017 10:23 AM
To:
Just FYI...
Equifax hack preventable with patch
http://thehill.com/policy/cybersecurity/350616-equifax-hack-due-to-patchable-security-flaw
On Thu, Sep 14, 2017 at 11:44 AM John McKown
wrote:
> On Thu, Sep 14, 2017 at 10:31 AM, Jesse 1 Robinson <
>
I think it is not documented, but must exits.
You can use IRXFLOC, an empty one in LINKLIB.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO
On Thu, Sep 14, 2017 at 10:31 AM, Jesse 1 Robinson
wrote:
> Thanks for the Draco education. ;-)
>
> One point I failed to mention is the question of why US companies should
> be overwrought by an EU regulation. This is still in the 'opinion' stage,
> but it was pointed
On 9/14/2017 8:22 AM, Steve Beaver wrote:
The SYSTEM will NEVER allow you to run 2 or more batch jobs with the same name.
That lock/prohibition has been
There since JES was written. It been a convenient way to single thread
multiple jobs with the same name.
That restriction was lifted over
Thanks for the Draco education. ;-)
One point I failed to mention is the question of why US companies should be
overwrought by an EU regulation. This is still in the 'opinion' stage, but it
was pointed out at SHARE that the data breach penalty is intended to protect EU
citizens--wherever they
The SYSTEM will NEVER allow you to run 2 or more batch jobs with the same name.
That lock/prohibition has been
There since JES was written. It been a convenient way to single thread
multiple jobs with the same name.
That being said you can have MULTIPLE STC's with the same name but you best
Thanks Barry
Steve
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Barry Merrill
Sent: Wednesday, September 13, 2017 3:05 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: DB2
It's not exactly what you asked for, but this 1995
In our case, we use Connect:Direct between LPARs and one of the functions
people use is the RUN TASK to tell CA7 to release a job on the receiving
end. Since they are calling the same job name (CDC7NDMT) that is run to
tell CA7 this, along with the job details, if there a whole bunch of
transfers
There is. It is documented in the JES2 INIT and TUNING. Go to www.ibm.com and
search on JES2 DUPLICATE JOBS
However, what problem are you trying to solve?
When you switch this on - it will be an way of running that JES2 supports but
it is not normal for JES2. It was setup with serial
There is.
sas
On Thu, Sep 14, 2017 at 9:28 AM, Mark Regan wrote:
> Just asking if there is a way.
>
> --
>
> Regards,
>
> Mark T. Regan
>
> --
> For IBM-MAIN subscribe / signoff / archive access
Just asking if there is a way.
--
Regards,
Mark T. Regan
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Clark Morris wrote:
>In looking at the news, I'm wondering if encryption would have
>prevented any of the known data breaches. I'm thinking of Equifax,
>Anthem, Target and Yahoo for starters.
The Anthem breach was the result of a phishing attack, and an internal machine
was compromised. At that
On Thu, 14 Sep 2017 13:02:54 +0200, Peter Hunkeler wrote:
>The LPA is built as part of the IPL process, but only load modules
>not programs objects can be loaded into PLA at that time because
>program objects live in PDS/Es.
The LPA statement in PROGxx is processed at the end of IPL.
PDSEs can
"Breach" comes doen from middle English, and it didn't originally mean
"hack into a computer system and steal data". Peter's take is that an
unauthorized part broke through at least one layer of defense, and
that is certainly something to be concerned about. And I'd call that
at least a
As Chris B wrote, "not happening".
You would not only have to relocate any intra-module adcons, but resolve
any extra-module v-cons.
For completeness you would have to rebuild the control structures used for
NUCLKUP.
None of that is supported in any way.
Adding the module as page-fixed to
>> In my opinion PDSE design wasn't and still isn't ready for prime time.
>> It couldn't and still can't handle SYS1.NUCLEUS and SYS1.LPALIB because it
depends on a started task.
>
>Kind of an arbitrary standard, isn't it? I could argue VSAM or DB2 are not
>ready for prime time because you can't
>It's possible I got confused. So what is a Scheduler Address Space, as
opposed to the MASTER Scheduler Address Space?
Martin, the former's jobname is IEFSCHAS, the latter's is *MASTER*. Two
different address spaces.
--
Peter Hunkeler
Thanks, Rob, much appreciated.
-- Peter Hunkeler
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
I don't have access to any source materials, however it could be that IEFSCHAS
only purpose in life is to manage cross-system ENF signals.
Message IEFE002I with reason "IEFSCHAS ADDRESS SPACE UNAVAILABLE" indicates
that the following items are impacted :
(i) The system will not notify other
It's possible I got confused. So what is a Scheduler Address Space, as
opposed to the MASTER Scheduler Address Space?
Thanks, Martin
Martin Packer,
zChampion, Principal Systems Investigator,
Worldwide Cloud & Systems Performance, IBM
+44-7802-245-584
email: martin_pac...@uk.ibm.com
Twitter /
> On Sep 14, 2017, at 12:13 AM, Peter Hunkeler wrote:
>
>
>
>> Long time ago and when MVS first came out, we used to do this quite often
>> (once a week). A product we had called DUO (DOS under MVS). DUO maintained a
>> table in the nucleus for which dos jobs were running. They
42 matches
Mail list logo