Mike,

Thanks for your good advice and suggestions, it pointed me in the right 
direction.  It turned out that the problem was MAINT did not have the privilege 
to force off users, it now does.  RSU 0902 was applied fully and successfully.  
PUT2PROD had an issue with building the HELP Segment, which was resolved with 
IBM's assistance in moving the segment from C00-CFF to B00-CFF.  All is well, 
Thanks Mike and a special Thanks to Susan for her help.   

Thank you,

Scott


-----Original Message-----
From: The IBM z/VM Operating System [mailto:[email protected]] On Behalf 
Of Mike Walter
Sent: Wednesday, July 29, 2009 9:51 AM
To: [email protected]
Subject: Re: RSU 0902

> How do I continue?
That depends entirely upon the success/failure of SERVICE. 

Did you look in the "$VMFSRV  $MSGLOG  A1" file for any errors?   (The 
newest entries are at the top). 

Did you look at every "* $MSGLOG A" file that is newer than the "VMFSRV 
$MSGLOG A" (i.e. those that were created as SERVICE was running)?

Did you just try to run SERVICE again?  If there's no file to allow a 
SERVICE RESTART, then it can't hurt to rerun SERVICE the same way you did 
it when the problem occurred - and it may help confirm that the source of 
the problem has actually been corrected.  (Or it may not help, since if 
there's nothing to build, VMFBLD may not be executed).

It may help to understand that SERVICE and PUT2PROD are relatively new 
VMSES/E commands.  In essence, they are just rexx scripts that execute 
multiple other tedious VMSES/E commands that we used to have to enter 
manually by ourselves, after when we had to check the results of each by 
hand.  SERVICE and PUT2PROD just execute and check the results of all 
those other commands to make it easier for z/VM newbies.  And of course, 
easier for us tired old hands, too!    :-)

Your execution of SERVICE did fail due to the bad LINK return code.  I 
would not just run PUT2PROD until I was quite certain that whatever could 
not LINK that disk was identified and corrected. 

I'd examine the "* $MSGLOG A' files, and then probably re-run SERVICE from 
the beginning just to be 100% certain.  It won't re-apply service that was 
already applied, but it should re-build anything that wasn't quite 
completed the first time.

Mike Walter
Hewitt Associates
Any opinions expressed herein are mine alone and do not necessarily 
represent the opinions or policies of Hewitt Associates.




"Wandschneider, Scott" <[email protected]> 

Sent by: "The IBM z/VM Operating System" <[email protected]>
07/29/2009 08:39 AM
Please respond to
"The IBM z/VM Operating System" <[email protected]>



To
[email protected]
cc

Subject
Re: RSU 0902






I Issued "vmfsetup zvm cp" followed by "filelist * * * (After 07/22/2009" 
and found these:

5VMHCD40 SRVPROD  D1 V         49          3          1  7/23/2009 
18:34:45 
4OSASF40 SRVPROD  D1 V         82         15          1  7/23/2009 
18:34:44 
5VMCMS40 SRVPROD  D1 V         82         13          1  7/23/2009 
18:34:44 
5VMCPR40 SRVPROD  D1 V         82         76          2  7/23/2009 
18:34:44 
5VMGCS40 SRVPROD  D1 V         82          4          1  7/23/2009 
18:34:44 
5VMTCP40 SRVPROD  D1 V         82         39          1  7/23/2009 
18:34:44

I assume these components received maintenance ( individually the members 
list the PTFs applied) - correct?  How do I continue?  PUT2PROD?

Thank you,

Scott


-----Original Message-----
From: The IBM z/VM Operating System [mailto:[email protected]] On 
Behalf Of Mike Walter
Sent: Monday, July 27, 2009 5:23 PM
To: [email protected]
Subject: Re: RSU 0902

Here's one of my favorite often-overlooked commands: 

   FILELIST  * * * (TODAY

I use it pretty much after every VMSES/E command to see what has changed 
before releasing any disks.  (OK, not looking into EVERY file, but often 
getting a sense for what and how many have changed).  And true, when 
running the SERVICE command, many disks are accessed and released to 
process the different components in the service package.  But my 
home-grown FINDFILE EXEC can be used to search for all files on all LINKed 

mdisks that would match FILELIST options (such as "TODAY").

You should be able to see what VMSES/E accomplished (or failed to 
accomplish) by entering: 
   FL   *   $MSGLOG*   *
Browse the recently updated files, watching carefully for errors in 
anything to which you applied service.  The VMSES/E command 'VMFVIEW' 
permits you to view the same files, and can be used to "separate the chaff 

from the wheat".  But I like to see the whole story, especially if 
anything seems to have gone wrong.

What you do then depends on what you observe in the MSGLOG files.

Mike Walter
Hewitt Associates
Any opinions expressed herein are mine alone and do not necessarily 
represent the opinions or policies of Hewitt Associates.






"Wandschneider, Scott" <[email protected]> 

Sent by: "The IBM z/VM Operating System" <[email protected]>
07/27/2009 02:53 PM
Please respond to
"The IBM z/VM Operating System" <[email protected]>



To
[email protected]
cc

Subject
Re: RSU 0902






The original error was a return code 4, so I am wondering if I don't just 
continue with PUT2PROD?  A service restart resulted in the following.  So 
I am not sure where to go from here.

service restart 
VMFSRV2760I SERVICE RESTART processing started 
VMFSRV2305E File SERVICE $RESTART A was not found 
VMFSRV2760I SERVICE processing completed unsuccessfully 
<MAINT AT ZVMV5R40 > Ready(00028); T=0.46/0.51 15:49:28 
 


Thank you,

Scott


-----Original Message-----
From: The IBM z/VM Operating System [mailto:[email protected]] On 
Behalf Of Mike Walter
Sent: Monday, July 27, 2009 10:52 AM
To: [email protected]
Subject: Re: RSU 0902

And closing the loop... how'd it go, Scott?  Did SERVICE RESTART fix it 
all up once MAINT was given the privclass (or ESM authorization once you 
got that far) that it had when IBM shipped it?

Mike Walter
Hewitt Associates
Any opinions expressed herein are mine alone and do not necessarily 
represent the opinions or policies of Hewitt Associates.




Mike Walter/National/Hewitt associa...@hewitt Associates NA 

Sent by: "The IBM z/VM Operating System" <[email protected]>
07/24/2009 01:33 PM
Please respond to
"The IBM z/VM Operating System" <[email protected]>



To
[email protected]
cc

Subject
Re: RSU 0902






SERVICE RESTART?

(Sent from the wee keyboard on a Blackberry.)

  From: "Wandschneider, Scott" [[email protected]]
  Sent: 07/24/2009 11:07 AM MST
  To: [email protected]
  Subject: Re: RSU 0902

I think the original error was caused because MAINT did not have the 
ability to FORCE off users (BLDNUC).  I have given MAINT that privilege, 
but how do I restart or continue?  Thanks in advance!
 
Thank you,
 
Scott
 
From: The IBM z/VM Operating System [mailto:[email protected]] On 
Behalf Of Kris Buelens
Sent: Friday, July 24, 2009 9:39 AM
To: [email protected]
Subject: Re: RSU 0902
 
It was visible in the first append: BLDNUC had 490 in R/W
2009/7/24 Mike Walter <[email protected]>
Before SERVICE RESTART, read paragraphs 2-3 below to ensure that nothing 
else has the 490 disk linked R/W.

If none other than MAINT has it R/W you should be good to go.

Mike Walter
Hewitt Associates

(Sent from the wee keyboard on a Blackberry.)


----- Original Message -----
From: "Wandschneider, Scott" [[email protected]]
Sent: 07/24/2009 07:07 AM MST
To: [email protected]
Subject: Re: RSU 0902



I am running this process from MAINT.  It did not fail previously.

How do I restart?   SERVICE RESTART?

Thank you,

Scott

-----Original Message-----
From: The IBM z/VM Operating System [mailto:[email protected]] On 
Behalf Of Mike Walter
Sent: Thursday, July 23, 2009 7:06 PM
To: [email protected]
Subject: Re: RSU 0902

>From what userid were you running SERVICE?  Did it fail earlier, leaving 
something logged on - perhaps an I'd like; BLDxxx?

Regardless, issue a CP Q LINKS 490 and see which userid has it linked.

Also (rather than just telling you what it means) look up the CP LINK 
command to better understand link mode 'M'.

Between those pieces of info you'll probably figure out what to do on your 


own.

Mike Walter
Hewitt Associates

(Sent from the wee keyboard on a Blackberry.)


----- Original Message -----
From: "Wandschneider, Scott" [[email protected]]
Sent: 07/23/2009 04:04 PM MST
To: [email protected]
Subject: RSU 0902



I was applying RSU0902 on top of VM 5.4 0901 and received these messages:

SV:HCPLNM105E MAINT 0490 not linked; R/W by BLDNUC
WN:VMFSRV1966W The command, CP LINK MAINT 490 490 M, completed with
WN:            return code 105
SV:HCPLGA054E Already logged on disconnected

I'm not sure what my next step should be.  Can somebody show me the error 
of my way?  Thanks in advance.

Thank you,
Scott R Wandschneider
Senior Systems Programmer|| Infocrossing, a Wipro Company || 11707 Miracle 


Hills Drive, Omaha, NE, 68154-4457|| ': 402.963.8905 || Ë:847.849.7223  || 


 : [email protected] **Think Green  - Please print 
responsibly**




The information contained in this e-mail and any accompanying documents 
may contain information that is confidential or otherwise protected from 
disclosure. If you are not the intended recipient of this message, or if 
this message has been addressed to you in error, please immediately alert 
the sender by reply e-mail and then delete this message, including any 
attachments. Any dissemination, distribution or other use of the contents 
of this message by anyone other than the intended recipient is strictly 
prohibited. All messages sent to and from this e-mail address may be 
monitored as permitted by applicable law and regulations to ensure 
compliance with our internal policies and to protect our business. E-mails 


are not secure and cannot be guaranteed to be error free as they can be 
intercepted, amended, lost or destroyed, or contain viruses. You are 
deemed to have accepted these risks if you communicate with us by e-mail.

Confidentiality Note: This e-mail, including any attachment to it, may 
contain material that is confidential, proprietary, privileged and/or 
"Protected Health Information," within the meaning of the regulations 
under the Health Insurance Portability & Accountability Act as amended. If 


it is not clear that you are the intended recipient, you are hereby 
notified that you have received this transmittal in error, and any review, 


dissemination, distribution or copying of this e-mail, including any 
attachment to it, is strictly prohibited. If you have received this e-mail 


in error, please immediately return it to the sender and delete it from 
your system. Thank you.



The information contained in this e-mail and any accompanying documents 
may contain information that is confidential or otherwise protected from 
disclosure. If you are not the intended recipient of this message, or if 
this message has been addressed to you in error, please immediately alert 
the sender by reply e-mail and then delete this message, including any 
attachments. Any dissemination, distribution or other use of the contents 
of this message by anyone other than the intended recipient is strictly 
prohibited. All messages sent to and from this e-mail address may be 
monitored as permitted by applicable law and regulations to ensure 
compliance with our internal policies and to protect our business. E-mails 


are not secure and cannot be guaranteed to be error free as they can be 
intercepted, amended, lost or destroyed, or contain viruses. You are 
deemed to have accepted these risks if you communicate with us by e-mail.



-- 
Kris Buelens,
IBM Belgium, VM customer support

The information contained in this e-mail and any accompanying documents 
may contain information that is confidential or otherwise protected from 
disclosure. If you are not the intended recipient of this message, or if 
this message has been addressed to you in error, please immediately alert 
the sender by reply e-mail and then delete this message, including any 
attachments. Any dissemination, distribution or other use of the contents 
of this message by anyone other than the intended recipient is strictly 
prohibited. All messages sent to and from this e-mail address may be 
monitored as permitted by applicable law and regulations to ensure 
compliance with our internal policies and to protect our business. E-mails 


are not secure and cannot be guaranteed to be error free as they can be 
intercepted, amended, lost or destroyed, or contain viruses. You are 
deemed to have accepted these risks if you communicate with us by e-mail. 

The information contained in this e-mail and any accompanying documents 
may contain information that is confidential or otherwise protected from 
disclosure. If you are not the intended recipient of this message, or if 
this message has been addressed to you in error, please immediately alert 
the sender by reply e-mail and then delete this message, including any 
attachments. Any dissemination, distribution or other use of the contents 
of this message by anyone other than the intended recipient is strictly 
prohibited. All messages sent to and from this e-mail address may be 
monitored as permitted by applicable law and regulations to ensure 
compliance with our internal policies and to protect our business. E-mails 


are not secure and cannot be guaranteed to be error free as they can be 
intercepted, amended, lost or destroyed, or contain viruses. You are 
deemed to have accepted these risks if you communicate with us by e-mail. 




The information contained in this e-mail and any accompanying documents 
may contain information that is confidential or otherwise protected from 
disclosure. If you are not the intended recipient of this message, or if 
this message has been addressed to you in error, please immediately alert 
the sender by reply e-mail and then delete this message, including any 
attachments. Any dissemination, distribution or other use of the contents 
of this message by anyone other than the intended recipient is strictly 
prohibited. All messages sent to and from this e-mail address may be 
monitored as permitted by applicable law and regulations to ensure 
compliance with our internal policies and to protect our business. E-mails 

are not secure and cannot be guaranteed to be error free as they can be 
intercepted, amended, lost or destroyed, or contain viruses. You are 
deemed to have accepted these risks if you communicate with us by e-mail. 

Confidentiality Note: This e-mail, including any attachment to it, may 
contain material that is confidential, proprietary, privileged and/or 
"Protected Health Information," within the meaning of the regulations 
under the Health Insurance Portability & Accountability Act as amended. If 

it is not clear that you are the intended recipient, you are hereby 
notified that you have received this transmittal in error, and any review, 

dissemination, distribution or copying of this e-mail, including any 
attachment to it, is strictly prohibited. If you have received this e-mail 

in error, please immediately return it to the sender and delete it from 
your system. Thank you.






The information contained in this e-mail and any accompanying documents 
may contain information that is confidential or otherwise protected from 
disclosure. If you are not the intended recipient of this message, or if 
this message has been addressed to you in error, please immediately alert 
the sender by reply e-mail and then delete this message, including any 
attachments. Any dissemination, distribution or other use of the contents 
of this message by anyone other than the intended recipient is strictly 
prohibited. All messages sent to and from this e-mail address may be 
monitored as permitted by applicable law and regulations to ensure 
compliance with our internal policies and to protect our business. E-mails 
are not secure and cannot be guaranteed to be error free as they can be 
intercepted, amended, lost or destroyed, or contain viruses. You are 
deemed to have accepted these risks if you communicate with us by e-mail. 

Confidentiality Note: This e-mail, including any attachment to it, may 
contain material that is confidential, proprietary, privileged and/or 
"Protected Health Information," within the meaning of the regulations 
under the Health Insurance Portability & Accountability Act as amended. If 
it is not clear that you are the intended recipient, you are hereby 
notified that you have received this transmittal in error, and any review, 
dissemination, distribution or copying of this e-mail, including any 
attachment to it, is strictly prohibited. If you have received this e-mail 
in error, please immediately return it to the sender and delete it from 
your system. Thank you.






The information contained in this e-mail and any accompanying documents may 
contain information that is confidential or otherwise protected from 
disclosure. If you are not the intended recipient of this message, or if this 
message has been addressed to you in error, please immediately alert the sender 
by reply e-mail and then delete this message, including any attachments. Any 
dissemination, distribution or other use of the contents of this message by 
anyone other than the intended recipient is strictly prohibited. All messages 
sent to and from this e-mail address may be monitored as permitted by 
applicable law and regulations to ensure compliance with our internal policies 
and to protect our business. E-mails are not secure and cannot be guaranteed to 
be error free as they can be intercepted, amended, lost or destroyed, or 
contain viruses. You are deemed to have accepted these risks if you communicate 
with us by e-mail. 

Confidentiality Note: This e-mail, including any attachment to it, may contain 
material that is confidential, proprietary, privileged and/or "Protected Health 
Information," within the meaning of the regulations under the Health Insurance 
Portability & Accountability Act as amended.  If it is not clear that you are 
the intended recipient, you are hereby notified that you have received this 
transmittal in error, and any review, dissemination, distribution or copying of 
this e-mail, including any attachment to it, is strictly prohibited. If you 
have received this e-mail in error, please immediately return it to the sender 
and delete it from your system. Thank you.

Reply via email to