Re: Accessing USS on Mainframe thru Telnet

[Rob Schramm]

In the spirit by which this conversation was started

Acronym
An abbreviation formed from the initial letters of other words and
pronounced as a word

z/OS Unix is not an acronym.  It is at best a short version of the
entire phrase z/OS Unix System Services or might be considered the
"real name"... but still is not an acronym.

zUSS would qualify, by definition, as an acronym.  And I think I am
ready to cede providing it will shutup, gag, disable pedantic feature,
put a stake in this conversation, quit filling up my inbox, and
otherwise cease this very much a waste of my valuable time posting on
this subject.

But as he has already disputed this shortened version... even though
it conflicts with the definition of acronym... this will continue with
no shore in site and only postings of people with time to waste on
such trivial musings.

Rob Schramm
Senior Systems Consultant
Imperium Group




On Sat, Apr 7, 2012 at 1:06 AM, Pommier, Rex R.
 wrote:
> John,
>
> For the most part I agree with you, except in the first line of his actual 
> post, the original poster made it quite obvious to anybody which of the two 
> USS's he was referring to, which makes this current argument all the more 
> stupid.  I think this whole thing is painfully silly, as Mr. Mason will never 
> give up on his crusade to stop anybody from using USS to refer to Unix stuff, 
> and a few others seem to take delight in needling him on, and the vast 
> majority of us would prefer the whole thing just dry up.  No amount of 
> cajoling will get either side to change their respective minds, but 
> unfortunately apparently no amount of begging them to "just give it up" will 
> make that happen either.
>
> And it's too bad, because I have been the recipient on a couple occasions of 
> some of Mr. Mason's wisdom in regards to a VTAM issue that I was having.  
> Unfortunately the gems get lost in the bickering.
>
> Like you, this will be my last (and in my case my first) post on the subject.
>
> Rex
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf 
> Of McKown, John
> Sent: Friday, April 06, 2012 2:03 PM
> To: IBM-MAIN@bama.ua.edu
> Subject: Re: Accessing USS on Mainframe thru Telnet
>
> Well, possibly to the relief of all, I will hencefore ignore any and all 
> posts to this forum which include the letters USS which do not also 
> explicitly say UNIX or VTAM. I'm simply to old and tired to bother any more. 
> In this particular thread, I will agree that USS could be confusing since 
> "telnet" could refer to either accessing a z/OS UNIX shell prompt via 
> "historic" telnet, or to accessing an LU2 VTAM application via TN3270E which 
> is also a special encoded 3270 data stream using the telnet protocol.
>
> --
> John McKown
> Systems Engineer IV
> IT
>
> Administrative Services Group
>
> HealthMarkets(r)
>
> 9151 Boulevard 26 * N. Richland Hills * TX 76010
> (817) 255-3225 phone *
> john.mck...@healthmarkets.com * www.HealthMarkets.com
>
> Confidentiality Notice: This e-mail message may contain confidential or 
> proprietary information. If you are not the intended recipient, please 
> contact the sender by reply e-mail and destroy all copies of the original 
> message. HealthMarkets(r) is the brand name for products underwritten and 
> issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake 
> Life Insurance Company(r), Mid-West National Life Insurance Company of 
> TennesseeSM and The MEGA Life and Health Insurance Company.SM
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
>
> The information contained in this e-mail may contain confidential and/or 
> privileged information and is intended for the sole use of the intended 
> recipient. If you are not the intended recipient, you are hereby notified 
> that any unauthorized use, disclosure, distribution or copying of this 
> communication is strictly prohibited and that you will be held responsible 
> for any such unauthorized activity, including liability for any resulting 
> damages. As appropriate, such incident(s) may also be reported to law 
> enforcement. If you received this e-mail in error, please reply to sender and 
> destroy or delete the message and any attachments. Thank you.
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

Re: Accessing USS on Mainframe thru Telnet

[Pommier, Rex R.]

John,

For the most part I agree with you, except in the first line of his actual 
post, the original poster made it quite obvious to anybody which of the two 
USS's he was referring to, which makes this current argument all the more 
stupid.  I think this whole thing is painfully silly, as Mr. Mason will never 
give up on his crusade to stop anybody from using USS to refer to Unix stuff, 
and a few others seem to take delight in needling him on, and the vast majority 
of us would prefer the whole thing just dry up.  No amount of cajoling will get 
either side to change their respective minds, but unfortunately apparently no 
amount of begging them to "just give it up" will make that happen either.

And it's too bad, because I have been the recipient on a couple occasions of 
some of Mr. Mason's wisdom in regards to a VTAM issue that I was having.  
Unfortunately the gems get lost in the bickering.

Like you, this will be my last (and in my case my first) post on the subject.

Rex

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of 
McKown, John
Sent: Friday, April 06, 2012 2:03 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: Accessing USS on Mainframe thru Telnet

Well, possibly to the relief of all, I will hencefore ignore any and all posts 
to this forum which include the letters USS which do not also explicitly say 
UNIX or VTAM. I'm simply to old and tired to bother any more. In this 
particular thread, I will agree that USS could be confusing since "telnet" 
could refer to either accessing a z/OS UNIX shell prompt via "historic" telnet, 
or to accessing an LU2 VTAM application via TN3270E which is also a special 
encoded 3270 data stream using the telnet protocol.

--
John McKown
Systems Engineer IV
IT

Administrative Services Group

HealthMarkets(r)

9151 Boulevard 26 * N. Richland Hills * TX 76010
(817) 255-3225 phone *
john.mck...@healthmarkets.com * www.HealthMarkets.com

Confidentiality Notice: This e-mail message may contain confidential or 
proprietary information. If you are not the intended recipient, please contact 
the sender by reply e-mail and destroy all copies of the original message. 
HealthMarkets(r) is the brand name for products underwritten and issued by the 
insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance 
Company(r), Mid-West National Life Insurance Company of TennesseeSM and The 
MEGA Life and Health Insurance Company.SM

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

The information contained in this e-mail may contain confidential and/or 
privileged information and is intended for the sole use of the intended 
recipient. If you are not the intended recipient, you are hereby notified that 
any unauthorized use, disclosure, distribution or copying of this communication 
is strictly prohibited and that you will be held responsible for any such 
unauthorized activity, including liability for any resulting damages. As 
appropriate, such incident(s) may also be reported to law enforcement. If you 
received this e-mail in error, please reply to sender and destroy or delete the 
message and any attachments. Thank you.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

Re: Accessing USS on Mainframe thru Telnet

[Ron Hawkins]

Hook, line, and sinker...

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On
> Behalf Of Chris Mason
> Sent: Friday, April 06, 2012 3:33 PM
> To: IBM-MAIN@bama.ua.edu
> Subject: Re: [IBM-MAIN] Accessing USS on Mainframe thru Telnet
> 
> Ron
> 
> When were you born?
> 
> Was it in 1997 or 1977?
> 
> If it was 1997, you would now be 20 years older than if it was 1977 -
according
> to your logic.
> 
> > Frankly I've never understood Chris's problem with USS, ...
> 
> Now you know!
> 
> Chris Mason
> 
> P.S. Please take the trouble actually to read through the initial post of
the still
> active thread "A z/OS Redbook Corrected - just about!", Wed, 21 Mar 2012
> 07:34:55 -0500.
> 
> 
> On Fri, 6 Apr 2012 11:54:33 -0700, Ron Hawkins
>  wrote:
> 
> >John,
> >
> >Frankly I've never understood Chris's problem with USS, except that he
> >may suffer from some sort of OCD reaction when he sees those letters.
> >
> >We all know that USS stands for Unix System Services, and any other
> >employment of the acronym with the Mainframe community should spell
> out
> >that it is not using this accepted, commonplace, default meaning.
> >
> >VTAM Unformatted System Services is one good example, where authors
> >should discipline themselves to explain that they are not referring to
> >Unix System Services rather than confusing everyone by hijacking this
> acronym.
> >
> > ...
> >
> >Ron
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send email
to
> lists...@bama.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

Re: Accessing USS on Mainframe thru Telnet

[Chris Mason]

Ron

When were you born?

Was it in 1997 or 1977?

If it was 1997, you would now be 20 years older than if it was 1977 - according 
to your logic.

> Frankly I've never understood Chris's problem with USS, ...

Now you know!

Chris Mason

P.S. Please take the trouble actually to read through the initial post of the 
still active thread "A z/OS Redbook Corrected - just about!", Wed, 21 Mar 2012 
07:34:55 -0500.


On Fri, 6 Apr 2012 11:54:33 -0700, Ron Hawkins  
wrote:

>John,
>
>Frankly I've never understood Chris's problem with USS, except that he may
>suffer from some sort of OCD reaction when he sees those letters.
>
>We all know that USS stands for Unix System Services, and any other
>employment of the acronym with the Mainframe community should spell out that
>it is not using this accepted, commonplace, default meaning.
>
>VTAM Unformatted System Services is one good example, where authors should
>discipline themselves to explain that they are not referring to Unix System
>Services rather than confusing everyone by hijacking this acronym.
>
> ...
>
>Ron

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

Re: Accessing USS on Mainframe thru Telnet

[Steve Comstock]

On 4/6/2012 1:18 PM, Steve Thompson wrote:

Kirk Wolf:

"Unfortunately, there isn't an official acronym for z/OS Unix System
Services.

Until such time as there is, maybe we should use zUSS or maybe Xeus :-)"




Since you insisted:


http://www-03.ibm.com/systems/z/os/zos/features/unix/


Regards,
Steve Thompson



And if you click on the 'Education' tab ...



--

Kind regards,

-Steve Comstock
The Trainer's Friend, Inc.

303-355-2752
http://www.trainersfriend.com

* To get a good Return on your Investment, first make an investment!
  + Training your people is an excellent investment

* Try our tool for calculating your Return On Investment
for training dollars at
  http://www.trainersfriend.com/ROI/roi.html

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

Re: Accessing USS on Mainframe thru Telnet

[Steve Thompson]

Kirk Wolf:

"Unfortunately, there isn't an official acronym for z/OS Unix System Services. 
Until such time as there is, maybe we should use zUSS or maybe Xeus :-)"



Since you insisted:


http://www-03.ibm.com/systems/z/os/zos/features/unix/


Regards,
Steve Thompson

Opinions expressed by this poster do not necessarily reflect those of poster's 
employer.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

Re: Accessing USS on Mainframe thru Telnet

[Staller, Allan]

USS plus useful content - Read fully
USS acronym wars --Plonk!

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

Re: Accessing USS on Mainframe thru Telnet

[McKown, John]

Well, possibly to the relief of all, I will hencefore ignore any and all posts 
to this forum which include the letters USS which do not also explicitly say 
UNIX or VTAM. I'm simply to old and tired to bother any more. In this 
particular thread, I will agree that USS could be confusing since "telnet" 
could refer to either accessing a z/OS UNIX shell prompt via "historic" telnet, 
or to accessing an LU2 VTAM application via TN3270E which is also a special 
encoded 3270 data stream using the telnet protocol.

--
John McKown 
Systems Engineer IV
IT

Administrative Services Group

HealthMarkets(r)

9151 Boulevard 26 * N. Richland Hills * TX 76010
(817) 255-3225 phone * 
john.mck...@healthmarkets.com * www.HealthMarkets.com

Confidentiality Notice: This e-mail message may contain confidential or 
proprietary information. If you are not the intended recipient, please contact 
the sender by reply e-mail and destroy all copies of the original message. 
HealthMarkets(r) is the brand name for products underwritten and issued by the 
insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance 
Company(r), Mid-West National Life Insurance Company of TennesseeSM and The 
MEGA Life and Health Insurance Company.SM

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

Re: Accessing USS on Mainframe thru Telnet

[Kirk Wolf]

No amount of discussion has or will ever quell this battle.   Declare your
own victory and do as I have:

a) Don't use "USS" to refer to z/OS Unix System Services
b) Don't correct someone who does
c) Filter emails from Chris Mason.   A pity that 5% of his voluminous posts
are valuable, but not worth the rest.

Unfortunately, there isn't an official acronym for z/OS Unix System
Services.   Until such time as there is, maybe we should use zUSS or maybe
Xeus :-)

Kirk Wolf
Dovetailed Technologies
http://dovetail.com

On Fri, Apr 6, 2012 at 12:50 PM, Veilleux, Jon L wrote:

> I prefer to keep my comments succinct rather than ramble on about inane
> complaints about acronym usage.
> You must have too much time on your hands to waste so much of it on
> useless bickering, ergo, you need to get a life.
>
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

Re: Accessing USS on Mainframe thru Telnet

[Mike Schwab]

http://en.wikipedia.org/wiki/USS_Yorktown_(CG-48)
On 21 September 1997, while on maneuvers off the coast of Cape
Charles, Virginia, a crew member entered a zero into a database field
causing a divide by zero error in the ship's Remote Data Base Manager
which brought down all the machines on the network, causing the ship's
propulsion system to fail.[5]
[deleted[
Atlantic Fleet officials also denied the towing, reporting that
Yorktown was "dead in the water" for just 2 hours and 45 minutes.[6]
[deleted]

On Fri, Apr 6, 2012 at 8:32 AM, McKown, John
 wrote:
> Probably, given how we do things anymore, it would likely run Windows. I 
> dread the day that we lose a war because our weapons "blue screened".
>
> --
> John McKown
> Systems Engineer IV
-- 
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

Re: Accessing USS on Mainframe thru Telnet

[Ron Hawkins]

John,

Frankly I've never understood Chris's problem with USS, except that he may
suffer from some sort of OCD reaction when he sees those letters.

We all know that USS stands for Unix System Services, and any other
employment of the acronym with the Mainframe community should spell out that
it is not using this accepted, commonplace, default meaning.

VTAM Unformatted System Services is one good example, where authors should
discipline themselves to explain that they are not referring to Unix System
Services rather than confusing everyone by hijacking this acronym. 

And as for naming boats, how would HMAS ever get confused with USS?

Is this the appropriate place for the :-)

Ron

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On
> Behalf Of McKown, John
> Sent: Friday, April 06, 2012 6:10 AM
> To: IBM-MAIN@bama.ua.edu
> Subject: Re: [IBM-MAIN] Accessing USS on Mainframe thru Telnet
> 
> I appreciate Chris' knowledge of most things, especially VTAM. But
> apparently he has a "thing" about USS. And also appears to believe that if
he
> continues to be "bothersome" about the "misuse" of the term USS, that
> either: (a) people will be educated and will voluntarily change or (b)
will
> become tired of hearing the rants and so change their usage just to shut
him
> up. I doubt that either will occur. IMO, in most cases the meaning of USS
is
> easily recognizable from the context. If it is not, then the email is
likely so
> vague or poorly written that trying to understand what is needed is a
waste
> of my time, and I ignore it.
> 
> --
> John McKown
> Systems Engineer IV
> IT
> 
> Administrative Services Group
> 
> HealthMarkets(r)
> 
> 9151 Boulevard 26 * N. Richland Hills * TX 76010
> (817) 255-3225 phone *
> john.mck...@healthmarkets.com * www.HealthMarkets.com
> 
> Confidentiality Notice: This e-mail message may contain confidential or
> proprietary information. If you are not the intended recipient, please
contact
> the sender by reply e-mail and destroy all copies of the original message.
> HealthMarkets(r) is the brand name for products underwritten and issued by
> the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life
> Insurance Company(r), Mid-West National Life Insurance Company of
> TennesseeSM and The MEGA Life and Health Insurance Company.SM
> 
> 
> 
> > -Original Message-
> > From: IBM Mainframe Discussion List
> > [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Paul Gilmartin
> > Sent: Thursday, April 05, 2012 11:45 AM
> > To: IBM-MAIN@bama.ua.edu
> > Subject: Re: Accessing USS on Mainframe thru Telnet
> >
> > On Thu, 5 Apr 2012 09:31:57 -0500, Chris Mason wrote:
> > >
> > >However, there are indications you have been seduced by the
> > incorrect use of the abbreviation for what started out as VTAM's
> > Unformatted System Services at least two decades before UNIX System
> > Services appeared on the IBM scene.
> > >
> > Don't badger the novice.  Vaunting your superiority is unseemly.
> >
> > -- gil
> >
> > --
> > For IBM-MAIN subscribe / signoff / archive access instructions, send
> > email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
> >
> >
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send email
to
> lists...@bama.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

Re: Accessing USS on Mainframe thru Telnet

[Veilleux, Jon L]

I prefer to keep my comments succinct rather than ramble on about inane 
complaints about acronym usage.
You must have too much time on your hands to waste so much of it on useless 
bickering, ergo, you need to get a life.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of 
Chris Mason
Sent: Friday, April 06, 2012 1:28 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: Accessing USS on Mainframe thru Telnet

Garrulousity personified

On Fri, 6 Apr 2012 12:48:02 -0400, Veilleux, Jon L  wrote:

>Get a life!

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@bama.ua.edu with the message: INFO IBM-MAIN
This e-mail may contain confidential or privileged information. If
you think you have received this e-mail in error, please advise the
sender by reply e-mail and then delete this e-mail immediately.
Thank you. Aetna   

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

Re: Accessing USS on Mainframe thru Telnet

[Chris Mason]

Garrulousity personified

On Fri, 6 Apr 2012 12:48:02 -0400, Veilleux, Jon L  wrote:

>Get a life!

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

Re: Accessing USS on Mainframe thru Telnet

[Chris Mason]

John

> ...  appears to believe that if he continues to be "bothersome" about the 
> "misuse" of the term USS, ...

Did you not notice the extreme provocation which led to last month's post? One 
of the redbook authors actually had the temerity to claim that the misuse was 
official! Since my riposte referred to some IBM-MAIN traffic - in addition to 
the consolidation of the reasons why it was so wrong - it seemed only polite to 
pass on the text to the subscribers.

> IMO, in most cases the meaning of USS is easily recognizable from the context.

"Most" is not "all". And it is in the difference between "most" and "all" that 
the *immediate* ambiguity/confusion can arise. In these cases, as in this 
thread, TELNET will be involved.

For novices, the problem is a "delayed" ambiguity. As I'm sure I've said 
recently, probably more than once, a novice will become bamboozled with the 
repeated misuse and will suffer when and if presented with the genuine article 
in an easily imagined scenario.

Howard Rifkind - bless him - is the living - I hope - proof!

It is, of course, so totally unnecessary since IBM in its wisdom back when it 
was decided to change OpenEdition to UNIX System Services so thoughtfully 
provided the abbreviation OS/390 UNIX - which naturally needed to morph into 
z/OS UNIX - which incidentally, even under provocation, you adopt.

> If it is not, then the email is likely so vague or poorly written that trying 
> to understand what is needed is a waste of my time, and I ignore it.

It's also not too easy what you are trying to say here. It has the aura of a 
bit of a wriggle!

Finally, if I have reason to participate in a thread and the post to which I am 
replying contains the misuse, I reserve the right - against all the rants of 
the spittle-flecked[2] - to insert a correction, if only to maintain 
credibility!

-

Anyhow I'm pleased that your efforts and mine and Mark Zelden's probably 
provided Chokalingam Thangavelu with all he needed to know.

-

[1] I hope he forgives the reference but it so precisely illustrates my point 
and he was brave enough to express his confusion. I expect many another has 
suffered - and will suffer - in silence.

Thread: Mainframe hacking
Date: Mon, 20 Jul 2009 05:36:28 -0700

[2] If there's any "ranting" going on, it is inevitably the spittle-flecked who 
start it and I feel obliged to respond in kind in order to give no possibility 
of credence to the falsehoods expressed. In the case you quoted, it was the 
Gilmartin character - and I didn't even get round to rubbishing the total lack 
of logic in his final comment.

-
 
Chris Mason


On Fri, 6 Apr 2012 08:09:53 -0500, McKown, John  
wrote:

>I appreciate Chris' knowledge of most things, especially VTAM. But apparently 
>he has a "thing" about USS. And also appears to believe that if he continues 
>to be "bothersome" about the "misuse" of the term USS, that either: (a) people 
>will be educated and will voluntarily change or (b) will become tired of 
>hearing the rants and so change their usage just to shut him up. I doubt that 
>either will occur. IMO, in most cases the meaning of USS is easily 
>recognizable from the context. If it is not, then the email is likely so vague 
>or poorly written that trying to understand what is needed is a waste of my 
>time, and I ignore it.
>
>--
>John McKown

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

Re: Accessing USS on Mainframe thru Telnet

[Veilleux, Jon L]

Get a life!

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of 
Chris Mason
Sent: Friday, April 06, 2012 12:45 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: Accessing USS on Mainframe thru Telnet

Edward

> I chose option (c).

That'll be don't misuse the abbreviation in the first place and use it only for 
the IBM context for which it was first coined - I suppose.

Chris Mason

On Fri, 6 Apr 2012 09:31:32 -0700, Edward Jaffe  
wrote:

>On 4/6/2012 6:09 AM, McKown, John wrote:
...
> (a) people will be educated and will voluntarily change or
> (b) will become tired of hearing the rants and so change their usage just to 
> shut him up.
...
>I chose option (c). ;-)
>
>--
>Edward E Jaffe

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@bama.ua.edu with the message: INFO IBM-MAIN
This e-mail may contain confidential or privileged information. If
you think you have received this e-mail in error, please advise the
sender by reply e-mail and then delete this e-mail immediately.
Thank you. Aetna   

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

Re: Accessing USS on Mainframe thru Telnet

[Chris Mason]

Edward

> I chose option (c).

That'll be don't misuse the abbreviation in the first place and use it only for 
the IBM context for which it was first coined - I suppose.

Chris Mason

On Fri, 6 Apr 2012 09:31:32 -0700, Edward Jaffe  
wrote:

>On 4/6/2012 6:09 AM, McKown, John wrote:
...
> (a) people will be educated and will voluntarily change or 
> (b) will become tired of hearing the rants and so change their usage just to 
> shut him up.
...
>I chose option (c). ;-)
>
>--
>Edward E Jaffe

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

Re: Accessing USS on Mainframe thru Telnet

[Edward Jaffe]

On 4/6/2012 6:09 AM, McKown, John wrote:

I appreciate Chris' knowledge of most things, especially VTAM. But apparently he has a "thing" 
about USS. And also appears to believe that if he continues to be "bothersome" about the 
"misuse" of the term USS, that either: (a) people will be educated and will voluntarily change or 
(b) will become tired of hearing the rants and so change their usage just to shut him up.


I chose option (c). ;-)

--
Edward E Jaffe
Phoenix Software International, Inc
831 Parkview Drive North
El Segundo, CA 90245
310-338-0400 x318
edja...@phoenixsoftware.com
http://www.phoenixsoftware.com/

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

Re: Accessing USS on Mainframe thru Telnet

[McKown, John]

Probably, given how we do things anymore, it would likely run Windows. I dread 
the day that we lose a war because our weapons "blue screened".

--
John McKown 
Systems Engineer IV
IT

Administrative Services Group

HealthMarkets(r)

9151 Boulevard 26 * N. Richland Hills * TX 76010
(817) 255-3225 phone * 
john.mck...@healthmarkets.com * www.HealthMarkets.com

Confidentiality Notice: This e-mail message may contain confidential or 
proprietary information. If you are not the intended recipient, please contact 
the sender by reply e-mail and destroy all copies of the original message. 
HealthMarkets(r) is the brand name for products underwritten and issued by the 
insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance 
Company(r), Mid-West National Life Insurance Company of TennesseeSM and The 
MEGA Life and Health Insurance Company.SM

> -Original Message-
> From: IBM Mainframe Discussion List 
> [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Tony's Comcast account
> Sent: Friday, April 06, 2012 8:23 AM
> To: IBM-MAIN@bama.ua.edu
> Subject: Re: Accessing USS on Mainframe thru Telnet
> 
> So if our navy ever launches a ship called USS VTAM, what 
> type of software
> would it use?
> 
> Sorry, it's Friday.  ;-)
> 
> 
> 
>  
> 
> -Original Message-
> From: IBM Mainframe Discussion List 
> [mailto:IBM-MAIN@bama.ua.edu] On Behalf
> Of McKown, John
> Sent: Friday, April 06, 2012 8:10 AM
> To: IBM-MAIN@bama.ua.edu
> Subject: Re: Accessing USS on Mainframe thru Telnet
> 
> I appreciate Chris' knowledge of most things, especially VTAM. But
> apparently he has a "thing" about USS. And also appears to 
> believe that if
> he continues to be "bothersome" about the "misuse" of the 
> term USS, that
> either: (a) people will be educated and will voluntarily 
> change or (b) will
> become tired of hearing the rants and so change their usage 
> just to shut him
> up. I doubt that either will occur. IMO, in most cases the 
> meaning of USS is
> easily recognizable from the context. If it is not, then the 
> email is likely
> so vague or poorly written that trying to understand what is 
> needed is a
> waste of my time, and I ignore it.
> 
> --
> John McKown 
> Systems Engineer IV
> IT
> 
> Administrative Services Group
> 
> HealthMarkets(r)
> 
> 9151 Boulevard 26 * N. Richland Hills * TX 76010
> (817) 255-3225 phone * 
> john.mck...@healthmarkets.com * www.HealthMarkets.com
> 
> Confidentiality Notice: This e-mail message may contain 
> confidential or
> proprietary information. If you are not the intended recipient, please
> contact the sender by reply e-mail and destroy all copies of 
> the original
> message. HealthMarkets(r) is the brand name for products 
> underwritten and
> issued by the insurance subsidiaries of HealthMarkets, Inc. 
> -The Chesapeake
> Life Insurance Company(r), Mid-West National Life Insurance Company of
> TennesseeSM and The MEGA Life and Health Insurance Company.SM
> 
>  
> 
> > -Original Message-
> > From: IBM Mainframe Discussion List 
> > [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Paul Gilmartin
> > Sent: Thursday, April 05, 2012 11:45 AM
> > To: IBM-MAIN@bama.ua.edu
> > Subject: Re: Accessing USS on Mainframe thru Telnet
> > 
> > On Thu, 5 Apr 2012 09:31:57 -0500, Chris Mason wrote:
> > >
> > >However, there are indications you have been seduced by the 
> > incorrect use of the abbreviation for what started out as 
> > VTAM's Unformatted System Services at least two decades 
> > before UNIX System Services appeared on the IBM scene.
> > > 
> > Don't badger the novice.  Vaunting your superiority is unseemly.
> > 
> > -- gil
> > 
> > 
> --
> > For IBM-MAIN subscribe / signoff / archive access instructions,
> > send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
> > 
> > 
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
> 
> 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

Re: Accessing USS on Mainframe thru Telnet

[Tony's Comcast account]

So if our navy ever launches a ship called USS VTAM, what type of software
would it use?

Sorry, it's Friday.  ;-)



 

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf
Of McKown, John
Sent: Friday, April 06, 2012 8:10 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: Accessing USS on Mainframe thru Telnet

I appreciate Chris' knowledge of most things, especially VTAM. But
apparently he has a "thing" about USS. And also appears to believe that if
he continues to be "bothersome" about the "misuse" of the term USS, that
either: (a) people will be educated and will voluntarily change or (b) will
become tired of hearing the rants and so change their usage just to shut him
up. I doubt that either will occur. IMO, in most cases the meaning of USS is
easily recognizable from the context. If it is not, then the email is likely
so vague or poorly written that trying to understand what is needed is a
waste of my time, and I ignore it.

--
John McKown 
Systems Engineer IV
IT

Administrative Services Group

HealthMarkets(r)

9151 Boulevard 26 * N. Richland Hills * TX 76010
(817) 255-3225 phone * 
john.mck...@healthmarkets.com * www.HealthMarkets.com

Confidentiality Notice: This e-mail message may contain confidential or
proprietary information. If you are not the intended recipient, please
contact the sender by reply e-mail and destroy all copies of the original
message. HealthMarkets(r) is the brand name for products underwritten and
issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake
Life Insurance Company(r), Mid-West National Life Insurance Company of
TennesseeSM and The MEGA Life and Health Insurance Company.SM

 

> -Original Message-
> From: IBM Mainframe Discussion List 
> [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Paul Gilmartin
> Sent: Thursday, April 05, 2012 11:45 AM
> To: IBM-MAIN@bama.ua.edu
> Subject: Re: Accessing USS on Mainframe thru Telnet
> 
> On Thu, 5 Apr 2012 09:31:57 -0500, Chris Mason wrote:
> >
> >However, there are indications you have been seduced by the 
> incorrect use of the abbreviation for what started out as 
> VTAM's Unformatted System Services at least two decades 
> before UNIX System Services appeared on the IBM scene.
> > 
> Don't badger the novice.  Vaunting your superiority is unseemly.
> 
> -- gil
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
> 
> 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

Re: Accessing USS on Mainframe thru Telnet

[McKown, John]

I appreciate Chris' knowledge of most things, especially VTAM. But apparently 
he has a "thing" about USS. And also appears to believe that if he continues to 
be "bothersome" about the "misuse" of the term USS, that either: (a) people 
will be educated and will voluntarily change or (b) will become tired of 
hearing the rants and so change their usage just to shut him up. I doubt that 
either will occur. IMO, in most cases the meaning of USS is easily recognizable 
from the context. If it is not, then the email is likely so vague or poorly 
written that trying to understand what is needed is a waste of my time, and I 
ignore it.

--
John McKown 
Systems Engineer IV
IT

Administrative Services Group

HealthMarkets(r)

9151 Boulevard 26 * N. Richland Hills * TX 76010
(817) 255-3225 phone * 
john.mck...@healthmarkets.com * www.HealthMarkets.com

Confidentiality Notice: This e-mail message may contain confidential or 
proprietary information. If you are not the intended recipient, please contact 
the sender by reply e-mail and destroy all copies of the original message. 
HealthMarkets(r) is the brand name for products underwritten and issued by the 
insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance 
Company(r), Mid-West National Life Insurance Company of TennesseeSM and The 
MEGA Life and Health Insurance Company.SM

 

> -Original Message-
> From: IBM Mainframe Discussion List 
> [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Paul Gilmartin
> Sent: Thursday, April 05, 2012 11:45 AM
> To: IBM-MAIN@bama.ua.edu
> Subject: Re: Accessing USS on Mainframe thru Telnet
> 
> On Thu, 5 Apr 2012 09:31:57 -0500, Chris Mason wrote:
> >
> >However, there are indications you have been seduced by the 
> incorrect use of the abbreviation for what started out as 
> VTAM's Unformatted System Services at least two decades 
> before UNIX System Services appeared on the IBM scene.
> > 
> Don't badger the novice.  Vaunting your superiority is unseemly.
> 
> -- gil
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
> 
> 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

Re: Accessing USS on Mainframe thru Telnet

[Chris Mason]

Mr Gilmartin

As I have attempted to point out on numerous occasions - but you seem to hold 
my opinions in utter contempt - it is very precisely the *novice* who needs 
assistance in getting rid of the pernicious influence of this perpetuating 
travesty.

You probably haven't taken the trouble to notice that, not only were we 
probably dealing with a novice, but that the topic under discussion was TELNET, 
the topic giving rise to the maximum likelihood of actual immediate ambiguity.

On the contrary I am sure we would all appreciate some relief from the 
contentious drivel from your quarter.

Have you managed to get rid of all the pieces of felt from between your teeth 
yet?

Mason

On Thu, 5 Apr 2012 11:44:39 -0500, Paul Gilmartin  wrote:

>On Thu, 5 Apr 2012 09:31:57 -0500, Chris Mason wrote:
>>
>>However, there are indications you have been seduced by the incorrect use of 
>>the abbreviation for what started out as VTAM's Unformatted System Services 
>>at least two decades before UNIX System Services appeared on the IBM scene.
>>
>Don't badger the novice.  Vaunting your superiority is unseemly.
>
>-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

Re: Accessing USS on Mainframe thru Telnet

[Paul Gilmartin]

On Thu, 5 Apr 2012 09:31:57 -0500, Chris Mason wrote:
>
>However, there are indications you have been seduced by the incorrect use of 
>the abbreviation for what started out as VTAM's Unformatted System Services at 
>least two decades before UNIX System Services appeared on the IBM scene.
> 
Don't badger the novice.  Vaunting your superiority is unseemly.

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

Re: Accessing USS on Mainframe thru Telnet

[Mark Zelden]

My client has been using telnet long before openssh was available... and still 
does. 

The port is in /etc/services.  My inetd.conf looks like this:
 
#==
# service | socket | protocol | wait/ | user | server  | server program
# name| type   |  | nowait|  | program |   arguments   
#==
#  
otelnet   stream tcp nowait OMVSKERN /usr/sbin/otelnetd otelnetd -l
shell stream tcp nowait OMVSKERN /usr/sbin/orshd orshd -LV 
login stream tcp nowait OMVSKERN /usr/sbin/rlogind rlogind -m  
oexec stream tcp nowait OMVSKERN /usr/sbin/orexecd orexecd -LV 
ssh   stream tcp nowait OMVSKERN /usr/sbin/sshd sshd -i

/etc/services has a line like this added:

otelnet nnn/tcp OMVS(nnn is the port - usually n23 
or nn23)

The PORT statement in TCPIP profile has it reserved as well:

nnn TCP OMVS; OE TELNET SERVER   


Regards,

Mark
--
Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS   
mailto:m...@mzelden.com
Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html 
Systems Programming expert at http://expertanswercenter.techtarget.com/


On Thu, 5 Apr 2012 09:44:39 -0500, McKown, John  
wrote:

>Using SSH is, IMO, superior. But if you are dead set on using Telnet (perhaps 
>due to lack of an SSH client - I suggest PuTTY), then you must be running the 
>INETD daemon. And you must have a dedicated port number on z/OS to use. We use 
>port 2023. In the /etc/inetd.conf file, you need a line like:
>
>2023  stream tcp nowait BPXROOT /usr/sbin/otelnetd otelnetd -l -t -D login
>
>Replace the "2023" with the port you want to use. Then, to get a UNIX shell 
>prompt, you telnet into that port number. This works for me.
>
>--
>John McKown
>Systems Engineer IV
>IT
>
>Administrative Services Group
>
>HealthMarkets(r)
>
>9151 Boulevard 26 * N. Richland Hills * TX 76010
>(817) 255-3225 phone *
>john.mck...@healthmarkets.com * www.HealthMarkets.com
>
>Confidentiality Notice: This e-mail message may contain confidential or 
>proprietary information. If you are not the intended recipient, please contact 
>the sender by reply e-mail and destroy all copies of the original message. 
>HealthMarkets(r) is the brand name for products underwritten and issued by the 
>insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance 
>Company(r), Mid-West National Life Insurance Company of TennesseeSM and The 
>MEGA Life and Health Insurance Company.SM
>
>
>
>> -Original Message-
>> From: IBM Mainframe Discussion List
>> [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Chokalingam Thangavelu
>> Sent: Thursday, April 05, 2012 8:52 AM
>> To: IBM-MAIN@bama.ua.edu
>> Subject: Accessing USS on Mainframe thru Telnet
>>
>> Hi,
>>
>> I am unable to access the Unix system services thru Telnet
>> and could not find below configurations in USS files.
>>
>>
>> 1.   Could not find 'otelnet in file /etc/services' which
>> points to the port of the USS telnet.
>>
>> 2.   There is no otelnetd daemon or the configured inetd
>> is running on the system
>>
>> 3.   Could not fine INET in /etc/inet.conf
>>
>> Please let me know how to define above TELNET configurations
>> and access USS thru TELNET.
>>
>> Regards,
>> Chokalingam
>>
>> Please do not print this email unless it is absolutely necessary.
>>
>> The information contained in this electronic message and any
>> attachments to this message are intended for the exclusive
>> use of the addressee(s) and may contain proprietary,
>> confidential or privileged information. If you are not the
>> intended recipient, you should not disseminate, distribute or
>> copy this e-mail. Please notify the sender immediately and
>> destroy all copies of this message and any attachments.
>>
>> WARNING: Computer viruses can be transmitted via email. The
>> recipient should check this email and any attachments for the
>> presence of viruses. The company accepts no liability for any
>> damage caused by any virus transmitted by this email.
>>
>> www.wipro.com
>>
>> --
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
>>
>>
>
>--
>For IBM-MAIN subscribe / signoff / archive access instructions,
>send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

Re: Accessing USS on Mainframe thru Telnet

[Steve Comstock]

On 4/5/2012 9:56 AM, Chris Mason wrote:

Steve


We don't have a port in our /etc/inted.conf file; in fact, the only non-comment 
line we have is:



otelnet  stream tcp nowait OMVSKERN /usr/sbin/otelnetd otelnetd



I think this is because '23' is the default telnet server port, and we
have

that port allocated to telnet in our tcpparms profile.


You may recall that one of the items in Chokalingam's list was the following:


1. Could not find 'otelnet in file /etc/services' which points to the port of 
the USS telnet.


This is where the association between the "service name" in the first
position

of the inetd.conf file and the port number is established. It is *not* taken
from the PORT statement list entry.


Chris Mason



Ah, thanks for the clarification.




On Thu, 5 Apr 2012 09:06:11 -0600, Steve Comstock  
wrote:

...

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN




--

Kind regards,

-Steve Comstock
The Trainer's Friend, Inc.

303-355-2752
http://www.trainersfriend.com

* To get a good Return on your Investment, first make an investment!
  + Training your people is an excellent investment

* Try our tool for calculating your Return On Investment
for training dollars at
  http://www.trainersfriend.com/ROI/roi.html

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

Re: Accessing USS on Mainframe thru Telnet

[Chris Mason]

Steve

> We don't have a port in our /etc/inted.conf file; in fact, the only 
> non-comment line we have is:

> otelnet  stream tcp nowait OMVSKERN /usr/sbin/otelnetd otelnetd

> I think this is because '23' is the default telnet server port, and we have 
> that port allocated to telnet in our tcpparms profile.

You may recall that one of the items in Chokalingam's list was the following:

> 1. Could not find 'otelnet in file /etc/services' which points to the port of 
> the USS telnet.

This is where the association between the "service name" in the first position 
of the inetd.conf file and the port number is established. It is *not* taken 
from the PORT statement list entry.

Chris Mason


On Thu, 5 Apr 2012 09:06:11 -0600, Steve Comstock  
wrote:

...

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

Re: Accessing USS on Mainframe thru Telnet

[Chris Mason]

> And you must have a dedicated port number on z/OS to use. We use port 2023.

Sorry John - not strictly true - unless there's a consideration of which I am 
unaware which prevents use of the well-documented technique I am about to 
propose as an alternative.

The "trick" is to use "virtual IP addresses" (VIPAs) - decided on the IBMTCP-L 
list better to be described as "virtual *interface* IP addresses" - in 
combination with the BIND parameter of the relevant PORT statement list entries.

Thus you have a PORT statement list entry for the SNA-oriented TELNET server 
and you have a PORT statement list entry for the UNIX-oriented TELNET server.

Here's an example based on just how the BIND parameter works, the sample given 
in section 2.22.5, "Configuring TSO and z/OS UNIX Remote Execution servers to 
use the same port" in the z/OS Communications Server IP Configuration Guide, 
various other bits and pieces of information in the same manual and the 
Configuration Reference manual:

Definition of VIPAs:

VIPADYNAMIC
 VIPARANGE 255.255.255.255 10.1.1.1
 VIPARANGE 255.255.255.255 10.1.1.2
ENDVIPADYNAMIC

Extract of PORT statement:

PORT
 ...
 23 TCP TN3270E BIND 10.1.1.1
 23 TCP OMVSBIND 10.1.1.2
 ...

Extract of /etc/services:

...
otelnet 23/tcp
...

Extract of inetd.conf:

...
otelnet stream tcp nowait OMVSKERN /usr/sbin/otelnetd otelnetd
...

For clients who wish to access the SNA-oriented TELNET server, ideally a name 
system entry will be available which specifies IP address 10.1.1.1 as the 
destination so that entry of the command

telnet sna.my.lovely.system.com

causes a TELNET connection to 10.1.1.1, port 23.

For clients who wish to access the UNIX-oriented TELNET server, ideally a name 
system entry will be available which specifies IP address 10.1.1.2 as the 
destination so that entry of the command

telnet unix.my.lovely.system.com

causes a TELNET connection to 10.1.1.2, port 23.

Thus neither of the TELNET servers need use a *dedicated* port number.

Note that I prefer to propose VIPARANGE dynamic VIPA with the PORT statement 
list entry BIND parameter rather than static VIPA for server applications just 
as a matter of course. The reason is that the associated "service" will be 
"advertised" using whatever dynamic routing protocol is in use *only* when the 
"service" is available.

-

Incidentally, I'd be grateful if someone with a "sandbox" and a bit of time on 
their hands could verify this sample.

-

Chris Mason

On Thu, 5 Apr 2012 09:44:39 -0500, McKown, John  
wrote:

>Using SSH is, IMO, superior. But if you are dead set on using Telnet (perhaps 
>due to lack of an SSH client - I suggest PuTTY), then you must be running the 
>INETD daemon. And you must have a dedicated port number on z/OS to use. We use 
>port 2023. In the /etc/inetd.conf file, you need a line like:
>
>2023  stream tcp nowait BPXROOT /usr/sbin/otelnetd otelnetd -l -t -D login
>
>Replace the "2023" with the port you want to use. Then, to get a UNIX shell 
>prompt, you telnet into that port number. This works for me.
>
>--
>John McKown

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

Re: Accessing USS on Mainframe thru Telnet

[Kirk Wolf]

We use a Dallas RDP system, and IBM installed IBM Ported Tools OpenSSH for
us.I think that all I had to do was to customize the SSHD started task
a bit.

There isn't much payback for using ssh over tty telnet, until your password
is snatched from an unencrypted telnet session :-)   But if you are using
unencrypted TN3270, its the same issue.


> BTW, we use telnet because that's the way our system from Dallas
> is set up. We are not sysprogs so we try to minimize the systems
> programming work we need to do. (Oh, we do some, of course, to
> install new versions of products, etc., but these are driven by
> course needs, e.g.: setting up DB2 8 and 9 and 10 as needed; even
> then, the Dallas staff does most the work, we merely need to
> tailor things to our config).
>
> There doesn't seem to be much payback to go to ssh in return for
> the work. Our system is actually only in non-sleep mode a few days
> a month (well, it's erratic, depending on our current development
> work).
>
>
>
>  --
>> John McKown
>> Systems Engineer IV
>> IT
>>
>> Administrative Services Group
>>
>> HealthMarkets(r)
>>
>> 9151 Boulevard 26 * N. Richland Hills * TX 76010
>> (817) 255-3225 phone *
>> john.mck...@healthmarkets.com * www.HealthMarkets.com
>>
>> Confidentiality Notice: This e-mail message may contain confidential or
>> proprietary information. If you are not the intended recipient, please
>> contact the sender by reply e-mail and destroy all copies of the original
>> message. HealthMarkets(r) is the brand name for products underwritten and
>> issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake
>> Life Insurance Company(r), Mid-West National Life Insurance Company of
>> TennesseeSM and The MEGA Life and Health Insurance Company.SM
>>
>>
>>
>>  -Original Message-
>>> From: IBM Mainframe Discussion List
>>> [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Chokalingam Thangavelu
>>> Sent: Thursday, April 05, 2012 8:52 AM
>>> To: IBM-MAIN@bama.ua.edu
>>> Subject: Accessing USS on Mainframe thru Telnet
>>>
>>> Hi,
>>>
>>> I am unable to access the Unix system services thru Telnet
>>> and could not find below configurations in USS files.
>>>
>>>
>>> 1.   Could not find 'otelnet in file /etc/services' which
>>> points to the port of the USS telnet.
>>>
>>> 2.   There is no otelnetd daemon or the configured inetd
>>> is running on the system
>>>
>>> 3.   Could not fine INET in /etc/inet.conf
>>>
>>> Please let me know how to define above TELNET configurations
>>> and access USS thru TELNET.
>>>
>>> Regards,
>>> Chokalingam
>>>
>>>
>
> --
>
> Kind regards,
>
> -Steve Comstock
> The Trainer's Friend, Inc.
>
> 303-355-2752
> http://www.trainersfriend.com
>
> * To get a good Return on your Investment, first make an investment!
>  + Training your people is an excellent investment
>
> * Try our tool for calculating your Return On Investment
>for training dollars at
>  
> http://www.trainersfriend.com/**ROI/roi.html
>
>
> --**--**--
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

Re: Accessing USS on Mainframe thru Telnet

[Steve Comstock]

On 4/5/2012 8:44 AM, McKown, John wrote:

Using SSH is, IMO, superior. But if you are dead set on using Telnet
(perhaps

due to lack of an SSH client - I suggest PuTTY), then you must be running the
INETD daemon. And you must have a dedicated port number on z/OS to use. We use
port 2023. In the /etc/inetd.conf file, you need a line like:


2023  stream tcp nowait BPXROOT /usr/sbin/otelnetd otelnetd -l -t -D login

Replace the "2023" with the port you want to use. Then, to get a UNIX shell 
prompt, you telnet into that port number. This works for me.



We don't have a port in our /etc/inted.conf file; in fact, the only
non-comment line we have is:

otelnet  stream tcp nowait OMVSKERN /usr/sbin/otelnetd otelnetd

I think this is because '23' is the default telnet server port, and we
have that port allocated to telnet in our tcpparms profile.


BTW, we use telnet because that's the way our system from Dallas
is set up. We are not sysprogs so we try to minimize the systems
programming work we need to do. (Oh, we do some, of course, to
install new versions of products, etc., but these are driven by
course needs, e.g.: setting up DB2 8 and 9 and 10 as needed; even
then, the Dallas staff does most the work, we merely need to
tailor things to our config).

There doesn't seem to be much payback to go to ssh in return for
the work. Our system is actually only in non-sleep mode a few days
a month (well, it's erratic, depending on our current development
work).



--
John McKown
Systems Engineer IV
IT

Administrative Services Group

HealthMarkets(r)

9151 Boulevard 26 * N. Richland Hills * TX 76010
(817) 255-3225 phone *
john.mck...@healthmarkets.com * www.HealthMarkets.com

Confidentiality Notice: This e-mail message may contain confidential or 
proprietary information. If you are not the intended recipient, please contact 
the sender by reply e-mail and destroy all copies of the original message. 
HealthMarkets(r) is the brand name for products underwritten and issued by the 
insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance 
Company(r), Mid-West National Life Insurance Company of TennesseeSM and The 
MEGA Life and Health Insurance Company.SM




-Original Message-
From: IBM Mainframe Discussion List
[mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Chokalingam Thangavelu
Sent: Thursday, April 05, 2012 8:52 AM
To: IBM-MAIN@bama.ua.edu
Subject: Accessing USS on Mainframe thru Telnet

Hi,

I am unable to access the Unix system services thru Telnet
and could not find below configurations in USS files.


1.   Could not find 'otelnet in file /etc/services' which
points to the port of the USS telnet.

2.   There is no otelnetd daemon or the configured inetd
is running on the system

3.   Could not fine INET in /etc/inet.conf

Please let me know how to define above TELNET configurations
and access USS thru TELNET.

Regards,
Chokalingam




--

Kind regards,

-Steve Comstock
The Trainer's Friend, Inc.

303-355-2752
http://www.trainersfriend.com

* To get a good Return on your Investment, first make an investment!
  + Training your people is an excellent investment

* Try our tool for calculating your Return On Investment
for training dollars at
  http://www.trainersfriend.com/ROI/roi.html

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

Re: Accessing USS on Mainframe thru Telnet

[McKown, John]

Using SSH is, IMO, superior. But if you are dead set on using Telnet (perhaps 
due to lack of an SSH client - I suggest PuTTY), then you must be running the 
INETD daemon. And you must have a dedicated port number on z/OS to use. We use 
port 2023. In the /etc/inetd.conf file, you need a line like:

2023  stream tcp nowait BPXROOT /usr/sbin/otelnetd otelnetd -l -t -D login

Replace the "2023" with the port you want to use. Then, to get a UNIX shell 
prompt, you telnet into that port number. This works for me.

--
John McKown 
Systems Engineer IV
IT

Administrative Services Group

HealthMarkets(r)

9151 Boulevard 26 * N. Richland Hills * TX 76010
(817) 255-3225 phone * 
john.mck...@healthmarkets.com * www.HealthMarkets.com

Confidentiality Notice: This e-mail message may contain confidential or 
proprietary information. If you are not the intended recipient, please contact 
the sender by reply e-mail and destroy all copies of the original message. 
HealthMarkets(r) is the brand name for products underwritten and issued by the 
insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance 
Company(r), Mid-West National Life Insurance Company of TennesseeSM and The 
MEGA Life and Health Insurance Company.SM

 

> -Original Message-
> From: IBM Mainframe Discussion List 
> [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Chokalingam Thangavelu
> Sent: Thursday, April 05, 2012 8:52 AM
> To: IBM-MAIN@bama.ua.edu
> Subject: Accessing USS on Mainframe thru Telnet
> 
> Hi,
> 
> I am unable to access the Unix system services thru Telnet 
> and could not find below configurations in USS files.
> 
> 
> 1.   Could not find 'otelnet in file /etc/services' which 
> points to the port of the USS telnet.
> 
> 2.   There is no otelnetd daemon or the configured inetd 
> is running on the system
> 
> 3.   Could not fine INET in /etc/inet.conf
> 
> Please let me know how to define above TELNET configurations 
> and access USS thru TELNET.
> 
> Regards,
> Chokalingam
> 
> Please do not print this email unless it is absolutely necessary. 
> 
> The information contained in this electronic message and any 
> attachments to this message are intended for the exclusive 
> use of the addressee(s) and may contain proprietary, 
> confidential or privileged information. If you are not the 
> intended recipient, you should not disseminate, distribute or 
> copy this e-mail. Please notify the sender immediately and 
> destroy all copies of this message and any attachments. 
> 
> WARNING: Computer viruses can be transmitted via email. The 
> recipient should check this email and any attachments for the 
> presence of viruses. The company accepts no liability for any 
> damage caused by any virus transmitted by this email. 
> 
> www.wipro.com
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
> 
> 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

Re: Accessing USS on Mainframe thru Telnet

[Chris Mason]

Chokalingam

What your subject line could be taken to suggest is that you should use the 
following reference in order to use USS with the SNA-oriented TELNET server, 
identified in the manuals as TN3270E:

Section 2.2.1.4.15, "Using the Telnet solicitor or USS logon screen" in the 
z/OS Communications Server IP Configuration Guide

http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/f1a1b3b0/2.2.1.4.15

However, there are indications you have been seduced by the incorrect use of 
the abbreviation for what started out as VTAM's Unformatted System Services at 
least two decades before UNIX System Services appeared on the IBM scene.

That being so, the TELNET server you really need is *not* the SNA-oriented 
TELNET Server but the UNIX-oriented TELNET Server  documented as follows:

Section 2.2.2, "Configuring the z/OS UNIX Telnet server" in the z/OS 
Communications Server IP Configuration Guide

http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/F1A1B3B0/2.2.2

If you find all this a bit puzzling, please review my very recent post right 
here in IBM-MAIN with the following Subject line:

A z/OS Redbook Corrected - just about!

http://www.mail-archive.com/ibm-main@bama.ua.edu/msg151511.html

-

Incidentally, reviewing your post, it looks as if you may simply need to edit 
the files on your system so that they look like the files in the documentation 
I have given you.

-

Chris Mason

On Thu, 5 Apr 2012 13:51:45 +, Chokalingam Thangavelu 
 wrote:

>Hi,
>
>I am unable to access the Unix system services thru Telnet and could not find 
>below configurations in USS files.
>
>
>1.   Could not find 'otelnet in file /etc/services' which points to the 
>port of the USS telnet.
>
>2.   There is no otelnetd daemon or the configured inetd is running on the 
>system
>
>3.   Could not fine INET in /etc/inet.conf
>
>Please let me know how to define above TELNET configurations and access USS 
>thru TELNET.
>
>Regards,
>Chokalingam

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

Re: Accessing USS on Mainframe thru Telnet

[Kirk Wolf]

I agree with Mark.

IBM Ported Tools for z/OS - OpenSSH is free, and works well to encrypt your
connections.   With most recent PTFs, it is not possible to use ICSF and
CPACF to enable hardware acceleration of the ciphers and macs, which allows
for much less CPU usage.

Kirk Wolf
Dovetailed Technologies
http://dovetail.com


On Thu, Apr 5, 2012 at 9:00 AM, Mark Jacobs wrote:

> Unless you're dead set on using telnet (which is a bad idea) you should
> setup the ssh daemon and use it to connect to the OMVS environment.
>
> Mark Jacobs
>
>
> On 04/05/12 09:51, Chokalingam Thangavelu wrote:
>
>> Hi,
>>
>> I am unable to access the Unix system services thru Telnet and could not
>> find below configurations in USS files.
>>
>>
>> 1.   Could not find 'otelnet in file /etc/services' which points to
>> the port of the USS telnet.
>>
>> 2.   There is no otelnetd daemon or the configured inetd is running
>> on the system
>>
>> 3.   Could not fine INET in /etc/inet.conf
>>
>> Please let me know how to define above TELNET configurations and access
>> USS thru TELNET.
>>
>> Regards,
>> Chokalingam
>>
>> Please do not print this email unless it is absolutely necessary.
>>
>> The information contained in this electronic message and any attachments
>> to this message are intended for the exclusive use of the addressee(s) and
>> may contain proprietary, confidential or privileged information. If you are
>> not the intended recipient, you should not disseminate, distribute or copy
>> this e-mail. Please notify the sender immediately and destroy all copies of
>> this message and any attachments.
>>
>> WARNING: Computer viruses can be transmitted via email. The recipient
>> should check this email and any attachments for the presence of viruses.
>> The company accepts no liability for any damage caused by any virus
>> transmitted by this email.
>>
>> www.wipro.com
>>
>> --**--**
>> --
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
>>
>>
>>
>
>
> --
> Mark Jacobs
> Time Customer Service
> Tampa, FL
> 
>
> Learn from yesterday, live for today, hope for tomorrow.
> The important thing is to not stop questioning.
>
> - Albert Einstein
>
>
> --**--**--
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

Re: Accessing USS on Mainframe thru Telnet

[Mark Jacobs]

Unless you're dead set on using telnet (which is a bad idea) you should 
setup the ssh daemon and use it to connect to the OMVS environment.


Mark Jacobs

On 04/05/12 09:51, Chokalingam Thangavelu wrote:

Hi,

I am unable to access the Unix system services thru Telnet and could not find 
below configurations in USS files.


1.   Could not find 'otelnet in file /etc/services' which points to the 
port of the USS telnet.

2.   There is no otelnetd daemon or the configured inetd is running on the 
system

3.   Could not fine INET in /etc/inet.conf

Please let me know how to define above TELNET configurations and access USS 
thru TELNET.

Regards,
Chokalingam

Please do not print this email unless it is absolutely necessary.

The information contained in this electronic message and any attachments to 
this message are intended for the exclusive use of the addressee(s) and may 
contain proprietary, confidential or privileged information. If you are not the 
intended recipient, you should not disseminate, distribute or copy this e-mail. 
Please notify the sender immediately and destroy all copies of this message and 
any attachments.

WARNING: Computer viruses can be transmitted via email. The recipient should 
check this email and any attachments for the presence of viruses. The company 
accepts no liability for any damage caused by any virus transmitted by this 
email.

www.wipro.com

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN

   



--
Mark Jacobs
Time Customer Service
Tampa, FL


Learn from yesterday, live for today, hope for tomorrow.
The important thing is to not stop questioning.

- Albert Einstein

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN