It's far fuzzier than it needs to be I'm afraid. We have the old man on the 
mountain. His z/OS experience and general methodology for that arena is
top drawer. We're coming up on the 2 year mark for z/VM experience in this 
shop. He has 2 years of z/VM experience total, and not doing anything
really remotely cutting edge with it. He even is against linking disks 
Multi-write. He'd prefer that I don't cat a file with cmsfscat and grep/awk the
contents. He'd prefer I just read file.extention to figure out what to do cuz 
we're doing I/O to put stuff in the file, we're doing i/o to cat the
file. Why cant we just have a file that says {system name}.NOWAS if we don't 
want websphere to start. I figured if I wanted to control whether
WebSphere starts, I would perhaps in the future control DB2 Connect, MySQL, 
CVS, and whatever else so it wsa designed with that in mind.

I've been working with our  NEW sysprog with much VM experience We designed 
something using the CMSFS. Our senior person is opposed to things he
consideres 'bolt-on' unsupported code. I will concede that point to a degree. I 
myself am opposed to using kernel modifications that take us out of
supported status. CMSFS is a utility, not a kernal module or some other deep 
weeds modification .

In any case it comes down to politics.

I am going to implement things my way for now so I have something for the DR 
test. We can argue about meothods at another time.

Thanks again for all your help on this an other things I've asked the last 
couple years, everyone. I've learned so much.

-J




             "Post, Mark K" <[EMAIL PROTECTED]>
             Sent by: Linux on 390 Port
             <[email protected]>                                          
                                                                   To
                                                                     
[email protected]
                                                                                
                                                                   cc
             03/21/2006 09:12 PM
                                                                                
                                                              Subject
                                                                     Re: 
Passing a parameter to a Linux guest at IPL time
                            Please respond to
               Linux on 390 Port <[email protected]>








It requires one of Lucius' mods, which would put you in a non-supported
position from your Linux distribution provider.

I have no idea why your HS (when I was in college, these letters had a
totally different meaning, but perhaps still appropriate) is against the
use of CMSFS, but the question I have is: does he control what's on the
191 disk of your guests?  If not, it's your call, not his.  My VM guys
are more than willing to do what makes sense from a VM perspective.
They don't worry at all (much) about what happens after the "IPL CMS" is
done.


Mark Post

-----Original Message-----
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
James Melin
Sent: Thursday, March 16, 2006 5:02 PM
To: [email protected]
Subject: Re: Passing a parameter to a Linux guest at IPL time


Ok... how about on the IPL statement itself? Isn't there a way to pass
parameters that way?

While it may be possible, this exercise is silly to me, because I have
the CMSFS driven thing working. Just isn't being bought by the Head
Sysprog here. He's convinced doing it via CMSFS is going to bite us hard
in the fleshy part of the gluteus maximus some day.

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to