I need to ipl my old z/vm 5.1 system on a test lpar to look at some
stuff. I don't want AUTOLOG1 to start. Trying to find how to do that
on ipl, but in the mean time if anyone could enlighten me, I'd be
grateful!
At the START prompt ... reply NOAUTOLOG ...
08:42:33 z/VM V5 R3.0 SERVICE LEVEL 0701 (64-BIT)
08:42:33 SYSTEM NUCLEUS CREATED ON 2007-07-23 AT 07:26:47, LOADED FROM
PARM
08:42:33
08:42:33
08:42:33 * LICENSED MATERIALS - PROPERTY
AH.. thanks!
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Imler, Steven J
Sent: Thursday, September 06, 2007 7:04 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: no xautolog
At the START prompt ... reply NOAUTOLOG ...
08:42:33
Beware though: depending on the definitions in SYSTEM CONFIG, the IPL prompt
can be bypassed. The safest way is then to IPL with a SAPL screen, fill in
the address of a 3270 screen, or SYSG if you use an integrated 3270
console, at the SAPL screen, enter PROMPT in the IPL options input field.
We always use the SAPL screen, so I should be safe there... I converted
to z/vm 5.3 last night, but my diskacnt routines were wrong so I didn't
get the accounting this morning! I think I have it fixed so I won't
need to ipl the 5.1 system (at least not today). However, if something
else needs
http://searchdatacenter.techtarget.com/originalContent/0,289142,sid80_gc
i1270788,00.html?track=NL-576ad=602745asrc=EM_NLT_2119907uid=5701628
I begin to think that Perry Ruiter and I should start hiring lawyers and
license the ideas we come up with. 8-(
-- db
On Thursday, 09/06/2007 at 08:08 EDT, Kris Buelens
[EMAIL PROTECTED] wrote:
MDSK OLDVM.DISKACNT 191 (FILELIST DETACH
and the MDSK EXEC finds the MDISK in OLDVM DIRECT, ATTACHes the volume
to
SYSTEM, issue DEFINE MDISK, ACCESS it, start FILELIST; when FILELIST
ends,
everything gets
Kris,
Please send that EXEC to me as well. I think it would come in handy as I
prepare to 'go live' with VM 5.3 next week.
Thanks
Kris Buelens [EMAIL PROTECTED]
Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU
09/06/2007 07:07 AM
Please respond to
The IBM z/VM Operating
When you say source of the old CP directory are you referring to the
whole USER DIRECT?
I tried to ATT rdev * and I added a MDISK statement in my 5.3 user
directory, but I couldn't acc the mdisk.
It kept saying the volume wasn't mounted. (It was the 510W01 volume
that I needed.. so no
We use 3590 B1A drives, with 10/30 carts providing native capacity of
10GB, with up to 30GB using hardware compression. I am under the
impression that the hardware will choose the best compression possible
UNLESS it is specifically told otherwise (i.e. via a TAPE COMP/NOCOMP
and DDR
No, MDSK is not that clever. It will be after my holidays next week...
2007/9/6, Alan Altmark [EMAIL PROTECTED]:
On Thursday, 09/06/2007 at 08:08 EDT, Kris Buelens
[EMAIL PROTECTED] wrote:
MDSK OLDVM.DISKACNT 191 (FILELIST DETACH
and the MDSK EXEC finds the MDISK in OLDVM DIRECT,
Yes, you need the whole USER DIRECT, but please rename it to some other
fname that you don't confuse it with the 5.3 directory.
With ATTACH to yourself, you can see the whole volume. To access a minidisk
on that volume, you need some help from CP, therefore, the disk must be
attached to CP (i.e.
I actually have a copy of USER DIRECT from 5.1 saved in z/os...
I already had a mdisk defined in the 5.3 user direct pointing to the
spot on the 5.1 volume that I needed.
So, I was able to do the ATT dasd SYSTEM and I could then ACCess ii!
I will have to look at your EXEC a bit. Much too
Hello Michael,
you must install the mtst command in your Linux.
After that you can enable the hardwarecompression (as far as I know the dafault
is OFF)
# mtst -f /dev/rtibm0 compression 1
This helped in my environment(Suse sles9)
kindest regards
Mit freundlichen Grüßen,
Horst Rempel
On Thu, 6 Sep 2007 09:14:17 -0400, Michael Coffin
[EMAIL PROTECTED] wrote:
We use 3590 B1A drives, with 10/30 carts providing native capacity of
10GB, with up to 30GB using hardware compression. I am under the
impression that the hardware will choose the best compression possible
UNLESS it is
Sorry, I meant the IBMLZ1 compression. IDRC is for 3490's.
On Thu, 6 Sep 2007 09:00:45 -0500, Brian Nielsen [EMAIL PROTECTED]
wrote:
IDRC compression is on by default, but can be turned off via software
parameters.
Some data is not well suited to compression, which may be the case with
Does anyone have an example of obtaining basic systrm info from CMS assembler?
I have several back level VM systems so I can't use the new REXX API. I need
output from FC=1 and SEL1 2 = 1. My concerns are: does the instruction
require 64 bit mode? Does the 4K data area have to be a REAL level
DIAG 0 also reports a lot of nice information about the system and the
VM release.
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Derek Ackerman
Sent: Thursday, September 06, 2007 10:19 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject:
This could be handy for anyone migrating to new systems, or even managing
multiple systems. Sure... we can do it ourselves (and probably most do),
but when chip a new wheel from old stone? Could you send the updated
MDSK package to the IBM VM Download Page? Yes, you knew someone would
ask.
Can use use the STSI pipeline stage that is part of the free runtime
library distribution? (see
http://vm.marist.edu/~pipeline/index.html#Runtime). That's what I've
been using for several years..
On 9/6/07, Derek Ackerman [EMAIL PROTECTED] wrote:
Does anyone have an example of obtaining
On Thursday, 09/06/2007 at 10:19 EDT, Derek Ackerman
[EMAIL PROTECTED] wrote:
Does anyone have an example of obtaining basic systrm info from CMS
assembler?
What kind of information are you looking for?
I have several back level VM systems so I can't use the new REXX
API. I need
The default is indeed a R/O access, but no, it doesn't use ACCESSM0 (yet).
We use it to access disks of our other VM systems.
But, since we've got even better MDSK is not much used. The more clever
version -named FLDISK- first finds the volser of the object directory in a
control file, it then
After slightly missing the closing date of end of 2001, it looks like we
will be shutting down sometimes between October 1 and December 30.
One good thing about our VM/ESA 2.4 system -- no new bugs in a very long
time.
I have been baby-sitting the system on a part-time basis for the last four
Derek, here is some Assembler code that I was working on at one time to
issue STSI for the basic machine configuration, (1.1.1). I had plans to
add code to set REXX variables for the extracted fields, but I didn't hav
e
time to complete it before I was let go. So I will leave that part to
That's the way I'm hoping to phase into retirement. Congratulations.
Jim
Larry Israel wrote:
After slightly missing the closing date of end of 2001, it looks like we
will be shutting down sometimes between October 1 and December 30.
One good thing about our VM/ESA 2.4 system -- no new bugs in
...throw it a shiva not a wake!
sad day. no virtualized linuxes I guess in their future
David
-Original Message-
From: The IBM z/VM Operating System on behalf of David Boyes
Sent: Thu 9/6/2007 2:48 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: [IBMVM] Weizmann Institute of Science (WIS) VM
After slightly missing the closing date of end of 2001, it looks like
we
will be shutting down sometimes between October 1 and December 30.
One good thing about our VM/ESA 2.4 system -- no new bugs in a very
long
time.
I have been baby-sitting the system on a part-time basis for the last
four
Sure, I can take APARs! Then I'll take several months to come out with a
PTF that's broken, then several more months to fix it, which will break i
t
for other people who were relying on the original broken PTF! :-)
--
Dale R. Smith
(Not related to Chuckie or Alan! :-) )
I haven't failed.
Hello Everyone,
What is the highest RSU for z/VM 5.3? 5301 (701)?
Ed Martin
Aultman Health Foundation
330-588-4723
[EMAIL PROTECTED]
ext. 40441
Hey, Good Luck and have a very fine retirement.
Ed Martin
Aultman Health Foundation
330-588-4723
[EMAIL PROTECTED]
ext. 40441
-Original Message-
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED]
On
Behalf Of Larry Israel
Sent: Thursday, September 06, 2007 2:34 PM
I have 5301
--
.~.Robert P. Nix Mayo Foundation
/V\RO-OE-5-55200 First Street SW
/( )\ 507-284-0844 Rochester, MN 55905
^^-^^ -
In theory, theory and practice are the same, but
in practice, theory and practice
Ok, you network gurus; I've got one for you -
The TCP/IP address of my z/OS 1.8 system is 111.222.333.11. (not really,
and yes, I know this is the VM list)
When I run this REXX Exec -
/* REXX */
SAY SOCKET('INITIALIZE','MYID')
Getting the answer to that question is why I keep a CURRRSU EXEC on
MAINT's 191 disk. It contains:
---snip---
/* */
say 'The most-current RSU is always included on PTF UM97vrm'
say 'e.g. UM97520 for z/VM 5.2.0, and UM97530 for z/VM 5.3.0.'
---snip---
Very simple, usually relatively
Any know of any good tools for the manipulation (reading/writing/updating) of
XML structures for REXX on CMS? Or am I looking at another roll your own job
here?
Ian S Worthington
...
http://isw.me.uk/
Dulce et decorum est pro patria mori, sed dulcius pro patria vivere,
Dale,
Thanks very much, I made my changes (see att) and output is:
EP AT 8001 --- IN CASE I NEED TO TRACE
2066-004.IBM
I couldn't find the HCPSSIBK, however.
Derek Ackerman
Capacity Planning etc.
(201) 759-0833
-Original
Larry,
I am sorry to hear that your VM is finally really going away.
We at the Israel Police are still very grateful to you for
the library of screen control routines you gave me back
in the 80s, which is still heavily used, after being embedded
in my WYSIWIG screen painter program.
Enjoy your
Take a look at this file on the CBT Site
http://www.cbttape.org/ftp/cbt/CBT647.zip
It is described as: An XML parser written in REXX from Andrew Armstrong
cheers
Lionel B. Dyck, Consultant/Specialist
Enterprise Platform Services, Mainframe Engineering
KP-IT Enterprise Engineering, Client
Also: http://www.vm.ibm.com/download/packages/xmlparse.vmarc
On Thu, 2007-09-06 at 14:25 -0700, Lionel B. Dyck wrote:
Take a look at this file on the CBT Site
http://www.cbttape.org/ftp/cbt/CBT647.zip
It is described as: An XML parser written in REXX from Andrew
Armstrong
z/VM supports very large disk sizes. With the shared file system, you
can pool disk volumes together into even larger minidisks.
How much disk space do you think you'll need?
Suleiman Shahin wrote:
Greetings folks,
I know this is elementary, but I have to ask!
I have an application that
I wonder how large an m-disk I can allocate for this app without going
overboard.
The largest usable CMS minidisk you can define is 1 cylinder smaller
than the physical size of the volume where the minidisk resides (cyl 0
of the disk is used for the CP volume label).
If you need more space
This application now has 2 3390-9s.
The SFS sounds like a reasonable option.
Some tips about SFS:
1) Be sure to do the math for the size of the control disks and catalog
disks before you start seriously loading stuff into SFS and
overallocate, overallocate, overallocate; better too big than
Everyone, or almost everyone, does the same type of thing. You might
ask yourself how far back you need to have quick access to an old report
or listing. For things that are probably never going to be seen again,
write them to tape after x months. I let the OPERATOR and some other
service
Thanks David and Rich.
This application now has 2 3390-9s.
The SFS sounds like a reasonable option.
Suleiman Shahin
Date: Thu, 6 Sep 2007 20:31:55 -0400
From: [EMAIL PROTECTED]
Subject: Re: Size of Mdisk
To: IBMVM@LISTSERV.UARK.EDU
I wonder how large an m-disk I can allocate for
Greetings folks,
I know this is elementary, but I have to ask!
I have an application that sends lots of VSE/POWER listings to a CMS userid
with a hot reader that reads these files and stores them packed. The older
files get deleted and new files keep coming and so on.
I wonder how large an
44 matches
Mail list logo
