'STREAMSTATE INPUT' should not be required here...
My guess is that process has set the returncode to 0, so your
do-loop condition check is not testing the return code of READTO.
The pseudocode also suggests your stage does delay the record. You
should code it like this:
'PEEKTO INPUT' /* Get
Thanks, Alan. We may need that mod too. We are getting ready to extend
our channels, but aren't quite there yet.
Regards,
Richard Schuh
-Original Message-
From: The IBM z/VM Operating System
[mailto:[EMAIL PROTECTED] On Behalf Of Alan Ackerman
Sent: Monday, June 02, 2008 10:50
Mike,
This is Alan's co-worker. This happened several years ago, so I could
be fuzzy on the details.
In our case, the devices were check sorters, not tape drives. They were
bus-and-tag devices that should have been on a converted channel.
Someone was trying to save channels, so they were on an
Dennis,
I suspected that the problem may have involved B/T to ESCON conversion.
You were likely using the CNT USD for ESCON extension with an Optica B/T
convertor (which CNT re-sold as the NSBT).
We provided UIMs that added custom device types such as B/T Tape models
connected to ESCON channels,
The other data center is ours, just not a twin of the center where VM
resides. Contractual first rights are not a consideration.
The idea of two different VM:Backup machines and jobs might not be so
far fetched. There is no requirement that the two backups be identical
or nearly so. The
On Mon, Jun 9, 2008 at 3:08 PM, Kris Buelens [EMAIL PROTECTED] wrote:
'STREAMSTATE INPUT' should not be required here...
In most cases the suitable approach is to use
signal on error
do forever
peekto
.. process..
readto
streamstate output
end
error: return rc * ( rc 12 )
The
Perhaps by measuring the amount of tape left on the spindle? A light,
possibly laser, shining on a tangent to the spindle at a specified
height could be detected only when the tape remaining is not thick
enough to block the light. This would remove any dependence on stickers
which are supposed to
Hello all,
I’m having a problem restoring minidisks which I backed up using DDR.
Backing them up all on one tape.
I batched up a bunch of minidisks, a quick sample is below:
SYSPRINT CONS
PROMPTS OFF
INPUT 12C4 3390
OUTPUT 181 3590 (LEAVE
DUMP ALL
Hi Howard. Use the “( LEAVE” option as you did on the dump example. The
default is to unload tape after the command completes. The first restore all
will unload the tape so the other will try to run with and unloaded tape drive.
Hans
From: The IBM z/VM Operating System [mailto:[EMAIL
Howard,
You might want to try using the SKIP parm on the INPUT statement
to bypass the first file. My guess is that would allow you to restore
the subsequent disks without issue.
Ed Zell
Illinois Mutual Life
(309) 636-0107
From: The IBM z/VM
The first minidisk being empty has nothing whatsoever to do with it.
That is not an error condition unless the disk has not been initialized
and had the Track Capacity Record, R0, written on each track. If that is
the case, there is no r0 on any track and no volume serial on the disk.
DDR happily
Agreed. It would appear that Hans was right on when he mentioned using
the (LEAVE parm on the restores so that the tape does not unload. I
was
just taking a guess based on what I knew at the time.
Ed
From: The IBM z/VM Operating System [mailto:[EMAIL
We started with vSwitch grants in SYSTEM CONFIG, then moved to reading lists
of Linux guests and dynamically granting them to the vSwitch. We then
switched (no pun inteneded) to COMMAND statements in each CP Directory to
grant the vSwitch and couple the NIC to the vSwitch. This seemed to be the
Thanks all. We will take a closer look at the source disks.
Schuh, Richard [EMAIL PROTECTED] 6/9/2008 5:21 PM
The first minidisk being empty has nothing whatsoever to do with it.
That is not an error condition unless the disk has not been initialized
and had the Track Capacity Record, R0,
Is there a way to change the threshold for initiation of a CDB
dynamically or is it only in the start-up? Searching the File Pool
Planning, Administration and Operation manual has so far turned up a
blank.
Regards,
Richard Schuh
On Monday, 06/09/2008 at 04:06 EDT, Schuh, Richard [EMAIL PROTECTED]
wrote:
I would hope that the use of stickers to denote EOT would have gone out
way back in my career.
Reflective stickers went away with the 3480. It introduced a servo
track that the drive uses to know the position of the
I just knew that you (IBM) had to have done something about those
stickers. They were a PITA.
Regards,
Richard Schuh
-Original Message-
From: The IBM z/VM Operating System
[mailto:[EMAIL PROTECTED] On Behalf Of Alan Altmark
Sent: Monday, June 09, 2008 3:09 PM
To:
17 matches
Mail list logo
