no telnet after go save 21
Hi,
Why after ran go save 21, My system, like every day, starts but telnet service is down? I can no start it again and musty rboot the server.
Why after ran go save 21, My system, like every day, starts but telnet service is down? I can no start it again and musty rboot the server.
...after ran go save 21, My system, like every day, starts...Can you explain that more?
You say that your system "starts". What does that mean? Can you connect from a PC to your database through ODBC? Can you FTP from a PC to your system? Can you run iSeries Navigator and see the status of your servers?
...but telnet service is down? I can no start it again and musty rboot the server.
The last step of Save 21 should be to start the controlling subsystem. That should also be the last step of an IPL. The active processes on the system should be the same.
Because of that, something needs more explanation.
Tom
You say that your system "starts". What does that mean? Can you connect from a PC to your database through ODBC? Can you FTP from a PC to your system? Can you run iSeries Navigator and see the status of your servers?
...but telnet service is down? I can no start it again and musty rboot the server.
The last step of Save 21 should be to start the controlling subsystem. That should also be the last step of an IPL. The active processes on the system should be the same.
Because of that, something needs more explanation.
Tom
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
See this article from IBM re: problem with telnet after save.
http://www-01.ibm.com/support/docview.wss?uid=nas1bd4b2b414406c70d8625722d0048df7d
I haven't run into that problem and we did a save just last weekend. Telnet came back up with no problem. Maybe it has something to do with the config or ptf levels.
The article mentions a change in V6R1 that corrects it. If you aren't on 6.1 this is probably the issue.
http://www-01.ibm.com/support/docview.wss?uid=nas1bd4b2b414406c70d8625722d0048df7d
I haven't run into that problem and we did a save just last weekend. Telnet came back up with no problem. Maybe it has something to do with the config or ptf levels.
The article mentions a change in V6R1 that corrects it. If you aren't on 6.1 this is probably the issue.
Use WRKACTJOB to check the status of the controlling subsystem, probably QCTL. If the status is END, use STRSBS QCTL to start it. Wait for the system to start up.
Is the interface coming active?
Use the Configure TCP/IP command CFGTCP. This menu is the starting point for configuring TCP/IP
Use option 1 Work with TCP/IP interfaces
Look for your IP address(es) in the list and note the name of the line description beside it.
Press F11 to see the interface status.
If it is inactive, try option 9 to start it. You may have to start TCP/IP using STRTCP.
Is the line active?
Work with the line description that you found in the previous step, using WRKLIND myline
Press F14 to see the status.
It should be status ACTIVE; if not, use option 1 to vary it on.
There should be a job listed beside the ethernet device named QTCPIP. If not, use STRTCP to start it.
This is a good starting point.
Post back any questions!
Barry