Differences Between HP Micro Focus COBOL/HP-UX andHP Micro Focus COBOL/iX [ HP Micro Focus COBOL/iX Implementation Notes ] MPE/iX 5.0 Documentation
HP Micro Focus COBOL/iX Implementation Notes
Differences Between HP Micro Focus COBOL/HP-UX andHP Micro Focus COBOL/iX
* Due to changes in the Micro Focus interpreted code, you must
regenerate and relink all existing programs created using previous
releases of Micro Focus COBOL prior to Version V3.0.50.
* Moving .int files from HP-UX to MPE/iX is supported, provided the
.int files are created with HP Micro Focus COBOL/UX Version
B.07.xx.
* HP Micro Focus COBOL/iX programs must be run from the MPE/iX
Shell. The program files can reside and be executed from a
directory.
* The product includes the following components from Micro Focus,
not HP: SORT, ISAM, curses.
* HP Micro Focus COBOL/iX programs can access byte stream files
only, not MPE/iX files (such as relative, message, or KSAM files).
* Programs that use ADIS screen I/O require a newer DTC: model 2345A
with options 803, 625 and 242. Running programs with ADIS screen
I/O is only supported with the terminal connected through a DTC;
there is no vt3k, DSLINE, or workstation support.
* Function keys are supported only if the session is connected
through a DTC.
* ADIS uses character mode, not block mode. When the documentation
says to use the Enter key, use the Return key to terminate data
entry.
* HP Micro Focus COBOL/iX screen I/O has been tested with the
hp2392a terminfo file only. terminfo files are not supplied as
part of this product; any terminfo issues should be directed to
MPE/iX support.
* Because shared libraries are not supported, applications will be
built with archive libraries. Therefore, executable files will be
larger on MPE/iX than executable files built with shared libraries
on HP-UX.
* Multiple RIN (MR) capability is not required to lock multiple
records in an HP Micro Focus COBOL/iX application.
* All user and accounts that use the HP Micro Focus COBOL/iX product
must have PH (process handling) capability. If an HP Micro Focus
COBOL/iX program resides in an MPE group, the group must have PH
capability for the program to load. However, if a program resides
in a HFS directory, the loader loads the program automatically.
* HP Micro Focus COBOL/iX is not fully X/Open compliant.
* User libraries must be POSIX compliant, not ANSI compliant, and
must be in .a format to link them into an HP Micro Focus COBOL/iX
application.
* HP Micro Focus COBOL/iX does not enable the Control-C trap; use
Control-Y to abort a program. When you use Control-Y to stop a
program (for example, myprog), you will see:
$ cobrun myprog
control-Y detected...
* When using the Go or Zoom command in Animator, use Control-Y
instead of the escape key to break out of Go or Zoom mode.
* Symbolic debugging, using XDB, is supported in the MPE/iX Shell.
However, symbolic debugging of a Micro Focus COBOL native code
program is not supported. Only assembly debugging of a Micro
Focus COBOL native code program is supported. XDB is supported in
the MPE/iX Shell with a limitation that command line arguments can
not be passed to a subprocess. For example, a C main program, or
a COBOL program, will not be able to access argc or argv when it
is run in XDB.
Use -g cob option to compile Micro Focus COBOL or C source files.
You can also use /bin/c89 to compile C source files. You must
compile with the -g option when using XDB for debugging.
To initiate an XDB session, type /SYS/PUB/XDB and enter a program
name when the following prompt is displayed:
XDB arguments and program file?
Example
shell/iX>cob -gx foo.cbl foo1.c
shell/iX>/SYS/PUB/XDB
XDB arguments and program file? foo
* All accounts that use HP Micro Focus COBOL/iX must have a TMP
group to which any user in that account can write and save files.
* To invoke the C compiler, use c89 instead of cc; the cob command
invokes c89 when you request C code compilation.
* Because the lp command is not supported on MPE/iX, the following
COBOL syntax is not supported:
SELECT ... ASSIGN TO PRINTER and dd_LPT1=">lp"
DISPLAY ... UPON PRINTER
The work around for line one is to unset dd_LPT1 so that the
output goes to the file LPT1 and use the MPE/iX print command to
print LPT1:
shell/iX>callci "file lp;dev=lp"
shell/iX>callci "print ./LPT1;out=*lp"
* Because the nm command is not supported on MPE/iX, call the Link
Editor to display symbol information. For example, instead of nm
myprog.o, enter:
shell/iX>callci "linkedit 'listobj ./myprog.o'"
[REV DEL]
Unsupported Features on HP Micro Focus COBOL/iX
Features of HP Micro Focus COBOL/UX that are not supported in this
release of HP Micro Focus COBOL/iX are:
* gnt and snt code, for example cob flags -u and +u are rejected.
* Shared libraries (.sl and XL files).
* Building programs that require shared libraries or XLs.
* SimpleLink.
* Passing options to the system link editor with the cob flag -Q.
[REV BEG]
* 8-bit NLS.[REV END]
* Specifying assembly code on the cob command line.
* Moving .o, .gnt, .snt, .sl, .exe files from HP-UX to MPE/iX.
* Format 7 of the SET statement (to assign the address of an entry
point to a PROCEDURE-POINTER data item).
* The Type Ahead Switch (HPCOBSW=+/-t) is ignored.[REV DEL]
* External Check Switch (HPCOBSW=+/-e).
* Native Code generator options, hparch and hpsched. MPE/iX only
supports PA-RISC1.0 instructions.
Micro Focus COBOL-related Products
The separate add-on products called Toolbox and Dialog System are not
available on MPE/iX. Therefore, PanelsV2 is not available on MPE/iX. As
on HP-UX, other Micro Focus COBOL add-on products are not available on
MPE/iX.
Moving Files from HP-UX
To move source and data files from HP-UX to MPE/iX, you can use one of
the methods shown in the following examples.
* tar:
Note that MPE/iX does not come with the default device file,
/dev/mt/0m. As MANAGER.SYS in PUB.SYS you must first create
/dev/dat as an MPE named device link file as follows:
:mknod "/dev/dat c 0 7"
Once /dev/dat is built, issue the following commands:
$ tar cv . on HP-UX, build a DDS tape
shell/iX>tar xvf /dev/dat on MPE/iX from the MPE/iX Shell
Note that tar on MPE/iX may display warning messages like the
following message because of differences in user naming
conventions between MPE/iX and HP-UX:
tar: ./myfile: cannot set uid/gid: Invalid argument
These warning messages can be ignored.
* ftp from HP-UX (be sure the ftp job is running on the MPE/iX
system):
$ ll bigfile.cbl
(note number of bytes in the file)
$ ftp mympesys
Name (mympesys:user): user.account
331 Password required for USER.ACCOUNT. Syntax: ,acctpass
ftp> cd mydir
ftp> put mudemo.cbl ./mudemo.cbl;rec=,,b
ftp> put bigfile.cbl ./bigfile.cbl;rec=,,b;disc=xxxxx
(where xxxxx is the number of bytes in the file; only needed for large files)
ftp> bye
For more information, refer to the MPE/iX manual set.
MPE/iX 5.0 Documentation