JES

JES-managed batch processes are used in various manners by Developer for z/OS®. The most common usage is for MVS builds, where a job is submitted and monitored to determine when it ends. But Developer for z/OS could also start a CARMA server in batch, and communicate with it using TCP/IP.

• CARMA

  CARMA is a Developer for z/OS server that is used to interact with host based Software Configuration Managers (SCMs), such as CA Endevor® SCM. Developer for z/OS allows for different startup methods for a CARMA server, some of which become a JES workload. You should specify a high-performance, one-period velocity goal, because the task does not report individual transactions to WLM. Resource usage depends heavily on user actions, and will therefore fluctuate, but is expected to be minimal.

• MVS build
  When a client initiates a build for an MVS project, Developer for z/OS will start a batch job to perform the build. Resource usage depends heavily on user actions, and will therefore fluctuate, but is expected to be moderate to substantial, depending on the size of the project. Different moderate-performance goal strategies can be advisable, depending on your local circumstances.

  • You could specify a multi-period goal with a percentile response time period and a trailing velocity period. In this case, your developers should be using mostly the same build procedure and similar sized input files to create jobs with uniform response times. There must also be a steady arrival rate of jobs (at least 10 jobs in 20 minutes) for WLM to properly manage a response time goal.
  • A velocity goal is best suited for most batch-jobs, because this goal can handle highly variable execution times and arrival rates.