Comments on: tape backup and system save

By: tomliotta

tomliotta — Sun, 15 Nov 2009 06:54:50 +0000

Your question description doesn’t make a lot of sense.

option 21 did nothing after about an hour the system unlocked and I had to IPL

Was that “Option 21 did nothing after about an hour.”
Followed by “The system unlocked, and I had to IPL.”

Lack of punctuation makes it difficult to be sure. Worse, the words are confusing.

What is meant by “the system unlocked”? What changed to make “unlocked” meaningful? And why did you have to IPL?

What’s really missing is any info from the console joblog that would describe what the backup options thought was happening. There might also have been messages in the QSYSOPR message queue, but the joblog would tell why any messages were sent and what the result was.

Tom

By: mjjager

mjjager — Tue, 18 Oct 2005 13:58:15 +0000

Also check you messages to verify you are going into restricted state. If you don’t go restricted, the backup will not kick off. Checking cable connections and device status also wouldn’t hurt.

By: cjmedina

cjmedina — Mon, 17 Oct 2005 16:22:42 +0000

I have had a similar problem, and the cause was an incorrect tape type. Can you review if the tape is the same as you used before, or maybe the tape is not in good conditions.
The process to make a system save must initialize the tapes by itself.

By: bkr0963c

bkr0963c — Mon, 17 Oct 2005 16:17:34 +0000

INZTAP command. Press F4 to prompt so that you can fill in the parameters.

By: rayne427

rayne427 — Mon, 17 Oct 2005 08:38:09 +0000

The initialize tape command can also be called from the command line by typing INZTAP followed by enter.