HP 3000 Manuals HP 3000 Manuals
Detected Incompatibilities
Incompatibilities that are detected by the Migration Toolset are listed
in the following table. This table lists incompatibilities by number as
reported by the Migration Toolset. This table contains:
* A message number as returned by the Migration Toolset.
* The complete incompatibility message.
* The mode in which the incompatibility would arise and the
migration tool used to detect the incompatibility. Also specified
is the severity level of the incompatibility assigned by MPT and
the event class you must enable before the RTM will detect the
incompatibility.
* The cause of the incompatibility.
* Action to take to work around the incompatibility.
NOTE Message numbers reported by the A.00.01 version of the Migration
Toolset (MPT version A.01.04, OCA version A.00.03, and RTM version
A.00.01) may differ from those reported by previous versions of the
Migration Toolset.
You can find further information about differences between MPE V/E and
MPE/iX in the Introduction to MPE XL for MPE V Programmers (30367-90005),
where potential incompatibilities associated with system intrinsics are
described in greater detail than in this appendix.
101 MESSAGE XARITRAP intrinsic may require a new trap handler in MPE/iX
NM.
MODE NM incompatibility detected by MPT (severity level WARNING),
OCA, and RTM (Event Class 1).
CAUSE HP-PA is a 32-bit architecture, while the architecture of MPE
V/E-based computer systems is a 16-bit architecture. In NM,
memory addresses represented as pointers or plabels must be
32-bit entities, while in MPE V/E and in CM, pointers and
plabels must be 16-bit entities. The XARITRAP intrinsic uses
plabels.
ACTION Redeclare the variables you pass through the required plabel,
oldplabel, and mask parameters of XARITRAP to be 32-bit
entities. If you wish to have arithmetic traps enabled in
both CM and NM for a mixed-mode program, you must have two
trap routines--one in CM and one in NM.
---------------------------------------------------------------------------------------
102 MESSAGE XCONTRAP intrinsic may require a new trap handler in MPE/iX
NM.
MODE NM incompatibility detected by MPT (severity level WARNING),
OCA, and RTM (Event Class 1).
CAUSE HP-PA is a 32-bit architecture, while the architecture of MPE
V/E-based computer systems is a 16-bit architecture. In NM,
memory addresses represented as pointers or plabels must be
32-bit entities, while in MPE V/E and in CM, pointers and
plabels must be 16-bit entities. The XCONTRAP intrinsic uses
plabels.
ACTION Redeclare the variables you pass through the required plabel
and oldplabel parameters of XCONTRAP to be 32-bit entities.
---------------------------------------------------------------------------------------
103 MESSAGE iXIBTRAP intrinsic may require a new trap handler in MPE/iX
NM.
MODE NM incompatibility detected by MPT (severity level WARNING),
OCA, and RTM (Event Class 1).
CAUSE HP-PA is a 32-bit architecture, while the architecture of MPE
V/E-based computer systems is a 16-bit architecture. In NM,
memory addresses represented as pointers or plabels must be
32-bit entities, while in MPE V/E and in CM, pointers and
plabels must be 16-bit entities. The iXIBTRAP intrinsic uses
plabels.
ACTION Redeclare the variables you pass through the required plabel
and oldplabel parameters of iXIBTRAP to be 32-bit entities.
If you wish to have library traps enabled in both CM and NM
for a mixed-mode program, you must have two trap
routines--one in CM and one in NM.
---------------------------------------------------------------------------------------
104 MESSAGE XSYSTRAP intrinsic may require a new trap handler in MPE/iX
NM.
MODE NM incompatibility detected by MPT (severity level WARNING),
OCA, and RTM (Event Class 1).
CAUSE HP-PA is a 32-bit architecture, while the architecture of MPE
V/E-based computer systems is a 16-bit architecture. In NM,
memory addresses represented as pointers or plabels must be
32-bit entities, while in MPE V/E and in CM, pointers and
plabels must be 16-bit entities. The XSYSTRAP intrinsic uses
plabels.
ACTION Redeclare the variables you pass through the required plabel
and oldplabel parameters of XSYSTRAP to be 32-bit entities.
If you wish to have system traps enabled in both CM and NM
for a mixed-mode program, you must have two trap
routines--one in CM and one in NM.
---------------------------------------------------------------------------------------
105 MESSAGE SEARCH intrinsic may encounter pointer problems in MPE/iX NM.
MODE NM incompatibility detected by MPT (severity level POSSIBLE),
OCA, and RTM (Event Class 1).
CAUSE HP-PA is a 32-bit architecture, while the architecture of MPE
V/E-based computer systems is a 16-bit architecture. In NM,
memory addresses represented as pointers or plabels must be
32-bit entities, while in MPE V/E and in CM, pointers and
plabels must be 16-bit entities. The SEARCH intrinsic may
use pointers.
ACTION If you use the optional defn parameter of SEARCH, you must
redeclare the variable you pass through it to be a 32-bit
entity.
---------------------------------------------------------------------------------------
106 MESSAGE MYCOMMAND intrinsic may encounter pointer problems in MPE/iX
NM.
MODE NM incompatibility detected by MPT (severity level WARNING),
OCA, and RTM (Event Class 1).
CAUSE HP-PA is a 32-bit architecture, while the architecture of MPE
V/E-based computer systems is a 16-bit architecture. In NM,
memory addresses represented as pointers or plabels must be
32-bit entities, while in MPE V/E and in CM, pointers and
plabels must be 16-bit entities. The MYCOMMAND intrinsic
uses pointers.
ACTION Redeclare the variable you pass through the required params
parameter of MYCOMMAND to be a an array of 32-bit entities.
In addition, if you use the optional defn parameter, you must
redeclare the variable you pass through it to be a 32-bit
entity.
---------------------------------------------------------------------------------------
107 MESSAGE CREATEPROCESS intrinsic may encounter pointer problems in MPE
iX NM.
MODE NM incompatibility detected by MPT severity level POSSIBLE),
OCA, and RTM (Event Class 1).
CAUSE HP-PA is a 32-bit architecture, while the architecture of MPE
V/E-based computer systems is a 16-bit architecture. In NM,
memory addresses represented as pointers or plabels must be
32-bit entities, while in MPE V/E and in CM, pointers and
plabels must be 16-bit entities. The CREATEPROCESS intrinsic
may use pointers.
ACTION If you use the optional itemnums and items parameters of
CREATEPROCESS, you must redeclare the variables you pass
through them to be arrays of 32-bit entities.
---------------------------------------------------------------------------------------
108 MESSAGE GENMESSAGE intrinsic may encounter pointer problems in MPE/iX
NM.
MODE NM incompatibility detected by MPT (severity level POSSIBLE),
OCA, and RTM (Event Class 1).
CAUSE HP-PA is a 32-bit architecture, while the architecture of MPE
V/E-based computer systems is a 16-bit architecture. In NM,
memory addresses represented as pointers or plabels must be
32-bit entities, while in MPE V/E and in CM, pointers and
plabels must be 16-bit entities. The GENMESSAGE intrinsic
may use pointers.
ACTION If you use the optional param parameter of GENMESSAGE, you
must redeclare the variable you pass through it to be a
32-bit entity.
---------------------------------------------------------------------------------------
109 MESSAGE SWITCHDB intrinsic not supported in NM.
MODE NM incompatibility detected by MPT (severity level ERROR) and
OCA.
CAUSE The SWITCHDB intrinsic changes the DB register so that it
points to the base of an extra data segment instead of the
base of the stack on MPE V/E and in CM. The SWITCHDB
intrinsic is not available to programs executing in NM.
ACTION Remove all SWITCHDB invocations and dependent code from
programs which will execute in NM.
---------------------------------------------------------------------------------------
110 MESSAGE ARITRAP intrinsic state parameter is 32-bit signed integer.
MODE NM incompatibility detected by MPT (severity level WARNING)
and OCA.
CAUSE The ARITRAP intrinsic collectively enables or disables
arithmetic traps. On MPE V/E and in CM, the state parameter
is a required logical by value entity. In NM, ARITRAP uses
the trapstate parameter instead, which is a required 32-bit
signed integer by value entity.
ACTION Redeclare the variables you pass through the required
trapstate parameter to be a 32-bit entity for programs which
will execute in NM. If you wish to have arithmetic traps
collectively enabled in both CM and NM for a mixed-mode
program you must have two trap routines--one in CM and one in
NM.
---------------------------------------------------------------------------------------
196 MESSAGE LOADPROC intrinsic -> HPGETPROCPLABEL intrinsic for NM.
MODE NM incompatibility detected by MPT (severity level WARNING)
and OCA.
CAUSE Library routines may exist in either CM libraries (SLs) or in
NM libraries (iXs). The internal structures of these
libraries differ significantly. The LOADPROC intrinsic
dynamically loads procedures from MPE V/E or CM libraries
only.
ACTION If your library routine is in a CM SL, you must use LOADPROC
from a CM program, or either HPLOADCMPROCEDURE or LOADPROC
from a NM program to dynamically load this procedure. If you
move your library routine to a NM iX, you must use
HPGETPROCPLABEL from a NM program, or HPLOADNMPROC from a CM
program.
---------------------------------------------------------------------------------------
200 MESSAGE COMMAND intrinsic possible programmatic execution of
incompatible commands.
MODE CM and NM incompatibility detected by MPT (severity level
POSSIBLE) and OCA.
CAUSE Some MPE V/E commands have either been modified for use on
MPE/iX or are no longer supported on MPE/iX. The COMMAND
intrinsic may execute one of the following modified or
unsupported commands: :LISTF, :LISTACCT, :LISTUSER,
:LISTGROUP, :PTAPE, :TUNE, SHOWCACHE, :CACHECONTROL,
:STARTCACHE, :STOPCACHE, :SHOWCOM, :DSCONTROL, :STARTSESS,
and :SPEED.
ACTION If OCA or MPT reports this event, enable Event Class 2 of RTM
to detect when COMMAND executes one of the commands listed
above. Check for event numbers 201 through 218, which
indicate that RTM detected execution of a modified or
unsupported command. In all cases, analyze the program to
determine whether the command executed was acquired
interactively or embedded in code and evaluate how the
command is used.
---------------------------------------------------------------------------------------
201 MESSAGE Programmatic :LISTF.
MODE CM and NM incompatibility detected by MPT (severity level
POSSIBLE) and RTM (Event Class 2).
CAUSE Because of differences between HP-PA and the architecture of
MPE V/E-based computer systems, MPE/iX :LISTF -1 output is
different from MPE V/E :LISTF -1 format. In addition,
because of changes in extent management on MPE/iX, the MX
(maximum extents) field of :LISTF -2 will contain an asterisk
if a maximum number of extents was not specified at file
creation.
ACTION Remove code dependent upon :LISTF -1 output. Determine what
data you needed from :LISTF -1 and evaluate alternative ways
to retrieve that data, for example, through the FLABELINFO
intrinsic. Furthermore, MPE/iX enhancements to the :LISTF
command may also provide this data. If your code is
dependent upon data retrieved from the MX field output by
:LISTF 2, you may have to modify your code to handle the
asterisk.
---------------------------------------------------------------------------------------
202 MESSAGE Programmatic :LISTACCT to a file.
MODE CM and NM incompatibility detected by MPT (severity level
POSSIBLE) and RTM (Event Class 2).
CAUSE Because of enhancements to the MPE/iX operating system,
output from the :LISTACCT command appears in ASCII format.
ACTION If you are doing programmatic analysis of the :LISTACCT
output, you must modify your code to handle the new output
format.
---------------------------------------------------------------------------------------
203 MESSAGE Programmatic :LISTUSER to a file.
MODE CM and NM incompatibility detected by MPT (severity level
POSSIBLE) and RTM (Event Class 2).
CAUSE Because of enhancements to the MPE/iX operating system,
output from the :LISTUSER command appears in ASCII format.
ACTION If you are doing programmatic analysis of the :LISTUSER
output, you must modify your code to handle the new output
format.
---------------------------------------------------------------------------------------
204 MESSAGE Programmatic :LISTGROUP to a file.
MODE CM and NM incompatibility detected by MPT (severity level
POSSIBLE) and RTM (Event Class 2).
CAUSE Because of enhancements to the MPE/iX operating system,
output from the :LISTGROUP command appears in ASCII format.
ACTION If you are doing programmatic analysis of the :LISTGROUP
output, you must modify your code to handle the new output
format.
---------------------------------------------------------------------------------------
205 MESSAGE Programmatic :PTAPE command not supported.
MODE CM and NM incompatibility detected by MPT (severity level
ERROR) and RTM (Event Class 2).
CAUSE Modifications have been made to the attached peripheral
environment of MPE/iX, resulting in paper tape readers being
unsupported on MPE/iX-based computer systems. The :PTAPE
command is not supported on MPE iX-based computer systems.
ACTION Remove all :PTAPE invocations and dependent code. If you are
using :PTAPE for uses other than reading from paper tape
devices, you must determine the original need for the call to
:PTAPE and develop alternative solutions.
---------------------------------------------------------------------------------------
207 MESSAGE Programmatic :TUNE.
MODE CM and NM incompatibility detected by MPT (severity level
POSSIBLE) and RTM (Event Class 2).
CAUSE Because of enhancements to the MPE/iX operating system, the
required minclockcycle parameter of the :TUNE command is
ignored.
ACTION No action is required, as the minclockcycle parameter of
:TUNE is ignored by the operating system.
---------------------------------------------------------------------------------------
208 MESSAGE Programmatic :SHOWCACHE.
MODE CM and NM incompatibility detected by MPT (severity level
ERROR) and RTM (Event Class 2).
CAUSE HP-PA features include complete operating system management
of all cache activities. Programmatic control of cache
activities is not allowed. MPE V/E cache management
commands, including the :SHOWCACHE command are not supported
on MPE/iX.
ACTION Remove all :SHOWCACHE invocations and dependent code.
---------------------------------------------------------------------------------------
209 MESSAGE Programmatic :CACHECONTROL.
MODE CM and NM incompatibility detected by MPT (severity level
ERROR) and RTM (Event Class 2).
CAUSE HP-PA features include complete operating system management
of all cache activities. Programmatic control of cache
activities is not allowed. In addition, BLOCKONWRITE on a
system-wide basis is not supported on MPE/iX. MPE V/E cache
management commands, including the :CACHECONTROL command, are
not supported on MPE/iX.
ACTION Remove all :CACHECONTROL invocations and dependent code.
BLOCKONWRITE on a file-by-file basis is available through the
FSETMODE intrinsic.
---------------------------------------------------------------------------------------
210 MESSAGE Programmatic :STARTCACHE.
MODE CM and NM Mode incompatibility detected by MPT (severity
level ERROR) and RTM (Event Class 2).
CAUSE HP-PA features include complete operating system management
of all cache activities. Programmatic control of cache
activities is not allowed. MPE V/E cache management
commands, including the :STARTCACHE command, are not
supported on MPE/iX.
ACTION Remove all :STARTCACHE invocations and dependent code.
---------------------------------------------------------------------------------------
211 MESSAGE Programmatic :STOPCACHE.
MODE CM and NM incompatibility detected by MPT (severity level
ERROR) and RTM (Event Class 2).
CAUSE HP-PA features include complete operating system management
of all cache activities. Programmatic control of cache
activities is not allowed. MPE V/E cache management
commands, including the :STOPCACHE command, are not supported
on MPE/iX.
ACTION Remove all :STOPCACHE invocations and dependent code.
---------------------------------------------------------------------------------------
215 MESSAGE Programmatic :SHOWCOM.
MODE CM and NM event detected by MPT (severity level ERROR) and
RTM (Event Class 2).
CAUSE Modifications have been made to the attached peripheral
environment of MPE/iX; the Intelligent Network Processor
(INP) and the associated :SHOWCOM command are not supported
on MPE/iX.
ACTION Remove all :SHOWCOM invocations and dependent code. Evaluate
your original need for :SHOWCOM and determine alternative
solutions. Equivalent functionality may be available through
the NS3000/XL subsystem.
---------------------------------------------------------------------------------------
216 MESSAGE Programmatic :DSCONTROL.
MODE CM and NM event detected by MPT (severity level ERROR) and
RTM (Event Class 2).
CAUSE Modifications have been made to the attached peripheral
environment of MPE/iX, resulting in the DS/3000 subsystem
being replaced on MPE/iX with the NS3000/XL subsystem (an
enhanced version of the NS3000/V subsystem available on MPE
V/E). The :DSCONTROL command is not supported on MPE/iX.
ACTION Remove all :DSCONTROL invocations and dependent code.
Evaluate your original need for :DSCONTROL and determine
alternative solutions, for example, the :NSCONTROL command
currently available through the NS3000/V subsystem. In
addition, equivalent functionality may be available through
the NS3000/XL subsystem.
---------------------------------------------------------------------------------------
217 MESSAGE Programmatic :STARTSESS.
MODE CM and NM event detected by MPT (severity level POSSIBLE) and
RTM (Event Class 2).
CAUSE Modifications have been made to the attached peripheral
environment of MPE/iX; the following termtypes are not
supported: 4, 6, 12, 13, 14, 15, 16, 19, and 20. The
required logonstring parameter of the :STARTSESS command may
specify an unsupported termtype.
ACTION If the required logonstring parameter of :STARTSESS includes
a termtype, you may have to modify the variable passed
through logonstring to specify a supported termtype (10, 18,
21, and 22).
---------------------------------------------------------------------------------------
218 MESSAGE Programmatic :SPEED.
MODE CM and NM event detected by MPT (severity level POSSIBLE) and
RTM (Event Class 2).
CAUSE Modifications have been made to the attached peripheral
environment of MPE/iX; the following baud rates are not
supported: 110, 150, and 600. The :SPEED command uses a
baud rate.
ACTION Modify only the :SPEED invocations that specify the
unsupported baud rates listed above, replacing unsupported
baud rates with supported baud rates.
---------------------------------------------------------------------------------------
250 MESSAGE Error numbers returned by the COMMAND intrinsic may be
different.
MODE CM and NM incompatibility detected by MPT (severity level
WARNING), OCA, and RTM (Event Class 2). When RTM detects
events 250, 251, and 252, only event 250 is actually logged
to a system log file located on disk. This minimizes disk
space consumption associated with each detected invocation of
the COMMAND intrinsic.
CAUSE Because of differences between HP-PA and the architecture of
MPE-V/E based computer systems, a few MPE V/E Command
Interpreter (CI) error numbers and their associated messages
have been replaced on MPE/iX with more precise error numbers
and messages. The required error parameter of the COMMAND
intrinsic may , in a very few cases, return a different CI
error number on an MPE/iX-based computer system than it would
on an MPE V/E-based computer system for the same type of
error.
ACTION If you have code that relies upon specific non-zero values
returned in the required error parameter of COMMAND, you may
have to modify your code. Analyze your source code and list
the error numbers upon which your MPE V/E code relies. When
MPE/iX error numbers are available, check for
incompatibilities. In addition, if this event is logged by
RTM, analyze your code to determine whether the
incompatibility is associated with event 250, 251, or 252.
---------------------------------------------------------------------------------------
251 MESSAGE The meaning of the value returned in param has changed for
the COMMAND intrinsic.
MODE CM and NM incompatibility detected by MPT (severity level
POSSIBLE) and OCA. If RTM logs event 250, event 251 may apply
to the event detected by RTM. Analyze your code to determine
if this is the case.
CAUSE Because of enhancements to the MPE/iX operating system, a
value returned by the required param parameter of the COMMAND
intrinsic has a different interpretation on MPE/iX than it
does on MPE V/E. On MPE V/E, a positive value n less than 12
indicates that an error occurred in the nth parameter of the
character array passed through the comimage parameter; a
positive value greater than 12 is a file system error number.
On MPE/iX, a negative value indicates the character position
within the comimage array which contains the first character
of the parameter where an error occurred; a positive value
indicates a file system error number.
ACTION If you have code that relies upon the value returned by the
param parameter of COMMAND, determine what, if any, changes
you need to make.
---------------------------------------------------------------------------------------
252 MESSAGE COMMAND intrinsic supports process creation on MPE/iX.
MODE CM and NM incompatibility detected by MPT (severity level
POSSIBLE) and OCA. If RTM logs event 250, event 252 may apply
to the event detected by RTM. Analyze your code to determine
if this is the case.
CAUSE Because of enhancements to the MPE/iX operating system, you
can use the COMMAND intrinsic to invoke commands that create
processes, for example, :RUN, :SEGMENTER, and so forth.
ACTION If your program is using the COMMAND intrinsic to invoke a CI
command that has been input by a user, you should investigate
whether or not you want the user to invoke process creation
commands not allowed on MPE V/E.
---------------------------------------------------------------------------------------
300 MESSAGE Some FFILEINFO intrinsic item values may not be valid on
MPE/iX.
MODE CM and NM incompatibility detected by MPT (severity level
POSSIBLE) and OCA.
CAUSE Some values returned in the optional itemvalue parameter of
the FFILEINFO intrinsic either have modified meanings or have
no meaning on an MPE iX-based computer system. Affected
itemvalues are those associated with the following values
passed in an associated itemnums parameter: 5, 7, 13, 15,
16, 40, 41, 42, 44, 47, 48, and 49.
ACTION If OCA or MPT reports this event, enable Event Class 3 of RTM
to detect when FFILEINFO returns one of the itemvalues listed
above. Check for event numbers 305 through 349 which
indicate that RTM detected that FFILEINFO returned a modified
or meaningless itemvalue.
---------------------------------------------------------------------------------------
305 MESSAGE FFILEINFO intrinsic itemvalue 5 device type/subtype.
MODE CM and NM incompatibility detected by MPT (severity level
WARNING) and RTM (Event Class 3).
CAUSE When the specified file is a standard disk file (as opposed
to a KSAM, RIO, or CIR disk file), MPE/iX does not
distinguish between the supported disk devices' device types.
In this specific case, the value returned by itemvalue 5
always represents device type 3, subtype 8 (indicating a 793X
disk drive).
ACTION If the standard disk file specified in the FFILEINFO call
will not reside on a 793X disk drive, you must remove
dependency upon itemvalue 5.
---------------------------------------------------------------------------------------
306 MESSAGE FFILEINFO intrinsic - Item 6 (ldev) may be invalid for disk.
MODE CM and NM incompatibility detected by MPT (severity level
WARNING) and RTM (Event Class 3).
CAUSE When the specified file is a standard disk file (as opposed
to a KSAM, RIO, or CIR disk file), MPE/iX returns the logical
device number where the disk file's file label resides. This
may not be the same logical device that contains the file's
data.
ACTION If your code relies upon the disk file label's logical device
number being the same as the logical device number for the
file's data, you will have to modify your code to remove this
dependency.
---------------------------------------------------------------------------------------
307 MESSAGE FFILEINFO intrinsic itemvalue 7 hardware device address.
MODE CM and NM incompatibility detected by MPT (severity level
WARNING) and RTM (Event Class 3).
CAUSE MPE/iX does not support the DRT number/unit number hardware
address. When the specified file is located on a disk, the
value returned by itemvalue 7 always represents DRT number 8,
unit number 0, meaningless values. For MPE/iX disk files,
the DRT number/unit number representation for a hardware
device address has been replaced by device path, available
through itemvalue 75 of the FFILEINFO intrinsic.
ACTION Remove dependency upon itemvalue 7 of FFILEINFO. Evaluate why
your program used this value. You may be able to perform an
equivalent action using the device path returned by itemvalue
75 of FFILEINFO.
---------------------------------------------------------------------------------------
313 MESSAGE FFILEINFO intrinsic itemvalue 13 physical I/O count.
MODE CM and NM incompatibility detected by MPT (severity level
POSSIBLE) and RTM (Event Class 3).
CAUSE Because of enhancements to the MPE/iX operating system, the
value returned by itemvalue 13 of the FFILEINFO intrinsic is
the buffered physical count of data blocks transferred. If
the file was opened using other than buffered access (for
example, NOBUF), the value returned will not be meaningful.
ACTION If your code relies upon itemvalue 13 of FFILEINFO returning
the physical I/O count for unbuffered files, you must remove
dependency on physical I/O count.
---------------------------------------------------------------------------------------
315 MESSAGE FFILEINFO intrinsic - Item 15 extent size.
MODE CM and NM incompatibility detected by MPT (severity level
WARNING) and RTM (Event Class 3).
CAUSE On MPE/iX, the file system manages extent allocation, where
variable numbers of extents, each of variable size, are
allocated based on need. There is no fixed extent size for a
file. Extent information specified at file creation is
meaningless on an MPE/iX-based computer system and is stored
in the file label only to maintain backward compatibility
with MPE V/E-based computer systems. Therefore, itemvalue 15
of the FFILEINFO intrinsic returns a value that is
meaningless on MPE/iX.
ACTION If your code relies upon the extent size returned by
itemvalue 15 of FFILEINFO, you will have to modify your code
to remove dependency upon extent size.
---------------------------------------------------------------------------------------
316 MESSAGE FFILEINFO intrinsic - Item 16 maximum number of extents.
MODE CM and NM incompatibility detected by MPT (severity level
WARNING) and RTM (Event Class 3).
CAUSE On MPE/iX, the file system manages extent allocation, where
variable numbers of extents, each of variable size, are
allocated based on need. There is no practical limit to the
number of extents for a file. Extent information specified
at file creation is meaningless on an MPE/iX-based computer
system and is stored in the file label only to maintain
backward compatibility with MPE V/E-based computer systems.
Therefore, itemvalue 16 of the FFILEINFO intrinsic returns a
value that is meaningless on MPE/iX.
ACTION If your code relies upon the number of extents returned by
itemvalue 16 of FFILEINFO, you will have to modify your code
to remove dependency upon number of extents.
---------------------------------------------------------------------------------------
319 MESSAGE FFILEINFO intrinsic - Item 19 (flabel disk sec addr) returns
0.
MODE CM and NM incompatibility detected by MPT (severity level
WARNING) and RTM (Event Class 3).
CAUSE When the specified file is a standard disk file (as opposed
to a KSAM, RIO, or CIR disk file), the file label disk sector
address returned in itemvalue 19 of the FFILEINFO intrinsic
has no meaning, but always returns a 0. This itemvalue is
kept only to maintain backward compatibility with MPE
V/E-based computer.
ACTION If your code relies upon the file label disk sector address
returned by itemvalue 19 of FFILEINFO, you will have to
modify your code to remove this dependency.
---------------------------------------------------------------------------------------
340 MESSAGE FFILEINFO intrinsic - Item 40 disk device status.
MODE CM and NM incompatibility detected by MPT (severity level
WARNING) and RTM (Event Class 3).
CAUSE When the specified file is a standard disk file (as opposed
to a KSAM, RIO, or CIR disk file), the disk device status
returned in itemvalue 40 of the FFILEINFO intrinsic has no
meaning, but always returns a 0. This itemvalue is kept only
to maintain backward compatibility with MPE V/E-based
computer systems.
ACTION If your code relies upon the disk device status returned by
itemvalue 40 of FFILEINFO, you will have to modify your code
to remove the dependency.
---------------------------------------------------------------------------------------
341 MESSAGE FFILEINFO intrinsic - Item 41 device type.
MODE CM and NM incompatibility detected by MPT (severity level
WARNING) and RTM (Event Class 3).
CAUSE When the specified file is a standard disk file (as opposed
to a KSAM, RIO, or CIR disk file), MPE/iX does not
distinguish between the supported disk devices' device types.
In this specific case, the value returned by itemvalue 41 of
the FFILEINFO intrinsic always represents device type 3
(indicating a 79xx disk drive).
ACTION If the standard disk file specified in the FFILEINFO call
will not reside not a 79xx disk drive, you must remove
dependency upon itemvalue 41.
---------------------------------------------------------------------------------------
342 MESSAGE FFILEINFO intrinsic - Item 42 device subtype.
MODE CM and NM incompatibility detected by MPT (severity level
WARNING) and RTM (Event Class 3).
CAUSE When the specified file is a standard disk file (as opposed
to a KSAM, RIO, or CIR disk file), MPE/iX does not
distinguish between the supported disk devices' device types.
In this specific case, the value returned by itemvalue 42
always represents device subtype 8 (indicating a 793x disk
drive).
ACTION If the standard disk file specified in the FFILEINFO call
will not reside not a 793x disk drive, you must remove
dependency upon itemvalue 42.
---------------------------------------------------------------------------------------
344 MESSAGE FFILEINFO intrinsic - Item 44 last extent allocated.
MODE CM and NM incompatibility detected by MPT (severity level
WARNING) and RTM (Event Class 3).
CAUSE Because of enhancements to the MPE/iX operating system,
itemvalue 44 of the FFILEINFO intrinsic returns a value that
represents the number of extents that have been accessed
during the current open. On MPE V/E-based computer systems,
this same itemvalue returns the cardinal number of the last
extent accessed.
ACTION If your code relies upon the information returned in
itemvalue 44 of FFILEINFO, you will have to either remove the
dependency or modify your code to rely upon the MPE/iX
interpretation of itemvalue 44.
---------------------------------------------------------------------------------------
347 MESSAGE FFILEINFO intrinsic - Item 47 DRT number.
MODE CM and NM incompatibility detected by MPT (severity level
WARNING) and RTM (Event Class 3).
CAUSE MPE/iX does not support the DRT number/unit number hardware
address. When the specified file is located on a disk, the
value returned in itemvalue 47 of the FFILEINFO intrinsic
always represents DRT number 8, a meaningless value. For
MPE/iX disk files, the DRT number/unit number representation
for a hardware device address has been replaced by device
path, available through itemvalue 75 of FFILEINFO.
ACTION Remove dependency upon itemvalue 47 of FFILEINFO. Evaluate
why your program used this value. You may be able to perform
an equivalent action using the device path returned by
itemvalue 75 of FFILEINFO.
---------------------------------------------------------------------------------------
348 MESSAGE FFILEINFO intrinsic - Item 48 device unit number.
MODE CM and NM incompatibility detected by MPT (severity level
WARNING) and RTM (Event Class 3).
CAUSE MPE/iX does not support the DRT number/unit number hardware
address. When the specified file is located on a disk, the
value returned the value returned by itemvalue 48 of the
FFILEINFO intrinsic always represents unit number 0, a
meaningless value. For MPE/iX disk files, the DRT
number/unit number representation for a hardware device
address has been replaced by device path, available through
itemvalue 75 of FFILEINFO.
ACTION Remove dependency upon itemvalue 48 of FFILEINFO. Evaluate
why your program used this value. You may be able to perform
an equivalent action using the device path returned by
itemvalue 75 of FFILEINFO.
---------------------------------------------------------------------------------------
349 MESSAGE FFILEINFO intrinsic - Item 49 software interrupt plabel (MSG
files).
MODE NM incompatibility detected by MPT (severity level WARNING)
and RTM (Event Class 3).
CAUSE HP-PA is a 32-bit architecture, while the architecture of MPE
V/E-based computer systems is a 16-bit architecture. In NM,
memory addresses represented as pointers or plabels must be
32-bit entities, while in MPE V/E and in CM, pointers and
plabels must be 16-bit entities. An integer equivalent to a
plabel of a software interrupt handler is returned in
itemvalue 49 of the FFILEINFO intrinsic.
ACTION Redeclare the variable you use to hold the value returned by
itemvalue 49 of FFILEINFO to be a 32-bit entity.
---------------------------------------------------------------------------------------
400 MESSAGE Some FGETINFO intrinsic item values may not be valid on
MPE/iX.
MODE CM and NM incompatibility detected by MPT (severity level
POSSIBLE) and OCA.
CAUSE The values returned in the optional devtype, hdaddr,
physcount, extsize, and numextents parameters of the FGETINFO
intrinsic have either modified meanings or no meaning on an
MPE/iX-based computer system.
ACTION If MPT or OCA reports this event, enable Event Class 4 of RTM
to detect when FGETINFO returns one of the optional
parameters listed above. Check for event numbers 405 through
416, which indicate that RTM detected that FGETINFO returned
a modified or meaningless parameter value.
---------------------------------------------------------------------------------------
405 MESSAGE FGETINFO intrinsic devtype parameter.
MODE CM and NM incompatibility detected by MPT (severity level
WARNING) and RTM (Event Class 4).
CAUSE When the specified file is a standard disk file (as opposed
to a KSAM, RIO, or CIR disk file), MPE/iX does not
distinguish between the supported disk devices' device types.
In this specific case, the value returned by the optional
devtype parameter of the FGETINFO intrinsic always represents
device type 3, subtype 8 (indicating a 793x disk drive).
ACTION If the standard disk file specified in the FGETINFO call will
not reside on a 793x disk drive, you must remove dependency
upon the devtype parameter.
---------------------------------------------------------------------------------------
407 MESSAGE FGETINFO intrinsic hdaddr parameter.
MODE CM and NM incompatibility detected by MPT (severity level
WARNING) and RTM (Event Class 4).
CAUSE MPE/iX does not support the DRT number/unit number hardware
address. When the specified file is located on a disk, the
value returned by the optional hdaddr parameter of the
FGETINFO intrinsic always represents DRT number 8, unit
number 0. For MPE/iX disk files, the DRT number/unit number
representation for a hardware device address has been
replaced by device path, available through itemvalue 75 of
the FFILEINFO intrinsic.
ACTION Remove dependency upon the hdaddr parameter of FGETINFO.
Evaluate why your program used this value. You may be able
to perform an equivalent action using the device path
returned by itemvalue 75 of FFILEINFO.
---------------------------------------------------------------------------------------
413 MESSAGE FGETINFO intrinsic physcount parameter.
MODE CM and NM incompatibility detected by MPT (severity level
POSSIBLE) and RTM (Event Class 4).
CAUSE Because of enhancements to the MPE/iX operating system, the
value returned by the optional physcount parameter of the
FGETINFO intrinsic is the buffered physical count of data
blocks transferred. If the file was opened using other than
buffered access (for example, NOBUF), the value returned will
not be meaningful.
ACTION If your code relies upon the physcount parameter of FGETINFO
returning the physical I/O count for unbuffered files, you
must remove dependency on physical I/O count.
---------------------------------------------------------------------------------------
415 MESSAGE FGETINFO intrinsic extsize parameter.
MODE CM and NM incompatibility detected by MPT (severity level
WARNING) and RTM (Event Class 4).
CAUSE On MPE/iX, the file system manages extent allocation, where
variable numbers of extents, each of variable size, are
allocated based on need. There is no fixed extent size for a
file. Extent information specified at file creation is
meaningless on an MPE/iX-based computer system and is stored
in the file label only to maintain backward compatibility
with MPE V/E-based computer systems. Therefore, the optional
extsize parameter of the FGETINFO intrinsic returns a value
that is meaningless on MPE/iX.
ACTION If your code relies upon the extent size returned by the
extsize parameter of FGETINFO, you will have to modify your
code to remove dependency upon extent size.
---------------------------------------------------------------------------------------
416 MESSAGE FGETINFO intrinsic numextents parameter.
MODE CM and NM incompatibility detected by MPT (severity level
WARNING) and RTM (Event Class 4).
CAUSE On MPE/iX, the file system manages extent allocation, where
variable numbers of extents, each of variable size, are
allocated based on need. There is no practical limit to the
number of extents for a file. Extent information specified
at file creation is meaningless on an MPE/iX-based computer
system and is stored in the file label only to maintain
backward compatibility with MPE V/E-based computer systems.
Therefore, the optional numextents parameter of the FGETINFO
intrinsic returns a value that is meaningless on MPE/iX.
ACTION If your code relies upon the number of extents returned by
the numextents parameter of FGETINFO, you will have to modify
your code to remove dependency upon number of extents.
---------------------------------------------------------------------------------------
500 MESSAGE Some FCONTROL intrinsic controlcodes are not valid on MPE/iX.
MODE CM and NM incompatibility detected by MPT (severity level
POSSIBLE) and OCA.
CAUSE Some values that may be contained in the required param
parameter of the FCONTROL intrinsic have either been modified
or have no meaning on an MPE/ iX-based computer system.
Affected params are those associated with controlcodes 3 and
48.
ACTION If MPT or OCA reports this event, enable Event Class 5 of RTM
to detect when FCONTROL calls controlcode 3 and 48.
---------------------------------------------------------------------------------------
503 MESSAGE FCONTROL intrinsic controlcode 3 Read hardware status word.
MODE CM and NM incompatibility detected by MPT (severity level
ERROR) and RTM (Event Class 5).
CAUSE Because of differences between HP-PA and the architecture of
MPE V/E-based computer systems, the system hardware status
word returned by FCONTROL has no meaning on MPE/iX. A
meaningless value is returned in the required param parameter
of the FCONTROL intrinsic when a value of 3 is passed in
required controlcode parameter.
ACTION Remove dependencies upon controlcode 3 of FCONTROL.
---------------------------------------------------------------------------------------
548 MESSAGE FCONTROL intrinsic controlcode 48 Enable/Disable software
interrupts.
MODE NM incompatibility detected by MPT (severity level WARNING)
and RTM (Event Class 5).
CAUSE HP-PA is a 32-bit architecture, while the architecture of MPE
V/E-based computer systems is a 16-bit architecture. In NM,
memory addresses represented as pointers or plabels must be
32-bit entities, while in MPE V/E and in CM, pointers and
plabels must be 16-bit entities. The plabel of a software
interrupt handler may be passed through the required param
parameter of FCONTROL if the required controlcode parameter
passes the value 48.
ACTION Redeclare the variable you pass through the param parameter
of FCONTROL to be a 32-bit entity when you also pass a
controlcode value of 48.
---------------------------------------------------------------------------------------
601 MESSAGE The PTAPE intrinsic is not available on MPE/iX.
MODE CM and NM incompatibility detected by MPT (severity level
ERROR), OCA, and RTM (Event Class 6).
CAUSE Modifications have been made to the attached peripheral
environment of MPE/iX, resulting in paper tape readers being
unsupported on MPE/iX-based computer systems. The PTAPE
intrinsic is not supported on MPE/ iX-based computer systems.
ACTION Remove all PTAPE invocations and dependent code. If you are
using PTAPE for uses other than reading from paper tape
devices, you must determine the original need for the call to
PTAPE and develop alternative solutions.
---------------------------------------------------------------------------------------
602 MESSAGE The FCARD intrinsic is not available on MPE/iX.
MODE CM and NM incompatibility detected by MPT (severity level
ERROR), OCA , and RTM (Event Class 6).
CAUSE Modifications have been made to the attached peripheral
environment of MPE/iX; the HP 7260 series of card readers is
not supported on MPE/iX-based computer systems. Because the
FCARD intrinsic accesses only these card readers, FCARD
likewise is not supported on MPE/iX.
ACTION Remove all FCARD invocations and dependent code.
---------------------------------------------------------------------------------------
604 MESSAGE FDEVICECONTROL intrinsic controlcode parameter value of 192.
MODE CM and NM incompatibility detected by MPT (severity level
WARNING) and OCA.
CAUSE FDEVICECONTROL with controlcode of 192 is used for devices
connected through the terminal subsystem. Modifications have
been made to the terminal subsystem of MPE/iX, resulting in
FDEVICECONTROL being unsupported for these devices on the 1.0
version of MPE/iX-based computer systems.
ACTION If you are migrating to the 1.0 release of MPE/iX, remove all
FDEVICECONTROL calls using a controlcode of 192 and dependent
code. Evaluate your original need for FDEVICECONTROL and
determine alternative solutions. Some of the functions of
such calls are no longer necessary; for example, changes to
ENQ/ACK protocol are not needed since this protocol is not
used on MPE/iX. Other functions that FDEVICECONTROL provides
are also available through the FCONTROL intrinsic, such as
using parity checking and setting new values for the
Subsystem Break or Alternate End-of-Record.
On release 1.1 or later, FDEVICECONTROL with control code 192
and its dependent codes is implemented as on MPE V, with the
exception of Alternate End-of-Record. On MPE V systems, you
are allowed to designate multiple AEOR characters for a
single device. MPE/iX, however, allows you to designate only
one AEOR character for a device at any given time.
Modifications may be necessary to provide only one AEOR
character in existing code. For more information refer to
MPE XL Asynchronous Serial Communications Programmer's
Reference Manual (32022-90012) for further information.
---------------------------------------------------------------------------------------