dispatcher doesn't need to check the shared CPs
that are only activated.
Case (2) will probably be as good as case(1). Simply deactivating them will get
lpar to redistribute those resources.
Barbara Nitz
--
For IBM-MAIN
. That
also means that the SFM intervals get computed automatically and can be
displayed with a D XCF command.
I believe there is an XCF health check that tells you you did right if you
didn't specify anything.
Barbara Nitz
What's this? Do my eyes deceive me? Barbara singing the praises of a health
check - any
health check? :-) (just kidding!!)
Well, must have been one of the few that I didn't delete. On the other hand,
one couldn't help but notice the D XCF,CPL output has become even larger on
1.12. When
and have done it themselves,
without consideration for other departments/applications, much less for the
overall picture.
Barbara Nitz
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists
since that message that might have caused the alternate dataset to be
temporarily unavailable?
Barbara Nitz
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu
Could having a logical processor to physical processor ratio of greater than
2 (e.g. 8 logicals in a 3 CP cec) be bad?
In my opinion, it depends on the box you're running on. We ran a z196 at a 4:1
ratio. The result was that up to 1.5% of all cpu consumed on that box across
all apars was
On one monoplex it also has RESOLVER, on another (which is a one-system sysplex
with a CF) the stepname changes from an in-house STC to APPC.
What they all seem to have in common is that the names appearing do not have a
JES id. That inhouse-STC gets me 'JCT unavailable' when I try to see the
So my current fundamental question is: what identifies an address space
besides the ASID?
The STOKEN is the only thing that uniquely identifies an address space for the
life of the IPL.
That is, I would have thought that ASID X'1234' meant the same address space,
whoever referred to it. An
This is probably a very basic JES3 question, but I have been unable to find an
answer both searching the internet and the JES3 books. Can somebody running
JES3 please tell me what the jobid for a TSO user looks like? In JES2 it would
be TSUx or T0xx. Same for a started task - in JES2
Thanks so much, Klaus! The things you've cited fit the note on the JES3 service
that I had found. I had gotten the impression that JES3 primarily uses job
numbers and that it is up to the product presenting information to get a jobid
and present it one way or another.
Barbara
Check: ASM_LOCAL_SLOT_USAGE
Adding more locals is always an option (again), my question was more on
experiences people have with locals on WebSphere LPARs. We're using quite
large locals (as big as the DASDs they are located on - 10k CYLS, one full
model 9 3390 DASD).
Does it make sense
For me,
the breakthrough here is that IBM is agreeing to license z/OS to ANYONE,
That's not how it works for us. An RDT system (and I have been maintaining
ours for almost two years now, but RDT has been around longer than that) has
licenced the z1090 code (RDT) and that code only. That's
Does the RDT license allow you to get updated ADCD images when they become
available? E.G., when an ADCD version is made available for z/OS 2.1, can
you load it on your RDT system?
Yes, you can. Having gone through that two times (migration 1.10 - 1.13 and
then moving 'the system' from
This will make things slightly easier (but only slightly) when upgrading in
the future. At the next upgrade, the S1CFG1 disk can be made part of the new
configuration, for the time it takes to complete the job. During that time,
the contents of libraries on S1CFG1 can be used as a source for
// SPACE=(TRK,(4000,0,0)),UNIT=3390,VOL=SER=TGT001
Somewhat irritatingly, IEBCOPY exhibits this behavior even when I specify
such as:
SPACE=(TRK,(4000,0)),DSNTYPE=LIBRARY
Exactly. Which lead me to (erroneously) conclude that it doesn't matter what
you specify for directory when
The ADCD release for RDT is currently running 6-9 months behind
the ADCD for PWD, primarily due to testing the Rational development
components for compatibility.
Which is a joke in itself, since the release of RDz we have been getting from
the ADCD system for *both* z/OS 1.10 and 1.13 has been
I can tell you the intent. Each allocation of above-2G storage fits into
one of 5 should I include it in the dump? categories --
- like region (default for private)
- like LSQA
- like CSA (default for common)
- like SQA
- do not dump automatically
The intent is to dump like x when 'x' is
For HVCOMMON, I would think that SDUMP should be turning on
the common storage bit in the dump record prefix, and IPCS should
be respecting that and allowing you to access the storage via any
ASID.
Big thanks (again) to Jim Mulder for looking at this. SDUMP does indeed
everything it should and
Tom,
>I'll be covering this in the Bit Bucket at SHARE in Atlanta. Thanks for
>giving me some more information about this. If you go to zTechU in
>Munich, I'm presenting there, so please look me up.
I had planned on it when I saw your name on the roster...
Barbara
I was kinda blind. The Exit command without DIAG shows both exits, it just
doesn't show them vertically.
Why are the LoadPt and ModLen for the IPL-loaded Exits not shown in either DYNX
or the DIAG output?
Barbara
>you're completely right, SYS.IEFUSI is a different *exitname* to
Rob,
you're completely right, SYS.IEFUSI is a different *exitname* to SYSTSO.IEFUSI.
That explains why I saw DYNX with only the default IEFUSI - I looked at the
wrong statement. Now I see that DYNX shows me two lines:
SYSTSO.IEFUSI 1 IEFUSITS YESYES 8E0A0EA8 0E0A0EA8 0158
>Since we do not use APPC, are type "AO" address spaces all UNIX process
>running in BPXAS initiator address spaces?
It appears so. I recently implemented OPERCMDS security for START/STOP
commands, and when a SAS User tries to kill his hanging process/thread/whatever
into USS, the CANCEL
> However, keep in mind that this is a statement about the CPU
>architecture, and not
>the I/O architecture. For example, zPDT does not support MIDAWs, which
>were
>introduced on the z9 machines.
And there are other hardware features that are NOT implemented, which I found
out the hard
>It specifically is LPA vs not.
Thanks Peter (and Rob). Also thanks for that DYNX panel - now we can see the
many exit that are silently established without traces in our parmlib... More
to check and cleanup.
Barbara
--
For
Last time I looked at PDSE performance was before PDSE V2. And I checked
specifically PDSEs with RECFM=VB. About 1 member in a 18000cyl PDSE
library. ISPF 3.4 took about 90 seconds. That time was spent on I/O (reponse
time about 4ms for each I/O). During that time about 1 I/Os were
My system came up with an old default IEFUSI exit. SYS.IEFUSI and SYSTSO.IEFUSI
are defined via SMFPRM. I need a new exit (IEFUSITS) for SYSTSO, so I did this:
SETPROG EXIT,ADD,EN=SYSTSO.IEFUSI,MODNAME=IEFUSITS,DSN=SYS1.LPALIB
CSV420I MODULE IEFUSITS HAS BEEN ADDED TO EXIT SYSTSO.IEFUSI
Using
>The minimum specs we were provided insist on a 2-CP solution, but when I
>pressed them, other than "commands took a long time", I received no
>valid reason why a single CP with sufficient memory would not be enough.
>Does anyone have experience with GDDR LPARs, specifically the CP
>requirement,
When we started working with our z13, IBM recommended to use the integrated
console(s) that are defined as HMCS to z/OS. So we put in the definition and
managed to IPL the first system in each sysplex with the HMCS console instead
of Operating System Messages console, which is hard to handle.
>The real question is whether dynamic _deletion_ and subsequent
>_replacement_ of a wrongly-defined IPL-time HMCS specification will
>work. On the surface it seems like it ought to work, but I think there's
>a reasonable chance it won't...
Well, it does. :-) The only surprise was that I had to
>I discussed this further with Jim Mulder. The z12, where I recently noticed
>the 'unassigned' value, introduced 2 GB pages, one of whose consequences is
>that LPAR boundaries are rounded up as needed to the nearest 2 GB boundary. If
>an image profile specifies any other value, the 'excess' is
>I feel that our system trace is a bit small, especially since we moved to z13.
>We currently have set them to 15M (per processor).
>What do others use?
We're still at 1M per processor (even on z13), but then there isn't much system
trace reading done here. If your central storage layout can
>I cannot remember exactly, but what happened was that in IMS the STOP REGION
>command was issued and the address space was not listed anymore in IMS
>(Display active showed it was gone).
>It was visible in JES but nothing could be done about it, it did neither
>accept cancel nor force.
Do you
>If you need help setting them up, send me an offline email and I can direct
>you through it. It will take you all of about 10 minutes to do the OSA
>changes and another 5 to generate the NIP OS consoles in your IODF.
Thanks Brian, we do have those consoles set up (someone else did it), and
Hi Tom,
>I found this forum post, which says you can have one HMCS console per
>z/OS image (WTW).
I have this in my (shared) CONSOLxx:
CONSOLE DEVNUM(HMCS) NAME(HMCS) AUTH(MASTER) ROUTCODE(ALL)
INTIDS(Y) LEVEL(ALL) UNKNIDS(Y)
I had assumed that this definition would
>> CONSOLE DEVNUM(HMCS) NAME(HMCS) AUTH(MASTER) ROUTCODE(ALL)
>> INTIDS(Y) LEVEL(ALL) UNKNIDS(Y)
>
>I've noticed SHARE and IBM Tech-U presentations full of the same silly
>example that can't possibly work. They recommend exactly what you have:
>CONSOLE DEVNUM(HMCS) NAME(HMCS) etc. which
>Have you seen this http://support.sas.com/kb/54/206.html
Chuck,
yes, we did. And we are at a higher maintenance level already. One of the
problems is that u1335 seems to occur in all kinds of problems, which is why I
want to see what it actually *means*.
Barbara
We are currently experiencing abend u1335 in SAS 9.4_m3 in different jobs. My
first step would be to determine what that user abend actually tells me - but I
cannot find the book containing the abend code meanings. Does anyone know what
book contains that information?
(We already have a
>We don't document internal abend codes as the vast majority will
>(hopefully) never be seen. They can change from release to release
>and even at a maintenance release. They're used when the program
>can't continue to run for some reason. Usually, they are accompanied
>by a message to the SAS
>a) I see a couple of FREEMAIN (SSRV 78) trace entries pointing to a TCB in
>read/write nucleus (TCB address is 00FDD4F8). Do these hold some useful
>information for me?
The only tcb I know of that actually, really is located in the R/W nucleus is
the first tcb in the *master* address space.
RDT systems being based on ADCD distributions I suggest to discard all current
JES definitions on that RDT system and cold start with a jes2parm similar to
this (you'll need to adjust data set names and volumes):
BUFDEF BELOWBUF=(LIMIT=100,WARN=80),
>I don't want to turn this into a debugging session, but this is what I see in
>RMF3 on the non-DB2 utility system.
>All of the TPX 'regions' are below this list sorted by Aux Slots. No task
>shows any page-ins.
Not sure that you haven't already done this: Use IPCS active on that system,
and
Hi Greg,
>A FORCE command becomes a CALLRTM TYPE=MEMTERM request which will drive
>address space level resource manager routines in the *MASTER* address
>space for the memterm'd address space. Ideally a resource manager
>routine should never need, or at least wait for, serialization of a
Apparently we ran into another of those PDSE latch contention bugs. While
terminating the holder of the latch, we had to force the batch job since cancel
had absolutely no effect.
We got messages
IEF743I INIT FORCED - CODE SA22 - IN ADDRESS SPACE 0040
IEF743I AUTO39P FORCED - CODE SA22 -
>But is it a valid data point? We use z/OSMF only insofar as we are forced to
>for IP configuration and upkeep. We did not use z/OSMF to install v2.2, and I
>don't know whether we'll use it to install v2.3. There is talk of it, but it
>seems to be largely motivated by the thought that we
A colleague of mine just asked me if ISPF statistics in a data set, especially
the USERID field, can be manipulated. We used ISPF 3.5 and we were both
astonished that I was easily able to fake a userid as the one who last changed
a member (testing in my own dataset, of course).
This
>Evidence of what Barb ? Don't hang anyone on this evidence. Anyone with
>update access to the pds can update this field..
My colleague asked me on Friday if it is possible to fake the ISPF Statistics.
I already knew that you can write them yourself using something other than
ISPF. So we tested
>soon after the system were up and verified, an incorrect policy0 was written
>into the CFRM data set, had the wrong serial number and wrong partion number
>for the CF LPAR.
>both systems have been IPL'd successfully multiple times since the install.
Not surprising. You must have activated the
>Weird one. Since IOEZPARM is saying 8K block, I'd try CISIZE(8192). If
>it still doesn't work, scheisse zeit.
Bingo. The collective wisdom of this group is great! With
CONTROLINTERVALSIZE(8192) I get the same problem as before, so I left it off
completely (as Peter suggested), and the ZFS
TSO BPXMTEXT EA0B0248
BPXMTEXT does not support reason code qualifier EA0B
That was the first thing I tried.
Barbara
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu
I am fighting with USS. Again.
I am installing HCR77C0 and am trying to get a ZFS formatted:
//ZFSALLOC EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSINDD *
>Would you mind, and do you have time to open a PMR? If zFS cannot cope with
>non-default CI size, it should say so clearly when asked to format a new
>cluster. At the very least, the 0248 reason code must be documented.
Amen.
But I really really really hate SR, so I really want to avoid
>I opened a hardware issue for this same reason and hardware support reported
>that MCL patches needed to be applied to the HMC. Those patches were recently
>put on but I haven't had a chance to be at the HMC during a sandbox IPL to
>verify if it is fixed.
When I first detected this last
Peter,
go into IPCS, option 3.5. Then put a t for takedump in front of the symptom
string. In the background, that will turn off DAE, set a marker and
re-establish DAE. Make sure that your ADYSETxx members are properly customized
and that you have ADYOPCMD in the authorized command section of
>I'm trying to use the new Java-less Operating System Messages console on
>the HMC. My version is Blippy McBlipperson, which makes it extremely
>difficult to use, because you can't watch it. As new messages are sent
>to the console, the display collapses and expands at least 10x/sec.
>Anybody
>For this one, though, since we built the download code into the dialog
>itself, we thought it safe to assume you had a copy of it already. So,
>we did not see the need to allow a first-time installation path for it.
> Since I wrote that design (quite some time ago), I have never heard
>anyone
I am using a different url to access pubcenter, and I get thrown back to the
initial page, too. Using IE (company mandated). Is that IBM's way of enforcing
the use of knowledge center?
Barbara
--
For IBM-MAIN subscribe /
>So, my question is, are there any repercussions changing to USEZOSV1R9RULES(
>NO) for shop running, lets say z/OS 2.2 + all OEM products up to date with
>compatibility?
>we're not a large DB2 shop be most of our workload is DB2, DB2 data sharing in
>a 3 system sysplex.
>any recommendations?
> Can you point me to the best place to see if Ziip is getting maxed out.
Look at the TYPE70 SMF records. They will show you if the ZIIP is 100% busy.
Regards, Barbara
--
For IBM-MAIN subscribe / signoff / archive access
We had the (admittedly not so) bright idea to accomate the request from
application development to activate the HEAPCHK LE Option generally. We did
this in conjunction with upgrading from 2.1 to 2.3.
As a result, the crappy design of HWIBCPII address space revealed itself. (It
had been
>> HWIBCPII is one of those magical address spaces that is started by
>> Abracadabra:
>>
>> S IEESYSAS,PROG=HWIAMIN2
>
>Or by:
>
>S HWISTART (which essentially does the same)
Not quite. S HWISTART waits for JES2 to come up, it does NOT start HWIBCPII
immediately. (Which is why I tried the
Ed,
please reread my first post!
>If that's the case, then the fault lies with LE and not BCPii.
How is LE to know that it runs under an implicit sub=mstr? That is not how your
standard Cobol/PL/I program runs.
What started this off was our general setting of HEAPCHK(ON) on request of
>Hree, I thought it was just me doing something dumb in FF and IE. :-)
I second that. It kind of made me angry that the link opens the certificate in
IE, with readable (ASCII) characters in it. I expect a page with choices of how
to download! I also tried searching that digicert site for the
zD comes with an ADCD system, which used to lag behind 12-18 months (when I
worked on an RDT system) about 2 years ago.
ADCD does not have *any* z/OS support as we know it (when you only have an RDT
system, you cannot order ptfs). The process of 'migrating' to a new ADCD
version is cumbersome
I took a chance (since a colleague had set up internet access directly from the
host) and ordered z/OS 2.3 via ShopZ as downloadable from internet.
The only browser I can use is Chrome, and I cannot change anything in the
settings (corporate mandate). IE will not even let me log in to ShopZ.
>I get the "Error: CSRF attack detected" frequently if I am doing a page
>refresh too quickly or trying to navigate backwards and it doesn't want to let
>me do it. I end up
>re-driving the url again and all is well. All this on FireFox.
>
>You might try Lvl2 support. Here is one person that has
>I agree with the above under "normal" circumstances. tut what if RACF is
>broken for some reason?
>UADS may save you’re a**s.
Allan,
I completely agree. I am not saying not to have a sys1.uads on a running
system, I am dissatisfied with having half (the definition) in SMPE but not the
actual
>So how do people protect the same dataset differently on various LPAR's, or is
>it just not possible?
We had to make sure that the compilers do not run on a system that doesn't have
licence=z/OS. We used when(sysid) in class PROGRAM, for the names of the
compilers as the program name to be
On Mon, 23 Jul 2018 06:05:43 -0400, John Eells wrote:
>Over the past few years, COBOL and PL/I have added support for Product
>Registration Services, and can be disabled using IFAPRFxx entries. XL
>C/C++ is a feature of z/OS and can similarly be enabled or disabled with
>IFAPRDxx.
>
>This does
What a good thing we are not using z/OSMF. Last Friday I downloaded a refresh
for z/OS 2.3 from ShopZ. Everything went fine *except* ptfs UI55431, UI55737,
UI56534, UI57065 and UI57212. They fail to go in.
I install maintenance into /SERVICE, so the root is mounted under /SERVICE.
SBBLZFS is
David,
>Are you sure you had all of your Service filesystems mounted correctly? The
>error indicates the possibility that maybe not? On my systems IZUUSRD is
>mounted off /var/zosmf and is NOT updated by SMPE as it is the ZOSMF
>operational data container. My V2.3 SMPE shows DDDEF SIZUFSD
>That’s correct Barbara.
And it worked like a charm. Which made me wonder why I was able to mount on a
non-empty mount point (assuming it was non-empty!). Turns out I only had the
parm set to warning, not to fail. And sure enough, there was a message that I
mounted on a non-empty mount point.
I am curious: Why is Rocket Software defending missing SDSF actions and bad
documentation??? Has IBM 'outsourced' the SDSFAUX server?
I am annoyed with the ISFTABL thing (which we addressed in our logon
procedure), too, because that message was irritating all of us.
The ISF.CONNECT thing is
Something has changed with SDSFAUX between z/OS 2.1 and z/OS 2.3.
Under z/OS 2.3, each and every user gets a RACF Message when they access their
part of SDSF (that's the primary RACF panel). That missing right is for
ISF.CONNECT.system, which is described as access to SDSFAUX. None of those
While installing my (downloaded :-) ) serverpac for z/OS 2.3, I have noticed
three problems (so far):
Datasets FFST.V120ESA.AEPWBENU and IOA.AIOAIBIN were both placed on my target
volume instead of my DLIB volume.
And SYS1.AUADS is in SMPE, but it is completely missing, even from the RESTORE
>I believe your point is that if you do not intend for multiple userids
>to use the same certificate, then you don't need to connect it to your
>keyring with USAGE(CERTAUTH). Fair point.
Thanks Kurt, for your answer. I did not set up the download capability (and did
not read the book), and the
>this has been my request for a long long long time. (with the exception of
>the ZFS datasets of course). The problem with this is that the other
>Serverpac jobs that massage the CPAC parmlib/proclib that come with it.
That was my other 'problem'. I don't want that CPAC stuff on my
We are in the process of migrating to z/OS 2.3, and I want to use the new
IRRPRMxx parmlib member. The documentation in oa52560 is suspiciously silent on
how to activate this in a sysplex data sharing environment, so I went through
the RACF books.
It seems that IRRPRMxx can only be activated
>Ouch. I never saw Walt's proviso mentioned in the doc. Yes, these nodes are
>all totally under our control. However each node (sysplex) constitutes a
>different business environment supported by a different RACF data base. A
>person may have the same userid on sandbox and on production, but
Tom,
>Your 2.3 system will use the IRRPRMxx member and your 2.1 systems will
>continue to use the information you specified in the ICHRDSNT load module. All
>we did was take the information that we specify in the load module and put it
>in a parmlib member. We have not had any issues
Tom,
>The way I read this is that the PARMLIB member does not agree with the
>ICHRDSNT already in use by the RACF sharing group. Are you absolutely
>sure that the PARMLIB member is correct and agrees with your current
>ICHRDSNT in every respect? If so, then I would open a PMR for this issue.
Replying to several posts:
When I activated OA53355 on my z/OS 2.3 system, I activated that check. It
tripped immediately and gave me the possibilities (other than what the diag
trap we've been running with already excluded):
- SCOPE=ALL data space
- IARVSERV SHARE
>Has anyone else gotten frustrated when opened an IBM Service Request in having
>to select the Operating System, which should have been automatic after
>selecting the Product and the applicable operating system release level?
Me too. One *always* gets asked what had already been answered. Plus,
Brian,
>I would think your RASP dump would only be a point in time view of User Key
>Common at the instant of taking the dump. User Key Common that didn't exist at
>the time you took the dump wouldn't appear, right?
Completely true. On the other hand: In my experience, user key common (CADS,
On Mon, 26 Mar 2018 15:23:42 -0400, John Eells wrote:
>In addition to that, you can take a laptop outside your firewall,
>download stuff*, bring the laptop back in, connect to your internal
>network, and upload it to z/OS to be processed.
No, you cannot. Where I work, the
>$ /usr/lpp/java/J8.0_64/bin/java
>-version
Try
java -Xmcrs2048k -version
My colleague who had figured that out set the specified parm somewhere in USS,
so now it always works for us just using -version.
Regards, Barbara
--
>And where can I look up PTFs? IBMLINK / SIS was my major website doing
>this.
>The "Granular APAR search" doesn't work for me with PTF numbers.
What's wrong with SIS? I can get in and can do searches, just as always. My
login link is
On Thu, 4 Apr 2019 20:33:36 +0300, Binyamin Dissen
wrote:
>What does this give over IPCS of ACTIVE?
>
My question exactly, too.
>Joseph Reichmann answered: "Going thru control blocks specially if there is
>eyecatcher and it formats it
>Makes it real easy to go thru control blocks "
Well,
I have a strange issue with the ISPF main (first) panel. I have added
permission to view the APF list:
pe ISFCMD.ODSP.APF.* cl(sdsf) id(grpname) ac(r)
and I have refreshed the raclisted sdsf class. I expected the APF command to
show up in the ISPF main panel once I call ISPF. It does NOT show
Again: The APF command is NOT failing, it 'just' does not show on the main
panel! It only shows *after* the APF command was *successfully* executed! And
then only for as long as I stay within that session.
With the exception of 4 userids, *everybody* is in ISFUSER, which doesn't mean
anything
>Are you using the default panel ISFPCU41? Has anyone modified it?
Vanilla ISPF/SDSF, no usermods, and the panel is always named ISFPCU41.
>How are you invoking it? Like this?PGM(ISFISP) NOCHECK NEWAPPL(ISF)
>SCRNAME(SDSF)
Exactly like this: PGM(ISFISP) NEWAPPL(ISF) SCRNAME(SDSF) NOCHECK
>How many lines in your ISFPCU41?
541 :-) with the copyright by Rocket Software. But then, the primary panel is
one column only these days (which took some getting-used-to).
>Ungodly? :-) I have 153 entries and almost never issue =blah.blah.blah.blah
The problem is that many of the entries we
I know we've been through a few iterations of this, and I still have questions:
We had one offender that was using a key=8 CADS. They have since provided a
release where they use a system key for their CADS, and that release has been
installed on all sysplexes/systems.
I was really astonished
>Not to hijack the thread, but... I thought ServerPac already
>automatically adds 20% (25?) free space, but I could be wrong. In any
>case, how much free space should be allocated by ServerPac? I saw 50%
>mentioned. Is that enough? Should it be the same for every data set,
>or just the three
One problem we had was unequal usage on the available volumes. The first
volumes considered by SMS were almost full, no way to fulfill the primary space
allocation. There was enough space in volumes that SMS would have checked
later, but before SMS got there, the volcount was reached. We ended
Hello David,
parm(new) did the trick! This bit of information must have been buried in all
the RUCSA stuff that I skipped over because it doesn't apply to us.
We don't have oa56180 applied yet, so that explains why the audit bit wasn't on
in some cases.
I feel much more confident now to
Hi Bruce,
>I have the same query open with IBM at the moment.
Well, it helps that I am not alone with that question. :-)
>If you could provide an example of a RESET command I would most appreciate.
I didn't use it. All I did was go into sdsf and then scroll to the extreme
right of the health
>There shouldn’t be Jake. I'm running MOD-54's for my sysres volumes and have
>been for years. Probably the only issue you might have is if you are going
>from a multi-sysres config where you had multiple system symbols for catalog
>purposes, you'll just have to fix that to all use either
>I just checked my master cat and EVERY entry has , 2, or 3 except
>SYS1.PARMLIB on the SYSRES It has **. and both are set
>to since we use mod 27s. We are at z/OS 2.3.
All, thanks for checking.
So my conclusion way back when must have been wrong. I had left SYS1.PARMLIB
(that came
>I have never has a problem using anywhere ** could have been used.
>Actually, the resolution of occurs very early in the IPL, long before
>CAS is initialized.
>
>The difference is that is resolved by CAS, which is not yet initialized
>at that moment. Until then, ** does the built-in
>What if the res volume is spreaded on two volumes ? Can we still use
>'**' ?
No, not according to how I read the book. Only the data sets on the volume that
you specify in the IPLPARM can use **. Any other volume containing non-VSAM
system data sets would be considered an *extension*
1 - 100 of 165 matches
Mail list logo