HP 3000 Manuals HP 3000 Manuals
(Subsystem 143) (contd)
1034 MESSAGE The reserved file for the Current Working
Directory has become corrupted. (FILE SYSTEM ERROR
-1034)
CAUSE The file system could not get a pointer to the CWD
reserved file.
ACTION Abort and restart the process.
---------------------------------------------------------------
1035 MESSAGE Directory services encountered a security
violation while trying to traverse the specified
path. (FILE SYSTEM ERROR -1035)
CAUSE The user lacks access to or through one of the
directory nodes.
ACTION Have the system manager grant the user access to
the offending directory.
---------------------------------------------------------------
1036 MESSAGE The caller lacks traverse access to one of the
HFS path directory components. (FILE SYSTEM ERROR
-1036)
CAUSE The user is not granted TD access to one or more of
the components in the path.
ACTION Have the system adminstrator grant TD access to
this user.
---------------------------------------------------------------
1037 MESSAGE The caller lacks the ability to delete entries
from the target directory. (FILE SYSTEM ERROR
-1037)' \CAUSE\The user does not have DD access to
the parent directory.
ACTION Have the system adminstrator grant DD access to
this user.
---------------------------------------------------------------
1038 MESSAGE The caller lacks the ability to create entries in
the target directory. (FILE SYSTEM ERROR -1038)
CAUSE The user lacks CD access to the parent directory or
does not have SF capability.
ACTION Have the system administrator grant sufficient
access.
---------------------------------------------------------------
1039 MESSAGE The volume set indicated by the directory mount
record is not available. (FILE SYSTEM ERROR -1039)
CAUSE The volume set is not mounted or the disk drive is
not turned on.
ACTION Mount the necessary volumes and make sure the
drive(s) are functioning.
---------------------------------------------------------------
1040 MESSAGE Directory services encountered an error while
trying to update the file label. (FILE SYSTEM
ERROR -1040)
CAUSE An error occurred during a file label update.
ACTION File an SR.
---------------------------------------------------------------
1041 MESSAGE An empty path was provided to the directory
services. (FILE SYSTEM ERROR -1041)
CAUSE The caller provided an empty path.
ACTION Provide a non-empty path.
---------------------------------------------------------------
1042 MESSAGE Directory services detected that a component of
the path has a name length which exceeds the
maximum for that directory. (FILE SYSTEM ERROR
-1042)
CAUSE A name exceeds the directory specific name length
limit.
ACTION Provide a shorter name.
---------------------------------------------------------------
1043 MESSAGE An attempt was made to insert a name greater than
16 characters into the root, an account, or a
group. (FILE SYSTEM ERROR -1043)
CAUSE The caller specified a name greater than 16
characters in an MPE directory component.
ACTION Provide a name less than or equal to 16 characters.
---------------------------------------------------------------
1044 MESSAGE An illegal attempt was made to purge a file that
was opened by UFID. (FILE SYSTEM ERROR -1044)
CAUSE The caller opened the file by UFID, then did an
FCLOSE purge.
ACTION To purge this file, it must be opened with a name.
---------------------------------------------------------------
1046 MESSAGE The IOWAIT type manager layer requests the
intrinsic layer to requeue the present I/O and
retry the IOWAIT. (FILE SYSTEM ERROR -1046)
CAUSE The type manager is unable to process the I/O at
this time.
ACTION No action is necessary.
---------------------------------------------------------------
1047 MESSAGE Incompatible version of the file.
CAUSE The FOPEN/HPFOPEN request has been denied because
the version of the file is not compatible with the
version of the operating system.
ACTION On a 5.0 or later system, copy the KSAM/XL file to
another file specifying DEFBLK to create a
compatible version of the file. Then, copy the
newly created file to the pre-5.0 system
---------------------------------------------------------------
1050 MESSAGE TM_REC_TOO_SHORT: The record specified for
writing is too short.
CAUSE The record does not have all the keys present.
ACTION Specify a larger record with all the keys present.
---------------------------------------------------------------
1051 MESSAGE TM_NONSEQ_WRITE: This error indicates that the
current FWRITE had a primary key which was not in
sequential order when compared with the previous
FWRITE.
CAUSE A write was attempted with the primary key not in
sequential order when compared with the previous
write.
ACTION Change the order in which the records are written
to the file so that the primary key is always in
sequential order. Or rebuild the file and specify
the SEQ flag to be false.
---------------------------------------------------------------
1052 MESSAGE TM_DUP_KEY_DISALLOWED: An attempt was made to
insert a duplicate key to an index which disallows
duplicate keys.
CAUSE One of the indexes in the file has the DUP flag set
to false; however, an attempt was made to insert a
key which already existed in that index.
ACTION Modify the record so that the key is not a
duplicate of a previous record; or create the file
with the index DUP flag set to TRUE.
---------------------------------------------------------------
1054 MESSAGE TM_KSM_CBLOCK_FAILED:An error was detected while
scanning the B TREE where the information relating
to the user specified keys is kept.
CAUSE This error is not currently used.
ACTION Nothing.
---------------------------------------------------------------
1055 MESSAGE TM_KEY_NOT_FOUND: The user specified key cannot
be found in the index area of the KSAM XL file.
CAUSE The user may have specified a key that does not
exist in the KSAM XL file.
ACTION Use a valid key specification.
---------------------------------------------------------------
1056 MESSAGE TM_PRIM_KEY_CHANGED: An FUPDATE call attempted to
modify the primary key value.
CAUSE The file was opened for sequential processing and
the primary key was changed while doing an FUPDATE.
ACTION Check the record to be written to make sure the
primary key in not changed. Compare the buffer
that was FREAD from the file to the buffer that you
are passing to FUPDATE.
---------------------------------------------------------------
1057 MESSAGE TM_KEY_SEARCH_ERROR: An error was detected while
scanning the B TREE where the information relating
to the user specified keys is kept.
CAUSE The internal B TREE structure is corrupted.
ACTION Close the KSAM XL file, store it to tape, and
contact your HP Support Representative.
---------------------------------------------------------------
1058 MESSAGE TM_XM_START_SYS_TRANS_FAILED: A system
transaction could not be started.
CAUSE This is probably due to an MPE/iX operating system
defect.
ACTION Take a memory dump and contact your HP Support
Representative.
---------------------------------------------------------------
1059 MESSAGE TM_XM_END_SYS_TRANS_FAILED: A system transaction
could not be terminated.
CAUSE This is probably due to an MPE/iX operating system
defect.
ACTION Take a memory dump and contact your HP Support
Representative.
---------------------------------------------------------------
1060 MESSAGE TM_RECORD_DELETED: The particular record in
question was deleted.
CAUSE An attempt was made to read or update or delete a
record which was deleted.
ACTION When positioning the data pointer before the read,
make sure the pointer is not positioned to a
deleted record.
---------------------------------------------------------------
1061 MESSAGE TM_BTREE_INTERNAL_ERROR: An error was detected
while scanning the B TREE where the information
relating to the user specified keys is kept.
CAUSE The internal B TREE sturucture is corrupted.
ACTION The KSAM XL file is corrupted. Close the KSAM
file, store it to tape, and contact your HP Support
Representative.
---------------------------------------------------------------
1062 MESSAGE TM_OUT_OF_INDEX_SPACE: The space reserved for the
index area in the file is full and has reached the
start of the data area.
CAUSE The B TREE is probably very sparsely filled.
ACTION FCOPY the KSAM XL file to another KSAM XL file.
This should make more efficient use of the index
blocks. If that fails, build the KSAM XL file with
a larger file limit.
---------------------------------------------------------------
1063 MESSAGE TM_INVALID_KEY_SPECIFIED: The key specification
provided by the user is not a valid one.
CAUSE The key specified in a procedure such as FREADBYKEY
does not match the one specified in building the
file.
ACTION Check the key specified in the procedure call to
FREADBYKEY or FFINDBYKEY.
---------------------------------------------------------------
1065 MESSAGE TM_FFIND_FAILED: An FFINDN failed based on the
relative record number specified.
CAUSE The relative record number specified was greater
than the largest relative record number in the B
TREE.
ACTION Check the second parameter in the call to FFINDN
specifying the relative record number.
---------------------------------------------------------------
1066 MESSAGE TM_DUP_KEY_FOUND: Duplicate keys were found for
the key currently being specified.
CAUSE The detection of the existence of duplicate keys is
specificaly performed for COBOL in FREAD and
FREADBYKEY intrinsics called by COBOL.
ACTION This status will be returned to COBOL programs
only.
---------------------------------------------------------------
1067 MESSAGE TM_KSM_SPACE_FAILED: An error ocurred while doing
FSPACE.
CAUSE The displacement specified in the FSPACE parameter
is too large or too small.
ACTION Check the displacement specified in the FSPACE
parameter.
---------------------------------------------------------------
1068 MESSAGE TM_INVALID_INDEX_RRN: An error was detected in a
B TREE entry for location of a data record.
CAUSE The internal B TREE sturucture is corrupted.
ACTION Close this file and build a new file. Use FCOPY
specifying KEY=0 to rebuild a new KSAM XL file.
---------------------------------------------------------------
1069 MESSAGE TM_INVALID_DATA_PTR_CALCULATED: The position of
the data pointer computed is before the first data
record or after the end of file.
CAUSE The KSAM XL file is corrupted in the data pointer
of the index area.
ACTION Close the KSAM file, store it to tape, and contact
your HP Support Representative.
---------------------------------------------------------------
1070 MESSAGE TM_INVALID_REC_NUM: An invalid recnum was
specified in the call to a pointer positioning
procedure such as FPOINT, or FREADDIR.
CAUSE A relative record number specified is not valid,
either before the first record or beyond the last
record.
ACTION Specify a valid relative record number.
---------------------------------------------------------------
1071 MESSAGE TM_DPAGE_FIND_FAILED: An error occurred while
scanning for a data page with a vacant slot in it.
CAUSE All the data pages are used.
ACTION Close the file, build a new KSAM XL file with
similar characteristics and FREADC from the old
file and FWRITE into the new file.
---------------------------------------------------------------
1072 MESSAGE TM_KSM_NO_REC: The KSAM XL file is empty, no
records in the file.
CAUSE An attempt was made to read or modify a KSAM XL
file which has no active records in it.
ACTION Check the content of the file before accesssing it.
---------------------------------------------------------------
1073 MESSAGE TM_KSM_XM_ATTACH_FAILED: An error was detected
while trying to attach the file to the XM log.
CAUSE An internal MPE/iX error occurred.
ACTION Take a memory dump and call your HP Support
Representative.
---------------------------------------------------------------
1074 MESSAGE TM_KSM_INVALID_DATA_PTR: The logical data pointer
is currently incorrectly positioned.
CAUSE The logical data pointer is currently position
before the start of the data area or after the end
of file.
ACTION Do an FCLOSE followed by an FOPEN or do FPOINT to
reposition the data pointer.
---------------------------------------------------------------
1075 MESSAGE TM_KSM_INVALID_CHILD_PTR: An invalid child
pointer was detected in the index part of the file.
CAUSE The internal B TREE structure is corrupted.
ACTION Close the KSAM file, store it to tape, and call
your HP Support Representative.
---------------------------------------------------------------
1076 MESSAGE TM_KSM_CORRUPTED_FILE: During a previous KSAM
operation, the KSAM file was discovered to be
corrupt so that FWRITEs, FREMOVEs, and FUPDATEs are
disallowed.
CAUSE The internal B TREE structure is corrupted.
ACTION Close the KSAM file, store it to tape, and call
your HP Support Representative.
---------------------------------------------------------------
1077 MESSAGE The file system was unable to start a user
transaction under transaction management. (FILE
SYSTEM ERROR -1077)
CAUSE A call to transaction management failed.
ACTION Make sure the file is attached to XM, otherwise
file an SR.
---------------------------------------------------------------
1078 MESSAGE The file system was unable to end a user
transaction under transaction management. (FILE
SYSTEM ERROR -1078)
CAUSE A call to transaction management failed.
ACTION File an SR.
---------------------------------------------------------------
1079 MESSAGE An invalid offset value was provided for a
KSAM/XL file. (FILE SYSTEM ERROR -1079)
CAUSE The user supplied an invalid file offset.
ACTION Supply a valid offset value to the intrinsic.
---------------------------------------------------------------
1080 MESSAGE The KSAM/XL subsystem detected an unknown
internal error. (FILE SYSTEM ERROR -1080)
CAUSE An internal error was detected.
ACTION File an SR.
---------------------------------------------------------------
1110 MESSAGE The file system was unable to create the File I/O
State Table. (FILE SYSTEM ERROR -1110)
CAUSE The FIOST table could not be created.
ACTION File an SR.
---------------------------------------------------------------
1111 MESSAGE The file system was unable to initialize the File
I/O State Table. (FILE SYSTEM ERROR 1111)
CAUSE The FIOST table could not be initialized.
ACTION File an SR.
---------------------------------------------------------------
1112 MESSAGE The file system was unable to create the File I/O
State Semaphore Table. (FILE SYSTEM ERROR -1112)
CAUSE An error occurred while creating the FIOST
Semaphore Table.
ACTION File an SR.
---------------------------------------------------------------
1113 MESSAGE The file system was unable to initialize the File
I/O State Semaphore Table. (FILE SYSTEM ERROR
-1113)
CAUSE An error occurred while initializing the FIOST
Semaphore Table.
ACTION File an SR.
---------------------------------------------------------------
1500 MESSAGE An unexpected High-level IO error was encountered
while executing a tape IO request.
CAUSE Either the IO request was invalid, or the device is
not ready/accessible.
ACTION Make sure the requested IO operation is a valid
one, and the devcie is accessible for the process.
---------------------------------------------------------------
1501 MESSAGE An unexpected Low-level IO error was encountered
while executing the tape IO request.
CAUSE The device encountered an error during IO
execution. It could be a medium, device or
hardware error, or a driver internal error.
ACTION Make sure the medium and device are in a proper
state. For example, check for device power, tape
positioning, medium misload...etc... If nothing
wrong with the device and medium, then you should
contact Hewlett-Packard for support.
---------------------------------------------------------------
1502 MESSAGE A tape IO request failed because a write access
was denied.
CAUSE Either the medium is protected from write access,
or the process does not have write access to the
device.
ACTION Make sure the process has write access to the
device and the medium is not write protected.
---------------------------------------------------------------
1503 MESSAGE The device is not ready for executing this tape
IO request.
CAUSE Either the device is not online, or the device is
not in a state ready to execute this IO request.
ACTION Make sure the device is on line and the medium is
readily positioned.
---------------------------------------------------------------
1504 MESSAGE A tape IO request failed because the attempted
device operation is not supported by the operating
system.
CAUSE Either the requested device operation is not valid
for this device, or a file system internal error
was encountered.
ACTION Make sure the requested IO operation is valid for
this device. If so, contact Hewlett-Packard for
support.
---------------------------------------------------------------
1505 MESSAGE An attempt to backspace failed because the medium
is already positioned at its beginning.
CAUSE The device was positioning at the beginning of the
medium, an attempt to backspace the medium could
not be performed.
ACTION Do not try to backspace the medium when it is
positioned at its beginning.
---------------------------------------------------------------
1506 MESSAGE A tape IO operation failed because the end of the
medium was encountered.
CAUSE An attempt was made to execute a device operation
beyond the end of the medium.
ACTION Do not try to access the medium beyond the end of
tape mark. Rewind, mount another tape and try
again.
---------------------------------------------------------------