RE: Restarting Telnet

Chris,

Nothing wrong with his technique. As long as you have a fall back plan,
such as:
- Remote command
- Remote console capability
- IBM i Navigator
- FTP access
or any number of other options.
Well, I guess the problem might be that you do not make yourself familiar
with all the other options. That, is the real problem with the submitting
job option.

Like the recent long drawn out post from the person who thought they only
shutdown TCP. Only to find out they had to have powered off their system
(after a day or so of working on it).
Or the other person who had a message that was causing TCP issues and
tried an IPL to correct it and I think we eventually determined that they
had multiple lpars with guesting going on and were so unfamiliar with the
operation they couldn't bring the machine up in the right fashion.

There's just some things where it doesn't hurt to practice things on a
periodic basis as a refresher.
I take refresher courses in CPR and First Aid (dual benefit with being a
first responder at work and being in Scouts). Be Prepared.
At times the legendary machine that runs forever even while dry walled
into a closet can be a real hindrance when you've forgotten how to do
basic operations. (I understand that some may feel that there is no such
thing as "basic operations" on a multi lpar machine with guesting, vios,
etc.)

Sure, there are other problems with the submitting job of a custom CL
option.
- If others have to maintain it.
- The many lpars we have with no development tools loaded.
- Guessing how long a DLYJOB is needed, versus the complexity of actually
checking the jobs status's.
- Downtime is increased by the writing of the program, overestimating
DLYJOB times just to be safe, etc.

I think some just are so enamoured of their false god of twinax that they
go into Luddite mode and will only use the Lan Console or HMC at gunpoint.

Rob Berendt