In service mode the /etc and /var directories are supposed to be true 
directories so maintenance can be applied. When you clone them to become the 
running versions there is a script to run to switch to a symlink. Look in the 
doc for the Installation of the serverpac and at the server pac jobs.

Jerry Whitteridge
Lead Systems Programmer
Safeway Inc.
925 951 4184

If you feel in control
you just aren't going fast enough.

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
Of John Chase
Sent: Monday, June 18, 2012 7:04 AM
To: [email protected]
Subject: Re: installing serverpac for 1.13 using 1.11 system

On Mon, 18 Jun 2012 07:41:37 -0500, Mark Zelden <[email protected]> wrote:

>On Sun, 17 Jun 2012 18:29:26 -0500, John Chase <[email protected]> wrote:
>
>>
>>We just rolled out z/OS 1.13 (from 1.11) on our TEST/DEV lpar, and I noticed 
>>something "strange":  In the 1.13 root filesystem, the /etc and /var 
>>directories show as directories, whereas on 1.11 (and earlier) they showed as 
>>symlinks to /SYSTEM/etc and /SYSTEM/var respectively.  I looked at our 
>>installation/"sandbox" lpar and it's the same there.  Yet the /SYSTEM 
>>directory contains /etc and /var subdirectories, along with /dev and /tmp, as 
>>in the past.
>>
>>Did we "do something wrong" at installation?  Or are /etc and /var now (1.13) 
>>supposed to be directories in / rather than symlinks to the /SYSTEM 
>>subdirectories?
>>
>
>They are still symlinks for z/OS 1.13.   What do the directories look like on 
>your
>service mount point?  Or does you install into the live root in your 
>"installation/sandbox"
>LPAR (eek!).

The "installation copy" of the 1.13 root f/s that came with the Serverpac shows 
/etc and /var as directories, not symlinks, so perhaps we got a "devective" 
Serverpac?  At install time we created a separate /Service113 directory on 
which to mount the 1.13 root f/s while the sandbox was running 1.11.  I did not 
perform the actual installation; a colleague did.

I'll make them symlinks when we "clone" the root f/s for a maintenance copy.  
At the moment we don't share filesystems outside the respective LPARs, and 
everything works the way it is now.  But at some point in the future we may go 
"platinum plex" and will need the symlinks.  :-)

    -jc-

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN


"Email Firewall" made the following annotations.
------------------------------------------------------------------------------

Warning: 
All e-mail sent to this address will be received by the corporate e-mail 
system, and is subject to archival and review by someone other than the 
recipient.  This e-mail may contain proprietary information and is intended 
only for the use of the intended recipient(s).  If the reader of this message 
is not the intended recipient(s), you are notified that you have received this 
message in error and that any review, dissemination, distribution or copying of 
this message is strictly prohibited.  If you have received this message in 
error, please notify the sender immediately.   
 
==============================================================================

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to