Hello Listers,
I am looking into XLINK. The main goal is to be able to determine if a
minidiskextent on DASD is already in R/W use on a different VM. This way
we
could provide for an easy switch for linux guests from one VM to another.
We do not setup the full CSE here. SPOOL and DIRMAINT are
Hi all,
We are currently installing a second-level z/VM via DVD installation and we
are getting this error when issuing the command:
pipe ftpget -h ipaddr -u user -p password -d ftpdir -v BEF -DVDEOF
-f CKD222* | unpack | eckdrest
CKD222*
On the advice of a respected member of the list, I tried
adding a LOT of virtual storage to MAINT, but even with 512M
I get the same result. This makes sense, since the error message
is not mentioning any problem loading the content of the segment.
This is happening in VMFBDSEG EXEC at lines
On Tue, Mar 17, 2009 at 11:41 AM, jose raul baron jba...@calculo-sa.es wrote:
Hi all,
We are currently installing a second-level z/VM via DVD installation and we
are getting this error when issuing the command:
pipe ftpget -h ipaddr -u user -p password -d ftpdir -v BEF -DVDEOF
-f CKD222* |
Rob, just a quick note. The size for minidisk must be EXACTLY of 5 cyl.
Not less AND NOT MORE :-)
if more than 5 cyl. are defined you get RC=1.
This goes too with the other disks that must be EXACTLY of:
- Minidisk 22CC: 5 cyl.
- Minidisk 2CF1: 120 cyl.
BRGDS and thank you again for
Search your A-disk for LSEGMAP and PSEGMAP files, they may tell the
segment storage is full.
VMSES's SEGGEN usage is an area for improvement: all debugging
information is missing.
2009/3/17 Shimon Lebowitz shimon...@gmail.com:
On the advice of a respected member of the list, I tried
adding a
XLINK makes it possible to protect multiple minidisks on a shared
pack. XLINK checks cylinder ranges.
You can test this
- on VMA, use LINK userid vdev 1 M
- on VMB try LINK userid vdev 1 M
and this should fail, CP should tell userid vdev not linked, R/W by VMA
Note that there are no commands to
Hi Rob. Yes, I have looked into my disk and it varied from being empty
to be filled with lots of files (67 files to be more accurate). I suppose
this is no big problem, but just wanted to make sure. (The old costume to
look for RC=0's).
I will take your advise and go on.
Thanks for your
On Tue, Mar 17, 2009 at 12:32 PM, Kris Buelens kris.buel...@gmail.com wrote:
XLINK makes it possible to protect multiple minidisks on a shared
pack. XLINK checks cylinder ranges.
Incorrect Kris. XLINK only protects the starting cylinder. However, as
long as magic ensures identical directories,
Thank you to both Dennis and Mark. I had the mount commands in my DTCPARMS,
they just weren't syntactically correct. Everything appears to be fine now...
Mark Wiggins
-Original Message-
From: Mark Cibula [mailto:cibul...@us.ibm.com]
Sent: Monday, March 16, 2009 6:11 PM
Subject: Re: New
If you use anything larger than a 3390-3 - I believe you'll need the first 9
cylinders (0-8) reserved for XLINK data. Not too bad if you're just doing
the z/VM volumes - some extent rearranging -- but it can be a major effort
if volumes with Linux data are included.
Scott
On Tue, Mar 17, 2009
On zVM 5.3, I have in my CMS RDR Queue a file with 52535 records but when I
peek it, I only see 46182.
My defined storage is 256M and my effective Peek command is Peek 2345 (for *
Why Can't I see the rest of the file?
Thanks.
Suleiman Shahin
My guess is that the 52535 number indicates the number of 80 byte records..
but when you go into XEDIT, you're seeing the number of records with CR/LF
(variable length perhaps?) being honored.
Scott
On Tue, Mar 17, 2009 at 8:27 AM, Suleiman Shahin s_s_sha...@hotmail.comwrote:
On zVM 5.3, I
Hello Suleiman Shahin,
Your defaults are set to low.
VM command DEFAULTS
will show you what is set.
Ed Martin
Aultman Health Foundation
330-588-4723
ext 40441
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On
It does depend on what the format of the file is. A reader or punch
accepts cards, that is 80 bytes per record (RDR also handles console
prt files, but that's a deviation to the architecture, 80 should it
be, no more no less.
What if you want to punch a file wide file (SENDFILE uses a PUCNH
And yet one more possibility: the file is in NetData format.
NetData format is what SENDFILE creates, taking files with long records,
breaking them into 80-byte records (including some control information at
the start of each). When you PEEK the file in the reader, or RECEIVE it
to disk, the
On Mar 17, 2009, at 5:56 AM, Rob van der Heij wrote:
Are you sure the disk is R/W and that it is the right size? I
tried to do it from the quick ref guide and found that it was
missing some of the steps that you need (and are only in the real
book).
You mean the missing 22cc and 2cf1
Sure, your defaults could be set to low as Ed suggested, but the
default low where you would not see everything is like 200, so I
don't think that is the problem.
My guess is that Scott's note came close: But the format is NETDATA
rather than CR/LF per se. If the file was sent in NETDATA
Shimon,
VMSES/E is a great tool, but the clarity is not quite the best at some
times It seems that error message from building segments is a particular
weak point to me, too.
One command that has helped me understand VMSES/E a lot better (until I
forget again!) is one I use after any VMSES/E
Also: for a 3390-9 you can move the CSE area. When you define the
volume in SYSTEM CONFIG you can include a parameter that indicates the
starting cylinder of the CSE are - this means you can move it to the
end of a volume if you want to CSE protect a volume that already has
minidisks on it.
The
On the z/VM download page there is a very good package XBROWSE that does not
use XEDIT or large amounts of storage to 'peek' at large files.. Many very nice
features i.e. book marking the file you are browsing.. Take a look at it I
think it is pretty good.
-Original Message-
From: The
On Tuesday, 03/17/2009 at 10:51 EDT, Richard Troth vmcow...@gmail.com
wrote:
My guess is that Scott's note came close: But the format is NETDATA
rather than CR/LF per se. If the file was sent in NETDATA format,
then RDRLIST will of course show the number of 80 byte records punched
to you,
My apologies for that earlier post...misdirected.
I have to accept Alan's statement! I played with the file a few ways! Receive
receives the short file same as peek. The pipe from Kris loaded the count
indicated, but mangled the file beyond recognition :(-
Peek did not have any complaints only showed the record size was 89..
Thanks all!
You might want to look at SHOW. I find that nice for READER files as
well as disk files.
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On
Behalf Of Huegel, Thomas
Sent: Tuesday, March 17, 2009 8:07 AM
To: IBMVM@LISTSERV.UARK.EDU
On Tuesday, 03/17/2009 at 11:01 EDT, Mike Walter mike.wal...@hewitt.com
wrote:
VMSES/E is a great tool, but the clarity is not quite the best at some
times
It seems that error message from building segments is a particular weak
point
to me, too.
Please report problems with
On Tue, Mar 17, 2009 at 3:46 PM, Adam Thornton athorn...@sinenomine.net wrote:
On Mar 17, 2009, at 5:56 AM, Rob van der Heij wrote:
Are you sure the disk is R/W and that it is the right size? I
tried to do it from the quick ref guide and found that it was
missing some of the steps that
Apparently I wan't clear enough in my append
My PIPE was meant to show how a RAW RDR file looks like. PIPE didn't
mangle anything, it shows the mess created by SENDFILE, exactly as it
sits in the VM spool. Not a complete mess, because PEEK, RECEIVE,
NETDATA, ... know how to unmangle. If
On Mar 17, 2009, at 11:23 AM, Rob van der Heij wrote:
It really does not have to be in MAINT - you don't want to run the 2nd
level system in MAINT anyway, so why mess with things. It's also only
needed briefly in the process, so for me 3 T-disks would be fine. And
in theory when you ship the GA
Yes, note SEGGEN, it has been painful since day one.
I no longer had problems since the day I had my own front-end (BLDSEG
EXEC), it releases most minidisks and segments
'PIPE (end ?)',
'Command QUERY ACCESSED|Drop 1',
'| NFind S|NFind Y|NFind A|NFind B|NFind D'||,
'| Spec W4 1 1-*
I just installed a virgin z/VM 5.4 with all products on filepool
rather than on minidisk.
I only tweaked it enough to get a TCPIP stack up and running so that I
could FTP the RSU over to it, DETERSE it, and apply service. I've
done literally nothing else to the system.
0 * * * Top
The component is cpsfs or cmssfs ... Not cp or cms which are for minidisks.
On 3/17/09 3:36 PM, Adam Thornton athorn...@sinenomine.net wrote:
I just installed a virgin z/VM 5.4 with all products on filepool
rather than on minidisk.
I only tweaked it enough to get a TCPIP stack up and
On Mar 17, 2009, at 2:43 PM, Neale Ferguson wrote:
The component is cpsfs or cmssfs ... Not cp or cms which are for
minidisks.
I just tried to run SERVICE ALL RPTF0168
Which, you know, *should* be able to figure it out. It has in the past.
Adam
Adam,
It looks like SERVICE is trying to service LE instead of LESFS. There
are a couple of items in the PSP bucket that have to do with SFS, but
the descriptions aren't an exact match for this problem. Did you read
all of the ZVM540 subsets and do what they said?
It's certainly possible to
On Mar 17, 2009, at 2:53 PM, O'Brien, Dennis L wrote:
Adam,
It looks like SERVICE is trying to service LE instead of LESFS. There
are a couple of items in the PSP bucket that have to do with SFS, but
the descriptions aren't an exact match for this problem. Did you read
all of the ZVM540
I am out of the office until 03/19/2009.
I will be out of the office Tuesday 3/17 and return Thursday 3/19.
Note: This is an automated response to your message FW: ASSEMBLER-LIST
Digest - 14 Mar 2009 to 15 Mar 2009 (#2009-72) sent on 3/17/09 8:35:19.
This is the only notification you will
On Tuesday, 03/17/2009 at 04:11 EDT, Adam Thornton
athorn...@sinenomine.net wrote:
All I did was download the RSU and then follow the Service Procedure
paragraph on the Quick Install Guide.
Because there's only so much you can put on one page and have it remain
legible, the Quick Guides are
On Mar 17, 2009, at 5:03 PM, Alan Altmark wrote:
On Tuesday, 03/17/2009 at 04:11 EDT, Adam Thornton
athorn...@sinenomine.net wrote:
All I did was download the RSU and then follow the Service
Procedure
paragraph on the Quick Install Guide.
Because there's only so much you can put on one
Umm -- how about 2 pages or 3 .. a foldout like all those 'quick start'
guides I get with just about anything I purchase nowadays?
There's got to be a happy medium between a single page and several hundred?
(oops - and I see that Adam is maybe wondering the same?)
Scott
p.s. I'll even put
OK, so now instead of reading some we will read nothing.
After you have done something 20 times you do not need a 3000 page
manual, you need something quick.
I vote to keep them.
David Dean
Information Systems
*bcbstauthorized*
From: The IBM z/VM
So, any idea why the DOSINST and CMSDOS segments didn't want to rebuild
(I stupidly had CF1 accessed and was screwing around with SYSTEM CONFIG
while PUT2PROD was running, so I had to rebuild CMS and all the segments
the old-fashioned way)? I seem to recall this failing before sometime.
I don't
No prob, Phil. I suspect a lot of us old BAL-heads enjoyed it.
-Chip-
On 3/17/09 12:35 Phil Smith said:
My apologies for that earlier post...misdirected.
I also vote for keeping the Quick Guides... I think they are the best
thing since sliced bread!
The only suggestion I would make would be to 'simplify'; them by completely
separating the 1st level and 2nd level install instructions,.
I find that skipping around the other parts causes more
Ditto here. Installing VMWare is a 90 page booklet. The one page install was a
great comparison.
On 3/17/09 9:45 PM, Mike Hammock mike.hamm...@mainline.com wrote:
I also vote for keeping the Quick Guides... I think they are the best
thing since sliced bread!
I'm not sure how the file originated, but I think this explanation makes sense.
I had no limit on number of records peeked. (Peek (for *)
Thanks every one.
Suleiman Shahin
Date: Tue, 17 Mar 2009 09:46:30 -0500
From: mike.wal...@hewitt.com
Subject: Re: Puzzle or what?
To:
On Tuesday, 03/17/2009 at 09:45 EDT, Mike Hammock
mike.hamm...@mainline.com wrote:
I also vote for keeping the Quick Guides... I think they are the best
thing since sliced bread!
The only suggestion I would make would be to 'simplify'; them by
completely
separating the 1st level and 2nd
46 matches
Mail list logo
