When you create a new application server, it is automatically configured to run in 64-bit mode. You can deselect the Run in 64 bit JVM mode setting if you need to run the server in 31-bit mode. However, whenever possible, leave your servers configured to run in 64-bit mode because support for running servers in 31-bit mode is deprecated. If you have any servers, that you migrated from a previous version of the product, that are running in 31-bit mode, consider reconfiguring them to run in 64-bit mode.
BBOO0340W: 31-BIT MODE IS DEPRECATED FOR THE APPLICATION SERVER RUNNING ON THE Z/OS OPERATING SYSTEM. CONSIDER USING 64-BIT MODE FOR server_name AS AN ALTERNATIVE.depfeat
The AMODE parameter can be used to specify a particular addressing mode, either 31-bit or 64-bit, for the server. This parameter can also be set to a value of 00, which indicates that the server is to use the configured addressing mode. In the generated procedures, 00 is the default value for the AMODE parameter.
If you convert a 31-bit server to the 64-bit addressing mode, make sure that your automation does not specify AMODE=31 on the MVS START command. If a server is started with an AMODE value that does not match the configured addressing mode, the server does not start.
BBOO0336E START OF WEBSPHERE FOR Z/OS PROCESS FAILED BECAUSE INPUT AMODE 31 DOES NOT MATCH CONFIGURED AMODE 64
BBOO0336E START OF WEBSPHERE FOR Z/OS PROCESS FAILED BECAUSE INPUT AMODE 64 DOES NOT MATCH CONFIGURED AMODE 31
The DLLs and other native code that your applications call must match the addressing mode of the server on which the applications are running. If you convert an existing application server from 31-bit mode to 64-bit mode, you must change any Java™ applications containing native code, for example, C++ or Cobol, that you plan to run on the converted server, to run in 64-bit mode. Java applications can use the com.ibm.vm.bitmode Java property to determine the mode in which the server is running, and then load the correct 31-bit or 64-bit DLL to the native code.
An abend might occur if a server that is running in 64-bit mode tries to invoke an application that contains a 31-bit native module. Similarly, An abend might occur if a server that is running in 31-bit mode tries to invoke an application that contains a 64-bit native module.
For more information about converting language-environment (LE) applications to run in 64-bit mode, see the z/OS publication Language Environment® Programming Guide for 64-bit Virtual Addressing Mode, SA22-7569.
To convert an application server from 31-bit mode to 64-bit mode, in the administrative console select the Run in 64 bit JVM mode option on the configuration settings page for that application server, and change the minimum and maximum JVM heap sizes to values that are appropriate for a 64-bit process. Similarly to convert an application server from 64-bit mode to 31-bit mode, deselect the Run in 64 bit JVM mode option on the configuration settings page for that application server, and change the minimum and maximum JVM heap sizes to values that are appropriate for a 31-bit process.
If you use the MVS START command to start a 64-bit server, make sure that the AMODE parameter is set to 00 or 64, or is allowed to default to 00, on the START command. For example, you might issue one of the following commands:
S BBO7ACR,JOBNAME=BBOS001,ENV=BBOBASE.BBONODE.BBOS001,AMODE=64
S BBO7ACR,JOBNAME=BBOS001,ENV=BBOBASE.BBONODE.BBOS001
The startServer.sh command, and the administrative console, automatically add the AMODE=64 parameter when they are used to start a 64-bit application server.
The DLLs and other native code that your applications call must match the addressing mode of the server on which the applications are running. If you convert an existing application server from 31-bit mode to 64-bit mode, you must change any Java applications containing native code, for example, C++ or Cobol, that you plan to run on the converted server, to run in 64-bit mode. Java applications can use the com.ibm.vm.bitmode Java property to determine the mode in which the server is running, and then load the correct 31-bit or 64-bit DLL to the native code.
An abend might occur if a server that is running in 64-bit mode tries to invoke an application that contains a 31-bit native module. Similarly, An abend might occur if a server that is running in 31-bit mode tries to invoke an application that contains a 64-bit native module.
For more information about converting language-environment (LE) applications to run in 64-bit mode, see the z/OS publication Language Environment Programming Guide for 64-bit Virtual Addressing Mode, SA22-7569.
To convert a deployment manager from 31-bit mode to 64-bit mode, in the administrative console, select the Run in 64 bit JVM mode option on the configuration settings page for the deployment manager, and change the minimum and maximum JVM heap sizes to values that are appropriate for a 64-bit process.
If you use the MVS START command to start a 64-bit deployment manager, make sure that the AMODE parameter is set to 00 or 64, or is allowed to default to 00, on the START command. For example, you might issue one of the following commands:
S BBO7DCR,JOBNAME=BBODMGR,ENV=PLEXA.PLEXABBOCELL.BBODMGR.BBODMGR,AMODE=64
S BBO7DCR,JOBNAME=BBODMGR,ENV=BBOCELL.BBODMGR.BBODMGR
The startServer.sh command, and the administrative console, automatically add the AMODE=64 parameter when they are used to start a 64-bit deployment manager.