G06.26 ReadMe

o FUP (T6553)
Solution 10-041123-2122
FUP displays TYPE 0, LENGTH 0 for the primary key columns of a SQLMX
table. These values are default values since such information is not
stored in the object label.
Recovery
None.
Workaround
The information can be obtained from the SQLMX Metadata using the
column number of the primary key columns.
o INSPECT (T9673)
Solution 10-031031-0977
When attempting to open a number of large SAVEABEND files using the
ADD PROGRAM capability, INSPECT may abend trying to load the second
or third SAVEABEND file. A stack trace is produced.
Recovery
Close and exit INSPECT and restart the debugging session.
Workaround
Analyze one SAVEABEND file at a time.
o Labeled Tape (T6958)
Solution 10-050112-0220
To avoid all tapes in a rack be unloaded automatically, resulting in
a pending mount request, a multi-tape OSS backup command must be
issued in such a way that it starts within a tape that already has a
tape file. An Append capable pool should be used and a single tape
OSS backup job should follow.
Recovery
None.
Workaround
Use tapes with a status of "SCRATCH" instead of as "ASSIGNED."
o Mediacom (T6027)
Solution 10-040919-9925
Under the following conditions:
1. There is no local VOLCAT in the system.
2. Either there are no local FILECATs or the version of all local
FILECATs are recognized.
The MEDIACOM ALTER MEDIADB,LONGNAME command results in
**ERROR-6007** Call to MEDIADBM failed with file system error 201.
Also, generate three save abend files may be generated.
Recovery
Page
2
of
10