Just in case VM itself... Do a snapdump now. So you have something to send
to IBM.
Marcy Cortes
"This message may contain confidential and/or privileged information. If you
are not the addressee or authorized to receive this for the addressee, you
must not use, copy, disclose, or take any ac
We're having a problem today where it appears that VM itself is using a lot of
cpu. We use ESAMON and I've looked for a smoking gun. I know it's not regular
users because their cpu utilization is low where as the system utilization is
way above normal for us. Thing is I can't find a screen in ESA
90% an exercise to clean out obsolete garbage. 10% an exercise in becoming more
familiar with SFS, something we've neglected far too long and which could make
multi-VM system support easier in the future.
Now, if only SFS had an option to log who, and. what accessed a file we could
really clea
>> The RSCS TCPNJE implementation did not include sending a periodic
>> timing packet to the other side.
>
>But RSCS would kindly respond to the CPQ TIME commands sent from the
>non-mainframe end.
Yes
Best Regards,
Les Geer
IBM z/VM and Linux Development
On Thu, 2007-06-14 at 21:55 -0400, Les Geer (607-429-3580) wrote:
>
> The RSCS TCPNJE implementation did not include sending a periodic
> timing packet to the other side.
But RSCS would kindly respond to the CPQ TIME commands sent from the
non-mainframe end.
>The implementation of NJE for Linux, Unix, and Windows that we wrote was
>based on a line driver that used to send CPQ TIME commands between nodes
>every minute or so as a method of detecting whether the link was up or
>not.
The RSCS TCPNJE implementation did not include sending a periodic
timing
> I use "VMFCOPY ... (OLDDATE PRODID %" to copy any
third-party,
> home-grown, or misc IBM program product files to the Y-disk, where
> % is a productname/componentid (made up where necessary),
so
> that VMSES PARTCAT Y shows a complete inventory of the disk.
This triggere
> I suppose that I should have started this thread by stating right away that
> we have and use
> SAFESFS. Given it's price, ease of use, the complexity of SFS's native ACLs,
> and the
> reduction in backup times from hugely fewer authorizations, I can't
> understand why anyone
> using SFS w
And they were private only because of ignorance or lack of desire on the
part of those who could link to the disk. Before there was ACCESSM0
there was DDR, so the only reasonable guarantee of privacy was to not
let anyone link to the disk. Even then, there were those who had
LNKNOPASS capabilities,
On Thursday, 06/14/2007 at 02:36 EST, Mike Walter <[EMAIL PROTECTED]>
wrote:
> b) Why is it that filemode 0 (zero) files appear in a read-only SFS
filespace?
> OK, the "ACCESS" doc does not mention MODE0 for anything but MDISKs.
But why
> would it even be designed to show filemode 0 in read
I suppose that I should have started this thread by stating right away
that we have and use SAFESFS. Given it's price, ease of use, the
complexity of SFS's native ACLs, and the reduction in backup times from
hugely fewer authorizations, I can't understand why anyone using SFS would
not have pu
Well... we kind'a already did that at one point with our own "COPY2 EXEC".
Along with other things (like keeping us from forgetting OLDDATE and
preventing us from using REPLACE -- remember it was written for an MDISK
and will be changed to the copy to SFS) it appends to a "HEWITT PARTCAT".
Whi
With a DIRC, SFS security is pretty much like a minidisk. For your Y-disk
you'd issue a "GRANT AUTH dirid TO PUBLIC (DIRREAD" and everyone can read
any file on it. For a filecontrol directory one must indeed have a grant
for the directory and for each file.
2007/6/14, David Boyes <[EMAIL PROTEC
Yes, I use VMFCOPY too to copy the old 19E disk over to the new one. I
invented my own prodid for things we wrote ourselves or other vendor
products.
I even have a tool to help me with this copy process: it compares both VMSES
PARTCATs and lets you copy product by product. Before you do that, yo
> a) Has anyone else done this as (1) a form of housecleaning or (2) a
> generally good idea
> for the Y-disk? Do you have any guidance for those about to trod upon the
> road "less
> traveled by"?
I know of a couple sites that did this. The major complaints I heard were:
1) install tools
As far as I know, there is nothing that would read the "hidden" files on
19E. Unless you would still be running a special command (who's name is
probably GENDIRT) to store the pointers to these hidden files, you would
need to run this each time such a hidden file is moved. So, IMHO all non-2
fil
> So, finally, the questions...
> a) Has anyone else done this as (1) a form of housecleaning or (2) a
> generally good idea for the Y-disk?
I use "VMFCOPY ... (OLDDATE PRODID %" to copy any third-party,
home-grown, or misc IBM program product files to the Y-disk, where
%
The implementation of NJE for Linux, Unix, and Windows that we wrote was
based on a line driver that used to send CPQ TIME commands between nodes
every minute or so as a method of detecting whether the link was up or
not.
On Thu, 2007-06-14 at 12:36 -0700, Schuh, Richard wrote:
> I actually see no
) Why is it that filemode 0 (zero) files appear in a read-only SFS
filespace?
I asked IBM that question way back when and was told that is the way it
works.
-Original Message-
From: The IBM z/VM Operating System
[mailto:[EMAIL PROTECTED] On Behalf Of Mike Walter
S
OK, ok. :-)
I had a rough morning. At least I think I did ... it's after lunch now.
:-)
Mike Walter
Hewitt Associates
Any opinions expressed herein are mine alone and do not necessarily
represent the opinions or policies of Hewitt Associates.
"Kris Buelens" <[EMAIL PROTECTED]>
Sent by:
I actually see no harm in the way it is working. The MVS folks are the
ones who question the integrity of the link. Your band-aid might be a
security blanket for them.
Regards,
Richard Schuh
-Original Message-
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of R
Exposing my (monumental) SFS ignorance...
Stuff here has been accumulating on the Y-disk for (literally) decades.
For example, one of the oldest files is:
HASMOPT COPY Y1 1 5/27/82 15:48:06
The source of many of the files can be identified by fileid naming
standards. But there's a lot of acc
*Thus, filemode "C" is the right choice, and as Jim Vincent Kris Buelens
said, keeps your "$VMF $MSGLOG"s in one place -- a very "GOOD THING".*
On: Thu, Jun 14, 2007 at 10:13:13AM -0700,Schuh, Richard Wrote:
} Should we be concerned about missing jobs, files or messages? The MVS
} folks think that this is a game breaker. It certainly appears to me to
} be more of a nuisance - the time-out occurs, the link is restarted when
} a job is subm
> > What is the difference between the NJE keepalive and the RSCS
> keepaliv=yes?
> > We have tried both =yes and =no to no effect.
>
> Same thing. Since the RSCS keepalive essentially does a simple NJE
> transaction periodically, and it doesn't look like a normal TCP
> timemark.
Uh. Scratch that
>> What is the difference between the NJE keepalive and the RSCS
>keepaliv=yes? We
>> have tried both =yes and =no to no effect. We have been running with
>keepalive
>> turned on for 48 hours. The same errors show up like clockwork when the
>link is
>> idle for an extended period.
>
>I'm not aware
That was my understanding of the Keepalive. IIRC, it was a note from
Alan to the list that was the basis of my understanding, so he knew it,
too :-)
So we have covered both of the bases. I have asked the MVS guys to
verify that the PTF mentioned by Alan has been installed.
Should we be concerned
> As the Mythbusters like to say, "Busted." The firewall guys tell us
that there is not a
> single firewall between point A (VM) and point B (MVS).
OK, scratch that. Pretty much eliminates that theory, then.
> Tracerte is not very helpful, either. It seems to confirm what the
firewall guys said
Thank you all for the information.
Ann
The information contained in this message may be CONFIDENTIAL and is for the
intended addressee only. Any unauthorized use, dissemination of the
information, or copying of this message is prohibited. If you are not the
intended addressee, please not
On Thursday, 06/14/2007 at 08:53 MST, "Schuh, Richard" <[EMAIL PROTECTED]>
wrote:
> What is the difference between the NJE keepalive and the RSCS
keepaliv=yes? We
> have tried both =yes and =no to no effect. We have been running with
keepalive
> turned on for 48 hours. The same errors show up
As the Mythbusters like to say, "Busted." The firewall guys tell us that
there is not a single firewall between point A (VM) and point B (MVS).
Both are on the same internal network. The only firewall is between it
and the outside world.
Tracerte is not very helpful, either. It seems to confirm
A beginner DDR image would be very nice. Then all you need is something
to edit the config from CMS before starting the new image, such as SNA's
EXT2TOOL. Putting /config on it's own little file system would make the
configurations sharable/movable between images.
Ray Mrohs
U.S. Department of Jus
> Thank for your info, accessing 500 A works
Maybe so, but Jim Vincent's (and others) suggestion to ACCESS 500 C as a
better choice.
Now that he posted it, the pre-lunch memory synapses have spring to life
-- I did use C.
I've often used 'W' in the past, which may work when you're apply
Filemode C has been "special" since very long, that is even before VMSES was
available. At that time, moste service execs neede to be started from disk
C. Maybe that's the reason why VMSES leaves filemode C untouched.
So, I'd say: leave the 191 as A, then all $MSGLOG files remain there, you
hav
Or, as I did, make the 191 1,000 cylinders.
-Original Message-
From: The IBM z/VM Operating System
[mailto:[EMAIL PROTECTED] On Behalf Of James Vincent
Sent: Thursday, June 14, 2007 10:02 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Service for VM
VMSES/E has specific file modes that are "free" to access disks/directories
at. Guessing what file modes to access disks at is probably not a grand
idea because it could be that some component will use that file mode later
and then strange things will happen.
HELP VMSES VMFSETUP explains in the
Jim and MIke,
Thank for your info, accessing 500 A works
Thank you very much ! !
Ann
"Jim Bohnsack" <[EMAIL PROTECTED]>
Sent by: "The IBM z/VM Operating System"
06/14/2007 09:26 AM
Please respond to
"The IBM z/VM Operating System"
To
IBMVM@LISTSERV.UARK.EDU
cc
Subject
Re: Servi
[EMAIL PROTECTED] wrote:
>> I am trying to service all envelops for RSU,
>> The envelops are in 500 disk rather than 191.
>> But when SERVICE was invoked, it reaccess disks.
>> How do I make 500 available for service, Do I need to update
>> some ppf file ?
Hi Ann
The standard method (t
A simple ACC 500 L (o K) works .
Good luck.
Jim Bohnsack wrote:
Ann--I took the cowards way out and made the 500 disk my 191 disk. If I
remember correctly, I copy some or most of what I thought I'd need from
191 to the much larger 500 disk and then changed mdisk addresses.
Jim
[EMAIL PR
I access it as U, no particular reason other than it wasn't used. Any
reason why you chose A?
Your 'after lunch' comment reminds me of a T-shirt I saw on a TV show,
"If I don't remember it, it didn't happen!"
Mike Walter wrote:
Second, try ACCESS 500 A. Then issue the SERVICE command. I'
First, remember that IBM's VM Development lab really responds to "Reader
Comment Forms" (RCF's) - you should report this so that other new-to-z/VM
customers don't have to figure it out on their own, too.
Second, try ACCESS 500 A. Then issue the SERVICE command. I'm pretty
sure that's what I d
Ann--I took the cowards way out and made the 500 disk my 191 disk. If I
remember correctly, I copy some or most of what I thought I'd need from
191 to the much larger 500 disk and then changed mdisk addresses.
Jim
[EMAIL PROTECTED] wrote:
This is a multipart message in MIME format.
--=_altern
Hi, listers,
I am trying to service all envelops for RSU,
The envelops are in 500 disk rather than 191.
But when SERVICE was invoked, it reaccess disks.
How do I make 500 available for service, Do I need to update
some ppf file ?
Thanks,
Ann
The information contained in this message may
43 matches
Mail list logo
