In
7006637956401197.wa.elardus.engelbrechtsita.co...@listserv.ua.edu,
on 07/13/2015
at 10:19 AM, Elardus Engelbrecht elardus.engelbre...@sita.co.za
said:
Perhaps, but, Shmuel, what will YOU do if you are in the same
position which John is talking?
What position? Or didn't you catch that
In 559bf24e.5050...@us.ibm.com, on 07/07/2015
at 11:37 AM, John Eells ee...@us.ibm.com said:
Even if you are sure you will never
need it.
You're paranoid, but are you paranoid enough? Finagle has not failed
me yet. Always look for more failure modes and find them before they
find you.
--
Shmuel Metz (Seymour J.) wrote:
John Eells ee...@us.ibm.com said:
Even if you are sure you will never need it.
You're paranoid, but are you paranoid enough?
Perhaps, but, Shmuel, what will YOU do if you are in the same position which
John is talking?
Groete / Greetings
Elardus Engelbrecht
In p06240800d1c5bdfc20a1@[192.168.1.11], on 07/10/2015
at 02:26 PM, Robert A. Rosenberg hal9...@panix.com said:
I was thinking of. As for needed
support, my question was about how you connect to it
Unless TSSO has changed drastically, you don't need no stinking VTAM.
Of couste if all of your
Watch what you say or someone may knock the SNA out of you :)
--- shmuel+ibm-m...@patriot.net wrote:
From: Shmuel Metz (Seymour J.) shmuel+ibm-m...@patriot.net
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: TSO-only proc (was Re: Product Remove from z/OS)
Date: Mon, 13 Jul
Or QUERY your PSERVIC...
In a message dated 7/13/2015 4:10:36 P.M. Central Daylight Time,
rpin...@netscape.com writes:
say or someone may knock the SNA out of you :)
--
For IBM-MAIN subscribe / signoff / archive access
On Mon, 13 Jul 2015 16:24:37 -0400, Shmuel Metz (Seymour J.)
shmuel+ibm-m...@patriot.net wrote:
Unless TSSO has changed drastically, ...
Unless TSSO has changed drastically it won't work very well since the last
phases of console restructuring circa z/os 1.11-1.12, which introduced changes
@listserv.ua.edu] On Behalf
Of Gerhard Adam
Sent: Thursday, July 09, 2015 3:47 PM
To: IBM-MAIN@listserv.ua.edu
Subject: [EXTERNAL] Re: TSO-only proc (was Re: Product Remove from z/OS)
I'm assuming that this was an early MVS system, then and not something earlier?
Adam
-Original Message-
From: IBM
At 18:08 -0400 on 07/09/2015, Ed Finnell wrote about Re: TSO-only
proc (was Re: Product Remove from z/OS):
TSSO. It doesn't need anything else.
Yes that was the Subsystem TSO I was thinking of. As for needed
support, my question was about how you connect to it since VTAM may
Needs a consol-just like MVS!
In a message dated 7/10/2015 1:50:05 P.M. Central Daylight Time,
hal9...@panix.com writes:
Yes that was the Subsystem TSO I was thinking of. As for needed
support, my question was about how you connect to it since VTAM may
not be available to serve as the
Of Gerhard Adam
Sent: Thursday, July 09, 2015 2:48 PM
To: IBM-MAIN@listserv.ua.edu
Subject: [EXTERNAL] Re: TSO-only proc (was Re: Product Remove from z/OS)
I'm not clear on why you would have had to restore every DASD device on the
system. The only thing that needed to be restored was the deleted
McKown
Sent: Tuesday, July 07, 2015 11:46 AM
To: IBM-MAIN@listserv.ua.edu
Subject: [EXTERNAL] Re: TSO-only proc (was Re: Product Remove from z/OS)
On Tue, Jul 7, 2015 at 10:39 AM, Richard Pinion rpin...@netscape.com
wrote:
Naw, card punch and card reader are your best friends in such an
emergency
] On Behalf
Of Schmeelk, Gregory P.
Sent: Thursday, July 9, 2015 11:21 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: TSO-only proc (was Re: Product Remove from z/OS)
Thank you for bringing back the very painful memory of working for the Navy
when someone deleted a library that was in the JES2 proc
, John Eells wrote about TSO-only proc
(was Re: Product Remove from z/OS):
That works for updating the procs themselves, and it's an
outstanding precaution everyone should use as a matter of routine.
But it does not work so well for a volume failure, when a data set
named in the proc is moved
: TSO-only proc (was Re: Product Remove from z/OS)
It was unknown where the dataset was at and I had no VTOC listings (or any
other listings for that matter) for anything and no online access to anything.
It was a very unusual case.
-Original Message-
From: IBM Mainframe Discussion List
TSSO. It doesn't need anything else. It does need care and feeding and
testing as new releases and
CPUs are brought online. There's also _www.newera.com_
(http://www.newera.com) for vendor supported. They used to have PC
IODF creator but sold it to IBM.
Never hurts to have 'one pack'
That works for updating the procs themselves, and it's an outstanding
precaution everyone should use as a matter of routine.
But it does not work so well for a volume failure, when a data set named
in the proc is moved (and referenced by volser) or renamed, or when the
concatenation limit is
We keep a TSO rescue proc with '911' in the name. It lives in SYS1.PROCLIB
away from the standard location for TSO procs
We do something similar, but often it's easier to FTP the broken logon proc to
a PC, edit it, and FTP it back to the host.
Bob Shannon
Rocket Software
...@us.ibm.com wrote:
From: John Eells ee...@us.ibm.com
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: TSO-only proc (was Re: Product Remove from z/OS)
Date: Tue, 7 Jul 2015 11:37:50 -0400
That works for updating the procs themselves, and it's an outstanding
precaution everyone should
Yeah, but what about breaking the VTAM and worse yet the JES2 procs?
--- bshan...@rocketsoftware.com wrote:
From: Bob Shannon bshan...@rocketsoftware.com
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: TSO-only proc (was Re: Product Remove from z/OS)
Date: Tue, 7 Jul 2015
Mobile
jo.skip.robin...@sce.com
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of John Eells
Sent: Tuesday, July 07, 2015 8:38 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: TSO-only proc (was Re: Product Remove from z/OS)
That works for updating
Naw, card punch and card reader are your best friends in such an
emergency :)
--- ee...@us.ibm.com wrote:
From: John Eells ee...@us.ibm.com
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: TSO-only proc (was Re: Product Remove from z/OS)
Date: Tue, 7 Jul 2015 11:37:50 -0400
Of Richard Pinion
Sent: Tuesday, July 07, 2015 9:42 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: TSO-only proc (was Re: Product Remove from z/OS)
Yeah, but what about breaking the VTAM and worse yet the JES2 procs?
--- bshan...@rocketsoftware.com wrote:
From: Bob Shannon bshan
On Jul 7, 2015, at 10:37 AM, John Eells wrote:
That works for updating the procs themselves, and it's an
outstanding precaution everyone should use as a matter of routine.
But it does not work so well for a volume failure, when a data set
named in the proc is moved (and referenced by
AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: TSO-only proc (was Re: Product Remove from z/OS)
Yeah, but what about breaking the VTAM and worse yet the JES2 procs?
--- bshan...@rocketsoftware.com wrote:
From: Bob Shannon bshan...@rocketsoftware.com
To: IBM-MAIN
25 matches
Mail list logo
