Hi,
IBM introduced the concept of JES2 step-level restart in z/OS 1.13 and we're
interested in that function. However, this enhancement requires JES2
journalling, which we don't use.
I'm interested in any feedback those of you who do use journalling can provide.
I'm particularly concerned
/LIBDEF
but (1
it's not compatible with our existing infrastructure, (2 it's going to require
coding exec's
for each of our vendor and internal products and (3 it won't provide the
performance
benefits of TRX.
Thanks,
Dennis Schaffer
.
We've turned on MEMSTALLTIME this weekend and installed AM01403. We've
noticed no ill effects from either, though its still early. I'd recommend
MQ v7 users consider installing AM01403 and XCF users implement
MEMSTALLTIME.
Please let me know if you have any questions.
Thanks,
Dennis Schaffer
Claude,
Thanks. DSNTYPE=LARGE is exactly what I needed.
Skip and Sam, thanks for your input, too. I'm going to give the 3390-27 a try,
on at least on my largest system. I'm hoping to replace 64 3390-3s.
Thanks,
Dennis
--
so
with 3390-9? Has anyone done so with 3390-27? Have you experienced any
performance problems w/ 3390-27?
Thanks,
Dennis Schaffer
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL
into the category of
OPERCMDS.JES2.UNKNOWN.
Or possibly, a JES2 Exit36 (Pre-Security Authorization) is required.
Has anyone done this? Will OPERCMDS.JES2.UNKOWN secure $ADDEXIT/
$REPEXIT? Or is Exit36 required?
Thanks in advance for your responses.
Dennis Schaffer
Bill,
The link to which you pointed was a SASware 2006 ballot, whose results
were announced at SUGI in March.
The results were that the port SAS to Linux on the mainframe issue
received 73 votes, ranking it as the 92nd most popular issue overall, out
of 184 items, exactly 50%. Its not likely
7 matches
Mail list logo
