1 Preface

As of BS2000/OSD-BC V1.0, 3591 Magnetic Tape Cartridge Units can be operated as

emulations of 3590E devices of the internal device type C4 with magnetic tape cartridges
(MTCs) of volume type TAPE-C4. (In certain interface elements in this manual the German
abbreviation MBK has been used for magnetic tape cartridge.) This operating mode is
referred to below as C4 mode of the 3591 device, or C4 mode for short.
As of BS2000/OSD-BC V2.0, 3591 devices can be used in the original as devices of type
3591 with the internal device type C5 and MTCs of volume type TAPE-C5. This operating
mode is referred to below as C5 mode of the 3591 device, or C5 mode for short.
In this C5 mode, all functions and advantages of the 3591 devices can be used. These
include above all the full functionality of the stacker in all operating modes:

MANUAL mode (manual individual operation)

AUTOMATIC mode (automatic processing of the next tape)
SYSTEM mode (system-controlled processing of the next tape)
RANDOM mode (system-controlled processing of any tape)

RANDOM mode, which allows random access to all ten possible cartridges in the stacker,
can only be used if the device is generated as type C5 in BS2000/OSD.
Even when small block sizes are used in an application (e.g. 2 Kbytes or less), the full tape
capacity of the C5 device is used (up to 30 Gbytes compressed). Applications such as
ARCHIVE, which work with large blocks, always use the full tape capacity anyway.

U25751-J-Z125-1-7600

Target group

Preface

1.1 Target group

This Migration Guide is intended for users with a knowledge of system administration who
already use 3591 devices in C4 mode and wish to convert them to C5 mode in order to
exploit the full functionality of the devices.
The manual explains what you need to do to convert to 3591-C5 mode and what to look out
for when using it. Which version of BS2000/OSD you are using is important in this context.
Users with BS2000/OSD-BC V1.0
Users who still work with BS2000/OSD-BC V1.0 but want to upgrade to V2.0 or V3.0 and
already work with 3591 devices in C4 mode can now generate the magnetic tape devices
as type C5 when they switch their BS2000/OSD version.
These users are one of the target groups of this manual.
This Migration Guide does not concern users who work with BS2000/OSD-BC V1.0 and do
not want to upgrade to V2.0 or V3.0. They can still use 3591 devices in C4 mode only.
Users with BS2000/OSD-BC V2.0 and higher
Users with BS2000/OSD V2.0 or higher who have already used 3591 devices in C4 mode
should now install the devices as type C5 to avoid a more time-consuming conversion
process later.
These users are also a target group of this manual.

This Migration Guide affects only the administration of the 3591 devices and the
128-track cartridges to be processed on these devices.
As of BS2000/OSD-BC V2.0, 3591 devices should now only be generated as type
C5. Although 3591 devices can be operated side by side in the original in C5 mode
and as an emulation in C4 mode, for reasons of clarity this is not recommended.

U25751-J-Z125-1-7600

Preface

Summary of contents

1.2 Summary of contents

This manual describes all requirements and measures that are necessary for migrating the
3591 devices from type C4 to type C5:

hardware and software requirements,

technical and administrative measures,

conversion measures in affected catalogs and directory files, and

any other modifications.

This information is followed by an introduction to the specific tools that can be used for
carrying out these measures.
To understand this manual, you will need to be familiar with BS2000/OSD device
management and generation, MTC devices, volume types and volume management. You
will find information on these topics in the following manuals:

Introductory Guide to Systems Support (BS2000/OSD-BC) [1]

System Installation (BS2000/OSD-BC) [2]
SINIX-2000 [3]
ROBAR [4]
MAREN [5]
TLS [6]

README file on migration tools

Information on any functional changes and additions to the current product version of the
migration tools described in chapter 6 can be found in the product-specific README file.
You will find the README file on your BS2000 computer under the file name
SYSRME.product.version.language. The user ID under which the README file is cataloged
can be obtained from your systems support staff. You can view the README file using the
SHOW-FILE command or an editor, and print it out on a standard printer using the following
command:
/PRINT-DOCUMENT filename, LINE-SPACING=*BY-EBCDIC-CONTROL

With SPOOL versions earlier than V3.0A:

/PRINT-FILE FILE-NAME=filename,LAYOUT-CONTROL=
*PARAMETERS(CONTROL-*CHARACTERS=EBCDIC)

U25751-J-Z125-1-7600

Notational conventions

Preface

1.3 Notational conventions

Indicates a warning note

Indicates important information to be read

Name

This font is used for names of functions, menus, windows, fields and messages
in the body of the text

[KEY]

Symbolizes a function key for operating the sysadm menu

(see Operating the FMLI interfaces in SINIX-2000 [3]).

References to other publications are represented in the text by the abbreviated title followed
by a number in square brackets.
The full title of each document referred to can be found in the list of related publications at
the back of this manual.

U25751-J-Z125-1-7600

2 Affected hardware

2.1 3970-KAx Channel Adapter

3970-KAx Channel Adapters are used to connect 3591 MTC devices to a BS2000 host with
channel type 2 or S.
The User Guide SINIX-2000, Installation, Operation and Administration [3] describes in
detail how devices which are connected to BS2000/OSD via channel adapters are configured. For a brief description of the TAPE-C5 device configuration, see chapter Configuring C5 devices on the 3970-KAx Channel Adapter on page 9ff in the present manual.

2.2 Standalone devices

From the point of view of the operating system and the application, the 3591 devices can
be operated in two modes:

3591-C4 mode: device type 3590E (internal C4), volume type TAPE-C4
As of BS2000/OSD-BC V1.0, 3591 devices can be operated in compatible mode as devices
of type 3590E (internal code C4) and of volume type TAPE-C4. 3591-C4 mode, or C4 mode
for short, means that the device on the user interface appears as a 3590E device, but physically a 128-track volume is processed. In C4 mode, the operating modes MANUAL,
AUTOMATIC and SYSTEM are available.

U25751-J-Z125-1-7600

3594 Tape Library System

Affected hardware

3591-C5 mode: device type 3591 (internal C5), volume type TAPE-C5
As of BS2000/OSD-BC V2.0, 3591 devices can be operated in the original mode as MTC
devices of type 3591 (internal C5) and with volume type TAPE-C5.
In C5 mode the operating modes MANUAL, SYSTEM, AUTOMATIC and RANDOM are
available.
The full functionality of the stacker, especially the random access to cartridges in the
stacker (RANDOM mode), is only available during operation in C5 mode.

2.3 3594 Tape Library System

If the MTC drive 3591-B1A is to work in native mode with 128-track volumes, it is supplied
with the 3594 Tape Library System exclusively as a device of type C5. In other words,
migration is not necessary.
The MTC drive 3591-B1A does not have a stacker.
When the Virtual Tape Server (VTS) is used, the 3591 MTC drives it contains are not
operated in native mode as 128-track drives; instead, the capacity of the volumes is divided
up so that several C4 volumes exist virtually. The MTC drives are also made virtual. In
BS2000/OSD these virtual drives always appear as C4 drives with C4 volumes with a
maximum capacity of 800 Mbytes (virtual 36-track volumes).
Migration to C5 is pointless in this case.

2.4 ABBA archive system

In ROBAR Version 2.7A and below, the MTC drive 3591-B1GL, which is installed in ABBA
archive systems, works in C4 mode only. In mixed configurations with 3590E (36-track
devices), 3591 and 3590E require separate locations and therefore two ROBAR installations.
As of ROBAR V3.0A, the MTC drive 3591-B1GL is supported as a TAPE-C5 drive. All 3591
devices and volumes must be defined or converted for C5 mode. All accompanying 3591
drives must be entered in the ROBAR configuration file as TAPE-C5 drives.
ROBAR V3.0A is scheduled for May 1998. The MTC drive 3591-B1GL has no stacker.

U25751-J-Z125-1-7600

3 Comparison of the software configuration

As of BS2000/OSD-BC V1.0, the use of 3591 MTC Units is subject to restrictions which no
longer apply as of BS2000/OSD-BC V2.0. The following sections show the resulting differences between the software configurations for BS2000/OSD-BC V1.0 and for BS2000/
OSD-BC V2.0 or higher.

3.1 BS2000/OSD-BC V1.0

This is the first BS2000/OSD version in which 3591 MTC Units are supported.
Operation in C4 mode only
For 3591 no separate device type and no separate volume type are available in BS2000/
OSD-BC V1.0. The device is therefore operated in 3591-C4 mode, i.e. with the same
hardware/software interface as the 3590E devices, with the internal device type C4 and the
volume type TAPE-C4.
The 128-track cartridges written to on this device are entered in the catalogs (TSOSCAT,
MARENCAT) and in the ARCHIVE directory as volume type TAPE-C4.
Device selection via separate locations for 3591 and 3590E
If drives of types 3591 and 3590E are used together, when a volume is requested the
correct device can only be selected via the location. This is not possible without the use of
MAREN. The location of a volume is entered in the MAREN catalog.
Using the location, which NDM determines from MAREN when a volume is requested, NDM
can select the appropriate device if 36-track and 128-track devices are assigned to different
locations (ADD/REMOVE-DEVICE-DEPOT command). This procedure is the same as the
one applied when several robots and the same devices are used, where the correct devices
are also determined via the location.
As of ARCHIVE V3.5, a new parameter, LOCATION, has been added to the existing
DEVICE-TYPE parameter. With it you can specify explicitly whether a 36-track device
(3590E) or a 128-track device (3591) is to be used.
The new LOCATION parameter has also been added to HSMS as of V4.0.
U25751-J-Z125-1-7600

BS2000/OSD-BC V2.0 and higher

Comparison of the software configuration

In BS2000 (FILE processing) there is no equivalent option.

It is not always possible to specify the type of the tape to be written to (e.g. scratch tapes).
Implicit selection of the location can also be programmed by means of MAREN exits. The
MAREN component MARENLM offers standard exits which can be used to implicitly route
a scratch request to a location in accordance with specified criteria (job name, user ID).
Sequential access to the stacker
In BS2000/OSD-BC V1.0 the stacker can only be accessed sequentially, because
RANDOM mode (see page 1) is not yet supported.

3.2 BS2000/OSD-BC V2.0 and higher

Operation in C5 mode
For 3591, a separate device type (internal C5) and the volume type TAPE-C5 are available
as of BS2000/OSD-BC V2.0. The device is operated in 3591-C5 mode (original mode). In
the case of system generation with UGEN, 3591 devices can be generated with the internal
device type C5.
Device selection via the volume type
If 3590E and 3591 devices are used simultaneously and the 3591 devices are generated
with the new type C5, the device management NDM can, in contrast to BS2000/OSD-BC
V1.0, find the correct device by specifying the volume type TAPE-C4 or TAPE-C5 in the
device selection process.
Scratch requests for 36-track and 128-track cartridges can be clearly distinguished by
specification of the volume type. The default volume type set for MAREN need no longer be
used for this.
MAREN only remains necessary for distinguishing between 3591 and 3590E devices if
devices of the same type are in different locations (e.g. if several robots are in use). If
MAREN is to be removed, this must not happen until after the conversion from 3591-C4 to
3591-C5, because the C4/C5 migration tool works with the information stored in the
MAREN catalog (see chapter C4/C5 migration tool on page 21ff).
In view of the many advantages for volume management, however, removing MAREN is not
advisable.
Random access to the stacker
The functionality of RANDOM mode permits random access to the stacker.
8

U25751-J-Z125-1-7600

4 Configuring C5 devices on the 3970-KAx

Channel Adapter
The BS2000 devices and the channel interface are configured in SINIX mode under the
sysadm ID.
The procedure is as follows:
1. Delete all 3591 devices which are configured as TAPE-C4
(see Delete tape device on page 12).
2. Change the type of these devices under sysadm/Sinix_2000/chad from mbk6 to
mbk7 (see section Channel interface (chad) on page 13).
3. Regenerate the 3591 devices as TAPE-C5 devices
(see Generate new tape device on page 11).
How to use the sysadm menu is described in Operating the FMLI interfaces in the SINIX2000 manual ([3], ).

4.1 BS2000 devices

Below you will see only the section of the sysadm menu tree that is of relevance for configuring the tape devices.
The entries in figure 1 have the following format:

Menu name: menu item to be selected

The numbered symbols through refer to the forms which are explained after the
diagrams with regard to the TAPE-C5 devices.

U25751-J-Z125-1-7600

sysadm menu section

Configuring C5 devices on the 3970-KAx Channel Adapter

UNIX System V/386 Operations, Administration and Maintenance:

sinix_2000 - System Administration SINIX-2000
System Administration SINIX-2000: bs2000_devices - Configuration of BS2000 Devices
BS2000 Device Configuration: Host-Connector - Select by Host Connector
Select by Host Connector: Host Connector x - aaaa Board
Unit Host Connector x: yy - none
Host Connector x Unit yy: New - Make new device
Device Type Host Connector: x Unit: yy: Tape

Unit Host Connector x: yy - Tape <0/1 mnemonic event ID>

Host Connector x Unit yy: Change - Change device

Host Connector x Unit yy: Delete - Delete device

Host Connector x Unit yy: Show - Show device

BS2000 Device Configuration: Device - Select by Device Type

Device Type: Tape
Device Type: Tape: x_yy - Tape <0/1 mnemonic event ID>

x:
yy:
aaaa:
0/1:
Mnemonic:
Event ID:

Host Connector x Unit yy: Change - Change device

Host Connector x Unit yy: Delete - Delete device

Host Connector x Unit yy: Show - Show device

Host connector number

Unit number
Connection type (letters)
Emulation not active (0) or active (1)
Mnemonic of the emulation
Event ID of the emulation
(see also SINIX-2000 [3])

Figure 1: Section of the sysadm menu tree for the configuration of tape devices

10

U25751-J-Z125-1-7600

Configuring C5 devices on the 3970-KAx Channel Adapter

Generate new tape device

Generate new tape device

Each 3591 device to be migrated must be generated in the BS2000 device configuration as
a new TAPE-C5 tape device.
Before the regeneration, however, the channel interface must first be configured via the
chad menu (see section Channel interface (chad) on page 13).
When you select the menu item Tape, a form will be displayed which, after selection of a
TAPE-C5 device, could look like this:
8

Tape

Host Connector:0 Unit: 2

Device:
Mnemonic:
Device Number:
Event ID:
Sense ID:

TAPE-C5 ( C5 MBK ACF )

SINIX Device:

/dev/rmt/mbk9t2hs

active:

CNTAPE

FF359000359011

YES

The input fields can be selected with the cursor keys.

In the underscored section of the selection field Device:, set the connected TAPE-C5
device using the function key [CHOICES].

The selection list shows only those devices which are currently connected and
addressable. The devices are generally connected and preconfigured by the
service department.

The following types of TAPE-C5 device can appear in the selection list:
Device

Selection Meaning

TAPE-C5 (C5 MBK)

NTTAPE0

TAPE-C5 (C5 MBK ACF)

NTTAPEA Standalone device with stacker

TAPE-C5 (C5 MBK in 3594)

CNTAPE

Standalone device
In the 3594 Tape Library System

The meaning and selection options of the remaining form fields are described in the SINIX2000 manual [3].

U25751-J-Z125-1-7600

11

Modify / delete / show device

Configuring C5 devices on the 3970-KAx Channel Adapter

Modify tape device

Modifying an already configured TAPE-C4 device is not recommended, as the channel

interface must be reconfigured beforehand via the chad menu. However, this is only
possible without problems if the tape device has previously been deleted from the configuration.

Delete tape device

An existing 3591 device that was already configured as a TAPE-C4 device should be
deleted with Delete - Delete device and regenerated as a TAPE-C5 device (see ).
Before the regeneration, however, the channel interface must first be configured via the
chad menu (see section Channel interface (chad) on page 13).

Show tape device

The menu item Show - Show device opens a form which is identical in structure to the
one under and contains the configuration data of the previously selected tape device.
You cannot make any changes in this form.

12

U25751-J-Z125-1-7600

Configuring C5 devices on the 3970-KAx Channel Adapter

Channel interface (chad)

4.2 Channel interface (chad)

The menu item chad is used to configure the channel modules ECIC and EBEC, with which
the 3970-KAx Channel Adapter operates the BS2000 channel interfaces.
The menu item chad is for use by the service department only.

In the form Configuration of host connector x the hardware/software interface for

the tape device must be modified (see figure 2).
UNIX System V/386 Operations, Administration and Maintenance:
Sinix_2000 - System Administration SINIX-2000
System Administration SINIX-2000: chad - ECIC / EBEC Board Configuration
Host Connector Board Configuration: Configure - Configure Host Connector Board
Configure Host Connector: Host Connector x
Configuration Host Connector Board x: HSI:

select
mbk7

Figure 2: Section of the sysadm menu for setting the device type during chad configuration

Select mbk7 from the selection field HSI:.

The meaning and selection options of the remaining form fields as well as possible error
messages are described in the SINIX-2000 manual [3].

U25751-J-Z125-1-7600

13

Eine Dokuschablone von Frank Flachenecker

by f.f. 1992

5 Software modifications and measures

This section is only relevant for users who want to access 3591devices exclusively from
BS2000/OSD V2.0 and higher.
In BS2000/OSD-BC V1.0 and lower, it is only possible to operate the 128-track MTC Unit
in C4 mode (device type 3590E (internal C4) and volume type TAPE-C4). Tools and
BS2000 directories contain these type designations.
Migration is necessary if all existing 128-track cartridges are to be used in future as volumes
of type TAPE-C5.

In mixed operation of BS2000/OSD-BC V1.0 and versions > 1.0 (e.g. with VM2000),
the 3591 MTC Unit must continue to be operated in C4 mode if it is still to be
accessed from BS2000/OSD-BC V1.0.

5.1 Usage scenarios

Using 3591 devices for the first time
System installation as of BS2000/OSD-BC V2.0
If 3591 devices are being used for the first time, they should be operated exclusively in C5
mode. They must be generated with the internal device type C5 (see the description of the
DVC statement and the table of device type codes in the System Installation manual [2]).
This avoids the need for migration and the volume types do not need to be converted into
catalogs (see below).
Mixed configuration: BS2000/OSD-BC V1.0 and higher
It is recommended that you upgrade all systems to BS2000/OSD-BC V2.0 and higher in
order to avoid the potential problems attendant on migration.

U25751-J-Z125-1-7600

15

Usage scenarios

Software modifications and measures

3591 devices already in use, but no conversion desired

If 3591 devices are already being used in C4 mode, the applications have been modified to
reflect the current location, and no change to the configuration and the operating system
version is planned, a conversion is generally not necessary. The generation can be
retained; no further actions are necessary. This also applies if the BS2000/OSD version is
changed.
The conditions for the use of 3591 devices in C4 mode remain unchanged:

In the case of mixed configurations with 3590E devices, MAREN is necessary for
managing the locations.

Users with volumes of types TAPE-C1 and TAPE-C2 and running only C4 devices
(3590E and 3591 in C4 mode) must ensure that TAPE-C1 and TAPE-C2 read requests
only run on 3590E devices. The devices must be selected via their location.

If scratch tapes are requested, the user is committed to the default volume type defined
with MAREN.

3591 devices already in use, conversion desired

If you want to convert to 3591-C5 mode, you must perform the measures described in the
following section.

16

U25751-J-Z125-1-7600

Software modifications and measures

Migration measures

5.2 Migration measures

You are strongly advised to perform the migration for all devices and volumes which may be
affected. In the following it is assumed that this is the aim.
Initial conditions
One of the places the volume type of a tape is stored is in the MAREN catalog. If a MAREN
system manages the volumes of different BS2000 systems, a particular volume must have
the same type in all BS2000 systems. Because of the relationship between volume type and
device type, the 3591 devices must be generated the same in all BS2000 systems, i.e. 3591
either always with the internal device type C5 or always with the internal device type C4. If
one of the BS2000 systems has a version earlier than OSD V2.0, the 3591 devices can only
be operated in C4 mode.
The measures described in the following must all be performed in the order given if
migration is necessary, i.e. if any of the following conditions apply:

only BS2000/OSD versions as of V2.0 are used

3591 devices are already in use in C4 mode and are to be used in 3591-C5 mode

one location in the MAREN catalog contains all 128-track MTCs to be converted from
volume type TAPE-C4 to volume type TAPE-C5 and no other MTCs (e.g. 36-track
MTCs).

When the tapes are written to, it is assumed that the location assignment of the tape
devices and volumes remains unchanged. The specifications of the ADD-DEVICE-DEPOT
command in the RUN file can be retained.
All measures must be performed before tape processing begins, i.e. before the ATTACHDEVICE for the first tape device.

5.2.1 BS2000 generation (UGEN)

If a device is to be operated as a 3591, XC5 must be assigned as its device type code in
the DVC statement (UGEN) (see the description of the DVC statement and the table of
device type codes in the System Installation manual [2]). BS2000 must then be restarted.
This measure is also necessary when a 3591 is used for the first time.

U25751-J-Z125-1-7600

17

Migration measures

Software modifications and measures

5.2.2 Activating the 3591 emulation on all channel adapters

The following measures must also be taken the first time 3591 is used.
In the sysadm menu of the 3970-KAx Channel Adapter you must delete all 3591 devices
which are configured as TAPE-C4 (see Delete tape device on page 12.
You must then change the type of these devices under sysadm/Sinix_2000/chad from
mbk6 to mbk7 (see section Channel interface (chad) on page 13).
Then you must regenerate the 3591 devices as TAPE-C5 devices (see Generate new tape
device on page 11).

5.2.3 Changing the volume type in data structures

In all catalogs in which 128-track MTCs with volume type TAPE-C4 are registered, the
volume type must be changed to TAPE-C5. TAPE-C4 entries for 36-track MTCs must not
be changed.
The following are affected:

the MAREN catalog MARENCAT

the DMS file catalog TSOSCAT of the tape files

ARCHIVE directory files

TSOSCAT entries of the migrated files

The C4/C5 migration tool is available for conversion of the catalogs (see page 21ff).

5.2.4 Activating the ROBAR rule files for 3591

As of ROBAR V2.7B (provisionally available from January 1998), there are new ROBAR
rule files (RRF) for supporting the 3591 devices in C5 mode. This always requires two
ROBAR installations.
As of ROBAR V3.0A, only one ROBAR installation is necessary for mixed configurations
with 3590E/3588 devices (TAPE-C4) and 3591 devices (TAPE-C5). In the ROBAR configuration file the 3591 devices can be entered as TAPE-C5 drives. This entry refers to the RRF
for 3591 as a C5 device.
If 3591 devices are to continue being operated in C4 mode, two ROBAR installations are
also necessary with ROBAR V3.0A, so that the separate locations for 3591-C4 devices and
all other devices can be served.

18

U25751-J-Z125-1-7600

Software modifications and measures

Migration measures

5.2.5 Setting up a free tape pool with TAPE-C5 volumes

The migration of the MAREN free tape pool from TAPE-C4 to TAPE-C5 occurs together with
the migration of the MAREN catalog. The VSNs of the TAPE-C4 locations which are to be
migrated to TAPE-C5 are changed to TAPE-C5 regardless of their status in MAREN (free
or reserved).

5.2.6 Changes to user procedures

All user procedures which explicitly contain the volume type TAPE-C4 for 128-track MTCs
must be modified. The following commands could be among those affected:
CREATE-FILE(-GENERATION)
CREATE-TAPE-SET
EXTEND-TAPE-SET
IMPORT-FILE
MODIFY-FILE-ATTRIBUTES
MODIFY-FILE-GENERATION-SUPPORT
SHOW-DEVICE-STATUS
WRITE-SPOOL-TAPE
SECURE-RESOURCE-ALLOCATION
START-TAPE-OUTPUT
For ARCHIVE applications the type specification must be changed to *BY-VOLUMECATALOG.

5.2.7 Changes to MAREN exits and the MARENLM reservation file

The MAREN exits which use the device type as a criterion are affected. You must ensure
that the MARENLM reservation file does not contain the volume type TAPE-C4 for 128-track
MTCs. If this is in fact the case, the volume type must be changed to TAPE-C5 with the help
of MARENLM.

5.2.8 Changes to the TPM configuration

The Tape Pool Manager PROP-TPM must regenerate its configuration. The table of tape
devices in the OPZTPMD macro must be modified (TYP parameter).
The device type TAPE-C5 is only supported as of PROP-TPM V2.2B (provisionally from
March 1998). 3591 devices defined as TAPE-C5 are defined in the PROP-TPM configuration with TYP=3591.
With PROP-TPM V2.2A and lower, 3591 devices with TYP=3590E (TAPE-C4) must be
generated with separate locations in the PROP-TPM configuration.
U25751-J-Z125-1-7600

19

Note on RANDOM mode

Software modifications and measures

5.3 Note on RANDOM mode

There are certain rules which you must comply with when using RANDOM mode, otherwise
unmanned operation, which in principle is possible with this device, cannot be guaranteed.
Possible conflict situations and restrictions on use of this mode are described in the manual
BS2000/OSD-BC V3.0, Introductory Guide to Systems Support [1] under the 3591 MTC
system.

20

U25751-J-Z125-1-7600

6 C4/C5 migration tool

At the same time as the upgrade from BS2000/OSD-BC V1.0 to V2.0 or higher, 3591 MTC
Units which were previously used in C4 mode should be converted to C5 mode.
To guarantee general consistency, the entries in MARENCAT, in the ARCHIVE directory
files and in TSOSCAT for 3591 volumes must be migrated from volume type TAPE-C4 to
TAPE-C5.
The entries to be migrated can be selected according to their location, because in BS2000/
OSD-BC V1.0 and below the 3591 devices were isolated in homogeneous locations.
MAREN is required in order to define the locations. If, for TAPE-C4 MTCs, only 3591
devices in C4 mode were used or operation was manual, this means that software configurations were possible without MAREN.
The following software configurations can occur:
1. MAREN and ARCHIVE
2. MAREN, ARCHIVE and HSMS
3. ARCHIVE without MAREN
4. ARCHIVE and HSMS without MAREN
5. MAREN without ARCHIVE
6. Neither MAREN nor ARCHIVE
MAREN should be installed on all systems on which 3591 devices are operated, as without
it manual intervention is necessary.
All 3591 volumes with the volume type TAPE-C4 in ARCHIVE directory files and in
TSOSCAT must be migrated to TAPE-C5. In addition, the block ID format in the ARCHIVE
directory files must be brought into line accordingly.
MARENCAT is migrated via PERCON. The migration of the ARCHIVE directory files and
TSOSCAT is performed using the MIGRATE-ARCHIVE-DIRECTORIES and MIGRATECATALOG-ENTRIES commands respectively. The TSOSCAT entries of the files that were
migrated by HSMS via ARCHIVE directories are also updated.

U25751-J-Z125-1-7600

21

C4/C5 migration tool

The following table shows which entries are or could be present in the catalogs and which
actions (procedures) are necessary as a result, depending on the software configurations
listed on page 21.
Software configuration
Migration of

Process

1.

2.

P1/P4

Entry in TSOSCAT

P2

(X)

(X)

(X)

ARCHIVE directory file

P3

Files migrated by HSMS

P3

Entry in MARENCAT

X
(X)
P1
P2
P3
P4

3.

4.

5.

6.

X
(X)

(X)

= Entry exists
= Entry may exist
= MAREN.C5-MIG procedure
= MIGRATE-CATALOG-ENTRIES command
= MIGRATE-ARCHIVE-DIRECTORIES command
= TAPEFILES.C5-MIG procedure (called automatically through P1)

The software configurations 3, 4 and 6 require manually created input files.

Standalone system
With a standalone system, migration is complete when the processes marked with X have
executed correctly according to the software configuration (see table above).
Multiuser system
In SPD mode the migration procedures must be executed on all systems in the network.
In RFA mode the conversion can be executed in one operation on one host if access to all
pubsets is possible with RFA (locally imported). The TSOSCAT of remote pubsets is not
migrated. The migration must be repeated for these pubsets - either on a host that works
with the same MARENCAT and has imported these pubsets locally - or after the nonmigrated pubsets on the first host have been locally imported.
If MAREN is present, the migration of MARENCAT must be performed first.

22

U25751-J-Z125-1-7600

C4/C5 migration tool

Overview of the C5 migrator

6.1 Overview of the C5 migrator

The tool for migrating TAPE-C4 to TAPE-C5 (C5 migrator) comprises a number of SDF-P
procedures and a privileged DSSM subsystem.
The P1 procedure (MAREN.C5-MIG) is intended for the migration of the MAREN catalog
and works together with PERCON. If the local MAREN parameter CID-UID is not specified
in the local MARENCP parameters, none of the file names in the MARENCAT contains the
catalog ID or the user ID.
The P4 procedure (TAPEFILES.C5-MIG) extracts the full file names of the tape files from
all pubsets which can be accessed. These file names are used for assigning the file names
of MARENCAT.
P4 is automatically called by the P1 procedure.
The TSOSCAT is migrated using the privileged command MIGRATE-CATALOG-ENTRIES
(P2). This command is executed in the P1 procedure.
The migration of the ARCHIVE directory files, and possibly of the TSOSCAT entries from
files which were migrated by HSMS to 3591 volumes, is performed using the privileged
command MIGRATE-ARCHIVE-DIRECTORIES (P3).
The MIGRATE-CATALOG-ENTRIES and MIGRATE-ARCHIVE-DIRECTORIES commands
are implemented in the TPR subsystem C5-MIG.
The components of the C5 migrator and how they interact are illustrated in figure 3 on
page 24.

U25751-J-Z125-1-7600

The C5 migration procedure for the conversion of MARENCAT uses the chargeable
software product PERCON. Users who do not have PERCON can use it for the
limited period of the migration from TAPE-C4 to TAPE-C5. Please contact your
regional office to find out about usage rights.

23

Overview of the C5 migrator

C4/C5 migration tool

DMS
List of tape
files (**)

TAPEFILES.
C5-MIG

P4
MAREN
catalog
(C4)

P4
call

Subsystem
DMS
List of tape
files (*)
P2 call

MAREN.
C5-MIG

P1

/MIGRATECATALOGENTRIES

P2

List of
ARCHIVE
directory files

TSOSCAT

Subsystem
MAREN
catalog
(C5)
ARCHIVE
directory
files

/MIGRATEARCHIVEDIRECTORIES

P3

List of
ARCHIVE
directory files
(*) with or without catalog ID and user ID
(**) with catalog ID and user ID

of
system
migration
archives

Figure 3: Overview of the components of the C5 migrator and their interaction

24

U25751-J-Z125-1-7600

C4/C5 migration tool

Installation

6.2 Installation
The following components are supplied for the C5 migrator:
for BS2000/OSD-BC
Supply component

V1.0

V2.0

V3.0

SYSPRC.C5-MIGRATOR.010
PLAM library with the elements:
MAREN.C5-MIG
(SDF-P main procedure for MARENCAT migration
(compiled as type-SYSJ element and in source code as
type-J element)
TAPEFILES.C5-MIG
SDF-P procedure for listing the full tape file names on all
accessible pubsets
(as type-SYSJ and type-J element)

SYSLNK.C5-MIGRATOR.010: migration subsystem (type L)

SYSMSV.C5-MIGRATOR.010: message file

X
X

SYSMES.C5-MIGRATOR.010: message file

SYSSDF.C5-MIGRATOR.010.110: syntax file

SYSSDF.C5-MIGRATOR.010.112: syntax file

SYSSSC.C5-MIGRATOR.010.110: subsystem declaration

*)

SYSSSC.C5-MIGRATOR.010.112: subsystem declaration

*)

SYSSSC.C5-MIGRATOR.010.120: subsystem declaration

*)

X
X
X

SYSREP.C5-MIGRATOR.010: REP file

SYSRMS.C5-MIGRATOR.010: RMS delivery packet

SYSSII.C5-MIGRATOR.010:
information file on structure and installation

SRMLNK.C5-MIGRATOR.010.121:
library with the subsystem LLM for OSD-SVP V1.0
SRMSSC.C5-MIGRATOR.010.121:
subsystem declaration for OSD-SVP V1.0 *)
Supply components of the C5 migrator
*) The name of the subsystem is C5-MIG (start with: /START-SUBSYSTEM C5-MIG)

The files must be installed under TSOS and the procedures must be executed under TSOS.

U25751-J-Z125-1-7600

25

Notes on the migration run

C4/C5 migration tool

6.3 Notes on the migration run

1. Migration should be performed on an exclusively available operating system. The
subsystems MAREN, ARCHIVE and HSMS must be stopped.
2. All tape accesses to 3591 devices must be stopped.
3. The migration must be performed on all systems in the network before MAREN is
started.
4. The MAREN.C5-MIG procedure migrates all TAPE-C4 volumes which are assigned to
the defined location. Before the procedure is executed, you must therefore ensure that
all MTCs are actually at this location. If the volumes were not defined in a specific
location, they must be manually assigned to a location with the MAREN statement
MODIFY-VOLUME-ATTRIBUTES (HOME-LOCATION). After migration, the VSNs
should be reassigned to the original location (MODIFY-VOLUME-ATTRIBUTES
statement).
5. If problems occur, the procedures/commands can be executed again. For each
TSOSCAT entry that has already been migrated, message MIG0014 is output.
6. After the migration and before MAREN is restarted, the two secondary index files (user
index, file index) must be deleted. After MAREN is restarted, they must be regenerated
with the following statements:
VERIFY-MAREN-CATALOG SELECT=*ALL
OPEN-MAREN-FILES

7. The migration must be performed with the latest MAREN catalog, as it is not possible
to reconstruct the MAREN catalog from an older log file. It is advisable to create a
backup copy of the MAREN catalog after migration using the following statement:
COPY-VOLUME-CATALOG

8. If MARENUCP is used in the system, the volume type TAPE-C5 must be entered in the
table which contains the volume types permitted for new reservations. This is done with
the following statement:
MODIFY-MAREN-PARAMETERS
RESERVE-DEVICE-TYPES=*PARAMETERS(DEVICE-TYPE=TAPE-C5,ACTION=*ADD)

Restrictions
The tape files can be written over a maximum of 28 volumes.

26

U25751-J-Z125-1-7600

C4/C5 migration tool

MARENCAT migration

6.4 MARENCAT migration

Migration is performed by a special tool which migrates the MARENCAT entries of volumes
which belong to a particular MAREN location.
An SDF-P procedure, which calls PERCON, searches MARENCAT and modifies the
volume type of the MARENCAT entries of this location from TAPE-C4 to TAPE-C5.
The procedure creates a list (SAM file) of the tape file names in the MARENCAT. This file
is used as input for updating the volume type in the TSOSCAT with the MIGRATECATALOG-ENTRIES command.
If the local MAREN parameter CID-UID is not specified in the MARENCP parameters, the
file names in the MARENCAT do not contain a catalog ID or user ID. The P4 procedure is
executed in any case, in order to extract the complete file names of the tape files from all
accessible pubsets. These file names are written to a SAM file and used to supplement the
file names extracted from MARENCAT.
The TSOSCAT update is performed with the help of the privileged command MIGRATECATALOG-ENTRIES. If ARCHIVE is present on the system, the ARCHIVE directory file
names are written to a different file, which is later used as input for the privileged MIGRATEARCHIVE-DIRECTORIES command.
To guarantee the integrity of MARENCAT, the updating is done in a copy. The migration is
complete when all entries in MARENCAT have been migrated.
If the procedure runs without errors, the old MARENCAT must be overwritten with the newly
generated one and MAREN must be restarted.
With migration under BS2000/OSD-BC V1.0, you should note that the data on the
TAPE-C5 volumes can no longer be read in BS2000/OSD-BC V1.0 after the
migration, as TAPE-C5 volumes are only supported as of BS2000/OSD-BC V2.0.

6.4.1 User interface

The SDF-P procedure MAREN.C5-MIG must be executed under TSOS.
Software requirements

BS2000/OSD-BC V1.0 or higher

PERCON
EDT
SDF-P (basis)

U25751-J-Z125-1-7600

27

MARENCAT migration

C4/C5 migration tool

Call parameters
Input
Parameter

Meaning

INPUT-MAREN

File name of the MARENCAT to be migrated

(default: $SYSMAREN.MARENCAT)

LOCATION

MAREN location to be migrated (no default)

SYSOUT

<filename 1..54>:
File name of a cataloged file in which the SYSOUT outputs of
the C5 migrator are logged
(default: C5-MIG.SYSOUT)
*NO
SYSOUT is not logged in a file.

ERASE

Specifies whether work files C5-MIG.WORK.<date>.<tsn> and

OUT.<date>.<tsn>.<catid> are deleted or not.
Default: YES
NO = Work files are not deleted.

Output

28

Parameter

Meaning

OUTPUT-MAREN

File name of the migrated MARENCAT

(default: $SYSMAREN.MARENCAT.MIGRATED);
here the specification must be different from that for INPUT-FILE

MAREN-FILE-LIST

File name of the list with the file names in TSOSCAT that are to
be migrated
(default: FILENAMES.LIST)

DIRLIST

File name of the list of the ARCHIVE directory files to be

migrated
(default: DIRECTORIES.LIST)

TAPE-FILE

File name of the list of tape files extracted from the accessible
pubsets
(default: TAPE.FILE)

U25751-J-Z125-1-7600

C4/C5 migration tool

MARENCAT migration

Record structures of the files

MAREN-FILE-LIST (sorted list of file names)
Structure element

Data type (length)

File name

CHAR(41)

Filler character

CHAR(1)

Catalog ID

CHAR(4)

User ID

CHAR(8)

Filler character

Comma

FSEQ

CHAR(4)

Filler character

Comma

List of up to 28 VSNs

CHAR(6) separated by commas

TAPE-FILE-LIST (sorted list of file names with catid and userid)

Structure element

Data type (length)

File name

CHAR(41)

Filler character

CHAR(1)

Catalog ID

CHAR(4)

User ID

CHAR(8)

DIRLIST (sorted list of file names)

Structure element

Data type (length)

Directory file name

CHAR(54)

Filler character

Blank, at least CHAR(1)

List of up to 25 VSNs

CHAR(6) separated by commas

During the procedure run, the work files C5-MIG.WORK.<date>.<tsn> and

OUT.<date>.<tsn>.<catid> are generated; unless ERASE=NO was specified in the
procedure call, they are then deleted.
If the work files already existed, they are overwritten.

U25751-J-Z125-1-7600

29

MARENCAT migration

C4/C5 migration tool

Error messages
INPUT AND OUTPUT FILES ARE IDENTICAL, PROCEDURE STOPS

Meaning
The names of the input and output MARENCAT files must be different. The procedure is
aborted.
Response
Give the input and output files different names and then call the procedure again.

6.4.2 Example of a procedure call

/CALL-PROCEDURE / FROM-FILE=*LIB-ELEM(LIB=SYSPRC.C5-MIGRATOR.010,ELEM=MAREN.C5-MIG),/ PROC-PAR=(INPUT-MAREN=$SYSMAREN.MARENCAT,/
OUTPUT-MAREN=$SYSMAREN.MARENCAT.OUT,LOCATION=ROBOTER1)

6.4.3 Further procedure

If errors have occurred, they must be corrected and the procedure must be executed again.
If the procedure executes without errors, the old MARENCAT must be overwritten by the
new one.

Before you overwrite MARENCAT, make sure that the procedure really did run with
no errors.

The next step is the TSOSCAT migration.

If ARCHIVE is installed on the system, ARCHIVE directory files must also be migrated (see
section Migration of the ARCHIVE directory files on page 35ff).

30

U25751-J-Z125-1-7600

C4/C5 migration tool

TSOSCAT migration

6.5 TSOSCAT migration

The migration can be performed using a privileged command which migrates the TSOSCAT
entries listed in a file. This file is created by the MARENCAT migration procedure. If MAREN
is not installed, the user must provide a file with a list of the TSOSCAT entries which are to
be migrated in TSOSCAT (see section TSOSCAT migration without MAREN on page 34).
This file is provided as input for the MIGRATE-CATALOG-ENTRIES command, with which
the volume type is updated in TSOSCAT. This command must be executed under TSOS.
The migration is complete when all 3591 entries in TSOSCAT have been migrated.
Before the TSOSCAT migration you must create a backup copy of the PVS with the
help of FDDRL. This is because the original TSOSCAT (not a copy!) is used in the
course of the migration.

6.5.1 User interface

The MIGRATE-CATALOG-ENTRIES command must be executed under TSOS.
Before the command is executed, the input files must be assigned using the SET-FILE-LINK
command:
File name

Link name

MAREN-FILE-LIST

TSCATMIG

TAPE-FILE-LIST

TAPEFILE

In the MAREN.C5-MIG procedure, the link names are automatically assigned during the
MARENCAT migration.
Software requirements

BS2000/OSD-BC V1.0 or higher

SDF-P (basis)

Started C5-MIG subsystem

U25751-J-Z125-1-7600

31

TSOSCAT migration

C4/C5 migration tool

Command format

MIGRATE-CATALOG-ENTRIES

The MIGRATE-CATALOG-ENTRIES command has no operands.

Before the command is executed, however, the link names must be assigned.
/SET-FILE-LINK LINK-NAME=TSCATMIG,FILE-NAME=<file name of MAREN file list>
/SET-FILE-LINK LINK-NAME=TAPEFILE,FILE-NAME=<file name of tape file list>
/MIGRATE-CATALOG-ENTRIES

Record structures of the files

See Record structures of the files on page 29 (MARENCAT migration).

Messages
The messages are output to SYSOUT.
MIG0001

ERROR IN (&00) WITH ERROR CODE (&01)

Meaning
This message is sent when an error occured in macro.
(&00): name of macro.
(&01): error code of the macro call.
MIG0002

FILENAME (&00) WITH FSEQ (&01) AND VSN (&02) NOT PRESENT IN TSOSCAT

MIG0003

FILENAME (&00) MIGRATED FROM TAPE-C4 TO TAPE-C5

MIG0004

VSN (&00), FILE SEQUENCE (&01) AND DEVICE TYPE (&02) PARAMETERS OF
FILENAME (&03) DO NOT MATCH PARAMETERS OF MARENCAT FILE

MIG0005

FILENAME (&00) NOT PRESENT

MIG0006

MIGRATION TERMINATED WITHOUT ERROR

MIG0007

MIGRATION TERMINATED WITH ERROR(S), SOME FILE(S) ARE NOT MIGRATED

Meaning
Some file(s) are not migrated, see the message in the SYSOUT file.

32

U25751-J-Z125-1-7600

C4/C5 migration tool

MIG0008

USER TASK MUST HAVE TSOS PRIVILEGES TO MIGRATE TSOSCAT

MIG0009

COMMAND (&00) ABNORMALLY TERMINATED

TSOSCAT migration

Meaning
See the sysout to find the reason.
MIG0010

ERROR IN (&00) WITH ERROR CODE (&01) ON FILE WITH LINKNAME TSCATMIG

Meaning
An error has been reported by a macro call.
(&00): name of macro.
(&01): error code of the error.
MIG0011

ERROR IN (&00) WITH ERROR CODE (&01) ON FILE WITH LINKNAME TAPEFILE

Meaning
An error has been reported by a macro call.
(&00): name of macro.
(&01): error code of the error.
MIG0012

COMMAND (&00) NORMALLY TERMINATED

MIG0013

FILE (&00) DOES NOT MATCH PARAMETERS OF TSOSCAT FILE OR IS NOT LOCALLY
ACCESSIBLE

Meaning
The parameters of the file (&00) (vsn ,fseq or/and device-type) do not match the TSOSCAT
entry or the catalog-id is not locally accessible (remote host).
MIG0014

DEVICE-TYPE ALREADY TAPE-C5 FOR FILE (&00); PROCESSING CONTINUES

MIG0015

INVALID RECORD IN INPUT FILE

6.5.2 Example
/SET-FILE-LINK LINK-NAME=TSCATMIG,FILE-NAME=MAREN.FILE.LIST
/SET-FILE-LINK LINK-NAME=TAPEFILE,FILE-NAME=TAPE.LIST
/MIGRATE-CATALOG-ENTRIES

U25751-J-Z125-1-7600

33

TSOSCAT migration

C4/C5 migration tool

6.5.3 TSOSCAT migration without MAREN

If MAREN is not installed, the TSOSCAT migrator can still be used if a SAM file in the format
described under Record structures of the files on page 32 (MAREN-FILE-LIST) is
provided.
This SAM file must contain the names of the files which are written on 3591 cartridges that
are to be migrated from TAPE-C4 to TAPE-C5. The TAPEFILES.C5-MIG procedure in the
SYSPRC.C5-MIGRATOR.010 library is helpful here in generating a list of all file names of
the tape files in all active pubsets of the network. The user must then select the files to be
migrated from this list, supplement the corresponding FSEQ and VSNs and delete the file
names which are not to be migrated from the list.
This procedure has only one output parameter:
OUTPUT-FILE: file name of the tape file list
Example
/CALL-PROCEDURE / FROM-FILE=*LIB-ELEM($TSOS.SYSPRC.C5-MIGRATOR.010,TAPEFILES.C5-MIG), / PROC-PAR=(OUTPUT-FILE=TAPEFILE)
/COPY-FILE FROM-FILE=TAPEFILE,TO-FILE=TAPE.FILE.LIST
/ .
/ .
Manual modification of the TAPE.FILE.LIST file using an editor, e.g. EDT
/ .
/SET-FILE-LINK FILE-NAME=TAPE.FILE.LIST,LINK-NAME=TSCATMIG
/SET-FILE-LINK FILE-NAME=TAPE.LIST,LINK-NAME=TAPEFILE
/MIGRATE-CATALOG-ENTRIES

34

U25751-J-Z125-1-7600

C4/C5 migration tool

Migration of the ARCHIVE directory files

6.6 Migration of the ARCHIVE directory files

Before the ARCHIVE directory files can be migrated, you must make sure that the MAREN
catalog (if you are working with MAREN) has already been migrated using the MAREN.C5MIG procedure, and the TSOSCAT has already been migrated using the MIGRATECATALOG-ENTRIES command.
The migration is performed with the privileged command MIGRATE-ARCHIVEDIRECTORIES, which migrates the ARCHIVE directory files listed in a file. It also updates
the TSOSCAT entries of files which have been migrated with directory files by HSMS.

Because the migration of the ARCHIVE directory files is performed directly, you
should create backup copies of the directory files to be migrated.
Unless already done during the TSOSCAT migration, a backup copy of the PVS
should also be created using FDDRL before the migration begins.

A SAM file containing a list of the ARCHIVE directory files to be migrated and the corresponding VSNs is passed to the command. This file is created by the MAREN.C5-MIG
procedure if MAREN is installed on the system. Otherwise, the user must create the file
himself/herself (see Record structures of the files on page 29). If only the file name of the
directory file is passed on, all TAPE-C4s in this directory file will be changed to TAPE-C5s.

If, in a directory file, real TAPE-C4s (from 3590E devices) are also used, migration
without specification of the VSNs that are actually to be migrated causes real TAPEC4s also to be converted to TAPE-C5s, which then cease to be usable. This cannot
be undone.
You should therefore make backup copies of directory files beforehand!

To modify the TSOSCAT entries when HSMS is used on the system, you must inform the
tool which directory files are used for system migration archives (SYSMIGRATE). To do this
you must pass to the command a further SAM file containing a list of the directory files of
migration archives. This list can be generated with the following HSMS statement:
//SHOW-ARCHIVE-ATTRIBUTES ALLOWED-USAGE=*MIGRATION

You must bear in mind that only directory files containing 3591 volumes (128-track
MTCs) can be selected.
If the TSOSCAT entry of a migrated file was converted incorrectly, this entry can be
restored with the following HSMS command:
/RESTORE-FILES ...,MIGRATED-FILES=CATALOG-ONLY

U25751-J-Z125-1-7600

35

Migration of the ARCHIVE directory files

C4/C5 migration tool

6.6.1 User interface

The MIGRATE-ARCHIVE-DIRECTORIES command must be executed under TSOS.
Software requirements

BS2000/OSD-BC V1.0 or higher

SDF-P (basis)

Started C5-MIG subsystem

Command format

MIGRATE-ARCHIVE-DIRECTORIES

The MIGRATE-ARCHIVE-DIRECTORIES command has no operands.

Before the command is executed, however, the link names must be assigned.
/SET-FILE-LINK LINK-NAME=DRECLIST,FILE-NAME=DIRECTORIES.AND.VSN.LIST, /
ACCESS-METHOD=*SAM
/SET-FILE-LINK LINK-NAME=MIGDRLST,FILE-NAME=MIGRATION.DIRECTORIES.LIST, /
ACCESS-METHOD=*SAM
/MIGRATE-ARCHIVE-DIRECTORIES

The MIGDRLST specification is optional and is only required if SYSMIGRATE directory files
have to be converted.

36

U25751-J-Z125-1-7600

C4/C5 migration tool

Migration of the ARCHIVE directory files

Record structures of the files

List of the directory files (DIRLIST of MAREN.C5-MIG)
Structure element

Data type (length)

Directory file name

CHAR(54)

Filler character

Blank, at least CHAR(1)

List of up to 25 VSNs

CHAR(6) separated by commas

List of the directory files for system migration archives (MIGDIRLIST)

This list must always be generated by the user himself/herself.
Structure element

Data type (length)

Directory file name

CHAR(54)

If MAREN is not installed, the ARCHIVE migrator can still be used if a SAM file with
the format described under DIRLIST is provided. The SAM file must contain the file
names of the ARCHIVE directory files to be migrated from TAPE-C4 to TAPE-C5.

Error messages
MIG0100

ERROR IN (&00) WITH ERROR CODE (&01) ON FILE OR LINK-NAME (&02)

Meaning
(&00) Name of the macro
(&01) Error code returned by the macro
(&02) Filename or link-name of the file for which the macro has been invoked.
MIG0101

CONVERSION OF DIRECTORY (&00) STARTED

MIG0102

CONVERSION OF DIRECTORY (&00) ENDED

MIG0103

VSN (&00) NOT IN DIRECTORY (&01) OR NOT DECLARED AS TAPE-C4

MIG0104

MIGRATION DIRECTORY LIST NOT FOUND, NO CATALOG ENTRY WILL BE ALTERED

MIG0105

CATALOG ENTRY OF FILE (&00) MIGRATED

U25751-J-Z125-1-7600

37

Migration of the ARCHIVE directory files

MIG0106

C4/C5 migration tool

CATALOG ENTRY OF FILE (&00) HAS NOT BEEN MIGRATED

Meaning
Possible reasons:
1. An error was encountered during the execution of a macro. If this is the case, a
MIG0100 message must precede this one, telling more about the error detected.
2. The file has been recalled and there is no point to altering its Catalog Entry.
3. The information contained in the directory does not match with the information from the
file Catalog Entry.
MIG0107

DISCREPANCY FOR FILE (&00) : DIRECTORY SAYS VSN (&01) BUT CAT ENTRY SAYS
VSN (&02) AND DEVICE TYPE (&03).

Meaning
Although the file is reported as migrated on tape with VSN (&01) in the directory, it appears
from the Catalog Entry that it is migrated on tape (&02) (device type = (&03)).

Error handling
If errors occur, the command can be executed again. For directory files which have already
been migrated, warnings are displayed. To prevent these warnings being displayed, you
must remove the names of the directory files concerned from the DIRLIST and
MIGDIRLIST files before the command is executed again.
These names are listed in the SYSOUT output of the previous run.

38

U25751-J-Z125-1-7600

C4/C5 migration tool

Migration of the ARCHIVE directory files

6.6.2 Restrictions

The tool does not process copies of directory files on tapes which were created with
DIRSAVE=YES. Therefore, in the event of a system crash, the user must process them
again after the restoration of the directory files from tape.
The input files should therefore be stored in a safe place.

If a backup file contains a mixture of emulated TAPE-C4 volumes (for 3591) and real
TAPE-C4 volumes (for 3590E), this file must be copied to a new, homogeneous backup
file, which contains either only emulated or only real TAPE-C4 volumes. This must occur
before migration of the affected ARCHIVE directory files and of MARENCAT.

Make sure that emulated and real TAPE-C4 volumes are not mixed in the same
backup file. The migration to TAPE-C5 makes such backup files unusable.

HSMS repositories used when saving or archiving with the HSMS statement BACKUPNODE-FILES and ARCHIVE-NODE-FILES cannot be migrated using the tools
mentioned here. With the aid of the SHOW-FILE-ATTRIBUTES command, such HSMS
repositories can be identified with regard to the possible ARCHIVE directory files:
ARCHIVE directory files with KEY-LEN=155 are used with the HSMS statement
BACKUP-NODE-FILES. However, the migration tool can only migrate ARCHIVE
directory files with KEY-LEN=55.
For information on the C4/C5 migration of such HSMS repositories please refer to the
release notice supplied with this tool, section Restrictions.

U25751-J-Z125-1-7600

39

Eine Dokuschablone von Frank Flachenecker

by f.f. 1992

Abbreviations
ABBA

automatic tape operating archive (German acronym)

ARCHIVE

archiving tool

FMLI

Form and Menu Language Interpreter

FSEQ

File SEQuence number

HSI

Hardware/Software Interface

HSMS

Hierarchical Storage Management System

KAx

channel adapter (x: digit)

MAREN

magnetic volume archiving system in the computer network

(German acronym)

MARENCAT

MAREN catalog

MTC

Magnetic Tape Cartridge (sometimes MBK, German acronym)

NDM

Nucleus Device Management

OSD

Open Server Dimension

PERCON

PERipheral CONverter

RFA

Remote File Access

ROBAR

ROBot ARchive (ABBA support)

RRF

ROBAR Rule File

SAM

Sequential Access Method

SDF

System Dialog Facility

U25751-J-Z125-1-7600

41

Abbreviations

42

SPD

Shared Private Disk

TLS

Tape Library System

TPM

Tape Pool Manager

TSOS

Time-Sharing Operating System

TSOSCAT

TSOS CATalog

UGEN

Universal GENerator

VSN

Volume Serial Number

VTS

Virtual Tape Server

U25751-J-Z125-1-7600

Related publications
Please apply to your local office for ordering the manuals.
[1]

BS2000/OSD-BC
Introductory Guide to Systems Support
User Guide
Target group
This manual is addressed to BS2000/OSD systems support staff and operators.
Contents
The manual covers the following topics relating to the management and monitoring of the
BS2000/OSD basic configuration: system initialization, parameter service, job and task
control, memory/device/user/file management, assignment of privileges, accounting and
operator functions.

[2]

BS2000/OSD-BC
System Installation
User Guide
Target group
This manual is intended for BS2000/OSD system administration.
Contents
The manual describes the generation of the hardware and software configuration with
UGEN and the following installation services: disk organization with MPVS, the installation
of volumes using the SIR-IP utility routine, and the IOCFCOPY utility routine.

U25751-J-Z125-1-7600

43

Related publications

[3]

SINIX-2000 V7.0
Installation, Operation and Administration
User Guide
Target group
This manual is intended for privileged users (operators, system administrators) of the
service/console processor 3970-SKP, the channel adapter 3970-KAx, and the business
servers C80-2 and SR2000.
Contents
The manual contains all the information required to ensure that the systems service/
console processor 3970-SKP/S110 and 3970-SKP/S130, channel adapter 3970-KAx and
business servers C80-2 and SR2000 are ready for use. This includes helpful information on
configuring the systems and a description of important functions for system operation and
administration.

[4]

ROBAR (BS2000/OSD, SINIX)

Tape Cartridge Archiving System
User Guide
Target group
Computer centers working with the ABBA robot system (CC staff, in particular system
administrators and archivers), ROBAR users
Contents
The manual describes the ROBAR software product that, in conjunction with the ABBA
system, controls automatic operation within a tape cartridge archiving system. It describes:
the concept and mode of operation
the user interfaces in BS2000 and SINIX
installation and messages

[5]

MAREN (BS2000/OSD)
for Administrators
System Administrator Guide
Target group
Computer center and system administrators.
Contents
Description of the MAREN system (volume archiving system in computer networks) for
managing data on volumes in BS2000 computer centers.

44

U25751-J-Z125-1-7600

Related publications

[6]

TLS (BS2000/OSD)
Tape Library System
User Guide
Target group
Computer centers which use the 3594 Tape Library System (computer center staff,
archiving staff).
Contents
The manual describes the TLS subsystem, which is used together with MAREN to manage
and control the 3594 Tape Library System. It contains the TLS functions and provides
information on installation and location management.

[7]

3970-SKP / 3970-KAx
Operating Manual
Target group
The manual addresses privileged users (operators, system administrators).
Contents
The manual contains all the information required to operate the hardware of the service/
console processor SKP 3970 and the 3970-KAx channel adapter.

U25751-J-Z125-1-7600

45

Eine Dokuschablone von Frank Flachenecker

by f.f. 1992

Index
128-track MTC 5, 7, 8, 15, 18
3590E (MTC device) 5
3591 (MTC device) 1, 5, 7
already used in C4 mode 16
first-time use 15
3594 Tape Library System 6
36-track MTC 8, 18
3970-KAx Channel Adapter 5
A
activate emulation for 3591 18
active pubsets 34
ARCHIVE 21
ARCHIVE directory file 18, 21
migration 35
ARCHIVE-NODE-FILES (HSMS statement)
AUTOMATIC mode (operating mode) 1, 6

39

B
backup file (HSMS) 39
BACKUP-NODE-FILES statement 39
BS2000 host 5
BS2000/OSD version dependence 2
C
C4 mode 1, 5, 7, 21
C5 migrator, overview 23
C5 mode 1, 6, 8, 21
C5-MIG (TPR subsystem) 23
catalog
MARENCAT 7
TSOSCAT 7
chad, configure (SINIX-2000) 13
channel adapter 3970-KAx 5
channel interface, configure (SINIX-2000)

U25751-J-Z125-1-7600

13
47

Index

channel type 2/S 5

CID-UID (MAREN parameter) 27
command
MIGRATE-ARCHIVE-DIRECTORIES 36
MIGRATE-CATALOG-ENTRIES 32
configure
3970-KAx Channel Adapter 9
BS2000 devices (SINIX-2000) 9
chad (SINIX-2000) 13
channel interface (SINIX-2000) 13
tape devices 9
COPY-VOLUME-CATALOG (MAREN statement)

26

D
default volume type (MAREN) 16
delete tape device (SINIX-2000) 12
device selection
via location 7
via volume type 8
directory file (ARCHIVE) 18
DIRLIST 29, 37
F
free tape pool, set up
FSEQ 34

19

G
generate
BS2000/OSD 17
new tape device (SINIX-2000)

11

H
HSMS 21
HSMS repository 39
HSMS-CL, see HSMS repository
I
index files (MAREN)
installation files 25

26

L
locally imported pubsets
locations 21
separate 7
log file (MAREN) 26
48

22

U25751-J-Z125-1-7600

Index

M
MANUAL mode (operating mode) 1, 6
manual operation 21
MAREN 8, 21
MAREN exits 19
MAREN.C5-MIG (S procedure) 23
call parameters 28
example 30
file record structure 29
MARENCAT (catalog) 7, 18, 21
migration 27
overwrite 30
reconstruct 26
MAREN-FILE-LIST 29
MARENLM reservation file 19
MARENUCP 26
MBK7 18
MIGDIRLIST 37
MIGRATE-ARCHIVE-DIRECTORIES command
MIGRATE-CATALOG-ENTRIES command 32
migrated files 21
migration
measures 17
notes 26
mixed configuration 16, 18
multiuser system 22

36

N
NDM 7
network 22
O
operating modes of standalone devices
operation, manual 21
original mode (C5 mode) 1, 8

P
PERCON 21, 23
procedure
MAREN.C5-MIG 23
TAPEFILES.C5-MIG 23, 34
pubset
active 34
locally imported 22

U25751-J-Z125-1-7600

49

Index

remote

22

R
RANDOM mode (operating mode) 1, 6
README file 3
remote pubsets 22
reservation table, permitted volume types 26
RESTORE-NODE-FILES, see HSMS repository
restrictions
directory file copy 39
RFA mode 22
ROBAR rule file 18
RUN file 17
S
scratch request 8, 16
secondary index files (MAREN) 26
separate locations 7
setting up a free tape pool 19
show tape device (SINIX-2000) 12
SPD mode 22
stacker 1, 6
random access 8
sequential access 8
standalone system 22
supply components for C5-MIGRATOR 25
sysadm menu (channel adapter) 9
SYSMIGRATE (HSMS) 35
system migration archive (HSMS) 35
SYSTEM mode (operating mode) 1, 6
T
tape files, written over a number of volumes
tape library system 3594 6
TAPE-C1/TAPE-C2 volumes 16
TAPE-C4 1, 5, 21
TAPE-C5 1, 6, 21
TAPE-FILE-LIST 29
TAPEFILES.C5-MIG (S procedure) 23, 34
TPM configuration 19
TSOSCAT (catalog) 7, 18, 21
migration 31
migration without MAREN 34

50

26

U25751-J-Z125-1-7600

Index

U
UGEN 17
user procedure, changes

19

V
VERIFY-MAREN-CATALOG (MAREN statement)
volume type
TAPE-C4 1, 5, 21
TAPE-C5 1, 6, 21
VSN 34
VTS 6

U25751-J-Z125-1-7600

26

51

Eine Dokuschablone von Frank Flachenecker

by f.f. 1992

Contents
1
1.1
1.2
1.3

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Target group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Summary of contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Notational conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1
2
3
4

2
2.1
2.2

2.3
2.4

Affected hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3970-KAx Channel Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Standalone devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3591-C4 mode: device type 3590E (internal C4), volume type TAPE-C4 . . . . . . . . . . . .
3591-C5 mode: device type 3591 (internal C5), volume type TAPE-C5 . . . . . . . . . . . . .
3594 Tape Library System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ABBA archive system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5
5
5
5
6
6
6

3
3.1
3.2

Comparison of the software configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

BS2000/OSD-BC V1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
BS2000/OSD-BC V2.0 and higher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

4
4.1

Configuring C5 devices on the 3970-KAx Channel Adapter . . . . . . . . . . . . . . . . . . . 9

BS2000 devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Generate new tape device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Modify tape device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Delete tape device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Show tape device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Channel interface (chad) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

4.2
5
5.1

5.2
5.2.1
5.2.2
5.2.3
5.2.4
5.2.5

Software modifications and measures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Usage scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using 3591 devices for the first time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3591 devices already in use, but no conversion desired . . . . . . . . . . . . . . . . . . . . . . . .
3591 devices already in use, conversion desired . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Migration measures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BS2000 generation (UGEN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Activating the 3591 emulation on all channel adapters . . . . . . . . . . . . . . . . . . . . . . . . .
Changing the volume type in data structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Activating the ROBAR rule files for 3591 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting up a free tape pool with TAPE-C5 volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . .

U25751-J-Z125-1-7600

15
15
15
16
16
17
17
18
18
18
19

53

Contents

5.2.6
5.2.7
5.2.8
5.3

Changes to user procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Changes to MAREN exits and the MARENLM reservation file . . . . . . . . . . . . . . . . . . .
Changes to the TPM configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Note on RANDOM mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

19
19
19
20

6
6.1
6.2
6.3
6.4
6.4.1

C4/C5 migration tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overview of the C5 migrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Notes on the migration run . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MARENCAT migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
User interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Call parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Record structures of the files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Example of a procedure call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Further procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TSOSCAT migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
User interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Command format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Record structures of the files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TSOSCAT migration without MAREN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Migration of the ARCHIVE directory files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
User interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Command format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Record structures of the files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Error handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

21
23
25
26
27
27
28
29
30
30
30
31
31
32
32
32
33
34
35
36
36
37
37
38
39

6.4.2
6.4.3
6.5
6.5.1

6.5.2
6.5.3
6.6
6.6.1

6.6.2

Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

54

U25751-J-Z125-1-7600

C4/C5 Migration Guide for 3591 MTC Units

User Guide
Target group
This manual is intended for users on the level of system administrators who run 3591 MTC
Units in C4 mode and wish to migrate to C5 mode.
Contents
The manual describes the prerequisites and measures necessary for migrating 3591 MTC
Units from type C4 to type C5:
hardware and software requirements
technical and administrative measures
conversion measures in the affected catalogs and directory files
all other modifications
migration tools

Edition: March 1998

File: C4_C5.PDF

BS2000 is a registered trademark of Siemens Nixdorf Informationssyteme AG.

Copyright Siemens Nixdorf Informationssysteme AG, 1998.
All rights, including rights of translation, reproduction by printing, copying or similar
methods, even of parts, are reserved.
Offenders will be liable for damages. All rights, including rights created by patent grant or
registration of a utility model or design, are reserved.
Delivery subject to availability; right of technical modifications reserved.

U25751-J-Z125-1-7600

55

Information on this document

On April 1, 2009, Fujitsu became the sole owner of Fujitsu Siemens Computers. This new subsidiary of Fujitsu has been renamed Fujitsu Technology Solutions.
This document from the document archive refers to a product version which
was released a considerable time ago or which is no longer marketed.
Please note that all company references and copyrights in this document have
been legally transferred to Fujitsu Technology Solutions.
Contact and support addresses will now be offered by Fujitsu Technology Solutions and have the format @ts.fujitsu.com.
The Internet pages of Fujitsu Technology Solutions are available at
http://ts.fujitsu.com/...
and the user documentation at http://manuals.ts.fujitsu.com.
Copyright Fujitsu Technology Solutions, 2009

Hinweise zum vorliegenden Dokument

Zum 1. April 2009 ist Fujitsu Siemens Computers in den alleinigen Besitz von
Fujitsu bergegangen. Diese neue Tochtergesellschaft von Fujitsu trgt seitdem den Namen Fujitsu Technology Solutions.
Das vorliegende Dokument aus dem Dokumentenarchiv bezieht sich auf eine
bereits vor lngerer Zeit freigegebene oder nicht mehr im Vertrieb befindliche
Produktversion.
Bitte beachten Sie, dass alle Firmenbezge und Copyrights im vorliegenden
Dokument rechtlich auf Fujitsu Technology Solutions bergegangen sind.
Kontakt- und Supportadressen werden nun von Fujitsu Technology Solutions
angeboten und haben die Form @ts.fujitsu.com.
Die Internetseiten von Fujitsu Technology Solutions finden Sie unter
http://de.ts.fujitsu.com/..., und unter http://manuals.ts.fujitsu.com finden Sie die
Benutzerdokumentation.
Copyright Fujitsu Technology Solutions, 2009