On Fri, 2 Jan 2009 20:27:05 +, Ted MacNEIL eamacn...@yahoo.ca
wrote:
If in the future we decide to introduce a multisystem sysplex then we can
rethink our NJE naming conventions. Does this sound safe?
Not 100%.
Since you are doing changes now, why not be proactive on the NODENAME?
One
I thought I would try to clean up some of our naming conventions. We are
running a monoplex. I've named our SYSNAME and SMF ID values the same.
What would be most appropriate for our JES2 node name? Should I make all 3
the same name? I'm currently using the sysplex name for the JES2 node
On Fri, 2 Jan 2009 10:59:32 -0600, George Dranes gd-dra...@wiu.edu wrote:
I thought I would try to clean up some of our naming conventions. We are
running a monoplex. I've named our SYSNAME and SMF ID values the same.
What would be most appropriate for our JES2 node name? Should I make all 3
There is very little chance we will ever connect to an external system. Maybe
something like WIUJESP1 (P for our production JES2)?
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to
George Dranes wrote:
I thought I would try to clean up some of our naming conventions. We are
running a monoplex. I've named our SYSNAME and SMF ID values the same.
What would be most appropriate for our JES2 node name? Should I make all 3
the same name? I'm currently using the sysplex
Actually, I would probably be more confused if the SMF ID and SYSNAME
didn't match. Of course I'm easily confused. lol
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with
On Fri, 2 Jan 2009, Edward Jaffe wrote:
George Dranes wrote:
I thought I would try to clean up some of our naming conventions. We are
running a monoplex. I've named our SYSNAME and SMF ID values the same.
What would be most appropriate for our JES2 node name? Should I make all 3
George Dranes wrote:
Actually, I would probably be more confused if the SMF ID and SYSNAME
didn't match. Of course I'm easily confused. lol
I've seen programs, including some from IBM, that mix up the SMF ID, JES
member name, and system name. The authors developed their code on
systems
-Original Message-
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On
Behalf Of John McKown
Sent: Friday, January 02, 2009 12:58 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: JES2 Node Name
On Fri, 2 Jan 2009, Edward Jaffe wrote:
SNIPAGE
this would only confuse me. Let's
So I take it many of you use the same name for SYSNAME, SID and JES2
NODENAME?
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the
PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: JES2 Node Name
So I take it many of you use the same name for SYSNAME, SID and JES2
NODENAME?
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists
Thompson, Steve wrote:
One more thing to consider: How would GRS determine who is reserving
(enqueue) what from whom? So wouldn't you be forced into RESERVES? And
there goes response/through-put.
The values you use for SMF IDs and JES member names have no effect
whatsoever on
On Fri, 2 Jan 2009 13:14:41 -0600, George Dranes gd-dra...@wiu.edu wrote:
So I take it many of you use the same name for SYSNAME, SID and JES2
NODENAME?
Most certainly. I have enough problems with programmers who cannot
understand that z/OS and MVS are basically different names for the same
George Dranes wrote:
So I take it many of you use the same name for SYSNAME, SID and JES2
NODENAME?
I must be missing something...
If every JES2 member has its own NJE node name, you create the false
impression that the systems in a JESplex (MAS) are not interconnected.
You'll have jobs
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of John McKown
[ snip ]
Some of them are still looking for the COBAL compiler grin. And what
happened to IKJCBL00? ...
IKFCBL00?
-jc-
--
For
On Fri, 2 Jan 2009 14:09:39 -0500, Thompson, Steve
steve_thomp...@stercomm.com wrote:
You made the points I was planning to make for me.
One more thing to consider: How would GRS determine who is reserving
(enqueue) what from whom? So wouldn't you be forced into RESERVES? And
there goes
On Fri, 2 Jan 2009 13:37:29 -0600, Chase, John jch...@ussco.com wrote:
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of John McKown
[ snip ]
Some of them are still looking for the COBAL compiler grin. And what
happened to IKJCBL00? ...
IKFCBL00?
-jc-
What.
-Original Message-
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On
Behalf Of Edward Jaffe
Sent: Friday, January 02, 2009 1:22 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: JES2 Node Name
Thompson, Steve wrote:
One more thing to consider: How would GRS determine who
On Fri, 2 Jan 2009 13:14:41 -0600, George Dranes gd-dra...@wiu.edu wrote:
So I take it many of you use the same name for SYSNAME, SID and JES2
NODENAME?
SYSNAME and SID... common. JES2, I've rarely seen it. It would be
really confusing in a JES2 MAS since it could only match on one of the
John McKown wrote:
[snip]
Most certainly. I have enough problems with programmers who cannot
understand that z/OS and MVS are basically different names for the same
thing. (I know that technically z/OS is the evolution of MVS which is the
evolution of SVS which is the evolution of MVT). Our
Considering our system is a monoplex and there is only on system in the MAS,
it would probably make much more sense for us to set the 3 values the same.
If in the future we decide to introduce a multisystem sysplex then we can
rethink our NJE naming conventions. Does this sound safe?
Thompson, Steve wrote:
So let us look at TCP. How would you ID the stack you need to go to, for
an application running on MVSA, when all your images are named MVSA? How
would you put in your DNS entries to know which is which? And even if
you did, your application can't seem to get affinity to
On Fri, 2 Jan 2009 12:54:30 -0700, Steve Comstock st...@trainersfriend.com
wrote:
John McKown wrote:
[snip]
Most certainly. I have enough problems with programmers who cannot
understand that z/OS and MVS are basically different names for the same
thing. (I know that technically z/OS is the
SNIP
TCP/IP DNS names are yet another name choice you get to make. Sysplex
distributor, especially when coupled with Cisco local director, is
supposed to allow you to specify the cluster IP name and get routed to
the image with the best chance of fulfilling your request in the
shortest amount
Actually, I would probably be more confused if the SMF ID and SYSNAME
didn't match.
I've always kept them same, except at one shop where they wanted to move JES
names around in case of a system failure.
It never happened, while I was there.
And, GDPS made them non-movable (automation was
So I take it many of you use the same name for SYSNAME, SID and JES2
NODENAME?
Not a good idea for NODENAME.
Member name, okay.
What happens if you expand to add another system in the same MAS?
You'll confuse people if your NODE was called SYSA (for example) and you add
another system (SYSB?).
If in the future we decide to introduce a multisystem sysplex then we can
rethink our NJE naming conventions. Does this sound safe?
Not 100%.
Since you are doing changes now, why not be proactive on the NODENAME?
One less change needed in future, if that projected future arrives.
-
Too busy
George Dranes wrote:
Considering our system is a monoplex and there is only on system in the MAS,
it would probably make much more sense for us to set the 3 values the same.
If in the future we decide to introduce a multisystem sysplex then we can
rethink our NJE naming conventions. Does
ibm-m...@bama.ua Subject
.edu Re: JES2 Node Name
Never take names lightly. Most especially, do not name things casually with
the expectation that you can always rename them later.
Technically, it's easy.
Politically, ...!
Naming is one of the biggest headaches in company mergers. Do your future self
the favor of taking great care today.
We
30 matches
Mail list logo
