tape backup and system save
My recent attempt to run a system save with "Go Save" and option 21 did nothing after about an hour the system unlocked and I had to IPL to allow other users to access the server. Could this be a problem of using a tape that was not initialized?. If so what is a command to initialize a tape? We normally initialize with backup.
Software/Hardware used:
Software/Hardware used:
ASKED:
October 16, 2005 10:31 PM
UPDATED:
November 15, 2009 6:54 AM
Answer Wiki:
first go to the menu tape using the command
go tape
in that menu use the option 2 for intialize the tape.
To see all answers submitted to the Answer Wiki: View Answer History.
The initialize tape command can also be called from the command line by typing INZTAP followed by enter.
INZTAP command. Press F4 to prompt so that you can fill in the parameters.
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.
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.
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