If this helps:
We run a parallel sysplex with sites at 16 - 18 km (2 separate routes with some
difference in distance) with active systems and CFs at both sites, without
problems.
Most Sync CF Requests to the Remote CFs are converted to Async.
To minimize the Async/Remote CF delays, we configure
>The problem is when a program is started from OMVS under a USERID and runs
>under a different name, which makes it difficult for someone to cancel the job
>or issue modify commands against it.
>The system keeps appending numerical values to the USERID and you have to do a
>DA userid* command to
You talk about 'speeds'. Just to make sure there is no confusion between
'speed' and 'capacity'. In any generation of Z system, the processor cycle
(speed) time is always the same. Taking a single CP system as an example. what
you have is different CAPACITY SETTINGs e.g. 401 or 501 or 601 or 701
Hi,
Please advise... where is this parameter updated?
IGW01011T THE FMH SIZE IS LESS THAN THE MINIMUM ALLOWED. LENGTH SUPPLIED = 0
, MINIMUM REQUIRED = 104
Examine the FMHLEN field in the passed FMH and determine the type of request.
Increase
A couple quick comments from me:
1. IBM eliminated Single Version Charge (SVC) time limits. If, for example,
you have an OS/VS COBOL application that's still lagging behind, you could
keep a CICS Transaction Server 2.3 AOR running it until you can get it
pulled forward, and surround that laggard A
If you have full speed processor then you can have ...more processors.
Let's not talk about models with all 170 processors activated and in use ;-)
However Len suggested the full speed processor can have some hidden
capacity. Well, maybe it has, but there is no evidence for such approach.
--
W dniu 2018-01-10 o 18:17, Edward Gould pisze:
On Jan 10, 2018, at 5:26 AM, R.S. wrote:
W dniu 2018-01-09 o 23:59, Mike Schwab pisze:
EAV volumes must be an exact multiple of 1,113 cylinders. Under 64K
volumes some storage devices allow multiple of 1,113 cylinders others
multiples of 1 cylind
J.O.Skip Robinson wrote:
>Losing XCF connection to a sysplex member would be a whole
>nother level of impact that I've never been willing to sign
>up for even though our network today is far more reliable
>than it was 20 years ago.
Isn't losing XCF connectivity something worth planning for? It's r
Has anyone done anything with passphrases beyond TSO?
Thanks in advance
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
John McKown wrote:
On Wed, Jan 10, 2018 at 11:19 AM, Thomas David Rivers
wrote:
In Systems/C , this is simply:
#include
#include
main()
{
printf("Job name is %s\n", __jobname());
}
That is a nice enhancement for the C language under z/OS. As a general
rule
I know about this field, which was disclosed under an NDA, so I'm not
at liberty to talk about it in public. I assume that neither are you.
So I suggest that a) you read that NDA you should have signed, and b)
read the manual. You've got a long way to go if you don't understand
this error.
sas
On Thu, Jan 11, 2018 at 1:44 AM, Peter Hunkeler wrote:
>
>
> >Userids have nothing to do with job names, in general. If a user logs
> into
> a UNIX shell, the UNIX process runs in a new STC whose name is based on the
> USERID plus 1 character (sort of "random"). I am _guessing_ that with an 8
>
It sounds like for z/VM at least, that any performance impact will be dependent
on the workload and "enablement settings".And application of these MCLs
without applying operating system software PTFs will not have an impact on
system performance. I would have to assume the z/OS PTFs will s
__jobname(), __stepname() etc are not documented in the
XL C/C++ Runtime Library Reference Version 2 Release 2 SC14
manual. Where are they documented?
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Thomas David Rivers
Sent: Thursda
On Thu, Jan 11, 2018 at 7:36 AM, Barkow, Eileen
wrote:
> __jobname(), __stepname() etc are not documented in the
> XL C/C++ Runtime Library Reference Version 2 Release 2 SC14
> manual. Where are they documented?
>
Those are part of the C run-time for the _Dignus_ C compiler, not the IBM
run-ti
We've tested them in TSO, CICS, and CA-Roscoe within our own group. Nothing
been rolled to the masses yet. We are also working on CA MFA as well.
_
Dave Jousma
Manager Mainframe Engineering, Assistant Vice President
david.jou...@5
I agree: from a practical perspective, unauthorized user code running on on a
typical z/OS system has many more practical barriers to being able to use the
side channel communication methods involved in Meltdown/Spectre. However,
"difficult" and "unlikely" doesn't mean "impossible". That's assum
File-AID/MVS has a Compare feature that will meet your requirements. And the
compare can be run "online" or in batch. There are a number of Compare
Criteria that can be used:
Use "S" to select member compare criteria:
S Module Name
_ Load Module Size
_ Entry Point
_ Link Attributes
_ Lin
> On Jan 11, 2018, at 6:44 AM, R.S. wrote:
>
> Ed:
> I am sure I had read that. Of course such promise can be broken in the future
> (why not?), but whole idea of so called mod-27, mod-54 and finally EAV was to
> extend volume size with no change to geometry.
>
> (speculation mode)
> IMHO the
One company had data centers in Miami and New Orleans. Miami shut
down for a hurricane, and wasn't back up before Katrina hit New
Orleans.
On Thu, Jan 11, 2018 at 6:44 AM, Timothy Sipples wrote:
> J.O.Skip Robinson wrote:
>>Losing XCF connection to a sysplex member would be a whole
>>nother leve
>Ah, you're right. It's when I execute a command from the shell that the
digit is added to the end of the "jobname". I.e. the shell itself runs
under "USERID", but when I do a "sleep 60s", the sleep command runs under
"USERID1" (for example).
Every command that the shell fork()s will run in a se
If you need the stepname the code I posted will work, assuming you reference
tiocjstn in the last line.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Barkow, Eileen
Sent: Thursday, January 11, 2018 5:36 AM
To: IBM-MAIN@LIS
In article <03a901d38ade$7d657410$78305c30$@stevebeaver.com> you wrote:
> Has anyone done anything with passphrases beyond TSO?
> Thanks in advance
We added support to SAS/Connect to use allow password phrases. This
was at version 9.4. I think we allowed mixed-case passwords either at
9.2 or 9.3.
Hi
Is anyone following a standard release calendar format for the Mainframe
activity in your shop ?
If so would you be willing.to share that template ?
Regards
Peter
--
For IBM-MAIN subscribe / signoff / archive access instruct
Good point. Thanks. The code in question is unlikely to run as an SRB, but
anything is possible in the future.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Peter Hunkeler
Sent: Wednesday, January 10, 2018 11:15 PM
To: IBM-M
I am not using a template. When fixes are available, we either install them on
a 6 month (sometimes) cycle.
Or if the fix is urgent, then schedule sooner.
A majority of our fixes are done without an IPL, so they are mostly dynamic.
Our change tickets detail the changes going in and what actio
Working for a outsourcer some years back, some of out clients dictated our
downtime schedule one year in advance, for the most part I always knew what
weekends or times to stay away from.
I scheduled maint based on a 6 month cycle most of the time, unless like
Lizette stated, there was a hyper
SFM and planning for what your surviving system should always be done. And
yes early on there was a failure of one of the two dark fiber connections
and the sysplex timers were not connected properly to allow for a continued
service.
Planning planning planning.
On Thu, Jan 11, 2018 at 10:22 AM M
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Rob Schramm
> Sent: Thursday, January 11, 2018 9:01 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: SYSPLEX distance
>
> SFM and planning for what your surviving system should alway
Message is documented publicly:
https://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos.v2r2.ieam900/m012363.htm
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Steve Smith
Sent: Thursday, January 11, 2018 5:21
> For example FBA world changed (actually came back *) the sector size which
> was 512B net for ages and
now it's commonly extended to 4096kB.
I think that should say 4KiB, not 4096KiB. 4MiB would seem to waste an awful
lot of storage.
--
Peter Hunkeler
-
Yeah, we put performance bonds on everything from pencil sharpeners to
bulldozers. In the past we were able to work out agreements with vendors. Some
scale, some fail some just pass it on. In a tort friendly state we usually at
least cover the cost of conversion.
In a message dated 1/11/2018 8
Is there an official statement from IBM regarding Meltdown and Spectre on
System z (or is it System Z)?
I saw that Red Hat and SuSE have stated that there is the exposure with Linux
on z.
Thank you
--
Lionel B. Dyck <
Main
ResourceLink, in the Security Alerts area. You have to be registered to get
into that area, separately from Resourcelink.
_
Dave Jousma
Manager Mainframe Engineering, Assistant Vice President
david.jou...@53.com
1830 East Paris, Gr
To clarify. We have *no* XCF connection between primary and backup data
centers. All DASD is mirrored continuously via XRC, but the DR LPARs are
'cold'. They get IPLed only on demand: for (frequent) testing and for
(godforbid) actual failover.
When got into serious DR in the 90s, channel techno
On Wed, 10 Jan 2018 15:26:04 -0600, Tom Marchant
wrote:
>On Wed, 10 Jan 2018 21:44:29 +0100, R.S. wrote:
>
>>BTW: It's worth to remember chances the vulnerability would really
>>compromise system security are really small. (IMHO)
>
>I agree. Especially since the method of exploiting it involves
W dniu 2018-01-11 o 19:20, Peter Hunkeler pisze:
For example FBA world changed (actually came back *) the sector size which was
512B net for ages and
now it's commonly extended to 4096kB.
I think that should say 4KiB, not 4096KiB. 4MiB would seem to waste an awful
lot of storage.
OK, OK,
W dniu 2018-01-11 o 23:03, Walt Farrell pisze:
On Wed, 10 Jan 2018 15:26:04 -0600, Tom Marchant
wrote:
On Wed, 10 Jan 2018 21:44:29 +0100, R.S. wrote:
BTW: It's worth to remember chances the vulnerability would really
compromise system security are really small. (IMHO)
I agree. Especially
Please follow the standard operating procedures that have been in place for
years. If you haven't done so yet, here they are:
1. Visit here:
https://www.ibm.com/it-infrastructure/z/capabilities/system-integrity
2. Scroll down to "IBM Security Portal."
3. Follow the "To Register" instructions.
39 matches
Mail list logo
