HP 3000 Manuals HP 3000 Manuals
Transferring Reports between MPE V and MPE XL
You can transfer reports from HP BRW/V to HP ALLBASE/BRW. However, you
must recompile an HP BRW/V report with HP ALLBASE/BRW if you want to
obtain the full performance benefits of an MPE XL system. It is also
possible to transfer reports from HP ALLBASE/BRW to HP BRW/V provided the
report does not reference an HP ALLBASE/SQL table and does not contain
names longer than 16 characters.
MPE V to MPE XL (to run in Native Mode)
In order to run an existing MPE V report in native mode on MPE XL, you
must create a new HP ALLBASE/BRW report execution file by compiling the
HP BRW/V report specification file on the MPE XL.
To transfer from MPE V for native mode on MPE XL
1. Store the following from the MPE V system and restore them on the
MPE XL system:
a. the data files
b. the data dictionary
c. the report specification files
d. any report job files
e. any amended configuration files and standard job files
2. Run the appropriate BRWDIC generating program (BRWD3000.PUB.SYS,
BRWAPPD.PUB.SYS, BRWSD.PUB.SYS, BRWACCSD.PUB.SYS or
BRWGEND.PUB.SYS) to create a BRWDIC file from the restored MPE V
data dictionary.
If you have MPE or KSAM files that contain real numbers, you must
tell HP ALLBASE/BRW that these numbers are in HP 3000 format by
adding the longname !REAL-HP3000 (for HP Dictionary/V) or the
element-subtype HP 3000 (for HP System Dictionary) to the item's
definition in the data dictionary before creating the BRWDIC file.
See chapter 18, "Preparing a Data Dictionary."
_________________________________________________________________
NOTE You can remove the data dictionaries as soon as you have
created the BRWDIC file.
_________________________________________________________________
3. Edit the report job files so that the program filenames refer to
HP ALLBASE/BRW programs.
4. Edit the amended standard job files so that any program filenames
refer to HP ALLBASE/BRW programs.
5. Rename the following files:
a. standard job files from RJOB to BRWJOB
b. the configuration files from RCONF to BRWCONF
6. Using the programs BRWXL.PUB.SYS or BRWCOMP.PUB.SYS, compile the
report specification files to create HP ALLBASE/BRW report
execution files
The reports are now ready to run in MPE XL native mode.
MPE V to MPE XL (to run in Compatibility Mode)
To tranfer from MPE V to MPE XL for Compatibility Mode
1. Store the data from the MPE V system and restore it on the MPE XL
system.
2. Store the report execution files from the MPE V system and restore
them on the MPE XL system.
3. Store any report job files from the MPE V system and restore them
on the MPE XL system.
4. Store any amended configuration files and standard job files from
the MPE V system and restore them on the MPE XL system.
The reports are now ready to run in MPE XL compatibility mode.
NOTE The above instructions assume that you only want to run the HP
BRW/V reports in compatibility mode on MPE XL. If you want to
modify or compile the reports in compatibility mode on your MPE XL
system, you must also transfer the report specification files and
RDIC file from the MPE V system to the MPE XL system.
MPE XL to MPE V
To use an HP ALLBASE/BRW report from MPE XL on an MPE V system, you
should first verify that the report will be compatible on MPE V.
If you do development on the MPE XL system, and only intend to execute
the reports on MPE V, you don't need to copy the data dictionaries or
specification files. Just create RDIC on the MPE XL with the
compatibility mode RDIC generating program, then use BRW.PUB.SYS or
RCOMP.PUB.SYS on MPE XL to make the report execution file.
You don't have to have copies of the databases on both machines.
To verify compatibility for a report
1. Go to the HP ALLBASE/BRW Select Report screen or the Global Values
screen of BRWSETUP.
2. Choose Verify to check whether a report accesses an SQL database
or if it contains names with a length greater than 16 characters.
Reports that access an SQL database cannot be used on MPE V. If a report
contains names with a length greater than 16 characters, they must be
changed to 16 characters or less.
If no SQL files are accessed and no names are greater than 16 characters
in length, you get a messages that the report has been verified. You can
transfer the report to MPE V.
If conflicts are detected, warning messages appear on the screen and are
also written to a temporary file called RVERIFYM. These are the warning
messages:
SQL accessed
Name > 16 chars
You can print the warning messages by pressing Print.
NOTE In addition to the compatibility checks done by using Verify, you
need to be aware that HP BRW/V does not support IEEE-type real
numbers.
To transfer a compatible report from MPE XL to MPE V
1. When there are no conflicts in the report, store the following
from the MPE XL system and restore it on the MPE V system:
a. the data files
b. any report job files
c. any amended configuration files and standard job files
2. Edit these file so that the program filenames are those of HP
BRW/V:
a. report job file
b. amended standard job files
3. Rename these files:
a. the standard job files from BRWJOB to RJOB
b. the configuration files from BRWCONF to RCONF
4. Run the appropriate RDIC generating program (RDIC3000.PUB.SYS,
RAPPDIC.PUB.SYS, RSYSDIC.PUB.SYS, RACCSDIC.PUB.SYS, or
RGENDIC.PUB.SYS) to create an RDIC file from the data dictionary.
You can remove the data dictionaries as soon as you have created
the RDIC file.
5. Using BRW.PUB.SYS or RCOMP.PUB.SYS on HP ALLBASE/BRW, compile the
report specification files to create HP BRW/V report execution
files.
6. Store the HP BRW/V report execution files from the MPE XL system
and restore them on the MPE V system.
The reports are now ready to run on the MPE V system.
NOTE The MIT version of the MPE V operating system where you restore the
execution file must be V-Delta-1 MIT (G.03.01) or later.