Re: VM64814 information
On Thursday, 09/23/2010 at 11:27 EDT, Alan Ackerman wrote: > Support Statement: > IBM is supporting this in customer test environments until APAR > VM64816 becomes available later this year (2010). IBM will > support all z/VM production environments at that time. > > That makes it sound like a beta! Is this safe to put on? What constitute > "customer test > environments"? Where should we NOT install it? You asked some specific questions that I forgot to answer: 1. Yes, VM64814 is a beta program for the XRC support. The beta will end when the PTF for APAR VM64816 is available. Availability was announced to be December, but it could, of course, come sooner. 2. Development assures me that it is safe to install the PTF for VM64814 as long as you don't engage the STP-related items that the PTF enables. Install it on any system you like, but don't turn on any of the stuff Matt described in his post, as it isn't an 'open' beta. When VM64816 closes, then it will be safe for everyone to enable. Alan Altmark z/VM and Linux on System z Consultant IBM System Lab Services and Training ibm.com/systems/services/labservices office: 607.429.3323 alan_altm...@us.ibm.com IBM Endicott
Re: VM64814 information
I don't think it's either. I think its an artifact of how IBM promotes changes. From a process perspective, a PTF is supposed to fix something, not provide new function. Because the PTF process was co-opted as the method for new function delivery by a different set of developers, the entire PTF process is not used. Thus, the paperwork doesn't get done. From: The IBM z/VM Operating System on behalf of Alan Ackerman Sent: Sun 9/26/2010 2:07 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VM64814 information So is VM64814 a beta, test, whatever, or not? When I want to know about something, the first thing I look at is IBMLink= . I don't usually look at announcement letters. If I don't get an answer, I will post a question, e= ither on IBMLink or here. Wouldn't it be cheaper for IBM to just put the description in the APAR in= stead of forcing people to ask? OK, maybe it wasn't secrecy, just bureaucratic incompetence. I apolo= gize. On Sat, 25 Sep 2010 21:40:56 -0400, Alan Altmark wrote: >On Thursday, 09/23/2010 at 11:27 EDT, Alan Ackerman > wrote: >> I went and looked at APARs VM64814 and VM64816 on IBMLink. Almost no >> information! They both simply say NF NEWFUNCT, with no description. >> Come on IBM, why the secrecy? > >Such accusations! From the z/VM 6.1 July 22 announcement letter 210-23= 4: > "XRC time stamping support is provided with the PTFs for APAR VM64814 a= nd >VM64816 for z/VM V5.4 and z/VM V6.1, all of which have a planned >availability date of December 31, 2010." Not to mention Matt's detaile= d >response to Dennis' question on the same APARs. > >As to why the APARs don't have their descriptions, I'm guessing it's jus= t >a paperwork snafu, not a conspiracy. > >That said, sometimes we do choose to have a beta program and those PTFs >are indeed labeled as "new function" until the beta is complete. > >Alan Altmark > >z/VM and Linux on System z Consultant >IBM System Lab Services and Training >ibm.com/systems/services/labservices >office: 607.429.3323 >alan_altm...@us.ibm.com >IBM Endicott >= == == ==
Re: VM64814 information
So is VM64814 a beta, test, whatever, or not? When I want to know about something, the first thing I look at is IBMLink . I don't usually look at announcement letters. If I don't get an answer, I will post a question, e ither on IBMLink or here. Wouldn't it be cheaper for IBM to just put the description in the APAR in stead of forcing people to ask? OK, maybe it wasn't secrecy, just bureaucratic incompetence. I apolo gize. On Sat, 25 Sep 2010 21:40:56 -0400, Alan Altmark wrote: >On Thursday, 09/23/2010 at 11:27 EDT, Alan Ackerman > wrote: >> I went and looked at APARs VM64814 and VM64816 on IBMLink. Almost no >> information! They both simply say NF NEWFUNCT, with no description. >> Come on IBM, why the secrecy? > >Such accusations! From the z/VM 6.1 July 22 announcement letter 210-23 4: > "XRC time stamping support is provided with the PTFs for APAR VM64814 a nd >VM64816 for z/VM V5.4 and z/VM V6.1, all of which have a planned >availability date of December 31, 2010." Not to mention Matt's detaile d >response to Dennis' question on the same APARs. > >As to why the APARs don't have their descriptions, I'm guessing it's jus t >a paperwork snafu, not a conspiracy. > >That said, sometimes we do choose to have a beta program and those PTFs >are indeed labeled as "new function" until the beta is complete. > >Alan Altmark > >z/VM and Linux on System z Consultant >IBM System Lab Services and Training >ibm.com/systems/services/labservices >office: 607.429.3323 >alan_altm...@us.ibm.com >IBM Endicott > = == ==
Re: VM64814 information
On Thursday, 09/23/2010 at 11:27 EDT, Alan Ackerman wrote: > I went and looked at APARs VM64814 and VM64816 on IBMLink. Almost no > information! They both simply say NF NEWFUNCT, with no description. > Come on IBM, why the secrecy? Such accusations! From the z/VM 6.1 July 22 announcement letter 210-234: "XRC time stamping support is provided with the PTFs for APAR VM64814 and VM64816 for z/VM V5.4 and z/VM V6.1, all of which have a planned availability date of December 31, 2010." Not to mention Matt's detailed response to Dennis' question on the same APARs. As to why the APARs don't have their descriptions, I'm guessing it's just a paperwork snafu, not a conspiracy. That said, sometimes we do choose to have a beta program and those PTFs are indeed labeled as "new function" until the beta is complete. Alan Altmark z/VM and Linux on System z Consultant IBM System Lab Services and Training ibm.com/systems/services/labservices office: 607.429.3323 alan_altm...@us.ibm.com IBM Endicott
Re: VM64814 information
I went and looked at APARs VM64814 and VM64816 on IBMLink. Almost no info rmation! They both simply say NF NEWFUNCT, with no description. Come on IBM, why the secrecy ? VM64814 says: COMMENTS: New Function Support Statement: IBM is supporting this in customer test environments until APAR VM64816 becomes available later this year (2010). IBM will support all z/VM production environments at that time. That makes it sound like a beta! Is this safe to put on? What constitute "customer test environments"? Where should we NOT install it? Alan Ackerman On Tue, 21 Sep 2010 10:19:50 -0700, O'Brien, Dennis L wrote: >I understand that VM64814 adds XRC timestamp support. The PTF's are ava ilable. The z/VM platform update at SHARE mentioned that there would be a SYSTEM CONFIG ch ange to activate it. Where do I find information on that? The recent SSL changes had a nice w eb page with all the details, and one of the PTF's described the changes. I haven't been able to find any of that for VM64814. The APAR and PTF just say "new function". If it weren't for SH ARE, and someone who told me what the APAR was for, I'd have no idea what new function I was p utting in, or that an additional step was required to activate it. > >I found a couple of references on the IBM site that said VM64814 and VM6 4816 would add the function. VM64816 is "assigned to a programmer". Does VM64814 do anythi ng without VM64816? Will VM64816 provide the documentation? > Dennis O'Brien > >"A slipping sear could let your M203 grenade launcher fire when you leas t expect it. That would make you quite unpopular in what's left of your unit." -- August 1993 is sue of PS Magazine, preventive maintenance magazine of the US Army > = == =
Re: VM64814 information
Date: 09/21/2010 04:36 PM
Subject:Re: VM64814 information
Sent by:The IBM z/VM Operating System
Matt,
I'm running z/VM 5.4.0, so the applicable PTF is UM33146. I looked in
UM33146 $PTFPART, but I didn't find a UMEMO section. Is there somewhere
else that I should be looking for the memo? I'll order the 6.1.0 PTF and
see if it's there.
Dennis
"A slipping sear could let your M203 grenade launcher fire when you least
expect it. That would make you quite unpopular in what's left of your
unit." -- August 1993 issue of PS Magazine, preventive maintenance magazine
of the US Army
-Original Message-
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On
Behalf Of Matthew Rosato
Sent: Tuesday, September 21, 2010 13:15
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: [IBMVM] VM64814 information
Hi Dennis,
There is a memo-to-users file included with VM64814 that describes the new
FEATUREs statements that are included as part of XRC timestamping support.
I believe that these statements are the additional step that you are
referring to.
You can certainly pick up VM64814 today and use XRC timestamping. VM64816
will bring along a few internal changes, but nothing that would prevent
you from using XRC timestamping today.
Thanks,
Matt
Matthew J. Rosato
z/VM I/O Development
From: "O'Brien, Dennis L"
To: IBMVM@LISTSERV.UARK.EDU
Date: 09/21/2010 01:20 PM
Subject:VM64814 information
Sent by:The IBM z/VM Operating System
I understand that VM64814 adds XRC timestamp support. The PTF's are
available. The z/VM platform update at SHARE mentioned that there would be
a SYSTEM CONFIG change to activate it. Where do I find information on
that? The recent SSL changes had a nice web page with all the details, and
one of the PTF's described the changes. I haven't been able to find any of
that for VM64814. The APAR and PTF just say "new function". If it weren't
for SHARE, and someone who told me what the APAR was for, I'd have no idea
what new function I was putting in, or that an additional step was required
to activate it.
I found a couple of references on the IBM site that said VM64814 and
VM64816 would add the function. VM64816 is "assigned to a programmer".
Does VM64814 do anything without VM64816? Will VM64816 provide the
documentation?
Dennis O'Brien
"A slipping sear could let your M203 grenade launcher fire when you least
expect it. That would make you quite unpopular in what's left of your
unit." -- August 1993 issue of PS Magazine, preventive maintenance magazine
of the US Army
Re: VM64814 information
Matt,
I found it. The 5VMCPR40 MEMO file on MAINT was from the RSU, even though I
applied this PTF later. Maybe it's hiding somewhere until I do PUT2PROD, or
maybe that file just doesn't get loaded for COR service. Anyway, it was in the
envelope file when I looked for it. Thanks.
Dennis
"A slipping sear could let your M203 grenade launcher fire when you least
expect it. That would make you quite unpopular in what's left of your unit."
-- August 1993 issue of PS Magazine, preventive maintenance magazine of the US
Army
-Original Message-
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf
Of Matthew Rosato
Sent: Tuesday, September 21, 2010 14:40
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: [IBMVM] VM64814 information
Dennis,
You should be able to find the text in the MEMO file (for example,
5VMCPR40 MEMO). If you ordered electronically, the MEMO should be located
in the SHIPDOCS file.
In case others have the same question, here's the contents of the memo as
they relate to VM64814:
Memo to Users for APAR VM64814
The following configuration file operands have been added by this APAR:
FEATURES ENABLE STP_Timestamping
tells CP to enable the STP protocol (if the STP facility is
installed) and apply timestamps to all XRC-capable DASD devices.
FEATURES ENABLE STP_TIMEZone
FEATURES ENABLE STP_TZ
tells CP to enable the STP protocol (if the STP facility is
installed) and obtain timezone information automatically from the STP
server.
FEATURES ENABLE XRC_OPTional
when STP_Timestamping is also enabled, this will allow non-
timestamped I/O to be issued whenever STP is in an unsynchronized
state, as opposed to deferring I/O until STP synchronization com-
pletes.
FEATURES ENABLE XRC_TEST
tells CP to timestamp I/O regardless of STP availability. This
option is meant only for vendor and testing purposes, and can only be
specified for systems running within a virtual machine.
The following commands have been added by this APAR:
QUERY STP
returns information regarding the current state of STP usage on the
system.
The following commands have been modified by this APAR:
DEFINE TIMEZONE
this command cannot be issued while STP_TIMEZone is in effect.
SET TIMEZONE
this command cannot be issued while STP_TIMEZone is in effect.
QUERY TIMEZONE
this command was updated to include STP timezone boundary information
when STP_TIMEZone is in effect.
The following messages have been added:
HCP985E
HCP986I
HCP987E
HCP988I
The following publications have been modified:
CP Messages and Codes (GC24-6119-07 and GC24-6177-01)
New entries were added for the messages referenced above.
CP Planning and Administration (SC24-6083-07 and SC24-6178-01)
New entries were added for the FEATURES statements described above.
CP Commands and Utilities Reference (SC24-6081-07 and SC24-6175-01)
A new entry was added for QUERY STP.
Entries for SET TIMEZONE, DEFINE TIMEZONE and QUERY TIMEZONE were
updated.
System Operation (SC24-6121-03 and SC24-6233-01)
Added the following paragraph to Chapter 3 'Bringing up the System'
under the heading 'Setting the Time of Day Clock':
If your hardware is enabled and configured for Server Time Protocol
(STP) and
this feature has been enabled in your configuration file (using the
STP_TIMESTAMPING or STP_TZ features statements), you will not receive
any
prompts to change the TOD clock. Instead, STP is automatically used to
initialize the TOD clock with the STP-coordinated TOD value. When the
TOD
clock is initialized, you will receive message HCP986I "TOD Clock
Synchronized via STP."
Hope this helps,
Matt
Matthew J. Rosato
z/VM I/O Development
From: "O'Brien, Dennis L"
To: IBMVM@LISTSERV.UARK.EDU
Date: 09/21/2010 04:36 PM
Subject:Re: VM64814 information
Re: VM64814 information
Dennis,
You should be able to find the text in the MEMO file (for example,
5VMCPR40 MEMO). If you ordered electronically, the MEMO should be located
in the SHIPDOCS file.
In case others have the same question, here's the contents of the memo as
they relate to VM64814:
Memo to Users for APAR VM64814
The following configuration file operands have been added by this APAR:
FEATURES ENABLE STP_Timestamping
tells CP to enable the STP protocol (if the STP facility is
installed) and apply timestamps to all XRC-capable DASD devices.
FEATURES ENABLE STP_TIMEZone
FEATURES ENABLE STP_TZ
tells CP to enable the STP protocol (if the STP facility is
installed) and obtain timezone information automatically from the STP
server.
FEATURES ENABLE XRC_OPTional
when STP_Timestamping is also enabled, this will allow non-
timestamped I/O to be issued whenever STP is in an unsynchronized
state, as opposed to deferring I/O until STP synchronization com-
pletes.
FEATURES ENABLE XRC_TEST
tells CP to timestamp I/O regardless of STP availability. This
option is meant only for vendor and testing purposes, and can only be
specified for systems running within a virtual machine.
The following commands have been added by this APAR:
QUERY STP
returns information regarding the current state of STP usage on the
system.
The following commands have been modified by this APAR:
DEFINE TIMEZONE
this command cannot be issued while STP_TIMEZone is in effect.
SET TIMEZONE
this command cannot be issued while STP_TIMEZone is in effect.
QUERY TIMEZONE
this command was updated to include STP timezone boundary information
when STP_TIMEZone is in effect.
The following messages have been added:
HCP985E
HCP986I
HCP987E
HCP988I
The following publications have been modified:
CP Messages and Codes (GC24-6119-07 and GC24-6177-01)
New entries were added for the messages referenced above.
CP Planning and Administration (SC24-6083-07 and SC24-6178-01)
New entries were added for the FEATURES statements described above.
CP Commands and Utilities Reference (SC24-6081-07 and SC24-6175-01)
A new entry was added for QUERY STP.
Entries for SET TIMEZONE, DEFINE TIMEZONE and QUERY TIMEZONE were
updated.
System Operation (SC24-6121-03 and SC24-6233-01)
Added the following paragraph to Chapter 3 'Bringing up the System'
under the heading 'Setting the Time of Day Clock':
If your hardware is enabled and configured for Server Time Protocol
(STP) and
this feature has been enabled in your configuration file (using the
STP_TIMESTAMPING or STP_TZ features statements), you will not receive
any
prompts to change the TOD clock. Instead, STP is automatically used to
initialize the TOD clock with the STP-coordinated TOD value. When the
TOD
clock is initialized, you will receive message HCP986I "TOD Clock
Synchronized via STP."
Hope this helps,
Matt
Matthew J. Rosato
z/VM I/O Development
From: "O'Brien, Dennis L"
To: IBMVM@LISTSERV.UARK.EDU
Date: 09/21/2010 04:36 PM
Subject:Re: VM64814 information
Sent by:The IBM z/VM Operating System
Matt,
I'm running z/VM 5.4.0, so the applicable PTF is UM33146. I looked in
UM33146 $PTFPART, but I didn't find a UMEMO section. Is there somewhere
else that I should be looking for the memo? I'll order the 6.1.0 PTF and
see if it's there.
Dennis
"A slipping sear could let your M203 grenade launcher fire when you least
expect it. That would make you quite unpopular in what's left of your
unit." -- August 1993 issue of PS Magazine, preventive maintenance magazine
of the US Army
-Original Message-
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On
Behalf Of Matthew Rosato
Sent: Tuesday, September 21, 2010 13:15
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: [IBMVM] VM64814 information
Hi Dennis,
There is a memo-to-users file included with VM64814 that describes the new
FEATUREs statements that are included as part of XRC timestamping support.
I believe that these statements are the additional step that you are
referring to.
You can certainly pick up VM64814 today and use XRC timestamping. VM64816
will bring along a few internal changes, but nothing that would prevent
you from using XRC timestamping today.
Thanks,
Matt
Matthew J. Rosato
z/VM I/O Development
From:
Re: VM64814 information
Matt, I'm running z/VM 5.4.0, so the applicable PTF is UM33146. I looked in UM33146 $PTFPART, but I didn't find a UMEMO section. Is there somewhere else that I should be looking for the memo? I'll order the 6.1.0 PTF and see if it's there. Dennis "A slipping sear could let your M203 grenade launcher fire when you least expect it. That would make you quite unpopular in what's left of your unit." -- August 1993 issue of PS Magazine, preventive maintenance magazine of the US Army -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Matthew Rosato Sent: Tuesday, September 21, 2010 13:15 To: IBMVM@LISTSERV.UARK.EDU Subject: Re: [IBMVM] VM64814 information Hi Dennis, There is a memo-to-users file included with VM64814 that describes the new FEATUREs statements that are included as part of XRC timestamping support. I believe that these statements are the additional step that you are referring to. You can certainly pick up VM64814 today and use XRC timestamping. VM64816 will bring along a few internal changes, but nothing that would prevent you from using XRC timestamping today. Thanks, Matt Matthew J. Rosato z/VM I/O Development From: "O'Brien, Dennis L" To: IBMVM@LISTSERV.UARK.EDU Date: 09/21/2010 01:20 PM Subject:VM64814 information Sent by:The IBM z/VM Operating System I understand that VM64814 adds XRC timestamp support. The PTF's are available. The z/VM platform update at SHARE mentioned that there would be a SYSTEM CONFIG change to activate it. Where do I find information on that? The recent SSL changes had a nice web page with all the details, and one of the PTF's described the changes. I haven't been able to find any of that for VM64814. The APAR and PTF just say "new function". If it weren't for SHARE, and someone who told me what the APAR was for, I'd have no idea what new function I was putting in, or that an additional step was required to activate it. I found a couple of references on the IBM site that said VM64814 and VM64816 would add the function. VM64816 is "assigned to a programmer". Does VM64814 do anything without VM64816? Will VM64816 provide the documentation? Dennis O'Brien "A slipping sear could let your M203 grenade launcher fire when you least expect it. That would make you quite unpopular in what's left of your unit." -- August 1993 issue of PS Magazine, preventive maintenance magazine of the US Army
Re: VM64814 information
Hi Dennis, There is a memo-to-users file included with VM64814 that describes the new FEATUREs statements that are included as part of XRC timestamping support. I believe that these statements are the additional step that you are referring to. You can certainly pick up VM64814 today and use XRC timestamping. VM64816 will bring along a few internal changes, but nothing that would prevent you from using XRC timestamping today. Thanks, Matt Matthew J. Rosato z/VM I/O Development From: "O'Brien, Dennis L" To: IBMVM@LISTSERV.UARK.EDU Date: 09/21/2010 01:20 PM Subject:VM64814 information Sent by:The IBM z/VM Operating System I understand that VM64814 adds XRC timestamp support. The PTF's are available. The z/VM platform update at SHARE mentioned that there would be a SYSTEM CONFIG change to activate it. Where do I find information on that? The recent SSL changes had a nice web page with all the details, and one of the PTF's described the changes. I haven't been able to find any of that for VM64814. The APAR and PTF just say "new function". If it weren't for SHARE, and someone who told me what the APAR was for, I'd have no idea what new function I was putting in, or that an additional step was required to activate it. I found a couple of references on the IBM site that said VM64814 and VM64816 would add the function. VM64816 is "assigned to a programmer". Does VM64814 do anything without VM64816? Will VM64816 provide the documentation? Dennis O'Brien "A slipping sear could let your M203 grenade launcher fire when you least expect it. That would make you quite unpopular in what's left of your unit." -- August 1993 issue of PS Magazine, preventive maintenance magazine of the US Army
