You can use the Cobol container to start Cobol modules from a batch application

You can use the cobol container to start cobol

This preview shows page 197 - 200 out of 672 pages.

creates these based on the data and linkage definitions in the Cobol source. You can use the Cobol container to start Cobol modules from a batch application, creating a direct integration of Cobol into Java batch processing. You can also dynamically update a Cobol module without having to restart the application server. With WebSphere Application Server V8.5, Cobol support includes the following key features: In z/OS, you can call standard Cobol modules from Java on the same thread in same process. Java and Cobol run in same transaction scope. DB2 connections that are managed by WebSphere are shareable with Cobol. You can use Cobol working storage isolation per job step or per remote call. IBM Rational Application Developer tools are available for Java call stub generation. For more information about Cobol features on z/OS, see 16.6.2, “WebSphere Batch on z/OS” on page 570. 6.5.4 CommandRunner utility job step Use the CommandRunner utility job step to run shell command lines as job steps. The command lines can include shell commands, shell scripts, and compiled programs. The CommandRunner utility runs the specified shell command line in an operating system process. Standard output and standard error streams are captured and written to the job log. The command-line return code is captured and set as the step return code. If the job step is canceled, the return code is -8. Use the syntax in Example 6-3 for the CommandRunner utility. Example 6-3 CommandRunner syntax <job-step name={step_name}> <classname>com.ibm.websphere.batch.utility.CommandRunner</classname> {job_step_properties} </job-step> The job step code that is shown in Example 6-4 runs a command-line Java program. Example 6-4 Job step that runs a program by using the CommandRunner utility <job-step name="RunJava"> <classname>com.ibm.websphere.batch.utility.CommandRunner</classname> <props> <prop name="com.ibm.websphere.batch.cmdLine" value="java.exe com.ibm.websphere.batch.samples.TestCase" /> <prop name="CLASSPATH" value="${user.dir}\testcases;${user.dir}\bin" /> <prop name="Path" value="${java.home}\bin;${env:Path}" /> </props> </job-step>
Image of page 197
172 WebSphere Application Server V8.5 Concepts, Planning, and Design Guide
Image of page 198
© Copyright IBM Corp. 2012, 2013. All rights reserved. 173 Infrastructure You must consider many factors when planning and designing an infrastructure for a WebSphere Application Server environment. The most important aspects to create a WebSphere Application Server infrastructure to run a successful WebSphere project are addressed. This chapter includes the following sections: Infrastructure planning Environment planning Design considerations Sizing the infrastructure Monitoring Backup and recovery Cloud infrastructure For more information about topics relevant for infrastructure decisions, see: Monitoring is addressed in Chapter 10, “Performance, scalability, and high availability” on page 303.
Image of page 199
Image of page 200

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture