Access Methods and Plug-Ins Awsaumst

IBM Workload SchedulerVersion 9 Release 3

Access Methods and Plug-ins

NoteBefore using this information and the product it supports, read the information in Notices on page 349.

This edition applies to version 9, release 3, modification level 0 of IBM Workload Scheduler (program number5698-WSH) and to all subsequent releases and modifications until otherwise indicated in new editions.

Copyright IBM Corporation 2001, 2015.US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

ContentsFigures . . . . . . . . . . . . . . . ix

Tables . . . . . . . . . . . . . . . xi

About this Publication . . . . . . . . xiiiWhat is new in this release . . . . . . . . . xiiiWho should read this publication. . . . . . . xiiiAccessibility . . . . . . . . . . . . . . xivTechnical training . . . . . . . . . . . . xivSupport information . . . . . . . . . . . xivHow to read syntax diagrams . . . . . . . . xiv

Part 1. General information . . . . . 1

Chapter 1. Product overview . . . . . . 3

Chapter 2. Supported agentworkstations. . . . . . . . . . . . . 5

Chapter 3. Installing and configuring theaccess methods . . . . . . . . . . . 7Setting options for the access methods . . . . . . 7

Option value inheritance . . . . . . . . . 10Editing the options files . . . . . . . . . 10Using the Option Editor . . . . . . . . . 10

Defining supported agent workstations . . . . . 13Creating a workstation using the DynamicWorkload Console . . . . . . . . . . . 13Creating a workstation using the command line 14Defining workstations for end-to-end scheduling 15

Defining jobs for supported agents . . . . . . 17Defining jobs with the Dynamic WorkloadConsole. . . . . . . . . . . . . . . 18Defining jobs using the command line . . . . 18Defining jobs for end-to-end scheduling . . . . 19

Submitting jobs . . . . . . . . . . . . . 20Configuring FIPS mode . . . . . . . . . . 21

Part 2. SAP R/3 access method. . . 23

Chapter 4. Introducing IBM WorkloadScheduler for SAP. . . . . . . . . . 25Features . . . . . . . . . . . . . . . 25Scheduling process for the agent workstationhosting the r3batch access method. . . . . . . 26Roles and responsibilities . . . . . . . . . . 27Configuring user authorization (Security file) . . . 29Unicode support. . . . . . . . . . . . . 29

What is Unicode. . . . . . . . . . . . 29Unicode support on r3batch . . . . . . . . 30

Chapter 5. Configuring the SAP R/3environment . . . . . . . . . . . . 31Overview . . . . . . . . . . . . . . . 31Creating the IBM Workload Scheduler RFC user . . 31Creating the authorization profile for the IBMWorkload Scheduler user . . . . . . . . . . 31

Using transaction su02 and manually creating theprofile . . . . . . . . . . . . . . . 32Using transaction PFCG (Profile Generator). . . 32

Copying the correction and transport files . . . . 34Importing ABAP/4 function modules into SAP R/3 35Changing the IBM Workload Scheduler RFC user IDpassword . . . . . . . . . . . . . . . 38Securing data communication . . . . . . . . 39Migrating from previous versions . . . . . . . 40Print parameter and job class issues . . . . . . 40

Chapter 6. Configuring the SAP R/3access method . . . . . . . . . . . 43Defining the configuration options. . . . . . . 44

Defining the global options . . . . . . . . 44Defining the local options . . . . . . . . 45Defining the common options . . . . . . . 47SAP R/3 option file example . . . . . . . 55Encrypting SAP R/3 user passwords . . . . . 55

Configuration options usage . . . . . . . . . 55Connecting to the SAP system . . . . . . . . 56

Connecting to a specific application server . . . 56Connecting to a logon group . . . . . . . 57

Configuring SAP event monitoring . . . . . . 57Prerequisite to defining event rules based on SAPevents . . . . . . . . . . . . . . . 57Monitoring SAP events . . . . . . . . . 58

Chapter 7. Defining SAP jobs . . . . . 59Creating SAP Standard R/3 jobs from the DynamicWorkload Console . . . . . . . . . . . . 59

Create an SAP job and associate it to an IBMWorkload Scheduler job . . . . . . . . . 60Create an IBM Workload Scheduler job andassociate it to an SAP job . . . . . . . . . 61Creating a SAP job from the Dynamic WorkloadConsole. . . . . . . . . . . . . . . 63

Setting the SAP data connection . . . . . . . 64Managing SAP variants using the DynamicWorkload Console . . . . . . . . . . . . 64

Creating or editing a variant. . . . . . . . 66Editing a standard SAP job . . . . . . . . . 67Task string to define SAP jobs . . . . . . . . 68

Chapter 8. Managing SAP jobs . . . . 77Displaying details about a standard SAP job . . . 77Verifying the status of a standard SAP job . . . . 77Deleting a standard SAP job from the SAP database 78

Copyright IBM Corp. 2001, 2015 iii

Balancing SAP workload using server groups . . . 78Mapping between IBM Workload Scheduler andSAP job states . . . . . . . . . . . . . 79Managing spools . . . . . . . . . . . . 79

Browsing spool data . . . . . . . . . . 80Killing an SAP job instance . . . . . . . . . 80Raising an SAP event . . . . . . . . . . . 81Rerunning a standard SAP job . . . . . . . . 82

Old copy and new copy of a rerunning job . . . 84

Chapter 9. Defining SAP jobsdynamically . . . . . . . . . . . . 85Task string to define SAP jobs dynamically . . . . 85

Defining attributes for ABAP steps . . . . . 94Defining attributes for external programs andexternal commands steps . . . . . . . . . 96

Specifying job parameters using variablesubstitution . . . . . . . . . . . . . . 98Examples: Dynamically defining and updating SAPjobs . . . . . . . . . . . . . . . . . 98

Chapter 10. Defining conditions andcriteria . . . . . . . . . . . . . . 101Example: Defining which raised events to log . . 102

Create the criteria profile . . . . . . . . 102Build the criteria hierarchy . . . . . . . . 103Activate the criteria profile . . . . . . . . 104

Chapter 11. Using the BDC Waitoption . . . . . . . . . . . . . . 105

Chapter 12. Job interception andparent-child features . . . . . . . . 107Implementing job interception . . . . . . . . 107

Job interception and the BC-XBP 2.0 interface 107Job interception and the BC-XBP 3.0 interface 108Collecting intercepted jobs periodically forBC-XBP 2.0 . . . . . . . . . . . . . 108Collecting intercepted jobs periodically forBC-XBP 3.0 . . . . . . . . . . . . . 109Setting interception criteria on the SAP R/3system . . . . . . . . . . . . . . 109Setting interception criteria on IBM WorkloadScheduler. . . . . . . . . . . . . . 110Activating the job interception feature . . . . 115

The parent-child feature . . . . . . . . . . 115

Chapter 13. Using BusinessInformation Warehouse . . . . . . . 117Business Warehouse components . . . . . . . 117Defining user authorizations to manage SAP R/3Business Warehouse InfoPackages and processchains . . . . . . . . . . . . . . . . 117Managing SAP R/3 Business WarehouseInfoPackages and process chains . . . . . . . 118

Creating a IBM Workload Scheduler job thatcontains InfoPackages or process chains . . . 118Task string to define Business WarehouseInfoPackages and process chain jobs. . . . . 120

Displaying details about Business WarehouseInfoPackages . . . . . . . . . . . . 123Displaying details about a process chain job . . 123Rerunning a process chain job . . . . . . . 125

Chapter 14. Job throttling feature. . . 133Business scenario . . . . . . . . . . . . 133Software prerequisites . . . . . . . . . . 133Setting and using job throttling . . . . . . . 133

Step 1. Setting the options in the options file 134Step 2. Enabling and configuring the jobinterception feature . . . . . . . . . . 134Step 3. Enabling job class inheritance . . . . 134Step 4. Configuring the logging properties. . . 135Step 5. Starting and stopping the job throttlingfeature . . . . . . . . . . . . . . 135

Sending data from job throttling to the CCMSMonitoring Architecture . . . . . . . . . . 136

Deleting the monitoring tree elements . . . . 137

Chapter 15. Exporting SAP R/3 factorycalendars . . . . . . . . . . . . . 139Business scenario . . . . . . . . . . . . 139Exporting and importing SAP R/3 factorycalendars . . . . . . . . . . . . . . . 139

Exporting factory calendars. . . . . . . . 139Importing factory calendars . . . . . . . 142

Chapter 16. Defining internetworkdependencies and event rules basedon SAP R/3 background events . . . 143Defining internetwork dependencies based on SAPbackground events . . . . . . . . . . . 143

Committing SAP background events by anexternal task. . . . . . . . . . . . . 145

Defining internetwork dependencies based on SAPbackground events with the Dynamic WorkloadConsole . . . . . . . . . . . . . . . 146Defining event rules based on SAP backgroundevents . . . . . . . . . . . . . . . . 147

SAP events matching criteria . . . . . . . 148Setting a filter for SAP background events in thesecurity file . . . . . . . . . . . . . . 150

Chapter 17. Defining event rulesbased on IDoc records . . . . . . . 151Business scenario . . . . . . . . . . . . 151Creating event rules based on IDocs. . . . . . 151

Events matching criteria . . . . . . . . . 152Examples of event rules based on IDocs . . . . 157

Chapter 18. Defining event rulesbased on CCMS MonitoringArchitecture alerts . . . . . . . . . 159Business scenarios . . . . . . . . . . . . 159

Business scenario: defining an event rule toprocess alerts related to IDocs . . . . . . . 159Business scenario: defining an event rule toprocess alerts related to operating system . . . 159

iv IBM Workload Scheduler: Access Methods and Plug-ins

Creating event rules based on CCMS alerts . . . 160Mapping between the MTE name and IBMWorkload Scheduler fields . . . . . . . . 162Setting correlation rules and action parameters 164

Getting alert status and committing alerts by anexternal task. . . . . . . . . . . . . . 166

Getting CCMS alert status . . . . . . . . 166Committing CCMS alerts . . . . . . . . 167

Example of an event rule based on CCMS alerts 168

Chapter 19. Scheduling jobs on IBMWorkload Scheduler from SAPSolution Manager . . . . . . . . . 171Registering the master domain manager on SAPSolution Manager . . . . . . . . . . . . 171Scheduling . . . . . . . . . . . . . . 174

Scheduling jobs directly . . . . . . . . . 174Scheduling from job documentation . . . . . 175

Monitoring . . . . . . . . . . . . . . 176Setting up to log traces on WebSphere ApplicationServer . . . . . . . . . . . . . . . . 177

Chapter 20. National Languagesupport . . . . . . . . . . . . . . 179Setting National Language support options . . . 179SAP R/3 supported code pages . . . . . . . 180

Chapter 21. Troubleshooting . . . . . 181Troubleshooting the SAP R/3 connection . . . . 181Other known problems . . . . . . . . . . 181

Part 3. Managing SAP PI channeljobs . . . . . . . . . . . . . . . 193Chapter 22. Overview . . . . . . . . 195

Chapter 23. Business scenario . . . . 197

Chapter 24. Tasks . . . . . . . . . 199

Chapter 25. Roles and responsibilities 201Assigning J2EE roles . . . . . . . . . . . 201

Chapter 26. Configuring externalcontrol . . . . . . . . . . . . . . 203

Chapter 27. Defining an IBM WorkloadScheduler job that runs an SAP PIChannel job . . . . . . . . . . . . 205Defining an IBM Workload Scheduler job that runsan SAP PI Channel job by using composer . . . 205

Job definition for SAP PI Channel jobs . . . . 205Defining IBM Workload Scheduler jobs to run SAPPI Channel jobs by using the Dynamic WorkloadConsole . . . . . . . . . . . . . . . 207

Chapter 28. Submitting IBM WorkloadScheduler job streams for SAP PIChannel jobs . . . . . . . . . . . 209Chapter 29. Monitoring SAP PIChannel jobs . . . . . . . . . . . 211Mapping between IBM Workload Scheduler andSAP PI Channel job statuses . . . . . . . . 211Analyzing the job log. . . . . . . . . . . 211

Job log output . . . . . . . . . . . . 212

Part 4. PeopleSoft access method 213

Chapter 30. Introducing IBM WorkloadScheduler access method forPeopleSoft . . . . . . . . . . . . 215Features . . . . . . . . . . . . . . . 215Roles and responsibilities . . . . . . . . . 215Scheduling process for the PeopleSoft supportedagents . . . . . . . . . . . . . . . . 216PeopleSoft job tracking in IBM Workload Scheduler 216Security . . . . . . . . . . . . . . . 216

Chapter 31. Configuring thePeopleSoft access method . . . . . 217Defining the configuration options . . . . . . 217

PeopleSoft options file example . . . . . . 219Connecting to more than one PeopleSoftapplication server . . . . . . . . . . . 220

Creating a batch processing ID in PeopleSoft . . . 220Configuring the ITWS_PSXA PeopleSoft project 220Uploading the PeopleSoft project . . . . . . . 221

Chapter 32. Defining PeopleSoft jobs 225Defining PeopleSoft jobs in IBM WorkloadScheduler. . . . . . . . . . . . . . . 225

Task string parameters for PeopleSoft jobs . . . 225Configuring the job status mapping policy . . . 227

Part 5. z/OS access method . . . . 229

Chapter 33. Introducing IBM WorkloadScheduler access method for z/OS . . 231Features . . . . . . . . . . . . . . . 231Roles and responsibilities . . . . . . . . . 231Installing, configuring, and uninstalling the z/OSgateway . . . . . . . . . . . . . . . 232

Installing . . . . . . . . . . . . . . 232Configuring . . . . . . . . . . . . . 234Uninstalling . . . . . . . . . . . . . 235

Additional information . . . . . . . . . . 235Gateway software components . . . . . . 235IEFU84 Exit . . . . . . . . . . . . . 236Security . . . . . . . . . . . . . . 236Startup . . . . . . . . . . . . . . 236SYSTSIN variables. . . . . . . . . . . 236z/OS gateway version . . . . . . . . . 239

Contents v

||||||||||||||||||

Downloading z/OS gateway fixes from FTP . . . 239Locating product support . . . . . . . . . 241

Chapter 34. Configuring the z/OSaccess method. . . . . . . . . . . 243Defining the configuration options . . . . . . 243Defining jobs in z/OS . . . . . . . . . . 244Defining z/OS jobs in IBM Workload Scheduler 244

Task definition syntax for z/OS jobs scheduledwith IBM Workload Scheduler. . . . . . . 245Task definition syntax for other z/OS jobs. . . 246Operational considerations for the EEWSERVEgateway task . . . . . . . . . . . . 247File (OPENS) dependencies syntax on z/OS files 248

Chapter 35. Reference information 249Technical overview . . . . . . . . . . . 249

Managing JES jobs. . . . . . . . . . . 249Managing IBM Workload Scheduler for z/OSjobs . . . . . . . . . . . . . . . 251Checking for files on z/OS . . . . . . . . 252Timing considerations . . . . . . . . . 252

Diagnostic information . . . . . . . . . . 253Troubleshooting . . . . . . . . . . . . 253

Part 6. Common serviceability forthe access methods . . . . . . . 257

Chapter 36. The return code mappingfeature . . . . . . . . . . . . . . 259Parameters . . . . . . . . . . . . . . 259Creating a return code mapping file . . . . . . 259

Syntax. . . . . . . . . . . . . . . 260Examples . . . . . . . . . . . . . . 260Considerations . . . . . . . . . . . . 260

Return code mapping for psagent . . . . . . 261Return code mapping for r3batch. . . . . . . 261

Return code mapping file names for r3batch . . 263Mapping return codes for intercepted jobs. . . 264

Chapter 37. Configuring the tracingutility . . . . . . . . . . . . . . . 265Customizing the .properties file . . . . . . . 265Configuration file example for the SAP accessmethod . . . . . . . . . . . . . . . 266

Part 7. Managing InfoSphereDataStage jobs . . . . . . . . . . 269

Chapter 38. Overview . . . . . . . . 271


Chapter 40. Tasks . . . . . . . . . 275

Chapter 41. Roles and responsibilities 277

Chapter 42. Customizing IBMWorkload Scheduler to run InfoSphereDataStage jobs. . . . . . . . . . . 279Chapter 43. Defining a IBM WorkloadScheduler job to run an InfoSphereDataStage job . . . . . . . . . . . 281Defining a IBM Workload Scheduler job to run anInfoSphere DataStage job by using composer . . . 281

Job definition for InfoSphere DataStage jobs . . 281Defining IBM Workload Scheduler jobs to runInfoSphere DataStage jobs by using the DynamicWorkload Console . . . . . . . . . . . . 285

Chapter 44. Scheduling andsubmitting job streams for InfoSphereDataStage jobs. . . . . . . . . . . 287Chapter 45. Monitoring InfoSphereDataStage jobs. . . . . . . . . . . 289Mapping between IBM Workload Scheduler andInfoSphere DataStage job statuses . . . . . . 289Analyzing the job log. . . . . . . . . . . 290

Job log output . . . . . . . . . . . . 290

Chapter 46. Analyzing the InfoSphereDataStage job properties . . . . . . 293

Part 8. Managing Cognos reports 295

vi IBM Workload Scheduler: Access Methods and Plug-ins



Chapter 49. Tasks . . . . . . . . . 301


Chapter 51. Customizing IBMWorkload Scheduler to run Cognosreports . . . . . . . . . . . . . . 305

Chapter 52. Configuring the agent touse Cognos in SSL . . . . . . . . . 307

Chapter 53. Defining an IBM WorkloadScheduler job to run a Cognos report . 309Defining jobs by using composer . . . . . . . 309

Job definition for Cognos reports . . . . . . 309Defining jobs by using the Dynamic WorkloadConsole . . . . . . . . . . . . . . . 314Specifying the parameter format for date, time, andtime stamp . . . . . . . . . . . . . . 315Specifying parameterized filters . . . . . . . 316

Chapter 54. Scheduling andsubmitting job streams for Cognosreports . . . . . . . . . . . . . . 319

Chapter 55. Monitoring IBM WorkloadScheduler jobs that run Cognosreports . . . . . . . . . . . . . . 321Mapping between job statuses and Cognos reportstatuses . . . . . . . . . . . . . . . 321Analyzing the job log. . . . . . . . . . . 321

Job log output . . . . . . . . . . . . 322

Part 9. Managing OracleE-Business Suite jobs . . . . . . 325



Chapter 58. Tasks . . . . . . . . . 331


Chapter 60. Customizing IBMWorkload Scheduler to run OracleE-Business Suite jobs . . . . . . . 335Chapter 61. Defining an IBM WorkloadScheduler job to run an OracleE-Business Suite job . . . . . . . . 337Defining an IBM Workload Scheduler job to run anOracle E-Business Suite job by using composer . . 337Job definition for Oracle E-Business Suite jobs . . 337Defining IBM Workload Scheduler jobs to runOracle E-Business Suite jobs by using the DynamicWorkload Console . . . . . . . . . . . . 340Scheduling and submitting job streams for OracleE-Business Suite jobs . . . . . . . . . . . 341Monitoring Oracle E-Business Suite jobs . . . . 341Mapping between IBM Workload Scheduler jobstatuses and Oracle E-Business Suite applicationstatuses . . . . . . . . . . . . . . . 342Analyzing the job log. . . . . . . . . . . 342

Chapter 62. Analyzing the OracleE-Business Suite job properties . . . 345

Part 10. Appendixes . . . . . . . 347

Notices . . . . . . . . . . . . . . 349Trademarks . . . . . . . . . . . . . . 351Terms and conditions for product documentation 351Notices and information. . . . . . . . . . 352Libmsg . . . . . . . . . . . . . . . 353Apache Jakarta ORO . . . . . . . . . . . 353ISMP Installer (InstallShield 10.50x) . . . . . . 354JXML CODE. . . . . . . . . . . . . . 354InfoZip CODE . . . . . . . . . . . . . 355HSQL Code . . . . . . . . . . . . . . 356HP-UX Runtime Environment, for the Java 2Platform . . . . . . . . . . . . . . . 356

Index . . . . . . . . . . . . . . . 371

Contents vii

viii IBM Workload Scheduler: Access Methods and Plug-ins

Figures1. Supported agent configurations . . . . . . 42. The Option Editor . . . . . . . . . . 113. Defining an Extended Agent workstation 174. Defining an Extended Agent job for end-to-end

scheduling . . . . . . . . . . . . . 195. The Variant List panel . . . . . . . . . 656. The Variant Information page of the Variant

List panel . . . . . . . . . . . . . 667. The Raise Event panel . . . . . . . . . 818. The Table Criteria panel . . . . . . . . 111

9. The Table Criteria panel . . . . . . . . 11410. Dynamic Workload Console - Table of results 12411. Dynamic Workload Console - Details of a

process chain job . . . . . . . . . . 12512. Managing high priority IDocs overview 15113. A monitor and its MTEs - SAP AG 2009.

All rights reserved. . . . . . . . . . 16014. Name and description of an MTE - SAP

AG 2009. All rights reserved. . . . . . . 162

Copyright IBM Corp. 2001, 2015 ix

x IBM Workload Scheduler: Access Methods and Plug-ins

Tables1. How to complete the extended agents

definition . . . . . . . . . . . . . 132. IBM Workload Scheduler for SAP features 253. Roles and responsibilities in IBM Workload

Scheduler for SAP . . . . . . . . . . 274. Access keywords for activities with SAP

scheduling objects . . . . . . . . . . 295. ABAP/4 modules installed according to the

SAP release . . . . . . . . . . . . 366. ABAP/4 modules contents . . . . . . . 377. r3batch global configuration options . . . . 448. r3batch local configuration options . . . . . 469. r3batch common configuration options 4810. Placeholders and counters for extended

variants . . . . . . . . . . . . . . 6711. Task string parameters for SAP jobs . . . . 7112. Status transitions in IBM Workload Scheduler

(internal status) and the corresponding SAPR/3 status . . . . . . . . . . . . . 79

13. Task string parameters for SAP jobs (dynamicdefinition) . . . . . . . . . . . . . 88

14. Supported attributes for ABAP step definition 9415. Supported attributes for external programs and

external commands step definition . . . . . 9616. Placeholders for job interception template files 11417. Task string parameters for SAP R/3 jobs 12018. Actions performed when you rerun a process

chain job . . . . . . . . . . . . . 12619. Parameters to define an SAP internetwork

dependency . . . . . . . . . . . . 14420. Internetwork dependency definition and

possible resolution . . . . . . . . . . 14521. History table of the SAP events raised 14822. SAP event matching with the event rule

defined . . . . . . . . . . . . . 14923. History table of the SAP events raised 14924. SAP events matching with the event rule

defined . . . . . . . . . . . . . 15025. IBM Workload Scheduler fields used to define

event rules based on IDocs . . . . . . . 15226. IBM Workload Scheduler fields used to define

correlation rules for IDoc events . . . . . 15327. Parameters of IDOCEventGenerated event

type. . . . . . . . . . . . . . . 15428. Standard outbound IDoc statuses . . . . . 15529. Standard inbound IDoc statuses . . . . . 15630. Mapping between root context MTE name

and IBM Workload Scheduler fields . . . . 16331. Mapping between summary context MTE

name and IBM Workload Scheduler fields . . 16332. Mapping between object MTE name and IBM

Workload Scheduler fields . . . . . . . 16433. Mapping between attribute MTE name and

IBM Workload Scheduler fields . . . . . 16434. Alert properties for correlations . . . . . 165

35. Properties for the smseadapter.propertiesfile. . . . . . . . . . . . . . . . 172

36. SAP R/3 supported code pages . . . . . 18037. Miscellaneous troubleshooting items . . . . 18138. Required and optional attributes for the job

definition of SAP PI Channel jobs. . . . . 20639. Mapping between IBM Workload Scheduler

and SAP PI Channel job statuses . . . . . 21140. Roles and responsibilities in IBM Workload

Scheduler access method for PeopleSoft. . . 21541. Psagent access method options. . . . . . 21742. Task string parameters for PeopleSoft jobs 22643. Relationship between the run status, the

distribution status, and the IBM WorkloadScheduler job status . . . . . . . . . 227

44. Relationship between the run status and theIBM Workload Scheduler job status . . . . 228

45. Roles and responsibilities in IBM WorkloadScheduler access method for z/OS . . . . 231

46. SYSTSIN variables . . . . . . . . . . 23747. File characteristics for obtaining the gateway

fix pack files by FTP . . . . . . . . . 23948. File characteristics for the LOADLIB file after

receiving it . . . . . . . . . . . . 24149. File characteristics for the SAMPLIB file after

receiving it . . . . . . . . . . . . 24150. IBM Workload Scheduler access method for

z/OS access method options . . . . . . 24351. JES job states with respect to IBM Workload

Scheduler . . . . . . . . . . . . . 24952. IBM Workload Scheduler for z/OS operation

states with respect to IBM WorkloadScheduler . . . . . . . . . . . . . 251

53. IBM Workload Scheduler for z/OS operationoccurrence states with respect to IBMWorkload Scheduler . . . . . . . . . 251

54. Job states and return codes for the PeopleSoftaccess method . . . . . . . . . . . 261

55. Roles and responsibilities in IBM WorkloadScheduler for InfoSphere DataStage . . . . 277

56. Properties to run InfoSphere DataStage jobs 27957. Required and optional attributes for the job

definition of InfoSphere DataStage jobs. . . . 28258. Mapping between IBM Workload Scheduler

and InfoSphere DataStage job statuses . . . 28959. Roles and responsibilities in IBM Workload

Scheduler for Cognos . . . . . . . . . 30360. Properties for running Cognos reports 30561. Required and optional attributes for the

definition of jobs running Cognos reports. . . 31062. Examples to use for parameters of date, time,

and time stamp formats . . . . . . . . 31663. Mapping between job statuses and Cognos

report statuses . . . . . . . . . . . 32164. Roles and responsibilities in IBM Workload

Scheduler for Oracle E-Business Suite . . . 333

Copyright IBM Corp. 2001, 2015 xi

|||

65. Properties to run Oracle E-Business Suite jobs 33566. Required and optional attributes for the job

definition of Oracle E-Business Suite jobs. . . 33867. Mapping between IBM Workload Scheduler

and Oracle E-Business Suite applicationstatuses . . . . . . . . . . . . . 342

68. Examples: renaming the job defintion 36269. Comparison operators . . . . . . . . 36570. Logical operators . . . . . . . . . . 36571. Recovery options and actions . . . . . . 367

xii IBM Workload Scheduler: Access Methods and Plug-ins

About this PublicationThis guide provides information about how to set up and use the IBM WorkloadScheduler:v Access methods that run and control jobs of the following applications:

PeopleSoft SAP R/3 z/OS

v Plug-ins for the following applications: BigInsights Cognos Hadoop Distributed File System Hadoop Map Reduce Informatica PowerCenter InfoSphere DataStage Oracle E-Business Suite Salesforce SAP BusinessObjects BI SAP PI Channel Sterling Connect: Direct WebSphere MQ

What is new in this releaseLearn what is new in this release.

For information about the new or changed functions in this release, see IBMWorkload Automation: Overview, section Summary of enhancements.

For information about the APARs that this release addresses, see the IBM WorkloadScheduler Release Notes at http://www-01.ibm.com/support/docview.wss?rs=672&uid=swg27045180 and the Dynamic Workload Console Release Notes athttp://www-01.ibm.com/support/docview.wss?rs=672&uid=swg27045183.

Who should read this publicationLearn who should read this publication.

This publication is intended for job schedulers who want to run and controlapplication jobs by using IBM Workload Scheduler. Readers of this publicationshould have some knowledge of:v IBM Workload Schedulerv Dynamic Workload Consolev The specific application environment.

Copyright IBM Corp. 2001, 2015 xiii

AccessibilityAccessibility features help users with a physical disability, such as restrictedmobility or limited vision, to use software products successfully.

With this product, you can use assistive technologies to hear and navigate theinterface. You can also use the keyboard instead of the mouse to operate allfeatures of the graphical user interface.

For full information, see the Accessibility Appendix in the IBM Workload SchedulerUser's Guide and Reference.

Technical trainingCloud & Smarter Infrastructure provides technical training.

For Cloud & Smarter Infrastructure technical training information, see:http://www.ibm.com/software/tivoli/education

Support informationIBM provides several ways for you to obtain support when you encounter aproblem.

If you have a problem with your IBM software, you want to resolve it quickly. IBMprovides the following ways for you to obtain the support you need:v Searching knowledge bases: You can search across a large collection of known

problems and workarounds, Technotes, and other information.v Obtaining fixes: You can locate the latest fixes that are already available for your

product.v Contacting IBM Software Support: If you still cannot solve your problem, and

you need to work with someone from IBM, you can use a variety of ways tocontact IBM Software Support.

For more information about these three ways of resolving problems, see theappendix on support information in IBM Workload Scheduler: Troubleshooting Guide.

How to read syntax diagramsSyntax diagrams help to show syntax in a graphical way.

Throughout this publication, syntax is described in diagrams like the one shownhere, which describes the SRSTAT TSO command:

SRSTAT ' resource name 'OPCA

SUBSYS ( subsystem name )MSTR

xiv IBM Workload Scheduler: Access Methods and Plug-ins

KEEP

AVAIL ( RESET )NOYES

KEEPDEVIATION ( amount )

RESET

KEEP

QUANTITY ( amount )RESET

YESCREATE ( NO )

0

TRACE ( trace level )

The symbols have these meanings:

The statement begins here.

The statement is continued on the next line.

The statement is continued from a previous line.

The statement ends here.

Read the syntax diagrams from left to right and from top to bottom, following thepath of the line.

These are the conventions used in the diagrams:v Required items appear on the horizontal line (main path):

STATEMENT required item

v Optional items appear below the main path:

STATEMENToptional item

v An arrow returning to the left above the item indicates an item that you canrepeat. If a separator is required between items, it is shown on the repeat arrow.

STATEMENT

,

repeatable item

v If you can choose from two or more items, they appear vertically in a stack. If you must choose one of the items, one item of the stack appears on the

main path:

STATEMENT required choice 1required choice 2

About this Publication xv

If choosing one of the items is optional, the entire stack appears below themain path:

STATEMENToptional choice 1optional choice 2

A repeat arrow above a stack indicates that you can make more than onechoice from the stacked items:

STATEMENT

,

optional choice 1optional choice 2optional choice 3

STATEMENT

,

required choice 1required choice 2required choice 3

v Parameters that are above the main line are default parameters:

STATEMENTdefault

alternative

v Keywords appear in uppercase (for example, STATEMENT).v Parentheses and commas must be entered as part of the command syntax, as

shown.v For complex commands, the item attributes might not fit on one horizontal line.

If that line cannot be split, the attributes appear at the bottom of the syntaxdiagram:

STATEMENT required choice 1option 1 option 2

required choice 2required choice 3

option 1

defaultoptional choice 1 ( alternative )

option 2

defaultoptional choice 2 ( alternative )

xvi IBM Workload Scheduler: Access Methods and Plug-ins

Part 1. General information

Copyright IBM Corp. 2001, 2015 1

2 IBM Workload Scheduler: Access Methods and Plug-ins

Chapter 1. Product overviewLearn about access methods and plug-ins and how to use them.

Important: The access methods and plug-ins listed below are included with IBMWorkload Scheduler, but to be entitled to use them, you must purchase a separatechargeable component as well as IBM Workload Scheduler or IBM WorkloadScheduler for z/OS Agent. Ask your IBM representative for details.

Use access methods to extend the job scheduling capability of IBM WorkloadScheduler to other systems and applications. Access methods run on:v Extended agents to extend static scheduling capability.v Dynamic agents and IBM Workload Scheduler for z/OS Agents to extend

dynamic scheduling capability.

For more details about which workstations can run the access methods, seeChapter 2, Supported agent workstations, on page 5.

An access method interacts with the external system through either its commandline or the Dynamic Workload Console. IBM Workload Scheduler includes thefollowing access methods:v PeopleSoft (psagent)v SAP R/3 (r3batch)v z/OS (mvsjes and mvsopc)

You can also extend job scheduling capability with IBM Workload Schedulerplug-ins to external applications to take advantage of all the IBM WorkloadScheduler functions to manage these jobs.

The plug-ins are:v BigInsights (see User's Guide and Reference)v Cognosv Hadoop Distributed File System (see User's Guide and Reference)v Hadoop Map Reduce (see User's Guide and Reference)v Informatica PowerCenter (see IBM Workload Scheduler Plug-in for Informatica

PowerCenter: Users Guide)v InfoSphere DataStagev Oracle E-Business Suitev Salesforce (see User's Guide and Reference)v SAP BusinessObjects BI (see User's Guide and Reference)v SAP PI Channelv Sterling Connect: Direct (see User's Guide and Reference)v WebSphere MQ (see User's Guide and Reference).

To see how these elements fit together in a typical extended agent or dynamicagent configuration, see Figure 1 on page 4:


XA Wks2.opts

XA Wks1.optsFile_1.opts File_2.opts

File_3.opts

Dynamic AgentWorkstation_1Dynamic AgentWorkstation_1

XA Wks2

XA Wks1

ExternalEnvironment 2

(SAP)


(SAP)

ExternalEnvironment 3(PeopleSoft)

ExternalEnvironment 3(PeopleSoft)


(SAP)


(SAP)

Figure 1. Supported agent configurations


Chapter 2. Supported agent workstationsYou can extend IBM Workload Scheduler capabilities for scheduling on one ormore external applications, such as PeopleSoft, SAP R/3, and z/OS JES2 or JES3.To extend scheduling capabilities on these external applications, one of these agenttypes are needed:

Extended agents

Extended agents extend the static scheduling capability. They are logicalworkstations related to an access method hosted by a physical IBMWorkload Scheduler workstation (a fault-tolerant agent). More than oneextended agent workstation can be hosted by the same IBM WorkloadScheduler fault-tolerant agent and rely on the same access method. Theextended agent is defined in a standard IBM Workload Schedulerworkstation definition, which gives the extended agent a name andidentifies the access method. An access method is a program that is run bythe hosting workstation whenever IBM Workload Scheduler submits a jobto an external system.

Jobs are defined for an extended agent in the same manner as for otherIBM Workload Scheduler workstations, except for any job attributes thatdepend on the external system or application.

To launch and monitor a job on an extended agent, the host runs the accessmethod, passing to it job details as command line options. The accessmethod communicates with the external system to launch the job andreturns the status of the job. To launch a job in an external environment,IBM Workload Scheduler runs the extended agent access method providingit with the extended agent workstation name and information about thejob. The method looks at the corresponding file namedXANAME_accessmethod.opts (where XANAME is the name of the extendedagent workstation) to determine which external environment instance itconnects to. The access method can then launch jobs on that instance andmonitor them through completion, writing job progress and statusinformation in the standard list file of the job.

A physical workstation can host a maximum of 255 extended agents.

Extended agents can also be used to run jobs in an end-to-endenvironment, where job scheduling and monitoring is managed from anIBM Workload Scheduler for z/OS controller.

Dynamic agents and IBM Workload Scheduler for z/OS agents

Dynamic agents and IBM Workload Scheduler for z/OS agents extend thedynamic scheduling capability. To run access methods on externalapplications using dynamic agents, you define a job of type AccessMethod. The access method communicates with the external system tolaunch the job and returns the status of the job. The method uses thecorresponding file named optionsfile_accessmethod.opts (whereoptionsfile is the configuration file that depends on the selected accessmethod). The dynamic agent and the IBM Workload Scheduler for z/OSagent can have more than one associated .opts file to determine whichexternal environment instance it connects to. The access method can launchjobs on that instance and monitor them through completion, writing jobprogress and status information in the standard list file of the job.


Chapter 3. Installing and configuring the access methodsThe access methods documented in this guide are packaged with IBM WorkloadScheduler and are automatically installed with the product on dynamic andfault-tolerant agents. To be entitled to their use, you must purchase thecorresponding chargeable component. See the IBM Workload Scheduler Planningand Installation guide for details on installing an IBM Workload Schedulerdynamic or fault-tolerant agent.

To use any of the access methods on supported agents, you create an options file,which configures the access method and defines the workstation and the jobs thatextend the scheduling capability to external systems or applications.

Setting options for the access methodsAn options file is a text file located in the methods directory of the IBM WorkloadScheduler installation, containing a set of options to customize the behavior of theaccess method. The options must be written one per line and have the followingformat (with no spaces included):option=value

Extended agents

All access methods use two types of options file:

Global options fileA common configuration file created by default for each accessmethod installed, whose settings apply to all the extended agentworkstations defined for that method. When the global options fileis created, it contains only the LJuser option, which represents theoperating system user ID used to launch the access method. Youcan customize the global options file by adding the optionsappropriate to the access method.

The name of the global options file is accessmethod.opts, which,depending on your operating system, corresponds to:

For PeopleSoftpsagent.opts

For SAP R/3r3batch.opts

For z/OSmvsjes.opts, mvsopc.opts

For custom access methodsnetmth.opts

Local options fileA configuration file that is specific to each extended agentworkstation within a particular installation of an access method.The name of this file is XANAME_accessmethod.opts, where:

XANAMEIs the name of the extended agent workstation.


accessmethodIs the name of the access method.

If you do not create a local options file, the global options file isused. Every extended agent workstation, except for z/OS, musthave a local options file with its own configuration options.

Note: The value for XANAME must be written in uppercasealphanumeric characters. Double-byte character set (DBCS),single-byte character set (SBCS), and bidirectional text are notsupported. For information about acceptable values for theextended agent workstation name, See Table 1 on page 13.

For example, if the installation of the r3batch access methodincludes two extended agent workstations, CPU1 and CPU2, thenames of the local options files are CPU1_r3batch.opts andCPU2_r3batch.opts.


All access methods use two types of options files:

Global options fileA common configuration file created by default for each accessmethod installed, whose settings apply to all the dynamic agentworkstations defined for that method. When the global options fileis created, it contains only the LJuser option, which represents theoperating system user ID used to launch the access method. Youcan customize the global options file by adding the optionsappropriate to the access method.

The name of the global options file is accessmethod.opts, which,depending on your operating system, corresponds to:

For PeopleSoftpsagent.opts

For SAP R/3r3batch.opts

For z/OSmvsjes.opts, mvsopc.opts

Local options fileOne or more configuration files that are specific to each accessmethod. The name of this file is optionsfile_accessmethod.opts.

In a distributed environment

v If you are defining a job to run the access method byusing the Dynamic Workload Console, it is the optionfile you specify in the New > Job definition > ERP >Access Method XA Task tab.

v If you are defining the SAP R/3 job to run the accessmethod by using the Dynamic Workload Console, it isthe option file you specify in the New > Job definition> ERP > SAP Job on Dynamic Workstations XA Tasktab.

v If you are defining the job to run the access method byusing composer, it is the option file you specify in thetarget attribute of the job definition.


If you do not create a local options file, the global optionsfile is used.

In a z/OS environment

v If you are defining a job to run the access method byusing the Dynamic Workload Console, it is the optionfile you specify in the New > ERP > Access Method XATask tab.

v If you are defining the SAP R/3 job to run the accessmethod by using the Dynamic Workload Console, it isthe option file you specify in the New > ERP > SAP XATask tab.

v If you are defining the job to run the access method byusing the JOBREC statement, it is the name of theworkstation where the access method runs.

If you do not create a local options file, the global optionsfile is used.

On dynamic agents, when defining PeopleSoft or SAP jobs, theDynamic Workload Console provides an Option Editor, availablefrom the XA Task tab to edit existing option files or to create a newoption.

If you do not specify an option in theoptionsfile_accessmethod.opts file, while the access method isrunning, the product uses the values specified for that option inthe global options file. If you do not specify options either in theoptionsfile_accessmethod.opts or in the global option file, theproduct issues an error message.

For example, if the SAP R/3 access methods are installed forAGENT1 workstation, but you have two external SAP systems onwhich to schedule jobs, in the /TWS/methods directory,you create the following options files:v SAP1_AGENT1_r3batch.optsv SAP2_AGENT1_r3batch.optsIf you have a dynamic pool containing n agents, create an optionsfile for the dynamic pool and copy it into the /TWS/methods of each agent of the n agents of the pool. For example, ifthe SAP R/3 access method is installed for AGENT1 and AGENT2which belong to the dynamic pool DYN_POOL, create in the/TWS/methods directory of each agent the followingoptions files:

AGENT1

v FILEOPTS_DYN_POOL_r3batch.optsAGENT2

v FILEOPTS_DYN_POOL_r3batch.opts

The options files must be located in the /TWS/methods directory. They areread when the supported agent is started. Options are specific to each accessmethod. For details about how to configure each access method, see the followingsections:

PeopleSoftChapter 31, Configuring the PeopleSoft access method, on page 217.

Chapter 3. Installing and configuring the access methods 9

||||

SAP R/3Chapter 6, Configuring the SAP R/3 access method, on page 43.

z/OS Chapter 34, Configuring the z/OS access method, on page 243.

Option value inheritanceThis property is currently available for r3batch only. Local options files can inheritexisting values from the same options in the global options file r3batch.opts. Foran access method, the options are listed twice; once as global options and once aslocal options. If the local options file does not contain a value for the option, thenthe value for that option in the global options file is used. Otherwise the optionvalue in the local options file is always used.

For example, you might want to define the same value for the Ljuser option and adifferent value for the retrieve_joblog option. To do this, you define the Ljuseroption value in the r3batch.opts file. Then you define a different value for theretrieve_joblog option in each local options file. This results in the followingactions when launching the SAP R/3 job:v The value for the Ljuser option is extracted from the r3batch.opts file.v The value for the retrieve_joblog option is taken from each local options file.

Editing the options filesTo modify a local or global options file, or to create a local options file, you canuse either a text editor or the Option Editor described in Using the OptionEditor.

When you define access method jobs on dynamic workstations with the DynamicWorkload Console, you have the additional choice of editing the options files fromone the definition panels of the access method job.

Using the Option EditorUsing the Option Editor.

How you use the Option Editor to perform the following tasks:v Modify local or global options file, see Modifying local or global options files

on page 12.v Create a local options file, see Creating local options files on page 12.To start the Option Editor, go to the TWS_home/methods/opted directory of your IBMWorkload Scheduler installation and, depending on your operating system, run thefollowing command:

On Windows operating systemsopted.bat

On UNIX operating systemsopted.sh

Note: To use the Option Editor on a UNIX workstation, you must have agraphical environment.

The Option Editor automatically loads all the existing global and local options filesgrouped by access method.


The Option Editor window has three main areas, as shown in Figure 2. To choosewhich areas you want to see, select View > Show. The areas are:

File Options TreeShows a list of all the existing options files, grouped by method.

Option DescriptorGives a description of the current selection.

File Options ViewDisplays the options of a selected file in any of the three available views.

The Option Editor provides three possible views of an options file. To change theview in which the options file is displayed select View > Display As. The viewsare:

SimpleDisplays the options as a sequence of tabs that you can select to edit oneoption at a time. To view or edit an option, select the tab with the optionname to display the field for the value. This is the easiest way to editoptions, because you only see the actual value that is used in the file.Inherited or default values are not displayed.

Table Provides a tabular view of all the options for a selected file. This is thedefault view. For each option the following columns are displayed:

Name The name of the option.

Options Files Tree Option Descriptor File Options View

Figure 2. The Option Editor


Value The value specified in the file.

Default ValueThe value used by the method if not specified in the options file orinherited.

Inherited ValueThe value obtained from the global options file if inheritance issupported by the access method. For a detailed explanation, seeOption value inheritance on page 10.

Actual ValueThe value used at run time. The values are used in the order:value, if available; inherited value, if supported; default value.

Text Displays an options file in the typical format, showing only the optionsthat have a value. This view is generally used for preview purposes,because files are shown in read-only form. Password fields are shownencrypted.

Mandatory options are identified by a yellow background and are marked with anasterisk (*). Options that are not correctly entered are shown with a redbackground. The Option Editor performs only syntactic checks.

Restrict access to the Option Editor. If you have multiple installations of asupported agent, you can increase security by maintaining only one copy of theOption Editor, for example, on the master workstation.

Modifying local or global options filesTo modify local or global options files, using the Option Editor, perform thefollowing steps:1. From the File Options Tree area, select the options file that you want to

modify. The options are displayed in the File Options View area.2. Select the option that you want to modify and modify its value.3. Save and close the options file.

Creating local options filesWhile global options files are created each time you install an access method, youcreate local options files when you define a new supported agent workstation. Tocreate a local options file, using the Option Editor, perform the following steps:1. Click File > New in the menu bar. The New Option File window is displayed.2. In the Insert XA CPU Name field:

Extended agentsEnter the name of the extended agent workstation XANAME for whichyou want to create an options file.


optionsfileThe name of the options file. This value can be different fromthe dynamic agent and IBM Workload Scheduler for z/OSagent workstation name.

3. Select an access method from the Insert Method Name drop-down menu.Extended agents

accessmethodThe access method you selected.



accessmethodThe access method you selected.

4. Enter values for the options you want to define.5. Save and close the options file.

Defining supported agent workstationsA workstation definition is required for each entity of an access method throughwhich IBM Workload Scheduler schedules and launches jobs. For further detailsabout supported agents, see Chapter 2, Supported agent workstations, on page 5.

Creating a workstation using the Dynamic Workload ConsoleHow to create a workstation definition for supported agents using the DynamicWorkload Console.

Extended agents

To define an extended agent workstation using the Dynamic WorkloadConsole, perform the following steps:1. From the Dynamic Workload Console portfolio, click Administration >

Workload Environment Design > Create Workstations.2. Select an engine, distributed or z/OS, from the list and click Create

Workstation.3. In the Workstations properties panel, specify the attributes for the

extended agent workstation you are creating. For all the details aboutavailable fields and options, see the online help by clicking the "?" inthe top-right corner. In the workstation definition, specify the accessmethod and other properties, as shown in Table 1. For furtherinformation about the workstation definition properties, see IBMWorkload Scheduler User's Guide and Reference

4. To assign the workstation to an existing domain or to create a newdomain, click Assign to Domain.

5. Click Save.

The following table shows how to complete some specific fields of theworkstation properties panel for extended agents.

Table 1. How to complete the extended agents definitionField Description by Access Method

PeopleSoft z/OS SAP R/3

Name The name for the extended agent workstation. For all access methods (except forz/OS, which always has a limit of 8 characters), the name must start with a letter andcan contain alphanumeric characters, dashes, and underscores. The maximum lengthis 16 characters. Workstation names must be unique and cannot be the same asworkstation class and domain names. Double-byte character set (DBCS), single-bytecharacter set (SBCS), and bidirectional text are not supported. If a workstation namecontains these characters and, as a result, the options file name contains the samename, the workstation cannot be validated by the SAP system.

For all the access methods, this name must be consistent with the name of the optionsfile associated with the extended agent workstation. That is, if the options file name isMYXAGENT_accessmethod.opts, then MYXAGENT and Name must be the same.


Table 1. How to complete the extended agents definition (continued)Field Description by Access Method

PeopleSoft z/OS SAP R/3

Node Name null The node name or IP addressof the z/OS system. Fullyqualified domain names areaccepted.

null

TCP Port Any number other than0.

The TCP/IP address (portnumber) of the z/OS gatewayon the z/OS system. Enter thesame value as the SYSTSINvariable PORT.

Any number other than 0.

Access Method psagent Depending on your jobscheduling interface, one of thefollowing:

mvsjes To launch andmonitor z/OS jobsusing JES2 or JES3.

mvsopcTo launch andmonitor z/OS jobsusing IBM WorkloadScheduler for z/OS.

Note: In UNIX operatingsystems, the name is casesensitive and must belowercase.

r3batchNote: In UNIX the nameis case sensitive and mustbe lowercase.

Dynamic agents and IBM Workload Scheduler for z/OS agentsThe agents are automatically registered to the IBM Workload Schedulernetwork. For further information about the dynamic agents registration,see IBM Workload Scheduler User's Guide and Reference.

Creating a workstation using the command lineYou can define supported agents workstations also using the composer commandline of IBM Workload Scheduler.

Extended agentsThe following example shows a definition for a z/OS extended agentworkstation named MVSCPU that uses the mvsjes access method.cpuname MVSCPU description "zOS extended agent"

os othernode mvsesa36.rome.tivoli.comtcpaddr 5000domain masterdmfor maestro

type x-agenthost ROCIOUSaccess mvsjes

end

Dynamic agentsThe following example shows a definition for a dynamic agent workstationnamed LINUX248 that uses the secure protocol https to connect to theBroker server.


CPUNAME LINUX248DESCRIPTION "This workstation was automatically created."OS UNIXNODE linux248.romelab.it.ibm.com SECUREADDR 31114TIMEZONE Europe/RomeFOR MAESTRO HOST NC118003_DWB

AGENTID "FD640FCA740311E18C4EE96D727FA991"TYPE AGENTPROTOCOL HTTPS

END

For details about defining workstations with composer, see the IBM WorkloadScheduler User's Guide and Reference.

Defining workstations for end-to-end schedulingHow to create a workstation definition for end-to-end environment.

Scheduling in an end-to-end environment means that in IBM Workload Schedulerfor z/OS you are scheduling and monitoring jobs that are physically running onIBM Workload Scheduler workstations. For the agents supported in the z/OSenvironment, see Chapter 2, Supported agent workstations, on page 5.

Extended agents

Extended agent workstations must be defined as fault-tolerantworkstations in IBM Workload Scheduler for z/OS.

A fault-tolerant workstation is the IBM Workload Scheduler for z/OSdefinition of an existing IBM Workload Scheduler agent in the distributednetwork. The IBM Workload Scheduler agent is where the job associatedwith the fault-tolerant workstation actually runs in the distributednetwork.

To define the extended agent workstation in IBM Workload Scheduler forz/OS, you must:1. Define the workstation in the CPUREC initialization statement. For an

example, see Creating the CPUREC statement for extended agents.2. Add the same workstation definition to the database using ISPF or the

Dynamic Workload Console. For a description of how to define theworkstation using the Dynamic Workload Console, see DynamicWorkload Console User's Guide. For an example, see Defining theworkstation with ISPF on page 16.

IBM Workload Scheduler for z/OS agents

To define the agent workstation with z-centric capability in IBM WorkloadScheduler for z/OS, add the workstation definition to the database usingISPF or the Dynamic Workload Console. For further information, seeScheduling End-to-end with z-centric Capabilities.

Creating the CPUREC statement for extended agentsThis section is valid only for Extended agents. Create the CPUREC statement for theworkstation in the TOPOLOGY initialization statement. The TOPOLOGY initializationstatement is used to define parameters related to the topology of the connectedIBM Workload Scheduler network. Such a network topology statement is made upof one or more (one for each domain) DOMREC statements that describe the topologyof the distributed network, and by several CPUREC statements, one for eachfault-tolerant workstation.


The following example shows a CPUREC statement for an SAP R/3 extended agentworkstation named R3XA. The extended agent is hosted by a IBM WorkloadScheduler agent named TWSA, which is also the domain manager of DOMAIN1.****************TPLGINFO MEMBER ***************************

/*********************************************************************//* DOMREC: Domain definition *//*********************************************************************/DOMREC DOMAIN(DOMAIN1)

DOMMNGR(TWSA)DOMPARENT(MASTERDM)

/*********************************************************************//* CPUREC: Extended agent workstation definition *//*********************************************************************/CPUREC CPUNAME(R3XA)

CPUOS(OTHER)CPUNODE(NODE1)CPUDOMAIN(DOMAIN1)CPUHOST(TWSA)CPUTYPE(XAGENT)CPUACCESS(r3batch)CPUUSER(TWSuser)CPUTZ(Europe/Rome)

/*********************************************************************//* CPUREC: Domain manager workstation definition *//*********************************************************************/CPUREC CPUNAME(TWSA)

CPUNODE(NODE1)CPUAUTOLINK(ON)CPUDOMAIN(DOMAIN1)CPUTYPE(FTA)CPUUSER(TWSuser)CPUTZ(Europe/Rome)

The following keywords define R3XA as an extended agent:

CPUACCESSThe extended agent access method. For SAP R/3, it is r3batch.

CPUHOSTThe name of the IBM Workload Scheduler workstation hosting theextended agent. It cannot be another standard agent or extended agent.

CPUTYPEThe workstation type. For an extended agent, it must be XAGENT.

Note: The CPUREC statement does not exist for a IBM Workload Scheduler for z/OSagent workstation.

For further information about CPUREC for extended agents, see Customization andTuning.

Defining the workstation with ISPFHow to create a workstation definition with ISPF.

This section shows the ISPF definition for extended agents and agents withz-centric capability.

Extended agents

In ISPF, define the workstation as computer automatic and then set the FTWork station field to Y. The CPUREC statement with the three keywords


described in Creating the CPUREC statement for extended agents onpage 15 provides the extended agent specification.

Note: Make sure you write the CPUREC statement before making the ISPFor Dynamic Workload Console definition, because they have no effectwithout the CPUREC statement.

IBM Workload Scheduler for z/OS agentsFor detailed information and examples about the ISPF definition of IBMWorkload Scheduler for z/OS agents with z-centric capabilities, seeScheduling End-to-end with z-centric capabilities.

Defining jobs for supported agentsTo run and monitor a PeopleSoft, SAP R/3, or z/OS job with IBM WorkloadScheduler, the supported agents, or access method require an IBM WorkloadScheduler job definition, where you specify the external job you want to schedule,the workstation (also defined in IBM Workload Scheduler) on which it is to run,and any recovery actions. To define the job, use either of the following methods:v Dynamic Workload Console.v IBM Workload Scheduler composer command line.

If you are scheduling in an end-to-end environment, to define the job, use either ofthe following methods:v Dynamic Workload Console.v IBM Workload Scheduler for z/OS ISPF dialogs. You must also create a member

in the SCRIPTLIB with a JOBREC statement for the job.

Jobs defined for supported agents are added to job streams and scheduled in thesame way as any other job in IBM Workload Scheduler and IBM WorkloadScheduler for z/OS.

-------------- CREATING GENERAL INFORMATION ABOUT A W0RK STATION --------------Command ===>

Enter the command R for resources A for availability or M for access methodabove, or enter data below:

WORK STATION NAME ===> R3XADESCRIPTION ===> Extended agent for R/3 access method____________________WORK STATION TYPE ===> C G General, C Computer, P PrinterREPORTING ATTR ===> A A Automatic, S Manual start and completion

C Completion only, N Non reportingFT Work station ===> Y FT Work station, Y or NPRINTOUT ROUTING ===> SYSPRINT The ddname of daily plan printout data setSERVER USAGE ===> N Parallel server usage C , P , B or N

Options:SPLITTABLE ===> N Interruption of operation allowed, Y or NJOB SETUP ===> N Editing of JCL allowed, Y or NSTARTED TASK, STC ===> N Started task support, Y or NWTO ===> N Automatic WTO, Y or NDESTINATION ===> ________ Name of destination

Defaults:TRANSPORT TIME ===> 00.00 Time from previous work station HH.MMDURATION ===> ________ Duration for a normal operation HH.MM.SS

Figure 3. Defining an Extended Agent workstation


Defining jobs with the Dynamic Workload ConsoleHow to create a job definition for supported agents using the Dynamic WorkloadConsole.

Steps for defining a job for supported agents.

To define jobs, follow these steps:1. From the Dynamic Workload Console portfolio, click Administration >

Workload Design > Manage Workload Definitions.2. Specify an engine name, either distributed or z/OS. The Workload Designer

window opens. Job types and characteristics vary depending on whether youselect a distributed or a z/OS engine.

3. In the Working List pane, select New > Job Definition.4. Select the category and type of job you want to create.

v For SAP jobs, ERP > SAP Job on XA Workstations or SAP Job on DynamicWorkstations. See Creating SAP Standard R/3 jobs from the DynamicWorkload Console on page 59.

v For z/OS and PeopleSoft, ERP > Access Method.5. In the properties panel, specify the attributes for the job definition you are

creating. For all the details about available fields and options, see the onlinehelp by clicking the "?" in the top-right corner.

6. Click Save to save the job definition in the database.

Note: The access method for SAP R/3 provides supplementary features if you usethe alternative steps described in Create an SAP job and associate it to an IBMWorkload Scheduler job on page 60 or Creating a SAP job from the DynamicWorkload Console on page 63. You can create native SAP R/3 Standard jobs on aremote SAP system directly from the Dynamic Workload Console.

Defining jobs using the command lineYou can also define jobs using the composer command line of IBM WorkloadScheduler.

Extended agentsThe following example describes an IBM Workload Scheduler job namedpsjob2 that runs on a PeopleSoft extended agent workstation namedxaps002. IBM Workload Scheduler logs on to UNIX operating system aspsjobs and launches a job under PeopleSoft. The PeopleSoft process isnamed XRFWIN. If recovery is needed, IBM Workload Scheduler runs jobrecov2 and then continues processing.xaps002#psjob2

streamlogon psjobsscriptname-process XRFWIN -type SQR Report -runcontrol 1 -runlocationdescr PSNTdescription "peoplesoft job #2"recovery continue after recov2

The arguments of scriptname differ by application. For details, see:v Task string parameters for PeopleSoft jobs on page 225.v Task string to define SAP jobs on page 68.v Task definition syntax for z/OS jobs scheduled with IBM Workload

Scheduler on page 245.


Dynamic agentsThe following example describes a IBM Workload Scheduler job namedDYN_JOB_R3_0001 that runs on a dynamic agent workstation namedNC112015_1. The IBM Workload Scheduler launches a job in a SAPenvironment named JOB_APPS_93.NC112015_1#DYN_JOB_R3_0001TASK

/ -job JOB_APPS_93 -i 14514200 -c c

-flag ENABLE_APPL_RC

RECOVERY STOP

For more information about using the composer command line to define jobs, seeIBM Workload Scheduler: User's Guide and Reference.

Defining jobs for end-to-end schedulingExtended agents

Extended agent jobs scheduled to run in an end-to-end environmentcannot be defined using the Dynamic Workload Console or the IBMWorkload Scheduler command line, but must be added to the SCRIPTLIB ofIBM Workload Scheduler for z/OS.

In the OPERATIONS ISPF panel of IBM Workload Scheduler for z/OS,extended agent jobs are defined like any other job, but with the specificattribute for a job defined on an extended agent workstation. Thefollowing example shows the definition of a job named SAPJOB. This is theIBM Workload Scheduler for z/OS job that drives the running of on SAPR/3 job (named BAPRINT46B as shown in the next example). It shows as anextended agent job because the associated workstation is an extendedagent workstation named R3XA.

--------------------------------- OPERATIONS -----------------Row 1 to 1 of 1Command ===> Scroll ===> PAGE

Enter/Change data in the rows, and/or enter any of the followingrow commands:I(nn) - Insert, R(nn),RR(nn) - Repeat, D(nn),DD - DeleteS - Select operation details, J - Edit JCLEnter the TEXT command above to include operation text in this list, or,enter the GRAPH command to view the list graphically.

Application : APLL1 FTW appl

Row Oper Duration Job name Internal predecessors Morepredscmd ws no. HH.MM.SS -IntExt- R3XA 001 00.00.01 SAPJOB___ ___ ___ ___ ___ ___ ___ ___ ___ 0 0******************************* Bottom of data ********************************

Figure 4. Defining an Extended Agent job for end-to-end scheduling


For each job, create a member in the SCRIPTLIB of IBM Workload Schedulerfor z/OS with details about the job in a JOBREC statement. A SAPJOBmember was created for the job of the previous example. It contains aJOBREC statement like this:JOBREC

JOBCMD(/-job BAPRINT46B -user MAESTRO -i 14160001 -c C)JOBUSR(twsila)

The string in JOBCMD is read and interpreted by the access method beforerunning the job. The job of this example, BAPRINT46B, was previouslydefined on SAP R/3 and assigned with an ID of 14160001, that wasmanually written in JOBCMD.

The following example is for a PeopleSoft job. The entire string thatfollows the JOBCMD keyword must be enclosed within quotation marks ("),because for PeopleSoft jobs single quotes are already used in the string.JOBREC

JOBCMD("/ -process XRFWIN -type SQR Report -runcontrol IWS")JOBUSR(PsBuild)

IBM Workload Scheduler for z/OS agentsFor information about the jobs definition for agent with z-centriccapabilities, see Scheduling End-to-end with z-centric capabilities.

The arguments of JOBCMD differ by application. For details, see:v Task string parameters for PeopleSoft jobs on page 225.v Task string to define SAP jobs on page 68 or Chapter 9, Defining SAP jobs

dynamically, on page 85.v Task definition syntax for z/OS jobs scheduled with IBM Workload Scheduler

on page 245.

Submitting jobsTo submit jobs on the supported agent workstation, perform the following steps:1. Verify that the application system to which the job belongs and the related

database is up and running.2. Launch the job. For details, see:

Extended agents

v IBM Workload Scheduler User's Guide and Reference for conmancommand line.

v Dynamic Workload Console User's Guide for Dynamic WorkloadConsole.

Dynamic agents

v IBM Workload Scheduler User's Guide and Reference for conmancommand line.


IBM Workload scheduler for z/OS agents

v IBM Workload Scheduler for z/OS: Scheduling End-to-end with z-centricCapabilities for ISPF panel.



Configuring FIPS modeConfigure IBM Workload Scheduler to use Federal Information ProcessingStandards (FIPS) cryptographic modules.

Federal Information Processing Standards (FIPS) are standards and guidelinesissued by the National Institute of Standards and Technology (NIST) for federalcomputer systems. FIPS are developed when there are compelling federalgovernment requirements for standards, such as for security and interoperability,but acceptable industry standards or solutions do not exist. IBM WorkloadScheduler can be configured to use the FIPS 140-2 approved cryptographicprovider(s); IBMJCEFIPS (certificate 376) and/or IBMJSSEFIPS (certificate 409)and/or IBM Crypto for C (ICC (certificate 384) for cryptography. The certificatesare listed on the NIST website at http://csrc.nist.gov. For more information aboutFIPS crytographic modules, see the Administration Guide.

To configure IBM Workload Scheduler to use FIPS cryptographic modules, performthe following steps:

Edit the SDK master security properties file, java.security, located in theTWS_HOME/methods/_tools/_jvm/jre/lib/security directory to insert theIBMJCEFIPS provider (com.ibm.crypto.fips.provider.IBMJCEFIPS). IBMJCEFIPSmust precede the IBMJCE provider in the provider list.The following is an example of the edited SDK java.security file:security.provider.1=com.ibm.crypto.fips.provider.IBMJCEFIPSsecurity.provider.2=com.ibm.crypto.provider.IBMJCEsecurity.provider.3=com.ibm.jsse.IBMJSSEProvidersecurity.provider.4=com.ibm.jsse2.IBMJSSEProvider2security.provider.5=com.ibm.security.jgss.IBMJGSSProvidersecurity.provider.6=com.ibm.security.cert.IBMCertPathsecurity.provider.7=com.ibm.crypto.pkcs11.provider.IBMPKCS11security.provider.8=com.ibm.security.cmskeystore.CMSProvidersecurity.provider.9=com.ibm.security.jgss.mech.spnego.IBMSPNEGO

The following is an example of the edited java.security file if you are using theJava Virtual Machine for HP-UX or Solaris:security.provider.1=sun.security.provider.Sunsecurity.provider.2=com.ibm.crypto.fips.provider.IBMJCEFIPSsecurity.provider.3=com.ibm.crypto.provider.IBMJCEsecurity.provider.4=com.ibm.jsse.IBMJSSEProvidersecurity.provider.5=com.ibm.jsse2.IBMJSSEProvider2security.provider.6=com.ibm.security.jgss.IBMJGSSProvidersecurity.provider.7=com.ibm.security.cert.IBMCertPathsecurity.provider.8=com.ibm.i5os.jsse.JSSEProvider#security.provider.8=com.ibm.crypto.pkcs11.provider.IBMPKCS11security.provider.9=com.ibm.security.jgss.mech.spnego.IBMSPNEGO

To begin working in FIPS operational mode, enable the use_fips option in thecommon options file. See Defining the common options on page 47.


Part 2. SAP R/3 access method


Chapter 4. Introducing IBM Workload Scheduler for SAPUsing IBM Workload Scheduler for SAP, you can create, schedule, and control SAPjobs using the job scheduling features of IBM Workload Scheduler.

IBM Workload Scheduler is certified by SAP for the following SAP interfaces:v BC-XBP 6.10 (V2.0) - Background Processingv BC-XBP 7.00 (V3.0) - Background Processingv BW-SCH 3.0 - Business Information Warehousev SAP Solution ManagerCertification Category: Background Processing, Business Information Warehouse,Job Scheduling, Platform User Licensing Compliant, Scheduling, Solution ManagerReady, System Management

SAP Certified - Integration with SAP NetWeaver.

Note: For detailed information, see the SAP online product partner directory .

FeaturesTable 2 shows the tasks you can perform with IBM Workload Scheduler for SAPeither in a distributed or an end-to-end environment.

Table 2. IBM Workload Scheduler for SAP features

FeatureDistributedenvironment End-to-end

Using IBM Workload Scheduler standard jobdependencies and controls on SAP jobs

U U

Listing jobs, defining jobs, variants, and extendedvariants using the IBM Workload Schedulerinterface

U U

Defining jobs and variants dynamically at run time U U

Scheduling SAP jobs to run on specified days andtimes, and in a prescribed order

U U

Defining the national language support options U U

Using the SAP Business Warehouse Supportfunctions

U U

Customizing job execution return codes U U

Using SAP logon groups for load balancing andfault-tolerance

U U

Using Business Component-eXternal InterfaceBackground Processing (XBP 2.0 and later) interfacesupport to:

v Collectinterceptedjobs.

v Track childjobs

v Keep all jobattributes whenyou rerun a job

v Raise events

v Track childjobs

v Keep all jobattributes whenyou rerun a job

v Raise events


Table 2. IBM Workload Scheduler for SAP features (continued)

FeatureDistributedenvironment End-to-end

Using Business Component-eXternal InterfaceBackground Processing (XBP 3.0) interface supportto:

v Create criteriaprofiles to lograised events,reorganize theevent history,and interceptand relaunchjobs, accordingto the criteriayou specify.

v SAPapplication logand applicationreturn code

v Spool listrequest anddisplay for jobsthat have run.

v Temporaryvariants

v Create criteriaprofiles to lograised events,reorganize theevent history,and interceptand relaunchjobs, accordingto the criteriayou specify.

v SAPapplication logand applicationreturn code

v Spool listrequest anddisplay for jobsthat have run.

v Temporaryvariants

Assigning an SAP job to a server group, for batchprocessing

U U

Exporting SAP factory calendars and adding theirdefinitions to the IBM Workload Scheduler database

U

Defining internetwork dependencies and event rulesfor IBM Workload Scheduler based on SAP events

U

Defining event rules based on IDoc records U

Defining event rules based on CCMS MonitoringArchitecture alerts

U

Rerunning a job that submits a process chain from aspecific process, from failed processes, or as a newinstance

U U

Displaying the details of a job that submits aprocess chain

U U

Enabling job throttling U U

Scheduling process for the agent workstation hosting the r3batchaccess method

IBM Workload Scheduler launches jobs in SAP using IBM Workload Scheduler jobsdefined to run on a supported agent workstations.

Supported agent workstations include:v extended agentsv dynamic agentsv IBM Workload Scheduler for z/OS AgentsSee Chapter 2, Supported agent workstations, on page 5 for more details aboutthese agent workstations.


The supported agent workstations use the access method, r3batch, to pass SAPjob-specific information to predefined SAP instances. The access method usesinformation provided in an options file to connect and launch jobs on an SAPinstance.

Multiple extended agent workstations can be defined to use the same host, byusing multiple options entries or multiple options files. Using the SAP extendedagent name as a key, r3batch uses the corresponding options file to determinewhich instance of SAP will run the job. It makes a copy of a template job in SAPand marks it as able to run with a start time of start immediate. It then monitorsthe job through to completion, writing job progress and status information to a jobstandard list on the host workstation.

On dynamic agent workstations, more than one options file can be associated tothe workstation.

For more information about job management, refer to the IBM Workload Scheduler:User's Guide and Reference.

For more detailed information about configuration files on extended agents anddynamic agents, see Chapter 6, Configuring the SAP R/3 access method, on page43.

Roles and responsibilitiesIn a typical enterprise, different users contribute to the implementation andoperation of the product. Table 3 describes the roles and responsibilities of all usersin the process model, showing the tasks they perform.

Table 3. Roles and responsibilities in IBM Workload Scheduler for SAPUser role User task

IBM Workload Scheduleradministrator

v Creating the IBM Workload Scheduler RFC useron page 31

v Creating the authorization profile for the IBMWorkload Scheduler user on page 31

v Copying the correction and transport files onpage 34

v Importing ABAP/4 function modules into SAPR/3 on page 35

Chapter 4. Introducing IBM Workload Scheduler for SAP 27

Table 3. Roles and responsibilities in IBM Workload Scheduler for SAP (continued)User role User task

IBM Workload Schedulerconfigurator

v Changing the IBM Workload Scheduler RFC userID password on page 38

v Migrating from previous versions on page 40v Print parameter and job class issues on page 40v Defining the configuration options on page 44v Connecting to the SAP system on page 56v Creating SAP Standard R/3 jobs from the

Dynamic Workload Console on page 59

v Chapter 11, Using the BDC Wait option, on page105

v Implementing job interception on page 107v Defining user authorizations to manage SAP R/3

Business Warehouse InfoPackages and processchains on page 117

v Setting and using job throttling on page 133v Chapter 15, Exporting SAP R/3 factory

calendars, on page 139

v Setting National Language support options onpage 179

IBM Workload Scheduler developer v Editing a standard SAP job on page 67v Task string to define SAP jobs on page 68v Displaying details about a standard SAP job on

page 77

v Verifying the status of a standard SAP job onpage 77

v Deleting a standard SAP job from the SAPdatabase on page 78

v Balancing SAP workload using server groups onpage 78

v Chapter 9, Defining SAP jobs dynamically, onpage 85

v Managing SAP R/3 Business WarehouseInfoPackages and process chains on page 118

IBM Workload Scheduler developer v Chapter 16, Defining internetwork dependenciesand event rules based on SAP R/3 backgroundevents, on page 143

v Chapter 17, Defining event rules based on IDocrecords, on page 151

v Chapter 18, Defining event rules based on CCMSMonitoring Architecture alerts, on page 159

IBM Workload Scheduler operator v Rerunning a standard SAP job on page 82v Mapping between IBM Workload Scheduler and

SAP job states on page 79

v Raising an SAP event on page 81v Killing an SAP job instance on page 80v Displaying details about a process chain job on

page 123


Configuring user authorization (Security file)IBM Workload Scheduler manages security through the use of a configuration file,the security file. In the security file, you specify which scheduling objects a usercan manage and how. You define these settings by writing user definitions. A userdefinition is an association between a name and a set of users, the objects they canaccess, and the actions they can perform on the specified objects.

For more detailed information about the security file, security file syntax, and howto configure the security file, see "Configuring user authorization (Security file)" inthe Administration Guide.

The following table displays the access keywords required to grant authorization toaccess and work with SAP scheduling objects assigned to IBM Workload Schedulerusers.

Table 4. Access keywords for activities with SAP scheduling objects

Activity

Accesskeywordsrequired

Dynamic WorkloadConsole

Define or search for SAP jobs on an extended agent workstation. display on theworkstation

Retrieve the spool list on an extended agent workstation. display on theworkstation

Rerun from a step on an extended agent. rerun on thejob

Define or search for SAP jobs on a dynamic agent workstation, pool, ordynamic pool.

display andrun on theworkstation

Retrieve the spool list on a dynamic agent workstation, pool, or dynamicpool.

display andrun on the job

Rerun from a step on a dynamic agent workstation, pool, or dynamic pool. rerun on thejob

Unicode supportIBM Workload Scheduler access method for SAP supports the Unicode standard.

What is UnicodeUnicode was devised to address the problem caused by the profusion of code sets.Since the early days of computer programming hundreds of encodings have beendeveloped, each for small groups of languages and special purposes. As a result,the interpretation of text, input, sorting, display, and storage depends on theknowledge of all the different types of character sets and their encodings.Programs are written to either handle one single encoding at a time and switchbetween them, or to convert between external and internal encodings.

The problem is that there is no single, authoritative source of precise definitions ofmany of the encodings and their names. Transferring text from one computer toanother often causes some loss of information. Also, if a program has the code andthe data to perform conversion between many subsets of traditional encodings,then it needs to hold several Megabytes of data.

Chapter 4. Introducing IBM Workload Scheduler for SAP 29

Unicode provides a single character set that covers the languages of the world, anda small number of machine-friendly encoding forms and schemes to fit the needsof existing applications and protocols. It is designed for best interoperability withboth ASCII and ISO-8859-1, the most widely used character sets, to make it easierfor Unicode to be used in applications and protocols.

Unicode makes it possible to access and manipulate characters by unique numbers,their Unicode code points, and use older encodings only for input and output, if atall. The most widely used forms of Unicode are:v UTF-32, with 32-bit code units, each storing a single code point. It is the most

appropriate for encoding single characters.v UTF-16, with one or two 16-bit code units for each code point. It is the default

encoding for Unicode.v UTF-8, with one to four 8-bit code units (bytes) for each code point. It is used

mainly as a direct replacement for older MBCS (multiple byte character set)encodings.

Unicode support on r3batchStarting with R/3 version 4.7 (R/3 Enterprise), Unicode is used on all layers of theR/3 system:v UTF-8, UTF-16, and UTF-32 on the databasev UTF-16 on the application server and graphical user interface

r3batch uses the UTF-8 code page internally. Because it communicates with SAPR/3 at the application server layer, it uses UTF-16 when communicating withUnicode-enabled SAP R/3 systems.

To use Unicode support, the following conditions must be met:v IBM Workload Scheduler access method for SAP must run on one of the

following operating systems: Microsoft Windows Server 2003 and later on IA32, 32-bit Microsoft Windows Server 2003 and later on x64, 64-bit Microsoft Windows Server 2003 and later on IA64, 64-bit IBM AIX, 64-bit Sun Solaris Operating Environment, 64-bit Sun Solaris Operating Environment for Opteron HP-UX for Integrity HP-UX for PA-RISC, 64-bit Linux on xSeries Linux on zSeries, 64-bit

The product does not support Unicode on the other operating systems where itcan be installed.

v The SAP R/3 systems that communicate with r3batch must be runningUnicode-enabled SAP R/3 versions.

If these conditions are not met, you cannot use Unicode support and must makesure that r3batch, the Dynamic Workload Console, and the target SAP R/3 systemcode page settings are aligned. Use the options related to national languagesupport described in SAP R/3 supported code pages on page 180.


Chapter 5. Configuring the SAP R/3 environmentTo communicate and manage the running of jobs on SAP R/3 systems using theaccess method for SAP R/3, perform the following configuration steps in the SAPR/3 environment.

The steps described in this chapter require that you have knowledge of an SAPR/3 Basis Administrator.

OverviewHere is an overview of the customization procedure:1. Create a new user ID for RFC communications in SAP R/3 for IBM Workload

Scheduler.2. Create the authorization profile as described in Creating the authorization

profile for the IBM Workload Scheduler user.3. Copy the correction and transport files from the IBM Workload Scheduler

server to the SAP R/3 server.4. Import the correction and transport files into SAP R/3 and verify the

installation.

Note: The import procedure adds new ABAP/4 function modules and severalnew internal tables to the SAP R/3 system. It does not modify any of the existingobjects.

Creating the IBM Workload Scheduler RFC userFor IBM Workload Scheduler to communicate with SAP R/3, you must create auser ID in SAP R/3 for IBM Workload Scheduler batch processing. For securityreasons, use a new user ID rather than an existing one.1. Create a new RFC user ID.2. Give this new RFC user ID the following attributes:

v A user type of CPIC, Communications, or DIALOG, depending on the SAPR/3 release.

v A password at least six characters in length. IBM Workload Schedulerrequires this password to start or monitor SAP R/3 jobs. If this passwordchanges in SAP R/3, you must update the options file used by r3batch withthe new password.

v The appropriate security profiles, depending on your version of SAP R/3.

Creating the authorization profile for the IBM Workload Scheduler userThe two ways to create the authorization profile for the IBM Workload Scheduleruser.

There are two alternative ways to perform this task:v Using transaction su02 and manually creating the profile.v Using the Profile Generator (transaction PFCG).


Using transaction su02 and manually creating the profilePerform the following steps:1. Write a profile name, for example Z_TWS, and a description.2. Manually add the authorizations according to the following table:

Object Description Authorization

S_ADMI_FCD System authorizations S_ADMI_ALL

S_APPL_LOG Application l

Documents

Access Methods and Plug-Ins Awsaumst