Q:
ABSTRACT: Using PSF/AIX tape support to unload MVS fonts.
SEARCH ARG: psf/aix tape
TOPIC THREAD: PRINT
PSF/AIX
..
I have read items RTA000101832 and RTA000090151 regarding tape support
under PSF/AIX and I have a question. I understand that I should be able
to read files that have been unloaded from MVS using IEBCOPY into the
AIX file system, such as AFP resources.
My customer got a tape from IBM which contains the Century Schoolbook
font set. On this tape there is a set of fonts for MVS which are in
IEBCOPY unloaded format. The customer used the PSF/AIX smit panels to
try and read the resources into PSF/AIX. PSF/AIX recognizes that the
tape contains IEBCOPY format but it tells the customer that the block
size is incorrect.
Any ideas or thoughts on where to go from here? The customer does have a
3480 tape drive attached to their RISC system. They do not have an MVS
system to unload the tape. Thanks for the help.
A:
Here is information concerning unloading customer-ordered tapes
containing IBM font collections. These collections violate some of the
assumptions that were originally made when designing the PSF/AIX utility
to unload resource libraries from tape.
All the below *can* be done with smit panels if you want but could
produce error messages that could be misleading, so I'll give you the
steps to unload the resources manually.
ASSUMPTIONS:
1) Tape is inserted in device /dev/rmt1.
2) Customer wants to unload resources into /var/psf/tmp/reslib_tape,
which is a directory which the userid can write (should be root)
and in which there are no like-named resources (preferably an empty
directory).
3) The directory /usr/lpp/psf/bin is in the userid's PATH. If not,
prepend the /usr/lpp/psf/bin on the front of the t2file and tlist
commands.
STEPS:
1) List the file(s) on the tape:
tlist -t rmt1.1
Explanation: The tape should consist of three logical files. Since
it's a IBM Standard Labeled tape, each file has a header, data, and
trailer physical file. The three files are:
a) SMP file (we don't care about)
b) The PDS to unload
c) Sample JCL (for unloading under MVS)
(If there are multiple PDS datasets, see final note below.)
2) Rewind the tape:
tctl -f /dev/rmt1.1 rewind 0
Explanation: Rewind the tape to the start to assure the correct
positioning.
3) Forwardspace three tape marks to position the tape to the header
file for the PDS dataset:
tctl -f /dev/rmt1.1 fsf 3
Explanation: The SMP dataset is not valid, nor do we care about it,
so we must position the tape past that logical file (three physical
files). The important parts of this command are fsf (forward skip
file) and 3 (number of file marks to skip). Using this command,
you can select the correct location to start processing.
4) Unload the PDS file:
t2file -t rmt1 -d /var/psf/tmp/reslib_tape -s
Explanation: Request that one file (beginning at the current tape
location) be unloaded into the directory /var/psf/tmp/reslib_tape.
The -s tells the utility that it should process only one logical file.
The resources contained in this second logical file (on the tape)
will be unloaded into the correct directory.
Note: If there are multiple resource PDS files on the tape, you can
re-issue the t2file command again, possibly pointing to a different
destination directory. Unloading to the same directory works as well
(assuming that there are no like-named members). You could also,
after positioning the tape to the header file for the first PDS, omit
the -s parameter and the utility will unload all remaining PDS
datasets until an error occurs (which it will since a non-PDS JCL
dataset is on the tape). The problem(s) with unloading multiple
datasets this way with an error is that it's not made clear on which
file the problem occurred, so you'll need to check that all resources
were unloaded correctly. You also do not have the option to unload
resources in separate directories.
I hope that helps.
S e a r c h - k e y w o r d s:
PSF/6000 PSF AIX tape iebcopy block size blocksize unloaded MVS
3480 unload tctl t2file tlist psf/aix
WWQA: ITEM: RTA000106441 ITEM: RTA000106441
Dated: 06/1998 Category: XPSF6000
This HTML file was generated 99/06/24~12:43:34
Comments or suggestions?
Contact us