Just my personal opinion... I've never been too fond of VMFVIEW.  It hides 
a lot of stuff unless one knows to poke around to look for it.

For example, if one enters "VMFVIEW SERVICE", it reports:
No messages meet the search criteria. 
************************************************************************ 
****             SERVICE               USERID: MAINT                **** 
************************************************************************ 
****            Date: 05/24/10            Time: 12:31:14            **** 
************************************************************************ 

"No messages meet the search criteria"?  Why? 

After pressing F5 (Status), it then reports:
You are viewing ST: messages from the LAST run. 
Number of messages shown = 8 <===> Number of messages not shown = 0 
************************************************************************ 
****             SERVICE               USERID: MAINT                **** 
************************************************************************ 
****            Date: 05/24/10            Time: 12:31:14            **** 
************************************************************************ 
ST:VMFSRV2195I SERVICE ALL STATUS PK65850 
ST:VMFSRV2760I SERVICE processing started 
ST:DASD 0491 LINKED R/W; R/O BY     6 USERS 
ST:DASD 0492 LINKED R/W; R/O BY     6 USERS 
ST:VMFSRV1226I TCPIP (5VMTCP40%TCPIP) APAR PK65850 (PTF UK40952) status: 
ST:VMFSRV1226I    RECEIVED  04/08/09 15:56:41 
ST:VMFSRV1226I    APPLIED   03/09/09 22:25:09 
ST:VMFSRV1226I    BUILT     04/08/09 16:01:50 
ST:VMFSRV1226I    PUT2PROD  04/08/09 18:46:35 
ST:VMFSRV2760I SERVICE processing completed successfully 
* * * End of File * * * 

Ah.. much better!  But that's still only the most recent run.  What if one 
wants more runs, perhaps ALL of them?
There's nothing to direct the newbie to enter at the command line: ALL
But doing so does display all the status messages (and intervening comment 
lines) from all the SERVICE runs.

But then there's no hint how one can display only certain messages, like 
the aforementioned: VMFSRV2195I
XEDIT's ALL macro does not (at least not obviously) work from inside 
VMFVIEW.

IMHO, some tools are more complex than the simple tools they attempt to 
replace - and actually result in poorer understanding of all that really 
went on.

Respectully,

Mike Walter
Aon Hewitt
The opinions expressed herein are mine alone, not my employer's.



"Alan Altmark" <alan_altm...@us.ibm.com> 

Sent by: "The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU>
10/20/2010 01:42 PM
Please respond to
"The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU>



To
IBMVM@LISTSERV.UARK.EDU
cc

Subject
Re: RSU or PSU?






On Wednesday, 10/20/2010 at 02:21 EDT, Mike Walter 
<mike.wal...@hewitt.com> wrote:

> This is tough to solve without access to your disks and logs.
> 
> 1) What SERVLINK files arrived with that RSU?
> 
> Did you apply the RSU using the SERVICE command?
> 2) If so, what was the syntax you entered for that command?
> Hint: XEDIT $VMFSRV  $MSGLOG  A1
> Another hint, XEDIT command: ALL /VMFSRV2195I/
> Be sure to QUIT that file, you don't want to change it by accident!

"VMFVIEW SERVICE".

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






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. 

Reply via email to