RE: Failed GO SAVE 21

John,

I've seen/had similar instances in the past.
Remember, tape errors/retries are handled by the drive, i5/OS may not see them.
Some errors were false errors, corrected by any of the below.
Could be tape firmware, PTFs, and/or 16. Work with threshold table.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John McKee
Sent: Thursday, September 24, 2015 10:48 AM
To: Midrange Systems Technical Discussion
Subject: Re: Failed GO SAVE 21

Yesterday was the fourth week in a row that Go SAVE 21 failed. But, very differently.

Following the misadventure where a tape got stuck, I ended up (since time was already allocated) doing an IPL. That lowered max unprotect from 20 G to around 5G yesterday. Co mbine that with save/delete of a number of libraries. No idea if there is any relation.

So, yesterday, I saw the SAV portion move along. Then, it froze for a long time. Initially, I thought perhaps just a really big IFS file. Maybe, but no idea. The progress line disappeared at some point and then reappeared.
That was followed by messages that spooled output had been created for... a number of times. I think 21 spool files. Disk usage dropped as a result of IPL and removal of libraries to the point that I thought it was low enough (from before) that second tape would not be needed. There was NO message requesting a tape change. Just failed backup, and device left FAILED and damaged.

But, this is different. This time, a problem was logged. The symptom string is 5722 F/QTADMPDV.

I did attempt to Google this. But, I do not understand what I received, as it appears to be related to MLB installation.

Just looked at PRTERRLOG. I decided to no longer use the "standard" of WEEKLY for the volume id. The tape I usedhad one temporary write error, with 138457 M Bytes written. This was the first time this volume id had ever been used.

To summarize: four fails, only last one logged a problem, last failure also did NOT issue a tape change request, and there were entries in LIC LOG much as before. The LIC LOG had no activity posted prior to the failure, which is also different. The entries, to my uneducated mind, appear to be same type as before.

Question: Is this one of >those< issues that violate that stupid dogma "If it ain't broke...", and was there some PTF already created?

Also, from WRKPRB, F11 display APAR library, shows 45 entries. Only two do NOT text. The text for the others has this: Problem 1526634180 and system serial number.

Any distant bells ringing?

John McKee

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

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

This is hopefully the link to access the joblog


https://drive.google.com/file/d/0BxXuBYIdtkWtVHNGQWI0eTVfMzlkNkVZY2VN
V1VRODZJSFRJ/view?usp=sharing

The joblog does seem to indicate that the partial damage condition
was detected on the SAV request, as a *previously set* damage
condition while processing the Tape (volume) Open (QTAVOPEN),
suggesting the /damage/ did not occur and get set\detected at that
specific point in processing, per
EC0 aka RC0; i.e. Error Class = 0000, indicating prior damage vs
damage-set. The condition happens to get detected during that open
processing, requested during Tape End Of Volume (QTAFEOV) processing.
If accurate, that begs the question why none of the other prior SAVxxx
activity [i.e. SAVSYS, SAVLIB *NONSYS, SAVDLO] had encountered that
instead; do not all of those requests also have to perform effectively
the /same/ Open processing [via the component-specific processor for
the effective Tape File (¿QTAOPEN vs QTAVOPEN?) when invoked from
Common Data Management].?

I suppose there could be an error whereby the SAVxxx processes a
code-path that fails to /detect/ the existing damage, and that this
particular QTAVOPEN code path is /properly diagnosing/ the condition.
If so, that would seem likely to imply that either the recovery from
the prior incident had not been performed or had not been properly
effected; i.e. the vary-off and vary-on sequence either was not issued
[since the last incident, prior to this failing save] or that
vary-sequence did not remove the /partially damaged/ designation.?

I do not recall what is the partial damage indicator [a bit in the
object header], but the formatted dump of the device may give an
indication if that is set; such a dump could be produced prior to a
new save, to ensure the bit is off before a GO SAVE Opt21. The
re-create of the device also should ensure the partial-damage
indicator is not set, prior to the next usage; seems safe assumption
that merely varying-on the device will not leave the device damaged.

Without the VLogs, although even with those, there is unlikely to be
anything I could offer further. As I had suggested originally, I
would get [an equivalent of] a complete backup [albeit taken outside
of the GO SAVE Opt21, so as to bypass the issue with the failing
save\system-backup] and then apply preventive maintenance to include
the Cumulative and HIPer groups.

Symptoms [for the archives]:

SAV as part of GO SAVE Opt21
msgCPA4088 F/QTAERR T/QTAERR
msg *NONE Reply F/QMHDSMSS T/QTAERR
msgMCH1668 F/#cfdamst T/QTAVOPEN ec0 rc0
msgCPF8105 F/QRCPDMGN T/QTAVOPEN
msgCPF8105 [re-signaled apparently] T/T/QTAFEOV
msgCPF9999 *FC T/QTAFEOV rcCPF8105
remaining symptoms are irrelevant\normal\aspecific

For reference, some pertinent parts of the joblog:

*NONE Request 09/09/15 08:01:41.018840
QUICMD QSYS 0461 QUICMD QSYS 0461
Message . . . : -go save
CPC2196 Completion 00 09/09/15 08:01:51.963808
QLICUSRL QSYS 0113 Q1AQS QBRM *STMT
To module . . : Q1AQS
To procedure : q1aQCAPCMD
Statement . . : 1
Message . . . : Library QBRM added to library list.
Cause . . . . : If the ADDLIBLE command was used, QBRM was added to the
user library list. If the CHGSYSLIBL command was used, QBRM was added
to the system portion of the library list.
CPC2206 Completion 00 09/09/15 08:01:52.171136
QSYCHONR QSYS 0665 QLIINSRT QSYS 0453
Message . . . : Ownership of object QBRMSPC in QTEMP type *USRSPC
changed.
Cause . . . . : The ownership of object QBRMSPC in library QTEMP type
*USRSPC has changed.
CPC2206 Completion 00 09/09/15 08:01:52.208744
QSYCHONR QSYS 0665 QLIINSRT QSYS 0453
Message . . . : Ownership of object QBRMSPC2 in QTEMP type *USRSPC
changed.
Cause . . . . : The ownership of object QBRMSPC2 in library QTEMP type
*USRSPC has changed.
CPC6778 Completion 00 09/09/15 08:01:55.134712
QTACHECK QSYS 0285 QMNUIM QSYS 01E3
Message . . . : Volume WEEKLY found on device TAP35.
Cause . . . . : Volume identifier WEEKLY found on device TAP35. *N
indicates that the volume is a nonlabeled tape volume.
CPF0936 Information 00 09/09/15 08:02:01.419232
QWCCSDUC QSYS 0500 QMNSRBND QSYS 02C5
Message . . . : ENDSBS SBS(*ALL) in progress.
Cause . . . . : All subsystems and all jobs will be ended except the
controlling subsystem and the requester's job. The system will be in
a restricted condition.
CPC2206 Completion 00 09/09/15 08:03:09.122432
QSYCHONR QSYS 0665 QLIINSRT QSYS 0453
Message . . . : Ownership of object Q1AUSADSM in QTEMP type *USRSPC
changed.
Cause . . . . : The ownership of object Q1AUSADSM in library QTEMP type
*USRSPC has changed.
CPC2206 Completion 00 09/09/15 08:03:11.677168
QSYCHONR QSYS 0665 QLIINSRT QSYS 0453
Message . . . : Ownership of object Q1ALCKQ in QTEMP type *DTAQ changed.
Cause . . . . : The ownership of object Q1ALCKQ in library QTEMP type
*DTAQ has changed.
BRM1481 Information 40 09/09/15 08:03:11.928064
Q1ACALG QBRM *STMT Q1ACALG QBRM *STMT
From module . : Q1ACALG
From procedure: Q1ACALG

5722SS1 V5R4M0 060210 -Job Log-S1015362 09/09/15 09:48:01 Page 23
Job name: DSP04 User: BSYPGMR4 Number: 737486
Job description: BCTL Library: BSYOBJ1
MSGID TYPE SEV DATE TIME
FROM PGM LIBRARY INST TO PGM LIBRARY INST
Statement . . : 229
To module . . : Q1ACALG
To procedure : Q1ACALG
Statement . . : 229
Message . . . : Volume WEEKLY not under media management control.
Cause . . . . : Volume WEEKLY is being used for output, but is not
enrolled in the BRMS media inventory. Usage is by DSP04/BSYPGMR/737486.
CPI6705 Information 00 09/09/15 08:03:31.365288
QTAERR QSYS 00EA QSRSVDEQ QSYS 04AF
Message . . . : 6798 blocks processed for sequence 1, volume WEEKLY, on
device TAP35.
Cause . . . . : 6798 blocks were processed for file label QFILEIML,
sequence 1 for volume WEEKLY loaded on device TAP35. The maximum block
size is 32760. The tape file was opened at 09/09/15 08:03:17 and
closed at
09/09/15 08:03:31. The total time the file was open was 13 seconds. If
the device is a tape library the cartridge is *N and the resource is *N.
CPI6705 Information 00 09/09/15 08:03:33.143272
QTAERR QSYS 00EA QSRSVDEQ QSYS 04AF
Message . . . : 1 blocks processed for sequence 2, volume WEEKLY, on
device TAP35.
Cause . . . . : 1 blocks were processed for file label
QV5R4M0L00.L2924, sequence 2 for volume WEEKLY loaded on device TAP35.
The maximum block size is 32760. The tape file was opened at 09/09/15
08:03:33 and closed at 09/09/15 08:03:33. The total time the file was
open was 0 seconds. If the device is a tape library the cartridge is
*N and the resource is *N.
CPI6705 Information 00 09/09/15 08:03:35.494816
QTAERR QSYS 00EA QSRSVDEQ QSYS 04AF
Message . . . : 216 blocks processed for sequence 3, volume WEEKLY, on
device TAP35.
Cause . . . . : 216 blocks were processed for file label QFILESCR,
sequence 3 for volume WEEKLY loaded on device TAP35. The maximum block
size is 32760. The tape file was opened at 09/09/15 08:03:33 and
closed at
09/09/15 08:03:35. The total time the file was open was 2 seconds. If
the device is a tape library the cartridge is *N and the resource is *N.
CPI6705 Information 00 09/09/15 08:03:36.298904
QTAERR QSYS 00EA QSRSVDEQ QSYS 04AF
Message . . . : 1 blocks processed for sequence 4, volume WEEKLY, on
device TAP35.
Cause . . . . : 1 blocks were processed for file label QIAM400,
sequence 4 for volume WEEKLY loaded on device TAP35. The maximum block
size is 32760. The tape file was opened at 09/09/15 08:03:36 and
closed at
09/09/15 08:03:36. The total time the file was open was 0 seconds. If
the device is a tape library the cartridge is *N and the resource is *N.
CPI6705 Information 00 09/09/15 08:03:37.018320
QTAERR QSYS 00EA QSRSVDEQ QSYS 04AF
Message . . . : 19 blocks processed for sequence 5, volume WEEKLY, on
device TAP35.
Cause . . . . : 19 blocks were processed for file label QFILELDS,
sequence 5 for volume WEEKLY loaded on device TAP35. The maximum block
size is 32760. The tape file was opened at 09/09/15 08:03:36 and
closed at
09/09/15 08:03:37. The total time the file was open was 0 seconds. If
the device is a tape library the cartridge is *N and the resource is *N.
CPI6705 Information 00 09/09/15 08:04:26.818136
QTAERR QSYS 00EA QSRSVDEQ QSYS 04AF
Message . . . : 34391 blocks processed for sequence 6, volume WEEKLY,
on device TAP35.
Cause . . . . : 34391 blocks were processed for file label QFILEMCD,
sequence 6 for volume WEEKLY loaded on device TAP35. The maximum block
size

5722SS1 V5R4M0 060210 -Job Log- S1015362 09/09/15 09:48:01 Page 24
Job name: DSP04 User: BSYPGMR4 Number: 737486
Job description: BCTL Library: BSYOBJ1
MSGID TYPE SEV DATE TIME
FROM PGM LIBRARY INST TO PGM LIBRARY INST
is 32760. The tape file was opened at 09/09/15 08:03:37 and closed at
09/09/15 08:04:26. The total time the file was open was 49 seconds. If
the device is a tape library the cartridge is *N and the resource is *N.
CPI6705 Information 00 09/09/15 08:04:27.589312
QTAERR QSYS 00EA QSRSVDEQ QSYS 04AF
Message . . . : 1 blocks processed for sequence 7, volume WEEKLY, on
device TAP35.
Cause . . . . : 1 blocks were processed for file label
QV5R4M0L00.L2924, sequence 7 for volume WEEKLY loaded on device TAP35.
The maximum block size is 32760. The tape file was opened at 09/09/15
08:04:27 and closed at 09/09/15 08:04:27. The total time the file was
open was 0 seconds. If the device is a tape library the cartridge is
*N and the resource is *N.
CPI6705 Information 00 09/09/15 08:04:28.308448
QTAERR QSYS 00EA QSRSVDEQ QSYS 04AF
Message . . . : 26 blocks processed for sequence 8, volume WEEKLY, on
device TAP35.
Cause . . . . : 26 blocks were processed for file label QFILEIPL,
sequence 8 for volume WEEKLY loaded on device TAP35. The maximum block
size is 32760. The tape file was opened at 09/09/15 08:04:28 and
closed at
09/09/15 08:04:28. The total time the file was open was 0 seconds. If
the device is a tape library the cartridge is *N and the resource is *N.
CPI6705 Information 00 09/09/15 08:04:29.100544
QTAERR QSYS 00EA QSRSVDEQ QSYS 04AF
Message . . . : 59 blocks processed for sequence 9, volume WEEKLY, on
device TAP35.
Cause . . . . : 59 blocks were processed for file label QFILEIN,
sequence 9 for volume WEEKLY loaded on device TAP35. The maximum block
size is 32760. The tape file was opened at 09/09/15 08:04:28 and
closed at
09/09/15 08:04:29. The total time the file was open was 0 seconds. If
the device is a tape library the cartridge is *N and the resource is *N.
CPI6705 Information 00 09/09/15 08:04:34.037704
QTAERR QSYS 00EA QSRSVDEQ QSYS 04AF
Message . . . : 199 blocks processed for sequence 10, volume WEEKLY, on
device TAP35.
Cause . . . . : 199 blocks were processed for file label
Q5722SS1540M.0001, sequence 10 for volume WEEKLY loaded on device TAP35.
The maximum block size is 262144. The tape file was opened at 09/09/15
08:04:29 and closed at 09/09/15 08:04:34. The total time the file was
open was 4 seconds. If the device is a tape library the cartridge is
*N and the resource is *N.
CPI6705 Information 00 09/09/15 08:04:39.291656
QTAERR QSYS 00EA QSRSVDEQ QSYS 04AF
Message . . . : 354 blocks processed for sequence 11, volume WEEKLY, on
device TAP35.
Cause . . . . : 354 blocks were processed for file label
Q5722SS1540M.0002, sequence 11 for volume WEEKLY loaded on device TAP35.
The maximum block size is 262144. The tape file was opened at 09/09/15
08:04:35 and closed at 09/09/15 08:04:39. The total time the file was
open was 4 seconds. If the device is a tape library the cartridge is
*N and the resource is *N.
CPI6705 Information 00 09/09/15 08:04:44.720288
QTAERR QSYS 00EA QSRSVDEQ QSYS 04AF
Message . . . : 184 blocks processed for sequence 12, volume WEEKLY, on
device TAP35.
Cause . . . . : 184 blocks were processed for file label
Q5722SS1540M.0003, sequence 12 for volume WEEKLY loaded on device TAP35.
The maximum block size is 262144. The tape file was opened at 09/09/15
08:04:40 and closed at 09/09/15 08:04:44. The total time the file was
open was 4

[...] [...] [...] [...] [...]

5722SS1 V5R4M0 060210 -Job Log- S1015362 09/09/15 09:48:01 Page 198
Job name: DSP04 User: BSYPGMR4 Number: 737486
Job description: BCTL Library: BSYOBJ1
MSGID TYPE SEV DATE TIME
FROM PGM LIBRARY INST TO PGM LIBRARY INST
specified, and 2 logical access paths are stored on the media with
file ZMSSN1P in library ZMODLIB10X.
CPI6705 Information 00 09/09/15 09:10:31.975240
QTAERR QSYS 00EA QSRSVDEQ QSYS 04AF
Message . . . : 57 blocks processed for sequence 273, volume WEEKLY, on
device TAP35.
Cause . . . . : 57 blocks were processed for file label ZMODPTF20,
sequence 273 for volume WEEKLY loaded on device TAP35. The maximum
block size is 262144. The tape file was opened at 09/09/15 09:10:31
and closed at
09/09/15 09:10:31. The total time the file was open was 1 seconds. If
the device is a tape library the cartridge is *N and the resource is *N.
CPC3701 Completion 00 09/09/15 09:10:36.396448
QSRSLCP2 QSYS 0243 QMNSAVE QSYS 00D4
Message . . . : 22 objects saved from library V16UPGRADE.
Cause . . . . : -- 22 objects were saved. -- 0 spooled files were
saved. Data was saved on volumes WEEKLY sequence number 269 at
09/09/15 08:09:00. The save operation ended on volume WEEKLY. If
UPDHST(*YES) was specified, the save/restore history was updated
unless otherwise indicated by the previously listed messages.
CPC3701 Completion 00 09/09/15 09:10:36.396744
QSRSLCP2 QSYS 0243 QMNSAVE QSYS 00D4
Message . . . : 50 objects saved from library XTOOLS0714.
Cause . . . . : -- 50 objects were saved. -- 0 spooled files were
saved. Data was saved on volumes WEEKLY sequence number 270 at
09/09/15 08:09:00. The save operation ended on volume WEEKLY. If
UPDHST(*YES) was specified, the save/restore history was updated
unless otherwise indicated by the previously listed messages.
CPC3701 Completion 00 09/09/15 09:10:36.396960
QSRSLCP2 QSYS 0243 QMNSAVE QSYS 00D4
Message . . . : 729 objects saved from library ZMODLIB10.
Cause . . . . : -- 729 objects were saved. -- 0 spooled files were
saved. Data was saved on volumes WEEKLY sequence number 271 at
09/09/15 08:09:00. The save operation ended on volume WEEKLY. If
UPDHST(*YES) was specified, the save/restore history was updated
unless otherwise indicated by the previously listed messages.
CPC3701 Completion 00 09/09/15 09:10:36.397448
QSRSLCP2 QSYS 0243 QMNSAVE QSYS 00D4
Message . . . : 601 objects saved from library ZMODLIB10X.
Cause . . . . : -- 601 objects were saved. -- 0 spooled files were
saved. Data was saved on volumes WEEKLY sequence number 272 at
09/09/15 08:09:00. The save operation ended on volume WEEKLY. If
UPDHST(*YES) was specified, the save/restore history was updated
unless otherwise indicated by the previously listed messages.
CPC3701 Completion 00 09/09/15 09:10:36.397872
QSRSLCP2 QSYS 0243 QMNSAVE QSYS 00D4
Message . . . : 101 objects saved from library ZMODPTF20.
Cause . . . . : -- 101 objects were saved. -- 0 spooled files were
saved. Data was saved on volumes WEEKLY sequence number 273 at
09/09/15 08:09:00. The save operation ended on volume WEEKLY. If
UPDHST(*YES) was specified, the save/restore history was updated
unless otherwise indicated by the previously listed messages.
CPC3707 Completion 00 09/09/15 09:10:36.398496
QSRSLCP2 QSYS 0243 QMNSAVE QSYS 00D4
Message . . . : 236 libraries saved at 09/09/15 08:09:00.
Cause . . . . : The save operation ended on volume WEEKLY.
CPI6705 Information 00 09/09/15 09:11:13.349624
QTAERR QSYS 00EA QSRSVDEQ QSYS 04AF
Message . . . : 3858 blocks processed for sequence 274, volume WEEKLY,
on device TAP35.
Cause . . . . : 3858 blocks were processed for file label QDOC, sequence

5722SS1 V5R4M0 060210 -Job Log- S1015362 09/09/15 09:48:01 Page 199
Job name: DSP04 User: BSYPGMR4 Number: 737486
Job description: BCTL Library: BSYOBJ1
MSGID TYPE SEV DATE TIME
FROM PGM LIBRARY INST TO PGM LIBRARY INST
274 for volume WEEKLY loaded on device TAP35. The maximum block size
is 262144. The tape file was opened at 09/09/15 09:10:39 and closed at
09/09/15 09:11:13. The total time the file was open was 34 seconds. If
the device is a tape library the cartridge is *N and the resource is *N.
CPC9410 Completion 00 09/09/15 09:11:16.935928
QOJSVCPR QSYS 080D QMNSAVE QSYS 0114
Message . . . : 7579 document library objects saved.
Cause . . . . : 7579 objects were saved on volumes WEEKLY starting with
sequence number 274 and ending with sequence number 274 at 09/09/15
09:10:36. The save request ended on volume WEEKLY on device TAP35. --
68 folders were saved. -- 7506 documents were saved. -- 5
distributions were saved.
CPI6705 Information 00 09/09/15 09:37:12.510728
QTAERR QSYS 00EA QSRGENSE QSYS *STMT
To module . . : QSRUFCB
To procedure : qsrFeovDevUfcb__FP9qsrFileCb
Statement . . : 18
Message . . . : 173936 blocks processed for sequence 275, volume
WEEKLY, on device TAP35.
Cause . . . . : 173936 blocks were processed for file label
SAV20150909, sequence 275 for volume WEEKLY loaded on device TAP35.
The maximum block size is 262144. The tape file was opened at 09/09/15
09:11:21 and closed at 09/09/15 09:37:10. The total time the file was
open was 1550 seconds. If the device is a tape library the cartridge
is *N and the resource is *N.
CPA4088 Sender copy 99 09/09/15 09:40:14.278424
QTAERR QSYS 0129 QTAERR QSYS 0129
Message . . . : Load next tape volume on device TAP35. (C G)
Cause . . . . : The end of the tape volume has been reached.
Recovery . . : Type C to cancel processing, or put the next tape
volume on device TAP35 and type G to continue processing. Possible
choices for replying to Message . . . :
G -- Continue processing. C -- Cancel processing.
*NONE Reply 09/09/15 09:42:38.280704
QMHDSMSS QSYS 0B22 QTAERR QSYS 0129
Message . . . : G
MCH1668 Escape 40 09/09/15 09:42:38.313264
#cfdamst 000A5C QTAVOPEN QSYS 11E4
Message . . . : System object TAP35 partially damaged. Internal dump ID
. Error class 0, device number X'0000'.
Cause . . . . : This partially damaged system object TAP35 has an error
class 0 and a device number X'0000'. Error class indicates how damage
was
detected: 0000-previously marked damage; 0001-detected abnormal
condition; 0002-logically invalid device sector; 0003-device error.
For error class 0003, the device number identifies the failing device,
or contains zero if main storage is damaged.
CPF8105 Escape 40 09/09/15 09:42:38.346768
QRCPDMGN QSYS 00C5 QTAVOPEN QSYS 11E4
Message . . . : Device description TAP35 damaged.
Cause . . . . : Device description TAP35 has Partial damage and may no
longer be usable. The VLOG dump identifier is *NONE.
Recovery . . : 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

5722SS1 V5R4M0 060210 -Job Log- S1015362 09/09/15 09:48:01 Page 200
Job name: DSP04 User: BSYPGMR4 Number: 737486
Job description: BCTL Library: BSYOBJ1
MSGID TYPE SEV DATE TIME
FROM PGM LIBRARY INST TO PGM LIBRARY INST
to be deleted and created again. If the damaged device description is
the console, the system may need to be powered down (PWRDWNSYS
command). If the system is powered down, do an initial program load (IPL) of the system.
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.
CPF9999 Escape 40 09/09/15 09:42:38.346912
QMHUNMSG *N QTAFEOV QSYS 00D3
Message . . . : Function check. CPF8105 unmonitored by QTAVOPEN at
Statement *N, instruction X'11E4'.
Cause . . . . : An escape exception message was sent to a program which
did not monitor for that message. The full name of the program to
which the unmonitored message was sent is QTAVOPEN . At the time the
message was sent the program was stopped at higher level language
statement number(s) *N. If more than one statement number is shown,
the program was a bound program. Optimization does not allow a single
statement number to be determined. If *N is shown as a value, it means
the actual value was not available.
Recovery . . . : See the low level messages previously listed to
locate the cause of the function check. Correct any errors, and then
try the request again.
CPF5257 Diagnostic 70 09/09/15 09:42:38.370872
QTAERR QSYS 00EA QMNSAVE QSYS 0187
Message . . . : Failure for device or member TAP35 file QSYSTAP in
library QSYS.
Cause . . . . : An error occurred during a read or write operation. If
this is a display file, the display may not be usable.
Recovery . . . : See the previously listed messages, correct the
errors, and try the request again. If the problem continues, report
the problem (ANZPRB command).
MCH1668 Escape 40 09/09/15 09:42:39.807032
#cfdamst 000A5C QTACLOSE QSYS 04D7
Message . . . : System object TAP35 partially damaged. Internal dump ID
. Error class 0, device number X'0000'.
Cause . . . . : This partially damaged system object TAP35 has an error
class 0 and a device number X'0000'. Error class indicates how damage
was
detected: 0000-previously marked damage; 0001-detected abnormal
condition; 0002-logically invalid device sector; 0003-device error.
For error class 0003, the device number identifies the failing device,
or contains zero if main storage is damaged.
CPF3794 Escape 30 09/09/15 09:42:38.379680
QSRGENSE QSYS *STMT QMNSAVE QSYS 0187
From user . . : QSECOFR
From module . : QSRUFCB
From procedure: qsrHandleUFCB_Exceptions__FP21_INTRPT_Hndlr_Parms_T
Statement . . : 90
Message . . . : Save or restore operation ended unsuccessfully.
Cause . . . . : The save or restore operation has ended unsuccessfully
because a data management error has occurred.
Recovery . . : Press F10 or use the Display Job Log (DSPJOBLOG)
command to see the previously listed message CPF5257. Message CPF5257
may refer to override commands, but overrides do not apply to a save
or restore operation. Correct any errors and try the request again.
If the error occurred when the *ALLUSR, *IBM, or *NONSYS value was
specified on the LIB parameter on a Save Library (SAVLIB)

5722SS1 V5R4M0 060210 -Job Log-S1015362 09/09/15 09:48:01 Page 201
Job name: DSP04 User: BSYPGMR4 Number: 737486
Job description: BCTL Library: BSYOBJ1
MSGID TYPE SEV DATE TIME
FROM PGM LIBRARY INST TO PGM LIBRARY INST
command, you can specify a value for the STRLIB parameter on the
SAVLIB command to save the remaining libraries. If the error occurred
when the *ALLUSR, *IBM, or *NONSYS value was specified on the SAVLIB
parameter on a Restore Library (RSTLIB) command, you can specify a
value for the STRLIB parameter on the RSTLIB command to restore the remaining libraries.
CPF0902 Completion 00 09/09/15 09:42:40.386024
QWCCSUUC QSYS 0212 QMNSRBND QSYS 03C3
Message . . . : Subsystem BCTL in library BSYOBJ1 being started.
CPF0902 Completion 00 09/09/15 09:42:40.454312
QWCCSUUC QSYS 0212 QWCCSUUC QSYS 038B
Message . . . : Subsystem QSYSWRK in library QSYS being started.
CPF2361 Diagnostic 20 09/09/15 09:42:40.559328
QMNSRBND QSYS 040F QUIMNDRV QSYS 060C
Message . . . : Error occurred with the option.
Cause . . . . : An error occurred while you were trying to run one of
the following: -- Save entire system. -- Save system data only. --
Save all user data. -- Create a distribution tape. -- Display log for
messages. -- Restore system and user data. -- Restore system data
only. -- Restore all user data. -- Power off the system.
Recovery . . . : Press F10 (Display messages in job log) or display the
job log (DSPJOBLOG command). Correct the error and try the request again.
*NONE Request 09/09/15 09:47:42.141304
QPTCHECK *N QUICMD QSYS 0461
Message . . . : -DSPJOBLOG OUTPUT(*PRINT)

--
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,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.

--
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,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.