PORT messages
Port library messages.
JVMPORT001E Failed to allocate memory while attempting to write to a file.
Explanation
The system was unable to satisfy a memory allocation request.System action
Subsequent memory allocation attempts are likely to fail, resulting in the termination of the process.User response
Increase the amount of memory available to the process, or contact your IBM service representative.JVMPORT002E Unknown error loading shared library
Explanation
There was an unknown error loading a shared library.System action
The process shuts down.User response
This message is accompanied by another message that provides more detail. Check that the shared library exists. If the library exists, contact your IBM® service representative.JVMPORT003E Dependent module %s could not be loaded
Explanation
The named dependent module could not be loaded.System action
If the module was critical to the JVM, the process ends.User response
If the JVM ends, contact your IBM service representative.JVMPORT004E Symbol resolution failure
Explanation
There was a problem with symbol resolution while looking for a particular symbol.System action
If the symbol was critical to the JVM, the JVM ends, and more information is provided.User response
If the JVM ends, contact your IBM service representative.JVMPORT015E Unable to resolve shared library references - a prerequisite shared library may be missing
Explanation
The operating system could not resolve a shared library reference. A prerequisite shared library might be missing.System action
If the library is critical to the JVM, the process ends.User response
If the process ends, check that the library exists. If the library exists, contact your IBM service representative.JVMPORT016E Internal Error %i
Explanation
An internal error occurred while looking for a shared library.System action
If the library is critical to the JVM, the process ends.User response
If the process ends, check that the library exists. If the library exists, contact your IBM service representative.JVMPORT019W Unable to create directory %s. Shared classes will be disabled until this directory is created.
Explanation
You included a directory when you provided the name of the shared classes cache. This directory could not be created.System action
If you specified the -Xshareclasses:nonfatal parameter, the JVM continues without using shared classes. If you did not specify that parameter, the JVM ends.User response
Contact your IBM service representative.JVMPORT022I Appending .X&DS to user-specified dump template to enable multi-part dumps.
Explanation
You specified a dump template, by using the -Xdump:system:file= parameter or the JAVA_DUMP_TDUMP_PATTERN environment variable. The maximum amount of data that can be dumped in a single IEATDUMP file is 2 GB. For address spaces larger than 2 GB, the z/OS® operating system generates multiple dump files. To enable this behavior, the suffix &DS is required in the dump name. The suffix is replaced with a counter that identifies which part of the dump is in the file. If you do not add the suffix, the JVM appends it to the dump template.System action
The JVM adds .X&DS to the dump template, then continues to run.User response
You can ignore this message, and allow the JVM to alter the dump file name, unless the extended dump file name is too long. If the file name is too long, the JVM uses the default dump template instead. Avoid the message by including the &DS suffix in your dump template or by using the default dump template.JVMPORT023W IEATDUMP failed because user-specified dump template was too long. Retrying dump with default template.
Explanation
You specified a dump template, by using the -Xdump:system:file= parameter or the JAVA_DUMP_TDUMP_PATTERN environment variable. When the system tried to take a dump by using the template, the IEATDUMP routine returned with return code 0x8 and reason code 0x22, indicating that the dump failed because the name was too long.System action
The JVM tries to take the dump again using the default dump template.User response
Specify a shorter dump template. Note that, on the z/OS 64 operating system, the JVM appends .X&DS to the user-specified dump template, to enable multi-part z/OS dumps (required to store a full 64-bit address space). If the template you specified was close to 44 characters long, the addition of .X&DS might make it too long.JVMPORT024E IEATDUMP failed because we couldn't allocate the dump dataset (likely disk full).
Explanation
The JVM attempted to take an IEATDUMP, but the dump routine returned with return code 0x8 and reason code 0x26, indicating that the dump failed because the dump data set could not be allocated.System action
The JVM continues, but fails to create a dump.User response
The most common cause for this error message is that you have run out of space for dump data sets. Check your available dump storage.JVMPORT025E Invalid lock type for file lock operation. lockFlags: %1$d
Explanation
A file lock operation failed because the value of the flag that specifies the lock type was not valid.System action
The normal operation of the JVM is affected, possibly resulting in a failure to load one or more libraries.User response
Contact your IBM service representative.JVMPORT026E File specified is a directory
Explanation
A file-open operation failed when the system attempted to open a directory as a file.System action
The normal operation of the JVM is affected, possibly resulting in a failure to load one or more libraries.User response
Contact your IBM service representative.JVMPORT027E mmap failed due to invalid memory protection parameter.
Explanation
The value for the memory protection parameter is not valid.System action
The normal operation of the JVM is affected, possibly resulting in a failure to load one or more libraries.User response
Contact your IBM service representative.JVMPORT028E mmap failed due to invalid mapping options.
Explanation
The value for the flag parameter that specifies mapping options is not valid.System action
The normal operation of the JVM is affected, possibly resulting in a failure to load one or more libraries.User response
Contact your IBM service representative.JVMPORT029E Invalid handle. file handle: %1$d.
Explanation
A file map operation failed because a file handle was not valid.System action
The normal operation of the JVM is affected, possibly resulting in a failure to load one or more libraries.User response
Contact your IBM service representative.JVMPORT030W %s setting "%s" specifies that the core dump is to be piped to an external program. Attempting to rename either core or core.%d.
Explanation
Linux tools such as ABRT and Apport use the information in the /proc/sys/kernel/core_pattern file to redirect the core file to an external program, for example to create bug reports.System action
The virtual machine looks in the current directory for a file called either core or core.process ID, depending on the contents of the /proc/sys/kernel/core_uses_pid file.User response
Refer to the documentation for the external program specified in the /proc/sys/kernel/core_pattern file.JVMPORT031E The LE condition %s%i, which corresponds to a software-raised POSIX signal, was received
Explanation
The JVM was instructed at startup to run with Language Environment® (LE) condition handlers instead of POSIX signal handlers. A LE condition that corresponds to a software-raised POSIX signal was received.System action
The JVM creates a dump containing diagnostic data and ends.User response
Contact your IBM service representative.JVMPORT034W Attempted to attach shared memory created in storage protection key %lu, but currently running in key %lu.
Explanation
Shared memory could not be opened because the z/OS storage protection key used to create the shared memory is not compatible with the current storage protection key.System action
None.User response
Any problems are reported using a different message. Check for other error messages.JVMPORT035E __malloc31 failed to allocate buffer on z/OS
Explanation
The __malloc31 process failed to allocate a buffer.System action
The JVM continues, but hypervisor related information is not provided.User response
Contact your IBM service representative.JVMPORT036E Unexpected return code from CSRSI service on z/OS
Explanation
An unexpected return code is received from the CSRSI service on z/OS.System action
The JVM continues, but hypervisor related information is not provided.User response
Contact your IBM service representative.JVMPORT038E Malformed value for IBM_JAVA_HYPERVISOR_SETTINGS
Explanation
The IBM_JAVA_HYPERVISOR_SETTINGS environment variable is missing a closing quote character.System action
The JVM ends.User response
Correct the IBM_JAVA_HYPERVISOR_SETTINGS environment variable and try again.JVMPORT046E The executable could not be opened
Explanation
The executable file could not be opened.System action
The process shuts down.User response
This message is accompanied by another message that provides more detail.JVMPORT048E Failed to create system dump because a non-regular file \"%s\" exists with the same name as the expected system dump file
Explanation
The JVM did not produce a system dump because a non-regular file exists with the same name as the expected system dump file. The non-regular file might be a directory, symbolic link, pipe, or socket.System action
The JVM continues.User response
Check whether the name of a non-regular file in the current working directory of the Java application clashes with one of the following names or settings:- The default system dump file name, which is core or core.<process ID>.
- The setting of /proc/sys/kernel/core_pattern and /proc/sys/kernel/core_uses_pid.