tivoli | Operating System | Scheduling (Computing)

Tivoli Workload Scheduler for Applications

®

Version 8.4 (Revised June 2008)

User’s Guide

SC32-1278-05

Tivoli Workload Scheduler for Applications
®

Version 8.4 (Revised June 2008)

User’s Guide

SC32-1278-05

Note Before using this information and the product it supports, read the information in “Notices” on page 317.

This edition applies to version 8, release 4, Fix Pack 1 of IBM Tivoli Workload Scheduler for Applications (program number 5698-WSE) and to all subsequent releases and modifications until otherwise indicated in new editions. This edition replaces SC32-1278-04. © Copyright International Business Machines Corporation 2003, 2008. All rights reserved. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Contents
Figures . . . . . . . . . . . . . . vii Tables . . . . . . . . . . . . . . . ix About this publication . . . . . . . . xi
What is new in this release . . . What is new in this publication . . Who should read this publication . What this publication contains . . Publications . . . . . . . . Accessibility . . . . . . . . Tivoli technical training . . . . Support information . . . . . How to read syntax diagrams . . . xi . xi . . . . . . xiii . . . . . . xiii . . . . . . xv . . . . . . xv . . . . . . xvi . . . . . . xvi . . . . . . xvi . . . . . . . . . . Upgrading Tivoli Workload Scheduler for Applications using the silent installation . . . . Upgrading Tivoli Workload Scheduler for Applications using Tivoli Configuration Manager . Upgrading Tivoli Workload Scheduler for Applications using twsappsinst . . . . . . . Uninstalling . . . . . . . . . . . . . . Before uninstalling . . . . . . . . . . . Uninstalling the language pack using ISMP wizard . . . . . . . . . . . . . . . Uninstalling Tivoli Workload Scheduler for Applications using ISMP wizard . . . . . . Uninstalling Tivoli Workload Scheduler for Applications or its language pack using Tivoli Configuration Manager . . . . . . . . . Uninstalling the language pack using silent uninstallation . . . . . . . . . . . . . Uninstalling Tivoli Workload Scheduler for Applications using silent uninstallation . . . . Uninstalling IBM Tivoli Workload Scheduler for Applications and its language pack using twsappsinst . . . . . . . . . . . . . Completing the removal of the access method for Oracle E-Business Suite . . . . . . . . . 34 34 35 36 37 38 38

39 39 40

Part 1. Common installation and configuration tasks . . . . . . . . . 1
Chapter 1. Product overview . . . . . . 3 Chapter 2. Installing, upgrading, and uninstalling IBM Tivoli Workload Scheduler for Applications . . . . . . 5
Planning installation . . . . . . . . . . . . 5 Supported operating systems . . . . . . . . 5 Software prerequisites . . . . . . . . . . 6 Installation prerequisites . . . . . . . . . 6 The installation CDs . . . . . . . . . . . 8 Support for Internet Protocol version 6 . . . . 9 Before installing . . . . . . . . . . . . 9 Installing . . . . . . . . . . . . . . . 10 Installing Tivoli Workload Scheduler for Applications using the launchpad . . . . . . 10 Installing Tivoli Workload Scheduler for Applications using the ISMP installation wizard . 11 Installing the language pack using the ISMP installation wizard . . . . . . . . . . . 13 Installing Tivoli Workload Scheduler for Applications using the silent installation . . . . 14 Installing the language pack using silent installation . . . . . . . . . . . . . 17 Installing IBM Tivoli Workload Scheduler for Applications using Tivoli Software Distribution, version 4.1 or Tivoli Configuration Manager, version 4.2 or later . . . . . . . . . . . 19 Installing IBM Tivoli Workload Scheduler for Applications using twsappsinst . . . . . . . 26 Installing the language pack using twsappsinst 28 Completing the installation of the access method for Oracle E-Business Suite . . . . . . . . 31 Upgrading . . . . . . . . . . . . . . . 33 Upgrading Tivoli Workload Scheduler for Applications using the ISMP installation wizard . 33
© Copyright IBM Corp. 2003, 2008

40 41

Chapter 3. Setting options with the Option Editor . . . . . . . . . . . . 43
Option value inheritance . . . . Using the Option Editor . . . . Modifying local or global options Creating local options files . . . . . . files . . . . . . . . . . . . . . . . . . 44 44 46 46

| | |

Chapter 4. Defining extended agent workstations . . . . . . . . . . . . 47
Creating a workstation using the Job Scheduling Console. . . . . . . . . . . . . . . Creating a workstation using the command line . Defining workstations for end-to-end scheduling . Creating the CPUREC statement . . . . . Defining the workstation with ISPF . . . . . . . . . 47 50 51 51 52

Chapter 5. Defining extended agent jobs . . . . . . . . . . . . . . . . 53
Defining jobs with the Job Scheduling Console . General page . . . . . . . . . . . . Task page . . . . . . . . . . . . . Defining jobs using the Tivoli Workload Scheduler command line . . . . . . . . . . . . Defining jobs for end-to-end scheduling . . . . Submitting extended agent jobs . . . . . . . . 53 . 54 . 56 . 57 . 57 . 58

Part 2. Oracle E-Business Suite access method . . . . . . . . . . 59
iii

Chapter 6. Introducing Tivoli Workload Scheduler for Applications for Oracle E-Business Suite . . . . . . . . . . 61
|
Software requirements . . Features . . . . . . Roles and responsibilities . Interface software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 61 61 62

Chapter 12. Introducing Tivoli Workload Scheduler for Applications for SAP . . . . . . . . . . . . . . 89
1 Features |
Software requirements . . . . . . . . . . . . . . . . . . . . . . . . Scheduling process for the SAP extended agent . Roles and responsibilities . . . . . . . . . Unicode support. . . . . . . . . . . . What is Unicode . . . . . . . . . . . Unicode support on r3batch . . . . . . . . . . . . . . 89 90 91 91 93 93 93

Chapter 7. Configuring the Oracle E-Business Suite access method . . . 63
Defining the configuration options. . . . Examples . . . . . . . . . . . Encrypting Oracle E-Business Suite user passwords . . . . . . . . . . . . . . . . . . 63 . 65 . 66

Chapter 13. Configuring the SAP R/3 environment . . . . . . . . . . . . 95
Overview . . . . . . . . . . . . . . . 95 Creating the IBM Tivoli Workload Scheduler RFC user . . . . . . . . . . . . . . . . . 95 Creating the authorization profile for the Tivoli Workload Scheduler user . . . . . . . . . . 95 Using Transaction SU02 and manually creating the profile . . . . . . . . . . . . . . 96 Using Transaction PFCG (Profile Generator) . . 96 Copying the correction and transport files . . . . 98 Importing ABAP/4 function modules into SAP R/3 98 Changing the Tivoli Workload Scheduler RFC user ID password . . . . . . . . . . . . . 101 Migrating from previous versions . . . . . . 101 Print parameter and job class issues . . . . . . 102

Chapter 8. Defining Oracle E-Business Suite jobs . . . . . . . . . . . . . 67
Defining jobs in Oracle E-Business Suite . . . . Running a single job concurrently . . . . . Defining Oracle E-Business Suite jobs in Tivoli Workload Scheduler . . . . . . . . . . Task string parameters for Oracle E-Business Suite jobs . . . . . . . . . . . . . Tivoli Workload Scheduler and Oracle E-Business Suite job states . . . . . . . . . . . . . 67 . 67 . 67 . 67 . 69

Part 3. PeopleSoft access method

71

Chapter 9. Introducing Tivoli Workload Scheduler for Applications for PeopleSoft . . . . . . . . . . . . . 73
|
Software requirements . . . . . . . . . Features . . . . . . . . . . . . . Roles and responsibilities . . . . . . . . Scheduling process for the PeopleSoft extended agent . . . . . . . . . . . . . . PeopleSoft job tracking in Tivoli Workload Scheduler . . . . . . . . . . . . . Security . . . . . . . . . . . . . . . . . . . . 73 . 73 . 73 . 74 . 74 . 74

Chapter 14. Configuring the SAP R/3 access method . . . . . . . . . . . 103
Defining the configuration options . . . . Defining the global options . . . . . . Defining the local options . . . . . . Defining the common options . . . . . SAP R/3 option file example . . . . . Encrypting SAP R/3 user passwords . . Configuration options usage . . . . . . Connecting to the SAP system . . . . . . Connecting to a specific application server Connecting to a logon group . . . . . . . . . . . . . . . . . . . . . . . . . 103 103 105 106 111 111 111 112 112 113

Chapter 10. Configuring the PeopleSoft access method . . . . . . . . . . . 75
Defining the configuration options. . . . . PeopleSoft options file example . . . . . Connecting to more than one PeopleSoft application server . . . . . . . . . Creating a batch processing ID in PeopleSoft . Configuring the ITWS_PSXA PeopleSoft project Uploading the PeopleSoft project . . . . . . . . . . . . 75 . 77 . . . . 77 78 78 79

Chapter 15. Managing the running of SAP jobs . . . . . . . . . . . . . 115
Defining a job that runs an SAP job . . General page . . . . . . . . Task page. . . . . . . . . . Managing SAP variants using the Job Scheduling Console . . . . . . Editing a standard SAP job . . . . . Task string to define SAP jobs . . . . Rerunning an SAP job . . . . . . Rerunning a standard SAP job . . . 1 Rerunning a process chain job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 . 116 . 118 . . . . . . 126 128 129 137 137 138

Chapter 11. Defining PeopleSoft jobs
Defining Peoplesoft jobs in Tivoli Workload Scheduler . . . . . . . . . . . . . Task string parameters for PeopleSoft jobs . Configuring the job status mapping policy . . . . .

83
. 83 . 83 . 85

Chapter 16. Managing SAP jobs . . . 141
Displaying details about a standard SAP job . Verifying the status of a standard SAP job . . . . . 141 . 144

1 Displaying details about a process chain job . . . 142

Part 4. SAP R/3 access method . . . 87
iv
IBM Tivoli Workload Scheduler for Applications: User’s Guide

Deleting a standard SAP job from the SAP database . . . . . . . . . . . . . . | Balancing SAP workload using server groups . Mapping between Tivoli Workload Scheduler and SAP job states . . . . . . . . . . . . Raising an SAP event . . . . . . . . . . 1 Killing an SAP job instance . . . . . . . .

. 144 . 144 . 145 . 145 . 147

| Prerequisite to defining event rules based on | SAP . . . . . . . . . . . . . . . 190 | Monitoring SAP events . . . . . . . . . 190 | Setting a filter for SAP events in the security file 192 1 1 1 1 1 1

Chapter 23. Defining event rules based on IDoc records . . . . . . . 195
Business scenario . . . . . . . . Creating event rules based on IDocs . . Events matching criteria . . . . . Examples of event rules based on IDocs . . . . . . . . . . . . . . . . 195 196 196 201

Chapter 17. Defining SAP jobs dynamically . . . . . . . . . . . . 149
Task string to define SAP jobs dynamically . . Defining attributes for ABAP steps . . . . Defining attributes for external programs and external commands steps . . . . . . . Specifying job parameters using variable substitution . . . . . . . . . . . . . Dynamically defining and updating SAP jobs: some examples . . . . . . . . . . . . . 150 . 156 . 159 . 160 . 160

Chapter 24. National Language support . . . . . . . . . . . . . . 203
Setting National Language support options . SAP R/3 supported code pages . . . . . Supported configurations and limitations . . . . . . 203 . 204 . 204

Chapter 18. Using Business Information Warehouse . . . . . . . 163
Business Warehouse components . . . . . . Defining user authorizations to manage SAP R/3 Business Warehouse InfoPackages and process chains . . . . . . . . . . . . . . . Managing SAP R/3 Business Warehouse InfoPackages and process chains . . . . . . Creating a Tivoli Workload Scheduler job that contains InfoPackages or process chains . . Displaying details about Business Warehouse InfoPackages . . . . . . . . . . . Task string to define Business Warehouse InfoPackages and process chains . . . . . . 163

Part 5. z/OS access method . . . . 205
Chapter 25. Introducing Tivoli Workload Scheduler for Applications for z/OS . . . . . . . . . . . . . . 207
|
Software requirements . . . . . . . . . Features . . . . . . . . . . . . . . Roles and responsibilities . . . . . . . . Installing, configuring, and uninstalling the z/OS gateway . . . . . . . . . . . . . . Installing . . . . . . . . . . . . . Configuring . . . . . . . . . . . . Uninstalling . . . . . . . . . . . . Additional information . . . . . . . . . Gateway software components . . . . . IEFU84 Exit . . . . . . . . . . . . Security . . . . . . . . . . . . . Console Security . . . . . . . . . . Startup . . . . . . . . . . . . . SYSTSIN variables . . . . . . . . . . z/OS gateway version . . . . . . . . Downloading z/OS gateway fixes from FTP . . Locating product support . . . . . . . . . 207 . 207 . 208 . . . . . . . . . . . . . . 208 208 210 211 212 212 212 212 213 213 213 217 218 220

. 164 . 164 . 164 . 169 . 169

Chapter 19. Using the BDC Wait option . . . . . . . . . . . . . . 173 Chapter 20. Job interception and parent-child features . . . . . . . . 175
Job interception . . . . . . Implementing job interception . The parent-child feature . . . . . . . . . . . . . . . . . . . . 175 . 175 . 180

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

Chapter 21. Exporting SAP R/3 factory calendars . . . . . . . . . . . . . 181
Business scenario . . . . . . Using the r3batch export function . . . . . . . . . . . 181 . 181

Chapter 26. Configuring the z/OS access method . . . . . . . . . . . 221
Defining the configuration options . . . . . . Defining jobs in z/OS . . . . . . . . . . Defining z/OS jobs in Tivoli Workload Scheduler Task definition syntax for z/OS jobs scheduled with Tivoli Workload Scheduler . . . . . . Task definition syntax for other z/OS jobs . . . Operational considerations for the EEWSERVE gateway task . . . . . . . . . . . . File (OPENS) dependencies syntax on z/OS files 221 222 223 223 225 226 227

Chapter 22. Defining internetwork dependencies and event rules based on SAP R/3 events . . . . . . . . . 185
Defining internetwork dependencies based on SAP events . . . . . . . . . . . . . . . . Committing SAP events by an external task . . Defining internetwork dependencies based on SAP events with the Job Scheduling Console . . . . Defining event rules based on SAP events . . . . 185 187 188 189

Chapter 27. Reference information
Technical overview . . Managing JES jobs. . Managing CA-7 jobs . . . . . . . . . . . . . . . . . . . . . . . . .

229
. 229 . 229 . 231

Contents

v

. . . . . . . . . . . 251 . . . . . . Configuration file example for the SAP access method . . . PeopleSoft access method messages . . . 327 Chapter 30. . Return code mapping for psagent and MCMAGENT . . .50x) . . . . . . . .O . . . . . . 261 Chapter 31. . . . . . .HTWGT . for . Other known problems . . . . . . Libmsg . . . . . . . . . . . . . . . . . Apache Jakarta ORO . . . .P . . . Troubleshooting . . . Timing considerations . . . . . . . . . . . . for the Platform . . 239 239 240 240 241 242 242 244 245 Notices . . . . . . Examples . . . . . . 251 Index . . .I . . . . . . . . . . . . . . . . . . . 232 234 234 235 235 Known installation problems . . . . . . . . . . . . . . . . . Message text . . . . . . . . . . . . . . Troubleshooting the SAP R/3 connection . PeopleSoft access method messages . . Messages . . HSQL Code . . . . . . . . . . . Trademarks . InfoZip CODE . . . . . . . . . . 317 Notices and information . . JXML CODE. . . . . 329 vi IBM Tivoli Workload Scheduler for Applications: User’s Guide . . . . Return code mapping file names for r3batch Mapping return codes for intercepted jobs . . . . . . . . . . . Common serviceability . 247 .N . ISMP Installer (InstallShield 10. . . . . . . . . . . 237 Chapter 28. . . . . . . . Return code mapping for r3batch . . 263 IBM Tivoli message format . . . . . . . Syntax . . . HP-UX Runtime Environment. . . . . . 249 . . . . . .properties file . . . . SAP R/3 access method messages . . . . . . . . . . . . Message number .Managing Tivoli Workload Scheduler jobs . 323 . . . . . . . . z/OS . Oracle access method messages . . . . . . . . . . . . . . . . . . . . . . Message help . . Diagnostic information . . . . . . . . . . . . Examples . . . . . . . . . . . . 257 . . 318 319 319 320 320 321 322 Chapter 29. . . . . . . z/OS gateway messages . Considerations . . . . . Java(tm) 2 . . . . . . . . . . . . . . . Checking for files on z/OS . . . . . . . . The return code mapping feature . . . . . . . . . . . .AI . . . . . . . . . . 263 263 265 265 266 270 276 278 313 314 Part 6. . . . . . . . . 247 Customizing the . . . Troubleshooting . . . . . . . . . . 239 Creating a return code mapping file . . . . . . . . . . . twsappsinst installation messages . . . . . . . . . . . . . Configuring the tracing utility . . . . . . . . . . . . . . . . . . . . .

. . 116 The Task page of the Properties . . . 1 1 17. . . . . . . The SAP Pick List panel . The Print Parameter Flags panel . .Figures | 1. . . . . . . Tivoli Dynamic Workload Console . . . . . 2003. . . . . . How extended agents work . . . . . 9. . . . . 118 The SAP Job Definition panel . 22. . 4. . . The General page of the Properties . . . . . . . . . .Job Definition panel . | 23. . . . . . . Managing high priority IDocs overview 125 126 127 142 143 146 165 167 168 177 178 179 195 1 16. . . . . 11 The Option Editor . . The Variant Information page of the Variant List panel . 15. . . | 24. 56 Defining an Extended Agent job for end-to-end scheduling . . . . . . . .Job Definition panel. . 45 Defining a workstation using the Job Scheduling Console . . . . . . . . . . . . . . .Details of a process chain job . . . .Job Definition panel . 7. . . . . The Raise Event panel . . . . . . . . 6. . . . © Copyright IBM Corp. The Table Criteria panel . 21. . . . . . 48 Defining an Extended Agent workstation 52 The General Page of the Properties . . . 14. . 20. . . . . . . . 58 The General page of the Properties . . . . . . . . The Table Criteria panel . The Table Criteria panel . . . . . . . . . . . . . 54 The Task Page of the Properties . . . . Tivoli Dynamic Workload Console . . . 2008 vii . . . . . . . . . . .Table of results . . . . . 1 25. . . . . . . . . . .Job Definition panel . . . . . . . . . . 8. . 10. 5. . . . . . 1 18. . . . . . . . 121 The Steps page of the SAP Job Definition panel . 19. 11.Job Definition panel . . 4 Welcome page. . . 3. . . The Variant List panel . . 123 13. . . . 12. The SAP Pick List panel . . 2. . . . . . . . . .

viii IBM Tivoli Workload Scheduler for Applications: User’s Guide .

. . . . . 8 Options required for silent installation . . 23. . . . . 46. . . 35 twsappsinst parameters to uninstall IBM Tivoli Workload Scheduler for Applications . . . . . . . . . 86 SAP R/3 support packages . . . . . . . File characteristics for the SAMPLIB file after receiving it . . . . . . . . . . . . . . . | | 18. 31. 53. . . . 9. . . . . 100 r3batch global configuration options . . . . 7 Installation CDs for IBM Tivoli Workload Scheduler for Applications . Status transitions in Tivoli Workload Scheduler (internal status) and the corresponding SAP R/3 status . . . . 1 28. . . SAP R/3 supported code pages . . . . . . Task string parameters for SAP jobs . . . 27 twsappsinst parameters to install IBM Tivoli Workload Scheduler for Applications language pack . . Tivoli Workload Scheduler for z/OS operation states with respect to Tivoli Workload Scheduler . . . . . . 3. 91 ABAP/4 modules . . . . . . 29 Options required for silent upgrade . 2. . 40. . . Task string parameters for SAP jobs (dynamic definition) . . . .Tables | 1. . r3batch common configuration options Placeholders and counters for extended variants . . . 35. . 60. . 6. . . . . . . . . 26. . . . . 63 Task string parameters for Oracle E-Business Suite jobs . . . 7 ISMP temporary space requirements in megabytes . . . . . . 13. . . . . . . 41. 61. 1 36. . . . 45. 25. . . . 59. . . . . . . . . . Standard inbound IDoc statuses . . 75 Task string parameters for PeopleSoft jobs 84 Relationship between the run status. . . . . . . 69 Roles and responsibilities in Tivoli Workload Scheduler for Applications for PeopleSoft . . . 22 Options to install Tivoli Workload Scheduler for Applications using SPBs . . . . History table of the SAP events raised SAP event matching with the event rule defined . . . Supported attributes for ABAP step definition Supported attributes for external programs and external commands step definition . . . . . . . 57. . 56. . . . . . . the distribution status. . 11. . . . . . . . . and the Tivoli Workload Scheduler job status . . 41 How to complete the fields of the Properties Workstation in Database panel . . . . . . . . . . 89 SAP Business Warehouse support packages 90 Tivoli Workload Scheduler for Applications for SAP features . . . . File characteristics for the LOADLIB file after receiving it . . . . . 64. . 103 r3batch local configuration options . 16. . . . . 49 Roles and responsibilities in Tivoli Workload Scheduler for Applications for Oracle E-Business Suite . . . . . . . . . File characteristics for obtaining the gateway fix pack files by FTP . . . . . 2003. . . . 52. . . . | | | | | | | | | | | | 1 1 1 1 1 1 1 1 | | | 21. . . . . 4. . . 50. . Standard outbound IDoc statuses . . . . . . . . . | 30. . 73 Psagent access method options . . . Parameters to define an SAP internetwork dependency . . 5 Disk space requirements in megabytes . . . . . . . . 105 33. . . . 106 127 131 138 1 37. 1 27. 15. 49. . . . 22 Options to install the language packs using SPBs . . . . . . . Supported operating systems . . . . . . . . . . . . . . . . 19 Software package block to install IBM Tivoli Workload Scheduler for Applications language pack . . . . . Tivoli Workload Scheduler fields used to define event rules . . . Internetwork dependency definition and possible resolution . 48. . . . . Additional z/OS software requirements Roles and responsibilities in Tivoli Workload Scheduler for Applications for z/OS . . . . 14. . Tivoli Workload Scheduler fields used to define correlation rules . . . . . . . . . Actions performed when you rerun a process chain job . . . . . . . . . . . CA-7 job states with respect to Tivoli Workload Scheduler . . . . . . 55. . 43. . 233 © Copyright IBM Corp. . 54. . . . 18 List of software package blocks to install IBM Tivoli Workload Scheduler for Applications . . 7. . 19. . . 5. . 34 twsappsinst parameters to upgrade IBM Tivoli Workload Scheduler for Applications . . 12. . . 2008 ix . 85 Relationship between the run status and the Tivoli Workload Scheduler job status . . . . . . 42. 145 152 156 159 170 179 186 187 191 191 192 192 196 197 198 199 200 204 207 208 213 218 219 220 222 229 231 38. . . . . . . . . | 22. . . . . 34. . 90 Roles and responsibilities in Tivoli Workload Scheduler for Applications for SAP . 63. 1 | 29. . . 58. . . . 39. 61 MCMAGENT access method options . 32. . . . . . . . . SYSTSIN variables . . . . . . . . . . . . 68 Tivoli Workload Scheduler and Oracle E-Business Suite job states . | 17. 15 Options for the language pack silent installation . . . . . . . . . . . 24. . 23 twsappsinst parameters to install IBM Tivoli Workload Scheduler for Applications . . . . . . . Tivoli Workload Scheduler for Applications for z/OS access method options . . 47. . . . . . . 8. . . 51. . . 10. . . . . . . . . . . . . . . . . Task string parameters for SAP R/3 jobs Placeholders for job interception template files . 44. . 62. History table of the SAP events raised SAP events matching with the event rule defined . . JES job states with respect to Tivoli Workload Scheduler . . . 20. . . . . . . . . . . Parameters of IDOCEventGenerated event type. . . . . . . .

z/OS module names . . . . Tivoli Workload Scheduler for z/OS operation occurrence states with respect to Tivoli Workload Scheduler . 257 . Known installation problems . . . 69. . . . 241 68. . . . . 66. Tivoli Workload Scheduler for Applications messages . . . . . . . Miscellaneous troubleshooting items . . . 241 Job states and return codes for the PeopleSoft access method . 67. . . . . . .65. 233 Job states and return codes for the Oracle E-Business Suite access method . . . . . . 71. . . 270 x IBM Tivoli Workload Scheduler for Applications: User’s Guide . 70. . . . . . 251 . 263 .component codes .

and use the IBM® Tivoli® Workload Scheduler access methods that run and control jobs of the following applications: v Oracle E-Business Suite v PeopleSoft v SAP R/3 v z/OS® What is new in this release For information about the new and changed functions in this release. if the text was changed or added with respect to the previous version. Oracle E-Business Suite access method v To help you identify the users' roles and tasks. Part 1. and so on. v By the number of a fix pack. For information about the APARs that this release addresses. 1 to refer to Fix Pack 1. 2008 xi .About this publication The IBM Tivoli Workload Scheduler for Applications: User’s Guide provides information about how to install. see Tivoli Workload Scheduling Suite: Overview. Part 2. Part 3. see “Completing the installation of the access method for Oracle E-Business Suite” on page 31. a table that links roles and responsibilities is provided in Table 17 on page 61.ibm. 2003. Common installation and configuration tasks v The following operating systems are no longer supported: – Compaq Tru64 – IBM Sequent Dynix – SGI IRIX v Information about supporting Internet Protocol version 6 is provided in “Support for Internet Protocol version 6” on page 9. What is new in this publication This section describes what has changed in this publication since version 8. PeopleSoft access method © Copyright IBM Corp. For example.com/support/docview. see the IBM Tivoli Workload Scheduler for Applications Download Document at http:// www. For details. v Information about how to install the product using the launchpad is provided in “Installing Tivoli Workload Scheduler for Applications using the launchpad” on page 10. set up.wss?rs=673&uid=swg24017449. v The procedure to complete the installation of the Oracle E-Business Suite access method has been modified. 1 1 1 1 1 1 | | | | | | | | | | | | | | | Note: Changed or added text is marked in the left margin as follows: v By a vertical bar. if the changed or added text applies only after a particular fix pack is installed.3 fix pack 1.

Scheduling for SAP BW 3.” on page 195. Job Scheduling. For detailed information. see the SAP online product partner directory. You can assign a SAP R/3 job to a server group. For details. You can now export SAP R/3 factory calendars into an output file compatible with the Tivoli Workload Scheduler composer and use it to create or replace Tivoli Workload Scheduler calendars.0 .0) Certification Category: Background Processing. see “Balancing SAP workload using server groups” on page 144. to perform a specific action. a table that links roles and responsibilities is provided in Table 21 on page 73. xii IBM Tivoli Workload Scheduler for Applications: User’s Guide . “Defining event rules based on IDoc records.” on page 181. according to any BDC processing failure. You can control how Tivoli Workload Scheduler sets the completion status of a job running BDC sessions. For details.What is new | | 1 1 1 1 1 1 1 1 1 1 1 1 1 | | 1 1 1 1 1 1 1 1 1 1 | | | | | | | | | | | 1 1 1 | | v To help you identify the users' roles and tasks. Scheduling.10 (Version 2.10 . To define an internetwork dependency or event rule based on SAP R/3 events.4 is certified by SAP for the following two SAP interfaces: BW-SCH 3. see Chapter 21. and to monitor and filter SAP R/3 events. Job Scheduling Qualification: Certified for SAP NetWeaver BW-XBP 6. You can determine the action performed by Tivoli Workload Scheduler when you rerun a job that submits a process chain. Part 4. a table that links roles and responsibilities is provided in Table 56 on page 208. System Management Qualification: Certified for SAP NetWeaver Note: For detailed information. v v v v v v v v You can monitor IDoc records and forward events to Tivoli Workload Scheduler. “Exporting SAP R/3 factory calendars.” on page 185. For details. a table that links roles and responsibilities is provided in Table 29 on page 91. For details. z/OS access method v To help you identify the users' roles and tasks.Background Processing. “Defining internetwork dependencies and event rules based on SAP R/3 events. SAP R/3 access method v Tivoli Workload Scheduler for Applications 8. see the bdc_job_status_failed option described in “Defining the common options” on page 106. Job Scheduling 6. To display details about an SAP process chain that you ran as a Tivoli Workload Scheduler job. refer to Chapter 23. refer to “Rerunning a process chain job” on page 138. To help you identify the users' roles and tasks. see “Displaying details about a process chain job” on page 142. Part 3. for batch processing.0 Certification Category: Business Information Warehouse. refer to Chapter 22.

users' roles and tasks.” on page 47 describes how to define extended agent workstations for all the access methods. PeopleSoft access method Part 3 contains the following chapters: v Chapter 9.” on page 43 describes how to use the Option Editor. upgrading. “Setting options with the Option Editor. Part 2. “Configuring the Oracle E-Business Suite access method. v Chapter 4. Part 3. Oracle E-Business Suite access method Part 2 contains the following chapters: v Chapter 6.” on page 73 describes software requirements. “Defining extended agent jobs.” on page 5 describes the various ways of installing.” on page 53 describes how to define extended agent jobs for all the access methods. and uninstalling the product and its language pack. together with the operating systems it supports and its prerequisites. features.” on page 3 describes the basic functions of an extended agent. “Defining extended agent workstations. v Chapter 8.” on page 63 describes how to configure the options used by the Oracle E-Business Suite access method. v Chapter 3. and interface software specifically for the Oracle E-Business Suite access method. Users of this publication should have some knowledge of: v IBM Tivoli Workload Scheduler v Tivoli Job Scheduling Console v The specific application environment What this publication contains This publication contains the following sections: Part 1.” on page 61 describes software requirements. “Installing. v Chapter 2. and other general information specific to the PeopleSoft access method. users' roles and tasks. features. upgrading.” on page 67 describes how to define Tivoli Workload Scheduler jobs specifically for the Oracle E-Business Suite access method. About this publication xiii . “Introducing Tivoli Workload Scheduler for Applications for PeopleSoft. and uninstalling IBM Tivoli Workload Scheduler for Applications. v Chapter 7.Who should read this publication Who should read this publication This publication is intended for job schedulers who intend to run and control jobs of the applications with IBM Tivoli Workload Scheduler. “Product overview. “Introducing Tivoli Workload Scheduler for Applications for Oracle E-Business Suite. v Chapter 5. Common installation and configuration tasks Part 1 contains the following chapters: v Chapter 1. “Defining Oracle E-Business Suite jobs.

” on page 83 describes how to define Tivoli Workload Scheduler jobs specifically for the PeopleSoft access method.” on page 185 describes how to define internetwork dependencies and event rules for Tivoli Workload Scheduler based on SAP R/3 events.” on page 75 describes how to configure the options used by the PeopleSoft access method. without creating or referencing pre-defined job templates. SAP R/3 access method Part 4 contains the following chapters: v Chapter 12. “Introducing Tivoli Workload Scheduler for Applications for SAP. and how to add the exported calendar definitions to the Tivoli Workload Scheduler database. v Chapter 15. v Chapter 24. “Configuring the PeopleSoft access method. “Configuring the SAP R/3 access method.0. v Chapter 22. “Defining event rules based on IDoc records. “Managing the running of SAP jobs. “National Language support. v Chapter 11. v Chapter 14.” on page 163 provides information on how to use the access method with the Business Information Warehouse. v Chapter 18.” on page 103 describes how to configure the options used by this access method. “Managing SAP jobs.” on page 95 describes how to configure this access method for use with SAP R/3.” on page 173 provides details on BDC wait option.” on page 181 describes how to export SAP R/3 factory calendars so that they can be processed by Tivoli Workload Scheduler. “Using the BDC Wait option. Part 5. “Exporting SAP R/3 factory calendars.” on page 195 describes how to define event rules for Tivoli Workload Scheduler based on IDoc records.” on page 175 describes the Job interception and Parent-child features of XBP 2.What this publication contains v Chapter 10. “Defining PeopleSoft jobs. features. v Chapter 13.” on page 89 describes software requirements. z/OS access method 1 1 1 | | | | | | | | 1 1 1 xiv IBM Tivoli Workload Scheduler for Applications: User’s Guide . v Chapter 21. “Defining SAP jobs dynamically. and Unicode support for the SAP R/3 access method. users' roles and tasks. Part 4. v Chapter 23. v Chapter 17. “Job interception and parent-child features. “Configuring the SAP R/3 environment. for example displaying details about a job or balancing the workload among servers. “Using Business Information Warehouse. v Chapter 20.” on page 141 describes how you can work with SAP R/3 jobs.” on page 203 describes national language support for this access method.” on page 149 describes how to create and submit SAP R/3 jobs instantly in the end-to-end scheduling environment.” on page 115 describes how to define Tivoli Workload Scheduler jobs specifically for the SAP R/3 access method. “Defining internetwork dependencies and event rules based on SAP R/3 events. v Chapter 19. v Chapter 16.

“Messages.” on page 263 provides you with help on error and warning messages issued by: – twsappsinst – z/OS gateway – PeopleSoft access method – SAP R/3 access method – Oracle E-Business Suite access method Publications Full details of Tivoli Workload Scheduler publications can be found in Tivoli Workload Scheduling Suite: Publications. users' roles and tasks for the z/OS access method. A glossary of terms used in the product can be found in Tivoli Workload Scheduling Suite: Glossary. such as restricted mobility or limited vision. About this publication xv . Accessibility Accessibility features help users with a physical disability. “Introducing Tivoli Workload Scheduler for Applications for z/OS.” on page 221 describes how to configure the options used by this access method and provides method-specific information on defining jobs. see the Accessibility Appendix in the Tivoli Workload Scheduler: Job Scheduling Console User’s Guide. “Configuring the tracing utility.” on page 239 describes how to use the return code mapping utility.” on page 207 provides software requirements.What this publication contains Part 5 contains the following chapters: v Chapter 25. It also describes how to install the gateway component on z/OS. v Chapter 26. Part 6. v Chapter 31. For full information with respect to the Job Scheduling Console. v Chapter 30. v Chapter 29.” on page 247 describes how to configure the tracing utility. “Troubleshooting. Common serviceability Part 6 contains the following chapters: v Chapter 28. With this product. “Reference information. “The return code mapping feature. v Chapter 27. Both of these are in the Information Center as separate publications. This document also contains information about the conventions used in the publications.” on page 251 provides some general troubleshooting information. “Configuring the z/OS access method.” on page 229 provides reference information for operating with the supported job schedulers and lists gateway messages. features. you can use assistive technologies to hear and navigate the interface. You can also use the keyboard instead of the mouse to operate all features of the graphical user interface. to use software products successfully.

see the Accessibility Appendix in the Tivoli Workload Scheduler: User's Guide and Reference. xvi IBM Tivoli Workload Scheduler for Applications: User’s Guide . and other information. Technotes. syntax is described in diagrams like the one shown here. and you need to work with someone from IBM. How to read syntax diagrams Throughout this publication. see the Appendix about support information in Tivoli Workload Scheduler: Troubleshooting Guide. you want to resolve it quickly. Tivoli technical training For Tivoli technical training information. For more information about these three ways of resolving problems. v Obtaining fixes: You can locate the latest fixes that are already available for your product. IBM provides 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. v Contacting IBM Software Support: If you still cannot solve your problem. refer to the following IBM Tivoli Education Web site: http://www.com/software/tivoli/education Support information If you have a problem with your IBM software.Accessibility For full information with respect to the Tivoli Dynamic Workload Console.ibm. you can use a variety of ways to contact IBM Software Support. which describes the SRSTAT command: SRSTAT ' resource name ' SUBSYS( OPCA subsystem name MSTR ) AVAIL( KEEP RESET NO YES ) DEVIATION( KEEP amount RESET ) QUANTITY( KEEP amount RESET ) CREATE( YES NO ) TRACE( 0 trace level ) The symbols have these meanings: ───── The statement begins here.

they appear vertically in a stack. 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: STATEMENT optional item v An arrow returning to the left above the item indicates an item that you can repeat. STATEMENT optional choice 1 optional choice 2 optional choice 3 About this publication xvii . Read the syntax diagrams from left to right and from top to bottom. the entire stack appears below the main path: STATEMENT optional choice 1 optional choice 2 – A repeat arrow above a stack indicates that you can make more than one choice from the stacked items: . If a separator is required between items. ────── The statement is continued from a previous line. one item of the stack appears on the main path: STATEMENT required choice 1 required choice 2 – If choosing one of the items is optional. .Support information ────── The statement is continued on the next line. STATEMENT repeatable item v If you can choose from two or more items. ───── The statement ends here. it is shown on the repeat arrow. following the path of the line. – If you must choose one of the items.

STATEMENT required choice 1 required choice 2 required choice 3 v Parameters that are above the main line are default parameters: default STATEMENT alternative v Keywords appear in uppercase (for example. If that line cannot be split. the item attributes might not fit on one horizontal line. as shown. STATEMENT).Support information . the attributes appear at the bottom of the syntax diagram: STATEMENT required choice 1 option 1 required choice 2 required choice 3 option 2 option 1 default alternative optional choice 1( ) option 2 default alternative optional choice 2( ) xviii IBM Tivoli Workload Scheduler for Applications: User’s Guide . v For complex commands. v Parentheses and commas must be entered as part of the command syntax.

2008 1 . Common installation and configuration tasks © Copyright IBM Corp.Part 1. 2003.

2 IBM Tivoli Workload Scheduler for Applications: User’s Guide .

More than one extended agent workstation can be hosted by the same Tivoli Workload Scheduler workstation and rely on the same access method. | | | | | | | An extended agent workstation is a logical entity related to an access method hosted by the physical Tivoli Workload Scheduler workstation (a fault-tolerant agent or standard agent). mvsjes.Chapter 1. Tivoli Workload Scheduler for Applications includes the following access methods: v Oracle E-Business Suite (MCMAGENT) v PeopleSoft (psagent) v SAP R/3 (r3batch) v z/OS (mvsca7. The extended agent is defined in a standard Tivoli Workload Scheduler workstation definition. The access method communicates with the external system to launch the job and returns the status of the job. passing it job details as command line options. the host runs the access method. Figure 1 on page 4 shows how these elements fit together in the case of a typical extended agent configuration. which gives the extended agent a name and identifies the access method. Product overview Extended agents (XA) are used to extend the job scheduling functions of IBM Tivoli Workload Scheduler to other systems and applications. © Copyright IBM Corp. An extended agent is defined as a workstation that has a host and an access method. The host is a Tivoli Workload Scheduler fault-tolerant agent (FTA) or standard agent (SA). and mvsopc) To launch and monitor a job on an extended agent. The access method is a program that is run by the hosting workstation whenever Tivoli Workload Scheduler needs to interact with the external system either through its command line or the Tivoli Job Scheduling Console. 2003. 2008 3 .

opts to determine which external environment instance it will connect to.Product overview Figure 1. Extended agents can also be used to run jobs in an end-to-end environment. The access method can then launch jobs on that instance and monitor them through completion. writing job progress and status information in the standard list file of the job. where their scheduling and monitoring is performed from an IBM Tivoli Workload Scheduler for z/OS controller. How extended agents work To launch a job in an external environment. 4 IBM Tivoli Workload Scheduler for Applications: User’s Guide . The method looks at the corresponding file named WORKSTATIONNAME_methodname. Tivoli Workload Scheduler runs the extended agent access method providing it with the extended agent workstation name and information about the job.

10 Sun Solaris Operating Environment for Opteron. 2008 Table 1. version 8. 5. Supported operating systems Operating System z/OS (Gateway) z/OS (Transaction Server) Access Method SAP R/3 PeopleSoft Oracle E-Business Suite U U U U U U U U U U U U U U U U U U U U U U 5 . and uninstall Tivoli Workload Scheduler for Applications and its language pack.3. and uninstalling IBM Tivoli Workload Scheduler for Applications This chapter describes how to install. version 10 HP-UX © Copyright IBM Corp. It is divided into the following sections: v “Planning installation” v “Installing” on page 10 v “Upgrading” on page 33 v “Uninstalling” on page 36 Planning installation Refer to the following sections to plan your installation of Tivoli Workload Scheduler for Applications: v “Supported operating systems” v “Software prerequisites” on page 6 v “Installation prerequisites” on page 6 v “The installation CDs” on page 8 v “Support for Internet Protocol version 6” on page 9 v “Before installing” on page 9 Supported operating systems Table 1 lists the operating systems supported by Tivoli Workload Scheduler for Applications.2. 2003. Installing.4: | | | | | | | | | | | | | | | | | | | | Microsoft® Windows Microsoft Windows 2000 Microsoft Windows 2003 Microsoft Windows XP Professional Microsoft Vista IBM AIX IBM AIX version 5. 5.4 Sun Solaris Operating Environment Sun Solaris Operating Environment version 9.Chapter 2. upgrade. upgrading.

4 Fix Pack 1. 5.0.2. the master domain manager must have Tivoli Workload Scheduler 8.0. installed. or later.0 SuSE Linux Enterprise Server version 9 SuSE Linux Enterprise Server version 10 Linux on zSeries Red Hat Enterprise Linux Advanced Server version 4. Supported operating systems (continued) Operating System z/OS (Gateway) z/OS (Transaction Server) U U Access Method SAP R/3 PeopleSoft Oracle E-Business Suite U U U U U U U U Red Hat Enterprise Linux Advanced Server version 4. 11i v3 for Integrity IBM OS/390® IBM OS/390 V2R10 IBM z/OS IBM z/OS version 1.Supported operating systems | | | | | | | | | | | | | | | | | | | | | | | | | | | | HP-UX version 11i v2.4 Fix Pack 1.4 interacts with the following products: v Oracle E-Business Suite v PeopleSoft v SAP R/3 v z/OS Installation prerequisites Before you install the product. 10. v You have root permissions on UNIX and administrator permissions on Windows to run the installation. or later.2. Tivoli Workload Scheduler for Applications 8.8 Linux on xSeries ® ® Table 1. 6 IBM Tivoli Workload Scheduler for Applications: User’s Guide .0 SuSE Linux Enterprise Server version 9. ensure that the following prerequisites are met: v You have a working installation of Tivoli Workload Scheduler version 8. 11i v3 for PA-RISC HP-UX version 11i v2. 5. installed on your workstation.4 prerequisites Tivoli Workload Scheduler version 8.0 U U U U U U U U U U U U U U U Software prerequisites Tivoli Workload Scheduler for Applications version 8. or later. 1 1 1 Note: To define event rules based on SAP R/3 events with Tivoli Workload Scheduler for Applications 8.0.

The other installation methods do not have any temporary space requirements. v For the access method for PeopleSoft.Installation prerequisites v There are no scheduling activities currently running for the application you want to install. you have at least 10 MB of temporary space available on your workstation. Table 2. Disk space requirements in megabytes Operating system z/OS Disk Space (MB) SAP R/3 PeopleSoft Oracle E-Business Suite Microsoft Windows IBM AIX Sun Solaris Operating Environment HP-UX for PA-RISC HP-UX for Integrity Linux on xSeries Linux on zSeries 3MB 3MB 3MB 3MB 3MB 1MB 4MB 22MB 22MB 23MB 22MB 22MB 21MB 11MB 150MB 150MB 1MB 1MB 200MB 200MB 150MB 1MB 1MB 1MB Table 3 lists the temporary space required to install IBM Tivoli Workload Scheduler for Applications using the ISMP installation method. v If you are installing using the ISMP both interactive and silent: – The X Server is installed on a workstation in your environment. v If you are installing the product on HP-UX version 11. v If you are installing the language pack. ISMP temporary space requirements in megabytes Operating system Microsoft Windows ISMP temporary space (MB) 200MB Chapter 2. v The installation process is not already running on the workstation. you set the maxdsiz kernel parameter to 0x06000000 hexadecimal (100663296). the Oracle E-Business Suite server is already installed on the same physical node where the access method and the Tivoli Workload Scheduler host resides. you have the disk space indicated in Table 2 and the temporary space indicated in Table 3.0 using the ISMP Installation Wizard. the corresponding PeopleSoft environment is already installed and fully accessible from the workstation where you are installing. v There are no monitoring activities on SAP R/3 events currently running. v If you are installing the product. upgrading. Installing. v For the access method for Oracle E-Business Suite. and uninstalling IBM Tivoli Workload Scheduler for Applications 7 . You can verify this by running one of the following commands: If you are installing using ISMP ps -ef | grep setup. – The X-windows Display is appropriately exported if you are launching the installation process using a telnet session. Table 3.bin 1 If you are installing using twsappsinst ps -ef | grep twsappsinst v The Option Editor is not running.

Table 4. It also includes the following directories: v LICENSE v RESPONSE_FILE v z/OS libraries for the specific operating systems Sun Solaris.Installation prerequisites Table 3. It also includes the following directories: v LICENSE v RESPONSE_FILE v z/OS libraries for the specific operating systems Sun Solaris for Opteron. Installation CDs for IBM Tivoli Workload Scheduler for Applications CD label IBM Tivoli Workload Scheduler for Applications Installation CD 1 Operating systems AIX and Microsoft Windows. It also includes the following directories: v LICENSE v RESPONSE_FILE v z/OS libraries for the specific operating systems HP-UX for PA-RISC. ISMP temporary space requirements in megabytes (continued) Operating system IBM AIX Sun Solaris Operating Environment HP-UX for Integrity HP-UX for PA-RISC IBM z/OS Linux on xSeries Linux on zSeries 45MB 45MB ISMP temporary space (MB) 45MB 30MB 300MB 300MB The installation CDs Table 4 shows the CDs contained in IBM Tivoli Workload Scheduler for Applications and the operating systems to which they apply. It also includes the following directories: v LICENSE v RESPONSE_FILE v z/OS libraries for the specific operating systems IBM Tivoli Workload Scheduler for Applications Installation CD 2 | | | | | | | | | | | | | | | | | | IBM Tivoli Workload Scheduler for Applications Installation CD 3 IBM Tivoli Workload Scheduler for Applications Installation CD 4 IBM Tivoli Workload Scheduler for Applications Installation CD 5 IBM Tivoli Workload Scheduler for Applications Installation CD 6 8 IBM Tivoli Workload Scheduler for Applications: User’s Guide . It also includes the following directories: v LICENSE v RESPONSE_FILE v z/OS libraries for the specific operating systems HP-UX for Integrity. It also includes the following directories: v LICENSE v RESPONSE_FILE v z/OS libraries for the specific operating systems Linux and Linux S390.

jar file available on the workstation where you are installing Tivoli Workload Scheduler for Applications.45. or using twsappsinst and you want to specify an installation directory different from the IBM Tivoli Workload Scheduler user home directory.jar file corresponding to the release of PeopleSoft you are working with.4. If you are installing using the ISMP silent installation. user1 for r3batch and user2 for psagent. or later v TCP/IP for the z/OS system on IBM 3. For version 8. For example. and uninstalling IBM Tivoli Workload Scheduler for Applications 9 . /home/tws84/tws If you are installing using the ISMP silent installation or if the ISMP wizard discovery process does not detect any existing installation A name for the installation of Tivoli Workload Scheduler for Applications. Support to IPv6 is provided only on the z/OS extended agent with the following software requirements: v IBM Tivoli Workload Scheduler version 8. To make the psjoa. For example. version 8. Note: The psjoa.1.2 or later. supports Internet Protocol version 6 (IPv6) in addition to legacy IPv4. Chapter 2. For example. do the following: 1. use the psjoa. during the installation of Tivoli Workload Scheduler for Applications you are asked to provide the following information: Regardless of the installation method you use The name of the operating system user ID used to launch the access method you are installing. locate the ps_home\class\ psjoa.jar file of PeopleSoft version 8. TWS. TWS. For example. it is the same as the TWSuser name. Installing. For example.4.45 if you are working with version 8. On the workstation where the PeopleSoft application is installed. or the ISMP wizard discovery process does not detect any existing installation The path of the IBM Tivoli Workload Scheduler installation where you want to install Tivoli Workload Scheduler for Applications. Either copy the file to the workstation where you are installing Tivoli Workload Scheduler for Applications or make it accessible by mapping the path to the workstation where the PeopleSoft application is installed. 2. If you are installing using twsappsinst The TWSuser name. upgrading.jar path cannot contain special characters.Support for IPv6 | | | | | | Support for Internet Protocol version 6 IBM Tivoli Workload Scheduler for Applications. or later Before installing Depending on the installation method you use.jar file. If you are installing PeopleSoft The full path to the psjoa.

version 4. v Optionally. Insert the CD containing the installation image for your operating system into the CD drive.1 product or the Software Distribution component of Tivoli Configuration Manager. Solaris. You must install all the access methods using the same installation procedure: v The launchpad v The InstallShield MultiPlatform (ISMP) wizard v The ISMP silent installation v The Tivoli Software Distribution. If not.Installing Installing | | | | | | | | | | | | | By installing Tivoli Workload Scheduler for Applications. you can use any of the following procedures. you install: v One or more access methods to interact with the following products: – Oracle E-Business Suite For this access method. UNIX. – PeopleSoft – SAP R/3 – z/OS v The Option Editor. and Linux operating systems.2 or later v On AIX. version 4. start the launchpad: On Windows On UNIX The launchpad should start automatically. To install Tivoli Workload Scheduler for Applications and its language pack. From this user interface you can access the following sources of information: v Tivoli Workload Scheduler for Applications home page v Tivoli Workload Scheduler for Applications Download Document v Tivoli Workload Scheduler for Applications information center v Tivoli Workload Scheduler for Applications support Web site You can use the launchpad only with one of the following Web browsers: v Mozilla v Firefox v Internet Explorer (for Windows operating systems. From the root directory of the CD. you must complete the installation as described in “Completing the installation of the access method for Oracle E-Business Suite” on page 31. Depending on the operating system. one or more Tivoli Workload Scheduler for Applications language packs. from the root directory of the CD. HP-UX. | | | | | | | | | | | | | | | | | | | | | | Installing Tivoli Workload Scheduler for Applications using the launchpad Use the launchpad if you want to be guided through a set of panels that help you become familiar with the product documentation. only) The general procedure for starting the launchpad installation program is as follows: 1. the twsappsinst command. run the launchpad. run the launchpad.sh file.exe file. 2. a graphical tool to help you configure your environment after installation. 10 IBM Tivoli Workload Scheduler for Applications: User’s Guide . regardless of the installation procedure you choose.

v Add an access method to an already existing installation of Tivoli Workload Scheduler for Applications. Welcome page 3. Chapter 2. The installation starts. perform the following steps: 1. Navigate the documentation and. To install one or more access methods of Tivoli Workload Scheduler for Applications. ensure that the path where you copy the images does not contains blanks and that you maintain the CD directory structure. refer to “Installing Tivoli Workload Scheduler for Applications using the ISMP installation wizard. Note: If you decide to perform the installation from an image.” Installing Tivoli Workload Scheduler for Applications using the ISMP installation wizard This section explains how to perform the following tasks using the ISMP installation wizard: v Install IBM Tivoli Workload Scheduler for Applications. Installing. From the product CD for the operating system on which you are installing the product. and uninstalling IBM Tivoli Workload Scheduler for Applications 11 . upgrading. The Option Editor is a Java-based file editor that you use to define options for the access methods you installed.Installing using the launchpad | | | The launchpad opens: | | | | | | | | Figure 2. or from an image. when you are ready to start the installation process. For details about how to continue the installation. Using the ISMP installation wizard you also automatically install the Option Editor. click Install IBM Tivoli Workload Scheduler for Applications in the left frame of the page. run the setup installation command located in the INSTALLER directory.

If you select Install. See “Upgrading” on page 33 for a detailed description about how to upgrade from version 8.2. Install Tivoli Workload Scheduler for Applications before adding an access method.2 or 8. If the installation process does not detect any installations. If you select Add on the Select the type of installation panel. Select the language in which you want the wizard to be displayed. 5. Upgrade Proceed with step 8. or 8. The Welcome panel is displayed. Select one of the following: Install Add To install Tivoli Workload Scheduler for Applications. Click Next. Select the access methods that you want to install on your workstation and click Next. This can be the same name of 12 IBM Tivoli Workload Scheduler for Applications: User’s Guide . b. 4.4. 6. that is the name as the operating system user ID used to launch the selected method. The installation program detects and lists all the features of Tivoli Workload Scheduler for Applications that you can install on your workstation. Click Next.2. one or more additional panels request specific access method information: v For all access methods: the LJuser. To add an access method to an already existing installation of Tivoli Workload Scheduler for Applications.Installing using ISMP installation wizard 2. 7. the installation program detects and lists all the Tivoli Workload Scheduler for Applications installations that already exist on your workstation. Return to the previous panel and select Install. The Software License Agreement panel is displayed. 8. Read the welcome information and click Next. For example. To upgrade an already existing installation of Tivoli Workload Scheduler for Applications version 8. 8. the following message is displayed: The installation program did not find any Tivoli Workload Scheduler for Applications installations.4. Read the Software License Agreement information and select the radio button to accept the license agreement. If you select this option. The Select the Type of Installation panel is displayed. 3.3. or 8.4 on your workstation.3. click Next and proceed with step 7.2. click Next and proceed with step 6. If the product does not detect any existing installation a panel is displayed where you have to specify the name and the directory of another existing installation.1 to version 8. Using this option you can also repair a corrupted installation. Depending on how many and which access methods you select.x. for the name of the installation you can use the user name associated to the IBM Tivoli Workload Scheduler installation. and click OK.3 to version 8.1. a. If you select this option.2. The installation name must be unique. In this case return to step 5 and select Install. 8. the installation program detects and lists all the installations of Tivoli Workload Scheduler version 8. Select the Tivoli Workload Scheduler for Applications installation where you want to install the features and click Next. Select the IBM Tivoli Workload Scheduler installation where you want to install IBM Tivoli Workload Scheduler for Applications version 8.

the full path to the psjoa. To install the IBM Tivoli Workload Scheduler for Applications language pack or add a language to an existing language pack. From the product CD for the operating system on which you are installing the product. Note: On UNIX operating systems. “Setting options with the Option Editor. 10. v For the PeopleSoft access method. v Add a language to an existing IBM Tivoli Workload Scheduler for Applications language pack. If you click Yes. The Welcome panel is displayed.jar file. if you want to install the language pack after this installation. The Option Editor is a Java-based file editor that you use to define options for the access methods you installed. When the installation has completed. that is the user that was defined when Tivoli Workload Scheduler was installed.” on page 43 to learn how to use the Option Editor. Install Tivoli Workload Scheduler for Applications as described in “Installing Tivoli Workload Scheduler for Applications using the ISMP installation wizard” on page 11. The installation progress panel is displayed showing the status of the installation. Installing the language pack using the ISMP installation wizard This section describes how to perform the following tasks using the ISMP installation wizard: v Install the IBM Tivoli Workload Scheduler for Applications language pack. Select the language in which you want the wizard to be displayed. and uninstalling IBM Tivoli Workload Scheduler for Applications 13 . upgrading. you can do it later. 11.log and the /tmp/TWS4APPS_installationname_accessmethod^8. Click Next. The installation starts. 5. and click OK. or when you have finished with the Option Editor. or from an image. The installation process begins to install the selected access methods on your workstation. See “Before installing” on page 9 for detailed information. run the setup installation command located in the LANG_PACK directory. If you received error messages. a panel is displayed asking if you want to open the Option Editor. Verify that the TWS4APPS_JDKHOME environment variable is set to the following path: twsinstallationdir/methods/_tools 3. 2. 12. analyze the /tmp/tws4apps_ismp. Click Finish to exit the installation wizard and complete the installation. Enter the requested information and click Next. See Chapter 3.Installing using ISMP installation wizard the owner of the Tivoli Workload Scheduler installation. A summary information panel is displayed. perform the following steps: 1. you need to log out and log in from the UNIX shell before installing the language pack. If you click No. 4. If you decide not to run the Option Editor now. The Software License Agreement panel is displayed. the Option Editor is displayed and you can set your options for the methods you installed.log installation log files. Chapter 2. Note: If you decide to perform the installation from an image ensure that the path where you copy the images does not contains blanks and to maintain the CD directory structure. the installation exit window is displayed. Installing. Read the welcome information and click Next.4. 9.

log and the /tmp/TWS4APPS_installationname_LANGS^8. Tivoli Workload Scheduler for Applications provides you with the TWS4APPSSilent. Click Next. See “Installing Tivoli Workload Scheduler for Applications using the ISMP installation wizard” on page 11 for a detailed description about how to install IBM Tivoli Workload Scheduler for Applications. Note: If you have not installed IBM Tivoli Workload Scheduler for Applications. perform the following steps: 1. 9. 8. Messages are written in the /tmp/tws4apps_ismp. Click Finish to complete the installation. analyze the /tmp/tws4appslangs. The installation progress panel is displayed showing the status of the installation. A panel listing the discovered IBM Tivoli Workload Scheduler for Applications installations is displayed. you use a response file to run the installation without user intervention. From the list of discovered IBM Tivoli Workload Scheduler for Applications installations.log and in the/tmp/ TWS4APPS_installationname_accessmethod^8. The installation program installs the selected languages for all the installed access methods. Clear the languages you do not want to install and click Next. When the installation has completed.4. When running the installation in silent mode no messages are displayed. an error message appears. To run a silent installation. 14 IBM Tivoli Workload Scheduler for Applications: User’s Guide . using silent installation. select the installation where you want to install the language pack. By default.log installation log files.txt response file to include the options required to complete the installation. The Option Editor is a Java-based file editor that you use to define options for the access methods you installed. Cancel the installation and proceed with the installation of IBM Tivoli Workload Scheduler for Applications. See Table 5 on page 15 for a list of the available options. Installing Tivoli Workload Scheduler for Applications using the silent installation To install Tivoli Workload Scheduler for Applications. Entries in the response file are in the format option=value. Read the Software License Agreement information and select the radio button to accept the license agreement. 7.txt response file located on any product CD under the RESPONSE_FILES directory.4. Using the ISMP silent installation you also automatically install the Option Editor.log installation log files. If you receive error messages. Create your response file or customize the TWS4APPSSilent. Click Next. a panel showing the results of the installation is displayed. A summary information panel is displayed. The response file must be accessible from the workstation where you want to perform the installation. Each entry must be written on a separate line. Using the silent installation method you can install one or more access methods simultaneously. all the languages are installed. A panel is displayed where you can choose which languages you want to install. This is a template response file that you can customize to reflect the type of installation you want to perform.Installing language pack using ISMP installation wizard 6. Click Next. 10. or one of the access methods.

upgrading. -options responsefile Indicates the fully qualified path to the response file that contains the installation options. The path to A fully qualified path. Value Do not change this value.selectedSetupTypeId Yes -P TWS4APPS.bin -silent -options responsefile where: -silent Specifies that the installation is driven by a response file. and uninstalling IBM Tivoli Workload Scheduler for Applications 15 . For example: tws -W SETUP_TYPE_BEAN. A name. Table 5 lists the options you can specify to drive the installation.active -P TWS4APPS. located in the INSTALLER directory: On Windows setup. Options required for silent installation Option -W SETUP_TYPE_BEAN.name Yes Chapter 2. For the Tivoli example: /home/tws84/tws Workload Scheduler installation where you want to install Tivoli Workload Scheduler for Applications.installLocation Required Yes Yes Description For internal use only. A name for the installation of Tivoli Workload Scheduler for Applications.exe -silent -options responsefile On UNIX setup.Installing using silent installation 2. The value is false. Table 5. Note: Enclose all the option values within double quotes ("). Specifies if NEW_INSTANCE_TYPE you are To perform a new performing a installation new installation or UPGRADE_INSTANCE_TYPE if you are To add one or more access adding an methods to an existing access method installation to an already existing installation. responsefile is any text file with the name and extension you choose. Insert the product CD for your operating system and run the setup command. unless the value you must specify is Boolean requiring the answer true or false. Installing.

active Required No Description Specifies that the access method for SAP R/3 is to be installed. A full path. Specifies that the access method forPeopleSoft is to be installed. Value True or False. See “Before installing” on page 9 for detailed information. Usually you specify the name of the Tivoli Workload Scheduler user where the access method is installed. Usually you specify the name of the Tivoli Workload Scheduler user where the method is installed. For example: user1 -P PSAGENT_FEATURE. -W LJUSER_R3BATCH_INPUT_BEAN.Installing using silent installation Table 5.jar -P MCMAGENT_FEATURE. -W LJUSER_MCMAGENT_INPUT_BEAN. The operating system user ID user name. The name of the operating system user ID used to launch the SAP R/3 access method. Options required for silent installation (continued) Option -P R3BATCH_FEATURE. The operating system user ID user name. The name of the operating system user ID used to launch the Oracle E-Business Suite access method. The operating system user ID user name.active No True or False. 16 IBM Tivoli Workload Scheduler for Applications: User’s Guide . Specifies the full path to the psjoa. For example: c:\pt845\class\psjoa. -W LJUSER_PSAGENT_INPUT_BEAN. The name of the operating system user ID used to launch the PeopleSoft access method. Specifies that the access method for Oracle E-Business Suite is to be installed.PSJOAPATH Yes If you are installing the PeopleSoft method.active No True or False.jar file.LJUSER Yes If you are installing the PeopleSoft method. For example: user1 -W LJUSER_PSAGENT_INPUT_BEAN.LJUSER Yes If you are installing the SAP R/3 method.LJUSER Yes If you are installing the Oracle E-Business Suite method. Usually you specify the name of the Oracle E-Business Suite user where the method is installed.

For example: user1 The following is an example of the command you run to perform a silent installation using the tws4appssilent_inst. Create your response file.active=true -W LJUSER_PSAGENT_INPUT_BEAN. Usually you specify the name of the Tivoli Workload Scheduler user where the method is installed. perform the following steps: 1. To run a silent installation. Tivoli Workload Scheduler for Applications provides you with the TWS4APPSLangSilent. Value True or False.txt template response file located on any product CD under the RESPONSE_FILES directory. or customize the TWS4APPSLangSilent.LJUSER Yes If you are installing the z/OS method.active=true -W LJUSER_R3BATCH_INPUT_BEAN.log and in the /tmp/TWS4APPS_installationname_LANGS^8. Verify that the TWS4APPS_JDKHOME environment variable is set to the following path: twsinstallationdir/methods/_tools 2.txt The following example shows a response file that installs the R/3 and PeopleSoft access methods on a Windows workstation: # INSTALL LOCATION and INSTANCE NAME -W SETUP_TYPE_BEAN_. The name of the operating system user ID used to launch the z/OS access method. no messages are displayed.LJUSER="tws" -W LJUSER_PSAGENT_INPUT_BEAN. This is a template response file that you can customize to reflect which languages you want to install. The operating system user ID user name.Installing using silent installation Table 5.txt template response file. to include the languages you want to install.PSJOAPATH="c:\pt845\class\psjoa. but all messages are written in the /tmp/tws4appslangs. Using the response file you run the installation in silent mode without user intervention. -W LJUSER_ZOSAGENT_INPUT_BEAN.active=false -P TWS4APPS.installLocation="C:\Program Files\IBM\TWS\maestro" -P TWS4APPS.4.log installation log files.txt response file on a UNIX workstation: setup. upgrading. When running the installation in silent mode.bin –silent –options /tmp/tws4appssilent_inst. Options required for silent installation (continued) Option -P ZOSAGENT_FEATURE. and uninstalling IBM Tivoli Workload Scheduler for Applications 17 . as described in the TWS4APPSLangSilent. Installing.txt response file.active Required No Description Specifies that the access method for z/OS is to be installed.LJUSER="twsuser" # PSAGENT SETTINGS -P PSAGENT_FEATURE.name="SILENT" # R3BATCH SETTINGS -P R3BATCH_FEATURE.jar" Installing the language pack using silent installation To install one or all of the supported languages using silent installation you use a response file. The response file must be accessible Chapter 2.

Table 6 lists the options you can specify to drive the installation. Note: Enclose all the option values within double quotes ("). true or false. true or false. Entries in the response file are in the format option=value.active -P LANGSPACK_FR_FEATURE.active -P LANGSPACK_ZH_TW_FEATURE. The default value is true.active -P LANGSPACK_IT_FEATURE.Installing language pack using silent installation from the workstation where you want to perform the installation.active -P LANGSPACK_ES_FEATURE. The default value is true.active -P LANGSPACK_PT_BR_FEATURE. Specifies that the Korean language is installed. responsefile is any text file with the name and extension you choose. Specifies that the Japanese language is installed.installLocation -P TWS4APPS_LANGSPACK. -options responsefile Indicates the fully qualified path to the response file that contains the installation options. true or false. true or false. value is true.active -P LANGSPACK_JA_FEATURE. The default value is true.bin -silent -options responsefile where: -silent Specifies that the installation is driven by a response file. Insert the product CD for the operating system on which you are installing the product and run the setup command located in the LANG_PACK directory: On Windows setup.active No No Specifies that the Chinese true or false. Specifies that the Brazilian Portuguese language is installed. true or false.exe -silent -options responsefile On UNIX setup. Specifies that the Spanish language is installed. Specifies that the German language is installed. -P LANGSPACK_DE_FEATURE. Specifies that the Italian language is installed. true or false.name Required Yes Description The path where you installed Tivoli Workload Scheduler for Applications. The default value is true. Specifies that the French language is installed. The default Simplified language is installed. true or false.active -P LANGSPACK_KO_FEATURE. The default value is true. The default value is true. The default value is true. Each entry must be written on a separate line. Options for the language pack silent installation Option -P TWS4APPS_LANGSPACK. 3. 18 IBM Tivoli Workload Scheduler for Applications: User’s Guide . For example: TWS the Tivoli Workload Scheduler for Applications language pack. true or false. Value A fully qualified path.active No No No No No No No -P LANGSPACK_ZH_CN_FEATURE. For example: /home/tws84/tws Yes A name for this installation of A name. Table 6. The default value is true. Specifies that the Chinese Traditional language is installed.

active="false" -P LANGSPACK_ES_FEATURE. Installing. version 8.active="false" -P LANGSPACK_ZH_TW_FEATURE.active="false" -P LANGSPACK_ZH_CN_FEATURE.2 or later This section describes how to install IBM Tivoli Workload Scheduler for Applications and its language pack by using a software package block (SPB).active="false" -P LANGSPACK_DE_FEATURE.1 or the Software Distribution component of IBM Tivoli Configuration Manager.active="false" -P LANGSPACK_PT_BR_FEATURE.4 CDs.active="false" -P LANGSPACK_KO_FEATURE. Installs the HP-UX for PA-RISC Oracle E-Business Suite extended agent. version 4. Table 8 on page 22 lists the software package block available to install language packs and its location on the product CDs. version 4.bin –silent –options /tmp/tws4appslangsilent.2 or later. Table 7. # INSTALL LOCATION and INSTANCE NAME -P TWS4APPS_LANGSPACK.active="false" # -P LANGSPACK_FR_FEATURE. Table 7 lists the software package blocks available to install IBM Tivoli Workload Scheduler for Applications and their location in the product CDs. version 4.Installing language pack using silent installation The following is an example of the command you run to perform a silent installation using the tws4appslangsilent.1 or the Software Distribution component of IBM Tivoli Configuration Manager. and uninstalling IBM Tivoli Workload Scheduler for Applications 19 .name="SILENT" # INSTALL THE ITALIAN AND FRENCH LANGUAGE PACKS # -P LANGSPACK_IT_FEATURE.active="false" Installing IBM Tivoli Workload Scheduler for Applications using Tivoli Software Distribution.txt The following is an example of a response file that installs the Italian and French languages. version 4. The distribution and installation of the software package blocks can be performed on workstations running IBM Tivoli Management Framework. upgrading.txt response file on a UNIX workstation: setup.1 or Tivoli Configuration Manager.SPB File TWS4APPS_MCMAGENT_AIX. See “For language pack” on page 25 for a detailed explanation about how to install the language packs using Tivoli Software Distribution. CD Location productCD for operating system/AIX/INSTALLER/SPB productCD for operating system/HP/INSTALLER/SPB Chapter 2.SPB Software Package Description Installs the AIX Oracle E-Business Suite extended agent. The software package blocks are located on the IBM Tivoli Workload Scheduler for Applications.2 or later.installLocation="/home/tws84/tws" -P TWS4APPS_LANGSPACK. You can install any access method by distributing a software package block using the Tivoli Desktop or the winstsp command of Tivoli Software Distribution.active="false" -P LANGSPACK_JA_FEATURE.SPB TWS4APPS_MCMAGENT_HP. version 4. version 4. The software package blocks to install the language packs are located on the CD related to the operating system for which you want to perform the installation. List of software package blocks to install IBM Tivoli Workload Scheduler for Applications .

productCD for operating system/HPIA64/INSTALLER/SPB productCD for operating system/I386NT/INSTALLER/SPB productCD for operating system/LINUXS390/INSTALLER/SPB productCD for operating system/LINUX/INSTALLER/SPB productCD for operating system/SOLARIS/INSTALLER/SPB productCD for operating system/SOLARIS/INSTALLER/SPB productCD for operating system/AIX/INSTALLER/SPB productCD for operating system/HP/INSTALLER/SPB productCD for operating system/HPIA64/INSTALLER/SPB productCD for operating system/I386NT/INSTALLER/SPB productCD for operating system/LINUX/INSTALLER/SPB | | TWS4APPS_R3BATCH_HPIA64.SPB TWS4APPS_R3BATCH_AIX.SPB TWS4APPS_ZOSAGENT_AIX. Installs the Windows z/OS extended agent. Installs the AIX z/OS extended agent.SPB Software Package Description Installs the HP-UX IA64 for Integrity Oracle E-Business Suite extended agent.SPB 1 TWS4APPS_R3BATCH_LINUX. system/HP/INSTALLER/SPB Installs the HP-UX IA64 for Integrity R/3 extended agent.SPB File TWS4APPS_MCMAGENT_HPIA64. Installs the AIX for 64 bit R/3 extended agent productCD for operating system/AIX/INSTALLER/SPB productCD for operating system/AIX/INSTALLER/SPB Installs the HP-UX for PA-RISC 32 productCD for operating bit R/3 extended agent. Installs the Solaris Oracle E-Business Suite extended agent.SPB1 Installs the Linux for zSeries z/OS productCD for operating extended agent. Installs the Linux R/3 extended agent Installs the Solaris R/3 extended agent. Installs the HP-UX IA64 for Integrity z/OS extended agent.SPB Installs the HP-UX IA64 for productCD for operating IntegrityPeopleSoft extended agent system/HPIA64/INSTALLER/SPB Installs the AIX R/3 extended agent.SPB 1 TWS4APPS_PSAGENT_HP.Installing using Tivoli Software Distribution or Tivoli Configuration Manager Table 7.SPB TWS4APPS_R3BATCH_SOLARIS. Installs the HP-UX for PA-RISC z/OS extended agent.SPB TWS4APPS_ZOSAGENT_HP.SPB TWS4APPS_R3BATCH_AIX64.SPB TWS4APPS_ZOSAGENT_I386NT.SPB TWS4APPS_MCMAGENT_LINUX.SPB | | TWS4APPS_ZOSAGENT_HPIA64.SPB TWS4APPS_R3BATCH_SOLARIS64.SPB TWS4APPS_R3BATCH_HP.SPB TWS4APPS_R3BATCH_HP64. system/LINUXS390/INSTALLER/SPB 20 IBM Tivoli Workload Scheduler for Applications: User’s Guide .SPB TWS4APPS_PSAGENT_LINUX. Installs the Linux z/OS extended agent. List of software package blocks to install IBM Tivoli Workload Scheduler for Applications (continued) .SPB TWS4APPS_PSAGENT_HPIA64.SPB | | | | TWS4APPS_ZOSAGENT_LINUX.SPB 1 TWS4APPS_PSAGENT_I386NT.SPB TWS4APPS_ZOSAGENT_LINUX390.SPB TWS4APPS_R3BATCH_I386NT. Installs the Linux PeopleSoft extended agent Installs the HP-UX for PA-RISC PeopleSoft extended agent CD Location productCD for operating system/HPIA64/INSTALLER/SPB productCD for operating system/SOLARIS/INSTALLER/SPB productCD for operating system/LINUX/INSTALLER/SPB productCD for operating system/I386NT/INSTALLER/SPB productCD for operating system/LINUX/INSTALLER/SPB productCD for operating system/HP/INSTALLER/SPB TWS4APPS_MCMAGENT_SOLARIS. Installs the Windows PeopleSoft extended agent. Installs the Solaris for 64 bit R/3 extended agent. system/HP/INSTALLER/SPB Installs the HP-UX for PA-RISC 64 productCD for operating bit R/3 extended agent. Installs the Linux Oracle E-Business Suite extended agent.SPB | | | | TWS4APPS_R3BATCH_LINUX390. Installs the Windows R/3 extended agent. Installs the Linux for zSeries R/3 extended agent.

License Information. Installs the Solaris Java Runtime Environment (JRE) version 1. Chapter 2.SPB JRE142_LINUX.4.SPB TWS4APPS_COMMON_SOLARIS.SPB TWS4APPS_COMMON_LINUX. License Information.2. and License Agreement files for HP Installs GSKit.SPB File Software Package Description Installs the Solaris z/OS extended agent. Installs the HP-UX for Integrity Java Runtime Environment (JRE) version 1. Installing.2. and License Agreement files for Linux for zSeries Installs GSKit.SPB JRE142_HP.2. License Information. and License Agreement files for Solaris JRE142_HPIA64.4.SPB JRE142_I386.SPB TWS4APPS_COMMON_HP.4.4. License Information. Installs the Windows Java Runtime Environment (JRE) version 1.2.2. Installs the Linux for zSeries Java Runtime Environment (JRE) version 1.4.SPB TWS4APPS_COMMON_I386NT.2.SPB2 JRE142_AIX. Installs the Linux for xSeries Java Runtime Environment (JRE) version 1. License Information.SPB1 JRE142_ZLINUX. and License Agreement files for Windows Installs GSKit.SPB TWS4APPS_COMMON_HP. CD Location productCD for operating system/SOLARIS/INSTALLER/SPB productCD for operating system/operating system/INSTALLER/SPB productCD for operating system/AIX/JVM_CM productCD for operating system/HP/JVM_CM productCD for operating system/HPIA64/JVM_CM productCD for operating systemI386NT/JVM_CM productCD for operating system/LINUX/JVM_CM productCD for operating system/ZLINUX/JVM_CM productCD for operating system/SOLARIS/JVM_CM productCD for operating system/AIX/INSTALLER/SPB productCD for operating system/HP/INSTALLER/SPB productCD for operating system/HPIA64/INSTALLER/SPB productCD for operating system/I386NT/INSTALLER/SPB productCD for operating system/LINUX/INSTALLER/SPB productCD for operating system/LINUXS390/INSTALLER/SPB | | TWS4APPS_ZOSAGENT_SOLARIS. Installs GSKit.Installing using Tivoli Software Distribution or Tivoli Configuration Manager Table 7. License Information. The SPB packages for Linux cannot be imported using Tivoli Software Distribution. and License Agreement files for Linux Installs GSKit. Installs the Option Editor. and License Agreement files for HP IA64 Installs GSKit. version 4. List of software package blocks to install IBM Tivoli Workload Scheduler for Applications (continued) .SPB TWS4APPS_OPTED. and License Agreement files for AIX Installs GSKit.1. Installs the HP-UX for PA-RISC Java Runtime Environment (JRE) version 1.SPB | | | | | | | | | | | | | | | | | | | | | | TWS4APPS_COMMON_AIX.4.SPB1 JRE142_SOLARIS.4.SPB productCD for operating system/SOLARIS/INSTALLER/SPB Notes: 1. upgrading.2. License Information. and uninstalling IBM Tivoli Workload Scheduler for Applications 21 .SPB TWS4APPS_COMMON_LINUX390.SPB Installs the AIX Java Runtime Environment (JRE) version 1.

and your Tivoli Workload Scheduler engine on the target workstation is version 8. Software package block to install IBM Tivoli Workload Scheduler for Applications language pack Language Pack . Table 8.2. Using this method you can install only one access method per software package block. Table 9.8. 22 IBM Tivoli Workload Scheduler for Applications: User’s Guide . if you are installing the PeopleSoft method. make sure you know the name of the installation directory of the engine before you start. version 1.4 v For the Option Editor: TWS4APPS_installationname_OPTED. Table 9 describes the options required to install Tivoli Workload Scheduler for Applications using SPBs. LJUSER PSJOAPATH Yes Yes. If you already have the Java Runtime Environment (JRE) installed. If you choose to drive the installation process from the Tivoli Desktop.4 where: installationname Specifies the name that you used for the IBM Tivoli Workload Scheduler for Applications installation. to use the Option Editor you still need to install Java Runtime Environment (JRE).4 v For the R/3 access method: TWS4APPS_installationname_R3BATCH_operatingsystem. The full path to the psjoa.2 or later.8.jar file. For example.Installing using Tivoli Software Distribution or Tivoli Configuration Manager 2. Options to install Tivoli Workload Scheduler for Applications using SPBs Option INSTALL_DIR Yes Required Description The fully qualified path to the Tivoli Workload Scheduler installation where you want to install Tivoli Workload Scheduler for Applications. The name of the operating system user ID used to launch the access method.SPB File Software Package Description CD Location productCD for operating system/operating system/LANG_PACK TWS4APPS_LANGS.8. If you use multiple SPBs to install additional access methods.8. see “Before installing” on page 9.4. The software package profile name has the following format: v For the Oracle E-Business Suite access method: TWS4APPS_installationname_MCMAGENT_operatingsystem. be careful to use different names for the software package profile. For detailed information.SPB Installs the language pack for all the extended agents.8. TWS.4 v For the z/OS access method: TWS4APPS_installationname_ZOS_operatingsystem.4 v For the PeopleSoft access method: TWS4APPS_installationname_PSAGENT_operatingsystem. operating system Specifies the operating system where you are installing the software package.

true or false. JA No Japanese language pack. The default value is false. The default value is true. The default value is true. The default value is true. to install Tivoli Workload Scheduler for Applications. Table 10. using either the command line or the Tivoli Desktop. FR No French language pack. The default value is true. true or false. Import the software package block into a software package profile. Installation procedure To install a software package. ZH_CN No Chinese Simplified language pack. The default value is true. true or false. Installing. 1. Options to install the language packs using SPBs Option INSTALL_DIR Required Yes Description Value The path to the Tivoli Workload Fully qualified Scheduler installation where you want path. true or false. ES No Spanish language pack. INST_OPTED No DE No German language pack. true or false. Do this for the software package blocks for the: v Access methods you want to install v Language pack If you want to use the Option Editor: v Java Runtime Environment (JRE) version 1. upgrading. The default value is true. The default value is true. IT No Italian language pack. true or false. true or false. The default value is true. ZH_TW No Chinese Traditional language pack. PT_BR No Brazilian Portuguese language pack.2 v Option Editor Chapter 2. true or false. and uninstalling IBM Tivoli Workload Scheduler for Applications 23 .4. Option Editor languages. perform the following actions. Create a software package profile 2. true or false. true or false.Installing using Tivoli Software Distribution or Tivoli Configuration Manager Table 10 describes the options to install the language pack using SPBs. KO No Korean language pack. The default value is true.

SPB TWS4APPS_TWSuser_R3BATCH_AIX. 3. the installation process is complete. shows an Operation Successful message.. A different Java Runtime Environment (JRE) software package block exists for each operating system.SPB software package block on an AIX workstation for the TWSuser user.. shows an Operation Successful message.4 TWS4APPS_TWS_R3BATCH_AIX. for example the jreprofile profile manager. Install the software package profile on the endpoints managed by IBM Tivoli Management Framework. by using the following command: wimpspo -c jreprofile -f src_path/JRE142_AIX.8. For example. to install the TWS4APPS_TWSuser_JRE142_AIX. For example. you must rename the software package profile for each installation.8.8.SPB TWS4APPS_TWSuser_JRE142_AIX.SPB software package block into a Tivoli Management Framework profile manager.4.8.SPB software package block for the TWSuser user.Installation procedure Note: Before using the Option Editor ensure you have already installed the access method and the JRE software package blocks.4 must refer to dest_path_local/ TWS44APPS_R3BATCH_AIX. in this example the $BINDIR/.4 software package profile on a workstation whose hostname is epAIX. the installation process is complete. Refer to the IBM Tivoli Configuration Manager documentation for a detailed explanation about how to perform the above steps.4 @epwaix When the installation log. 24 IBM Tivoli Workload Scheduler for Applications: User’s Guide .8.log file./swdis/work/ TWS4APPS_TWSuser_R3BATCH_AIX.SPB -t build -p dest_path_local/JRE142_AIX. in this example the $BINDIR/. Install the TWS4APPS_TWSuser_R3BATCH_AIX. perform the following steps: 1./swdis/work/ TWS4APPS_TWSuser_JRE142_AIX.8.4 software package profile on a workstation which must also be defined as a Tivoli Management Framework endpoint.8.4 @epAIX When the installation log.SPB software package block file in a Tivoli Management Framework profile manager. perform the steps below.SPB as the local file holding the required information. Install the TWS4APPS_TWSuser_JRE142AIX.8.4 2. Note: For multiple installations of the same software package block on the same workstation. for example. use the following command: winstsp -D INSTALL_DIR=twshome -D LJUSER=TWSuser TWS4APPS_TWSuser_R3BATCH_AIX. to install the TWS4APPS_TWS_R3BATCH_AIX.SPB -t build -p dest_path_local/TWS4APPS_R3BATCH_AIX.4 software package profile on a workstation which must also be defined as a Tivoli Management Framework endpoint.4 software package profile on a workstation whose hostname is epwaix. by using the following command: wimpspo -c r3profile -f src_path/TWS4APPS_R3BATCH_AIX.8.4. 1. For SAP R/3: To install the SAP R/3 access method using the TWS4APPS_R3BATCH_AIX. Import the TWS4APPS_R3BATCH_AIX. For the Java Runtime Environment (JRE): To install the JRE142_AIX.log file. Import the JRE142_AIX. the r3profile profile manager.8. use the following command: winstsp -D INSTALL_DIR=twshome TWS4APPS_TWSuser_JRE142_AIX.8. 2.

To install the language pack for any access method using TWS4APPS_LANGS.SPB software package block file into a Tivoli Management Framework profile manager. upgrading.4 @epAIX When the installation log.4 software package profile on a workstation which must also be defined as a Tivoli Management Framework endpoint. Install the Java Runtime Environment as described in the installation procedure “For the Java Runtime Environment (JRE)” on page 24.log file. 3.8. perform the following steps: 1. For example. use the following command: winstsp -D INSTALL_DIR=twshome -D LJUSER=TWSuser -D PSJOAPATH=c:\pt845\class\psjoa.4 must refer to dest_path_local/ TWS4APPS_PSAGENT_I386NT. the installation process is complete.SPB as the local file holding the required information. for example the psagentprofile profile manager. Note: For multiple installations of the same software package block on the same workstation.SPB software package block on an AIX workstation for the TWSuser user. the installation process is complete. in this example the $BINDIR/.SPB software package block.SPB -t build -p dest_path_local/TWS4APPS_PSAGENT_I386NT.SPB TWS4APPS_TWSuser_PSAGENT.8.8.4 TWS4APPS_TWS_PSAGENT.log file. Install the TWS4APPS_TWS_PSAGENT. for example the langpackprofile profile manager.4. Import the TWS4APPS_OPTED. For language pack: This section describes how to install the TWS4APPS_LANGS.jar TWS4APPS_TWSuser_PSAGENT. by using the following command: wimpspo -c psagentprofile -f src_path/TWS4APPS_PSAGENT_I386NT. use the following command: winstsp -D INSTALL_DIR=twshome TWS4APPS_TWSuser_OPTED. For the Option Editor: The software package block of the Option Editor is the same for all the operating systems.. For example. To install the TWS4APPS_OPTED. you must rename the software package profile for each installation..8. Import the TWS4APPS_LANGS.Installation procedure For PeopleSoft: To install the PeopleSoft access method using the TTWS4APPS_PSAGENT_I386NT.4 @epwwindows When the installation log. perform the following steps: 1. to install the TWS4APPS_TWSuser_PSAGENT.8./swdis/work/ TWS4APPS_TWS_PSAGENT. Installing.4 software package profile on a workstation whose hostname is epAIX.8. 2.8. shows an Operation Successful message. by using the following command: Chapter 2.8.4.8.SPB TWS4APPS_TWSuser_OPTED.4 software package profile on a workstation whose hostname is epwwindows. to install the TWS4APPS_TWSuser_OPTED. and uninstalling IBM Tivoli Workload Scheduler for Applications 25 . for example the optprofile profile manager.8.4 software package profile on a workstation which must also be defined as a Tivoli Management Framework endpoint./swdis/work/ TWS4APPS_TWSuser_OPTED. by using the following command: wimpspo -c optprofile -f src_path/TWS4APPS_OPTED. Install the TWS4APPS_TWSuser_OPTED.SPB -t build -p dest_path_local/TWS4APPS_OPTED. shows an Operation Successful message. Import the TWS4APPS_PSAGENT_I386NT.SPB for the twsuser. in this example the $BINDIR/.4 2.SPB software package block into a Tivoli Management Framework profile manager.8.SPB software package block for the TWSuser user. perform the following steps: 1.SPB software package block file into a Tivoli Management Framework profile manager.

3. Log in as root and locate the installation directory of the operating system where you want to install. perform the following steps: 1.8.8..4 software package profile on a workstation whose hostname is epwaix.4 TWS4APPS_TWSuser_LANGS.8. It installs the Java Runtime Environment for PeopleSoft only.8.8. Installing IBM Tivoli Workload Scheduler for Applications using twsappsinst This section explains how to perform the following tasks using the twsappsinst script: v Install IBM Tivoli Workload Scheduler for Applications.8. When the installation log.log installation log files.Installation procedure wimpspo -c langpackprofile -f src_path/TWS4APPS_LANGS. If you receive error messages. Note: For multiple installations of the same software package block on the same workstation. shows an Operation Successful message. v Add an access method to an already existing installation of Tivoli Workload Scheduler for Applications. run twsappsinst as follows: 26 IBM Tivoli Workload Scheduler for Applications: User’s Guide . Run the twsappsinst script using the syntax described below. 2. analyze the /tmp/twappsint. Install the TWS4APPS_TWSuser_LANGS. To know the syntax for the twsappsinst command.4 @epwaix Using this command you install all the languages simultaneously. The software is installed by default in the home directory of the user.SPB TWS4APPS_TWSuser_LANGS.SPB -t build -p dest_path_local/TWS4APPS_LANGS. or copy locally the ALT_INST directory and its content. to install the TWS4APPS_TWS_LANGS. 2.4 must refer to dest_path_local/ TWS4APPS_LANGS. Insert the product CD for the operating system on which you are installing the product./swdis/work/ TWS4APPS_TWSuser_LANGS.SPB as the local file holding the required information. For example.4.log file. use the following command: winstsp -D INSTALL_DIR=twshome -D TWS4APPS_TWSuser_LANGS. referred to as twshome.log and the /tmp/TWS4APPS_installationname_accessmethod^8.4. you must rename the software package block for each installation. Note: This method does not install the Option Editor. run twsappsinst as follows: twsappsinst -u If you want to know the version of the twsappsinst command. To install IBM Tivoli Workload Scheduler for Applications using twsappsinst. in this example the $BINDIR/.4 software package profile on a workstation which must also be defined as a Tivoli Management Framework endpoint. the installation process is complete.

See “Before installing” PeopleSoft access on page 9 for detailed information. Tivoli Workload Scheduler for Applications is installed under the home directory of the specified user. The name of the user for which Tivoli Workload Scheduler is installed. Installing. twsappsinst parameters to install IBM Tivoli Workload Scheduler for Applications Parameter -install -wsuser TWSUser Yes Yes Required Description Installs Tivoli Workload Scheduler for Applications. ljuser is the name of the operating system user ID used to launch the access method. For example: tws84. This user name is not to be confused with the user performing the installation logged on as root. ljuser is the name of the operating system user ID used to launch the access method.jar file. If you are installing the psjoapath is the full path to the psjoa. method. Installs the SAP R/3 access method. Enclose the name within double quotes if it contains a blank. Yes If you are installing the Oracle E-Business Suite access method. ljuser is the name of the operating system user ID used to launch the access method.Installing using twsappsinst twsappsinst -v The syntax of the twsappsinst command to install IBM Tivoli Workload Scheduler for Applications or add an access method is as follows: twsappsinst -install -twsuser TWSUser Access method -inst_dir TWS_installation_path -lang messages_language Access method: (1) -mcm_ljuser -r3_ljuser -ps_ljuser -zos_ljuser ljuser_name ljuser_name ljuser_name -psjoapath psjoa_path ljuser_name Notes: 1 Do not specify the same access method more than once. -r3_ljuser ljuser Yes If you are installing the SAP R/3 access method. The software is installed in this user's home directory. Table 11 describes the twsappsinst parameters used to install IBM Tivoli Workload Scheduler for Applications. -ps_ljuser ljuser -psjopath psjopath Yes Installs the PeopleSoft access method. Table 11. Installs the Oracle E-Business Suite access method. -mcm_ljuser ljuser Chapter 2. and uninstalling IBM Tivoli Workload Scheduler for Applications 27 . upgrading.

28 IBM Tivoli Workload Scheduler for Applications: User’s Guide . To install the IBM Tivoli Workload Scheduler for Applications language pack using twsappsinst. -inst_dir TWS_installation_ path -lang messages_language No Required Description Installs the z/OS access method. The path to the Tivoli Workload Scheduler installation where you want to install Tivoli Workload Scheduler for Applications. or copy locally the altinst directory and its content.4.Installing using twsappsinst Table 11. Ensure you have already installed IBM Tivoli Workload Scheduler for Applications version 8. ljuser is the name of the operating system user ID used to launch the access method. twsappsinst parameters to install IBM Tivoli Workload Scheduler for Applications (continued) Parameter -zos_ljuser ljuser Yes If you are installing the z/OS access method. If not specified. perform the following steps: 1. the default C language catalog is used. Insert the product CD appropriate for the operating system on which you are installing the product. If the related catalog is missing. the system LANG is used. 2. referred to as twshome. For example: /home/tws84/tws. The software is installed by default in the home directory of the user. Possible values are: de German it Italian es Spanish fr French es Spanish ko Korean ja Japanese pt_BR Brazilian Portuguese zh_CN Chinese Simplified zh_TW Chinese Traditional No Examples of how to install Tivoli Workload Scheduler for Applications using twsappsinst This section shows some examples to install IBM Tivoli Workload Scheduler for Applications access methods using twsappsinst.jar -zos_ljuser zosuser -inst_dir /home/tws84/tws -lang it Installing the language pack using twsappsinst This section explains how to perform the following tasks using twsappsinst script: v Install the IBM Tivoli Workload Scheduler for Applications language pack v Add a language to an existing IBM Tivoli Workload Scheduler for Applications language pack. The language in which the twsappsinst messages are displayed. The following is an example of how to install the Tivoli Workload Scheduler for Applications R/3 access method using twsappsinst: twsappsinst -install -twsuser tws84 -r3_ljuser r3user -inst_dir /home/tws84/tws -lang it The following is an example of how to install the Tivoli Workload Scheduler for Applications for PeopleSoft and Tivoli Workload Scheduler for Applications for z/OS using twsappsinst: twsappsinst -install -twsuser tws84 -ps_ljuser psuser -psjoapath c:\pt845\class\psjoa.

log and the /tmp/TWS4APPS_installationname_LANGS^8. twsappsinst parameters to install IBM Tivoli Workload Scheduler for Applications language pack Parameter -languages Required Yes Description Installs IBM Tivoli Workload Scheduler for Applications language pack or one of the supported languages. Chapter 2. referred to as twshome. analyze the /tmp/twappsint. Log in as root and locate the installation directory of the operating system where you want to install. and uninstalling IBM Tivoli Workload Scheduler for Applications 29 . To know the syntax for the twsappsinst command. Installing. Run the twsappsinst script using the syntax described on page 29.Installing language pack using twsappsinst 3.3.log installation log file. run twsappsinst as follows: twsappsinst -u To know the version of the twsappsinst command. Table 12 describes the twsappsinst parameters used to install IBM Tivoli Workload Scheduler for Applications language pack: Table 12. upgrading. If you receive error messages. run twsappsinst as follows: twsappsinst -v The syntax of the twsappsinst command to install IBM Tivoli Workload Scheduler for Applications language pack or add a language is as follows: twsappsinst -languages -twsuser TWSUser Language pack -inst_dir TWS_installation_path -lang messages_language Language pack: (1) -de -it -es -fr -ko -ja -pt_BR -zh_CN -zh_TW Notes: 1 Do not specify the same language pack more than once. The software is installed by default in the user's home directory. 4.

If the related catalog is missing. The software is installed by default in the user's home directory. The language you want to install. For example: tws.Installing language pack using twsappsinst Table 12. The software is installed in this user's home directory. If not specified. referred to as twshome. Tivoli Workload Scheduler will be installed under the HOME directory of the specified user. Possible values are: de German it Italian es Spanish fr French ko Korean ja Japanese pt_BR Brazilian Portuguese zh_CN Chinese Simplified zh_TW Chinese Traditional The path to the Tivoli Workload Scheduler installation where you want to install Tivoli Workload Scheduler for Applications. twsappsinst parameters to install IBM Tivoli Workload Scheduler for Applications language pack (continued) Parameter Required Description The name of the user for which IBM Tivoli Workload Scheduler is installed. the default C language catalog is used. For example: /home/tws84/tws. Enclose the name within double quotes if it contains a blank. The language in which the twsappsinst messages are displayed. Possible values are: de German it Italian es Spanish fr French ko Korean ja Japanese pt_BR Brazilian Portuguese zh_CN Chinese Simplified zh_TW Chinese Traditional -twsuser TWSuser Yes -Language pack Yes -inst_dir TWS_install_path No -lang No messages_language Example of how to install the Tivoli Workload Scheduler for Applications language pack using twsappsinst This section shows an example to install the Tivoli Workload Scheduler for Applications language pack using twsappsinst: twsappsinst -languages -twsuser tws84 -it -de -inst_dir /home/tws84/tws -lang it 30 IBM Tivoli Workload Scheduler for Applications: User’s Guide . the system LANG is used. This user name is not to be confused with the user performing the installation logged on as root.

env files into the contextname_MCM.env file. If you are working with a version of Oracle E-Business Suite prior to 11.sh file.sh b.env files into the APPScontextname_MCM. replace the variable ORACLE_SID_database_name with the actual name of the Oracle SID database. Set the APPLFENV environment variable to the contextname_MCM. 2. copy the content of the following files: v APPScontextname.Completing installation of Oracle E-Business Suite access method Completing the installation of the access method for Oracle E-Business Suite After you have installed Tivoli Workload Scheduler for Applications. Run the APPScontextname_MCM.env | | | | | | | | where APPL_installation_path is the complete installation path. If you do.env file. from the TWShome/methods/OracleTMP directory.env 8.env file by replacing the line: . At the end of the file. and OracleTMP directories located in TWShome. who has access to all the files in the Oracle Application Top directory. 6.TWShome+/methods/mcmsetting. Change to the installed directory: cd TWShome/methods/OracleTMP 10.env file as follows: a. 9. Log on as an Oracle Applications UNIX user. upgrading. The default value is the SID_hostname. 5. Make a backup copy of the TWShome/methods/OracleTMP directory. where contextname is the Applications context name.env main application environment file to set the environment: . add the line: . Ensure that the Oracle Applications logon has permissions to write in the methods. this prevents you from performing the link steps successfully. Installing. /APPL_installation_path/contextname_MCM. In the Oracle Application Top directory. run the installation script mcminstall with the following command: sh mcminstall Note: If you need to define the TWO_TASK environment variable to allow for an Oracle three-tier configuration. Modify the APPScontextname_MCM. do not set it externally from mcminstall or in any scripts provided as input parameters. and uninstalling IBM Tivoli Workload Scheduler for Applications 31 . perform the following steps to complete the installation of the access method for Oracle E-Business Suite: 1. Modify the Oracle E-Business Suite contextname_MCM. To link the binary files. append MCM to the APPLSHAR and APPLFULL variables as follows: APPLSHAR=’ALR FF MCM’ APPLFULL=’FND AD AX AK GL RG INV OP MCM’ 7. 11. usually the $APPL_TOP installation directory. 4. /APPL_installation_path/contextname. c.0. 3. APPScontextname_MCM.env | | with: . In the TWShome/methods/mcmsetting.env file. v contextname. Chapter 2. Change the user and group ownership of the installed files to that of your Oracle E-Business Suite application owner.

The default is mcminstall. “Configuring the Oracle E-Business Suite access method. Press c to continue the installation.” on page 63 and Chapter 3. 32 IBM Tivoli Workload Scheduler for Applications: User’s Guide . “Setting options with the Option Editor. If you encounter problems during the link step. The installation is now complete. Perform the following steps: a. fix them and run the link step again.env. Enter the name of the APPScontextname_MCM. This utility also registers the MCM as a module in Oracle E-Business Suite. you find the following executables in the $MCM_TOP/bin directory: v MCMLJ v MCMSTAT v MCMTJ These binary files are created by the adrelink utility for Oracle E-Business Suite. e. d.Completing installation of Oracle E-Business Suite access method The installation process now attempts to link the Tivoli Workload Scheduler for Applications executables with the Oracle E-Business Suite application shared libraries. Enter the name of the installation log file. After the link process has completed successfully. c. see Chapter 7. For details.env main application environment file. 13. because this step is responsible for creating the binary files that enable Tivoli Workload Scheduler for Applications to interact with the Oracle Concurrent Manager in submitting and monitoring jobs. b. The default is APPLSYS. 12.” on page 43. located in the TWShome/methods directory. An Oracle Tivoli shell panel is displayed.log. Enter the TWShome installation directory. Edit the options file. Press i to install.

3. version 4. upgrading. A summary information window is displayed. Click Finish to exit the installation wizard and complete the upgrade.1.3 to version 8. 4. the twsappsinst command. or 8. If you click Yes. 10.2.” on page 43 to learn how to use the Option Editor. If you click No. The Select the Type of Installation panel is displayed. 8. The setup installation commands are located in operating system specific directories located in the INSTALLER directory.2. Note: If you decide to perform the installation from an image ensure that the path where you copy the images does not contains blanks and to maintain the CD directory structure 2. If the program does not detect any existing installation. 9. See Chapter 3. The Welcome panel is displayed.2. a window is displayed asking if you want to open the Option Editor. Click Next. Click Next. or 8. Select the installation that you want to upgrade. 5. the installation exit window is displayed. When the upgrade has completed. Chapter 2. use one of the following methods: v The InstallShield MultiPlatform (ISMP) wizard v The silent installation v Tivoli Software Distribution. 6. The installation process begins the upgrade process. 8.3 to version 8.3 on your workstation. The Software License Agreement panel is displayed. Read the welcome information and click Next. v In a UNIX environment. If you decide not to run the Option Editor now. Read the Software License Agreement information and select the radio button to accept the license agreement. or 8. 8. version 4. perform the following steps: 1. The installation program detects and lists all the installations of Tivoli Workload Scheduler for Applications version 8. or when you have finished with the Option Editor. you can do it later. Click Next.Upgrading Upgrading To upgrade Tivoli Workload Scheduler for Applications version 8. From the product CD. Select the language in which you want the wizard to be displayed. The Option Editor is a Java-based file editor that you use to define options for the access methods you installed.4 using the ISMP installation wizard. Select Upgrade. Upgrading Tivoli Workload Scheduler for Applications using the ISMP installation wizard To upgrade Tivoli Workload Scheduler for Applications version 8. “Setting options with the Option Editor. click Cancel and proceed with a new installation as described in “Installing” on page 10.2. the Option Editor is displayed and you can set your options for the methods you installed.4. The installation progress window is displayed showing the status of the upgrade. 7. The installation starts. 8. and uninstalling IBM Tivoli Workload Scheduler for Applications 33 .2.2.1. or from an image.2 or later.1.1 or the Software Distribution component of Tivoli Configuration Manager. and click OK. Installing. run the setup installation command for the operating system on which you are installing the product.

Every Software Distribution package has its own log file. 8. you must follow the same procedure outlined in “Installing IBM Tivoli Workload Scheduler for Applications using Tivoli Software Distribution.Upgrading using ISMP installation wizard Note: If you want to install the language pack after this installation.1 or later for specific information.4. A name for the installation of Tivoli Workload Scheduler for Applications. Table 13 shows the option required for a silent upgrade. you need to log out and log in from the UNIX shell before installing the language pack. v View the Software Distribution log files on the workstation.log installation log files. Table 13. if you want to install the language pack after the upgrade. Refer to the IBM Tivoli Configuration Manager User’s Guide for Inventory.selectedSetupTypeId Yes MIGRATE_INSTANCE_TYPE -P TWS4APPS. For example: tws Upgrading Tivoli Workload Scheduler for Applications using Tivoli Configuration Manager To upgrade Tivoli Workload Scheduler for Applications using Tivoli Configuration Manager.4.2. use either of the two following procedures: v Use the Inventory component of Tivoli Configuration Manager version 4.active -P TWS4APPS. to run the query named CM_STATUS_QUERY and list which software packages are installed on which workstation. analyze the /tmp/tws4pps_ismp.1 or Tivoli Configuration Manager.1 or later. Options required for silent upgrade Option -W SETUP_TYPE_BEAN. To see a list of the packages installed on the workstation by Software Distribution. A log file is a text file that records the 34 IBM Tivoli Workload Scheduler for Applications: User’s Guide . For example: /home/tws84/tws -W SETUP_TYPE_BEAN.1. If you received error messages. Value Do not change this value. Specifies that you are upgrading from version 8.2 or later” on page 19.3 to version 8. Note: On UNIX operating systems.installLocation Required Yes Yes Description For internal use only.2. The path to the Tivoli Workload Scheduler installation where you want to install Tivoli Workload Scheduler for Applications. version 4.name Yes A name. The value is false.2. A fully qualified path. you need to log out and log in from the UNIX shell before installing the language pack. version 4.log and the /tmp/TWS4APPS_installationname_accessmethod^8.2. or 8. Upgrading Tivoli Workload Scheduler for Applications using the silent installation To upgrade Tivoli Workload Scheduler for Applications using the silent installation. version 4. you must follow the same procedure outlined in “Installing Tivoli Workload Scheduler for Applications using the silent installation” on page 14.

4. Log in as root and locate the installation directory of the operating system where you want to install. 8. If you receive error messages.log file. run twsappsinst as follows: twsappsinst -u To know the version of the twsappsinst command. twsappsinst parameters to upgrade IBM Tivoli Workload Scheduler for Applications Parameter -upgrade -twsuser TWSUser Required Yes Yes Description Upgrades IBM Tivoli Workload Scheduler for Applications version 8.2.. launch the following command: . and uninstalling IBM Tivoli Workload Scheduler for Applications 35 . 4./swdis/work directory.2.log. The name of the user for which Tivoli Workload Scheduler is upgraded.3.1. To know the syntax for the twsappsinst command. r3batch_tws_AIX. The software is upgraded in this user's home directory.4. is stored in the $BINDIR/.3 to version 8.2. run twsappsinst as follows: twsappsinst -v The syntax of the twsappsinst command to upgrade IBM Tivoli Workload Scheduler for Applications is as follows: twsappsinst -upgrade -twsuser TWSUser -inst_dir TWS_installation_path -lang messages_language Table 14 describes the twsappsinst parameters used to upgrade IBM Tivoli Workload Scheduler for Applications: Table 14. upgrading. For example. Enclose the name within double quotes if it contains a blank. 8. or 8.2. 2.2. or 8. For example: tws84.1.4 using twsappsinst. Ensure you have already installed IBM Tivoli Workload Scheduler for Applications version 8. /etc/Tivoli/setup_env. To initialize the $BINDIR environment path of Tivoli Management Framework. Run the twsappsinst script using the syntax described below.3 to version 8.2. the log file on an AIX system of the SAP R/3 access method package. Insert the product CD for the operating system on which you are installing the product. and the /tmp/ TWS4APPS_installationname_accessmethod^8. analyze the twsappsinst.Upgrading using Tivoli Configuration Manager installation and uninstallation history of the package.sh Upgrading Tivoli Workload Scheduler for Applications using twsappsinst To upgrade IBM Tivoli Workload Scheduler for Applications version 8. perform the following steps: 1. Installing. or 8. Chapter 2. 8.log installation log files. or copy locally the altinst directory and its content.1. 3.

you can choose to uninstall: v The access methods (this includes the Option Editor): – Oracle E-Business Suite For this access method.1.4 using twsappsinst This section shows an example to upgrade Tivoli Workload Scheduler for Applications version 8. twsappsinst parameters to upgrade IBM Tivoli Workload Scheduler for Applications (continued) Parameter -inst_dir TWS_install_path Required No Description The path to the Tivoli Workload Scheduler installation where you want to upgrade Tivoli Workload Scheduler for Applications. follow the same procedure you used at installation time: v If you installed using ISMP.2. If the related catalog is missing. The language in which the twsappsinst messages related to the upgrade process are displayed. Possible values are: de German it Italian es Spanish fr French ko Korean ja Japanese pt_BR Brazilian Portuguese zh_CN Chinese Simplified zh_TW Chinese Traditional -lang No messages_language Example of how to upgrade Tivoli Workload Scheduler for Applications to version 8. regardless of the uninstallation procedure you choose. v If you installed using software distribution. 36 IBM Tivoli Workload Scheduler for Applications: User’s Guide .2. the system LANG is used. – PeopleSoft – SAP R/3 – z/OS v One or more Tivoli Workload Scheduler for Applications language packs. “Troubleshooting. the default C language catalog is used.4 using twsappsinst: twsappsinst -upgrade -twsuser tws84 -inst_dir /home/tws84/tws –lang it Uninstalling | | | | | | | | | | | When you uninstall Tivoli Workload Scheduler for Applications. use the procedure described in Chapter 30. or 8. uninstall using the same method. v If you installed using twsappsinst. If not specified. To uninstall Tivoli Workload Scheduler for Applications from a workstation.Upgrading using twsappsinst Table 14. 8. The software is installed by default in the user's home directory. uninstall using the same method. you must complete the uninstallation as described in “Completing the removal of the access method for Oracle E-Business Suite” on page 41.” on page 251. However. if you installed Tivoli Workload Scheduler for Applications using ISMP. uninstall using an ISMP-compatible method. For example: /home/tws84/tws. but you want to perform a centralized uninstallation of the Tivoli Workload Scheduler for Applications. referred to as twshome.3 to version 8.

1 or later For details. ensure that the following prerequisites are met: v You have root permissions on UNIX and administrator permissions on Windows to run the installation. version 4. you must uninstall it before uninstalling Tivoli Workload Scheduler for Applications. see “Uninstalling the language pack using silent uninstallation” on page 39 and “Uninstalling Tivoli Workload Scheduler for Applications using silent uninstallation” on page 40. You can verify this by running one of the following commands: If you are installing using ISMP ps -ef | grep setup. Silent uninstallation For details.1 or the Software Distribution component of Tivoli Configuration Manager. and uninstalling IBM Tivoli Workload Scheduler for Applications 37 . twsappsinst For details. Tivoli Software Distribution. you can use any of the following procedures: ISMP wizard For details. Chapter 2. upgrading. The uninstallation procedure only removes the files that you did not modify. v The installation process is not already running on the workstation. Before uninstalling Before you uninstall the product.bin | | If you are installing using twsappsinst ps -ef | grep twsappsinst v The Option Editor is not running.Uninstalling Note: If you installed the language pack using ISMP. v There are no scheduling and SAP monitoring activities currently running for the application you want to uninstall. To uninstall Tivoli Workload Scheduler for Applications and its language packs. see “Uninstalling Tivoli Workload Scheduler for Applications or its language pack using Tivoli Configuration Manager” on page 39. version 4. Installing. see “Uninstalling Tivoli Workload Scheduler for Applications using ISMP wizard” on page 38 and “Uninstalling the language pack using ISMP wizard” on page 38. see “Uninstalling IBM Tivoli Workload Scheduler for Applications and its language pack using twsappsinst” on page 40.

Uninstalling language pack using ISMP wizard Uninstalling the language pack using ISMP wizard The language pack uninstallation procedure uninstalls all the languages simultaneously. To uninstall the product using the ISMP wizard.bin Note: If you upgraded Tivoli Workload Scheduler for Applications to version 8. 3. From the twshome/methods directory.\_lxauninst\uninstaller. perform the following steps: 1.jar The ISMP Uninstall program starts. 4.4. you must exit from the _lxauninst directory to complete the uninstallation. In any case.bin 2. Read the welcome information and click Next. From the twshome/methods directory. If you received error messages. Uninstalling Tivoli Workload Scheduler for Applications using ISMP wizard Using the SMP wizard you can uninstall the entire product or one access method at a time./_xauninst2/uninstaller. Note: If you launched the uninstaller command from the _lxauninst directory. Click Next.exe On UNIX . 5. run the following command: On Windows . Select the language in which you want the wizard to be displayed and click OK. Click Finish to complete the uninstallation./_lxauninst/uninstaller. The uninstallation process starts. depending on your operating system. A summary information window is displayed listing all the languages to be uninstalled. run the following command: On Windows .exe On UNIX .exe On UNIX ./_xauninst/uninstaller.4. analyze the /tmp/tws4appslangs_uninst.\_xauninst2\uninstaller. after the uninstallation completed successfully remove the _lxauninst directory. When the uninstallation process has completed.log installation log file. run the following command: On Windows . The ISMP uninstall program starts. from the twshome/methods directory. 38 IBM Tivoli Workload Scheduler for Applications: User’s Guide . perform the following steps: 1. To uninstall the language pack using the ISMP wizard.bin If you do not find the uninstaller run the following command: java -jar twshome/methods/_xauninst2/uninstall. a window showing the results of the uninstallation is displayed. The Welcome window is displayed.\_xauninst\uninstaller.log file and the /tmp/TWS4APPS_installationname_LANGS^8.

Chapter 2. v View the Software Distribution log files on the workstation. 3. To perform this task.1 or later for detailed information. To initialize the $BINDIR environment path of Tivoli Management Framework. run the following command: .2. Refer to the IBM Tivoli Configuration Manager User’s Guide for Inventory.sh Uninstalling the language pack using silent uninstallation This section describes how to uninstall the Tivoli Workload Scheduler for Applications language pack using silent uninstallation.4./_lxauninst/uninstaller. to run the query named CM_STATUS_QUERY and list which software packages are installed on which workstation. After the uninstallation completed successfully remove the _xauninst directory. By default the product uninstalls all the access methods.1 or later.log and the /tmp/TWS4APPS_installationname_accessmethod^8. the log file on an AIX system of the SAP R/3 access method package. you can uninstall the language pack without user intervention. version 4.1 or later for specific information. 5.log installation log files. Installing. r3batch_tws_AIX. Uninstalling Tivoli Workload Scheduler for Applications or its language pack using Tivoli Configuration Manager To uninstall the product or the language pack using Software Distribution. /etc/Tivoli/setup_env. Click Finish to exit the uninstallation wizard. For example. A log file is a text file that records the installation and uninstallation history of the package. use either of the two following procedures: v Use the Inventory component of Tivoli Configuration Manager version 4.Uninstalling using ISMP wizard 2. To see a list of the packages installed on the workstation by Software Distribution.. When the uninstallation has completed.log installation log files.log. If you received error messages. Every Software Distribution package has its own log file. Select the language for the wizard.2. launch the following command: .log and /tmp/TWS4APPS_installationname_LANGS^8./swdis/work directory. Using silent uninstallation.4.bin -silent When running the uninstallation in silent mode no messages are displayed. a window showing the results is displayed. but all messages are written in the /tmp/tws4appslangs_uninst. Refer to the IBM Tivoli Configuration Manager Reference Manual for Software Distribution. is stored in the $BINDIR/. you must exit from the _xauninst directory to complete the uninstallation. and click OK. The Welcome window is displayed. A summary information window is displayed listing all the access methods to be uninstalled. Note: If you launched the uninstaller command from the _xauninst directory. Clear the access methods you do not want to uninstall and click Next. 6. upgrading. and uninstalling IBM Tivoli Workload Scheduler for Applications 39 . analyze the /tmp/tws4apps_uninst_ismp. 4. Read the welcome information and click Next. The uninstall process starts. version 4.2. you can use either the Tivoli Desktop or the wremovsp command.

log and /tmp/TWS4APPS_installationname_accessmethod^8.Uninstalling using silent uninstallation Uninstalling Tivoli Workload Scheduler for Applications using silent uninstallation This section describes how to uninstall Tivoli Workload Scheduler for Applications using the silent installation.log v /tmp/TWS4APPS_installationname_LANGS^8.log To know the syntax for the twsappsinst command. analyze the following installation log files: v /tmp/twsappsinst. run the following command from the twshome/methods directory: ./_xauninst/uninstaller. If you received error messages. run twsappsinst as follows: twsappsinst -u If you want to know the version of the twsappsinst command.log installation log files. From the TWShome/methods/xaunist directory.4. run the twsappsinst script using the syntax described below. 2. The silent uninstallation enables you to uninstall the product in silent mode without user intervention. perform the following steps: 1. When running the uninstallation in silent mode no messages are displayed. run twsappsinst as follows: twsappsinst -v The syntax of the twsappsinst command to uninstall IBM Tivoli Workload Scheduler for Applications is as follows: twsappsinst -uninst -twsuser user_name -inst_dir TWS_installation_path -lang messages_language Table 15 on page 41 describes the twsappsinst parameters used to uninstall IBM Tivoli Workload Scheduler for Applications: 40 IBM Tivoli Workload Scheduler for Applications: User’s Guide .4. but all messages are written in the /tmp/tws4apps_uninst_ismp.log v /tmp/TWS4APPS_installationname_accessmethod^8. To uninstall Tivoli Workload Scheduler for Applications.bin -silent Uninstalling IBM Tivoli Workload Scheduler for Applications and its language pack using twsappsinst To uninstall IBM Tivoli Workload Scheduler for Applications and its language pack using twsappsinst. Log in as root and locate the installation directory of the operating system where you want to uninstall.4.

Installing.env to its original contents by removing the MCM string from the APPLSHAR and APPLFUL variables. Restore APPLSYS. MCMSTAT.O. when the uninstallation process has completed. upgrading. For example: tws84. and MCMTJ. Enclose the name within double quotes if it contains a blank. The software is uninstalled in this user's home directory. For example: APPLSHAR=’ALR FF MCM’ becomes: APPLSHAR=’ALR FF’ 2.cat v MCMLJ. If the related catalog is missing. the default C language catalog is used. twsappsinst parameters to uninstall IBM Tivoli Workload Scheduler for Applications Parameter –uninst –twsuser user_name Required Yes Yes Description Uninstalls IBM Tivoli Workload Scheduler for Applications version 8. referred to as TWShome. perform the following steps: 1. and MCMTJ located in the $MCM_TOP/bin directory v MCMLJ.4 using twsappsinst: twsappsinst -uninst -twsuser tws84 -inst_dir /home/tws84/tws Completing the removal of the access method for Oracle E-Business Suite For the Oracle E-Business Suite access method.O.4 and its language pack. Remove the following files: v TWShome/methods/MCMAGENT v TWShome/catalog/C/mcm.txt located in the $APPL_TOP/admin directory v All the options files Chapter 2. Enclose the name within double quotes if it contains a blank. For example: /home/tws84/tws. The path to the Tivoli Workload Scheduler installation where you want to uninstall Tivoli Workload Scheduler for Applications. and uninstalling IBM Tivoli Workload Scheduler for Applications 41 . Possible values are: de German it Italian es Spanish fr French ko Korean ja Japanese pt_BR Brazilian Portuguese zh_CN Chinese Simplified zh_TW Chinese Traditional –inst_dir No TWS_installation_path –lang messages_language No Example to uninstall Tivoli Workload Scheduler for Applications version 8. Specifies the name of the user for which Tivoli Workload Scheduler is uninstalled. The language in which the twsappsinst uninstallation messages are displayed.Uninstalling using twsappsinst Table 15. MCMSTAT.4 using twsappsinst Following is an example of how to uninstall Tivoli Workload Scheduler for Applications version 8. The software is installed by default in the user's home directory.O located in the $MCM_TOP/LIB directory v MCMprod. If not specified. the system LANG is used.

Completing removal of the Oracle E-Business Suite access method 42 IBM Tivoli Workload Scheduler for Applications: User’s Guide .

where WORKSTATIONNAME is the name of the extended agent.Chapter 3. The files must reside in the methods subdirectory of the Tivoli Workload Scheduler installation and are read when the extended agent is initialized. you can either use a text editor or the Option Editor described in “Using the Option Editor” on page 44. it contains only the LJuser option. which. You can customize the global options file by adding the options appropriate to the access method. the global options file is used. mvsopc. mvsjes.opts psagent. if the installation of the access method for SAP R/3 includes two extended agent workstations.opts and CPU2_r3batch.opts mvsca7.” on page 221 for z/OS To modify a local or global options file.opts.” on page 75 for PeopleSoft v Chapter 14.opts. Setting options with the Option Editor An options file is a text file containing a set of options to customize the behavior of the access method when submitting a job. To know the options of each access method. Options are specific to each access method. CPU1 and CPU2. If you do not create a local options file.opts Local options file A configuration file that is specific to each extended agent workstation within a particular installation of an access method. must have a local options file with its own configuration options. For example. which represents the operating system user ID used to launch the access method. except for z/OS. The name of this file is WORKSTATIONNAME_accessmethod. | | Note: WORKSTATIONNAME must be written in uppercase characters and cannot contain DBCS characters. depending on your operating system.” on page 103 for SAP R/3 v Chapter 26. © Copyright IBM Corp. “Configuring the z/OS access method.opts.opts. The options must be written one per line and have the following format (with no spaces included): option=value All access methods use two types of options files: Global options file A common configuration file created by default for each access method installed.opts. or create a local options files. 2003. see: v Chapter 7. corresponds to: For Oracle E-Business Suite For PeopleSoft For SAP R/3 For z/OS MCMAGENT. The name of the global options file is accessmethod.opts r3batch. the names of the local options files are respectively CPU1_r3batch. Every extended agent workstation. When the global options file is created. whose settings apply to all the extended agent workstations defined for that method. 2008 43 . “Configuring the SAP R/3 access method. “Configuring the Oracle E-Business Suite access method.” on page 63 for Oracle v Chapter 10. “Configuring the PeopleSoft access method.

v The value for the retrive_joblog option is taken from each local options file. The areas are: File Options Tree Shows a list of all the existing options files.exe opted. grouped by method. v Create a local options file. To choose which areas you want to see. See “Modifying local or global options files” on page 46 for a detailed explanation. If the local options file does not contain a value for the option. Then you define a different value for the retrive_joblog option in each local options file. Using the Option Editor This section describes the Option Editor and how to use it to perform the following tasks: v Modify local or global options file. To do this. See “Creating local options files” on page 46 for a detailed explanation. Local options files can inherit existing values from the same options in the global options file (r3batch. File Options View Displays the options of a selected file in any of the three available views. Tivoli Workload Scheduler for Applications optionally starts the Option Editor to let you define local options. depending on you operating system. you must have a graphical environment. Otherwise the option value in the local options file is always used. The Option Editor window has three main areas.opts).bin Note: To use the Option Editor on a UNIX workstation. The Option Editor automatically loads all the existing global and local options files grouped by access method. go to the TWShome/methods directory of your Tivoli Workload Scheduler installation and. Option value inheritance This property is currently available for r3batch only. you might want to define the same value for the Ljuser option and a different value for the retrive_joblog option. For example. Option Descriptor Gives a description of the current selection. you define the Ljuser option value in the r3batch. To start the Option Editor.Setting options with the Option Editor Before completing installation. while some of the values you entered during the process are used to create a global options file. as shown in Figure 3 on page 45.opts file.opts file. then the value for that option in the global options file is used. run the following command: On Windows On UNIX opted. For an access method the options are listed twice: once as global options and once as local options. 44 IBM Tivoli Workload Scheduler for Applications: User’s Guide . select View→Show. This results in the following when launching the SAP R/3 job: v The value for the Ljuser option is extracted from the r3batch.

Setting options with the Option Editor 45 . Value The value specified in the file. Default Value The value used by the method if not specified in the options file or inherited. The values are used in the order: value. To view or edit an option. because you only see the actual value that is used in the file. if supported. This is the easiest way to edit options. The Option Editor The Option Editor provides three possible views of an options file. Inherited or default values are not displayed. See “Option value inheritance” on page 44 for a detailed explanation.Using the Option Editor File Options View Option Descriptor Options Files Tree Figure 3. Actual Value The value actually used at run time. To change the view in which the options file is displayed select View→Display As. default value. For each option the following columns are displayed: Name The name of the option. The views are: Simple Displays the options as a sequence of tabs that you can select to edit one option at a time. Chapter 3. select the tab with the option name to display the field for the value. This is the default view. if available. Table Provides a tabular view of all the options for a selected file. inherited value. Inherited Value The value obtained from the global options file if inheritance is supported by the access method.

Ensure that the Option Editor is not running before you add or update an existing Tivoli Workload Scheduler for Applications installation. for example. From the File Options Tree area. perform the following steps: 1. on the master workstation. accessmethod The access method you selected from the Insert Method Name drop-down menu 4. perform the following steps: 1. Options that are not correctly entered are shown with a red background.opts where: WORKSTATION The name you specified in the Insert XA CPU Name field. Select the option you want to modify and modify its value. you can increase security by maintaining only one copy of the Option Editor. The new options file has the following name: WORKSTATION_accessmethod. The Option Editor performs only syntactic checks. Mandatory options are identified by a yellow background and are marked with an asterisk (*). Save and close the options file. 2. Save and close the options file. you create local options files when you define a new extended agent workstation. If you have multiple installations of an extended agent. To create a local options file. 3. Click File→New in the menu bar. In the Insert XA CPU Name field. The options are displayed in the File Options View area. using the Option Editor. showing only the options that have a value. using the Option Editor. because files are shown in read-only form.Using the Option Editor Text Displays an options file in the typical format. Password fields are shown encrypted. Creating local options files While global options files are created each time you install an access method. This view is generally used for preview purposes. 3. You should restrict access to the Option Editor. Modifying local or global options files To modify local or global options files. The New Option File window is displayed. Select an access method from the Insert Method Name drop-down menu. 46 IBM Tivoli Workload Scheduler for Applications: User’s Guide . select the options file you want to modify. enter the name of the extended agent workstation for which you want to create an options file. 5. Enter values for the options you want to define. 2.

2. SAP R/3.Workstation in Database panel is displayed. © Copyright IBM Corp. perform the following steps: 1. PeopleSoft. In the Actions list of the Job Scheduling Console main window. To launch a job on an extended agent workstation. The Properties . The access method communicates with the instance of the particular Oracle E-Business Suite. Select an engine. 2003. Creating a workstation using the Job Scheduling Console To define an extended agent workstation with the Job Scheduling Console.Chapter 4. select New Workstation. Extended agent workstations are defined in the standard manner and include the name of the extended agent host and the method name. 2008 47 . Defining extended agent workstations An extended agent workstation definition is required for each entity of an access method through which Tivoli Workload Scheduler schedules and lunches jobs. or z/OS system and monitors the job through completion. passing it information about the job. writing job progress and status information to the job’s standard list file. Tivoli Workload Scheduler runs the access method.

Click OK to save and close the panel. Table 16 on page 49 shows how to complete the fields of the workstation properties panel depending on which extended agent workstation you are defining. 4.Creating a workstation using the Job Scheduling Console Figure 4. Defining a workstation using the Job Scheduling Console 3. 48 IBM Tivoli Workload Scheduler for Applications: User’s Guide . Complete the fields using the information in Table 16 on page 49.

null The node name or IP address of the z/OS system. An optional free-form textual description of the workstation. The name must start with a letter and can contain alphanumeric characters. To ensure the accuracy of scheduling times. the name must start with a letter and can contain alphanumeric characters. refer to the Tivoli Workload Scheduler: User's Guide and Reference. That is. The maximum length is 120 characters. null null Use Master Description Workstation Type Operating System Full Status Time Zone Node Name TCP Port Any number other than 0. dashes. Any number other than Any number other 0. Click ellipsis (. Domain names must be unique and cannot be the same as workstation and workstation class names. Workstation names must be unique and cannot be the same as workstation class and domain names. this time zone must be the same as the workstation operating system time zone. For a description of time zone names. The name for the extended agent workstation. How to complete the fields of the Properties . For all the access methods. and underscores. if this is not the case. Refer to the Tivoli Workload Scheduler: Planning and Installation Guide. Not used on extended agent workstations. It is useful if you want to predefine job streams. The TCP/IP address (port number) of the z/OS gateway on the z/OS system. Not used on extended agent workstations. this name must be consistent with the name of the options file associated with the workstation. and underscores. if the options file name is <myworkstation>_<mymethod>. than 0.. Enter the same value as the SYSTSIN variable PORT described in Table 57 on page 213. Select it to specify that the host workstation is in the same domain as the master domain manager. The maximum length is 16 characters. SSL Communication SSL Port Mailman Server Behind Firewall Not used on extended agent workstations. then myworkstation and Name must be the same. Select Extended Agent. For all access methods (except the one for z/OS which always has a limit of 8 characters). select the appropriate time zone from the drop-down list.) to display a list of existing domains. Chapter 4. The maximum length is 16 characters. Leave the field blank.Workstation in Database panel Field PeopleSoft Ignore Description by Access Method z/OS Oracle E-Business Suite SAP R/3 Select this option only if you want Tivoli Workload Scheduler to ignore this workstation definition. Fully qualified domain names are accepted. jobs. Defining extended agent workstations 49 . If the Tivoli Workload Scheduler network is using the Time Zone option.. Not used on extended agent workstations.opts. The time zone of the workstation. The Time Zone feature is enabled using the optman command. and objects for a system that has not yet been installed. Name Domain The name of the Tivoli Workload Scheduler domain of the host workstation. dashes. Select Other.Creating a workstation using the Job Scheduling Console Table 16. Not used on extended agent workstations.

tivoli. Host The Tivoli Workload Scheduler name of the host system.. mvsjes To launch and monitor z/OS jobs using JES2 or JES3.rome. refer to the IBM Tivoli Workload Scheduler Reference Guide.Workstation in Database panel (continued) Field PeopleSoft AutoLink Access Method psagent Description by Access Method z/OS Oracle E-Business Suite SAP R/3 Not used on extended agent workstations. Click ellipsis (. Depending on your job scheduling interface. MCMAGENT Note: The name is case sensitive and must be in uppercase. Creating a workstation using the command line Extended agent workstation definitions can also be made on the Tivoli Workload Scheduler command line using the composer program. one of the following: mvsca7 To launch and monitor z/OS jobs using CA-7. The following example shows a definition for a z/OS extended agent workstation named MVSCPU that uses the mvsjes access method.Creating a workstation using the Job Scheduling Console Table 16. Note: In UNIX the name is case sensitive and must be in lowercase.) to see a list of existing hosts. How to complete the fields of the Properties .com tcpaddr 5000 domain masterdm for maestro type x-agent host ROCIOUS access mvsjes end For further details about defining workstations with composer. cpuname MVSCPU description "zOS extended agent" os other node mvsesa36.. r3batch Note: In UNIX the name is case sensitive and must be in lowercase. This is the Tivoli Workload Scheduler fault-tolerant agent or standard agent on which the extended agent is installed. mvsopc To launch and monitor z/OS jobs using Tivoli Workload Scheduler for z/OS. 50 IBM Tivoli Workload Scheduler for Applications: User’s Guide .

Such a network topology statement is made up of one or more (one for each domain) DOMREC statements that describe the topology of the distributed network. The extended agent is hosted by a Tivoli Workload Scheduler agent named TWSA. Extended agent workstations must be defined as fault-tolerant workstations in Tivoli Workload Scheduler for z/OS. 2.Defining workstations for end-to-end scheduling Defining workstations for end-to-end scheduling Scheduling in an end-to-end environment means that in Tivoli Workload Scheduler for z/OS you are scheduling and monitoring jobs that are physically running on Tivoli Workload Scheduler workstations. refer to the Tivoli Job Scheduling Console User’s Guide. you must: 1. For a description of how to define the workstation using the Job Scheduling Console. A fault-tolerant workstation is the Tivoli Workload Scheduler for z/OS definition of an existing Tivoli Workload Scheduler agent in the distributed network. The TOPOLOGY initialization statement is used to define parameters related to the topology of the connected Tivoli Workload Scheduler network. Defining extended agent workstations 51 . ****************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) Chapter 4. Add the same workstation definition to the database using ISPF or the Job Scheduling Console. To define the extended agent workstation in Tivoli Workload Scheduler for z/OS. The Tivoli Workload Scheduler agent is where the job associated with the fault-tolerant workstation actually runs in the distributed network. which is also the domain manager of DOMAIN1. and by several CPUREC statements. The following example shows a CPUREC statement for an SAP R/3 extended agent workstation named R3XA. Define the workstation in the CPUREC initialization statement. Creating the CPUREC statement Create the CPUREC statement for the workstation in the TOPOLOGY initialization statement. one for each fault-tolerant workstation.

Defining the workstation with ISPF Figure 5 shows the ISPF definition for R3XA. It cannot be another standard agent or extended agent. N Non reporting ===> Y FT Work station. Y or N N Started task support. STC WTO DESTINATION Defaults: TRANSPORT TIME DURATION ===> ===> ===> ===> R3XA Extended agent for R/3 access method____________________ C G General. The workstation type. The name of the Tivoli Workload Scheduler workstation hosting the extended agent. see Tivoli Workload Scheduler for z/OS Customization and Tuning. Note: Make sure you write the CPUREC statement before making the ISPF or Job Scheduling Console definition.SS Figure 5. It is the CPUREC statement with the three keywords described in “Creating the CPUREC statement” on page 51 that provides the extended agent specification. For an extended agent. In ISPF (and in the Job Scheduling Console). -------------.MM ===> ________ Duration for a normal operation HH. define the workstation as computer automatic and then set the FT Work station field to Y. P Printer A A Automatic. it must be XAGENT. Y or N N Editing of JCL allowed. Defining an Extended Agent workstation 52 IBM Tivoli Workload Scheduler for Applications: User’s Guide . B or N ===> ===> ===> ===> ===> N Interruption of operation allowed. For SAP R/3. Y or N ________ Name of destination ===> 00. it is r3batch. Y or N ===> SYSPRINT The ddname of daily plan printout data set ===> N Parallel server usage C .CREATING GENERAL INFORMATION ABOUT A W0RK STATION -------------Command ===> Enter the command R for resources A for availability or M for access method above. S Manual start and completion C Completion only. or enter data below: WORK STATION NAME DESCRIPTION WORK STATION TYPE REPORTING ATTR FT Work station PRINTOUT ROUTING SERVER USAGE Options: SPLITTABLE JOB SETUP STARTED TASK.Creating the CPUREC statement CPUDOMAIN(DOMAIN1) CPUTYPE(FTA) CPUUSER(TWSuser) CPUTZ(’Europe/Rome’) The following keywords define R3XA as an extended agent: CPUACCESS CPUHOST The extended agent access method. Y or N N Automatic WTO. CPUTYPE For further information on CPUREC. C Computer.00 Time from previous work station HH. because they alone have no effect without the CPUREC statement.MM. P .

Oracle. and any recovery actions. Defining jobs with the Job Scheduling Console The steps described here for defining an extended agent job are common to all access methods. you must use the Tivoli Workload Scheduler for z/OS ISPF dialogs to define the job. SAP R/3. the extended agent (or access method) requires a Tivoli Workload Scheduler job definition. Extended agent jobs are added to job streams and scheduled in the same way as any other job in Tivoli Workload Scheduler and Tivoli Workload Scheduler for z/OS. 2008 53 . To define the job. or z/OS job with Tivoli Workload Scheduler. In the Actions list of the Job Scheduling Console main window. the access method for SAP R/3 provides supplementary features if you use the alternative steps described in “R/3 Job page” on page 121. To run and monitor a PeopleSoft. © Copyright IBM Corp. The General page of the Properties .Job Definition panel is displayed. Defining extended agent jobs This chapter describes how to define the Tivoli Workload Scheduler jobs associated with the external jobs you want to run through the extended agents. 2. where you specify the external job you want to schedule.Chapter 5. Also. the workstation (also defined in Tivoli Workload Scheduler) on which it is to run. 2003. For all access methods. you can use either of the following: v The Tivoli Job Scheduling Console v The Tivoli Workload Scheduler command line If you are scheduling in an end-to-end environment. follow these steps: 1. select New Job Definition. You must also create a member in the SCRIPTLIB with a JOBREC statement for the job. Select an engine.

” on page 115. “Managing the running of SAP jobs. The SAP task type is displayed only if you installed the extended agent for SAP R/3. 54 IBM Tivoli Workload Scheduler for Applications: User’s Guide .Job Definition panel The panel consists of the following: v “General page” v “Task page” on page 56 General page Use the General page to provide general information about the new job definition. The page consists of the following: v Information group: Task Type From the pull-down menu.Defining jobs with the Job Scheduling Console Figure 6. For detailed information see Chapter 15. select one of the following: Other The job is a Tivoli Workload Scheduler job that runs a job belonging to one of the following applications: – PeopleSoft – Oracle E-Business Suite – z/OS SAP The job is a Tivoli Workload Scheduler job that runs an SAP R/3 job. The General Page of the Properties .

Possible values are: Stop Continue Rerun Do not continue with the next job. It can be the same as the external job name.. select the recovery option you want to associate with the job if it ends in error. Rerun the job.) to display a list of workstations. Description Type a description of the job. This must be a valid user on the Tivoli Workload Scheduler host workstation who must also be able to access the external product. The maximum length is 40 characters. The text can contain up to 64 characters.) to display a list of recovery jobs from which to select the recovery job to run if the job you are defining ends in error. The Status of All Prompts shows all recovery prompts. the prompt status is Asked and the message is displayed. – The recovery job workstation must be in the same domain as the parent job workstation. Workstation Name Type the name of the extended agent workstation where the Tivoli Workload Scheduler job runs or use ellipsis (. Follow these guidelines: – If either workstation is an extended agent. This is the default value. Recovery jobs are run only once for each instance of the job. Normally.General page Name Type the name of the Tivoli Workload Scheduler job that runs the external application job whose name you provide in the Job Name field of the Task page. Job Click ellipsis (. Add Parameter Adds a parameter to the login field. Not all jobs are eligible to have recovery jobs run on a different workstation. The maximum length is 47 characters. If a job ended successfully. For more information. specified during the installation of Tivoli Workload Scheduler for Applications. Message Type the text of a recovery prompt to be displayed if the job ends in error.. this is the value of the LJuser parameter. Specify a user that can log on to the workstation where the job runs. dashes. Defining extended agent jobs 55 . The name is entered automatically when you select a recovery job.. Continue with the next job. the status is Not Asked. v Recovery Options group: From the pull-down menu. Workstation Name Displays the name of the workstation where the recovery job runs. as long as it is valid in Tivoli Workload Scheduler. see Tivoli Workload Scheduler: Job Scheduling Console User’s Guide. and can contain alphanumeric characters. it must be hosted by a domain manager or a fault-tolerant agent that runs in Full Status mode. The recovery prompt is an ad hoc prompt. Chapter 5.. If a job ended in error. that is in the options file for the method. v Login group: Login Type the name of the user who launches the job. The maximum length is 120 characters. and underscores. The name must start with a letter.

Figure 7. Do not use double quotes (″). If you selected Other. see “Task string parameters for Oracle E-Business Suite jobs” on page 67. v For Oracle Applications jobs. The maximum length is 4095 characters.Job Definition panel The content of the task page depends on the task type you selected. Script When the task is a script. Write the parameters in a string having the following format: -parameter1 value1 -parameter2 value2. if you selected SAP.-parametern valuen 56 IBM Tivoli Workload Scheduler for Applications: User’s Guide . proceed as described in “Task page” on page 118. it must run in Full Status mode. v For z/OS jobs. This page is not available until a workstation has been specified in the General page. see “Task string parameters for PeopleSoft jobs” on page 83.. provide the following information. v For SAP R/3 jobs. type the name in a file that does not have spaces and use the second file..General page – If the recovery job workstation is a fault-tolerant agent. v For Peoplesoft jobs. If the file name contains blanks. Do not specify files on mapped drives. The Task Page of the Properties . Task page Use the Task page to provide task information for the external job that is run by the Tivoli Workload Scheduler job defined in the General page. this is the file name and any options and arguments. see “Task definition syntax for z/OS jobs scheduled with Tivoli Workload Scheduler” on page 223. see “Task string to define SAP jobs” on page 129.

.” on page 239. The Find Parameters panel displays where you can list and add pre-defined Tivoli Workload Scheduler parameters to the Script field. Defining jobs using the Tivoli Workload Scheduler command line You can also be define jobs using the composer command line of Tivoli Workload Scheduler. but must be added to the SCRIPTLIB of Tivoli Workload Scheduler for z/OS. The Oracle Applications job is named poxacr and its owner is global. Enter a logical expression that defines the success condition. v “Task definition syntax for z/OS jobs scheduled with Tivoli Workload Scheduler” on page 223. != or <>.General page Clicking on Add Parameter. Tivoli Workload Scheduler will run job recov2 and then continue processing.. The following example describes a Tivoli Workload Scheduler job named orajob2 that runs in an Oracle Applications extended agent workstation named ora002. Defining jobs for end-to-end scheduling Extended agent jobs scheduled to run in an end-to-end environment cannot be defined using the Job Scheduling Console or the Tivoli Workload Scheduler command line. see Chapter 28. It logs on to UNIX as orajobs and launches a job under Oracle Applications. This is the Tivoli Workload Scheduler for z/OS job that is to drive the running of an SAP R/3 job (named BAPRINT46B as shown in the next example). If recovery is needed. It shows as an extended agent job because the associated workstation is Chapter 5. but the choice of an extended agent workstation denotes their kind. ora002#orajob2 streamlogon orajobs scriptname "-user global -job fnd ’application developer’ po poxacr -prn ps4 2 -v1 ’abc’" description "oracle apps job #2" recovery continue after recov2 The arguments of scriptname differ by application. Allowed operators are comparison operators (=. extended agent jobs are defined like any other job. refer to the Tivoli Workload Scheduler Reference Guide. “The return code mapping feature. v “Task string parameters for PeopleSoft jobs” on page 83.. For a detailed description about how Tivoli Workload Scheduler calculates the return code mapping for PeopleSoft. The following example shows the definition of a job named SAPJOB. In the OPERATIONS ISPF panel of Tivoli Workload Scheduler for z/OS. see: v “Task string parameters for Oracle E-Business Suite jobs” on page 67. >=. <=) and logical operators (AND. OR. <. v “Task string to define SAP jobs” on page 129. >. Return Code Mapping Expression The return codes that cause the job to be successful. NOT). For more information about using the command line to define jobs. For a detailed description about how Tivoli Workload Scheduler calculates the return code mapping for SAP R/3 and Oracle E-Business Suite. Defining extended agent jobs 57 . For details. see “Configuring the job status mapping policy” on page 85.

enter the GRAPH command to view the list graphically. v “Task string parameters for PeopleSoft jobs” on page 83. because for PeopleSoft jobs single quotes are already used in the string. create a member in the SCRIPTLIB of Tivoli Workload Scheduler for z/OS with details about the job in a JOBREC statement. was previously defined on SAP R/3 and assigned with an ID of 14160001. --------------------------------.Delete S . HH. Launch the job.Select operation details. Application : APLL1 FTW appl Row Oper Duration Job name Internal predecessors Morepreds cmd ws no. For details. R(nn). A SAPJOB member was created for the job of the previous example.00. refer to the Tivoli Workload Scheduler documentation. Verify that the application system to which the job belongs and the related database is up and running. It contains a JOBREC 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 prior to running the job. see: v “Task string parameters for Oracle E-Business Suite jobs” on page 67. The entire string that follows the JOBCMD keyword must be enclosed within double quotation marks. The following example is for a PeopleSoft job.DD .01 SAPJOB___ ___ ___ ___ ___ ___ ___ ___ ___ 0 0 ******************************* Bottom of data ******************************** Figure 8.Edit JCL Enter the TEXT command above to include operation text in this list. v “Task string to define SAP jobs” on page 129 or Chapter 17.RR(nn) .Repeat. 58 IBM Tivoli Workload Scheduler for Applications: User’s Guide .Insert.SS -IntExt’’’’ R3XA 001 00. For details. v “Task definition syntax for z/OS jobs scheduled with Tivoli Workload Scheduler” on page 223.MM. BAPRINT46B.” on page 149. JOBREC JOBCMD("/ -process XRFWIN -type ’SQR Report’ -runcontrol TWS") JOBUSR(PsBuild) The arguments of JOBCMD differ by application. Defining an Extended Agent job for end-to-end scheduling For each job.OPERATIONS -----------------Row 1 to 1 of 1 Command ===> Scroll ===> PAGE Enter/Change data in the rows. D(nn). J . 2. that was manually written in JOBCMD. “Defining SAP jobs dynamically. The job of this example. or.Defining jobs for end-to-end scheduling an extended agent workstation named R3XA. and/or enter any of the following row commands: I(nn) . Submitting extended agent jobs To submit extended agent jobs perform the following steps: 1.

Oracle E-Business Suite access method © Copyright IBM Corp. 2003.Part 2. 2008 59 .

60 IBM Tivoli Workload Scheduler for Applications: User’s Guide .

v Define inter-dependencies between Oracle Applications jobs and jobs that run on different systems such as SAP R/3 and PeopleSoft.Chapter 6. Table 17 describes the roles and responsibilities of all actors in the process model. showing the tasks they perform. upgrading. and Oracle E-Business Suite instance must be installed on the same physical node. and in a prescribed order. different users contribute to the implementation and operation of the product. and uninstalling IBM Tivoli Workload Scheduler for Applications. v Define inter-dependencies between Oracle Applications jobs and jobs that run on different operating systems. times.i. “Installing. unless otherwise specified. Note: The procedure described in this part refers to Oracle E-Business Suite and applies both to Oracle Applications version 10. Introducing Tivoli Workload Scheduler for Applications for Oracle E-Business Suite Using Tivoli Workload Scheduler for Applications for Oracle E-Business Suite you can schedule Oracle E-Business Suite jobs using Tivoli Workload Scheduler.i installed.0 or 11. Roles and responsibilities in Tivoli Workload Scheduler for Applications for Oracle E-Business Suite User role Oracle E-Business Suite administrator Oracle E-Business Suite developer Tivoli Workload Scheduler for Applications configurator © Copyright IBM Corp.0 or 11. you must have Oracle Applications version 10. | | | | | | | | | | | | | Roles and responsibilities In a typical enterprise. 2008 User task “Completing the installation of the access method for Oracle E-Business Suite” on page 31 “Defining jobs in Oracle E-Business Suite” on page 67 “Defining the configuration options” on page 63 61 . v Schedule Oracle E-Business Suite jobs to run on specified days.” on page 5. you can perform the following tasks: v Use Tivoli Workload Scheduler standard job dependencies (except Open File dependencies). Software requirements In addition to the supported operating systems and prerequisite software listed in Chapter 2. The Tivoli Workload Scheduler host. 2003. Features Using Tivoli Workload Scheduler for Applications for Oracle E-Business Suite. Table 17.7 and to Oracle E-Business Suite versions 11. Tivoli Workload Scheduler extended agent for Oracle E-Business Suite.7 or Oracle E-Business Suite versions 11. v Customize job execution return codes.

Use this to prepare a job for launching. “Setting options with the Option Editor. optionally.opts A global options file which contains configuration settings for the access method.mk Options MCMAGENT. When you launch. the method launches one of the back-end programs to accomplish the task.” on page 63 and Chapter 3. “Configuring the Oracle E-Business Suite access method. A program that monitors the status of the submitted job. See Chapter 7. Back-end MCMLJ MCMSTAT MCMTJ mcm.” on page 43 for details. “Configuring the Oracle E-Business Suite access method.Features | | | | | | | Table 17. “Setting options with the Option Editor.opts A local options file which contains configuration settings for the extended agent. See Chapter 7. A program that stops the submitted job on receiving a kill signal from Tivoli Workload Scheduler. A program that submits a job to Oracle Concurrent Manager. WORKSTATION_ NAME_MCMAGENT. One file is required for each extended agent workstation that you define. It is created by the installation process of Tivoli Workload Scheduler for Applications with some of the values you enter during installation. Roles and responsibilities in Tivoli Workload Scheduler for Applications for Oracle E-Business Suite (continued) User role Tivoli Workload Scheduler for Applications developer User task “Defining Oracle E-Business Suite jobs in Tivoli Workload Scheduler” on page 67 Interface software The interface between Tivoli Workload Scheduler and Oracle E-Business Suite comprises the following software: Front-end MCMAGENT The Tivoli Workload Scheduler for Applications for Oracle E-Business Suite access method. stop the job. using the options of the method.” on page 63 and Chapter 3. A makefile utility for linking the above programs with Oracle E-Business Suite.” on page 43 for details. monitor and. 62 IBM Tivoli Workload Scheduler for Applications: User’s Guide .

named WORKSTATIONNAME_MCMAGENT. The . you can use either the Option Editor available with this product. the agent uses.opts.Chapter 7. Table 18 lists the options that you can define for the MCMAGENT access method. You can also create local files.env filename identified here is used to set the environment dynamically when Tivoli Workload Scheduler runs jobs on the Oracle Applications extended agent. To edit both options files. If you do not create a local options file. The options must be written one per line and have the following format (with no spaces included): OPTION=VALUE Table 18. It can be the same as LJUSER. 2003. which must be located in the TWShome/methods directory of the hosting computer for the extended agent.env or APPDEMO. or any other text editor. (Mandatory) The FND top directory where the Oracle E-Business Suite Object Library resides. named MCMAGENT. For examples of an options file for this access method. see “Examples” on page 65. MCMAGENT access method options Option Description (Mandatory) Assigns the user name used by the access method to check file dependencies (CF tasks). Configuring the Oracle E-Business Suite access method This chapter provides detailed reference information about the Tivoli Workload Scheduler for Applications for Oracle E-Business Suite options file. | | | CFUSER ENV FND_TOPDIR © Copyright IBM Corp.” on page 43.env). by default.opts. Each instance of Oracle E-Business Suite has its own environment file (APPLSYS. the global options file. For details about how to create and edit the options files with the Option Editor. (Mandatory) The environment file to run. “Setting options with the Option Editor. see Chapter 3. Defining the configuration options The Tivoli Workload Scheduler for Applications installation process creates a default global options file for the Oracle E-Business Suite access method. 2008 63 .

64 IBM Tivoli Workload Scheduler for Applications: User’s Guide . Use MIN_TIME and MAX_TIME to poll for status information more frequently when the job has just started (helping you to catch an immediate job failure as soon as possible. | | | | | PASSWORD PATH PRINTER_NAME THREE_TIER_DB | | | | | | TWSMETH_CP (Optional) The code page that the MCMAGENT access method uses to write its output. and then change to a longer interval for jobs that are expected to take some time before completion. To encrypt the password use the enigma utility. It can be any of the existing TIS codepages. and then change to a longer interval for jobs that are expected to take some time before completion. The job status polling interval is incremented each polling cycle (see MIN_TIME). including the existing path. see “Encrypting Oracle E-Business Suite user passwords” on page 66. (Mandatory) The password for the selected user ID. It is expressed in seconds. (Mandatory) The default printer ID. (Mandatory) The UNIX directory where Oracle E-Business Suite is installed. This option must be consistent with TWSMETH_CP. This option must be consistent with TWSMETH_LANG. it remains at this value. for example). (Mandatory) The Oracle system identifier of the database instance you are connecting to. TWSMETH_LANG (Optional) The language used to report messages. (Mandatory) The setting of the PATH variable. provided with the product. the path to the include directory under the FND Top directory. for example). Use MIN_TIME and MAX_TIME to poll for status information more frequently when the job has just started (helping you to catch an immediate job failure as soon as possible. When the interval reaches or exceeds the value of this option. It is expressed in seconds. (Optional) Allows the extended agent to function in a three-tier Oracle connectivity environment. MCMAGENT access method options (continued) Option MAX_TIME Description (Mandatory) This acts as the maximum increment of the job status polling interval. For details. and as the incremental value by which the polling interval is increased each polling cycle. ORA_APP_TOPDIR ORACLE_HOME ORACLE_SID (Mandatory) The UNIX directory where Oracle E-Business Suite is installed. This corresponds to the value of the Oracle E-Business Suite$ORACLE_SID variable. the path to the bin directory of Oracle E-Business Suite. See the sample options file shown in “Examples” on page 65. Supply the TNS service name defined in the Oracle environment pointing to a remote database server. and others as needed.Defining the Oracle E-Business Suite configuration options Table 18. It must be encrypted. MIN_TIME (Mandatory) This value is used as both the initial job status polling interval.

28 PATH=$PATH:$FND_TOP/bin:$MCM_TOP/bin ENV=$APPL_TOP/APPTST.env USERID=APPS_US PASSWORD=APPS_US PRINTER_NAME=PRINTER1 MIN_TIME=10 MAX_TIME=200 The following example shows the options file of an extended agent configured for an Oracle three-tier connectivity environment. (Mandatory) A database user ID that has access to all the modules in Oracle E-Business Suite. TST is the name of the Oracle database instance where the Oracle E-Business Suite database is located and REMOTEDB is the TNS Oracle service name. The default value is 0. manage. In this example. MIN_TIME=10 ORACLE_HOME=/oracle/db/TST ORACLE_SID=TST ORA_APP_TOPDIR=/oracle/Apps11 FND_TOPDIR=$APPL_TOP/fnd/11. and terminate jobs in Oracle E-Business Suite. MCMAGENT access method options (continued) Option Description (Optional) Specifies the encoding character set of the Oracle E-Business Suite database. (Optional) Enables the encoding of the extended parameters in UTF-8 format.opts is a sample options file: ORACLE_HOME=/general/ora716 ORACLE_SID=DEMO106 ORA_APP_TOPDIR=/apps106 FND_TOPDIR=$APPL_TOP/fnd/* PATH=$PATH:$ORACLE_HOME/bin:$FND_TOP/include ENV=$APPL_TOP/APPDEMO106. meaning that the code set of the operating system is used. Configuring the Oracle E-Business Suite access method 65 . It must be able to launch. The default value is the default code set of the operating system.env USERID=apps PASSWORD=##3Y-UGcZ-3Kap-6m PRINTER_NAME=prt4b2 MAX_TIME=150 THREE_TIER_DB=REMOTEDB | | | | | The following example shows the encoding options to set for an Oracle E-Business Suite database that uses the code page UTF8 so that it can process a job whose task string contains Japanese characters. or 0 to disable it. Specify 1 to enable the option.0.Defining the Oracle E-Business Suite configuration options Table 18. UTF8CMDLINE=1 TWSXA_CP=UTF8 Chapter 7. | | | TWSXA_CP USERID | | | | UTF8CMDLINE Examples File ORACLECPU_MCMAGENT.

a new algorithm is applied to encrypt the password that is stored in the options file. The old password encryption is still recognized and processed by Tivoli Workload Scheduler for Applications version 8. The program returns an encrypted version that you can then enter in the options file.4. Run the enigma program as follows: enigma [password] You can include the password on the command line or enter it in the response to a prompt. | | | | | | | With Tivoli Workload Scheduler for Applications version 8. the password value is automatically encrypted before it is written to the file. or the Option Editor the password is encrypted by applying this new algorithm. When you use enigma.Encrypting Oracle E-Business Suite user passwords Encrypting Oracle E-Business Suite user passwords When you make entries in the options file. It is also applied if you open and save the options file with the Option Editor.4. 66 IBM Tivoli Workload Scheduler for Applications: User’s Guide . you must run the enigma program to encrypt the password before writing it to the file. so you do not need to encrypt the password again. If you modify the file with a text editor. pwdcrypt.

Defining Oracle E-Business Suite jobs This chapter provides information for defining Oracle E-Business Suite jobs in Tivoli Workload Scheduler. and recovery options. Task string parameters for Oracle E-Business Suite jobs This section describes the task string parameters that manage the operation of Oracle E-Business Suite jobs. To define a job. if you use the Tivoli Workload Scheduler command line. See Chapter 5. 2008 The name of a valid Oracle Applications user (Apps login). v As arguments of the scriptname keyword in the job definition statement. specify the scheduling and resubmission information. The following is an example of a JOBREC statement: JOBREC JOBCMD(’/-user appslogin -job jobspecs’) JOBUSR(TWS_user_name) | | | | | | | | where: appslogin © Copyright IBM Corp. the jobs run normally.Job Definition Window. When you are submitting the job in Oracle Concurrent Manager. jobs that are to be scheduled with Tivoli Workload Scheduler are defined in the same way as other Oracle E-Business Suite jobs (and can be submitted in Oracle Concurrent Manager). 67 . v As arguments of the JOBCMD keyword in the JOBREC statement in the SCRIPTLIB of Tivoli Workload Scheduler for z/OS.” on page 53.Chapter 8. if you use the Job Scheduling Console. However. use the Define Concurrent Program Executables and Define Concurrent Program forms and fill in the general data information for the job. if you are scheduling in an end-to-end environment. Running a single job concurrently If an Oracle E-Business Suite job is scheduled to run more than once in Tivoli Workload Scheduler. if the Oracle E-Business Suite user has specified that the job cannot run concurrently. and Tivoli Workload Scheduler launches it concurrently. The job is now available for scheduling from Tivoli Workload Scheduler (and can also be submitted in Oracle Concurrent Manager). 2003. the second job enters a state of WAIT until the first job completes. Defining jobs in Oracle E-Business Suite In Oracle E-Business Suite. “Defining extended agent jobs. Tivoli Workload Scheduler will handle the scheduling and re-submission information. user name. Oracle E-Business Suite jobs are defined in Tivoli Workload Scheduler like other jobs and include job name. Specify them in the following places when you define their associated Tivoli Workload Scheduler jobs: v In the Command field of the Task page of the Properties . When you are submitting the job through Tivoli Workload Scheduler. Defining Oracle E-Business Suite jobs in Tivoli Workload Scheduler Tivoli Workload Scheduler job definitions are required for each Oracle E-Business Suite job you plan to schedule.

PO). 2. 2. ‘Application Developer’). Possible values are: 1 2 3 Only error messages are written in the trace file. 4. The job name (for example. For details. Informational messages and warnings are also written in the trace file. The printer name (optional). Table 19 describes the parameters to define Oracle E-Business Suite jobs. A most verbose debug output is written in the trace file. The job name must be uppercase. There are four job attributes that must be specified in the following order: 1. If omitted. They must be entered in the following order: 1. The name of the application that registered the job (for example. The attributes of the Oracle Applications job. For example: -prn ps4 2 tracelvl Specify the trace setting for the job. The name of the Applications module used to sign on to Oracle Applications (for example. 3. POXACR).Task string parameters for Oracle E-Business Suite jobs | | | | | | jobspecs TWS_user_name The Tivoli Workload Scheduler for z/OS user who runs the MCMAGENT access method from the end-to-end scheduling environment. see Table 19. The attributes of the Oracle Applications job. the default printer specified in the options file is used. A valid responsibility for the Applications module (for example. FND). The number of copies. “Configuring the tracing utility. Task string parameters for Oracle E-Business Suite jobs Parameter -user appslogin -job jobspecs Description The name of a valid Oracle Applications user (Apps login).” on page 247 for detailed information. For example: -job FND ’Application Developer’ PO POXACR -prn printopts The two printer options for the job. Refer to Chapter 29. This is the default. Table 19. This parameter must be enclosed in single quotes. 68 IBM Tivoli Workload Scheduler for Applications: User’s Guide .

The access method automatically adds all the parameters that you do not specify in the definition with a value of null. Task string parameters for Oracle E-Business Suite jobs (continued) Parameter [-vn (’value’|null|:parameter)] Description The job’s parameters. Table 20 provides you with a list of the state transitions in Tivoli Workload Scheduler and the corresponding Oracle E-Business Suite states.Task string parameters for Oracle E-Business Suite jobs Table 19. v2. refer to the Tivoli Workload Scheduler Reference Guide. Defining Oracle E-Business Suite jobs 69 . you can monitor its progress with conman. if any. Enclose value in single quotes if it contains special characters. v n is the parameter number (v1. refer to the Tivoli Workload Scheduler Reference Manual. Tivoli Workload Scheduler and Oracle E-Business Suite job states Oracle Concurrent Manager States Request Failure or Request not Found Inactive Pending Pending Normal Running Normal Completed Normal Completed Warning Completed Error Completed Terminated Completed Canceled Tivoli Workload Scheduler States UT (unsupported task) SUSP WAIT ADD EXEC SUCC SUCC ABEND ABEND ABEND For more information about job management. These are two examples: -v4 ’abc’ -v15 :p1 The following is an example of an entire task string specification: -user GLOBAL -job FND ’Application Developer’ PO POXACR -prn ps4 2 -v1 ’abc’ Tivoli Workload Scheduler and Oracle E-Business Suite job states When an Oracle E-Business Suite job is launched by Tivoli Workload Scheduler. This string is optional if no parameters are specified for the job in Oracle Applications. Chapter 8. v One of the following: value An actual value. and so on). Table 20. :parameter The name of an already defined Tivoli Workload Scheduler parameter. For more information about Tivoli Workload Scheduler parameters.

70

IBM Tivoli Workload Scheduler for Applications: User’s Guide

Part 3. PeopleSoft access method

© Copyright IBM Corp. 2003, 2008

71

72

IBM Tivoli Workload Scheduler for Applications: User’s Guide

Chapter 9. Introducing Tivoli Workload Scheduler for Applications for PeopleSoft
Using Tivoli Workload Scheduler for Applications for PeopleSoft you can run and monitor PeopleSoft jobs from the Tivoli Workload Scheduler environment. These jobs can be run as part of a schedule or submitted for ad-hoc job processing. PeopleSoft extended agent jobs can have all of the same dependencies and recovery options as other Tivoli Workload Scheduler jobs. PeopleSoft jobs must be defined in Tivoli Workload Scheduler to be run and managed in the Tivoli Workload Scheduler environment.

Software requirements
In addition to the supported operating systems and prerequisite software listed in Chapter 2, “Installing, upgrading, and uninstalling IBM Tivoli Workload Scheduler for Applications,” on page 5, you must have the following: v PeopleTools version 8.44, or later. v Access to the psjoa.jar file located in the ps_home\class directory.

Features
Using Tivoli Workload Scheduler for Applications for PeopleSoft, you can perform the following tasks: v Use Tivoli Workload Scheduler standard job dependencies on PeopleSoft jobs. v Schedule PeopleSoft jobs to run on specified days, times, and in a prescribed order. v Define inter-dependencies between PeopleSoft jobs and Tivoli Workload Scheduler jobs that run on different applications such as SAP R/3 and Oracle E-Business Suite. v Define inter-dependencies between PeopleSoft jobs and jobs that run on different operating systems. | | | | | | | | | | | | | | |

Roles and responsibilities
In a typical enterprise, different users contribute to the implementation and operation of the product. Table 21 describes the roles and responsibilities of all actors in the process model, showing the tasks they perform.
Table 21. Roles and responsibilities in Tivoli Workload Scheduler for Applications for PeopleSoft User role Tivoli Workload Scheduler for Applications configurator Tivoli Workload Scheduler for Applications developer User task “Defining the configuration options” on page 75 v “Defining Peoplesoft jobs in Tivoli Workload Scheduler” on page 83 v “Configuring the job status mapping policy” on page 85

© Copyright IBM Corp. 2003, 2008

73

Features
| | | | | | | | | | |
Table 21. Roles and responsibilities in Tivoli Workload Scheduler for Applications for PeopleSoft (continued) User role PeopleSoft administrator User task v “Creating a batch processing ID in PeopleSoft” on page 78 v “Configuring the ITWS_PSXA PeopleSoft project” on page 78 v “Uploading the PeopleSoft project” on page 79

Scheduling process for the PeopleSoft extended agent
Tivoli Workload Scheduler can launch and monitor jobs in the PeopleSoft process scheduler using a PeopleSoft extended agent workstation. The PeopleSoft extended agent is defined in a standard Tivoli Workload Scheduler workstation definition. This definition is a logical workstation name and specifies the access method as psagent. The access method is used to communicate job requests to the PeopleSoft process scheduler. To launch a PeopleSoft job, Tivoli Workload Scheduler runs the psagent method, passing it information about the job. An options file provides the method with the path, the executable, and other information about the PeopleSoft process scheduler and application server used to launch the job. The extended agent can then access the PeopleSoft process request table and make an entry in the table to launch the job. Job progress and status information is written to the job’s standard list file. There is no need to install Database connectivity on fault-tolerant agents hosting PeopleSoft extended agents because the method currently uses the PeopleSoft 3-tier architecture. You must configure at least one PeopleSoft Application Server for the extended agent to work. The application server must be active to successfully submit jobs to the PeopleSoft process scheduler.

PeopleSoft job tracking in Tivoli Workload Scheduler
A PeopleSoft job is a collection of processes that run together as a single unit. Tivoli Workload Scheduler jobs can be defined in one of the following ways: v As PeopleSoft jobs, that is, as a collection of PeopleSoft processes. In this case, the status of the PeopleSoft job is tracked, not the status of the individual processes within the job. v As PeopleSoft processes. In this case, the status of the individual process is tracked and Tivoli Workload Scheduler schedules can be defined to create complex inter-dependencies and recovery options between PeopleSoft processes.

Security
Security for the PeopleSoft jobs is handled by standard Tivoli Workload Scheduler security.

74

IBM Tivoli Workload Scheduler for Applications: User’s Guide

Chapter 10. Configuring the PeopleSoft access method
This chapter provides detailed reference information about the PeopleSoft options and how to define them in the options file. It also describes the tasks for: v “Creating a batch processing ID in PeopleSoft” on page 78 v “Configuring the ITWS_PSXA PeopleSoft project” on page 78 v “Uploading the PeopleSoft project” on page 79

Defining the configuration options
The Tivoli Workload Scheduler for Applications installation process creates a default global options file for the psagent access method, named psagent.opts. You can also create local files, named WORKSTATIONNAME_psagent.ops, which must be located in the TWShome/methods directory of the hosting computer for the extended agent. To edit both options file, you can use either the Option Editor available with this product, or any other text editor. For details about how to create and edit the options files with the Option Editor, see Chapter 3, “Setting options with the Option Editor,” on page 43. For examples of options files for this access method, see“PeopleSoft options file example” on page 77. Table 22 describes the options for the psagent access method. Option names are case insensitive. Before you use a manually-created options file, check that all the option names are written correctly, otherwise they will be ignored.
Table 22. Psagent access method options Option CHECKINTERVAL Description (Optional) Specifies the frequency (in seconds) with which the psagent monitors a submitted process up to completion. The default is 120. (Optional) Specifies the ID of the Tivoli Workload Scheduler user that runs the psagent to launch jobs (LJ tasks). This user must be a valid Tivoli Workload Scheduler user on the Tivoli Workload Scheduler hosting workstation. (Optional) Determines whether the distribution status of the PeopleSoft request is taken into account when determining the status of the Tivoli Workload Scheduler job. Values are 0 (not taken into account) or 1 (taken into account - the default value). (Mandatory) Specifies the PeopleSoft operator ID used for the connection to the PeopleSoft application server. (Mandatory) Specifies the encrypted password (case-sensitive) of the PeopleSoft operator ID used for the connection to the PeopleSoft application server. For details about how to encrypt the password, see “Encrypting PeopleSoft operator passwords” on page 77.

LJUSER

PS_DISTSTATUS

PSFT_OPERATOR_ID PSFT_OPERATOR_PWD

© Copyright IBM Corp. 2003, 2008

75

Defining PeopleSoft options
Table 22. Psagent access method options (continued) Option PSJOAPATH Description (Optional) Specifies the full path name of the psjoa.jar file. If this option is not set, the path name provided during the installation is used. Ensure you identify the version of the psjoa.jar file that corresponds to the version of PeopleSoft that you are using. RUNLOCATION SERVER_NAME_LIST (Optional) Specifies the default PeopleTools process server that processes the requests. (Mandatory) Specifies the list of application servers that the psagent tries to connect to. It is a comma-separated list of addresses in the format: <server>:<port> [,<server>:<port>] ... where: <server> <port> TWS_MAX_WAIT_TIME Species the host name or TCP/IP address of the server Specifies the port number the server is listening on.

(Optional) Specifies the maximum time that the extended agent waits (timeout) after a failed operation on the PeopleSoft application server before retrying the operation. The default is 10 seconds. (Optional) Specifies the minimum time that the extended agent waits (timeout) after a failed operation on the PeopleSoft application server before retrying the operation. The default is 5 seconds. (Optional) The maximum number of times that the extended agent attempts a failed operation on the PeopleSoft application server. The default is 5. (Optional) Specifies the name of the component interface that the psagent invokes to submit jobs to PeopleSoft. The default is ITWS_PROCESSREQUEST. If you use this default, you must perform the customization steps described in “Configuring the ITWS_PSXA PeopleSoft project” on page 78. If you do not plan to schedule jobs containing in-line variables, and you do not want to perform the additional customization steps, you must replace the default value with PROCESSREQUEST. This is the component interface invoked by previous versions of the access method; it does not allow the use of in-line variables.

TWS_MIN_WAIT_TIME

TWS_RETRY

TWSXA_INLINE_CI

TWSA_SCHED_METH

(Optional) Specifies the name of the PeopleSoft method invoked by the component interface specified in TWSXA_INLINE_CI. Both ITWS_PROCESSREQUEST and PROCESSREQUEST use the default method Schedule. If you are using either of these component interfaces, leave the default. If you are using a different component interface, specify the name of the method called by your component interface, respecting the case of the PeopleSoft object name.

76

IBM Tivoli Workload Scheduler for Applications: User’s Guide

LJuser=TwsUsr CheckInterval=120 PSFT_OPERATOR_ID=PSHC PSFT_OPERATOR_PWD=***** SERVER_NAME_LIST=9. you can set up multiple PeopleSoft extended agent workstations that connect to the same method but use different options files. a new algorithm is applied to encrypt the password that is stored in the options file.” Encrypting PeopleSoft operator passwords When you add or change the PeopleSoft operator password using the Option Editor. the password is automatically encrypted and inserted into the file. pwdcrypt. each with a separate application server.120. Remember to save the file in the TWShome\methods directory. or the Option Editor the password is encrypted by applying this new algorithm. This allows the user to set up an extended agent for each PeopleSoft application server. it first looks for the options file with extended agent workstation name prepended to psagent. and PRODUCTION environment.PeopleSoft options file example PeopleSoft options file example Below is a sample options file for PeopleTools version 8. so you do not need to encrypt the password again. It is also applied if you open and save the options file with the Option Editor. It can help you determine your specific site requirements although your options file might be different. Configuring the PeopleSoft access method 77 . and appears as asterisks on the screen. and then for the default psagent. To support this. as described in “Encrypting PeopleSoft operator passwords.opts file.36:9000 If you create the options file manually. DEMO.opts. Chapter 10. This requires that the psagent method uses a separate connect string for each application server.4.87.opts The psagent method searches first for an options file with the extended agent workstation name. Connecting to more than one PeopleSoft application server It might be necessary for thepsagent method to connect to more than one PeopleSoft application server. To run the encryption program.4. | | | | | | | With Tivoli Workload Scheduler for Applications version 8. When a workstation starts the method. you must encrypt the PeopleSoft operator password. you must run the pwdcrypt program to encrypt the password before writing it in the file. enter the following command: pwdcrypt password The program returns an encrypted version that you can then copy and paste into the options file. For example.44. a PeopleSoft extended agent named ps847system would have the following options file: ps847system_psagent. When you use enigma. For example. The old password encryption is still recognized and processed by Tivoli Workload Scheduler for Applications version 8. When you add or change the PeopleSoft user password using a text editor. a single installation of PeopleSoft might have a TEST.

Configuring the ITWS_PSXA PeopleSoft project The configuration steps described in this section are necessary to enable Tivoli Workload Scheduler for Applications to schedule PeopleSoft jobs that have in-line variables in their definitions. The ITWS_PROCESSREQUEST component interface works around some limitations of the PeopleSoft APIs when invoked from a batch environment. so if the PeopleSoft process uses work records in its parameter list. data that is stored in the PeopleSoft database and referred to by a runcontrol ID parameter that is used to retrieve a runcontrol data record. the name of the process type in the PeopleSoft GUI becomes ITWS_process type. v A work record definition name for Structured Query Report reports starts with R_ When you use Tivoli Workload Scheduler to submit a process that has in-line bind variables. With current PeopleSoft APIs.PeopleSoft options file example To connect to only one application server. Tivoli Workload Scheduler cannot schedule jobs defined with in-line bind variables. This operator ID must be granted authority to use the Component Interface in the PeopleTools environment. needs to be loaded into the Component Buffer before scheduling the API invocation. For example. To identify work records. When unresolved data is present in the submitted job. Creating a batch processing ID in PeopleSoft Create an operator ID in PeopleSoft dedicated to batch scheduling. It then allows job submission regardless of the use of in-line variable definitions in the jobs. All the jobs submitted by IBM Tivoli Workload Scheduler should use this operator ID. the PeopleSoft system refuses submission and ends with an error. SQR Process becomes ITWS_SQR Process. The variable substitution mechanism does not support work records. even though it is available in the database. This cannot be done from a batch environment. use the following PeopleSoft naming conventions: v A derived work record name ends with ’_WRK’. when invoking the PeopleSoft scheduling APIs from a batch interface. the data related to the runcontrol ID is not available for the submission of a job. Because of these limitations.opts. the access method provides the ability to use data stored in the PeopleSoft database to resolve in-line variable values by taking data from the database and substituting it with variable definitions. use the default name for the options file. By invoking this component interface. To schedule a job that contains in-line variables in its definition you must perform the following tasks: 78 IBM Tivoli Workload Scheduler for Applications: User’s Guide .ORA-00942: table or view does not exist Statement: select nvsdlist from PS_NVS_WRK WHERE BUSINESS_UNIT = :1 AND REPORT_ID = :2 Original Statement: SELECT NVSDLIST FROM PS_NVS_WRK WHERE BUSINESS_UNIT = :1 AND REPORT_ID = :2. psagent. Therefore. you find a message similar to the following in the Tivoli Workload Scheduler joblog: Error Position: 21 Return: 942 . The ITWS_PROCESSREQUEST component interface enables Tivoli Workload Scheduler for Applications to schedule PeopleSoft jobs that have in-line variables in their definitions.

and uninstalling IBM Tivoli Workload Scheduler for Applications. “Installing. a list of projects appears in the Project Name field of the Copy Project From File window. After you specify the project folder.” on page 5. The name of the PeopleSoft project is ITWS.ini ITWS_PSXA. The Copy window is displayed showing a list of definition types.. Click OK d. See “Defining the configuration options” on page 75 for a detailed explanation. Tivoli Workload Scheduler installs the PeopleSoft project directories. upgrading. The project is contained in the TWShome/methods/PeopleSoft/PT844 subdirectories.XML 2.. Click Select All e. a confirmation window enquires if you want to replace the existing one. Click Report Filter b. Oracle v Database Name: database instance name v User ID: PeopleSoft operator name. a. 4. If you already configured ITWS_PSXA (perhaps after installing a fix pack). Click Yes. the PeopleSoft Database contains the following objects: v ITWS process type definitions v ITWS permissions list Chapter 10. perform the following steps: 1.” Uploading the PeopleSoft project This section describes how to upload a new PeopleSoft project related to PeopleTools 8.Configuring ITWS_PSXA PeopleSoft project v Leave the value of the TWSXA_INLINE_CI option set to ITWS_PROCESSREQUEST. for example. into the PeopleSoft database. 5. Start the Application Designer and from the sign-on window select to start the Application Designer in tier-two mode by entering the following information: v Connection Type: database used. Using the browser. as shown in the following structure: TWS_HOME\methods\ \---PeopleSoft \---PT844 \---ITWS_PSXA ITWS_PSXA. edit the full path to specify the folder where the project that you want to load is located. v Upload the PeopleSoft project as described in “Uploading the PeopleSoft project. or later. A progress bar appears After loading the project. PS v Password of user ID 3. Click Select All c. select Tools -> Copy Project-> From file. that is the default value.44. Choose ITWS_PSXA and click Open. After installing the product as described in Chapter 2. Click Options to select the new settings. for example. Mount the PT844 PeopleSoft project directory or copy it to the workstation from where you launch the Application Designer. Using the Application Designer. 6. Click Copy. Configuring the PeopleSoft access method 79 .

Select your PeopleTools server c. Select the Add a new value tab c. You can use either the PeopleSoft Web GUI or the Application Designer. customized for your database environment: INSERT INTO PS_SERVERCLASS SELECT o. You can use either the PeopleSoft Web GUI or the Application Designer. Select PeopleTools -> Process Scheduler -> Servers b.o. Select Process Scheduler Manager b. You can use either the PeopleSoft Web GUI or the Application Designer. Grant ITWS_ROLE authority to all users who want to schedule jobs from Tivoli Workload Scheduler. Follow the steps below: From the PeopleSoft Web GUI: a. edit the ITWS_ROLE window b. Select the Permissions list tab -> ITWS -> Save From the Application Designer GUI: a. Follow the steps below: From the menu of the PeopleSoft Web GUI: a. Follow the steps below: From the PeopleSoft Web GUI: a. the same task can be performed by the following sample statement.Configuring ITWS_PSXA PeopleSoft project v ITWS component interfaces 7.OPSYS. Using Maintain Security. Type or select ITWS_ROLE in the Role Name field d. Select: People tools -> Security -> Permission and Roles -> Roles b.SERVERNAME AND i.OPSYS=o.OPSYS=o.PRCSTYPE ) = 0 AND ( select count(*) from PS_PRCSTYPEDEFN a where a. Select the Roles tab d. edit the user name b. o. Add the ITWS_* Type definitions and save From the Application Designer GUI: a.’ITWS_’||o. Add the ITWS process type definitions to the required PeopleTools process scheduler.PRCSTYPE=’ITWS_’||o.OPSYS AND i. Add ITWS_ROLE and save 9. Add ITWS_ROLE and save From the Application Designer GUI: a. Select your PeopleTools server c. Select the Permissions list tab -> ITWS -> Save 8. Add the ITWS_* Type definitions and save Note: From the SQL interactive command line.PRCSTYPE=’ITWS_’||o.OPSYS ) > 0 10. Select the Roles tab c.MAXCONCURRENT FROM PS_SERVERCLASS o WHERE ( SELECT count(*) FROM PS_SERVERCLASS i WHERE i. Select: People tools -> Security -> User Profiles b. o. Restart the process servers.PRCSTYPE AND a.SERVERNAME.SERVERNAME=o.PRCSTYPE. Create the ITWS_ROLE security role. Type the user name of the user who wants to schedule jobs from Tivoli Workload Scheduler c. Using Maintain Security. 80 IBM Tivoli Workload Scheduler for Applications: User’s Guide .PRCSPRIORITY.

Configuring ITWS_PSXA PeopleSoft project You do not need to change the existing Tivoli Workload Scheduler job definitions.REPORT_ID.REPORT_ID convention.VARIABLE is the BUSINESS_UNIT. Configuring the PeopleSoft access method 81 . The following is an example of a job definition for the scheduling nVision process: -process ’NVSRUN’ -type nVision-Report -runcontrol AUS01. where the runcontrol ID must be specified using the BUSINESS_UNIT. Chapter 10. except for the scheduling nVision process.VARIABLE where NVSRUN is the process name and AUS01.

Configuring ITWS_PSXA PeopleSoft project 82 IBM Tivoli Workload Scheduler for Applications: User’s Guide .

“Defining extended agent jobs. The process type for the PeopleSoft job.” on page 53. if you are scheduling in an end-to-end environment. The process name for the PeopleSoft job. 2003. In this case the entire string following the JOBCMD keyword must be enclosed within double quotes. This entry must be enclosed within single quotes. if you use the Tivoli Workload Scheduler command line. Defining PeopleSoft jobs This chapter provides job definition information for jobs using the extended agent for PeopleSoft. The runcontrol ID for the PeopleSoft job. © Copyright IBM Corp. v As arguments of the JOBCMD keyword in the JOBREC statement in the SCRIPTLIB of Tivoli Workload Scheduler for z/OS. Task string parameters for PeopleSoft jobs This section describes the task string parameters that control the operation of PeopleSoft jobs. 2008 83 . Defining Peoplesoft jobs in Tivoli Workload Scheduler A Tivoli Workload Scheduler job definition is required for every PeopleSoft job you want to manage. if you use the Job Scheduling Console. A Tivoli Workload Scheduler job is associated to an already defined PeopleSoft job and its definition includes: v The name of the Tivoli Workload Scheduler job that runs the PeopleSoft job v The name of the extended agent workstation or workstation class where the Tivoli Workload Scheduler job runs v The name of the user launching the job v Recovery options v The Script file specifications For more information. The following is an example of a JOBREC statement: JOBREC JOBCMD("/-process process_name -type ’process_type’ -runcontrol runcontrol_ID") JOBUSR(TWS_user_name) | | | | | | | | | | | | | | | | | where: process_name process_type runcontrol_ID TWS_user_name The Tivoli Workload Scheduler for z/OS user who runs the psagent access method from the end-to-end scheduling environment. You must specify them in the following places when you define their associated Tivoli Workload Scheduler jobs: v In the Command field of the Task page of the Properties .Chapter 11. refer to Chapter 5.Job Definition panel. v As arguments of the scriptname keyword in the job definition statement.

The PeopleSoft process scheduler responsible for processing the PeopleSoft job. The process type for the PeopleSoft job. defaults are used. Table 23. The destination of the PeopleSoft job output. -outputformat The output format of the PeopleSoft job. Task string parameters for PeopleSoft jobs Parameter -process -type -runcontrol -outputdest -outputtype Description The process name for the PeopleSoft job.Task string parameters for PeopleSoft jobs Table 23 describes the parameters to define PeopleSoft jobs. In this case the PeopleSoft default value is used. some combinations of the value of this option with the value of the outputtype option are not supported. some combinations of the value of this option with the value of the outputformat option are not supported. and foldername). Valid values are: None PDF CSV PS DOC RPT Default RTF HP SPF HTM TXT LP WKS OTHER XLS Note: Depending on the PeopleSoft configuration. This entry must be enclosed within single quotes. Specify the trace setting for the job. Informational messages and warnings are also written in the trace file.” on page 247 for detailed information. Note: Depending on the PeopleSoft configuration. Note: No syntax checking is performed on the output control values (outputdest. “Configuring the tracing utility. Possible values are: v Any v Email v File v None v Printer v Web v Window If you do not specify any value. outputtype. The output type of the PeopleSoft job. Possible values are: 1 2 3 Only error messages are written in the trace file. -runlocationdescr -foldername tracelvl A most verbose debug output is written in the trace file. outputformat. This is the default. 84 IBM Tivoli Workload Scheduler for Applications: User’s Guide . In this case the PeopleSoft default value is used. The name of the report folder used for this job. The folder must have been already created using PeopleSoft Report Manager. Refer to Chapter 29. If the values are not recognized. The runcontrol ID for the PeopleSoft job. Tivoli Workload Scheduler uses the value associated to the PeopleSoft job you are submitting.

the distribution status. Table 24 shows the relationship between the run status.Task string parameters for PeopleSoft jobs The following is an example of a task string specification for a Peoplesoft 8. Chapter 11. and the Tivoli Workload Scheduler job status PeopleSoft job run status v Success (9) v Warning (17) v Success (9) v Warning (17) v Success (9) v Warning (17) PeopleSoft job distribution status v Posted (5) v None (0) v Not Posted (4) v Delete (6) v v v v Not Available (1) Processing (2) Generated (3) Posting (7) Tivoli Workload Scheduler job status SUCC ABEND EXEC v v v v v v v Cancel (1) Delete (2) Error (3) Canceled (8) No Success (10) Blocked (18) Restart (19) Any distribution status ABEND Table 25 on page 86 shows the relationship between the PeopleSoft run status and the Tivoli Workload Scheduler job status. The return code associated with the status is shown in parentheses. the distribution status monitors the status of the output of the job.Job Definition panel. Defining PeopleSoft jobs 85 . the run status monitors the running of the job until it reaches a final status. Table 24. In PeopleSoft.Job Definition panel. the distribution status. Tivoli Workload Scheduler uses this return code to evaluate the return code condition you specified in the Return Code Mapping Expression field of the Properties .44 job: -process XRFWIN -type ’SQR Report’ -runcontrol 1 -runlocationdescr PSNT Configuring the job status mapping policy Tivoli Workload Scheduler calculates the status of a Tivoli Workload Scheduler job based on the PeopleSoft job Run Status and Distribution Status. see “Task page” on page 56. Relationship between the run status. and the Tivoli Workload Scheduler job status. This is the default value. The return code associated with the status is shown in parentheses. see “Task page” on page 56. For more details about this field. Tivoli Workload Scheduler uses this return code to evaluate the return code condition you specified in the Return Code Mapping Expression field of the Properties . If the final status of a PeopleSoft job is neither success nor warning. 1 The distribution status is used and the Tivoli Workload Scheduler job status is calculated as shown in Table 24. If the final status of a PeopleSoft job is success or warning. For more details about this field. you can decide whether to use the distribution status of the PeopleSoft job when determining the status of the Tivoli Workload Scheduler job by setting the PS_DISTSTATUS option in the options file: 0 The distribution status is ignored and the Tivoli Workload Scheduler job status is calculated as shown in Table 25 on page 86. Tivoli Workload Scheduler ignores the distribution status and the Tivoli Workload Scheduler job status is ABEND.

the Tivoli Workload Scheduler job status is DONE. 86 IBM Tivoli Workload Scheduler for Applications: User’s Guide . Relationship between the run status and the Tivoli Workload Scheduler job status PeopleSoft final run status Cancel (1) Delete (2) Error (3) Hold (4) Queued (5) Initiated (6) Processing (7) Canceled (8) Success (9) No Success (10) Pending (16) Warning (17) Blocked (18) Restart (19) IBM Tivoli Workload Scheduler status ABEND ABEND ABEND WAIT WAIT INIT EXEC ABEND SUCC ABEND EXEC SUCC ABEND ABEND Note: If Tivoli Workload Scheduler fails to retrieve the status of the PeopleSoft job.Configuring job status mapping Table 25.

2008 87 . 2003.Part 4. SAP R/3 access method © Copyright IBM Corp.

88 IBM Tivoli Workload Scheduler for Applications: User’s Guide .

upgrading.40 unicode/non-unicode 7. Note 758829 resolves job step management problems. 352606. 4. 2.6D. 635095. 610480. 758829. 790615 602683. 399449. 6. 602683. 610480. Notes 357924 and 517672 are release-independent.00 unicode/non-unicode Notes: 1. 6. 758829 357924. Introducing Tivoli Workload Scheduler for Applications for SAP Using Tivoli Workload Scheduler for Applications for SAP. and control SAP jobs using the job scheduling features of Tivoli Workload Scheduler. or 7. InfoPackages are supported by Tivoli Workload Scheduler for Applications on SAP Business Warehouse systems 2. 610480. you can create. 758829. 604496. 6. 612564. 784446.0B.00. 604496. 1079601 602683. 612564.30.7. 602683. as shown in Table 27 on page 90. 2003. Note 399449 resolves print parameter issues. 517672. 784446. v The appropriate SAP R/3 Support Package. as shown in Table 26. 758829.20. 517672.Chapter 12. “Installing.7 unicode/non-unicode 6.10. 604496. you must have the following: v SAP R/3 version 4. 357924. Notes 602683. 1 1 Ensure that you have installed the required SAP Business Warehouse Support Package. SAP R/3 support packages SAP Versions 4. 399449.10 unicode/non-unicode | | | | | | | | | | | 6.6D SAP Notes 326752. 612564. 612564. Table 26. 604496. and uninstalling IBM Tivoli Workload Scheduler for Applications. 758829 602683. 435111. 635095. and 612564 are required if you want to use the BC-XBP 2. 453135. 435111. or later. 453135. 612564. 635095. 604496. 790615 602683.0 interface. schedule. Process chains are supported on SAP Business Warehouse systems 3. Software requirements In addition to the supported operating systems and prerequisite software listed in Chapter 2. 604496. 790615. 758829.30 unicode/non-unicode 6. or later. 1079601 862989 | 4.” on page 5.20 unicode/non-unicode 6.1 is required for the extended agent to be able to launch process chains. 784446. See Table 69 on page 257. 6.40. 2008 89 . 3.0B. 612564. The Support Package 9 (SAPKW31009) for SAP Business Warehouse Version 3. © Copyright IBM Corp. 604496.

786749. and 786412. Table 28. 795858. variants. 826878. and in a prescribed order Defining the national language support options Using the SAP Business Warehouse Support functions Customizing job execution return codes Using SAP logon groups for load balancing and fault-tolerance Using Business Component-eXternal Interface Background Processing (XBP 2. 1059049.00 SAP Notes 786748. 786748.40 with support package 04. 786749. for batch processing Exporting SAP factory calendars and adding their definitions to the Tivoli Workload Scheduler database 90 IBM Tivoli Workload Scheduler for Applications: User’s Guide .0) interface support to: Distributed environment U U U U U U U U U U U U U U End-to-end U v Collect v Track child intercepted jobs jobs v Keep all job v Track child attributes when jobs you rerun a job v Keep all job v Raise events attributes when you rerun a job v Raise events U U U Assigning an SAP job to a server group. and extended variants using the Tivoli Workload Scheduler interface Defining jobs and variants dynamically at run time Scheduling SAP jobs to run on specified days and times. 826878 826878. 1059049. and later For a list of functions and limitations about SAP R/3 server groups. 1130034 Server groups are supported by Tivoli Workload Scheduler for Applications on the following versions of SAP Basis: v 6.Software requirements 1 1 1 1 | 1 1 | | | | | | 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 Table 27. 1049735. 1100457. Tivoli Workload Scheduler for Applications for SAP features Feature Using Tivoli Workload Scheduler standard job dependencies and controls on SAP jobs Defining jobs. Features Table 28 shows the tasks you can perform with Tivoli Workload Scheduler for Applications for SAP either in a distributed or an end-to-end environment. refer to SAP Notes 612838.10 with support package 40 v 6. SAP Business Warehouse support packages SAP Business Warehouse Versions 3.20 with support package 41 v 6. 3. 795858.10 7.0B. 729317.50 3.

described in Chapter 14. It then monitors the job through to completion.Features 1 1 1 1 1 1 1 1 1 1 1 1 1 Table 28. to connect and launch jobs on an SAP instance. Roles and responsibilities in Tivoli Workload Scheduler for Applications for SAP User role Tivoli Workload Scheduler for Applications administrator User task v “Creating the IBM Tivoli Workload Scheduler RFC user” on page 95 v “Creating the authorization profile for the Tivoli Workload Scheduler user” on page 95 v “Copying the correction and transport files” on page 98 v “Importing ABAP/4 function modules into SAP R/3” on page 98 Chapter 12. Table 29 describes the roles and responsibilities of all users in the process model. or as a new instance Displaying the details of a job that submits a process chain Distributed environment U U U U End-to-end U U Scheduling process for the SAP extended agent Tivoli Workload Scheduler launches jobs in SAP using jobs defined to run on a Tivoli Workload Scheduler extended agent workstation. The access method uses information provided in an options file. The SAP extended agent workstation uses the access method r3batch to pass SAP job-specific information to predefined SAP instances. Introducing Tivoli Workload Scheduler for Applications for SAP 91 . | | | | | | | | | | | | | | | | Roles and responsibilities In a typical enterprise. writing job progress and status information to a job standard list on the host workstation. Using the SAP extended agent name as a key. “Configuring the SAP R/3 access method. For more information about job management. r3batch uses the corresponding options file to determine which instance of SAP will run the job.” on page 103. Multiple extended agent workstations can be defined to use the same host. showing the tasks they perform. refer to the IBM Tivoli Workload Scheduler Reference Guide. Tivoli Workload Scheduler for Applications for SAP features (continued) Feature Defining internetwork dependencies and event rules for Tivoli Workload Scheduler based on SAP events Defining event rules based on IDoc records Rerunning a job that submits a process chain from a specific process. by using multiple options entries or multiple options files. Table 29. different users contribute to the implementation and operation of the product. from failed processes. It makes a copy of a template job in SAP and marks it as able to run with a start time of start immediate. An SAP extended agent workstation is defined as a Tivoli Workload Scheduler workstation that is hosted by a fault-tolerant agent or master workstation which uses the r3batch access method.

“Defining event rules based on IDoc records. “Exporting SAP R/3 factory calendars.” on page 185 v Chapter 23. Roles and responsibilities in Tivoli Workload Scheduler for Applications for SAP (continued) User role Tivoli Workload Scheduler for Applications configurator User task v “Changing the Tivoli Workload Scheduler RFC user ID password” on page 101 v “Migrating from previous versions” on page 101 v “Print parameter and job class issues” on page 102 v “Defining the configuration options” on page 103 v “Connecting to the SAP system” on page 112 v “Defining user authorizations to manage SAP R/3 Business Warehouse InfoPackages and process chains” on page 164 v Chapter 19.” on page 173 v “Implementing job interception” on page 175 v Chapter 21.” on page 195 Tivoli Workload Scheduler for Applications operator v “Rerunning an SAP job” on page 137 v “Displaying details about a process chain job” on page 142 v “Mapping between Tivoli Workload Scheduler and SAP job states” on page 145 v “Raising an SAP event” on page 145 v “Killing an SAP job instance” on page 147 92 IBM Tivoli Workload Scheduler for Applications: User’s Guide . “Using the BDC Wait option. “Defining SAP jobs dynamically.” on page 149 v Chapter 22.” on page 181 v “Setting National Language support options” on page 203 Tivoli Workload Scheduler for Applications developer v “Defining a job that runs an SAP job” on page 115 v “Editing a standard SAP job” on page 128 v “Task string to define SAP jobs” on page 129 v “Displaying details about a standard SAP job” on page 141 v “Verifying the status of a standard SAP job” on page 144 v “Deleting a standard SAP job from the SAP database” on page 144 v “Balancing SAP workload using server groups” on page 144 v “Managing SAP R/3 Business Warehouse InfoPackages and process chains” on page 164 v Chapter 17.Scheduling process for the SAP extended agent | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1 1 | | | 1 1 | | | | | | Table 29. “Defining internetwork dependencies and event rules based on SAP R/3 events.

Unicode makes it possible to access and manipulate characters by unique numbers.4 must run on one of the following operating systems: – Microsoft Windows XP with SP1. Introducing Tivoli Workload Scheduler for Applications for SAP 93 . it uses UTF-16 when communicating with Unicode-enabled SAP R/3 systems. if a program has the code and the data to perform conversion between many subsets of traditional encodings. Since the early days of computer programming hundreds of encodings have been developed. Transferring text from one computer to another often causes some loss of information. each storing a single code point. with one or two 16-bit code units for each code point.Unicode support Unicode support Tivoli Workload Scheduler for Applications for SAP supports the Unicode standard. your system must meet the following conditions: v Tivoli Workload Scheduler for Applications for SAP version 8. The most widely used forms of Unicode are: v UTF-32. 32-bit version – Microsoft Windows 2003. each for small groups of languages and special purposes. 32-bit version – Microsoft Windows 2000. Because it communicates with SAP R/3 at the application server layer. Unicode support on r3batch Starting with R/3 version 4. and use older encodings only for input and output. if at all. The problem is that there is no single. to make it easier for Unicode to be used in applications and protocols. As a result. v UTF-8. input. It is the default encoding for Unicode. Unicode is used on all layers of the R/3 system: v UTF-8. sorting. v UTF-16. UTF-16. 32-bit version Chapter 12. with one to four 8-bit code units (bytes) for each code point. It is the most appropriate for encoding single characters. It is used mainly as a direct replacement for older MBCS (multiple byte character set) encodings. What is Unicode Unicode was devised to address the problem caused by the profusion of code sets. and storage depends on the knowledge of all the different types of character sets and their encodings. To use Unicode support. then it needs to hold several Megabytes of data. and a small number of machine-friendly encoding forms and schemes to fit the needs of existing applications and protocols. display. Also. the most widely used character sets. the interpretation of text. or to convert between external and internal encodings. Programs are written to either handle one single encoding at a time and switch between them. It is designed for best interoperability with both ASCII and ISO-8859-1. their Unicode code points. and UTF-32 on the database v UTF-16 on the application server and graphical user interface r3batch uses the UTF-8 code page internally. authoritative source of precise definitions of many of the encodings and their names. Unicode provides a single character set that covers the languages of the world.7 (R/3 Enterprise). with 32-bit code units.

94 IBM Tivoli Workload Scheduler for Applications: User’s Guide . 5. use at least version 1. 5.0 SuSE Linux Enterprise Server version 9. 64-bit versions: 11i v2. r3batch cannot support Unicode with earlier versions of the Job Scheduling Console.2. 64-bit versions 9. 10 HP-UX. If these conditions are not met. 11i v3 Red Hat Enterprise Linux Advanced Server versions 4. v If you are scheduling your jobs through the Job Scheduling Console. Use the options related to national language support described in “SAP R/3 supported code pages” on page 204. the Job Scheduling Console. and the target SAP R/3 system code page settings are aligned. you cannot use Unicode support and must make sure that r3batch.3.0.4 Sun Solaris Operating Environment. 5.0. v The SAP R/3 systems that communicate with r3batch must be running Unicode-enabled SAP R/3 versions.Unicode support on r3batch – – – – – IBM AIX. 64-bit versions: 5.3.0 The product does not support Unicode on the other operating systems where it can be installed. 10.

perform the following configuration steps in the SAP R/3 environment. or DIALOG. 4. Create the authorization profile as described in “Creating the authorization profile for the Tivoli Workload Scheduler user. depending on your version of SAP R/3. Tivoli Workload Scheduler requires this password to start or monitor SAP R/3 jobs. If this password changes in SAP R/3. v Using the Profile Generator (transaction PFCG). It does not modify any of the existing objects. 2003. you must create a user ID in SAP R/3 for Tivoli Workload Scheduler batch processing. Creating the authorization profile for the Tivoli Workload Scheduler user There are two alternative ways to perform this task: v Using transaction SU02 and manually creating the profile. 2. depending on the SAP R/3 release. Import the correction and transport files into SAP R/3 and verify the installation. Overview Here is an overview of the customization procedure: 1. use a new user ID rather than an existing one. © Copyright IBM Corp. Creating the IBM Tivoli Workload Scheduler RFC user For Tivoli Workload Scheduler to communicate with SAP R/3. Configuring the SAP R/3 environment To communicate and manage the running of jobs on SAP R/3 systems using the access method for SAP R/3.” 3. Note: The import procedure adds new ABAP/4 function modules and several new internal tables to the SAP R/3 system. Give this new RFC user ID the following attributes: v A user type of CPIC. 1. For security reasons. v The appropriate security profiles. Copy the correction and transport files from the Tivoli Workload Scheduler server to the SAP R/3 server. The steps described in this chapter require that you have knowledge of an SAP R/3 BASIS Administrator. 2.Chapter 13. v A password at least six characters in length. Create a new RFC user ID. 2008 95 . Communications. Create a new user ID for RFC communications in SAP R/3 for Tivoli Workload Scheduler. you must update the options file used by r3batch with the new password.

Click Create Role and write a description for the role. Select Authorizations. for example Z_TWS. and a description. Save the profile. 96 IBM Tivoli Workload Scheduler for Applications: User’s Guide . Save the user data. Go to the user maintenance panel and assign the profile to the Tivoli Workload Scheduler SAP R/3 user. 4. 2. Click Change Authorization Data. Manually add the authorizations according to the following table: Object S_ADMI_FCD S_BTCH_ADM S_BTCH_JOB Description System authorizations Background processing: Background administrator Background processing: Operations on background jobs Background processing: Background user name ABAP Workbench: full authorization to modify objects of type PROG ABAP: program run checks Authoritation. Write a profile name. in Role Name. 5. Depending on the version of SAP R/3. 4. check for RFC access CCMS: System Administration Spool: Actions Spool: Device authorizations Internal access authorizations for XMI log Authorization for external management interfaces (XMI) Authorization S_ADMI_ALL S_BTCH_ADM S_BTCH_ALL S_BTCH_NAM S_BTCH_ALL E_ABAP_ALL 1 1 1 S_DEVELOP S_PROGRAM S_RFC S_RZL_ADM S_SPO_ACT S_SPO_DEV S_XMI_LOG S_XMI_PROD S_ABAP_ALL S_RFC_ALL S_RZL_ALL S_SPO_ALL S_SPO_DEV_AL S_XMILOG_ADM S_XMI_ADMIN The authorizations are located in the ″Basis: Administration″ object class. Write a name. 2. Save the role. 3. 5. such as ″Role for the TWS user″.Using transaction SU02 and manually creating the profile Using Transaction SU02 and manually creating the profile Perform the following steps: 1. for example ZTWS. the authorization S_RFC_ALL might be located in the ″Cross-application Authorization objects″ or in the ″Non-application-specific Authorization Objects″ object class. 3. Using Transaction PFCG (Profile Generator) Perform the following steps: 1.

Manually add the following authorization objects: Object S_ADMI_FCD S_BTCH_ADM S_BTCH_JOB S_BTCH_NAM S_PROGRAM Description System authorizations Background processing: Background administrator Background processing: Operations on background jobs Background processing: Background user name ABAP: Program run checks ABAP Workbench: full authorization to modify objects of type PROG Authorization check for RFC access CCMS: System Administration Spool: Actions Spool: Device authorizations Internal access authorizations for XMI log Authorization for external management interfaces (XMI) 1 1 S_DEVELOP S_RFC S_RZL_ADM S_SPO_ACT S_SPO_DEV S_XMI_LOG S_XMI_PROD 8.Using Transaction PFCG (Profile Generator) 6. Fill in the values according to the following scheme: Object S_ADMI_FCD Description System authorizations v System administration function: Full authorization S_BTCH_ADM S_BTCH_JOB Background processing: Background administrator v Background administrator ID: Full authorization Background processing: Operations on background jobs v Job operations: Full authorization v Summary of jobs for a group: Full authorization S_BTCH_NAM Background processing: Background user name v Background user name for authorization check: Full authorization S_PROGRAM ABAP: Program run checks v User action ABAP/4 program: Full authorization v Authorization group ABAP/4 program: Full authorization S_RFC Authorization check for RFC access v Activity: Full authorization v Name of RFC to be protected: Full authorization v Type of RFC object to be protected: Full authorization S_RZL_ADM Activity: Full authorization Chapter 13. 7. select Templates. Configuring the SAP R/3 environment 97 . In the pop-up.

Generate a profile. activate. 1 1 1 Importing ABAP/4 function modules into SAP R/3 This section describes the procedure to generate.TV1 (data file) where x is a digit generated by the SAP system. Copy the control file and data file from the TWShome\methods directory to the following directories on your SAP R/3 database server: copy controlfile /usr/sap/trans/cofiles/ copy datafile /usr/sap/trans/data/ The names of controlfile and datafile vary from release to release.TV1 (control file) and R9006xx. 98 IBM Tivoli Workload Scheduler for Applications: User’s Guide .Using Transaction PFCG (Profile Generator) Object S_SPO_ACT Description Spool: Actions v Authorization field for spool actions: Full authorization v Value for authorization check: Full authorization S_SPO_DEV S_XMI_LOG S_XMI_PROD Spool: Device authorizations v Spool .TV1 (control file) and R000xxx. log onto your SAP R/3 system as an administrator. Copy these correction and transport files to the SAP R/3 server and import them into the SAP R/3 database.TV2 (data file) For SAP R/3 release 6.Company name: TIVOLI* v XMI logging . Save the role. Use the same name that you wrote in Role Name.TV1 (data file) v K900xxx. as follows: 1. 11. Save the authorizations. 13.TV1 (data file) v K9006xx.Program name: MAESTRO* v Interface ID: Full authorization 9. 2. Exit the authorization management panel and select User.TV2 (control file) and R900xxx.Long device names: Full authorization Internal access authorizations for XMI log v Access method for XMI log: Full authorization Authorization for external management interfaces (XMI) v XMI logging . Copying the correction and transport files The setup file loads four correction and transport files into the Tivoli Workload Scheduler home directory. Add the Tivoli Workload Scheduler user to the role. You do not modify any existing SAP R/3 system objects.TV1 (control file) and R9005xx. or later: v K9005xx.10: v K000xxx.10. On your SAP R/3 database server. 10. and commit new ABAP/4 function modules to your SAP R/3 system and several new internal tables. 12. The files are installed in the TWShome\methods directory and have the following file names and format: For SAP R/3 releases earlier than 6.

TV1 (function modules for IDoc monitoring) where x is a digit generated by the SAP system.Importing ABAP/4 modules into SAP R/3 1 1 1 1 1 1 1 1 1 1 The number of ABAP/4 modules that you install with the import process varies from release to release.TV1. or later: v K9005xx. Chapter 13. If there are errors.10 or later and you apply the standard transport and the IDOC transport. Configuring the SAP R/3 environment 99 . 42 modules are installed. If you are using SAP release 6. if the transport file in the TWShome\methods directory is named K900xxx. 4.TV1 (function modules for standard job scheduling extensions) v K900xxx. 20 modules are installed. Change to the following directory: cd /usr/sap/trans/bin 2.TV1 (function modules for standard job scheduling extensions) v K9006xx. Run the following command to import all the files in the buffer: tp import transport sid This command generates the new ABAP/4 modules and commits them to the SAP R/3 database. After running this command. or try using unconditional modes to do the import. Table 30 on page 100 lists the ABAP modules installed according to the SAP release. check the log files stored in the /usr/sap/trans/log directory to verify that the ABAP/4 modules were imported successfully. check with a person experienced in correction and transport.10.10: v K000xxx. For a list of the transport files to be used. If a problem is encountered. When the import is complete. Run the tp tst command to test the import: tp tst transport sid After running this command. The SAP R/3 system ID. They automatically become active. use unconditional mode when running this step: tp import transport sid U126 5. The number of ABAP/4 modules installed by the import process varies depending on the SAP release you are using. Warnings of severity level 4 are normal. 3. If you are using an SAP release earlier than 6. examine the log files in the /user/sap/trans/log directory for error messages. Warnings of severity level 4 are normal. examine the log files in the /user/sap/trans/log directory for error messages. 1 1 1 1 For example. refer to “Importing ABAP/4 function modules into SAP R/3” on page 98.TV2 (function modules for IDoc monitoring) For SAP R/3 release 6. To import ABAP/4 function modules into SAP R/3: 1. Add the transport file to the buffer: tp addtobuffer transport sid where: transport sid The transport request file. the transport request is tv1K900xxx.10. The modules are installed in the TWShome\methods directory and have the following file names and format: For SAP R/3 releases earlier than 6.

10 U U U U U U U U U U U U U U U U U U U U U U U U U U U U U U U U U U U U U U U U U U U U U U U U U U U U U SAP releases 6.10 or later U U U U 1 J_1O1_IDOC_SELECT J_1O1_JOB_ADJUST_CLIENT J_1O1_JOB_ABAP_STEP_MODIFY J_1O1_JOB_ADD_ABAP_STEP J_1O1_JOB_ADD_EXTPGM_STEP J_1O1_JOB_CLOSE J_1O1_JOB_COPY J_1O1_JOB_DEFINITION_GET J_1O1_JOB_DELETE J_1O1_JOB_EXTPGM_STEP_MODFY J_1O1_JOB_FIND J_1O1_JOB_FINDALL J_1O1_JOB_HAS_EXTENDED_VARIANT J_1O1_JOB_LOG J_1O1_JOB_LOG_READ J_1O1_JOB_OPEN J_1O1_JOB_START J_1O1_JOB_STATUS J_1O1_JOB_STATUS_CHECK J_1O1_JOB_STOP J_1O1_RAISE_EVENT J_1O1_REPORT_ALL_SELECTIONS J_1O1_REPORT_DYNSEL_GET_DEF J_1O1_REPORT_GET_TEXTPOOL J_1O1_TABLE_GET_NAMETAB J_1O1_VARIANT_COPY J_1O1_VARIANT_COPY_4X J_1O1_VARIANT_CREATE J_1O1_VARIANT_CREATE_NEW J_1O1_VARIANT_DELETE J_1O1_VARIANT_DELETE_NEW J_1O1_VARIANT_EXISTS J_1O1_VARIANT_GET_DEFINITION J_1O1_VARIANT_GET_DEF_NEW J_1O1_VARIANT_GET_HELP_VALUES J_1O1_VARIANT_INFO_GET J_1O1_VARIANT_MAINTAIN_CNT_TBL 100 IBM Tivoli Workload Scheduler for Applications: User’s Guide .Importing ABAP/4 modules into SAP R/3 Table 30. ABAP/4 modules ABAP/4 module J_1O1_BDC_STATUS J_1O1_DATE_TIME SAP releases earlier than 6.

log on as an administrator and start a DOS shell on the system where Tivoli Workload Scheduler is installed. After you have completed the imports as described in “Importing ABAP/4 function modules into SAP R/3” on page 98. the options file used by r3batch must be updated with this change. type: enigma newpwd where newpwd is the new password for the Tivoli Workload Scheduler RFC user ID. Generate an encrypted version of the new password using the enigma command in TWShome/methods. In Windows. which is located in the TWShome/methods directory. The encrypted password looks similar to: {3des}Hchwu6IsF5o= If the encrypted password is not entered correctly.Importing ABAP/4 modules into SAP R/3 Table 30. Copy the encrypted password into the options file.x uses the official SAP R/3 RFC interfaces for job scheduling. you can delete the following function modules from your SAP R/3 system: Chapter 13. If you had a previous installation of Tivoli Workload Scheduler extended agent for SAP R/3 on your system. and punctuation. The enigma command prints an encrypted version of the password. preserving uppercase. Tivoli Workload Scheduler is unable to start or monitor SAP R/3 batch jobs. In UNIX.1g to 4. Migrating from previous versions This version of the Tivoli Workload Scheduler extended agent for SAP R/3 supports all the SAP R/3 versions listed in Table 26 on page 89. Configuring the SAP R/3 environment 101 . The file can be edited with any text editor. The Tivoli Workload Scheduler extended agent for SAP R/3 version 4.5a To avoid conflicts with other vendors.10 U U U SAP releases 6. the Tivoli Workload Scheduler ABAP modules now belong to the Tivoli Workload Scheduler partner namespace J_1O1_xxx. as follows: 1. log on as root to the system where Tivoli Workload Scheduler is installed. These are: v The SXMI_XBP interface for SAP R/3 versions 3. lowercase. To do this in a command shell. the RFC J_1O1_xxx function modules are installed on your system. 2.10 or later U U Changing the Tivoli Workload Scheduler RFC user ID password If the password of the Tivoli Workload Scheduler RFC user ID is modified after the initial installation.0x v The BAPI_XBP interface since version 4. Ensure you copy the password exactly. ABAP/4 modules (continued) ABAP/4 module J_1O1_VARIANT_MAINTAIN_SEL_TBL J_1O1_VARIANT_MODIFY J_1O1_VARIANT_MODIFY_NEW SAP releases earlier than 6.

These limitations are no longer true with XBP 2. This is because of limitations in the RFC interfaces. 102 IBM Tivoli Workload Scheduler for Applications: User’s Guide . You can also delete the function group YMA3.x to 6.0.40 for job scheduling. Print parameter and job class issues The extended agent for SAP R/3 uses the official RFC interfaces of SAP R/3 versions 4. It is not necessary to delete the function modules and the function group. The same applies to the job class. When you migrate from previous versions of SAP R/3. install the appropriate SAP R/3 Support Package as stated in the SAP R/3 notes 399449 and 430087. but delete them if you want to clean up your system. Installing the SAP R/3 Support Package also resolves this issue. The following is a list of print parameters supported by BAPI XBP 1.Migrating from previous versions Z_MAE2_BDC_STATUS Z_MAE2_DATE_TIME Z_MAE2_JOB_COPY Z_MAE2_JOB_DELETE Z_MAE2_JOB_FIND Z_MAE2_JOB_FINDALL Z_MAE2_JOB_LOG Z_MAE2_JOB_OPEN Z_MAE2_JOB_START Z_MAE2_JOB_STATUS Z_MAE2_JOB_STOP These are old versions of the Tivoli ABAP functions.0 for SAP R/3 release 4. which belong to the customer name space. Official SAP R/3 interfaces only allow class C jobs. there can be problems with print parameters in jobs launched by Tivoli Workload Scheduler.6x and later: v output device v print immediately v delete after output v number of copies v archiving mode v authorization v selection cover page v sap cover page v spool retention period v recipient v lines v columns To resolve the loss of print parameters when copying a job.

The options files for the SAP access method are the following: r3batch. Defining the global options Table 31 lists the options that can be specified only in the global configuration file r3batch. Table 31. Note: WKSTNAME is the name of the extended agent workstation and must be written in uppercase characters. with the r3batch access method. Configuring the SAP R/3 access method This chapter provides detailed reference information about the Tivoli Workload Scheduler for Applications for SAP options and how to define them in the option files. Its options affect only the r3batch instance that is used by that particular workstation. 2008 103 .opts A configuration file that is specific to each Tivoli Workload Scheduler extended agent workstation that uses the r3batch access method. to define two extended agents named wkst1 and wkst2 that access two SAP systems. (Optional) The project ID for the job semaphore. For example. whose settings affect all the r3batch instances. it ignores the duplicate information contained in r3batch.Chapter 14. (Optional) Enables (ON) the SAP print parameter PRIMM (Print Immediately) for all jobs.opts v Local file WKST2_r3batch. It functions as a “global” configuration file. c a OFF OFF icp_sem_proj job_sem_proj | | | | primm_enable prnew_enable © Copyright IBM Corp.opts and in WKSTNAME_r3batch. It functions as a “local” configuration file. r3batch global configuration options Option Description Default | | | dep_sem_proj (Optional) The project ID for the external dependency d semaphore used for handling SAP R/3 background processing events as external follows dependencies.opts | | Note: If r3batch finds the local configuration file for an extended agent. (Optional) Enables (ON) the SAP print parameter PRNEW (New Spool Request) for all jobs. you must define the following three configuration files: v Global r3batch.opts v Local file WKST1_r3batch. WKSTNAME_r3batch.opts.opts A common configuration file for the r3batch access method. (Optional) The project ID for the job interception semaphore.opts. Defining the configuration options This section describes the options you can configure in r3batch. SAP1 and SAP2.opts. 2003.

you cannot use the options editor to modify these values. in the ASCII table. Tivoli Workload Scheduler for Applications for SAP uses two parameters: a path name and a project ID (which is a character value). It uses one semaphore for job-related tasks and another one for tasks related to variant maintenance. or its default value. Default OFF | | | | | | | | | prrel_enable prsap_enable OFF prunx_enable OFF var_sem_proj b | | | | | | | Modifying the default values of the semaphore options is particularly useful when the IDs that are generated would be the same as the IDs already used by other applications. dep_sem_proj It is reset to the third character that. The semaphore options must be edited directly in the global options file using a text editor. follows the value assigned to var_sem_proj. the communication partners must use the same identifier. var_sem_proj It is reset to the first character that. (Optional) Enables (ON) the SAP print parameter PRSAP (Print SAP Cover Page) for all jobs. Notes: 1. in the ASCII table.SAP global options Table 31. If these options are omitted. which work for most installations. To synchronize on the same semaphore. (Optional) The project ID for the variant semaphore. The project ID is taken from the options described in Table 31 on page 103. to resolve the problem of duplicated IDs. | | | | | | | | | | | | | 104 IBM Tivoli Workload Scheduler for Applications: User’s Guide . in the ASCII table. follows the value assigned to var_sem_proj. Tivoli Workload Scheduler for Applications for SAP uses system-5 semaphores to synchronize critical ABAP function module calls. follows the value assigned to var_sem_proj. (Optional) Enables (ON) the SAP print parameter PRUNX (Print Operating System Cover Page) for all jobs. The default value is OFF. On UNIX and Linux. The path name parameter is the fully qualified path to the options file. all the semaphore values are reset according to the following rule: job_sem_proj It keeps the value assigned. Tivoli Workload Scheduler for Applications for SAP uses default values. If two semaphore options are assigned the same value. r3batch global configuration options (continued) Option Description (Optional) Enables (ON) the SAP print parameter PRREL (Immediately delete the spool output after printing) for all jobs. There are several ways to choose this identifier. icp_sem_proj It is reset to the second character that. 2.

primm_enable prnew_enable prrel_enable prsap_enable prunx_enable (Optional) Enables (ON) the SAP print parameter PRIMM (Print Immediately) for all jobs. Ensure you enter the same password when creating this user in the SAP system. r3sid r3user (Mandatory) The SAP system ID. r3instance (Mandatory) The SAP instance number. (Optional) Enables (ON) the SAP print parameter PRREL (Print Release) for all jobs. (Mandatory) The SAP client number. It is sometimes also called the Maestro™ User ID. (Optional) Enables (ON) the SAP print parameter PRUNX (Print Operating System Cover Page) for all jobs. The default value is OFF. or the host name of the application server in all other cases. It must have the appropriate privileges for running background jobs. The default value is OFF. To retrieve the job duration from the SAP system. | | | | | | | | | | | | | | | | | | | | | job_duration r3client r3gateway r3group r3gwservice r3host | Chapter 14. this option is ignored. The default value is OFF. The value is case sensitive. (Optional) Enables (ON) the SAP print parameter PRNEW (New Spool Request) for all jobs.40 and 7. (Mandatory) The name of the SAP user with which the access method connects to the SAP system. Table 32. The default value is OFF.SAP local options Defining the local options Table 32 lists the options that you can specify only in the local configuration files. Configuring the SAP R/3 access method 105 . Default value is OFF. see “Creating the authorization profile for the Tivoli Workload Scheduler user” on page 95. The default value is OFF. r3batch local configuration options Option Description (Optional) Enables (ON) that the CPU time value in the production plan report that is run from the Tivoli Dynamic Workload Console is set to the actual duration of the SAP job. r3password (Mandatory) The password for the r3user. For information about how to encrypt the password see “Encrypting SAP R/3 user passwords” on page 111. (Optional) Enables (ON) the SAP print parameter PRSAP (Print SAP Cover Page) for all jobs. (Mandatory) The host name of the SAP message server when using logon groups. If r3group is set.00) For details about the authorization profile. use a string in the format /H/gateway/H/ for each of them. If this server can be reached through one or more SAP gateways. (Optional) The host name of the SAP gateway. (Optional) The name of the SAP logon group. ensure that the authorization profile contains the following authorization objects: v S_DEVELOP v S_TCODE with parameter SE38 (only for SAP 6. It can be a maximum of eight characters and is stored in encrypted format. (Optional) The service number of the SAP gateway.

For details about these options. Tivoli Workload Scheduler sets the job completion status as successful. If you disable or delete this option. (Optional) The ID of the user who runs the access method to retrieve job information. see Table 43 on page 186. For details about the -commit parameter. (Optional) Enables (ON) or disables (OFF) the product to retrieve only the most recent matching IDocs. evmon_interval ifuser (Optional) The polling rate (in seconds) that the r3evmon process applies to monitor the list of events. internetwork dependencies are committed immediately by default. For example. (Optional) The ID of the user who runs the access method to launch jobs (LJ tasks) and manage jobs (MJ tasks). Specify r3batch to enable the option. If you specify OFF. the -commit parameter set in the internetwork dependency definition is applied.SAP common options Defining the common options Table 33 lists additional options that you can specify in either configuration file. then only the most recent matching IDoc is retrieved. Table 33.cfg file to retrieve the date and time for the next monitoring loop. The allowed values are: n If at least n BDC sessions failed (where n is an integer greater than 0). (Optional) Enables (ON) or disables (OFF) the product to retrieve only IDoc data that is generated from the time when the monitoring process has started. you can use the Job Scheduling Console to define jobs. If you specify OFF. matching an event rule condition. ignore When all the BDC sessions complete. Tivoli Workload Scheduler sets the job completion status as failed. all matching IDocs are retrieved. see “Task string to define SAP jobs” on page 129. (Optional) Enables (ON) or disables (OFF) the product to commit internetwork dependencies after processing. according to a possible BDC processing failure. r3batch ON 60 None ON Default ignore 1 bdc_job_status_failed 1 1 1 1 1 1 1 1 1 1 1 1 1 | | | | | | | | | commit_dependency OFF 1 idoc_no_history 1 1 1 1 1 1 1 1 idoc_shallow_result 1 1 1 1 1 1 1 ljuser None 106 IBM Tivoli Workload Scheduler for Applications: User’s Guide . r3evmon uses the XAname_r3idocmon. all If all the BDC sessions failed. r3batch common configuration options Option Description (Optional) How Tivoli Workload Scheduler sets the completion status of a job running BDC sessions. occurs more than once in the sequence of statuses. and any other value to disable it. suppose you set idoc_shallow_result=ON. regardless of their status. Note: This option is ignored if you defined the job by setting the nobdc or nobdcwait option. jobdef (Optional) If enabled. When processing this option. If the status of an IDoc changes several times during the monitoring interval and the same status. Tivoli Workload Scheduler sets the job completion status as failed. all matching IDocs are retrieved. If you enable this option. This is the default. in addition to the command line. included those that were generated before the monitoring process started.

refer to “Rerunning a process chain job” on page 138. r3batch common configuration options (continued) Option log_r3syslog Description Default (Optional) Enables (ON) or disables (OFF) the access method to write OFF the latest entries from the SAP syslog to its trace file when an RFC returns with a general error. (Optional) The maximum value of the variant name counter. For details about rerunning a process chain job. between status checks. it starts again from 0. See also short_interval. nojobdefs (Optional) Disables (1) or enables (0) the definition of new SAP jobs using the Job Scheduling Console GUI. If the N0 counter reaches the specified value.1 40 job name_counter_policy (Optional) The name counter policy: step job The name counter is increased once for every step. even though the function module BAPI_XBP_JOB_COPY is present on the SAP system. 0 oldcopy 0 1 pchain_recover 1 1 1 1 1 1 1 1 1 pchain_details 1 1 pchainlog_bapi_msg rerun OFF (Optional) Enables (ON) or disables (OFF) the product to retrieve ON additional messages from the BAPI calls from the SAP Business Warehouse process chains and appends them to the stdlist of Tivoli Workload Scheduler. it starts again from 0. It cannot be greater than 3600 seconds. If this option is set to 1. (Optional) The maximum interval. you must create the job definitions in the SAP job before creating the Tivoli Workload Scheduler for Applications job that is going to schedule them. (Optional) The N0 counter policy: step job The N0 counter is increased once for every step. (Optional) The action taken by Tivoli Workload Scheduler when you rerun a job that submits a process chain. The allowed values are: rerun Tivoli Workload Scheduler creates another process chain instance and submits it to be run again. (Optional) Enables (1) or disables (0) the access method to use the old way of copying jobs. Configuring the SAP R/3 access method 107 . job 3600 long_interval max_n0_counter max_name_counter n0_counter_policy 2^15 . Chapter 14.SAP common options Table 33. The N0 counter is increased once for every job. The name counter is increased once for every job. in seconds. (Optional) Enables (ON) or disables (OFF) the display of details about an SAP process chain that you scheduled as a Tivoli Workload Scheduler job. (Optional) The maximum value of the N0 counter. restart Tivoli Workload Scheduler restarts the original process chain from the failing processes to the end. If the name counter reaches the specified value.

r3batch common configuration options (continued) Option pchainlog_level Description (Optional) Supplements the option retrieve_pchainlog. the default BTCTEST is used. the default is complete. chains_and_failed_proc In addition to the process chains. because of problems in the implementation of the QoS service. and leave retrieve_pchainlog set to ON. Specifies which type of process chain logs you want to retrieve. global nor local option. r3auditlevel rcmap (Optional) The audit level for the XBP. you can activate this feature by using the INITXBP2 ABAP report. if you indicate 2 only the first two levels are logged. (Optional) Enables (ON) or disables (OFF) the Return Code mapping capabilities of Tivoli Workload Scheduler for Applications for SAP. Note: You can use this option only if you activated the parent-child feature on the SAP system. If you omit this option. neither as to monitor an SAP event defined as external dependency. For example. ON OFF 108 IBM Tivoli Workload Scheduler for Applications: User’s Guide .0 SAP system. level_number Process chains are logged down to the level of chain you indicate here. Note: This option affects the entire process chain. | | | | | placeholder_abap_step (Optional) If XBP version 2. pc_launch_child (Optional) Enables (ON) or disables (OFF) the product to launch OFF child jobs that are in scheduled state. Without this option. A number from 0 (low) to 3 3 (high). logs all failed processes. the connection between r3batch and the SAP RFC library does not work. Specifies which level of process chain logs you want to retrieve. verbosity cannot be reduced for individual processes.SAP common options Table 33. Permitted values are: 1 Only the first level of process chain is logged. qos_disable (Optional) Enables (ON) or disables (OFF) the creation of the environment variable QOS_DISABLE on Microsoft Windows systems that use the Quality of Service (QoS) feature. (Optional) Supplements the option retrieve_pchainlog.0 is used. before r3batch opens an RFC connection. On the XBP 2. and leave retrieve_pchainlog set to ON. the name of the ABAP report If this option is not used as the dummy step in the SAP placeholder job that is created specified. all pchainlog_verbosity All process chains are logged. the default is level 1. Permitted values are: chains_only Logs only the process chains. complete Logs all process chains and processes. Default If you omit this option.

Notes: 1. use this option with the pchainlog_level and pchainlog_verbosity options. See also long_interval. Allowed values are in the range from 0 to 9999. r3batch common configuration options (continued) Option retrieve_joblog Description (Optional) Enables (ON) or disables (OFF) the retrieval and appending of the SAP job logs to the stdlist of Tivoli Workload Scheduler. Specify an integer greater than 0 to limit the number of retries. This option on its own retrieves the log of only the first level of a process chain. (Optional) Enables (ON) or disables (OFF) the retrieval and appending of the SAP BW process chain logs to the stdlist of Tivoli Workload Scheduler. 2. The retrieval and appending of job logs to the stdlist might be time-consuming for jobs that produce large logs. The retrieval and appending of SAP job spool lists to the stdlist might be time-consuming for jobs that produce large spool lists. Specify an integer greater than 0. 5 1800 5 ON ON Default ON retrieve_pchainlog 1 rfc_timeout 1 1 short_interval 600 10 Chapter 14. Configuring the SAP R/3 access method 109 . you also disable the return code mapping function for the log entries. To retrieve more complete logs. 0 means no timeout. you also disable the return code mapping function for the spool list entries. 3. retry rfc_open_delay rfc_open_retry (Optional) The retry count for SAP function module calls. It cannot be less than 10 seconds. between status checks. retrieve_ipaklog (Optional) Enables (ON) or disables (OFF) the retrieval and ON appending of the SAP BW InfoPackage logs to the stdlist of Tivoli Workload Scheduler. 2. (Optional) The retry count for opening an RFC connection to the SAP system. This option does not affect the BDC Wait feature. (Optional) The time (in seconds) that r3batch waits before cancelling a non-responding RFC communication. 2. or -1 for an unlimited number of retries. Notes: 1.SAP common options Table 33. you also disable the return code mapping function for the log entries. retrieve_spoollist (Optional) Enables (ON) or disables (OFF) the retrieval and appending of the SAP job spool lists to the stdlist of Tivoli Workload Scheduler. Notes: 1. (Optional) The maximum number of seconds to wait between two consecutive calls before opening an RFC connection. If you disable the retrieval of the SAP job spool lists. in seconds. Note: The retrieval and appending of SAP BW InfoPackage job logs to the stdlist might be time-consuming for jobs that produce large logs. The retrieval and appending of SAP BW process chain logs to the stdlist might be time-consuming for jobs that produce large logs. 3. If you disable the retrieval of the job logs. (Optional) The minimum interval. If you disable the retrieval of the SAP BW process chain logs.

refer to the SAP Note 977462. This value overwrites the XBP version automatically determined during RFC logon. The default value is 0. This option must be consistent with twsmeth_cp. and JA can be set from the Option Editor. EN. | | | | | | | | | twsxa_cp (Optional) The encoding used by r3batch to establish RFC connections with SAP systems. r3batch common configuration options (continued) Option twsmeth_cp Description (Optional) The code page that r3batch uses to write its output. The language of the locale of the workstation that hosts the r3batch access method. Specify an integer value. This option must be consistent with twsmeth_lang. Possible values are: v 1100 v 1103 v 8000 v 8300 v 8400 twsxa_lang (Optional) The language used to log in to SAP systems. Default The code page used by the Tivoli Workload Scheduler workstation that hosts the r3batch access method.0 and SAP Netweaver 2004s with SP9. EN | | | | | | | | | | | | | | utf8cmdline (Optional) Enables (1) or disables (0) the encoding of extended parameters in UTF-8 format. 1100 twsmeth_lang (Optional) The language used to report messages.SAP common options Table 33. The XBP version determined by r3batch during RFC logon from the SAP system. xbpversion (Optional) The XBP version used on the target SAP system. Note: If you have both global and local options files and you want to change the default value for utf8cmdline. The other languages can be set using any text editor. modify the local options file because this overrides the global options. It can be any of the existing TIS codepages. Use this option if r3batch is not Unicode-enabled. Specify one of the following: DE German EN English ES Spanish FR French IT Italian JA Japanese KO Korean pt_BR Brazilian Portuguese zh_CN Simplified Chinese zh_TW Traditional Chinese DE. 110 IBM Tivoli Workload Scheduler for Applications: User’s Guide . Note: For details about XBP 3.

pwdcrypt..com r3instance=00 r3password={3des}Hchwu6IsF5o= r3sid=GS7 r3user=twstest long_interval=120 r3auditlevel=3 short_interval=10 twsxa_lang=EN Encrypting SAP R/3 user passwords When you add your entries in the options file. enter the following command: enigma [password] You can include the password on the command line or enter it in response to a prompt. You can put a local option in the global configuration file if you need to give the same option to all the r3batch instances.tivlab. The program returns an encrypted version that you can then enter in the options file. JobDef. so you do not need to encrypt the password again. only has effect in the global configuration file. with no blanks before the option. and LogFileName options in r3batch.raleigh.opts configuration file is the following: option1=value1 option2=value2 option3=value3 . or before or after the equals (=) character. IFuser. Chapter 14. you can place the r3user option in the global file without duplicating that information in all the local configuration files.4. | | | | | | | With Tivoli Workload Scheduler for Applications version 8. wkst1_r3batch. or the Option Editor the password is encrypted by applying this new algorithm. When you use enigma. although your options file might be different. such as the LJuser. while you can put tailored data for the target SAP system of the extended agent (for example. To run the encryption program.opts). you must run the enigma program to encrypt the password before writing it in the file. The old password encryption is still recognized and processed by Tivoli Workload Scheduler for Applications 8. For example. Configuration options usage The format of the CPUname_r3batch.. like job_sem_proj. It is also applied if you open and save the options file with the Option Editor. If you put global options in a local file they have no effect.opts. r3client=100 r3host=/H/amsaix64.SAP common options SAP R/3 option file example Below is an example of an options file for SAP. You can put all the common information. the password value is automatically encrypted before it is written in the file. after the value. A global option. SAP1) in a local configuration file (for example. a new algorithm is applied to encrypt the password that is stored in the options file. If you modify the file with a text editor.ibm. It can help you determine your specific site requirements. if the SAP user name is the same in all your SAP systems.4. Configuring the SAP R/3 access method 111 .

if both the global and the local configuration files contain the r3user option. and r3host in the local one. the SAP RFC library supports SAP routers.raleigh. Connecting to a specific application server In its basic form.com Moreover. it is recommended to use simple host names. which are placed at the boundaries of the sub-networks and act as proxies. modern companies use more complex network topologies. you can use the IP address. Alternatively.Configuration options usage r3batch reads the global configuration file first and then the local file.tivlab. the connection string is a composite of basic connection strings for each SAP router. Note: These configuration files are not created during the installation process. to prevent unauthorized access.raleigh. r3batch uses the one in the local file.tivlab. the basic connection string for the SAP router is followed by /P/ and the password of the router. For example. To support this type of network. 112 IBM Tivoli Workload Scheduler for Applications: User’s Guide . This is a real limitation in complex network environments. r3client. For this type of network. for example: /H/hemlock. for example: /H/litespeed/H/amsaix33/H/hemlock. There are six mandatory options that r3batch requires: v r3client v r3host v r3instance v r3password v r3sid v r3user You can put them all in the local configuration file or you can spread them between the global and the local files. which cannot communicate directly through TCP/IP. you could place r3user and r3password in the global configuration file and r3sid. because it is difficult to maintain. with a number of small sub-networks. a connection string consists of the host name (or IP name) of an SAP application server. Connecting to the SAP system Tivoli Workload Scheduler for Applications for SAP uses the SAP remote connection call (RFC) library to connect to the SAP system. In this case. The connection address for an SAP system is denoted as a connection string.ibm.com This type of connection string works only in very simple network environments. It must be placed either in the global configuration file or the local configuration file. Note: The SAP RFC library limits the length of the connection string to a maximum of 128 characters. Every option (except the global options) contained in the local configuration file will override those in the global file. followed by the basic connection string for the target SAP system. The r3user option is both local and mandatory. Usually. r3instance. As a workaround. but this is not recommended. you can secure the SAP routers with passwords. without the domain name whenever possible. where all application servers can be reached directly through TCP/IP. For example.ibm.

de r3group=PUBLIC r3sid=QB6 The hostname of the message server. The SAP instance number. the application servers are usually configured in logon groups for load balancing and fault-tolerance purposes. called the message server. basic and composite.sap-ag. Chapter 14. Connecting to a logon group In large SAP installations.Connecting to a specific application server Tivoli Workload Scheduler for Applications for SAP supports both types of connection strings. Set the following options to configure r3batch to connect to a logon group: r3host r3group r3sid For example: r3host=pwdf0647. The message server automatically assigns users to the application server with the least workload of the logon group it controls. where: r3host r3instance r3sid For example: r3host=/H/litespeed/H/amsaix33/H/hemlock.ibm. The name of the logon group.raleigh. Load balancing is done by a dedicated server. Configuring the SAP R/3 access method 113 .wdf.tivlab. The SAP system ID.com r3instance=00 r3sid=TV1 The connection string. The SAP system ID.

Logon groups 114 IBM Tivoli Workload Scheduler for Applications: User’s Guide .

The Properties . select New Job Definition. you must define the following: Jobs in SAP that you want to run under Tivoli Workload Scheduler control You can define these jobs using standard SAP tools. To define a job that runs an SAP job. perform the following steps: 1. © Copyright IBM Corp. Managing the running of SAP jobs This chapter describes how to perform the following tasks: v “Defining a job that runs an SAP job” v “Editing a standard SAP job” on page 128 v “Task string to define SAP jobs” on page 129 v “Rerunning an SAP job” on page 137 To manage the running of jobs on an SAP workstation from Tivoli Workload Scheduler. The SAP job can: v Already exist in the SAP system and be identified using the information defined in the SAP Job Identity group on page 119 v Be created directly by clicking New in the Task page on page 119. or the Tivoli Dynamic Workload Console. you can define a Tivoli Workload Scheduler job that runs an SAP job. the SAP-specific panels of the Job Scheduling Console. In the Actions list of the Job Scheduling Console main window.Job Definition panel is displayed. 2008 115 . 2.Chapter 15. Defining a job that runs an SAP job Using the Job Scheduling Console. 2003. Select an engine. Jobs in Tivoli Workload Scheduler that correspond to the jobs in SAP The Tivoli Workload Scheduler job definitions are used in scheduling and defining dependencies. but the SAP jobs are actually run.

Name Type the name of the Tivoli Workload Scheduler job that runs the SAP job whose name you provide in the Job Name field of the Task page. dashes. The page consists of the following: v Information group: Task Type Select SAP.) to display a list of SAP workstations.Defining a job that runs SAP job Figure 9. The name must start with a letter. 116 IBM Tivoli Workload Scheduler for Applications: User’s Guide .. The General page of the Properties . and can contain alphanumeric characters. and underscores. The maximum length is 40 characters.. Workstation Name Type the name of the SAP workstation where the Tivoli Workload Scheduler job runs or use ellipsis (.Job Definition panel The panel consists of the following: v “General page” v “Task page” on page 118 General page Use the General page to provide general information about the new job definition.

If a job ended in error. Workstation Name Displays the name of the workstation where the recovery job runs. Job Click ellipsis (. Possible values are: – Stop. – If the recovery job workstation is a fault-tolerant agent. The recovery prompt is an ad hoc prompt. v Recovery Options group: Select the recovery option you want to associate with the job if it ends in error. the prompt status is Asked and the message is displayed. Continue with the next job. – Rerun. The name is entered automatically when you select a recovery job. the status is Not Asked. The text can contain up to 64 characters. Rerun the job. If a job ended successfully. The maximum length is 47 characters. Follow these guidelines: – If either workstation is an extended agent. v Login group: Login Type the name of the user who launches the job. Message Type the text of a recovery prompt to be displayed if the job ends in error. it must run in Full Status mode. Chapter 15. Managing the running of SAP jobs 117 . Do not continue with the next job. Specify a user that can log on to the workstation where the job runs. Add Parameter Adds a parameter to the login field. The Status of All Prompts shows all recovery prompts.General page Description Type a description of the job. Not all jobs are eligible to have recovery jobs run on a different workstation...) to display a list of recovery jobs from which to select the recovery job to run if the job you are defining ends in error. The maximum length is 120 characters. This is the default value. – The recovery job workstation must be in the same domain as the parent job workstation. For more information. – Continue. see Tivoli Workload Scheduler: Job Scheduling Console User’s Guide. Recovery jobs are run only once for each instance of the job. it must be hosted by a domain manager or a fault-tolerant agent that runs in Full Status mode.

Task page Task page Use the Task page to provide task information for the SAP job that is run by the Tivoli Workload Scheduler job defined in the General page.Job Definition panel The page consists of the following: v Task Type group: 118 IBM Tivoli Workload Scheduler for Applications: User’s Guide . This page is not available until a workstation has been specified in the General page. Figure 10. The Task page of the Properties .

Disable BDC Wait Select to disable the BDC Wait option for the job. If you specified a value for a parameter both using the GUI field and the R3 command line. such as -client 500 -exec_client 500 -s 1 -s1 program=BTCTEST -s1 type=a -flag type=exec. Ensure you delete the trace option from the job after you have performed debug procedures.” on page 173. refer to Chapter 19. v Job Options group: Job Spoolist Select to retrieve the spool list in the job log. as shown in Figure 11 on page 121. Launch Job Immediately Select to launch the SAP job immediately. If you select blank. “Using the BDC Wait option. The default value is displayed when the creation is completed. Possible values are: – Blank.. Job Action Click New to create a standard SAP job in the SAP database.Task page This information field indicates that the job is SAP task type. User Name Type the name of an SAP user. Managing the running of SAP jobs 119 . the value used is enabled. The task type depends on the SAP system where you defined the job. v R/3 Job Type group: R/3 Job Type Select Standard R/3 job. v Debug and Setting Options group: Trace Select to create a trace file dev_rfc in the Tivoli Workload Scheduler home directory. The default value is the value of the r3user option contained in the WKSTNAME_r3batch. For details. Debug Select to include additional debug information in the stdlist file of the job. v R/3 Job Identity group: Job Name Type the name of the SAP jobs.opts file.. You cannot create on the SAP system database either the Business Warehouse InfoPackage or the Business Warehouse Process Chain job type using the Job Scheduling Console. the product uses the value specified on the command line. See Table 35 on page 131 to know which flags are supported by the GUI and which flags are supported by the command line. If you did not define the retrieve_spoollist option. Tivoli Workload Scheduler uses the value you set for the retrieve_spoollist option. v R3 Command Line group: R3 Command Line Type any flags that are valid for the SAP command line. The SAP Job Definition panel is displayed.) to display a list of SAP job already defined in the SAP system whose status is scheduled. Click ellipsis (. Job ID Displays the job identifier assigned by the SAP system when the creation is completed. The dev_rfc file can become very large and cause problems to your system. – Enabled Chapter 15.

<. Complete the information as described in the following sections: v “R/3 Job page” on page 121 v “Steps” on page 122 120 IBM Tivoli Workload Scheduler for Applications: User’s Guide . If you select blank. – Enabled – Disabled Job Log Select to retrieve the job log. Allowed operators are comparison operators (=. Possible values are: – Blank. OR. Tivoli Workload Scheduler uses the value you set for the retrieve_spoollist option. >. Possible values are: Blank Low priority. != or <>. – Enabled – Disabled Job Class Displays the class assigned to the job in the Job Class field in the R/3 Job page. For example. This represents the priority with which the job runs in the SAP system. This is the default value. >=. <=) and logical operators (AND. A High priority B Medium priority C Low priority v Return Code Mapping group: Expression Type a logical expression that defines the success condition.Task page – Disabled | | | | | PChain Log (for job process chain only) Select it to retrieve the job process chain log. Possible values are: – Blank. NOT). the expression RC>= 6 indicates that a return code greater than or equal to 6 means the task is successful. the value used is enabled. If you did not define the retrieve_joblog option.

A High priority B Medium priority C Low priority Displays the identifier of the event defined in the SAP system. This represents the priority with which the job runs in the SAP system. This is the default value.Task page R/3 Job page Use the R/3 Job page to define or modify the native SAP job to run under the control of Tivoli Workload Scheduler (as a task of the job you specified in the General tab). Possible values are: Blank Low priority. The SAP Job Definition panel The page consists of the following: Job Name Job Class Type the name of the SAP job. Figure 11. Type the class of the SAP job. Event ID Event Parameter Displays the parameter of the event defined in the SAP system. Chapter 15. Managing the running of SAP jobs 121 .

The name has the format hostname_SAPsystemname_SAPsystemnumber. or external commands for the SAP job.10 with SP 40 (for more details. balancing the workload among the various application servers. To display a list of available SAP server groups. If you specify a server group. the SAP system runs it on an application server that belongs to that group. you cannot set a server group.Task page Client Displays the value indicated in the R3Client option of the workstation_r3batch.). Target Host | | | | | | | | | | | Steps Use the Steps page to define one or more ABAPs. you cannot set a target host.opts option file. If you specify a target host. This means that when the job is launched. as for example amss80a0_gs7_90. The field is case sensitive. Type the name of the SAP workstation where the job is to run. refer to “Balancing SAP workload using server groups” on page 144). Server Group Type the name of the SAP server group to assign to the job. This field is available from SAP Basis version 6.. 122 IBM Tivoli Workload Scheduler for Applications: User’s Guide . This field is filled when the job creation completes.. click ellipsis (. external programs.

) to display a list of external commands. Possible values are: – ABAP – External programs – External commands The name of the SAP step. If you are creating an ABAP jobs type its name or use ellipsis (. Managing the running of SAP jobs Name 123 ..) to display a list of ABAP job.Task page Figure 12. use ellipsis (.. If you are creating an external program. The Steps page of the SAP Job Definition panel The page consists of the following: v Common Value group: Type Specify the type of programs contained in the job.. Chapter 15. If you are creating an external command.. type its name.

Type any variants or parameters for the step. Type the SAP target host workstation for this step. Click ellipsis (. Print Formatting Specify the page format of the output.Task page User Var / Parm The name of the SAP user who launches the step. Spool Data Set Type the spool Data Set name. or change a variant. Name Spool Request Type the name of the spool request. Print Parameters Flags Click Print Parameter Flags to set the flags for the print parameters. Not all ABAPs require variants and not all external programs and external commands require parameters.. List Lines Type the number of list lines.) to display a list. Set this only if you do not want to print immediately. Only users with this authorization can view the contents of the request. Recipient Type the recipient name for the SAP cover sheet. Authorization Type the authorization for the spool request. Columns Type the number of characters per list line. and parameters are used with external programs and external commands. This option is applicable to external programs and external commands. Use this list to select. you can set different formats with different maximum page length and width values in this field. See “Managing SAP variants using the Job Scheduling Console” on page 126 for details. Department Specify the department name for the SAP cover sheet. 124 IBM Tivoli Workload Scheduler for Applications: User’s Guide . Depending on the printer connected.. Output Device Type the name of the printer or fax.. The default value is 1. This text appears on the standard cover page. Click ellipsis (.) to display a list of variants associated with the ABAP. Text Cover Page Type the description text of the spool request.. Variants are used with ABAP modules. v Print Parameters group (for ABAP programs only): Target Host Number of Copies Type the number of copies you want to print. create.

Does not use any cover page.0. SAP Cover Page Specify the SAP cover page. v Control Flags group (for external programs only): Job to wait for Ext Program to End Select it to run the SAP job when the external program ends. 'D' Prints the default host cover page. 'D' Prints the default host cover page. Delete After Printing Select it to delete the print job after printing. Chapter 15. Print Immediately Select it to print the job immediately.0. Host Spool Cover Page Type the value to associate to the cover page of the host spool. The default value is 8. This field is available for jobs created using SAP BC-XBP 2. Spool Retention Period Specify how long the spool is retained after printing. Possible values are: '' Blank.0. The Print Parameter Flags panel Archiving Mode Displays the archive mode for the print parameters.Task page Figure 13. This field is available for jobs created using SAP BC-XBP 2. This field is available for jobs created using SAP BC-XBP 2. Does not use any cover page. 'X' Prints the host cover page. Spool Request Priority Specify the priority for the print. Managing the running of SAP jobs 125 . 'X' Prints the host cover page. Selection Cover Page Select it to select a cover page for the print job. New Spool List Select it to create a new spool list for the print job. Possible values are: '' Blank.

” To display information on an existing variant. Delete To delete a variant. In the step page of the SAP Job Definition panel.. Figure 14.. Creating or editing a variant This section describes how to create or edit a variant. To modify information on an existing variant as described in “Creating or editing a variant. click the Var/Parm (. you can perform the following actions: Set Refresh To refresh the content of the variant list with the information contained in the SAP database. The Variant List panel 2.” To associate the value chosen from the list to the ABAP.) ellipsis. Activate Trace Select it to activate the traces.Task page Output Joblog Select it to log the output of the job in the SAP system. Managing SAP variants using the Job Scheduling Console This section describes how to manage variants using the Tivoli Job Scheduling Console: 1. The Variant List panel is displayed listing all the variants associated with the ABAP specified in the Name field. New View Edit To create a new variant as described in “Creating or editing a variant. To create or edit a variant perform the following steps: 126 IBM Tivoli Workload Scheduler for Applications: User’s Guide . Error Output Joblog Select it to log all the external errors in the SAP system. From this panel.

the fields and selections are not empty. In the Variant List panel. If you are editing an existing variant. you can use placeholders and counters that eliminate the error-prone task of adjusting values and therefore minimize the effort for variant maintenance. Placeholders and counters for extended variants Symbol $S $D $_D Meaning Timestamp Day of the month Date Syntax YYYYMMDDHHMM DD YYYYMMDD Chapter 15. The panel consists of the following pages: v Variant Information: a. Enter or modify the variant name and description. The Variant Information page of the Variant List panel 2. Figure 15. counter becomes available. b. A Variant Frame panel similar to that shown in Figure 15 is displayed. click New or Edit. Supported placeholders and counters are: Table 34. Managing the running of SAP jobs 127 . check a Properties box: Background The variant can only be used in background processing. For extended variants.Managing SAP variants using the Job Scheduling Console 1. Protected The variant is protected against being changed by other users. Placeholders and counters are preprocessed by Tivoli Workload Scheduler and the values are automatically adjusted when the job is launched. If you check this box. Extended Allows for the use of placeholders and counters as variant values. Optionally. Invisible The variant will not be displayed in the F4 value list in the SAP GUI.

The panel consists of the following: v “General page” on page 116. 5. 4. 2.$N9 ($N = $N0) Like the datecalc command. The SAP Job definition panel is displayed. Double-click the SAP job you want to edit. Modify the information described on the following pages as appropriate: v “R/3 Job page” on page 121.Job Definition panel is displayed. −. v “Task page” on page 118. 6. v Variant Values: In the Variant Values page. *. In the Work with engines pane. In the Steps page.Job Definition dialog is displayed. Arithmetic expressions allowing for +. select an engine → database list → job definition list. For each step you add or delete. click the Modify Step icon. the Job ID in the Task page is automatically replaced with the one associated to the new job name. To modify the SAP job information in the SAP database. The Properties . Placeholders and counters for extended variants (continued) Symbol $M $Y $_Y $H $T $_T $Nx $(date expression) $[arithmetic expression] Meaning Month Year Year Hour Minute Time Counters Date expression Arithmetic expression Syntax MM YY YYYY HH MM HHMMSS 10 counters: $N0 . 128 IBM Tivoli Workload Scheduler for Applications: User’s Guide . v “Steps” on page 122. In the R/3 job page. the Job ID in the Task page is automatically modified. 7. Click OK. The Properties . when you modify the Job Name or the Target Host and click OK. on the Task page click Edit. Enclosed within $( and ). perform the following steps: 1. Editing a standard SAP job To edit a standard SAP job. 3. for each step you modify. Click OK.Managing SAP variants using the Job Scheduling Console Table 34. The list of job pane displays all the available jobs. the fields and values are dynamically built through r3batch depending on the characteristics of the variant or step and are identical to the ones in the equivalent SAP panel. Modify the information contained in the pages as appropriate. and / operations between integers and counters. This operation saves the new step information in the SAP database.

You must specify them in the following places when you define their associated Tivoli Workload Scheduler jobs: v In the Command field of the Task page of the Properties .Task string parameters for SAP jobs Task string to define SAP jobs This section describes the task string parameters that define and control the running of SAP jobs. The following is an example of a JOBREC statement: JOBREC JOBCMD(’/-job job_name -user user_name -i job_ID -c class_value’) JOBUSR(TWS_user_name) | | | | | | | | | | | | | | | | where: class_value job_ID job_name user_name TWS_user_name The Tivoli Workload Scheduler for z/OS user who runs the r3batch access method from the end-to-end scheduling environment. | -host -ts host_name -sg server_group -client source_client -exec_client target_client Chapter 15. The string syntax is the following: Job definition syntax -job job_name -i -id job_ID -user user_name The priority with which the job runs in the SAP system. see Table 35. For details.Job Definition panel. v As arguments of the JOBCMD keyword in the JOBREC statement in the SCRIPTLIB of Tivoli Workload Scheduler for z/OS. see Table 35. see Table 35. if you use the Tivoli Workload Scheduler command line. if you use the Job Scheduling Console and selected SAP for a new job definition.Job Definition panel. v In the R3 Command Line field of the Task page of the Properties . The unique SAP job ID. For details. if you use the Job Scheduling Console and selected Other (and not SAP) for a new job definition. if you are scheduling in an end-to-end environment. For details. The SAP user who owns the target job. The name of the SAP job to run. v As arguments of the scriptname keyword in the job definition statement. see Table 35. For details. Managing the running of SAP jobs 129 .

Task string parameters for SAP jobs -c class_value -s starting_step_number 1 -bdc_job_status_failed bdc_processing -nobdc -nobdcwait -sStep_number attribute_name =attribute_value -vStep_number variant_name -vtxtStep_number variant_description -vparStep_number name=variant_value -vselStep_number name= i e #operation#lowest #highest -recipient R/3_login_name -rectype recipient_type -flag reccp recbl -flag recex -flag recnf -flag im immed -flag enable_joblog disable_joblog -flag enable_spoollist disable_spoollist -flag pc_launch -debug 130 IBM Tivoli Workload Scheduler for Applications: User’s Guide .

It is mutually exclusive with -host and -ts. 3. host_name has the format hostname_SAPsystemname_SAPsystemnumber. The unique SAP job ID. U Chapter 15. This parameter is mandatory. Use this parameter to run the job on an application server that belongs to the group. Specify this parameter if you are submitting a job that refers to a predefined job template stored in the SAP database for which you want to change a parameter. Use this parameter when the target SAP system has only one job with the specified name for the specified user.Task string parameters for SAP jobs -tracelvl 1 2 3 -rfctrace Table 35 describes the parameters for the task string to define SAP jobs. For example. The name of the SAP server group where the job is to be run. but the user name is ignored. The name of the SAP workstation where the job is to be run. The server group must exist on the SAP system. This parameter has no effect if a job ID is specified in the job definition. regardless of the client number defined by the r3client keyword in the options file. You can specify both -i or -id and -user in the same job definition. This parameter is case-sensitive and can be up to 20 characters. The SAP user who owns the target job. The number that identifies the SAP client where the job definition is to be found. This parameter has no effect if a job ID is specified in the job definition. the name of a host might be amss80a0_gs7_90 GUI Support U U -user user_name U -host host_name -ts host_name U | | | | | | | | -client source_client -sg server_group These parameters are mutually exclusive with -sg. 2. -client and -exec_client are ignored because the ID is unique for the entire SAP system. Typically. Task string parameters for SAP jobs Section JOB Parameters -job job_name -i job_ID -id job_ID Description The name of the job to run. Managing the running of SAP jobs 131 . otherwise an error code is returned and the job is not launched. Table 35. Notes: 1. the -debug and -trace options are for debugging the extended agent and should not be used in standard production. When you specify the job ID.

this option is ignored. Tivoli Workload Scheduler sets the job completion status as failed. If -nobdc or -nobdcwait is set. This value overwrites the value specified by the r3client keyword in the corresponding r3batch options file. Tivoli Workload Scheduler sets the job completion status as successful. Possible values are: A High priority B Medium priority C Low priority. Task string parameters for SAP jobs (continued) Section JOB Parameters -exec_client target_client Description The number that identifies the SAP client where the job is to be run. regardless of their status. The priority with which the job runs in the SAP system. ignore When all the BDC sessions complete. Tivoli Workload Scheduler sets the job completion status as failed.Task string parameters for SAP jobs Table 35. all If all the BDC sessions failed. U GUI Support | -rfc_client rfc_logon_client -c class_value 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 -bdc_job_status_failed bdc_processing How Tivoli Workload Scheduler sets the completion status of a job running BDC sessions. This is the default value. This parameter has no effect if a job ID is specified in the job definition. -nobdc -nobdcwait Disables the BDC Wait option (enabled by default) to have the job considered as completed even if not all its BDC sessions have ended. The allowed values are: n If at least n BDC sessions failed (where n is an integer greater than 0). regardless of the client number defined by the r3client keyword in the options file. This is the default. U U 132 IBM Tivoli Workload Scheduler for Applications: User’s Guide . The number that identifies the SAP client to be used for RFC logon. according to a possible BDC processing failure.

If the validation fails.. The step number and its attributes. attribute_value The value of the attribute. the Tivoli Workload Scheduler job goes into the ABEND state. where: step_number The number of the step being defined. It is optional for some attributes. see “Defining attributes for ABAP steps” on page 156 and “Defining attributes for external programs and external commands steps” on page 159. Attributes can be defined in any order. Managing the running of SAP jobs 133 . For example. but cannot be repeated for the same step. Attribute validation is performed before the job is created in the SAP system. For a detailed description of each attribute and its value. 3.. the following step (step 8) is an ABAP module running the report MYPGM and has two attributes. Task string parameters for SAP jobs (continued) Section STEP Parameters -s starting_step_number -sstep_number attribute_name=attribute_value Description The number of the starting step.n) using the step number attribute_name The name of the attribute.Task string parameters for SAP jobs Table 35. only one of which has a value. Each step is identified by a sequential number (1. . 2. -s8 type=A -s8 program=MYPGM -s8 pr_cover="My title" -s8 pr_immed GUI Support U U Chapter 15.

in the Tivoli Workload Scheduler logon language (customizable with the TWSXA_LANG option of r3batch). 134 IBM Tivoli Workload Scheduler for Applications: User’s Guide . sign Sign of the operation. The textual description of the variant. The value for a variant parameter for the specified step number. The maximum length is 30 characters. For a complete list of the supported attributes for ABAP steps. You can use up to 45 characters. This attribute is optional. See “Defining attributes for ABAP steps” on page 156 for a complete list of the supported attributes for ABAP steps. Possible values are: I Include E Exclude values are: Equals Not equal to Between Not between Less than Less than or equal to Greater than Greater than or equal to Contains pattern Does not contain pattern GUI Support U U -vparstep_number name=value U -vselstep_number name=sign#operation#lowest[#highest] U operation Possible EQ NE BT NB LT LE GT GE CP NP lowest Low value of the selection. The value for a variant selection option for the specified step number. highest High value of the selection. see“Defining attributes for ABAP steps” on page 156.Task string parameters for SAP jobs Table 35. Task string parameters for SAP jobs (continued) Section VARIANT Parameters -vstep_number name -vtxtstep_number variant_description Description The variant name for the specified step number. For ABAP modules only. You can use up to 45 characters. For ABAP modules only. This parameter is mandatory when creating a new variant.

Enables or disables retrieval of the spool lists of the job. Managing the running of SAP jobs 135 . Note: You can use this option only if you activated the parent-child feature on the SAP system. Specifies to launch child jobs that are in scheduled state. Enables or disables retrieval of the joblog. Possible values are: recp The spool list is sent as a copy. ON The product launches child jobs that are in scheduled state. meaning that if there are no spare work processes. recbl The spool list is sent as a blind copy. Specifies how the spool list is sent to the recipient. Task string parameters for SAP jobs (continued) Section SPOOL Parameters -recipient name -flag {recp|recbl} Description The login name of an SAP user. the job fails.500 address 'G' Organization object/ID 'H' Organization unit 'I' SAP object 'L' Telex number 'O' SAPOffice user 'P' Private distribution list 'R' SAP user in another SAP system 'U' Internet address '1' Other recipient type Specifies to launch job immediately.0 SAP system you can activate this feature using the INITXBP2 ABAP report U U U GUI Support -flag recex -flag recnf -rectype type FLAGS -flag im -flag immed -flag enable_joblog -flag disable_joblog -flag enable_spoollist -flag disable_spoollist -flag pc_launch Chapter 15. OFF The product does not launch child jobs that are in scheduled state. Specifies that the spool list is sent as an express message to the recipient. Specifies the recipient type.Task string parameters for SAP jobs Table 35. This is the default value. Possible values are: '' SAP user (default value) 'B' SAP user 'C' Shared distribution list 'D' X. On the XBP 2. Specifies that the recipient is not allowed to forward the spool list.

Task string parameters for SAP jobs (continued) Section TRACING Parameters -debug -tracelvl 1|2|3 Description Enables maximum trace level. 2 Informational messages and warnings are also written in the trace file. refer to Chapter 29.Task string parameters for SAP jobs Table 35. 3 A most verbose debug output is written in the trace file. “Configuring the tracing utility.” on page 247. GUI Support U U -rfctrace trace The following is an example for an SAP job named BVTTEST with ID 03102401 and user myuser: -job BVTTEST –i 03102401 -user myuser -debug 136 IBM Tivoli Workload Scheduler for Applications: User’s Guide . Possible values are: 1 Only error messages are written in the trace file. This is the default. For detailed information. Specifies the trace setting for the job. Enables RFC trace.

refer to “Old copy and new copy of a rerunning job. refer to the Tivoli Dynamic Workload Console online help. Job Scheduling Console For details. When r3batch reruns a job from its first step. or H3. It is performed using a new SAP function module that is part of the SAP Support Package as stated in the SAP Notes 399449 and 430087. preserving steps. if you specify a job step to rerun. 00003. and all print and archive parameters.1i. job class. Note: By default. it makes a copy of a template job and runs it. The new copy feature is available for SAP versions 3. to rerun a job from the third step. refer to the Tivoli Workload Scheduler: Reference Guide. Chapter 15. you can use: A03. refer to the Tivoli Workload Scheduler: Reference Guide. Before you rerun an SAP job with Tivoli Workload Scheduler. This affects r3batch in the following ways: v If you use a step name that is up to 9 digits (or 8 digits preceded by a character) in length. creates a new SAP job and adds the steps with a loop that starts from the step name or number you specified. and later. To keep the original job name. the name is ignored and the job is rerun starting from the first step For example. Refer to the following sections for details about: v “Rerunning a standard SAP job” v “Rerunning a process chain job” on page 138 1 Rerunning a standard SAP job For an SAP extended agent. this name is used as the starting step number for the rerunning job v If you use any different format.0 support: v The old copy does not preserve all the print and archive parameters.Task string parameters for SAP jobs Rerunning an SAP job 1 1 1 1 1 1 1 1 1 1 1 1 To rerun an SAP job. the new job is assigned the name of the step you indicated. For details about this option. set the Tivoli Workload Scheduler global option enRetainNameOnRerunFrom to yes. you can use one of the following consoles: conman For details.” Old copy and new copy of a rerunning job When the access method for SAP launches a job. r3batch uses the old copy to rerun the job. The old copy feature. based on standard SAP function modules. you have the option of providing a step name for the job. unless you have XBP 2. see the Tivoli Workload Scheduler: Planning and Installation Guide. If the starting step is greater than one. a step is the numeric step of the SAP instruction from which a job can be restarted. it uses the new copy feature. Be aware that. either because you specified it as the starting step or because no starting step was specified. Managing the running of SAP jobs 137 . For a description about the difference between the new and old copy of a rerunning job. if applicable. It copies an entire job. Tivoli Dynamic Workload Console For details. instead. 3.

For a description of this option. In an end-to-end environment. you set -flag pchain_restart. This setting overrides the settings in the job definition and options file. 138 IBM Tivoli Workload Scheduler for Applications: User’s Guide . you set the pchain_recover option to rerun. if any. if any.Old copy and new copy of a rerunning job v The job class of the copy is always set to class C. refer to Table 33 on page 106. This action occurs when: v You specify RERUNvalue as the step to rerun. you can rerun the process chain job from the failed processes and have its run completed. refer to Table 33 on page 106. It occurs when: v You specify RESTARTvalue as the step to rerun. In an end-to-end environment. This setting overrides the settings in the job definition and options file. This setting overrides the setting in the options file. after you detected the error that caused the failure and performed the recovery action. you set the pchain_recover option to restart. This setting overrides the setting in the options file. Actions performed when you rerun a process chain job Action performed A new process chain instance is submitted Description and setting Tivoli Workload Scheduler creates another process chain instance and submits it to be run again. 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 Rerunning a process chain job Table 36 shows the action performed when you rerun a Tivoli Workload Scheduler job that submits a process chain. if any. you set -flag pchain_rerun. you can perform this action on a centralized job by adding the following parameter to the script file: -flag pchain_restart v In the job definition. SAP Note 758829 is required to ensure proper operation of the new copy and old copy features. For a description of this parameter. where value is any value you want. if any. For a description of this parameter. depending on the settings you specify. see Table 41 on page 170. See also Table 69 on page 257. Table 36. Refer to “Print parameter and job class issues” on page 102 to learn how to resolve the issue of lost job class and print and archive parameters. v In the options file. For a description of this option. where value is any value you want. This action is performed only if at least one process in the process chain did not complete successfully. see Table 41 on page 170. you can perform this action on a centralized job by adding the following parameter to the script file: -flag pchain_rerun v In the job definition. The original process chain is rerun from the failed processes Tivoli Workload Scheduler restarts the original process chain from the failed processes to the end. In this way. v In the options file.

. Actions performed when you rerun a process chain job (continued) Action performed The process that you specify is restarted Description and setting Tivoli Workload Scheduler restarts the process of the original process chain that you specify. the process chain is removed from schedule in the SAP Business Information Warehouse system. Process Variant: PCHAIN1_STARTER. Process Type: ABAP. you require at least the following SAP Business Information Warehouse versions: v 3.Rerunning process chain job 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 Table 36. and monitors the process chain run until its final state. Actual State: F. The process IDs are shown in the Tivoli Workload Scheduler job log. Notes: 1.. Managing the running of SAP jobs 139 .0 with SP25 v 3. . In an end-to-end environment.1 with SP19 Chapter 15. where processID is the identifier of the process you want. you set -flag pchain_refresh. see Table 41 on page 170. This setting overrides the setting in the job definition. For a description of this parameter. Instance: D3C0ZXL3IJ8LR5O9Q1D9A4Y4N. Process Type: ABAP. If you kill a Tivoli Workload Scheduler job that submits a process chain. 2. rerunning a process chain job corresponds to submitting a new process chain instance. +++ EEWO1072I End of process chain PCHAIN1 In an end-to-end environment. if you do not specify any setting. Actual State: . chain are updated This action occurs when: v You specify REFRESHvalue as the step to rerun. if any. >> Process ID: 3. where value is any value you want. >> Process ID: 4. you can perform this action on a centralized job by adding the following parameter to the script file: -flag pchain_refresh v In the job definition. This action occurs when you specify PROCESSprocessID as the step to rerun. Process Variant: Z_PCHAIN1_NODE1. To restart the same process chain instance with r3batch. Actual State: F. Instance: D3C0ZZKS0RR88DKRJQ09Z1WW7. -------------------------Process Type: TRIGGER. as follows: +++ EEWO1071I Start of process chain PCHAIN1 Process Chain PCHAIN1 (Log ID:D3C0ZWAYESD58PXOYPEOGNZK7). By default. you can perform this action on a centralized job by adding the following parameter to the script file: -pchain_pid processID The status and details Tivoli Workload Scheduler monitors the original process chain of the original process until its final status. Process Variant: Z_PCHAIN1_NODE3.

In this way. Restart the failed transformation process only after the data has been reloaded. After fixing the problem with the transformation process. for example by using aggregate functions. 140 IBM Tivoli Workload Scheduler for Applications: User’s Guide . the original process chain is rerun from the failed processes and continues until the ending step. you must restart the InfoPackage extraction process to reload the data. You ask the SAP administrator to fix the cause of the error. The process chains include a set of Infopackages. you can see what processes failed either through the Tivoli Dynamic Workload Console (for details. During batch processing. you can restart the process chain only manually. To administer from a single point of control. then you rerun the Tivoli Workload Scheduler job by setting the step as RESTARTvalue. A job stream contains jobs that collect and prepare data for month-end closing over all sales channels. a Tivoli Workload Scheduler job comprising a process chain. If the process that transforms this data fails. through the SAP graphical interface. you link the SAP process chains to Tivoli Workload Scheduler through Tivoli Workload Scheduler for Applications.Rerunning process chain job 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 v 3. and operating system jobs to sort the report data by a logical hierarchy. it might corrupt the data that the preceding InfoPacakge process had successfully extracted. see “Displaying details about a process chain job” on page 142) or the job log. ABAP reports. Business scenario: restarting a process of the process chain You might decide to restart a single process as a preparation step before restarting the failed processes of a process chain. so you run the single process to restore the data and set up the required system state before you rerun the other processes in the process chain. The workflow is one or more job streams in Tivoli Workload Scheduler. A failed process might have corrupted some data. Suppose you are using InfoPackages and process chains to extract data from one or several sources and you want to transform this data into managerial reports. Business scenario: rerunning the original process chain job from the failed process As a scheduling administrator. The month-end closing report requires data to be collected from several sales and distribution systems. Data is collected using local and remote process chains in the SAP Business Intelligence system. even though this extraction process had completed successfully before. failed. either by restarting the failed processes of the process chain or restarting just the failed transformation process. you are responsible for managing batch jobs in SAP and non-SAP systems.0 If your version of SAP Business Information Warehouse is earlier.5 with SP10 v 7. Optionally.

Chapter 16. The Properties . The Properties Job Definition panel is displayed. perform the following steps: 1. Managing SAP jobs This chapter describes how to perform the following tasks: v “Displaying details about a standard SAP job” v “Displaying details about a process chain job” on page 142 v “Verifying the status of a standard SAP job” on page 144 v “Deleting a standard SAP job from the SAP database” on page 144 v “Balancing SAP workload using server groups” on page 144 v “Raising an SAP event” on page 145 v “Mapping between Tivoli Workload Scheduler and SAP job states” on page 145 v “Killing an SAP job instance” on page 147 1 Displaying details about a standard SAP job To display details about a standard SAP job. The panel consists of the following: v “General page” on page 116 v “Task page” on page 118 3. 2008 141 . 2. click Details. On the Task page. Double-click the SAP job whose details you want to display. select an engine → database list → job definition list. 2003. 5. The list of job pane displays the available jobs. Click OK. In the Work with engines pane. 4. © Copyright IBM Corp.Job Definition dialog is displayed. Click OK. It contains all the information relevant for the job. The Details panel is displayed.

1. The table of results for the task is displayed: 1 1 Figure 16. For more information about this option. perform the following steps from the Tivoli Dynamic Workload Console. 2.Displaying details about process chain jobs 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 Displaying details about a process chain job To display details about an SAP process chain that you scheduled as a Tivoli Workload Scheduler job. For each process chain job. the Job Type column shows a hyperlink named 1 SAP Process Chain. From your Tivoli Workload Scheduler list of tasks. Click the hyperlink for the job whose details you want to 1 display.4 Fix Pack 1 to show the Job Type column. refer to “Defining the common options” on page 106. Note: You can perform these steps only if you: v Did not set the pchain_details option to OFF in the job definition. v Customized the Browse Jobs tasks that you created before installing Tivoli Workload Scheduler for Applications 8. For details about how to customize the task properties. Tivoli Dynamic Workload Console .Table of results 1 3. click the Jobs task that you want to run. Enter any information required and click OK. refer to the Tivoli Dynamic Workload Console online help. A panel like the following opens: 1 1 142 IBM Tivoli Workload Scheduler for Applications: User’s Guide .

Chapter 16. Click the hyperlink you want.Details of a process chain job 1 You are shown the details of the process chain job. to display details about the corresponding subchain job. If the process chain contains local subchains. you can display the process chain details from the job properties panel by clicking the hyperlink that is shown under SAP Job Details. The details shown reflect the last monitoring process performed. Tivoli Dynamic Workload Console . Alternatively. 4.Displaying details about process chain jobs 1 1 1 Figure 17. Managing SAP jobs 143 . a hyperlink is displayed for each one. 1 1 1 1 1 1 1 1 1 Note: Tivoli Workload Scheduler for Applications monitors the process chain job until the job completes.

With SAP Basis version 6. | | | | | | | | | | | | | | | | | Balancing SAP workload using server groups SAP jobs run on application servers that host work processes of type batch. The panel consists of the following: v “General page” on page 116 v “Task page” on page 118 3. select an engine → database list → job definition list. the SAP system runs it on an application server that belongs to that group. With Tivoli Workload Scheduler for Applications. the job defined as belonging to that server group is not affected and does not need to be modified. Click OK. Click OK. 4. on specific application servers. Click OK.Job Definition dialog is displayed. with Service Pack 40 v SAP Basis 6.10 and later. perform the following steps: 1.Job Definition dialog is displayed. In this way. 5. Click OK. The Properties . Select the job you want to delete. to delete the SAP job displayed in the Job Name field.10. In the Task page click Delete. In the Task page click Status. The panel consists of the following: v “General page” on page 116 v “Task page” on page 118 3. balancing the workload among the various application servers. when a job is launched.. you can assign a server group to a job.Job Definition panel is displayed.. In the Work with engines pane. The batch execution targets are reorganized in the SAP system without having to change job definitions in Tivoli Workload Scheduler for Applications. This function is supported with the following versions of SAP: v SAP Basis 6. application servers can be assigned to server groups. The Properties .Verifying the status of a standard SAP job Verifying the status of a standard SAP job To verify the status of a standard SAP job. Critical batch jobs are run in specific time frames. 2. Double-click the SAP job you want to delete.40. 2. perform the following steps: 1. To delete a job different from the one displayed in the Job Name field.) to display a list of available jobs. The Properties. Deleting a standard SAP job from the SAP database To delete a standard SAP job from the SAP database. 4. The list of job pane displays the available jobs.20. In the Work with engines pane. Double-click the SAP job whose status you want to display. The Properties. The SAP Job Status panel is displayed with the status of the job. If the application servers defined in a group are modified in the SAP system. 5. select an engine → database list → job definition list.Job Definition panel is displayed. with Service Pack 41 v SAP Basis 6. The list of job pane displays the available jobs. with Service Pack 04 144 IBM Tivoli Workload Scheduler for Applications: User’s Guide . click ellipsis (.

Check that this job was not intercepted by the interception function. Because it takes some time to get a job queued and into the ready column. The list of job pane displays the available jobs. The Raise Event panel opens. the job has not yet entered the ready state. To use this option. Managing SAP jobs 145 . The status transitions in Tivoli Workload Scheduler (internal status) and the corresponding SAP status are listed in Table 37.00. Status transitions in Tivoli Workload Scheduler (internal status) and the corresponding SAP R/3 status Tivoli Workload Scheduler Job State INTRO WAIT EXEC SUCC ABEND SAP Job State Not Available Ready. you can monitor its progress. see Chapter 19. 4.” on page 173. create a job that has as start condition an SAP event. In the Work with engines pane. 2. the INTRO state might last a few minutes if the SAP system is particularly busy. Raising an SAP event You can raise events on XBP 2. and later Mapping between Tivoli Workload Scheduler and SAP job states When an SAP job is launched by Tivoli Workload Scheduler. Chapter 16. “Using the BDC Wait option. 3. select an engine → database list → job definition list. On the SAP system.0 SAP jobs in the Tivoli Workload Scheduler database in one of the following ways: Using the Raise Event function Perform the following steps: 1. Even if a job is finished in SAP. When you create this job its status is released.Balancing SAP workload using server groups | v SAP Basis 7. Table 37. 5. Select a Tivoli Workload Scheduler job whose workstation has been defined to connect to the SAP system. Right-click the job and select Raise Event. Tivoli Workload Scheduler keeps it in the EXEC state if its BDC sessions are not complete and you have not selected the Disable BDC Wait option. but in SAP. Release Active Finished Canceled The INTRO state indicates that Tivoli Workload Scheduler is in the process of introducing the job.

Click OK. parameter The parameter defined for the event.Raising an SAP event Figure 18.Job Definition panel is displayed. In the Task page. 146 IBM Tivoli Workload Scheduler for Applications: User’s Guide . Use the Task page to provide task information for the job. The event is raised. The Properties . SAP_event_ID The identifier of the event. Event Parameter The parameter of the event that is to be raised. Use the General page to provide general information about the new job definition. This is the name specified in the r3user option. In the Actions list of the Job Scheduling Console main window. Select an engine. The Raise Event panel The panel consists of the following: Event ID The identifier of the event that is to be raised. Creating a job that launches a Windows or UNIX command that performs a raise event Perform the following steps: 1. select Command and type the following command that performs the raise event in the command string: TWShome/methods/r3event -c workstation_name -u user_name -e SAP_event_ID -p parameter where: workstation_name The name of the workstation where the SAP R/3 job is defined. 4. The panel consists of the following: v “General page” on page 116 v “Task page” on page 118 3. 5. 2. user_name The name of the SAP user with which the access method connects to the SAP system. select New Job Definition. 6.

2. the SAP system stops as soon as the process that is currently running completes.Killing an SAP job instance 1 1 1 1 1 1 1 1 1 1 1 1 Killing an SAP job instance This section describes how to kill a Tivoli Workload Scheduler job that submits either a standard SAP job or an SAP process chain. 2. perform the following steps: 1. Chapter 16. To kill an SAP job instance. Run a list of job instances that contains the job that you want to kill. Managing SAP jobs 147 . you must install IBM Tivoli Workload Scheduler version 8. The SAP job or process chain is set to canceled in the SAP system. Note: If you kill a process chain job. or later.1 Fix Pack 1. Right-click the job instance and select Kill from the pop-up menu. Note: To perform this function on a Windows operating system. The Tivoli Workload Scheduler job status is set to ABEND.

Killing an SAP job instance 148 IBM Tivoli Workload Scheduler for Applications: User’s Guide .

1 Chapter 17. To take full advantage of this feature.0 installed. Tivoli Workload Scheduler makes a copy of the predefined job (also known as a template job) and runs the copy. 1 1 1 © Copyright IBM Corp. make sure you have XBP version 2. v “Specifying job parameters using variable substitution” on page 160 explains how to provide parameters at run time by using the variable substitution feature. v A job that references a predefined job template stored in the SAP R/3 database for which you want to change a parameter. a job that does not refer to an existing template in the SAP R/3 database. by submitting: v In the SAP system. In this chapter: v “Task string to define SAP jobs dynamically” on page 150 uses a syntax diagram to show the complete library of job creation parameters and provides a detailed explanation of each parameter. 2003. Defining SAP jobs dynamically When you launch a job created as described in “Defining a job that runs an SAP job” on page 115 and “Task string to define SAP jobs” on page 129. v “Dynamically defining and updating SAP jobs: some examples” on page 160 shows examples of this feature. This chapter describes how to create and submit SAP jobs dynamically without creating or referencing predefined job templates. 2008 149 . you need to manually create the template job on each system. or provide a way to set the job class or the spool list recipient. If you want to run the job on several SAP systems. because earlier versions of XBP do not support the full set of print and archive parameters.

These sections are grouped in Table 38 on page 152 and are related to the: v Job v Job steps v Variants associated with the steps (for ABAP modules only) v Spool list recipients associated with the job v Flags associated with the job v Tracing specifications for the job To define and submit an SAP R/3 job dynamically. You can build an entire job definition by using the six main sections concerning SAP job parameters. use the following syntax: Job definition syntax -job job_name -i -id job_ID -flag type=exec -host -ts host_name -sg server_group -client source_client -exec_client target_client -c class_value -s starting_step_number -bdc_job_status_failed bdc_processing -nobdc -nobdcwait -sStep_number attribute_name =attribute_value -vStep_number variant_name -vtxtStep_number variant_description 150 IBM Tivoli Workload Scheduler for Applications: User’s Guide .Task string to define SAP jobs dynamically Task string to define SAP jobs dynamically 1 1 1 1 1 1 1 1 1 1 This section describes the task string that controls the running of SAP jobs.

Task string to define SAP jobs dynamically -vparStep_number name=variant_value -vselStep_number name= i e #operation#lowest #highest -recipient R/3_login_name -rectype recipient_type -flag reccp recbl -flag recex -flag recnf -flag im immed -flag enable_joblog disable_joblog -flag enable_spoollist disable_spoollist -flag pc_launch -debug -tracelvl 1 2 3 -rfctrace -rfc_client rfc_logon_client The following is an example of a definition for the SAPTEST job: -job SAPTEST -C A -user MAESTRO -s1 program=BTCTEST -s1 type=A -s1 pr_release -s2 report=BTCTEST -s2 variant=BVT –s2 type=A -flag type=exec -vpar2 TESTNAME=test -vtxt2 Test Table 38 on page 152 describes the parameters for the task string to define SAP jobs dynamically. Chapter 17. Note: The parameter values are case sensitive. Defining SAP jobs dynamically 151 .

the target SAP system must have only one job with the specified name for the specified user. This parameter is mandatory. The number that identifies the SAP client where the job definition is to be found. This parameter has no effect if a job ID is specified in the job definition. regardless of the client number defined by the r3client key in the options file. Task string parameters for SAP jobs (dynamic definition) Section JOB Parameters -job job_name -i job_ID -id job_ID Description The name of the job to be run. It is mutually exclusive with -host and -ts. The number that identifies the SAP client where the job is to be run. This parameter is case-sensitive and can be up to 20 characters.Task string to define SAP jobs dynamically Table 38. This is the default value. 1 1 1 1 1 1 1 1 | | -exec_client target_client -c class_value 152 IBM Tivoli Workload Scheduler for Applications: User’s Guide . This value overwrites the value specified by the r3client keyword in the corresponding r3batch options file. Possible values are: A High priority B Medium priority C Low priority. The priority with which the job runs in the SAP system. regardless of the client number defined by the r3client key in the options file. otherwise an error code is returned and the job is not launched. The name of the SAP server group where the job is to be run. The server group must exist on the SAP system. Specify this parameter if you are submitting a job that refers to a predefined job template stored in the SAP database for which you want to change a parameter. This parameter has no effect if a job ID is specified in the job definition. To use this parameter. For example. -rfc_client rfc_logon_client The number that identifies the SAP client to be used for RFC logon. -host host_name -ts host_name The name of SAP workstation where the job is to be run. The SAP user who owns the template job. This parameter has no effect if a job ID is specified in the job definition. the name of a host might be amss80a0_gs7_90 1 1 1 1 1 1 1 -user user_name | | | | | | | | -client source_client -sg server_group These parameters are mutually exclusive with -sg. This parameter requires that the client-dependent data (such as the user name and report variants) exists on both the source and target clients. host_name has the format hostname_SAPsystemname_SAPsystemnumber. Specify this parameter if you want to create a copy of the template job. The unique SAP job ID. Use this parameter to run the job on an application server that belongs to the group.

If the validation fails. where: step_number The number of the step being defined. It is optional for some attributes. -s8 type=A -s8 program=MYPGM -s8 pr_cover="My title" -s8 pr_immed 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 Chapter 17. but cannot be repeated for the same step. Each step is identified by a sequential number (1.n) using the step number. attribute_name The name of the attribute. according to a possible BDC processing failure. The step number and its attributes. .Task string to define SAP jobs dynamically Table 38. all If all the BDC sessions failed. Task string parameters for SAP jobs (dynamic definition) (continued) Section JOB Parameters -flag type=exec -bdc_job_status_failed bdc_processing Description Specify this parameter to enable the dynamic definition of the SAP job. Tivoli Workload Scheduler sets the job completion status as failed. attribute_value The value of the attribute. this option is ignored. see “Defining attributes for ABAP steps” on page 156 and “Defining attributes for external programs and external commands steps” on page 159. regardless of their status.. Defining SAP jobs dynamically 153 .. The number of the starting step. Attributes can be defined in any order. Tivoli Workload Scheduler sets the job completion status as failed. Attribute validation is performed before the job is created in the SAP system. -nobdc-nobdcwait STEP -s starting_step_number -sstep_number attribute_name=attribute_value Disables the BDC Wait option (enabled by default) to have the job considered as completed even if not all its BDC sessions have ended. only one of which has a value. Tivoli Workload Scheduler sets the job completion status as successful. ignore When all the BDC sessions complete. The allowed values are: n If at least n BDC sessions failed (where n is an integer greater than 0). This is the default value. How Tivoli Workload Scheduler sets the completion status of a job running BDC sessions. For a detailed description of each attribute and its values. the following step (step 8) is an ABAP module running the report "MYPGM" and has two attributes. If -nobdc or -nobdcwait is set. This parameter is mandatory. 3. For example. the Tivoli Workload Scheduler job goes into the ABEND state. 2.

in the Tivoli Workload Scheduler logon language (customizable with the TWSXA_LANG option of r3batch). You can use up to 45 characters. You can use up to 45 characters. sign Sign of the operation. This parameter is mandatory when creating a new variant. see “Defining attributes for ABAP steps” on page 156. The value for a variant selection option for the specified step number. The textual description of the variant. For a complete list of the supported attributes for ABAP steps. The maximum length is 30 characters. For ABAP modules only. The value for a variant parameter for the specified step number. 154 IBM Tivoli Workload Scheduler for Applications: User’s Guide .Task string to define SAP jobs dynamically Table 38. For a complete list of the supported attributes for ABAP steps. For ABAP modules only. see “Defining attributes for ABAP steps” on page 156. highest High value of the selection. Possible values are: I Include E Exclude values are: Equals Not equal to Between Not between Less than Less than or equal to Greater than Greater than or equal to Contains pattern Does not contain pattern -vparstep_number name=value -vselstep_number name=sign#operation#lowest[#highest] operation Possible EQ NE BT NB LT LE GT GE CP NP lowest Low value of the selection. Task string parameters for SAP jobs (dynamic definition) (continued) Section VARIANT 1 Parameters -vstep_number name -vtxtstep_number variant_description Description The variant name for the specified step number. This attribute is optional.

For more details. the job fails. Chapter 17. Enables or disables retrieval of the joblog. Possible values are: 1 2 3 Only error messages are written in the trace file.0 SAP system you can activate this feature using the INITXBP2 ABAP report Enables maximum trace level. -rfctrace trace Enables RFC trace. Specifies how the spool list is sent to the recipient. recbl The spool list is sent as a blind copy. Specifies the recipient type. Possible values are: recp The spool list is sent as a copy. OFF The product does not launch child jobs that are in scheduled state. Note: You can use this option only if you activated the parent-child feature on the SAP system. Specifies to launch child jobs that are in scheduled state. Specifies that the spool list is sent as an express message to the recipient. Enables or disables retrieval of the spool lists of the job. ON The product launches child jobs that are in scheduled state. “Configuring the tracing utility. This is the default value. Specifies that the recipient is not allowed to forward the spool list. Specifies the trace setting for the job. Informational messages and warnings are also written in the trace file. On the XBP 2. This is the default. -flag recex -flag recnf -rectype type FLAGS -flag im -flag immed -flag enable_joblog -flag disable_joblog -flag enable_spoollist -flag disable_spoollist -flag pc_launch TRACING -debug -tracelvl 1|2|3 A most verbose debug output is written in the trace file. Task string parameters for SAP jobs (dynamic definition) (continued) Section SPOOL Parameters -recipient name -flag {recp|recbl} Description The login name of an SAP user.Task string to define SAP jobs dynamically Table 38. Possible values are: blank SAP user (default value) B SAP user C Shared distribution list D X.” on page 247. meaning that if there are no spare work processes.500 address G Organization object/ID H Organization unit I SAP object L Telex number O SAP Office user P Private distribution list R SAP user in another SAP system U Internet address 1 Other recipient type Specifies to launch the job immediately. refer to Chapter 29. Defining SAP jobs dynamically 155 .

v All changes to the variant values are permanent. its values are modified according to the command line parameters. The following rules apply when you create or update SAP jobs dynamically: v To create or reference a variant within an ABAP step. it is created with the parameters specified in the job definition statement. all the required attributes of the variant must be given a value. the login language of the access method is used (customize using the option XAMETH_LANG in the r3batch option files) The product performs a check for a valid language prior to launching the job. Possible values are: v A v ABAP The product performs a check for correct attribute values prior to launching the job. the job step is run using this variant instance. Supported attributes for ABAP step definition Attribute name type Synonym typ Description Specify the step type. If the existing variant is an extended one. You cannot create empty variants. Defining attributes for ABAP steps Table 39 shows a complete list of the supported attributes for ABAP step module definition: Table 39. for example D. nor deletes the variants created after the job is run. v If a variant is already present in the SAP system. program parameter user language authcknam lang Specify the ABAP program name. That is. Specify the ABAP variant name. In this case. Specify the user of the step Specify the step language This attribute accepts language names in either the ISO format (two characters. U U U U Required U 156 IBM Tivoli Workload Scheduler for Applications: User’s Guide .Task string to define SAP jobs dynamically Notes: 1. Tivoli Workload Scheduler neither restores the old values of the variants. Finally. for example DE. EN) or the R/3 format (one character. you can use one of the following equivalent syntaxes: – -s1 Variant=Var1 – -s1 Parameter=Var1 – -v1 Var1 v If a variant does not exist. E) If this attribute is not specified. Tivoli Workload Scheduler does not change the case of the variant values. This new variant instance is then updated using the values from the command line. a new instance of it is created with resolved placeholders and updated counters. pr_dest printer pdest Print Parameter: Specify the Printer for the output.

The value of this attribute must be numeric. SAP ArchiveLink: Object type of business object SAP ArchiveLink: Document type SAP ArchiveLink: Info field SAP ArchiveLink: Target storage system ¹ SAP ArchiveLink: Document class ¹ SAP ArchiveLink: PRC host ¹ Required pr_lines linct pr_sapbanner prsap pr_exp pexpi pr_spoolname plist pr_format pr_dep pr_spoolds pr_spoolprio pr_immed pr_release pr_banner pr_newspool pr_cover paart prabt prdsn priot primm prrel prbig prnew prtxt pr_hostcover prunx al_sapobject al_object al_info al_id al_doctype al_rpchost sap_object object info archiv_id doc_type rpc_host Chapter 17. Print Parameter: Host spool cover page ¹ . pr_columns linsz Print Parameter: Specify the page width. 'X' Prints the host cover page. A corresponding check is performed prior to launching the job. A corresponding check is performed prior to launching the job. Possible values are: '' Blank. A corresponding check is performed prior to launching the job. pr_auth pr_arcmode prber armod Print Parameter: Authorization Print Parameter: Archiving mode Print Parameter: SAP cover page Print Parameter: Spool retention period The value of this attribute must be a single digit. A corresponding check is performed prior to launching the job. Does not use any cover page. Defining SAP jobs dynamically 157 . 'D' Prints the default host cover page. Print Parameter: Specify the page length.Defining attributes for ABAP steps Table 39. The value of this attribute must be numeric. If the string contains spaces it must be enclosed between single quotes. The value of this attribute must be numeric. Supported attributes for ABAP step definition (continued) Attribute name pr_copies Synonym prcop Description Print Parameter: Specify the number of copies. pr_recip prrec Print Parameter: Recipient Print Parameter: Name of spool request ¹ Print Parameter: Print formatting ¹ Print Parameter: Department on cover page ¹ Print Parameter: Name of spool data set ¹ Print Parameter: Spool request priority ¹ Print Parameter: Print immediately ² Print Parameter: Delete after printing ² Print Parameter: Selection cover page ² Print Parameter: New spool request ¹ ² Print Parameter: Text for cover page ¹.

This attribute is available for BC-XBP 2. If the validation fails. for example: –s2 pr_release Tivoli Workload Scheduler performs the following syntax validation on job attributes: v Only valid attributes are allowed v Checks if a particular attribute requires a value v The values of the following attributes are checked: – type – language – pr_copies – pr_lines – pr_colums Validation is performed before the job is created in the SAP system.Defining attributes for ABAP steps Table 39. it does not have a value. Supported attributes for ABAP step definition (continued) Attribute name al_rpcserv al_iface al_client al_report al_text al_date al_user al_printer al_format al_path al_protocol al_version formular archivpath protokoll arctext datum arcuser Synonym rpc_servic interface mandant Description SAP ArchiveLink: RPC service / RFC destination ¹ SAP ArchiveLink: Name of communication connection component ¹ SAP ArchiveLink: Client ¹ SAP ArchiveLink: Report name ¹ SAP ArchiveLink: Text information field ¹ SAP ArchiveLink: Archiving date ¹ SAP ArchiveLink: Data element for user ¹ SAP ArchiveLink: Target printer ¹ SAP ArchiveLink: Output format ¹ SAP ArchiveLink: Standard archive path ¹ SAP ArchiveLink: Storage connection protocol ¹ SAP ArchiveLink: Version number ¹ Required Notes: 1. 158 IBM Tivoli Workload Scheduler for Applications: User’s Guide . that is. the Tivoli Workload Scheduler job goes into the ABEND state.0 and later 2. This attribute is a flag.

E). the login language of the access method is used (customize using the XAMETH_LANG option in the r3batch option files). EN) or the R/3 format (one character. Supported attributes for external programs and external commands step definition Attribute name type Synonym typ Description The step type can assume one of the following values: For external programs v X v EXTPGM For external commands v C v EXTCMD Before launching the job. Operating system for the external command. ¹ ² Chapter 17. Step language. User of the step. Table 40. ² Control flag: whether SAP tracing level 3 is activated for tracing SAPXPG. This name must be exactly the same as the name shown in the External Operating System Commands table in the SAP system (transaction SM69). Defining SAP jobs dynamically 159 . This attribute accepts language names in either the ISO format (two characters. Parameters for the external program or command. Required U 1 1 report parameter user language authcknam lang ABAP program name or name of the external program or command. os opsystem termcntl tracecntl waitforterm Control flag: whether an external command or program is to be run synchronously. the product performs a check for correct attribute values. the program that starts an external command or program. If this attribute is not specified. for example DE. The product performs a check for a valid language prior to launching the job. This name must be exactly the same as the name shown in the External Operating System Commands table in the SAP system (transaction SM69). for example D.Defining attributes for external programs and external commands steps Defining attributes for external programs and external commands steps Table 40 shows a complete list of the supported attributes for external programs and external commands step definition. U 1 1 1 1 1 1 1 1 1 1 targethost xpgtgtsys Target host for the external program or command.

Supported attributes for external programs and external commands step definition (continued) Attribute name stdoutcntl Synonym Description Control flag: indicates whether standard output from an external command or program is to be written to the job log.Defining attributes for external programs and external commands steps Table 40. This attribute is a flag. The only requirement is that the elements referred to are known in the SAP system (user. there should be a set of values to define the content of the variant for its creation (pairs of –vpar<N> -vsel<N> parameters for the parameters and selections of the ABAP program). the value appears as: -s1 report=&VARNAME The variable substitution process occurs while Tivoli Workload Scheduler is creating the symphony file.0 and later 2. For example. This attribute is available for BC-XBP 2. ¹ ² Required stderrcntl Notes: 1. The first step runs the ABAP MYPROG1 using variant VAR01 and associated variant parameter. the Tivoli Workload Scheduler job goes into the ABEND state. ¹ ² Control flag: indicates whether standard error from an external command or program is to be written to the job log. program). Step 3 uses the same ABAP as step 1 with no associated variant. for example: –s2 pr_release Tivoli Workload Scheduler performs the following syntax validation on job attributes: v Only valid attributes are allowed v Checks if a particular attribute requires a value v The values of the following attributes are checked: – type – language – pr_copies – pr_lines – pr_colums Validation is performed before the job is created in the SAP system. it does not have a value. 160 IBM Tivoli Workload Scheduler for Applications: User’s Guide . that is. Specifying job parameters using variable substitution Parameters can be provided at run time using the variable substitution feature. If the validation fails. Step 2 has a step user defined. Dynamically defining and updating SAP jobs: some examples This section describes some usage examples of this feature: Job definition and run scenario using the -flag type=exec parameter The following example creates and runs a 3-step job assigned to the user MAESTRO. If the variant does not exist.

-job TEMPLAJOB –I 56780123 -s1 pr_immed -flag type=exec Chapter 17. -job TESTJOB01 –i 12345678 –s1 variant=VAR01A –vpar1 TESTNAME=TST2 –s4 type=X -s4 report=niping –s4 parameter=-t -flag type=exec Copy and overwrite a job referencing an existing job template The following example shows a job creation referencing a job template (previously created without using this feature).Dynamically defining and updating SAP jobs: examples -job TESTJOB01 –user MAESTRO –c A -s1 type=A –s1 program=MYPROG1–v1 VAR01 –vpar1 TESTNAME=TST -s2 report=SPOOLX1 –s2 user=PRTUSER –s3 type=A –s3 program=MYPROG1 –flag type=exec The job returns job ID 12345678 Job copy and overwrite the job created in the previous step The following job statement references the job created in the previous example. In this case the variant for step 1 is modified and a new external program step (Step 4) is added. A new copy of the job is made and the parameters specified in the invocation are used to update the definition. Defining SAP jobs dynamically 161 . It is a single ABAP step job to which we now add some print parameters. A template job called TEMPLAJOB already exists on the SAP system with an ID of 56780123.

Dynamically defining and updating SAP jobs: examples 162 IBM Tivoli Workload Scheduler for Applications: User’s Guide .

3 can launch Process Chains.0B or higher installed. it contains job specific parameters such as start time. 2003. The processes within a process chain are not limited to data load processes. It allows business reporting and decision support. This chapter provides information about: v “Business Warehouse components” v “Defining user authorizations to manage SAP R/3 Business Warehouse InfoPackages and process chains” on page 164 v “Managing SAP R/3 Business Warehouse InfoPackages and process chains” on page 164 Business Warehouse components SAP R/3 supports two main Business Warehouse components. generically named InfoObject).0B or higher installed. and dependencies. version 3. but also include: v Attribute/Hierarchy Change run v Aggregate rollup v ABAP program v Another process chain v Customer build process © Copyright IBM Corp. Technically.1 is required so that r3batch 8. InfoPackages and Process Chains. or InfoPackages. A Process Chain is a complex chain of different processes and their relationships. version 2. An InfoPackage is the entry point for the loading process from a specific InfoSource (a logical container of data source. an InfoPackage is an SAP R/3 job whose aim is to load data.Chapter 18. The Support Package 9 (SAPKW31009) for SAP Business Warehouse 3. To use the InfoPackages component. Like any other SAP R/3 job. you must have the SAP Business Warehouse Systems. To use the Process Chains component. Using Business Information Warehouse Business Information Warehouse (BIW) is a data warehouse solution tailored to SAP R/3. 2008 163 . you must have the SAP Business Warehouse Systems.

This section describes how to perform the following tasks on the SAP R/3 Business Warehouse InfoPackages and process chains: v “Creating a Tivoli Workload Scheduler job that contains InfoPackages or process chains” v “Displaying details about Business Warehouse InfoPackages” on page 169 v “Task string to define Business Warehouse InfoPackages and process chains” on page 169 v “Mapping between Tivoli Workload Scheduler and SAP job states” on page 145 Creating a Tivoli Workload Scheduler job that contains InfoPackages or process chains This section describes how to create a Tivoli Workload Scheduler job that contains a Business Warehouse InfoPackage or a process chain. The user must also belong to the following profiles: v S_BI-WHM_RFC (for Business Information Warehouse version 7. In the Actions list of the Job Scheduling Console main window. the scheduling options of the InfoPackage must have: v Start type set to Start later in background process. you must define a Tivoli Workload Scheduler user within SAP R/3 with full authorization for the ABAP Workbench object S_DEVELOP.Job Definition panel is displayed. To be able to schedule InfoPackages using Tivoli Workload Scheduler.3. 2. To create a Tivoli Workload Scheduler job definition that contains an InfoPackage or process chain in the Tivoli Workload Scheduler database. since feature level 1. Select an engine. However. The Properties . so that you can also define Tivoli Workload Scheduler extended agent jobs for these objects.Defining user authorizations to manage InfoPackages and process chains Defining user authorizations to manage SAP R/3 Business Warehouse InfoPackages and process chains Tivoli Workload Scheduler for Applications for SAP can manage SAP R/3 Business Warehouse InfoPackages and process chains. perform the following steps: 1. select New Job Definition. v Start time set to immediate. To use the SAP R/3 Business Warehouse functions. the Job Scheduling Console supports pick lists of InfoPackages and process chains. 164 IBM Tivoli Workload Scheduler for Applications: User’s Guide . or later) v S_RS_ALL v Z_MAESTRO Managing SAP R/3 Business Warehouse InfoPackages and process chains Business Warehouse InfoPackages and process chains can only be created from the SAP R/3 environment.0.

.Creating Tivoli Workload Scheduler job with InfoPackages or process chains Figure 19.) to display a list of SAP R/3 workstations. The maximum length is 40 characters. The General page of the Properties . Chapter 18. dashes. Using Business Information Warehouse 165 . The page consists of the following: v Information group: Task Type Select SAP. and can contain alphanumeric characters.. and underscores. Name Type the name of the IBM Tivoli Workload Scheduler job. Workstation Name Type the name of the SAP R/3 workstation where the IBM Tivoli Workload Scheduler job runs or use ellipsis (.Job Definition panel The panel consists of the following: v “General page” v “Task page” on page 166 General page Use the General page to provide general information about the new job definition. The name must start with a letter.

Message Type the text of a recovery prompt to be displayed if the job ends in error.. The recovery prompt is an ad hoc prompt. The maximum length is 120 characters. The Status of All Prompts shows all recovery prompts.Creating Tivoli Workload Scheduler job with InfoPackages or process chains Description Type a description of the IBM Tivoli Workload Scheduler job. The name is entered automatically when you select a recovery job. The page consists of the following: Task Type This information field indicates that the job is SAP R/3 task type. Not all jobs are eligible to have recovery jobs run on a different workstation. – Rerun. If a job ended successfully. Specify a user who can log on to the workstation where the job runs. The maximum length is 47 characters. it must be hosted by a domain manager or a fault-tolerant agent that runs in Full Status mode. Rerun the job. Recovery jobs are run only once for each instance of the parent job ended in error. Continue with the next job. – If the recovery job workstation is a fault-tolerant agent.. it must run in Full Status mode. Follow these guidelines: – If either workstation is an extended agent. the status is Not Asked. If a job ended in error. v R/3 Job Identity group: 166 IBM Tivoli Workload Scheduler for Applications: User’s Guide .) to display a list of recovery jobs from where to select the recovery job to run if the parent job ends in error. Task page Use the Task page to provide task information for the Tivoli Workload Scheduler job. The text can contain up to 64 characters. v Login group: Login Type the name of the user who launches the IBM Tivoli Workload Scheduler job. Job Click ellipsis (. This is the default value. – Continue. the prompt status is Asked and the message is displayed. Do not continue with the next job. Workstation Name Displays the name of the workstation where the recovery job runs. – The recovery job workstation must be in the same domain as the parent job workstation. v Recovery Options group: Select the recovery option you want to associate with the IBM Tivoli Workload Scheduler job if it ends in error. The task type depends on the SAP R/3 system where you defined the job. v R/3 Job Type group: R/3 Job Type Select Business Warehouse InfoPackage or Business Warehouse Process Chain. Possible values are: – Stop.

. The SAP Pick List panel Click Start to get a complete list of existing InfoPackages or filter your query by filling in one or more of the following fields: Name & Location group: Find Specify an SAP R/3 InfoPackage name. If you use asterisks and specify an information in the Advanced Filter group fields the search tool displays: – The information you specified if contained in the SAP R/3 database. Figure 20. InfoSource The structure that consists of InfoObjects and is used as a non-persistent store to connect two transformations.).Creating Tivoli Workload Scheduler job with InfoPackages or process chains Job Name Type the SAP R/3 job name or use ellipsis (. Business Warehouse InfoPackages: The SAP Pick List panel. The SAP Pick List panel is displayed. Advanced Filter group: Click Advanced Filter and specify one or more of the following items of information. You can use the wildcard asterisk (*). You cannot use the wildcard asterisk (*). – All the information contained in the SAP R/3 database if the information you specified does not exist. DataSource The object that makes data for a business unit available to Business Chapter 18.. The search tool lists all the InfoPackages having this name. Using Business Information Warehouse 167 . The list is displayed in the language set in the twsxa_lang option.

Creating Tivoli Workload Scheduler job with InfoPackages or process chains
Information Warehouse. A DataSource contains a number of logically-related fields that are arranged in a flat structure and contain data to be transferred into Business Information Warehouse. SourceSystem The system that is available to Business Information Warehouse for data extraction and transfer purposes. Note: If you specify any information that does not exist, the search tool lists all the information contained in the SAP R/3 database. Business Warehouse Process Chains: The SAP Pick List panel

Figure 21. The SAP Pick List panel

Click Start to get a complete list of existing Process Chains or filter your query by filling in one or more of the following fields: Name & Location group: Find Specify an SAP R/3 process chain. You can also use asterisks (*). The search tool lists all the process chains having this name.

Technical Name Specify the name that identifies the process chain. The search tool lists all the SAP R/3 process chains having this technical name. Job ID Displays the job identifier assigned by the SAP R/3 system. Possible values are: ipak_ For Infopackges pchain_ For Process Chains v Debug and Setting Options group: Trace Select to create a trace file dev_rfc in the Tivoli Workload Scheduler home directory. Ensure you delete the trace option from the job after you have performed debug procedures. The dev_rfc file can become very large and cause problems to your system.

168

IBM Tivoli Workload Scheduler for Applications: User’s Guide

Creating Tivoli Workload Scheduler job with InfoPackages or process chains
Debug Select to include additional debug information in the stdlist file of the job. v R3 Command Line group: R3 Command Line Type any flags that are valid for the SAP R/3 command line, such as the following for process chains:
-flag level_all_pchainlog -flag pchainlog_chains_only -flag enable_pchainlog_bapi_msg

and the following for InfoPackages:
-flag enable_ipaklog

v Job Options group: PChain Log (for job process chain only) Select it to retrieve the job process chain log. Possible values are: – Blank – Enabled – Disabled v Return Code Mapping group: Expression Type a logical expression that defines the success condition. Allowed operators are comparison operators (=, != or <>, >, >=, <, <=) and logical operators (AND, OR, NOT). For example, the expression RC>= 6 indicates that a return code greater than or equal to 6 means the task is successful.

Displaying details about Business Warehouse InfoPackages
To display details about a Business Warehouse Info Package, perform the following steps: 1. In the Work with engines pane, select an engine → database list → job definition list. The list of job pane displays the available jobs. 2. Double-click the SAP R/3 job whose details you want to display. The Properties - Job Definition panel is displayed. The panel consists of the following: v “General page” on page 165 v “Task page” on page 166 3. In the Task page, click Details. The Details panel is displayed. It contains all the information relevant for the job. 4. Click OK. The Properties- Job Definition dialog is displayed. 5. Click OK.

Task string to define Business Warehouse InfoPackages and process chains
This section describes the task string parameters that control the running of the Business Warehouse InfoPackages and process chains jobs. You must specify them in the following places when you define their associated Tivoli Workload Scheduler jobs: v If you use the Job Scheduling Console, in the Command field of the Task page of the Properties - Job Definition panel. You must select Other as task type and not SAP for the new job definition.

Chapter 18. Using Business Information Warehouse

169

Task string to define InfoPackages and process chain jobs
v As arguments of the scriptname keyword in the job definition statement, if you use the Tivoli Workload Scheduler command line. v As arguments of the JOBCMD keyword in the JOBREC statement in the SCRIPTLIB of Tivoli Workload Scheduler for z/OS, if you are scheduling in an end-to-end environment. The string syntax is the following: Job definition syntax
-job job_name -i ipak_ pchain_

-debug

-trace

-flag

imm immed

-flag

enable_pchainlog disable_pchainlog

-flag

enable_ipaklog disable_ipaklog

-flag

level_all_pchainlog level_n_pchainlog

-flag

pchainlog_chains_only pchainlog_chains_and_failed_proc pchainlog_complete

-flag

enable_pchainlog_bapi_msg disable_pchainlog_bapi_msg

1
-flag enable_pchain_details disable_pchain_details -flag pchain_rerun pchain_restart pchain_refresh

The parameters are described in Table 35.
Table 41. Task string parameters for SAP R/3 jobs Parameter -job job_name Description The name of the task to be run. It is either an InfoPackage technical field name, or a process chain name. This parameter is mandatory. One of the following: ipak_ pchain_ -debug Target job is an InfoPackage Target job is a process chain U GUI Support U

-i {ipak_ | pchain_}

U

Turns on the most verbose r3batch trace. This option is for debugging the extended agent and should not be used in standard production.

170

IBM Tivoli Workload Scheduler for Applications: User’s Guide

Task string to define InfoPackages and process chain jobs
Table 41. Task string parameters for SAP R/3 jobs (continued) Parameter -trace Description Turns on the SAP RFC trace. When you use this option, a trace file is created in the Tivoli Workload Scheduler methods directory. In UNIX, this trace file is called dev_rfc. In Windows, the file is called rfcxxxxx_xxxxx.trc. This option is for debugging the extended agent and should not be used in standard production. Ensure you delete the trace option from the job after you have performed debug procedures. The trace file can become very large and unmanageable. -flag {imm | immed} -flag {enable_pchainlog | disable_pchainlog} Specifies to launch job immediately, meaning that if there are no spare work processes, the job fails. Enables or disables retrieval and appending of the process chain job log in the Tivoli Workload Scheduler stdlist. Disable if the size of the log affects performance. A related configuration option can be set for this purpose at a more general level. See Table 33 on page 106. Enables or disables retrieval and appending of the InfoPackage job log in the Tivoli Workload Scheduler stdlist. Disable if the size of the log affects performance. A related configuration option can be set for this purpose at a more general level. See Table 33 on page 106. Allows for retrieval of process chain logs down to the process chain level you specify. level_n_pchainlog Specifies that the process chains are logged down to, and including, the level represented by number n. level_all_pchainlog Specifies that all the process chains are logged. The default is level_1_pchainlog. A related configuration option can be set for this purpose at a more general level. See Table 33 on page 106. U U GUI Support U

-flag {enable_ipaklog | disable_ipaklog}

-flag {level_n_pchainlog | level_all_pchainlog}

Chapter 18. Using Business Information Warehouse

171

Task string to define InfoPackages and process chain jobs
Table 41. Task string parameters for SAP R/3 jobs (continued) Parameter -flag {pchainlog_chains_only | pchainlog_chains_and_failed_proc | pchainlog_complete} Description Specifies what type of process chain-related logs will be retrieved. pchainlog_chains_only Only the process chains are logged. pchainlog_chains_and_failed_proc In addition to the process chains, all the processes that failed are also logged. pchainlog_complete The process chains and all processes are logged. The default is pchainlog_complete. A related configuration option can be set for this purpose at a more general level. See Table 33 on page 106. -flag {enable_pchainlog_bapi_msg | disable_pchainlog_bapi_msg} Enables or disables retrieval of additional messages from the BAPI calls from the SAP Business Warehouse process chains and appends them to the Tivoli Workload Scheduler stdlist. Enables or disables the display of details about the process chain job. A related configuration option can be set for this purpose at a more general level. See Table 33 on page 106. Determines the action that Tivoli Workload Scheduler performs when you rerun a job that submits a process chain. pchain_rerun Tivoli Workload Scheduler creates another process chain instance and submits it to be run again. pchain_restart Tivoli Workload Scheduler restarts the original process chain from the failing processes to the end. pchain_refresh Tivoli Workload Scheduler updates the status and details of the original process chain. For more details about rerunning a process chain, refer to “Rerunning a process chain job” on page 138. U GUI Support

1 -flag {enable_pchain_details | 1 disable_pchain_details} 1 1 1 -flag {pchain_rerun | pchain_restart | 1 pchain_refresh} 1 1 1 1 1 1 1 1 1 1 1 1

U

Note: Typically, the -debug and -trace options are for debugging the extended agent and should not be used in standard production. The following is an example for an InfoPackage job whose technical field name is ZPAK_3LZ3JRF29AJDQM65ZJBJF5OMY:
-job ZPAK_3LZ3JRF29AJDQM65ZJBJF5OMY -i ipak_

172

IBM Tivoli Workload Scheduler for Applications: User’s Guide

Chapter 19. Using the BDC Wait option
With the Batch Data Collector (BDC) Wait option, you can specify that an R/3 job launched by Tivoli Workload Scheduler is not to be considered complete until all of its BDC sessions have completed. This prevents other Tivoli Workload Scheduler jobs that are dependent on the R/3 job from being launched until all of the related BDC sessions for the R/3 job have ended. To make use of the option, an R/3 job must write informational messages in its job log. This can be done by modifying the SAP function module BDC_OPEN_GROUP as follows:
FUNCTION BDC_OPEN_GROUP. ... CALL ’BDC_OPEN_GROUP’ ID ’CLIENT’ FIELD CLIENT ID ’GROUP’ FIELD GROUP ID ’USER’ FIELD USER ID ’KEEP’ FIELD KEEP ID ’HOLDDATE’ FIELD HOLDDATE ID ’DESTINATION’ FIELD DEST ID ’QID’ FIELD QID ID ’RECORD’ FIELD RECORD ID ’PROG’ FIELD PROG. * IF SY-SUBRC EQ 0. BQID = QID. BUSER = SY-MSGV1. BGROUP = GROUP. * CALL FUNCTION ’DB_COMMIT’. CALL FUNCTION ’ENQUEUE_BDC_QID’ EXPORTING DATATYP = ’BDC ’ GROUPID = BGROUP QID = BQID EXCEPTIONS FOREIGN_LOCK = 98 SYSTEM_FAILURE = 99. IF SY-SUBRC EQ 0. message i368(00) with ’BDCWAIT: ’ qid. ENDIF. ENDIF. * PERFORM FEHLER_BEHANDLUNG USING SY-SUBRC. * * ENDFUNCTION.

Note: The actual parameters of the call of the C function (CALL ‘BDC_OPEN_GROUP’ ID ...) might vary depending on the SAP release. With this approach, you obtain a global change in your R/3 system. 1 1 1 1 1 The completion status of an R/3 job launched by Tivoli Workload Scheduler is based on the value you set for the bdc_job_status_failed option. By default, this option is set to ignore, meaning that the job is considered successfully completed when the BDC sessions are finished, regardless of their success or failure. For details about the bdc_job_status_failed option, refer to Table 35 on page 131.

© Copyright IBM Corp. 2003, 2008

173

174

IBM Tivoli Workload Scheduler for Applications: User’s Guide

Implementing job interception This section describes what action you need to take to implement job interception. Define a Tivoli Workload Scheduler job to periodically collect the intercepted SAP R/3 jobs.0 interface.0 interface. This job can be referred to as the interception collector job. you need to define a Tivoli Workload Scheduler job that uses the SAP R/3 interception collector task to collect and restart them. Collecting intercepted jobs periodically Because intercepted jobs remain in the scheduled status until they are re-launched. which only considers jobs whose start conditions have been fulfilled due to time or SAP event restrictions. Job interception and parent-child features This chapter describes how the job interception and parent-child features of BC-XBP 2. 3. 2. 4. 2008 175 .0 are supported by Tivoli Workload Scheduler for Applications. run ABAP report INITXBP2. Install the BC-XBP 2. It enables Tivoli Workload Scheduler to have a very sophisticated control over the jobs launched by SAP R/3 users from the SAP graphical interface. Activating the job interception feature Refer to SAP note 604496 to know if your SAP R/3 system already has the BC-XBP 2.Chapter 20. when the start conditions of an SAP R/3 job are fulfilled). Implement the following steps to set up Tivoli Workload Scheduler to handle job interception in an SAP R/3 environment: 1. This is due to the design of the interception mechanism. 2003. and when the job parameters match the criteria. Note: Jobs launched by Tivoli Workload Scheduler. 5. denoting that the job has been intercepted. If Tivoli Workload Scheduler has been set up to handle job interception. This report shows you the current status of the job interception and parent-child features. Activate the job interception feature of the BC-XBP 2. it periodically runs its own job to retrieve a list of intercepted jobs and reschedules them. The job interception mechanism becomes active when the SAP R/3 job scheduler is about to start an SAP R/3 job (that is. creator. the SAP R/3 job is set back to the scheduled status and is marked with a special flag. client) against the entries in the SAP R/3 table TBCICPT1. To enable the job interception feature. cannot be intercepted. or by any other external scheduler using the BC-XBP interface. It checks the job parameters (job name. Specify interception criteria in the SAP R/3 system.0 interface. and allows you to toggle the status of both features.0 interface. © Copyright IBM Corp. Job interception Job interception is a feature of the BC-XBP 2. or which SAP R/3 support package you need to install to enable it. Specify interception criteria in Tivoli Workload Scheduler.

Right-click the job and select Table Criteria. use the following syntax: CPUNAME#JOBNAME SCRIPTNAME "TWShome/methods/r3batch -t HIJ -c CPUNAME" DESCRIPTION "Collects intercepted jobs on SAP XA CPUNAME" STREAMLOGON TWSuser RECOVERY STOP CPUNAME JOBNAME TWShome –t HIJ TWSuser The name of the extended agent workstation. All the other jobs are run normally. HIJ stands for Handle Intercepted Jobs. You can maintain the entries in this table by using transaction se16 and setting the following: v Client number v Job mask v User mask Setting interception criteria on Tivoli Workload Scheduler In Tivoli Workload Scheduler. and launches them again according to a template. 2. Only jobs that match the criteria of this table are intercepted.Collecting intercepted jobs periodically To define a Tivoli Workload Scheduler job that intercept jobs in scheduled status. The name of the Tivoli Workload Scheduler user that launches the access method. 176 IBM Tivoli Workload Scheduler for Applications: User’s Guide . when their start conditions are fulfilled. see “Using template files” on page 177. for example. The Table Criteria panel opens. every 10 minutes. Setting interception criteria on the SAP R/3 system On SAP R/3. The fully qualified path to your Tivoli Workload Scheduler installation. The name of the Tivoli Workload Scheduler job. The incerception collector job runs at periodical intervals.” Template files (optional) For details about how you create template files. see “Setting SAP R/3 table criteria using the Job Scheduling Console. It retrieves all the jobs that have been intercepted since the last run of the interception collector. the interception criteria are held in table TBCICPT1. You can set these using the Job Scheduling Console. In the Work with engines pane. perform the following steps: 1. select an engine → database list → job definition list. The list of job pane displays the available jobs. Setting SAP R/3 table criteria using the Job Scheduling Console To set table criteria on an SAP R/3 job using the Job Scheduling Console. The SAP R/3 task type to intercept jobs in scheduled status. interception criteria are defined and used by setting: Table criteria For details about how you set table criteria.

Job Creator Specify a filter to match a set of SAP R/3 job creator. Job Name Specify a filter to match a set of SAP R/3 jobs. Click OK. The Table Criteria panel The panel consists of the following: Client The client workstation of the SAP R/3 job. For more information about template files. Delete To delete a new interception criteria. 4. specify the template file that contains instructions for the interception collector about how to run the intercepted SAP R/3 job under control of Tivoli Workload Scheduler. Using template files: A template is a file with extension .Setting SAP R/3 table criteria Figure 22. The template file contains instructions for the interception collector about how to run | | | Chapter 20.jdf located in the same directory as the interception criteria file (TWShome/methods/r3batch_icp). Use the * (asterisk) to match a set of jobs.” 3. Job interception and parent-child features 177 . Select a row To modify an interception criteria. | | | | | Job Template Optionally. see “Using template files. Use the * (asterisk) to match a set of jobs. Perform one of the following actions: Add To add a new interception criteria.

Thus. the following instructions are used: alias=SAP_$RUN_$JOBNAME_$JOBCOUNT This means that the intercepted SAP R/3 jobs are to be restarted immediately. 3. due to the absence of the at= job option. From the default template file. and the name and ID of the SAP R/3 job. 2. From the default instruction set. if an existing template is specified in the interception criteria file. if the template is specified in the interception criteria file but does not exist. the current run number of the interception collector.Setting SAP R/3 table criteria | | | | | | | | | | | | | | | | | | | | | | the intercepted SAP R/3 job under control of Tivoli Workload Scheduler. The Table Criteria panel The interception criteria file in Tivoli Workload Scheduler contains the following entry: 178 IBM Tivoli Workload Scheduler for Applications: User’s Guide . Its syntax corresponds to the syntax of docommand in conman. the instruction set for restarting an intercepted SAP R/3 job is retrieved in the following order: 1. a template file named default. if the default template file does not exist. or if the template is not specified in the interception criteria file.jdf does not exist. From the template file. Their Tivoli Workload Scheduler names are composed of the string SAP_. Job interception example: The interception criteria table on SAP R/3 contains the following entry: | | | | | | Figure 23. If default.jdf is used. If the user template file is empty. You can use any text editor to maintain this file.

The Table Criteria panel The template file at1700. the template: alias=ICP_$RAND_$JOBNAME_$JOBCOUNT_$CLIENT. Placeholders for job interception template files Placeholder $CPU $CLIENT $JOBNAME $JOBCOUNT $USER $JOBNUM $RUN $SCHED $RAND Description Name of the extended agent workstation on which the interception collector runs. will be intercepted. The interception collector restarts the jobs using the instructions from the template file at1700.at=1700 This implies that all jobs. Name of the user who launched the SAP R/3 job. Job number of the interception collector. due to the alias command. Job interception and parent-child features 179 . Job ID of the intercepted SAP R/3 job. started in client 000 by SAP R/3 users whose user name begins with fa. Table 42.jdf contains the following entry: alias. Name of the intercepted SAP R/3 job. Client number of the intercepted SAP R/3 job. They are listed in Table 42. Schedule name of the interception collector.Setting SAP R/3 table criteria | | | | | | | | | | | | | | | | | | | | | | | | | | | | Figure 24.jdf. The SAP R/3 jobs are restarted at 17:00 with a random name. Using placeholders: In the template files you can use a number of placeholders that are replaced by the interception collector at run time. Random number.at=1000 Chapter 20. Thus. Current run number of the interception collector.

Tivoli Workload Scheduler considers an SAP R/3 job as finished only after all its child jobs have terminated. The BC-XBP 2. In this case. Before BC-XBP 2. The status of the Tivoli Workload Scheduler job remains as EXEC while the parent job or any of its child jobs are running. The joblogs of the child jobs are appended in the Tivoli Workload Scheduler stdlist after the joblog of the parent job. 180 IBM Tivoli Workload Scheduler for Applications: User’s Guide . which you can also use to toggle the status of job interception. for example. When the parent-child feature is active. an SAP R/3 job dynamically spawns a number of other jobs. The parent-child feature In some situations. The status of the Tivoli Workload Scheduler job becomes SUCC if the parent job and all child jobs terminate successfully. use the INITXBP2 ABAP report. Note: The parent-child feature can interfere with job interception because. the Tivoli Workload Scheduler job remains in the EXEC status until the intercepted child job has been relaunched and has terminated. because the business process does not usually end with the termination of the initial job (parent job). but with the termination of all subjobs (child jobs). Prominent examples are the mass activity jobs of the SAP R/3 FI-CA component. to distribute the workload to the free application servers. and so it is now possible to track them. To activate this feature.0. although the parent job cannot be intercepted. If any of the jobs terminated with an error. together with their names and IDs.Setting SAP R/3 table criteria | | | instructs the interception collector to restart the SAP R/3 job named DEMO_JOB with job ID 12345678 on client 100 at 10:00 as Tivoli Workload Scheduler job ICP_1432_DEMO_JOB_12345678_100. it was difficult for external schedulers to handle this situation.0 interface allows you to determine whether a job has launched subjobs. any of its child jobs can be intercepted if they match the interception criteria. the status of the Tivoli Workload Scheduler job becomes ABEND.

To do this. 2003. For details about the Tivoli Workload Scheduler calendar definitions.| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Chapter 21. Using the r3batch export function Use the export function to access and download factory calendars that are available in an SAP R/3 system. Your Tivoli Workload Scheduler and SAP R/3 calendars are now synchronized. To keep the Tivoli Workload Scheduler and SAP R/3 calendar definitions synchronized and avoid duplicating data maintenance in the two environments. The main purpose of this export function is to create an output file that can be used by the composer to synchronize Tivoli Workload Scheduler calendars with existing SAP R/3 factory calendars. use the r3batch export function to export the SAP R/3 calendar definitions into a file whose format is compatible with the Tivoli Workload Scheduler composer command line. from twshome/methods (where twshome is the complete path where you installed Tivoli Workload Scheduler) enter the following command: Command syntax -r3batch -t RSC -c cpu_name -. refer to the Tivoli Workload Scheduler Reference Guide. To export an SAP R/3 calendar.″ -calendar_ID calendarID -getworkdays -year_from yyyy -year_to yyyy -getfreedays -tws_name tws_cal_name -tws_description tws_cal_desc | © Copyright IBM Corp. 2008 181 . Based on the parameters you specify. to import the calendar definitions into the Tivoli Workload Scheduler database. integrating the calendar definitions from SAP R/3 into Tivoli Workload Scheduler. to add the exported calendar definitions to the Tivoli Workload Scheduler database. Exporting SAP R/3 factory calendars This chapter describes how to export SAP R/3 factory calendars into a file whose format can be processed by the Tivoli Workload Scheduler composer command line. Business scenario You might want to configure your Tivoli Workload Scheduler scheduling activities based on the schedule calendar in your SAP R/3 system. you create a file that contains only the SAP R/3 calendar definitions that meet your scheduling requirements. you can schedule to export the calendar definitions from SAP R/3 and import them to Tivoli Workload Scheduler on a regular basis using a dedicated job. Use this file as input for the composer add command.

which consists of two alphanumeric characters. the default Tivoli Workload Scheduler name for an exported calendar. In this way. This parameter is required. whose identifier is 04. This parameter is optional. This parameter is required. The identifier of the SAP R/3 calendar. These parameters are optional and mutually exclusive. -year_to yyyy The year of the calendar when to stop exporting dates. If the description contains blanks. the default is getworkdays. in this case RSC (Retrieve SAP R/3 Calendars). where: XX calendarID Corresponds to WK if the calendar includes only working days or FR if the calendar includes only non-working days. -tws_description tws_cal_desc The description of the Tivoli Workload Scheduler calendar. in the format yyyy. The SAP R/3 system must be configured as a workstation to Tivoli Workload Scheduler. in the format yyyy. You can specify up to eight alphanumeric characters. 182 IBM Tivoli Workload Scheduler for Applications: User’s Guide .Using r3batch export function | -filename output_filename ″ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Where: -t RSC The identifier of the task to be performed. If you do not specify either. that includes only working days. It is stored in the output file. You can specify up to 120 alphanumeric characters. -filename output_filename The name of the output file that is to contain the calendar definitions. It is stored in the output file. This parameter is required. -c cpu_name The CPU name of the SAP R/3 system where the calendar data to export resides. This file is written in a scheduling language that can be processed by the composer when you add the calendar data to the Tivoli Workload Scheduler database. Each date of a non-working day is stored in the output file. -year_from yyyy The year of the calendar from when to start exporting dates. -tws_name tws_cal_name The Tivoli Workload Scheduler name for the exported SAP R/3 factory calendar. This parameter is required. is SAPWK_04. Specify getfreedays to create the Tivoli Workload Scheduler calendar definition based on the holidays of the SAP R/3 calendar. it must be enclosed between single quotes. each date of a working day is stored in the output file. -getworkdays | -getfreedays Specify getworkdays to create the Tivoli Workload Scheduler calendar definition based on the working days of the SAP R/3 calendar. -calendar_id calendarID The identifier of the SAP R/3 calendar to be exported. the default is SAPXX_calendarID. This parameter is optional. This parameter is required. For example.

.dat file exported in the previous example.. it is overwritten.dat. The following is an example of an SAP R/3 factory calendar export command: r3batch -t RSC -c tivoli10 -. Exporting SAP R/3 factory calendars 183 . with its complete path. where tws_name is the value you set for the tws_name parameter. If the path you specify does not exist. considering only working days. You can specify up to the maximum characters allowed by your operating system. to import the tws_calendar_01. For example... and the description written in the output file is TWS SAP Calendar 01.dat’ " This command exports the SAP R/3 calendar named 01. enter: -add twshome/methods/my dir/tws_calendar_01. The output file is named tws_calendar_01. it must be enclosed between single quotes. the file is created in the current directory. the command returns an error message and is not performed. that resides on the SAP R/3 system named tivoli10.Using r3batch export function | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | You can specify a file name with its complete or partial path. if you do not specify any path. Otherwise.dat where twshome is the complete path where you installed Tivoli Workload Scheduler. it is created. If the name of the file contains blanks.. provided that you have the appropriate access rights." -calendar_id 01 -year_from 2007 -year_to 2010 -tws_name TWS_CAL1 -tws_description ’TWS SAP Calendar 01’ -getworkdays -filename ’my dir/tws_calendar_01. copy the file to the master workstation. This parameter is optional. The Tivoli Workload Scheduler name used for the calendar is TWS_CAL1. copy the output file from the extended agent for SAP R/3 to the master workstation and from the composer command line on the master workstation. and its content looks like the following: $CALENDAR TWS_CAL1 "TWS SAP Calendar 01" 01/02/2007 01/03/2007 01/11/2007 01/12/2007 01/22/2007 01/23/2007 01/31/2007 02/01/2007 . enter the following command: -add output_filename where ouput_filename is the name of the exported file. If another file with the same name exists. Chapter 21. From the composer command line on the master workstation.. The dates exported begin from year 2007. until year 2010.txt. stored in twshome/methods/my dir. 11/24/2010 11/25/2010 12/03/2010 12/06/2010 12/14/2010 12/15/2010 12/23/2010 12/24/2010 01/04/2007 01/15/2007 01/24/2007 02/02/2007 11/26/2010 12/07/2010 12/16/2010 12/27/2010 01/05/2007 01/16/2007 01/25/2007 02/05/2007 11/29/2010 12/08/2010 12/17/2010 12/28/2010 01/08/2007 01/17/2007 01/26/2007 02/06/2007 11/30/2010 12/09/2010 12/20/2010 12/29/2010 01/09/2007 01/18/2007 01/29/2007 02/07/2007 12/01/2010 12/10/2010 12/21/2010 12/30/2010 01/10/2007 01/19/2007 01/30/2007 02/08/2007 12/02/2010 12/13/2010 12/22/2010 12/31/2010 To import the exported calendar definitions into the Tivoli Workload Scheduler database. The default value is tws_name.

184 IBM Tivoli Workload Scheduler for Applications: User’s Guide .

As soon as the SAP event is raised. is not considered.0 (supported by SAP NetWeaver 7.| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Chapter 22. therefore a SAP event is considered raised as soon as the corresponding placeholder job has completed. with the following differences: XBP version 2. Defining internetwork dependencies and event rules based on SAP R/3 events This chapter describes how to define internetwork dependencies and event rules for Tivoli Workload Scheduler based on SAP events. To check if your SAP system provides XBP 3. for each SAP event to be checked. Internetwork dependencies are dependencies checked by the extended agent workstation to which they belong. To define SAP events as internetwork dependencies. 2003. a placeholder SAP job is created. As a prerequisite. an SAP event raised before the internetwork dependency is created. Note: Because an SAP event history is ignored. therefore.0. or later) Only the SAP events stored in the SAP event history table are considered by Tivoli Workload Scheduler to check for internetwork dependencies resolution. run reorganization tasks against the SAP event history. XBP versions 2. If your system contains the module. For more details about internetwork dependencies. the SAP extended agent commits the event and instructs Tivoli Workload Scheduler to resolve the corresponding internetwork dependency. In response to an internetwork dependency. the SAP administrator must create the appropriate event history profiles and criteria on the target SAP system. For more details about how to raise SAP events.0 SAP events can release Tivoli Workload Scheduler internetwork dependencies only if the dependencies are created or checked before the SAP event is raised. To avoid performance reduction.0 still return XBP version as 2. the SAP extended agent checks for the occurrence of the SAP event specified in the dependency.0. set © Copyright IBM Corp. 2008 185 .0 and 3. This is a dummy job whose running depends on the SAP event. invoke the transaction SE37 and search for the function module BAPI_XBP_BTC_EVTHISTORY_GET. It contains the following sections: v “Defining internetwork dependencies based on SAP events” v “Defining internetwork dependencies based on SAP events with the Job Scheduling Console” on page 188 v “Defining event rules based on SAP events” on page 189 v “Monitoring SAP events” on page 190 Defining internetwork dependencies based on SAP events Dependencies are prerequisites that must be satisfied before a job or job stream can start. An event history is ignored. XBP version 3.0 with SP 9. Note: Some SAP systems providing XBP version 3. refer to the Tivoli Workload Scheduler Reference Guide. see “Raising an SAP event” on page 145.0 are supported.

an error is issued. refer to “Committing SAP events by an external task” on page 187. if -commit is specified. without parameter. For details about the commit_dependency option. Note: With XBP version 2. use the following parameters: Table 43. 186 IBM Tivoli Workload Scheduler for Applications: User’s Guide . In this way. r3batch will ignore the XBP value returned by the SAP system. For details about the xbpversion option. If the parameter contains blanks. the event is committed. the SAP event SAPEVT is raised. In addition to this parameter. The SAP event parameter. specifying -commit. If you do not specify -commit. After its processing. where SAPWS is the name of the Extended Agent CPU that connects to the SAP background processing system where the event runs: follows SAPWS::"-evtid SAP_TEST -evtpar 12345678" The following example shows how to define an internetwork dependency based on the SAP event named SAP_TEST. enclose it between single quotes. defining two internetwork dependencies on the same SAP event might lead to an error. For example. Then you define a second internetwork dependency based on SAPEVT. GUI support U U Defines that the SAP event is committed immediately U after the internetwork dependency has been resolved.0. This parameter is required. you can set as default that the system commits internetwork dependencies immediately by specifying commit_dependency=on in the options file. Parameters to define an SAP internetwork dependency Parameter -evtid sap_event_name -evtpar sap_event_parm -commit Description The name of the SAP event.Defining internetwork dependencies based on SAP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | the xbpversion option to 3. As soon as the internetwork dependency is resolved. with the consequence that the first dependency becomes impossible to resolve. the event must be committed by running the r3batch task PI. If the name contains blanks. suppose you define an internetwork dependency for the SAP event SAPEVT. -evtid SAP_TEST -evtpar 12345678 The resulting internetwork dependency looks like the following. refer to Table 33 on page 106. Therefore. up to 32 characters. the event is not immediately committed. After this definition. To define an SAP event as an internetwork dependency. when the first job checks for the internetwork dependency. For details about the PI task. up to 64 characters. This parameter is optional. The following example shows how to define an internetwork dependency based on the SAP event named SAP_TEST with the parameter 12345678. with or without setting -commit. see Table 33 on page 106. The default is that -commit is not specified. enclose it between single quotes. The second dependency immediately commits the SAP event.

it is recommended that you run this task at the end of the working day. in this case PI (Put Information). By doing so. From a command line. Internetwork dependency definition and possible resolution Tivoli Workload Scheduler internetwork dependency resolved No No Yes Yes No Yes No Tivoli Workload Scheduler internetwork dependency specified -evtid SAP_TEST -evtid SAP_TEST -evtid SAP_TEST -evtid SAP_TEST -evtid SAP_TEST -evtpar 12345678 -evtid SAP_TEST -evtpar 12345678 -evtid SAP_TEST -evtpar 12345678 SAP event raised in SAP system none END_OF_JOB SAP_TEST SAP_TEST SAP_TEST SAP_TEST SAP_TEST SAP event parameter none none none 12345678 none 12345678 ABCDEFG Committing SAP events by an external task SAP events defined as Tivoli Workload Scheduler internetwork dependencies. In this table. You can modify this default by specifying the -commit parameter. Otherwise. Chapter 22. For this reason. Table 44. internetwork dependencies that are already resolved are not reset and the objects depending on them are not blocked until they are resolved again. where SAPWS is the name of the Extended Agent CPU that connects to the SAP background processing system where the event runs: follows SAPWS::"-evtid SAP_TEST -evtpar 12345678" Table 44 shows the correspondence between the definition and possible resolution of an internetwork dependency that depends on an SAP event. enter the following command: Command syntax -r3batch -t PI -c cpu_name ″ -evtpar sap_event_parm -. you must commit the processed event by the external task Put Information (PI). This parameter is required. with or without parameters assigned. SAP_TEST is used as the event name and 12345678 or ABCDEFG as the event parameter. Defining internetwork dependencies and event rules based on SAP R/3 events 187 . if you leave the default. by default are not automatically committed after their processing. The PI task commits all the processed events that meet the given criteria.Defining internetwork dependencies based on SAP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | -evtid SAP_TEST -commit The resulting internetwork dependency looks like the following.″ -t CE -evtid sap_event_name Where: -t PI The identifier of the task to be performed.

-evtpar sap_event_parm The parameter of the SAP event running on the background processing system. The following is an example of how to commit the SAP event named SAP_TEST. This parameter is required. and return to the Job Stream Editor. running on the background processing system named tivoli10: r3batch -t PI -c tivoli10 -. in this case CE (Commit Event). all the SAP events with the name you specified. 4. If you do not specify it. 2. If the parameter contains blanks. Run a list of job streams and double-click the job stream you want to manage. enter the parameters to define the internetwork dependency. Click OK to save and close the panel. 7. There is no visible result when you click Add Link. For a description of the parameters allowed. enclose it between single quotes. This parameter is required. 3. You have created the dependency. If the name contains blanks. In the Network Agent field. are committed on the target system. refer to Table 43 on page 186. with or without a parameter. enter the CPU name of the SAP background processing system where the event runs. You must click the dependency icon you want to link. 5. select Add Dependency on Internetwork." -t CE -evtid SAP_TEST -evtpar 1234567" Defining internetwork dependencies based on SAP events with the Job Scheduling Console To define an SAP event as an internetwork dependency with the Job Scheduling Console. This parameter is optional. In the Actions list. hold down the mouse button and drag the link to the job icon. The Job Stream Editor panel opens. perform the following steps: 1. -t CE The identifier of the task to be performed.Defining internetwork dependencies based on SAP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | -c cpu_name The CPU name of the SAP background processing system where the event is run. To link the dependency to the job you want. 6. The Internetwork Dependency panel opens. 188 IBM Tivoli Workload Scheduler for Applications: User’s Guide . in the Actions list select Add Link. Save the Job Stream Editor panel. enclose it between single quotes. with parameter 1234567. In the Dependency field. This parameter is required. -evtid sap_event_name The name of the SAP R/3 event running on the background processing system.

Defining internetwork dependencies and event rules based on SAP R/3 events 189 . percentage (%). the time frame of its validity. The definition of an event rule correlates events and triggers actions. only the SAP events that are stored in the event history table are considered by Tivoli Workload Scheduler. if any. For example. Notes: 1. or question mark (?). define that an event belonging to an SAP system is monitored by one extended agent workstation only.Defining internetwork dependencies based on SAP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Defining event rules based on SAP events A scheduling event rule defines a set of actions to run when specific event conditions occur. An event rule is identified by a rule name and by a set of attributes that specify if the rule is active. you can use either of the following: The composer command line You edit the rules with an XML editor of your choice. If the same SAP event is monitored by more than one extended agent. If you are using XBP 3. use the backslash (\) immediately before the special character. and other information required to decide when actions are triggered. specify it as SAP\?PARM. As a best practice. specify it as SAP\*NAME. see the IBM Tivoli Workload Scheduler: Reference Guide. or question mark (?). If you are using the Tivoli Dynamic Workload Console and you want to specify a parameter that contains the special character asterisk (*). use the backslash (\) immediately before the special character. if the parameter of the SAP event is SAP?PARM. It includes information related to the specific events (eventCondition) that the rule must detect and the specific actions it is to trigger upon their detection or timeout (ruleAction). Wildcards are not allowed. If you are using the Tivoli Dynamic Workload Console and you want to specify an event name that contains the special character asterisk (*). To define event rules. you might either be notified Chapter 22. For example. For details about how to use the composer to define event rules. Wildcards are not allowed. 2. The SAP event is identified by the following information: Event name The name of the SAP event. all the extended agents whose name matches the pattern will monitor the specified event. If you specify a pattern with the wildcard asterisk (*). percentage (%). if the name of the SAP event is SAP*NAME. refer to the Tivoli Dynamic Workload Console online help. The Tivoli Dynamic Workload Console For details. Extended agent workstation The name of the extended agent workstation responsible for the event monitoring. Complex rules might include multiple events and multiple actions. Event parameter The parameter associated with the SAP event.0.

to make the changes effective you must stop and restart the agent. that event is monitored by Tivoli Workload Scheduler. Stops monitoring SAP events. For UNIX only. refer to “Raising an SAP event” on page 145.Defining internetwork dependencies based on SAP | | | | | | | | | | | | | 1 1 1 1 | | | | | | | | | | | | | | | | | | | | | | | | | Where: start | stop The action to perform: start stop Starts monitoring SAP events.0. If you modify the r3batch option files. for example when a new operation mode is activated.4): twshome/methods/SAPPlugin/SapMonitorPlugIn. If you modify the extended agent configuration in the r3batch option files. This type of event cannot be modified by the user. Events defined by the user The events that are triggered by ABAP or external processes. to make the changes effective you must stop and restart the extended agent monitoring processes with the following command. multiple times for the same event occurrence or the first extended agent that notifies the event occurrence makes that event unavailable to the other extended agents. Monitoring SAP events Whenever you define an event rule based on an SAP event in your Tivoli Workload Scheduler plan. stop the Tivoli Workload Scheduler WebSphere Application Server and copy the following file (located on the system where you installed Tivoli Workload Scheduler for Applications 8. for example when a process triggers an SAP event to signal that external data has arrived and must be read by the SAP system. If the master domain manager is connected to the Tivoli Dynamic Workload Console. stop and restart also the Tivoli Dynamic Workload Console Application Server. Prerequisite to defining event rules based on SAP To be able to define event rules based on one or more SAP events. Tivoli Workload Scheduler monitors two types of SAP event: Events defined by the SAP system The events that are triggered automatically by system changes. this command must be entered by the owner of the Tivoli Workload Scheduler installation: Command syntax r3evman start stop 190 IBM Tivoli Workload Scheduler for Applications: User’s Guide . or later.jar to the following directory of the master domain manager and of its backup nodes: twshome/eventPlugIn For the changes to take effect. For details about how to trigger events by external processes. 3. stop and restart the Tivoli Workload Scheduler WebSphere Application Server. Monitoring SAP events is allowed only if you use XPB version 3.

.. Suppose that the following SAP events were raised on the SAP system: Table 45. the event is committed on the SAP system and its state changed to C (Confirmed). Chapter 22. 20070925 16:00 EVENT PROCESS STATE STATE N OK COUNT OF JOBS 4 SAP_TEST ABCDEF If the notification is successfully sent. Also. .Defining internetwork dependencies based on SAP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | SAP events matching criteria The SAP events specified in the event rule are matched with the events raised in the SAP system. The information collected about the matching SAP event is sent by the r3evmon process to Tivoli Workload Scheduler. the SAP event name must be the same as the ID of the events raised in the SAP system whose state is N (New). Defining internetwork dependencies and event rules based on SAP R/3 events 191 .. according to the following criteria.. the event state must be N (New). History table of the SAP events raised EVENT EVENT GUID ID 1234 2345 3456 4567 EVENT PARM EVENT EVENT SERVER TIMESTAMP ... . the event is committed on the SAP system and its state changed to C (Confirmed). Depending on the parameters you set: The SAP event name and parameter are specified in the event rule To match. For example... The parameters of the SAP events. If the notification is successfully sent. the SAP event name and parameter must be the same as the event ID and event parameter raised in the SAP system.cfg is created on GENIUS. whether specified or not. The information collected about all the matching SAP events is sent by the r3evmon process to Tivoli Workload Scheduler.. It contains the following !R3EVENT keyword: !R3EVENT 0008SAP_TEST0006ABCDEF Monitoring of the SAP_TEST event with parameter ABCDEF is automatically started. you define an event rule in your Tivoli Workload Scheduler plan based on the following SAP event: SAP event name SAP event parameter Extended agent workstation SAP_TEST ABCDEF GENIUS According to these settings. Each event successfully notified is committed on the SAP system and its status changed to C (Confirmed). Only the SAP event name is specified in the event rule To match.. 20070925 13:00 20070925 14:00 20070925 15:00 20070925 16:00 EVENT PROCESS STATE STATE C N N N OK OK OK OK COUNT OF JOBS 1 2 3 4 SAP_TEST ABC123 SAP_TEST ABCD SAP_TEST SAP_TEST ABCDEF Only the following SAP event is notified to Tivoli Workload Scheduler: Table 46. a file named GENIUS_r3evmon. SAP events with a different parameter or without any parameter are ignored. . are not taken into account. SAP event matching with the event rule defined EVENT EVENT GUID ID 4567 EVENT PARM EVENT EVENT SERVER TIMESTAMP .

. SAP events matching with the event rule defined EVENT EVENT GUID ID 2345 3456 4567 EVENT PARM EVENT EVENT SERVER TIMESTAMP . you restrict the use of certain SAP events to specific users.. +CUSTOM=SAP_USA@ Specifies that the user can use only the SAP events whose ID begins with SAP_USA... assume that you want your USA department to manage only the SAP events whose ID begins with SAP_USA. . 192 IBM Tivoli Workload Scheduler for Applications: User’s Guide ... define the CUSTOM keyword for the EVENT object as follows: EVENT PROVIDER=@ +CUSTOM=SAP_USA@ ACCESS=USE where: PROVIDER=@ Specifies that the user can use the events coming from any provider. 20070925 13:00 20070925 14:00 20070925 15:00 20070925 16:00 EVENT PROCESS STATE STATE C N N N OK OK OK OK COUNT OF JOBS 1 2 3 4 SAP_TEST ABC123 SAP_TEST ABCD SAP_TEST SAP_TEST ABCDEF Only the following SAP events are notified to Tivoli Workload Scheduler: Table 48. Suppose that the following SAP events were raised on the SAP system: Table 47.Defining internetwork dependencies based on SAP | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | For example. 20070925 14:00 20070925 15:00 20070925 16:00 EVENT PROCESS STATE STATE N N N OK OK OK COUNT OF JOBS 2 3 4 SAP_TEST ABCD SAP_TEST SAP_TEST ABCDEF Each event whose notification is successfully sent is committed on the SAP system and its state changed to C (Confirmed). you can filter the SAP events that can be used to define event rules. you define an event rule in your Tivoli Workload Scheduler plan based on the following SAP event: SAP event name Extended agent workstation SAP_TEST GENIUS According to these settings.. a file named GENIUS_r3evmon. By doing so. . For example. . ....cfg is created on GENIUS. It contains the following !R3EVENT keyword: !R3EVENT 0008SAP_TEST Monitoring of the SAP_TEST event is automatically started.. and your Italy department to manage all events except those beginning with SAP_USA.. This keyword applies only to the SAP provider (SapMonitor). . Setting a filter for SAP events in the security file In the security file. In the security file that defines the user access for the USA department. History table of the SAP events raised EVENT EVENT GUID ID 1234 2345 3456 4567 EVENT PARM EVENT EVENT SERVER TIMESTAMP ...

For more details about the security file and how to set up user authorizations. ~CUSTOM=SAP_USA@ Specifies that the user can use all SAP events. define the CUSTOM keyword for the EVENT object as follows: EVENT PROVIDER=@ ~CUSTOM=SAP_USA@ ACCESS=USE where: PROVIDER=@ Specifies that the user can use the events coming from any provider. This keyword applies only to the SAP provider (SapMonitor). In the security file that defines the user access for the Italy department. except those whose ID begins with SAP_USA. Chapter 22.Defining internetwork dependencies based on SAP | | | | | | | | | | | | | | ACCESS=USE ACCESS=USE Sets the user access to the object to USE. see the IBM Tivoli Workload Scheduler: Reference Guide. Sets the user access to the object to USE. Defining internetwork dependencies and event rules based on SAP R/3 events 193 .

194 IBM Tivoli Workload Scheduler for Applications: User’s Guide .

therefore have different IDoc message types. Business scenario You connected your Internet sales application to your SAP Customer Relationship Management (CRM) system. the action you associated with it (for example. in Tivoli Workload Scheduler for Applications.1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 Chapter 23. which receives the orders as incoming IDocs. running a job) is performed. 2008 195 . In Tivoli Workload Scheduler. you can monitor Intermediate Document (IDoc) records in SAP systems and forward events to the Tivoli Workload Scheduler’s event integration framework. 2003. You define an event condition that contains the criteria that the IDocs must match to be forwarded to Tivoli Workload Scheduler. Internet Order System order IDocs SAP CRM Tivoli Workload Triggers immediate import Scheduler for high priority orders Monitors IDocs IDoc tables 1 1 1 1 Figure 25. You want the emergency orders to be imported into the CRM system directly. and the ordinary orders to be processed in batch mode. v “Examples of event rules based on IDocs” on page 201 shows some examples. you define an event rule that monitors the IDoc message types corresponding to emergency orders and sends an event to Tivoli Workload Scheduler. Defining event rules based on IDoc records With Tivoli Workload Scheduler for Applications. In this chapter: v “Business scenario” provides a real-life example of how you can use event rules based on IDocs in your business environment. v “Creating event rules based on IDocs” on page 196 describes the fields you can specify as matching criteria for the IDoc monitoring process. Managing high priority IDocs overview © Copyright IBM Corp. To do this. When the event condition occurs. The orders are classified as emergency and ordinary. you define a job to be released when this type of event is received and is linked to an SAP job that runs an import ABAP report for these specific types of IDocs.

Table 49. For a general explanation about how to use the composer to define event rules. specify the fields to be used as matching criteria during IDoc monitoring. refer to “Events matching criteria. Tivoli Workload Scheduler fields used to define event rules Composer property SAPClient SAPIDocStatus SAPDirectionIDocTransmission SAPReceiverPort SAPReceiverPartnerFunction SAPReceiverPartnerType SAPReceiverPartnerNumber SAPSenderPort SAPSenderPartnerType SAPSenderPartnerFunction SAPSenderPartnerNumber SAPLogicalMessageType SAPNameOfBasicType SAPLogicalMessageCode SAPLogicalMessageFunction SAPTestFlag SAPOutputMode Console property SAP client Status Direction Receiver port Receiver partner function Receiver partner type Receiver partner number Sender port Sender partner type Sender partner function Sender partner number Logical message type Name of basic type Logical message code Logical message function Test flag Output mode IDoc field MANDT STATUS DIRECT RCVPOR RCVPFC RCVPRT RCVPRN SNDPOR SNDPRT SNDPFC SNDPRN MESTYP IDOCTP MESCOD MESFCT TEST OUTMOD Optionally. you can use either of the following: The composer command line You edit the rules with an XML editor of your choice.Creating event rules based on IDocs 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 Creating event rules based on IDocs To define event rules based on IDocs. Events matching criteria Table 49 lists the Tivoli Workload Scheduler fields corresponding to the fields in the IDoc record that you want to search. v IDOCEventGenerated as event type. refer to the Tivoli Dynamic Workload Console online help. see the IBM Tivoli Workload Scheduler: Reference Guide. The event condition requires: v SAPMonitor as event monitor provider. During monitoring. For details about these fields.” To create the event rules. For a list of the values you can specify in the attributeFilter name when defining the event condition. each IDoc matching the search criteria generates an event that is sent to Tivoli Workload Scheduler. The Tivoli Dynamic Workload Console For details. refer to Table 51 on page 198. you can define also correlation rules by using the fields listed in Table 50 on page 197: 196 IBM Tivoli Workload Scheduler for Applications: User’s Guide .

use the evmon_interval option. Defining event rules based on IDoc records 197 . the r3evmon process of Tivoli Workload Scheduler for Applications monitors the events related to IDoc records according to a polling rate.Creating event rules based on IDocs 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 Table 50. Chapter 23. Tivoli Workload Scheduler fields used to define correlation rules Composer property SAPIDocNumber SAPReleaseForIDoc SAPIDocType SAPReceiverAddress SAPReceiverSADRClient SAPFlagForInternationalReceiverAddress SAPReceiverCommunicationType SAPDefaultFlagForReceiverAddress SAPReceiverAddressSequentialNumber SAPReceiverLogicalAddress SAPEDIStandard SAPEDIStandardVersion SAPEDIMessageType SAPSenderAddress SAPSenderSADRClient SAPFlagForInternationalSenderAddress SAPSenderCommunicationType SAPDefaultFlagForSenderAddress SAPSenderAddressSequentialNumber SAPSenderLogicalAddress SAPReferenceToInterchangeFile SAPReferenceToMessageGroup SAPReferenceToMessage SAPEDIArchiveKey SAPIDocCreationDate SAPIDocCreationTime SAPExtension SAPEDIALESerializationField SAPOverridingInInboundProcessing SAPIDocChangeDate SAPIDocChangeTime Console property IDoc number IDoc SAP release IDoc type Receiver SADR address Receiver SADR client Receiver SADR flag Receiver SADR communication type Receiver SADR default flag Receiver SADR sequential number Receiver logical address EDI Standard EDI standard version EDI message type Sender SADR address Sender SADR client Sender SADR flag Sender SADR communication type Sender SADR default flag Sender SADR sequential number Sender logical address Interchange file reference Message group reference Message reference EDI archive key IDoc creation date IDoc creation time Extension EDI/ALE Serialization field Overriding in inbound processing IDoc last update date IDoc last update time IDoc field DOCNUM DOCREL DOCTYP RCVSAD RCVSMN RCVSNA RCVSCA RCVSDF RCVSLF RCVLAD STD STDVRS STDMES SNDSAD SNDSMN SNDSNA SNDSCA SNDSDF SNDSLF SNDLAD REFINT REFGRP REFMES ARCKEY CREDAT CRETIM CIMTYP SERIAL EXPRSS UPDDAT UPDTIM Based on the defined rule. see “Defining the common options” on page 106. To customize this polling rate. for details.

Multiple values allowed 1 Table 51. Optionally. SAP system. numeric SAPDirectionIDocTransmission IDoc direction Value can be: 1 outbound 2 inbound string numeric (0-9) Filtering allowed U Required U Wildcard allowed U Length (min-max) 1 3 U U U 1 2 U U 1 1 SAPReceiverPort Receiver port.Creating event rules based on IDocs 1 1 Table 51 lists the values you can specify as attribute filter name when defining the event condition. you receive an error message and you cannot save the rule definition. 02 as status and 2 as direction). EDI subsystem Partner function of receiver Partner type of receiver Partner number of receiver Sender port. perform the following steps: 198 IBM Tivoli Workload Scheduler for Applications: User’s Guide . If you activate the check and specify inconsistent values when defining a rule (for example. To activate the check. refer to Table 52 on page 199 and Table 53 on page 200. SAP system. Parameters of IDOCEventGenerated event type 1 1 Property name Description Type 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 SAPClient SAP client number IDoc status information SAPIDocStatus For a list of allowed numeric values. you can activate a check to prevent event rule definitions with inconsistent IDoc status list and direction. EDI subsystem Partner type of sender Partner function of sender Partner number of sender Logical message type Name of basic type Logical message code Logical message function Test flag U 1 10 SAPReceiverPartnerFunction SAPReceiverPartnerType SAPReceiverPartnerNumber string string string U U U 1 1 1 2 2 10 SAPSenderPort string U 1 10 SAPSenderPartnerType SAPSenderPartnerFunction SAPSenderPartnerNumber SAPLogicalMessageType SAPNameOfBasicType SAPLogicalMessageCode SAPLogicalMessageFunction SAPTestFlag string string string string string string string string string Value can be: 2 immediate sending 4 collected sending U U U U U U U U U U 1 1 1 1 1 1 1 1 2 2 10 30 30 3 3 1 SAPOutputMode Output Mode U 1 1 Table 52 on page 199 lists the standard outbound IDoc statuses and Table 53 on page 200 lists the standard inbound IDoc statuses.

properties file. The default value is false. In the twshome/eventPlugIn directory. acknowledgement still due Error during retransmission Control information of EDI subsystem OK Processing despite syntax error Error during syntax check of IDoc Error in dispatch level (ALE service) Error in ALE service IDoc ready for dispatch (ALE service) Error no further processing IDoc was edited Original of an IDoc which was edited Chapter 23. create the SapMonitorPlugIn. To have predictable event action results.properties to set the following configuration property: TWSPlugIn.Creating event rules based on IDocs 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1. 2. Table 52. Defining event rules based on IDoc records 199 .check = true 3.idoc. Edit SapMonitorPlugIn. Standard outbound IDoc statuses Status 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 22 23 24 25 26 27 29 30 31 32 33 Description IDoc generated Error passing data to port Data passed to port Error within control information of EDI subsystem Error during translation Translation Error during syntax check Syntax check Error during interchange Interchange handling Error during dispatch Dispatch OK Retransmission OK Interchange acknowledgement positive Interchange acknowledgement negative Functional acknowledgement positive Functional acknowledgement negative Triggering EDI subsystem OK Data transfer for test OK Error triggering EDI subsystem Dispatch OK. stop and restart the event processing server by using. when defining event rules consider using only non-transitory statuses that allow user checks.consistency. From conman. the stopeventprocessor and starteventprocessor commands.event. respectively.

Standard outbound IDoc statuses (continued) Status 34 36 37 38 39 40 41 42 Description Error in control record of IDoc Electronic signature not performed (timeout) IDoc added incorrectly IDoc archived IDoc is in the target system (ALE service) Application document not created in target system Application document created in target system IDoc was created by test transaction Table 53. you define a rule with the following attributes: Extended agent workstation SAP client number IDoc status list IDoc direction SAPCPU 001 56.60 2 (inbound) 200 IBM Tivoli Workload Scheduler for Applications: User’s Guide . Standard inbound IDoc statuses Status 50 51 52 53 54 55 56 57 58 60 61 62 63 64 65 66 68 69 70 71 73 74 Description IDoc added Application document not posted Application document not fully posted Application document posted Error during formal application check Formal application check OK IDoc with errors added Error during application check IDoc copy from R/2 connection Error during syntax check of IDoc Processing despite syntax error IDoc passed to application Error passing IDoc to application IDoc ready to be transferred to application Error in ALE service IDoc is waiting for predecessor IDoc (serialization) Error .Creating event rules based on IDocs 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 Table 52.no further processing IDoc was edited Original of an IDoc which was edited IDoc reloaded from archive IDoc archived IDoc was created by test transaction For example.

When the event condition is verified. Defining event rules based on IDoc records 201 .0" encoding="UTF-8"?> <eventRuleSet xmlns:xsi="http://www. when the rule becomes active a file named SAPCPU_r3evmon.org/2001/XMLSchema-instance" xmlns="http://www. refer to Table 69 on page 257.cfg is created on SAPCPU. It contains the following !IDOC keyword: !IDOC 0003001000556. the action defined in the rule is triggered For an explanation of the !IDOC keyword format.com/xmlns/prod/tws/1.600001200000000000000000000000000000000000000000000000000000000 IDoc monitoring is automatically started. <?xml version="1. Examples of event rules based on IDocs The following example applies to the scenario described in “Business scenario” on page 195.xsd"> <eventRule name="scenario1_IDoc" ruleType="filter" isDraft="no"> <eventCondition name="IDocEventRaised1" eventProvider="SapMonitor" eventType="IDocEventGenerated"> <scope> 001 ON SAPCU WITH 2 <scope> <filteringPredicate> <attributeFilter name="Workstation" operator="eq"> <value>SAPCPU</value> </attributeFilter> <attributeFilter name="SAPClient" operator="eq"> <value>001</value> </attributeFilter> <attributeFilter name="SAPIDocStatus" operator="eq"> <value>50</value> </attributeFilter> <attributeFilter name="SAPDirectionIDocTransmission" operator="eq"> <value>2</value> </attributeFilter> <attributeFilter name="SAPLogicalMessageType" operator="eq"> value>EORD1</value> </attributeFilter> </filteringPredicate> </eventCondition> <action actionProvider="TWSaction" actionType="sbj" responseType="onDetection"> <description>Trigger immediate report for high priority orders </description> <parameter name="JobDefinitionWorkstationName"> <value>MASTER84</value> </parameter> <parameter name="JobDefinitionName"> <value>triggerimport</value> </parameter> </action> </eventRule> </eventRuleSet> The following example shows an event rule defined to create a ticket for failing IDocs in the SAP Solution Manager or any other problem management system: when an IDoc with a syntax error is detected.com/xmlns/prod/tws/1.0/event-management/rules" xsi:schemaLocation="http://www. the engine submits a job to create a ticket for the failing IDoc. Chapter 23.ibm.w3. It shows an event rule that triggers an import ABAP report when an IDoc is added with a message type corresponding to emergency orders.0/ event-management/rules EventRules.ibm.Creating event rules based on IDocs 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 After saving the rule according to these settings.

org/2001/XMLSchema-instance" xmlns="http://www.ibm.com/xmlns/prod/tws/1.xsd"> <eventRule name="scenario1_IDoc" ruleType="filter" isDraft="no"> <eventCondition name="IDocEventRaised1" eventProvider="SapMonitor" eventType="IDocEventGenerated"> <filteringPredicate> <attributeFilter name="Workstation" operator="eq"> <value>SAPCPU</value> </attributeFilter> <attributeFilter name="SAPClient" operator="eq"> <value>001</value> </attributeFilter> <attributeFilter name="SAPIDocStatus" operator="eq"> <value>60</value> <attributeFilter name="SAPDirectionIDocTransmission" operator="eq"> <value>2</value> </attributeFilter> </attributeFilter> <attributeFilter name="SAPLogicalMessageType" operator="eq"> value>MYORD1</value> </attributeFilter> </filteringPredicate> </eventCondition> <action actionProvider="TWSaction" actionType="sbj" responseType="onDetection"> <description>Create a ticket for failing IDocs </description> <parameter name="JobDefinitionWorkstationName"> <value>MASTER84</value> </parameter> <parameter name="JobDefinitionName"> <value>createticket</value> </parameter> </action> </eventRule> </eventRuleSet> 202 IBM Tivoli Workload Scheduler for Applications: User’s Guide .Examples of event rules based on IDocs 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 <?xml version="1.w3.0" encoding="UTF-8"?> <eventRuleSet xmlns:xsi="http://www.0/ event-management/rules EventRules.0/event-management/rules" xsi:schemaLocation="http://www.com/xmlns/prod/tws/1.ibm.

© Copyright IBM Corp. this option is ignored.2. The default value is the SAP R/3 code page 1100. It can be one of the following: v Brazilian Portuguese (pt_BR) v English (EN. National Language support Using the local and global configuration files. job streams. which is widely supported by R/3 systems since version 4. However. If you are running a non-Unicode version of r3batch.7. and R/3 variants. the default value) v French (FR) v German (DE) v Italian (IT) v Japanese (JA) v Korean (KO) v Simplified Chinese (zh_CN) v Spanish (ES) v Traditional Chinese (zh_TW) DE. if either the workstation running r3batch or the target R/3 systems do not support Unicode. 2008 203 . EN. when Unicode support is not used: | | | | | | | | TWSXA_CP The code page used to establish the connection between r3batch and the target SAP R/3 system. and JA can be set from the Option Editor. Setting National Language support options The following options control the code page and national language used by Tivoli Workload Scheduler for Applications for SAP version 8. refer to “SAP R/3 supported code pages” on page 204). set this option to the code page installed on the SAP R/3 system (for a list of the valid code pages.1 Chapter 24. you can set up r3batch to use different code pages and languages for both its output and the connection with a remote R/3 system. this version of Tivoli Workload Scheduler for Applications for SAP features Unicode. this chapter describes how you configure code pages and national languages for r3batch. As explained in “Unicode support” on page 93. The National Language support feature allows you to install r3batch on a localized Tivoli Workload Scheduler workstation and use localized characters for Tivoli Workload Scheduler job names. The other languages can be set using any text editor. TWSXA_LANG The language that r3batch uses to log in. 2003. In all other cases.1. similar to the standard ISO8859-1.

you must run the Job Scheduling Console on a system that uses the same code page as the Tivoli Workload Scheduler workstation where r3batch is installed.Setting National Language support options TWSMETH_CP The code page that r3batch uses for its output. interact with r3batch via UTF-8. to retrieve the r3batch output. SAP R/3 supported code pages SAP R/3 code pages 1100 1103 8000 8300 8400 Description 8859-1. Ensure that the TWSMETH_CP and TWSMETH_LANG options are consistent. TWSMETH_LANG The catalog language used by r3batch. The default is the language used by the Tivoli Workload Scheduler workstation that hosts r3batch. therefore this limitation no longer exists. Tivoli Workload Scheduler for Applications for SAP uses the following code pages. only when r3batch does not support Unicode.2. Use these values to set option TWSXA_CP. If the hosting agent uses MS932. The default is the code page used by the Tivoli Workload Scheduler workstation that hosts r3batch. Ensure that the TWSMETH_CP and TWSMETH_LANG options are consistent. SAP R/3 supported code pages To communicate with SAP R/3 systems. Job Scheduling Console version 1. 204 IBM Tivoli Workload Scheduler for Applications: User’s Guide . Even if both the r3batch and the target R/3 system are Unicode-supporting versions.3. run the Job Scheduling Console on a Japanese system with that code page. Table 54. this is the default value MS 850 SJIS: Shift JIS BIG5: Traditional Chinese GBK: Simplified Chinese Supported configurations and limitations The following is a limitation of the Job Scheduling Console version 1. and later.

Part 5. 2008 205 . 2003. z/OS access method © Copyright IBM Corp.

206 IBM Tivoli Workload Scheduler for Applications: User’s Guide .

a JES job must be run on the LPAR where it is submitted.Chapter 25.1. 2003. Note: In a z/OS Parallel Sysplex® environment.4 or later. configuring. For detailed information. for TCP/IP on IBM 3. version 8. or later v Open Connect 2. or later. the term z/OS is used to refer also to supported versions of OS/390. v Define dependencies for Tivoli Workload Scheduler jobs based on the completion of z/OS jobs that were not launched by Tivoli Workload Scheduler.1. upgrading.” This chapter contains the following sections: v “Software requirements” v “Features” v “Installing. you must have the following: Table 55. Job Scheduling Interface Features Using Tivoli Workload Scheduler for Applications for z/OS you can: v Use Tivoli Workload Scheduler to schedule z/OS jobs to run at specific times and in a prescribed order. 2008 207 . or later v JES2 or JES3. v OPC interface: IBM Tivoli Workload Scheduler for z/OS. Note: Support to IPv6 is provided only with Tivoli Workload Scheduler. see “Software requirements. or later v Interlink 3. v Define dependencies between Tivoli Workload Scheduler jobs running on different systems and operating systems. v CA-7 interface: any currently supported version. and uninstalling IBM Tivoli Workload Scheduler for Applications.” on page 5. Additional z/OS software requirements Software Requirement TCP/IP Version One of the following: v IBM 3. Introducing Tivoli Workload Scheduler for Applications for z/OS Using Tivoli Workload Scheduler for Applications for z/OS you can schedule and control z/OS jobs using the job scheduling features of Tivoli Workload Scheduler. “Installing. and uninstalling the z/OS gateway” on page 208 v “Additional information” on page 212 v “Downloading z/OS gateway fixes from FTP” on page 218 Software requirements In addition to the supported operating systems and prerequisite software listed in Chapter 2. Note: Throughout this publication. © Copyright IBM Corp.3.1.

” v Unload the files from a 3480 tape cartridge written in non-IDRC (uncompressed) format. | | | | | | | | | | | | | | | | | Roles and responsibilities In a typical enterprise. From your TSO session emulator. refer to the following sections: v “Installing” v “Configuring” on page 210 v “Uninstalling” on page 211 Installing You can install the z/OS gateway module in either of these two ways: v Unload the files from the IBM Tivoli Workload Scheduler for Applications CD. Table 56. configure. To install the Tivoli Workload Scheduler for Applications for z/OS access method and its language pack. select the ISPF command shell (TSO command) and use the File Transfer utility (Send to Host) to transfer the 208 IBM Tivoli Workload Scheduler for Applications: User’s Guide . and uninstalling IBM Tivoli Workload Scheduler for Applications. Table 56 describes the roles and responsibilities of all the users in the process model. See “Unloading the files from the tape” on page 209. and uninstalling the z/OS gateway Tivoli Workload Scheduler for Applications for z/OS consists of the z/OS access method that must reside on the Tivoli Workload Scheduler host. configuring. To install. “Installing. refer to Chapter 2.Features v Define dependencies for Tivoli Workload Scheduler jobs based on the existence of files on a z/OS system. upgrading. Unloading the files from the CD The z/OS gateway files are stored in the ZOS directory of the product CD and are named: v LOADLIB v SAMPLES To unload the files onto your z/OS system: 1. See “Unloading the files from the CD. showing the tasks they perform. and of the gateway software that resides on z/OS. configuring. and uninstall the z/OS gateway.” on page 5. and uninstalling the z/OS gateway” v “Downloading z/OS gateway fixes from FTP” on page 218 Tivoli Workload Scheduler for Applications configurator Tivoli Workload Scheduler for Applications developer “Defining the configuration options” on page 221 “Defining z/OS jobs in Tivoli Workload Scheduler” on page 223 Installing. different users contribute to the implementation and operation of the product. Roles and responsibilities in Tivoli Workload Scheduler for Applications for z/OS User role z/OS administrator User task v “Installing.

// MSGCLASS=A. This unloads 12 load modules into the output library and two samples into the sample library. //MVSXAUNL JOB (876903.XAGENT.SAMPLIB from TWSUSR2 on NODENAME NMR906A Enter restore parameters or ’DELETE’ or ’END’ + *** 2. Some IEBCOPY messages are displayed as the library is uncompressed.CLASS=A. SAMPLIB 1.LOADLIB’) Where: ″da″ means ″data set″ and the MVS™ data set name in quotes is the name you want for the output loadlib data set.LOADLIB from TWSUSR2 on NODENAME NMR906A Enter restore parameters or ’DELETE’ or ’END’ + *** 2.1). Introducing Tivoli Workload Scheduler for Applications for z/OS 209 .DRV1511.L80’) A prompt is displayed similar to the following: INMR901I Dataset TWS84.FIXPAC04.4 TO CUSTOMIZE * //* * //********************************************************************** Chapter 25. v Identify a 3480 tape device.’OPCL3’.V8R4M0. Some IEBCOPY messages are displayed as the library is uncompressed.FIXPAC04. Issue the following command: TSO RECEIVE INDSN(’TWS4APPS.LOADLIB. Issue the following command: TSO RECEIVE INDSN(’TWS4APPS. Reply: da(’TWS4APPS.V8R4M0. setting the transfer for a logical record length of 80 and a fixed record format. Reply: da(’TWS4APPS.MSGLEVEL=(1.SAMPLIB.NOTIFY=&SYSUID //********************************************************************** //* * //* THIS IS THE JOB THAT UNLOADS THE TIVOLI WORKLOAD SCHEDULER FOR * //* APPLICATIONS z/OS Access Method Version 8.DRV1511. 2. Modify and submit the JCL below to unload the tape.D07). For example: LOADLIB 1.SAMPLIB’) Where: ″da″ means ″data set″ and the MVS data set name in quotes is the name you want for the output samplib data set. Unloading the files from the tape The z/OS gateway files are supplied on a 3480 tape cartridge written in non-IDRC (uncompressed) format.XAGENT. Customize the job card and modify the following parameters according to your environment standards: v Enter an appropriate job name. Receive the members in output data sets using the INDSN option.Unloading the files from the CD LOADLIB library and SAMPLES member from the CD to the z/OS system.L80’) | | | A prompt is displayed similar to the following: INMR901I Dataset TWS84.

or by issuing the following command: PARMLIB UPDATE(00) 5. or copy its contents into another authorized load library. See “Setting RACF authorizations on z/OS” on page 211 for details. See “Setting APF authorizations on z/OS” on page 211 for details. Set the RACF permissions so that the user who will use the gateway can issue the PARMLIB command. Note: This member must have the PACK OFF option set in its profile.(50. // LABEL=(2.CATLG).BLKSIZE=32760). // DISP=(NEW.SERVICE.SPACE=(TRK. To do this. // LABEL=(1.INDD=((INDD. Verify that the TCP/IP port specified in the PARMLIB member is not in use. 4.SPACE=(TRK.R)) //* Configuring To configure the z/OS gateway: 1.SL) //OUTDD DD DSN=TWSX.PARMLIB) 3.V8R4M0.(2.SPACE=(TRK.INDD=((INDD. // SPACE=(32760. Make the IKJTSO00 change effective by performing an IPL.SAMPLES.UNIT=600.VOL=SER=OPC00C //SYSUT3 DD UNIT=SYSDA.BLKSIZE=0). // UNIT=3390.1. // DISP=(OLD. // DCB=(RECFM=FB. choose another that is not in use and modify the PARMLIB member.APFLIB1. // SPACE=(32760. // VOL=SER=IBM001. Create a PARMLIB member with the appropriate startup parameters for EEWSPACE and EEWSERVE.V8R4M0.10)). include STEPLIB. Add EEWTCP00 to the AUTHCMD list in IKJTSO00 (SYS1.PASS). If PACK ON is set.SL) //OUTDD DD DSN=TWSX.10)) //SYSIN DD * COPY OUTDD=OUTDD.LRECL=80.1.R)) //STEP02 EXEC PGM=IEBCOPY //SYSPRINT DD SYSOUT=* //INDD DD DSN=TWSX.(20. the started task will end with RC=04.10)) //SYSUT4 DD UNIT=SYSDA.UNIT=600.SPACE=(TRK.50)). 7. Authorize the TWS4APPS.LOADLIB in APF. 2. // UNIT=3390. // DISP=(OLD.V8R4M0. Copy EEWSPACE and EEWSERVE to the PROCLIB ( from SAMPLIB) and edit it (for example.2. 6. 210 IBM Tivoli Workload Scheduler for Applications: User’s Guide .VOL=SER=OPC00C //SYSUT3 DD UNIT=SYSDA. issue the following command and review the output: TSO NETSTAT PORTLIST If the port is in use.10)) //SYSUT4 DD UNIT=SYSDA.50.1.(20. // VOL=SER=IBM001.CATLG).SAMPLES.(20.1. and specify the appropriate PARMLIB member name).SERVICE. // DCB=(RECFM=U. // DISP=(NEW.V8R4M0.Unloading the files from the tape //STEP01 EXEC PGM=IEBCOPY //SYSPRINT DD SYSOUT=* //INDD DD DSN=TWSX.PASS).(20.10)) //SYSIN DD * COPY OUTDD=OUTDD.APFLIB1.

issue the following commands: rdefine tsoauth parmlib uacc(upd) permit parmlib class(tsoauth) id(ibmuser) acc(upd) setropts raclist(tsoauth) refresh To set the RACF permissions for the started tasks EEWSPACE and EEWSERVE.** rdelete started EEWSERVE.** stdata(user(<user_ID>) group(group_name)) setropts raclist(started) refresh Uninstalling To 1. 2. Update the PROGxx member of SYS1. Introducing Tivoli Workload Scheduler for Applications for z/OS 211 . or the authorization will be lost at your next IPL. to make the changes effective issue the command: SET SMF=xx 9.PARMLIB(IKJTSOxx).PARMLIB. start EEWSERVE.O If the SMFPRMxx member must be changed. or by issuing the following console command: D SMF. To set the RACF permissions to authorize the PARMLIB command to be used by the user "ibmuser". 3. Ensure that the IEFU84 exit is enabled by checking the SYS1.SAMPLES member. or: SETPROG APF.” 10.APFLIB1. When EEWSPACE is up. Start EEWSPACE. 3.SERVICE.LOADLIB library and the TWS4APPS.** stdata(user(<user_ID>) group(group_name)) redefine started EEWSERVE. see “Setting RACF authorizations on z/OS. by following these steps: 1. 2.** setropts raclist(started) refresh Chapter 25. 11. VOL=xxxxxx where: xxxxxx is the volume serial number where the load library is located. uninstall the z/OS gateway: Stop the started tasks EEWSPACE and EEWSERVE. Issuing the SETPROG command from the console log. Add EEWTCP00 to the AUTCHCMD NAMES section of SYS1.ADD. Setting APF authorizations on z/OS This section describes how to authorize the load library in APF.Configuring z/OS gateway 8.ADD.VOL=SMS which indicates a volume controlled by SMS. Setting RACF authorizations on z/OS This section describes how to set RACF permissions. Remove the started task entries from the RACF database by issuing the following commands: rdelete started EEWSPACE.PARMLIB member SMFPRMxx. For example: SETPROG APF.SERVICE. Cancel the TWS4APPS.APFLIB1.DSN=twsx. issue the following commands: redefine started EEWSPACE.DSN=twsx. Set the RACF permissions for the started tasks EEWSPACE and EEWSERVE. For details.

and ACF2 or Top Secret equivalents. Both of the programs run as started tasks. routes z/OS information back to Tivoli Workload Scheduler. EEWTCP00 This is the “gateway” program that manages TCP/IP communications between Tivoli Workload Scheduler and the z/OS system. can be used to control which job names and user IDs (with or without passwords) can be submitted by EEWSERVE. IBM distributes a dummy IEFU84 exit with the operating system that is an IEFBR14 program. When EEWSPACE is terminated. to ensure that they shut down properly without impacting other programs that use the IEFU84 Exit. EEWTCP00 translates Tivoli Workload Scheduler commands to z/OS equivalents. Security Security is enforced in several areas. This exit must be turned on in the SMF parm member in SYS1. with a TIME=NOLIMIT parameter. The EEWSPACE job dynamically chains to the IEFU84 exit. IEFU84 Exit The extended agent for z/OS tracks job streams using the IEFU84 exit. which continue to run normally. and ACF2. they should be stopped. ACF2 and Top Secret equivalents can also be used. and performs EBCDIC-ASCII data conversions.PARMLIB. If the IEFU84 exit is currently being used. The JCL should not contain passwords. It is important to note that EEWSPACE has no effect on the existing IEFU84 exit or exits.Additional information Additional information The following topics provide additional information for the z/OS extended agent: v “Gateway software components” v “IEFU84 Exit” v “Security” v “Console Security” on page 213 v “Startup” on page 213 v “SYSTSIN variables” on page 213 v “z/OS gateway version” on page 217 Gateway software components The two z/OS program components of the Tivoli Workload Scheduler gateway are: EEWTCP02 This program establishes that Tivoli Workload Scheduler is tracking on the z/OS system. It is started by the EEWSERVE job. Resource class JESJOBS in RACF. not canceled. This can be authorized using SURROGAT class resources in RACF. it removes itself from the chain and restores the chain to its original status. EEWSPACE will “front-end” the IEFU84 exit. usually. If the programs must be terminated for any reason. Top Secret. and then branch to the existing user exit(s). EEWTCP02 is always started first. The EEWSERVE job should have the ability to submit jobs that run under the user IDs that are supplied in the JCL to be submitted. and the equivalents in ACF2 and Top Secret. PROPCNTL class resources in RACF should be used to prevent submitted jobs from running under the EEWSERVE user ID. RACF. 212 IBM Tivoli Workload Scheduler for Applications: User’s Guide . The program is started by the EEWSPACE job. followed by EEWTCP00. obtain the information it requires.

TRMID=EEW. Introducing Tivoli Workload Scheduler for Applications for z/OS 213 .OPEN=YES LINE. The default values are shown in parentheses. To shut down. stop EEWSERVE before stopping EEWSPACE. See “SYSTSIN variables” for a description of parameter settings. The CA-7 release options. The default is determined from the CA-7 subsystem vector table entry and you should not change it unless directed to do so by IBM Software Support. EEWSPACE creates the Data Space and installs the IEFU84 exit.NLINE=10.DEVICE=CONSL.Gateway software components Console Security The EEWSERVE job completely owns the console when displaying job streams and issuing modify commands to CA-7. It must have the authority to use an extended console.LINELEN=110. Customize and start the EEWSPACE procedure (following the commented instructions contained therein) to start the extended agent Gateway Data Space. See also “SYSTSIN variables” for information about specifying a user ID of authority. The following example shows the CA-7 parameters needed to support the use of the modify command from a console: GROUP.BUFSIZE=150. Set to NO if you do not use this interface. SYSTSIN variables Variable CA7INTERFACE(CONSOLE) Description CONSOLE is the only supported interface for CA-7 and is the default value for this variable. b. CA7NAME(CA7ONL) CA7OPTIONS(X’32’) Chapter 25.NAME=EEW. OPERCMDS should be modified to allow this function if not already allowed. Notes: a. Table 57.DEVICE=CONSL. See “SYSTSIN variables” for a description of parameter settings. Modify the settings as required for your site configuration. Note that CA-7 must be configured to allow users to issue modify commands through the master or extended consoles.OPEN=YES TERM. 3. To terminate the job. The name of the CA-7 control region address space. SYSTSIN variables Table 57 lists all the SYSTSIN variables and their description.TNAME=EEW.LNAME=EEW.NAME=EEW. EEWSPACE must be active before EEWSERVE is started. The job must be a started task and must not be canceled. Ignored if CA-7 is not used. See your security administrator to ensure that this is the case. Customize and start the EEWSERVE procedure following the commented instructions contained therein.STANIDS=(EEW) Startup Follow these steps: 1. use the STOP EEWSPACE command from any z/OS console. use the STOP EEWSERVE command from any z/OS console.NAME=EEW STATIONS. 2. To terminate the job.

it must be a 4-digit number in the format HHMM. The amount of time. so that it is possible to distinguish the case where the variable is not used. For more details. an invalid value. in hundredths of a second. that each gateway task waits after CA-7 has confirmed that the gateway request to LOGON to it has been successfully processed. The user ID that is used to issue CA-7 commands. before issuing the next command to CA-7. Ignored if CA-7 is not used. v CA7SPAN(0130) means 1 hour and 30 minutes. The number represents the minimum interval (in hours and minutes) after which it is possible to launch from Tivoli Workload Scheduler the same job without specifying a different SCHID. For example: v CA7SPAN(0010) means 10 minutes. The default is 0. CA7SUBSYSTEM(UC07) CA7USER(CA7CNSL) CA7WAIT(0) The name of the CA-7 subsystem. refer to “Other CA-7 tips” on page 232. 214 IBM Tivoli Workload Scheduler for Applications: User’s Guide . which means that the next command is issued immediately. SYSTSIN variables (continued) Variable CA7SPAN(9999) Description This variable applies exclusively to the CA-7 interface. The maximum value must be less than half the value specified for MAXWAIT. If specified. The default is intentionally set to 9999.SYSTSIN variables Table 57.

INTERLINKSUBSYSTEM(ACSS) JESCMDCHR($) JESINTERFACE(CONSOLE) MAXWAIT(500) MCSSTORAGE(3) Chapter 25. Ignored if Interlink is not used as TCP/IP stack. This variable can assume one of the following values: LASTSTEP The completion code for a JES multi-step job is determined by the last run step in the job. Any condition code different from 0 in the last step (if LASTSTEP was selected) or in any step (if MAXSTEP was selected) causes the job to be considered unsuccessfully completed. to wait for a response to commands. This variable is ignored if you set both CA7INTERFACE and JESINTERFACE to NO. The job command recognition character. This variable is ignored if you set both CA7INTERFACE and JESINTERFACE to NO. This is the default value. unless the flushed step is the last one. it causes the gateway to output diagnostic messages. unless differently specified using the condcode option in the job definition in Tivoli Workload Scheduler. it is not taken into consideration when determining the completion code of the job. The amount of storage. The maximum amount of time. Change this variable only if a different command recognition character is being used. in which case the job is always considered as completed unsuccessfully.SYSTSIN variables Table 57. DEBUG(NO) If set to YES. MAXSTEP The completion code is determined by the highest completion code of any run step in the job. Use only in coordination with IBM Software Support. Set to NO if you do not use this interface. Introducing Tivoli Workload Scheduler for Applications for z/OS 215 . used by each extended console used by the gateway. The name of the subsystem used by Interlink TCP/IP stack. The default is set to dollar sign ($) for JES2 systems and to asterisk (*) for JES3 systems. in hundredths of a second. If a step is flushed. CONSOLE is the only supported value for JES and it is the default value. in megabytes. SYSTSIN variables (continued) Variable COMPLETIONCODE(LASTSTEP/MAXSTEP) Description Specifies the job completion code of a JES multi-step job.

To connect to an extended agent that supports only Internet Protocol version 4. The asterisk causes the class to be set to the same value as EEWSERVE.2. Use only in coordination with IBM Software Support.2. For better security. 8. Ignored if Tivoli Workload Scheduler for z/OS is not used. 3. Set to NO if you do not use this interface. The message class for the dynamically allocated message logs used by Tivoli Workload Scheduler for z/OS. Notes: 1. 0:0:0:0:0:0:0:0. PORT(5000) The TCP/IP port number used by Tivoli Workload Scheduler and the gateway for communications.SYSTSIN variables Table 57. The maximum number of messages to be queued to an extended console. The subsystem name used for communications with the Tivoli Workload Scheduler for z/OS control region. 2.″ (for IPv4) or ″:″ (for IPv6) between the 0s. If you are migrating from Tivoli Workload Scheduler for Applications 8. The prefix used by the extended agent for z/OS as the first four characters of extended console names. The vendor of TCP/IP stack (IBM. It is also used as the first four characters of internal reader DDNAMES. Change only in coordination with IBM Software Support. permits access by any host. you must use IPv4. OPCMSGCLASS(*) OPCSUBSYSTEM(OPCS) | | | | | | | | | | | | | | | | | PEERADDRESS(0:0:0:0:0:0:0:0) PUTLINE(YES) QLIMIT(2000) SUBSYS(UNIS) SVCDUMP(NO) TCPIPSTACK(IBM) 216 IBM Tivoli Workload Scheduler for Applications: User’s Guide . INTERLINK. When set to YES. SYSTSIN variables (continued) Variable OPCINTERFACE(PIF) Description PIF is the only supported interface for Tivoli Workload Scheduler for z/OS and is the default value for this variable. abends cause a SVC dump.1. or OPENCONNECT). When set to YES.3. Depending on the Internet Protocol you are using. it directs trace information to DDNAME SYSTSPRT. or 8. enter the IP address of the Workload Scheduler host of the z/OS extended agent. ensure that you modify this variable to comply with the current format. The default. specify an IPv4 or IPv6 address by including also the ″. This must be the same as the value entered in the TCP/IP Address field of the z/OS x-agent workstation definition.

y the release. When set to YES. PUTLINE(YES) and WTP(NO) are required if DEBUG(YES). provided that the release of the corresponding subsystem(s) support(s) it.SYSTSIN variables Table 57. ZOSV1R2(NO) Set to YES if you are using the JES3 interface with z/OS V1R2 or later. The transaction termination character. z the modification level. For example: EEWTCP10 VERSION RELEASE MODIFICATION LEVEL = VxRyMz where x is the version. the level of the operating system does not make any difference for the product v If you are using the CA-7 or Tivoli Workload Scheduler for z/OS interfaces. When you use CA-7. SYSTSIN variables (continued) Variable TCPNAME(TCPIP) Description The name of the TCP/IP address space when the IBM version of TCP/IP stack is used. This can be used if SYSTSPRT does not suit your needs. Chapter 25. This parameter is ignored if you are not using the JES3 interface. the support of z/OS V1R2 or later is ensured. Do not change the default unless directed to do so by IBM Software Support. TERMINATOR(X’25’) WTP(NO) z/OS gateway version The version of EEWSERVE (and EEWSPACE) appears in the first line of the EEWSERVE (and EEWSPACE) log. because: v If you are using the JES2 interface. it directs trace information to SYSLOG as write-to-programmer information. Introducing Tivoli Workload Scheduler for Applications for z/OS 217 .

with your e-mail address as the password.ibm. Issue the following commands: tso ftp ftp. Use FTP to retrieve the LOADLIB and SAMPLES fix pack files from the download site.software.L80’ (rep get samples_file_name ’TWS4APPS.4.0/ cd patch_name cd ZOS bin get loadlib_file_name ’TWS4APPS.L80’ (rep quit For example.4.L80 (for the load library) v TWS4APPS.4 is issued by IBM. version 8.L80 (for the samples library) Use the file characteristics shown in Table 58.SAMPLIB. File characteristics for obtaining the gateway fix pack files by FTP Characteristic Organization Record format Record length Block size 1st extent cylinders Secondary cylinders Value PS FB 80 27920 1 1 Note: These files are not allocated as type PDS but as regular sequential files. 2.SAMPLIB. Download the z/OS gateway fix pack files as follows: 1. For example: v TWS4APPS. for fix pack 01 the variables in this list of commands would have the following values: patch_name loadlib_file_name LOADLIB_820WSEFP07 samples_file_name SAMPLES_820WSEFP07 Note: The data set names in quotes on the get commands (the MVS file names) must match the files that were allocated in step 1.z/OS gateway version Downloading z/OS gateway fixes from FTP This section describes how to obtain the files in a fix or fix pack from the IBM software FTP site. by logging in as anonymous. Allocate two data sets with LRECL=80 RECFM=80 to hold the downloaded files. you can receive it by downloading the files from the IBM software FTP site.com anonymous your_e-mail_address cd software/tivoli_support/patches/patches_8. If a fix or fix pack for Tivoli Workload Scheduler for Applications for z/OS.LOADLIB.LOADLIB. 8.0-TIV-TWSWSE-FP0001 218 IBM Tivoli Workload Scheduler for Applications: User’s Guide . Table 58.

4. Issue the following command: TSO RECEIVE INDSN(’TWS4APPS. Some IEBCOPY messages are displayed as the library is uncompressed..... Table 59.DRV1511. Issue the following command: TSO RECEIVE INDSN(’TWS4APPS.. The downloaded files are in an 80-byte packed format.. . . Reply: da(’TWS4APPS. browse them. After receiving the files... Receive the downloaded data sets..... \INMR02.DRV1511.......XAGENT....A.DRV1511...FIXPAC04.. Introducing Tivoli Workload Scheduler for Applications for z/OS 219 ......&....NODENAME...TWS84... the file characteristics change to those shown in Table 59.... The beginning of the output should be similar to the following: BROWSE TWS4APPS...LOADLIB.FIXPAC04.TWSUSR2......SAMPLIB..L80’) A prompt is displayed similar to the following: INMR901I Dataset TWS84.. as follows: LOADLIB a.... Some IEBCOPY messages are displayed as the library is uncompressed. To ensure that the files have been downloaded correctly.... SAMPLIB a....LO If it is not.z/OS gateway version 3. .LOADLIB PO U 0 32760 10 Chapter 25.IEBCOPY...LOADLIB.. ......L80’) A prompt is displayed similar to the following: INMR901I Dataset TWS84....V8R4M0..... .L80 Line \INMR01.... Reply: da(’TWS4APPS. File characteristics for the LOADLIB file after receiving it Characteristic Data Set Name Organization Record format Record length Block size 1st extent blocks Value TWS4APPS....LOADLIB’) where da means data set and the MVS data set name in quotes is the name you want for the output loadlib data set..A.SAMPLIB’) where da means data set and the MVS data set name in quotes is the name you want for the output samplib data set.......SAMPLIB from TWSUSR2 on NODENAME NMR906A Enter restore parameters or ’DELETE’ or ’END’ + *** b. retry the downloads..XAGENT.... ..XAGENT.FIXPAC04.20 ....LOADLIB from TWSUSR2 on NODENAME NMR906A Enter restore parameters or ’DELETE’ or ’END’ + *** b..V8R4M0..... .."8..V8R4M0..

File characteristics for the SAMPLIB file after receiving it Characteristic Data Set Name Organization Record format Record length Block size 1st extent blocks Secondary blocks Data set name type Value TWS4APPS. 220 IBM Tivoli Workload Scheduler for Applications: User’s Guide . JES2. Use the Search Support option to search for items of interest to you. Useful terms to enter for Tivoli Workload Scheduler for Applications for z/OS are: ″TWS4APPS″.SAMPLIB PO FB 80 27920 4 1 PDS Configure the downloaded fix pack files as described in “Configuring” on page 210. message IDs. or the interface types ("TWS for z/OS". ″TWS applications z/OS″. ″EEWSERVE″. File characteristics for the LOADLIB file after receiving it (continued) Characteristic Secondary blocks Data set name type Value 5 PDS Table 60.z/OS gateway version Table 59. ABEND codes. Locating product support To find the Tivoli Workload Scheduler for Applications support page. see the appendix on support information in Tivoli Workload Scheduler: Troubleshooting Guide. ″MVS xagent″. CA-7. JES3).

See “Defining the configuration options. or mvsopc. Table 61 on page 222 describes the options that you can define for the z/OS access method. writing job progress and status information to the job’s standard list file.” v Define an extended agent for a z/OS job. the agent uses by default one of the global options file (either mvsca7. The options file must reside on the Tivoli Workload Scheduler hosting computer for the extended agent in the TWShome\methods directory.Chapter 26. This chapter describes how to: v Define the options for the z/OS method. passing it information about the job. See “Defining jobs in z/OS” on page 222.opts.opts). 2008 221 . You can create it during or after the installation of the access method with either the Option Editor (see Chapter 3. The extended agent for z/OS workstation is a workstation definition linked to an instance of the z/OS system. To launch a job on an extended agent for z/OS workstation. “Setting options with the Option Editor. If you do not create one. See “Defining z/OS jobs in Tivoli Workload Scheduler” on page 223. mvsjes. “Defining extended agent workstations. Configuring the z/OS access method Tivoli Workload Scheduler launches jobs on an extended agent for z/OS workstation.” on page 43) or any common text editor. The access method communicates with the instance of the z/OS host and monitors the job through completion.opts. © Copyright IBM Corp. 2003. v Schedule an extended agent for a z/OS job. which gives it a name and identifies the access method to be used. Defining the configuration options | | | | Every installed instance of the z/OS access method must have a matching options file. The extended agent for z/OS is defined in a standard Tivoli Workload Scheduler workstation definition. Tivoli Workload Scheduler runs the access method.” on page 47 to learn how to define an extended agent workstation in Tivoli Workload Scheduler. See Chapter 4.

For best results. Defining jobs in z/OS In z/OS. (Optional 1) Assigns the user name used by the access method to launch jobs (LJ tasks). The default is 10. jobs that are scheduled with Tivoli Workload Scheduler are defined as described in the following sections: v “For JES jobs:” on page 223 v “For CA-7 jobs:” on page 223 v “For Tivoli Workload Scheduler for z/OS jobs:” on page 224 222 IBM Tivoli Workload Scheduler for Applications: User’s Guide . For details. (Optional 1) Assigns the user name used by the access method to check non-Tivoli Workload Scheduler-launched jobs on z/OS that are used as dependencies (GS tasks). see options CHECKINTERVAL and BLOCKTIME. The default is 2. On the mvsca7 gateway. in minutes. for example. and marks it in the abend state. and GSUSER to take the default values. allow LJUSER. Fractional values are accepted. (Optional) Defines the polling rate.Defining the z/OS configuration options Table 61. and GSUSER. It can be the same as LJUSER.5 for one minute and 30 seconds. in minutes. the method will wait for a response to a status check before timing out. This value must be less than the value of CHECKINTERVAL (described below) and of Tivoli Workload Scheduler’s local option bm check status. CFUSER. The default is root.5 for 30 seconds. for checking the status of z/OS jobs that were launched by the method. CFUSER. . The default is the login parameter in the job definition.5 for one minute and 30 seconds. CFUSER=name (Optional 1) Assigns the user name used by the access method to check file dependencies (CF tasks). the method uses the Tivoli Workload Scheduler local option bm check status instead of CHECKINTERVAL to determine its polling rate. (Optional) Defines the number of times a status check is attempted before Tivoli Workload Scheduler writes a timeout message to a job’s stdlist file.5 for 30 seconds. Tivoli Workload Scheduler for Applications for z/OS access method options Options File Entries BLOCKTIME=min Description (Optional) Defines the amount of time. The default is 2. or 1. the CA7USER ID is not related to LJUSER. . Note: Only change this option from the default value if specific network problems cause delays in the transmission of data from the z/OS gateway. This must be a valid UNIX or Windows user who submits local jobs and is able to connect to the Tivoli Workload Scheduler z/OS gateway on the z/OS system. for example. Fractional values are accepted. When checking non-Tivoli Workload Scheduler-launched jobs on z/OS that are used as dependencies. CHECKINTERVAL=min GSUSER=name LJUSER=name RETRYCOUNT=count Notes: 1. or 1.

v As arguments of the JOBCMD keyword in the JOBREC statement in the SCRIPTLIB of Tivoli Workload Scheduler for z/OS. Task definition syntax for z/OS jobs scheduled with Tivoli Workload Scheduler The following are descriptions of the task definition syntax (command line “scriptname”) for z/OS jobs that Tivoli Workload Scheduler schedules and launches from extended agent workstations using the mvsjes (JES2/3 jobs). z/OS rejects the name and abends the job if it finds them. if you are scheduling in an end-to-end environment.Job Definition Window. other than dash (-) and underscore (_).apayable. special script name options. if you use the Job Scheduling Console. if you use the Tivoli Workload Scheduler command line. “Defining extended agent jobs. They are defined like other Tivoli Workload Scheduler jobs and include job name. See Chapter 5. and optional recovery options. For JES jobs: The syntax is: dataset [<|= condcode] where: dataset condcode Specifies the JES job data set or the name of a member of a partitioned data set. or mvsopc ( IBM Tivoli Workload Scheduler for z/OS jobs) methods.. If preceded by <. nor national characters in the Tivoli Workload Scheduler job name.Defining z/OS jobs in Tivoli Workload Scheduler Defining z/OS jobs in Tivoli Workload Scheduler Tivoli Workload Scheduler job definitions are required for each z/OS job you intend to schedule and launch with Tivoli Workload Scheduler. v As arguments of the scriptname keyword in the job definition statement.] [RO(EQ|LT|GT|GE|LE|NE|#S|IG|NO) [SET(SKP|NTR|NDB) ] ] Chapter 26. Example: gold. “= 0000” is used. Specifies the condition code that indicates successful job completion. Remember that you should include neither special characters. Configuring the z/OS access method 223 . mvsca7 (CA-7 jobs). You specify these task string parameters in the following places when you define their associated Tivoli Workload Scheduler jobs: v In the Command field of the Task page of the Properties . Such characters are not supported in z/OS.” on page 53 for reference. If omitted.cntl(apayjob1) = 0004 For CA-7 jobs: The syntax is: jobname [SCHID(nnn)] [CC(nnnn)] [. If preceded by =. Note that there must be a space on both sides of the operator (< or =). the condition code must be equal to this value. the condition code must be less than or equal to this value. and when the Tivoli Workload Scheduler job is passed to z/OS by the access method. user name..

) Add predecessor dependencies. The deadline arrival date and time in the form: yymmddhhmm. refer to the Tivoli Workload Scheduler for z/OS documentation. The schedule ID (a number 1-255) to be assigned to the job. The condition code used with RO that indicates successful job completion. DEADLINETIME The deadline arrival time in the form: hhmm.] [DEADLINE(yymmddhhmm)|DEADLINETIME(hhmm)] [PRIORITY(pri)] [CPDEPR(Y|N|P|S)] where: appl IA IATIME DEADLINE The name of the Tivoli Workload Scheduler for z/OS application to be inserted into the current plan. Do not add any dependencies. The input arrival time in the form: hhmm. refer to the CA-7 Commands Guide. Example: PREFABJOB44 IA(0202181000) PRIORITY(5) CPDEPR(Y) 224 IBM Tivoli Workload Scheduler for Applications: User’s Guide . or bypass database loading on completion (NDB). (the default. The relational operator for condition code CC. For complete descriptions of the parameters..Task definition syntax for z/OS jobs where: jobname SCHID CC RO SET The name of the job in CA-7. Example: ARCVJOB SCHID(203) CC(0001) RO(EQ) SET(NDB) For Tivoli Workload Scheduler for z/OS jobs: The syntax is: appl [IA(yymmddhhmm)|IATIME(hhmm)] [. Add successor dependencies. disable normal job triggering (NTR). Sets job options to skip the next scheduled run (SKP). Y N P S Add all successor and predecessor dependencies.. For complete descriptions of the parameters. PRIORITY CPDEPR The priority (1-9) at which to run the application. The current plan dependency resolution selection. The input arrival date and time in the form: yymmddhhmm.

. or to check for dependency failures. The identification of the z/OS job.Task definition syntax for other z/OS Jobs Task definition syntax for other z/OS jobs The following are descriptions of the task definition syntax (command line “scriptname”) for z/OS jobs that are to be monitored for completion. “= 0000” is used. mvsca7. The basic syntax is: tws-job follows xagent::"mvs-job" where: tws-job xagent The name of the Tivoli Workload Scheduler job that depends on the completion of the specified z/OS job. or Tivoli Workload Scheduler for z/OS. mvs-job For JES jobs: The syntax is: "jobname[<|= condcode]" where: jobname condcode The name of the job in JES. work with the host subsystem operator who can obtain this information from the EEWSERVE log. Tivoli Workload Scheduler only records whether or not these jobs completed successfully. or mvsopc method. The details of the outcome of such jobs must be checked in the subsystem where the jobs were launched.scope)} {(startdate. that is. The completion of these z/OS jobs can be used as “follows” dependencies for Tivoli Workload Scheduler-launched jobs.endtime)} where: Chapter 26.starttime. The jobs to be monitored can be JES. See the syntax descriptions below. the condition code must be less than or equal to this value. To find the reason for the failed submission or completion of one of these jobs.. the condition code must be equal to this value. CA-7. If omitted. Configuring the z/OS access method 225 . If preceded by <.]" [DATE(*|*yyddd)}] [SPAN( {* })] {scope} {date} {(startdate. The condition code that indicates successful job completion.starttime. There must be a space on both sides of the operator (< or =). Tivoli Workload Scheduler monitors these jobs until their status changes to success. Example: job5 follows jesworkstation::"apayable = 0004" For CA-7 jobs: The syntax is: "jobname [SCHID(nnn)] [. If preceded by =.enddate. The name of the Tivoli Workload Scheduler extended agent workstation associated with the scheduler of the z/OS job. The two colons (::) are a required delimiter. an extended agent defined with the mvsjes. This string must be enclosed in quotation marks.

it will fail with RC=04. For Tivoli Workload Scheduler for z/OS jobs: The syntax is: "application[IA(yymmddhhmm)|IATIME(hhmm)][. For example: joba follows workstation::"arcvjob schid(203) span(12)" See also “Other CA-7 tips” on page 232. If included. The z/OS job name. So even if you use different started 226 IBM Tivoli Workload Scheduler for Applications: User’s Guide . refer to the CA-7 Commands Guide. For this reason. For complete descriptions of the parameters. For example: joba follows twsworkstation::"PREFABJOB44 IA(0202181000) JOBNAME(PFJ3)" Operational considerations for the EEWSERVE gateway task The following considerations apply: EEWSERVE not running If the EEWSERVE task on the mainframe is not running. only one instance of the EEWTCP02 task (default name EEWSPACE) can be run on a z/OS LPAR. the application is considered completed when it reaches this operation number. The input arrival time. A specific log date to be searched for the job. Tivoli Workload Scheduler for Applications for z/OS or CA-7. The extended agent workstation still shows its status as linked even if EEWSERVE is not running. a rule should be written to detect any outages of the EEWSERVE task. The schedule ID (a number 1-255) of the job.]" [JOBNAME(jobname)] [OPNO(num)] where: application IA IATIME JOBNAME OPNO The name of the Tivoli Workload Scheduler for z/OS application (job stream) in the current plan. However. refer to the Tivoli Workload Scheduler for z/OS documentation. the job will show an error status and will fail. and a Tivoli Workload Scheduler job with no follows dependency is submitted from the extended agent. the job will not run after the EEWSERVE task is started. if a Tivoli Workload Scheduler job has a follows dependency for an external (non-Tivoli Workload Scheduler) job which runs under JES. If a second instance is started.. Instance limitations in LPARs Due to the ENQ/DEQ mechanism in use. the internal check job (CJ) command is reissued after EEWSERVE is started. The span of log records to be searched for the job.Task definition syntax for other z/OS Jobs jobname SCHID DATE SPAN The name of the job in CA-7. The operation number (1-255). For complete descriptions of the parameters. The input arrival date and time.. if a z/OS automation product such as NetView is available on the mainframe. that is.

Chapter 26. Configuring the z/OS access method 227 . The basic syntax is: tws-job opens xagent#"hlq1.hlq3" where: tws-job xagent The name of the Tivoli Workload Scheduler job dependent on the specified z/OS file. For more information.hlq3 The identification of the z/OS file in high level qualifier terms.hlq2. only one instance of EEWSPACE or EEWSERVE can exist concurrently on a z/OS LPAR. Note: This string must be enclosed in quotation marks. hlq1. Note: The # sign is a required delimiter. an extended agent defined with the mvsjes. see “Checking for files on z/OS” on page 234. The name of the Tivoli Workload Scheduler extended agent workstation associated with the scheduler of the z/OS job.hlq2. File (OPENS) dependencies syntax on z/OS files Tivoli Workload Scheduler jobs and job streams can use z/OS files as dependencies.Task definition syntax for other z/OS Jobs task names and PORT numbers. or mvsopc method. mvsca7. that is.

228 IBM Tivoli Workload Scheduler for Applications: User’s Guide .

the job and condition code information are made available to Tivoli Workload Scheduler. JES job states with respect to Tivoli Workload Scheduler Tivoli Workload Scheduler Job State intro wait wait JES Job State Not available Queued Not available Comment Tivoli Workload Scheduler is starting the method. The program issues the MCSOPER macro to activate an extended MCS console. Reference information This chapter describes job states when operating on JES. the job name and JES job ID are also entered in the Tablespace. (Currently the Gateway uses Type 30 SMF records and also subtypes 1. All the return codes from the extended MCS macros are handled as documented in IBM z/OS Programming: Authorized Assembler Services Reference. When a job is submitted. submits it to JES.) Tivoli Workload Scheduler checks submitted jobs periodically to see if they are active. This situation might occur if a job fails for security reasons or JCL syntax problems. Managing JES jobs The following sections describes how to manage JES jobs. it is able to check for the specific job it submitted. Job is queued. Table 62. Because Tivoli Workload Scheduler keeps track of both the job name and the JES job ID.Chapter 27. it might be due to a security violation in z/OS. The gateway allocates an internal reader at the start of each task and then submits the job to the reader. and can issue commands by issuing the MGCRE macro. and Tivoli Workload Scheduler for z/OS in the Tivoli Workload Scheduler environment. Tivoli Workload Scheduler passes the name of the JCL data set or partition data set it wants to run to the z/OS gateway. © Copyright IBM Corp. JES job states: Table 62 lists JES job states with respect to Tivoli Workload Scheduler. When an SMF record containing relevant job scheduling data is passed through the IEFU84 exit. CA-7. 2003. 2008 229 . in turn. Check the job on the z/OS system. Submissions occur using dynamically allocated internal readers in JES. Volume 3. the job is marked as abend in Tivoli Workload Scheduler displays. Launching JES jobs To launch and monitor a JES job. If the job remains in this state. which. If a Tivoli Workload Scheduler-submitted job is not active and no information about it is found through the IEFU84 exit. The z/OS gateway is then able to receive messages and command responses by issuing the MCSOPMSG macro.5. Technical overview The z/OS gateway uses an extended MCS console to communicate with JES and CA-7. SA22-7611.4.

The IEFU84 exit cannot handle every job without impacting the performance of the entire system because it is invoked for each job running on the z/OS system. the Tivoli Workload Scheduler operator should work with the host subsystem operator who can obtain this information from the EEWSERVE log. Job’s condition code meets the completion criteria in the Tivoli Workload Scheduler job definition. System abend codes. the gateway inserts the job into the dataspace the first time it receives the request from Tivoli 230 IBM Tivoli Workload Scheduler for Applications: User’s Guide . Status unknown. Can occur only when checking a job that is used as a dependency. v If the job is submitted by Tivoli Workload Scheduler. Because Tivoli Workload Scheduler did not submit the job. the gateway inserts the job into the dataspace. In this case the IEFU84 exit monitors the status of the job and of each step contained in the job.Launching JES jobs Table 62. Checking JES jobs To check a JES job that was not launched by Tivoli Workload Scheduler. Job condition code does not meet the completion criteria in the Tivoli Workload Scheduler job definition. the name of the job is passed by Tivoli Workload Scheduler to the gateway. v If the job is not present in the gateway dataspace. the IEFU84 exit does not perform any action. the JES job ID is not available. and user abend codes. The internetwork dependencies of a z/OS job are handled by Tivoli Workload Scheduler in the following ways: v If there are no occurrences of z/OS jobs in the job queues. Both types of code are written to the job stdlist file. JES job states with respect to Tivoli Workload Scheduler (continued) Tivoli Workload Scheduler Job State exec succ JES Job State Executing Completed Comment Job is running. v If the job is not submitted by Tivoli Workload Scheduler. in decimal. the gateway inserts the job into the dataspace only if the gateway receives a request from Tivoli Workload Scheduler to check its status because the job represents an internetwork dependency. If any occurrences of the z/OS job are present then purge them. To find the reason for a failed submission or failed completion of one of these jobs or to check for dependency failures. From Tivoli Workload Scheduler you should only expect to find out whether these jobs completed successfully or not. or a system or user abend has occurred. are prefixed with ″U″. and waits for information about the job to appear in SMF records passed through the IEFU84 exit. abend Completed extrn Not available Monitoring JES jobs The details of the outcome of JES jobs must be requested from the subsystem where these jobs were launched. ensure that there are no occurrences of the z/OS job in any job queue including the output queue. are prefixed with ″S″. To have the internetwork dependencies of a z/OS job correctly handled by Tivoli Workload Scheduler on the z/OS system. The Gateway enters the name in the Tablespace. in hexadecimal.

The gateway inserts the job into the dataspace with an unknown job ID ready to be monitored. CA-7 job states with respect to Tivoli Workload Scheduler Tivoli Workload Scheduler Job State CA-7 Job State intro wait exec succ Not applicable Ready Queue Active Queue Completed Comment Workload Scheduler is starting the method. The job is queued. Status unknown. and optionally the CA-7 sched ID. Tivoli Workload Scheduler passes the job name. is passed by Tivoli Workload Scheduler to the gateway. the name of the job.Monitoring JES jobs Workload Scheduler to check the job status. To see if the job is currently being scheduled or run by CA-7. From now on the z/OS job is monitored using the associated JES job ID. and the internetwork dependency is correctly resolved. Check the job on the z/OS system. and Active Queue. v When the z/OS job is submitted. At the time of the submission request. It is important to note that CA-7 itself must be authorized to accept commands from the console for this mechanism to work. Also see note below. refer to the CA-7 documentation for a description of the Modify and Login commands. which is used to track all subsequent activity for the job. Request queue as result of an abend. Can occur only when checking a job that is used as a dependency. The job is running The job condition code meets the completion criteria in the Tivoli Workload Scheduler job definition. the IEFU84 exit finds the job in the dataspace and updates the corresponding entry with the JES job ID. Tivoli Workload Scheduler rechecks at a rate defined by the bm check status value in its local options file. abend extrn Request Queue Not applicable Note: If a job remains in the abend or extrn states. If the job is not found. Chapter 27. the gateway returns the information to Tivoli Workload Scheduler. Managing CA-7 jobs The following sections describe how to manage CA-7 jobs. If the job completes successfully. the gateway searches the following CA-7 queues. CA-7 job states Table 63 lists CA-7 job states with respect to Tivoli Workload Scheduler. the gateway receives the CA-7 job number. Ready Queue. Reference information 231 . Table 63. in this order: Request Queue. Launching CA-7 jobs To launch and monitor a CA-7 job. and optionally the CA-7 sched ID. For more information about this feature. it might be due to a security violation in z/OS. Checking CA-7 jobs To check a CA-7 job that was not launched by Tivoli Workload Scheduler. it wants to run to the z/OS Gateway.

JOB=XXXXXXXXX). make sure that they do not suppress CA-7 messages. priority. that suppress console messages. it wants to run to the z/OS Gateway. It is important to know that. deadline arrival. the only condition being that the interval between two submissions must be greater than the value specified with CA7SPAN. the CA7USER must be a CA-7 ID that is authorized to issue demand commands from the MVS console (MODIFY CA7. The input arrival. and automatic dependency resolution parameters. if specified. It is good practice to have the CA7SPAN (or SPAN) greater than RetryCount*CheckInterval. If it exists in the Tivoli Workload Scheduler for z/OS database. and other optional parameters. 2. such as AFOPER. override any values specified in Tivoli Workload Scheduler for z/OS. Launching Tivoli Workload Scheduler for z/OS jobs To launch and monitor a Tivoli Workload Scheduler for z/OS job. then CA7SPAN is ignored. If SPAN is not specified (or cannot be specified. This circumvents the limitation according to which each occurrence must be uniquely identified and makes it possible to launch from Tivoli Workload Scheduler the same job with the same SCHID. the value of CA7SPAN will be used in all the inquiries to CA-7 (if they refer to jobs launched by Tivoli Workload Scheduler or if they are issued to check internetwork dependencies for jobs not launched by Tivoli Workload Scheduler) except for those jobs that have SPAN specified in their Tivoli Workload Scheduler definition. v The limitation that in prior versions of the product forced users to uniquely identify occurrences when defining CA-7 jobs in Tivoli Workload Scheduler (that is. The logic behind the implementation of CA7SPAN is the following: if SPAN is specified in the Tivoli Workload Scheduler definition of a job. Tivoli Workload Scheduler passes the application name. the application is inserted into the current plan. If the . if included.Checking CA-7 jobs Other CA-7 tips v When using CA-7. as in the case of jobs launched by Tivoli Workload Scheduler). by adding either or both the SCHID and SPAN operands) has now been removed through the new initialization parameter CA7SPAN. v If you run products. The previous configuration with SUP(YES) AUTO(YES) is no longer valid. then CA7SPAN is taken into consideration and its value is used in the inquiries to CA-7 as SPAN. v Ensure that any MPFLSTxx member used (or any suppression product) does not suppress the following message IDs: CA-7* SPO7* SLIF* nn* (where nn are the last two digits of the calendar year) Notes: 1.DEMAND. Managing Tivoli Workload Scheduler for z/OS jobs The following sections describes how to manage Tivoli Workload Scheduler for z/OS jobs.NO_ENTRY parameter of MPFLSTxx has SUP(YES). 232 IBM Tivoli Workload Scheduler for Applications: User’s Guide . Messages in the format nn* are included because some of the messages issued in response to a CA-7 LRLOG command have no message ID other than the Julian date. then all of the above message IDs must appear in the MPFLSTxx member with SUP(NO).

Reference information 233 . Status unknown. Chapter 27.Managing Tivoli Workload Scheduler for z/OS jobs At a rate defined by the CheckInterval value in the method options file. Tivoli Workload Scheduler rechecks at a rate defined by the bm check status value in its local options file. Tivoli Workload Scheduler checks the status of the occurrence (application) in Tivoli Workload Scheduler for z/OS. A check is made to see if the occurrence or operation is in the current plan. Tivoli Workload Scheduler for z/OS operation states with respect to Tivoli Workload Scheduler Tivoli Workload Scheduler Job State wait wait wait wait exec succ abend abend abend abend extrn Tivoli Workload Scheduler for z/OS Operation State pending undecided wait ready started complete interrupted error deleted Not applicable Not applicable Tivoli Workload Scheduler for z/OS occurrence states Table 65 lists Tivoli Workload Scheduler for z/OS operation occurrence states with respect to Tivoli Workload Scheduler. If it is not found. Table 64. the name of the application. Can occur only when checking a job that is used as a dependency. is passed to the gateway. and optionally the operation. Tivoli Workload Scheduler for z/OS operation states Table 64 lists Tivoli Workload Scheduler for z/OS operation states with respect to Tivoli Workload Scheduler. Tivoli Workload Scheduler for z/OS operation occurrence states with respect to Tivoli Workload Scheduler Tivoli Workload Scheduler Job Stream State Tivoli Workload Scheduler for z/OS Occurrence State wait wait exec succ abend abend abend extrn pending undecided started complete error deleted Not applicable Not applicable. Table 65. Checking Tivoli Workload Scheduler for z/OS jobs To check a Tivoli Workload Scheduler for z/OS job that was not launched by Tivoli Workload Scheduler.

and is considered to exist if the following conditions apply: v The data is cataloged v It is allocated v It is not being used by another task If the data set does not exist. After the z/OS job has been submitted and has successfully completed. v Subsequently to the first check. To check for the existence of a file on z/OS. If this synchronization is not taken into account. For the correct resolution of these external dependencies. Tivoli Workload Scheduler continues to wait and check for the file at a frequency determined by the bm check file option in the localopts file of the fault-tolerant workstation that is hosting the extended agent. the dependency is checked with a frequency determined by the Tivoli Workload Scheduler configuration parameters. Note: Tivoli Workload Scheduler can only use fully qualified data set names for non-partitioned files. v If the external dependency is preceded by another dependency. However. it must be the fully qualified name and not a relative name (for example. A similar problem can occur as the result of a communication failure between the z/OS and Tivoli Workload Scheduler environments that prevents Tivoli Workload Scheduler from determining the status of a z/OS job to satisfy a job dependency. xxxxx. you should schedule the job so that the first dependency check takes place before the z/OS job is submitted. Tivoli Workload Scheduler might wait indefinitely to resolve a job dependency.xxxxx(-1) cannot be used). the external dependency will not be checked until the other dependency is resolved. when creating external dependencies in Tivoli Workload Scheduler on Tivoli Workload Scheduler for Applications z/OS jobs. or months. Tivoli Workload Scheduler passes the file name to the Gateway. 234 IBM Tivoli Workload Scheduler for Applications: User’s Guide . certain timing issues are critical to ensuring that any associated job dependencies are correctly resolved. External dependencies are checked by Tivoli Workload Scheduler in the following circumstances: v If the external dependency on a Tivoli Workload Scheduler for Applications z/OS job is the only dependency in the job. If a Generation Data Group name is to be used. this might not be very frequently. Timing considerations When Tivoli Workload Scheduler checks dependencies on z/OS jobs not launched by Tivoli Workload Scheduler for Applications. Tivoli Workload Scheduler must attempt to resolve the dependency at least once before the z/OS job is submitted. The localopts options are described in the Tivoli Workload Scheduler: Planning and Installation Guide. as the plan might have a period of several days. weeks. Thus. the dependency is checked immediately after the plan is generated or extended. the next periodic check of the dependency by Tivoli Workload Scheduler is able to manage the dependency. The file name is allocated with DISP=OLD.Checking for files on z/OS Checking for files on z/OS The existence of a file can be used as a job dependency in Tivoli Workload Scheduler.

Tivoli Workload Scheduler recognizes that it no longer exists. No further information is provided. This will help in determining the context in which a message was issued. Obtains its condition code and user abend code.Diagnostic information Diagnostic information z/OS jobs submitted by Tivoli Workload Scheduler can fail to complete for a number of reasons. and marks it as abended in Console Manager (Conman) displays. v If a job fails after being started. you should obtain the following: v The CA-7 log v The console log for the interval covering the test period v The job log of the job resulting in error (if this is the case) v The UNIX script file related to that job Chapter 27. ensure the JES log is obtained for the EEWSPACE and EEWSERVE started tasks. if you use CA-7. The step in the submission process in which a job fails determines how much information is available and is provided by Tivoli Workload Scheduler as follows: v If a job fails before it is actually initiated (usually the result of a JCL or security problem). Reference information 235 . Writes them to the job standard list file 3. Marks the job as abend in Console Manager (Conman) or Job Scheduling Console displays Job standard lists can be displayed with the Console Manager (Conman) and with the Job Scheduling Console. Depending on the job scheduling interface you use. Troubleshooting To assist in troubleshooting. Tivoli Workload Scheduler: 1. additional helpful information might be obtained from other logs. For example. if any 2.

Troubleshooting for z/OS 236 IBM Tivoli Workload Scheduler for Applications: User’s Guide .

Common serviceability © Copyright IBM Corp. 2003.Part 6. 2008 237 .

238 IBM Tivoli Workload Scheduler for Applications: User’s Guide .

If you use 239 . Syntax Use the following syntax to create the return code mapping file: [#] “pattern1” “pattern2”. Pattern strings delimited by double quotes (“ and ”).. Job return code mapping provides the following capabilities: v Users can define a job final status (successful or failed) based on a condition on the return code of the execution of the program or script of the job. If this message is received.Chapter 28. For the SAP R/3 access method. All the lines starting with this symbol (#) are not used for mapping. Return code mapping files that are specific to a workstation are named according to the following scheme: TWShome/methods/rcm/<method_name>-<type>-<workstation>.“patternn” = RC value Parameters # patternn © Copyright IBM Corp. Creating a return code mapping file You can create a return code mapping file to customize your own return codes with respect to certain conditions that might affect a job when it runs.. the job state is updated accordingly. The mapping files can be either global or local for a workstation. Use this file to set the success condition of the job.rcm For the Oracle E-Business Suite and PeopleSoft access methods. v The return code can be provided also to the recovery job that is associated with it in the job definition. type is always equal to rcmap.rcm Global mapping files have a file name according to the following scheme: TWShome/methods/rcm/<method_name>-<type>. which Tivoli Workload Scheduler uses to assess if the job completes successfully or in error. This causes the recovery job to perform different processing based on the return code. type is as described in “Return code mapping file names for r3batch” on page 244. 2008 Optional comment. The return code mapping feature The return code mapping feature provides a standard way of mapping messages into return code values. This feature is available for the following access methods: v Oracle E-Business Suite v PeopleSoft v SAP R/3 The return code mapping feature provides more granularity when defining the success or failure policies of jobs and improved flexibility in controlling job execution flows based on execution results. Each method has its own set of files to map the messages into return code values. 2003. You can also customize the return code mapping. The return code is sent to Tivoli Workload Scheduler in the form of a %RC nnnn message.

v Line 2 is blank and is ignored. When you use the asterisk in this way and not as a wildcard. It matches the same messages as the pattern of line 3. 4. but are shown for reference: 1.Return code mapping file syntax only one pattern string. Considerations Note the following facts: v The order of the pattern lines is important as the first matching pattern line is used to build the return code value. then it must be escaped by backslash (\). # This is an RC mapping file for joblog. v Line 4 matches every message starting with three asterisks (*) followed by a blank. “User * missing ” = 102 “\*\*\*” = 103 “User \ * \ missing” = 102 In this example: v Line 1 is a comment and is not used for mapping. but the second pattern line is never used. 5. The line numbers in bold do not belong to the file. v Line 3 matches every message starting with the string User and ending with the string missing. the following is a valid pattern sequence. 7. 6. For example. RC value The return code value. you can omit the double quotes. you need to escape it with a backslash. it is always matched first. 3. Backslash (\) Escape character. “625” “User * missing” = 104 “” “User * missing” = 102 The following pattern sequence is formally valid. All blanks preceding or following a pattern string are ignored. Because the first line is more general. Question mark (?) Matches a single character. v Lines 5 through 7 contain a pattern taking several lines. v Empty pattern strings (“”) are ignored by the pattern matching procedure. 2. This value is sent by the method to Tivoli Workload Scheduler by a %RC nnnn message. as well as those between the equals sign and the return code value. Examples The following is an example of a return code mapping file. The first line is more restrictive than the second line. The string can contain the following wildcards and special characters: Asterisk (*) Matches an arbitrary number of characters. “” “User * missing” = 102 “625” “User * missing” = 104 240 IBM Tivoli Workload Scheduler for Applications: User’s Guide . If the pattern string contains a double quote character.

Table 66. When no return code mapping files are defined. Job states and return codes for the Oracle E-Business Suite access method MCMAGENT job state ″RUNNING″ ″PENDING″ ″COMPLETE″ ″INACTIVE″ ″NORMAL″ ″TERMINATING″ ″PAUSED″ ″RESUMING″ ″STANDBY″ ″SCHEDULED″ ″WAITING″ ″WARNING″ ″ERROR″ ″TERMINATED″ ″DELETED″ ″ON HOLD″ ″DISABLED″ ″NO MANAGER″ ″SUSPENDED″ ″TEST FAILURE″ ″NOT FOUND″ MCMAGENT return code 1 2 3 4 5 6 7 8 9 10 11 13 14 15 16 17 18 19 20 21 22 Table 67. you can write return code mapping files associating the internal states listed in Table 66 and Table 67. the access method uses the respective standard return codes listed in the tables.Return code mapping for psagent and MCMAGENT Return code mapping for psagent and MCMAGENT For the Oracle E-Business Suite and PeopleSoft access method. or when a string returned by the access method does not satisfy any of the matching patterns of the mapping file. Job states and return codes for the PeopleSoft access method psagent job state ″CANCEL″ ″DELETE″ ″ERROR″ ″HOLD″ ″QUEUED″ ″INITIATED″ ″PROCESSING″ ″CANCELED″ ″SUCCESS″ psagent return code 1 2 3 4 5 6 7 8 9 Chapter 28. The return code mapping feature 241 .

Return code mapping for r3batch Using return code mapping with r3batch can be useful in overcoming differences in the return code mechanisms of R/3. and exceptions from RFC function modules into return code values that Tivoli Workload Scheduler can handle. the access method finds the matching pattern and sends a return code value of 1 as listed in Table 66 on page 241."DELETED"=1 In this case. v The return code mapping file is: "NORMAL"=0 "ERROR". Job states and return codes for the PeopleSoft access method (continued) psagent job state ″NO SUCCESSPOSTED″ ″POSTED″ ″NOT POSTED″ ″RESEND″ ″POSTING″ ″GENERATED″ psagent return code 10 11 12 13 14 15 Examples The extended agent for Oracle E-Business Suite returns the TERMINATED string. you can map messages from R/3 logs. These return codes are used together with the rccondsucc keyword set in the extended agent job definition and handled accordingly. the access method does not find the matching pattern and sends a return code value of 15 as listed in Table 66 on page 241. v A return code mapping file exists and is: "NORMAL"=0 "TERMINATED". The resulting return code depends on the following conditions: v No return code mapping file exists. Tivoli Workload Scheduler displays only the r3batch exit code. 3. as listed in Table 66 on page 241. Return code mapping is 242 IBM Tivoli Workload Scheduler for Applications: User’s Guide . 2. the R/3 return messages or codes are mapped into your custom return codes and passed on to Tivoli Workload Scheduler. r3batch reads the output retrieved from the R/3 system (R/3 job log. and so on appended to the stdlist of the related Tivoli Workload Scheduler job). spool list. which returns a mixture of messages and numbers. Following your specifications in the rcm files. spool lists. the method sends a return code value of 15. In this case. In this case."DELETED"=1 In this case. Note that when you do not use this feature. and of Tivoli Workload Scheduler. The return code mapping mechanism works as follows: 1. r3batch does not send any return codes to Tivoli Workload Scheduler. which handles exclusively numeric return codes. By customizing the return code mapping files listed in “Return code mapping file names for r3batch” on page 244. which cannot be used to set up rccondsucc conditions. process chain log.Return code mapping for psagent and MCMAGENT Table 67.

Chapter 28. Please check R/3 *** syslog.Return code mapping for r3batch meaningful only if you use the return codes to write the expressions that determine job completion. the return code sent back to Tivoli Workload Scheduler is 9999 because it is the higher of the two matching patterns. When setting up your return code mapping for r3batch. Could not create and *** start an instance of the R/3 batch job. v If you want to map messages from the R/3 syslog. consider the following: v You can define any return code numbers for your use because there are no reserved return codes for the access method or for Tivoli Workload Scheduler. If you want to map only a part of the entry. the use of rccondsucc is significant only if Tivoli Workload Scheduler gets return codes (not exit codes) from the access method. v If two lines match two different patterns. retrieve_pchainlog. v If no matching takes place.rcm file contains the following matching line: "118""*"=100 while the r3batch-syslog. When you define a mapping file. set the log_r3syslog option to ON and manually create the corresponding rcm file. and retrieve_spoollist options as ON and manually create the corresponding rcm files.rcm file contains the following matching line: "*MAESTRO*Step 1 contains illegal values"=9999 In this case. write the most restrictive strings first. *** ERROR 118 *** EEWO0118E Execution terminated. v When you define a mapping file. In general the return code is set to the highest value among the ones yielded by the matched patterns. *** ERROR 552 *** EEWO0552E The R/3 job scheduling system has found an *** error for user name * and job name PAYT410. leave the default settings of the retrieve_joblog. Conversely. ERROR LEVEL=118 and the system log contains the following line: |011:05:12|MAESTRO|SAPMSSY1|EFT|> Step 1 contains illegal values The r3batch-joblog. v Depending on which R/3 logs you want r3batch to read and map. no return code is sent to Tivoli Workload Scheduler. remember that the R/3 log messages are read in their entirety. *** ERROR 176 *** EEWO0176E Failed to add step 1. This is shown in the following example: The job log returned after job PAYT410 has run is: *** ERROR 778 *** EEWO0778E Failed to modify the job PAYT410 with job id *** 05710310. you must use the wildcard characters. in the case of this extended agent. The return code mapping feature 243 . v Mapping files are scanned sequentially: the first match found performs the corresponding mapping. To use the return code mapping feature: v Leave the value of the rcmap option as ON (this is the default). then the return code is set to the higher value.

the messages in the joblog are ignored. variant GIULIO. user name TWSDEV) will match the following pattern line in TWShome/methods/rcm/r3batchjoblog. The format of the mapping file is: 244 IBM Tivoli Workload Scheduler for Applications: User’s Guide . The R/3 system log should be checked only when R/3 returns the generic 552 error to r3batch.rcm: | "*Step*" "*" "550" "*"=5 because: | | | | | | | | | <message text pattern> "Step 001 started (program BTCTEST. For example. the following line appended in the job log: 04/26/2005 10:08:04 00 550Step 001 started (program BTCTEST. TWShome/methods/rcm/r3batch-joblog. If this file is not present. user name TWSDEV)" <program pattern> "*" <message number pattern> "550" <message id pattern> "*" TWShome/methods/rcm/r3batch-pchainlog. You must manually create the rcm directory under TWShome/methods and the mapping files you want to implement.rcm Maps messages in the job spool list of an R/3 job into return code values. The format of the mapping file is: <message text pattern> [<program pattern>[<message number pattern>[<message id pattern>]]]=RC value where <program pattern> is the external program that produced the output shown in the job log and <message ID pattern> is the message class. the messages in the spool list are ignored. If this file is not present. The format of the mapping file is: <message number pattern> [<message id pattern>[<message variable 1>[<message variable 2> [<message variable 3>[<message variable 4>[<message type>]]]]]]=RC value TWShome/methods/rcm/r3batch-spoollist. the messages in the protocol are ignored. variant GIULIO. The format of the mapping file is: <spool list row pattern>=RC value TWShome/methods/rcm/r3batch-syslog. the messages in the system log are ignored. If this file is not present.rcm Maps messages from the protocol of a Process Chain into return code values.rcm Maps messages from the R/3 job log of a job into return code values. If this file is not present.rcm Maps messages in the syslog of an R/3 system into return code values.Return code mapping file names for r3batch Return code mapping file names for r3batch r3batch uses the global return code mapping files listed below.

jdf containing the following: alias. The return code mapping feature 245 . be sure to set the log_r3syslog option of r3batch to ON (the default is OFF). after defining the appropriate return code conditions in the r3batch-joblog.rccondsucc "Success Condition" where the ″Success Condition″ must match a condition saved in the rcm file. Chapter 28. That is. The format of the mapping file is: <message number>=RC value <message number> is the error message number. 2.icp referring to the jdf file you created as follows: client job_mask user_mask rctemplate Tivoli Workload Scheduler manages the intercepted R/3 job as a docommand job with all the options specified in the customized jdf file. If this file is not present. The last message number is always used. TWShome/methods/rcm/r3batch-msgrc. Create a customized template file named TWShome/methods/r3batch_icp/ rctemplate.rcm Maps ABAP exceptions and BAPI return codes of RFC function modules into return code values.Return code mapping file names for r3batch <system log row pattern>=RC value If you plan to map system log messages. if two error messages are generated. the mapping is done using a hardcoded table. Modify the TWShome/methods/r3batch_icp/CPUNAME_r3batch. only the second one is checked against the mapping file. Mapping return codes for intercepted jobs To set up return code mapping for intercepted jobs.rcm file. You can check if your intercepted job is correctly submitted by reading the job_interceptor joblog. do the following: 1.

Mapping return codes for intercepted jobs 246 IBM Tivoli Workload Scheduler for Applications: User’s Guide .

Customizing the . Configuring the tracing utility This chapter describes how to configure the trace utility for all the access methods. See “R/3 Job page” on page 121 and “Task string to define SAP jobs” on page 129.properties For the PeopleSoft access method. r3evmon.properties file Depending on the access method you are working with. specify the following option in the job definition: -tracelvl=(1|2|3) where: v 1 = DEBUG_MIN v 2 = DEBUG_MID v 3 = DEBUG_MAX © Copyright IBM Corp. mvsjes. DEBUG_MAX A most verbose debug output is written in the trace file.properties. With this access method.Chapter 29. To specify a different trace setting for a particular job.properties For the SAP R/3 access method.properties. you can also specify debug and trace parameters in the single job definitions. | | | | | r3batch.level Specify the level of tracing you want to set.tracers. The value you set in the . Tivoli Workload Scheduler for Applications logs all the processing information in the TWShome/methods/access_method. 2008 247 .trace. Tivoli Workload Scheduler for Applications creates a new file with all the default values and contains the following comment: # This file was automatically created using the default values.properties. depending on the scheduler with which you are working. Note: If you delete this file accidentally. 2003. or mvsca7. This is the default. For each .properties file you can customize the following parameters: access_method. psagent.properties For the Oracle E-Business Suite access method.properties configuration file. customize the trace parameters in the following properties files: mcmagent.properties For the z/OS access method.properties file applies to all the jobs of the corresponding access method. Possible values are: DEBUG_MIN Only error messages are written in the trace file. DEBUG_MID Informational messages and warnings are also written in the trace file. or mvsopc.

traceFile.traceFile. trace-xagent_name-r3evmon. the default is: | | SAP R/3 TWShome/methods/traces All other access methods TWShome/methods Ensure that the new path you specify has already been created as a fully qualified path with write permissions. The trace file name is: trace-mcmagent. trace-psagent.fileDir Specifies the path where the trace file is created.tracers. trace-mvsjes. The trace files give information about the method execution to the desired level of detail.handlers.handlers.trace. Possible values are: true false 1 1 1 1 1 1 1 1 To enable the trace utility. or trace-mvsopc.maxFiles The maximum number of trace files that are created before the oldest one is deleted.traceFile.log For the PeopleSoft access method.properties file access_method. no traces are written in the trace-access_method. If this parameter is set to 1.logging Specifies to enable or disable the trace utility.trace.trace. This parameter is valid only if the r3batch. to guarantee a First-Failure Data Capture (FFDC) ability.trace.handlers. access_method. r3batch. To disable the trace utility.log For the Oracle E-Business Suite access method.log For the SAP R/3 access method. r3batch.log.handlers. Always use slashes (or backslashes) when you specify a new path. The minimum trace level is always on.maxFiles is set to a value greater than 1. This is the default value. If you set this parameter to false.Configuring the .log. Depending on the scheduler with which you are working.traceFile. | | trace-r3batch. or trace-mvsca7. even if you are working on Windows operating systems.log. Traces are written in XML format.trace.maxFileSize The maximum size (in bytes) that the trace file can reach before it is renamed and a new trace file is created. 248 IBM Tivoli Workload Scheduler for Applications: User’s Guide .log For the z/OS access method. the current trace file is never replaced and can grow without limit.log file even if there are problems. Depending on the access method.

handlers.tracers.fileDir=home/maestro/methods r3batch.trace.trace.trace.maxFileSize=104805100 r3batch.maxFiles=3 Chapter 29.properties file is an example of a configuration file for the SAP access method with the following characteristics: v The level of tracing set is DEBUG_MID.traceFile r3batch.traceFile.traceFile.product=TWS4APPS r3batch.trace. r3batch.traceFile. whose maximum size can be 10 MB.trace.formatterName=r3batch. v The trace file is created in the home/maestro/methods directory. 1 v The tracing process creates three trace files.tracers.component=R3BATCH r3batch.trace.traceFile.level=DEBUG_MID r3batch.handlers.organization=IBM r3batch. Configuring the tracing utility 249 .formatter r3batch.tracers.logging=true r3batch.listenerNames=r3batch.handlers.trace.handlers.trace.trace. This means that not only error messages but also informational messages and warnings are written in the trace file.handlers.Configuration file example for the SAP R/3 access method Configuration file example for the SAP access method The following r3batch.

Configuration file example for the SAP R/3 access method 250 IBM Tivoli Workload Scheduler for Applications: User’s Guide .

Cause and Solution: This is due to the value set for the maxdsiz kernel parameter.0 following message: Bundled JRE is not binary compatible with host OS/Arch or it is corrupt. To solve the problem. Table 68. the installation of Tivoli Workload Scheduler for Applications with InstallShield (both interactive and silent).8 and 5. randomly displays the following error message: error calculating the uncompressed size of bundled JRE or it is corrupted Cause and Solution: This is due to a performance problem. set the value of the OPTED_SPB_BEAN. You can ignore the message. Known installation problems Table 68 lists known installation problems. or updating key.Chapter 30.estimatedTimeToInstall parameter to 1000.. even 11i v1 if the installation was successfully performed: Install Shield got an error while updating VPD catalog. 2008 251 .9 Item Symptom: On Solaris version 5. ISMP installation Symptom: On HP-UX version 11i v1. The Tivoli Workload Scheduler for Applications installation completes successfully. Known installation problems Area ISMP installation on Solaris version 5. the installation of Tivoli Workload Scheduler for on HP-UX version Applications with the InstallShield wizard randomly displays the following error message.. Troubleshooting This chapter describes a number of problems that might occur when installing or using Tivoli Workload Scheduler for Applications or the access methods. Set the value to 0x06000000 hex (100663296).. Cause and Solution: This is due to an InstallShield error. Testing bundled JRE failed. © Copyright IBM Corp.8 and 5. ISMP installation Symptom: Installation of Tivoli Workload Scheduler for Applications with InstallShield (both on HP-UX version interactive and silent) fails on specific HP-UX operating systems (HP-UX version 11.0) with the 11.9.. 2003.

Stop the installation program if it remains in pending state or click OK if the message is displayed. Please run the program again using the option -is:javahome JAVAHOME_DIR Cause and Solution: The problem occurs because the installation program cannot find the Java Virtual Machine (JVM) in the /methods/_tools path directory and is looking for it in all the directories.Known installation problems Table 68. proceed as described in “Uninstalling” on page 36. 2. Installing the language pack Symptom: If you cancel the installation of a Tivoli Workload Scheduler for Applications language pack. severity = 0) Cause and Solution: The Tivoli Workload Scheduler for Applications language pack is installed. Wait a few minutes and if the installation program does not continue or the above message is displayed. perform the following steps: 1. Set the JAV AHOME_DIR to twsinstallationdir/methods/_tools using the following command: is:javahome twsinstallationdir/methods/_tools or set the TWS4APPS_JDKHOME environment variable to the following path: twsinstallationdir/methods/_tools In a UNIX environment This variable is located in /etc/profile file. The installation program exits. a Java exception is displayed: ServiceException: (error code = 315. In a Windows environment This variable is located in the HKEYLOCAL_MACHINE->SYSTEM->ControlSet001>Control->SessionManager->Environment->TWS4APPS_JDKHOME registry key. To uninstall it. 252 IBM Tivoli Workload Scheduler for Applications: User’s Guide . it remains in pending state or the following message is displayed: A suitable JVM could not be found. message = "product bean R3BATCH_SOLARIS64_C OMPONENT_BEAN does not exist". Known installation problems (continued) Area Installing the language pack Item Symptom: When installing the Tivoli Workload Scheduler for Applications language pack.

For example./. . Known installation problems (continued) Area Uninstalling the product Item Symptom: You are unable to uninstall Tivoli Workload Scheduler for Applications or its language pack. _xauninst1..jar or twsinstallationdir/methods/_tools/_jvm/jre/bin/ java -jar twsinstallationdir/methods/_lxauninstn/uninstall... and you did not exit from those directories to complete the uninstallation./_xauninst /. v You did not remove the _xauninst or _lxauninst directories after the uninstallation completed successfully. To solve the problem.jar or twsinstallationdir/methods/_tools/_jvm/bin/ Java -jar twsinstallationdir/methods/_lxauninstn/uninstall. Troubleshooting 253 . Chapter 30._xauninstn To uninstall the language pack .... _xauninst2.Known installation problems Table 68. The following directories are present: To uninstall Tivoli Workload Scheduler for Applications . run the following command: On all the operating systems./_lxauninst:._lxauninstn Cause and Solution: Possible causes are: v You launched the uninstaller command from the _xauninst or _lxauninst directories. . n The number of directories that have been created.jar where: twsinstallationdir The directory where you installed the product.jar On HP-UX and Solaris twsinstallationdir/methods/_tools/_jvm/bin/ java -jar twsinstallationdir/methods/_xauninstn/uninstall. except HP-UX and Solaris twsinstallationdir/methods/_tools/_jvm/jre/bin/ java -jar twsinstallationdir/methods/_xauninstn/uninstall.

bin 1 Uninstalling the 1 product 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 Sun Solaris Operating Environment ibm142_swd_solaris.bin ibm-jre-n142p-hpux10-installer. 2. therefore you are unable to: v Uninstall another product package v Use the Option Editor v Submit PeopleSoft jobs Cause and Solution: To install JVM again.bin ibm142_swd_linux. According to your operating system. To install JVM again. Create the directory inst/methods/_tools.bin ibm142_swd_hpia64. run the following command from TWShome/INSTALLER: For Windows setup.Known installation problems Table 68. from inst/methods/_tools run the executable file.bin 4. Known installation problems (continued) Area Item Symptom: Uninstalling the base product or its language pack uninstalls also the Java Virtual Machine (JVM).bin Windows ibm142_swd_win32. From TWShome/INSTALLER copy the following executable file to the inst/methods/_tools directory: AIX HP-UX for PA-RISC HP-UX for Integrity Linux ibm142_swd_aix.exe -is:extract For the other operating systems setup. 254 IBM Tivoli Workload Scheduler for Applications: User’s Guide . perform the following steps: 1.bin -is:extract The JVM file installer is extracted to the TWShome/INSTALLER directory. 3.bin Sun Solaris Operating Environment for Opteron ibm142_swd_solaris2-ix86.

name. state.sh wdlssp Where: product_image opsys | | | | | | | | | | | | | | | | | | | | | | | | | | Uninstalling with twsappsint The Tivoli Workload Scheduler for Applications image file. version. -----------------------------------------------------DISSE0164I Name : TWS4APPS_instance_package DISSE0164I Version : version DISSE0164I State : state -----------------------------------------------------.version Chapter 30. Where: instance package version state The The The The instance package package package name. but the uninstallation process leaves some packages in the catalog..4. try to uninstall the product.Known installation problems Table 68.. Cause and Solution: List the packages that were not removed by running the following commands: cd product_image/opsys/ALT_INST/_swdcli . Troubleshooting 255 .. The product packages that were not removed are shown as follows: .. ./swd_env. From the same shell. uninstall the product packages manually by running the following command: wdrmvsp -f TWS4APPS_instance_package. Known installation problems (continued) Area Item Symptom: You are unable to upgrade to Tivoli Workload Scheduler for Applications version 8. The operating system to which the image file applies.

.version 256 IBM Tivoli Workload Scheduler for Applications: User’s Guide ..Known installation problems Table 68. because monitoring processes were running.sh wdlssp Where: product_image opsys | | | | | | | | | | | | | | | | | | | | | | | | | | Uninstallation with ISMP The Tivoli Workload Scheduler for Applications image file. name. From the same shell./swd_env. Cause and Solution: List the package that was not removed by running the following commands: cd product_image/opsys/ALT_INST/_swdcli . version. state. uninstall the product package manually by running the following command (before uninstalling. . ensure that you stopped all monitoring processes): wdrmvsp -f TWS4APPS_instance_package.. Known installation problems (continued) Area Item Symptom: You are unable to uninstall the extended agent with ISMP. The product package that was not removed is shown as follows: . -----------------------------------------------------DISSE0164I Name : TWS4APPS_instance_package DISSE0164I Version : version DISSE0164I State : state -----------------------------------------------------. The operating system to which the image file applies.. Where: instance package version state The The The The instance package package package name.

no check on the extended agent workstation is made: if the workstation does not exist. For each configuration file. SAP_event_parm The parameter associated with the SAP event to monitor. see “SAP events matching criteria” on page 191. The port that the master domain manager uses to receive the event notification. The format is nnnn. For UNIX only. Solution: Ensure that the extended agent workstation you specified in the SAP event definition exists. r3evmon -t SEM -c XAname -. 0008. Solution: The SAP events being monitored are listed in the following file: twshome/monconf/XAname_r3evmon. The host name or IP address of the master domain manager. For example. Check that the file is updated and contains the current monitoring plan."[-EIFSRV EIF_server -EIFPORT EIF_port]" where: XAname EIF_server EIF_port r3batch: monitoring SAP events is not performed The name of the extended agent workstation. 0007. Notes: 1. Miscellaneous troubleshooting items Area Item Symptom: The SAP events on which the event rule is based are not monitored nor committed. if any. the command prompt is not returned until the process completes. in the format nnnn. When you define an SAP event within an event rule. if the event name is SAP_PAR. Troubleshooting 257 . Table 69. SAP_event_parm_length The length of the parameter associated with the SAP event to monitor. the event rule is saved and activated but it will never be resolved. if the event name is SAP_TEST. if any. Chapter 30. This value is optional. enter the following command. but omitting it identifies an SAP event with no parameter associated.cfg and the SAP system. For details about how the events are matched between r3evmon.Other known problems Other known problems Table 69 lists miscellaneous troubleshooting problems. r3evmon must be entered by the owner of the Tivoli Workload Scheduler installation: 2. To start an r3evmon monitoring process for a specific extended agent workstation. SAP_event_name The name of the SAP event to monitor. If you run r3evmon from a Windows DOS shell. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | r3batch: monitoring SAP events is not performed Symptom: The SAP event on which the event rule is based is neither monitored nor committed.cfg where XAname is the name of the SAP extended agent workstation. an r3evmon process is started to monitor the SAP events listed. The SAP events are indicated by the following keyword (one for each SAP event on the same extended agent): !R3EVENT SAP_event_name_lengthSAP_event_name[SAP_event_parm_lengthSAP_event_parm] where: SAP_event_name_length The length of the SAP event name to monitor. For example.

0. Symptom: The events on which the event rule is based are not monitored or no event is generated during IDoc monitoring. Check that the file is updated and contains the current monitoring plan. For a list of the supported IDoc fields.cfg where XAname is the name of the SAP extended agent workstation. refer to Table 49 on page 196. The events corresponding to the IDOCEventGenerated event type are indicated by the following keyword (one for each event on the same extended agent): !IDOC nnnn<Client Number>nnnn<IDoc Status List>nnnn<Direction>nnnn<Receiver Port> nnnn<Receiver Partner Type>nnnn<Partner Function of Receiver> nnnn<Partner Number of Receiver>nnnn<Sender Port>nnnn<Sender Partner Type> nnnn<Partner Function of Sender>nnnn<Partner Number of Sender> nnnn<Message Type>nnnn<IDoc Type>nnnn<Logical Message Variant> nnnn<Logical Message Function>nnnn<Test Flag>nnnn<Output Mode> where: nnnn The length of the IDoc field. For example. It is the same file used to monitor SAP events in general. Solution: Ensure that the SAP event was not excluded from logging in the SAP event history table. the SAP event is raised but Tivoli Workload Scheduler is not notified and therefore does not act as expected. 258 IBM Tivoli Workload Scheduler for Applications: User’s Guide . 0005 indicates the value of an IDoc status list corresponding to 56. <> Contains the value of the field associated with the IDoc to be monitored. Make sure that an r3evmon monitoring process is started for the involved extended agent workstation. an r3evmon process is started to monitor the events listed.Other known problems Table 69. Solution: The events being monitored are listed in the following file: twshome/monconf/XAname_r3evmon.60. Solution: Refer to SAP Notes 1021071 and 1109413. | | | | | | r3batch: monitoring SAP events is not performed 1 r3batch:IDoc 1 monitoring is not 1 performed 1 1 1 1 1 1 r3evmon: monitoring SAP and IDoc events increases memory consumption Symptom: Memory consumption increases continuously during monitoring of IDoc and standard SAP events. For each configuration file. Miscellaneous troubleshooting items (continued) Area Item Symptom: With XBP 3.

check the date and time in the XAname_r3idocmon. 1 1 1 1 r3batch: Duplicated events generated during IDoc monitoring 1 r3batch: No event Symptom: The expected event actions are not triggered. Use the following format for the start date and time: start_date=YYYYMMDD start_time=HHMMSS For example: start_date=20080307 start_time=115749 Check the value of the idoc_no_history option: v If it is set to OFF and no XAname_r3idocmon. v If it is set to ON (default value).cfg where XAname is the name of the SAP extended agent workstation. then all matching IDocs are retrieved. J_101_REPORT_ALL_SELECTIONS please install the latest ABAP routine for Maestro!! Solution: This defect is caused by an error in an SAP function module.cfg file.cfg file. Troubleshooting 259 . r3batch: error message when scheduling SAP jobs Symptom: When creating an SAP job. Chapter 30. the XBP 2.Other known problems Table 69. except the variant name of the first step (which is provided as the option parameter). These values are stored in the following file: twshome/monconf/XAname_r3idocmon. SAP describes this problem and possible solutions in the SAP notes 0351293 and 0116354. As a consequence. 1 IDoc monitoring check the date and time in the XAname_r3idocmon. delete the XAname_r3idocmon.0 interface ignores the user parameter passed by r3batch. not only the current ones.cfg file and then start r3evmon again. the following message is displayed while trying to view the details of an ABAP’s variant: AWSO0101E Missing ABAP routine. r3batch gets error 221: MSG_CANNOT_GET_PRIARC_PARAMS: "Retrieving new print and archive parameters failed" The problem is solved by installing SAP note 758829.OR v Stop r3evmon. and subsequently. if it is set to ON (default value). The problem is solved by installing SAP note 758829. Miscellaneous troubleshooting items (continued) Area Item Symptom: The action defined in an event rule with IDOCEventGenerated event type is unexpectedly repeated. r3batch creates a job by copying all the data from the original template. they are incorrect. r3batch: modify job step error You change print parameters with the BAPI_XBP_MODIFY_JOB_STEP function module. r3batch: modify job step error The BAPI_XBP_MODIFY_JOB_STEP function module always uses the name of the logged-on user as the name for the step user. However. Solution: Reset the start date and time for the next monitoring loop. when adding a step to a new job. set the date and time in the XAname_r3idocmon. and startr3evmon again.cfg file exists. In this case. This procedure is usually referred to as the ″old copy″. . when submitting a job with the -vX options. 1 is generated during Solution: Check the value of the idoc_no_history option. Therefore you can either: v Stop r3evmon.cfg file to the values you want.

Verify that your Oracle naming methods are set correctly.Launch job failed Solution: Submitting an Oracle job might fail because there is a connection problem to the Oracle database.java:220) Cause and Solution: The psjoa. refer to the Oracle Net Services Administrator's Guide.<clinit>(JoltSessionAttributes.getJoltSession(JoltSessionPool.JoltSessionPool.Other known problems Table 69.EEWP0027 Error . changed to active psagent: misleading message displayed if the local options file has no right permissions The job log shows the following message: EEW00439E You did not specify the required options either in the global or in the local options file.JoltSessionAttributes.java:363) at psft.pt8. Define a path without special characters. Exit code: 1.net.ExceptionInInitializerError at bea.java:183) at psft.createConnection(JoltSessionPool. For details about how to configure naming methods. 260 IBM Tivoli Workload Scheduler for Applications: User’s Guide .7 Symptom: An S047 abend is returned if the EEWSERVE started task does not have an associated RACF owner ID. subchain.net. Solution: In the RACF database.JoltSessionPool. No messages written in the job log The submission of a PeopleSoft job fails Symptom: Tivoli Workload Scheduler for Applications does not write any messages in the job log if the file system for tracing is full or the ljuser does not have the correct permission to write in the trace directory. the status of the original process chain is not Solution: Refer to SAP Note 1075876.jar path contains special characters. but all the mandatory options were correctly set in the options file. Symptom: The submission of a PeopleSoft job fails and the Tivoli Workload Scheduler job log contains a Java exception similar to the following: Exception in thread "3194" java. | | | | | | | The submission of an Oracle job fails Symptom: The submission of an Oracle job fails and the Tivoli Workload Scheduler job log shows the following information: EEWP0017 Child MCMLJ exited normally. the status of the original process chain the process of a is not changed to active.pt8.jolt. mvsjes: RACF authorization problem on z/OS version 1.lang. Miscellaneous troubleshooting items (continued) Area Item 1 1 1 1 1 1 When you restart Symptom: When you restart the process of a subchain. Check that the options file has read and write permissions available to the user who is trying to launch the job. associate an authorized RACF ID with the EEWSERVE started task as specified in “Setting RACF authorizations on z/OS” on page 211.

ensure that you choose a dummy report. you can either: v Choose another existing report. In the panel that opens. 2. replace the host name with the IP address. this means that communication between r3batch and the SAP R/3 application server is down.0. v Note that using the SAP R/3 routers to access the R/3 system could exceed the size of internal buffers of the RFC library used to store the hostname of the SAP R/3 system. v If the SAP R/3 gateway truncates the connection string. When this occurs. v Log on to the SAP R/3 system as an administrator and verify that the Tivoli Workload Scheduler RFC user (created in the “Creating the IBM Tivoli Workload Scheduler RFC user” on page 95) exists. do not fully qualify the name of the SAP R/3 routers or alternatively use the IP addresses. causing the connection to the R/3 system to fail.OR v Set the placeholder_abap_step option to a custom developed ABAP code of your choice. Check if the BCTEST report is defined in your SAP system by invoking either one of the following transactions: SA38 SE38 Enter BTC* and click the picklist button. click the picklist button and check if BTCTEST is shown in the list that is displayed. Because the report assigned to the placeholder job is run when the corresponding event is raised. This shows basic network connectivity. when you try to define an internetwork dependency based on an SAP event the following error message is displayed: *** ERROR 778 *** EEWO0778E An internal error has occurred.S. v If r3batch runs on an AIX system that does not use U. Troubleshooting the SAP R/3 connection If you are unable to submit SAP R/3 jobs using Tivoli Workload Scheduler after the R/3 configuration. in the local options file. Language Environment is installed on both the IBM Tivoli Workload Chapter 30.Other known problems Table 69. Enter BTC* and click the picklist button. the hostname gets truncated. set the placeholder_abap_step option to the name you chose. Troubleshooting 261 . The program could not modify the following job: Job name: Job ID: %CJ ERROR Solution: Perform the following steps: 1. Check if BTCTEST is shown in the list that is displayed. and. If report BTCTEST is not found in the list. . Miscellaneous troubleshooting items (continued) Area Error defining an internetwork dependency based on SAP event Item Symptom: If you work with XBP 2. perform the following tests: v Ensure you can ping the SAP R/3 system from the Tivoli Workload Scheduler system. English. If the command fails to complete.S. make sure that the U. see Table 33 on page 106. For details about the placeholder_abap_step option. To work around this problem. v Run the following telnet command to verify connectivity: telnet systemname 33xx where systemname is the system name or IP address of the SAP R/3 server and xx is the SAP R/3 instance.

Otherwise the error BAD TEXTENV (or a similar error message) might appear in the dev_rfc trace file and connections to SAP R/3 fail. 262 IBM Tivoli Workload Scheduler for Applications: User’s Guide .Troubleshooting the SAP R/3 connection Scheduler workstation and the SAP R/3 database workstation.

v The messages. IBM Tivoli message format This section describes the format of the message that is displayed on your screen or written in a log file.component codes Message set description twsappsinst installation z/OS gateway PeopleSoft access method R/3 access method Oracle access method Message component ID EEW EEW EEW EEW EEW AI I N O P Page number of message help 266 270 276 278 313 314 Tivoli Workload Scheduler for HTWGT Visualized Data Centers. Messages This chapter describes many of the messages issued by Tivoli Workload Scheduler for Applications and its agent processes. Message number Tivoli Workload Scheduler for Applications message numbers (codes) have the following format: <xxx><component_code><numeric_identifier><severity> where the parts of the message are as follows: | | | <xxx> The product prefix. The following table helps you to find message help for a specific component. This help consists of an explanation of the message. Table 70. © Copyright IBM Corp.Chapter 31. This chapter also includes help for many of the more important error and warning messages. presented in alphabetic order of the subcomponent codes. because they are complete within themselves. 2003. and information about what you should do to solve the problem. It is divided into the following sections: v “IBM Tivoli message format” explains the message standard used by Tivoli Workload Scheduler for Applications. and do not need further explanation. which can be: EEW For all Tivoli Workload Scheduler for Applications messages. 2008 263 . A message consists of a message number and a message text. Tivoli Workload Scheduler for Applications messages . These items are described in more detail in the following sections. a description of what the system does. used by the PeopleSoft access method Note: This guide does not contain any details about Informational messages.

or request information from users in cases where the outcome will not be negative. but the program can continue. Examples: v The replay table could not be sent. 3-. Tivoli Workload Scheduler for Applications Oracle access method messages. v A file already exists with the same name. as follows: AI I O P N Tivoli Workload Scheduler for Applications twsappsinst installation messages. used by the PeopleSoft access method messages. Examples: v The status request is processing. <numeric_identifier> A 2-. Tivoli Workload Scheduler for Applications z/OS gateway messages. The link to Agent_name proceeds with a reduced replay protocol. <severity> The severity indicator. v Do you want to save your output in file a or in file b? W Warning: Warning messages indicate that potentially undesirable conditions have occurred or could occur. Warning messages often ask users to make decisions before processing continues. Examples: v The specified file could not be found. v The files were successfully transferred. <component_code> An alphabetic code for the Tivoli Workload Scheduler for Applications component. An example of an error message number is as follows: EEWAI004E 264 IBM Tivoli Workload Scheduler for Applications: User’s Guide . Tivoli Workload Scheduler for Applications R/3 access method messages. regardless of the response. Do you want to overwrite this file? E Error: Error messages indicate problems that require intervention or correction before the program can continue. The file cannot be saved to this drive. v You are out of space on the x drive. or 4-digit numeric identifier that is unique within any combination of prefix and component code. Tivoli Workload Scheduler for Applications PeopleSoft access method messages. as follows: I Informational: Informational messages provide users with information or feedback about normal events that have occurred or are occurring.Message format | | | HTWGT For Tivoli Workload Scheduler for Visualized Data Centers.

describing the type of information referred to by the variable. Operator response What you should do in response to the condition that caused the message. this variable information is represented in this guide by an italicized label.Message format Message text Every attempt has been made to represent the message text exactly as it appears to the user in the displayed or written message. The link to agent_name will proceed with a reduced replay protocol. of the message text. but sometimes you will be asked to contact IBM Software Support. where necessary. This help provides the following: Explanation An explanation. the message text shown in the guide would be: The replay table could not be sent. For example. Any differences that occur are usually caused by the different layout of the book (in two columns) with respect to the message display panel or log. Where the system has included variable information in the message text. Messages 265 . Often you will be able to resolve such conditions yourself. System action A description of what the system or process does as a result of the condition that caused the message. Chapter 31. The link to TRC8470 will proceed with a reduced replay protocol. See also A reference to any Tivoli Workload Scheduler for Applications documentation that might give you assistance with understanding or resolving the problem. if the message text that appears on your screen is: The replay table could not be sent. Message help This chapter provides you with help for many of the more important error and warning messages. In this case the label agent_name tells you that the information that will be inserted by the system is the name of the agent which could not receive the replay table.

266 IBM Tivoli Workload Scheduler for Applications: User’s Guide . The operation is not performed. Explanation: See message. or run the installation as a user that has the required permissions. To verify the syntax use the following command: twsappsinst -u. Operator response: Analyze the log file. this refers to the language of the installation program. The following option is specified more than once: "option_name" Explanation: See message. For detailed information. EEWAI003E The "twsappsinst" installation program cannot uninstall Tivoli Workload Scheduler for Applications. either give yourself the required permissions. that you copy the entire CD to hard disk. Operator response: Correct the syntax and resubmit the command. For detailed information. correct the error. EEWAI002E The installation program cannot convert the Software Distribution catalog correctly. that all required files have been copied. Operator response: Analyze the log file. not the language of the installed product. Ensure that if you have copied the installation program and its associated files from the product CD. EEWAI004E The installation program cannot install Tivoli Workload Scheduler for Applications. In this case. either give yourself the required permissions. refer to the log file: log_file_name Explanation: See message. and resubmit the installation. System action: The installation program stops. Explanation: See message. EEWAI006E There is a syntax error in the installation option specification. For detailed information. and resubmit the installation. correct the error. or run the installation as a user that has the required permissions. System action: The installation program stops. correct the error. v You do not have the root permissions necessary to perform the operation. The operation is not performed. The installation is not completed. Explanation: See message. Ensure that if you have copied the installation program and its associated files from the product CD. that all required files have been copied.AI This section lists error and warning messages that might be issued by the Tivoli Workload Scheduler for Applications twsappsinst installation method. You are recommended that if you do not want to run the installation directly from the CD. The language of the installation program will default to English. See also: The User’s Guide for details of the command syntax. refer to the log file: log_file_name. In this case. EEWAI007E There is a syntax error in the installation option specification. Explanation: See message. Operator response: Analyze the log file. Note.EEWAI002E • EEWAI008W twsappsinst installation messages . To verify the syntax use the following command: twsappsinst -u. and resubmit the uninstallation. v One or more of the files needed to perform the installation are missing. Possible causes can be: EEWAI008W The supplied language ID: " language_ID" is not valid. The operation is not performed. refer to the log file: log_file_name. Possible causes of the error can be the following: v One or more of the files needed to perform the uninstallation are missing. System action: The installation program stops. See also: The User’s Guide for details of the command syntax. You are recommended that if you do not want to run the uninstallation directly from the CD. The uninstallation is not performed. The correct syntax is as follows: "option_name". to ensure to maintain the correct relationship between the files used by the installation program when performing the uninstallation. System action: The "twsappsinst" installation program stops. v You do not have the root permissions necessary to perform the operation. that you copy the entire CD to hard disk. System action: The installation program stops. Operator response: Correct the syntax and resubmit the command. to ensure to maintain the correct relationship between the files used by the installation program when performing the installation.

See also: The User’s Guide for details of the command syntax. The operation is not performed. Explanation: See message. Chapter 31. EEWAI016E There is a syntax error in the installation option specification. To verify the syntax run the following command: twsappsinst -u. Explanation: See message. Operator response: Resubmit the command specifying at least one of the required options.EEWAI009E • EEWAI017E System action: The process continues. See also: The User’s Guide for details of the command syntax. EEWAI011E There is a syntax error in the installation option specification. System action: The installation program stops. ensuring that the installation option is supplied only once. Operator response: Either add root permissions to the user you were logged on as and resubmit the installation. Messages 267 . Operator response: None. See also: The User’s Guide for details of the command syntax. EEWAI015E There is a syntax error in the installation option specification. System action: The installation program stops. The operation is not performed. or logon as a user with root permissions and resubmit the installation. System action: The installation program stops. See also: The User’s Guide for details of the command syntax. "-languages". The operation is not performed. Operator response: Verify the supported operating systems and choose a different operating system on which to install Tivoli Workload Scheduler for Applications. Explanation: See message. See also: The User’s Guide for details of the command syntax. Operator response: Resubmit the command. The "option_name" option is not allowed when the "option_name" option is specified. EEWAI010E You must have root permissions to run the "twsappsinst" installation program. specifying one of the options listed above as the first option. EEWAI009E The "twsappsinst" installation program does not work on the operating_system_name operating system running on this computer. The operation is not performed. EEWAI017E There is a syntax error in the installation option specification. To verify the syntax run the following command: twsappsinst -u. The first option specified must be one of the following: "-install". The operation is not performed. System action: The installation program stops. System action: The installation program stops. Explanation: See message. ensuring to supply the correct combination of options. EEWAI013E There is a syntax error in the installation option specification. Explanation: See message. You must specify at least one option to run the "twsappsinst" installation program. System action: The installation program stops. The operation is not performed. Operator response: Resubmit the command. The following option is specified more than once: "option_name". System action: The installation program stops. Operator response: Resubmit the command. "-upgrade". See also: The User’s Guide or Release Notes for the list of supported operating systems. To verify the syntax run the following command: twsappsinst -u. Operator response: Resubmit the command. To verify the syntax run the following command: twsappsinst -u. "-uninst". Explanation: See message. The option_name option can only be specified when the option_name option is specified. ensuring to supply the correct combination of options. Explanation: See message. The operation is not performed. To verify the syntax run the following command: twsappsinst -u.

Operator response: Resubmit the command. System action: The installation program stops. If Tivoli Workload Scheduler is installed in a directory other than the home directory of the TWSuser. Operator response: Verify in the User’s Guide which options are available for the operating system where you are installing the product. 268 IBM Tivoli Workload Scheduler for Applications: User’s Guide . ensuring that all the required options are specified correctly. EEWAI020E There is a syntax error in the installation option specification. EEWAI022E The TWSuser that was specified: "user_name" is not the TWSuser of any Tivoli Workload Scheduler installation. The option_name option cannot be specified for the operating_system operating system. System action: The installation program stops. The operation is not performed. See also: The User’s Guide for details of the command syntax. See also: The User’s Guide for details of the command syntax. To verify the syntax run the following command: twsappsinst -u. Operator response: Resubmit the command. See also: The User’s Guide for details of the command syntax. ensuring that the options you require are specified correctly. Operator response: Resubmit the command. Operator response: If Tivoli Workload Scheduler is installed in a path that includes spaces. and should resubmit the command without any spaces in the installation directory path. Explanation: See message. Either choose to install the product on a different operating system. Install Tivoli Workload Scheduler using this TWSuser. System action: The installation program stops. Explanation: See message. Otherwise. Operator response: Do one of the following: v Resubmit the command. System action: The installation program stops. resubmit the installation command. The operation is not performed. and then resubmit this command as before. The operation is not performed.EEWAI018E • EEWAI025E EEWAI018E There is a syntax error in the installation option specification. An unrecognizable option has been specified: "option_name". change that path so that there are no spaces in it. See also: The User’s Guide for details of the command syntax. and resubmit the command. The operation is not performed. System action: The installation program stops. Explanation: See message. A required option was not specified: "option_name". Explanation: See message. ensuring that at least one "LJuser" is specified. EEWAI025E The supplied Tivoli Workload Scheduler directory path contains blank characters. The operation is not performed. Explanation: See message. you have supplied an incorrect path. See also: The User’s Guide for details of the command syntax. System action: The installation program stops. To verify the syntax run the following command: twsappsinst -u. The operation is not performed. EEWAI019E There is a syntax error in the installation option specification. Explanation: See message. EEWAI021E There is a syntax error in the installation option specification. To verify the syntax run the following command: twsappsinst -u. Explanation: See message. EEWAI023E The installation program cannot locate the home directory of the specified TWSuser: "user_name". At least one "LJuser" must be specified with the "-install" option. which are not permitted. The operation is not performed. Operator response: Verify that the TWSuser you specified has an associated home directory and ensure that it contains Tivoli Workload Scheduler. System action: The installation program stops. or install the product on the original operating system but using only the permitted options. specifying a different TWSuser that is the valid TWSuser of a Tivoli Workload Scheduler installation. supplying the following option to identify the installation directory of Tivoli Workload Scheduler: -inst_dir <TWS_installation_directory>.

supplying the correct name of the Tivoli Workload Scheduler directory. EEWAI036E The value of the "-psjoapath" option does not point to a valid psjoa. the "-psjoapath" option can be specified only if "-ps_ljuser" is also specified. The operation is not performed. ensuring that the full path to an existing psjoa. Using the "-install" option. Explanation: See message. System action: The installation program stops. Correct the error and resubmit the installation program.jar file is specified as the "-psjoapath" option value. looking at the messages that preceded this one. See also: The User’s Guide for details of the command syntax. EEWAI035E There is a syntax error in the installation option specification. Explanation: See message. Operator response: Resubmit the command.EEWAI026E • EEWAI036E EEWAI026E The supplied Tivoli Workload Scheduler directory does not exist: "TWS_installation_directory". To verify the syntax run the following command: twsappsinst -u. Chapter 31. The operation is not performed. Operator response: Resubmit the command. System action: The installation program stops. System action: The installation program stops. EEWAI027E The installation program failed for an unspecified reason. For details. Operator response: Resubmit the command. See also: The User’s Guide for details of the command syntax. Operator response: Analyze the log file. Explanation: See message. Explanation: See message. System action: The installation program stops. ensuring that "ps_ljuser" is also specified. The operation is not performed. The operation is not performed.jar file. Messages 269 . see the log file: "log_file_name".

z/OS gateway messages . Table 71 includes a list of these modules. Most messages contains a reference to modules. z/OS module names Module Name EEWPRE84 EEWTCP00 EEWTCP01 EEWTCP02 EEWTCP05 EEWTCP07 EEWTCP08 EEWTCP10 EEWTCP15 EEWTCP20 EEWTCP21 EEWTCP22 EEWTCP23 EEWTCP25 EEWTCP26 EEWTCP27 EEWTCP30 EEWTCP31 EEWTCP32 EEWTCP84 EEWTCP87 EEWTCP88 EEWTCP89 EEWTCP90 EEWTCP91 EEWTCP92 EEWTCP93 EEWTCP94 EEWTCP95 EEWTCP96 EEWTCP97 EEWTCP98 EEWTCP99 EEWTCPC7 EEWTCPCA Description Previous SMF exit Main processing routine Server test vehicle Main dataspace construction routine Establish ESTAE routine to issue failure message Find data set name associated with open ACB/DCB Find data set name associated with DDNAME Initialize and examine variables Locate and initialize control blocks Locate and initialize control blocks Client test vehicle Client test vehicle Client test vehicle Concurrent server Concurrent server Interlink TCP/IP provider Concurrent server for Openconnect TCP/IP stack Child server task Child server task for Interlink TCP/IP stack Child server task SMF record exit for SMFEWTM IBM Tivoli Workload Scheduler interface IBM Tivoli Workload Scheduler interface post CA-7 BTI Issue command and wait for response Issues TERROR to format messages and issues WTOS Find substring within string Issue CA-7 command and wait for response STIMER exit to post ECB past in parm Calls IKJEFF02 to extract buffer using EEWTCP99 ESTAE routine to issue failure message Calls IKJEFF19 (DAIRFAIL/VSAMFAIL) to issue message Calls IKJEFF02 to issue message from EEWTCP99 Message table Check CA-7 job Check application request handler 270 IBM Tivoli Workload Scheduler for Applications: User’s Guide . Table 71.I This section lists error and warning messages issued by the z/OS gateway processes.

In Tivoli Workload Scheduler they are always displayed in their complete form. For a detailed list. These messages appear with different characteristics in the z/OS system and on the Tivoli Workload Scheduler. The name of the label in the source code nearest to the instruction that failed. z/OS module names (continued) Module Name EEWTCPCF EEWTCPCJ EEWTCPCO EEWTCPCV EEWTCPED EEWTCPEJ EEWTCPFJ EEWTCPIA EEWTCPIE EEWTCPKJ EEWTCPKO EEWTCPL7 EEWTCPLJ EEWTCPLO EEWTCPQ7 EEWTCPQJ EEWTCPQO EEWTCPQS EEWTCPRC EEWTCPSC EEWTCPSE EEWTCPUC EEWTCPWT EEWTCPXX Description Check file request handler Check job request handler Check operation request handler Enumerate job String encrypt/decrypt Enumerate job request handler Free job request handler Insert application String initialization Kill job request handler Delete IBM Tivoli Workload Scheduler application Launch CA-7 job request handler Launch job request handler Insert IBM Tivoli Workload Scheduler application Query CA-7 job request handler Query job request handler Query IBM Tivoli Workload Scheduler application Query subsystem request handler Return code System abend String encryption/decryption User abend Wait for specified amount of time Invalid request handler All the messages listed below are written in the EEWSPACE or in the EEWSERVE log files.EEWI01E Table 71. see Table 71 on page 270. One possible cause might be a TCP/IP connection problem. The name of the macro after that the error message was issued. yymmdd hhmmss The date and time the error occurred. MACRO macro NEAR LABEL label WITH RETURN CODE = reason code & REASON CODE = reason code module The name of the module that issued the message. Messages 271 . macro label Explanation: The specified module failed because an error occurred in the specified macro. This is because the maximum length of each text record is 251 characters. In the z/OS system log the messages appear in the text of another message and in some cases they might appear truncated. Chapter 31. EEWI01E yymmdd hhmmss module FAILED. In the files the messages are written starting from column 1. for example EEWI27I. These are the files indicated in the SYSTSPRT DD card of the respective procedure. except for the messages that do not contain the date and time after the message identifier.

MACRO macro NEAR LABEL label WITH RETURN CODE = return code & ERROR NUMBER = error number Explanation: The specified module ended abnormally with the specified reason code. see Table 71 on page 270. For a detailed list. Explanation: You specified an invalid value for the TERMINATOR parameter. This message is issued by the ESTAE routine. For a detailed list. If the problem persists contact IBM Software Support for assistance. yymmdd hhmmss The date and time the error occurred. The name of the macro after which the error message is issued. The offset value. return code error number data set dd label System action: The system proceeds. EEWI02E yymmdd hhmmss module FAILED. module The name of the module that issued the message. The reason code value. If the problem persists contact IBM Software Support for assistance. see Table 71 on page 270.EEWI02E • EEWI18E return code reason code The return code value. One of the possible causes can be TCP/IP connection problem. For a detailed list. For a detailed list. module The name of the module that issued the message. If the problem persists contact IBM Software Support for assistance. module The name of the module that issued the message. The reason code value. term System action: The system stops. The error number. reason code System action: The system stops. EEWI08S yymmdd hhmmss module FAILED. Operator response: Set SVCDUMP to YES collect the dump and send it to IBM Software Support for assistance. yymmdd hhmmss The date and time the error occurred. The internal dd. The name of the label in the source code nearest to the instruction that failed. module The name of the module that issued the message. yymmdd hhmmss The date and time the error occurred. v You are authorized to use the specified data set. The value you assigned to the TERMINATOR parameter. For a detailed list. EEWI18E yymmdd hhmmss module INVALID TERMINATOR term offset System action: The system stops. see Table 71 on page 270. module The name of the module that issued the message. If the problem persists contact IBM Software Support for assistance. v The data set is not in use. System action: The system proceeds. The return code value. The name of the label in the source code nearest to the instruction that failed. yymmdd hhmmss The date and time the error occurred. see Table 71 on page 270. Operator response: Restart the start task that contains the module. 272 IBM Tivoli Workload Scheduler for Applications: User’s Guide . AT OFFSET offset Explanation: See text. macro label Explanation: The specified data set is not available. Operator response: Verify one of the following conditions: v The data set was not deleted. Operator response: Verify the return code and the reason code specified in the message to understand the error. Operator response: Verify the return code and the error number specified in the message to understand the error. EEWI10S yymmdd hhmmss module ABENDED WITH ASSOCIATED REASON CODE reason code System action: The system proceeds. yymmdd hhmmss The date and time the error occurred. EEWI15E yymmdd hhmmss module DATASET ″dataset″ DDNAME ″dd″ FAILED TO OPEN NEAR LABEL label Explanation: The specified module failed because an error occurred in the specified macro. see Table 71 on page 270. The name of the data set that failed to open.

see Table 71 on page 270. The name of the variable that has an invalid value. The default value is x’25’. yymmdd hhmmss The date and time the error occurred. For a detailed list. label Explanation: There is no further help information available. label System action: The system stops. yymmdd hhmmss The date and time the error occurred. Possible values are: System action: The system stops. EEWI24E yymmdd hhmmss module NEAR LABEL label error description Explanation: See text. EEWI19E yymmdd hhmmss module near label label invalid value found name = value v Unkwown status in occurrence record v IBM Tivoli Workload Scheduler current plan status in not active System action: The system stops. System action: The system proceeds.EEWI19E • EEWI30S Operator response: Specify a valid value for the TERMINATOR parameter and restart the start task. v The input arrival date and time specified during the submission is outside the current plan validity interval. Operator response: If the problem persists. see Table 71 on page 270. EEWI30S yymmdd hhmmss module CA7SPAN MUST BE 4 DIGITS IN FORMAT HHMM Explanation: The IEFU84 exit is not active. EEWI27I APPLICATION application WAS INSERTED IN CURRENT PLAN WITH INPUT ARRIVAL DATE AND TIME yymmdd hhmmss Explanation: You specified an invalid value for the TERMINATOR parameter. The default value is x’25’. module The name of the module that issued the message. application iadatetime The name of the application that was not submitted in the current plan. module The name of the module that issued the message. contact IBM Software Support for assistance. EEWI28W yymmdd hhmmss APPLICATION application WAS NOT INSERTED IN CURRENT PLAN WITH INPUT ARRIVAL DATE AND TIME iadatetime name value System action: The system stops. Operator response: Specify a valid value for the TERMINATOR parameter and restart the module. yymmdd hhmmss The date and time the error occurred. v You did not already submit this application with the same input arrival date and time. The name of the label in the source code nearest to the instruction that failed. yymmdd hhmmss The date and time the error occurred. see Table 71 on page 270. module The name of the module that issued the message. see Table 71 on page 270. label error description Chapter 31. module The name of the module that issued the message. Operator response: Specify a value for the CA7SPAN in the correct format and restart the module. yymmdd hhmmss The date and time the error occurred. For a detailed list. For a detailed list. The actual value of the variable. The input arrival date and time. Operator response: Activate the IEFU84 exit. The name of the label in the source code nearest to the instruction that failed. For a detailed list. Operator response: Verify the following: v The date and time on which you submitted the application is outside the validity interval specified when the application was defined. The description of the error. Explanation: The IEFU84 exit is not active. Messages 273 . The name of the label in the source code nearest to the instruction that failed. EEWI20E yymmdd hhmmss module NEAR LABEL label FAILED TO FIND ACTIVE SMF IEFU84 EXIT Explanation: The specified application was not submitted in the current plan.

Operator response: Reissue the request. EEWI38I jobname (jobid) n1 n2 result restype System action: The system proceeds. System action: The system proceeds. CA-7. The name of the application that was submitted in the current plan. jobid n1 n2 result The identifier of the job. and OPCINTERFACE and restart the started task. member The name of the member containing the JCL. Operator response: Define the application correctly in the Tivoli Workload Scheduler for z/OS database and restart the request. see Table 71 on page 270. | EEWI34W | APPLICATION application CANNOT BE INSERTED IN THE CURRENT PLAN Explanation: See text. supplying only one of the indicated parameters. otherwise the access method has no interface with which to communicate. In this case restype can be: Sxyz System Abend | Explanation: The occurrence could not be inserted in | the current plan of Tivoli Workload Scheduler for | z/OS. Explanation: All the interfaces. yymmdd hhmmss The date and time the error occurred. Unnnn User Abend CONDCOD The job does not end successfully due to the condition code of one step that does not match the definition. TWS for z/OS and JES are set to NO. Explanation: Both the IA and the IATIME parameters were supplied in the task definition.EEWI32S • EEWI38I EEWI32S yymmdd hhmmss module AT LEAST ONE INTERFACE MUST BE DIFFERENT FROM NODE EEWI35W JCL dataset(member) NOT FOUND Explanation: The indicated JCL was not found in the JCL library. Explanation: Both the DEADLINE and the DEADLINETIME parameters were supplied in the task definition. Operator response: Reissue the request. task application The name of the task that issued the message. EEWI36W yymmdd hhmmss IA AND IATIME CANNOT BE SPECIFIED TOGETHER System action: The system stops. Operator response: Define the JCL in the correct member of the data set and restart the request. System action: The system proceeds. For a detailed list. In this case restype 274 IBM Tivoli Workload Scheduler for Applications: User’s Guide . supplying only one of the indicated parameters. dataset The name of the data set that was expected to contain the JCL. | Operator response: Define the application correctly in | the Tivoli Workload Scheduler for z/OS database and | restart the request. yymmdd hhmmss The date and time the error occurred. Can be one of the following values: ABEND If the job ends abnormally. The number of seconds of CPU time consumed. | Possible reasons are: | v The application is not defined in the Tivoli Workload Scheduler for z/OS Application Description database | | v The application valid-from date is later than the current plan end date | | System action: The system proceeds. EEWI37W yymmdd hhmmss DEADLINE AND DEADLINETIME CANNOT BE SPECIFIED TOGETHER | EEWI33W | | yymmdd hhmmss TASK task APPLICATION application CANNOT BE INSERTED IN THE CURRENT PLAN Explanation: The occurrence could not be inserted in the current plan of Tivoli Workload Scheduler for z/OS. One must be set to YES. JESINTERFACE. System action: The system proceeds. yymmdd hhmmss The date and time the error occurred. yymmdd hhmmss The date and time the error occurred. The number of seconds passed from the request. Operator response: Specify a value other than NO for at least one of the parameters: CA7INTERFACE. module The name of the module that issued the message.

EEWI42I contains: the RC=nnnnn value of the return code of the last step that was run. blank In case of an internetwork dependency when the manual submission was not performed. | EEWI42I | | | | yymmdd hhmmss TASK task MODULE EEWTCP65 ISSUED. MACRO 'EZASMI TYPE=GETPEERNAME' NEAR LABEL 'M2505710' TO GET PEER ADDRESS = address | Explanation: See text. The address of the remote partner. SUCCES If the job completed successfully. Messages 275 . UNKNOWN If the job ID is unknown. | yymmdd hhmmss The date and time the error occurred. if LASTSTEP specified. Chapter 31. or of the worst step that does not match the definition of the job on the distributed side. | task | address The name of the task. JCLERRO If the job failed due to a JCL error. EXEC If the job is running or is in the input queue.

the application server address. If the values are correct. stop the program. Explanation: The access method was unable to submit the PeopleSoft process. System action: The program continues. EEWN0102W Option "option(value)" is greater than the maximum value allowed (maximum_value). are incorrectly specified in the options file v The PeopleSoft application server refused the connection. The submission was tried number_of_tries times. are incorrectly specified in the options file v The PeopleSoft application server IP address or host name. or both. Operator response: If you do not want to use the default values. then analyze the PeopleSoft application server log for the failed connection attempt. Note: In addition to these messages. change the option to a positive value and restart the program. The error was due to an unmanaged conflict between concurrent database save operations in PeopleSoft. EEWN0100W Option "lower_option(lower_option_value)" must have a value not greater than option "higher_option(higher_option_value)". stop the program. and which are listed under the product code HTW and the component code GT (see “PeopleSoft access method messages . No further submission attempts will be made because the maximum number of retries (tws_retry option value) has been reached.N This section lists error and warning messages that might be issued by the PeopleSoft access method processes. Explanation: See message. and password). and restart the program. When you have found the problem. the PeopleSoft access method also issues messages which it shares with Tivoli Workload Scheduler for Visualized Data Centers. and that process uses inline bind variables. v A network failure occurred. and restart the program. or its port number. using the default values for this option. Explanation: See message. and the application server port are correct. System action: The PeopleSoft process cannot be submitted and monitored. This might occur when several Tivoli Workload Scheduler jobs submit the same PeopleSoft process. or both. run the Tivoli Workload Scheduler job again. application server port. using the default values for this option. stop the program. System action: The program continues.HTWGT” on page 314). or its password. 276 IBM Tivoli Workload Scheduler for Applications: User’s Guide . System action: The Tivoli Workload Scheduler job is put into the "abend" status. Operator response: If you do not want to use the default values. System action: The program continues. Operator response: Check the values of the options that define the connection (application server name or IP address. Operator response: If you do not want to use the default values. check if there were network failures at the time of the submission. Operator response: Verify that the values in the options file for the PeopleSoft user. Explanation: See message. change the options so that the value of the lower_option is not greater than the value of the higher_option. EEWN0101W Option "option(value)" is not a positive value. Explanation: The indicated option must have a positive value. EEWN0070E The connection to the server "server" for user "user" has failed. using the default values for these options. EEWN0105E The process submission failed due to a conflict in the PeopleSoft database. its encrypted password. If the option values are correct. This can be due to any of the following reasons: v The PeopleSoft user ID.EEWN0070E • EEWN0105E PeopleSoft access method messages . When you have identified and fixed the problem. correct it and retry the operation. EEWN0104E The method failed to submit and monitor the PeopleSoft process to completion due to a connection failure. Explanation: The connection to the PeopleSoft application server could not be made or has failed. user ID. change the option to a value not greater than the maximum allowed.

EEWN0106E • EEWN0120E
System action: The PeopleSoft process could not be submitted. The Tivoli Workload Scheduler job is put into the "abend" status. Operator response: Rerun the Tivoli Workload Scheduler job. If the problem persists, contact IBM Software Support for assistance. EEWN0106E The process submission has failed for an unknown reason. Explanation: See message. System action: The Tivoli Workload Scheduler job is put into the "abend" status. Operator response: Check the Tivoli Workload Scheduler job definition. Check that all parameters are correct and that the referred objects all exist. Retry the operation. If the problem persists, contact IBM Software Support for assistance. EEWN0107E The monitoring of the PeopleSoft process has failed. Explanation: See message. System action: The Tivoli Workload Scheduler job is put into the "abend" status. Operator response: Monitor the PeopleSoft process in the PeopleSoft Process Monitor page. EEWN0110W The process submission has failed due to a conflict in the PeopleSoft database. The submission is retried until the maximum number of retries is reached. Explanation: See message. System action: The program tries to resubmit the PeopleSoft process until the maximum number of retries is reached (the value of the tws_reply option). Operator response: None. EEWN0111E The submission, control, or monitoring of the PeopleSoft process has failed for an unknown reason. The access method does not attempt to resubmit it. Explanation: See message. System action: The Tivoli Workload Scheduler job is put into the "abend" status. Operator response: Retry the operation. If the problem persists, contact IBM Software Support for assistance. EEWN0112E The process submission attempt failed due to a possible connection failure. Explanation: See message. System action: The Tivoli Workload Scheduler job is put into the "abend" status. Operator response: Check the values of the options that define the connection (application server name or IP address, application server port, user ID, and password). If the values are correct, check if there were network failures at the time of the submission. When you have identified and fixed the problem, run the Tivoli Workload Scheduler job again. EEWN0113W The attempt to monitor the progress of the PeopleSoft job has failed. The attempt is retried until the maximum number of retries is reached. Explanation: See message. System action: The program tries to monitor the PeopleSoft process until the maximum number of retries is reached (the value of the tws_reply option). Operator response: None. EEWN0119E The retrieved run status (status) has an incorrect format. Explanation: See message. System action: The Tivoli Workload Scheduler job is put into the "abend" status. Operator response: Resubmit the PeopleSoft process. If the problem persists, contact IBM Software Support for assistance. EEWN0120E An internal error "exception" has occurred. The error message is: "exception_message". Explanation: See message. System action: The Tivoli Workload Scheduler job is put into the "abend" status. Operator response: Resubmit the PeopleSoft process. If the problem persists, contact IBM Software Support for assistance.

Chapter 31. Messages

277

EEWO0001E • EEWO0016E

SAP R/3 access method messages - O
This section lists error and warning messages that might be issued by the SAP R/3 access method processes.
EEWO0001E Job aborted. Explanation: See message. System action: R3batch stops. Operator response: This is an internal error. Retry the operation (the error might be transient). If the problem persists, contact IBM Software Support for assistance. EEWO0010E The extended agent has not started. The command to launch it included no options. Explanation: See message. System action: R3batch stops Operator response: See the User’s Guide for a list of the parameters you can specify with the r3batch command. Reissue the command with the correct parameters. See also: The User’s Guide for details of the command syntax. EEWO0011E The extended agent has not started. The command to launch it has syntax errors. Explanation: See message. System action: R3batch stops. Operator response: See the User’s Guide for a list of the parameters you can specify with the r3batch command. Reissue the command with the correct parameters. See also: The User’s Guide for details about the command syntax. EEWO0012E The extended agent could not be initialized. Explanation: See message. System action: R3batch stops. Operator response: Check that the connections between the SAP system and the local host are correct. Check also that the local options file exists, is in the correct directory, has read permission for the user running r3batch, and is not corrupt. When you have found and corrected the error, rerun r3batch. EEWO0013E The extended agent could not find the following Tivoli Workload Scheduler home directory: TWS_home_directory. Explanation: TWS_home_directory is the directory where Tivoli Workload Scheduler is installed. System action: R3batch stops. Operator response: Check that the directory indicated in the message has the correct name, that it exists, and that it has read permission for the user running r3batch. When you have found and corrected the error, rerun r3batch. EEWO0014E The extended agent could not find the following method options file: method_options_file. Explanation: method_options_file is the file that contains the R/3 method options. System action: R3batch stops. Operator response: Check that the file indicated in the message has the correct name, that it exists, and that it has read permission for the user running r3batch. If the file is missing, follow the instructions that describes how to create it in the User’s Guide. When you have found and corrected the error, rerun r3batch. See also: The User’s Guide for the instructions on how to create the method options file. EEWO0015E The method options file: method_options_file for the following job: job_name does not contain the required options. Explanation: method_options_file is the file that contains the R/3 method options. job_name is the name of the job that you are trying to run. System action: R3batch stops. Operator response: Check in the User’s Guide for details about the options that must be supplied for the job that you want to run. When you have found and corrected the error, rerun r3batch. See also: The User’s Guide for details about the options you must include in the method options file for each type of job. EEWO0016E The method options file: method_options_file for the following job: job_name does not contain all of the required options. Explanation: method_options_file is the file that contains the R/3 method options.

278

IBM Tivoli Workload Scheduler for Applications: User’s Guide

EEWO0017E • EEWO0033E
job_name is the name of the job that you are trying to run. System action: R3batch stops. Operator response: Check in the User’s Guide for details about the options that must be supplied for the job that you want to run. When you have found and corrected the error, rerun r3batch. See also: The User’s Guide for details about the options you must include in the method options file for each type of job. EEWO0017E An internal I/O error occurred reading the following method options file: method_options_file. Explanation: method_options_file is the file that contains the R/3 method options. System action: R3batch stops. Operator response: Check the following: v The file system where the method options file is located has enough memory available. v The file has read permission for the user that is running r3batch. v The operating system has not reached the maximum number of files it can have open at the same time. When you have found and corrected the error, rerun r3batch. EEWO0018E An internal I/O error occurred reading the following method options file: method_options_file. Explanation: method_options_file is the file that contains the R/3 method options. System action: R3batch stops. Operator response: Check the following: v The file system where the method options file is located has enough memory available. v The file has read permission for the user that is running r3batch. v The operating system has not reached the maximum number of files it can have open at the same time. When you have found and corrected the error, rerun r3batch. If the error persists, contact IBM Software Support for assistance. EEWO0019E An internal error occurred while trying to initialize the TWSMETH_CP code page. Explanation: See message. System action: R3batch stops. Operator response: This is an internal error. Contact IBM Software Support for assistance. EEWO0020E An internal error occurred while trying to decrypt the R/3 password. Explanation: See message. System action: R3batch stops. Operator response: This is an internal error. Contact IBM Software Support for assistance. EEWO0030E An error occurred while trying to convert a timestamp read from SAP R/3 system. Explanation: See message. System action: R3batch stops. Operator response: Check the timestamp on SAP R/3 is valid. EEWO0031E The value EIF_Port_Number is not a valid EIF port number. Explanation: See message. System action: The program stops. Operator response: Specify a valid port number, in the range 0 - 65535. EEWO0032E Cannot open the event configuration file CFG_File. Explanation: See message. System action: The program stops. Operator response: Verify that the file exists and is readable. EEWO0033E Cannot create the PID file for the extended agent XA_Workstation_Name. Explanation: See message. System action: The program stops. Operator response: The monitoring process was unable to create the file in which to store the PID number. For detailed information, see the trace file for the XA workstation indicated in the message.

Chapter 31. Messages

279

EEWO0034E • EEWO0103E
EEWO0034E An internal error occurred while parsing the event configuration file for the XA_Workstation_Name workstation. Explanation: See message. System action: The program stops. Operator response: This is an internal error. Contact IBM Software Support for assistance. EEWO0035E Monitoring of the XA_Workstation_Name workstation is already running. Program exiting. Explanation: See message. System action: The program stops. Operator response: Ensure that only one instance of the event monitoring runs on one extended agent workstation. EEWO0036E The monitoring process failed to daemonize. Explanation: See message. System action: The program stops. Operator response: For detailed information, see the trace file for the XA workstation indicated in the message. EEWO0037E An error occurred: Parameter EIFSRV is missing. Explanation: See message. System action: R3batch stops. Operator response: Specify the parameter EIFSRV on the command line. EEWO0038E An error occurred: Parameter EIFPORT is missing. Explanation: See message. System action: R3batch stops. Operator response: Specify the parameter EIFPORT on the command line. EEWO0100E An internal error has occurred. The following unknown BAPI return code: BAPI_return_code (BAPI_message) was received while calling the following function: function. Explanation: BAPI_return_code is the code returned by the BAPI module. BAPI_message is the message associated with the code returned by the BAPI module. EEWO0103E R3batch has run out of memory (the function RfcAllocParamSpace has failed in the following module: module). Explanation: module is the module being performed. System action: R3batch stops. Operator response: Check the following: 1. Verify if the workstation has enough memory available. Information about the memory requirements of Tivoli Workload Scheduler for Applications is provided in the Download Document. If not, you might need to increase the memory of the workstation or make changes in memory management and paging to make more memory available to r3batch. Rerun r3batch. 2. If the workstation memory is adequate, try closing all the applications that you do not need, and then rerun r3batch. 3. If the problem persists, reboot the workstation, and then rerun r3batch. 4. If the problem persists, contact IBM Software Support for assistance. EEWO0101E The following ABAP module cannot be found: "ABAP_module". All required ABAP modules must be installed before running the extended agent. Explanation: ABAP_module is a required module that has not been installed. System action: R3batch stops. Operator response: Use the User’s Guide to determine the ABAP modules required. Contact your SAP system administrator to have them installed. See also: The User’s Guide for details about the ABAP modules required. EEWO0102E An internal error has occurred. The function ItCreate has failed for the following object: object in the following module: module. Explanation: object is the object that the function ItCreate was trying to perform on. module is the module being processed. System action: R3batch stops. Operator response: This is an internal error. Contact IBM Software Support for assistance. function is one of the functions used by the program. System action: R3batch stops. Operator response: This is an internal error. Contact IBM Software Support for assistance.

280

IBM Tivoli Workload Scheduler for Applications: User’s Guide

EEWO0104E • EEWO0113E
See also: The Download Document for details about memory requirements. EEWO0104E An internal error has occurred. The RFC system failed while calling the following module: module. Explanation: module is the module being performed. System action: R3batch stops. Operator response: This is an internal error. Contact IBM Software Support for assistance. EEWO0107E This extended agent for R/3 does not support your version of the SAP R/3 system, which is the following: R/3_version. Explanation: R/3_version is the version number of the SAP R/3 system on this workstation. System action: R3batch stops. Operator response: See the User’s Guide to determine the versions of SAP supported. If you are using a lower version of SAP than those supported, upgrade to a supported version. If you are using a higher version of SAP than those supported, check on the IBM products Web site to see if there is a later version of Tivoli Workload Scheduler for Applications available. See also: The User’s Guide for details about the versions of SAP that are supported. EEWO0108E R3batch has found that the following component is not at the correct version: component. Explanation: component is the component of Tivoli Workload Scheduler for Applications that is at the wrong version level. System action: R3batch stops. Operator response: Upgrade the specific component. If not possible, upgrade or reinstall Tivoli Workload Scheduler for Applications. See the User’s Guide for details about the installation. See also: The User’s Guide for details about the installation. EEWO0109E An internal error has occurred. The following RFC function: function_name failed after the following number of attempts: attempts. Explanation: function_name is the name of the function being performed. attempts is a count of the number of tries that r3batch made at performing the function. System action: R3batch stops. Operator response: This is an internal error. Contact IBM Software Support for assistance. EEWO0110E An internal error has occurred. The RFC was not initialized when calling the following function: function_name. Explanation: function_name is the name of the function being performed. System action: R3batch stops. Operator response: This is an internal error. Contact IBM Software Support for assistance. EEWO0111E This user cannot define jobs on the following SAP R/3 system: SAP_system_name. Explanation: You do not have the required authority to define or create jobs on the SAP system. SAP_system_name is the name of the SAP system where you do not have permission to define or create jobs. System action: R3batch continues, but the job you are trying to run is not processed. Operator response: Consult your local SAP or Tivoli Workload Scheduler administrator to determine if the user ID that you used is the correct one, and if this user has the authorization to run jobs on the SAP system. When the problem is resolved restart r3batch. EEWO0112E The extended agent cannot create the following job: "job_name" with job ID: "job_ID". Explanation: job_name is the name of the job that cannot be created. job_ID is the job ID of the job that cannot be created. System action: R3batch continues, but the job you are trying to run is not processed. The batch log (r3batch_trace.log) is produced giving more details about the steps that occurred before the job creation failed. Operator response: Use the batch log to determine the cause of the problem. If the log file does not contain enough information, set the debug_level to MAX as described in the User’s Guide. Then rerun r3batch. When you have located and resolved the problem, rerun r3batch. EEWO0113E An internal error has occurred. An exception: exception_number has occurred while calling the following function module: function_module_name. Explanation: exception_number is the error number.
Chapter 31. Messages

281

EEWO0114E • EEWO0120E
function_module_name is the name of the function module being performed when the error occurred. System action: R3batch stops. Operator response: This error might not be repeated. Try restarting r3batch. If the error persists, contact IBM Software Support for assistance. EEWO0114E An internal error has occurred. The following database name is not correct: database_name. The help view is not retrieved. Explanation: database_name is the database name that is not correct. System action: R3batch stops. Operator response: This is an internal error. Retry the operation (the error might be transient). If the problem persists, contact IBM Software Support for assistance. EEWO0115E An internal error occurred. The following counter ID is not valid: counter_ID. Explanation: counter_ID is the counter ID that is not valid. System action: R3batch stops. Operator response: This is an internal error. Retry the operation (the error might be transient). If the problem persists, contact IBM Software Support for assistance. EEWO0116E The extended agent could not open the following joblog (stdlist) file: joblog_file_name. Explanation: Another process has locked the joblog file. joblog_file_name is the name of the file that is locked. System action: R3batch continues. Operator response: Take these steps. v Use the operating system facilities to determine which process has locked the joblog file. v Wait until the process that has locked the file stops. v If the process does not stop in an acceptable time frame, consider forcing it to stop (you should evaluate the risk of leaving data in a corrupted state). Use the operating system facilities to accomplish this. EEWO0117E R3batch has failed because the workstation where it is running has insufficient memory. Explanation: See message. System action: R3batch stops. EEWO0120E The job you are trying to monitor does not exists. The job number and name are as follows: "job_number: job_name". Explanation: job_number is the job number of the job that does not exist. job_name is the name of the job that does not exist. System action: The program might stop. Operator response: Verify that the job number and job name you are trying to monitor match an existing job. To determine which jobs are available, use the Find Job functionality in the Job Scheduling Console. If you have Operator response: Check the following: 1. Verify if the workstation has enough memory available. Information about the memory requirements of Tivoli Workload Scheduler for Applications is provided in the Download Document. If not, you may need to increase the memory of the workstation or make changes in memory management and paging to make more memory available to r3batch. Rerun r3batch. 2. If the workstation memory is adequate, try closing all the applications that you do not need, and then rerun r3batch. 3. If the problem persists, reboot the workstation, and then rerun r3batch. 4. If the problem persists, contact IBM Software Support for assistance. See also: The Download Document for details about memory requirements. EEWO0118E R3batch has failed because it could not create and start a job instance. Explanation: See message. System action: The job instance is not created. Operator response: Check the r3batch log file for the reason for the error and try to resolve it. If you have corrected the error, rerun r3batch. If the problem persists, contact IBM Software Support for assistance. EEWO0119E An internal error occurred. The cleanup task could not delete the following job: "job_name". The job ID is: "job_ID". Explanation: job_name is the name of the job that cannot be deleted. job_ID is the job ID of the job that cannot be deleted. System action: R3batch stops. Operator response: This is an internal error. Retry the operation (the error might be transient). If the problem persists, contact IBM Software Support for assistance.

282

IBM Tivoli Workload Scheduler for Applications: User’s Guide

EEWO0121E • EEWO0162E
corrected the error, rerun r3batch. EEWO0121E The R/3 system might not be available. BDCWAIT has failed to start after the following number of failed attempts: . Explanation: attempts is the number of times that r3batch tried to start BDCWAIT. System action: The program might stop. Operator response: Check that the R/3 system is running. Check the job status. If you have corrected the error, rerun r3batch. EEWO0122E An internal error has occurred. R3batch could not scan the R/3 joblog for BDCWAIT messages. Explanation: See message. System action: The batch job stops. Operator response: This is an internal error. Contact IBM Software Support for assistance. EEWO0123E An internal error has occurred. R3batch could not check the BDC session status in the R/3 system. Explanation: See message. System action: The batch job stops. Operator response: This is an internal error. Contact IBM Software Support for assistance. EEWO0124E The following SAP R/3 system defined in the method options file is not running: SAP_system_name. Explanation: SAP_system_name is the name of the SAP R/3 system that is not running. System action: R3batch stops. Operator response: Verify that the information in the options file is correct. Check that the SAP system is available, for example, by pinging the IP address of the SAP system. If you have corrected the error, rerun r3batch. EEWO0125E The SAP job specified in the job definition cannot be performed, because it has an incorrect job type. Explanation: See message. System action: R3batch continues, but the job being processed is ignored. Operator response: Check that the SAP job name specified in the job definition is correct and matches with the name of the SAP job defined in the SAP system. Check that the job type is correct. If you have corrected the error, rerun r3batch. EEWO0126E The following mapping file cannot be read due to an I/O error: mapping_file_name. Explanation: mapping_file_name is the name of the return code mapping file that cannot be read. System action: The job processing continues, but the return code mapping is not performed. Operator response: Check that the file with the indicated name exists, in the correct directory, and with read permission for the user running r3batch. Open the file with a text editor to ensure that it is readable. If you have corrected the error, rerun r3batch. EEWO0160E An internal error has occurred. The following method: "method_name" was called by the following request: "request_type", which is currently not supported by the following module: module. Explanation: method_name is the name of the method being called. request_type is the type of request being made. module is the module that does not support this request. System action: R3batch stops. Operator response: This is an internal error. Retry the operation (the error might be transient). If the problem persists, contact IBM Software Support for assistance. EEWO0161E A syntax error occurred when r3batch was started. The following task parameter is unrecognized: task_parameter. Explanation: task_parameter is the task parameter that is not recognized. System action: R3batch stops. Operator response: See the User’s Guide for a list parameters you can specify with the r3batch command. Reissue the command with the correct parameters. See also: The User’s Guide for details about the command syntax. EEWO0162E A syntax error occurred when r3batch was started. One or more parameters is missing from the following task: task_name. It needs the -c, -j, -l, -t, and ’--’ parameters. Explanation: task_name is the name of the task that you are trying to run. System action: R3batch stops.
Chapter 31. Messages

283

System action: R3batch stops. but the step number (step_number) cannot be determined. System action: R3batch stops. Rerun r3batch. See also: The User’s Guide for a description of the task parameters. See also: The User’s Guide for a description of the task parameters. System action: R3batch stops. Operator response: See the SAP system administrator. Explanation: step_number is the number of the step that is not in the correct format to be determined. Explanation: task_name is the name of the task that you are trying to run. supplying the correct task parameters. System action: R3batch stops. See also: The User’s Guide for a description of the task parameters. System action: R3batch stops. Operator response: This is an internal error. EEWO0163E A syntax error occurred when r3batch was started. If a variant is missing it must be created. System action: R3batch stops. supplying the correct task parameters. One or more internal parameters is missing from the following task: task_name. supplying the correct task parameters. Explanation: task_name is the name of the task that you are trying to run. Explanation: task_name is the name of the task that you are trying to run. One or more parameters is missing from the following task: task_name. EEWO0167E An error occurred when r3batch was started. and ’--’ parameters. One or more parameters is missing from the following task: task_name. EEWO0172E You have defined a job as a series of steps. supplying the correct task parameters. Rerun r3batch. Explanation: See message. Explanation: ABAP_name is the name of the ABAP module which is specified to be run. Operator response: See the SAP system administrator and determine the correct step number. -t. It needs the -c. but one of the steps has a number which is out of range: step_number. EEWO0171E You have specified a step to run an ABAP or an external program. It needs the -c.EEWO0163E • EEWO0173E Operator response: See User’s Guide for a description of the task parameters. and ’--’ parameters. and ’--’ parameters. -o. System action: R3batch stops. Operator response: See User’s Guide for a description of the task parameters. Rerun r3batch. Rerun r3batch. Operator response: This is an internal error. Explanation: task_name is the name of the task being run. Explanation: step_number is the number of the step that is not in the correct range. -j. It needs the following parameter: parameter_name. -t. One or more parameters is missing from the following task: task_name. EEWO0166E An internal error has occurred: GI and PI require task specification. There are two alternative ways to create a variant: 284 IBM Tivoli Workload Scheduler for Applications: User’s Guide . It needs the -c. System action: R3batch stops. Contact IBM Software Support for assistance. Operator response: Determine the correct variants to use from the SAP system administrator. Operator response: See User’s Guide for a description of the task parameters. Contact IBM Software Support for assistance. but no variants have been specified. EEWO0165E A syntax error occurred when r3batch was started. -j. See also: The User’s Guide for a description of the task parameters. Operator response: See User’s Guide for a description of the task parameters. -l. EEWO0173E You have specified a step to run the following ABAP: ABAP_name which requires one or more variants. Change the job specification to add the variant or variants. EEWO0164E A syntax error occurred when r3batch was started. -t. parameter_name is the name of the missing internal parameter.

Explanation: step_type is the non-valid type that has been supplied by the GUI for the step. System action: R3batch stops. and the variant details. also check the connectivity with the SAP system. EEWO0179E An internal error occurred because a variant name counter field was missing for the following report: "report_name" and variant: "variant_name". also check the connectivity with the SAP system. variant_name the name of the variant that was being processed when the error occurred. If the problem persists. System action: R3batch continues. EEWO0177E The following step is not valid. variant_name the name of the variant that was being processed when the error occurred. Retry the operation (the error might be transient). EEWO0176E There is an error in the job information that has prevented the r3batch program from creating the following step: step_number. System action: R3batch continues. System action: R3batch continues. System action: The step is not added. If the problem continues. contact IBM Software Support for assistance. Explanation: report_name the name of the report that r3batch was trying to create. EEWO0178E An internal error has occurred. Contact IBM Software Support for assistance. If the problem persists. Explanation: You are trying to add a step but an error in the step data prevents it from being added. but the step is not performed. Operator response: Rerun r3batch (the problem might be transient). rerun r3batch. contact IBM Software Support for assistance. If you find the problem and correct it. step_number is the number of the step being processed. but the job is not processed. Operator response: This is an internal error. Explanation: step_number is the number of the step that is not valid. original_variant_name the name of the variant that was being processed when the error occurred. r3batch could not make a copy of the following variant: "original_variant_name" because the copy name of the variant generated automatically by the program: "variant_copy_name" is the same as that of an existing variant. rerun r3batch. the user name. Operator response: This is an internal error. Verify the name of the job. System action: R3batch continues. If you find the problem and correct it.EEWO0174E • EEWO0180E v Follow the instructions in the User’s Guide to create a variant using the Job Scheduling Console v Ask the SAP system administrator to create the variant using the SAP GUI. and the variant details . such as the name of the job. Explanation: report_name the name of the report that r3batch was trying to create. Operator response: Rerun r3batch (the problem might be transient). EEWO0174E An internal error occurred while accessing the variant selection table J1O1VARSO for the following report: "report_name" and variant: "variant_name". If the problem continues. EEWO0180E During the preparation of the following report: "report_name". but the job is not processed. Operator response: Verify the correctness of the information in the step. Messages 285 . Explanation: report_name the name of the report that r3batch was trying to create. step_number is the number of the step you are trying to add. and cannot be performed: step_number. the user name. Explanation: report_name the name of the report that r3batch was trying to create. but the step is not performed. correct any errors and retry the add step action. EEWO0175E An internal error occurred while accessing the variant counter table J1O1VARCO for the following report: "report_name" and variant: "variant_name". If the problem persists. variant_name the name of the variant that was being processed when the error occurred. variant_copy_name the name of the copy that r3batch is Chapter 31. contact IBM Software Support for assistance. The following incorrect step type: "step_type" has been supplied for step: "step_number". Operator response: Verify the correctness of the information in the step.

correct the job definition and rerun r3batch. but the processing of the job stops. variant_name the name of the variant that was being processed when the error occurred. EEWO0185E The properties of the variant required for this job indicate that is protected by another user. rerun r3batch. System action: R3batch continues. There are two alternative ways to create a variant: v Follow the instructions in the User’s Guide to create a variant using the Job Scheduling Console v Ask the SAP system administrator to create the variant using the SAP GUI. Explanation: See message. and to correct them. Operator response: Check in the job definition that the variant is correctly specified. EEWO0182E R3batch could not create the following report: "report_name" because the variant: "variant_name" has one or more incorrect values (placeholders or counters). contact IBM Software Support for assistance. EEWO0183E An internal error has occurred while calling the function "j_1O1_variant_maintain_sel_tbl". but the variant is not processed. Decide whether to stop that application or wait for it to stop or unlock the variant itself. If you find the problem and correct it. Operator response: Check in the job definition that the variant is correctly specified. Operator response: Contact the SAP system administrator to determine why the values are incorrect. It is also the name of the existing variant. System action: R3batch stops. There are two alternative ways to create a variant: v Follow the instructions in the User’s Guide to create a variant using the Job Scheduling Console 286 IBM Tivoli Workload Scheduler for Applications: User’s Guide . because the parameters to the call were not valid. EEWO0184E A variant required for this job is locked by another application. System action: R3batch stops. Explanation: See message. System action: R3batch stops. EEWO0186E A variant required for this job no longer exists. EEWO0181E R3batch could not obtain the semaphore identified in the global options file (required to control access to shared resources). See also: See the User’s Guide for more information about variants and semaphores. Rerun r3batch. If it is not. System action: R3batch stops. If you find the problem and correct it. Explanation: See message. v Change the name of the original variant which was being copied (the copy name is based on the original. Operator response: Request the user that protected the variant to remove the protection so that you can use it for your job. Explanation: See message. rerun r3batch. Explanation: See message. so any change in the original name will create a copy with a different name). If it is correctly specified. System action: R3batch continues. the variant is missing and must be created. change the variant specification to refer to a variant that is not obsolete or create a new variant. rerun r3batch.EEWO0181E • EEWO0187E trying to create. If you find the problem and correct it. If you find the problem and correct it. Operator response: Contact the SAP system administrator to determine why the semaphore is missing. rerun r3batch. When the job definition is pointing to an existing variant. Operator response: Take either of these steps: v Change the name of the existing variant with the same name. System action: R3batch stops. Operator response: User the operating system tools to determine which application has locked the variant. If it is not. EEWO0187E A variant required for this job is obsolete and cannot be used. rerun r3batch. Explanation: report_name the name of the report that r3batch was trying to create. If the problem persists. Explanation: See message. If it is correctly specified. Retry the operation (the error might be transient). Operator response: This is an internal error. but the report is not created. System action: R3batch continues. correct the job definition and rerun r3batch.

The following identify the job: Host: host_name Job: job_name User: user_name Client: client. More job options were submitted than the maximum allowed: maximum_job_options. The job recovery is not performed. user_name is the name of the user running the job. or contact the SAP system administrator to stop the previous job. The recovery process has started with a non-valid or missing batch job ID: job_ID. When the job definition is pointing to an existing. System action: The recovery process does not continue.EEWO0189E • EEWO0263E v Ask the SAP system administrator to create the variant using the SAP GUI. EEWO0223E Either no matching job could be found in the following R/3 instance: R/3_instance. client identifies the R/3 client. EEWO0189E A variant required for this job cannot be created. Contact IBM Software Support for assistance. EEWO0263E A syntax error has been found with the job options. EEWO0224E R3batch cannot perform a job because it has the same job name user name and client number as an existing job. Explanation: job_ID identifies the job that cannot be processed. Contact IBM Software Support for assistance. by dividing it into two jobs. The job recovery is not performed. host_name is the name of the SAP system host. Correct the syntax and rerun r3batch. EEWO0261E An internal error has occurred. EEWO0260E An internal error has occurred. job_name is the name of the job for which a match cannot be found on the R/3 system. Explanation: variant_data is the data used to create a variant that is too long. or a job is found with steps but no start time. Then rerun r3batch. each of which would have a reduced number of job options. Explanation: See message. Operator response: This is an internal error. Explanation: job_option is the option that does not start with a hyphen. System action: R3batch stops. Explanation: maximum_job_options is the maximum number of job options that you can define. See also: The User’s Guide for details about the job options syntax. System action: R3batch stops. Explanation: job_ID identifies the job that cannot be processed. rerun r3batch. correct the Tivoli Workload Scheduler for Applications job definition and rerun r3batch. System action: R3batch stops. EEWO0262E A syntax error has been found with the job options. for example. The variant data is not valid (too long): variant_data. Also verify that the R/3 transaction SM37 shows the job in the "released" state. Chapter 31. See also: The User’s Guide for details about the job options syntax. System action: R3batch stops. It must be an eight digit number: job_ID. Operator response: Check whether there is a job on the SAP system which has a matching R/3 client. Reduce the number of job options for this job. Operator response: Check the data used to create the variant. either wait for the previous job to finish. The following option does not start with a hyphen: job_option. The recovery process has started with a non-numeric or wrong-length batch job ID. If you need to run this job. Operator response: Check the job option syntax in the User’s Guide. job name and user name as the Tivoli Workload Scheduler for Applications job definition for this job. Messages 287 . System action: The program might stop. Operator response: Check if you have tried to accidentally run the same job twice. Correct the syntax and rerun r3batch. System action: The recovery process does not continue. Operator response: Check the job option syntax in the User’s Guide. Explanation: You have probably supplied incorrect information to describe the R/3 job. When you have identified the error. non-obsolete variant. If you find an error and correct it. rerun r3batch. Operator response: This is an internal error.

job_option1. but that does not match a valid job option. Explanation: job_option is the option that requires a value. However. System action: R3batch stops. System action: R3batch stops. job_option3 requires a value. The job recovery is not performed. Correct the syntax by adding the value to the indicated option and rerun r3batch. The following option could not be recognized: unrecognizable_job_option. Operator response: Check the job option syntax in the User’s Guide. System action: R3batch stops. The following option: "job_option" has a non-valid value: "option_value". The following option: "job_option" has a non-valid value for the variant selection option sign: "option_value". Operator response: Check the job option syntax in the User’s Guide. System action: R3batch stops. See also: The User’s Guide for details about the job options syntax. valid_values is a list of the permitted values for the option in this context. Correct the syntax by changing the value of the indicated option so that it is valid and rerun r3batch. Operator response: Check the job option syntax in the User’s Guide. See also: The User’s Guide for details about the job options syntax. Contact IBM Software Support for assistance. option_value is the value that is not valid. See also: The User’s Guide for details about the job options syntax. The following job ID is not valid: job_ID. The following job option requires a value after keyword: job_option. EEWO0266E A syntax error has been found with the job options. System action: R3batch stops. The above message might exactly explain the problem. Operator response: This is an internal error. Explanation: unrecognizable_job_option is a string that by its position in the syntax and the presence of a hyphen in the first position indicates that it is a job option. Correct the syntax and rerun r3batch. Explanation: job_ID is the job ID that is not valid. EEWO0269E A syntax error has been found with the job options. but also for all others. The recovery process has started with the following non-valid parameter: parameter. is the option that must not precede job_option2. Operator response: Check the job option syntax in the User’s Guide. Correct the job ID and rerun r3batch. option_value is the value that is not valid for the variant selection option sign. EEWO0268E An internal error has occurred. it might be that an error of syntax has allowed the program to interpret a value as a job option. Explanation: There is a problem with the syntax of the job options. EEWO0267E A syntax error has been found with the job options. See also: The User’s Guide for details about the job options syntax. which cannot commence with a hyphen. Correct the syntax and rerun r3batch. System action: R3batch stops. EEWO0265E A syntax error has been found with the job options. Explanation: job_option is the option that has a non-valid value. Operator response: Check the job option syntax in the 288 IBM Tivoli Workload Scheduler for Applications: User’s Guide . which cannot begin with a hyphen (minus sign). See also: The User’s Guide for details about the job options syntax. The value must be one of the following: "valid_values".EEWO0264E • EEWO0270E EEWO0264E A syntax error has been found with the job options. Explanation: parameter is the non-valid parameter of the job that cannot be processed. The "job_option3" option requires a value. EEWO0270E A syntax error has been found with the job options. System action: The recovery process does not continue. Explanation: job_option is the option that has a non-valid value. The following option sequence is not correct: "job_option1" "job_option2". not only for the indicated job options. Operator response: Check the full job option syntax in the User’s Guide.

attempts is the number of times that r3batch has tried. Explanation: host_name is the workstation where r3batch cannot connect to the R/3 system. System action: R3batch stops. Correct the syntax by changing the value of the indicated option so that it is valid and rerun r3batch. R/3 user ID. v Check that the user running r3batch has read and write permissions in the Tivoli Workload Scheduler for Applications install directory and its subdirectories. correct it and rerun r3batch. Operator response: The problem might be one of several: v Check that there is available disk space in the file set where Tivoli Workload Scheduler for Applications is installed. EEWO0383E R3batch failed to connect to the R/3 system on the following host: "host_name". Explanation: R/3_instance identifies the R/3 instance that could not be connected to. Explanation: job_option is the option that has a non-valid value. or stop other applications that are using files. If there is a problem with permissions. The following option: "job_option" has a non-valid value for the variant selection option operation: "option_value". rerun r3batch. Messages host_name is the workstation where r3batch cannot connect to the R/3 system. See also: The User’s Guide for details about the job options syntax. System action: R3batch stops. Operator response: The problem might have one of two causes: v Check that the client number. create more space and rerun r3batch. Rerun r3batch. and password in the options file are correct. Operator response: Check the job option syntax in the User’s Guide.EEWO0271E • EEWO0422E User’s Guide. The value must be one of the following: "valid_values". option_value is the value that is not valid for the variant selection option operation. EEWO0384E R3batch failed to establish a connection to the following R/3 instance: "R/3_instance" on the following host: "host_name". Chapter 31. See also: The User’s Guide for details about the job options syntax. v Check that the operating system has not reached the maximum number of files that it can open at the same time. Operator response: Contact the SAP system administrator to determine the correct format and value for the indicated variant option. System action: R3batch stops. System action: R3batch stops. 289 . R3batch either could not open or could not copy the R/3 job. v Check with the SAP system administrator that the XA for SAP function modules (the programs for the Tivoli Workload Scheduler Xagent feature) have been installed and activated on the host If you have resolved the problem. v If the problem is not one of these. either use the operating system facilities to allow more file descriptors. If there is not sufficient space. valid_values is a list of the permitted values for the option in this context. attempts is the number of times that r3batch has tried. after the following number of attempts: attempts. EEWO0420E An internal error has occurred. after the following number of attempts: attempts. wait for other applications that are using files to close them. System action: The program might stop. contact IBM Software Support for assistance. Operator response: The problem might have one of two causes: v Check that the client number. EEWO0422E The following variant option is not valid: variant_option Explanation: variant_option is the variant option (parameter) that is not valid. EEWO0271E A syntax error has been found with the job options. Explanation: See message. Correct the syntax by changing the value of the indicated option so that it is valid and rerun r3batch. rerun r3batch. Correct the job definition and rerun r3batch. If this is the problem. R/3 user ID and password in the options file are correct v Check with the SAP system administrator that the indicated R/3 instance is running on the host If you have resolved the problem.

Contact the SAP system administrator to determine the correct identification of the R/3 job. Operator response: Either contact the SAP system administrator to have the appropriate authorizations given to the indicated user. Operator response: Check that the job has been correctly defined in the job definitions. and that it exists. Explanation: Either the specified filename is not in the correct format or r3batch does not have the access rights to create the file or directory. EEWO0451E R3batch could not create the file or directory: "filename". System action: R3batch stops. ignoring the action that encountered the error. System action: R3batch stops. Contact IBM Software Support for assistance. Explanation: The action being performed by the r3batch x-agent running the SAP job needs the values of one or more specific options that it expects to find in the global or local option file. Operator response: Contact the SAP system administrator to determine the correct value (the port number) of the R/3 client. For more details about the options in the global and local options files see the User’s Guide. EEWO0439E The required options are not specified either in the global or in the local options file. 290 IBM Tivoli Workload Scheduler for Applications: User’s Guide . Operator response: Check in the User’s Guide to determine the required options. Operator response: This is an internal error. It could not find those options. The program could not create the temporary variant table for this job (the rowptr from ItAppline is null). Operator response: Change the value of the indicated keyword to be a four-digit number and rerun the command. EEWO0428E An internal error has occurred. See also: The User’s Guide for more details about the values allowed for the indicated keywords. or is not in a correct state: "job_name" with the following job ID: "job_ID". System action: R3batch stops. Correct the problem and rerun r3batch. and that it is in one of the above-indicated statuses. not "Released" or "Finished". Client numbers must be between 0 and 999. Explanation: user_name identifies the user that does not have R/3 authorization to create and start batch jobs. Explanation: The year_from or year_to keyword was set to a value thatis not valid. EEWO0450E The year number "year_number" of keyword "keyword" is not valid: . The following R/3 RFC user does not have the appropriate R/3 user authorization to create and start batch jobs: user_name. v Change the path of the indicated filename to a location where r3batch is authorized to create and edit files. changing it if not. Amend the global or local options file (or both) to include those options. Rerun r3batch. System action: R3batch stops. The details about which options are required are given in the User’s Guide. Rerun r3batch. Check that the client option in the global or local options file has this value. The value for the year must be specified in the format yyyy. Some options are mandatory for all actions while other options are action-specific. See also: The User’s Guide for more details about the options in the global and local options files.EEWO0426E • EEWO0451E EEWO0426E R3batch cannot create the job. Explanation: client_number is the client number (SAP port number) that is not an integer between 0 and 999. Explanation: job_name and job_ID identify the job that was not found. The state must be shown in R/3 as "Scheduled". System action: R3batch stops. Explanation: See message. Either the filename is not valid or access rights are missing. See also: The User’s Guide for more details about the values allowed for the indicated keywords. Rerun r3batch. or is not in a correct state. Operator response: Do one of the following and rerun the command: v Contact your system administrator to change the access rights of the desired location so that r3batch is authorized to create and edit the file or directory in the path you want. if possible. Year numbers must be 4 digit numeric values. System action: R3batch stops. EEWO0441E The following client number is not valid: "client_number". System action: The program continues. EEWO0429E The following job was not found. or change the RFC user in the job definitions to a user that has the required authorizations.

291 . System action: R3batch stops.EEWO0452E • EEWO0507E EEWO0452E The supplied year range is not valid. System action: R3batch stops. contact IBM Software Support for assistance. Operator response: Retry the operation. Explanation: See message. See also: The User’s Guide for more details about using SAP background processing events as external dependencies. EEWO0506E An internal error has occurred: (RFC failed: SXMI_LOGON). Explanation: See message. EEWO0505E An internal error has occurred: (RFC failed: SXMI_VERSIONS_GET). contact IBM Software Support for assistance. Explanation: The request to commit the external Chapter 31. If the problem persists.0 or later. Retry the operation (the error might be transient). System action: R3batch stops. System action: R3batch stops. contact IBM Software Support for assistance. Explanation: See message. System action: R3batch stops. EEWO0460E The SAP system does not have the correct XBP interface version. v Change the path to a location where r3batch is authorized to create and edit files. contact IBM Software Support for assistance. The XBP interface version must be 2. Operator response: Do one of the following: v Check the log file for preceeding error messages. v Contact your system administrator to validate the XBP event history. EEWO0461E An internal error occurred during an external dependency operation. System action: R3batch stops. See also: The User’s Guide for more details about the values allowed for the indicated keywords. If the problem persists. Explanation: The date set for the year_from keyword is later than the value set for the year_to keyword. v Retry the operation. Explanation: See message. Retry the operation (the error might be transient). EEWO0453E R3batch could not create the following directory: "directory". System action: R3batch stops. Explanation: See message. EEWO0507E An internal error has occurred: (RFC failed: SXMI_AUDITLEVEL_SET). If the problem persists. System action: R3batch stops. Messages dependency. Retry the operation (the error might be transient). Event name: "event_name". The from year:"year_from" is greater than the to year:"year_to". Operator response: This is an internal error. If the problem persists. failed on the target SAP system. Operator response: This is an internal error. If the problem persists. Operator response: Correct the year range so that the starting year is earlier than the ending year. Operator response: Do one of the following and rerun the command: v Contact your system administrator to change the access rights of the desired location so that r3batch is authorized to create and edit the directory in the path you want. Retry the operation (the error might be transient). EEWO0504E An internal error has occurred: (RFC failed: SXMI_LOGON). Event parameter: "event_parameter". Explanation: See message. System action: R3batch stops. See also: The User’s Guide for more details about the values allowed for the indicated keywords. Either the directory name is not valid or "r3batch" does not have access rights required to create the file or directory. Explanation: See message. Operator response: Choose a SAP system with the correct XBP interface version. EEWO0462E R3batch could not commit the external dependency on the SAP system. Operator response: This is an internal error. identified by the SAP event name and parameter indicated in the message. If the problem persists. Operator response: This is an internal error. contact IBM Software Support for assistance. contact IBM Software Support for assistance.

Explanation: user_name identifies the user for which the job cannot be run. Operator response: Contact the R/3 system administrator to check the R/3 syslog. Explanation: user_name identifies the user for which the job cannot be run. System action: R3batch stops. job_name identifies the job that cannot be run. Check if the R/3 transaction SM37 shows the job in the "released" state. Correct the problem and rerun r3batch. Explanation: job_name is the name of the job that cannot be selected. If the problem persists. Explanation: See message. Explanation: See message. System action: R3batch stops. Correct the problem and continue. Retry the operation (the error might be transient). EEWO0550E No job name has been specified for the following user: user_name. Ensure they match with the R/3 job. EEWO0553E The XBP interface has returned the following error: "The external user is missing. job_name identifies the job that cannot be run. EEWO0558E The XBP interface has returned the following error: "Cannot select the following job: job_name with the following job ID: job_ID".". Operator response: This is an internal error. The following identify the job: User: user_name Job: job_name. which should contain more details about the error. or the job that is found has a "released" status. Operator response: This is an internal error. otherwise contact IBM Software Support for assistance. If it is. Ensure they 292 IBM Tivoli Workload Scheduler for Applications: User’s Guide . as SAP jobs in the "released" state cannot be run. or a job is found with steps but no start time. or if the error persists. Contact IBM Software Support for assistance. System action: R3batch stops. Also check the correctness of the indicated user name and job name. job_ID is the ID of the job that cannot be selected. contact IBM Software Support for assistance. EEWO0554E R3batch has stopped because the R/3 XMI logging mechanism has returned an error. Operator response: Check that the job name and ID are correctly identified in the job options. EEWO0552E The R/3 job scheduling system has found an error for the following job: User: user_name Job: job_name. contact IBM Software Support for assistance. EEWO0555E R3batch could not invoke the R/3 XMI interface. If the problem persists.EEWO0510E • EEWO0559E EEWO0510E An internal error has occurred: (get_record: Non-valid keyword. There might be a connection problem. Correct any error you find and rerun r3batch. System action: R3batch stops. Explanation: See message. Operator response: Check that the connection with the R/3 system is working correctly. System action: R3batch stops. contact IBM Software Support for assistance." Explanation: See message. System action: The program waits for you to correct the input or exit. Operator response: Check whether the R/3 job name and user name match the Tivoli Workload Scheduler for Applications job definition for this job. EEWO0551E Either no matching job could be found. Explanation: expected_keyword is the keyword expected at this point. Explanation: user_name identifies the user for which a job name has not been specified. System action: R3batch stops. EEWO0559E The XBP interface has returned the following error: "Cannot process the job because the job name or job ID is missing. Retry the operation (the error might be transient). Expected: expected_keyword). System action: R3batch stops. Operator response: This is an internal error. Operator response: Check that the job name and ID are correctly identified in the job options. Operator response: Supply a job name and continue. System action: The program waits for you to correct the input or exit. There might be a connection problem.

" Explanation: See message. If the problem persists. EEWO0562E The XBP interface has returned the following error: "The ABAP program name is missing. which should contain more details about the error. Operator response: Check the ABAP program name in the job definition. EEWO0568E The following job cannot be started "immediately": Job name: "job_name" Job ID: "job_ID". Take the appropriate action and rerun r3batch. EEWO0565E The XBP interface has returned the following error: "The supplied archive parameters are not valid. Operator response: Check that the job name and ID are correctly identified in the job options. Job name: "job_name" Job ID: "job_ID"." Explanation: See message. Correct any error you find and rerun r3batch. Messages 293 . Operator response: Check that the job definition settings of an "immediate" run time and dependencies is correct. Retry the operation (the error might be transient). Operator response: This is an internal error. If not. System action: R3batch stops. System action: R3batch stops. Explanation: The indicated job has been defined to run immediately. Correct any error you find and rerun r3batch. otherwise contact IBM Software Support for assistance. Correct any error you find and rerun r3batch. Check that the user has the correct permission to run the job. System action: R3batch stops. decide whether you want to wait for the dependencies to be resolved or delete them to let the job go ahead. job_ID is the ID of the job that cannot be deleted. System action: R3batch stops. Contact IBM Software Support for assistance. Operator response: Specify the host name or exit. job_ID is the ID of the job that cannot be immediately. System action: R3batch stops." Explanation: See message. Explanation: job_name is the name of the job that cannot be deleted. Operator response: This is an internal error. System action: The program waits for you to correct the input or exit. Explanation: See message. System action: R3batch stops. If the settings are correct. System action: R3batch stops. job_name is the name of the job that cannot be run immediately." Explanation: See message. but the target host name is missing in the step definition. contact IBM Software Support for assistance. EEWO0566E The target host name is required for external step definition. EEWO0563E The XBP interface has returned the following error: "The archive information cannot be found. Contact the R/3 system administrator to check the R/3 syslog. Ensure they match with the R/3 job. The step count is not correct. Operator response: This is an internal error. but the job has dependencies that cannot be resolved immediately. otherwise contact IBM Software Support for assistance. Explanation: You have defined a job with an external step. otherwise contact IBM Software Support for assistance.EEWO0561E • EEWO0569E match with the R/3 job. Operator response: Check the print parameters in the job definition (see the User’s Guide for details. Correct any error you find and rerun r3batch. correct the job definition and rerun r3batch. EEWO0561E The XBP interface has returned the following error: "Cannot delete the following job:". EEWO0564E The XBP interface has returned the following error: "The supplied print parameters are not valid. See also: The User’s Guide for details about the print parameters. Contact IBM Software Support for assistance. otherwise contact IBM Software Support for assistance. Chapter 31. EEWO0569E An internal error has occurred.

EEWO0574E An internal error has occurred. contact IBM Software Support for assistance. If the problem persists. Operator response: This is an internal error. If the problem persists. Retry the operation (the error might be transient). infopackage_name identifies the InfoPackage that does not exist. Operator response: This is an internal error. Retry the operation (the error might be transient). Explanation: infopackage_name identifies the InfoPackage that cannot be utilized. Explanation: infopackage_name identifies the InfoPackage with the incorrect source system. Explanation: See message. Explanation: infopackage_name identifies the InfoPackage that has been cancelled. Operator response: Contact the SAP system administrator and verify the SAP log to analyze the reason for the process chain not starting. Explanation: See message. job_ID is the ID of the job that does not have steps. Ask the R/3 system administrator to check for its existence in the R/3 system. System action: R3batch stops. contact IBM Software Support for assistance. or cancel the job. System action: R3batch stops. Explanation: See message. If the problem persists. wait for it to be fixed and rerun r3batch. System action: R3batch stops.EEWO0570E • EEWO0579E EEWO0570E The following job does not have steps: Job name: job_name Job ID: job_ID. Retry the operation (the error might be transient). System action: R3batch stops. Retry the operation (the error might be transient). System action: R3batch stops. If you find an error in the definition of the process chain in the job definitions. EEWO0573E The transfer structure for the following InfoPackage is not yet active: infopackage_name. contact IBM Software Support for assistance. Operator response: This is an internal error. Retry the operation (the error might be transient). Operator response: Edit the job definition to supply the missing step definitions and continue. Explanation: job_name is the name of the job that does not have steps. 294 IBM Tivoli Workload Scheduler for Applications: User’s Guide . The step count is missing. Operator response: Check the definition of the InfoPackage in the job definitions. Explanation: infopackage_name identifies the InfoPackage that is already running. EEWO0572E A Process Chain cannot be started. contact IBM Software Support for assistance. Operator response: This is an internal error. Explanation: See message. The request ID could not be found. System action: R3batch stops. EEWO0571E An internal error has occurred. contact IBM Software Support for assistance. If the error is on the R/3 side. System action: R3batch stops. Explanation: The probable reason is that the InfoPackage has been deleted after the job was defined but before it was run. EEWO0576E The job defined in the following InfoPackage is already running: infopackage_name. EEWO0579E An internal error has occurred (incorrect parametrization) while retrieving the list of available InfoPackages. System action: R3batch stops. Retry the operation (the error might be transient). EEWO0575E The action has been cancelled for the following InfoPackage: infopackage_name. System action: R3batch waits for a response from you. Operator response: This is an internal error. Retry the operation (the error might be transient). System action: The program might stop. If the problem persists. Operator response: This is an internal error. Operator response: This is an internal error. If the problem persists. contact IBM Software Support for assistance. EEWO0577E The source system of the following InfoPackage is not correct: infopackage_name. Correct any error you find and rerun r3batch. contact IBM Software Support for assistance. EEWO0578E The following InfoPackage does not exist: infopackage_name. If the problem persists. If the problem persists. correct it and rerun r3batch.

Explanation: infopackage_name identifies the InfoPackage that is already running. Either have the component installed or change the job definition to allow the job to run without this component. Explanation: See message. or if you want to stop the previous InfoPackage from running. In the latter case. because of its status.EEWO0580E • EEWO0587E EEWO0580E The following InfoPackage cannot be run as it is already running: infopackage_name. 1 Only process chains with status 1 canceled or failed can be restarted. Operator response: This is an internal error. It cannot be restarted. 1 log_id identifies the run instance of the process chain. Then rerun r3batch. System action: R3batch stops. EEWO0581E The required Business Information Warehouse component is not installed on this R/3 system. Operator response: Contact the SAP system administrator to discuss why the component is not supported. System action: R3batch stops. System action: The program might stop. Operator response: Contact the SAP system administrator to determine if it is possible to change the RFC user’s permissions on the R/3 system. 1 EEWO0585E The process chain process_chain could not 1 be scheduled on the SAP BW system. contact IBM Software Support for assistance. modify the job definitions to use the different RFC user. 1 System action: R3batch stops. Messages 295 . Explanation: See message. If you cannot determine such a reason. Explanation: See message. System action: R3batch stops. or whether you should run this job as a different R/3 RFC user. Decide whether you want to wait for the previous InfoPackage to finish. Either have the component upgraded or change the job definition to allow the job to run without this component. then run r3batch again. 1 Explanation: process_chain identifies the process chain 1 that the SAP BW system indicates as running. Operator response: Contact the SAP system administrator to discuss why the component is not available. 1 Operator response: Contact the SAP system 1 administrator to have the process chain corrected on 1 the SAP BW system. 1 log_id identifies the run instance of the process chain. Chapter 31. ask the SAP system administrator to stop the previous InfoPackage. 1 System action: R3batch stops. Then rerun r3batch. 1 Explanation: process_chain identifies the process chain 1 that could not be restarted on the SAP BW system. Rerun r3batch. Explanation: user_name identifies the user that does not have the appropriate R/3 user authorization for the indicated purposes. EEWO0584E The following R/3 RFC user does not have the appropriate R/3 user authorization to change the status of the interception or parent-child functionality: user_name. then run r3batch again. Then rerun r3batch. Operator response: Check the definition of the InfoPackage in the job definitions. EEWO0582E An internal error occurred while retrieving the version of the Business Information Warehouse component. 1 System action: R3batch stops. In the latter case. 1 Operator response: Contact the SAP system 1 administrator to have the process chain corrected on 1 the R/3 system. System action: R3batch stops. then run r3batch again. Check the log for information that might explain why the version of the component cannot be retrieved. to allow your job to run. 1 Operator response: Contact the SAP system 1 administrator to have the process chain corrected on 1 the SAP BW system. 1 EEWO0586E The process chain process_chain with log 1 ID log_id could not be restarted on the 1 SAP BW system. 1 EEWO0587E The process chain process_chain with log 1 ID log_id is already running on the SAP 1 BW system. 1 The R/3 system level does not support 1 this function. Check that you are not trying to run the same job twice. EEWO0583E The required Business Information Warehouse component is not supported on this R/3 system level. 1 Explanation: process_chain identifies the process chain 1 that could not be scheduled on the SAP BW system.

R3batch tried to open the file_name file. EEWO0702E An internal error has occurred. but the 1 request failed with return code 1 return_code. If it has. R3batch 1 tried to read the file_name file. If the problem 1 persists. contact IBM Software Support for assistance. 1 1 Explanation: See message. 1 EEWO0592E An internal error has occurred. The external program flags are not valid. If the problem persists. but the request failed. contact IBM Software Support for assistance. wait for other jobs that are using files to close. v Check that the operating system has not reached its maximum limit of open files. Operator response: This is an internal error. or stop other jobs that are using files. 296 IBM Tivoli Workload Scheduler for Applications: User’s Guide . Operator response: The problem could have various causes: v Check that the user running the job has read permission for the joblog. If the problem persists. contact IBM Software Support for assistance. R3batch tried to append records to the file_name 1 file. 1 System action: R3batch stops. 1 Explanation: See message. Explanation: See message. contact IBM Software Support for assistance. System action: R3batch stops. contact IBM Software Support for assistance. 1 System action: R3batch stops. System action: R3batch stops. System action: R3batch stops. Retry the 1 operation (the error might be transient). Make more space available if it does not. The job class is not valid. Retry the operation (the error might be transient). 1 EEWO0594E An internal error has occurred. Explanation: See message. contact IBM Software Support for assistance. 1 1 Explanation: See message. If the problem 1 persists. either extend this limit. Retry the 1 operation (the error might be transient). but the 1 request failed with return code 1 return_code. 1 EEWO0593E An internal error has occurred. 1 Operator response: This is an internal error. Retry the 1 operation (the error might be transient). contact IBM Software Support for assistance. but the request failed with return 1 code return_code. Retry the operation (the error might be transient). Retry the 1 operation (the error might be transient). 1 1 Explanation: See message. Retry the operation (the error might be transient). If the problem 1 persists. Explanation: See message. Retry the 1 operation (the error might be transient). 1 System action: R3batch stops. R3batch tried to update the file_name file. 1 Operator response: This is an internal error. EEWO0703E The program cannot read the joblog. The print parameters are not valid. Give the user this permission if it does not. 1 System action: R3batch stops. EEWO0700E An internal error has occurred. EEWO0701E An internal error has occurred. R3batch tried to close the file_name file. If the problem 1 persists. Retry the 1 operation (the error might be transient). 1 System action: R3batch stops. 1 Operator response: This is an internal error. 1 EEWO0595E An internal error has occurred. but the 1 request failed with return code 1 return_code. 1 Operator response: This is an internal error. but the 1 request failed with return code 1 return_code. 1 Operator response: This is an internal error. System action: R3batch stops. R3batch tried to initialize the module internal 1 module. Operator response: This is an internal error. contact IBM Software Support for assistance. contact IBM Software Support for assistance. 1 Operator response: This is an internal error. 1 1 Explanation: See message. Operator response: This is an internal error. 1 EEWO0591E An internal error has occurred. 1 1 Explanation: See message. 1 System action: R3batch stops.EEWO0590E • EEWO0703E 1 EEWO0590E An internal error has occurred. If the problem 1 persists. v Check that there is sufficient disk space in the file system of the joblog. Explanation: See message. If the problem persists. If the problem 1 persists.

System action: The program might stop. contact IBM Software Support for assistance. contact IBM Software Support for assistance. contact IBM Software Support for assistance. System action: R3batch stops. Rerun r3batch. Otherwise.EEWO0705E • EEWO0714E Rerun r3batch. System action: R3batch stops. or both of them. Retry the operation (the error might be transient). EEWO0708E An internal error has occurred. as appropriate. If the job ID is not missing. Retry the operation (the error might be transient). Operator response: This is an internal error. Operator response: This is an internal error. Operator response: This is an internal error. Messages 297 . correct it and rerun r3batch. System action: R3batch stops. Explanation: See message. Operator response: This is an internal error. System action: R3batch stops. Explanation: See message. The job data is not valid. If you identify the problem. Chapter 31. contact IBM Software Support for assistance. If the problem persists. Explanation: See message. Operator response: Check the job definition. contact IBM Software Support for assistance. EEWO0707E An internal error has occurred. Explanation: See message. Explanation: See message. System action: R3batch stops. check the log to identify a possible cause. The initial step is not valid. If the problem persists. See also: The User’s Guide for details about the contents and syntax of the options files. Check the log to identify a possible cause. Explanation: See message. EEWO0711E An internal error has occurred. contact IBM Software Support for assistance. Explanation: See message. Operator response: Check both the local and global options files in the method directory. If the problem persists. If the problem persists. contact IBM Software Support for assistance. Retry the operation (the error might be transient). If the problem persists. If the problem persists. EEWO0705E The client number is missing in both the local and global options files. Retry the operation (the error might be transient). EEWO0710E An internal error has occurred. EEWO0706E An internal error has occurred. System action: R3batch stops. Add the client number (the port of the target host) to one. contact IBM Software Support for assistance. Explanation: See message. If the problem persists. System action: R3batch stops. System action: R3batch stops. If the problem persists. The joblog name is missing. check with the SAP system administrator to determine the correct ID and enter it in the job definition. EEWO0709E An internal error has occurred. contact IBM Software Support for assistance. Operator response: This is an internal error. The start date is not valid. EEWO0712E An internal error has occurred. The EXTCOMPANY and EXTPRODUCT parameters are different within a session. Retry the operation (the error might be transient). Operator response: This is an internal error. Otherwise. other. If you identify the problem. The step number is not valid. The dialog type is not valid. Explanation: See message. If none of these actions resolves the problem. System action: R3batch stops. Retry the operation (the error might be transient). correct it and rerun r3batch. If the job ID is missing. EEWO0714E An internal error has occurred. If no cause is evident. check the log to identify a possible cause. Explanation: See message. The job select process failed. Rerun r3batch. this is an internal error. Operator response: This is an internal error. Retry the operation (the error might be transient). Retry the operation (the error might be transient). contact IBM Software Support for assistance. EEWO0713E The job ID is missing. Operator response: This is an internal error.

Explanation: See message. Operator response: This is an internal error. If the problem persists. contact IBM Software Support for assistance. If it does not. but has a different job ID from that indicated in the message. check the log to see if it has been deleted by another action. System action: R3batch stops. If the problem persists. System action: R3batch stops. If the problem persists. Explanation: See message. The following identify the job: Job name: job_name Job ID: job_ID. The following identify the job: Job name: job_name Job ID: job_ID. If the problem persists. Explanation: See message. A job could not be deleted. Operator response: This is an internal error. System action: R3batch stops. Operator response: This is an internal error. If it does exist. Explanation: job_name and job_ID identify the job that could not be submitted. Operator response: This is an internal error. The following identify the job: Job name: job_name Job ID: job_ID. A file or database could not be locked. Explanation: job_name and job_ID identify the job that could not be deleted. This user is not authorized to work with the R/3 external job management system. EEWO0725E The logon has failed. If the problem persists. EEWO0716E An internal error has occurred. EEWO0719E The following job does not exist: Job name: job_name Job ID: job_ID. correct it and rerun r3batch. contact IBM Software Support for assistance. contact IBM Software Support for assistance. Retry the operation (the error might be transient). If you identify the problem. System action: R3batch stops. rerun the job as a user that has these privileges. A job could not be submitted.EEWO0715E • EEWO0727E EEWO0715E An internal error has occurred. Operator response: Retry the operation (the error might be transient). contact IBM Software Support for assistance. rerun the job as a user that has this permission. job_name and job_ID identify the job that does not exist. Retry the operation (the error might be transient). If the problem persists. Operator response: Determine from the system administrator whether the user can be granted "execute" privileges. System action: R3batch stops. Explanation: job_name and job_ID identify the job that could not be deleted. Explanation: The R/3 job might have been deleted by a different action. 298 IBM Tivoli Workload Scheduler for Applications: User’s Guide . contact IBM Software Support for assistance. A job could not be deleted because it is not active. and if so. Retry the operation (the error might be transient). Operator response: Contact the R/3 system administrator to determine if the user can be granted permission to work with the R/3 external job management system. If the problem persists. System action: R3batch stops. If not. EEWO0727E The following user does not have "execute" privileges: user_name. Retry the operation (the error might be transient). Operator response: This is an internal error. EEWO0726E An internal error has occurred. The name and qid are missing. Explanation: See message. check on the SAP system to see if the job exists. EEWO0724E An internal error has occurred. contact IBM Software Support for assistance. Operator response: This is an internal error. or it might have the correct job name but an incorrect job ID. System action: R3batch stops. The job failed to close. Otherwise. In all other circumstances contact IBM Software Support for assistance. System action: R3batch stops. check the log to identify a possible cause. Retry the operation (the error might be transient). EEWO0722E An internal error has occurred. EEWO0717E An internal error has occurred. Retry the operation (the error might be transient). Explanation: See message. If not. System action: R3batch stops. change the job definition accordingly and rerun r3batch. decide whether it needs to be rerun.

Retry the operation (the error might be transient). See also: The User’s Guide for details about how to define ABAP programs. and continue. System action: R3batch stops. Operator response: This is an internal error. contact IBM Software Support for assistance. See also: The User’s Guide for details about how to define ABAP programs. System action: The program waits for you to correct the data or exit. Operator response: This is an internal error. EEWO0739E The version of the required interface is not supported by the R/3 system. If not. System action: R3batch stops. System action: R3batch stops. System action: The program waits for you to correct the data or exit. If the problem persists. Operator response: Define the ABAP program associated with the variants you were trying to enter and continue. Retry the operation (the error might be transient). Retry the operation (the error might be transient). EEWO0733E The ABAP program is missing. contact IBM Software Support for assistance. System action: The program waits for you to correct the data or exit. EEWO0732E The ABAP program has no variants. Explanation: See message. System action: The program waits for you to correct the data or exit. EEWO0736E The selection has been cancelled. EEWO0738E The required interface is not supported by the R/3 system. Retry the operation (the error might be transient). contact IBM Software Support for assistance. Explanation: See message. Explanation: See message.EEWO0729E • EEWO0739E EEWO0729E The following user does not have any access privileges: user_name. Chapter 31. Operator response: Define the missing variants and continue. Operator response: This is an internal error. System action: R3batch stops. If the problem persists. System action: R3batch stops. contact IBM Software Support for assistance. Modify the job definition and continue. Explanation: See message. 299 . change the job definition. EEWO0731E The ABAP program does not exist. Explanation: See message. See also: The User’s Guide for details about the how to define variants. Explanation: You have tried to define variants but have not yet identified an ABAP program. Operator response: Contact the R/3 system administrator to determine the correct name of the ABAP program. Explanation: See message. EEWO0730E No variants have been defined. If the problem persists. Operator response: This is an internal error. EEWO0735E ABAP and external program set Explanation: See message. you should rerun the job as a user that has these privileges. System action: The program waits for you to correct the data or exit. The startrow is not valid. If the problem persists. See also: The User’s Guide for details about how to define ABAP programs. Operator response: Define the missing variants and continue. If the problem persists. Retry the operation (the error might be transient). Operator response: Determine from the system administrator whether the user can be granted "access" privileges. EEWO0737E An internal error has occurred. Messages EEWO0734E The ABAP program is not executable Explanation: You have defined an ABAP program that is not an executable file. Explanation: See message. Operator response: This is an internal error. See also: The User’s Guide for details about how to define variants. System action: R3batch stops. Explanation: See message. contact IBM Software Support for assistance. Operator response: Choose a different ABAP program.

Operator response: Check R/3 syslog. contact IBM Software Support for assistance. System action: R3batch stops. If not. System action: R3batch stops. An event is missing a parameter. System action: R3batch stops. contact IBM Software Support for assistance. Operator response: This is an internal error. Explanation: See message. If the problem persists. The select user name is missing. Explanation: See message. System action: R3batch stops. contact IBM Software Support for assistance. EEWO0742E The following user does not have "abort" privileges: user_name. If the problem persists. Explanation: job_name and job_ID identify the job that could not be copied. Operator response: This is an internal error. The BP_JOB_COPY function could not copy the following job: Job name: job_name Job ID: job_ID. Explanation: See message. Explanation: See message. System action: R3batch stops. EEWO0749E An internal error has occurred. The joblog of the job cannot be deleted. System action: R3batch stops. If the problem persists. EEWO0744E An internal error has occurred. Operator response: This is an internal error. contact IBM Software Support for assistance. A running job could not be deleted. Explanation: See message. Retry the operation (the error might be transient). EEWO0750E An internal error has occurred. Retry the operation (the error might be transient). The selection option is not valid. rerun the job as a user that has these privileges. Retry the operation (the error might be transient). Explanation: See message. rerun the job as a user that has these privileges. contact IBM Software Support for assistance. EEWO0747E An internal error has occurred. Operator response: This is an internal error. If the problem persists. Explanation: See message. contact IBM Software Support for assistance. Explanation: job_name and job_ID identify the job that could not be deleted. 300 IBM Tivoli Workload Scheduler for Applications: User’s Guide . System action: The program waits for you to correct the data or exit. If the problem persists. The following identify the job: Job name: job_name Job ID: job_ID Explanation: job_name and job_ID identify the job with a joblog that could not be deleted. System action: The program might stop. Operator response: Add the missing user name to the job definitions and continue. Operator response: Determine from the system administrator whether the user can be granted "abort" privileges. EEWO0746E The following user does not have "delete" privileges: user_name. If the problem persists. Operator response: Determine from the system administrator whether the user can be granted "release" privileges. System action: R3batch stops. EEWO0743E An internal error has occurred. Retry the operation (the error might be transient). EEWO0741E The following user does not have "release" privileges: user_name.EEWO0740E • EEWO0750E EEWO0740E The user name is missing. System action: R3batch stops. rerun the job as a user that has these privileges. The following identify the job: Job name: job_name Job ID: job_ID. Explanation: See message. If not. EEWO0745E An internal error has occurred. The select job name is missing. Operator response: This is an internal error. Operator response: This is an internal error. Operator response: Determine from the system administrator whether the user can be granted "delete" privileges. Retry the operation (the error might be transient). Retry the operation (the error might be transient). EEWO0748E An internal error has occurred. System action: R3batch stops. If not.

Operator response: This is an internal error. Operator response: This is an internal error. An incorrect action was performed while maintaining the status of interception and parent-child functionality. Retry the operation (the error might be transient). Messages 301 . See also: The User’s Guide for instructions about how to activate interception functions. If the problem persists. Retry the operation (the error might be transient). EEWO0752E An internal error has occurred. EEWO0753E An internal error has occurred. A selection parameter is not valid. EEWO0757E An internal error has occurred. If the problem persists. System action: R3batch stops. contact IBM Software Support for assistance. If the problem persists. If the problem persists. contact IBM Software Support for assistance. Operator response: Check R/3 syslog. See also: The User’s Guide for instructions about how to activate parent-child functions. Operator response: This is an internal error. Operator response: This is an internal error. EEWO0756E An internal error has occurred. Explanation: See message. Retry the operation (the error might be transient). Operator response: This is an internal error. contact IBM Software Support for assistance. Operator response: This is an internal error. EEWO0755E An internal error has occurred. Retry the operation (the error might be transient). Rerun r3batch. Retry the operation (the error might be transient). Explanation: See message. If the problem persists. The program could not commit the changes in the database tables when calling the following function module: module. Rerun r3batch. The specified date and/or time is invalid. contact IBM Software Support for assistance. An event does not exist. Retry the operation (the error might be transient). Explanation: See message. Retry the operation (the error might be transient). contact IBM Software Support for assistance. contact IBM Software Support for assistance. Retry the operation (the error might be transient). EEWO0762E Interception functionality is not active. An incorrect confirmation type was found while confirming a job. If the problem persists. Operator response: This is an internal error. System action: R3batch stops. Operator response: Activate interception functionality as described in the User’s Guide. Explanation: See message. System action: R3batch stops. Explanation: See message. EEWO0758E An internal error has occurred. Explanation: See message. Explanation: See message. EEWO0760E An internal error has occurred. Operator response: Check R/3 syslog. If the problem persists.EEWO0751E • EEWO0762E EEWO0751E An internal error has occurred. Explanation: See message. Chapter 31. Explanation: See message. contact IBM Software Support for assistance. contact IBM Software Support for assistance. EEWO0754E An internal error has occurred. System action: The program might stop. System action: R3batch stops. System action: R3batch stops. If the problem persists. EEWO0759E The confirmation of a job has failed. The specified server name is invalid Explanation: See message. System action: R3batch stops. System action: The program might stop. System action: R3batch stops. Operator response: This is an internal error. An event could not be raised. System action: R3batch stops. EEWO0761E Parent-child functionality is not active. System action: R3batch stops. An incorrect client was found while retrieving intercepted jobs. Explanation: See message. Operator response: Activate parent-child functionality as described in the User’s Guide. Explanation: See message.

EEWO0766E An internal error has occurred. Explanation: See message. The following identify the job: Job name: job_name Job ID: job_ID. Operator response: Determine from the system administrator whether the user can be granted "modify" privileges. System action: R3batch stops. Explanation: job_name and job_ID identify the job that could not be released.EEWO0763E • EEWO0771E EEWO0763E An internal error has occurred. job_name and job_ID identify the job that does not have a valid server. Change the job definition accordingly and continue. If the problem persists. Operator response: This is an internal error. contact IBM Software Support for assistance. Explanation: job_name and job_ID identify the job with data that could not be read. If the problem persists. An incorrect counter value was found while retrieving the list of reports. contact IBM Software Support for assistance. EEWO0769E An internal error occurred while locking a job in the R/3 database table. System action: R3batch stops. System action: R3batch stops. Retry the operation (the error might be transient). System action: R3batch stops. Retry the operation (the error might be transient). contact IBM Software Support for assistance. EEWO0764E The specified printer is not recognized by the R/3 system. If the problem persists. Operator response: This is an internal error. Retry the operation (the error might be transient). Retry the operation (the error might be transient). EEWO0767E An internal error has occurred. 302 IBM Tivoli Workload Scheduler for Applications: User’s Guide . contact IBM Software Support for assistance. If not. Operator response: This is an internal error. Explanation: See message. Operator response: This is an internal error. Explanation: job_name and job_ID identify the job that could not be locked. Operator response: This is an internal error. Operator response: This is an internal error. you should rerun the job as a user that has these privileges. Explanation: See message. Explanation: job_name and job_ID identify the job for which a child process could not be registered. The following identify the job: Job name: job_name Job ID: job_ID. Explanation: The target server indicated in the job definition is not correct. If the problem persists. System action: R3batch stops. Retry the operation (the error might be transient). System action: The program waits for you to change the job definitions and continue or to exit. The new data for a job are not valid. Retry the operation (the error might be transient). EEWO0770E An internal error occurred while attempting to release the following job: Job name: job_name Job ID: job_ID. System action: R3batch stops. If the problem persists. System action: R3batch stops. EEWO0768E The following user does not have "modify" privileges: user_name. Retry the operation (the error might be transient). System action: R3batch stops. Explanation: job_name and job_ID identify the job that has new data that is not valid. If the problem persists. EEWO0765E An internal error occurred during the registration of a child for the following job: Job name: job_name Job ID: job_ID. The job data for the following job could not be read: Job name: job_name Job ID: job_ID. contact IBM Software Support for assistance. Operator response: Contact the SAP system administrator to obtain the correct name of the target server for this job. contact IBM Software Support for assistance. contact IBM Software Support for assistance. EEWO0771E The target server for a job is not a valid server. If the problem persists. It has either been incorrectly typed or is not valid for the job. Operator response: This is an internal error. The following identify the job: Job name: job_name Job ID: job_ID.

contact IBM Software Support for assistance. A problem has been found with the print or archive mask. If the problem persists. EEWO0775E An internal error has occurred. The start date for a job is not valid. Retry the operation (the error might be transient). Operator response: This is an internal error. If not. Explanation: job_name and job_ID identify the job that has a non-valid start date. Retry the operation (the error might be transient). contact IBM Software Support for assistance. Explanation: job_name and job_ID identify the job for which print and archive parameters could not be retrieved. contact IBM Software Support for assistance. or both. Explanation: job_name and job_ID identify the job that could not be modified. EEWO0778E An internal error has occurred. Explanation: job_name and job_ID identify the job for which information could not be retrieved. contact IBM Software Support for assistance. this is an internal error. EEWO0777E An internal error has occurred. Operator response: This is an internal error. If the problem persists. Operator response: Check that all network connections are working and retry the operation (the error might be transient). System action: R3batch stops. Operator response: This is an internal error. Explanation: job_name and job_ID identify the job that could not be modified. Operator response: Retry the operation (the error might be transient). this is an internal error. contact IBM Software Support for assistance. System action: R3batch stops. The following job can no longer be modified: Job name: job_name Job ID: job_ID. System action: R3batch stops. If it persists. If the problem persists. The following identify the job: Job name: job_name Job ID: job_ID. System action: R3batch stops. Explanation: job_name and job_ID identify the job with an ABAP step that has a problem with the print or archive mask. The step that needs to be added to a job has the wrong step type. EEWO0779E An internal error has occurred. The program could not retrieve information about the following job: Job name: job_name Job ID: job_ID. contact the SAP system administrator to determine if the status of the indicated job has been changed such that it is no longer modifiable. contact IBM Software Support for assistance. Explanation: job_name and job_ID identify the job for Chapter 31. If the problem persists. Operator response: Check that all network connections are working and retry the operation (the error might be transient). The following identify the job: Job name: job_name Job ID: job_ID. EEWO0773E An internal error has occurred. EEWO0776E An internal error has occurred. EEWO0774E An internal error has occurred. this is an internal error. Retry the operation (the error might be transient). contact IBM Software Support for assistance. If the problem persists. System action: R3batch stops.EEWO0772E • EEWO0779E EEWO0772E An internal error has occurred. The program could not modify the following job: Job name: job_name Job ID: job_ID. while modifying an ABAP step of the following job: Job name: job_name Job ID: job_ID. Operator response: Check that all network connections are working and retry the operation (the error might be transient). Messages 303 . The program could not retrieve the print and archive parameters while adding a step to the following job: Job name: job_name Job ID: job_ID. System action: R3batch stops. System action: R3batch stops. or both. If the problem persists. this is an internal error. Explanation: job_name and job_ID identify the job that has the wrong step type. The program could not modify the worktable for the following job: Job name: job_name Job ID: job_ID.

contact IBM Software Support for assistance. If the problem persists. contact IBM Software Support for assistance. EEWO0787E An internal error has occurred. If the problem persists. If the problem persists. 304 IBM Tivoli Workload Scheduler for Applications: User’s Guide . Operator response: Check that all network connections are working and retry the operation (the error might be transient). System action: R3batch stops. EEWO0780E An internal error has occurred. If the problem persists. Explanation: See message. If the problem persists. Explanation: See message. Retry the operation (the error might be transient). EEWO0785E The variant already exists. Operator response: This is an internal error. this is an internal error. Operator response: Check that all network connections are working and retry the operation (the error might be transient). System action: R3batch stops. Operator response: This is an internal error. The program has found that the following job does not have an expected step: Job name: job_name Job ID: job_ID. contact IBM Software Support for assistance. Explanation: job_name and job_ID identify the job for which the step information is not available. The program has found incorrect selection options. Explanation: See message. Explanation: job_name and job_ID identify the job for which the parent-child relationship data is not consistent. EEWO0781E An internal error has occurred. Retry the operation (the error might be transient). this is an internal error. Operator response: This is an internal error. Retry the operation (the error might be transient). Retry the operation (the error might be transient). The program could not read the worktable for the following job: Job name: job_name Job ID: job_ID. System action: R3batch stops. System action: R3batch stops. Operator response: Check that all network connections are working and retry the operation (the error might be transient). Operator response: This is an internal error. this is an internal error. Retry the operation (the error might be transient). System action: R3batch stops. EEWO0784E An internal error has occurred. Retry the operation (the error might be transient). Explanation: job_name and job_ID identify the job for which an expected step is missing. The report or variant is not valid. System action: R3batch stops. Explanation: See message. EEWO0783E An internal error has occurred. Operator response: This is an internal error. contact IBM Software Support for assistance. The program could not modify the step for the following job because no step information has been provided: Job name: job_name Job ID: job_ID. System action: R3batch stops. EEWO0782E The program has found an inconsistency in the data concerning the parent-child relationship for the following job: Job name: job_name Job ID: job_ID. System action: R3batch stops. If the problem persists. Explanation: job_name and job_ID identify the job for which the worktable could not be read. contact IBM Software Support for assistance. If the problem persists. If the problem persists. contact IBM Software Support for assistance. contact IBM Software Support for assistance. EEWO0786E An internal error has occurred. The following user is not authorized to perform the requested action: user_name. If the problem persists.EEWO0780E • EEWO0787E which the worktable could not be modified. contact IBM Software Support for assistance. contact IBM Software Support for assistance. Operator response: This is an internal error. System action: R3batch stops.

Explanation: See message. contact IBM Software Support for assistance. Explanation: See message. Retry the operation (the error might be transient).EEWO0788E • EEWO0799E EEWO0788E An internal error has occurred. If the problem persists. The action has not been performed. EEWO0794E An internal error has occurred. System action: R3batch stops. The variant has not been supplied. Operator response: This is an internal error. The table is not active. Operator response: This is an internal error. contact IBM Software Support for assistance. contact IBM Software Support for assistance. Retry the operation (the error might be transient). The table has no fields. Operator response: This is an internal error. The report does not have selection screens. EEWO0791E An internal error has occurred. System action: R3batch stops. If the problem persists. contact IBM Software Support for assistance. Retry the operation (the error might be transient). EEWO0792E An internal error has occurred. If the problem persists. contact IBM Software Support for assistance. If the problem persists. Retry the operation (the error might be transient). System action: R3batch stops. Explanation: See message. If the problem persists. EEWO0789E An internal error has occurred. The variant could not be locked. Operator response: This is an internal error. Explanation: See message. System action: R3batch stops. Explanation: See message. Retry the operation (the error might be transient). The report definition could not be loaded. Operator response: This is an internal error. If the problem persists. Retry the operation (the error might be transient). System action: R3batch stops. contact IBM Software Support for assistance. contact IBM Software Support for assistance. Retry the operation (the error might be transient). System action: R3batch stops. EEWO0793E An internal error has occurred. Explanation: See message. contact IBM Software Support for assistance. Operator response: This is an internal error. If the problem persists. Retry the operation (the error might be transient). Explanation: See message. The variant selections do not match. Retry the operation (the error might be transient). Retry the operation (the error might be transient). EEWO0795E An internal error has occurred. The variant variable maintenance parameters are not valid. Explanation: See message. Operator response: This is an internal error. Retry the operation (the error might be transient). Explanation: See message. System action: R3batch stops. EEWO0797E An internal error has occurred. Explanation: See message. contact IBM Software Support for assistance. Operator response: This is an internal error. Chapter 31. The table is locked. If the problem persists. Operator response: This is an internal error. If the problem persists. EEWO0798E An internal error has occurred. EEWO0796E An internal error has occurred. Operator response: This is an internal error. Retry the operation (the error might be transient). If the problem persists. The variant name is not valid. The variant could not be deleted. Operator response: This is an internal error. Explanation: See message. If the problem persists. EEWO0790E An internal error has occurred. System action: R3batch stops. EEWO0799E An internal error has occurred. System action: R3batch stops. contact IBM Software Support for assistance. System action: R3batch stops. contact IBM Software Support for assistance. System action: R3batch stops. Messages 305 . Explanation: See message. contact IBM Software Support for assistance. Operator response: This is an internal error. If the problem persists. System action: R3batch stops.

Explanation: See message. If you find an error. Explanation: See message. System action: R3batch stops. this is an internal error. correct it and continue. Explanation: See message. If you do not find an error in the expression. Operator response: This is an internal error. If you find an error. contact IBM Software Support for assistance. Explanation: See message. The values for the requested field could not be read. Operator response: This is an internal error. If the problem persists. If the problem persists. If the problem persists. If you find an error. Retry the operation (the error might be transient). If you do not find an error in the expression. System action: R3batch stops. Retry the operation (the error might be transient). Retry the operation (the error might be transient). Retry the operation (the error might be transient). Retry the operation (the error might be transient). contact IBM Software Support for assistance. System action: R3batch waits for you to input data or exit. See also: The User’s Guide for details about the syntax of the arithmetic expression. 306 IBM Tivoli Workload Scheduler for Applications: User’s Guide . contact IBM Software Support for assistance. If the problem persists. Explanation: See message. If you do not find an error in the expression. If the problem persists. If the problem persists. EEWO0808E An internal syntax error has occurred: the arithmetic expression is not terminated.EEWO0800E • EEWO0808E EEWO0800E An internal error has occurred. If the problem persists. System action: R3batch waits for you to input data or exit. contact IBM Software Support for assistance. Operator response: Check the syntax of the date expression in the job definition. System action: R3batch stops. Explanation: See message. System action: R3batch waits for you to input data or exit. System action: R3batch stops. EEWO0804E An internal error has occurred. The function module J_1O1_DATETIME has failed. EEWO0802E An internal error has occurred. contact IBM Software Support for assistance. Retry the operation (the error might be transient). Retry the operation (the error might be transient). See also: The User’s Guide for details about the syntax of the date expression. EEWO0806E An internal syntax error has occurred: the date expression is not terminated Explanation: See message. The job last run time feature is not yet supported. EEWO0801E An internal error has occurred. contact IBM Software Support for assistance. contact IBM Software Support for assistance. System action: R3batch waits for you to input data or exit. Explanation: See message. If you find an error. Operator response: This is an internal error. Retry the operation (the error might be transient). If the problem persists. contact IBM Software Support for assistance. Operator response: Check the syntax of the date expression in the job definition. Operator response: Check the syntax of the arithmetic expression in the job definition. See also: The User’s Guide for details about the syntax of the date expression. Explanation: See message. contact IBM Software Support for assistance. this is an internal error. EEWO0803E An internal syntax error has occurred in the expression. See also: The User’s Guide for details about the syntax of the date expression. correct it and continue. The calendar placeholder feature is not yet supported. EEWO0807E An internal syntax error has occurred: the date expression contains no data. Retry the operation (the error might be transient). Operator response: This is an internal error. The expression could not be evaluated. If the problem persists. Operator response: This is an internal error. EEWO0805E An internal error has occurred. If you do not find an error in the expression. System action: R3batch stops. Operator response: Check the syntax of the date expression in the job definition. correct it and continue. correct it and continue. The result buffer for variant placeholders is too small. this is an internal error. this is an internal error.

EEWO0823E An internal error has occurred. If the problem persists. Retry the operation (the error might be transient). If the problem persists. Explanation: See message.EEWO0809E • EEWO0825E EEWO0809E An internal syntax error has occurred: the arithmetic expression contains no data.0. EEWO0822E An internal error has occurred. The internal buffer is too small for the arithmetic expression. this is an internal error. Retry the operation (the error might be transient). EEWO0825E An internal error has occurred. Explanation: See message. Operator response: This is an internal error. correct it and continue. System action: R3batch stops. System action: R3batch waits for you to input data or exit. If the problem persists. Explanation: See message. External command steps are not supported for versions of BC-XBP less than 2. Operator response: This is an internal error. System action: R3batch stops. No scheduling data can be found for the following InfoPackage: InfoPackage_name. contact IBM Software Support for assistance. Operator response: This is an internal error. Messages 307 . See also: The User’s Guide for details about the syntax of the arithmetic expression. Retry the operation (the error might be transient). The job of the following InfoPackage has not started: InfoPackage_name. contact IBM Software Support for assistance. Retry the operation (the error might be transient). System action: R3batch stops. System action: R3batch stops. Chapter 31. System action: R3batch waits for you to input data or exit. contact IBM Software Support for assistance. Explanation: See message. See also: The User’s Guide for details about the syntax of the arithmetic expression. Explanation: InfoPackage_name identifies the InfoPackage associated with this job or step. EEWO0820E An internal error has occurred. System action: R3batch stops. If you do not find an error in the expression. Explanation: See message. The table does not contain the requested field. Retry the operation (the error might be transient). Explanation: See message. System action: R3batch stops. System action: R3batch stops. this is an internal error. If the problem persists. The job of the following InfoPackage does not exist: InfoPackage_name. EEWO0821E An internal error has occurred. contact IBM Software Support for assistance. Retry the operation (the error might be transient). EEWO0811E An internal error has occurred. contact IBM Software Support for assistance. contact IBM Software Support for assistance. If you do not find an error in the expression. contact IBM Software Support for assistance. If you find an error. correct it and continue. Operator response: This is an internal error. Retry the operation (the error might be transient). If the problem persists. contact IBM Software Support for assistance. If the problem persists. EEWO0824E An internal error has occurred. If the problem persists. Operator response: Check the syntax of the arithmetic expression in the job definition. Operator response: This is an internal error. Operator response: This is an internal error. If you find an error. EEWO0810E An internal syntax error has occurred in the arithmetic expression. Retry the operation (the error might be transient). If the problem persists. If the problem persists. Operator response: Check the syntax of the arithmetic expression in the job definition. Operator response: This is an internal error. Retry the operation (the error might be transient). The variant has no description in the requested language. Explanation: See message. contact IBM Software Support for assistance. Explanation: See message.

Explanation: See message. stop the job. System action: The operation is not performed. Explanation: See message. System action: R3batch continues. No BDC sessions were found that matched the following session name: "session_name". If the problem persists. Explanation: See message. Explanation: See message. System action: R3batch continues. Operator response: If the BDCWAIT is essential to the successful performance of the job. The problem with copying the joblog does not impact how the job is performed. The program has found the following incorrectly formed BDCWAIT keyword: BDCWAIT_keyword.EEWO0826E • EEWO0910W EEWO0826E The extended agent could not delete a record from the interception criteria table on the target R/3 system. System action: R3batch continues. and rerun r3batch. Operator response: If you require SIGTERM handling for the correct processing of this job. Explanation: See message. System action: R3batch continues. System action: R3batch continues. ask the system administrator to allow SIGTERM handling for this product. stop the job. Operator response: If it is important to know the status of the job. contact IBM Software Support for assistance. System action: R3batch continues but SIGTERMs are ignored. EEWO0901W The following product could not be registered for SIGTERM handling: "product_name". The following BDCWAIT keyword does not have the correct syntax: BDCWAIT_keyword. Operator response: Retry the operation. 1 1 1 1 1 Explanation: The value set for the bdc_job_status_failed option is not valid. SIGTERMs will be ignored. Operator response: If the BDCWAIT is essential to the successful performance of the job. contact your R/3 system administrator. Explanation: See message. Retry the operation (the error might be transient). 308 IBM Tivoli Workload Scheduler for Applications: User’s Guide . For example. do so on the R/3 system instead of locally. EEWO0902W The program cannot check the status of the job. but the job has been cancelled. EEWO0909W An internal error has occurred. Explanation: See message. look at the syslog to attempt to identify what is preventing the status from being obtained. Retry the operation (the error might be transient). ignore. or an integer greater than 0. 1 System action: The operation is not performed. Operator response: If the BDCWAIT is essential to the successful performance of the job. 1 Operator response: Set a correct value for the option 1 and retry the operation. contact IBM Software Support for assistance. EEWO0904W The program could not copy the joblog to stdout. If the problem persists. Operator response: If you need to consult the joblog. The BDCWAIT will be ignored. Check with the Tivoli Workload Scheduler operator the reasons for the job cancellation and decide if you need to take any further action. Explanation: The extended agent tried to delete an interception criteria record on the R/3 system and the remote operation failed. stop the job. System action: R3batch continues. but the BDCWAIT is ignored. Retry the operation (the error might be transient). but the BDCWAIT is ignored. but the BDCWAIT is ignored. EEWO0908W An internal error has occurred. Operator response: Check the R/3 joblog for more details. EEWO0903W The job has been cancelled by the Tivoli Workload Scheduler operator. the agent continues. If the problem persists. but will try again later. The only allowed values are: all. stop the job. see the R/3 joblog for details. EEWO0910W An internal error has occurred. there might be a network problem restricting the communication with the job. If the 1 EEWO0827E The value set for the bdc_job_status_failed option is not 1 valid.

Retry the operation (the error might be transient). Either the joblog or the job protocol for the following job does not exist: Job name: job_name Job ID: job_ID. Explanation: The program creates an internal table of BDC sessions to maintain the status of each session. Either the joblog or the job protocol for the following job is empty: Job name: job_name Job ID: job_ID. If the problem persists. System action: R3batch continues. Explanation: job_name and job_ID identify the job for which the joblog is empty. The spool ID is not valid Explanation: See message. using the default trace level: DEBUG_MAX. stop the job and contact the SAP system administrator to determine why the spool ID is not valid. If the problem persists. contact IBM Software Support for assistance. System action: R3batch continues. Operator response: If you need to have log information for the successful running of this job. but the BDCWAIT is ended. If the problem persists. contact IBM Software Support for assistance. stop the job. The wait is terminated for the following session: "session_name" and "queue_id". Messages which the job protocol does not exist. System action: R3batch continues. The BDC session found previously can no longer be found in the BDC status table. EEWO0912W An internal error has occurred. No BDC sessions were found that matched the following qid: "qid". EEWO0915W An internal error has occurred. contact IBM Software Support for assistance.EEWO0911W • EEWO0917W problem persists. If the problem persists. but log information is not available. Operator response: If you need to have log information for the successful running of this job. EEWO0917W An internal error has occurred. Operator response: If you need to have log information for the successful running of this job. The default value of 3 (DEBUG_MAX) is used instead. System action: R3batch continues. When the problem has been resolved rerun r3batch. contact IBM Software Support for assistance. but log information is not available. 309 . contact IBM Software Support for assistance. System action: R3batch continues. contact IBM Software Support for assistance. If the problem persists. Operator response: If the BDCWAIT is essential to the successful performance of the job. stop the job and contact the SAP system administrator to determine why the step has no spool list. Operator response: If the BDCWAIT is essential to the successful performance of the job. but log information is not available. stop the job and contact the SAP system administrator to determine why the joblog or job protocol is empty. but the BDCWAIT is ignored. but log information is not available. Retry the operation (the error might be transient). Explanation: The -tracelvl option in the job definition has a value that is not valid. Explanation: job_name and job_ID identify the job for Chapter 31. When the problem has been resolved rerun r3batch. System action: R3batch continues. See also: The User’s Guide for details about the -tracelvl option settings in the job definition. The BDCWAIT will be ignored. When the problem has been resolved rerun r3batch. EEWO0911W An internal error has occurred. EEWO0914W An internal error has occurred. EEWO0916W An internal error has occurred. EEWO0913W The following trace level in the job definition is not valid: "trace_level". stop the job and contact the SAP system administrator to determine why the joblog or job protocol does not exist. stop the job. Explanation: See message. The step has no spool list Explanation: See message. A session that had previously been found and loaded into the table can no longer be found. Operator response: If you need to have log information for the successful running of this job. When the problem has been resolved rerun r3batch. System action: R3batch continues. Operator response: Correct the value supplied in the job definition for the -tracelvl option to one of the values indicated in the User’s Guide.

Operator response: Contact IBM Software Support for assistance. but log information is not available. Explanation: This is an internal error caused by one module of r3batch not supplying the indicated parameter when calling another module. System action: R3batch continues. contact IBM Software Support for assistance. and rerun the command. Explanation: You have tried to commit an external dependency on the SAP event name and parameter indicated in the message. EEWO0921W An internal error has occurred. it they have not. EEWO0961W The external dependency cannot be committed because the SAP event name: "event_name" and event parameter: "event_parameter" which is the subject of the dependency has not been found on the SAP system. EEWO0930W The following language is not valid: "language". The program requires the "-flag type=exec" parameter to be specified for dynamic job creation. System action: R3batch continues. Operator response: You might choose to warn the SAP system administrator that a job for this RFC user has been submitted. Explanation: See message. Explanation: job_name and job_ID identify the job for which the spoollist could not be read. Explanation: See message. but the job is not created. or both. edit the job options and change the twsxa_lang or twsmeth_lang parameter values to a valid value as described in the User’s Guide. Operator response: If you need to have log information for the successful running of this job. System action: R3batch continues. If they are not. with an internal error. When the problem has been resolved rerun r3batch. or it has not been created on the SAP system. but the job cannot be run. System action: R3batch continues. but the event could not be found on the SAP system. Operator response: Contact the R/3 system administrator to activate background processing resources in the R/3 system. The spoollist of the following job cannot be read: Job name: job_name Job ID: job_ID. this message might indicate that the process has completed successfully. EEWO0960W No calendar data for the SAP Factory Calendar ID and year range defined in the input can be found in the SAP R/3 system. EEWO0920W An internal error occurred. EEWO0950W The RFC user is already logged on Explanation: See message. Operator response: Check if the SAP event and parameter have been correctly defined in Tivoli Workload Scheduler and change them. Depending on circumstances. System action: R3batch continues. but that this user is already logged on. rerun r3batch (the problem might be transient). See also: The User’s Guide for more information about the language options. and your 310 IBM Tivoli Workload Scheduler for Applications: User’s Guide . Explanation: The SAP factory calendar ID and year range specified with the r3batch "RSC" task could not find any data to export. Operator response: If you do not want the job to continue in the indicated default language. The following default language is used: "default_language". or year range. stop the job and contact the SAP system administrator to determine why the spool list cannot be read. To correct the language selection. stop the job. Check whether the SAP event exists on the SAP system. If the problem persists. Either the SAP event is incorrectly defined in Tivoli Workload Scheduler. If the event does not exist. System action: R3batch continues. EEWO0919W There are no background processing resources active in the R/3 system. Operator response: Change the SAP Factory Calendar ID. but no output is provided. System action: R3batch continues. Then rerun r3batch.EEWO0918W • EEWO0961W EEWO0918W The report list selection is finished Explanation: The program is reading the report list from the SAP system. or that the selection has terminated unexpectedly. System action: R3batch continues. Operator response: Check that the reports received from the SAP system are what you are expecting.

stop it. For details. Without the semaphore. The process chain cannot be 1 restarted. 1 Explanation: See message. see the SAP Note: sap_note. Conman could not be run to submit the intercepted SAP job: Explanation: See message. The 1 process chain cannot be restarted. Retry the operation (the error might be transient). Explanation: The semaphore allows the RFC function modules to synchronize their use of system resources. 1 Explanation: See message.EEWO0970W • EEWO1065W dependency is defined correctly. but the process 1 chain is not restarted. waiting for a resource to become available. Contact 1 IBM Software Support for assistance. If the problem persists. The following RFC function module will not be synchronized: function_module. Contact 1 IBM Software Support for assistance. waiting for a resource to become available. When the problem has been resolved rerun r3batch. Operator response: This is an internal error. 1 System action: R3batch continues. EEWO1005W An error occurred while retrieving the spool list for a step: Explanation: See message. 1 System action: R3batch continues. If the problem persists. System action: R3batch stops. Retry the operation (the error might be transient). 1 1 Explanation: R3batch tries to perform an SAP R/3 1 function. Messages 311 . Chapter 31. Contact 1 IBM Software Support for assistance. Operator response: If the use of the semaphore is important for the job being run. 1 Operator response: This is an internal error. 1 System action: R3batch continues. 1 EEWO1063W An error occurred while adding the 1 information about the submitted process 1 chain to the common serialization file 1 file_name. a module might time-out. this message is for information only. but return code mapping of this job cannot be performed. Retry the operation (the error might be transient). but the backend system does not have the 1 correct SAP support package level installed. there is an internal error. If this is not possible to determine. contact IBM Software Support for assistance. 1 Operator response: Check the SAP system and follow 1 the instructions in the SAP Note. 1 Explanation: See message. System action: R3batch continues. If this is not possible to determine. a module might time-out. 1 EEWO1065W The environment variable env_var is 1 not set. System action: R3batch continues. If the problem persists. EEWO0998W An internal error occurred while trying to open the semaphore. function_module is the RFC function module that cannot open its semaphore. function_module is the RFC function module that cannot obtain a semaphore. check in the log and with the SAP system administrator to try and determine why the semaphore could not be obtained. 1 EEWO0970W The SAP component: sap_comp does not 1 have the correct SAP support package 1 level installed. there is an internal error. contact IBM Software Support for assistance. EEWO1034E An internal error has occurred. 1 EEWO1064W An error occurred while opening the 1 common serialization file file_name. System action: R3batch continues. 1 Operator response: This is an internal error. check in the log and with the SAP system administrator to try and determine why the semaphore could not be obtained. stop the job. The following RFC function module will not be synchronized: function_module. and contact the SAP system administrator to determine why the spool list could not be retrieved. The process chain cannot be 1 restarted. stop the job. Explanation: The semaphore allows the RFC function modules to synchronize their use of system resources. Operator response: If return code mapping is crucial to the job. contact IBM Software Support for assistance. but the process 1 chain is not restarted. EEWO0997W An internal error occurred while trying to obtain the semaphore. Without the semaphore. 1 System action: R3batch continues. Operator response: If the use of the semaphore is important for the job being run. 1 Operator response: This is an internal error. but the process 1 chain is not restarted.

1 System action: R3batch continues. 1 1 Explanation: See message. 1 Operator response: This is an internal error. 1 Operator response: This is an internal error. but the process 1 chain is not restarted. 1 1 Explanation: See message.EEWO1066W • EEWO1070E 1 EEWO1066W The file file_name cannot be locked. 1 System action: R3batch continues. Contact 1 IBM Software Support for assistance. 1 System action: R3batch continues. 1 Operator response: This is an internal error. but the process 1 chain is not restarted. 1 System action: R3batch continues. Contact 1 IBM Software Support for assistance. 1 Operator response: Specify a valid process ID and 1 retry the operation. 312 IBM Tivoli Workload Scheduler for Applications: User’s Guide . 1 EEWO1069E The common serialization file does not contain any information about the 1 process chain identified by value. 1 1 Explanation: See message. 1 1 Explanation: See message. It will not be updated. No process in the process chain 1 will be restarted. The process chain 1 is not restarted. The process chain cannot be 1 restarted. 1 EEWO1067W An error occurred while updating the information about the submitted process 1 chain in the common serialization file 1 file_name. but the process 1 chain is not restarted. Contact 1 IBM Software Support for assistance. 1 EEWO1070E The specified process ID process_id is not valid. but the process 1 chain is not restarted.

the agent has completed all its activities successfully. EEWP0050E An error has occurred in the Oracle application. and restart the agent. You might need to contact the Oracle application administrator. take no action. EEWP0101W back-end_program_name . System action: The agent stops. System action: The agent stops. If the Oracle job has not yet been stopped. contact IBM Software Support for assistance. This might be a violation of the security rules at your workplace. Explanation: See message. Operator response: Check the log for associated messages. Check in the logs for associated messages that might explain why the stop did not work.P This section lists error and warning messages that might be issued by the Oracle E-Business Suite access method processes. Fix the problem and restart the agent. stop the agent. System action: The extended agent stops. System action: The program continues. The return code is return_code EEWPD0410E MCMTJ . Operator response: If you intended to leave the password unencrypted. Explanation: See message. EEWP0049I The Tivoli Workload Scheduler for Oracle extended agent has terminated. look in the log for preceding messages that give more information. Fix any problems.You are using an unencrypted password. If the problem persists. Oracle messages can be found in the Tivoli Workload Scheduler log. Operator response: If the return code is 0.log for associated messages. and retry the operation. copy and paste the encrypted password into the options file. Fix the problem and restart the agent.An error occurred while the agent was stopping the Oracle job. Explanation: An error occurred while the MCMTJ back-end process was trying to stop the Oracle job. Operator response: Check in the Tivoli Workload Scheduler log and in the Oracle log file named sqlnet. use the enigma utility to encrypt the Chapter 31. System action: The extended agent stops. Operator response: You might want to ask the Oracle administrator to stop the Oracle job manually. Explanation: The indicated back-end program has found an unencrypted password in the options file. If you do not want to use unencrypted passwords. EEWP0046E An error has occurred while launching the back-end processes. contact IBM Software Support for assistance. save the options file. Some messages might also be found in the Oracle log file.EEWP0046E • EEWPD0410E Oracle access method messages . password. retry the operation. If the problem persists. If the problem persists. Explanation: See message. Messages 313 . If the return code is nonzero. contact IBM Software Support for assistance. Try to identify and fix the problem.

N” on page 276. System action: The program cannot proceed. retry the operation.HTWGT0001E • HTWGT0008W PeopleSoft access method messages . HTWGT0005E The program cannot read the file "file". HTWGT0008W The specified option "option" has been supplied more than once.HTWGT This section lists error and warning messages that might be issued by thePeopleSoft access method processes. See also: The User’s Guide for the syntax of the job definition. Operator response: If the default value is not correct. If the problem persists. v You have the correct permissions to access the file. The subcomponent code is GT. When you have fixed the problem. HTWGT0006E The job definition task string has not been specified. See also: The User’s Guide for a description of the valid values for the option. which has a product code of HTW. Explanation: See message. supplying a valid value for the option. supplying a valid value for the option. HTWGT0001E An internal error has occurred. The program cannot initialize the option source class "option_source_class" required to read the global or local options file. Job Definition 2. The default value for the computer where the access method is running is used. Operator response: Resubmit the job. HTWGT0007W The specified option "option" has been supplied without the required value. 314 IBM Tivoli Workload Scheduler for Applications: User’s Guide . cancel the job and resubmit it. specifying the job definition task string. Explanation: See message. Operator response: Retry the operation. System action: The program proceeds. Explanation: See message. These messages are from Tivoli Workload Scheduler for Visualized Data Centers. contact IBM Software Support for assistance. see “PeopleSoft access method messages . Global options Operator response: If the default value is not correct. HTWGT0003W The value of the specified option "option" is not valid. System action: The program proceeds. See also: The User’s Guide for a description of the valid values for the option. using the default value. Explanation: See message. Local options 3. HTWGT0002E An internal error has occurred. Explanation: See message. v The file is not corrupt. System action: The program cannot proceed. contact IBM Software Support for assistance. with different values. Explanation: See message. Operator response: Verify the following: v The file exists and the name of the file is correct. Explanation: This message occurs if an option has been supplied in more than one of the following: v Job definition v Local options v Global options System action: The program proceeds. System action: The program cannot proceed. If the problem persists. cancel the job and resubmit it. The program cannot find the option source class "option_source_class" required to read the global or local options file. Operator response: If the default value is not correct. using the value according to the following hierarchy: 1. Operator response: Retry the operation. System action: The program cannot proceed. Note: The PeopleSoft access method also issues messages that are part of Tivoli Workload Scheduler for Applications .

contact IBM Software Support for assistance. Explanation: See message. System action: The program cannot proceed. HTWGT0013E An internal error has occurred.HTWGT0009E • HTWGT0018E cancel the job and resubmit it. System action: The program cannot proceed. The program cannot open the logger class "class". Explanation: This agent only supports job submissions. System action: The program cannot proceed. re-create. Explanation: See message. Explanation: See message. contact IBM Software Support for assistance. or renamed. System action: The program cannot proceed. Operator response: Retry the operation. Explanation: See message. Messages 315 . The line "non-valid_option_line" is ignored. If the problem persists. Operator response: Retry the operation. moved. cancel the job. The program is not authorized to initialize the class "class". or rename it to the correct name. move. System action: The program cannot proceed. Explanation: See message. HTWGT0009E The file "file" does not exist. Resolve the problem and retry the operation. HTWGT0014E An internal error has occurred. HTWGT0017E An internal error has occurred. Explanation: See message. If the problem persists. If the problem persists. See also: The User’s Guide for details of the path and name of the options files. Operator response: Retry the operation. v That no process has locked it or is writing to it. HTWGT0018E The task "task" you specified cannot be run. HTWGT0011E An I/O error occurred when reading from file "file". supplying a valid value for the option. HTWGT0010E The file "file" cannot be read. System action: The program proceeds. Explanation: See message. See also: The User’s Guide for a description of the valid values for the option. HTWGT0015E An internal error has occurred. Resolve the problem and retry the operation. and resubmit the command. System action: The program cannot proceed. Ensure that no process has locked it or is writing to it. If the file is the local or global options file. You have tried to run it to perform a different task. Explanation: See message. Operator response: Retry the operation. The program cannot find the class "class". edit the option file. Operator response: Check whether the file has been corrupted by attempting to read it. Operator response: If the job needs the option in the ignored line. Operator response: Verify the following: v The file exists and the name of the file is correct. Operator response: Retry the operation. The program cannot initialize the class "class". ignoring the non-valid line and the option it contains. Operator response: Either rerun the program to Chapter 31. contact IBM Software Support for assistance. System action: The program cannot proceed. If the problem persists. supplying a valid option line. If the problem persists. Explanation: See message. System action: The program cannot proceed. which is not allowed. v You have the correct permissions to access the file. contact IBM Software Support for assistance. HTWGT0016W A non-valid option line has been detected in the options file "options_file". contact IBM Software Support for assistance. HTWGT0012E The program is trying to open the file called "name" but the object with that name is not a file. v The file is not corrupt. System action: The program cannot proceed. Operator response: Check whether the file has been deleted.

System action: The program cannot proceed. Explanation: See message. Operator response: Retry the operation. Operator response: Retry the operation. See also: The User’s Guide for a description of the valid values for the option. System action: The program cannot proceed. 316 IBM Tivoli Workload Scheduler for Applications: User’s Guide . The job will be terminated. HTWGT0023W The value "option_value" you specified for the option "option" is not valid. Explanation: See message. contact IBM Software Support for assistance. System action: The program cannot proceed. Operator response: Retry the operation. HTWGT0021E An internal error has occurred. System action: The program cannot proceed. contact IBM Software Support for assistance. Explanation: See message. Operator response: Change the value for the option and retry the operation. If the problem persists. Operator response: Retry the operation. or choose a different agent. HTWGT0020E An internal error has occurred. Explanation: See message. contact IBM Software Support for assistance. The program cannot find the Tivoli Workload Scheduler root directory "install_directory". Explanation: See message. System action: The program cannot proceed. If the problem persists. The Tivoli Workload Scheduler root directory "install_directory" you specified is not a directory. HTWGT0019E An internal error has occurred. If the problem persists. The program cannot read the Tivoli Workload Scheduler root directory "install_directory". HTWGT0022E An error was encountered while initializing the options. If the problem persists. contact IBM Software Support for assistance.HTWGT0019E • HTWGT0023W submit a job.

A. 2003. Any reference to an IBM product. BUT NOT LIMITED TO.S. program. or features discussed in this publication in other countries. to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk. or service that does not infringe any IBM intellectual property right may be used instead. Any functionally equivalent product. © Copyright IBM Corp. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. INCLUDING. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. services. Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION ″AS IS″ WITHOUT WARRANTY OF ANY KIND. Consult your local IBM representative for information on the products and services currently available in your area. This information could include technical inaccuracies or typographical errors. program. it is the user’s responsibility to evaluate and verify the operation of any non-IBM product. Minato-ku Tokyo 106. EITHER EXPRESS OR IMPLIED. this statement might not apply to you. For license inquiries regarding double-byte (DBCS) information. program. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.Notices This information was developed for products and services offered in the U. or service. 2008 317 . therefore. Some states do not allow disclaimer of express or implied warranties in certain transactions. You can send license inquiries. to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome. IBM may not offer the products. Changes are periodically made to the information herein.A. NY 10504-1785 U. these changes will be incorporated in new editions of the publication. The furnishing of this publication does not give you any license to these patents. or service is not intended to state or imply that only that IBM product. contact the IBM Intellectual Property Department in your country or send inquiries.S. in writing. IBM may have patents or pending patent applications covering subject matter described in this publication. or service may be used. program. in writing. However. THE IMPLIED WARRANTIES OF NON-INFRINGEMENT.

All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. brands. TX 78758 U. their published announcements or other publicly available sources. the third party software code identified below are ″Excluded Components″ and are subject 318 IBM Tivoli Workload Scheduler for Applications: User’s Guide .0 (the ″Program″).IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. the photographs and color illustrations might not appear. Therefore. IBM International Program License Agreement or any equivalent agreement between us. and products. subject to appropriate terms and conditions. some measurement may have been estimated through extrapolation. Notwithstanding the terms and conditions of any other agreement you may have with IBM or any of its related or affiliated entities (collectively ″IBM″). Actual results may vary. Such information may be available. Users of this document should verify the applicable data for their specific environment. If you are viewing this information in softcopy form.S. IBM has not tested those products and cannot confirm the accuracy of performance. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. the results obtained in other operating environments may vary significantly. Information concerning non-IBM products was obtained from the suppliers of those products. Any performance data contained herein was determined in a controlled environment. Notices and information The IBM license agreement and any applicable notices on the web download page for this product refers You to this file for details concerning terms and conditions applicable to software code identified as excluded components in the License Information document and included in IBM Tivoli Workload Scheduler for Applications 8. companies. the examples include the names of individuals. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. should contact: IBM Corporation 2Z4A/101 11400 Burnet Road Austin.4. including in some cases payment of a fee. Furthermore.A. To illustrate them as completely as possible. The licensed program described in this publication and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement. This information contains examples of data and reports used in daily business operations. compatibility or any other claims related to non-IBM products.

if and wherever such third-party acknowledgments normally appear. 3. The end-user documentation included with the redistribution. this list of conditions and the following disclaimer. The notices are provided for informational purposes.apache. Apache Jakarta ORO For the code entitled Jakarta ORO The Apache Software License. written prior permission. modify. ALPHALPHA DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE. ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.1 Copyright (c) 2000-2002 The Apache Software Foundation. if any. DATA OR PROFITS. The Program includes the following Excluded Components: v libmsg v Jakarta ORO v ISMP Installer v HSQLDB v Quick v Infozip Libmsg For the code entitled Libmsg Permission to use. and distribute this software and its documentation for any purpose and without fee is hereby granted. must include the following acknowledgment: ″This product includes software developed by the Apache Software Foundation (http://www. with or without modification. this acknowledgment may appear in the software itself. INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE. IN NO EVENT SHALL ALPHALPHA BE LIABLE FOR ANY SPECIAL. Redistribution and use in source and binary forms.org/). Redistributions in binary form must reproduce the above copyright notice. provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. 2. Version 1.to the terms and conditions of the License Information document accompanying the Program and not the license terms that may be contained in the notices below. this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. Notices 319 . NEGLIGENCE OR OTHER TORTIOUS ACTION. All rights reserved. WHETHER IN AN ACTION OF CONTRACT. copy. INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice. and that Alfalfa’s name not be used in advertising or publicity pertaining to distribution of the software without specific.″ Alternately.

0. are permitted provided that the following conditions are met: v Redistributions of source code must retain the above copyright notice. The names ″Apache″ and ″Apache Software Foundation″. OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE.4.1 v HSQLDB V1. We appreciate his contributions. THIS SOFTWARE IS PROVIDED ``AS IS’’ AND ANY EXPRESSED OR IMPLIED WARRANTIES. BUT NOT LIMITED TO. JXML. 320 IBM Tivoli Workload Scheduler for Applications: User’s Guide . with or without modification. DATA. without prior written permission of the Apache Software Foundation. Products derived from this software may not be called ″Apache″ or ″Jakarta-Oro″.41. BUT NOT LIMITED TO. OR CONSEQUENTIAL DAMAGES (INCLUDING. 1999.org/. Savarese. INDIRECT. The Program is accompanied by the following JXML software: v Quick V1. please contact apache@apache.1 IBM is required to provide you.org. Portions of this software are based upon software originally written by Daniel F. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT. INCIDENTAL.1 v InfoZip Unzip stub file V5. EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. V5. This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation. as the recipient of such software.7. SPECIAL.40. Redistribution and use in source and binary forms. All rights reserved. Inc. INCLUDING.50x) The Program includes the following Excluded Components: v Quick V1.apache. ″Jakarta-Oro″ must not be used to endorse or promote products derived from this software without prior written permission. For more information on the Apache Software Foundation. OR PROFITS. with a copy of the following license from JXML: Copyright (c) 1998. STRICT LIABILITY. 5.V5. EXEMPLARY. nor may ″Apache″ or ″Jakarta-Oro″ appear in their name. PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES. THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. please see http://www. LOSS OF USE.42 & V5. ISMP Installer (InstallShield 10. OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY.5 JXML CODE For the code entitled Quick JXML CODE. For written permission.50x) For the code entitled ISMP Installer (InstallShield 10.0. this list of conditions and the following disclaimer. WHETHER IN CONTRACT.

Rich Wales. The Program is accompanied by the following InfoZip software: v One or more of: InfoZip Unzipsfx stub file V5. Dirk Haase. AND CONTRIBUTORS ″AS IS″ AND ANY EXPRESS OR IMPLIED WARRANTIES. EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. INCIDENTAL. Mike White Notices 321 . For the purposes of this copyright and license.5 IBM is required to provide you. SPECIAL. V5. Paul von Behren. PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES. David Kirschbaum.jxml. Jean-loup Gailly. EXEMPLARY. OR PROFITS.com/mdsax/contributers. Steve P. IN NO EVENT SHALL JXML OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT. Johnny Lee. Miller. Greg Hartwig.40. Hunter Goatley. INC. Sergio Monesi.html Neither name of JXML nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. V5. ″Info-ZIP″ is defined as the following set of individuals: v Mark Adler. Dave Smith. INCLUDING. Antoine Verheijen.42 & V5. OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY.41. George Petrov. STRICT LIABILITY. Paul Kienitz. Onno van der Linden. Jonathan Hudson.html indefinitely. Harald Denker. Copyright (c) 1990-2000 Info-ZIP. as the recipient of such software.info-zip. InfoZip CODE For the code entitled InfoZip InfoZip CODE. INDIRECT. Keith Owens.v Redistributions in binary form must reproduce the above copyright notice. Greg Roelofs. THIS SOFTWARE IS PROVIDED BY JXML. BUT NOT LIMITED TO. Jean-Michel Dubois. OR CONSEQUENTIAL DAMAGES (INCLUDING. this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. Robert Heath. WHETHER IN CONTRACT. All product materials mentioning features or use of this software must display the following acknowledgement: v This product includes software developed by JXML. LOSS OF USE. Chris Herborth. Ian Gorman. Steve Salisbury. with a copy of the following license from InfoZip: v This is version 2000-Apr-09 of the Info-ZIP copyright and license. All rights reserved. The definitive version of this document should be available at ftp://ftp. Karl Davis. Inc. Kai Uwe Rommel. THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. Igor Mandrichenko.org/pub/infozip/license. Christian Spieler. OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE. BUT NOT LIMITED TO. John Bush. DATA. and its contributors: http://www.

definition. Permission is granted to anyone to use this software for any purpose. and this list of conditions. express or implied. including. special or consequential damages arising out of the use of or inability to use this software.″ and ″MacZip″ for its own source and binary releases. ports to new operating systems.″ ″Pocket UnZip. Redistributions in binary form must reproduce the above copyright notice.″ ″WiZ″ or ″MacZip″ without the explicit permission of Info-ZIP. this list of conditions and the following disclaimer. The HSQL Development Group All rights reserved. and to alter it and redistribute it freely.″ ″UnZip. as the recipient of such software. Redistributions of source code must retain the above copyright notice. 3. are permitted provided that the following conditions are met: Redistributions of source code must retain the above copyright notice. with a copy of the following license from the HSQL Development Group: Copyright (c) 2001-2002. existing ports with new graphical interfaces.1 IBM is required to provide you. different capitalizations). 322 IBM Tivoli Workload Scheduler for Applications: User’s Guide . Altered versions--including.″ ″Zip. incidental.″ without warranty of any kind. Info-ZIP retains the right to use the names ″Info-ZIP. this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.″ ″WiZ.″ ″Pocket Zip. Such altered versions are further prohibited from misrepresentative use of the Zip-Bugs or Info-ZIP e-mail addresses or of the Info-ZIP URL(s). indirect. HSQL Code For the code entitled HSQLDB HSQL CODE. disclaimer. but not limited to. Redistributions in binary form must reproduce the above copyright notice. and dynamic. Such altered versions also must not be misrepresented as being Info-ZIP releases--including. labeling of the altered versions with the names ″Info-ZIP″ (or any variation thereof. definition. Neither the name of the HSQL Development Group nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. In no event shall Info-ZIP or its contributors be held liable for any direct. and this list of conditions in documentation and/or other materials provided with the distribution. but not limited to. Redistribution and use in source and binary forms. subject to the following restrictions: 1. with or without modification. but not limited to. disclaimer. including commercial applications. 2.This software is provided ″as is. shared. 4. or static library versions--must be plainly marked as such and must not be misrepresented as being the original source. ″Pocket UnZip.7. The Program is accompanied by the following HSQL Development Group software: v HSQLDB V1.

with or without notice. ″Use″ means storing. NOTWITHSTANDING ANYTHING TO THE CONTRARY IN THIS NOTICE. If the Software is licensed for ″concurrent use″. for the Java(tm) 2 Platform TERMS FOR SEPARATELY LICENSED CODE This Program includes HP Runtime Environment for J2SE HP-UX 11i platform software as a third party component. installing. OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT. DATA. HP SOFTWARE LICENSE TERMS The following terms govern your use of the Software unless you have a separate written agreement with HP. IN NO EVENT SHALL HSQL DEVELOPMENT GROUP.THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ″AS IS″ AND ANY EXPRESS OR IMPLIED WARRANTIES. INCLUDING. Ownership Notices 323 . you may not allow more than the maximum number of authorized users to Use the Software concurrently. PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES.TXT FILE AND THE WARRANTY DISCLAIMER ATTACHED. YOU MAY NOT INSTALL OR OTHERWISE USE THE SOFTWARE. for the Java(tm) 2 Platform ATTENTION: USE OF THE SOFTWARE IS SUBJECT TO THE HP SOFTWARE LICENSE TERMS AND SUPPLEMENTAL RESTRICTIONS SET FORTH BELOW. HP-UX Runtime Environment. INCIDENTAL. STRICT LIABILITY. loading. BUT NOT LIMITED TO. License Grant HP grants you a license to Use one copy of the Software. HP has the right to change these terms and conditions at any time. executing or displaying the Software. WHETHER IN CONTRACT.ORG. INDIRECT. OR CONSEQUENTIAL DAMAGES (INCLUDING. EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. which is licensed to you under the terms of the following HP-UX license agreement and not those of this Agreement HP-UX Runtime Environment license text HP-UX Runtime Environment. THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. INSTALLING OR OTHERWISE USING THE SOFTWARE INDICATES YOUR ACCEPTANCE OF THESE LICENSE TERMS. THIRD PARTY SOFTWARE LICENSE TERMS FOUND IN THE THIRDPARTYLICENSEREADME. OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY. SPECIAL. HSQLDB. OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE. BUT NOT LIMITED TO. OR PROFITS. IF YOU DO NOT ACCEPT THESE TERMS FULLY. EXEMPLARY. You may not modify the Software or disable any licensing or control features of the Software. LOSS OF USE.

adaptations and merged portions in any form. Your license confers no title or ownership in the Software and is not a sale of any rights in the Software. unless expressly licensed for other purposes. The transferee must accept these License Terms as a condition to the transfer. HP’s consent may not be required for disassembly or decompilation. you will provide HP with reasonably detailed information regarding any disassembly or decompilation. Termination HP may terminate your license upon notice for failure to comply with any of these License Terms. You may not copy the Software onto any bulletin board or similar system. the disclaimer of warranty and limitation of liability provisions in this license shall apply to all code distributed as part of or bundled with the Software.The Software is owned and copyrighted by HP or its third party suppliers. You may not decrypt the Software unless decryption is a necessary part of the operation of the Software. In some jurisdictions. Source Code Software may contain source code that. Source code may not be redistributed unless expressly provided for in these License Terms. 324 IBM Tivoli Workload Scheduler for Applications: User’s Guide . you must immediately destroy the Software.txt file. you must deliver the Software. You must reproduce all copyright notices in the original Software on all copies or adaptations. including any copies and related documentation. Copies and Adaptations You may only make copies or adaptations of the Software for archival purposes or when copying or adaptation is an essential step in the authorized Use of the Software. together with all copies. Upon termination. to the transferee. In addition to any terms and conditions of any third party license identified in the THIRDPARTYLICENSEREADME. No Disassembly or Decryption You may not disassemble or decompile the Software unless HP’s prior written consent is obtained. Upon transfer. Third Party Code Some third-party code embedded or bundled with the Software is licensed to you under different terms and conditions as set forth in the THIRDPARTYLICENSEREADME. Export Requirements You may not export or re-export the Software or any copy or adaptation in violation of any applicable laws or regulations. HP’s third party suppliers may protect their rights in the event of any violation of these License Terms. Upon request.txt file. is provided solely for reference purposes pursuant to the terms of this license. Transfer Your license will automatically terminate upon any transfer of the Software.

and for the sole purpose of running your Java compatible applet or application (″Program″) into which the HP-UX Runtime Environment.This software or any copy or adaptation may not be exported. computer Software documentation and technical data for commercial items are licensed under HP’s standard commercial license.S. Iraq. Licensee must promptly publish broadly. for Java provided that you distribute the HP-UX Runtime Environment. consistent with FAR 12. v * Java Platform Interface. U. Licensee may not modify the Java Platform Interface (″JPI″.211 and 12. reexported or transferred to or within countries under U. identified as classes contained within the ″java″ package or any subpackages of the ″java″ package). Serbia.S. Iran.S. Government Contracts If the Software is licensed for use in the performance of a U. This software or any copy or adaptation may not be exported.212. or to any party directly or indirectly involved in the development or production of nuclear. government prime contract or subcontract. SUPPLEMENTAL RESTRICTIONS You acknowledge the Software is not designed or intended for use in on-line control of aircraft. chemical.S. by creating additional classes within the JPI or otherwise causing the addition to or modification of the classes in the JPI. operation or maintenance of any nuclear facility. for the Java 2 Platform is incorporated. biological weapons or related missile technology programs as specified in the U. Sudan and Syria. Department of Commerce Denied Parties List or on any U.S. North Korea. You are granted a royalty-free right to reproduce and distribute the HP-UX Runtime Environment. Export Administration Regulations (15 CFR 730). v * You may make the HP-UX Runtime Environment. aircraft navigation. Treasury Department Designated Nationals exclusion list. reexported or transferred to persons or entities listed on the U. HP disclaims any express or implied warranty of fitness for such uses. air traffic. You shall not be restricted hereunder from exposing or documenting interfaces to software components that use or access the HP-UX Runtime Environment. for the Java 2 Platform accessible to application programs developed by you provided that the programs allow such access only through the Invocation Interface specified and provided that you shall not expose or document other interfaces that permit access to such HP-UX Runtime Environment. This list is subject to change. HP WARRANTY STATEMENT DURATION OF LIMITED WARRANTY: 90 DAYS Notices 325 . economic embargo including the following countries: Afghanistan (Taliban-controlled areas). Libya. for the Java 2 Platform. you agree that. commercial computer Software. FOR THE JAVA(TM) 2 PLATFORM v * License to Distribute HP-UX Runtime Environment. construction. for the Java 2 Platform.S. only as a part of. In the event that Licensee creates any Java-related API and distributes such API to others for applet or application development. ADDITIONAL SUPPLEMENTAL RESTRICTIONS FOR HP-UX RUNTIME ENVIRONMENT. for the Java 2 Platform complete and unmodified. or in the design. an accurate specification for such API for free use by all developers of Java-based software. Cuba. for the Java(tm) 2 Platform. or aircraft communications.

the end customer. either repair or replace products which prove to be defective. HP products may contain remanufactured parts equivalent to new in performance or may have been subject to incidental use. state to state. AND FITNESS FOR A PARTICULAR PURPOSE. or (f) the presence of code from HP suppliers embedded in or bundled with any HP product. Alternatively. THE ABOVE WARRANTIES ARE EXCLUSIVE AND NO OTHER WARRANTY OR CONDITION. in the case of HP Software. you will be entitled to a refund of the purchase price upon prompt delivery to HP of written notice from you confirming destruction of the HP Software. or province to province. their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of 326 IBM Tivoli Workload Scheduler for Applications: User’s Guide . so the above limitation may not apply to you. Some countries. Warranty does not apply to defects resulting from: (a) improper or inadequate maintenance or calibration. CONSEQUENTIAL (INCLUDING LOST PROFIT OR DATA). WHETHER BASED IN CONTRACT. If HP receives notice of such defects during the warranty period. due to defects in materials and workmanship when properly installed and used. INCIDENTAL. or provinces do not allow the exclusion or limitation of incidental or consequential damages. interfacing. THE REMEDIES IN THIS WARRANTY STATEMENT ARE YOUR SOLE AND EXCLUSIVE REMEDIES. accessories. so the above limitation or exclusion may not apply to you. (c) unauthorized modification or misuse. SPECIAL. you will be entitled to a refund of the purchase price upon prompt return of the product. HP will. OR OTHER DAMAGE. WHETHER WRITTEN OR ORAL. OR OTHERWISE.HP warrants to you. Some countries. Replacement products may be either new or equivalent in performance to new. adaptations. If HP is unable. Information concerning non-IBM products was obtained from the suppliers of those products. (b) software. HP will replace Software which does not execute its programming instructions due to such defects. SATISFACTORY QUALITY. parts or supplies not supplied by HP. IS EXPRESSED OR IMPLIED AND HP SPECIFICALLY DISCLAIMS ANY IMPLIED WARRANTIES OR CONDITIONS OF MERCHANTABILITY. (e) improper site preparation or maintenance. and merged portions in any form. HP warrants to you that HP Software will not fail to execute its programming instructions after the date of purchase. This warranty gives you specific legal rights and you might also have other rights that vary from country to country. states. at its option. that HP hardware. to repair or replace any product to a condition warranted. EXCEPT AS INDICATED ABOVE. IN NO EVENT WILL HP OR ITS SUPPLIERS BE LIABLE FOR LOSS OF DATA OR FOR DIRECT. HP does not warrant that the operation of HP products will be uninterrupted or error free. within a reasonable time. together with all copies. If HP receives notice of such defects during the warranty period. TO THE EXTENT ALLOWED BY LOCAL LAW. TO THE EXTENT ALLOWED BY LOCAL LAW. TORT. or provinces do not allow limitations on the duration of an implied warranty. and supplies will be free from defects in materials and workmanship after the date of purchase for the period specified above. (d) operation outside of the published environmental specifications for the product. for the period specified above. states.

PostScript and all Adobe-based trademarks are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States. Trademarks Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems. Linux is a trademark of Linus Torvalds in the United States. UNIX is a registered trademark of The Open Group in the United States and other countries. Other company. other countries. Acrobat. Microsoft.performance. Windows. Inc. in the United States. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. or both. other countries. or both. or both. and service names may be trademarks or service marks of others. Adobe. compatibility or any other claims related to non-IBM products. other countries. and the Windows logo are trademarks of Microsoft Corporation in the United States. Notices 327 . other countries. product. or both. Windows NT.

328 IBM Tivoli Workload Scheduler for Applications: User’s Guide .

RFC user SAP R/3 101 checking CA-7 job 231 for files on z/OS 234 JES job 230 Tivoli Workload Scheduler for z/OS job 233 CHECKINTERVAL. 233 © Copyright IBM Corp. SYSTSIN variable 213 CA7OPTIONS. PeopleSoft option 75 CHECKINTERVAL. 104. SYSTSIN variable 214 CA7USER. 35. 40 uninstaller. SYSTSIN variable 213 CA7SPAN(9999). z/OS option 222 bm check status 231.bin 38.4 41 example to upgrade to version 8. SAP 106 B balancing SAP R/3 workload using server groups batch processing ID PeopleSoft 78 BDC wait R/3 173 BLOCKTIME. 2008 144 329 . 105 IZ12321 249 APF authorizations. z/OS option 222 CFUSER: Oracle option 63 changing password.Index A ABAP step definition attribute 156 ABAP/4 modules SAP R/3 importing 98 access method adding with ISMP wizard 11 adding with twsappsinst 26 installing with silent installation 14 MCMAGENT options 63 PeopleSoft options 75 SAP 91 SAP common options 106 SAP global configuration options 103 SAP local configuration options 105 twsappsinst parameter 27 upgrading with ISMP wizard 33 z/OS options 221 accessibility xv activating job interception 175 adding access method with ISMP wizard 11 access method with twsappsinst 26 IBM Tivoli Workload Scheduler for Applications with twsappsinst 26 language pack with ISMP wizard 13 language pack with silent installation 17 language pack with twsappsinst 28 AI component code twsappsinst installation messages 266 APARs IY97424 177. 13 twsappsinst 27. 2003. setting 211 application server SAP R/3 112 application servers multiple. setting 211 Business Information Warehouse support SAP R/3 163 Business Warehouse components InfoPackage 163 process chain 163 SAP R/3 163 Business Warehouse InfoPackage displaying details 169 Business Warehouse InfoPackage and process chain managing 164 C CA-7 job checking 231 launching 231 managing 231 state 231 task definition. PeopleSoft 77 application state Tivoli Workload Scheduler for z/OS 233 authorization profile SAP R/3 95 Transaction PFCG 96 Transaction SU02 96 authorizations APF.sh 44 wremovsp 39 command line committing SAP event 187 defining extended agent job 57 defining extended agent workstation 50 monitoring SAP event 190 command twsappsinst example to install language pack 30 example to install Tivoli Workload Scheduler for Applications 28 example to uninstall version 8. 178 IZ02886 63 IZ03505 103.4 36 common options. z/OS option 222 code messages 263 collecting job interception 175 command SETPROG 211 setup. SYSTSIN variable 214 CDs 8 CFUSER. SYSTSIN variable 214 CA7WAIT. setting 211 RACF. z/OS 223 CA7INTERFACE. SYSTSIN variable 214 CA7SUBSYSTEM. 39. 40 vopted. 29.bin 11. SYSTSIN variable 213 CA7NAME.

to filter SAP events 192 customization procedure SAP R/3 95 customizing properties file 247. 188 job containing InfoPackage 164 job containing process chains 164 local options file 46 PeopleSoft job 83 RFC user.compatibility SAP 89 COMPLETIONCODE. common 106 SAP.0 185 committing SAP event by external request 187 mapping between definition and resolution. 129 SAP job dynamically 149 SAP R/3 job 169 SAP variant 126 defining job Oracle E-Business Suite 67 SAP 129 SAP. limitation with XBP 2. global 103 SAP. SYSTSIN variable 215 defining ABAP step attribute 156 330 IBM Tivoli Workload Scheduler for Applications: User’s Guide . dynamically 149 z/OS 222 deleting SAP job 144 SAP variant 126 dependency based on SAP event. business scenario 195 event rule based on SAP event 189 internetwork dependency based on SAP event 186. defining SAP job 149 E education See Tivoli technical training EEWTCP00 z/OS program component 212 EEWTCP02 z/OS program component 212 encrypting user password 66 PeopleSoft 77 SAP 111 end-to-end scheduling defining extended agent job 57 defining extended agent workstation 51 D data file SAP R/3 98 DEBUG. usage 111 z/OS 221 configuring SAP access method 103 SAP environment 95 SAP R/3 95 tracing utility 247 z/OS 221 z/OS gateway 210 connecting SAP 112 connection to SAP R/3 troubleshooting 261 considerations about return code mapping 240 console security 213 control file SAP R/3 98 conventions used in publications xv correction and transport files SAP R/3 98 CPUREC statement creating 51 creating CPUREC statement 51 DOMREC statement 51 event rule based on IDocs 196 event rule based on IDocs. SAP R/3 95 SAP job 115 CUSTOM keyword. R/3 249 configuration options Oracle E-Business Suite 63 PeopleSoft 75 SAP. business scenario 195 event rule based on SAP event 189 extended agent job 53 extended agent workstation 47 external command step attribute 159 external program step attribute 159 global options file 43 local options file 43 Oracle E-Business Suite job 67 PeopleSoft job 83 SAP event as internetwork dependency 186. local 105 SAP. 188 SAP job 115. defining 186. SYSTSIN variable 215 component code Tivoli Workload Scheduler for Applications component codes 264 composer program defining extended agent job 57 defining extended agent workstation 50 configuration SAP R/3 204 configuration file example. 188 based on SAP event. 248 defining (continued) event rule based on IDocs 196 event rule based on IDocs. SAP 187 dependency on jobs z/OS 225 diagnostic information z/OS job 235 displaying details Business Warehouse InfoPackage 169 Business Warehouse InfoPackage job 169 process chain job 142 SAP job 141 DOMREC statement creating 51 downloading z/OS gateway fix pack files by FTP 218 dynamic job definition parameter description SAP R/3 151 dynamic job definition syntax ABAP step definition attribute 156 external command step definition attribute 159 external program step definition attribute 159 SAP 150 dynamically defining SAP jobs 150 dynamically.

silent installation 14 TWS4APPS_installationname_accessmethod^8. collecting SAP R/3 175 job interception.4 using twsappsinst 41 to upgrade to version 8.log.opts 43 mvsopc. 33.properties 247 mvsopc. silent installation 14 tws4apps_uninst_ismp.opts 43 modifying with Option Editor mvsca7.opts 43 mvsjes.properties 247 mvsca7. silent uninstallation 40 TWS4APPS_installationname_accessmethod^8. 40 TWS4APPS_installationname_LANGS^8. activating SAP R/3 175 job interception. silent uninstallation 39 TWS4APPS_installationname_LANGS^8. setting SAP R/3 176 Oracle E-Business Suite 61 parent-child R/3 180 PeopleSoft 73 return code mapping 239 SAP R/3 90 z/OS 207 file configuration for R/3 249 language pack Software Package Blocks (. z/OS gateway.log.log. SAP 103 glossary xv GSUSER. twsappsinst 35.log. R/3 175 job interception.log.4. silent uninstallation 39 tws4appslangs. silent installation 17 tws4appssilent.log. 33 tws4apps_ismp.log. 46 Index 331 .txt.4. matching criteria 196 definition 189 monitoring SAP event 190 SAP. 40 file name return code mapping 244 filtering SAP events in security file 192 fix pack files. silent uninstallation 40 tws4appslangs_uninst. business scenario 195 based on IDocs. prerequisite to define 190 example dynamic SAP job definition 160 mcmagent.spb) 22 TWS4APPS_installationname_accessmethod^8.4. filtering events 192 SAP.opts 43 r3batch. defining with command line 50 ISPF 52 Job Scheduling Console 47 external command step definition attribute 159 external program step definition attribute 159 F feature job interception. definition 264 event rule based on IDocs 196 based on IDocs. ISMP installation 13 TWS4APPS_installationname_LANGS^8.4 using twsappsinst 36 explanation message element 265 exporting SAP R/3 factory calendars 181 extended agent job SAP 115 submitting 58 extended agent job defining with command line 57 end-to-end scheduling 57 Job Scheduling Console 53 extended agent workstation defining with end-to-end scheduling 51 extended agent workstation. ISMP installation 11. ISMP uninstallation 38 TWS4APPS_installationname_LANGS^8. ISMP installation 11.log.log 35. downloading by FTP 218 FND_TOPDIR: Oracle option 63 format messages 263 FTP downloading fix pack files.log. implementing SAP R/3 175 job interception. silent installation 17 TWS4APPS_installationname_LANGS^8.properties 247 r3batch. defining 189 SAP.4. ISMP installation 38 tws4apps_uninst_ismp.log. ISMP uninstallation 38 tws4appslangs_uninst.properties 247 mvsjes. 242 to install the language pack using twsappsinst 30 to install the product using twsappsinst 28 to uninstall version 8.opts 43 name 43 psagent. z/OS option 222 44.opts file 65 return code mapping 240.log.enigma 66 enigma program encrypting user password 111 ENV: Oracle option 63 error messages.log.log.opts 43 global options.4. silent installation 14 twsappsinst.spb) 19 psagent.4.log 17 tws4appslangs.log.log.properties 247 file (continued) product Software Package Blocks (.log.spb) 22 mcmagent.txt. setting SAP R/3 176 features job interception and parent-child. SAP R/3 175 job interception.4. 38 TWS4APPS_installationname_accessmethod^8.4. z/OS gateway installation 218 G gateway z/OS messages 270 global options file defining 43 MCMAGENT.properties 247 return code mapping 239 Software Package Blocks (.4. ISMP installation 13 tws4appslangsilent. twsappsinst 40 tws4apps_ismp.

ISMP installation 13 TWS4APPS_installationname_LANGS^8. twsappsinst 35 TWS4APPS_installationname_LANGS^8. silent installation 14 tws4appslangs.log 17 tws4appslangs.4.4 using twsappsinst 41 example to upgrade to version 8.log. silent installation 17 tws4apps_ismp. ISMP installation 11. adding with twsappsinst 26 before installing 9 example to install using twsappsinst 28 example to uninstall version 8.4.4.log.log. definition 264 inheritance r3batch definition 44 inst_dir twsappsinst parameter 27. business scenario 195 defining event rule. ISMP installation 13 twsappsinst.H help messages 265 HTWGT component code PeopleSoft access method 314 I I component code z/OS message 270 IBM Tivoli Configuration Manager Java Runtime Environment (JRE) installing 24 language pack installing 25 Option Editor installing 25 PeopleSoft installing 25 SAP R/3 installing 24 IBM Tivoli Workload Scheduler for Applications access method. 33 tws4apps_ismp.4.log.log 35 installation overview z/OS 208 installation procedures 10 installation response file tws4appslangsilent.txt.log.log. 29. ISMP installation 11. silent installation 14 TWS4APPS_installationname_accessmethod^8. 25 TWS4APPS_installationname_accessmethod^8. 40 install IBM Tivoli Workload Scheduler for Applications twsappsinst parameter 27 install language pack twsappsinst parameter 29 installation 217 CDs 8 installation (continued) twsappsinst message 266 installation CDS Tivoli Workload Scheduler for Applications CD 1 8 Tivoli Workload Scheduler for Applications CD 2 8 Tivoli Workload Scheduler for Applications CD 3 8 Tivoli Workload Scheduler for Applications CD 4 8 installation log file Tivoli Configuration Manager 24. matching criteria 196 IEFU84 exit 212 implementing job interception 175 InfoPackage managing 164 user authorization 164 InfoPackage schedule options SAP R/3 164 informational messages.4. 35.txt. silent installation 17 tws4appssilent.log. 33 TWS4APPS_installationname_accessmethod^8. SAP R/3 feature 176 interface software 62 332 IBM Tivoli Workload Scheduler for Applications: User’s Guide .log. silent installation 14 installing access method with silent installation 11 before 9 IBM Tivoli Workload Scheduler for Applications 10 IBM Tivoli Workload Scheduler for Applications with ISMP wizard 11 IBM Tivoli Workload Scheduler for Applications with launchpad 10 IBM Tivoli Workload Scheduler for Applications with silent installation 14 IBM Tivoli Workload Scheduler for Applications with Tivoli Configuration Manager 19 IBM Tivoli Workload Scheduler for Applications with Tivoli Software Distribution 19 IBM Tivoli Workload Scheduler for Applications with twsappsinst 26 Java Runtime Environment (JRE) with Tivoli Configuration Manager 24 language pack with ISMP wizard 13 language pack with silent installation 17 language pack with Tivoli Configuration Manager 25 language pack with twsappsinst 28 Option Editor with Tivoli Configuration Manager 25 PeopleSoft with Tivoli Configuration Manager 25 prerequisites 6 procedures 10 SAP R/3 with Tivoli Configuration Manager 24 z/OS gateway 208 installing ABAP modules SAP R/3 95 intercepted job return code mapping 245 interception criteria setting.4 using twsappsinst 36 installation prerequisites 6 installation procedures 10 installing 10 installing with ISMP wizard 11 installing with launchpad 10 installing with silent installation 14 installing with Tivoli Configuration Manager 19 installing with Tivoli Software Distribution 19 installing with twsappsinst 26 language pack uninstalling with ISMP wizard 38 software prerequisites 6 uninstallation procedures 37 uninstalling 36 uninstalling language pack with silent uninstallation 39 uninstalling with ISMP wizard 38 uninstalling with silent installation 40 uninstalling with Tivoli Configuration Manager 39 uninstalling with twsappsinst 40 upgrading 33 upgrading with ISMP wizard 33 upgrading with twsappsinst 35 IDoc defining event rule 196 defining event rule.

SAP R/3 feature 175 collecting.0 185 based on SAP R/3 event. defining 186. ISMP installation 11. 230 JESCMDCHR. limitation with XBP 2. silent installation 14 TWS4APPS_installationname_accessmethod^8. 25 TWS4APPS_installationname_accessmethod^8.INTERLINKSUBSYSTEM. 29.log. z/OS option 222 local options file creating with Option Editor 46 defining 43 modifying with Option Editor 44. SYSTSIN variable SYSTSIN variable INTERLINKSUBSYSTEM 215 internetwork dependency based on SAP event. SYSTSIN variable 215 JESINTERFACE.4.log. SAP R/3 feature 175 SAP R/3 feature 175 24 Index 333 . 33. SAP R/3 105 log file Tivoli Configuration Manager 24. limitation with XBP 3. SAP R/3 feature 176 Job Scheduling Console accessibility xv defining extended agent job 53 defining extended agent workstation 47 job state Oracle E-Business Suite 69 SAP 145 job status mapping PeopleSoft 85 job Tivoli Workload Scheduler creating job containing InfoPackage 164 creating job containing process chain 164 job tracking PeopleSoft 74 jobs dynamic definition SAP 150 K killing SAP job 147 L lang twsappsinst parameter 27. SYSTSIN variable 215 job assigning a server group 144 Oracle E-Business Suite job states 69 PeopleSoft 83 SAP job state 145 submitting for extended agent 58 job definition PeopleSoft 83 SAP 129 SAP.4. 46 name 43 local options. dynamically 149 job definition parameter description SAP R/3 dynamic 151 job interception activating. prerequisites 185 committing SAP event by external request 187 mapping between definition and resolution. silent uninstallation 40 J Java Runtime Environment (JRE) installing with Tivoli Configuration Manager JCL to unload the tape z/OS gateway installation 209 JES job checking 230 launching 229 managing 229 monitoring 230 state 229 task definition.log.0 185 based on SAP event. PeopleSoft option 75 LJUSER.4. SAP 187 placeholder SAP job 185 introduction Oracle E-Business Suite 61 PeopleSoft 73 Tivoli Workload Scheduler for Applications for SAP 89 z/OS 207 ISMP wizard adding a language 13 adding an access method 11 installing IBM Tivoli Workload Scheduler for Applications 11 installing language pack 13 installing with 11 uninstalling IBM Tivoli Workload Scheduler for Applications 38 uninstalling language pack 38 upgrading IBM Tivoli Workload Scheduler for Applications 33 upgrading with 33 ISPF defining extended agent workstation 52 ITWS_PSXA project PeopleSoft 78 job interception (continued) setting placeholders in template file 179 setting. 35. z/OS 223 JES operation overview 229. 38 TWS4APPS_installationname_accessmethod^8. SAP R/3 feature 175 implementing. 188 based on SAP event. 40 language adding with twsappsinst 28 twsappsinst parameter 29 language pack access method adding with twsappsinst 28 adding with ISMP wizard 13 example to install using twsappsinst 30 installing with ISMP wizard 13 installing with Tivoli Configuration Manager 25 installing with twsappsinst 28 response file 17 silent installation 17 silent installation options 18 silent uninstallation 39 uninstalling with ISMP wizard 38 launching CA-7 job 231 JES job 229 Tivoli Workload Scheduler for z/OS job 232 launchpad installing with 10 LJUSER.

log.4.log.log. ISMP installation 13 twsappsinst. twsappsinst 35.properties file 247 mvsjes.properties file 247 mvsopc. ISMP installation 38 tws4apps_uninst_ismp.log. SYSTSIN variable 215 MCMAGENT 62 MCMAGENT. silent uninstallation 40 tws4appslangs_uninst. twsappsinst 40 tws4apps_ismp.log. silent uninstallation 39 tws4appslangs. SYSTSIN variable 215 message Oracle access method 313 PeopleSoft access method 276. ISMP uninstallation 38 TWS4APPS_installationname_LANGS^8.log.log file (continued) TWS4APPS_installationname_accessmethod^8. 40 TWS4APPS_installationname_LANGS^8.opts file definition 43 mvsopc.opts file definition 43 mvsjes. ISMP installation 13 TWS4APPS_installationname_LANGS^8.4.log 17 tws4appslangs.log.properties file 247 N N component code PeopleSoft access method 276 name global options file 43 local options file 43 National Language support R/3 203 new copy re-running jobs SAP 137 number messages 263 numeric identifier message definition 264 O O component code SAP R/3 access method 278 occurrence state Tivoli Workload Scheduler for z/OS 233 old copy re-running jobs SAP 137 OPCINTERFACE. silent installation 14 tws4apps_uninst_ismp.4. SYSTSIN variable 216 OPCMSGCLASS. SYSTSIN variable 216 OPCSUBSYSTEM.4.log. ISMP uninstallation 38 tws4appslangs_uninst. SYSTSIN variable 216 operating systems.opts file definition 43 mcmagent. XBP 2.log.opts file entry syntax 63 example 65 overview 63 MCMAGENT.log. 33 tws4apps_ismp.log 35.properties file 247 MCSSTORAGE.4. ISMP installation 11. silent installation 17 TWS4APPS_installationname_LANGS^8.4.log. silent uninstallation 39 TWS4APPS_installationname_LANGS^8.opts 62 mcmagent. 314 SAP R/3 access method 278 twsappsinst installation 266 z/OS gateway 270 message help explanation 265 operator response 265 see also 265 system action 265 message number component code 264 messages code 263 error 264 format 263 messages (continued) help 265 informational 264 number 263 numeric identifier 264 severity code 264 text 265 Tivoli Workload Scheduler for Applications component codes 264 warning 264 MIN_TIME: Oracle option 64 modifying global options file 46 local options file 46 monitoring JES job 230 SAP event defined as event rule 190 SAP event defined as internetwork dependency.0 185 multiple application servers. PeopleSoft 77 mvsca7. supported 5 operation overview Tivoli Workload Scheduler for z/OS 232 operation state Tivoli Workload Scheduler for z/OS 233 operator password encrypting on PeopleSoft 77 334 IBM Tivoli Workload Scheduler for Applications: User’s Guide .log.log. 40 logon group SAP R/3 113 M managing Business Warehouse InfoPackage and process chain 164 CA-7 job 231 JES job 229 SAP extended agent job running 115 Tivoli Workload Scheduler for z/OS job 232 mapping Tivoli Workload Scheduler and SAP job states 145 mapping job status PeopleSoft 85 MAX_TIME: Oracle option 64 MAXWAIT.

operator response message element 265 OPERCMDS 213 Option Editor global options file modifying 44 installing with Tivoli Configuration Manager 25 local options file modifying 44 Simple view 45 Table view 45 Text view 45 vopted.sh command 44 option inheritance r3batch definition 44 options language pack response file 18 language pack silent installation 18 product response file 15 product silent installation 15 R/3 National Language support 203 to install Software Package Blocks 22, 23 options file 74 global 43 local 43 mcmagent.opts 63 Oracle E-Business Suite 63 PeopleSoft 75, 77 SAP 91, 103 SAP example 111 z/OS 221 ORA_APP_TOPDIR: Oracle option 64 Oracle access method message 313 Oracle E-Business Suite access method options 63 completing installation 31 defining job 67 features 61 introduction 61 job state 69 options file 63 parameters to define job 68 password encryption 66 return code mapping 241 roles and responsibilities 61 software requirements 61 task string parameters 68 ORACLE_HOME: Oracle option 64 ORACLE_SID: Oracle option 64 other z/OS jobs task definition, z/OS 225 overview IBM Tivoli Workload Scheduler for Applications 3 Oracle E-Business Suite 61 PeopleSoft 73 Tivoli Workload Scheduler for Applications for SAP 89 z/OS 207

P
P component code Oracle access method 313 parameter access_method.trace.handlers.traceFile.fileDir 248 access_method.trace.tracers.level 247 access_method.trace.traces.logging 248 properties file 247, 248 r3batch.trace.handlers.traceFile.maxFiles 248

parameter (continued) r3batch.trace.handlers.traceFile.maxFileSize 248 return code mapping 239 SAP job definition 129 SAP R/3 dynamic job definition 151 parameter for twsappsinst access method 27 inst_dir 27, 29, 35, 40 install language pack 29 lang 27, 29, 35, 40 language 29 twsuser 27, 29, 35, 40 u 26, 29, 35, 40 uninst 40 upgrade 35 v 26, 29, 35, 40 parameters for twsappsinst install IBM Tivoli Workload Scheduler for Applications parent-child SAP R/3 feature 175 parent-child feature R/3 180 password encryption 66 PASSWORD: Oracle option 64 PATH: Oracle option 64 PEERADDRESS, SYSTSIN variable 216 PeopleSoft access method options 75 batch processing ID 78 configuration tasks 75 connecting to multiple application servers 77 creating job 83 defining job 83 encrypting operator password 77 functional overview 74 installing with Tivoli Configuration Manager 25 introduction 73 ITWS_PSXA project 78 job definition 83 job status mapping 85 job tracking 74 options file 75, 77 overview 73 parameters to define job 84 return code mapping 241 roles and responsibilities 73 security 74 software requirements 73 task string parameters 84 PeopleSoft access method message 276, 314 placeholder for job interception in template file 179 SAP job 185 PORT, SYSTSIN variable 216 prerequisites installation 6 software 6 PRINTER_NAME: Oracle option 64 process chain creating Tivoli Workload Scheduler job 164 managing 164 schedule options 164 user authorization 164 process chain job displaying details 142 rerunning 138 Index

27

335

product before installing 9 installation prerequisites 6 installing 10 overview 3 silent installation 14 silent uninstallation 40 software prerequisites 6 uninstalling with ISMP wizard 38 upgrading 33 product support. locating 220 program composer 50, 57 program component z/OS 212 project ITWS_PSXA PeopleSoft 78 properties file access_method.trace.handlers.traceFile.fileDir 248 access_method.trace.tracers.level 247 customizing 247 DEBUG_MAX 247 DEBUG_MID 247 DEBUG_MIN 247 parameter 247, 248 PS_DISTSTATUS, PeopleSoft option 75 psagent 74, 77 psagent.opts file definition 43 psagent.properties file 247 PSFT_OPERATOR_ID,PeopleSoft option 75 PSFT_OPERATOR_PWD, PeopleSoft option 75 PSJOAPATH, PeopleSoft option 76 publications xv PUTLINE, SYSTSIN variable 216 pwdcrypt program encrypting user password 77

raising SAP event 145 re-running job new copy, SAP 137 old copy, SAP 137 refreshing SAP variant 126 rerunning job process chain 138 SAP 137 response file language pack options 18 product options 15 tws4appslangsilent.txt, silent installation 17 tws4appssilent.txt, silent installation 14 RETRYCOUNT, z/OS option 222 return code mapping considerations 240 example 240, 242 feature 239 file name 244 file, creating 239 intercepted job 245 Oracle E-Business Suite 241 parameter 239 PeopleSoft 241 R/3 242 syntax 239 RFC profile SAP R/3 95 RFC user SAP R/3 261 RFC user password SAP R/3 101 roles and tasks Oracle E-Business Suite 61 PeopleSoft 73 SAP 91 z/OS 208 RUNLOCATION, PeopleSoft option 76

Q
QLIMIT, SYSTSIN variable 216

S
SAP re-running jobs 137 rerunning job 137 SAP event committing by external request 187 defining as event rule 189 defining as internetwork dependency 186, 188 filtering in security file 192 monitoring 190 placeholder job for internetwork dependencies 185 prerequisite to define a rule 190 prerequisites for defining as internetwork dependency 185 r3evman command 190 r3evmon configuration file 257 raising 145 SAP job defining dynamically 149 deleting 144 displaying details 141 editing 128 example of defining dynamically 160 killing 147 placeholder 185 task string 129

R
R/3 BDC wait 173 configuration file 249 National Language support 203 parent-child feature 180 return code mapping 242 Unicode support 93 r3batch definition option inheritance 44 r3batch inheritance definition 44 r3batch.opts options file 103 SAP R/3 103 r3batch.opts file definition 43 r3batch.properties file 247 r3evman command 190 r3evmon event configuration file 257 RACF authorization, setting 211

336

IBM Tivoli Workload Scheduler for Applications: User’s Guide

SAP job (continued) variable substitution 160 verifying status 144 SAP R/3 ABAP step definition attribute 156 ABAP/4 modules, importing 98 access method 91 application server 112 authorization profile 95 Business Information Warehouse support 163 Business Warehouse components 163 calendars, exporting 181 changing password, RFC user 101 committing event by external request 187 common options 106 configuration 95 configuration options 103 configuration options usage 111 connecting 112 connection 261 control file 98 correction and transport files 98 creating job containing InfoPackage 164 creating job containing process chain 164 creating RFC user 95 customization procedure 95 data file 98 defining event as event rule 189 defining event as internetwork dependency 186, 188 defining event rule based on IDocs 196 defining job 115, 129 defining job dynamically 149 defining variant 126 deleting variant 126 dynamic job definition example 160 dynamic job definition parameter description 151 dynamic job definition syntax 150 encrypting user password 111 event defined as event rule 189 event defined as internetwork dependency 186, 188 event rule based on IDocs, business scenario 195 event rule prerequisite 190 exporting calendars, business scenario 181 exporting factory calendars 181 extended agent job 115 external command step definition attribute 159 external program step definition attribute 159 factory calendars, exporting 181 features 90 filtering events in security file 192 global options 103 IDoc record used in event rule 196 InfoPackage schedule options 164 installing ABAP modules 95 installing with Tivoli Configuration Manager 24 introduction 89 job interception 175 job interception and parent-child 175 jobs dynamic definition 150 local options 105 logon group 113 mapping between definition and resolution of internetwork dependency 187 monitoring event 190 options file 91, 103, 111 options National Language support 203 parameters to define job 131

SAP R/3 (continued) placeholder job for internetwork dependencies 185 prerequisite to define event rule 190 process chain schedule options 164 r3evman command 190 r3evmon configuration file 257 refreshing variant 126 RFC user password 101 roles and responsibilities 91 security file, filtering events 192 setting a filter in security file 192 setting interception criteria 176 setting variant 126 software requirements 89 supported code pages 204 supported configurations 204 task string 129 task string parameter 169 task string parameters 131 Transaction PFCG 96 Transaction SU02 96 updating variant 126 variable substitution 160 viewing variant 126 SAP R/3 access method message 278 SAP R/3 table criteria setting template file 177 setting using the Job Scheduling Console 176 script file 224 security 212 PeopleSoft 74 security file, filtering SAP events 192 see also message element 265 server group balancing SAP R/3 workload 144 SERVER_NAME_LIST, PeopleSoft option 76 SETPROG command 211 setting job interception 176 job interception using interception criteria and template files 176 SAP R/3 table criteria using the Job Scheduling Console 176 SAP variant 126 template file 177 setup programs 8 setup.bin command for installation 11, 13 severity code message definition 264 silent installation adding a language 17 IBM Tivoli Workload Scheduler for Applications 14 IBM Tivoli Workload Scheduler for Applications options 15 language pack 17 language pack options 18 silent uninstallation language pack 39 Tivoli Workload Scheduler for Applications 40 software components 62 Software Package Blocks options to install the language pack 23 Index

337

Software Package Blocks (continued) options to install the product 22 Software Package Blocks (.spb) to install IBM Tivoli Workload Scheduler for Applications 19 to install language pack 22 software prerequisites Tivoli Workload Scheduler for Applications 6 software requirements Oracle E-Business Suite 61 PeopleSoft 73 SAP 89 z/OS 207 start up 213 state CA-7 job 231 JES job 229 SAP job 145 status mapping PeopleSoft job 85 structure installation CD 8 submitting extended agent job 58 SUBSYS, SYSTSIN variable 216 support, product, locating 220 supported code pages, SAP R/3 204 configuration, SAP R/3 204 Internet Protocol version 6 9 IPv6 9 operating system 5 SVCDUMP, SYSTSIN variable 216 syntax defining SAP jobs dynamically 150 mcmagent.opts file 63 return code mapping 239 task definition, z/OS 223 twsappsinst 27, 29, 35, 40 syntax diagrams, how to read xvi system action message element 265 SYSTSIN variable CA7INTERFACE 213 CA7NAME 213 CA7OPTIONS 213 CA7SPAN(9999) 214 CA7SUBSYSTEM 214 CA7USER 214 CA7WAIT 214 COMPLETIONCODE 215 DEBUG 215 JESCMDCHR 215 JESINTERFACE 215 MAXWAIT 215 MCSSTORAGE 215 OPCINTERFACE 216 OPCMSGCLASS 216 OPCSUBSYSTEM 216 PEERADDRESS 216 PORT 216 PUTLINE 216 QLIMIT 216 SUBSYS 216 SVCDUMP 216 TCPIPSTACK 216 TCPNAME 217

SYSTSIN variable (continued) TERMINATOR 217 WTP 217 ZOSV1R2 217

T
table criteria SAP R/3 setting template file 177 setting using the Tivoli Job Scheduling Console 176 tape unloading files, z/OS gateway installation 209 task definition syntax CA-7 job, z/OS 223 JES job, z/OS 223 other z/OS jobs 225 Tivoli Workload Scheduler for z/OS job 224 z/OS 223 task string parameters Oracle E-Business Suite job 68 PeopleSoft job 84 SAP job 131 SAP R/3 job 129, 169 TCP/IP: stack 216 TCP/IP: version 207 TCPIPSTACK, SYSTSIN variable 216 TCPNAME, SYSTSIN variable 217 technical overview z/OS 229 technical training See Tivoli technical training template file creating 177 description 177 setting placeholders for job interception 179 TERMINATOR, SYSTSIN variable 217 text messages 265 THREE_TIER_DB: Oracle option 64 timing consideration z/OS job 234 Tivoli Configuration Manager installing IBM Tivoli Workload Scheduler for Applications 19 Java Runtime Environment (JRE) installing 24 language pack installing 25 log file 24, 25 Option Editor installing 25 PeopleSoft installing 25 SAP R/3 installing 24 uninstalling IBM Tivoli Workload Scheduler for Applications 39 Tivoli Dynamic Workload Console accessibility xv Tivoli Message Standard 263 Tivoli Software Distribution installing IBM Tivoli Workload Scheduler for Applications 19 Tivoli technical training xvi Tivoli Workload Scheduler for Applications software prerequisites 6 Tivoli Workload Scheduler for z/OS application state 233 occurrence state 233 operation overview 232 operation state 233

338

IBM Tivoli Workload Scheduler for Applications: User’s Guide

Tivoli Workload Scheduler for z/OS job checking 233 launching 232 managing 232 task definition, z/OS 224 trace file trace-mcmagent.log 248 trace-mvsca7.log 248 trace-mvsjes.log 248 trace-mvsopc.log 248 trace-psagent.log 248 trace-r3batch.log 248 tracing utility configuring 247 tracking PeopleSoft job 74 training See also Tivoli technical training technical xvi Transaction PFCG SAP R/3 96 Transaction SU02 SAP R/3 96 troubleshooting 251 EEO0778E 261 extended agent job log 260 PeopleSoft, job submission fails 260 PeopleSoft, local options file rights 260 extendend agent Oracle, job submission fails 260 installing ISMP displays error on Solaris 251 ISMP on HP-UX 11.0 251 ISMP on HP-UX version 11i 251 language pack displays Java exception 252 language pack remains in pending state 252 mvsjes, S047 abend 260 r3batch modifying job step error 259 monitoring IDoc events 258, 259 monitoring SAP events 257, 258 scheduling SAP jobs 259 r3evmon monitoring events increases memory consumption restarting process of subchain 260 SAP R/3 connection 261 error defining internetwork dependency 261 uninstalling 253, 254 ISMP 256 some packages remains in catalog 255 z/OS 235 TWS_MAX_WAIT_TIME, PeopleSoft option 76 TWS_MIN_WAIT_TIME, PeopleSoft option 76 TWS_RETRY, PeopleSoft option 76 TWS4APPS_installationname_accessmethod^8.4.log log file 40 log file for ISMP installation 38 log file for ISMP installation wizard 33 log file for silent installation 14 log file for silent uninstallation 40 log file using twsappsinst 35 log file, ISMP installation 11 TWS4APPS_installationname_LANGS^8.4.log log file for ISMP installation wizard 13 log file for ISMP uninstallation 38

258

TWS4APPS_installationname_LANGS^8.4.log (continued) log file for silent installation 17 log file for silent uninstallation 39 log file for twsappsinst 40 tws4apps_ismp.log log file, ISMP installation 11, 33 log file, silent installation 14 tws4apps_uninst_ismp.log log file for ISMP installation 38 log file for silent uninstallation 40 tws4appslangs_uninst.log log file for silent uninstallation 39 log file ISMP uninstallation 38 tws4appslangs.log log file 17 log file, ISMP installation 13 tws4appslangsilent.txt installation response file for language pack 17 tws4appssilent.txt installation response file for product 14 TWSA_SCHED_METH, PeopleSoft option 76 twsappsinst adding a language 28 adding an IBM Tivoli Workload Scheduler for Applications access method 26 example to install language pack 30 example to install Tivoli Workload Scheduler for Applications 28 example to uninstall version 8.4 41 example to upgrade to version 8.4 36 installing IBM Tivoli Workload Scheduler for Applications 26 installing language pack 28 syntax 27, 29, 35, 40 uninstalling IBM Tivoli Workload Scheduler for Applications 40 upgrading IBM Tivoli Workload Scheduler for Applications 35 usage parameter 26, 29, 35, 40 twsappsinst parameter install language pack 29 lang 29, 35, 40 language 29 twsappsinst 29, 35, 40 twsuser 29, 35, 40 u 26, 29, 35, 40 uninst 40 upgrade 35 v 26, 29, 35, 40 twsappsinst parameters access method 27 install IBM Tivoli Workload Scheduler for Applications 27 lang 27 twsappsinst 27 twsuser 27 twsappsinst.log log file for twsappsinst 40 log file using twsappsinst 35 TWSMETH_CP: Oracle option 64 TWSMETH_LANG: Oracle option 64 twsuser twsappsinst parameter 27, 29, 35, 40 TWSXA_CP: Oracle option 65 TWSXA_INLINE_CI, PeopleSoft option 76

Index

339

U
u twsappsinst parameter 26, 29, 35, 40 Unicode support R/3 93 uninst twsappsinst parameter 40 uninstallation log file TWS4APPS_installationname_accessmethod^8.4.log, ISMP installation 38 TWS4APPS_installationname_accessmethod^8.4.log, silent uninstallation 40 TWS4APPS_installationname_accessmethod^8.4.log, twsappsinst 40 TWS4APPS_installationname_LANGS^8.4.log, ISMP uninstallation 38 TWS4APPS_installationname_LANGS^8.4.log, silent uninstallation 39 TWS4APPS_installationname_LANGS^8.4.log, twsappsinst 40 tws4apps_uninst_ismp.log, ISMP installation 38 tws4apps_uninst_ismp.log, silent uninstallation 40 tws4appslangs_uninst.log, ISMP uninstallation 38 tws4appslangs_uninst.log, silent uninstallation 39 twsappsinst.log 40 uninstallation procedures 37 uninstaller.bin command for uninstallation 38, 39, 40 uninstalling IBM Tivoli Workload Scheduler for Applications with ISMP wizard 38 IBM Tivoli Workload Scheduler for Applications with silent installation 40 IBM Tivoli Workload Scheduler for Applications with Tivoli Configuration Manager 39 IBM Tivoli Workload Scheduler for Applications with twsappsinst 40 language pack with ISMP wizard 38 language pack with silent uninstallation 39 procedures 37 Tivoli Workload Scheduler for Applications 36 z/OS gateway 211 unloading files from the CD, z/OS gateway installation 208 files from the tape, z/OS gateway installation 209 updating SAP variant 126 upgrade twsappsinst parameter 35 upgrading access method with ISMP wizard 33 IBM Tivoli Workload Scheduler for Applications 33 IBM Tivoli Workload Scheduler for Applications with ISMP wizard 33 IBM Tivoli Workload Scheduler for Applications with twsappsinst 35 usage twsappsinst 27, 29, 35, 40 user authorizations Business Warehouse InfoPackage 164 Business Warehouse process chain 164 user password encrypting on PeopleSoft 77 encrypting on SAP 111 USERID: Oracle option 65 UTF8CMDLINE: Oracle option 65

V
v twsappsinst parameter 26, 29, 35, 40 variable substitution SAP R/3 160 variant SAP R/3 defining 126 deleting 126 refreshing 126 setting 126 updating 126 viewing 126 verifying status SAP job 144 version supported, operating system 5 viewing SAP variant 126 vopted.sh command 44

W
warning messages, definition 264 wizard ISMP adding a language 13 adding an access method 11 installing IBM Tivoli Workload Scheduler for Applications 11 installing language pack 13 uninstalling IBM Tivoli Workload Scheduler for Applications 38 uninstalling language pack 38 upgrading IBM Tivoli Workload Scheduler for Applications 33 workload, balancing SAP R/3 144 workstation for extended agent, defining with command line 50 ISPF 52 Job Scheduling Console 47 WORKSTATION NAME_MCMAGENT.opts 62 wremovsp command 39 WTP, SYSTSIN variable 217

Z
z/OS access method options 221 configuring 221 configuring gateway 210 defining job 222 dependency on jobs 225 features 207 installing 208 installing gateway 208 introduction 207 JCL to unload the tape 209 program component 212 roles and responsibilities 208 setting APF authorizations 211 setting RACF authorizations 211 software requirements 207 task definition syntax 223, 224, 225 technical overview 229 troubleshooting 235 uninstalling gateway 211

340

IBM Tivoli Workload Scheduler for Applications: User’s Guide

z/OS gateway downloading fix pack files by FTP messages 270 unloading files from CD 208 unloading files from tape 209 z/OS job diagnostic information 235 timing consideration 234 z/OS program component EEWTCP00 212 EEWTCP02 212 zOS job dependencies 225 ZOSV1R2, SYSTSIN variable 217

218

Index

341

342 IBM Tivoli Workload Scheduler for Applications: User’s Guide .

.

Printed in USA SC32-1278-05 .

4 (Revised June 2008) User’s Guide .Spine information: IBM Tivoli Workload Scheduler for Applications Version 8.

Sign up to vote on this title
UsefulNot useful