You can configure and run the WebSphere Compute Grid high
performance external scheduler connector (native WSGrid) after native
WSGrid is installed.
About this task
Native WSGrid is implemented in a native compiled language
and uses WebSphere MQ for communication. The benefit of native WSGrid
is twofold:
- It makes more efficient use of z/OS system processors by obviating
the need for JVM startup processing on each use.
- It uses the most robust messaging service available on z/OS to
ensure reliable operation with a messaging service already known and
used by most z/OS customers.
Procedure
- Define MQ queues. Queue manager must be local.
Two queues are required: one for input, one for output. You can name
the queues according to your naming conventions. As an example, the
names WASIQ and WASOQ are used for input and output queues, respectively.
The queues can be local or shared, for example, coupling facility.
- Run the installWSGrid.py script with the following input
parameters:
wsadmin.sh -f installWSGridMQ.py
- -install {-cluster <cluster name> | -node <node name> -server <server>}
- -mqroot <dir of mq root>
- -qmgr <queue manager name>
- -inqueue <input queue name>
- -outqueue <output queue name>
For example:
wsadmin.sh -f installWSGridMQ.py -install -cluster scheduler -mqroot
/usr/lpp/mqm/V6R0M0 -qmgr M600 -inqueue WASIQ -outqueue WASOQ
- Create the WSGRID load module:
- The unpackWSGRID is a REXX script in user_install_root/longRunning directory.
- Perform unpack using unpackWSGrid script. Issuing unpackWSGRID
with no input prints syntax: unpackWSGRID <was home>
[<hlq>] [<work dir>] [<batch>] [<debug>]
- <was home> specifies required WAS HOME directory
- <hlq> specifies optional HIGH LEVEL QUALIFIER of output data
sets default = <user id>
- <work dir> specifies optional working directory default = /tmp
- <batch> specifies optional run mode for this script specify
'batch' or 'interactive' default is 'interactive'
- <debug> specifies optional debug mode specify 'debug' or 'nodebug'
default is 'nodebug
For example:
/u/USER26> unpackWSGRID /WebSphere/ND/AppServer
Sample
output:
Unpack WSGRID with values:
WAS_HOME=/WebSphere/ND/AppServer
HLQ =USER26
WORK_DIR=/tmp
BATCH =INTERACTIVE
DEBUG =NODEBUG
Continue? (Y|N)
Y
User response: Y
Unzip /WebSphere/ND/AppServer/bin/cg.load.xmi.zip
extracted: cg.load.xmi
Move cg.load.xmi to /tmp
Delete old dataset 'USER26.CG.LOAD.XMI'
Allocate new dataset 'USER26.CG.LOAD.XMI'
Copy USS file /tmp/cg.load.xmi to dataset 'USER26.CG.LOAD.XMI'
Delete USS file /tmp/cg.load.xmi
Delete old dataset 'USER26.CG.LOAD'
Go to TSO and issue RECEIVE INDSN('USER26.CG.LOAD.XMI') to create
CG.LOAD
- Go to TSO, ISPF, option 6, and type in the following:
RECEIVE INDSN('USER26.CG.LOAD.XMI')
The
following output is the result:
Dataset BBUILD.CG.LOAD from BBUILD on PLPSC
The incoming data set is a 'PROGRAM LIBRARY'
Enter restore parameters or 'DELETE' or 'END' +
Press
enter to end. The following output, or output similar to, will display:
IEB1135I IEBCOPY FMID HDZ11K0 SERVICE LEVEL UA4
07.00 z/OS 01.07.00 HBB7720 CPU 2097
IEB1035I USER26 WASDB2V8 WASDB2V8 17:12:15 MON
COPY INDD=((SYS00006,R)),OUTDD=SYS00005
IEB1013I COPYING FROM PDSU INDD=SYS00006 VOL=CPD
USER26.R0100122
IEB1014I
IGW01551I MEMBER WSGRID HAS BEEN LOADED
IGW01550I 1 OF 1 MEMBERS WERE LOADED
IEB147I END OF JOB - 0 WAS HIGHEST SEVERITY CODE
Restore successful to dataset 'USER26.CG.LOAD'
***