From QSYSOPR yesterday:

CPA4088 Load next tape volume on device TAP35. (C G) 09/09/15 09:40:14

I waited for tape to be ready at load point before responding G.

Then, received this:

CPI5922 Device description TAP35 is not usable at this time. 09/09/15

No messages between those two.

I do not know how I came up with the full damage bit. Definitely not
there. May have been misleading second level text.

The second level text for CPI5922 has this for Technical description:
A machine interface instruction has failed to complete causing device
description TAP35 to become partially damaged. The vertical licensed
internal code log entry identifier is 01011C08.

If I am looking in the right place within SST, I see an entry with that
identifier. Major/minor code is 0300 / 0210. On the right side of the
dump, I see IODRIVERTAPE and two lines down TAP35. Nothing more means
anything to me.

From the screen "Select Entries from Licensed Internal Code Log", the entry
id has Major Description "Damage set.

Prior to that entry is Source/Sink at 09:40:10, two more entries at
09:40:14 and a Tape support message with IoDriverTape Object. Then, the
damage set entry. I think I can print the entries and get them to Google
Docs, if they would be of any help.
Just have to move through a few hoops.

John McKee

On Thu, Sep 10, 2015 at 1:19 PM, CRPence <crpbottle@xxxxxxxxx> wrote:

On 09-Sep-2015 09:48 -0600, John McKee wrote:

The job log shows my G response to the load next tape message.
IMMEDIATELY after that is System object TAP35 partially damaged.
Further down, it states VLOG identifier is *NONE. For recovery, it
states to delete and recreate the DEVD.

Actually, the message reporting "Device description TAP35 damaged" did
not give that recovery for what was diagnosed prior, in that specific
scenario. The recovery for that error message [with symptom msgCPF8105
F/QRCPDMGN T/QTAVOPEN], per the preceding condition of "System object TAP35
partially damaged" [with symptom msgMCH1668 F/#cfdamst T/QTAVOPEN], is to
vary-off and vary-on the device; the damage diagnosed was "partial", not
"full"; despite possibly seemingly subtle distinction to other than an OS
programmer, a distinction with a very consequential difference.
Specifically, the message states:

"If *partial damage* occurred, vary off the device and vary the device on
(VRYCFG command) again. The system may need to be powered down (PWRDWNSYS
command) to vary off the device. If the system is powered down, do an
initial program load (IPL) of the system. If partial damage is indicated on
a 9347 Tape Unit, determine if it was processing a 3600 foot tape. A 9347
Tape Unit can only process up to 2400 foot tapes."

FWiW, the context given for the delete\recreate recovery was different;
only for a prior logged condition of "full" damage, for which the only
recovery is deletion of the full-damaged object, per the text:

"If *full damage* occurred, delete the device description (DLTDEVD
command), and do one of the following: -- Create the device description
again with the appropriate create device command. -- Restore the
configuration (RSTCFG command) from the save tape. The configuration must
be restored from a tape that was saved using the Save System (SAVSYS) or
Save Configuration (SAVCFG) commands. -- Restore the command source for the
device description. The command source must have been saved using a
previous Retrieve Configuration Source (RTVCFGSRC) command. Any associated
controller descriptions may need to be deleted and created again."

Regards, Chuck

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.