Reading system requirements for WebSphere MQ for z/OS versions 7.0.0, 7.0.1,
and 7.1.0, I could see that the minimal level for installing versions 7.0.0 and
7.0.1 is z/OS V1R8, while the minimal level for installing version 7.1.0 is
z/OS V1R11.
Due to an attempt to bridge the gap over SVC
There is a statement including more than one MAS in a sysplex is not
recommended on chapter 3.2.1.1 Group Names and Members for MVS Components and
Subsystems in the Setting Up a Sysplex manual.
This new parameter, USE_XCFGRPNM, is meant to help you set two or more
separate, distinct MAS
On Wed, 29 Jun 2011 12:07:01 +0300, #1490;#1491;#1497; amp;#1489;#1503;
#1488;#1489;#1497; gad...@malam.com wrote:
Hi,
I would like to install Java 64bit v6.0.1
I am running z/Os 1.11
The Program directory says that UA16880 is a prerequisite, but it looks to me
that it this PTF is for VTAM in
On Wed, 29 Jun 2011 12:59:23 +0300, #1490;#1491;#1497; amp;#1489;#1503;
#1488;#1489;#1497; gad...@malam.com wrote:
I know, but the PTF doesn't make sense.
I tried downloading it using SMP/E RECEIVE ORDER and got a message saying
NO APPLICABLE ++VER
Gadi
Sorry. Maybe it is a doc error (PTF
On Fri, 24 Jun 2011 12:24:13 +0530, sourabh khandelwal
sourabhkhandelwal...@gmail.com wrote:
Hello,
I was applying RSU on one of our z/OS system but during apply
process I received D37-04 abend for below datasets.
1) DIT.V1R3M0.SDITMOD1
2) SYS1.NUCLEUS
3) SYS1.SIOALMOD
.
.
.
2) I had
On Fri, 24 Jun 2011 13:24:37 +0530, sourabh khandelwal
sourabhkhandelwal...@gmail.com wrote:
Hello,
1) DIT.V1R3M0.SDITMOD1 -- This dataset is being used by LLA and XCFAS
2) SYS1.NUCLEUS -- Now its not being used by anybody.
3) SYS1.SIOALMOD -- LLA and XCFAS.
I think I will have have to
On Thu, 23 Jun 2011 13:00:46 -0500, Chip Grantham
cgrant...@ameritas.com wrote:
I've found the answer to my dilemma for compiler options from a COBOL load
module. They call them signature bytes. So now I'm looking for a VS
COBOL II V1.x programmer's guide, specifically the pages on signature
On Wed, 22 Jun 2011 12:36:13 -0500, Daniel Rose dan.r...@parker.com
wrote:
I had a COBOL programmer ask me how they could get the LPAR name,
SYSNAME,
or SMFSID from a COBOL program. I could not find a LE Function that would
do that. So, a co-worker located a sample program that chases
On Thu, 23 Jun 2011 07:02:22 +, Linda Mooney
linda.lst...@comcast.net wrote:
Hi Lizette,
I could browse some of the members, but not all. Could not copy to another
dataset - tried IEBCOPY, CA-Disk (backup, compress, archive), FDR (FDRDSF)
and was not able to get the dataset copied.Â
On Fri, 27 May 2011 07:02:30 -0500, Bill Neiman nei...@us.ibm.com wrote:
XCF does not use any of the interfaces that establish a reserve on a
device - not ENQ / RESERVE in any of its external implementations, nor the
Device Reserve (B4) command.
The reference to device-level serialization
On Wed, 25 May 2011 07:04:04 -0500, Bill Neiman nei...@us.ibm.com
wrote:
...
XCF uses several types of serialization to protect couple data sets.
But to clear up one misconception right away: Hardware reserves are
*NEVER*
used to serialize couple data sets.
...
Thank you Bill.
One last
Hi All,
We are trying to figure out how do XCF couple datasets get serialized in a
sysplex.
We can see there is a SYSDSN shared SYSTEM(*) ENQs on each sysplex
member system, but seems this is only the result of XCFAS doing dynamic
allocation for them when the system is being IPLed.
So,
On Tue, 24 May 2011 13:26:45 +0200, R.S.
r.skoru...@bremultibank.com.pl wrote:
Just to complement Barbara's excellent anwser:
One of the reasons why CDS datasets should reside on separate volumes is
hardware RESERVE. It is used for CDSes, at least in some situations.
--
Radoslaw Skorupka
Lodz,
suggestions and requests, to the extent of writing additional code
for incorporating them into the product.
In short: The product is excellent, and the support is excellent.
Giliad Wilf
Systems - z/OS Technical Support
iteam, a Mizrahi-Tefahot group member
15 Lincoln, 67134 Tel-Aviv, Israel
ph
We are trying to target cases where a COBOL program goes production but is
still
riddled with lots of active DISPLAY(*) statements left from its debugging period
Examining the output of such a program, one can see millions of records written
to a DD
named SYSOUT (COBOL's default)
We want to
Hi All,
In the days of VS COBOL II R4 we had three wonderful manuals that helped us
wade through
dumps:
LY27-9522 VS COBOL II Release 4 Diagnosis Reference
LY27-9523 VS COBOL II Release 4 Diagnosis Guide
SC26-4049 VS COBOL II Release 4 Application Programming Dubugging
Now that we use
Hi All,
We're a shop running z/OS V1R6 and z/OS V1R7, looking into migration to z/OS
V1R9
Migration manuals for z/OS V1R9 say nothing about supported migration paths for
safely
going from z/OS V1R6 to z/OS V1R9 and insuring safe fallback in case backing
out is
required (maybe IBM is only
17 matches
Mail list logo
