On Tue, 17 Oct 2023 12:03:37 +, Peter Relson wrote:
>Joe R wrote
>
>Trying to access via assembler storage access jesssct I got a RC 4
>
>
>Why is this a surprise? You didn't ask for the dump to include CSA; it didn't.
Joe never said what problem he wants to resolve. Since he already knew
On Wed, 18 Oct 2023 08:45:52 +1300, Laurence Chiu wrote:
>That is exactly the situation, The second LPAR will be on the same CEC as
>the first, share OSA adapters and be in a sysplex with XCF being the
>mechanism to share the VIPA information.
Since I've never seen an OSA, I must assume that
I just tried on three z/OS 2.5 systems and four 2.4 systems and it seems to be
working correctly. It only seems to say task busy when it should, i.e I have
terminated the task but it's not completely down yet.
Also our SyzEMAIL/z task allows me to change from accepting modifies to not
If the VIPA is set correctly, then the data can dynamically move between the
two LPARs so the workload is balanced across the two LPAR servers. I did that
with MQ and shared queues. Messages rotated between the two MQ managers and if
one system went down, the other system continued to handle
That is exactly the situation, The second LPAR will be on the same CEC as
the first, share OSA adapters and be in a sysplex with XCF being the
mechanism to share the VIPA information. From my reading of the docs, when
the server application on the primary LPAR is shutdown, and an incoming
I don't recall this happening until relatively recent z/OS versions. Not sure
when it began.
Program code, Assembler, has not been modified for ages.
Happens even when a single MODIFY command is issued even way after the program
initialized and is waiting for commands. In any case, the modify
isnt it possible to go
too far
in enforcing the rules ?
perhaps the rules should allow for a reasonable
amount of side discussion as might happen in
an office ?
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Darren Evans-Young
Sent: Monday, October 09, 2023
In addition to everything Jon has stated a few other questions may help figure
out what needs to be done, or not done.
Are both LPARS on the same CEC?
If both LPARS are on the same CEC, do they share OSA's?
Are the IP addresses you plan to use as VIPA's in the same subnet as the OSA's
IP
Joe R wrote
Trying to access via assembler storage access jesssct I got a RC 4
Why is this a surprise? You didn't ask for the dump to include CSA; it didn't.
However the RTCT bit settings for storage dumped were the same as the first
Isn't that in line with what I had written?
You had not
Another tip: If, like me, you are really bad at memorizing the IPCS command
syntax, you can write a small REXX which uses "address IPCS" to run all those
commands which you found useful. If you redirect the output into a PO dataset
(one member per command) you can then look through these
On Tue, 17 Oct 2023 16:00:56 +1300, Laurence Chiu wrote:
>We have one LPAR with static IP
You are saying:
LPAR 1 has static IP address 192.168.40.70
LPAR 2 has static IP address 192.168.40.71
> and a server on that LPAR
"on that LPAR" is wrong. You actually mean:
You have a server
11 matches
Mail list logo
