HP 3000 Manuals

HP ALLBASE/BRW Reference Manual

Transfer Reference 

Data 

MPE files, KSAM files, IMAGE databases, intermediate report files, and
dictionary output files can be used without amendment in either HP
ALLBASE/BRW or HP BRW/V. Data from HP ALLBASE/SQL tables cannot be
accessed in HP BRW/V.

Names In HP ALLBASE/BRW names can be up to 20 characters in length, but
in HP BRW/V they are restricted to 16 characters.

Configuration Files 

You can transfer configuration files from HP BRW/V to HP ALLBASE/BRW as
long as you rename the file BRWCONF. For example, if you defined a
special configuration file for group DATAIN in account ADMIN, the file
will be called RCONF.DATAIN.ADMIN. You can restore this file onto your
MPE XL system, but you must rename it BRWCONF before it will be used by
HP ALLBASE/BRW.
[REV BEG]

To transfer configuration files from HP ALLBASE/BRWto HP 
BRW/V 

   1.  Press the Verify function key on the Global Values screen to make
       sure no global function to be referenced in an HP BRW/V report
       contains names longer than 16 characters.

   2.  Rename the file from BRWCONF to RCONF.
[REV END]

HP ALLBASE/BRW Intrinsics 

HP ALLBASE/BRW intrinsics have the same characteristics as HP BRW/V
intrinsics except that:

   *   The BRW_COMAREA parameter used by the HP ALLBASE/BRW execution
       intrinsics (BRWOPEN, BRWINFO, BRWSTREAM, BRWEXEC, and BRWCLOSE)
       requires 332 bytes.

       (The BRW_COMAREA parameter used with the equivalent HP BRW/V
       intrinsics requires at least 300 bytes, but it is not a problem to
       use the larger number of bytes for both.  That way you can have
       one program that works for both systems).

   *   The element comarea_len of the parameter REQUEST_COMAREA (used by
       the HP ALLBASE/BRW  request report intrinsics BRWINITREQUEST,
       BRWSTARTREQUEST, and BRWSTOPREQUEST) must be set to 100.  (The
       element comarea_len of the parameter REQUEST_COMAREA used with the
       equivalent HP BRW/V intrinsics must be at least 50).

So if you transfer programs that use HP BRW/V intrinsics to MPE XL,
consult Appendix D, HP ALLBASE/BRW Intrinsics, and alter the parameter
length(s).

Report Job Files 

You must alter any appropriate program names when transferring report job
files between HP BRW/V and HP ALLBASE/BRW. (See the list of different
program file names near the beginning of this chapter.)  For example, a
report job file for HP BRW/V might contain:

       .
       .
       .
       $PRINTFILE
       !CONTINUE
       !RUN REXEC.PUB.SYS
       salesan.rexec
       sales-area = "WESTERN"
       !EOD
       .
       .

Before using this report job file with HP ALLBASE/BRW, you must amend the
file as below:

       .
       .
       .
       $PRINTFILE
       !CONTINUE
       !RUN BRWEXEC.PUB.SYS
       salesan.rexec
       sales-area = "WESTERN"
       !EOD
       .

Note that the REXEC program has been changed to BRWEXEC. You must also
make sure that the execution file salesan.rspec was compiled under HP
ALLBASE/BRW.

Standard Job Files 

You can transfer a standard job file from HP BRW/V to HP ALLBASE/BRW and
vice versa so long as you rename the files and alter any program names
within it.  For example, if you defined a special HP BRW/V standard job
file for group DATAIN in account ADMIN, the file will be called
RJOB.DATAIN.ADMIN. You can restore this file onto your MPE XL system, but
you must rename it BRWJOB before it will be used by HP ALLBASE/BRW. You
must also alter any appropriate program names.

MPE/iX 5.0 Documentation