You can use the wsadmin tool to configure and administer application servers, application deployment, and server run-time operations.
The wsadmin launcher supports several
scripting objects, including the AdminConfig, AdminControl, AdminApp,
AdminTask, and Help objects. Scripts use these objects for application
management, configuration, operational control, and for communication
with MBeans that run in product processes. You must start the wsadmin
scripting client before you perform any other task using scripting.
The wsadmin returns the following output when it establishes a connection to the server processs:
WASX7209I: Connected to process server1 on node myhost using SOAP connector; The type of process is: UnManagedProcess WASX7029I: For help, enter: "$Help help" wsadmin>
WASX7209I: Connected to process server1 on node myhost using SOAP connector; The type of process is: UnManagedProcess WASX7029I: For help, enter: "$Help help" wsadmin>
[ Unable to allocate an initial java heap of 268435456 bytes. ] [ **Out of memory, aborting** ] [ *** panic: JVMST016: Cannot allocate memory for initial java heap ] CEE5207E The signal SIGABRT was received.the wsadmin scripting client was unable to start because the region size on your login is not large enough to allocate the minimum heap size (-Xms ) that is specified on the Java Virtual Machine (JVM) that is created when wsadmin starts. The default value for the -Xms option, as specified in the wsadmin.sh file statement PERF_JVM_OPTIONS="-Xms256m -Xmx256m, is is 256 MB. To correct this problem, log out of TSO, and then when you log back in to TSO try to increase the value of the Size parameter on your login screen. If you cannot increase the value of the Size parameter on your login screen, check to see if any IEFUSI exits that prevents you from increasing the value of this parameter.
If
you're logging in via telnet to OMVS, the value that is used to determine
the address space size that your login receives is specified in the
BPXPRMxx parmlib member. BPXPRMxx controls the complete environment
of z/OS UNIX. Therefore the value that is set for the MAXASSIZE parameter
determines the size of the address space. However, if you are using
RACF, the address size can also be set for an individual user in the
respective RACF OMVS segment. In this situation the value specified
for the ASSIZEMAX parameter indicates, in bytes,
the address space size limit for that user. For example a setting
of ASSIZEMAX=0268435456 indicates the address
space allocated to that user is 256 MB.
In this information ...Related information
| IBM Redbooks, demos, education, and more(Index) |