Re: S213 Abend Backing Up 530RES Using z/OS FDR
On Monday, 01/21/2008 at 10:02 EST, "Dale R. Smith" <[EMAIL PROTECTED]> wrote: > The x'05050505' in the KEY area indicates that this is a Format-5 DSCB. > Immediately following the key identifier, the x'0001' is the first free > track available, (relative to the beginning of the volume). The x'' > after that is the number of free cylinders in the extent, in this case > zero. The x'00' after that is the number of additional free tracks, also > zero. Other free extents would follow this one, (there are none). This > Format-5 DSCB indicates that there is NO free space on this volume, which > is what z/OS would believe also. Your observations match mine from last Friday http://listserv.uark.edu/scripts/wa.exe?A2=ind0801&L=ibmvm&T=0&P=32477 > My guess is that DITTO may be looking > for Format-1 and Format-3 DSCBs, (they describe space used by allocated > datasets), and not finding any on a VM volume, it is a assuming that the > entire volume is free. z/OS will not allocate a dataset on a properly > formatted VM volume, regardless of what DITTO shows. (whew!) I'm glad its a DITTO bug. It explains why my playing with the Format-5 DSCB didn't affect what DITTO reported. I looked up the S213-04: It is because a format *1* DSCB cannot be found. I was confusing the lack of a dataset called SYS1.VTOC with the lack of a VTOC. Tricksy, it is! Alan Altmark z/VM Development IBM Endicott
Re: S213 Abend Backing Up 530RES Using z/OS FDR
Thanks Kris! I was wrong about the location of the Format-4 DSCB, it
doesn't always follow immediately after the volume label record. The
volume label record is always the third record on cylinder 0 track 0. Th
e
volume label record has a pointer to the first record in the VTOC, (which
is always a Format-4 record). The Format-5 record is always the next
record after the Format-4 record. Here is part of the volume label recor
d
from Kris's z/VM 5.3 install: (I'm posting from the web interface, which
doesn't allow very long lines, so I'm only posting parts of the DDR TYPE
output.)
CYL HD 00 REC 003 COUNT 03 04 0050
4 0004 KEY LENGTH
0 E5D6D3F1*VOL1
00080 0050 DATA LENGTH
0 E5D6D3F1 E5E3C5F5 F3D9F000 0005 *VOL1VTE53R0.
The DATA portion of the label starts with VOL1, then the 6 character
volser, (VTE53R), a one byte "security" code, ("0" - x"F0"), and a five
byte pointer to the first record in the VTOC, (Format-4), in CCHHR
format. This label says the VTOC starts in cylinder 0, track 0, record 5
.
Here is part of the Format-4 DSCB, (record 5):
CYL HD 00 REC 005 COUNT 05 2C 0060
00044 002C KEY LENGTH
0 04040404 04040404 04040404 04040404
00096 0060 DATA LENGTH
0 F400 0005 0001 0D0B 000F
The KEY area actually contains 44 bytes of x'04' and the first byte of th
e
DATA area is x'F4', which indicates that this is a Format-4 DSCB record.
The x'0D0B' is the number of cylinders, (3339), and x'000F' is the number
of tracks per cylinder, (15).
Here is part of the Format-5 DSCB, (record 6):
CYL HD 00 REC 006 COUNT 06 2C 0060
00044 002C KEY LENGTH
0 05050505 0001
00096 0060 DATA LENGTH
0 F500
The x'05050505' in the KEY area indicates that this is a Format-5 DSCB.
Immediately following the key identifier, the x'0001' is the first free
track available, (relative to the beginning of the volume). The x''
after that is the number of free cylinders in the extent, in this case
zero. The x'00' after that is the number of additional free tracks, also
zero. Other free extents would follow this one, (there are none). This
Format-5 DSCB indicates that there is NO free space on this volume, which
is what z/OS would believe also.
Kris's CPVOL formatted T-Disk is very similar to what is above, except
that the volser is TESTRS and it is only 10, (x'0A'), cylinders in size!
(If anybody wants to see the data from the formatted T-Disk, let me know
and I will post it.)
It looks to me like the VM install volumes are formatted correctly and
that ICKDSF CPVOLUME also formats them correctly, (Format-5 DSCB shows no
free cylinders/tracks available). My guess is that DITTO may be looking
for Format-1 and Format-3 DSCBs, (they describe space used by allocated
datasets), and not finding any on a VM volume, it is a assuming that the
entire volume is free. z/OS will not allocate a dataset on a properly
formatted VM volume, regardless of what DITTO shows.
--
Dale R. Smith
"Always acknowledge a fault. This will throw those in authority off
their guard and give you an opportunity to commit more."
- Mark Twain
On Mon, 21 Jan 2008 16:35:57 +0200, Kris Buelens <[EMAIL PROTECTED]>
wrote:
>I sent Dale a TYPE of two cyl 0 head 0 (one of z/VM 5.3 and one of an
>"ICKDSF CPVOL"-ed Tdisk)
>--
>Kris Buelens,
>IBM Belgium, VM customer support
>
=
Re: MITIME settings are being set by ?
On Monday, 01/21/2008 at 02:55 EST, Shimon Lebowitz <[EMAIL PROTECTED]> wrote: > Alan, > Your email quotes mine, but I do not see any > connection between what I asked and your response. > > To clarify my question: > If an individual MITIME setting was *added* manually, > either for a device class or a specific address > (or range of addresses), when will those manual > settings be removed, and the MITIME values revert > to their defaults? MIH settings are forgotten when you IPL. Aside from spool files, the only things remembered across IPLs are: - The clock sequence number used in Diag 0x238 - Enable/Disable status of local non-SNA 3270s - System log messages (via SET LOGMSG) - List of CP-owned volumes - Status of real unit record devices (started, drained, forms, ...) - Accounting information Alan Altmark z/VM Development IBM Endicott
Re: MITIME settings are being set by ?
Brian, According to the CP Commands and Utilities Reference, the following defaults are provided: . DASD 00:15 . GRAF 01:10 . UR 01:00 . TAPE 10:00 . SWITCH05:00 . MISC 12:00 For DASD and TAPE, the supplied defaults will be used if and only if the subsystem does not return a primary timeout value. The supplied defaults, or for DASD and TAPE, the primary timeout value returned by the subsystem, will be put into place following an IPL. Subsequently, an authorized operator may change the values by way of a SET MITIME command. For DASD and TAPE subsystems, check the appropriate subsystem documentation for the primary timeout value returned, if any. John P. Baker Systems Engineer HFD Technologies From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Hamilton, Brian Sent: Monday, January 21, 2008 10:39 AM To: IBMVM@LISTSERV.UARK.EDU Subject: MITIME settings are being set by ? Where would I find the initial or override settings for MITIME's? I've looked in the SYSTEM config and on the AUTOLOG1 or 2 ids but I don't see any SET commands. e.g. MITIME ON 2060-2085 00:40 MITIME ON 2000-201F 00:40 MITIME ON 086262:30 MITIME ON 086120:50 MITIME ON 086020:50 MITIME ON DASD00:15 MITIME ON GRAF01:10 MITIME ON TAPE10:00 MITIME ON UR 01:00 MITIME ON SWITCH 05:00 MITIME ON MISC12:00
Re: MITIME settings are being set by ?
Alan, Your email quotes mine, but I do not see any connection between what I asked and your response. To clarify my question: If an individual MITIME setting was *added* manually, either for a device class or a specific address (or range of addresses), when will those manual settings be removed, and the MITIME values revert to their defaults? I had posted my question in response to someone (sorry I forgot who) saying: > I assume after every IPL they would be reset > to some initial setting since my recollection is that the system 'saves' them through IPLs, until a cold start. Thanks, Shimon Original message >Date: Mon, 21 Jan 2008 13:40:36 -0500 >From: Alan Altmark <[EMAIL PROTECTED]> >Subject: Re: MITIME settings are being set by ? >To: IBMVM@LISTSERV.UARK.EDU > >On Monday, 01/21/2008 at 11:13 EST, Shimon Lebowitz <[EMAIL PROTECTED]> >wrote: >> You know what they say "assume" stands for? >> >> I seem to remember that nothing but a cold start >> removes MITIME settings that have been added. >> >> Does anyone have anything black-on-white (or >> bit-on-CD) about this? > >The description of SET MITIME gives the default values. Looking at the >IBM ESS S/390 Command Reference (E10, E20, F10, F20), the "primary missing >interrupt timer interval" is 30 seconds (from the NEQ returned by the Read >Configuration Data CCW). > >Our test systems show 40 seconds. As a guess, the difference is due to >different models (e.g. DS6000, DS8000). > >Alan Altmark >z/VM Development >IBM Endicott
Re: MITIME settings are being set by ?
On Monday, 01/21/2008 at 11:13 EST, Shimon Lebowitz <[EMAIL PROTECTED]> wrote: > You know what they say "assume" stands for? > > I seem to remember that nothing but a cold start > removes MITIME settings that have been added. > > Does anyone have anything black-on-white (or > bit-on-CD) about this? The description of SET MITIME gives the default values. Looking at the IBM ESS S/390 Command Reference (E10, E20, F10, F20), the "primary missing interrupt timer interval" is 30 seconds (from the NEQ returned by the Read Configuration Data CCW). Our test systems show 40 seconds. As a guess, the difference is due to different models (e.g. DS6000, DS8000). Alan Altmark z/VM Development IBM Endicott
Re: MITIME settings are being set by ?
> (David - is this one backwards too? Different > web interface this time) Looks fine to me, although this week I'm less easily amused. 8-) -- db
Re: MITIME settings are being set by ?
You know what they say "assume" stands for? I seem to remember that nothing but a cold start removes MITIME settings that have been added. Does anyone have anything black-on-white (or bit-on-CD) about this? Shimon (David - is this one backwards too? Different web interface this time) Original message >I assume after every IPL they would be reset to some initial setting, I >guess this is what I'm looking for.
Re: MITIME settings are being set by ?
Brian, If you want to make some changes to the MITIME settings then you can put the set's in the AUTOLOG1 PROFILE EXEC. I have some in the AUTOLOG1 PROFILE EXEC to change the default for some OSA's to turn MITIME OFF for those selected devices. Loren Charnley, Jr. IT Systems Engineer Family Dollar Stores, Inc. (704) 847-6961 Ext. 3327 (704) 814-3327 [EMAIL PROTECTED] -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Hamilton, Brian Sent: Monday, January 21, 2008 10:49 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: MITIME settings are being set by ? No one has changed them nor would anyone else then myself know how to. I just checked the Operator id and there is nothing there. I assume after every IPL they would be reset to some initial setting, I guess this is what I'm looking for. Thanks -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Rich Smrcina Sent: Monday, January 21, 2008 10:42 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: MITIME settings are being set by ? Any user with sufficient privileges can change the MITIME. Check OPERATORs PROFILE EXEC as well. Hamilton, Brian wrote: > Where would I find the initial or override settings for MITIME's? > > > > I've looked in the SYSTEM config and on the AUTOLOG1 or 2 ids but I > don't see any SET commands. > > > > e.g. > > > > MITIME ON 2060-2085 00:40 > > MITIME ON 2000-201F 00:40 > > MITIME ON 086262:30 > > MITIME ON 086120:50 > > MITIME ON 086020:50 > > MITIME ON DASD00:15 > > MITIME ON GRAF01:10 > > MITIME ON TAPE10:00 > > MITIME ON UR 01:00 > > MITIME ON SWITCH 05:00 > > MITIME ON MISC12:00 > -- Rich Smrcina VM Assist, Inc. Phone: 414-491-6001 Ans Service: 360-715-2467 rich.smrcina at vmassist.com http://www.linkedin.com/in/richsmrcina Catch the WAVV! http://www.wavv.org WAVV 2008 - Chattanooga - April 18-22, 2008 - NOTE: This e-mail message contains PRIVILEGED and CONFIDENTIAL information and is intended only for the use of the specific individual or individuals to which it is addressed. If you are not an intended recipient of this e-mail, you are hereby notified that any unauthorized use, dissemination or copying of this e-mail or the information contained herein or attached hereto is strictly prohibited. If you receive this e-mail in error, notify the person named above by reply e-mail and please delete it. Thank you.
Re: MITIME settings are being set by ?
In lieu of finding the fact the it is being explicitly set, it is possible that the DASD subsystem is returning a value that VM is then using for the MITIME value. There is a note in the HELP CP SET MITIME text that indicates this. See note 2. Hamilton, Brian wrote: No one has changed them nor would anyone else then myself know how to. I just checked the Operator id and there is nothing there. I assume after every IPL they would be reset to some initial setting, I guess this is what I'm looking for. Thanks -- Rich Smrcina VM Assist, Inc. Phone: 414-491-6001 Ans Service: 360-715-2467 rich.smrcina at vmassist.com http://www.linkedin.com/in/richsmrcina Catch the WAVV! http://www.wavv.org WAVV 2008 - Chattanooga - April 18-22, 2008
Re: MITIME settings are being set by ?
No one has changed them nor would anyone else then myself know how to. I just checked the Operator id and there is nothing there. I assume after every IPL they would be reset to some initial setting, I guess this is what I'm looking for. Thanks -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Rich Smrcina Sent: Monday, January 21, 2008 10:42 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: MITIME settings are being set by ? Any user with sufficient privileges can change the MITIME. Check OPERATORs PROFILE EXEC as well. Hamilton, Brian wrote: > Where would I find the initial or override settings for MITIME's? > > > > I've looked in the SYSTEM config and on the AUTOLOG1 or 2 ids but I > don't see any SET commands. > > > > e.g. > > > > MITIME ON 2060-2085 00:40 > > MITIME ON 2000-201F 00:40 > > MITIME ON 086262:30 > > MITIME ON 086120:50 > > MITIME ON 086020:50 > > MITIME ON DASD00:15 > > MITIME ON GRAF01:10 > > MITIME ON TAPE10:00 > > MITIME ON UR 01:00 > > MITIME ON SWITCH 05:00 > > MITIME ON MISC12:00 > -- Rich Smrcina VM Assist, Inc. Phone: 414-491-6001 Ans Service: 360-715-2467 rich.smrcina at vmassist.com http://www.linkedin.com/in/richsmrcina Catch the WAVV! http://www.wavv.org WAVV 2008 - Chattanooga - April 18-22, 2008
Re: MITIME settings are being set by ?
Any user with sufficient privileges can change the MITIME. Check OPERATORs PROFILE EXEC as well. Hamilton, Brian wrote: Where would I find the initial or override settings for MITIME’s? I’ve looked in the SYSTEM config and on the AUTOLOG1 or 2 ids but I don’t see any SET commands. e.g. MITIME ON 2060-2085 00:40 MITIME ON 2000-201F 00:40 MITIME ON 086262:30 MITIME ON 086120:50 MITIME ON 086020:50 MITIME ON DASD00:15 MITIME ON GRAF01:10 MITIME ON TAPE10:00 MITIME ON UR 01:00 MITIME ON SWITCH 05:00 MITIME ON MISC12:00 -- Rich Smrcina VM Assist, Inc. Phone: 414-491-6001 Ans Service: 360-715-2467 rich.smrcina at vmassist.com http://www.linkedin.com/in/richsmrcina Catch the WAVV! http://www.wavv.org WAVV 2008 - Chattanooga - April 18-22, 2008
MITIME settings are being set by ?
Where would I find the initial or override settings for MITIME's? I've looked in the SYSTEM config and on the AUTOLOG1 or 2 ids but I don't see any SET commands. e.g. MITIME ON 2060-2085 00:40 MITIME ON 2000-201F 00:40 MITIME ON 086262:30 MITIME ON 086120:50 MITIME ON 086020:50 MITIME ON DASD00:15 MITIME ON GRAF01:10 MITIME ON TAPE10:00 MITIME ON UR 01:00 MITIME ON SWITCH 05:00 MITIME ON MISC12:00
Re: Backups and failover
Robert, Could you forward me a copy of the code you indicated below? Thanks so much. George Shedlock Jr AEGON Information Technology AEGON USA 502-560-3541 From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of RPN01 Sent: Friday, January 11, 2008 8:05 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Backups and failover For the guarded failover portion, we have a rexx script and server that keeps track of which system the guest was last booted on. If it is logged in on the same host, the system just starts up. If it is autologged on the other host, it immediately logs off (it's 191 disk is R/O, so no damage done.) If it is logged in at a terminal on the other host, there is a prompt telling the user that it was last brought up on host, and do you really want to bring it up here? Answering no causes a logout. Answering yes starts the boot process, which includes logging the new boot into the system and the process is ready to work in the other direction. I have this code available, if you'd like a copy -- .~.Robert P. Nix Mayo Foundation /V\RO-OE-5-55 200 First Street SW / ( ) \ 507-284-0844 Rochester, MN 55905 ^^-^^ - "In theory, theory and practice are the same, but "Join the story... Ride Ural." in practice, theory and practice are different." On 1/10/08 10:33 AM, "Karl Kingston" <[EMAIL PROTECTED]> wrote: We just installed z/VM 5.3. We have 2 systems running. VM1 and VM2.Right now, all of our Linux guests (about 5) are on VM1. They also have a directory entry on VM2 (but password set to NOLOG). 1) What's the best way to do failover if we need to get something over? Right now, my plan is basically to log into VM2 and change the NOLOG to a password and then start the guest. Basically I want to avoid having our Operations staff make mistakes and start 2 instances of the same linux guest (on 2 VM systems). 2) We use FDR/ABR on our z/OS side for backing up for Disaster Recovery.We would like to keep using FDR.Now I know I can get clean backups if the systems are shut down. Are there any gotcha's if I take a FDR full dump against say 530RES or 530SPL while the system is up? \ 3) last of all, how often does VM get backed up when it's just used as a Linux server system?? Thanks
Re: S213 Abend Backing Up 530RES Using z/OS FDR
I sent Dale a TYPE of two cyl 0 head 0 (one of z/VM 5.3 and one of an "ICKDSF CPVOL"-ed Tdisk) 2008/1/18, Dale R. Smith <[EMAIL PROTECTED]>: > The VTOC should start right after the volume label. The first record in > > the VTOC should be the FMT4 (Format-4) DSCB record. The second record in > > the VTOC should be the FMT5 (Format-5) DSCB record. Here is a pointer to > > the layout of the Format-4 DSCB: http://publibz.boulder.ibm.com/cgi- > bin/bookmgr/BOOKS/dgt2s330/1.1.1.5? > SHELF=ez2zo10f.bks&DT=20050617115137&CASE= > Layout for the Format-5 DSCB: http://publibz.boulder.ibm.com/cgi- > bin/bookmgr/BOOKS/dgt2s330/1.1.1.6?SHELF=ez2zo10f.bks&DT=20050617 > 115137 > > Unfortunately, I don't have access to a VM system currently, or I would > > take a look myself. Kris, if you want to email me the the output of DDR > > TYPE, I'm willing to take a look at it and try to decipher it! :-)> > > -- > Dale R. Smith > > "Duct tape is like the Force, it has a dark side, it has a light side, > and it holds the universe together." > - Carl Zwanig > > On Fri, 18 Jan 2008 17:17:32 +0200, Kris Buelens <[EMAIL PROTECTED]> > > wrote: > > >DDR TYPE of cyl 0, track0 is still a lot of data. One should know which > > >fields to display. > > > >2008/1/18, Dale R. Smith <[EMAIL PROTECTED]>: > >> > >> IIRC, ICKDSF CPVOLUME FORMAT is supposed to set the FMT5 DSCB in > >> the "VTOC" for a volume to indicate that there is no free space on the > > >> > >> volume. The FMT4 DSCB should contain the size of the volume. I'm not > > >> > >> sure what DITTO is looking at, but z/OS should be using the FMT5 DSCB. > > >> > >> What does a DDR TYPE of cylinder 0, track 0 show? > >> > >> -- > >> Dale R. Smith > -- Kris Buelens, IBM Belgium, VM customer support
Re: DB2 7.5 manuals
> I take it, from previous posts, that no one has found the new > manuals for DB2 7.5. I have asked ID development in the Toronto Lab where the 7.5 pubs are online. Jim
