Community
Participate
Working Groups
Currently, the Data Collection Engine (DCE) available on z/OS is compiled using a 32-bit compiler and, as a result, only has access to a 31-bit address space. Any programs that are loaded into this address space are bound by 31 bits of addressability as well. This precludes the use of a 64-bit address space which is only accessible to 64-bit programs. As a result, the 64-bit JVM available on the z/OS platform cannot be used with the DCE. The 64-bit JVM would provide invoked applications access to a much larger heap. Consuming products that use the DCE to deploy and run applications are unable to utilize the necessary heap to allow the applications to perform large tasks that require lots of heap be available to the JVM. The current max address space for apps spawned by the DCE is 2 gigabytes (half of what's available for on other platforms). This address space is shared by a portion of the OS kernel and other low-level apps, so the effective addressable memeory is smaller than 2 gigabytes.
The intent of this enhancement request is to provide the ability to launch the 64-bit JVM on z/OS such that applications have access to a larger heap than provided by the 31-bit JVM.
Deferring from 4.1 as per the official 4.1 enhancement plan. http://eclipse.org/tptp/home/project_info/featureplans/features.php?source=All&project=All&release=4.1&file=TPTPFeatures_4.1.xml
Deferred as agent controller port to 64-bit is deferred from 4.2 plan.
Not containable in 4.3 and retarget to future. Please let me know if you have any concern.
Hi Bing. I have transferred my bugs to you for triage. Thanks.
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As such, TPTP is not delivering enhancements. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement is resolved as WONTFIX. For this enhancement to be considered, please re-open with an attached patch including the Description Document (see http://www.eclipse.org/tptp/home/documents/process/development/description_documents.html), code (see http://www.eclipse.org/tptp/home/documents/resources/TPTPDevGuide.htm), and test cases (see http://www.eclipse.org/tptp/home/documents/process/TPTP_Testing_Strategy.html).
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this enhancement/defect has been resolved and unverified for more than 1 year and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.
