The extended agent could not be initialized.

See message.

R3batch stops.

Check that the connections between the SAP system and the local host are correct. Check also that the local option 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 IBM Workload Scheduler home directory: "TWS_home_directory" .

TWS_home_directory is the directory where IBM Workload Scheduler is installed.

R3batch stops.

Check that the directory indicated in the message has the correct name. Check that the directory on the hard disk exists, and has read permission for the user running r3batch . When you have found and corrected the error, rerun r3batch .

An internal I/O error occurred reading the following method options file: "method_options_file" .

method_options_file is the file that contains the R/3 method options.

R3batch stops.

Check that there is sufficient disk space on the file system where the method options file is located. Check that the file has read permission for the user that is running r3batch . Check that 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" .

An internal error has occurred. The following unknown BAPI return code: "BAPI_return_code" ( "BAPI_message" ) was received while calling the following function: "function" .

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.

function is one of the functions used by the program.

R3batch stops.

This is an internal error. 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.

ABAP_module is a required module that has not been installed.

R3batch stops.

Use the User's Guide to determine the ABAP modules required. Contact your SAP system administrator to have them installed.

See The User's Guide for details of 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" .

object is the object that the function ItCreate was trying to perform on.

module is the module being processed.

R3batch stops.

This is an internal error. Contact IBM Software Support for assistance.

EEWO0103E

R3batch has run out of memory (the function RfcAllocParamSpace has failed in the following module: "module" ).

module is the module being performed.

R3batch stops.

Check the following:

Verify if the workstation has enough memory available. Information about the memory requirements of IBM Workload Scheduler for Applications is provided in the Release Notes . 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 .
If the workstation memory is adequate, try closing all the applications that you do not need, and then rerun r3batch .
If the problem persists, reboot the workstation, and then rerun r3batch .
If the problem persists, contact IBM Software Support for assistance.

See The Release Notes for details of memory requirements.

An internal error has occurred. The RFC was not initialized when calling the following function: "function_name" .

function_name is the name of the function being performed.

R3batch stops.

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" .

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.

R3batch continues, but the job you are trying to run is not processed.

Consult your local SAP or IBM Workload Scheduler administrator to determine if the user ID that you have used is the correct one, and if this user should have 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" .

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.

R3batch continues, but the job you are trying to run is not processed. The batch log ( r3batch_trace.log ) is produced giving more details of the steps that occurred before the job creation failed.

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" .

exception_number is the error number.

function_module_name is the name of the function module being performed when the error occurred.

R3batch stops.

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.

database_name is the name of the database that is not correct.

R3batch stops.

This is an internal error. Retry the operation (the error may be transient). If the problem persists, contact IBM Software Support for assistance.

EEWO0115E

An internal error has occurred. The following counter ID is not valid: "counter_ID" .

counter_ID is the counter ID that is not valid.

R3batch stops.

This is an internal error. Retry the operation (the error may 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" .

Another process has locked the joblog file.

joblog_file_name is the name of the file that is locked.

R3batch continues.

Take these steps.

Use the operating system facilities to determine which process has locked the joblog file.
Wait until the process that has locked the file stops.
If the process does not stop in an acceptable time frame, consider forcing the other process 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.

See message.

R3batch stops.

Check the following:

Verify if the workstation has enough memory available. Information about the memory requirements of IBM Workload Scheduler for Applications is provided in the Release Notes . 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 .
If the workstation memory is adequate, try closing all the applications that you do not need, and then rerun r3batch .
If the problem persists, reboot the workstation, and then rerun r3batch .
If the problem persists, contact IBM Software Support for assistance.

See The Release Notes for details of memory requirements.

EEWO0118E

R3batch has failed because it could not create and start a job instance.

See message.

The job instance is not created.

Check the r3batch log file for the reason for the error and try and resolve it. If you have corrected the error, rerun r3batch .

If the problem persists, contact IBM Software Support for assistance.

EEWO0119E

An internal error has occurred. The cleanup task could not delete the following job: "job_name" . The job ID is: "job_ID" .

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.

R3batch stops.

This is an internal error. Retry the operation (the error may be transient). If the problem persists, contact IBM Software Support for assistance.

EEWO0120E

The job you are trying to monitor does not exists. The job number and name are as follows: "job_number" : "job_name" .

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.

The program might stop.

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 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: "attempts" .

attempts is the number of times that r3batch tried to start BDCWAIT.

The program might stop.

Check that the R/3 system is running. Check the job status. If you find an error and correct it, rerun r3batch .

EEWO0122E

An internal error has occurred. R3batch could not scan the R/3 joblog for BDCWAIT messages.

See message.

The batch job stops.

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.

See message.

The batch job stops.

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" .

SAP_system_name is the name of the SAP R/3 system that is not running.

R3batch stops.

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.

See message.

R3batch continues, but the job being processed is ignored.

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" .

mapping_file_name is the name of the return code mapping file that cannot be read.

The job processing continues, but the return code mapping is not performed.

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 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" .

An internal error has occurred: GI and PI require task specification.

See message.

R3batch stops.

This is an internal error. Contact IBM Software Support for assistance.

EEWO0167E

An error occurred when r3batch was started. One or more internal parameters is missing from the following task: "task_name" . It needs the following parameter: "parameter_name" .

task_name is the name of the task being run.

parameter_name is the name of the missing internal parameter.

R3batch stops.

This is an internal error. Contact IBM Software Support for assistance.

EEWO0171E

You have specified a step to run an ABAP or an external program, but the step number ( "step_number" ) cannot be determined.

step_number is the number of the step that is not in the correct format to be determined.

R3batch stops.

See the SAP system administrator.

EEWO0172E

You have defined a job as a series of steps, but one of the steps has a number which is out of range: "step_number" .

step_number is the number of the step that is not in the correct range.

R3batch stops.

See the SAP system administrator and determine the correct step number.

EEWO0173E

You have specified a step to run the following ABAP: "ABAP_name" which requires one or more variants, but no variants have been specified.

ABAP_name is the name of the ABAP module which is specified to be run.

R3batch stops.

Determine the correct variants to use from the SAP system administrator. Change the job specification to add the variant or variants. If a variant is missing it must be created. There are two alternative ways to create a variant:

Follow the instructions in the User's Guide to create a variant using the Job Scheduling Console
Ask the SAP system administrator to create the variant using the SAP GUI

EEWO0174E

An internal error occurred while accessing the variant selection table J1O1VARSO for the following report: "report_name" and variant: "variant_name" .

report_name the name of the report that r3batch was trying to create.

variant_name the name of the variant that was being processed when the error occurred.

R3batch continues, but the job is not processed.

Rerun r3batch (the problem may have been transient). If the problem persists, contact IBM Software Support for assistance.

EEWO0175E

An internal error occurred while accessing the variant counter table J1O1VARCO for the following report: "report_name" and variant: "variant_name" .

report_name the name of the report that r3batch was trying to create.

variant_name the name of the variant that was being processed when the error occurred.

R3batch continues, but the job is not processed.

Rerun r3batch (the problem may have been transient). If the problem persists, contact IBM Software Support for assistance.

EEWO0176E

There is an error in the job information that has prevented the r3batch program from creating the following step: "step_number" .

You are trying to add a step but an error in the step data prevents it from being added.

step_number is the number of the step you are trying to add.

The step is not added.

Verify the correctness of the information in the step, such as the name of the job, the user name, and the variant details, correct any errors and retry the add step action. If the problem continues, also check the connectivity with the SAP system. If you find the problem and correct it, rerun r3batch .

EEWO0177E

The following step is not valid, and cannot be performed: "step_number" .

step_number is the number of the step that is not valid.

R3batch continues, but the step is not performed.

Verify the correctness of the information in the step. Verify the name of the job, the user name, and the variant details . If the problem continues, also check the connectivity with the SAP system. If you find the problem and correct it, rerun r3batch .

EEWO0178E

An internal error has occurred. The following incorrect step type: "step_type" has been supplied for step: "step_number" .

step_type is the non-valid type that has been supplied by the GUI for the step.

step_number is the number of the step being processed.

R3batch continues, but the step is not performed.

This is an internal error. Contact IBM Software Support for assistance.

EEWO0179E

An internal error occurred because a variant name counter field was missing for the following report: "report_name" and variant: "variant_name" .

report_name the name of the report that r3batch was trying to create.

variant_name the name of the variant that was being processed when the error occurred.

R3batch stops.

This is an internal error. Retry the operation (the error may be transient). If the problem persists, contact IBM Software Support for assistance.

EEWO0180E

During the preparation of the following report: "report_name" , 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.

report_name the name of the report that r3batch was trying to create.

original_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 trying to create - also the name of the existing variant.

R3batch stops.

Take either of these steps:

Change the name of the existing variant with which the copy name has clashed.
Change the name of the original variant which was being copied (the copy name is based on the original, so any change in the original name will create a copy with a different name)

Rerun r3batch .

EEWO0181E

R3batch could not obtain the semaphore identified in the global options file (required to control access to shared resources).

See message.

R3batch continues, but the variant is not processed.

Contact the SAP system administrator to determine why the semaphore is missing. If you find the problem and correct it, rerun r3batch .

See See the User's Guide for more information about variants and semaphores.

EEWO0182E

R3batch could not create the following report: "report_name" because the variant: "variant_name" has one or more incorrect values (placeholders or counters).

report_name the name of the report that r3batch was trying to create.

variant_name the name of the variant that was being processed when the error occurred.

R3batch continues, but the report is not created.

Contact the SAP system administrator to determine why the values are incorrect, and to correct them. If you find the problem and correct it, rerun r3batch .

EEWO0183E

An internal error has occurred while calling the function j_1O1_variant_maintain_sel_tbl , because the parameters to the call were not valid.

See message.

R3batch stops.

This is an internal error. Retry the operation (the error may be transient). If the problem persists, contact IBM Software Support for assistance.

EEWO0184E

A variant required for this job is locked by another application.

See message.

R3batch stops.

User the operating system tools to determine which application has locked the variant. Decide whether you should stop that application or wait for it to stop or unlock the variant of its own accord. If you find the problem and correct it, rerun r3batch .

EEWO0185E

The properties of the variant required for this job indicate that is protected by another user.

See message.

R3batch continues, but the processing of the job stops.

Contact the user that has protected the variant and request that the protection is removed so that you can use it for your job. If you find the problem and correct it, rerun r3batch .

EEWO0186E

A variant required for this job no longer exists.

See message.

R3batch stops.

Check in the job definition that the variant is correctly specified. If it is not, correct the job definition and rerun r3batch . If it is correctly specified, the variant is genuinely missing and must be created. There are two alternative ways to create a variant:

Follow the instructions in the User's Guide to create a variant using the Job Scheduling Console
Ask the SAP system administrator to create the variant using the SAP GUI

When the job definition is pointing to an existing variant, rerun r3batch .

EEWO0187E

A variant required for this job is obsolete and cannot be used.

See message.

R3batch stops.

Check in the job definition that the variant is correctly specified. If it is not, correct the job definition and rerun r3batch . If it is correctly specified, change the variant specification to refer to a variant that is not obsolete or create a new variant. There are two alternative ways to create a variant:

Follow the instructions in the User's Guide to create a variant using the Job Scheduling Console
Ask the SAP system administrator to create the variant using the SAP GUI

Check the job option syntax in the User's Guide . Correct the syntax and rerun r3batch .

See The User's Guide for details of the job options syntax.

EEWO0263E

A syntax error has been found with the job options. More job options were submitted than the maximum allowed: "maximum_job_options" .

maximum_job_options is the maximum number of job options that you can define.

R3batch stops.

Check the job option syntax in the User's Guide . Reduce the number of job options for this job, for example, by dividing it into two jobs, each of which would have a reduced number of job options. Correct the syntax and rerun r3batch .

See The User's Guide for details of the job options syntax.

EEWO0264E

A syntax error has been found with the job options. The following job option requires a value after keyword: "job_option" .

job_option is the option that requires a value.

R3batch stops.

Check the job option syntax in the User's Guide . Correct the syntax by adding the value to the indicated option and rerun r3batch .

See The User's Guide for details of the job options syntax.

EEWO0265E

A syntax error has been found with the job options. The following option sequence is not correct: "job_option1" "job_option2" . The "job_option3" option requires a value, which cannot begin with a hyphen (minus sign).

There is a problem with the syntax of the job options. The above message might exactly explain the problem. However, it might be that an error of syntax has allowed the program to interpret a value as a job option.

job_option1 , is the option that must not precede job_option2 .

job_option3 requires a value, which cannot commence with a hyphen.

R3batch stops.

Check the full job option syntax in the User's Guide , not only for the indicated job options, but also for all others. Correct the syntax and rerun r3batch .

See The User's Guide for details of the job options syntax.

EEWO0266E

A syntax error has been found with the job options. The following option could not be recognized: "unrecognizable_job_option" .

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, but that does not match a valid job option.

R3batch stops.

Check the job option syntax in the User's Guide . Correct the syntax and rerun r3batch .

See The User's Guide for details of the job options syntax.

EEWO0267E

A syntax error has been found with the job options. The following job ID is not valid: "job_ID" .

job_ID is the job ID that is not valid.

R3batch stops.

Check the job option syntax in the User's Guide . Correct the job ID and rerun r3batch .

See The User's Guide for details of the job options syntax.

EEWO0268E

An internal error has occurred. The recovery process has started with the following non-valid parameter: "parameter" .

parameter is the non-valid parameter of the job that cannot be processed.

The recovery process does not continue. The job recovery is not performed.

This is an internal error. Contact IBM Software Support for assistance.

R3batch failed to connect to the R/3 system on the following host: "host_name" , after the following number of attempts: "attempts" .

host_name is the workstation where r3batch cannot connect to the R/3 system.

attempts is the number of times that r3batch has tried.

R3batch stops.

The problem might have one of two causes:

Check that the client number, R/3 user ID and password in the options file are correct
Check with the SAP system administrator that the XA for SAP function modules (the programs for the IBM Workload Scheduler Xagent feature) have been installed and activated on the host

If you have resolved the problem, rerun r3batch .

EEWO0384E

R3batch failed to establish a connection to the following R/3 instance: "R/3_instance" on the following host: "host_name" , after the following number of attempts: "attempts" .

R/3_instance identifies the R/3 instance that could not be connected to.

host_name is the workstation where r3batch cannot connect to the R/3 system.

attempts is the number of times that r3batch has tried.

R3batch stops.

The problem might have one of two causes:

Check that the client number, R/3 user ID and password in the options file are correct
Check with the SAP system administrator that the indicated R/3 instance is running on the host

If you have resolved the problem, rerun r3batch .

EEWO0420E

An internal error has occurred. R3batch either could not open or could not copy the R/3 job.

See message.

The program might stop.

The problem might be one of several:

Check that there is available disk space in the file set where IBM Workload Scheduler for Applications is installed. If there is not sufficient space, create more space and rerun r3batch .
Check that the user running r3batch has read and write permissions in the IBM Workload Scheduler for Applications install directory and its subdirectories. If there is a problem with permissions, correct it and rerun r3batch .
Check that the operating system has not reached the maximum number of files that it can open at the same time. If this is the problem, either use the operating system facilities to allow more file descriptors, wait for other applications that are using files to close them, or stop other applications that are using files. Rerun r3batch .
If the problem is not one of these, contact IBM Software Support for assistance.

See The User's Guide for more details about the options in the global and local options files.

EEWO0450E

The year number "year_number" of keyword "keyword" is not valid: . Year numbers must be 4 digit numeric values.

The year_from or year_to keyword was set to a value that is not valid. The value for the year must be specified in the format yyyy.

R3batch stops.

Change the value of the indicated keyword to be a four-digit number and rerun the command.

See The User's Guide for more details about the values allowed for the indicated keywords.

EEWO0451E

R3batch could not create the file or directory: "filename". Either the filename is not valid or access rights are missing.

Either the specified filename is not in the correct format or r3batch does not have the access rights to create the file or directory.

R3batch stops.

Do one of the following and rerun the command:

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.
Change the path of the indicated filename to a location where r3batch is authorized to create and edit files.

See The User's Guide for more details about the values allowed for the indicated keywords.

EEWO0452E

The supplied year range is not valid. The from year:"year_from" is greater than the to year:"year_to".

The date set for the year_from keyword is later than the value set for the year_to keyword.

R3batch stops.

Correct the year range so that the starting year is earlier than the ending year.

See The User's Guide for more details about the values allowed for the indicated keywords.

EEWO0453E

R3batch could not create the following directory: "directory". Either the directory name is not valid or r3batch does not have access rights required to create the file or directory.

See message.

R3batch stops.

Do one of the following and rerun the command:

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.
Change the path to a location where r3batch is authorized to create and edit files.

See The User's Guide for more details about the values allowed for the indicated keywords.

EEWO0460E

The SAP system does not have the correct XBP interface version. The XBP interface version must be 2.0 or later.

See message.

R3batch stops.

Choose a SAP system with the correct XBP interface version.

EEWO0461E

An internal error occurred during an external dependency operation.

See message.

R3batch stops.

Retry the operation. If the problem persists, contact IBM Software Support for assistance.

EEWO0462E

R3batch could not commit the external dependency on the SAP system. Event name: "event_name". Event parameter: "event_parameter".

The request to commit the external dependency, identified by the SAP event name and parameter indicated in the message, failed on the target SAP system.

R3batch stops.

Do one of the following:

Check the log file for preceeding error messages.
Contact your system administrator to validate the XBP event history.
Retry the operation. If the problem persists, contact IBM Software Support for assistance.

Supply a job name and continue.

EEWO0551E

Either no matching job could be found, or a job is found with steps but no start time, or the job that is found has a released status. The following identify the job: User: "user_name" Job: "job_name" .

user_name identifies the user for which the job cannot be run.

job_name identifies the job that cannot be run.

The program waits for you to correct the input or exit.

Check whether the R/3 job name and user name match the IBM Workload Scheduler for Applications job definition for this job. Check if the R/3 transaction SM37 shows the job in the released state; as SAP jobs in the released state cannot be run.

Correct the problem and continue.

EEWO0552E

The R/3 job scheduling system has found an error for the following job: User: "user_name" Job: "job_name" .

user_name identifies the user for which the job cannot be run.

job_name identifies the job that cannot be run.

R3batch stops.

Contact the R/3 system administrator to check the R/3 syslog, which should contain more details of the error. Also check the correctness of the indicated user name and job name.

Correct the problem and rerun r3batch .

EEWO0553E

The XBP interface reports that the external user is missing.

See message.

R3batch stops.

This is an internal error. Retry the operation (the error may be transient). If the problem persists, contact IBM Software Support for assistance.

EEWO0554E

R3batch has stopped because the R/3 XMI logging mechanism has returned an error. There might be a connection problem.

See message.

R3batch stops.

Check that the connection with the R/3 system is working correctly. If it is, or if the error persists, contact IBM Software Support for assistance.

EEWO0555E

R3batch could not invoke the R/3 XMI interface. There might be a connection problem.

See message.

R3batch stops.

This is an internal error. Contact IBM Software Support for assistance.

EEWO0558E

The XBP interface has returned the following error: Cannot select the following job: "job_name" with the following job ID: "job_ID" .

job_name is the name of the job that cannot be selected.

job_ID is the ID of the job that cannot be selected.

R3batch stops.

Check that the job name and ID are correctly identified in the job options. Ensure they match with the R/3 job. Correct any error you find and rerun r3batch , otherwise contact IBM Software Support for assistance.

EEWO0559E

The XBP interface has returned the following error: Cannot process the job because the job name or job ID is missing. .

See message.

R3batch stops.

Check that the job name and ID are correctly identified in the job options. Ensure they match with the R/3 job. Correct any error you find and rerun r3batch , otherwise contact IBM Software Support for assistance.

EEWO0561E

The XBP interface has returned the following error: Cannot delete the following job: . Job name: "job_name" Job ID: "job_ID" .

job_name is the name of the job that cannot be deleted.

job_ID is the ID of the job that cannot be deleted.

R3batch stops.

Check that the job name and ID are correctly identified in the job options. Ensure they match with the R/3 job. Contact the R/3 system administrator to check the R/3 syslog, which should contain more details of the error. Check that the user has the correct permission to run the job.

Correct any error you find and rerun r3batch , otherwise contact IBM Software Support for assistance.

EEWO0562E

The XBP interface has returned the following error: The ABAP program name is missing.

See message.

R3batch stops.

Check the ABAP program name in the job definition.

Correct any error you find and rerun r3batch , otherwise contact IBM Software Support for assistance.

EEWO0563E

The XBP interface has returned the following error: The archive information cannot be found.

See message.

R3batch stops.

This is an internal error. Contact IBM Software Support for assistance.

EEWO0564E

The XBP interface has returned the following error: The supplied print parameters are not valid.

See message.

R3batch stops.

Check the print parameters in the job definition (see the User's Guide for details.

Correct any error you find and rerun r3batch , otherwise contact IBM Software Support for assistance.

See The User's Guide for details of the print parameters.

EEWO0565E

The XBP interface has returned the following error: The supplied archive parameters are not valid.

See message.

R3batch stops.

This is an internal error. Contact IBM Software Support for assistance.

EEWO0566E

The target host name is required for external step definition.

You have defined a job with an external step, but the target host name is missing in the step definition.

The program waits for you to correct the input or exit.

Specify the host name or exit.

EEWO0568E

The following job cannot be started immediately : Job name: "job_name" Job ID: "job_ID" .

The indicated job has been defined to run immediately , but the job has dependencies that cannot be resolved immediately.

job_name is the name of the job that cannot be run immediately.

job_ID is the ID of the job that cannot be immediately.

R3batch stops.

Check that the job definition settings of an immediate run time and dependencies is correct. If not, correct the job definition and rerun r3batch .

If the settings are correct, decide whether you want to wait for the dependencies to be resolved or delete them to let the job go ahead. Take the appropriate action and rerun r3batch .

EEWO0569E

An internal error has occurred. The step count is not correct.

See message.

R3batch stops.

This is an internal error. Retry the operation (the error may be transient). If the problem persists, contact IBM Software Support for assistance.

EEWO0570E

The following job does not have steps: Job name: "job_name" Job ID: "job_ID" .

The following InfoPackage does not exist: "infopackage_name" .

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" .

user_name identifies the user that does not have the appropriate R/3 user authorization for the indicated purposes.

R3batch stops.

Contact the SAP system administrator to determine if it is possible to change the RFC user's permissions on the R/3 system, or whether you should run this job as a different R/3 RFC user. In the latter case, modify the job definitions to use the different RFC user.

Then rerun r3batch .

The program cannot read the joblog.

See message.

R3batch stops.

The problem could have various causes:

Check that the user running the job has read permission for the joblog. Give the user this permission if it does not.
Check that there is sufficient disk space in the file system of the joblog. Make more space available if it does not.
Check that the operating system has not reached its maximum limit of open files. If it has, either extend this limit, wait for other jobs that are using files to close, or stop other jobs that are using files.

Rerun r3batch .

If none of these actions resolves the problem, contact IBM Software Support for assistance.

EEWO0705E

The client number is missing in both the local and global options files.

The job ID is missing.

Check the syntax of the date expression in the job definition. If you find an error, correct it and continue. If you do not find an error in the expression, this is an internal error. Retry the operation (the error may be transient). If the problem persists, contact IBM Software Support for assistance.

See The User's Guide for details of the syntax of the date expression.

EEWO0804E

An internal error has occurred. The job last run time feature is not yet supported.

See message.

R3batch stops.

This is an internal error. Retry the operation (the error may be transient). If the problem persists, contact IBM Software Support for assistance.

The following trace level in the job definition is not valid: "trace_level" . The default value of 3 (DEBUG_MAX) is used instead.

The -tracelvl option in the job definition has a non-valid value.

R3batch continues, using the default trace level: DEBUG_MAX.

Correct the value supplied in the job definition for the -tracelvl option to one of the values indicated in the User's Guide. .

See The User's Guide for details of the -tracelvl option settings in the job definition.

EEWO0914W

An internal error has occurred. Either the joblog or the job protocol for the following job does not exist: Job name: "job_name" Job ID: "job_ID" .

job_name and job_ID identify the job for which the job protocol does not exist.

R3batch continues, but log information is not available.

If you need to have log information for the successful running of this job, stop the job and contact the SAP system administrator to determine why the joblog or job protocol does not exist. When the problem has been resolved rerun r3batch . If the problem persists, contact IBM Software Support for assistance.

EEWO0915W

An internal error has occurred. Either the joblog or the job protocol for the following job is empty: Job name: "job_name" Job ID: "job_ID" .

job_name and job_ID identify the job for which the joblog is empty.

R3batch continues, but log information is not available.

If you need to have log information for the successful running of this job, stop the job and contact the SAP system administrator to determine why the joblog or job protocol is empty. When the problem has been resolved rerun r3batch . If the problem persists, contact IBM Software Support for assistance.

EEWO0916W

An internal error has occurred. The step has no spool list

See message.

R3batch continues, but log information is not available.

If you need to have log information for the successful running of this job, stop the job and contact the SAP system administrator to determine why the step has no spool list. When the problem has been resolved rerun r3batch .

EEWO0917W

An internal error has occurred. The spool ID is not valid

See message.

R3batch continues, but log information is not available.

If you need to have log information for the successful running of this job, stop the job and contact the SAP system administrator to determine why the spool ID is not valid. When the problem has been resolved rerun r3batch . If the problem persists, contact IBM Software Support for assistance.

EEWO0918W

The report list selection is finished

The program is reading the report list from the SAP system. Depending on circumstances, this message may indicate that the process has completed successfully, or that the selection has terminated unexpectedly, with an internal error.

R3batch continues.

Check that the reports received from the SAP system are what you are expecting. If they are not, rerun r3batch (the problem may be transient). If the problem persists, contact IBM Software Support for assistance.

EEWO0919W

There are no background processing resources active in the R/3 system.

See message.

R3batch continues, but the job cannot be run.

Contact the R/3 system administrator to activate background processing resources in the R/3 system.

EEWO0920W

An internal error has occurred. The spoollist of the following job cannot be read: Job name: "job_name" Job ID: "job_ID" .

job_name and job_ID identify the job for which the spoollist could not be read.

R3batch continues, but log information is not available.

If you need to have log information for the successful running of this job, stop the job and contact the SAP system administrator to determine why the spool list cannot be read. When the problem has been resolved rerun r3batch .

EEWO0921W

An internal error has occurred. The program requires the -flag type=exec parameter to be specified for dynamic job creation.

This is an internal error caused by one module of r3batch not supplying the indicated parameter when calling another module.

R3batch continues but the job is not created.

Contact IBM Software Support for assistance.

EEWO0922W

An internal error has occurred. The program could not read the application log on the SAP R/3 system.

R3batch could not read the application log on the SAP R/3 system.

R3batch continues, but the application log is not appended to the job log.

Contact IBM Software Support for assistance.

EEWO0930W

The following language is not valid: "language" . The following default language is used: "default_language" .

See message.

R3batch continues.

If you do not want the job to continue in the indicated default language, stop the job. To correct the language selection, 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 . Then rerun r3batch .

See The User's Guide for more information about the language options.

EEWO0950W

The RFC user is already logged on

See message.

R3batch continues.

You might choose to warn the SAP system administrator that a job for this RFC user has been submitted, but that this user is already logged on.

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.

The SAP factory calendar ID and year range specified with the r3batch RSC task could not find any data to export.

R3batch continues, but no output is provided.

Change the SAP Factory Calendar ID, or year range, or both, and rerun the command.

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.

You have tried to commit an external dependency on the SAP event name and parameter indicated in the message, but the event could not be found on the SAP system. Either the SAP event is incorrectly defined in IBM Workload Scheduler, or it has not been created on the SAP system.

R3batch continues.

Check if the SAP event and parameter have been correctly defined in IBM Workload Scheduler and change them, it they have not. Check whether the SAP event exists on the SAP system. If the event does not exist, and your dependency is defined correctly, this message is for information only.

An error occurred while trying to store information about the started process chain job. Any requests for the process chain details cannot be fulfilled.

See message.

R3batch continues, but any requests for the process chain details cannot be fulfilled.

This is an internal error. If the problem persists, search the IBM Support database for a solution at Support.

EEWO0001 - EEWO1080

EEWO0001E

EEWO0010E

EEWO0011E

EEWO0012E

EEWO0013E

EEWO0014E

EEWO0015E

EEWO0016E

EEWO0017E

EEWO0018E

EEWO0019E

EEWO0020E

EEWO0030E

EEWO0031E

EEWO0032E

EEWO0033E

EEWO0034E

EEWO0035E

EEWO0036E

EEWO0037E

EEWO0038E

EEWO0100E

EEWO0101E

EEWO0102E

EEWO0103E

EEWO0104E

EEWO0107E

EEWO0108E

EEWO0109E

EEWO0110E

EEWO0111E

EEWO0112E

EEWO0113E

EEWO0114E

EEWO0115E

EEWO0116E

EEWO0117E

EEWO0118E

EEWO0119E

EEWO0120E

EEWO0121E

EEWO0122E

EEWO0123E

EEWO0124E

EEWO0125E

EEWO0126E

EEWO0160E

EEWO0161E

EEWO0162E

EEWO0163E

EEWO0164E

EEWO0165E

EEWO0166E

EEWO0167E

EEWO0171E

EEWO0172E

EEWO0173E

EEWO0174E

EEWO0175E

EEWO0176E

EEWO0177E

EEWO0178E

EEWO0179E

EEWO0180E

EEWO0181E

EEWO0182E

EEWO0183E

EEWO0184E

EEWO0185E

EEWO0186E

EEWO0187E

EEWO0189E

EEWO0190E

EEWO0223E

EEWO0224E

EEWO0243E

EEWO0257E

EEWO0260E

EEWO0261E