  | 
»  | 
 | 
  
 | 
 | 
- -20
 
 - MESSAGE
  Verification arrays wrongly specified.
 - CAUSE
  Verification arrays to PUT were incorrectly specified.
 - ACTION
  Pass all 3 or none.
 
 
 - -21
 
 - MESSAGE
  Bad overall status.
 - CAUSE
  The overall status was inaccessible for write access.
 - ACTION
  Check for uninitialized pointers.
 
 
 - -22
 
 - MESSAGE
  Bad item status.
 - CAUSE
  The item status was inaccessible for write access.
 - ACTION
  Check for uninitialized pointers.
 
 
 - -23
 
 - MESSAGE
  Bad verification item status.
 - CAUSE
  The verification item status was inaccessible for write access.
 - ACTION
  Check for uninitialized pointers.
 
 
 - -24
 
 - MESSAGE
  Verification failed.
 - CAUSE
  The verification for PUT failed.
 - ACTION
  Check the ver item statuses for more information.
 
 
 - -25
 
 - MESSAGE
  Incorrect user capability.
 - CAUSE
  The AIF procedure called is inaccessible with the specified
user id.
 - ACTION
  Purchase the referenced AIF product component.
 
 
 - -26
 
 - MESSAGE
  Non-existent AIF user ID.
 - CAUSE
  The user-id specified does not exist.
 - ACTION
  Use the user ID distributed when AIFs were purchased.
 
 
 - -27
 
 - MESSAGE
  Invalid search key.
 - CAUSE
  The AIFSYSWIDEGET search key is no longer valid.
 - ACTION
  Restart AIFSYSWIDEGET calls.
 
 
  |  
 - -28
 
 - MESSAGE
  Invalid JSNum.
 - CAUSE
  The job/session specified does not exist.
 - ACTION
  Verify if the JSNum exists.
 
 
 - -29
 
 - MESSAGE
  PID PIN mismatch encountered.
 - CAUSE
  The PID process has died and a new process with same PIN was born.
 - ACTION
  Check the PID and the PIN.
 
 
 - -30
 
 - MESSAGE
  Process has died.
 - CAUSE
  No process with this PIN exists on the system.
 - ACTION
  Check the PIN.
 
 
 - -31
 
 - MESSAGE
  The process is not of type user, or son, or CI.
 - CAUSE
  Attempt to PUT to a process of a type that is neither user
nor son.
 - ACTION
  Check the process type and the PIN/PID.
 
 
 - -32
 
 - MESSAGE
  Invalid accounting name.
 - CAUSE
  AIFACCTGET/PUT could not find the specified account name.
 - ACTION
  Verify the existence of the specified user, group, and account.
 
 
 - -33
 
 - MESSAGE
  Invalid Fnum for this process.
 - CAUSE
  The process does not have a file open with this Fnum.
 - ACTION
  Check the PID - Fnum combination.  Verify that the file is not 
   one of the unsupported types.  Unsupported file types include: sockets,
   remote files, null files, dummy files opened for KSAM, and dummy files 
   opened for datacomm.
 
 
 - -34
 
 - MESSAGE
  A device file was encountered where it is not supposed to be.
 - CAUSE
  Attempted to AIFxxGET or AIFxxPUT to a file of device type.
 - ACTION
  Check the file type and the Fnum-PID combination.
 
 
 - -35
 
 - MESSAGE
  The UFID does not correspond to the file specified.
 - CAUSE
  The Fnum was closed and a new file was opened with same fnum.
 - ACTION
  Check the list of open files using AIFPROCGET.
 
 
  |  
 - -36
 
 - MESSAGE
  Not a user file.
 - CAUSE
  Attempted to PUT to a file with designator, not user.
 - ACTION
  Check the file designator.
 
 
 - -37
 
 - MESSAGE
  A directory object was encountered.
 - CAUSE
  Attempted to PUT to a file that is actually a Dir. object.
 - ACTION
  Check for Dir Obj. in AIFFILEGET.
 
 
 - -38
 
 - MESSAGE
  Parameter 1 was badly aligned.
 - CAUSE
  Parameter 1 was not aligned on a word (4-byte) boundary.
 - ACTION
  Check for uninitialized pointers.
 
 
 - -39
 
 - MESSAGE
  Parameter 2 was badly aligned.
 - CAUSE
  Parameter 2 was not aligned on a word (4-byte) boundary.
 - ACTION
  Check for uninitialized pointers.
 
 
 - -40
 
 - MESSAGE
  Parameter 3 was badly aligned.
 - CAUSE
  Parameter 3 was not aligned on a word (4-byte) boundary.
 - ACTION
  Check for uninitialized pointers.
 
 
 - -41
 
 - MESSAGE
  Parameter 4 was badly aligned.
 - CAUSE
  Parameter 4 was not aligned on a word (4-byte) boundary.
 - ACTION
  Check for uninitialized pointers.
 
 
 - -42
 
 - MESSAGE
  Invalid UFID.
 - CAUSE
  The UFID parameter specified does not exist.
 - ACTION
  Verify the UFID used.
 
 
 - -43
 
 - MESSAGE
  Invalid file name.
 - CAUSE
  The file name specified does not exist.
 - ACTION
  Verify if the file name exists.
 
 
  |  
 - -45
 
 - MESSAGE
  Return array1 write probe failed.
 - CAUSE
  User does not have write access to the array passed in.
 - ACTION
  Check for uninitialized pointers and num_array_entry.
 
 
 - -46
 
 - MESSAGE
  Return array2 write probe failed.
 - CAUSE
  User does not have write access to the array passed in.
 - ACTION
  Check for uninitialized pointers and num_array_entry.
 
 
 - -47
 
 - MESSAGE
  Invalid AIF key.
 - CAUSE
  AIFSYSWIDEGET did not recognize the aif_area key.
 - ACTION
  Try 1000, 2000, 5000, 6000, 8000, or 11000.
 
 
 - -48
 
 - MESSAGE
  Creation of shareable object failed.
 - CAUSE
  Call to AIFGLOBACQ was unsuccessful.
 - ACTION
  Possibly out of transient disk space.
 
 
 - -49
 
 - MESSAGE
  Release of shareable object failed.
 - CAUSE
  Call to AIFGLOBREL was unsuccessful.
 - ACTION
  Verify that the object pointer is valid.
 
 
 - -50
 
 - MESSAGE
  Missing criteria arrays.
 - CAUSE
  AIFSYSWIDEGET AIF key specified requires criteria arrays.
 - ACTION
  Use itemnum_array, item_array,
item_status_array parameters.
 
 
 - -51
 
 - MESSAGE
  Bad pointer was encountered for parameter 1.
 - CAUSE
  The address passed was inaccessible to the caller.
 - ACTION
  Pass only addresses in accessible spaces. 
 
 
 - -52
 
 - MESSAGE
  Bad pointer was encountered for parameter 2.
 - CAUSE
  The address passed was inaccessible to the caller.
 - ACTION
  Pass only addresses in accessible spaces.
 
 
  |  
 - -53
 
 - MESSAGE
  Bad pointer was encountered for parameter 3.
 - CAUSE
  The address passed was inaccessible to the caller.
 - ACTION
  Pass only addresses in accessible spaces.
 
 
 - -54
 
 - MESSAGE
  Bad pointer was encountered for parameter 4.
 - CAUSE
  The address passed was inaccessible to the caller.
 - ACTION
  Pass only addresses in accessible spaces.
 
 
 - -55
 
 - MESSAGE
  AIFCLOSE failed.
 - CAUSE
  Either a bad file_number was specified, another file with the
same name already exists, an illegal disposition (5, 6, 7) exists, or
any outstanding write I/Os may have failed.
 - ACTION
  Use FCHECK to determine why AIFCLOSE failed.
 
 
 - -56
 
 - MESSAGE
  The address passed for the verification item number array is not
accessible to the caller.
 - CAUSE
  The address passed is inaccessible to the caller.
 - ACTION
  Pass only addresses in accessible spaces.
 
 
 - -57
 
 - MESSAGE
  The address passed for the verification items array is not
accessible to the caller.
 - CAUSE
  The address passed is inaccessible to the caller.
 - ACTION
  Pass only addresses in accessible spaces.
 
 
 - -58
 
 - MESSAGE
 The address is not properly aligned for the verification item
number to be accessed.
 - CAUSE
 The address is not properly aligned for the data type to be
accessed.
 - ACTION
  Pass only a variable that has the proper data alignment.
 
 
 - -59
 
 - MESSAGE
 The address is not properly aligned for the verification items
to be accessed.
 - CAUSE
  The address is not properly aligned for the data type to be
accessed.
 - ACTION
  Pass only a variable that has the proper data alignment.
 
 
 - -60
 
 - MESSAGE
 The address is not properly aligned for the verification item
statuses.
 - CAUSE
  The address is not properly aligned for the data type to be
accessed.
 - ACTION
  Pass only a variable that has the proper data alignment.
 
 
  |  
 - -61
 
 - MESSAGE
 Unable to access the file AIFKUF.PUB.SYS.
 - CAUSE
  The file is deleted, or there is not enough disk space to create it.
 - ACTION
  Create enough disk space, if needed. Reboot the machine.
 
 
 - -63
 
 - MESSAGE
  Parameter 5 was badly aligned.
 - CAUSE
  Parameter 5 was not aligned on a word (4-byte boundary).
 - ACTION
  Check for proper alignment before calling the AIF.
 
 
 - -64
 
 - MESSAGE
 Parameter 5 not accessible to caller.
 - CAUSE
  The address passed was inaccessible to the caller.
 - ACTION
  Pass only addresses in accessible spaces.
 
 
 - -65
 
 - MESSAGE
  Invalid Path Identifier. 
 - CAUSE
  The Path id parameter specified is not valid. 
 - ACTION
  Verify the Path id used.
 
 
 - -66
 
 - MESSAGE
  Invalid pathname. 
 - CAUSE
  The pathname specified does not exist in the directory. 
 - ACTION
  Verify the pathname used.
 
 
 - -67
 
 - MESSAGE
  Could not get the Current Working Directory file pointer.
 - CAUSE
  The CWD file is closed.
 - ACTION
  Check your application to make sure that you are not closing the
CWD file. 
 
 
 - -68
 
 - MESSAGE
  The pathname is too large for the buffer size specified. 
 - CAUSE
  The user defined a buffer which is too small to hold the pathname. 
 - ACTION
  Increase the buffer size. 
 
 
 - -69
 
 - MESSAGE
  Path passed is empty; first character is a terminator or path
length is 0. 
 - CAUSE
  The user passed in a pathname which is empty.
 - ACTION
  Check the application. 
 
 
  |  
 - -70
 
 - MESSAGE
 Cannot traverse the directory; a directory file has been opened
exclusively.
 - CAUSE
  A directory is opened exclusively, which is preventing directory
traversal.
 - ACTION
  Re-run the application when the directory file has been closed.
 
 
 - -71
 
 - MESSAGE
  Incorrect pathname syntax.
 - CAUSE
  The user has specified a pathname which is not a valid syntax.
 - ACTION
  Consult the MPE/iX Commands Reference Manual
              Volumes 1 and 2 (32650-90003 and 32650-90364)
              for a description of a valid pathname syntax.
 
 
 - -72
 
 - MESSAGE
  User/process lacks Traverse Directory permission on a directory
component.
 - CAUSE
  The user/process is lacking one of the required directory
permissions.
 - ACTION
   Assign the user the appropriate directory security access
rights.
 
 
 - -73
 
 - MESSAGE
  User/process lacks Create Directory permission on the parent
directory.
 - CAUSE
  The user/process is lacking one of the required directory
permissions.
 - ACTION
  Assign the user the appropriate directory security access rights.
 
 
 - -74
 
 - MESSAGE
  User/process lacks Delete Directory permission on the parent
directory.
 - CAUSE
  The user/process is lacking the required directory permission.
 - ACTION
  Assign the user the appropriate directory security access rights.
 
 
 - -75
 
 - MESSAGE
  User/process lacks Read Directory permission on the parent
directory.
 - CAUSE
  The user/process is lacking the required directory permission.
 - ACTION
  Assign the user the appropriate directory security access rights.
 
 
 - -76
 
 - MESSAGE
  Could not open the HPUID.PUB.SYS file.
 - CAUSE
  HPUID.PUB.SYS may not exist, may be corrupt, or may be opened
exclusively.
 - ACTION
  If HPUID.PUB.SYS does not exist, create it with the PXUTIL.PUB.SYS
utility.
 
 
 - -77
 
 - MESSAGE
  Could not open the HPGID.PUB.SYS file.
 - CAUSE
  HPGID.PUB.SYS may not exist, may be corrupt, or may be opened
exclusively.
 - ACTION
  If HPGID.PUB.SYS does not exist, create it with the PXUTIL.PUB.SYS
utility.
 
 
  |  
 - -78
 
 - MESSAGE
  Could not retrieve the user entry from the HPUID.PUB.SYS file.
 - CAUSE
  The user entry could not be found in the HPUID.PUB.SYS file.
 - ACTION
  Update the HPUID.PUB.SYS file with the PXUTIL.PUB.SYS utility.
 
 
 - -79
 
 - MESSAGE
  Could not retrieve the group entry from the HPGID.PUB.SYS file.
 - CAUSE
  The group entry could not be found in the HPGID.PUB.SYS file.
 - ACTION
  Update the HPGID.PUB.SYS file with the PXUTIL.PUB.SYS utility.
 
 
 - -81
 
 - MESSAGE
 Cannot return a pathname which is larger than the maximum path
size. 
 - CAUSE
  Currently, it is possible to create a pathname too large to return.
 - ACTION
  Change to the application to return the long pathname relative to
your current working directory.
 
 
 - -82
 
 - MESSAGE
  Can't open a directory during directory traversal due to too many
files open.
 - CAUSE
  Too many files are already open; failed to open a directory.
 - ACTION
  Check the application.
 
 
 - -83
 
 - MESSAGE
  Security violation during directory traversal; failed to open
directory file.
 - CAUSE
  Encountered security violation when trying to open a directory
file.
 - ACTION
  Check the user/application security. 
 
 
 - -84
 
 - MESSAGE
  Read probe failed on pathname item key.
 - CAUSE
  When probing the pathname item key, an error was returned.
 - ACTION
  Make sure you are not passing in a bad length in the pathname item
key.
 
 
 - -85
 
 - MESSAGE
   The tempfile parm is not valid in conjunction with the pathname
item key. 
 - CAUSE
  Temporary files are currently not supported in the Hierarchical
File System. 
 - ACTION
  Use the filename or UFID parameter when interested in a
temporary file. 
 
 
 - -86
 
 - MESSAGE
   The pathname length specified is bad. 
 - CAUSE
  User specified a pathname length less than zero or greater than the maximum pathname length.
 - ACTION
  Check the application. 
 
 
  |  
 - -89
 
 - MESSAGE
   Error occurred when trying to get file label for this file.
UFID may be bad.
 - CAUSE
  The UFID passed to AIFSYSWIDEGET may be bad.
 - ACTION
   Check to see if the file exists. 
 
 
 - -90
 
 - MESSAGE
   An error occurred while trying to obtain ownershop of the device.
 - CAUSE
  The device is not currently available for use.
 - ACTION
   Check device.  Contact Hewlett-Packard for support. 
 
 
 - -91
 
 - MESSAGE
   An error occurred while trying to release device ownership.
 - CAUSE
  An unexpected internal error occurred.
 - ACTION
   Contact Hewlett-Packard for support. 
 
 
 - -101
 
 - MESSAGE
  Unsupported option.
 - CAUSE
  Port manage access was requested, but is not supported.
 - ACTION
  Do not attempt to open a port for Port Manager access.
 
 
 - -102
 
 - MESSAGE
  Too many receive opens on the AIF ports.
 - CAUSE
  The maximum number of receive opens have already been done.
 - ACTION
  Check the logic of your application.  The maximum is very large.
 
 
 - -103
 
 - MESSAGE
  Too many opens for manage access on the AIF ports.
 - CAUSE
  The maximum number of manage opens have already been done.
 - ACTION
  Check the logic of your application.
 
 
 - -104
 
 - MESSAGE
  Too many opens for send access on the AIF ports.
 - CAUSE
  The maximum number of send opens have already been done.
 - ACTION
  Check the logic of your application.  The maximum is very large.
 
 
 - -105
 
 - MESSAGE
  Invalid ACCESS MODE specified.
 - CAUSE
  The access mode code is not one of the allowed values.
 - ACTION
  Check the logic of your application.
 
 
 - -106
 
 - MESSAGE
  Message length is negative or greater than maximum.
 - CAUSE
  The specified message length is not valid.
 - ACTION
  Check the logic of your application.
 
 
  |  
 - -107
 
 - MESSAGE
  Specified port ID is not valid.
 - CAUSE
  The Port is either not open or is invalid.
 - ACTION
  Check the logic of your application.
 
 
 - -108
 
 - MESSAGE
  Attempted to send a message on Port not opened for Send access.
 - CAUSE
  The calling process does not have the Port open for Send access.
 - ACTION
  Check the logic of your application.
 
 
 - -109
 
 - MESSAGE
  Attempted to receive a message
from Port not open for Receive access.
 - CAUSE
  The calling process does not have the Port open for Receive access.
 - ACTION
  Check the logic of your application.
 
 
 - -110
 
 - MESSAGE
  Attempted to manage a Port not open for Manage access.
 - CAUSE
  The calling process is not the Port Manager.
 - ACTION
  Check the logic of your application.
 
 
 - -111
 
 - MESSAGE
  A timeout occurred.
 - CAUSE
  The specified number of seconds has passed.
 - ACTION
  Verify that the timeout value specified is sufficient.
 
 
 - -112
 
 - MESSAGE
  No Ports open for receive access, multi-port receive failed.
 - CAUSE
  The calling process has no ports open for receive access.
 - ACTION
  Check the logic of your application.
 
 
 - -113
 
 - MESSAGE
  Attempt to open Port for same access multiple times.
 - CAUSE
  Process attempted to open same port for same access multiple times.
 - ACTION
  Check the logic of your application.
 
 
 - -114
 
 - MESSAGE
  Unsupported procedure.
 - CAUSE
  A procedure that is not yet supported was called.
 - ACTION
  Check the logic of your application.
 
 
 - -115
 
 - MESSAGE
  No zero element terminator was found in the itemnums array.
 - CAUSE
  No terminator was found in the itemnums array.
 - ACTION
  Check the logic of your application.
 
 
  |  
 - -116
 
 - MESSAGE
  Invalid password.
 - CAUSE
  The named port exists, but the password supplied does not match.
 - ACTION
  Check the logic of your application.
 
 
 - -117
 
 - MESSAGE
  Internal error.
 - CAUSE
  The port does not exist.
 - ACTION
  Perform a dump. Contact Hewlett-Packard for support.
 
 
 - -125
 
 - MESSAGE
  Itemnums, Items, and Itemstatus not specified together.
 - CAUSE
  Must pass item option arrays as a triple.  All or none.
 - ACTION
  Check the logic of your application.
 
 
 - -126
 
 - MESSAGE
  Must complete two-part receive before receive from another port.
 - CAUSE
  Receive from second port before doing
second part of two part receive.
 - ACTION
  Check the logic of your application.
 
 
 - -127
 
 - MESSAGE
  Must request message return on 2nd receive of two-part receive.
 - CAUSE
  The second receive of a two-part receive did not request message.
 - ACTION
  Check the logic of your application.
 
 
 - -128
 
 - MESSAGE
  The message length specified on send was larger
than the max length specified when the Port was created.
 - CAUSE
  Message cannot be larger than the specified size.
 - ACTION
  Check the logic of your application.
 
 
 - -129
 
 - MESSAGE
  A NoWait receive was done while there was no message ready.
 - CAUSE
  A NoWait receive was done while there was no message ready.
 - ACTION
  Check the logic of your application.
 
 
 - -130
 
 - MESSAGE
  An attempt was made to access a port which is not open for the
calling process. 
 - CAUSE
  The port was not opened by the calling process.
 - ACTION
  Check the logic of your application.
 
 
  |  
 - -900 thru -942
 
 - MESSAGE
  Internal Error.
 - CAUSE
  An unexpected internal error occurred. 
 - ACTION
  Contact Hewlett-Packard for support. 
 
 
 - -943
 
 - MESSAGE
  Internal Error.
 - CAUSE
  Security Internal error returned from the FS_SEC_ACCESS routine. 
 - ACTION
  Contact Hewlett-Packard for support. 
 
 
 - -944
 
 - MESSAGE
  Internal Error. 
 - CAUSE
  An unexpected error occurred from the hierarchical directory
routines. 
 - ACTION
  Contact Hewlett-Packard for support. 
 
 
 - -945
 
 - MESSAGE
  Internal Error.
 - CAUSE
  An unexpected error occurred from the directory traversal routines. 
 - ACTION
  Contact Hewlett-Packard for support. 
 
 
 - -946
 
 - MESSAGE
  Internal error.  Error returned from HPDIRREAD when reading a
directory file.
 - CAUSE
  An unexpected error occurred from the directory traversal routines. 
 - ACTION
  Contact Hewlett-Packard for support.
 
 
 - -947
 
 - MESSAGE
  Internal error.  HPFOPEN returned bad status when opening a
directory file.
 - CAUSE
  An unexpected error occurred from the directory traversal routines.
 - ACTION
  Contact Hewlett-Packard for support.
 
 
 - -948
 
 - MESSAGE
  Internal error.  The directory UFID is bad.
 - CAUSE
  An unexpected error occurred from the directory traversal routines.
 - ACTION
  Contact Hewlett-Packard for support.
 
 
 - -949 thru -999
 
 - MESSAGE
  Internal Error.
 - CAUSE
  An unexpected internal error occurred.
 - ACTION
  Contact Hewlett-Packard for support.
 
 
  |  
  
 |