Tom, 

I can speak only for DB2/CICS/WMQ but I believe our MVS folks choose the same 
way. We use zFS for new products. 

During product installation we run the following SMPE job.
                                
   SET BOUNDARY(CIC310T) .                             
   ZONEEDIT DDDEF .                                    
   CHANGE PATH('/usr/lpp/cicsts/cic310'*,                          
               '/smpt/usr/lpp/cicsts/cic310'*) .       
   ENDZONEEDIT .                                       

So all apply goes to /smpt like /service which points to SMPT.CIC310.ZFSFILE 
(VSAM linear dataset)

Then we copy this file like this

 COPY DATASET(INCLUDE(SMPT.CIC310.ZFSFILE))  -                     
               RENUNC(SMPT.CIC310.ZFSFILE,   -                     
                      SYS5.CIC310A.ZFSFILE)  -                     
      SHARE                                  -                     
      TOL(ENQF)                              -                     
      STORCLAS(AA01)                         -                     
      MGMTCLAS(MSYST000)                     -                     
      CATALOG                                -                     
      TGTALLOC(CYL)                          -                     
      REPLACE                                                      
/*                                                                 
//*                                                                
//MOUNT   EXEC PGM=IKJEFT01                                        
//SYSPROC  DD  DISP=SHR,DSN=SYS5.STCSYS.CLIST                      
//         DD  DISP=SHR,DSN=SYS4.SPFSYS.CLIST                      
//SYSTSPRT DD  SYSOUT=*                                            
//SYSTSIN  DD  *                                                   
mount   FILESYSTEM('SYS5.CIC310A.ZFSFILE')          +              
        mountpoint('/add1') type(zfs) mode(rdwr)                   
                                                                   
unmount FILESYSTEM('SYS5.CIC310A.ZFSFILE')                         
mount   FILESYSTEM('SYS5.CIC310A.ZFSFILE')          +              
        mountpoint('/usr/lpp/cicsts/cic310')  type(zfs) mode(read)

For zFS you need to mount a new zFS as READ/WRITE and then unmount and mount it 
again as READ only. Product zFS or HFS are READ only and shared across several 
images. 

In case of new service we mount it again as 

  PROFILE MSGID WTPMSG                           
  MOUNT TYPE(zfs) +                              
    MODE(RDWR) +                                 
    MOUNTPOINT('/smpt/usr/lpp/cicsts/cic310') +  
    PARM('AGGRGROW')                          +  
    FILESYSTEM('SMPT.CIC310.ZFSFILE')            

and then apply the new service. The new zFS will then SYS5.CIC310B.ZFSFILE 
in case of a fallback.

Of course you need to create some mostly orphaned directory in you ROOT HFS.

It's a bit easier for HFS.

Roland

-----Original Message-----
From: IBM Mainframe Discussion List 
[mailto:[EMAIL PROTECTED] On Behalf Of Tom Marchant
Sent: Tuesday, August 16, 2005 10:58 PM
To: [email protected]
Subject: Re: Managing /service for SMP/E


Thanks, Eric.

Everything I've seen from IBM simply says to clone your HFS and 
mount it at /service, but that is hardly adequate when you have 
17 MVS images and can only get a few IPLs per year.  We have 
several target zones to keep track of, and we may need to apply 
service to any of them.  Automount is the best solution that I 
know to ensure that the correct HFSes are mounted at the 
correct mounty points.

I had written about this several years ago in http://tinyurl.com/ajjmc .

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to