The product provides sample files that support optimized local adapters for z/OS®. The sample files are located in the WebSphere® Application Server product directory under mso/OLA/samples.
A directory of the sample names and what they do is available in a directory in the @@README member of the native set of files. The samples include:
This data set should be allocated as RECFM=FB, DSORG=PO, LRECL=80, BLKSIZE=9040, TRKS=40. Copy, for example OGET, the files with file type “jclsamp” from the mso/OLA/samples directory to this data set. The header file mso/OLA/include/bboaapi.h should also be put in this data set as BBOAAPI.
This data set should be allocated as RECFM=FB, DSORG=PO, LRECL=80, BLKSIZE=9040, TRKS=15. In the sample JCL, this data set is named BOSS.OLA.SAMPLES.COPYBOOK.
It must be allocated as a LIBRARY rather than a PDS.
For all the members you update during these steps, you need to change the JCLLIB statement to point at your procedure libraries (for C compiles in this case). Someone familiar with where this information is located on your system should be involved in doing this. Also, the test case source has the daemon group (cell short name), the node short name, and the server short name embedded and you need to change these before compiling, in order for these to function on your system.
Some sample jobs refer to a data set named BOSS.OLA90902.SBBOLOAD. This represents the data set into which you copied the online adapter modules using the olaInstall.sh script.
This is a sample Cobol application that demonstrates a number of the optimized local adapters APIs from Cobol. It sends and receives the CICS BMS map, OLAMAP, and can send a message to any target enterprise bean in any locally attached application server. It can also be used to demonstrate how to make your CICS task into an optimized local adapters target service using the BBOA1SRV API. After updating the JCL to conform to your local data set name conventions, submit the job and the OLAUTIL load module is saved in the data set pointed to by the PROGLIB symbol.
Make sure that optimized local adapters support is enabled, logon to CICS with a user ID that is authorized to run the BBOC and OLAU transactions, and clear the screen. Enter BBOC START_TRUE to start the optimized local adapters CICS task-related user exit (TRUE). You will get a message about the exit starting successfully. If you do not get this message, you should get a message indicating what kind of error occurred. For more detailed messages, refer to the CICS job output and look in file BBOOUT. If you want to use the optimized local adapters Program List Table for Post Initialization (PLTPI) program to start the optimized local adapters TRUE during CICS startup, refer to the section below that describes this process.
If everything is working properly, the panel displays with the heading, * Optimized Local Adapters WAS z/OS Testing *. The Run parameters are listed on the panel, with Register first with a value of Y, Register name with a value of CICSTEST and Service name with a value of ejb/com/ibm/ola/olasample1_echoHome. The Number of Tests to run field has a value of 00001.
The panel display has now changed. The Register First? field changed from Y to N. Rerunning requests with this Register name does not require a register call first, so this changes to the value, N. If you get a return code 8 (RC8) and reason code 8 (RSN8) on Register, this means that you are already registered and do not need to register again. After leaving OLAU and coming back in later, that registration is still active, so you do not need to register again with that name and should set that to the value, N.
You need to update the service name field to whatever name you want to identify as your target service name and click PF5. This puts the screen into an x-wait since OLAUTIL calls the BBOA1SRV API with the service name and registration name that you requested. The panel shows a registration called CICSTEST and service name called myserv. Other parameters that show values on the panel are WAS server short name, WAS node short name, WAS cell short name (daemon group name), Number of Tests to run, and Number of Tests Completed.
Use the following URL (updating the IP/port# for your site): http://nn.nn.nn.nn:nnnn/OLA_Sample1_Web/ - change the nnnn port number to your non-SSL WebSphere Application Server application port.
This is a sample Cobol application that is the target of an EXEC CICS LINK with a COMMAREA. It writes the passed COMMAREA message data to the default Cobol standard out (CEEMSG) and echoes back the message. Update the JCL to point to your local data sets and submit it. The load library that this module is saved in must be in the CICS DFHRPL concatenation.
This is a sample Cobol application that is the target of an EXEC CICS LINK with a CONTAINER. It reads the CONTAINER contents and writes it back to the same container. Update the JCL to point to your local data sets and submit it. The load library that this module is saved in must be in the CICS DFHRPL concatenation.
Logon to CICS with a user ID that is authorized to run the BBOC, BBO# and BBO$ transactions, and clear the screen.
Enter BBOC START_TRUE to start the optimized local adapters CICS TRUE.
A message displays about the exit starting successfully. If you do not get this message, you should get a message indicating what kind of error occurred. For more detailed messages, refer to the CICS job output and look in file BBOOUT. If you want to use the optimized local adapters PLTPI program to start the optimized local adapters TRUE during CICS startup, refer to the section in this topic that describes this process.
This results in a BBO$ task starting with the register name OLASERVER, connecting the specified application server. Make sure to specify the server short name, cell short name and node short name for the server.
The sample job DFHPLTOL creates a PLTPI with suffix OL. Run this sample, placing the resulting module DFHPLTOL in a load modules library in the DFHRPL concatenation, and add OL to the SIT PLTPI specified for the CICS region, for example, PLTPI=OL.
+BBOA9920I WAS z/OS OLA CICS PLT init start. +BBOA9921I WAS z/OS OLA CICS TRUE enabled. +BBOA9925I WAS z/OS OLA CICS PLT init ending.