Hi,
Is there a command that can tell what these parameters are set to or do I need
to check all the mdisks that DIRMAINT has access to.
I started this thread and what we want is simple. For our VSE machines what we
want is WYSIWYG. When I want to do a 'DIRM REPLACE', DIRMAINT should
I think David, with Mike's correction is correct. We've got 2nd level
MVS machines that are used for our D/R tests. We always start the
exercise by loading the D/R backup tapes from S/A DFDSS. The consoles
on the 2nd level MVS id's are specified as being 3270 rather than 3215.
Works just
While I hesitate to correct David, in this case a correction is
warranted.
The proper command is:
CP TERMINAL CONMODE 3270
Perhaps David's suffering Monday Syndrome?
More like what idiot decided that Solaris kernel configuration files
should be in XML syndrome.
Mike is (of
But were one of your original ideas revisited... if the 80-character limit
to the directory records was eliminated, then comments could be in the
same line with the actual statement (perhaps with a hex character such as
'05'x or x'00'x as the field-mark?), then having to remember which related
http://www.vm.ibm.com/zos/
Probably a good idea to change the os/390 and vm/esa refs in the 2nd
section there to z/OS and z/VM at this point :)
Marcy Cortes
This message may contain confidential and/or privileged information. If
you are not the addressee or authorized to receive this for the
Also, some non-VM utilities really want CONMODE 3270. If Mike's
suggestion doesn't work, try SET CONMODE 3270 before you IPL 181, eg:
CP SET CONMODE 3270#IPL 181 CLEAR
(the SET CONMODE will cause CMS to choke, so be prepared). Press Enter
after the tape has stopped moving.
Thanks. I have:
SORT_DIRECTORY= NO | YES
SORT_BY_DEVICE_ADDRESS= NO | YES
SORT_COMMENTS_WITH_STATEMENTS= NO | YES
I am going to try to create a scenario where the comments are relocated.
Mike
-Original Message-
From: The
Michael--You can do a DIRM CMS L CONFIG* DATADVH * (DA. Mine, and I
think that this is the standard case, is on the DIRMAINT 11F disk. Also
I run with SORT_DIRECTORY= YES, SORT_COMMENTS_WITH_STATEMENTS= YES
(should not matter because we do not have SYSSAFIN specified, but who
knows), and
Yes.
-Original Message-
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Brian Nielsen
Sent: Monday, February 11, 2008 11:03 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Driver 67
This weekend our CE installed Driver 67 on our z9 and the operator
console
log shows
This weekend our CE installed Driver 67 on our z9 and the operator consol
e
log shows message HCPSAS879I CPU Installed Facilities have changed at
that time. After that time I no longer get any statistics from the other
LPARs on the ESALPARS screen/reports. Does VM need to re-IPL'd to start
I have just been doing some checking because we don't seem to have this
problem of comments moving around within the directory entry.
Initially, I thought this was because we use special local procedures that
interface with DIRMAINT but I just tried some vanilla GET's REPL's
without any
That looks like it. It was added to the 2096DEVICE and ZVM530 subsets
10/29/07. Unfortunately, I retrived those subsets a few days earlier
(10/25/07).
The only info I got from the IBM CE regarding Driver 67 was that z/VM 5.2
required maintanence to avoid a crash but that z/VM 5.3 was not
I knew because our IBM HW people talked to our HW people who asked me
about whether these things were on.
Would be nice if everyone got such service!
Marcy Cortes
This message may contain confidential and/or privileged information. If
you are not the addressee or authorized to receive this
Hi,
We are running z/VM Version 5 Release 2.0 service level 0702 (64-bit)
We have a standalone z/OS DFDSS 1.7 which we intend to IPL
from a z/VM guest to restore a tape backup to a dasd.
Upon IPL from tape (i.e. IPL 181 clear), we were able to load
the standalone dfdss program
The first question I have is, what do you both have your ³SORT_DIRECTORY=²
and ³SORT_BY_DEVICE_ADDRESS=² parameters set to, in CONFIG DATADVH or it¹s
minions? These may or may not be the issue.
Second, someone mentioned comments taking space in the object directory...
My impression / hope would
On Feb 11, 2008 5:08 PM, Marcy Cortes [EMAIL PROTECTED] wrote:
Could it be VM64323?
http://www.vm.ibm.com/service/redalert/
Thanks Marcy. I knew there as a problem where z/VM forgot it was
running in LPAR, but I could not find the APAR number... This
certainly explains why ESALPAR and ESALPARS
Could it be VM64323?
http://www.vm.ibm.com/service/redalert/
Marcy Cortes
Team Lead, Enterprise Virtualization - z/VM and z/Linux
Enterprise Hosting Services
w. (415) 243-6343
c. (415) 517-0895
This message may contain confidential and/or privileged information. If you
are not the addressee
Umm, not to rain on anyone's parade, here, but something tells me we're
trying to engineer a solution to a problem that might be better solved
elsewhere.
The problem that we're trying to solve (IMHO) is documenting what goes
where. If you start putting text commentary in the CP object directory,
On Feb 11, 2008 10:37 AM, Ivica Brodaric [EMAIL PROTECTED] wrote:
Another approach we've used in the past is a common file on each
system disk that lists the purpose and change history (e.g. @WHATSON
THISDISK).
But if you format that disk, you lose @WHATWASON THISDISK as well! :-)
I
Thanks very much for all the replies. I really didn't expect it, althoug
h
I should know better with this group.
I have passed on names and addresses to the folks in charge, and I want t
o
thank everyone who responded. I think a leading candidate has been
identified, and if no one else hears
On Monday, 02/11/2008 at 12:53 EST, Brian Nielsen [EMAIL PROTECTED]
wrote:
That looks like it. It was added to the 2096DEVICE and ZVM530 subsets
10/29/07. Unfortunately, I retrived those subsets a few days earlier
(10/25/07).
The only info I got from the IBM CE regarding Driver 67 was
21 matches
Mail list logo
