I think Jim goes into it briefly with this presentation - a follow up to 
9117 


9118 - Servicing and Maintaining z/VM with VM/SES - Live Demo

or maybe Kris could come to SHARE and give session 9119 


munson




David Boyes <dbo...@sinenomine.net> 
Sent by: The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU>
08/20/2009 12:53 PM
Please respond to
The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU>


To
IBMVM@LISTSERV.UARK.EDU
cc

Subject
Re: Extension of MAINT 190 (S-DISK)






On 8/19/09 5:57 PM, "Kris Buelens" <kris.buel...@gmail.com> wrote:

> If you invent your own product IDs, you can even catalog your own files 
when
> copied to 19E.  With a new release, VMFCOPY can be used to copy all 
files of a
> given product ID from the old to the new 19E.  That's what I did to 
store some
> customer code on the Y-disk, in a fully documented way.

You know, I'd really like to have an IBMer give a presentation on how to
package tools with SES. It would be really handy to have someone actually 
go
through the process with a non-IBM product, because I'd really like to
package a lot of our stuff to be SES-friendly.

Yes, I know that there is documentation for this, but given that
experimentation with SES has a bad habit of significantly screwing up your
system, it'd be really good to have someone walk you through it once.

--d b


*************************** IMPORTANT
NOTE***************************** The opinions expressed in this
message and/or any attachments are those of the author and not
necessarily those of Brown Brothers Harriman & Co., its
subsidiaries and affiliates ("BBH"). There is no guarantee that
this message is either private or confidential, and it may have
been altered by unauthorized sources without your or our knowledge.
Nothing in the message is capable or intended to create any legally
binding obligations on either party and it is not intended to
provide legal advice. BBH accepts no responsibility for loss or
damage from its use, including damage from virus.
************************************************************************

Reply via email to