Job Management Partner 1/Automatic Job Management System 3 for Enterprise Applications

Job Management Partner 1/Automatic Job Management System 3 for Enterprise Applications
Job Management Partner 1/Automatic Job
Management System 3 for Enterprise
Applications
Description, User's Guide and Reference
3020-3-S29(E)
„ Relevant program products
P-242C-6597 Job Management Partner 1/Automatic Job Management System 3 for Enterprise Applications 09-00 (for Windows
Server 2003, Windows Server 2003(x64))
P-2A2C-6597 Job Management Partner 1/Automatic Job Management System 3 for Enterprise Applications 09-00 (for Windows
Server 2008)
P-1J2C-6592 Job Management Partner 1/Automatic Job Management System 3 for Enterprise Applications 09-00 (for HP-UX
(IPF))
P-9D2C-6592 Job Management Partner 1/Automatic Job Management System 3 for Enterprise Applications 09-00 (for Solaris)
P-1M2C-6592 Job Management Partner 1/Automatic Job Management System 3 for Enterprise Applications 09-00 (for AIX)
„ Trademarks
ABAP is a registered trademark or a trademark of SAP AG in Germany and in other countries.
AIX is a registered trademark of the International Business Machines Corp. in the U.S.
HP-UX is a product name of Hewlett-Packard Company.
Itanium is a registered trademark of Intel Corporation or its subsidiaries in the United States and other countries.
Microsoft is a registered trademark of Microsoft Corp. in the U.S. and other countries.
R/3 is a registered trademark or a trademark of SAP AG in Germany and in other countries.
SAP is a registered trademark or a trademark of SAP AG in Germany and in other countries.
SAP NetWeaver is a trademark or registered trademark of SAP AG in Germany and other countries.
Solaris is a trademark or registered trademark of Sun Microsystems, Inc. in the United States and other countries.
UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company Limited.
Windows is a registered trademark of Microsoft Corp. in the U.S. and other countries.
Windows Server is a registered trademark of Microsoft Corporation in the United States and/or other countries.
The following program product contains some parts whose copyrights are reserved by Sun Microsystems, Inc.: P-9D2C-6592
The following program product contains some parts whose copyrights are reserved by UNIX System Laboratories, Inc.:
P-9D2C-6592
Other product and company names mentioned in this document may be the trademarks of their respective owners. Throughout this
document Hitachi has attempted to distinguish trademarks from descriptive terms by writing the name with the capitalization used
by the manufacturer, or by writing the name with initial capital letters. Hitachi cannot attest to the accuracy of this information. Use
of a trademark in this document should not be regarded as affecting the validity of the trademark.
This manual may also be used with other program products, in addition those listed above. For details, see the release notes.
„ Restrictions
Information in this document is subject to change without notice and does not represent a commitment on the part of Hitachi. The
software described in this manual is furnished according to a license agreement with Hitachi. The license agreement contains all of
the terms and conditions governing your use of the software and documentation, including all warranty rights, limitations of liability,
and disclaimers of warranty.
Material contained in this document may describe Hitachi products not available or features not available in your country.
No part of this material may be reproduced in any form or by any means without permission in writing from the publisher.
Printed in Japan.
„ Edition history
Edition 1 (3020-3-S29(E)): November 2009
„ Copyright
All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.
Preface
This manual explains the functions, use, and syntax of Job Management Partner 1/
Automatic Job Management System 3 for Enterprise Applications.
In this manual, JP1 is an abbreviation for Job Management Partner 1.
Intended readers
This manual is intended for users who want to know about the functions, use, and
syntax of JP1/AJS3 for EAP.
This manual assumes the reader has a basic understanding of:
• the R/3 system and its system management
• the SAP BW system and its system management if the SAP BW system is to be
used
Organization of this manual
This manual consists of the following chapters. Note that this manual applies equally
to all OSs. If a function operates differently in different OSs, the differences are noted.
1. Overview of JP1/AJS3 for EAP
This chapter describes the features and system configuration of JP1/AJS3 for
EAP and explains linkage with JP1 Series programs.
2. Installation and Setup
This chapter explains how to install and set up JP1/AJS3 for EAP.
3. Executing Background Jobs Using JP1/AJS
This chapter shows how to execute background jobs using JP1/AJS.
4. Commands
This chapter describes the command syntax of JP1/AJS3 for EAP.
5. Events
This chapter explains the events that JP1/AJS3 for EAP issues to other programs.
6. Messages
This chapter describes the messages that are issued by JP1/AJS3 for EAP.
i
7. syslog Messages (When UNIX Is Used)
This chapter explains the syslog messages of JP1/AJS3 for EAP output to the
syslog file.
8. Troubleshooting Guide for JP1/AJS3 for EAP
This chapter describes how to troubleshoot JP1/AJS3 for EAP.
Related publications
This manual is part of a comprehensive set of manuals for the JP1 series of software
products.
• Job Management Partner 1/Automatic Job Management System 3 Overview
(3020-3-S02(E))
• Job Management Partner 1/Automatic Job Management System 3 System Design
(Configuration) Guide (3020-3-S03(E))
• Job Management Partner 1/Automatic Job Management System 3 System Design
(Work Tasks) Guide (3020-3-S04(E))
• Job Management Partner 1/Automatic Job Management System 3 Configuration
Guide 1 (3020-3-S05(E))
• Job Management Partner 1/Automatic Job Management System 3 Configuration
Guide 2 (3020-3-S06(E))
• Job Management Partner 1/Automatic Job Management System 3 Administration
Guide (3020-3-S07(E))
• Job Management Partner 1/Automatic Job Management System 3
Troubleshooting (3020-3-S08(E))
• Job Management Partner 1/Automatic Job Management System 3 Operator's
Guide (3020-3-S09(E))
• Job Management Partner 1/Automatic Job Management System 3 Command
Reference 1 (3020-3-S10(E))
• Job Management Partner 1/Automatic Job Management System 3 Command
Reference 2 (3020-3-S11(E))
• Job Management Partner 1/Automatic Job Management System 3 Linkage Guide
(3020-3-S12(E))
• Job Management Partner 1/Automatic Job Management System 3 Messages 1
(3020-3-S13(E))
• Job Management Partner 1/Automatic Job Management System 3 Messages 2
(3020-3-S14(E))
ii
• Job Management Partner 1/Integrated Management - Manager Quick Reference
(3020-3-R75(E))
• Job Management Partner 1/Integrated Management - Manager Overview and
System Design Guide (3020-3-R76(E))
• Job Management Partner 1/Integrated Management - Manager Configuration
Guide (3020-3-R77(E))
• Job Management Partner 1/Integrated Management - Manager Administration
Guide (3020-3-R78(E))
• Job Management Partner 1/Integrated Management - Manager GUI Reference
(3020-3-R79(E))
• Job Management Partner 1/Integrated Management - Manager Command and
Definition File Reference (3020-3-R80(E))
• Job Management Partner 1/Integrated Management - Manager Messages
(3020-3-R81(E))
• Job Management Partner 1/Base User's Guide (3020-3-R71(E))
• Job Management Partner 1/Base Messages (3020-3-R72(E))
• Job Management Partner 1/Base Function Reference (3020-3-R73(E))
• Job Management Partner 1/Software Distribution Description and Planning
Guide (3020-3-S79(E)), for Windows systems
• Job Management Partner 1/Software Distribution Setup Guide (3020-3-S80(E)),
for Windows systems
• Job Management Partner 1/Software Distribution Administrator's Guide Volume
1 (3020-3-S81(E)), for Windows systems
• Job Management Partner 1/Software Distribution Administrator's Guide Volume
2 (3020-3-S82(E)), for Windows systems
• Job Management Partner 1/Script Description and Reference (3020-3-K55(E))
Conventions: Abbreviations
This manual uses the following abbreviations for product names:
Abbreviation
AIX
HP-UX
IPF
Full name
AIX 5L V5.3/V6.1
HP-UX (IPF)
HP-UX 11i V2/11i V3 (IPF)
Itanium(R) Processor Family
iii
Abbreviation
JP1/AJS
JP1/AJS Agent
JP1/AJS Manager
JP1/AJS View
Full name
JP1/AJS3
JP1/Automatic Job Management System 3 - Agent
JP1/Automatic Job Management System 3 - Manager
JP1/Automatic Job Management System 3 - View
JP1/AJS2
JP1/Automatic Job Management System 2 - Agent
JP1/Automatic Job Management System 2 - Manager
JP1/Automatic Job Management System 2 - View
JP1/AJS3 - Agent
JP1/Automatic Job Management System 3 - Agent
JP1/AJS2 - Agent
JP1/Automatic Job Management System 2 - Agent
JP1/AJS3 - Manager
JP1/Automatic Job Management System 3 - Manager
JP1/AJS2 - Manager
JP1/Automatic Job Management System 2 - Manager
JP1/AJS3 - View
JP1/Automatic Job Management System 3 - View
JP1/AJS2 - View
JP1/Automatic Job Management System 2 - View
JP1/AJS3 for EAP
JP1/Automatic Job Management System 3 for Enterprise
Applications
JP1/IM
JP1/Integrated Management - Manager
JP1/Integrated Management - View
R/3
SAP's product SAP R/3(R)
SAP BW
SAP's product SAP Business Information Warehouse
Solaris
Solaris 9/10
Windows
Windows
Server 2003
Windows
Server 2003
Microsoft(R) Windows Server(R) 2003 R2, Enterprise Edition
Microsoft(R) Windows Server(R) 2003 R2, Standard Edition
Microsoft(R) Windows Server(R) 2003, Enterprise Edition
Microsoft(R) Windows Server(R) 2003, Standard Edition
Windows
Server 2003
(x64)
Microsoft(R) Windows Server(R) 2003 R2, Enterprise x64
Edition
Microsoft(R) Windows Server(R) 2003 R2, Standard x64
Edition
Microsoft(R) Windows Server(R) 2003, Enterprise x64 Edition
Microsoft(R) Windows Server(R) 2003, Standard x64 Edition
Windows Server 2008
iv
Microsoft(R) Windows Server(R) 2008 Enterprise
Microsoft(R) Windows Server(R) 2008 Standard
This manual also uses the following abbreviations:
Abbreviation
Full name or meaning
ABAP
Advanced Business Application Programming
API
Application Programming Interface
EUC
Extended UNIX Code
FAT
File Allocation Table
ID
IDentification
JIS
Japanese Industrial Standards
LAN
Local Area Network
NTFS
New Technology File System
OS
Operating System
PC
Personal Computer
RFC
Remote Function Call
SNC
Secure Network Communications
TCP/IP
Transmission Control Protocol/Internet Protocol
UAC
User Account Control
UNC
Universal Naming Convention
XBP
eXternal Background Processing
XMI
eXternal Monitor Interface
v
Conventions: Diagrams
This manual uses the following conventions in diagrams:
Conventions: Fonts and symbols
Font and symbol conventions are classified as:
• General font conventions
• Conventions in syntax explanations
These conventions are described below.
General font conventions
The following table lists the general font conventions:
Font
vi
Convention
Bold
Bold type indicates text on a window, other than the window title. Such text includes menus,
menu options, buttons, radio box options, or explanatory labels. For example, bold is used in
sentences such as the following:
• From the File menu, choose Open.
• Click the Cancel button.
• In the Enter name entry box, type your name.
Italics
Italics are used to indicate a placeholder for some actual text provided by the user or system.
Italics are also used for emphasis. For example:
• Write the command as follows:
copy source-file target-file
• Do not delete the configuration file.
Font
Convention
Code font
A code font indicates text that the user enters without change, or text (such as messages) output
by the system. For example:
• At the prompt, enter dir.
• Use the send command to send mail.
• The following message is displayed:
The password is incorrect.
Examples of coding and messages appear as follows (although there may be some
exceptions, such as when coding is included in a diagram):
MakeDatabase
...
StoreDatabase temp DB32
In examples of coding, an ellipsis (...) indicates that one or more lines of coding are not
shown for purposes of brevity.
Conventions in syntax explanations
Syntax definitions appear as follows:
StoreDatabase [temp|perm] (database-name ...)
The following table lists the conventions used in syntax explanations:
Example font or symbol
StoreDatabase
database-name
SD
perm
Convention
Code-font characters must be entered exactly as shown.
This font style marks a placeholder that indicates where appropriate characters are
to be entered in an actual command.
Bold code-font characters indicate the abbreviation for a command.
Underlined characters indicate the default value.
-
This symbol delimits options. Options have the following structure:
• One or more alphanumeric characters
• One or more alphanumeric characters arguments
An argument may contain an option. If an argument contains an option or space
when specified, it can be enclosed by single (') or double (") quotation marks.
Example:
-ab, -a, '-b argument-1', "-a argument-2"
|
Only one of the options separated by a vertical bar can be specified at the same
time.
Example:
A|B|C means A, B, or C.
vii
Example font or symbol
Convention
{}
One of multiple items enclosed by braces must be selected. Items within the braces
are separated by a vertical line (|).
Example:
{A|B|C} means that one of A, B, or C must be specified.
[]
Square brackets enclose an item or set of items whose specification is optional.
Example:
[A] means that A can be specified as needed; otherwise, it need not be specified.
[B|C] means that B or C can be specified as needed; otherwise, neither need be
specified.
...
An ellipsis (...) indicates that the item or items enclosed in ( ) or [ ]
immediately preceding the ellipsis may be specified as many times as necessary.
()
Parentheses indicate the range of items to which the vertical bar (|) or ellipsis
(...) is applicable.
Conventions: KB, MB, GB, and TB
This manual uses the following conventions:
• 1 KB (kilobyte) is 1,024 bytes.
• 1 MB (megabyte) is 1,0242 bytes.
• 1 GB (gigabyte) is 1,0243 bytes.
• 1 TB (terabyte) is 1,0244 bytes.
Conventions: Version numbers
The version numbers of Hitachi program products are usually written as two sets of
two digits each, separated by a hyphen. For example:
• Version 1.00 (or 1.0) is written as 01-00.
• Version 2.05 is written as 02-05.
• Version 2.50 (or 2.5) is written as 02-50.
• Version 12.25 is written as 12-25.
The version number might be shown on the spine of a manual as Ver. 2.00, but the same
version number would be written in the program as 02-00.
viii
Contents
Preface
i
Intended readers .........................................................................................................i
Organization of this manual .......................................................................................i
Related publications ..................................................................................................ii
Conventions: Abbreviations .................................................................................... iii
Conventions: Diagrams ............................................................................................vi
Conventions: Fonts and symbols..............................................................................vi
Conventions: KB, MB, GB, and TB ..................................................................... viii
Conventions: Version numbers.............................................................................. viii
1. Overview of JP1/AJS3 for EAP
1
1.1 Features.......................................................................................................................2
1.2 System configuration..................................................................................................3
1.2.1 Controlling a background job..........................................................................3
1.2.2 Controlling InfoPackage or process chains.....................................................4
1.3 Job control function of JP1/AJS3 for EAP.................................................................6
1.3.1 Creating a background job ..............................................................................7
1.3.2 Releasing a background job ............................................................................7
1.3.3 Canceling a background job ............................................................................7
1.3.4 Deleting a background job ..............................................................................7
1.3.5 Displaying information about a background job.............................................7
1.3.6 Acquiring information about R/3 system resources ........................................8
1.4 InfoPackage or process chain control function of JP1/AJS3 for EAP .......................9
1.4.1 InfoPackage control function ..........................................................................9
1.4.2 Process chain control function ........................................................................9
1.5 Linkage with JP1 Series programs ...........................................................................10
1.5.1 Windows........................................................................................................10
1.5.2 All UNIX versions ........................................................................................10
2. Installation and Setup
13
2.1 Installation ................................................................................................................14
2.1.1 For Windows .................................................................................................14
2.1.2 For UNIX ......................................................................................................15
2.2 Job control function setup ........................................................................................18
2.2.1 Setting the operating environment for JP1/AJS3 for EAP (job control).......20
2.2.2 Setting the path..............................................................................................29
2.2.3 Setting the language type (UNIX).................................................................30
2.2.4 Adding R/3 system entries to the services file ..............................................30
ix
2.2.5 Adding R/3 system entries to the hosts file .................................................. 31
2.2.6 Steps to be completed before using the job control commands.................... 31
2.2.7 Creating the saprfc.ini file prior to R/3 system custom job execution
(Windows) .................................................................................................... 36
2.2.8 Enabling the XBP 2.0 interface (to use some functions).............................. 36
2.2.9 Providing a SAP user for job control............................................................ 37
2.3 InfoPackage or process chain control function setup .............................................. 39
2.3.1 Setting the operating environment for JP1/AJS3 for EAP (InfoPackage control
or process chain control) .............................................................................. 40
2.3.2 Setting the path ............................................................................................. 49
2.3.3 Setting the language type (UNIX) ................................................................ 49
2.3.4 Adding SAP BW system entries to the services file .................................... 50
2.3.5 Adding SAP BW system entries to the hosts file ......................................... 50
2.3.6 Steps to be completed before using the InfoPackage or process chain control
commands..................................................................................................... 51
2.3.7 Creating the saprfc.ini file prior to SAP BW system custom job execution
(Windows) .................................................................................................... 56
2.3.8 Specifying the action to take when InfoPackage ends with a warning on the
SAP BW system ........................................................................................... 56
2.3.9 Providing a SAP user for InfoPackage control or process chain control ..... 56
3. Executing Background Jobs Using JP1/AJS
59
3.1 Executing R/3 jobs by using JP1/AJS...................................................................... 60
3.1.1 Procedures for executing R/3 jobs................................................................ 60
3.1.2 Registering a custom job .............................................................................. 60
3.1.3 Defining a custom job................................................................................... 62
3.2 Executing InfoPackage or a process chain by using JP1/AJS ................................. 90
3.2.1 Procedures for executing InfoPackage or a process chain ........................... 90
3.2.2 Registering a custom job .............................................................................. 91
3.2.3 Defining a custom job................................................................................... 93
4. Commands
105
Command formats......................................................................................................... 106
Command list ................................................................................................................ 107
Common argument formats for various commands...................................................... 109
jbwipsta ..........................................................................................................................116
jr3bjcan ......................................................................................................................... 121
jr3bjdel .......................................................................................................................... 124
jr3bjrel........................................................................................................................... 127
jr3bjrep.......................................................................................................................... 135
jr3bjsho ......................................................................................................................... 137
jr3bjsub ......................................................................................................................... 142
jr3chrfc.......................................................................................................................... 155
x
5. Events
157
5.1 When a Windows event is used ..............................................................................158
5.1.1 Event ID format...........................................................................................158
5.1.2 List of events ...............................................................................................158
5.1.3 Maintenance information about events .......................................................163
6. Messages
167
6.1 Message format ......................................................................................................168
6.1.1 Output format of messages..........................................................................168
6.1.2 Format of message explanations .................................................................169
6.1.3 Output destinations of messages .................................................................169
6.2 Message list ............................................................................................................170
6.2.1 Messages common to all JP1/AJS3 for EAP functions...............................170
6.2.2 Messages specific to the job control function .............................................191
6.2.3 Messages specific to the InfoPackage control function and the process chain
control function ...........................................................................................205
7. syslog Messages (When UNIX Is Used)
217
7.1 syslog message format............................................................................................218
7.2 List of syslog messages ..........................................................................................219
8. Troubleshooting Guide for JP1/AJS3 for EAP
223
8.1 Troubleshooting procedure.....................................................................................224
8.2 Data to be collected if a problem occurs ................................................................225
8.2.1 Data to be collected about the job control function ....................................225
8.2.2 Data to be collected about the InfoPackage control function or the process
chain control function .................................................................................232
8.3 Actions to be taken for problems............................................................................240
8.3.1 Trouble related to the job control function..................................................240
8.3.2 Trouble related to the InfoPackage control function or the process chain
control function ...........................................................................................246
Appendixes
253
A. Directory List...........................................................................................................254
A.1 Folder list (Windows)....................................................................................254
A.2 Directory list (UNIX) ....................................................................................254
B. Port Numbers ...........................................................................................................257
B.1 Port numbers to be used for communication with an R/3 system or a SAP BW
system............................................................................................................257
B.2 Permitted direction of traffic when a firewall is used....................................258
C. Modifications Made in Each Version.......................................................................259
D. Glossary ...................................................................................................................261
xi
Index
xii
265
Chapter
1. Overview of JP1/AJS3 for EAP
The JP1/AJS3 for EAP program provides R/3 system job execution support. Using
JP1/AJS3 for EAP, it is possible to run background jobs from a non-R/3 system,
control InfoPackage and process chains on a SAP BW system from a non-SAP BW
system, and execute operations with other JP1 Series programs.
This chapter describes the features of JP1/AJS3 for EAP, the system configuration, the
job control functions of JP1/AJS3 for EAP, and linkage with JP1 Series programs.
1.1 Features
1.2 System configuration
1.3 Job control function of JP1/AJS3 for EAP
1.4 InfoPackage or process chain control function of JP1/AJS3 for EAP
1.5 Linkage with JP1 Series programs
1
1. Overview of JP1/AJS3 for EAP
1.1 Features
JP1/AJS3 for EAP is a JP1 Series program that enables you to link a non-R/3 system
with an R/3 system.
JP1/AJS3 for EAP provides the following features:
„
R/3 system jobs can now be controlled from non-R/3 systems. The following
operations on R/3 system background jobs (which, in this document, may be
referred to as R/3 jobs or simply jobs) can be controlled from JP1/AJS3 for EAP:
• Creation
• Release
• Cancellation
• Deletion
• Job information display
• Acquisition of R/3 system resource information
„
R/3 system background jobs can be executed with JP1 Series programs.
• Linkage with JP1/AJS (under Windows or UNIX)
JP1/AJS is a JP1 program that runs jobs automatically. It can assign sequence
numbers to processes and periodically run those processes in the specified
sequence. Alternatively, JP1/AJS3 can start processes when a specific event
occurs.
• Linkage with JP1/Script (under Windows)
JP1/Script is a JP1 Series program used to create script files.
JP1/Script allows you to create script files for commands of JP1/AJS3 for
EAP.
By using script files created with JP1/Script, you can specify the time to start
processing a script or to automatically execute a script during system startup.
2
„
InfoPackage in a SAP BW system can be controlled (InfoPackage defined on SAP
BW can be started) from a non-SAP BW system.
„
Process chains in a SAP BW system can be controlled (process chains defined on
SAP BW can be started) from a non-SAP BW system.
1. Overview of JP1/AJS3 for EAP
1.2 System configuration
The basic configuration of a JP1/AJS3 for EAP system consists of the following
machines:
• A machine running JP1/AJS3 for EAP
• An R/3 system (such as an application server or R/3 client machine) or a SAP BW
system (such as an application server or SAP BW client machine)
JP1 Series programs can be added as needed to the basic configuration.
1.2.1 Controlling a background job
Figure 1-1 shows a typical system configuration for background job control.
The example configuration shown below consists of the following machines:
• Machine running JP1/AJS3 for EAP, JP1/AJS, and JP1/Base (external machine
A)
• Machine running JP1/AJS3 for EAP (external machine B)
• Application server
• Machine running SAP front-end software (R/3 client machine)
3
1. Overview of JP1/AJS3 for EAP
Figure 1-1: Typical system configuration for background job control
1.2.2 Controlling InfoPackage or process chains
Figure 1-2 shows a typical system configuration for controlling InfoPackage or
process chains in a SAP BW system.
The example configuration shown below consists of the following machines:
• Machine running JP1/AJS3 for EAP, JP1/AJS, and JP1/Base (external machine
4
1. Overview of JP1/AJS3 for EAP
A)
• Machine running JP1/AJS3 for EAP (external machine B)
• Application server
• Machine running SAP front-end software (SAP BW client machine)
Figure 1-2: Typical system configuration for controlling InfoPackage or process
chains in a SAP BW system
5
1. Overview of JP1/AJS3 for EAP
1.3 Job control function of JP1/AJS3 for EAP
An R/3 system usually executes a program in interactive mode (online). However,
when a program is to be executed at a specific time (or at periodic intervals) or a large
quantity of data is to be printed, the processing is executed as a batch process
(background job) by the R/3 system.
By using the job control function of JP1/AJS3 for EAP, you can control the
background jobs of the R/3 system from a non-R/3 system.
JP1/AJS3 for EAP uses the XBP interface, which is an external management interface
for the R/3 system, to control the background jobs of the R/3 system. The XBP
interface is an open interface provided by SAP for controlling the background jobs of
the R/3 system from a non-R/3 system.
The background jobs of the R/3 system that can be controlled by JP1/AJS3 for EAP
are those that can be defined and executed using transaction code SM36.
Figure 1-3 shows the status transition of a background job within an R/3 system.
Figure 1-3: Status transition of a background job within an R/3 system
JP1/AJS3 for EAP allows you to use commands to control the status transition of a
background job shown in Figure 1-3. To change the job status from scheduled to
released, for instance, use the jr3bjrel command, which releases an R/3 system
background job.
Note that a background job consists of one or more job steps. The following two types
of job steps can be used in background jobs:
• ABAP program (report program created by using ABAP)
• External program (general program that can be executed by the R/3 system)
R/3 system background job control that can be executed from JP1/AJS3 for EAP is
explained below with reference to the transition sequence of the background job status.
For details of the commands used with JP1/AJS3 for EAP, see 4. Commands.
6
1. Overview of JP1/AJS3 for EAP
1.3.1 Creating a background job
To create a job, use the jr3bjsub command. An ABAP program or an external
program can be created as a job in the R/3 system. When the job is created, it is placed
in the scheduled state.
You can use the jr3bjdel command to delete scheduled jobs.
1.3.2 Releasing a background job
To release a job (specify the job start attribute), use either of the following methods:
• Specify the -rs or -ri option of jr3bjsub command.
• Specify the jr3bjrel command.
When the -rs or -ri option of the jr3bjsub command is used to specify the job start
attribute, the job can be released after creation (scheduling). The jr3bjrel command
can release jobs that were not released by the jr3bjsub command and jobs that are
created in the R/3 system. You can specify Release job as soon as possible or
Release job immediately as the job start attribute. When the command is
executed, the R/3 system job scheduler executes the job according to the job start
attribute. The job status then changes from scheduled to released.
If the -wait option is specified for job release, job completion is monitored. If a child
job is generated while the target job is being executed, you can monitor job completion
that includes the child jobs (completion monitoring of parent and child jobs). When
you monitor the completion of a job, the keyboard and other input devices will be
disabled until job execution terminates. If a communication error occurs during job
completion monitoring, the connection will be retried until a timeout occurs, as
defined in the environment setup file.
1.3.3 Canceling a background job
To cancel a job, use the jr3bjcan command. You can cancel an active job, which is
being executed. However, a scheduled, released, ready, finished, or terminated job
cannot be canceled.
1.3.4 Deleting a background job
To delete a job, use the jr3bjdel command. You can delete scheduled, released,
finished, and terminated jobs. You cannot delete active or ready jobs.
1.3.5 Displaying information about a background job
To display information about a job, use the jr3bjsho command. You can view the job
status in list or detailed list format. You can display jobs for a specific user only or jobs
for a specific status only, such as ready.
7
1. Overview of JP1/AJS3 for EAP
1.3.6 Acquiring information about R/3 system resources
To obtain information about R/3 system resources, use the jr3bjrep command. As
resource information, you can obtain the names of variants defined for a specified
ABAP program.
8
1. Overview of JP1/AJS3 for EAP
1.4 InfoPackage or process chain control function of JP1/AJS3 for
EAP
By using the InfoPackage control function and the process chain control function of
JP1/AJS3 for EAP, you can control InfoPackage and the process chains in a SAP BW
system from a non-SAP BW system.
1.4.1 InfoPackage control function
By using the InfoPackage control function of JP1/AJS3 for EAP, you can run
InfoPackage defined on a SAP BW system from a non-SAP BW system. InfoPackage
is a means of generating a transfer request when you want to transfer data to a SAP
BW system. By running InfoPackage, you can transfer data to a SAP BW system.
JP1/AJS3 for EAP uses the BW - STA interface, which is an external management
interface for a SAP BW system, to control InfoPackage in a SAP BW system. The BW
- STA interface is an open interface provided by SAP for controlling InfoPackage in a
SAP BW system from a non-SAP BW system.
To start InfoPackage, use the jbwipsta command. The jbwipsta command enables
you to start an InfoPackage already defined on a SAP BW system and monitor
InfoPackage until InfoPackage terminates. For details about the commands used with
JP1/AJS3 for EAP, see 4. Commands.
1.4.2 Process chain control function
By using the process chain control function of JP1/AJS3 for EAP, you can run process
chains defined on a SAP BW system from a non-SAP BW system. A process chain is
a means of automatically running the jobs in a SAP BW system and consists of a series
of processes (jobs) that are run in the background. By running a process chain, you can
automatically run a series of processes based on the execution sequence.
JP1/AJS3 for EAP uses the BW - SCH interface, which is an external management
interface for a SAP BW system, to control the process chains of the SAP BW system.
The BW - SCH interface is an open interface provided by SAP for controlling the
process chains of the SAP BW system from a non-SAP BW system.
To start a process chain, use the jbwipsta command. The jbwipsta command
enables you to start a process chain already defined on a SAP BW system and monitor
the process chain until the process chain ends. For details about the commands used
with JP1/AJS3 for EAP, see 4. Commands.
9
1. Overview of JP1/AJS3 for EAP
1.5 Linkage with JP1 Series programs
This section describes linkage with JP1 Series programs for each OS.
1.5.1 Windows
The following explains linkage with JP1/AJS and JP1/Script.
(1) Creating a background job in the R/3 system using JP1/AJS
To create a background job in the R/3 system using JP1/AJS, you must register and
define a custom job for the R/3 system using JP1/AJS. First, register the custom job
for the R/3 system in the Register Custom Job dialog box of JP1/AJS. Next, open the
Jobnet Editor window of JP1/AJS and define the custom job registered in JP1/AJS in
the jobnet. The R/3 system custom job defined in the jobnet can be executed using the
schedule and calendar functions of JP1/AJS.
For details about registering and defining a custom job for the R/3 system in the jobnet
of JP1/AJS, see 3.1 Executing R/3 jobs by using JP1/AJS.
(2) Starting InfoPackage or a process chain in a SAP BW system using JP1/AJS
To start InfoPackage or a process chain in a SAP BW system by using JP1/AJS, you
must use JP1/AJS to register and define a custom job for the SAP BW system. First,
register the custom job for the SAP BW system in the Register Custom Job dialog box
of JP1/AJS. Next, open the Jobnet Editor window of JP1/AJS and define the custom
job registered in JP1/AJS in a jobnet. The SAP BW system custom job defined in the
jobnet can be executed using the schedule and calendar functions of JP1/AJS.
For details about registering and defining a custom job for the SAP BW system in a
jobnet of JP1/AJS, see 3.2 Executing InfoPackage or a process chain by using JP1/
AJS.
(3) Controlling a background job in the R/3 system using JP1/Script
To use JP1/Script to control a background job in the R/3 system, create a script file for
commands of JP1/AJS3 for EAP.
For details about creating a script file, see the manual Job Management Partner 1/
Script Description and Reference.
1.5.2 All UNIX versions
The following explains linkage with JP1/AJS.
(1) Registering a background job in an R/3 system using JP1/AJS
To use JP1/AJS to register a background job in an R/3 system, define a command
(command line) for JP1/AJS3 for EAP as a job for JP1/AJS, and then define the job in
a JP1/AJS jobnet. An R/3 job defined in a jobnet can be registered in the R/3 system
10
1. Overview of JP1/AJS3 for EAP
and executed using the schedule and calendar functions of JP1/AJS.
For details about defining job and defining jobs in a jobnet, see the manual Job
Management Partner 1/Automatic Job Management System 3 Operator's Guide.
(2) Starting InfoPackage or a process chain in a SAP BW system by using JP1/
AJS
To start InfoPackage or a process chain in a SAP BW system by using JP1/AJS, define
JP1/AJS3 for EAP commands (command line) as a JP1/AJS job and define the job in
a JP1/AJS jobnet. The job defined in the jobnet can be registered in the SAP BW
system and executed with the schedule and calendar functions of JP1/AJS.
For details about defining jobs and defining jobs in a jobnet, see the manual Job
Management Partner 1/Automatic Job Management System 3 Operator's Guide.
(3) Controlling R/3 system background jobs with JP1/AJS
To control R/3 system background jobs using JP1/AJS, specify JP1/AJS3 for EAP
commands for the JP1/AJS action.
For details about specifying the JP1/AJS3 for EAP commands for a JP1/AJS action,
see the manual Job Management Partner 1/Automatic Job Management System 3
Linkage Guide.
(4) Controlling InfoPackage or a process chain in a SAP BW system by using
JP1/AJS
To control InfoPackage or a process chain in a SAP BW system by using JP1/AJS,
specify JP1/AJS3 for EAP commands for the JP1/AJS action.
For details about specifying JP1/AJS3 for EAP commands for a JP1/AJS action, see
the manual Job Management Partner 1/Automatic Job Management System 3 Linkage
Guide.
11
Chapter
2. Installation and Setup
This chapter describes how to install and set up JP1/AJS3 for EAP on each OS.
2.1 Installation
2.2 Job control function setup
2.3 InfoPackage or process chain control function setup
13
2. Installation and Setup
2.1 Installation
This section explains the procedures for installing and uninstalling JP1/AJS3 for EAP.
2.1.1 For Windows
JP1/AJS3 for EAP is designed for use with a Transmission Control Protocol/Internet
Protocol (TCP/IP) network configuration. Confirm the machine environment at the
installation site before installing JP1/AJS3 for EAP.
Once you have installed JP1/AJS for EAP, you need to restart the system to use the
product.
This section describes the procedures for uninstalling and installing
Windows-compliant JP1/AJS3 for EAP.
The following operations require you to log in as a user granted the Administrators
authority.
Also, if you have enabled the user account control function (UAC) of the OS, you must
upgrade to the Administrator role.
(1) Installing
To install JP1/AJS3 for EAP:
1.
Insert the disk supplied with JP1/AJS3 for EAP in the drive.
The initial screen opens. Follow the on-screen instructions to install JP1/AJS3 for
EAP.
For the folder and files created at installation, see A. Directory List.
2.
Restart the system.
Restart the system before using the product.
If you are using JP1/Software Distribution, you can remotely install JP1/AJS3 for
EAP. For instructions on how to perform remote installation, see the manual Job
Management Partner 1/Software Distribution Administrator's Guide Volume 1, for
Windows systems.
When the installation ends normally, perform the setup procedures required to use JP1/
AJS3 for EAP.
Note
If you have defined a custom job using the Windows version of JP1/AJS - View,
you need to update the customer job definition program registered in JP1/AJS View after installing the product.
14
2. Installation and Setup
Redo Procedure 1 of (1) If JP1/AJS - View is installed on a Windows machine in
3.1.1 Procedures for executing R/3 jobs and 3.2.1 Procedures for executing
InfoPackage or a process chain.
For details about directories created after product installation, see A. Directory List.
(2) Uninstalling
To uninstall JP1/AJS3 for EAP:
1.
Log on to the system.
2.
Open Control Panel and choose Add/Remove Programs or Programs and
Functions.
Delete JP1/AJS3 for EAP by following the instructions displayed in the window.
2.1.2 For UNIX
JP1/AJS3 for EAP is designed for use with a TCP/IP network configuration. Confirm
the machine environment at the installation site before installing JP1/AJS3 for EAP.
This section describes the procedures for uninstalling and installing UNIX-compliant
JP1/AJS3 for EAP.
(1) Installing
To install JP1/AJS3 for EAP, follow the procedure below.
(a) Prepare for installer startup
1.
Log in as a superuser or issue the su command to switch from a user to a
superuser.
2.
Make sure that JP1/AJS3 for EAP is not running.
3.
Insert the supplied JP1/AJS3 for EAP media into the drive.
(b) Start Hitachi PP Installer
Start Hitachi PP Installer using the following command:
For HP-UX
# /usr/sbin/mount -F cdfs -r device-filename /cdrom
# /cdrom/IPFHPUX/setup /cdrom
For Solaris
# /cdrom/SOLARIS/setup /cdrom/cdrom0
Note
If the OS is Solaris, you do not need to execute the mount command.
15
2. Installation and Setup
For AIX
# /usr/sbin/mount -F cdrfs -r device-filename /cdrom
# /cdrom/AIX/setup /cdrom
When Hitachi PP installer starts, the initial window of Hitachi PP Installer appears.
(c) Install
1.
In the initial window, enter I.
A list of the software that can be installed appears.
2.
Move the cursor to JP1/AJS3 for Enterprise Applications and press the space bar
to select it.
3.
Enter I to install JP1/AJS3 for EAP.
4.
Enter Y or y.
When installation is completed, enter Q to return to the initial screen.
For details about directories created during installation, see A. Directory List.
When the installation ends normally, perform the setup procedures required to use JP1/
AJS3 for EAP.
(2) Uninstalling
To uninstall JP1/AJS3 for EAP, follow the procedure below.
1.
Log in as a superuser or issue the su command to switch from a user to a
superuser.
2.
Check that JP1/AJS3 for EAP is not running.
3.
Execute the following command to start Hitachi PP Installer.
# /etc/hitachi_setup
When you start Hitachi PP Installer, the Hitachi PP Installer initial window opens.
4.
In the initial window, enter D.
A list of uninstallable software programs appears.
5.
Position the cursor on JP1/AJS3 for Enterprise Applications and press the space
bar to select it.
6.
Enter D.
The Installer uninstalls JP1/AJS3 for EAP.
7.
16
Enter Y or y.
2. Installation and Setup
Once uninstallation is complete, enter Q. The initial window reappears.
17
2. Installation and Setup
2.2 Job control function setup
This section explains the setup that must be performed to enable the use of the job
control functions of JP1/AJS3 for EAP. Before using the job control functions of JP1/
AJS3 for EAP, you must perform the setup outlined below. For UNIX, perform the
setup as a superuser.
Procedure 1
Setting up the operating environment for JP1/AJS3 for EAP (job control)
Procedure 2
Setting the path
Procedure 3
Setting the language type (UNIX)
Procedure 4
Adding R/3 system entries to the services file
Procedure 5
Adding R/3 system entries to the hosts file
Procedure 6
Completing the following setup steps before using the job control commands:
• Create the saprfc.ini file to make sure that the -d option for R/3
destination information is usable. #1
• Set the defaults for the command common arguments (R/3 destination
information and R/3 logon information). #2
Procedure 7
Creating the saprfc.ini file before R/3 system custom job execution#3
Procedure 8
Enabling the XBP 2.0 interface (to use functions)#4
Procedure 9
Preparing a SAP user for job control
Procedure 10
Setting the codepage when connecting to a Unicode version SAP system
18
2. Installation and Setup
#1
This step is not necessary if the -d option will not be used.
#2
This step must be performed when common arguments (R/3 destination
information and R/3 logon information) for the job control commands are not
specified. If the R/3 destination information and R/3 logon information are
specified on the command line, this step is not necessary.
#3
This step is not necessary if the saprfc.ini file will not be used for R/3 system
custom job definition.
#4
Perform this procedure to use the following functions:
• Monitoring the completion of a job, including child jobs that are generated
during the execution of the target job (completion monitoring of parent and
child jobs)
• Specifying job class A or B as the priority level of a job
• Controlling the following extended print parameters:
- Specifying the title of a spool request
- Specifying the output format using a format name
- Specifying the department name to be printed on the cover sheet
- Specifying the information text when archive data is output
The procedures are detailed in the following sections.
When JP1/AJS3 for EAP communicates with an R/3 system, the connecting side (JP1/
AJS3 for EAP) does not use a specific port number or a well-known port number, and
the connected side (R/3 system) uses a different port number based on the connection
method used. For details about the port numbers that are available in the R/3 system
based on the connection method, see B.1 Port numbers to be used for communication
with an R/3 system or a SAP BW system.
If a firewall will be placed between JP1/AJS3 for EAP and an R/3 system, see B.2
Permitted direction of traffic when a firewall is used.
Note
Use up to 15 bytes for the name of the OS user that executes commands or custom
jobs. If the OS user name is 16 bytes or longer, an interface error occurs at the SAP
side and jobs cannot be executed.
19
2. Installation and Setup
2.2.1 Setting the operating environment for JP1/AJS3 for EAP (job
control)
You can modify the operating environment for JP1/AJS3 for EAP (job control) by
creating a job control environment setup file.
The environment setup file for job control (conf file) is located in the following
directory. If the environment setup file does not exist at installation, the model file in
the same directory is automatically copied as the environment setup file at installation.
• Windows: (installation-path)\conf\conf
• UNIX: /etc/opt/jp1_am_r3/conf/conf
The following figure shows the contents of the model file on which the environment
setup file to be created at installation is based.
• For Windows
Figure 2-1: Model file for the environment setup file for job control (for
Windows)
20
2. Installation and Setup
• For UNIX-based OSs
Figure 2-2: Model file for the environment setup file for job control (for UNIX)
In situations where Windows is used with an NTFS type file system, we recommend
that you prevent tampering of the environment setup file information by defining the
access permission so that only personnel with Administrators permission can edit the
environment setup file.
Before reediting the environment setup file, make sure that no command has been
executed for JP1/AJS3 for EAP.
The environment setup file syntax is as follows:
[section]
key=string
• As the separator between section and key and between key and key, specify
one or more new-line codes.
• The character strings specified for section and key are case-insensitive.
• The key specifications within the same section can be in any order.
• If a semicolon (;) is placed at the beginning of a line, the line is handled as a
comment statement.
• When there are two or more section or key specifications having the same
name, the value of the first specification is used.
In the following situations, JP1/AJS3 for EAP operates using the defaults.
• An environment setup file is not created.
• An illegal value is specified for the environment setup file (includes a syntax
error).
• The environment setup file cannot be read.
21
2. Installation and Setup
The keys that can be specified for the environment setup file are explained below for
each section.
trace (trace section)
For trace (trace section), specify the name of the trace file that stores the trace level,
trace file size, and trace information. The following table describes the keys that can
be specified in the trace section.
Table 2-1: Keys that can be specified for trace
Key
Level
Value selectable as a string
0
No trace
1
Standard level
2
Detail level
3
Debug level
Size
22
0 or 1 to 65,535 (in kilobytes)
Explanation
Specify the trace level. If this key
specification is omitted, a trace
level of 1 is used. The trace volume
per command for each trace level is
as follows:
• When monitoring the
completion of jobs:
1 (standard level): 2.0 kilobytes
2 (detail level): 3.8 kilobytes +
(job execution time/completion
monitoring interval) x 0.2
kilobytes
3 (debug level): 32.0 kilobytes
+ (job execution time/
completion monitoring
interval) x 0.8 kilobytes
• When not monitoring the
completion of jobs:
1 (standard level): 2.0 kilobytes
2 (detail level): 3.8 kilobytes
3 (debug level): 32.0 kilobytes
Normally, select standard level.
Detail level or debug level should
be specified only if a failure occurs.
If you select no trace, no
information about the use of JP1/
AJS3 for EAP will be collected.
Specify the trace file size. If you
specify 0, the trace file size is 2
gigabytes. If you omit this key, the
trace file size is 12288 kilobytes.#1
To reduce the trace file size, delete
the created trace file and then
change the size.
2. Installation and Setup
Key
TargetDir
Value selectable as a string
Explanation
Windows:
Character string beginning with
(drive-name):\ or remote
resource name coded in UNC
(Universal Naming
Convention) format#2
UNIX:
Character string beginning with
Specify the directory containing the
trace file that stores the trace
information. If you omit this key, a
trace file is created for each
application in the default
directory#3.
Note
If you specify TargetFile,
any assignment to this key is
ignored.
/
Windows:
Character string beginning with
(drive-name):\ or remote
resource name coded in UNC
(Universal Naming
Convention) format#2
UNIX:
Character string beginning with
TargetFile
Trace information about all
applications will be collected in the
specified file.
Note
If you specify this key, any
assignment to TargetDir is
ignored.
/
#1
If you specify 12,288 kilobytes as the trace file size, the trace file can record at
least two days' worth of trace data when 100 jobs are executed per hour at trace
level 1 (default).
#2
The remote resource name expressed in UNC format is
\\computer-name\sharename, which is provided by Microsoft for networked
folder/file name specification purposes.
#3
For details about the default directory that stores the trace file, see A. Directory
List.
event (event section)
For event (event section), specify whether or not to generate events that are used in
Windows application logs.
For UNIX, make an event (event section) entry to specify whether to generate
syslog messages. The following table describes the keys that can be specified in the
event section.
23
2. Installation and Setup
Table 2-2: Keys that can be specified for an event
Key
Value selectable as a string
Explanation
ntevent
YES or NO
This entry can be made when you are
using Windows. Specify whether to
generate Windows events. If this key
specification is omitted, YES is used
as the event generation condition.
Syslog
YES or NO
This entry can be made when you are
using UNIX. Specify whether or not
to generate syslog messages. If this
key specification is omitted, YES is
used as the syslog message
generation condition.
command (command section)
For command (command section), specify whether or not to check the work directory
for JP1/AJS3 for EAP, the job completion monitoring interval, the appropriateness of
a specified R/3 object, the time and interval for attempting to retry connection in the
event of a communication error, and whether to output the R/3 job log to the standard
error output file. Also, specify the codepage number used when replacing the character
code in the connected Unicode version SAP system. The following table describes the
keys that can be specified in the command section.
Table 2-3: Keys that can be specified for command
Key
WorkDir
Value selectable as a string
Explanation
Windows:
Character string beginning with
(drive-name):\ or remote
resource name coded in
Universal Naming Convention
(UNC) format
UNIX:
Character string beginning with
Enter a full pathname to specify the
work directory for commands. The
work directory is set when you
execute a command.
If this key specification is omitted,
the current directory at the time the
command is executed is used.
(When JP1/AJS is used, the work
directory to be used for execution
of a JP1/AJS job#1 is used.)
/
24
2. Installation and Setup
Key
Value selectable as a string
Explanation
MonitorInterval
1 to 65,535 (in seconds)
Specify the job completion
monitoring interval. The value
specified will be used if the job
completion monitoring interval
specification is omitted from the
JP1/AJS3 for EAP jr3bjsub or
jr3bjrel command line. If this
key specification is omitted, the job
completion monitoring interval
value is 5 seconds.
CheckLevel
0
Specify the level for determining
whether to query the R/3 system
about the validity of the R/3 object
(ABAP program, variant) specified
in the job step information when a
job is registered (when the
jr3bjsub command is executed).
If you omit this key, the level is 2.
Does not query the R/3 system
about the appropriateness of a
specified value.
1
Queries the R/3 system about
the appropriateness of a
specified value regarding the
following points before a job is
created.#2
- Whether the specified ABAP
program exists
- Whether variants are
necessary for the specified
ABAP program
- Whether the specified variant
exists
2
Queries the R/3 system about
the appropriateness of a
specified value regarding the
following points before a job is
created.#2
- Whether the specified ABAP
program exists
- Whether the specified variant
exists
25
2. Installation and Setup
Key
Value selectable as a string
Explanation
RetryTime
0 to 65,535 (minutes)
Specify a period of time during
which attempts are made to restore
connection with the R/3 system if a
communication error occurs during
communication with the R/3
system.
Repeated attempts to recover the
connection will be made until the
duration specified here elapses. If
you type a setting of 0 or omit this
key specification, the encountered
error will be reported immediately
and no attempt will be made to
recover the connection.
If the RetryTime key is specified
together with the RetryCount key,
the RetryTime key is ignored. If
neither the RetryTime key nor the
RetryCount key is specified, the
RetryCount key is valid#3.
To specify the interval between
connection retries, use the
RetryInterval key.
RetryCount
0 to 65,535 (times)
Specify the number of retries for
the connection with the R/3 system
if a communication error occurs
during communication with the R/3
system.
If you specify 0, no retry is
attempted and an error is reported
immediately.
If you omit this key, 3 is assumed.
If the RetryCount key is specified
together with the RetryTime key,
the RetryTime key is ignored. If
neither the RetryCount key nor
the RetryTime key is specified, the
RetryCount key is valid#3.
To specify the interval between
connection retries, use the
RetryInterval key.
26
2. Installation and Setup
Key
Value selectable as a string
Explanation
RetryInterval
1 to 65,535 (seconds)
Specify the interval at which
attempts are made to restore
connection with the R/3 system if a
communication error occurs during
communication with the R/3
system. The value specified here
cannot exceed the value set for
RetryTime. If you omit to specify
this key, 180 seconds is set
automatically. If you do not specify
RetryTime or set 0 for it, this
RetryInterval setting is invalid.
JoblogAddToStderr
YES or NO
Specify whether to output the R/3
job log to the standard error output
file at the same time as it is output
to the specified output destination.
If you omit this key, NO is assumed
for the output condition.
Codepage
0 to 9999 (unit: Codepage number)
Specify the codepage number to be
used for character code conversion
in the connected Unicode version
SAP system.
When sending/receiving character
data in English, this key does not
need to be specified.
#1
For details about the work directory used when a JP1/AJS job is executed, see the
manual Job Management Partner 1/Automatic Job Management System 3 System
Design (Configuration) Guide.
#2
Network load will be greater than if a checklevel of 0 has been specified. The
required time for command execution will also be longer.
#3
The RetryCount key and the RetryTime key are mutually exclusive. The valid
key differs depending on the combination of the two keys as shown below:
Specified key
RetryCount key
Yes
Valid key
RetryTime key
Yes
RetryCount key
Yes
RetryTime key
No
27
2. Installation and Setup
Specified key
RetryCount key
Valid key
RetryTime key
RetryCount key
RetryTime key
Yes
No
Yes
No
No
Yes
No
Yes
No
No
Yes
No
Legend:
Yes: The key is specified or valid.
No: The key is not specified or not valid.
XMI (XMI section)
For XMI (XMI section), specify the XMI interface session audit level. The following
table describes the keys that can be specified in the XMI section.
Table 2-4: Keys that can be specified for XMI
Key
AuditLevel
Value selectable as a string
Explanation
Records data write (change)
operations.
Specify the XMI interface session
audit level. If this key specification
is omitted, the current XMI
interface session audit level
continues to be used.
0
1
Records data read errors.
2
Records data read operations.
3
Records external management
system access.
option (option section)
For option (option section), specify whether SAP Note 609462 or Note 710098 is
applied to the connection destination R/3 system. The following table describes the
keys that can be specified in the option section.
28
2. Installation and Setup
Table 2-5: Keys that can be specified for option
Key
Note609462
Value selectable as a string
YES or NO
Explanation
Specify whether to apply one of the following
support packages including SAP Note 609462 or
Note 710098 in the connection destination R/3
system:
• For the R/3 system release 6.20:
SAPKB62029
When you specify YES, the print parameters (-dp,
-ip, -sapcvr options) can correctly operate even
in an environment with SAP Note 609462 or Note
710098#.
If you omit this key, YES is assumed and the support
package is applied.
#
With SAP Note 609462 and SAP Note 710098, the specifications of SAP's
external management interface used by JP1/AJS3 for EAP have changed.
Accordingly, some print options specified in the jr3bjsub command may
operate incorrectly in an environment with SAP Note 609462 or SAP Note
710098, as indicated below:
- A print request may be deleted after print out even though the -dp option
(deletes a print request after print out) is not specified.
- A print request may be sent to a print device immediately even though the -ip
option (immediate print) is not specified.
- A SAP cover may be output even though N (no output) is specified for the
-sapcvr option (attaches a SAP cover).
2.2.2 Setting the path
To use the job control commands, define the command storage path for each user.
„
Windows Server 2008
With Windows, use the System Properties dialog box to define the environment
variable PATH.
To open the System Properties dialog box of Windows Server 2008, from Control
Panel, double-click the System icon.
Set the environment variable PATH to installation folder\program.
„
Windows Server 2003
With Windows, you need not define the command storage path.
29
2. Installation and Setup
The command storage path in Windows is defined when you restart the system
after installing JP1/AJS3 for EAP.
„
UNIX
With UNIX, the system administrator must enter the path definition in the system
profile. For the path definition, use environment variable PATH. Set the
environment variable PATH to /opt/jp1_am_r3/bin/.
2.2.3 Setting the language type (UNIX)
This setup need only be performed when you are using UNIX.
Messages can be output in English. To specify the language type, use environment
variable LANG. The following table describes the available character code sets and the
values that environment variable LANG may take.
Table 2-6: Available character codes and environment variable LANG values
OS
Available character code
Environment variable
LANG value
HP-UX
English
C
Solaris
English
C
AIX
English
C
Notes
• If any other value is set for LANG, English is used as the language type.
• If the JP1/AJS3 for EAP language environment and the R/3 language
environment do not have the same character codes, information that is obtained
from the R/3 system may be displayed incorrectly.
2.2.4 Adding R/3 system entries to the services file
Add the service name and the port number of the connection destination message
server in the services file when you connect a message server.
The following table describes the specification format for the service name and the
port number of the message server to be connected.
Table 2-7: Specification format for the service name and port number
Item
Message server
30
Service name
sapmssid#
Port number
Any/tcp
2. Installation and Setup
#
Specify the system ID of the R/3 system for sid in sapmssid.
For example, if the system ID of the connection destination message server is SD1
and the port number of the message server is 3601/tcp, add the following entry
(server name and port number) to the services file:
sapmsSD1
3601/tcp
The following figure shows typical additions to the R/3 system entries.
Figure 2-3: Example of adding R/3 system entries (services file)
2.2.5 Adding R/3 system entries to the hosts file
Add the host names of connection destination application servers to the hosts file.
The following figure shows typical additions to the R/3 system entries.
Figure 2-4: Example of adding R/3 system entries (hosts file)
2.2.6 Steps to be completed before using the job control commands
The following describes the procedures that must be completed when you want to use
the -d option of a command or you want to set the command common argument
defaults. The procedures are not necessary if the -d option will not be used or
command common argument defaults will not be set.
(1) Making sure that the -d option for R/3 destination information is usable
When using the -d option for the R/3 destination information on the command line of
JP1/AJS3 for EAP, the saprfc.ini file must be created. Either of the following
saprfc.ini files (or both) will be used depending on the operation method.
• saprfc.ini file created in the JP1/AJS3 for EAP work directory defined in the
31
2. Installation and Setup
job control environment setup file (or the current directory when a command is
executed if the JP1/AJS3 for EAP work directory is not specified)
• saprfc.ini file specified by environment variable RFC_INI
A saprfc.ini file search occurs in the following sequence:
• When saprfc.ini is specified by environment variable RFC_INI
Only the saprfc.ini file specified in environment variable RFC_INI is
searched for. The saprfc.ini file in the work directory of JP1/AJS3 for EAP is
not searched for.
• When saprfc.ini is not specified by environment variable RFC_INI
The saprfc.ini file in the JP1/AJS3 for EAP work directory defined in the
environment setup file is searched for.
The saprfc.ini file is usually created in the JP1/AJS3 for EAP work directory that
is defined in the environment setup file. To set up the saprfc.ini file for a specific
user, create the saprfc.ini file in the desired directory and specify the path for the
saprfc.ini file in environment variable RFC_INI.
After JP1/AJS3 for EAP is installed, a sample saprfc.ini file is stored in the
following directory:
• For Windows:
installation-folder\Sample\
• For UNIX-based OSs:
/opt/jp1_am_r3/sample
Copy the sample saprfc.ini file to the JP1/AJS3 for EAP working directory (or the
directory specified by the environment variable RFC_INI) and edit the copy sample
saprfc.ini file as required. If you intend to use environment variable RFC_INI,
specify it in advance.
Use the full path for the saprfc.ini file to be specified in environment variable
RFC_INI.
• Typical specification of environment variable RFC_INI (Windows)
RFC_INI=C:\home\user01\saprfc.ini
• Typical specification of environment variable RFC_INI (UNIX)
RFC_INI=/home/user01/saprfc.ini
The following figure shows an example of the saprfc.ini file. For details of the
32
2. Installation and Setup
saprfc.ini file entries, see the R/3 manual or online help.
Figure 2-5: Typical saprfc.ini file
There is more than one type of saprfc.ini file specification method (the figure
above is an example of type B). Edit the services file and hosts file as appropriate
for the type. For the specification items of each type and whether the services file
and hosts file must be edited, see the R/3 manual or online help.
(2) Specifying the defaults for command common arguments (R/3 destination
information and R/3 logon information)
If the common arguments (R/3 destination information and R/3 logon information)
entry is omitted from the command line for JP1/AJS3 for EAP, an r3defcon file must
be created. This file must be created in the home directory that is specified for the user
account.
Note
To use the Windows version r3defcon file, you need to specify the HOMEDRIVE
or HOMEPATH environment variable for job execution to identify the home
directory. Since these environment variables are not defined by default in the
execution environment of commands executed from JP1/AJS, you must define
them using environment variable items for job definition.
The following is a specification example of an environment variable (when the
r3defcon file is placed at C:\Documents and
Settings\Administrator):
HOMEDRIVE=C:
HOMEPATH=\Documents and Settings\Administrator
In those situations where Windows is employed with the NTFS file system, to prevent
unwanted access to r3defcon file information, you should specify a different home
directory for each user. With the FAT file system, however, you cannot protect the
r3defcon file information at the file level.
With UNIX, to prevent unwanted access to r3defcon file information, you should
33
2. Installation and Setup
define the access permissions for the r3defcon file so that only the user executing the
command can read the r3defcon file.
The following figure shows an example of creating the r3defcon file.
Figure 2-6: Example of creating an r3defcon file
The syntax for the r3defcon file is as follows:
[section]
key=string
• As the separator between section and key and between key and key, specify
one or more new-line codes.
• The character strings specified for section and key are case-insensitive.
• The key specifications within the same section can be in any order.
• If a semicolon (;) is placed at the beginning of a line, the line is handled as a
comment statement.
• When there are two or more section or key specifications that have the same
name, a KAJM0022-E message appears and command execution is terminated.
The keys that can be specified in the r3defcon file are explained below for each
section.
logon (logon section)
When omitting the R/3 logon information specification, specify logon (logon
section). The following table describes the keys that can be specified in the logon
section.
34
2. Installation and Setup
Table 2-8: Keys that can be specified for logon
Key
Value selectable as a string
Explanation
Client
1- to 3-byte character string (The
character string must consist of
numerals only.)
Specify the R/3 client number for
logging on to the R/3 system. Note
that a 1- or 2-byte R/3 client number
sent to the R/3 system is always
converted to a 3-byte number. If, for
instance, the client number is 001,
you can specify the number 1, 01, or
001. However, the 3-byte client
number 001 is always sent to the R/
3 system.
User
1- to 12-byte character string
Specify the SAP user name for
logging on to the R/3 system. For
details about the SAP users that can
be specified, see 2.2.9 Providing a
SAP user for job control.
Passwd
1- to 8-byte character string
Specify the password that has been
assigned to the SAP user for logging
on to the R/3 system.
Passwd2
1- to 40-byte character string
Specify the extended password that
was assigned to the SAP user for
logging in to the R/3 system.
The extended password is a
password rule that was extended in
the SAP systems based on SAP
NetWeaver 7.0 and later. You can
specify up to 40 bytes, and
alphabetic characters are
case-sensitive.
Lang
For English: E
Specify the language type that can
be used with the R/3 system. The
specifiable language type is English.
Note
When you specify the logon section, be sure to specify all the keys (client,
user, passwd or passwd2, and lang). Note that you cannot specify passwd
and passwd2 at the same time. Specify one of them according to the availability
of the extended password.
address (address section)
When omitting the R/3 destination information specification, specify address
(address section). The following table describes the keys that can be specified in the
address section.
35
2. Installation and Setup
Table 2-9: Keys that can be specified for address
Key
Value selectable as a string
Explanation
Host
1- to 100-byte character string
Specify the host name of a
destination R/3 system.
Sysno
1- to 2-byte character string (The
character string must consist of
numerals only.)
Specify the host SAP system number
of a destination R/3 system.
Dest
1- to 64-byte character string
Specify the destination (DEST value)
that is defined in the saprfc.ini
file.
Note
dest and host and sysno cannot be specified together. When specifying the
address section, specify dest only or specify host and sysno.
2.2.7 Creating the saprfc.ini file prior to R/3 system custom job
execution (Windows)
This setup need be performed only when you are using Windows.
If you plan to use the saprfc.ini file to define an R/3 system custom job, you must
create it in advance at the host where the jr3bjsub command is to be executed.
For saprfc.ini file creation, see (1) in 2.2.6 above.
2.2.8 Enabling the XBP 2.0 interface (to use some functions)
By using XBP interface version 2.0, which is an external management interface
provided by SAP (XBP 2.0 interface), you can use the following functions:
• Monitoring job completion that includes the child jobs that are generated during
the execution of the target job (completion monitoring of parent and child jobs)
• Specifying job class A or B as the priority level of a job
• Controlling the following extended print parameters:
• Specifying the title of a spool request
• Specifying the output format using a format name
• Specifying the department name to be printed on the cover sheet
• Specifying information text to be used when archive data is output
To use these functions, you need to enable the XBP 2.0 interface.
In addition, if you want to monitor the completion of parent and child jobs, you need
to enable the parent and child function in the connection destination R/3 system before
36
2. Installation and Setup
you execute the target job.
The following sections describe how to enable the XBP 2.0 interface and the parent
and child function.
(1) Enabling the XBP 2.0 interface
Check whether the XBP 2.0 interface is installed in the connection destination R/3
system and whether you can log on to the XBP 2.0 interface.
If the XBP 2.0 interface is not installed in the connection destination R/3 system, use
the appropriate support package for your R/3 to install the XBP 2.0 interface.
To check whether the XBP 2.0 interface is installed in the connection destination R/3
system, use transaction SE38 of the connection destination R/3 system to check
whether INITXBP2 (an ABAP program) exists. If INITXBP2 exists, the XBP 2.0
interface is installed.
For details about the XBP 2.0 interface, see SAP Note 604496.
(2) Enabling the parent and child function
To monitor the completion of parent and child jobs, you need to enable the parent and
child function in the connection destination R/3 system before you execute the jobs.
To enable the parent and child function, enable the XBP 2.0 interface and then use the
INITXBP2 ABAP program to turn on the parent and child function.
To turn on the parent and child function:
1.
Use the SAP front-end software to start the ABAP editor (transaction SE38).
2.
In the startup window of the ABAP editor, enter INITXBP2 for Program.
3.
From the Program menu, choose Execute.
The INITXBP2 program starts and the current settings are shown.
4.
In Change Settings in Parent-Child Function, select Switch On.
5.
From the Program menu, choose Execute.
The parent and child function is now enabled.
2.2.9 Providing a SAP user for job control
To control R/3 jobs, JP1/AJS3 for EAP uses RFC, which is the SAP Corporation
communication protocol used to execute the external management interface defined on
the SAP system side. For this reason you need to provide in advance, on the SAP
system side, a user to be used by JP1/AJS3 for EAP.
This section describes the user type, password, and role that need to be provided on the
SAP system side.
37
2. Installation and Setup
(1) User type
For the user type, you can use dialog, system, communication, or service.
(2) Characters that can be specified in the password
To define the password you can use numbers (from 0 to 9), alphabetic characters (a to
z, A to Z), and the following single-byte symbols:
[email protected]$%&/()=?'`*+~#-_.:{[]}<>|
(3) Required roles
The following roles are required for a user for job control.
„
Role object (S_RFC) for logging on from an external system
Assign a built-in role value (S_RFC_ALL).
„
Role object (S_XMI_PROD) for logging on to an external management interface
Assign a role value for which a value in the following table is set, or a built-in role
value (S_XMI_ADMIN).
Table 2-10: Roles required for role objects (S_XMI_PROD)
Role item
Description
Value
EXTCOMPANY
Company name of external management tool
HITACHI
EXTPRODUCT
Program name of external management tool
JP1
INTERFACE
Interface ID
*
„
Role object (S_BTCH_ADM and S_BTCH_NAM) for executing jobs
Assign the built-in role value (S_BTCH_ADM) for the S_BTCH_ADM role object,
and the built-in role value (S_BTCH_ALL) for the S_BTCH_NAM role object.
„
Role object (S_PROGRAM) for executing the ABAP program
Assign the built-in role value (S_ABAP_ALL) as the role object value.
38
2. Installation and Setup
2.3 InfoPackage or process chain control function setup
This section explains the setup that must be performed to use the InfoPackage control
function or the process chain control function of JP1/AJS3 for EAP.
Before using JP1/AJS3 for EAP (InfoPackage control or process chain control), you
must perform the setup outlined below. For UNIX, perform the setup as a superuser.
Procedure 1
Setting up the operating environment for JP1/AJS3 for EAP (InfoPackage control
or process chain control)
Procedure 2
Setting the path
Procedure 3
Setting the language type (UNIX)
Procedure 4
Adding SAP BW system entries to the services file
Procedure 5
Adding SAP BW system entries to the hosts file
Procedure 6
Completing the following setup steps before using the commands for
InfoPackage control or process chain control:
• Create the saprfc.ini file to make sure that the -d option for SAP BW
destination information is usable. #1
• Set the defaults for the command common arguments (SAP BW destination
information and SAP BW logon information). #2
Procedure 7
Creating the saprfc.ini file before SAP BW system custom job execution #3
(Windows)
Procedure 8
Specifying the action to take when InfoPackage ends with a warning on the SAP
BW system side
39
2. Installation and Setup
Procedure 9
Providing a SAP user for the InfoPackage control or process chain control
Procedure 10
Setting a codepage when connecting to a Unicode version SAP system
#1
This step is not necessary if the -d option will not be used.
#2
This step must be performed when common arguments (SAP BW destination
information and SAP BW logon information) for the InfoPackage control or
process chain control commands are not specified. If the SAP BW destination
information and SAP BW logon information are specified on the command line,
this step is not necessary.
#3
This step is not necessary if the saprfc.ini file will not be used for SAP BW
system custom job definition.
The procedures are detailed in the following sections.
When JP1/AJS3 for EAP communicates with a SAP BW system, the connecting side
(JP1/AJS3 for EAP) does not use a specific port number or a well-known port number,
and the connected side (SAP BW system) uses a different port number based on the
connection method used. For details about the port numbers that are available in the
SAP BW system based on connection methods, see B.1 Port numbers to be used for
communication with an R/3 system or a SAP BW system.
If a firewall will be placed between JP1/AJS3 for EAP and a SAP BW system, see B.2
Permitted direction of traffic when a firewall is used.
2.3.1 Setting the operating environment for JP1/AJS3 for EAP
(InfoPackage control or process chain control)
You can modify the operating environment for JP1/AJS3 for EAP (InfoPackage
control or process chain control) by creating an environment setup file for InfoPackage
control or process chain control.
The environment setup file for InfoPackage control or process chain control (conf
file) is located in the following directory. If the environment setup file does not exist
at installation, the model file in the same directory is automatically copied as the
environment setup file at installation.
• For Windows:
installation-folder\bwsta\conf\conf
40
2. Installation and Setup
• For UNIX-based OSs:
/etc/opt/jp1_am_r3/bwsta/conf/conf
The following figure shows the contents of the model file on which the environment
setup file to be created at installation is based.
• For Windows
Figure 2-7: Model file for the environment setup file for InfoPackage control or
process chain control (for Windows)
• For UNIX-based OSs
Figure 2-8: Model file for the environment setup file for InfoPackage control or
process chain control (for UNIX)
In situations where Windows is used with an NTFS type file system, we recommend
that you prevent tampering of the environment setup file information by defining the
access permission so that only personnel with Administrators permission can edit the
environment setup file.
41
2. Installation and Setup
Before reediting the environment setup file, make sure that no command has been
executed for JP1/AJS3 for EAP.
The environment setup file syntax is as follows:
[section]
key=string
• As the separator between section and key and between key and key, specify
one or more new-line codes.
• The character strings specified for section and key are case-insensitive.
• The key specifications within the same section can be in any order.
• If a semicolon (;) is placed at the beginning of a line, the line is handled as a
comment statement.
• When there are two or more section or key specifications having the same
name, the value of the first specification is used.
In the following situations, JP1/AJS3 for EAP operates using the defaults.
• An environment setup file is not created.
• An illegal value is specified for the environment setup file (includes a syntax
error).
• The environment setup file cannot be read.
The keys that can be specified for the environment setup file are explained below for
each section.
trace (trace section)
For trace (trace section), specify the name of the trace file that stores the trace level,
trace file size, and trace information. The following table describes the keys that can
be specified in the trace section.
42
2. Installation and Setup
Table 2-11: Keys that can be specified for trace
Key
Level
Value selectable as a string
0
No trace
1
Standard level
2
Detail level
3
Debug level
Size
0 or 1 to 65,535 (in kilobytes)
Explanation
Specify the trace level. If this key
specification is omitted, a trace
level of 1 is used. The trace volume
per command for each trace level is
as follows:
• When monitoring the
completion of InfoPackage or
process chains:
1 (standard level): 2.0
kilobytes
2 (detail level): 3.5 kilobytes +
(InfoPackage or process chain
execution time)/completion
monitoring interval) x 0.2
kilobytes
3 (debug level): 24.0 kilobytes
+ (InfoPackage or process
chain execution time)/
completion monitoring
interval) x 2.4 kilobytes
• When not monitoring the
completion of InfoPackage or
process chains:
1 (standard level): 2.0
kilobytes
2 (detail level): 3.5 kilobytes
3 (debug level): 24.0 kilobytes
Normally, select standard level.
The detail level or debug level
should be specified only if a failure
occurs. If you select no trace, no
information about the use of JP1/
AJS3 for EAP will be collected.
Specify the trace file size. If you
specify 0, the trace file size is 2
gigabytes. If this key specification
is omitted, the trace file size is
12,288 kilobytes.#1
To reduce the trace file size, delete
the created trace file and then
change the size.
43
2. Installation and Setup
Key
TargetFile
Value selectable as a string
Explanation
Windows:
Character string beginning with
(drive-name):\ or remote
resource name coded in
Universal Naming Convention
(UNC) format#2
UNIX:
Character string beginning with
Trace information about all
applications will be collected in the
specified file.
If you omit this key, a trace file is
created for each application in the
default directory.#3
/
#1
If you specify 12,288 kilobytes as the trace file size, the trace file can record at
least two days' worth of trace data when 100 jobs are executed per hour at trace
level 1 (default).
#2
The remote resource name expressed in UNC format is
\\computer-name\sharename, which is provided by Microsoft for networked
folder/file name specification purposes.
#3
For details about the default directory that stores the trace file, see A. Directory
List.
event (event section)
For event (event section) in Windows, specify whether or not to generate events that
are used in Windows application logs.
For event (event section) in UNIX, specify whether to generate syslog messages.
The following table describes the keys that can be specified in the event section.
Table 2-12: Keys that can be specified for an event
Key
ntevent
44
Value selectable as a string
YES or NO
Explanation
This entry can be made when you
are using Windows. Specify
whether to generate Windows
events. If this key specification is
omitted, YES is used as the event
generation condition.
2. Installation and Setup
Key
Value selectable as a string
YES or NO
Syslog
Explanation
This entry can be made when you
are using UNIX. Specify whether or
not to generate syslog messages. If
this key specification is omitted,
YES is used as the syslog message
generation condition.
command (command section)
For command (command section), specify the work directory for JP1/AJS3 for EAP,
the InfoPackage or process chain completion monitoring interval, and the time and
interval for attempting to retry connection in the event of a communication error. Also,
specify the codepage number to be used for character code conversion in the connected
Unicode version SAP system. The following table describes the keys that can be
specified in the command section.
Table 2-13: Keys that can be specified for command
Key
Value selectable as a
string
Explanation
WorkDir
Windows:
Character string
beginning with
(drive-name):\ or
remote resource name
coded in Universal
Naming Convention
(UNC) format
UNIX:
Character string
beginning with /
Enter a full pathname to specify the
work directory for InfoPackage control
function commands. The work
directory is set when you execute an
InfoPackage control function
command. If this key specification is
omitted, the current directory at the
time the command is executed is used.
(When JP1/AJS is used, the work
directory to be used for execution of a
JP1/AJS job#1 is used.)
MonitorInterval
1 to 65,535 (in seconds)
Specify the interval for monitoring the
completion of InfoPackage or a process
chain. This value is used if you do not
specify the interval for monitoring the
completion of InfoPackage or a process
chain on the jbwipsta command line
of JP1/AJS3 for EAP. If this key
specification is omitted, the
InfoPackage completion monitoring
interval value is 5 seconds.
45
2. Installation and Setup
Key
Value selectable as a
string
Explanation
RetryTime
0 to 65,535 (in minutes)
Specify a period of time during which
attempts are made to restore
connection with the SAP BW system if
a communication error occurs during
communication with the SAP BW
system. Repeated attempts to recover
the connection will be made until the
duration specified here elapses. If you
type a setting of 0 or omit this key
specification, the encountered error
will be reported immediately and no
attempt will be made to recover the
connection.
If the RetryTime key is specified
together with the RetryCount key, the
RetryTime key is ignored. If neither
the RetryTime key nor the
RetryCount key is specified, the
RetryCount key is valid#2.
To specify the interval between
reconnection retries, use the
RetryInterval key.
RetryCount
0 to 65,535 (times)
Specify the number of retries to restore
connection with the SAP BW system if
a communication error occurs during
communication with the SAP BW
system.
If you specify 0, no retry is attempted
and an error is reported immediately.
If you omit this key, 3 is assumed.
If the RetryCount key is specified
together with the RetryTime key, the
RetryTime key is ignored. If neither
the RetryCount key nor the
RetryTime key is specified, the
RetryCount key is valid#2.
To specify the interval between
connection retries, use the
RetryInterval key.
46
2. Installation and Setup
Key
Value selectable as a
string
Explanation
RetryInterval
1 to 65,535 (in seconds)
Specify the interval at which attempts
are made to restore connection with the
SAP BW system if a communication
error occurs during communication
with the SAP BW system. The value
specified here cannot exceed the value
set for RetryTime. If you omit to
specify this key, 180 seconds is set
automatically. If you do not specify
RetryTime or you set 0 for it, this
RetryInterval setting is invalid.
RequestMonitorTime
-1 or 0 to 65,535 (in
minutes)
Specify a period of time during which
InfoPackage request registrations are
monitored (request registration
monitoring time). If a request
registration does not complete within
the time specified by this value, the
InfoPackage completion monitoring
process ends abnormally. If you
specify -1, the request registration
monitoring time is the same as the
-time option (length of time during
which the completion is monitored) of
the jbwipsta command.
If you specify 0, the completion
monitoring for InfoPackage
immediately ends abnormally if the
request is not registered for the first
status query.
If you omit this key, -1 is assumed.
47
2. Installation and Setup
Key
Value selectable as a
string
Explanation
QMActionWaitTime
0 to 65,535 (in seconds)
Specify a time period (wait time)
during which InfoPackage ends
normally and then the job that executes
InfoPackage ends. In JP1/AJS3 for
EAP, the completion of QM action
(enabling processing of loaded data
that is executed after InfoPackage data
loading) or subsequent processing
(such as deletion of duplicated
requests) of InfoPackage cannot be
monitored. If you wish to execute a
subsequent job by waiting for the end
of that processing, set this wait time.
This value is used when you omit wait
time specification(-qmwait_time
option) in the jbwipsta command line
of JP1/AJS3 for EAP.
If this key specification is omitted, the
wait time is 0 seconds.
Codepage
0 to 9999 (unit: Codepage
number)
Specify the codepage number to be
used for character code conversion in
the connected Unicode version SAP
system.
When character data is sent or received
in English, this key does not need to be
specified.
#1
For details about the work path to use during execution of a JP1/AJS job, see the
manual Job Management Partner 1/Automatic Job Management System 3 System
Design (Configuration) Guide.
#2
The RetryCount key and the RetryTime key are mutually exclusive. The valid
key differs depending on the combination of the two keys as shown below:
Specified key
RetryCount key
Valid key
RetryTime key
RetryCount key
RetryTime key
Yes
Yes
Yes
No
Yes
No
Yes
No
No
Yes
No
Yes
48
2. Installation and Setup
Specified key
RetryCount key
No
Valid key
RetryTime key
No
RetryCount key
Yes
RetryTime key
No
Legend:
Yes: The key is specified or valid.
No: The key is not specified or not valid.
2.3.2 Setting the path
To use the InfoPackage or process chain control commands, it is convenient to define
the path for the command storage directory for each user.
„
Windows
With Windows, use the System Properties dialog box to define the environment
variable PATH.
To open the System Properties dialog box, from Control Panel, double-click the
System icon.
For the environment variable PATH, specify installation-folder\bwsta\program.
„
UNIX-based OSs
With UNIX, the system administrator must set the path in the system profile. Set
the path in the environment variable PATH. Set the environment variable PATH to
/opt/jp1_am_r3/bwsta/bin/.
2.3.3 Setting the language type (UNIX)
This setup need only be performed when you are using UNIX.
Messages can be output in English. To specify the language type, use environment
variable LANG. The following table describes the available character code sets and the
values that environment variable LANG may take.
Table 2-14: Available character codes and environment variable LANG values
OS
Available character code
Environment variable
LANG value
HP-UX
English
C
Solaris
English
C
AIX
English
C
49
2. Installation and Setup
Notes
• If any other value is set for LANG, English is used as the language type.
• If the JP1/AJS3 for EAP language environment and the SAP BW system language
environment do not have the same character codes, information that is obtained
from the SAP BW system may be displayed incorrectly.
2.3.4 Adding SAP BW system entries to the services file
Add the service name and the port number of the connection destination message
server into the services file when you connect a message server.
The following table describes the specification format for the service name and the
port number of the message server to be connected.
Table 2-15: Specification format for the service name and port number
Item
Message server
Service name
sapmssid#
Port number
Any/tcp
#
Specify the system ID of the SAP BW system for sid in sapmssid.
For example, if the system ID of the connection destination message server is IB1
and the port number of the message server is 3601/tcp, add the following entry
(service name, port number) to the services file:
sapmsIB1
3601/tcp
The following figure shows examples of additions to the SAP BW system entries.
Figure 2-9: Example of adding SAP BW system entries (services file)
2.3.5 Adding SAP BW system entries to the hosts file
Add the host names of connection destination application servers to the hosts file.
50
2. Installation and Setup
The following figure shows an example of an addition to the SAP BW system entries.
Figure 2-10: Example of adding SAP BW system entries (hosts file)
2.3.6 Steps to be completed before using the InfoPackage or
process chain control commands
The following describes the procedures that must be completed when you want to use
the -d option of a command or you want to set the command common argument
defaults. The procedures are not necessary if the -d option will not be used or
command common argument defaults will not be set.
(1) Making sure that the -d option for SAP BW destination information is usable
When using the -d option for the SAP BW destination information on the command
line of JP1/AJS3 for EAP, the saprfc.ini file must be created. Either of the
following saprfc.ini files (or both) will be used depending on the operation
method.
• saprfc.ini file created in the JP1/AJS3 for EAP work directory defined in the
environment setup file for InfoPackage or process chain control (or the current
directory if a command is executed when the JP1/AJS3 for EAP work directory
is not specified)
• saprfc.ini file specified by environment variable RFC_INI
Note that a saprfc.ini file search occurs in the following sequence:
• When saprfc.ini is specified by environment variable RFC_INI
Only the saprfc.ini file specified in environment variable RFC_INI is
searched for. The saprfc.ini file in the work directory of JP1/AJS3 for EAP is
not searched for.
• When saprfc.ini is not specified by environment variable RFC_INI
The saprfc.ini file in the JP1/AJS3 for EAP work directory defined in the
environment setup file is searched for.
The saprfc.ini file is usually created in the JP1/AJS3 for EAP work directory that
is defined in the environment setup file. To specify the saprfc.ini file for a specific
51
2. Installation and Setup
user, create the saprfc.ini file in the desired directory and specify the path for the
saprfc.ini file in environment variable RFC_INI.
After JP1/AJS3 for EAP is installed, a sample saprfc.ini file is stored in the
following directory:
• For Windows:
installation-folder\Sample\
• For UNIX-based OSs:
/opt/jp1_am_r3/sample
Copy the sample saprfc.ini file to the JP1/AJS3 for EAP working directory (or the
directory specified by environment variable RFC_INI) and edit the copy sample
saprfc.ini file as required. If you intend to use environment variable RFC_INI,
specify it in advance.
Use the full path for the saprfc.ini file to be specified in environment variable
RFC_INI.
• Typical specification of environment variable RFC_INI (Windows)
RFC_INI=C:\home\user01\saprfc.ini
• Typical specification of environment variable RFC_INI (UNIX)
RFC_INI=/home/user01/saprfc.ini
The following figure shows an example of the saprfc.ini file. For details about the
saprfc.ini file entries, see the R/3 manual or online help.
Figure 2-11: Typical saprfc.ini file
There is more than one type of saprfc.ini file specification method (the figure
above shows an example of type A). Edit the services file and hosts file as
appropriate for the type. For the specification items of each type and whether the
52
2. Installation and Setup
services file and hosts file must be edited, see the SAP BW manual or online help.
(2) Specifying the defaults for command common arguments (SAP BW
destination information and SAP BW logon information)
If the common arguments (SAP BW destination information and SAP BW logon
information) entry is omitted from the command line for JP1/AJS3 for EAP, an
r3defcon file must be created. This r3defcon file must be created in the home
directory that is specified for the user account.
Note
To use the r3defcon file in the Windows version, you need to specify the
HOMEDRIVE or HOMEPATH environment variable for job execution to identify the
home directory. Since these environment variables are not defined by default in
the execution environment of commands executed from JP1/AJS, you must
define them using environment variable items for job definition.
The following is a specification example of an environment variable (when the
r3defcon file is placed at C:\Documents and
Settings\Administrator):
HOMEDRIVE=C:
HOMEPATH=\Documents and Settings\Administrator
In those situations where Windows is employed with the NTFS file system, to prevent
leakage of r3defcon file information, you should specify a different home directory
for each user. With the FAT file system, however, you cannot protect the r3defcon
file information at the file level.
With UNIX, to prevent leakage of r3defcon file information, we recommend that you
define the access permissions for the r3defcon file so that only the user executing the
command can read the r3defcon file.
The following figure shows an example of creating the r3defcon file.
53
2. Installation and Setup
Figure 2-12: Example of creating an r3defcon file
The syntax for the r3defcon file is as follows:
[section]
key=string
• As the separator between section and key and between key and key, specify
one or more new-line codes.
• The character strings specified for section and key are case-insensitive.
• The key specifications within the same section can be in any order.
• If a semicolon (;) is placed at the beginning of a line, the line is handled as a
comment statement.
• When there are two or more section or key specifications that have the same
name, a KAJM0022-E message appears and command execution is terminated.
The keys that can be specified in the r3defcon file are explained below for each
section.
logon (logon section)
When omitting the SAP BW logon information specification, specify logon (logon
section). The following table describes the keys that can be specified in the logon
section.
54
2. Installation and Setup
Table 2-16: Keys that can be specified for logon
Key
Value selectable as a string
Explanation
Client
1- to 3-byte character string (The
character string must consist of
numerals only.)
Specify the SAP BW client number
for logging on to the SAP BW
system. Note that a 1- or 2-byte SAP
BW client number sent to the SAP
BW system is always converted to a
3-byte number.
If, for instance, the client number is
001, you can specify the number 1,
01, or 001. However, the 3-byte
client number 001 is always sent to
the SAP BW system.
User
1- to 12-byte character string
Specify the SAP user name for
logging on to the SAP BW system.
For details about the SAP users that
can be specified, see 2.3.9 Providing
a SAP user for InfoPackage control
or process chain control.
Passwd
1- to 8-byte character string
Specify the password that has been
assigned to the SAP user for logging
on to the SAP BW system.
Passwd2
1- to 40-byte character string
Specify the extended password that
was assigned to the SAP user for
logging in to the SAP BW system.
The extended password is a
password rule that was extended in
the SAP systems based on SAP
NetWeaver 7.0 and later. You can
specify up to 40 bytes, and
alphabetic characters are
case-sensitive.
Lang
For English: E
Specify the language type that can
be used with the SAP BW system.
The specifiable language type is
English.
Note
When you specify the logon section, be sure to specify all the keys (client,
user, passwd or passwd2, and lang). Note that you cannot specify passwd
and passwd2 at the same time. Specify one of them according to the availability
of the extended password.
address (address section)
When omitting the SAP BW destination information specification, specify address
55
2. Installation and Setup
(address section). The following table describes the keys that can be specified in the
address section.
Table 2-17: Keys that can be specified for address
Key
Value selectable as a string
Explanation
Host
1- to 100-byte character string
Specify the host name of a
destination SAP BW system.
Sysno
1- or 2-byte character string (The
character string must consist of
numerals only.)
Specify the host SAP system number
of a destination SAP BW system.
Dest
1- to 64-byte character string
Specify the destination (DEST value)
that is defined in the saprfc.ini
file.
Note
dest and host and sysno cannot be specified together. When specifying the
address section, specify dest only or specify host and sysno.
2.3.7 Creating the saprfc.ini file prior to SAP BW system custom job
execution (Windows)
This setup need be performed only when you are using Windows.
If you plan to use the saprfc.ini file to define an SAP BW system custom job, you
must create it in advance at the host where the jbwipsta command is to be executed.
For saprfc.ini file creation, see (1) in 2.3.6 above.
2.3.8 Specifying the action to take when InfoPackage ends with a
warning on the SAP BW system
To monitor the completion of InfoPackage, the SAP BW system requires a setting that
changes the signal to green or red when InfoPackage ends with an error. To set this
specification, open the Monitor window of the administrator workbench and choose
Settings -> Evaluation of requests (traffic light). In the opened dialog box, check
whether is judged to be successful (green lights) or is thought to have errors (red
lights) is selected in If no data is available in the system, the request and If warning
arise during processing, the request.
2.3.9 Providing a SAP user for InfoPackage control or process chain
control
To control InfoPackage or process chains, JP1/AJS3 for EAP uses RFC, which is the
SAP Corporation communication protocol used to execute the external management
interface defined on the SAP system side. For this reason you need to provide in
56
2. Installation and Setup
advance, on the SAP system side, a user to be used by JP1/AJS3 for EAP.
This section describes the user type, password, and roles that need to be provided on
the SAP system side.
(1) User type
For the user type, you can use dialog, system, communication, or service.
(2) Characters that can be specified in the password
To define the password, use numbers (from 0 to 9), alphabetic characters (a to z, A to
Z) and the following single-byte symbols:
[email protected]$%&/()=?'`*+~#-_.:{[]}<>|
(3) Required roles
The following roles are required in order for a SAP user to be able to perform
InfoPackage control or process chain control.
„
To use the InfoPackage control function:
To create a user who can execute InfoPackage, create a user based on the role
profile (S_BI-WHM_RFC) for the background user provided in the SAP BW
system.
„
To use the process chain control function:
A user who executes a process chain requires a role (S_RFC) to log on from an
external system in addition to the role to execute in the background each process
that comprises a process chain.
Assign the built-in role value (S_RFC_ALL) for the role (S_RFC) to log on from
an external system.
57
Chapter
3. Executing Background Jobs
Using JP1/AJS
This chapter describes the procedures for executing background jobs by using JP1/AJS
and explains the setup data required for JP1/AJS.
3.1 Executing R/3 jobs by using JP1/AJS
3.2 Executing InfoPackage or a process chain by using JP1/AJS
59
3. Executing Background Jobs Using JP1/AJS
3.1 Executing R/3 jobs by using JP1/AJS
This section explains the procedures for executing background jobs (R/3 jobs) by
using JP1/AJS and explains the setup data required for JP1/AJS.
3.1.1 Procedures for executing R/3 jobs
Before you can use JP1/AJS to execute R/3 jobs, you must perform the following tasks.
These tasks will vary depending on the OS of the machine on which JP1/AJS - View
is installed.
(1) If JP1/AJS - View is installed on a Windows machine
Procedure 1
Environment settings
If the machine on which JP1/AJS3 for EAP is installed runs Windows, manually
copy the following programs provided by JP1/AJS3 for EAP to the machine on
which JP1/AJS - View is installed:
• installation-folder\Program\jr3cjdfx.exe (definition program)
• installation-folder\Program\jr3cjdfx.hlp (help file)
• installation-folder\Program\jr3cjdfx.ini (initialization file)
Copy the above files to the same folder located anywhere on the machine on
which JP1/AJS - View is installed.
Procedure 2
Custom job registration
Procedure 3
Custom job definition
When the above procedures are completed and the JP1/AJS jobnet is started for
execution of the R/3 system custom job, the job is created in the R/3 system and then
executed.
(2) If JP1/AJS2 - View is installed on a machine that runs a UNIX-based OS
Set up jobs the same way as for ordinary jobs. For detailed information about jobs, see
the manual Job Management Partner 1/Automatic Job Management System 3
Operator's Guide.
3.1.2 Registering a custom job
Register the files as custom jobs in the Register Custom Job dialog box of JP1/AJS View.
60
3. Executing Background Jobs Using JP1/AJS
To register a custom job:
1.
Display the Register Custom Job dialog box in JP1/AJS - View.
2.
Choose the Add button.
The Set Properties of Custom Job dialog box is displayed.
3.
Register the custom job for the R/3 system.
Specify information in the entry boxes of the dialog box as described below.
Name
Specify a name from 1 to 8 bytes for the custom job of JP1/AJS3 for EAP.
61
3. Executing Background Jobs Using JP1/AJS
Comment
You can enter a comment from 1 to 40 bytes long. You cannot include slashes
(/) and blank characters in comments. You can omit Comment.
Defining program
Specify the pathname of the jr3cjdfx.exe program you have manually
copied for defining the custom job.
Note that you need not specify Defining program when you select UNIX in
Job Type.
Executing program
Specify installation_folder\Program\jr3bjsub.exe as the pathname of
the program for executing the custom job on the JP1/AJS - Agent (or JP1/
AJS - Manager) machine.
Note that you need not specify Executing program when you select UNIX
in Job Type.
Version
Specify 0600.
Class
Specify JP1AMR3.
Job Type
Select PC if the JP1/AJS - Agent (or JP1/AJS - Manager) machine on which
JP1/AJS3 for EAP is installed is a Windows machine. Select UNIX if it is a
UNIX machine.
4.
Choose the OK button.
For more details on how to register custom jobs, see the manual Job Management
Partner 1/Automatic Job Management System 3 Operator's Guide.
3.1.3 Defining a custom job
In the Jobnet Editor window of JP1/AJS, define the registered custom job in a jobnet.
To define a custom job for use with the R/3 system:
(1) Defining a custom job (PC job)
1.
Use the Jobnet Editor window of JP1/AJS to display the jobnet definition area.
2.
Select the Custom Jobs tab, and then drag the registered custom job to be used
with the R/3 system and drop it onto the jobnet definition area.
The registered custom job is added to the jobnet definition area and the Define
62
3. Executing Background Jobs Using JP1/AJS
Details - [Custom Job] dialog box is displayed.
3.
Specify the end judgment.
• If you want JP1/AJS to handle an abnormal job end (the return value of the
jr3bjsub command is 1) and other errors (the return value of the
jr3bjsub command is 2 or greater) as abnormal conditions:
Rule
Select Judgment by threshold.
Warning
Specify no value.
Abnormal
Specify 0.
• If you want JP1/AJS to issue a warning for an abnormal job end (the return
value of the jr3bjsub command is 1) and handle other errors (the return
value of the jr3bjsub command is 2 or greater) as abnormal conditions:
63
3. Executing Background Jobs Using JP1/AJS
Rule
Select Judgment by threshold.
Warning
Specify 0.
Abnormal
Specify 1.
4.
Choose the Details button.
The R/3 Job Definition dialog box is displayed.
5.
Define the attributes of the R/3 request.
Specify the following information in the dialog box.
• Specify the method for connecting to the R/3 system where the R/3 job will
be created.
• Define the R/3 job.
• Define the job steps.
• Specify the job release/completion monitoring settings.
• Specify the execution result output destination.
Note
When specifying the job cancellation time in the Define Details - [Custom
Job] dialog box, make sure that the setting is longer than the job cancellation
time specified by JP1/AJS3 for EAP.
6.
Choose the OK button.
For more details on how to define custom jobs, see the manual Job Management
Partner 1/Automatic Job Management System 3 Operator's Guide.
(2) Defining a custom job (UNIX job)
1.
Use the Jobnet Editor window of JP1/AJS to display the jobnet definition area.
2.
Select the Custom Jobs tab, and then drag the registered custom job to be used
with the R/3 system and drop it onto the jobnet definition area.
The registered custom job is added to the jobnet definition area and the Define
Details - [Custom Job] dialog box is displayed.
64
3. Executing Background Jobs Using JP1/AJS
3.
Define Command statement.
Specify command line parameters for the jr3bjsub command.
4.
Specify the end judgment.
• If you want JP1/AJS to handle an abnormal job end (the return value of the
jr3bjsub command is 1) and other errors (the return value of the
jr3bjsub command is 2 or greater) as abnormal conditions:
Rule
Select Judgment by threshold.
65
3. Executing Background Jobs Using JP1/AJS
Warning
Specify no value.
Abnormal
Specify 0.
• If you want JP1/AJS to issue a warning for an abnormal job end (the return
value of the jr3bjsub command is 1) and handle other errors (the return
value of the jr3bjsub command is 2 or greater) as abnormal conditions:
Rule
Select Judgment by threshold.
Warning
Specify 0.
Abnormal
Specify 1.
5.
Choose the OK button.
For more details on how to define custom jobs, see the manual Job Management
Partner 1/Automatic Job Management System 3 Operator's Guide.
(3) Specifying the method for connecting to the R/3 system
To specify the method for connecting to the R/3 system where the R/3 job will be
created, use the R/3 System page of the R/3 Job Definition dialog box.
The following figure shows the R/3 System page.
66
3. Executing Background Jobs Using JP1/AJS
Figure 3-1: R/3 System page - R/3 Job Definition dialog box
The items to be defined in the R/3 System page are explained below.
Definition items
Destination
Specify the method for connecting to the application server where the job will be
created. Use either of the following options to specify the application server to be
connected:
• Specify a specific application server.
• Use the destination specified in the saprfc.ini file.
Connect to a specific application server
Select this option when directly specifying the application server to be
connected to.
67
3. Executing Background Jobs Using JP1/AJS
Host name
Specify the host name of the application server (or SAP router) to be
connected to. A character string of 1 to 100 bytes can be entered for the host
name.
You can use host names in the following formats:
• Host name defined in the hosts file (for example, host1)
• IP address (for example, 123.123.123.123)
• SAP router address (for example, /H/hostname/S/port/H/host/
S/port/...)
For details about the SAP router address format, see the R/3 manual or online
help.
This item corresponds to the -h option of the jr3bjsub command.
System number
Specify the system number that identifies the target application server. A
character string of 1 or 2 bytes can be entered for the system number. Only
numerals can be used. Normally enter 00; however, some system
configurations may be assigned a different number. If you omit this option,
00 is assumed as the system number.
This item corresponds to the -s option of the jr3bjsub command.
Connect by saprfc.ini file
Select this option when you set the parameter that identifies the application
server to be connected to from the external file. You need to select this option
when you try to connect to the application server by balancing the workload.
For the saprfc.ini format and the details on available parameters, see the
R/3 manual or online help.
The saprfc.ini file must be in the work directory of the custom job or the
environment variable RFC_INI must define the fullpath name of the
saprfc.ini file.
You can also use the environment settings of JP1/R3 on the execution
destination to change the work directory.
For details about the work directory of the program for executing a custom
job, see the manual Job Management Partner 1/Automatic Job Management
System 3 Administration Guide.
Destination
Enter the value of the DEST key identifying the connection entry in the
68
3. Executing Background Jobs Using JP1/AJS
saprfc.ini file. A character string of 1 to 64 bytes can be entered for the
destination.
This item corresponds to the -d option of the jr3bjsub command.
Logon
Specify the user information used for the connection destination R/3 system. JP1/
AJS3 for EAP uses this information to log on to the R/3 system and execute jobs.
Client
Specify the number of the client assigned to the R/3 user who executes jobs.
The lengths of character strings you can specify are from 1 to 3 bytes. You
can only include digits in the character string. When an R/3 client number of
1 or 2 bytes is to be sent to the R/3 system, it is converted to 3 bytes.
For example, if the client number is 001, you can specify 1, 01, or 001.
When this client number is sent to the R/3 system, it is sent as 001.
This item corresponds to the -c option of the jr3bjsub command.
SAP user name
Specify the name of the R/3 user who executes jobs.
For details about the users who can be specified, see 2.2.9 Providing a SAP
user for job control.
When you do not explicitly specify the authorized user to define the job step,
the system executes the job step by using the permission specified in this
option.
The lengths of character strings you can specify are from 1 to 12 bytes. You
cannot include single-byte lower-case alphabetic characters in the user name.
This item corresponds to the -u option of the jr3bjsub command.
Password
For the R/3 user who executes jobs, enter the password or extended password
specified for the user name. A character string of 1 to 10 bytes can be entered
for the password. To use an extended password, select Use an extended
password.
The lengths of character strings you can specify are from 1 to 8 bytes for the
password, and from 1 to 40 bytes for the extended password. Entered
characters are marked with asterisks (*).
This item corresponds to the -p option of the jr3bjsub command if you use
the password, and the -p2 option of the jr3bjsub command if you use the
extended password.
69
3. Executing Background Jobs Using JP1/AJS
Using the extended password
To use the extended password, select the Use an extended password check
box. When you select this check box, confirm that the configuration at the
execution host is as follows:
• JP1/AJS3 for EAP 09-00 and later is installed.
• The availability of the extended password is set to ON by the jr3chrfc
command.
Language
Specify the language environment for executing jobs. You can use English.
Specify the following language supported by the R/3 system as the language
to be used.
• For English: E
(4) Defining an R/3 job
To create an R/3 job definition, use the R/3 Job Definition page of the R/3 Job
Definition dialog box.
The following figure shows the R/3 Job Definition page.
70
3. Executing Background Jobs Using JP1/AJS
Figure 3-2: Job Definition page - R/3 Job Definition dialog box
The items to be defined in the Job Definition page are explained below.
Definition items
Register job
Enter the setup data such as the job name and job step information necessary for
job registration.
A job consists of one or more job steps. ABAP report programs (ABAP programs)
or general programs (external programs) executable by the R/3 system can be
specified for the job steps.
The background jobs that can be registered on the R/3 system are those that can
be defined and executed using transaction code SM36.
Job name
Specify the job name to be registered in the R/3 system. The lengths of
71
3. Executing Background Jobs Using JP1/AJS
character strings you can specify are from 1 to 32 bytes. You cannot include
single-byte lower-case alphabetic characters in the job name.
This item corresponds to the -jn option of the jr3bjsub command.
Job class
Specify the job class (priority level of job execution) of the R/3 job to be
executed in the R/3 system. The available job classes are as follows:
• A - High
• B - Middle
• C - Low
Normally, specify C - Low. If you want to execute a job with a higher level
of priority, specify B - Middle. If you need to execute a job immediately
because of an emergency, specify A - High. The default is C - Low.
This item corresponds to the -class option of the jr3bjsub command.
Note
To specify A - High or B - Middle, JP1/AJS2 for EAP 07-50 or later must
be installed on the execution destination host and the XBP 2.0 interface must
be enabled in the connection destination R/3 system.
Defined job steps
Click Add, Delete, or Property to specify the job steps that constitute an R/
3 job. The programs specified as job steps (ABAP programs or external
programs) are executed in the order indicated in the Defined job steps
program list.
To change the program execution order, select the program you want to
move, and then click Up or Down.
• Add button
Use this button when adding a program as a job step. Clicking this
button opens the Job Step dialog box. In the dialog box, define the
program to be added.
• Delete button
Use this button when deleting a program from the Defined job steps
program list. You can delete the selected program from the program list.
• Property button
Use this button when referencing or updating the definitions of
programs listed in Defined job steps. Clicking this button opens the Job
Step dialog box for the selected program type.
72
3. Executing Background Jobs Using JP1/AJS
• Up button
Use this button to move the selected program up the execution order in
the Defined job steps program list.
• Down button
Use this button to move the selected program down the execution order
in the Defined job steps program list.
Define target host system
When you want to define the host of the application server that executes jobs,
select this check box, and then enter the host name.
If you do not select this check box, the R/3 system will distribute the
execution load of R/3 jobs among the application servers.
When you select this check box, the Define target application server check
box is cleared.
Define target host system is a job definition compatible parameter created
for Release 4.0 and earlier R/3 systems. To define jobs for Release 4.5 or
later R/3 systems, use Define target application server.
Note
If one of the following conditions is satisfied, and if you select the Define
target host system check box, the specification in the Host name field
becomes ineffective:
• Neither Release job as soon as possible nor Release job immediately
is selected as the release method in the Monitor dialog box.
• You have registered the job normally, but have failed to release the job.
In this case, no target host is assigned to the job registered on the R/3 system.
To execute the job on the target system, release the job by specifying the
target system using the -tgh or -tgs option in the jr3bjrel command. If
you release the job without specifying a target system using the jr3bjrel
command, the R/3 system will dynamically select the target system on which
the job will be executed.
Host name
Specify the host name of the application server that executes jobs.
From the list of host names displayed by the transaction SM51, select the
host name assigned to the application server that offers a background
processing service. Select one of the application servers that are running on
the specified host and designate it as the target system on which the job will
be executed.
73
3. Executing Background Jobs Using JP1/AJS
This item corresponds to the -tgh option of the jr3bjsub command.
Define target application server
To specify an application server or a job server group that executes the
created R/3 jobs, select the Define target application server check box. If
you do not specify an application server or a job server group in the text box,
the created R/3 jobs are distributed among the application servers for
execution.
When you select this check box, the Define target host system check box is
cleared.
Note
If either of the following conditions is satisfied, the server specified in the
Server name text box under the selected Define target application server
check box is invalid:
• If Release job as soon as possible or Release job immediately is not
selected as the release method in the Monitor dialog box
• If the job was successfully created but failed to be released
If either of these conditions applies, no execution destination server is set for
the jobs created on R/3.
To execute these jobs on a specific execution destination, use the -tgh
option or the -tgs option of the jr3bjrel command to specify the
execution destination and then release the jobs. If you release the jobs
without specifying an execution destination using the jr3bjrel command,
the execution destination for the jobs is dynamically selected by the R/3
system.
Server name
Specify the name of the application server or the job server group that
executes jobs. You can specify a character string of 1 to 20 bytes.
When you use an application server, you can specify one of the names
(upper-case and lower-case characters are differentiated) that are assigned to
the application servers for providing background processing services. These
application server names are listed by transaction SM51. When you use a job
server group, you can specify one of the names (upper-case and lower-case
characters are differentiated) of job server groups containing the application
servers that provide background processing services. These job server group
names are listed by transaction SM61.
This item corresponds to the -tgs option of the jr3bjsub command.
74
3. Executing Background Jobs Using JP1/AJS
Monitor job release and completion
Specify whether or not to release the job after you register the job, or whether or
not to monitor the completion of the released job.
• Set button
Use this button to browse or modify the existing settings in the Monitor
dialog box that prompts you to specify whether or not to release the job after
you register the job, or whether or not to monitor the completion of the
released job.
Output results
Specify the message that JP1/AJS3 for EAP (program for executing custom jobs)
outputs, or specify the method for obtaining logs of R/3 jobs whose termination
is monitored.
To browse or modify the existing settings, click the Set button on the right.
• Set button
Use this button to browse or modify the existing settings in the Output
Results dialog box that prompts you specify the method for obtaining
messages JP1/AJS3 for EAP outputs or log where the completion of the R/3
job is monitored.
(5) Defining job steps
For details about job step definition, use the Job Step dialog box. The Job Step dialog
box opens when you click the Add or Property button in the R/3 Job Definition dialog
box.
Figure 3-3 shows the Job Step dialog box for the ABAP program.
75
3. Executing Background Jobs Using JP1/AJS
Figure 3-3: Job Step dialog box (ABAP program)
Figure 3-4 shows the Job Step dialog box for the external program.
Figure 3-4: Job Step dialog box (External program)
The items to be defined in the Job Step dialog box are explained below.
Definition items
Job step
Define the program that is to be specified as the job step. You can define either an
ABAP program or an external program.
ABAP program
Select this option to define an ABAP program.
76
3. Executing Background Jobs Using JP1/AJS
External program
Select this option to define an external program.
Program
Specify the name of an ABAP program or an external program to be
specified as a job step. For an ABAP program, you can specify a character
string of 1 to 40 bytes. In an external program, you can enter a character
string of 1 to 128 bytes. You cannot use lower-case alphabetic characters for
ABAP programs.
This item corresponds to the -pa option of the jr3bjsub command (for
ABAP programs) and the -px option of the jr3bjsub command (for
external programs).
Argument
Specify the arguments of the ABAP program or the external program
specified in Program. For an ABAP program, you can specify a character
string of 1 to 14 bytes. For an external program, you can specify a character
string of 1 to 255 bytes. If the specified ABAP program or external program
does not have any arguments, you do not need to specify any. For ABAP
programs, you cannot use lower-case alphabetic characters.
This item corresponds to the -var option of the jr3bjsub command (for
ABAP programs) and the -arg option of the jr3bjsub command (for
external programs).
Authorized user
Specify the authorized user to be set when the ABAP program or the external
program specified in Program is executed. You can specify a character
string of 1 to 12 bytes for an ABAP program or an external program. The
default authorized user is the user who logs on to the R/3 system. You cannot
use lower-case alphabetic characters to specify an authorized user.
This item corresponds to the -auth option of the jr3bjsub command.
Language (for ABAP programs)
Use a single-byte alphabetic character to specify the language to be used
when ABAP programs are executed. You can use English. Specify the
following language supported by the R/3 system as the language to be used.
• For English: E
Output device (for ABAP programs)
Indicates the output destination of the execution results of the ABAP
program. To change the output device, click Change and use the Output
Parameters dialog box.
77
3. Executing Background Jobs Using JP1/AJS
Change button (for ABAP programs)
Click this button to open the Output Parameters dialog box to specify the
output destination of the execution results of the ABAP program and the
output method.
Target host system (for external programs)
Specify the name of the host that executes the specified external program.
A character string of 1 to 32 bytes can be entered for the target host system.
You can enter host names in the following formats:
• Host name defined in the hosts file (for example, host1)
• IP address (for example, 172.16.90.4)
This item corresponds to the -xpgtgh option of the jr3bjsub command.
(6) Defining the print method
To define the details about the method for printing the execution results of the ABAP
program, use the Output Parameters dialog box.
The Output Parameters dialog box opens when you click the Change button in the Job
Step dialog box (for ABAP programs).
The following figure shows the Output Parameters dialog box.
78
3. Executing Background Jobs Using JP1/AJS
Figure 3-5: Output Parameters dialog box
The items to be defined in the Output Parameters dialog box are explained below.
Definition items
Print parameters
Define the method for printing the execution results of the ABAP program.
Output device
Specify an execution result output device using the abbreviation of an output
device configured on the R/3 system. If you omit this option, the default
destination that the R/3 system defines is assumed.
This item corresponds to the -out option of the jr3bjsub command.
Number of copies
Specify the number of copies to be printed. The values you can specify are
from 1 to 255. The default value is 1.
79
3. Executing Background Jobs Using JP1/AJS
This item corresponds to the -cc option of the jr3bjsub command.
Spool request title
Specify the title of the spool request. You can specify a title of 1 to 68 bytes.
If you omit this item, the spool request title is blank.
This item corresponds to the -title option of the jr3bjsub command.
Note
To specify a title in Spool request title, JP1/AJS2 for EAP 07-50 or later
must be installed on the execution destination host and the XBP 2.0 interface
must be enabled in the connection destination R/3 system.
Authorization
To prevent the invalid operation of spool requests, you can specify an
authorized character string of 1 to 12 bytes.
The users, who have the permission for the spool action objects matching
with the authorized character string specified in this option, can request
spools.
This item corresponds to the -shwpwd option of the jr3bjsub command.
Print immediately
Select this check box to immediately send the execution results of the ABAP
program to the printer.
This item corresponds to the -ip option of the jr3bjsub command.
Set the spool retention period
Select this check box if you want to change the default spool period of the R/
3 system.
This item corresponds to the -rpd option of the jr3bjsub command.
Delete after printing
Select this check box to delete the execution results of the ABAP program
after printing. If printing succeeds, the R/3 system automatically deletes the
print requests associated with the spool requests.
When an error occurs, spool requests, print requests, and the associated logs
are kept in the system even if this option is selected.
This item corresponds to the -dp option of the jr3bjsub command.
Archiving mode
Specify a method for archiving the execution results of the ABAP program.
You can specify one of the following methods:
80
3. Executing Background Jobs Using JP1/AJS
• Print (default)
• Archive
• Print and archive
This item corresponds to the -armode option of the jr3bjsub command.
Output format
Specify the numbers of lines and columns or the format name for the output
format for the execution results of the ABAP program.
lines
Specify the number of lines on each page of the list. You can specify a
number from of 1 to 255. If you omit this option, the R/3 system assumes the
appropriate value.
When you select the By format name check box, the value specified in the
lines box is invalid.
This item corresponds to the -ln option of the jr3bjsub command.
columns
Specify the number of columns on each page of the list. You can specify a
number from 1 to 255. If you omit this option, the R/3 system assumes the
appropriate value.
When you select the By format name check box, the value specified in the
columns box is invalid.
This item corresponds to the -col option of the jr3bjsub command.
By format name
Specify the name of the desired output format. To do so, select the By format
name check box and specify a name in the text box on the right. You can
specify a character string of 1 to 16 bytes.
When you select this check box, the values specified in the lines and
columns boxes are invalid.
This item corresponds to the -fmt option of the jr3bjsub command.
Note
To specify a format name, JP1/AJS2 for EAP 07-50 or later must be installed
on the execution destination host and the XBP 2.0 interface must be enabled
in the connection destination R/3 system.
Cover Sheet button
Specify whether or not to print the SAP cover or selected-report cover, by
81
3. Executing Background Jobs Using JP1/AJS
browsing or modifying the existing settings in the Cover Sheet dialog box.
Archive parameters
Specify the following archive parameters.
Object type
Specify the object type of the archive document. The lengths of character
strings you can specify are from 1 to 10 bytes. If you select Archive or Print
and Archive as Archiving mode, you must fill in the Obj type field.
This item corresponds to the -objtyp option of the jr3bjsub command.
Document type
Specify the document type used to classify the archive document. The
lengths of character strings you can specify are from 1 to 10 bytes. If you
select Archive or Print and Archive as Archiving mode, you must fill in
the Doc type field.
This item corresponds to the -doctyp option of the jr3bjsub command.
Information
The left text box shows the ABAP program name. Specify the information
ID of the archive document. As well as the report name that generates the
print list displayed in the left text box, this information ID is registered as the
detailed information of the archive document. The lengths of character
strings you can specify are from 1 to 3 bytes. If you select Archive or Print
and Archive as Archiving mode, you must fill in the Information field.
This item corresponds to the -info option of the jr3bjsub command.
Text
Enter an explanation about the archive request.
You can enter a character string of 1 to 40 bytes. This text box is available
when you select Archive or Print and archive in the Archiving mode text
box. You can omit the Text box.
This item corresponds to the -text option of the jr3bjsub command.
Note
To enter an explanation in Text, JP1/AJS2 for EAP 07-50 or later must be
installed on the execution destination host and the XBP 2.0 interface must be
enabled in the connection destination R/3 system.
(7) Attaching a cover to the output results
You can add a SAP cover when printing the execution results of the ABAP program.
You define details of the SAP cover in the Cover dialog box.
82
3. Executing Background Jobs Using JP1/AJS
You can open the Cover dialog box by choosing Cover Sheet in the Output Parameter
dialog box.
The Cover dialog box contains the following definition items you specify.
Definition items
SAP cover sheet
Specify whether or not to print a SAP cover. You can select one of the following:
• Printer default (A SAP cover is printed depending on the settings for the
printer to be used)
• Print
• Not print
This item corresponds to the -sapcvr option of the jr3bjsub command.
Receiver
Enter the recipient name to be printed on the SAP page. The length of the
character string you can specify is from 1 to 12 bytes. You cannot include
single-byte lower-case alphabetic characters in the receiver name. If you specify
single-byte lower-case alphabetic characters, they are converted to upper-case
equivalents.
This item corresponds to the -receiver option of the jr3bjsub command.
Department
Enter the name of the department to be printed on the SAP cover.
You can specify a character string of 1 to 12 bytes. If you omit this item, the
department set in the profile of the user who is authorized to execute the ABAP
program is printed on the SAP cover.
This item corresponds to the -dpt option of the jr3bjsub command.
Note
To specify a name in Department, JP1/AJS2 for EAP 07-50 or later must be
installed on the execution destination host and the XBP 2.0 interface must be
enabled in the connection destination R/3 system.
Selection cover sheet
Print a selected-report cover describing execution conditions for the program.
This item corresponds to the -selcvr option of the jr3bjsub command.
(8) Specifying the job release/completion monitoring method
To specify the job release/completion monitoring method, use the Monitor dialog box.
83
3. Executing Background Jobs Using JP1/AJS
The Monitor dialog box opens when you click the Set button (for job release/
completion monitoring) in the R/3 Job Definition dialog box.
The following figure shows the Monitor dialog box (for job release/completion
monitoring).
Figure 3-6: Monitor dialog box
The items to be defined in the Monitor dialog box are explained below.
Definition items
Monitor job release and completion
Specify whether to release a job after you register the job, and whether to monitor
the completion of the released job.
Do not release job
Select this option when you only want to register the job without releasing
the job. Next time you release this job, be sure to release the job on the R/3
system.
Release job as soon as possible
Starts the job as soon as possible after you register the job. The system
immediately sets the start conditions, and the R/3 system starts the job if a
background process is available.
84
3. Executing Background Jobs Using JP1/AJS
To release the job, you must assign the permission (S_BTCH_JOB) for
operating the background job to the R/3 logged-on user and permit the
release operation.
This item corresponds to the -rs option of the jr3bjsub command.
Release job immediately
Immediately starts the registered job. If the system resource for executing the
job is not allocated on the system, release of the job fails and the job is left
registered.
To release the job, you must assign the permission (S_BTCH_JOB) for
operating the background job to the R/3 logged-on user and permit the
release operation.
This item corresponds to the -ri option of the jr3bjsub command.
Monitoring completion of released job
Select this check box to monitor the completion of a released job.
This item corresponds to the -wait option of the jr3bjsub command.
Include child jobs
Select Include child jobs to monitor the completion of all jobs, which
includes the child jobs that are generated during the execution of the target
job (completion monitoring of parent and child jobs).
This item corresponds to the -with_child option of the jr3bjsub
command.
Note
To select Include child jobs, JP1/AJS2 for EAP 07-50 or later must be
installed on the execution destination host, and the XBP 2.0 interface and the
parent and child function must be enabled in the connection destination R/3
system.
Set the query interval about job status
Select this check box to change the interval at which the R/3 system will be
inquired about the job status.
Monitor every [ ] seconds
Specify the interval at which the R/3 system will be queried about the job
status. You can specify 1 to 65,535 seconds.
This item corresponds to the -ival option of the jr3bjsub command.
85
3. Executing Background Jobs Using JP1/AJS
Set monitoring time limit
Select this check box to enter the monitoring time. If the R/3 job does not
stop within the specified monitoring time, execution of the custom job fails.
To release the job, you must assign the permission (S_BTCH_JOB) for
operating the background job to the R/3 logged-on user and permit the
release operation.
Monitor [ ] minutes
Specify the time for monitoring the job termination. You can specify 1 to
65,535 seconds. If no job termination monitoring time was specified,
monitoring continues indefinitely.
This item corresponds to the -time option of the jr3bjsub command.
Cancel R/3 job if timeout occurs during execution
Use this check box to cancel the executing R/3 job if the job does not
terminate in the specified monitoring time.
You cannot cancel an inactive job such as a released or ready job.
Alternatively, you cannot cancel a job that is executing an external program.
This item corresponds to the -cancel option of the jr3bjsub command.
(9) Specifying the execution result output destination
To specify the execution result output destination, use the Output Results dialog box.
The Output Results dialog box opens when you click the Set button (for execution
result output destination) in the R/3 Job Definition dialog box.
The following figure shows the Output Results dialog box (for execution result output
destination).
86
3. Executing Background Jobs Using JP1/AJS
Figure 3-7: Output Results dialog box
The items to be defined in the Output Results dialog box are explained below.
Definition items
Output results
Specify the method for obtaining the log of the messages JP1/AJS3 for EAP
outputs and the log of R/3 jobs whose termination are monitored.
Output standard messages to specified file
Click this check box when you want to save the standard output messages of
JP1/AJS3 for EAP to a specified file, and then enter the name of the
destination file. Messages with the information level indicating the
execution status of the program are output to the standard output. If the
specified file does not exit, it is newly created and messages are always
added in the file.
For details about the work directory of the program for executing the custom
job, see the manual Job Management Partner 1/Automatic Job Management
System 3 Administration Guide.
File (for standard output messages)
Use the full path to specify the name of the output destination file for storing
the standard output messages of JP1/AJS3 for EAP. You can enter a character
string of 1 to 259 bytes. You can include blank characters in the path.
If you do not specify the full path name for the destination file, the file is
created in the JP1/AJS3 for EAP work directory that is specified in the
environment setup file for job control. (If the JP1/AJS3 for EAP work
directory is not specified in the environment setup file, the file is created in
the work directory that is used when a JP1/AJS job is executed.)
87
3. Executing Background Jobs Using JP1/AJS
You can also write standard output messages to this file.
This item corresponds to the -so option of the jr3bjsub command.
Output standard error messages to specified file
Select this check box when you want to save the standard error output
messages of JP1/AJS3 for EAP to a specified file, and then enter the name of
the destination file. Messages with the caution and error level are output to
the standard error output. If the specified file does not exit, it is newly created
and messages are always added in the file.
If you use Jobnet Monitor of JP1/AJS2 to confirm the error status. deselect
this option.
For details about the work directory of the program for executing the custom
job, see the manual Job Management Partner 1/Automatic Job Management
System 3 Administration Guide.
File (for standard error output messages)
Use the full path to specify the name of the output destination file for storing
the standard error output messages of JP1/AJS3 for EAP. You can enter a
character string of 1 to 259 bytes. You can include blank characters in the
path.
If you do not specify the full path name for the destination file, the file is
created in the JP1/AJS3 for EAP work directory that is specified in the
environment setup file for job control. (If the JP1/AJS3 for EAP work
directory is not specified in the environment setup file, the file is created in
the work directory that is used when a JP1/AJS job is executed.)
You can also write standard output messages to this file.
This item corresponds to the -se option of the jr3bjsub command.
Output the R/3 job log to specified file
Select this check box when you want to obtain the log of an R/3 job which
ceased to be monitored, and then enter the name of the destination file. If the
specified file does not exit, it is newly created and messages are always
added in the file.
For details about the work directory of the program for executing the custom
job, see the manual Job Management Partner 1/Automatic Job Management
System 3 Administration Guide.
File (for R/3 job log)
Use the full path to specify the name of the output destination file for the R/
3 job log. You can specify a character string of 1 to 259 bytes. You can
include blank characters in the path.
88
3. Executing Background Jobs Using JP1/AJS
If you do not specify the full path name for the destination file, the file is
created in the JP1/AJS3 for EAP work directory that is specified in the
environment setup file for job control. (If the JP1/AJS3 for EAP work
directory is not specified in the environment setup file, the destination file is
created in the work directory that is used when a JP1/AJS job is executed.)
You can also write the R/3 job log to this file.
If you specify YES for the JoblogAddToStderr key of the Command
section of the environment settings file, you can output the R/3 job log to the
specified log and to the standard error output file at the same time. This
allows you to view the contents of the R/3 job log in the Execution Result
Details dialog box in the Jobnet Monitor window.
This item corresponds to the -jo option of the jr3bjsub command.
For details about the work directory that is used when JP1/AJS jobs are executed, see
the manual Job Management Partner 1/Automatic Job Management System 3 System
Design (Configuration) Guide.
89
3. Executing Background Jobs Using JP1/AJS
3.2 Executing InfoPackage or a process chain by using JP1/AJS
This section explains the procedures for executing InfoPackage or a process chain by
using JP1/AJS and explains the items that need to be set up for using JP1/AJS.
3.2.1 Procedures for executing InfoPackage or a process chain
Before you can use JP1/AJS to execute InfoPackage or a process chain, you must
perform the following tasks. These tasks vary depending on the OS of the machine on
which JP1/AJS - View is installed.
(1) If JP1/AJS - View is installed on a Windows machine
Procedure 1
Environment settings
If the machine on which JP1/AJS3 for EAP is installed runs Windows, manually
copy the following files provided by JP1/AJS3 for EAP to the machine on which
JP1/AJS - View is installed:
• installation-folder\Bwsta\Program\jbwcjdfx.exe (definition
program)
• installation-folder\Bwsta\Program\jbwcjdfx.hlp (help file)
• installation-folder\Bwsta\Program\jbwcjdfx.ini (initialization file)
Copy the above files to the same folder located anywhere on the machine on
which JP1/AJS - View is installed.
If the machine on which JP1/AJS3 for EAP is installed runs Windows and you
intend to link JP1/AJS3 for EAP with JP1/AJS2 - View 06-00 to 06-51, manually
copy the following files provided by JP1/AJS3 for EAP to
installation-folder-for-JP1/AJS2 - View\image\custom on the machine on
which JP1/AJS2 - View is installed:
• installation-folder\Bwsta\Image\CUSTOM_PC_JP1AMR3BW.gif
(Windows custom job icon)
• installation-folder\Bwsta\Image\CUSTOM_UX_JP1AMR3BW.gif
(UNIX custom job icon)
Procedure 2
Custom job registration
Procedure 3
Custom job definition
90
3. Executing Background Jobs Using JP1/AJS
When the above procedures are completed and the JP1/AJS jobnet is started to execute
the SAP BW system custom job, InfoPackage or a process chain in the SAP BW
system is executed.
(2) If JP1/AJS2 - View is installed on a machine that runs a UNIX-based OS
Set up jobs the same way as for ordinary jobs. For detailed information about jobs, see
the manual Job Management Partner 1/Automatic Job Management System 3
Operator's Guide.
3.2.2 Registering a custom job
Register the files as custom jobs in the Register Custom Job dialog box of JP1/AJS View.
To register a SAP BW system custom job:
1.
Display the Register Custom Job dialog box in JP1/AJS - View.
2.
Choose the Add button.
The Set Properties of Custom Job dialog box is displayed.
91
3. Executing Background Jobs Using JP1/AJS
3.
Register the custom job for the SAP BW system.
Specify information in the entry boxes of the dialog box as described below.
Name
Specify a name from 1 to 8 bytes for the custom job of JP1/AJS3 for EAP.
Comment
You can enter a comment from 1 to 40 bytes long. You cannot include slashes
(/) and blank characters in comments. You can omit Comment.
Defining program
Specify the pathname of the custom job definition program
(jbwcjdfx.exe) you have manually copied to JP1/AJS - View.
Note
You need not specify Defining program when you select UNIX in Job
Type.
Executing program
Specify installation-folder\Bwsta\Program\jbwipsta.exe as the
pathname of the program for executing the custom job on the JP1/AJS Agent (or JP1/AJS - Manager) machine on which JP1/AJS3 for EAP is
installed.
Note
You need not specify Executing program when you select UNIX in Job
Type.
92
3. Executing Background Jobs Using JP1/AJS
Version
Specify 0600.
Class
Specify JP1AMR3BW.
Job Type
Select PC if the JP1/AJS - Agent (or JP1/AJS - Manager) machine on which
JP1/AJS3 for EAP is installed is a Windows machine. Select UNIX if it is a
UNIX machine.
4.
Choose the OK button.
For more details on how to register custom jobs, see the manual Job Management
Partner 1/Automatic Job Management System 3 Operator's Guide.
3.2.3 Defining a custom job
In the Jobnet Editor window of JP1/AJS, define the custom job that you registered in
JP1/AJS in a jobnet.
To define a custom job for use with the SAP BW system:
(1) Defining a custom job (PC job)
1.
Display the jobnet definition area in the Jobnet Editor window of JP1/AJS.
2.
Select the Custom Jobs tab, and then drag the registered SAP BW system custom
job and drop it onto the jobnet definition area.
The SAP BW system custom job is added to the jobnet definition area and the
Define Details - [Custom Job] dialog box is displayed.
93
3. Executing Background Jobs Using JP1/AJS
3.
Specify the End judgment.
• If you want JP1/AJS to handle an abnormal end of InfoPackage or a process
chain (the return value of the jbwipsta command is 1) and other errors (the
return value of the jbwipsta command is 2 or greater) as abnormal
conditions:
Rule
Select Judgment by threshold.
Warning
Specify no value.
Abnormal.
Specify 0.
• If you want JP1/AJS to issue a warning for an abnormal end of InfoPackage
or a process chain (the return value of the jbwipsta command is 1) and
handle other errors (the return value of the jbwipsta command is 2 or
greater) as abnormal conditions:
Rule
94
3. Executing Background Jobs Using JP1/AJS
Select Judgment by threshold.
Warning
Specify 0.
Abnormal
Specify 1.
4.
Choose the Details button.
The SAP BW InfoPackage/Process Chain Definition dialog box is displayed.
5.
Specify the following information in the SAP BW InfoPackage/Process Chain
Definition dialog box.
• Specify the method for connecting to the SAP BW system containing
InfoPackage or a process chain to be started.
• Define InfoPackage or a process chain.
6.
Choose the OK button.
For more details on how to define custom jobs, see the manual Job Management
Partner 1/Automatic Job Management System 3 Operator's Guide.
(2) Defining a custom job (UNIX job)
1.
Display the jobnet definition area in the Jobnet Editor window of JP1/AJS.
2.
Select the Custom Jobs tab, and then drag the registered SAP BW system custom
job and drop it onto the jobnet definition area.
The SAP BW system custom job is added to the jobnet definition area and the
Define Details - [Custom Job] dialog box is displayed.
95
3. Executing Background Jobs Using JP1/AJS
3.
Define Command statement.
Define the command line for the jbwipsta command.
4.
Specify the End judgment.
• If you want JP1/AJS to handle an abnormal end of InfoPackage or a process
chain (the return value of the jbwipsta command is 1) and other errors (the
return value of the jbwipsta command is 2 or greater) as abnormal
conditions:
Rule
Select Judgment by threshold.
96
3. Executing Background Jobs Using JP1/AJS
Warning
Specify no value.
Abnormal
Specify 0.
• If you want JP1/AJS to issue a warning for an abnormal end of InfoPackage
or a process chain (the return value of the jbwipsta command is 1) and
handle other errors (the return value of the jbwipsta command is 2 or
greater) as abnormal conditions:
Rule
Select Judgment by threshold.
Warning
Specify 0.
Abnormal
Specify 1.
5.
Choose the OK button.
For more details on how to define custom jobs, see the manual Job Management
Partner 1/Automatic Job Management System 3 Operator's Guide.
(3) Specifying the method for connecting to the SAP BW system
To specify the method for connecting to the SAP BW system containing InfoPackage
or a process chain to be started, use the SAP BW System page of the SAP BW
InfoPackage/Process Chain Definition dialog box.
The following figure shows the SAP BW System page.
97
3. Executing Background Jobs Using JP1/AJS
Figure 3-8: SAP BW System page - SAP BW InfoPackage/Process Chain
Definition dialog box)
The items to be defined in the SAP BW System page are explained below.
Definition items
Destination
Specify the method for connecting to the application server in the SAP BW
system containing InfoPackage or a process chain to be started. Use either of the
following options to specify the application server to be connected:
• Specify a specific application server.
• Use the destination specified in the saprfc.ini file.
Connect to a specific application server
Select this option when directly specifying the application server to which
you want to connect.
98
3. Executing Background Jobs Using JP1/AJS
Host name
Specify the host name of the application server (or SAP router) to which you
want to connect. You can enter a character string of 1 to 100 bytes for the host
name.
You can use host names in the following formats:
• Host name defined in the hosts file
• IP address
• SAP router address
For details about the SAP router address format, see the R/3 manual or online
help.
This item corresponds to the -h option of the jbwipsta command.
System number
Specify the target system number on the SAP BW system. You can enter a
character string of 1 or 2 bytes for the system number. Only numerals can be
used. The default is 0.
This item corresponds to the -s option of the jbwipsta command.
Connect by saprfc.ini file
Select this option when you want to use the saprfc.ini file to connect to
the application server.
Destination
Specify the value that was specified for DEST in the saprfc.ini file. You
can enter a character string of 1 to 64 bytes for the destination.
This item corresponds to the -d option of the jbwipsta command.
Logon
Specify the logon information to be used for connecting to the application server
specified in Destination. You must also specify values in Client, SAP user
name, Password, and Language.
Client
Specify the client number of the logon destination SAP BW client. You can
enter a character string of 1 to 3 bytes for the client number. Only numerals
can be used. When a SAP BW client number of 1 or 2 bytes is to be sent to
the SAP BW system, it is converted to 3 bytes. For example, if the client
number is 001, you can specify 1, 01, or 001. However, when this client
number is sent to the SAP BW system, it is sent as the 3-byte client number
001.
99
3. Executing Background Jobs Using JP1/AJS
This item corresponds to the -c option of the jbwipsta command.
SAP user name
Specify the user name of the user who executes InfoPackage or a process
chain. InfoPackage or the process chain is executed with the specified user
name.
For details about the users who can be specified, see 2.3.9 Providing a SAP
user for InfoPackage control or process chain control.
You can enter a character string of 1 to 12 bytes for the user name. You
cannot include single-byte lower-case alphabetic characters in the user name.
This item corresponds to the -u option of the jbwipsta command.
Password
Enter the password or extended password for the user specified in SAP user
name who executes InfoPackage or a process chain. To use an extended
password, select the Use an extended password check box. The lengths of
character strings you can specify are from 1 to 8 bytes for the password and
from 1 to 40 bytes for the extended password. Entered characters are marked
with asterisks (*).
This item corresponds to the -p option of the jr3bjsub command if you use
the password, and the -p2 option of the jr3bjsub command if you use the
extended password.
Using the extended password
To use the extended password, select the Use an extended password check
box. When you select this check box, confirm that the configuration at the
execution host is as follows:
• JP1/AJS3 for EAP 09-00 and later is installed.
• The availability of the extended password is set to ON by the jr3chrfc
command.
Language
Enter a single-byte alphabetic character to specify the language to be used.
You can use English. Specify the following language supported by the SAP
BW system as the language to be used.
• For English: E
(4) Defining InfoPackage or a process chain
To define InfoPackage or a process chain, use the SAP BW InfoPackage or Process
Chain Definition page of the SAP BW InfoPackage/Process Chain Definition dialog
box.
100
3. Executing Background Jobs Using JP1/AJS
The following figure shows the SAP BW InfoPackage or Process Chain Definition
page.
Figure 3-9: SAP BW InfoPackage or Process Chain Definition page - SAP BW
InfoPackage/Process Chain Definition dialog box
The items to be defined in the SAP BW InfoPackage or Process Chain Definition
page are explained below.
Definition items
Start InfoPackage or process chain
Specify information about the InfoPackage or process chain to be started.
InfoPackage
Select this option to start InfoPackage.
process chain
Select this option to start a process chain.
101
3. Executing Background Jobs Using JP1/AJS
ID
Specify the ID of the InfoPackage or the process chain to be started. You can
enter a character string of 30 bytes (fixed) for InfoPackage and from 1 to 25
bytes for a process chain. You cannot specify lower-case alphabetic
characters in this text box.
This item corresponds to the -ip option or the -pc option of the jbwipsta
command.
Monitor InfoPackage or process chain completion
Specify information about completion monitoring when you want to monitor the
completion of the started InfoPackage or process chain. When you choose the
Reset button, the values specified in this box are replaced by the default values.
To monitor the completion of InfoPackage, the SAP BW system side requires a
setting that changes the signal to green or red when InfoPackage ends with an
error. For details about this setting, see 2.3.8 Specifying the action to take when
InfoPackage ends with a warning on the SAP BW system.
Monitoring completion of started InfoPackage or process chain
Select this option when you want to monitor the completion of the started
InfoPackage or process chain.
The completion of InfoPackage or a process chain is judged by acquiring the
following statuses from the SAP BW system:
• Monitor InfoPackage Completion
The InfoPackage request status that can be checked in the Monitors tree
of the transaction RSMON (Total and Technical status displayed in the
Status tab)
• Monitor Process Chain Completion
The process chain status that can be checked in the Log view window
of the transaction RSPC
This item corresponds to the -wait option of the jbwipsta command.
Set InfoPackage or process chain status monitoring interval
Select this check box when you want to specify an interval for querying the
SAP BW system about the status of InfoPackage or a process chain.
Monitor every [ ] seconds
Specify in seconds the interval for querying the SAP BW system about the
status of InfoPackage or a process chain. The specifiable range is from 1 to
102
3. Executing Background Jobs Using JP1/AJS
65,535. The default monitoring interval is the value specified in the
environment setup file. (If no value was specified in the environment setup
file or no environment setup file was created, 5 seconds is assumed.)
This item corresponds to the -ival option of the jbwipsta command.
Set monitoring time limit
Select this check box when you want to specify the length of time for
monitoring the completion of the started InfoPackage or process chain.
Monitor [ ] minutes
Specify in minutes the length of time for monitoring the completion of
InfoPackage or a process chain after it starts. The specifiable range is from 1
to 65,535. If no completion monitoring time is specified for InfoPackage or
the process chain, monitoring continues indefinitely.
This item corresponds to the -time option of the jbwipsta command.
Set the waiting period for after InfoPackage ends normally
Select this check box to set the length of time (wait time) between the normal
end of InfoPackage and the end of the job that executes InfoPackage.
Wait for [ ] seconds
Specify in seconds the length of time (wait time) between the normal end of
InfoPackage and the end of the job that executes InfoPackage. JP1/AJS3 for
EAP cannot monitor the completion of a QM action (enables the loaded data)
that is executed after loading of the InfoPackage data or the completion of
subsequent InfoPackage processing (such as deleting duplicated requests).
To execute a succeeding job after these types of processing, specify the wait
time here.
You can specify a value from 0 to 65,535. If you do not specify the wait time,
the number of seconds set for the QMActionWaitTime key (in the command
section) in the environment setup file is assumed.
This item corresponds to the -qmwait_time option of the jbwipsta
command.
103
Chapter
4. Commands
This chapter describes the JP1/AJS3 for EAP commands that are used for controlling
background jobs in the R/3 system and InfoPackage and process chains in the SAP BW
system.
Command formats
Command list
Common argument formats for various commands
105
Command formats
Command formats
The commands used with JP1/AJS3 for EAP and their formats are the same for
Windows and all versions of UNIX. Command execution on Windows is done from
the command prompt.
This section explains the headings used in the explanation of JP1/AJS3 for EAP
commands and the symbols used in the explanation of formats.
Headings in command explanations
This manual uses the following headings in explaining commands.
Format
Shows the command format. If two or more formats can be used for a command,
the Format 1, Format 2, etc., are used.
Description
Describes the functions of the command.
Arguments
Explains the command arguments (including options).
Return values
Shows the command return values and explains their meaning.
Precautions
Explains precautions to be taken when the command is used.
Supplement
Provides supplementary information.
Usage examples
Provides examples of how the command is used.
Syntax
The following summarizes the syntax of the JP1/AJS3 for EAP commands:
• When two or more options are specified, they can be specified in any order.
• If an unexpected option is specified, an error occurs.
Conventions used in format explanations
See Conventions in syntax explanations in Preface.
106
Command list
Command list
Commands used with JP1/AJS3 for EAP can be divided according to function as
follows:
• Commands used with the job control function
• Command used with the InfoPackage control function and the process chain
control function
• Common commands used with every control function
Table 4-1, Table 4-2, and Table 4-3 list the commands used with the various functions.
The commands are explained below in alphabetical order.
Table 4-1: Commands for the job control function
Function
Command name
Required execution authority
Cancels a background job.
jr3bjcan
None
Deletes a background job.
jr3bjdel
None
Releases a background job.
jr3bjrel
None
Acquires information regarding R/
3 system resources.
jr3bjrep
None
Displays information about a
background job.
jr3bjsho
None
Registers a background job.
jr3bjsub
None
Table 4-2: Command for the InfoPackage control function and the process chain
control function
Function
Starts InfoPackage or a process
chain.
Command name
jbwipsta
Required execution authority
None
107
Command list
Table 4-3: Common commands used by every control function
Function
Sets availability of the extended password
Command name
jr3chrfc
Required execution
authority
• Windows
user who has
Administrator
permissions#
• UNIX
superuser
#
If you have enabled the user account control function (UAC) of the OS, execute
the command at the command prompt using Administrator permissions.
Command usage precautions
The following are precautions on using commands for each type of OS.
„
Notes for Windows
Differences in command rules
The rules for JP1/AJS3 for EAP commands differ from in some respects
from those for Windows commands. When using the JP1/AJS3 for EAP
commands, keep in mind the following rule differences.
General rules for Windows commands
Rules for JP1/AJS3 for EAP
A slash (/) is used to separate options.
A hyphen (-) is used to separate options.
Alphabetic characters used in a specified option are
case-insensitive.
Alphabetic characters used in a specified option are
case-sensitive.
The common argument formats for commands are explained below.
108
Common argument formats for various commands
Common argument formats for various commands
This section explains the common argument formats: for the commands of the job
control function, and for the command of the InfoPackage control function and the
process chain control function.
(1) Common argument format for job control function commands
The following provides the detailed formats for R/3 destination information, R/3 logon
information, and redirection information. These formats are common to all job control
function commands.
R/3 destination information
The R/3 destination information is an argument for establishing a connection to the R/
3 system. The R/3 destination information format is explained below.
R/3 destination information
-h host-name [-s NN]|-d destination
The R/3 destination information options must be used as described below depending
on the method of connection to the R/3 system.
„
When connecting to the R/3 system using the specified host name
To connect to the R/3 system using the specified host name, use the format -h
host-name[-s NN].
-h host-name
Enter the R/3 system host name in the host-name position. Host names in the
following formats can be used:
- hosts address (e.g., r3host1)
- IP address (e.g., 123.123.123.123)
- SAP router address
For the SAP router address, see the R/3 manual or online help.
-s NN
The system number for R/3 system identification must be entered in the NN
position. A character string of 1 or 2 bytes can be entered. Only numerals can
be used. If this entry is omitted, system number 0 is automatically set.
„
When connecting to the R/3 system using the saprfc.ini file
To connect to the R/3 system using the saprfc.ini file, use the format -d
109
Common argument formats for various commands
destination.
-d destination
The DEST value specified in the saprfc.ini file must be entered in the
destination position. A saprfc.ini file search is conducted as follows. Be
sure that the destination has been entered in advance as the DEST value in the
saprfc.ini file.
When the saprfc.ini file is specified by environment variable RFC_INI
Only the saprfc.ini file specified in environment variable RFC_INI is
searched for. The saprfc.ini file in the work directory of JP1/AJS3 for
EAP is not searched for.
When the saprfc.ini file is not specified by environment variable
RFC_INI
The saprfc.ini file in the JP1/AJS3 for EAP work directory is searched
for.
„
When omitting R/3 destination information as part of the command line
If the R/3 destination information is not specified as part of the command line, all
options are omitted and the destination information (address section
information) specified in the r3defcon file will be used. Since the r3defcon
file must exist, create the r3defcon file beforehand in the home directory of the
user executing the command.
For the creation of the saprfc.ini file and r3defcon file, see 2. Installation and
Setup.
R/3 logon information
The R/3 logon information is an argument that specifies user information for logging
on to the R/3 system.
The R/3 logon information format is explained below.
R/3 logon information
-c R/3-client -u R/3-user-name {-p password | -p2 extended-password}
[-l language]
-c R/3-client
Specify the client number of an R/3 client that is valid for logon to the R/3 system.
A character string of 1 to 3 bytes can be entered for the client number
specification. Only numerals can be used.
Note that a 1- or 2-byte R/3 client number sent to the R/3 system is converted to
a 3-byte number.
110
Common argument formats for various commands
For example, if the client number is 001, you can specify 1, 01, or 001. However,
the 3-byte client number 001 is sent to the R/3 system.
-u R/3-user-name
Specify the name of an R/3 user that is valid in the R/3 system that you log on to.
For details about the R/3 users who can be specified, see 2.2.9 Providing a SAP
user for job control.
A character string of 1 to 12 bytes can be entered for the R/3 user name
specification.
R/3 system control will be executed under authority of this R/3 user.
-p password
Enter the password for the R/3 user that is specified by the -u option.
For details about the characters that can be specified for the password, see 2.2.9
Providing a SAP user for job control.
A character string of 1 to 8 bytes can be entered for the password.
-p2 extended-password
Specify an extended password that corresponds to the R/3 user specified by the
-u option.
For details about the characters that can be specified for the extended password,
see 2.2.9 Providing a SAP user for job control.
A character string of 1 to 40 bytes can be entered for the extended password.
-l language
Enter a single-byte alphabetic character to specify the language to be used. You
can use English. Specify the following language supported by the R/3 system as
the language to be used.
• For English: E
If the R/3 logon information is not specified as part of the command line, the logon
information (logon section information) specified by the r3defcon file is used. The
r3defcon file must therefore be created beforehand in the home directory of the user
executing the command.
For r3defcon file creation, see 2. Installation and Setup.
Redirection information
Use this argument to specify the standard output and standard error output files that
will be used when the command is being executed. The specification format is as
follows:
111
Common argument formats for various commands
-so standard-output-file-name
Specify a standard output file for command execution.
The lengths of character strings that can be specified as standard output file names
vary depending on whether the OS is Windows or a UNIX-based OS:
• For Windows:
The lengths of character string you can specify as standard output file names
are from 1 to 259 bytes.
• For a UNIX-based OS:
The lengths of character string you can specify as standard output file names
are from 1 to 255 bytes.
If you do not use the full path to specify the standard output file name, the file is
created in the work directory of JP1/AJS3 for EAP. (If the JP1/AJS3 for EAP
working directory is not available, the file will be created in the current directory.)
You can also write standard output messages for command execution in this file.
-se standard-error-output-file
Specify a standard error output file for command execution.
The lengths of character strings that can be specified as standard error output file
names vary depending on whether the OS is Windows or a UNIX-based OS:
• For Windows:
The lengths of character string you can specify as standard error output file
names are from 1 to 259 bytes.
• For a UNIX-based OS:
The lengths of character string you can specify as standard error output file
names are from 1 to 255 bytes.
If you do not use the full path to specify the standard error output file name, the
file is created in the work directory of JP1/AJS3 for EAP. (If the JP1/AJS3 for
EAP working directory is not available, the file will be created in the current
directory.)
You can also write standard error output messages for command execution in this
file.
(2) Argument formats for the command of the InfoPackage control
function and the process chain control function
The following provides the detailed formats for SAP BW destination information and
SAP BW logon information. These formats are applied to the command of the
112
Common argument formats for various commands
InfoPackage control function and the process chain control function.
SAP BW destination information
The SAP BW destination information is an argument for establishing a connection to
the SAP BW system. The detailed format for SAP BW destination information is
explained below.
SAP BW destination information
-h host-name [-s NN]|-d destination
The SAP BW destination information options must be used as described below
depending on the method of connection to the SAP BW system.
„
When connecting to the SAP BW system using the specified host name
To connect to the SAP BW system using the specified host name, use the format
-h host-name[-s NN].
-h host-name
Enter the SAP BW system host name in the host-name position. Host names
in the following formats can be used:
- hosts address (e.g., bwhost1)
- IP address (e.g., 123.123.123.123)
- SAP router address
For the format of the SAP router address, see the SAP BW manual or online
help.
-s NN
Enter the system number for identifying the SAP BW system in the NN
position. You can enter a character string of 1 or 2 bytes. Only numerals can
be used. If this entry is omitted, system number 0 is automatically set.
„
When connecting to the SAP BW system using the saprfc.ini file
To connect to the SAP BW system using the saprfc.ini file, use the format -d
destination.
-d destination
Specify the value specified for DEST in the saprfc.ini file in the
destination position. A saprfc.ini file search is conducted as follows.
Make sure that the destination has been entered in advance as the DEST value
in the saprfc.ini file.
When the saprfc.ini file is specified by environment variable RFC_INI
113
Common argument formats for various commands
Only the saprfc.ini file specified in environment variable RFC_INI is
searched for. The saprfc.ini file in the work directory of JP1/AJS3 for
EAP is not searched for.
When the saprfc.ini file is not specified by environment variable
RFC_INI
The saprfc.ini file in the JP1/AJS3 for EAP work directory is searched
for.
„
When omitting SAP BW destination information as part of the command line
If the SAP BW destination information is not specified as part of the command
line, all options are omitted and the destination information (address section
information) specified in the r3defcon file will be used. Since the r3defcon
file must exist, create the r3defcon file beforehand in the home directory of the
user executing the command.
For the creation of the saprfc.ini file and r3defcon file, see 2. Installation and
Setup.
SAP BW logon information
The SAP BW logon information is an argument that specifies user information for
logging on to the SAP BW system. The detailed format for SAP BW logon information
is explained below.
SAP BW logon information
-c SAP-BW-client -u SAP-BW-user-name {-p password | -p2
extended-password} [-l language]
-c SAP-BW-client
Specify the client number of a SAP BW client that is valid for logon to the SAP
BW system. You can enter a character string of 1 to 3 bytes for the client number.
Only numerals can be used. Note that a 1- or 2-byte SAP BW client number sent
to the SAP BW system is converted to a 3-byte number.
If, for instance, the client number is 001, you can enter 1, 01, or 001. However,
when this client number is sent to the SAP BW system, it is sent as the 3-byte
client number 001.
-u SAP-BW-user-name
Specify the name of a SAP BW user that is valid for logon to the SAP BW system.
For details about the SAP BW users who can be specified, see 2.3.9 Providing a
SAP user for InfoPackage control or process chain control.
You can enter a character string of 1 to 12 bytes for the user name.
SAP BW system control will be executed under authority of this SAP BW user.
114
Common argument formats for various commands
-p password
Enter the password for the SAP BW user that is specified by the -u option.
For details about the characters that can be specified for the password, see 2.3.9
Providing a SAP user for InfoPackage control or process chain control.
You can enter a character string of 1 to 8 bytes for the password.
-p2 extended-password
Specify an extended password that corresponds to the SAP BW user specified by
the -u option.
For details about the characters that can be specified for the extended password,
see 2.3.9 Providing a SAP user for InfoPackage control or process chain control.
You can enter a character string of 1 to 40 bytes for the extended password.
-l language
Enter a single-byte alphabetic character to specify the language to be used. You
can use English. Specify the following language supported by the SAP BW
system as the language to be used.
• For English: E
If the SAP BW logon information is not specified as part of the command line, the
logon information (logon section information) specified by the r3defcon file is
used. The r3defcon file must therefore be created beforehand in the home directory
of the user executing the command.
For the creation of the r3defcon file, see 2. Installation and Setup.
115
jbwipsta
jbwipsta
Format 1
[SAP-BW-destination-information]
[SAP-BW-logon-information]
{-ip InfoPackage-ID | -pc process-chain-ID}
[-wait [-time monitoring-time]
[-ival monitoring-interval]
[-qmwait_time wait-time]]
jbwipsta
Format 2
jbwipsta -help
Description
Starts InfoPackage or a process chain defined beforehand on the SAP BW system.
• To start InfoPackage
When InfoPackage is successfully started, the SAP BW system assigns a request
number to identify the InfoPackage request. This request number is output to the
standard output as part of a message.
The user can use the request number to check the status of InfoPackage with the
SAP front-end software.
• To start a process chain
When a process chain is successfully started, the SAP BW system assigns a log
ID to identify the execution log of the process chain. This log ID is output to the
standard output as part of a message. The user can use the log ID and the SAP
front-end software to check the status of the process chain and the execution log.
Arguments
„ SAP-BW-destination-information
Specify the SAP BW system where the InfoPackage or the process chain to be started
is registered. For details about the format of SAP BW destination information, see (2)
Argument formats for the command of the InfoPackage control function and the
process chain control function.
„ SAP-BW-logon-information
Specify the logon information that is valid in the SAP BW system where the
InfoPackage or the process chain to be started is registered. For details about the
format of SAP BW logon information, see (2) Argument formats for the command of
116
jbwipsta
the InfoPackage control function and the process chain control function.
„ -ip InfoPackage-ID
Specify the ID of the InfoPackage to be started. You can enter a character string of 30
bytes (fixed) for the InfoPackage ID.
You must specify either the -ip option or the -pc option. You cannot specify both
simultaneously.
„ -pc process-chain-ID
Specify the ID of the process chain to be started. You can specify a character string of
1 to 25 bytes.
You must specify either the -ip option or the -pc option. You cannot specify both
simultaneously.
„ -wait
This argument monitors the started InfoPackage or process chain until its completion
(until InfoPackage or process chain execution ends, commands cannot be executed
from the command line).
The completion of InfoPackage or the process chain is evaluated by acquiring the
following statuses from the SAP BW system.
• Monitoring of InfoPackage Completion
The InfoPackage request status that can be checked in the Monitors tree of the
transaction RSMON (Total and Technical statuses displayed in the Status tab)
• Monitoring of Process Chain Completion
The process chain status that can be checked in the Log view window of the
transaction RSPC
„ -time monitoring-time
Specify the length of time to monitor the completion of InfoPackage or a process chain
(in minutes). The completion of InfoPackage or the process chain is monitored for the
specified length of time. Make sure that this monitoring time setting is greater than the
monitoring interval value that is specified by the -ival option. The specifiable range
for the monitoring time is from 1 to 65,535. If the -time option is omitted, there is no
limit on the monitoring time.
If InfoPackage or the process chain does not end within the specified monitoring time,
InfoPackage or process chain monitoring results in a timeout error and the command
ends regardless of the status of InfoPackage or the process chain.
The -time option is valid when the -wait option is specified.
117
jbwipsta
„ -ival monitoring-interval
Specify the interval in seconds at which InfoPackage or a process chain is to be
monitored. InfoPackage or a process chain can be monitored at the specified
monitoring interval until InfoPackage or the process chain ends (InfoPackage or
process chain polling monitoring). The specifiable range for the monitoring interval is
from 1 to 65,535. If a monitoring interval is omitted when the -ival option is
specified, the monitoring interval is 5 seconds.
The default monitoring interval of 5 seconds can be changed in the environment setup
file.
The -ival option is valid when the -wait option is specified.
„ -qmwait_time wait-time
Specify the length of time (wait time in seconds) between the normal end of
InfoPackage and the end of the job that executes the InfoPackage. JP1/AJS3 for EAP
cannot monitor the completion of a QM action (enables the loaded data) that is
executed after loading of the InfoPackage data or the completion of the subsequent
processing of InfoPackage (such as deleting duplicated requests). To execute a
succeeding job after these types of processing, specify the wait time here. You can
specify a value from 0 to 65,535. If you omit the -qmwait_time option, the number
of seconds set for the QMActionWaitTime key (command section) in the
environment setup file is assumed.
The -qmwait_time option is valid when the -ip and -wait options are specified.
„ -help
This argument provides information on using the command.
Return values
„
When the -wait option is not specified
0
InfoPackage or a process chain was successfully started.
Integer of 1 or more
InfoPackage or a process chain was not started.
„
When the -ip and -wait options are specified
0
InfoPackage ended normally.
1
InfoPackage ended abnormally.
118
jbwipsta
2
Timeout occurred before InfoPackage completion was detected.
Integer of 3 or more
The command ended abnormally (InfoPackage startup failed or completion
monitoring failed).
„
When the -pc and -wait options are specified
0
The process chain ended normally.
1
The process chain ended abnormally or forcibly.
2
A timeout error occurred before process chain completion was detected.
Integer of 3 or more
The command ended abnormally (process chain startup failed or completion
monitoring failed).
Precautions
„
When starting InfoPackage
• To start InfoPackage using this command, you must define the InfoPackage
in SAP BW beforehand and confirm that it operates normally.
• To be able to start InfoPackage using this command, you must enter a
definition beforehand that enables InfoPackage to be started by background
processing. To do so, select background processing in the definition of the
InfoPackage scheduler and set immediate execution as the startup condition
for starting InfoPackage in the background.
• To monitor the completion of InfoPackage using this command, you need to
specify that the signal color changes to blue or red when InfoPackage ends
with a warning. To do so, open the Monitor window of the administrator
work bench, and choose Settings -> Evaluation of requests (traffic lights).
In the opened dialog box, select is judged to be successful (green lights) or
is thought to have errors (red lights) in If no data is available in the
system, the request and If warning arise during processing, the request.
„
When starting a process chain
• To start a process chain using this command, you must define the process
chain in SAP BW beforehand and confirm that it operates normally.
119
jbwipsta
• To start a process chain using this command, you must define the process
chain so it can be immediately executed from a non-SAP BW system. To do
so, in the startup process of the process chain, select Start Using Meta
Chain or API.
• When JP1/AJS re-executes a job that executes a process chain, the process
chain is re-executed from the beginning, not from the process that has failed.
Therefore, if you want JP1/AJS to re-execute jobs that execute process
chains, we recommend that you create each process chain in the smallest
re-executable unit as possible.
Usage examples
„
Start InfoPackage under the following conditions:
• SAP BW destination information is specified (host name: bw20b01, system
number: 00).
• SAP BW logon information is specified (client number: 100, user name:
JP1, password: bw2001, language: E).
• InfoPackage is specified (InfoPackage ID:
ZPAK_54QRO40UDA09WUQDLD92RSYRL).
• InfoPackage completion is to be monitored (monitoring time: 10 minutes,
monitoring interval: 10 seconds).
To start InfoPackage under the above conditions, make sure that the jbwipsta
command line is specified as follows:
jbwipsta -h bw20b01 -s 00 -c 100 -u JP1 -p bw2001 -l E
-ip ZPAK_54QRO40UDA09WUQDLD92RSYRL -wait -time 10 -ival 10
„
Start the process chain under the following conditions:
• SAP BW destination information is specified (host name: bw35001, system
number: 00).
• SAP BW logon information is specified (client number: 100, user name:
JP1, password: bw35001, language: E).
• A process chain is specified (process chain ID: ZPC_HRCALCMNTH)
• Process chain completion is to be monitored (monitoring time: 30 minutes,
monitoring interval: 5 seconds).
To start the process chain under the above conditions, make sure that the
jbwipsta command line is specified as follows:
jbwipsta -h bw35001 -s 00 -c 100 -u JP1 -p bw35001 -l E
-pc ZPC_HRCALCMNTH -wait -time 30 -ival 5
120
jr3bjcan
jr3bjcan
Format 1
jr3bjcan [R/3-destination-information]
[R/3-logon-information]
[redirection-information]
-jn job-name
[-jc job-count]
[-user SAP-user-name]
Note
If the character string for the argument specification contains a space, enclose the
argument with double quotation marks (").
Format 2
jr3bjcan -help
Description
Cancels a background job while an ABAP program job step is active (being executed).
The jr3bjcan command ends abnormally if an attempt is made to cancel a job in the
following states:
• Execution of the job has not started (the job is in the scheduled state).
• The job that is specified to start execution is still waiting for execution (the job is
in the released or ready state).
• The job has ended (either finished or terminated).
• The job is active and an external program job step is currently being executed.
When the jr3bjcan command ends normally, the job being executed by the R/3
system is placed in the terminated state.
Arguments
„ R/3-destination-information
Specify the R/3 system where the job to be canceled exists. For details about the format
of R/3 destination information, see (1) Common argument format for job control
function commands.
„ R/3-logon-information
Specify logon information that is valid in the R/3 system where the job to be canceled
121
jr3bjcan
exists. For details about the format of R/3 logon information, see (1) Common
argument format for job control function commands.
„ redirection-information
Specify standard output and standard error output files for command execution. For
details about the format of redirection information, see (1) Common argument format
for job control function commands.
„ -jn job-name
Specify the job name of the job to be canceled. A character string of 1 to 32 bytes can
be entered for the job name specification. If there are duplicate job names in the
specified R/3 system, enter the job count with the -jc option to specify the job.
Note that you must specify the -jn option.
„ -jc job-count
To differentiate jobs having the same name, specify the job count. If the job count
specification is omitted, all the jobs having the same name are canceled.
„ -user SAP-user-name
This argument cancels only the jobs that are specified by the -jn option and owned by
the specified SAP user. A character string of 1 to 12 bytes can be entered for the SAP
user name specification.
„ -help
This argument provides information on using the command.
Return values
0
All the specified jobs were successfully canceled.
Integer of 1 or more
The specified jobs were not canceled successfully.
Usage examples
„
Canceling job R3JOB1 of user R3USER1
The conditions are as follows:
• The saprfc.ini file will be used (-d R3SERV1).
• R/3 logon information will be specified (-c 001 -u R3USER1 -p
HT0110).
• The job count will be specified (-jc 15520501).
122
jr3bjcan
• The standard output file and standard error output file will be created in the
directory specified by the environment setup file (-so STDOUT1 -se
STDERR1).
To cancel job r3job1 of user r3user1 under the above conditions, specify the
jr3bjcan command line as follows:
jr3bjcan -d R3SERV1 -c 001 -u R3USER1 -p HT0110 -jn R3JOB1 -jc 15520501 -user
R3USER1 -so STDOUT1 -se STDERR1
123
jr3bjdel
jr3bjdel
Format 1
jr3bjdel [R/3-destination-information]
[R/3-logon-information]
[redirection-information]
-jn job-name
[-jc job-count]
[-user SAP-user-name]
Note
If the character string for the argument specification contains a space, enclose the
argument with double quotation marks (").
Format 2
jr3bjdel -help
Description
Deletes a background job on the R/3 system.
The jr3bjdel command ends abnormally if an attempt is made to delete an active or
ready job.
This command can act on a job that is in one of the following states:
• Execution of the job has not started (the job is in the scheduled state).
• The job that is specified to start execution is still waiting for execution (the job is
in the released state).
• The job has ended (either finished or terminated).
Arguments
„ R/3-destination-information
Specify the R/3 system where the job to be deleted exists. For details about the format
of R/3 destination information, see (1) Common argument format for job control
function commands.
„ R/3-logon-information
Specify logon information that is valid in the R/3 system where the job to be deleted
exists. For details about the format of R/3 logon information, see (1) Common
argument format for job control function commands.
124
jr3bjdel
„ redirection-information
Specify standard output and standard error output files for command execution. For
details about the format of redirection information, see (1) Common argument format
for job control function commands.
„ -jn job-name
Specify the job name of the job to be deleted. A character string of 1 to 32 bytes can
be entered for the job name specification. If there are duplicate job names in the
specified R/3 system, enter the job count with the -jc option to specify the job.
Note that you must specify the -jn option.
„ -jc job-count
To differentiate jobs having the same name, specify the job count. If the job count
specification is omitted, all the jobs having the same name are deleted.
„ -user SAP-user-name
This argument deletes only the jobs that are specified by the -jn option and owned by
the specified SAP user. A character string of 1 to 12 bytes can be entered for the SAP
user name specification.
„ -help
This argument provides information on using the command.
Return values
0
All the specified jobs were successfully deleted.
Integer of 1 or more
The specified jobs were not deleted successfully.
Usage examples
„
Deleting job R3JOB1 of user R3USER1
The conditions are as follows:
• The saprfc.ini file will be used (-d R3SERV1).
• R/3 logon information will be specified (-c 001 -u R3USER1 -p
HT0110).
• The job count will be specified (-jc 15520501).
• The standard output file and standard error output file will be created in the
directory specified by the environment setup file (-so STDOUT1 -se
STDERR1).
125
jr3bjdel
To delete job R3JOB1 of user R3USER1 under the above conditions, specify the
jr3bjdel command line as follows:
jr3bjdel -d R3SERV1 -c 001 -u R3USER1 -p HT0110 -jn R3JOB1 -jc 15520501 -user
R3USER1 -so STDOUT1 -se STDERR1
126
jr3bjrel
jr3bjrel
Format 1
jr3bjrel [R/3-destination-information]
[R/3-logon-information]
[redirection-information]
-jn job-name
[-jc job-count [-wait [-time monitoring-time [-cancel]]
[-ival monitoring-interval]
[-jo R/3-job-log-filename]
[-with_child]]]
[{-tgh target-host|-tgs target-server}]
[{-rs|-ri}]
[-user SAP-user-name]
Note
If the character string for the argument specification contains a space, enclose the
argument with double quotation marks (").
Format 2
jr3bjrel -help
Description
Releases a job created in the R/3 system.
If the -rs and -ri option specifications are omitted, the created job will be released
as soon as possible. When the jr3bjrel command ends normally, the job status in
the R/3 system changes to the released state. If a job is released just after system
resources needed to execute the job are allocated, the job is said to be released as soon
as possible.
The following jobs can be released by the jr3bjrel command:
• Jobs that are created for the R/3 system without using the -rs or -ri option of
the jr3bjsub command
• Jobs registered as scheduled within the R/3 system
Arguments
„ R/3-destination-information
Specify the R/3 system where the job to be released exists. For details about the format
of R/3 destination information, see (1) Common argument format for job control
function commands.
127
jr3bjrel
„ R/3-logon-information
Specify logon information that is valid in the R/3 system where the job to be released
exists. For details about the format of R/3 logon information, see (1) Common
argument format for job control function commands.
„ redirection-information
Specify standard output and standard error output files for command execution. For
details about the format of redirection information, see (1) Common argument format
for job control function commands.
„ -jn job-name
Specify the job name of the job to be released. A character string of 1 to 32 bytes can
be entered for the job name specification. If there are duplicate job names in the
specified R/3 system, enter the job count with the -jc option to specify the job.
Note that the -jn option specification cannot be omitted.
„ -jc job-count
To differentiate jobs having the same name, specify the job count. If the job count
specification is omitted, all the jobs having the same name are released. When using
the -wait option for monitoring job completion, be sure to specify the job count.
„ -wait
This argument performs job monitoring until execution of the released job ends (until
job execution ends, commands cannot be executed from the command line). The
-wait option is valid when the -rs or -ri option is specified.
„ -time monitoring-time
Specify the duration of job completion monitoring in minutes. Job completion will be
monitored for the specified period of time. Make sure that this monitoring time setting
is greater than the monitoring interval value that is specified by the -ival option. The
specifiable range for monitoring time is from 1 to 65,535. If the -time option
specification is omitted, there is no limit on the monitoring time.
When the -with_child option is specified, the completion of all jobs, including the
child jobs, is monitored during this time.
If the job does not end within the specified monitoring time, a job monitoring timeout
that terminates the command without regard to the job status occurs.
The -time option is valid when the -wait option is specified.
„ -cancel
This argument cancels a job having the job count specified by the -jc option if it does
not end within the time specified by the -time option. Note that this argument works
only on an active job (job currently being executed). It does not cancel jobs under the
128
jr3bjrel
following conditions:
• The job whose completion is being monitored is not active.
• An external program job step is being executed while the job whose completion
is being monitored is active.
When the -with_child option is specified, all jobs, including the child jobs, are
canceled.
If the -cancel option is not specified, job execution continues as is in the R/3 system.
The -cancel option is valid when the -time option is specified.
„ -ival monitoring-interval
Specify the interval in seconds at which a job is to be monitored. Job monitoring can
be performed at the specified monitoring interval until the job ends (job polling
monitoring). The specifiable monitoring interval range is from 1 to 65,535. If a
monitoring interval is omitted when the -ival option is specified, the monitoring
interval is 5 seconds.
The default monitoring interval of 5 seconds can be changed in the environment setup
file.
The -ival option is valid when the -wait option is specified.
„ -jo R/3-job-log-filename
Specify the destination of the R/3 job log output. The R/3 job log is acquired when job
execution ends (when the return value is 0 or 1 and the -wait option is specified). The
length of the character string for the R/3 job log filename varies depending on whether
Windows or UNIX is used.
• When Windows is used
A character string of 1 to 259 bytes can be entered for the R/3 job log filename.
• When UNIX is used
A character string of 1 to 255 bytes can be entered for the R/3 job log filename.
If you do not use the full path to specify the name of the R/3 job log file, the file is
created in the work directory of JP1/AJS3 for EAP. (If the JP1/AJS3 for EAP work
directory is not defined, the file will be created in the current directory.)
R/3 job log output is in write-date write-time message-code (message class and
message number) message-text format.
You can also write the R/3 job log to this file.
If you specify YES for the JoblogAddToStderr key of the Command section of the
environment settings file, you can output the R/3 job log to the specified log and to
standard error at the same time.
129
jr3bjrel
When the -with_child option is specified, the log of all jobs that are finished or
terminated is acquired when the completion monitoring of all jobs, including the child
jobs, ends (includes time out errors).
If the -jo option specification is omitted, the R/3 job log is not output to the JP1/AJS3
for EAP system.
„ -with_child
This argument monitors the completion of all jobs, including the child jobs that are
generated during the execution of the target job (completion monitoring of parent and
child jobs). The target child jobs are those that are detected when the job being
monitored for its completion is finished or terminated. A maximum of 100 jobs can be
monitored for their completion regardless of the generation numbers of the child jobs.
If the number of jobs to be monitored for completion exceeds the maximum limit, a
KAJM1872-W message appears. The completion monitoring then continues for the
jobs that can be monitored for their completion and the system returns 1, indicating
that the result of at least one job cannot be checked.
If a job being monitored for its completion is deleted, a KAJM1837-W message or a
KAJM1871-W message appears. The completion monitoring continues for other
target jobs and the system returns 1, indicating that the result of at least one job cannot
be checked.
If the system detects a child job that is not released, the completion monitoring may
not end. In such a case, a KAJM1838-W message appears. Follow the instructions in
the message.
The -with_child option is valid when the -wait option is specified.
Note
To specify the -with_child option, JP1/AJS2 for EAP 07-50 or later must be
installed on the execution destination host, and the XBP 2.0 interface and the
parent and child function must be enabled in the connection destination R/3
system.
„ -tgh target-host
Specify the host name of the application server that executes the registered job. You
can specify a target host name with a length from 1 to 32 bytes. From the list of host
names displayed by the transaction SM51, you can also select the host name assigned
to the application server that offers a background processing service.
If you specify this option, the command will select one of the application servers that
are running on the specified host and designate it as the target system.
If you omit this option and the -tgs option, the R/3 system will dynamically select the
target system on which the job will run. You cannot specify the tgh and -tgs options
at the same time.
130
jr3bjrel
Note
This option is the job definition compatible parameter created for Release 4.0 and
later R/3 systems. To define jobs for Release 4.5 or later R/3 systems, use the
-tgs option.
„ -tgs target-server
Specify the name of the application server or the job server group that executes the
registered job. You can specify a character string of 1 to 20 bytes. When you use an
application server, you can specify one of the names (upper-case and lower-case
characters are differentiated) that are assigned to the application servers for providing
background processing services. These application server names are listed by
transaction SM51. When you use a job server group, you can specify one of the names
(upper-case and lower-case characters are differentiated) of the job server groups
containing the application servers that provide background processing services. These
job server group names are listed by transaction SM61.
If you omit this option and the -tgh option, the R/3 system will dynamically select the
target server on which the job will run. You cannot specify the tgs and -tgh options
at the same time.
„ -rs
This argument releases a job as soon as possible.
This means that the job will be released after system resources to execute the job are
allocated.
The -rs option is the default when the -rs and -ri options are not specified.
„ -ri
This argument immediately releases a job. However, releasing a job fails unless R/3
system resources are allocated.
„ -user SAP-user-name
This argument cancels only the jobs that are specified by the -jn option and are owned
by the specified SAP user. A character string of 1 to 12 bytes can be entered for the
SAP user name specification.
Note that the -user option cannot be used together with the -wait option.
„ -help
This argument provides information on using the command.
131
jr3bjrel
Return values
„
When the -wait or -cancel option is not specified
0
All the specified jobs were successfully released.
Integer of 1 or more
The specified jobs were not successfully released.
„
When the -wait option is specified
0
The job ended normally.
All the jobs ended normally (when the -with_child option is specified).
1
The job was canceled.
One or more jobs were canceled or the result of at least one job could not be
checked because the number of jobs to be monitored exceeded the maximum
limit or the target job was deleted (when the -with_child option is
specified).
2
The job completion monitoring resulted in a timeout error.
Integer of 3 or more
The command ended abnormally (a job release or monitoring operation
failed).
„
When the -cancel option is specified
0
The job ended normally.
All the jobs ended normally (when the -with_child option is specified).
1
The job was canceled.
One or more jobs were canceled or the result of at least one job could not be
checked because the number of jobs to be monitored exceeded the maximum
limit or the target job was deleted (when the -with_child option is
specified).
132
jr3bjrel
2
All the jobs were successfully canceled when the job completion monitoring
resulted in a timeout error.
3
At least one job was not successfully canceled when the job completion
monitoring resulted in a timeout error.
Integer of 4 or more
The command ended abnormally (a job release or monitoring operation
failed).
Supplement
• When the -wait option is specified and the -rs or -ri option has been specified,
job monitoring will be performed until the execution of a released job ends (until
job execution ends, commands cannot be executed from the command line).
Specifying the -wait option adds job execution result (ended normally or
canceled) information to the command end code.
It should be remembered that jobs can also be released by the jr3bjsub
command.
Usage examples
„
Releasing job R3JOB1 of user R3USER1
The conditions are as follows:
• The saprfc.ini file will be used (-d R3SERV1).
• R/3 logon information will be specified (-c 001 -u R3USER1 -p
HT0110).
• The job count will be specified (-jc 11204501).
• The job will be released as soon as possible (-rs).
• The released job will be subject to job completion monitoring at 10-second
intervals for a period of 10 minutes (-wait -time 10 -ival 10).
• The job completion monitoring operation will be canceled in 10 minutes
(-cancel).
• The standard output file and standard error output file will be created in the
directory specified by the environment setup file (-so STDOUT1 -se
STDERR1).
To release job R3JOB1 of user R3USER1 under the above conditions, make sure
that the jr3bjrel command line is specified as follows:
133
jr3bjrel
jr3bjrel -d R3SERV1 -c 001 -u R3USER1 -p HT0110 -jn R3JOB1 -jc 11204501 -rs
-wait -time 10 -ival 10 cancel -so STDOUT1 -se STDERR1
134
jr3bjrep
jr3bjrep
Format 1
jr3bjrep
[R/3-destination-information]
[R/3-logon-information]
[redirection-information]
-pa ABAP-program-name
Note
If the character string for the argument specification contains a space, enclose the
argument with double quotation marks (").
Format 2
jr3bjrep -help
Description
Acquires information about R/3 system resources. The names of the variants defined
for a specified ABAP program can be enumerated as R/3 program resource
information.
Arguments
„ R/3-destination-information
Specify the R/3 system where the job about which resource information will be
obtained exists. For details about the format of R/3 destination information, see (1)
Common argument format for job control function commands.
„ R/3-logon-information
Specify logon information that is valid in the R/3 system where the job about which
resource information will be obtained exists. For details about the format of R/3 logon
information, see (1) Common argument format for job control function commands.
„ redirection-information
Specify standard output and standard error output files for command execution. For
details about the format of redirection information, see (1) Common argument format
for job control function commands.
„ -pa ABAP-program-name
Specify a desired ABAP program name. You can specify a character string from 1 to
40 bytes.
135
jr3bjrep
„ -help
This argument provides information on using the command.
Return values
0
The job resource information was successfully obtained.
Integer of 1 or more
Job resource information was not obtained.
Usage examples
„
Enumerating the variants of the ABAP program RSPO0041
The conditions are as follows:
• R/3 destination information will be specified (-h R3CENTRL -s 00).
• R/3 logon information will be specified (-c 001 -u "SAP*" -p
06071992).
• The standard output file and standard error output file will be created in the
system's standard output and standard error output, respectively.
To enumerate the variants of the ABAP program RSPO0041 under the above
conditions, make sure that the jr3bjrep command line is specified as follows:
jr3bjrep -h R3CENTRL -s 00 -c 000 -u "SAP*" -p 06071992
-pa RSPO0041
Output result:
136
jr3bjsho
jr3bjsho
Format 1
[R/3-destination-information]
[R/3-logon-information]
[redirection-information]
-jn job-name
[-jc job-count]
[-user SAP-user-name]
[-status status-name]
[-check]
[-ls]
[-lo]
jr3bjsho
Note
If the character string for the argument specification contains a space, enclose the
argument with double quotation marks (").
Format 2
jr3bjsho -help
Description
Displays the information (including the R/3 job log) about R/3 system background
jobs in list or detailed list format.
The characteristics of the display formats are summarized below.
• When list format is used
Information about a job complying with the an option-specified pattern can be
displayed in list format.
• When detailed form is used
Job information, including job step information and R/3 job log information, can
be displayed in detailed list format. The -ls and -lo options can be used.
Individual items of information in the prescribed format are transferred to the
standard output. The -ls and -lo options can be specified in any order.
Arguments
„ R/3-destination-information
Specify the R/3 system where the job about which information is to be displayed
exists. For details about the format of R/3 destination information, see (1) Common
137
jr3bjsho
argument format for job control function commands.
„ R/3-logon-information
Specify the logon information that is valid in the R/3 system where the job about which
information is to be displayed exists. For details about the format of R/3 logon
information, see (1) Common argument format for job control function commands.
„ redirection-information
Specify standard output and standard error output files for command execution. For
details about the format of redirection information, see (1) Common argument format
for job control function commands.
„ -jn job-name
Specify the job name of the job about which information is to be displayed. A character
string of 1 to 32 bytes can be entered for the job name specification. If there are
duplicate job names in the specified R/3 system, enter the job count with the -jc
option to specify the job.
Note that the -jn option specification cannot be omitted.
„ -jc job-count
To differentiate jobs having the same name, specify the job count. If the job count
specification is omitted, information about all jobs having the same name is displayed.
„ -user SAP-user-name
This argument displays information about only the jobs that are specified by the jn
option and owned by the specified SAP user. A character string of 1 to 12 bytes can be
entered for the SAP user name specification.
„ -status status-name
This argument displays only jobs that are specified by the -jn option and in the
specified state. Note that one or more status names can be specified (e.g., -status
RYF). If there are duplicate status name specifications, they are handled as one status
name.
The following are the allowed status names and their meanings:
P: Scheduled
S: Released
Y: Ready
R: Active
F: Finished
A: Terminated
138
jr3bjsho
„ -check
This argument displays the latest R/3 system job information.
„ -ls
This argument displays the job attribute information in detailed list format.
„ -lo
This argument displays an R/3 job log if there is one for the target job.
„ -help
This argument provides information on using the command.
Return values
0
All the specified jobs were successfully displayed.
Integer of 1 or more
The specified jobs were not successfully displayed.
Usage examples
„
Displaying job information about job JOB0129 in list format
The conditions are as follows:
• R/3 destination information will be specified (-h R3CENTRL -s 00).
• R/3 logon information will be specified (-c 000 -u "SAP*" -p
06071992).
• The standard output file and standard error output file will be created in the
system's standard output and standard error output, respectively.
To display the job information about job JOB0129 in list format under the above
conditions, make sure that the jr3bjsho command line is specified as follows:
jr3bjsho -h R3CENTRL -s 00 -c 000 -u "SAP*" -p 06071992
-jn JOB0129
Output result:
139
jr3bjsho
„
Displaying the job information about job JOB0129 in detailed list format
The conditions are as follows:
• R/3 destination information will be specified (-h R3CENTRL -s 00).
• R/3 logon information will be specified (-c 000 -u "SAP*" -p
06071992).
• The job count will be specified (-jc 13531901).
• The standard output file and standard error output file will be created in the
system's standard output and standard error output, respectively.
To display the job information about job JOB0129 in detailed list format under
the above conditions, make sure that the jr3bjsho command line is specified as
follows:
jr3bjsho -h R3CENTRL -s 00 -c 000 -u "SAP*" -p 06071992
-jn JOB0129 -jc 13531901 -ls -lo
140
jr3bjsho
Output result:
141
jr3bjsub
jr3bjsub
Format 1
jr3bjsub
[R/3-destination-information]
[R/3-logon-information]
[redirection-information]
-jn job-name
[-class job-class]
job-step-information...
[{-tgh target-host|-tgs target-server}]
[{-rs|-ri}]
[-wait [-time monitoring-time [-cancel]]
[-ival monitoring-interval]
[-jo R/3-job-log-filename]
[-with_child]]
Note
If the character string for the argument specification contains a space, enclose the
argument with double quotation marks (").
Format 2
jr3bjsub -help
Description
Creates a background job in an R/3 system.
The background jobs that can be registered on the R/3 system are those that can be
defined and executed using transaction code SM36.
When the job is successfully created, the R/3 system assigns a job count to it to identify
it. This job count is transferred to the standard output as part of a message.
The user can use the job count and the job name specified at creation to viewing the
status of a created job or to cancel job execution.
Use the jr3bjdel command to delete jobs registered on the R/3 system.
Arguments
„ R/3-destination-information
Specify the R/3 system in which the job is to be created. Created jobs are usually
executed with the load distributed among application servers that are capable of
executing the jobs. With the -tgh option, however, it is possible to specify the system
that will execute the jobs. For details about the format of R/3 destination information,
see (1) Common argument format for job control function commands.
142
jr3bjsub
„ R/3-logon-information
Specify logon information that is valid in the R/3 system in which the job is to be
created. Usually, a valid user for job execution is an R/3 user who is specified in the
R/3 logon information. With the -auth option in the job step information, however, it
is possible to specify a valid R/3 user for job execution.
The language specified by the -l option in the R/3 logon information does not affect
the execution of a created job when an ABAP program is specified as a job step. To
change the language type of the ABAP program defined as a job step from the default
of the R/3 system when you execute the job, use the -lang option in the job step
information. For details about the format of R/3 logon information, see (1) Common
argument format for job control function commands.
„ redirection-information
Specify standard output and standard error output files for command execution. For
details about the format of redirection information, see (1) Common argument format
for job control function commands.
„ -jn job-name
Specify the job name of the R/3 job to be created. A character string of 1 to 32 bytes
can be entered for the job name specification.
Note that the -jn option specification cannot be omitted.
„ -class job-class
Specify the job class (priority level of job execution) of the R/3 job to be created. The
following options are available:
A: High
B: Middle
C: Low
Normally, specify C. To execute a job with priority, specify B. To execute a job
immediately in an emergency, specify A. The default is C.
Note
To specify a job class, JP1/AJS2 for EAP 07-50 or later must be installed on the
execution destination host and the XBP 2.0 interface must be enabled in the
connection destination R/3 system.
„ job-step-information...
Specify a program (ABAP program or external program) as a job step in the job. If you
specify two or more sets of job step information, you can assign two or more job steps
to a job. Up to 99 sets of job step information can be specified. The job steps assigned
to a job are executed in the order of assignment.
143
jr3bjsub
The job step information format varies with the type of program specified as a job step.
The job step information format of each program type is described below.
Job step information format (ABAP program)
-pa ABAP-program [-var variant]
[-auth authorized-user]
[-lang language]
[-armode archive-mode]
[-out output-device]
[-ln lines] [-col columns]
[-fmt format]
[-cc number-of-copies]
[-shwpwd authority]
[-ip][-dp]
[-rpd spool-retention-period]
[-title spool-request-title]
[-sapcvr SAP-cover]
[-selcvr]
[-receiver recipient]
[-dpt department]
[-objtyp object-type]
[-doctyp document-type]
[-info information-ID]
[-text information-text]
-pa ABAP-program
Specify the name of the ABAP report program (ABAP program) to be added as a
job step. A character string of 1 to 40 bytes can be entered in the ABAP program.
Make sure that the ABAP program to be specified is preregistered in the R/3
system.
-var variant
When there is a variant for the ABAP program, specify its name. A character
string of 1 to 14 bytes can be entered for the variant name specification. Variants
that can be specified with the -var option are limited to those that have been
registered in the R/3 system.
-auth authorized-user
Specify the name of the authorized user that is set when the ABAP program is
executed. You can specify a character string of 1 to 12 bytes as the name of the
authorized user. If you omit the -auth option, the user who logged on to the R/3
system (user specified in the R/3 logon information) is set as the authorized user
when the ABAP program is executed.
-lang language
Enter a single-byte alphabetic character to specify the language to be used. You
can use English. Specify the following language that can be used in the execution
144
jr3bjsub
environment of the ABAP program.
• For English: E
-armode archive-mode
Specify a method for archiving the execution results of the ABAP program.
The following are the allowed status names and their meanings. The default
archive mode is P (print).
P: Print
A: Archive
PA (or AP): Print and archive
If you assign A or PA to armode, you must also specify -objtyp, -doctyp, and
-info.
-out output-device
Specify the name of the output destination device set for the R/3 system as the
print destination of the execution results of the specified ABAP program. Specify
the abbreviation of the output device. A character string of between one and four
bytes can be entered. If you omit the printer specification, the default output
device defined for the R/3 system is selected automatically.
-ln lines
Specify the number of lines to set the output format for the execution results of
the ABAP program. The specifiable values are 1 to 255. If you omit this option,
the R/3 system will select an appropriate format.
You cannot specify the -ln option and the -fmt option together.
-col columns
Specify the number of columns to set the output format for the execution results
of the ABAP program.
The specifiable values are 1 to 255. If you omit this option, the R/3 system will
select an appropriate format.
You cannot specify the -col option and the -fmt option together.
-fmt format
Specify the name of the output format for the execution results of the ABAP
program.
You can specify a character string of 1 to 16 bytes. If you omit this option, an
applicable format is selected by the R/3 system.
You cannot specify the -fmt option and the -ln option or the -col option
145
jr3bjsub
together.
Note
To specify the -fmt option, JP1/AJS2 for EAP 07-50 or later must be
installed on the execution destination host and the XBP 2.0 interface must be
enabled in the connection destination R/3 system.
-cc number-of-copies
Specify the number of copies to be printed. A value of between 1 and 255 can be
entered. If you omit the number of copies specification, it is automatically set to 1.
-shwpwd authorization
To prevent the illegal manipulation of print requests, you can specify an
authorization character string. Users are allowed to manipulate print requests only
when they have a spool action authorization object that matches the authorization
character string entered here. A character string of between one and twelve bytes
can be entered.
-ip
Immediately forwards print requests to the printer.
-dp
Deletes print requests after they have been sent to the printer.
-rpd spool-retention-period
Specify how many days the print request should be retained.
The following are the allowed status names and their meanings. If you omit this
option, the print request will be retained for eight days (it will be deleted after
eight days).
1 to 8: Number of days during which the print request will be retained
unlimited: The print request will be retained indefinitely.
-title spool-request-title
Specify the title of the spool request. You can specify a value of 1 to 68 bytes. If
you omit this option, the title of the spool request is blank.
Note
To specify the -title option, JP1/AJS2 for EAP 07-50 or later must be
installed on the execution destination host and the XBP 2.0 interface must be
enabled in the connection destination R/3 system.
-sapcvr SAP-cover
Specify this option to add a SAP cover, including the recipient name, section
146
jr3bjsub
name, and other information, to the ABAP program execution results. The
following are the allowed status names and their meanings.
Y: A SAP cover will be added.
N: No SAP cover will be added.
D: A SAP cover may or may not be added depending on the setting of the printer.
If you omit the -sapcvr option, D is assumed for the SAP cover.
-selcvr
Specify this option to add a selected-report cover, containing the program
execution condition, to the ABAP program execution results.
-receiver recipient
Specify this option to change the recipient of the print-out. If you specify this
option, the receiver name printed on the SAP cover will also be changed. You can
specify a character string of 1 to 12 bytes. If you do not specify a recipient, the
user who is permitted to execute the ABAP program is assumed.
-dpt department
Enter the name of the department to be printed on the SAP cover.
You can specify a character string of 1 to 12 bytes. If you omit this option, the
department specified in the profile of the user who is permitted to execute the
ABAP program is assumed.
Note
To specify the -dpt option, JP1/AJS2 for EAP 07-50 or later must be
installed on the execution destination host and the XBP 2.0 interface must be
enabled in the connection destination R/3 system.
-objtyp object-type
Specify an object type used to classify the archive of the report to be printed. You
can specify a character string of 1 to 10 bytes. You must register the object type
with the R/3 system in advance. This option is mandatory if you assign A
(Archive) or PA (Print and archive) to -armode. If you assign P (print) or nothing
to -armode, do not specify this option.
-doctyp document-type
Specify a document type used to classify the archive of the report to be printed.
You can specify a character string of 1 to 10 bytes. You must register the
document type with the R/3 system in advance. This option is mandatory if you
assign A (Archive) or PA (Print and archive) to -armode. If you assign P (print)
or nothing to -armode, do not specify this option.
147
jr3bjsub
-info information-ID
Specify an information ID that identifies the archive request. You can specify a
character string of 1 to 3 bytes. This option is mandatory if you assign A (Archive)
or PA (Print and archive) to -armode. If you assign P (print) or nothing to
-armode, do not specify this option.
-text information-text
Enter an explanation that describes the contents of the archive request.
You can specify a character string of 1 to 40 bytes. You can specify this option
when A (archive) or PA (print and archive) is set for -armode. You can omit this
option.
Note
To specify the -text option, JP1/AJS2 for EAP 07-50 or later must be
installed on the execution destination host and the XBP 2.0 interface must be
enabled in the connection destination R/3 system.
Job step information format (external program)
-px external-program -xpgtgh target-host
[-arg argument]
[-auth authorized-user]
-px external-program
Specify the name of the external program to be added as a job step. A character
string of 1 to 128 bytes can be entered for the external program specification.
The specified external program must comply with the following requirement:
• The external program must be executable by a SAP CPI-C user.
For information about SAP CPI-C users, see the R/3 manual or online help.
-xpgtgh target-host
Specify the name of the host that executes the external program. A character
string of 1 to 32 bytes can be entered for the target host specification. Host names
in the following formats can be used:
• Host name defined in the hosts file
• IP address
Note that the appropriateness of the target host specification (whether the
specified host name or IP address is in the hosts file) will not be checked
when the command is executed.
148
jr3bjsub
-arg argument
If the external program requires an argument, specify the name of the argument.
You can specify a character string of 1 to 255 bytes.
-auth authorized-user
Specify the name of the authorized user that is to be specified when the external
program is executed. A character string of 1 to 12 bytes can be entered for the
authorized user specification. However, since the external program is executed
via the SAP CPI-C user, the authorized user specified by the -auth option
becomes invalid. Note that the external programs are executed by SAP CPI-C
users.
If the -auth option specification is omitted, the user that logs on to the R/3
system (the user specified by the R/3 logon information) is set as the authorized
user when the external program is executed.
„ -tgh target-host
Specify the host name of the application server that executes the registered job. As the
target host designation, a character string of between 1 and 32 bytes can be entered.
From the list of host names displayed by the transaction SM51, you can also select the
host name assigned to the application server that offers a background processing
service.
If you specify this option, the command will select one of the application servers that
are running on the specified host and designate it as the target system.
If you omit this option and the -tgs option, the R/3 system will dynamically select the
target system on which the job will run. You cannot specify the tgh and -tgs options
at the same time.
Note
This option is the job definition compatible parameter created for Release 4.0 and
earlier R/3 systems. To define jobs for Release 4.5 or later R/3 systems, use the
-tgs option.
„ -tgs target-server
Specify the name of the application server or the job server group that executes the
registered job. You can specify a character string of 1 to 20 bytes for the target server.
When you use an application server, you can specify one of the names that are assigned
to the application servers for providing background processing services (upper-case
and lower-case characters are differentiated). These application server names are listed
as host names by transaction SM51. When you use a job server group, you can specify
one of the names (upper-case and lower-case characters are differentiated) of the job
server groups containing the application servers that provide background processing
services. These job server group names are listed by transaction SM61.
149
jr3bjsub
If you omit this option and the -tgh option, the R/3 system will dynamically select the
target system on which the job will run. You cannot specify the tgs and -tgh options
at the same time.
„ -rs
This argument releases the job as soon as possible after its creation. To release the job
as soon as possible means that the job will be released when required system resources
have been allocated for job execution.
„ -ri
This argument releases the job immediately after its creation. However, the release will
fail if R/3 system resource allocation fails.
„ -wait
This argument performs job monitoring until the execution of the released job ends
(until job execution ends, commands cannot be executed from the command line).
If the job being monitored for its completion is interrupted by the R/3 system, the
completion monitoring may not end. In such a case, a KAJM1836-W message appears.
Follow the instructions in the message.
The -wait option is valid when the -rs or -ri option is specified.
„ -time monitoring-time
Specify the duration of job completion monitoring in minutes. Job completion will be
monitored for the specified period of time. Make sure that this monitoring time setting
is greater than the monitoring interval value that is specified by the -ival option. The
specifiable range for monitoring time is from 1 to 65,535. If the -time option
specification is omitted, there is no limit on the monitoring time.
When the -with_child option is specified, all jobs, including the child jobs, are
monitored for their completion during this time.
If the job does not end within the specified monitoring time, that terminates the
command without regard to the job status occurs.
The -time option is valid when the -wait option is specified.
„ -cancel
This argument cancels a job having the job count specified by the -jc option if it does
not end within the time specified by the -time option. Note that this argument works
only on an active job (job currently being executed). It does not cancel jobs under the
following conditions:
• The job whose completion is being monitored is not active.
• An external program job step is being executed while the job whose completion
is being monitored is active.
150
jr3bjsub
When the -with_child option is specified, all jobs, including the child jobs, are
canceled.
If the -cancel option is not specified, the job execution continues as is in the R/3
system.
The -cancel option is valid when the -time option is specified.
„ -ival monitoring-interval
Specify the interval in seconds at which a job is to be monitored. Job monitoring can
be performed at the specified monitoring interval until the job ends (job polling
monitoring). The specifiable monitoring interval range is from 1 to 65535. If a
monitoring interval is omitted when the -ival option is specified, the monitoring
interval is 5 seconds.
The default monitoring interval setting of 5 seconds can be changed in the environment
setup file.
The -ival option is valid when the -wait option is specified.
„ -jo R/3-job-log-filename
Specify the R/3 job log output destination. The R/3 job log is acquired when job
execution ends (when the return value is 0 or 1 and the -wait option is specified). The
length of the character string for the R/3 job log filename varies depending on whether
Windows or UNIX is used.
• When Windows is used
A character string of 1 to 259 bytes can be entered for the R/3 job log filename.
• When UNIX is used
A character string of 1 to 255 bytes can be entered for the R/3 job log filename.
If you do not use the full path to specify the R/3 job log file, the file is created in the
work directory of JP1/AJS3 for EAP. (If the JP1/AJS3 for EAP work directory is not
defined, the file will be created in the current directory.)
The R/3 job log output is in write-date write-time message-code (message class and
message number) message-text format.
You can also write the R/3 job log to this file.
If you specify YES for the JoblogAddToStderr key of the Command section of the
environment settings file, you can output the R/3 job log to the specified log and to
standard error at the same time.
When the -with_child option is specified, the log of all jobs that are finished or
terminated is acquired when the completion monitoring of all jobs, including the child
jobs, ends (includes timeout errors).
151
jr3bjsub
If the -jo option specification is omitted, the R/3 job log will not be output to the JP1/
AJS3 for EAP system.
„ -with_child
This argument monitors the completion of all jobs, including the child jobs, that are
generated during the execution of the target job (completion monitoring of parent and
child jobs). The target child jobs are those that are detected when the job being
monitored for its completion is finished or terminated. A maximum of 100 jobs can be
monitored for their completion regardless of the generation numbers of the child jobs.
If the number of jobs to be monitored for their completion exceeds the maximum limit,
a KAJM1872-W message appears. The completion monitoring then continues for the
jobs that can be monitored for their completion and the system returns 1, indicating
that the result of at least one job cannot be checked.
If a job being monitored for its completion is deleted, a KAJM1837-W message or a
KAJM1871-W message appears. The completion monitoring then continues for other
target jobs and the system returns 1, indicating that the result of at least one job cannot
be checked.
If the system detects a child job that is not released, the completion monitoring may
not end. In such a case, a KAJM1838-W message appears. Follow the instructions in
the message.
The -with_child option is valid when the -wait option is specified.
Note
To specify the -with_child option, JP1/AJS2 for EAP 07-50 or later must be
installed on the execution destination host, and the XBP 2.0 interface and the
parent and child function must be enabled in the connection destination R/3
system.
„ -help
This argument provides information on using the command.
Return values
„
When the -wait or -cancel option is not specified
0
The job was successfully created.
Integer of 1 or more
The job was not created.
152
jr3bjsub
„
When the -wait option is specified
0
The job ended normally.
All the jobs ended normally (when the -with_child option is specified).
1
The job was canceled.
One or more jobs were canceled or the result of at least one job could not be
checked because the number of jobs to be monitored exceeded the maximum
limit or the target job was deleted (when the -with_child option is
specified).
2
The job completion monitoring resulted in a timeout error.
Integer of 3 or more
The command ended abnormally (job creation, release, or monitoring
failed).
„
When the -cancel option is specified
0
The job ended normally.
All the jobs ended normally (when the -with_child option is specified).
1
The job was canceled.
One or more jobs were canceled or the result of at least one job could not be
checked because the number of jobs to be monitored exceeded the maximum
limit or the target job was deleted (when the -with_child option is
specified).
2
All the jobs were successfully canceled when the job completion monitoring
resulted in a timeout error.
3
At least one job failed to be canceled when the job completion monitoring
resulted in a timeout error.
Integer of 4 or more
The command ended abnormally (job creation, release, or monitoring
153
jr3bjsub
failed).
Precautions
If one of the following conditions is satisfied, the job execution target option (-tgh or
-tgs) specified in the jr3bjsub command will be ineffective:
• The release option (-rs or -ri) is not specified.
• You have normally registered the job, but have failed to release the job.
In this event, no target host is assigned to the job registered on the R/3 system.
To execute the job on a particular target host or server, release the job by specifying
the target host or server using the -tgh or -tgs option in the jr3bjrel command. If
you use the jr3bjrel command to release the job without specifying a target host or
server, the R/3 system will dynamically select the target host or server on which the
job will be executed.
Supplement
• If an error occurs during job creation or jr3bjsub command execution is
aborted, unnecessary jobs (nonexecutable jobs) may remain in the R/3 system.
Delete unnecessary jobs using the jr3bjdel command.
Usage examples
„
Creating job R3JOB1 of user R3USER1
The conditions are as follows:
• The saprfc.ini file will be used (-d R3SERV1).
• R/3 logon information will be specified (-c 001 -u R3USER1 -p
HT0110).
• An ABAP program and an external program will be specified as job steps
(-pa PROG1 -var STANDARD1 -auth JP1USRA -px PROG2 -xpgtgh
111.11.11.11 -arg STANDARD2).
• The job will be released as soon as possible (-rs).
• The R/3 job log file, standard output file, and standard error output file will
be created in the directory specified by the environment setup file
(-jo JOBLOG1 -so STDOUT1 -se STDERR1).
To create job R3JOB1 of user R3USER1 under the above conditions, make sure
that the jr3bjsub command line is specified as follows:
jr3bjsub -d R3SERV1 -c 001 -u R3USER1 -p HT0110 -jn R3JOB1 -pa PROG1 -var
STANDARD1 -auth JP1USRA -px PROG2 -xpgtgh 111.11.11.11 -arg STANDARD2 -rs
-wait -jo JOBLOG1 -so STDOUT1 -se STDERR1
154
jr3chrfc
jr3chrfc
Format 1
jr3chrfc [-expwd {ON | OFF}]
Format 2
jr3chrfc -help
Function
Sets the availability of the extended password. Also, outputs the extended password's
availability status to standard output.
The content set by this command is saved in the RFC library status management file
(for Windows: installation destination folder \system\jr3chrfc, for UNIX: /etc/
opt/jp1_am_r3/.jr3chrfc).
In Windows, this command is executed by a user with Administrator permissions and
in UNIX, it is executed by a superuser.
Arguments
„ No argument
Outputs the extended password's availability status to standard output.
„ -expwd ON
Makes the extended password available. If the setting is changed, a KAJM0601-I
message appears.
If you failed to change the setting, a message appears and the command execution is
terminated. Take the action indicated by the displayed message.
You must specify the ON or OFF option. You cannot specify both at the same time. You
can specify ON in either upper- or lower-case.
„ -expwd OFF
Makes the extended password unavailable. If the setting is changed, a KAJM0601-I
message appears.
If you failed to change the setting, a message appears and the command execution is
terminated. Take the action indicated by the displayed message.
You must specify the ON or OFF option. You cannot specify both at the same time. You
can specify OFF in either upper- or lower-case.
„ -help
Displays how to use this command.
155
jr3chrfc
Return values
0
The availability of the extended password was successfully changed, or the
extended password's availability status was successfully displayed.
1
The change in availability of the extended password failed, or display of the
extended password's availability status failed.
Precautions
• Do not execute the jr3chrfc command while another command is executing.
Usage examples
• To display the extended password's availability status (when the extended
password is used)
The command line of the jr3chrfc command at this time is as follows:
jr3chrfc
Output result:
• To make the extended password available
The command line of the jr3chrfc command at this time is as follows:
jr3chrfc -expwd ON
156
Chapter
5. Events
This chapter describes the events issued by JP1/AJS3 for EAP for each type of OS.
5.1 When a Windows event is used
157
5. Events
5.1 When a Windows event is used
This section describes events issued by the Windows version of JP1/AJS3 for EAP.
Events issued by the Windows version of JP1/AJS3 for EAP are displayed as the
contents of the application log by the Windows administrative tool Event Viewer. In
this section, events that are issued by the Windows version of JP1/AJS3 for EAP are
described simply as events.
For job control function events, JP1/AM/R3 is set as the source for the Event Viewer.
For InfoPackage or process chain control function events, JP1/AM/R3/SAPBWOption
is set as the source for the Event Viewer.
5.1.1 Event ID format
The event ID format for the events issued by JP1/AJS3 for EAP is given below.
Event ID format: 0xXYZZ
The elements of an event ID are as follows:
X
Category code number. The code number 2 indicates an event that is related to the
environment setup (common to all functions) of JP1/AJS3 for EAP. The code
number 3 indicates an event related to the job control function. The code number
4 indicates an event related to the InfoPackage control function. The code number
5 indicates an event related to the process chain control function.
Y
Indicates a group within an individual category. For grouping purposes,
hexadecimal numbers from 0 to F are used.
ZZ
Sequential number assigned to each category. Sequential numbers are
hexadecimal numbers from 00 to FF.
5.1.2 List of events
The events issued by JP1/AJS3 for EAP are listed below for each category.
(1) Events related to the environment setup (common to all functions) for JP1/
AJS3 for EAP
The following table describes the events related to the environment setup (common to
all functions) of JP1/AJS3 for EAP.
158
5. Events
Table 5-1: List of events related to environment setup (common to all functions)
of JP1/AJS3 for EAP
Event ID
Event name
When event issued
Maintenance
information
0x2100
Environment setup file
(invalid key/invalid
section) warning
An environment setup
file key name (key) or
section name (section)
is invalid
No
0x2101
Invalid environment setup
file (key value illegality)
warning
An invalid value
(string) was specified
for an environment setup
file key.
No
0x2102
Invalid environment setup
file (duplicate keys or
sections) warning
An environment setup
file key name (key) or
section name (section)
was duplicated.
No
0x2103
Invalid environment setup
file (invalid character
string used) warning
The environment setup
file contains an invalid
character string.
No
0x2104
Invalid environment setup
file (environment setup file
inaccessible) warning
The environment setup
file cannot be accessed.
No
0x2105
Invalid parameter (trace
file inaccessibility)
warning
The trace file cannot be
accessed because of an
invalid parameter.
No
0x2106
Invalid parameter (unable
to create/extend trace file)
warning
The trace file cannot be
created or extended
because of an invalid
parameter.
No
(2) Events related to job control function
The following table describes the events that are related to the job control function of
JP1/AJS3 for EAP.
Table 5-2: List of events related to the job control function of JP1/AJS3 for EAP
Event ID
Event name
When event issued
Maintenance
information
0x3000
Job creation
R/3 job creation was
successful.
Yes
0x3100
Job creation failure
R/3 job creation failed.
Yes
159
5. Events
Event ID
Event name
When event issued
Maintenance
information
0x3400
Job release
R/3 job release was
successful.
Yes
0x3500
Job release failure
R/3 job release failed.
Yes
0x3600
Job termination
R/3 job termination was
successful.
Yes
0x3700
Job termination failure
R/3 job termination
failed.
Yes
0x3800
Job deletion
R/3 job deletion was
successful.
Yes
0x3900
Job deletion failure
R/3 job deletion failed.
Yes
0x3901
Incomplete-job deletion
failure
An incomplete R/3 job
failed to be deleted.
Yes
0x3A00
Job completion
monitoring success (when
a job has ended normally)
R/3 job completion
monitoring was
successful when the job
has ended normally.
Yes
0x3A01
Job completion
monitoring success (when
a job has been terminated)
R/3 job completion
monitoring was
successful when the job
has been terminated.
Yes
0x3B00
Job completion
monitoring timeout
An R/3 job completion
monitoring timeout
occurred.
Yes
0x3C00
Job completion
monitoring failure
R/3 job completion
monitoring failed.
Yes
0x3C01
Job completion
monitoring failure
because of reconnection
timeout
R/3 job completion
monitoring failed because
reconnection timeout
occurs.
Yes
0x3D00
XMI interface session
audit level change failure
An XMI interface session
audit level change failed.
Yes
0x3E00
R/3 job log acquisition
failure
R/3 job log acquisition
failed.
Yes
0x3F00
Job interrupt detection
An R/3 job interruption
was detected.
Yes
160
5. Events
Event ID
Event name
When event issued
Maintenance
information
0x3F01
Detection of a job without
confirmation of
completion (job deletion)
An R/3 job without
completion confirmation
was detected (since the
job to be monitored was
deleted).
Yes
0x3F02
Detection of a job without
confirmation of
completion (child job
detection failure)
An R/3 job without
completion confirmation
was detected (since the
job was deleted before
any child job was
detected).
Yes
0x3F03
Detection of a job without
confirmation of
completion (number of
jobs to be monitored
exceeded the maximum
limit)
An R/3 job without
completion confirmation
was detected (since the
number of jobs to be
monitored exceeded the
maximum limit).
Yes
0x3F04
Unreleased-job detection
An unreleased job was
detected.
Yes
(3) Events related to the InfoPackage control function
The following table describes the events that are related to the InfoPackage control
function of JP1/AJS3 for EAP.
Table 5-3: List of events related to the InfoPackage control function of JP1/
AJS3 for EAP
Event ID
Event name
When event issued
Maintenance
information
0x4000
InfoPackage startup
InfoPackage startup was
successful.
Yes
0x4100
InfoPackage startup
failure
InfoPackage startup
failed.
Yes
0x4200
InfoPackage completion
monitoring success (when
InfoPackage has ended
normally)
InfoPackage completion
monitoring was
successful when
InfoPackage has ended
normally.
Yes
161
5. Events
Event ID
Event name
When event issued
Maintenance
information
0x4201
InfoPackage completion
monitoring success (when
InfoPackage has ended
abnormally)
InfoPackage completion
monitoring was
successful when
InfoPackage has ended
abnormally.
Yes
0x4300
InfoPackage completion
monitoring timeout
An InfoPackage
completion monitoring
timeout occurred.
Yes
0x4400
InfoPackage completion
monitoring failure
InfoPackage completion
monitoring failed.
Yes
0x4500
InfoPackage completion
monitoring failure
because of reconnection
timeout
InfoPackage completion
monitoring failed because
reconnection timeout
occurred.
Yes
(4) Events related to the process chain control function
The following table describes the events that are related to the process chain function
of JP1/AJS3 for EAP.
Table 5-4: List of events related to the process chain control function of JP1/
AJS3 for EAP
Event ID
Event name
When event issued
Maintenance
information
0x5000
Process chain startup
Process chain startup was
successful.
Yes
0x5100
Process chain startup failure
Process chain startup failed.
Yes
0x5200
Process chain completion
monitoring success (when the
process chain ended normally)
Process chain completion
monitoring was successful when
the process chain ended normally.
Yes
0x5201
Process chain completion
monitoring success (when the
process chain ended abnormally)
Process chain completion
monitoring was successful when
the process chain ended
abnormally.
Yes
0x5300
Process chain completion
monitoring timeout
A process chain completion
monitoring timeout occurred.
Yes
0x5400
Process chain completion
monitoring failure
Process chain completion
monitoring failed.
Yes
162
5. Events
Event ID
Event name
When event issued
Process chain completion
monitoring failure because of a
reconnection timeout
0x5500
Process chain completion
monitoring failed because a
reconnection timeout occurred.
Maintenance
information
Yes
5.1.3 Maintenance information about events
The maintenance information about events is common within each category defined in
5.1.1 Event ID format. There is no maintenance information about events related to the
environment setup (common to all functions) of JP1/AJS3 for EAP (category code
number 2). Table 5-5 lists the maintenance information about events related to the job
control function (category code number 3). Table 5-6 lists the maintenance
information about events related to the InfoPackage control function (category code
number 4). Table 5-7 lists and describes the maintenance information about events
related to the process chain control function (category code number 5).
Table 5-5: Maintenance information about events related to the job control
function
Position
Length (in bytes)
Item name and description
1
0 to 64
R/3 destination.
R/3 system destination specified by the -d option. If the -d
option is not used to specify the destination, the length of this
item is 0.
2
0 to 100
R/3 application server name.
Application server name specified by the -h option. If the -h
option is not used to specify the application server, the length of
this item is 0.
3
0 to 2
R/3 system number.
System number specified by the -s option. If the system number
was not specified by the -s option, the length of this item is 0.
4
1 to 3
R/3 client.
Client number of the R/3 client to be logged on to.
5
1 to 12
R/3 user.
Name of the user who registered the R/3 job.
6
0 to 1
R/3 language.
Language type specified by the -l option. If the language type
was not specified by the -l option, the length of this item is 0.
7
0 to 32
R/3 job name#1, #2.
Background job name registered for the application server.
163
5. Events
Position
Length (in bytes)
Item name and description
8
0 to 8
R/3 job count#1, #2.
Sequential number assigned to the R/3 job. If a job count could
not be assigned, the length of this item is 0.
9
0 to 16
External user name for R/3 job registration#1, #2.
Name of the user who executed a JP1/AJS3 for EAP command.
The length of this item is 0 for the child jobs that are detected
during the completion monitoring of parent and child jobs.
10
0 to 32
Host on which the job is to be registered#1, #2.
If the application server executing the job is not specified by the
-tgh option of the jr3bjsub command, the length of this item
is 0.
The length of this item is 0 for the child jobs that are detected
during the completion monitoring of parent and child jobs.
11
0 to 1
Job status#1, #2.
P: Scheduled
S: Released
Y: Ready
R: Active
F: Finished
A: Terminated
#1
For event 0x3F02 (detection of a job without confirmation of completion (child
job detection failure)), the information about the parent job is set.
#2
For event 0x3F03 (detection of a job without confirmation of completion
(number of jobs to be monitored exceeded the maximum limit)), the length of this
item is 0.
Table 5-6: Maintenance information about events related to the InfoPackage
control function
Position
1
164
Length (in bytes)
0 to 64
Item name and description
SAP BW destination.
SAP BW system destination specified by the -d option. If the -d
option is not used to specify the destination, the length of this
item is 0.
5. Events
Position
Length (in bytes)
Item name and description
2
0 to 100
SAP BW application server name.
Application server name specified by the -h option. If the -h
option is not used to specify the application server, the length of
this item is 0.
3
0 to 2
SAP BW system number.
System number specified by the -s option. If the system number
was not specified by the -s option, the length of this item is 0.
4
1 to 3
SAP BW client.
Client number of the SAP BW client to be logged on to.
5
1 to 12
SAP BW user.
Name of the user who registered InfoPackage.
6
0 to 1
SAP BW language.
Language type specified by the -l option. If the language type
was not specified by the -l option, the length of this item is 0.
7
30
InfoPackage ID.
ID of the started InfoPackage.
8
30
InfoPackage request number.
This number is assigned to InfoPackage by the SAP BW system
when InfoPackage is started. The length of this item is 0 if
assignment of an InfoPackage request number failed.
9
1
InfoPackage status.
Y: Active
G: Terminated normally
R: Terminated abnormally
The length of this item is 0 if InfoPackage failed to be started.
Table 5-7: Maintenance information about events related to the process chain
control function
Position
Length (in bytes)
Item name and description
1
0 to 64
SAP BW destination.
SAP BW system destination specified by the -d option. If the -d
option is not used to specify the destination, the length of this item is 0.
2
0 to 100
SAP BW application server name.
Application server name specified by the -h option. If the -h option is
not used to specify the application server, the length of this item is 0.
165
5. Events
Position
Length (in bytes)
Item name and description
3
0 to 2
SAP BW system number.
System number specified by the -s option. If the system number is not
specified by the -s option, the length of this item is 0.
4
1 to 3
SAP BW client.
Client number of the SAP BW client to be logged on to.
5
1 to 12
SAP BW user.
Name of the user who registered the process chain.
6
0 to 1
SAP BW language.
Language type specified by the -l option. If the language type is not
specified by the -l option, the length of this item is 0.
7
1 to 25
Process chain ID.
ID of the started process chain.
8
0 to 25
Log ID.
Log ID of a process chain assigned by the SAP BW system when the
process chain starts. The length of this item is 0 if assignment of a log
ID failed.
9
0 to 1
Process chain end status.
G: Ended normally
R: Ended abnormally
X: Ended forcibly.
The length of this item is 0 if the process chain is not ended.
166
Chapter
6. Messages
This chapter describes the format of messages output by JP1/AJS3 for EAP and the
remedial action to be taken when they are received.
6.1 Message format
6.2 Message list
167
6. Messages
6.1 Message format
This section describes the format of the messages output by JP1/AJS3 for EAP and the
output destinations of the messages.
6.1.1 Output format of messages
Messages output by JP1/AJS3 for EAP have the same format whether Windows or
UNIX is used. Messages consist of a message ID and a message text that follows the
message ID.
Figure 6-1 shows the format of messages output by JP1/AJS3 for EAP.
Figure 6-1: Format of messages output by JP1/AJS3 for EAP
The elements of the message ID are explained below.
KAJM
Indicates that the message is a JP1/AJS3 for EAP message.
nnnn
Indicates the message number. Messages are numbered according to the
following rules.
• 0nnn
Indicates that the message is common to all functions of JP1/AJS3 for EAP.
• 1nnn
Indicates that the message relates to the job control function.
• 2nnn
Indicates that the message relates to the InfoPackage control function or the
process chain control function.
When nnn in 0nnn, 1nnn, or 2nnn is between 600 and 699, the message relates to
a common command. When nnn is between 700 and 799, the message relates to
the installer.
When nnn is between 800 and 899, the message relates to the SAP BW system.
When nnn is between 900 and 999, the message (environment settings error,
system error, or forced termination) relates to JP1/AJS3 for EAP.
168
6. Messages
Z
Indicates the message type.
E: Error. The processing is aborted.
W: Warning. Processing continues after the message is output.
I: Information. Imparts information to the user.
The language types available for message generation vary with the OS used. For the
language types available for message generation, see 2. Installation and Setup.
6.1.2 Format of message explanations
This manual lists the JP1/AJS3 for EAP messages in order by message ID. The format
of the message in this manual is shown below:
Message ID
Message text
Message explanation
S:
System action
O:
The action that the operator should take if this message is output
6.2 Message list lists the messages output by JP1/AJS3 for EAP.
6.1.3 Output destinations of messages
The destination of the messages that are output by JP1/AJS3 for EAP differs
depending on the type of the message. The following table describes the output
destination for each type of message.
Message type
Output destination
E (error)
Standard error output
W (warning)
Standard error output
I (information)
Standard output
169
6. Messages
6.2 Message list
The JP1/AJS3 for EAP messages are divided into three sections. The first subsection
contains the messages common to all JP1/AJS3 for EAP functions. The second
subsection contains the messages specific to the job control function. The third
subsection contains the messages specific to the InfoPackage control function or the
process chain function.
6.2.1 Messages common to all JP1/AJS3 for EAP functions
KAJM0001-I
Usage:format
Display of a command format was requested.
KAJM0002-E
Invalid option. (option:option)
An invalid option was specified.
S:
The system aborts command execution.
O:
Specify the correct option and execute the command again.
KAJM0003-E
Argument must be specified for this option. (option:option)
No argument was specified for the option.
S:
The system aborts command execution.
O:
Specify an argument for the option and execute the command again.
KAJM0004-E
Value of option is invalid. (option:option)
The value specified for the option is invalid.
S:
The system aborts command execution.
O:
Specify the correct argument for the option and execute the command again.
170
6. Messages
KAJM0005-E
Option is duplicated. (option:option)
An option that cannot be duplicated has been specified twice.
S:
The system aborts command execution.
O:
Specify the option correctly and execute the command again.
KAJM0006-E
Required option is missing.
A required option was not specified.
S:
The system aborts command execution.
O:
Specify the required option and execute the command again.
KAJM0007-E
Mutually-exclusive options are specified.
Some of the specified options are mutually exclusive.
S:
The system aborts command execution.
O:
Correct the option specification and execute the command again.
KAJM0008-E
In the release of the R/3 system at the connection destination,
this option is not supported. (release:release, option:option)
The specified option is invalid on the R/3 system you connect to.
S:
The system aborts command execution.
O:
Check if the specified option is supported by the appropriate R/3 system release.
KAJM0009-E
In the release of the R/3 system at the connection destination,
this command is not supported. (release:release)
An attempt was made to execute a command that is not supported by the target R/3
171
6. Messages
system.
S:
The system aborts command execution.
O:
Check the release of the target R/3 system.
KAJM0010-W
The file that defines the environment contains an invalid key or
section name. (section: section-name, key: key-name)
The environment setup file contains an invalid value entry.
S:
The system ignores the invalid value in the environment setup file and continues
to execute the command.
O:
Ignore the warning or correct the contents of the environment setup file and
execute the command again.
KAJM0011-W
The file that defines the environment contains an error in a key
value. (section: section-name, key: key-name)
The environment setup file contains an incorrect key value.
S:
The system uses the default value specified by the conf.model file and
continues with command execution.
O:
Ignore the warning or correct the contents of the environment setup file and
execute the command again.
KAJM0012-W
The file that defines the environment contains a duplicated key
or section name. (section: section-name, key: key-name)
The environment setup file contains duplicate values.
S:
The system uses the first-specified value and continues with command execution.
O:
Ignore the warning or correct the contents of the environment setup file and
execute the command again.
172
6. Messages
KAJM0013-W
The file that defines the environment contains an invalid
string.
The environment setup file contains an invalid character string.
S:
The system ignores the invalid character string and continues with command
execution.
O:
Ignore the warning or correct the contents of the environment setup file, and
execute the command again.
KAJM0014-E
This option cannot be used because the RFC library corresponding
to the extended password is not set. (option: option)
An attempt was made to execute a command with the -p2 option specified (or with
Use an extended password selected during execution from a custom PC job) without
an RFC library having been set for the extended password.
S:
The system aborts command execution.
O:
Use the jr3chrfc command to set an RFC library for the extended password,
and then execute the command again.
KAJM0020-E
The default information file for the R/3 connection contains an
invalid key or section name. (section: section-name, key: key-name)
The R/3 default connection destination information file (r3defcon file) contains an
incorrect value.
S:
The system aborts command execution.
O:
Correct the contents of the R/3 default connection destination information file
(r3defcon file) and execute the command again.
KAJM0021-E
The default information file for the R/3 connection contains an
error in a key value. (section: section-name, key: key-name)
The R/3 default connection destination information file (r3defcon file) contains an
incorrect key value.
173
6. Messages
S:
The system aborts command execution.
O:
Correct the contents of the R/3 default connection destination information file
(r3defcon file) and execute the command again.
KAJM0022-E
The default information file for the R/3 connection contains a
duplicated key or section name. (section: section-name, key: key-name)
The R/3 default connection destination information file (r3defcon file) contains
duplicate values.
S:
The system aborts command execution.
O:
Correct the contents of the R/3 default connection destination information file
(r3defcon file) and execute the command again.
KAJM0023-E
The default information file for the R/3 connection lacks a
required section or key.
The R/3 default connection destination information file (r3defcon file) does not
contain a required key name entry or section name entry.
S:
The system aborts command execution.
O:
Correct the contents of the R/3 default connection destination information file
(r3defcon file) and execute the command again.
KAJM0024-E
The default information file for the R/3 connection contains
mutually-exclusive sections or keys.
The R/3 default connection destination information file (r3defcon file) contains
mutually exclusive key name entries or section name entries.
S:
The system aborts command execution.
O:
Correct the contents of the R/3 default connection destination information file
174
6. Messages
(r3defcon file) and execute the command again.
KAJM0025-E
The default information file for the R/3 connection contains an
invalid string.
The R/3 default connection destination information file (r3defcon file) contains an
invalid character string.
S:
The system aborts command execution.
O:
Correct the contents of the R/3 default connection destination information file
(r3defcon file) and execute the command again.
KAJM0026-E
The key specified in the default information file for the R/3
connection cannot be used because the RFC library corresponding
to the extended password is not set. (section: section-name, key:
key-name)
An attempt was made to execute a command with the Passwd2 key specified for the
R/3 default connection destination information file without an RFC library having
been set for the extended password.
S:
The system aborts command execution.
O:
Use the jr3chrfc command to set an RFC library for the extended password,
and then execute the command again.
KAJM0100-E
Insufficient memory.
System memory was insufficient during command execution.
S:
The system aborts command execution.
O:
Ensure that sufficient system memory is available, and execute the command
again.
KAJM0101-E
File cannot be accessed. (file: filename)
The file could not be accessed.
175
6. Messages
S:
The system aborts command execution.
O:
Check the status of the indicated file.
KAJM0102-E
There is not enough free space for creating or extending a file.
(file: filename)
Disk space was insufficient during command execution.
S:
The system aborts command execution.
O:
Check for available space on the disk that is selected for the creation or extension
of the indicated file.
KAJM0103-W
File that defines the environment cannot be accessed. (file:
filename)
The environment setup file could not be accessed.
S:
The system uses the default value specified by the conf.model file and
continues with command execution.
O:
Check the status of the environment setup file.
KAJM0104-W
Trace file cannot be accessed. (file: filename)
The trace file could not be accessed.
S:
The system continues with command execution. However, trace information
output may not be sent to the trace file.
O:
Check the status of the trace file.
KAJM0105-E
Failed to access the default information file for the R/3
connection. (file: filename)
The R/3 default connection destination information file (r3defcon file) could not be
176
6. Messages
accessed.
S:
The system aborts command execution.
O:
Check the status of the R/3 default connection destination information file
(r3defcon file).
KAJM0106-W
There is not enough free space for creating or extending a trace
file. (file: filename)
Disk space was insufficient while trace information was being output to the trace file.
S:
The system continues with command execution. However, the trace information
may not be sent to the trace file.
O:
Check for available space on the disk containing the trace file.
KAJM0600-E
You do not have permission to execute the command.
An attempt to execute the command was made by a user who does not have
Administrator permissions.
If the user account control function (UAC) of the OS is enabled, execute the command
from the command prompt of the standard role.
This message is output for the Windows version only.
S:
The system aborts command execution.
O:
Have a user who has Administrator permissions execute the command again.
If the user account control function (UAC) of the OS is enabled, execute the
command at the command prompt using Administrator permissions.
KAJM0601-I
The RFC library setting was changed.
The RFC library setting was successfully changed by executing the jr3chrfc
command.
177
6. Messages
S:
The command ends normally.
KAJM0602-E
An attempt to open the RFC library status management file has
failed. (file: filename, maintenance code: maintenance-code)
An unrecoverable error occurred when opening the RFC library status management
file.
For filename in the message, the absolute path to the RFC library status management
file is output. For maintenance-code in the message, the API error code returned by the
OS is output.
S:
The system aborts command execution.
O:
Verify that the path to the RFC library status management file is correct, and then
execute the command again. If the status still does not recover, delete the RFC
library status management file, use the jr3chrfc command to set up the file
again, and then execute once more the command that caused the error.
KAJM0603-E
An attempt to lock the RFC library status management file has
failed. (file: filename, maintenance code: maintenance-code)
The possible causes of the error are as follows:
• During installation or patch execution, or while an RFC library setting was being
changed using the jr3chrfc command, the JP1/AJS3 for EAP command that
references the RFC library settings was executed.
• During execution of the JP1/AJS3 for EAP command that references the RFC
library settings, an RFC library setting was changed using the jr3chrfc
command.
For filename in the message, the absolute path to the RFC library status management
file is output. For maintenance-code in the message, the API error code returned by the
OS is output.
S:
The system aborts command execution.
O:
After changing or referencing the RFC library setting is completed, execute the
command again. If the status still does not recover, delete the RFC library status
management file, use the jr3chrfc command to set up the file again, and then
178
6. Messages
execute once more the command that caused the error.
KAJM0604-E
An attempt to read the RFC library status management file has
failed. (file: filename, maintenance code: maintenance-code)
An unrecoverable error occurred while reading the RFC library status management
file.
For filename in the message, the absolute path to the RFC library status management
file is output. For maintenance-code in the message, the API error code returned from
the OS is output.
S:
The system aborts command execution.
O:
Verify that the path to the RFC library status management file is correct, and then
execute the command again. If the status still does not recover, delete the RFC
library status management file, use the jr3chrfc command to set up the file
again, and then execute once more the command that caused the error.
KAJM0605-E
An attempt to write to the RFC library status management file
has failed. (file: filename, maintenance code: maintenance-code)
During a change to an RFC library setting using the jr3chrfc command, an
unrecoverable error occurred while writing to the RFC library status management file.
For filename in the message, the absolute path to the RFC library status management
file is output. For maintenance-code in the message, the API error code returned by the
OS is output.
S:
The system aborts command execution.
O:
Verify that the path to the RFC library status management file is correct and that
there is available space on the disk, and then execute the command again. If the
status still does not recover, delete the RFC library status management file, use
the jr3chrfc command to set up the file again, and then execute once more the
command that caused the error.
KAJM0606-E
The contents of the RFC library status management file are
invalid. (file: filename)
The RFC library status management file contains an error.
179
6. Messages
For filename in the message, the absolute path to the RFC library status management
file is output.
S:
The system aborts command execution.
O:
Use the jr3chrfc command to set up the RFC library setting again, and then
execute the command. If the status still does not recover, delete the RFC library
status management file, use the jr3chrfc command to set up the file again, and
then execute once more the command that caused the error.
KAJM0607-E
There is not enough free space to copy the RFC library file.
(source: filename, target: filename)
Disk space ran out while the RFC library file was being copied.
For filename in the inserted source paragraph, the absolute path to the RFC library file
of the copy source is output. For filename in the inserted target paragraph, the absolute
path to the copy destination RFC library file is output.
This message is output when an RFC library setting is changed using the Windows
version of the jr3chrfc command.
S:
The system aborts command execution.
O:
Delete unnecessary files to free up some disk space at the copy destination, and
then execute the jr3chrfc command again.
KAJM0608-E
The RFC library file cannot be copied. (source: filename, target:
filename, maintenance code: maintenance-code)
An error that is not attributable to a lack of disk space occurred while the RFC library
file was being copied.
For filename in the inserted source paragraph, the absolute path to the RFC library file
of the copy source is output. For filename in the inserted target paragraph, the absolute
path to the copy destination RFC library file is output. For maintenance-code in the
message, the API error code returned from the OS is output.
This message is output when an RFC library setting is changed using the Windows
version of the jr3chrfc command.
S:
The system aborts command execution.
180
6. Messages
O:
Delete the file at the copy destination, and then execute the command again.
KAJM0609-E
The symbolic link file cannot be created. (file: filename,
maintenance code: maintenance-code)
An error occurred during creation of the symbolic link file.
For filename in the message, the absolute path to the symbolic link file the system is
attempting to create is output. For maintenance-code in the message, the API error
code returned from the OS is output.
This message is output when an RFC library setting is changed using the UNIX version
of the jr3chrfc command.
S:
The system aborts command execution.
O:
Delete the symbolic link file, and then execute the command again.
KAJM0700-E
An attempt to open the RFC library status management file has
failed. (file: filename, maintenance code: maintenance-code,
maintenance message: maintenance-message)
An unrecoverable error occurred when opening the RFC library status management
file.
For filename in the message, the absolute path to the RFC library status management
file is output. For maintenance-code and maintenance-message in the message, the
API error code returned from the OS and the corresponding error message are output.
S:
The system terminates installation or patch execution.
O:
Check whether the path to the RFC library status management file is correct, and
then perform installation or patch execution. If the status still does not recover,
delete the RFC library status management file and then perform installation or
patch execution. After that, use the jr3chrfc command to set up the RFC library
status management file again.
KAJM0701-E
An attempt to lock the RFC library status management file has
failed. (file: filename, maintenance code: maintenance-code,
maintenance message: maintenance-message)
181
6. Messages
Installation or patch execution was performed while using a JP1/AJS3 for EAP
command to reference or change an RFC library setting.
For filename in the message, the absolute path to the RFC library status management
file is output. For maintenance-code and maintenance-message in the message, the
API error code returned from the OS, and the corresponding error message are output.
S:
The system terminates installation or patch execution.
O:
After changing or referencing the RFC library setting is completed, perform
installation or patch execution again. If the status still does not recover, delete the
RFC library status management file and then perform installation or patch
execution. After that, use the jr3chrfc command to set up the RFC library status
management file again.
KAJM0702-E
An attempt to read the RFC library status management file has
failed. (file: filename, maintenance code: maintenance-code,
maintenance message: maintenance-message)
An unrecoverable error occurred while reading the RFC library status management
file.
For filename in the message, the absolute path to the RFC library status management
file is output. For maintenance-code and maintenance-message in the message, the
API error code returned from the OS, and the corresponding error message are output.
S:
The system terminates installation or patch execution.
O:
Check whether the path to the RFC library status management file is correct, and
then perform installation or patch execution. If the status still does not recover,
delete the RFC library status management file and then perform installation or
patch execution. After that, use the jr3chrfc command to set up the RFC library
status management file again.
KAJM0703-E
The contents of the RFC library status management file are
invalid. (file: filename)
The RFC library status management file contains an error.
For filename in the message, the absolute path to the RFC library status management
file is output.
182
6. Messages
S:
The system terminates installation or patch execution.
O:
Delete the RFC library status management file and then perform installation or
patch execution. After that, use the jr3chrfc command to set up the RFC library
status management file again.
KAJM0704-E
There is not enough free space to copy the RFC library file.
(source: filename, target: filename)
Disk space ran out while the RFC library file was being copied.
For filename in the source message, the absolute path to the RFC library file of the
copy source is output. For filename in the target message, the absolute path to the copy
destination RFC library file is output.
S:
The system terminates installation or patch execution.
O:
Delete unnecessary files to free up some disk space at the copy destination, and
then perform installation or patch execution again.
KAJM0705-E
The RFC library file cannot be copied. (source: filename, target:
filename, maintenance code: maintenance-code, maintenance message:
maintenance-message)
An error that is not attributable to a lack of disk space occurred while the RFC library
file was being copied.
For filename in the source message, the absolute path to the RFC library file of the
copy source is output. For filename in the target message, the absolute path to the copy
destination RFC library file is output. For maintenance-code and
maintenance-message in the message, the API error code returned from the OS and the
corresponding error message are output.
S:
The system terminates installation or patch execution.
O:
Delete the RFC library status management file, and then perform installation or
patch execution again.
183
6. Messages
KAJM0801-E
Cannot connect to the R/3 system. (address: destination-name, host:
host-name, system No.: system-number)
A communication error occurred before RFC connection with the R/3 system was
established.
Immediately after this message, the name of the function where the error occurred and
a KAJM0802-E error message providing detailed information are output.
The possible causes of the error are as follows:
• The RFC connection information is incorrect (for example, the system number is
incorrect and the host name cannot be resolved).
• The R/3 system is inactive.
• The R/3 system is too busy to accept an RFC request.
• The network settings are incorrect.
S:
The system attempts to reconnect to the R/3 system if retry is specified.
If retry is not specified, the system aborts command execution.
O:
Consider specifying retry if no retry is specified (version 07-00 and earlier do not
retry by default).
KAJM0802-E
Operation : function
detailed-information ...
An error occurred when JP1/AJS3 for EAP called the RFC API (communication
function provided by SAP).
A message appears indicating the name of the function where the error occurred and
providing detail information about the RFC API error. The language used for the
message depends on the language (-l option specification value) specified during
logon to the SAP BW system.
The meaning of the values in the message is as follows:
• group: Integer for identifying key (three bytes)
• key: Code for identifying the error (32 bytes or less)
• message: Description of the error (messages may include linefeed characters and
are 512 bytes or less)
For these values, the values of the members in the RFC_ERROR_INFO_EX structure are
specified without changes. This structure is acquired using the GetRfcLastErrorEx
184
6. Messages
function that returns an RFC API error. For details about the RFC, see the R/3
documentation.
S:
The system aborts command execution.
O:
Identify the cause of the error and correct the problem.
KAJM0803-E
A communication error occurred with the R/3 system. (address:
destination-name, host: host-name, system No.: system-number)
An error occurred when JP1/AJS3 for EAP called the RFC API (communication
function provided by SAP).
Immediately after this message, the name of the function in which the error occurred
and a KAJM0802-E error message providing detailed information are output.
The possible causes of the error are as follows:
• The R/3 system is inactive.
• The R/3 system is too busy to accept an RFC request.
• The network settings are incorrect.
S:
If the communication error occurred while establishing communication or
monitoring the end of a job and retry is specified, the system attempts to reconnect
to the R/3 system. If the error occurred in other circumstances or if no retry is
specified, the system aborts command execution.
O:
Consider specifying retry if no retry is specified (version 07-00 and earlier do not
retry by default).
KAJM0804-E
Cannot log on to the R/3 system. (client: client, user: user-name,
language: language-name)
A logon error occurred when JP/AJS3 for EAP attempted to establish an RFC
connection with the R/3 system.
Immediately after this message, a KAJM0802-E message appears indicating the name
of the function where the error occurred and providing detailed information about the
error.
The possible causes of the error are as follows:
• The RFC connection information is incorrect (for example, a non-existent user or
185
6. Messages
incorrect password is specified).
• The user is locked out.
• The user was not granted the S_RFC permission correctly.
• An extended password containing lower-case characters is defined in the SAP
system based on SAP NetWeaver 7.0 and later, but connection information (-p
option or Passwd key of the r3defcon file) that does not correspond to the
extended password is specified.
S:
The system aborts command execution.
O:
Check the logon information used to log on to the R/3 system specified by the
command.
KAJM0805-I
Now recovering connection with the R/3 system. (address:
destination-name, host: host-name, system No.: system-number, retry-time:
retry-time-in-minutes min., retry-count: number-of-retries times)
The connection with the R/3 system is now being recovered.
retry-time in the message is output when the RetryTime key specified in the
command section of the environment setup file is valid. number-of-retries in the
message is output when the RetryCount key in the command section of the
environment setup file is valid.
S:
JP1/AJS3 for EAP reconnects with the R/3 system. If reconnection is performed
within the retry-time or number-of-retries limit, JP1/AJS3 for EAP continues
command processing. Otherwise, the system aborts command execution.
KAJM0806-I
Connection was recovered with the R/3 system. (address:
destination-name, host: host-name, system No.: system-number)
JP1/AJS3 for EAP has reconnected with the R/3 system.
KAJM0807-E
Time-out occurred in the connection with the R/3 system.
(address: destination-name, host: host-name, system No.: system-number)
JP1/AJS3 for EAP could not restore a connection with the R/3 system within the
specified reconnection retry time.
S:
The system aborts command execution.
186
6. Messages
O:
Read the messages that are output before this message and the R/3 system log to
determine the cause of the error. Check whether the value of the retry count or
retry time (RetryCount key or RetryTime key in the command section of the
environment setup file) is appropriate.
KAJM0810-E
The external management interface is not supported. (interface:
interface-name, version: version)
The external management interface version of the destination R/3 system does not
agree with the version asumed by JP1/AJS3 for EAP.
For interface-name and version in the message, the interface name and version of the
external management interface are output. However, the version is not output if the
version of the external management interface is not set.
S:
The system aborts command execution.
O:
Check the external management interface version of the destination R/3 system.
Note
The interface name and version number are provided with the message only
when they can be determined.
KAJM0811-E
Cannot log on to an external management interface. (interface:
interface-name, version: version)
An attempt to log on to the R/3 system external management interface was denied
(BAPI error).
The possible causes of the error are as follows:
• The connection destination R/3 system does not support the interface.
• The user was not granted the S_XMI_PROD permission correctly.
S:
The system aborts command execution.
O:
Check the following:
• Check whether the release and patch level of SAP Basis (SAP WebAS) of
187
6. Messages
the connection destination R/3 system satisfy the prerequisites.
• Check whether the user specified in the R/3 logon information is authorized
to log on to the external management interface.
Note
The interface name and version number are provided with the message only
when they can be determined.
KAJM0812-E
Error occurred at the external management interface. (interface:
interface-name, version: version)
The R/3 system external management interface returned an error. Immediately after
this message, a KAJM0813-E message appears indicating the name of the function
where the error occurred and the exception code.
S:
If more than one process was requested, the system continues with the subsequent
process.
O:
Check the R/3 system log to identify the cause of the error, fix the problem, and
then execute the command again.
Note
The interface name and version number are provided with the message only
when they can be determined.
KAJM0813-E
Function: function, Exception: exception
detailed-information
A general-purpose module of the R/3 system returned an error.
The name of the function where the error occurred and the exception code are output.
For BAPI, the detailed information about the external management interface error is
output after Detail. The language used for the message depends on the language (-l
option specification value) specified during logon to the SAP BW system. The
meaning of the values in the message is as follows:
• Type: One of the following characters (one byte) that indicates the importance of
the message
S: Normal
E: Error
188
6. Messages
W: Warning
I: Information
A: Forced termination
• Id: Message class (20 bytes or less)
• Number: Error code for identifying the error (three bytes or less)
• Message: Description of the error (220 bytes or less)
• LogNo: Log number for identifying the application log (20 bytes or less)
• LogMsgNo: Message number for identifying the message output to the application
log (six bytes or less)
For these values, the values of the members in the BAPIRET2 structure that contains
the BAPI error are specified without changes. For details about BAPI, see the R/3
system documentation. For details about the specifications of the BAPI that is called,
see the object navigator (SE80) documentation of the R/3 system, the BAPI browser
documentation (BAPI), or the R/3 documentation.
S:
If more than one process was requested, the system continues with the subsequent
process. If only one process is requested, the system aborts the process.
O:
Check the R/3 system log to identify the cause of the error, fix the problem, and
then execute the command again.
KAJM0820-E
There is no authority to perform this operation.
The specified R/3 user is not authorized to execute this operation.
S:
If more than one process was requested, the system continues with the subsequent
process.
O:
If more than one process was requested, the system continues with the subsequent
process. If only one process was requested, the system aborts the process.
KAJM0830-W
Failed to change an audit-level.
The audit level was not changed.
189
6. Messages
S:
The system continues processing without changing the audit level.
O:
Check the R/3 system log and other relevant information to investigate the cause
of the problem.
KAJM0900-E
Command terminated abnormally. (command: command-name)
An error occurred in JP1/AJS3 for EAP during command processing.
S:
The system aborts command execution.
O:
Gather the information needed to investigate the cause of the problem, and then
contact the system administrator.
KAJM0901-E
The user canceled the command. (command: command-name)
Command processing was aborted due to a Ctrl-C signal sent from the user or for
some other reason during command execution.
S:
The system aborts command execution.
KAJM0902-E
The product is not installed correctly.
JP1/AJS3 for EAP is not correctly installed.
S:
The system aborts command execution.
O:
Reinstall JP1/AJS3 for EAP.
KAJM0990-E
The evaluation period of (p.p.name) Trial Version expired.
An attempt was made to execute the command after the trial version had expired.
S:
The system aborts command execution.
190
6. Messages
KAJM0992-E
The product information could not be acquired. (Detailed
information: function-name, return-value)
Command execution failed because of insufficient resources or because the
environment is invalid.
S:
The system aborts command execution.
O:
Check whether system resources are insufficient.
If so, secure sufficient resources, and then execute the command again. If the
problem cannot be resolved, uninstall and then reinstall JP1/AJS3 for EAP, and
then execute the command again. If the problem is still not resolved, collect data,
and then contact the system administrator.
6.2.2 Messages specific to the job control function
KAJM1001-E
100 or more items of job step information were specified.
More than 99 items of job step information were specified.
S:
The system aborts command execution.
O:
Decrease the number of job step information items to 99 or fewer, and then
execute the command again.
KAJM1002-E
Job name cannot be omitted.
The job name -jn job-name was not specified.
S:
The system aborts command execution.
O:
Specify the job name -jn job-name, and then execute the command again.
KAJM1003-E
Program name cannot be omitted.
Required job step information was not specified.
191
6. Messages
S:
The system aborts command execution.
O:
Specify the required job step information, and then execute the command again.
KAJM1004-E
Job count cannot be omitted.
No job count was specified. When monitoring job completion, make sure to specify a
job count.
S:
The system aborts command execution.
O:
Specify the job count and then execute the command again.
KAJM1005-E
The name of the host that executes an external program cannot be
omitted.
The host name was not specified by the job step information for external program
execution.
S:
The system aborts command execution.
O:
Specify the host name and then execute the command again.
KAJM1006-E
The specified monitoring time is shorter than the monitoring
interval.
The job completion monitoring time is shorter than the job monitoring interval setting.
S:
The system aborts command execution.
O:
Specify the correct value and then execute the command again.
KAJM1007-E
The specified archive parameter is incomplete.
If you specify Archive or Print and archive for Archiving mode, you must also
specify Object type, Document type, and Information ID.
192
6. Messages
S:
The system aborts command execution.
O:
Revise Archiving mode and the archive parameters settings, and then execute the
command again.
KAJM1009-E
To specify this option, a new version of the XBP interface is
required. (option: option)
To specify the following options of the jr3bjsub or jr3bjrel command, you must
enable the external management interface, which is XBP version 2.0 (XBP 2.0
interface):
-with_child, -class, -title, -dpt, -fmt, -text
For details, see the description of the jr3bjsub or jr3bjrel command in 4.
Commands.
S:
The system aborts command execution.
O:
Enable the XBP 2.0 interface at the connection destination R/3 system. For
details, see 2.2.8(1) Enabling the XBP 2.0 interface.
KAJM1010-E
The parent-child function is set to OFF in the connected SAP
system.
Although completion monitoring for parent and child jobs (-with_child option) is
specified, the parent and child function is disabled in the R/3 system.
S:
The system aborts command execution.
O:
Enable the parent and child function in the connection destination R/3 system.
For details, see 2.2.8 (2) Enabling the parent and child function.
KAJM1800-E
No job satisfies the specified conditions.
There is no job that meets the specified conditions.
S:
The system aborts command execution.
193
6. Messages
O:
Specify the correct job and then execute the command again.
KAJM1801-E
This program does not exist. (program: program-name)
The specified program is not defined in the R/3 system.
S:
The system aborts command execution.
O:
Check whether the program name specified in the command is valid for the R/3
system. If necessary, define the specified program for the R/3 system, and then
execute the command again.
KAJM1802-E
A step required for execution is not defined.
The job step definition for the job is not complete.
S:
The system aborts command execution. If more than one process was requested,
the system continues with the subsequent process.
O:
Check the job step information definition.
KAJM1803-E
The job has already finished.
The specified job has already ended.
S:
The system aborts command execution. If more than one process was requested,
the system continues with the subsequent process.
O:
Check the job name and job count specified for the command.
KAJM1804-W
Failed to acquire an R/3 job log. (job name: job-name, job count:
job-count)
Job log acquisition was not successful.
job-name and job-count in the message are output only for JP1/AJS2 for EAP 07-50
or later.
194
6. Messages
S:
The system continues with command execution.
O:
Check the messages that are output before this message and the R/3 system log to
determine the cause of the error.
If KAJM0101-E was output immediately before this message, it is possible the
path specified as the job log output destination contains an error.
Check with the JP1/AJS3 for EAP host as to whether any of the following factors
exist:
• A nonexistent folder or directory is specified.
• The specified file is read-only (for the Windows version).
• The user does not have command execution write permission for the
specified file.
KAJM1805-E
The job log no longer exists.
The job log file for the specified job was not found in the R/3 system (it was illegally
deleted). Or, the job log file for the job specified in the R/3 system has not been created.
S:
The system aborts the job log acquisition/display operation. If more than one
process was requested, the system continues with the subsequent process.
O:
Execute the command again after execution of the specified job is completed. If
the situation does not change when the command is executed again, contact the
R/3 system administrator.
KAJM1806-E
Condition: Condition
Displays the condition for the preceding on-screen message.
KAJM1807-E
A log does not yet exist for the specified job.
A job log file for the specified job was not created in the R/3 system.
S:
The system aborts the job log acquisition/display operation. If more than one
process was requested, the system continues with the subsequent process.
195
6. Messages
O:
Execute the command again after the specified job is completed. If the situation
does not change when the command is executed again, contact the R/3 system
administrator.
KAJM1808-E
Job log is empty.
The job log was not output to the job log file for the specified job.
S:
The system aborts the job log acquisition/display operation. If more than one
process was requested, the system continues with the subsequent process.
O:
Wait for a while, and then execute the command again. If the situation does not
change when the command is executed again, contact the R/3 system
administrator.
KAJM1811-I
Job was created. (job name: job-name, job count: job-count)
The job was created in the R/3 system.
KAJM1812-E
Could not create the job. (job name: job-name, job count: job-count)
The job was not registered in the R/3 system.
S:
The system aborts command execution.
O:
Note any other on-screen messages, check the R/3 system log, and investigate the
cause of the problem. If the job count is displayed, it is possible that an incomplete
job (unexecutable job) may have been registered in the R/3 system.
KAJM1813-E
This variant does not exist. (variant: variant-name)
The specified variant was not found in the R/3 system.
S:
The system aborts command execution.
O:
Specify a correct variant name and then re-execute the command.
If this message appears even though a correct variant name has been specified, a
196
6. Messages
variant without a name may be registered in the specified program.
If a variant without a name is registered, take either of the following actions:
• Delete the variant without a name from the VARI table of the R/3 system.
• Change the setting (change the value of the CheckLevel key in the
command section of the environment setup file to 0) so that the validity of
the ABAP program and the values specified for variants are not checked, and
then re-execute the command.
If no variant without a name is registered, check the variant name and then
re-execute the command.
KAJM1814-E
This program is not executable. (program: program-name)
The specified program cannot be executed.
S:
The system aborts command execution.
O:
Check the status of the program specified by the command and the variant
information for the program.
KAJM1815-E
A variant required for executing this program is not specified.
(program: program-name)
The variant required for the specified program was not specified when the job was
registered.
S:
The system aborts command execution.
O:
Check whether the specified program runs normally without specifying variants.
If the program requires variants, specify the necessary variants and then
re-execute the command.
If the program does not require variants, change the setting (change the value of
the CheckLevel key in the command section of the environment setup file to 0)
so that the validity of the ABAP program and the values specified for variants are
not checked, and then re-execute the command.
KAJM1816-E
A program in ABAP cannot be assigned to a job step. (program:
program-name)
197
6. Messages
The job step for executing the indicated ABAP program could not be assigned.
S:
The system aborts command execution.
O:
Review the job step information.
KAJM1817-E
An external program cannot be assigned to a job step. (program:
program-name)
An external program was not assigned a job step for execution.
S:
The system aborts command execution.
O:
Review the job step information.
KAJM1818-E
No variant is defined to the program.(program: program-name)
No variant is defined for the specified program.
S:
The system aborts command execution.
O:
Check whether the specified program runs normally without specifying variants.
If the program requires variants, define the necessary variants in the program,
specify the defined variants, and then re-execute the command.
If the program does not require variants, change the setting (change the value of
the CheckLevel key in the command section of the environment setup file to 0)
so that the validity of the ABAP program and the values specified for variants are
not checked, and then re-execute the command.
KAJM1819-W
The incomplete job cannot be deleted. (job name: job-name, job
count: Job-count)
JP1/AJS3 for EAP could not delete the job that was being created with an incomplete
definition when registration of another job failed.
S:
The system continues command execution without deleting the job indicated by
job-name and job-count.
198
6. Messages
O:
Execute the jr3bjdel command to delete the job indicated by job-name and
job-count.
KAJM1820-E
The job was already released.
The specified job has already been released. You cannot release a job that has already
been released.
S:
If no job count was specified, the system continues processing subsequent jobs.
If there is no subsequent job or if a job count was specified, the system aborts
command execution.
O:
Check the job name and job count specified by the command.
KAJM1821-I
Job was released. (job name: job-name, job count: job-count)
The specified job was released.
KAJM1822-E
No background work processes are free.
The R/3 system background work processes are not free.
S:
If no job count was specified, the system continues processing subsequent jobs.
If there is no subsequent job or if a job count was specified, the system aborts
command execution.
O:
Wait for a while, and then execute the command again.
KAJM1825-E
The job cannot be released. (job name: job-name, job count:
job-count)
The specified job was not released.
S:
The system aborts command execution.
O:
Note the preceding on-screen messages, check the R/3 system log, and investigate
the cause of the problem.
199
6. Messages
KAJM1830-I
Now monitoring job-end. (monitoring time: monitoring-time-in-minutes
min.)
Job execution completion monitoring has been started.
S:
The system continues with job execution completion monitoring.
KAJM1831-E
Job-end monitoring is canceled because a timeout occurred. (job
name: job-name, job count: job-count)
Since the job did not end within the monitoring limit, job completion monitoring was
terminated.
S:
If an option for R/3 job cancellation was selected, the R/3 job is canceled when a
timeout occurs. If the option for R/3 job cancellation was not selected, command
execution is canceled when a timeout occurs.
O:
Check the R/3 job status and, if necessary, abort R/3 job execution.
KAJM1832-I
Job has finished. (job name: job-name, job count: job-count, status:
Finished)
The job has ended.
KAJM1833-W
The job was terminated. (job name: job-name, job count: job-count,
status: Terminated)
Job execution was terminated in the R/3 system.
O:
Check the job log and other relevant information, and investigate the cause of the
unexpected job termination.
KAJM1834-E
Could not monitor job-end. (job name: job-name, job count: job-count)
Job completion monitoring failed.
S:
The system aborts command execution.
O:
Note any preceding on-screen messages, check the R/3 system log, and
200
6. Messages
investigate the cause of the problem.
Use the SAP front-end software to check the status of the R/3 job. Cancel the R/
3 job if necessary.
KAJM1835-E
Job-end monitoring is canceled because a reconnection timeout
occurred. (job name: job-name, job count: job-count)
Job completion monitoring has been canceled because the connection with the R/3
system could not be restored within the reconnection retry time.
S:
The system aborts command execution.
O:
Check the messages that were output before this message and the R/3 system log
to determine the cause of the error. Check whether the value of the retry count or
the retry time (RetryCount key or RetryTime key in the command section of
the environment setup file) is appropriate.
Use the SAP front-end software to check the status of the R/3 job. Cancel the R/
3 job if necessary.
KAJM1836-W
The job was intercepted. (job name: job-name, job count: job-count)
A job whose completion is being monitored by JP1 has been interrupted by the R/3
system.
An interrupt occurs when the following conditions are satisfied:
• The XBP 2.0 interface is installed.
• The interrupt function is enabled using the INITXBP2 report program.
• Interrupt criteria that cause the job to be interrupted are set in the TBCICPT1 table.
S:
The system continues command execution (continues completion monitoring for
jobs, including the interrupted job).
O:
Release the interrupted job again. (Completion monitoring by JP1 is not
completed because the interrupted job is returned to Scheduled status by the R/3
system.)
KAJM1837-W
The job was deleted or state is unknown. (job name: job-name, job
count: job-count)
201
6. Messages
A job whose completion is being monitoring by JP1 is deleted (or the status of the job
is unknown).
If this message appears for a child job that is detected during completion monitoring
of parent and child jobs, the parent job may have been set at registration so that it is
automatically deleted at normal end.
S:
The system continues completion monitoring and returns 1, indicating that the
result of at least one job could not be checked.
O:
Register the target job so that it will not be deleted during completion monitoring.
If this message appears when there are jobs in the R/3 system, check the R/3
system log for the cause.
KAJM1838-W
The job is not released. (job name: job-name, job count: job-count)
A scheduled child job was detected during job completion monitoring. The child job
may have been registered without specifying the start attribute, or a user without
release permissions may have registered the child job.
S:
The system continues command execution (continues completion monitoring for
jobs, including the scheduled job).
O:
First, to complete completion monitoring, release the scheduled job.
Next, check whether the job start attribute is specified in the program that is
specified for the parent job of the registered child job. If the authorized user of the
ABAP program is changed using the -auth option, check whether the specified
user has release permissions for the job.
If you do not require completion monitoring of jobs including this job, consider
not specifying the -with_child option.
KAJM1840-I
The job was canceled. (job name: job-name, job count: job-count)
R/3 job execution was canceled.
KAJM1841-E
Job cannot be canceled because it is not active.
Although an attempt was made to cancel a job, it was not active.
202
6. Messages
S:
If no job count was specified, the system continues processing subsequent jobs.
If there is no subsequent job or if a job count was specified, the system aborts
command execution.
O:
Check the status of the job to be canceled. Execute the jr3bjcan command after
the job becomes active.
KAJM1844-E
The job cannot be canceled. (job name: job-name, job count:
job-count)
The specified job was not canceled.
S:
The system aborts command execution.
O:
Note any preceding on-screen messages, check the R/3 system log, and
investigate the cause of the problem.
KAJM1845-E
Unable to determine available server from execution host.
The server on which the job is to be run cannot be determined from the host name
assigned to the -tgh option.
S:
The system aborts command execution.
O:
Check whether the specified host name is correct, and whether a SAP instance is
correctly allocated to the host.
The -tgh option is a compatible parameter of the job definition created for
Releae 4.0 and earlier R/3 systems. To define a job for Release 4.5 and later R/3
systems, use the -tgs option.
KAJM1850-I
The job was deleted. (job name: job-name, job count: job-count)
The R/3 job specified by the jr3bjdel command was deleted.
KAJM1851-E
The job cannot be deleted. (job name: job-name, job count: job-count)
An attempt to delete the specified job failed.
203
6. Messages
S:
The system aborts command execution.
O:
Determine the cause by reading the messages that precede this one, and by
checking the R/3 system log.
KAJM1852-E
The job cannot be deleted because it is active or ready.
The specified job is active or ready.
S:
If no job count was specified, the system continues processing subsequent jobs.
If no subsequent job exists or if a job count is specified, the system aborts
command execution.
O:
Check the status of the job to be deleted. When the job is finished or terminated,
execute the jr3bjdel command. If you want to delete an active or ready job,
wait until job execution ends or use the jr3bjcan command to cancel the job,
and then delete it.
KAJM1870-I
The child job was detected. (job name: job-name, job count:
job-count, child job name: child-job-name, child job count:
child-job-count)
JP1/AJS3 for EAP detected a child job of a finished or terminated job during
completion monitoring of parent and child jobs.
S:
The system executes completion monitoring of the detected child job (completion
monitoring is extended).
KAJM1871-W
The child job was undetectable. (job name: job-name, job count:
job-count)
JP1/AJS3 for EAP failed to detect the child job of a job that is deleted. Immediately
before this message, a KAJM0812-E or KAJM0813-E message appears indicating the
cause of the error.
If this message appears for a child job that is detected during completion monitoring
of parent and child jobs, the parent job may have been set at registration so that it is
automatically deleted at normal end.
204
6. Messages
S:
The system continues completion monitoring and returns 1 to indicate that the
result of at least one job could not be checked.
O:
Register the target job so that it will not be deleted during completion monitoring.
KAJM1872-W
The maximum number of monitored jobs was exceeded. (maximum
number: maximum-number)
When maximum-number is 100, JP1/AJS3 for EAP can monitor the completion of one
job that is released from JP1 and 99 child jobs generated during its execution.
S:
The system does not detect any subsequent child jobs. The system continues
completion monitoring and returns 1 to indicate that the result of at least one job
could not be checked.
O:
Divide jobs or take other measures to ensure that the number of jobs being
monitored does not exceed the maximum limit.
6.2.3 Messages specific to the InfoPackage control function and the
process chain control function
KAJM2001-E
InfoPackage-ID or process-chain-ID cannot be omitted.
The required InfoPackage ID or process chain ID is not specified.
S:
The system aborts command execution.
O:
Specify the required InfoPackage ID or process chain ID and re-execute the
command.
KAJM2002-E
In the release of the SAP BW system at the connection
destination, this command is not supported. (release: release)
The executed command is invalid on the SAP BW system to which you want to
connect.
For release in the message, the release of SAP Basis included in the connection
destination SAP BW system is output.
205
6. Messages
S:
The system aborts command execution.
O:
Verify that the release of the SAP BW system at the connection destination
supports the executed command.
KAJM2801-E
Cannot connect to the SAP BW system. (address: destination-name,
host: host-name, system No.: system-number)
A communication error occurred when JP1/AJS3 for EAP attempted to establish an
RFC connection with the SAP BW system.
Immediately after this message, a KAJM2802-E message appears indicating the name
of the function where the error occurred and providing detailed information about the
error.
The possible causes of the error are as follows:
• The RFC connection information is incorrect (for example, the system number is
incorrect and the host name cannot be resolved).
• The SAP BW system is inactive.
• The SAP BW system is too busy to accept an RFC request.
• The network settings are incorrect.
S:
If retry is specified, the system attempts to reconnect to the SAP BW system.
If retry is not specified, the system aborts command execution.
O:
Consider specifying retry if no retry is specified (version 07-00 and earlier do not
retry by default).
KAJM2802-E
Operation : function
detailed-information ...
An error occurred when JP1/AJS3 for EAP called the RFC API (communication
function provided by SAP).
A message appears indicating the name of the function where the error occurred and
providing detailed information about the RFC API error. The language used for the
message depends on the language (-l option specification value) specified during
logon to the SAP BW system.
The meaning of the values in the message is as follows:
206
6. Messages
• group: Integer for identifying key (three bytes)
• key: Code for identifying the error (32 bytes or less)
• message: Description of error (messages may include linefeed characters and are
512 bytes or less)
For these values, the values of the members in the RFC_ERROR_INFO_EX structure are
set without change. This structure is acquired using the GetRfcLastErrorEx
function that returns an RFC API error. For RFC details, see the SAP BW
documentation.
S:
The system aborts command execution.
O:
Identify the cause of the error and correct the problem.
KAJM2803-E
A communication error occurred with the SAP BW system. (address:
destination-name, host: host-name, system No.: system-number)
An error occurred when JP1/AJS3 for EAP called the RFC API (communication
function provided by SAP).
Immediately after this message, a KAJM2802-E message appears indicating the name
of the function where the error occurred and providing detailed information about the
error.
The possible causes of the error are as follows:
• The SAP BW system is inactive.
• The SAP BW system is too busy to accept an RFC request.
• The network settings are incorrect.
S:
The system attempts to reconnect to the SAP BW system if a communication
error retry is specified. The system aborts command execution if no
communication error retry is specified.
O:
Consider specifying retry if no retry is specified (version 07-00 and earlier do not
retry by default).
KAJM2804-E
Cannot log on to the SAP BW system. (client: client, user: user-name,
language: language-name)
A logon error occurred when JP1/AJS3 for EAP attempted to establish an RFC
207
6. Messages
connection with the SAP BW system.
Immediately after this message, a KAJM2802-E message appears indicating the name
of the function where the error occurred and providing detailed information about the
error.
The possible causes of the error are as follows:
• The RFC connection information is incorrect (for example, a non-existent user or
an incorrect password is specified).
• The user is locked out.
• The user was not granted S_RFC permission correctly.
• An extended password containing lower-case characters is defined in the SAP
system based on SAP NetWeaver 7.0 and later, but connection information (the
-p option or Passwd key of the r3defcon file) that does not correspond to the
extended password is specified.
S:
The system aborts command execution.
O:
Check the SAP BW system logon information that was specified by the
command.
KAJM2805-I
Now recovering connection with the SAP BW system. (address:
destination-name, host: host-name, system No.: system-number, retry-time:
retry-time-in-minutes min., retry-count: number-of-retries times)
The connection with the SAP BW system is now being recovered.
retry-time in the message is output when the RetryTime key specified in the
command section of the environment setup file is valid. number-of-retries in the
message is output when the RetryCount key in the command section of the
environment setup file is valid.
S:
The system tries to reestablish connection with the SAP BW system. If
reconnection is performed within the retry-time or number-of-retries limit, JP1/
AJS3 for EAP continues command processing. Otherwise, the system aborts
command execution.
KAJM2806-I
Connection was recovered with the SAP BW system. (address:
destination-name, host: host-name, system No.: system-number)
Connection with the SAP BW system was recovered.
208
6. Messages
KAJM2807-E
Time-out occurred in the connection with the SAP BW system.
(address: destination-name, host: host-name, system No.: system-number)
The connection with the SAP BW system could not be restored within the
reconnection retry time.
S:
The system aborts command execution.
O:
Read the messages that are output before this message and the SAP BW system
log to determine the cause of the error. Check whether the value of the retry count
or the retry time (RetryCount key or RetryTime key in the command section
of the environment setup file) is appropriate.
KAJM2808-E
This InfoPackage does not exist. (InfoPackage: InfoPackage-ID)
The specified InfoPackage is not defined in the SAP BW system.
S:
The system aborts command execution.
O:
Check whether the InfoPackage specified in the command is valid for the SAP
BW system. If necessary, define the specified InfoPackage for the SAP BW
system, and then execute the command again.
KAJM2821-I
The InfoPackage was started. (InfoPackage: InfoPackage-ID, request:
request-number)
A request to start InfoPackage was successful and a request number was assigned in
the SAP BW system. The InfoPackage request is registered on the SAP BW system
side after this message is output.
JP1/AJS3 for EAP monitors completion of InfoPackage request registration and the
end of execution according to the request registration monitoring time (default:
completion monitoring time) and the completion monitoring time (default: unlimited)
if completion monitoring is specified.
To check whether request registration is completed, use the administrator workbench
of the SAP BW system.
KAJM2822-E
The InfoPackage cannot be started. (InfoPackage: InfoPackage-ID)
The specified InfoPackage could not be started.
209
6. Messages
S:
The system aborts command execution.
O:
Determine the cause by reading the messages displayed before this message as
well as the SAP BW system log. If job XXX is not started (yet) appears
in the detailed information of the KAJM0813-E message that appears before this
message, the SAP BW system may have a problem. Check whether SAP Note
693703 has been applied to the connection destination SAP BW system. If not,
apply it.
KAJM2823-I
Now monitoring InfoPackage-end. (monitoring time:
monitoring-time-in-minutes min.)
InfoPackage execution completion monitoring has been started.
S:
The system continues with InfoPackage execution completion monitoring.
KAJM2824-E
InfoPackage-end monitoring is canceled because a timeout
occurred. (InfoPackage: InfoPackage-ID, request: request-number)
InfoPackage completion monitoring is aborted because InfoPackage did not end
within the monitoring time.
S:
The system aborts command execution.
O:
Use the SAP front-end software to check the status of InfoPackage. Abort
execution of InfoPackage if necessary.
KAJM2825-E
Could not monitor InfoPackage-end. (InfoPackage: InfoPackage-ID,
request: request-number)
InfoPackage completion monitoring failed.
S:
The system aborts command execution.
O:
Determine the cause by reading the messages displayed before this message as
well as the SAP BW system log.
Use the SAP front-end software to check the status of InfoPackage. Abort the
210
6. Messages
execution of InfoPackage if necessary.
If request XXX could not be generated appears in the KAJM0813-E
message that appears before this message, a timeout error has occurred in
registration monitoring of the data load request. Check whether the registration
monitoring time value of the data load request (RequestMonitorTime key in
the command section of the environment setup file) is appropriate.
KAJM2826-I
The InfoPackage has finished. (InfoPackage: InfoPackage-ID,
request: request-number)
The InfoPackage has ended.
KAJM2827-E
Error occurred while executing the InfoPackage. (InfoPackage:
InfoPackage-ID, request:request-number)
Detail: detailed text
An error occurred during InfoPackage execution.
For detailed text, a message appears indicating the error factor returned from SAP BW.
The language used for the message depends on the language (-l option specification
value) specified during logon to the SAP BW system.
S:
The system aborts command execution.
O:
Check the Details line to identify the cause of the error, and check the status of the
InfoPackage with the SAP front-end software. Solve the problem and then
execute the command again.
If Processing exceeded the specified time appears in detailed text
immediately after InfoPackage is executed, the SAP BW system may have a
problem. Check whether SAP Notes 633981, 641466, 647855, and 655528
have been applied to the connection destination SAP BW system. If not, apply
them.
KAJM2828-E
InfoPackage-end monitoring is canceled because a reconnection
timeout occurred. (InfoPackage: InfoPackage-ID, request:
request-number)
InfoPackage completion monitoring is aborted because the connection with the SAP
BW system could not be restored within the reconnection retry time.
S:
The system aborts command execution.
211
6. Messages
O:
Read the messages that are output before this message and the SAP BW system
log to determine the cause of the error. Check whether the value of the retry count
or the retry time (RetryCount key or RetryTime key in the command section
of the environment setup file) is appropriate.
Use the SAP front-end software to check the status of InfoPackage. Abort the
execution of InfoPackage if necessary.
KAJM2829-I
Now waiting for the end of subsequent process of the InfoPackage.
(waiting time: waiting-time sec.)
JP1/AJS3 for EAP delays termination of the command for the specified number of
seconds (waiting time) set between the normal end of InfoPackage and the end of the
job that executes InfoPackage.
S:
The system delays termination of the command for the specified number of
seconds.
KAJM2841-I
The process chain was started. (process chain: process-chain-ID,
log: log-ID)
The process chain has been started.
KAJM2842-E
The process chain cannot be started. (process chain:
process-chain-ID)
The specified process chain does not exist or the definition is invalid.
S:
The system aborts command execution.
O:
Use the SAP front-end software to check the definition of the process chain.
Specify a correct process chain ID, and then re-execute the command. If the
correct process chain is specified, use the SAP front-end software to check the
definition of the process chain, correct any problems in the definition, and then
re-execute the command.
KAJM2843-I
Now monitoring process-chain-end. (monitoring time: monitoring-time
min.)
Completion monitoring for execution of the process chain started.
212
6. Messages
S:
The system continues startup of the process chain.
KAJM2844-E
Process-chain-end monitoring is canceled because a timeout
occurred. (process chain: process-chain-ID, log: log-ID)
Monitoring is aborted because the process chain did not end during the specified
monitoring time.
S:
The system aborts command execution.
O:
Use the SAP front-end software to check the status of the process chain. Abort
execution of the process chain if necessary.
KAJM2845-E
Could not monitor process-chain-end. (process chain:
process-chain-ID, log: log-ID)
Completion monitoring of the process chain failed.
S:
The system aborts command execution.
O:
Read the process chain log and the SAP BW system log to determine the cause of
the error.
Use the SAP front-end software to check the status of the process chain. Abort
execution of the process chain if necessary.
KAJM2846-I
The process chain has finished. (process chain: process-chain-ID,
log: log-ID)
The process chain has ended.
KAJM2847-E
Error occurred while executing the process chain. (process
chain: process-chain-ID, log: log-ID, status: status)
An error occurred during execution of the process chain. For status in the message,
Completed but errors occurred or Cancelled is set.
S:
The system aborts command execution.
213
6. Messages
O:
Use the SAP front-end software to determine the cause of the process error
indicated in the next message. Correct the error and then re-execute the command.
KAJM2848-E
message-class-message-number: message-text
JP1/AJS3 for EAP outputs the log (process chain log) that indicates the process
containing the error returned from SAP BW.
The language used for the log depends on the language (-l option specification value)
specified during logon to the SAP BW system.
S:
The system aborts command execution.
O:
Use the SAP front-end software to determine the cause of the process error
indicated in the message. Correct the error and then re-execute the command.
KAJM2849-E
Process-chain-end monitoring is canceled because a reconnection
timeout occurred. (process chain: process-chain-ID, log: log-ID)
Monitoring is aborted because reconnection was not performed during the specified
reconnection retry time.
S:
The system aborts command execution.
O:
Read the messages that are output before this message and the SAP BW system
log to determine the cause of the error. Check whether the value of the retry count
or the retry time (RetryCount key or RetryTime key in the command section
of the environment setup file) is appropriate.
Use the SAP front-end software to check the status of the process chain. Abort
execution of the process chain if necessary.
KAJM2850-W
Failed to acquire a process chain log. (process chain:
process-chain-ID, log: log-ID)
Acquisition of the process chain log failed.
S:
The system aborts command execution.
214
6. Messages
O:
Use the SAP front-end software to check the process where the error occurred.
Correct the error and then re-execute the command.
KAJM2852-E
message-class-message-number: message-to-be-inserted...
Conversion of the message text in the process chain log failed. The message shows the
data (message-class, message-number, message-to-be-inserted) before the
conversion.
S:
The system aborts command execution.
O:
Use the SAP front-end software (transaction SE91) to check the contents of the
AP BW system message indicated in this message. Correct the error and then
re-execute the command.
215
Chapter
7. syslog Messages (When UNIX Is
Used)
This chapter describes the syslog messages issued by UNIX compliant JP1/AJS3 for
EAP.
7.1 syslog message format
7.2 List of syslog messages
217
7. syslog Messages (When UNIX Is Used)
7.1 syslog message format
This section shows the format of syslog messages that are output to the syslog file.
„
Format of syslog messages of the job control function
date-and-time host-name JP1/AM/R3[process-ID]: message-ID message-text
„
Format of syslog messages of the InfoPackage control function
date-and-time host-name JP1/AM/R3/SAPBWOption[process-ID]: message-ID message-text
„
Format of syslog messages of the process chain control function
date-and-time host-name JP1/AM/R3/SAPBWOption[process-ID]: message-ID message-text
The maximum length of a message text is 512 bytes. Any text beyond 512 bytes is
discarded.
An example of syslog message output is given below.
Example
Oct 8 22:01:10 host1 JP1/AM/R3[377]: KAJM0006-E Required option is missing.
218
7. syslog Messages (When UNIX Is Used)
7.2 List of syslog messages
The following table describes the syslog messages that are issued by JP1/AJS3 for
EAP.
Table 7-1: List of syslog messages
Message ID
syslog message type
syslog message issuance level
KAJM0010-W
Invalid parameter warning
LOG_WARNING
KAJM0011-W
Invalid parameter warning
LOG_WARNING
KAJM0012-W
Invalid parameter warning
LOG_WARNING
KAJM0013-W
Invalid parameter warning
LOG_WARNING
KAJM0103-W
Invalid parameter warning
LOG_WARNING
KAJM0104-W
Invalid parameter warning
LOG_WARNING
KAJM0106-W
Invalid parameter warning
LOG_WARNING
KAJM0830-W
XMI interface session audit level change
failure
LOG_WARNING
KAJM1804-W
R/3 job log acquisition failure
LOG_WARNING
KAJM1811-I
Job creation
LOG_DEBUG
KAJM1812-E
Job creation failure
LOG_ERR
KAJM1819-W
Incomplete-job deletion failure
LOG_WARNING
KAJM1821-I
Job release
LOG_DEBUG
KAJM1825-E
Job release failure
LOG_ERR
KAJM1831-E
Job completion monitoring timeout
LOG_ERR
KAJM1832-I
Job completion monitoring success (when
a job has ended normally)
LOG_DEBUG
KAJM1833-W
Job completion monitoring success (when
a job has been terminated)
LOG_INFO
KAJM1834-E
Job completion monitoring failure
LOG_ERR
KAJM1835-E
Job completion monitoring failure
(reconnection timeout)
LOG_ERR
KAJM1836-W
Job interrupt detection
LOG_WARNING
219
7. syslog Messages (When UNIX Is Used)
Message ID
syslog message type
syslog message issuance level
KAJM1837-W
Detection of a job without confirmation of
completion (job deletion)
LOG_WARNING
KAJM1838-W
Unreleased-job detection
LOG_WARNING
KAJM1840-I
Job termination
LOG_DEBUG
KAJM1844-E
Job termination failure
LOG_ERR
KAJM1850-I
Job deletion
LOG_DEBUG
KAJM1851-E
Job deletion failure
LOG_ERR
KAJM1871-W
Detection of a job without confirmation of
completion (child job detection failure)
LOG_WARNING
KAJM1872-W
Detection of a job without confirmation of
completion (number of jobs to be
monitored exceeded the maximum limit)
LOG_WARNING
KAJM2821-I
InfoPackage startup
LOG_DEBUG
KAJM2822-E
InfoPackage startup failure
LOG_ERR
KAJM2824-E
InfoPackage completion monitoring
timeout
LOG_ERR
KAJM2825-E
InfoPackage completion monitoring
failure
LOG_ERR
KAJM2826-I
InfoPackage completion monitoring
success (when an InfoPackage has ended
normally)
LOG_DEBUG
KAJM2827-E
InfoPackage completion monitoring
success (when an InfoPackage has ended
abnormally)
LOG_ERR
KAJM2828-E
InfoPackage completion monitoring
failure (reconnection timeout)
LOG_ERR
KAJM2841-I
Process chain startup
LOG_DEBUG
KAJM2842-E
Process chain startup failure
LOG_ERR
KAJM2844-E
Process chain completion monitoring
timeout
LOG_ERR
KAJM2845-E
Process chain completion monitoring
failure
LOG_ERR
220
7. syslog Messages (When UNIX Is Used)
Message ID
syslog message type
syslog message issuance level
KAJM2846-I
Process chain completion monitoring
success (when a process chain ended
normally)
LOG_DEBUG
KAJM2847-E
Process chain completion monitoring
success (when a process chain ended
abnormally)
LOG_ERR
KAJM2849-E
Process chain completion monitoring
failure (reconnection timeout)
LOG_ERR
221
Chapter
8. Troubleshooting Guide for JP1/
AJS3 for EAP
This chapter describes the procedures for solving the problems that may occur in JP1/
AJS3 for EAP and explains the data (maintenance information) that needs to be
collected if a problem occurs. The chapter also describes the causes of the problems
that may occur while you are using JP1/AJS3 for EAP and the actions to be taken for
such problems.
8.1 Troubleshooting procedure
8.2 Data to be collected if a problem occurs
8.3 Actions to be taken for problems
223
8. Troubleshooting Guide for JP1/AJS3 for EAP
8.1 Troubleshooting procedure
Perform the following procedure if a problem occurs in JP1/AJS3 for EAP:
1.
Check the situation.
Note the circumstances when the problem occurred. If a message is output, check
the contents of the message. For the contents of messages (causes and actions to
be taken), see 6. Messages.
2.
Collect data.
Collect data (maintenance information) that can be used to determine the cause of
the problem. For details about the data to be collected, see 8.2 Data to be collected
if a problem occurs.
3.
Determine the cause of the problem.
Determine the cause of the problem based on the collected data. Isolate the part
with the problem or determine the scope of the problem.
4.
Take the necessary action.
Take appropriate action based on the cause.
224
8. Troubleshooting Guide for JP1/AJS3 for EAP
8.2 Data to be collected if a problem occurs
You can encounter errors from JP1/AJS3 for EAP, from the R/3 system, and from the
SAP BW system. If you can identify the cause of an error by referring to messages and
events relating to the error, you can correct the error.
If you cannot identify the cause from messages or events, collect the following data
(maintenance information) and contact the system administrator.
The data to be collected when a problem occurs is explained below for each function.
The data to be collected varies depending on whether Windows or UNIX is used.
8.2.1 Data to be collected about the job control function
If a problem occurs while you are using the job control function, collect the data
described below.
(1) When Windows is used
Collect the following data as maintenance information.
(a) OS log information
Table 8-1: OS log information (for Windows)
Type of information
to be collected
Procedure
Windows event log
Obtain the application log and the system log collected by Windows for the period of
time during which the problem occurred (contents of System Log and Application
Log in the Event Viewer window of Windows).
System information
Collect the system information managed by Windows (choose Accessories and then
System Tools, and collect the contents of System Information).
225
8. Troubleshooting Guide for JP1/AJS3 for EAP
Type of information
to be collected
Dump information
(Watson log file)
Procedure
If an application error occurs during execution of a custom job for the R/3 system or a
command provided by JP1/AJS3 for EAP:
Collect the following log file (*.log) and dump file (*.dump):
For Windows Server 2003
User specified folder#\drwtsn32.log
User specified folder#\user.dump
For Windows Server 2008
Dr. Watson has been changed to Problem report and solutions.
Collect the following problem report and user dump.
(1) Problem report
If the JP1/AJS3 for EAP process stops due to an application error, use the following
procedure to collect the problem report.
1. In the Specify a file name and execute text box, enter wercon and click the OK
button.
The Problem report and solutions dialog box opens.
2. On the left side area, click View Problem History.
The problem history is displayed in list form.
3. Double-click the relevant problem.
Details of the problem report appear.
4. Select Copy to clipboard.
5. Copy and save the copied content to a text file.
6. The saved problem report is collected as data for problem investigation.
(2) User dump
If the JP1/AJS3 for EAP process stops due to an application error and an error
dialog box appears, use the following procedure to collect the problem report.
Note
Collect the problem report while the error dialog box is displayed.
1. Start Task Manager.
2. From the Task Manager dialog box, click Process.
3. Right-click the JP1/AJS3 for EAP process name that stopped due to an
application error, and then select Create dump file.
4. When a dialog box appears asking you to specify the path to the user dump
output destination, collect data from there.
#
By default, system-drive\Documents and Settings\All
Users\Application Data\Microsoft\Dr Watson.
226
8. Troubleshooting Guide for JP1/AJS3 for EAP
(b) Information to be collected from JP1/AJS3 for EAP (job control)
Table 8-2: Information to be collected from JP1/AJS3 for EAP (job control) (for
Windows)
Type of information
to be collected
Procedure
Trace information
Collect the following files:
When a file name is specified for the TargetFile key in the trace section in the conf
file:
File specified by the TargetFile key
If no file name is specified for the TargetFile key in the trace section in the conf file:
Files in installation-folder\bwsta\log
In addition to the above files, collect all the files in the following folders regardless of
the conf file setting:
Files in installation-folder\log
Files in Windows-folder\Temp\jp1common\jp1amr3
Standard error output
information
If a command provided by JP1/AJS3 for EAP ends abnormally:
Obtain the error message text that is output to the standard error output.
Standard error output
When a command is executed from the command line:
File specified in the window where the command is executed or file specified by
the -se option
When a command is executed by JP1/AJS:
File defined as the standard error output by JP1/AJS, file defined as the standard
error output by a JP1/AJS custom job, or file specified in the -se option of the
command
Model, version, and
patch information
Collect the following version and patchlog.txt files:
installation-folder\system\version
installation-folder\system\patchlog.txt
Environment setup file
Collect the following conf file:
installation-folder\conf\conf
RFC trace file
If an error occurs during the execution of a custom job for the R/3 system or a command
of JP1/AJS3 for EAP:
Collect the file named dev_rfc.trc containing the trace information about the
communication with the R/3 system. This file is created in the work directory of JP1/
AJS3 for EAP.
RFC library status
management file
Collect the following jr3chrfc file:
installation-folder\system\jr3chrfc
227
8. Troubleshooting Guide for JP1/AJS3 for EAP
Type of information
to be collected
Product information
file
Procedure
Collect the following files:
For an x86 OS:
system-drive\Program Files\Hitachi\jp1common\jp1amr3\jp1amr3.dat
For an x64 OS:
system-drive\Program Files
(x86)\Hitachi\jp1common\jp1amr3\jp1amr3.dat
(c) Information to be collected from the R/3 system
Table 8-3: Information to be collected from the R/3 system (for Windows)
Type of information
to be collected
Procedure
System log
Run transaction SM21 via the SAP front-end software to collect the data matching the
following criteria:
• User: Not specified
• Transaction code: Not specified
• SAP process: Not specified
• Error class: All messages
• Starting and ending dates and times: Period during which the target error occurred
For details about the system log, see the R/3 documentation and the online help.
XMI log
Run transaction RZ15 via the SAP front-end software and collect the data matching the
following criteria:
• Interface: *
• Object: *
• Session ID: *
• External user: *
• Period: Period during which the target error occurred
Legend: *: Asterisk
For details about the XMI log, see the R/3 documentation and the online help.
Release and patch
information
Developer trace
228
• Start the SAP front-end software and choose System -> Status from the menu.
Obtain a hard copy of the displayed window.
• Obtain hard copies of the following windows that can be opened from the above
window:
System: Status window
System: Component Information window
System: Kernel Information window
If an error occurs during the execution of a custom job for the R/3 system or a command
provided by JP1/AJS3 for EAP:
Obtain the developer trace in the R/3 system (dev_w*, dec_rfc*, and dev_rd files
that are collected by running transaction ST11 via the SAP front-end software).
8. Troubleshooting Guide for JP1/AJS3 for EAP
(d) Operational details
Check the following information about the operation that was being performed when
the problem occurred:
• Detailed contents of the operation
• Time when the problem occurred
• Job in which the problem occurred (jobnet name and job name in JP1/AJS)
• Machine configuration (version of each OS, host name, and the configuration of
JP1/AJS and the R/3 system)
• Whether the problem is reproducible, how often the problem occurs
(2) When UNIX is used
Collect the following data as maintenance information.
(a) OS log information
Table 8-4: OS log information (for UNIX-based OSs)
Type of information
to be collected
Procedure
syslog file
Obtain the syslog files whose facility includes user in the /etc/syslog.conf file.
You only need the part of the system log that covers the period of time during which
the problem occurred.
Version information
Collect the execution result of the uname -a command.
Information about
installed Hitachi
products
Collect the /etc/.hitachi/pplistd/pplistd file.
229
8. Troubleshooting Guide for JP1/AJS3 for EAP
(b) Information to be collected from JP1/AJS3 for EAP (job control)
Table 8-5: Information to be collected from JP1/AJS3 for EAP (job control) (for
UNIX-based OSs)
Type of information
to be collected
Trace information
Procedure
Collect the following files:
When a directory name is specified for the TargetDir key in the trace section in the
conf file:
Files in the directory specified by the TargetDir key
When a file name is specified for the TargetFile key in the trace section in the conf
file:
File specified by the TargetFile key
When no directory name is specified for the TargetDir key and no file name is
specified for the TargetFile key in the trace section in the conf file:
Files in /var/opt/jp1_am_r3/log
In addition to the above files, collect the following file:
/var/opt/jp1_am_r3/log/jr3chrfc.log
Standard error output
information
If a command provided by JP1/AJS3 for EAP ends abnormally:
Collect the error message text that is output to the standard error output.
Model, version, and
patch information
Collect the following .version and .patch_hist files:
Environment setup file
Collect the following conf file:
/etc/opt/jp1_am_r3/conf/conf
RFC trace file
If an error occurs during the execution of a custom job for the R/3 system or a command
of JP1/AJS3 for EAP:
Collect the file named dev_rfc containing the trace information about the
communication with the R/3 system. This file is created in the work directory of JP1/
AJS3 for EAP.
RFC library status
management file
Collect the following .jr3chrfc file:
230
/etc/opt/jp1_am_r3/.version
/etc/opt/jp1_am_r3/.patch_hist
/etc/opt/jp1_am_r3/.jr3chrfc
8. Troubleshooting Guide for JP1/AJS3 for EAP
(c) Information to be collected from the R/3 system
Table 8-6: Information to be collected from the R/3 system (for UNIX-based
OSs)
Type of information
to be collected
Procedure
System log
Run transaction SM21 via the SAP front-end software and collect the data matching
the following criteria:
• User: Not specified
• Transaction code: Not specified
• SAP process: Not specified
• Error class: All messages
• Starting and ending dates and times: Period during which the target error occurred
For details about the system log, see the R/3 documentation and the online help.
XMI log
Run transaction RZ15 via the SAP front-end software and collect the data matching the
following criteria:
• Interface: *
• Object: *
• Session ID: *
• External user: *
• Period: Period during which the target error occurred
Legend: *: Asterisk
For details about the XMI log, see the R/3 documentation and the online help.
Release and patch
information
Developer trace
• Start the SAP front-end software and choose System and then Status from the
menu. Obtain a hard copy of the displayed window.
• Obtain hard copies of the following windows that can be opened from the above
window:
System: Status window
System: Component Information window
System: Kernel Information window
If an error occurs during the execution of a custom job for the R/3 system or a command
provided by JP1/AJS3 for EAP:
Obtain the developer trace in the R/3 system (dev_w*, dec_rfc*, and dev_rd files
that are collected by running transaction ST11 via the SAP front-end software).
(d) Operational details
Check the following information about the operation that was being performed when
the problem occurred:
• Detailed description of the operation
• Time when the problem occurred
• Job in which the problem occurred (jobnet name and job name in JP1/AJS)
• Machine configuration (version of each OS, host name, and the configuration of
231
8. Troubleshooting Guide for JP1/AJS3 for EAP
JP1/AJS and the R/3 system)
• Whether the problem is reproducible, how often the problem occurs
8.2.2 Data to be collected about the InfoPackage control function or
the process chain control function
If a problem occurs while you are using the InfoPackage control function or the
process chain control function, collect the data described below.
(1) When Windows is used
Collect the following data as maintenance information.
(a) OS log information
Table 8-7: OS log information (for Windows)
Type of information
to be collected
Procedure
Windows event log
Obtain the application log and the system log collected by Windows for the period of
time during which the problem occurred (contents of System Log and Application
Log in the Event Viewer window of Windows).
System information
Collect the system information managed by Windows (choose Accessories and then
System Tools, and collect the contents of System Information).
232
8. Troubleshooting Guide for JP1/AJS3 for EAP
Type of information
to be collected
Dump information
(Watson log file)
Procedure
If an application error occurs during execution of a custom job for the SAP BW system
or a command provided by JP1/AJS3 for EAP:
Collect the following log file (*.log) and dump file (*.dump):
For Windows Server 2003
User specified folder#\drwtsn32.log
User specified folder#\user.dump
For Windows Server 2008
Dr. Watson has been changed to Problem report and solutions.
Collect the following problem report and user dump.
(1) Problem report
If the JP1/AJS3 for EAP process stops due to an application error, use the following
procedure to collect the problem report.
1. In the Specify a file name and execute text box, enter wercon and click the OK
button.
The Problem report and solutions dialog box opens.
2. On the left side area, click View Problem History.
The problem history is displayed in list form.
3. Double-click the relevant problem.
Details of the problem report appear.
4. Select Copy to clipboard.
5. Copy and save the copied content to a text file.
6. The saved problem report is collected as data for problem investigation.
(2) User dump
If the JP1/AJS3 for EAP process stops due to an application error and an error
dialog box appears, use the following procedure to collect the problem report.
Note
Collect the problem report while the error dialog box is displayed.
1. Start Task Manager.
2. From the Task Manager dialog box, click Process.
3. Right-click the JP1/AJS3 for EAP process name that stopped due to an
application error, and then select Create dump file.
4. When a dialog box appears asking you to specify the path to the user dump
output destination, collect data from there.
#
By default, system-drive\Documents and Settings\All
Users\Application Data\Microsoft\Dr Watson.
233
8. Troubleshooting Guide for JP1/AJS3 for EAP
(b) Information to be collected from JP1/AJS3 for EAP (InfoPackage control
or process chain control)
Table 8-8: Information to be collected from JP1/AJS3 for EAP (InfoPackage
control or process chain control) (for Windows)
Type of information
to be collected
Procedure
Trace information
Collect the following files:
When a file name is specified for the TargetFile key in the trace section in the conf
file:
File specified by the TargetFile key
If no file name is specified for the TargetFile key in the trace section in the conf file:
Files in installation-folder\bwsta\log
In addition to the above files, collect all the files in the following folders regardless of
the conf file setting:
Files in installation-folder\log
Files in Windows-folder\Temp\jp1common\jp1amr3
Standard error output
information
If a command provided by JP1/AJS3 for EAP ends abnormally:
Obtain the error message text that is output to the standard error output.
Standard error output
When a command is executed from the command line:
File specified in the window where the command is executed or file specified by
the -se option
When a command is executed by JP1/AJS:
File defined as the standard error output by JP1/AJS, file defined as the standard
error output by a JP1/AJS custom job, or file specified in the -se option of the
command
Model, version, and
patch information
Collect the following version and patchlog.txt files:
installation-folder\system\version
installation-folder\system\patchlog.txt
Environment setup file
Collect the following conf file:
installation-folder\bwsta\conf\conf
RFC trace file
If an error occurs during the execution of a custom job for the SAP BW system or a
command of JP1/AJS3 for EAP:
Collect the file named dev_rfc.trc containing the trace information about the
communication with the SAP BW system. This file is created in the work directory of
JP1/AJS3 for EAP.
RFC library status
management file
Collect the following jr3chrfc file:
installation-folder\system\jr3chrfc
234
8. Troubleshooting Guide for JP1/AJS3 for EAP
Type of information
to be collected
Product information
file
Procedure
Collect the following files:
For an x86 OS:
system-drive\Program Files\Hitachi\jp1common\jp1amr3\jp1amr3.dat
For an x64 OS:
system-drive\Program Files
(x86)\Hitachi\jp1common\jp1amr3\jp1amr3.dat
(c) Information to be collected from the SAP BW system
Table 8-9: Information to be collected from the SAP BW system (for Windows)
Type of information
to be collected
System log
Release and patch
information
Procedure
Run transaction SM21 via the SAP front-end software to collect the data matching the
following criteria:
• User: Not specified
• Transaction code: Not specified
• SAP process: Not specified
• Error class: All messages
• Starting and ending dates and times: Period during which the target error occurred
For details about the system log, see the SAP BW documentation and the online help.
• Start the SAP front-end software and choose System and then Status from the
menu. Obtain a hard copy of the displayed window.
• Obtain hard copies of the following windows that can opened from the above
window:
System: Status window
System: Component Information window
System: Kernel Information window
Execution result of
InfoPackage (for
InfoPackage control)
If an error occurs during the execution of a custom job for the SAP BW system or
InfoPackage using the jbwipsta command:
Run transaction RSA1 via the SAP front-end software and display the monitor window.
Obtain the execution result of the InfoPackage with the problem (header, status,
contents of the Details page) from the window.
Execution result of a
process chain (for
process chain control)
If an error occurs during the execution of a custom job for the SAP BW system or a
process chain using the jbwipsta command:
Run transaction RSPC via the SAP front-end software and display the log view. Obtain
the execution result of the process chain and the execution logs of the process with the
problem (process log (contents of the Process page) and the job log of the process
(contents of the Backg page)).
Developer trace
If an error occurs during the execution of a custom job for the SAP BW system or a
command provided by JP1/AJS3 for EAP:
Obtain the developer trace in the SAP BW system (dev_w*, dec_rfc*, and dev_rd
files that are collected by running transaction ST11 via the SAP front-end software).
235
8. Troubleshooting Guide for JP1/AJS3 for EAP
(d) Operational details
Check the following information about the operation that was being performed when
the problem occurred:
• Detailed contents of the operation
• Time when the problem occurred
• Job in which the problem occurred (jobnet name and job name in JP1/AJS,
InfoPackage ID, process chain ID)
• Machine configuration (version of each OS, host name, and the configuration of
JP1/AJS and the SAP BW system)
• Whether the problem is reproducible, how often the problem occurs
(2) When UNIX is used
Collect the following data as maintenance information.
(a) OS log information
Table 8-10: OS log information (for UNIX-based OSs)
Type of information
to be collected
Procedure
syslog file
Obtain the syslog files whose facility includes user in the /etc/syslog.conf file.
You only need the part of the system log that covers the period of time during which
the problem occurred.
Version information
Obtain the execution result of the uname -a command.
Information about the
installed Hitachi
products
Collect the /etc/.hitachi/pplistd/pplistd file.
236
8. Troubleshooting Guide for JP1/AJS3 for EAP
(b) Information to be collected from JP1/AJS3 for EAP (InfoPackage control
or process chain control)
Table 8-11: Information to be collected from JP1/AJS3 for EAP (InfoPackage
control or process chain control) (for UNIX-based OSs)
Type of information
to be collected
Trace information
Procedure
Collect the following files:
When a file name is specified for the TargetFile key in the trace section in the conf
file:
File specified by the TargetFile key
When no file name is specified for the TargetFile key in the trace section in the conf
file:
Files in /var/opt/jp1_am_r3/bwsta/log
In addition to the above files, collect the following file:
/var/opt/jp1_am_r3/log/jr3chrfc.log
Standard error output
information
If a command provided by JP1/AJS3 for EAP ends abnormally:
Obtain the error message text that is output to the standard error output.
Model, version, and
patch information
Collect the following .version and .patch_hist files:
/etc/opt/jp1_am_r3/.version
/etc/opt/jp1_am_r3/.patch_hist
Environment setup file
Collect the following conf file:
/etc/opt/jp1_am_r3/bwsta/conf/conf
RFC trace file
If an error occurs during the execution of a custom job for the SAP BW system or a
command of JP1/AJS3 for EAP:
Collect the file named dev_rfc containing the trace information about the
communication with the SAP BW system. This file is created in the work directory of
JP1/AJS3 for EAP.
RFC library status
management file
Collect the following .jr3chrfc file:
/etc/opt/jp1_am_r3/.jr3chrfc
237
8. Troubleshooting Guide for JP1/AJS3 for EAP
(c) Information to be collected from the SAP BW system
Table 8-12: Information to be collected from the SAP BW system (for
UNIX-based OSs)
Type of information
to be collected
System log
Procedure
Run transaction SM21 via the SAP front-end software to collect the data matching the
following criteria:
• User: Not specified
• Transaction code: Not specified
• SAP process: Not specified
• Error class: All messages
• Starting and ending dates and times: Period during which the target error occurred
For details about the system log, see the SAP BW documentation and the online help.
Release and patch
information
• Start the SAP front-end software and choose System and then Status from the
menu. Obtain a hard copy of the displayed window.
• Obtain hard copies of the following windows that can be opened from the above
window:
System: Status window
System: Component Information window
System: Kernel Information window
Execution result of
InfoPackage (for
InfoPackage control)
If an error occurs during the execution of a custom job for the SAP BW system or
InfoPackage using the jbwipsta command:
Run transaction RSA1 via the SAP front-end software and display the monitor window.
Obtain the execution result of the InfoPackage with the problem (header, status,
contents of the Details page) from the window.
Execution result of a
process chain (for
process chain control)
If an error occurs during the execution of a custom job for the SAP BW system or a
process chain using the jbwipsta command:
Run transaction RSPC via the SAP front-end software and display the log view. Obtain
the execution result of the process chain and the execution logs of the process with the
problem (process log (contents of the Process page) and the job log of the process
(contents of the Backg page)).
Developer trace
If an error occurs during the execution of a custom job for the SAP BW system or a
command provided by JP1/AJS3 for EAP:
Obtain the developer trace in the SAP BW system (dev_w*, dec_rfc*, and dev_rd
files that are collected by running transaction ST11 via the SAP front-end software).
(d) Operational details
Check the following information about the operation that was being performed when
the problem occurred:
• Detailed description of the operation
• Time when the problem occurred
238
8. Troubleshooting Guide for JP1/AJS3 for EAP
• Job in which the problem occurred (jobnet name and job name in JP1/AJS,
InfoPackage ID, process chain ID)
• Machine configuration (version of each OS, host name, and the configuration of
JP1/AJS and the SAP BW system)
• Whether the problem is reproducible, how often the problem occurs
239
8. Troubleshooting Guide for JP1/AJS3 for EAP
8.3 Actions to be taken for problems
This section explains the cause of trouble that may occur while JP1/AJS3 for EAP is
being used and the troubleshooting procedures to be performed in such a case.
8.3.1 Trouble related to the job control function
This section explains trouble that may occur while the job control function is being
used.
(1) Trouble with connection to the R/3 system
This section deals with the troubles that may occur with the connection to the R/3
system.
If you cannot find the cause of a problem here, the problem may be caused by the RFC
API provided by SAP. When detailed information about the RFC API error is output
in a KAJM0802-E message, keep this information and contact the R/3 system
administrator.
(a) The R/3 system cannot be connected or an error occurs during
communication with the R/3 system.
The probable causes are described below.
„
The R/3 system definition information is incorrect.
First, check whether the specified R/3 system IP address (or host name or SAP
router address) is valid. If the specified IP address is invalid, specify a valid IP
address and reconnect the R/3 system.
If the specified IP address is valid, there may be a problem with the setup. Check
whether correct setup data was entered.
„
The communication port is defined incorrectly.
Check whether a port number corresponding to the system ID is defined in the
services file. If no port number corresponding to the system ID is defined in
the services file, define a port number that corresponds to the system ID.
„
A temporary communication error has occurred.
A temporary communication error may have occurred because the network load
was increased or no more communication ports were available. You can resolve a
temporary communication error and restore the connection with the R/3 system
by retrying.
If retries are not specified for communication errors, use the RetryCount key or
the RetryTime key in the command section of the environment setup file to
execute retries.
240
8. Troubleshooting Guide for JP1/AJS3 for EAP
(b) The logon to the R/3 system fails.
The probable causes are described below.
„
The user information for logging on to the R/3 system is incorrect.
Check whether the user information (client number, user name, and password)
entered in the logon process is valid for the R/3 system. If the user information
entry for logon is invalid, log on again to the R/3 system using user information
valid for the R/3 system.
„
The specified user is not authorized to log on from an external system.
Use either of the following procedures to acquire authorization (S_RFC) to log on
from an external system.
• Log on again with the name of a user who is authorized to log on from an
external system.
• Ask the R/3 system administrator to grant authority to log on from an
external system.
„
The release of the R/3 system you attempted to log on to is not valid.
Check whether the release of the R/3 system you tried to log on to is a supported
version.
(2) Trouble with R/3 job control
The following problems may occur while you are controlling R/3 jobs.
If you cannot find the cause of your problem here, the problem may be caused by the
external management interface provided by SAP. If a KAJM0812-E message appears,
a problem with the external management interface is likely. Obtain the name of the
function of the external management interface with the problem and the exception
code from the message, and contact the R/3 system administrator.
(a) A job cannot be created in the R/3 system.
The probable causes are described below.
„
The job step definition information is incorrect.
• When an ABAP program is specified as the job step
Check whether the ABAP program exists in the R/3 system. Also, check
whether the specified program name, authorized user name, and language
type are valid for the R/3 system.
If the ABAP program is not found in the R/3 system and the definition is
invalid, define an ABAP program that can be used in the R/3 system as the
job step.
241
8. Troubleshooting Guide for JP1/AJS3 for EAP
• When an external program is specified as the job step
Check whether the external program exists on the host. Also, check whether
the program name, authorized user name, and execution target host
specifications are correct. If the external program is not found on the host or
the definition information is invalid, define a valid external program as the
job step.
„
The job execution destination host is specified incorrectly.
Check whether the job execution destination host name specified in the -tgh
option is the same as the host name displayed by transaction SM51 (upper-case
and lower-case characters are differentiated). In addition, check whether an
application server for providing background processing services is active on the
specified host.
„
The job execution destination server is specified incorrectly.
Check whether the job execution destination server name or the job server group
name specified in the -tgs option is correct.
When you specify a server name in the option, check whether the specified server
name is the same as the server name displayed by transaction SM51 (upper-case
and lower-case characters are differentiated). In addition, check whether
background processing services are active on the specified server.
When you specify a job server group name in the option, check whether the
specified job server group name is the same as the job server group name
displayed by transaction SM61 (upper-case and lower-case characters are
differentiated). In addition, check whether the specified job server group contains
an application server for providing background processing services.
„
The variant definition contains an error.
Specify a correct variant name and re-execute the command.
If this message appears even though a correct variant name is specified, a variant
whose name is blank may be registered for the specified program. Open the
variant list of the R/3 system and check whether there is a variant whose name is
blank. If such a variant is registered, take either of the following actions:
• From the VARI table of the R/3 system, delete the variant whose name is
blank. If such a variant is not registered, check the variant name and
re-execute the command.
• Change the setting (change the value set for the CheckLevel key in the
command section in the environment setup file to 0) so that the validity of
the ABAP program and the values specified for variants is not checked. Then
re-execute the command.
242
8. Troubleshooting Guide for JP1/AJS3 for EAP
„
The required variant is not specified in the program.
Check whether the specified program runs correctly without specifying variants.
If the program requires variants, specify necessary variants and re-execute the
command.
If the program does not require variants, change the setting (change the value set
for the CheckLevel key in the command section in the environment setup file to
0) so that the validity of the ABAP program and the values specified for variants
is not checked. Then re-execute the command.
„
No variant is defined in the program.
Check whether the specified program runs correctly without specifying variants.
If the program requires variants, define necessary variants in the program, specify
the variants, and re-execute the command.
If the program does not require variants, change the setting (change the value set
for the CheckLevel key in the command section in the environment setup file to
0) so that the validity of the ABAP program and the values specified for variants
is not checked. Then re-execute the command.
„
The user who has logged on is not authorized to create a job.
Use either of the following procedures to acquire authority to create a job.
• Log on again with the name of a user who is authorized to create a job.
• Ask the R/3 system administrator to grant authority to create a job.
„
The name of the authorized user is in lower case.
Check whether the authorized user name specified in the -auth option is lower
case, or, if the -auth option is omitted, check whether the user name specified as
the authorized user in the logon information is lower case.
authorized-user is case-sensitive.
„
The number of characters of the OS user name is 16 bytes or more.
If the name of the OS user who executes the command is 16 bytes or more, an
error occurs with the external management interface at the SAP side. Use an OS
user name of up to 15 bytes to execute the command.
(b) The R/3 system job cannot be released.
The probable causes are described below.
„
The specified job has already been released.
An already released job cannot be released again from JP1/AJS3 for EAP.
243
8. Troubleshooting Guide for JP1/AJS3 for EAP
„
The job execution destination host is specified incorrectly.
Check whether the job execution destination host name specified in the -tgh
option is the same as the host name displayed by transaction SM51 (upper-case
and lower-case characters are differentiated). In addition, check whether an
application server for providing background processing services is active on the
specified host.
„
The job execution destination server is specified incorrectly.
Check whether the job execution destination server name or the job server group
name specified in the -tgs option is correct.
When you specify a server name in the option, check whether the specified server
name is the same as the server name displayed by transaction SM51 (upper-case
and lower-case characters are differentiated). In addition, check whether
background processing services are active on the specified server.
When you specify a job server group name in the option, check whether the
specified job server group name is the same as the job server group name
displayed by transaction SM61 (upper-case and lower-case characters are
differentiated). In addition, check whether the specified job server group contains
an application server for providing background processing services.
„
The user who has logged on is not authorized to release a job.
Use either of the following procedures to acquire authority to release a job.
• Log on again with the name of a user who is authorized to release a job.
• Ask the R/3 system administrator to grant authority to release a job.
„
The designated job is not created by the user who has logged on.
You are not authorized to release jobs that were created by the other users. If
necessary, ask the R/3 system administrator to grant authority to release jobs
created by the other users.
„
R/3 system resources are insufficient.
Release the job after R/3 system resources have been allocated.
(c) The R/3 system job cannot be canceled.
The probable causes are described below.
„
The specified job is not being executed (it is not active).
Inactive jobs (scheduled, released, ready, finished, or terminated jobs) cannot be
canceled.
„
The user who has logged on is not authorized to cancel a job.
Use either of the following procedures to acquire authority to cancel a job.
244
8. Troubleshooting Guide for JP1/AJS3 for EAP
• Log on again with the name of a user who is authorized to cancel a job.
• Ask the R/3 system administrator to grant authority to cancel a job.
„
The specified job was not created by the user who has logged on.
Jobs cannot be canceled if they were created by other users. If necessary, ask the
R/3 system administrator to grant authority to cancel jobs created by other users.
„
The job steps include an external program.
You cannot cancel the job while the external program is running. Cancel the job
after the external program ends.
(d) A job on the R/3 system cannot be deleted.
The probable causes are described below.
„
The specified job is active or ready.
You cannot delete an active or ready job. You can delete scheduled, released,
finished, and terminated jobs. If you want to delete an active or ready job, wait
until the job execution ends or use the jr3bjcan command to cancel the job, and
then delete the job.
„
The user who has logged on is not authorized to delete the job.
Use one of the following method to obtain job deletion permission.
• Log on under the name of a user who is authorized to delete the job.
• Ask the R/3 system administrator to grant you job deletion permission.
„
The specified job was not scheduled by the user who has logged on.
You cannot delete jobs that have been scheduled by another user. If necessary, ask
the R/3 system administrator to grant you permission to delete jobs scheduled by
other users.
(e) The R/3 system job information (job status and job log) cannot be
displayed.
The probable causes are described below.
„
The user who has logged on is not authorized to view the job information (job
status and job log).
Use either of the following procedures to acquire authority to view the job
information (job status and job log).
• Log on again with the name of a user who is authorized to view the job
information (job status and job log).
• Ask the R/3 system administrator to grant authority to view the job
information (job status and job log).
245
8. Troubleshooting Guide for JP1/AJS3 for EAP
„
The specified job was not created by the user who has logged on.
The information (job status and job log) about jobs cannot be viewed if they were
created by other users. If necessary, ask the R/3 system administrator to grant
authority to view the information (job status and job log) about jobs created by
other users.
(f) The R/3 system resource information cannot be acquired.
The probable causes are described below.
„
The specified ABAP program is not found in the R/3 system.
Specify an ABAP program that exists in the R/3 system.
„
The specified ABAP program does not have any variant.
There is no variant in the specified ABAP program.
„
No variant is defined in the specified ABAP program.
Although the specified ABAP program requires variants, no variant is defined.
Define necessary variants in the ABAP program.
„
The user who has logged on is not authorized to view the R/3 system resource
information.
Use either of the following procedures to acquire authority to view the R/3 system
resource information.
• Log on again with the name of a user who is authorized to view the R/3
system resource information.
• Ask the R/3 system administrator to grant authority to view the R/3 system
resource information.
(g) A file named dev_rfc.trc or dev_rfc was created in the JP1/AJS3 for EAP
work directory.
If an error occurs during R/3 system custom job execution or JP1/AJS3 for EAP
command execution, the RFC trace file (file named dev_rfc.trc or dev_rfc) is
created in the JP1/AJS3 for EAP work directory. The RFC trace file records the trace
information (error information) about the communications with the R/3 system.
The RFC trace file is needed only when a serious error occurs. We recommend that you
periodically delete the RFC trace file when no serious error has been encountered.
8.3.2 Trouble related to the InfoPackage control function or the
process chain control function
This subsection explains problems that may occur while you are using the InfoPackage
control function or the process chain control function.
246
8. Troubleshooting Guide for JP1/AJS3 for EAP
(1) Trouble with connection to the SAP BW system
This section deals with the trouble that may occur with the connection to the SAP BW
system.
If you cannot find the cause of a problem here, the problem may be caused by the RFC
API provided by SAP. If detailed information about the RFC API error is output in a
KAJM2802-E message, collect the information and contact the SAP BW system
administrator.
(a) The SAP BW system cannot be connected or an error occurs during the
communication with the SAP BW system.
The probable causes are described below.
„
The SAP BW system definition information is incorrect.
First, check whether the specified SAP BW system IP address (or host name or
SAP router address) is valid. If the specified IP address is invalid, specify a valid
IP address and reconnect the SAP BW system.
If the specified IP address is valid, there may be a problem with the setup. Check
whether correct setup data was entered.
„
The communication port is defined incorrectly.
Check whether a port number corresponding to the system ID is defined in the
services file. If no port number corresponding to the system ID is defined in
the services file, define a port number that corresponds to the system ID.
„
A temporary communication error has occurred.
A temporary communication error may have occurred because the network load
was increased or no more communication ports were available. You can resolve a
temporary communication error and restore the connection with the SAP BW
system by retrying.
If retries are not specified for communication errors, use the RetryCount key or
the RetryTime key in the command section of the environment setup file to
execute retries.
(b) Logon to the SAP BW system fails.
The probable causes are described below.
„
The user information for logging on to the SAP BW system is incorrect.
Check whether the user information (client number, user name, and password)
entered in the logon process is valid for the SAP BW system. If the user
information entry for logon is invalid, log on again to the SAP BW system using
user information valid for the SAP BW system.
247
8. Troubleshooting Guide for JP1/AJS3 for EAP
„
The specified user is not authorized to log on from an external system.
Use either of the following procedures to acquire authorization to log on from an
external system.
• Log on again with the name of a user who is authorized to log on from an
external system.
• Ask the SAP BW system administrator to grant authority to log on from an
external system.
„
The release of the SAP BW system you attempted to log on to is not valid.
Check whether the release of the SAP BW system you tried to log on to is a
supported version.
(2) Trouble with InfoPackage control
This subsection describes the problems that may occur while you are controlling
InfoPackage.
If you cannot find the cause of a problem here, the problem may be caused by the
external management interface provided by SAP. If a KAJM0812-E message appears,
a problem with the external management interface is likely. Obtain the name of the
function of the external management interface with the problem and the exception
code from the message, and contact the SAP BW system administrator.
(a) InfoPackage cannot be started in the SAP BW system.
The probable causes are described below.
„
InfoPackage has not been scheduled to be executable by background processing.
Check whether the InfoPackage definition in the SAP BW system (Schedule
page) allows InfoPackage to be executed by background processing. To start
InfoPackage in the background, set immediate execution as the startup condition.
„
The destination to which InfoPackage external data is to be read is not an
application server.
When you execute InfoPackage in the background, you need to set an application
server to read the data. Check whether the InfoPackage definition in the SAP BW
system (External Data page) defines an application server as the destination to
which InfoPackage external data is to be read.
„
The InfoPackage definition is being updated.
Use the SAP front-end software to check whether the definition of InfoPackage
you wish to start is not being updated.
„
The user who has logged on is not authorized to execute InfoPackage.
When you create a user that executes InfoPackage, create the user based on the
248
8. Troubleshooting Guide for JP1/AJS3 for EAP
permission profile (S_BI-WHM_RFC) for background users that is prepared by the
SAP BW system.
Use either of the following procedures to obtain permission to execute
InfoPackage:
• Log on again with a user name that is allowed to execute InfoPackage.
• Ask the SAP BW system administrator to grant permission to execute
InfoPackage.
„
SAP BW system resources are insufficient.
To execute InfoPackage, you need one background work process (BGD) and one
dialog work process (DIA). Make sure that a work process for executing
InfoPackage in the SAP BW system is allocated and then restart InfoPackage.
„
The SAP BW system has a known problem.
If Job XXX is not started (yet) appears as the detailed information in a
KAJM0813-E message that appears before KAJM2822-E message, there may be
a problem with the SAP BW system. Check whether SAP Note 693703 has been
applied to the connection destination SAP BW system. If not, apply the note.
(b) Completion monitoring of InfoPackage fails.
If Request XXX could not be generated appears in a KAJM0813-E message
that appears before KMJM2825-E message, a timeout error has occurred in the
monitoring of the registration of a data load request. Check whether the value of the
registration monitoring time for data load requests (RequestMonitorTime key in the
command section in the environment setup file) is appropriate.
(c) The started InfoPackage ends abnormally in the SAP BW system.
The probable causes are described below.
„
The display setting is incorrect for the end of InfoPackage with a warning.
If Processing exceeded the specified time appears as the detailed text
in a KAJM2827-E message, a timeout error may have occurred in the monitoring
of the request that was generated by InfoPackage in the SAP BW system after
InfoPackage ended with a warning. The InfoPackage probably ended abnormally.
If InfoPackage ends with a warning, check whether the signal color changes to
green or red. Open the Monitor window of the administrator workbench, and
choose Settings -> Evaluation of requests (traffic lights). In the opened dialog
box, check whether is judged to be successful (green lights) or is thought to
have errors (red lights) is selected in If no data is available in the system, the
request and If warning arise during processing, the request.
249
8. Troubleshooting Guide for JP1/AJS3 for EAP
„
The SAP BW system has a known problem.
If Processing exceeded the specified time appears as the detailed text
in a KAJM2827-E message immediately after execution of InfoPackage, there
may be a problem with the SAP BW system. Check whether SAP Notes 633981,
641466, 647855, and 655528 have been applied to the connection destination
SAP BW system. If not, apply the notes.
(d) The job following InfoPackage ends abnormally.
JP1/AJS3 for EAP cannot monitor the completion of a QM action (enables the loaded
data) that is executed after loading of the InfoPackage data or the completion of
subsequent InfoPackage processing (such as deleting duplicated requests). If resource
contention occurs between these types of processing and the succeeding job, the
succeeding job may end abnormally.
To prevent an abnormal end, you need to set the job that executes InfoPackage so that
it ends after a QM action or the subsequent InfoPackage processing. To do so, use the
-qmwait_time option of the jbwipsta command to set a period of time (wait time)
between the normal end of InfoPackage and the end of the job that executes
InfoPackage.
(e) A file named dev_rfc.trc or dev_rfc was created in the JP1/AJS3 for EAP
work directory.
If an error occurs during SAP BW system custom job execution or JP1/AJS3 for EAP
command execution, the RFC trace file (file named dev_rfc.trc or dev_rfc) is
created in the JP1/AJS3 for EAP work directory. The RFC trace file records the trace
information (error information) about the communications with the SAP BW system.
The RFC trace file is needed only when a serious error occurs. We recommend that you
periodically delete the RFC trace file when no serious error has been encountered.
(3) Trouble with process chain control
This subsection describes the problems that may occur while you are controlling
process chains.
If you cannot find the cause of a problem here, the problem may be caused by the
external management interface provided by SAP. If a KAJM0812-E message appears,
a problem with the external management interface is likely. Obtain the name of the
function of the external management interface with the problem and the exception
code from the message, and contact the SAP BW system administrator.
(a) The process chain for the SAP BW system cannot be started.
The probable causes are described below.
250
8. Troubleshooting Guide for JP1/AJS3 for EAP
„
The user who has logged on does not have permission to execute the process
chain.
To execute a process chain using the jbwipsta command, you need permission
to log on from an external system (S_RFC) as well as permission to execute each
process in each process chain in the background.
Perform either of the following procedures to obtain permission to execute
process chains:
• Log on again with a user name that is allowed to execute process chains.
• Ask the SAP BW system administrator to grant a permission to execute
process chains.
„
The definition of the process chain is incomplete.
Check the definition of the process chain you attempted to start in the SAP BW
system. Check whether the process chain is defined so it can be started correctly.
Then re-execute the command.
(b) The started process chain ends abnormally in the SAP BW system.
The probable causes are described below.
„
The user who has logged on does not have permission to execute the process
chain.
To execute a process chain using the jbwipsta command, you need permission
to log on from an external system (S_RFC) as well as permission to execute each
process in each process chain in the background.
Perform either of the following procedures to obtain permission to execute
process chains:
• Log on again with a user name that is allowed to execute process chains.
• Ask the SAP BW system administrator to grant permission to execute
process chains.
„
The process chain is being updated.
Use the SAP front-end software to check whether the definition of the processes
in the process chain is being updated.
If a process chain executed by JP1/AJS ends abnormally, perform either of the
following procedures to restore the job:
• Re-execute processing from the beginning of the process chain.
Re-execute the job for the abnormally ended process chain from JP1/AJS.
• Re-execute processing from the process where the error occurred.
251
8. Troubleshooting Guide for JP1/AJS3 for EAP
Use the SAP front-end software to check the status of the process chain that ended
abnormally and re-execute the processing from the process where the error
occurred. Allow JP1/AJS to execute the subsequent jobs when the re-executed
process chain is completed.
(c) A file named dev_rfc.trc or dev_rfc was created in the JP1/AJS3 for EAP
work directory.
If an error occurs during the execution of a custom job for the SAP BW system or a
JP1/AJS3 for EAP command, an RFC trace file named dev_rfc.trc or dev_rfc is
created in the work directory of JP1/AJS3 for EAP. The RFC trace file contains the
trace information about the communication with the SAP BW system (information
about the item that caused the error).
The RFC trace file is required for serious errors. If no serious errors occur, we
recommend that you delete the RFC trace file periodically.
252
Appendixes
A. Directory List
B. Port Numbers
C. Modifications Made in Each Version
D. Glossary
253
A. Directory List
A. Directory List
The directories created when JP1/AJS3 for EAP is installed are listed below for each
type of OS.
A.1 Folder list (Windows)
The following table describes some of the folders that are created after JP1/AJS3 for
EAP is installed.
Table A-1: JP1/AJS3 for EAP folder list (Windows)
Folder name
Description
Program\
This folder contains program files and other files.
System\
This folder contains system data files.
Conf\
This folder contains environment setup files.
Sample\
This folder contains sample files.
Log\
This folder contains default trace files.
Bwsta\
This folder is created for the InfoPackage control function or the
process chain control function.
Bwsta\Program\
This folder contains program files and other files.
Bwsta\Image\
This folder contains icon files.
Bwsta\Conf\
This folder contains environment setup files.
Bwsta\Log\
This folder contains default trace files.
Lib\
This folder contains library files.
Lib\Rfc\
This folder contains RFC library files.
Lib\Rfc\700\
This folder contains RFC library (7.00) files.
Lib\Hliclib\
This folder contains product information library files.
Tools\
This folder contains common commands.
A.2 Directory list (UNIX)
The following table describes some of the directories that are created after JP1/AJS3
for EAP is installed.
254
A. Directory List
Table A-2: JP1/AJS3 for EAP directory list (UNIX)
Directory name
Description
/etc/opt/jp1_am_r3/
This directory contains environment setup
information.
/etc/opt/jp1_am_r3/conf/
This directory contains environment setup files.
/etc/opt/jp1_am_r3/bwsta/
This directory is created for the InfoPackage control
function or the process chain control function.
/etc/opt/jp1_am_r3/bwsta/conf/
This directory contains environment setup files.
/opt/jp1_am_r3/
This directory contains execution context
information.
/opt/jp1_am_r3/bin/
This directory contains commands.
/opt/jp1_am_r3/bin/700/
This directory contains commands corresponding to
the RFC library (7.00).
/opt/jp1_am_r3/lib/
This directory contains library files.
/opt/jp1_am_r3/lib/rfc/
This directory contains REF library files common to
all versions.
/opt/jp1_am_r3/lib/rfc/700/
This directory contains RFC library files
corresponding to the RFC library (7.00).
/opt/jp1_am_r3/share/
This directory contains shared files.
/opt/jp1_am_r3/sample/
This directory contains sample files.
/opt/jp1_am_r3/bwsta/
This directory is created for the InfoPackage control
function or the process chain control function.
/opt/jp1_am_r3/bwsta/bin/
This directory contains commands.
/opt/jp1_am_r3/bwsta/bin/700/
This directory contains commands corresponding to
the RFC library (7.00).
/opt/jp1_am_r3/bwsta/lib/
This directory contains library files.
/opt/jp1_am_r3/bwsta/share/
This directory contains shared files.
/var/opt/jp1_am_r3/
This directory contains data.
/var/opt/jp1_am_r3/log/
This directory contains default trace files.
/var/opt/jp1_am_r3/bwsta/
This directory is created for the InfoPackage control
function or the process chain control function.
/var/opt/jp1_am_r3/bwsta/log/
This directory contains default trace files.
255
A. Directory List
Directory name
/opt/jp1_am_r3/tools/
256
Description
This directory contains common commands.
B. Port Numbers
B. Port Numbers
This appendix describes the port numbers that are used when JP1/AJS3 for EAP
communicates with an R/3 system or a SAP BW system and the direction of traffic
when a firewall is installed.
B.1 Port numbers to be used for communication with an R/3 system
or a SAP BW system
JP1/AJS3 for EAP uses Remote Function Call (RFC), which is a communication
program provided by SAP, to communicate with an R/3 system or a SAP BW system
(RFC connection). In an RFC connection, the connecting side (JP1/AJS3 for EAP)
does not use a specific port number or a well-known port number and, instead, uses
any available port assigned by the OS. The connected side (R3/system or SAP BW
system), however, uses different port numbers depending on the method of RFC
connection.
The following table describes the port numbers that can be used by the R/3 system or
the SAP BW system depending on the method of RFC connection.
Table B-1: Port numbers used for RFC connection
Type of
device for
connection
Service name
Port number
Direction of traffic
Application
server
sapgwnn#1, #2
33nn/tcp#1
JP1/AJS3 for EAP
R/3
system or SAP BW system
Message
server (load
balancing)
sapmssid#3
Any/tcp
(Default: 3600/tcp)
JP1/AJS3 for EAP
R/3
system or SAP BW system
SAP router
Any
(Default: sapdp99)
Any/tcp
(Default: 3299/tcp)
JP1/AJS3 for EAP
R/3
system or SAP BW system
Legend:
: Direction of traffic when a connection is established
#1
nn indicates the system number of the connection destination R/3 system or SAP
BW system.
#2
If you use secure network communication (SNC), use sapgwnns (port number
257
B. Port Numbers
range: 4800 to 4899/tcp (48nn/tcp).
#3
sid indicates the system ID of the connection destination R/3 system or SAP BW
system.
B.2 Permitted direction of traffic when a firewall is used
When you place a firewall between JP1/AJS3 for EAP and an R/3 system or a SAP
BW system, specify the port settings for the firewall to permit transmission in the
following direction:
From JP1/AJS3 for EAP to the R/3 system or the SAP BW system
258
C. Modifications Made in Each Version
C. Modifications Made in Each Version
This section lists the modifications made in each version.
(1) Modifications made for upgrading from version 08-00 to 09-00
The following modifications were made relative to upgrading from version 08-00 to
09-00:
• JP1/SES format events are no longer issued.
• The version of the provided RFC library is now limited to 7.00.
• SAP NetWeaver Process Integration 7.1 is now supported.
• The custom job function is now compatible with JP1/AJS3.
• The product name has been changed.
• The default value of the code page number can now be specified in the
environment setup file.
• SAP user setting-related explanations have been added.
• The password rule (extended password) extended in the SAP system based on
SAP NetWeaver 7.0 and later is now supported.
(2) Modifications made for upgrading from version 07-00 to 07-50
The following modification was made for upgrading from version 07-00 to 07-50:
• A function has been added to control process chains.
• Job classes can now be specified when R/3 jobs are created.
• The completion of multiple jobs that include child jobs can now be monitored.
• The print parameters, which can be specified when R/3 jobs are created, have
been extended.
(3) Modifications made for upgrading from version 06-71 to 07-00
The following modification was made for upgrading from version 06-71 to 07-00:
• Job control functions and InfoPackage control functions were integrated as a
single product. A new name was given to the product.
(4) Modifications made for upgrading from version 06-51 to 06-71
The following modification was made for upgrading from version 06-51 to 06-71:
• InfoPackage control functions were added.
259
C. Modifications Made in Each Version
(5) Modifications made for upgrading from version 06-00 to 06-51
The following modifications were made for upgrading from version 06-00 to 06-51:
• A command for deleting R/3 jobs was added.
• If a communication error occurs at establishment of a connection, it is now
possible to retry connection.
(6) Modifications made for upgrading from version 05-20 to 06-00
The following modifications were made for upgrading from version 05-20 to 06-00:
• The version 06-00 supports R/3 4.5 and 4.6.
• Custom jobs can now be used with JP1/AJS2.
• You can specify more detailed information in the print parameters you supply
when submitting an R/3 job.
(7) Modifications made for upgrading from version 05-11 to 05-20
The following modification was made for upgrading from version 05-11 to 05-20:
• The version 05-20 provides an additional function used to manage outputs from
the R/3 system.
(8) Modifications made for upgrading from version 05-00 to 05-11
The following modifications were made for upgrading from version 05-00 to 05-11:
• If a communication error occurs during the process of monitoring the termination
of an R/3 job, it is now possible to retry connection to the R/3 system.
• You can specify output files when submitting R/3 jobs.
260
D. Glossary
D. Glossary
This chapter explains JP1/AJS3 for EAP terminology, R/3 system terminology, and
other related specialized words.
ABAP
Fourth-generation language used with the R/3 system.
ABAP program
Report program created with a fourth-generation language (ABAP). Used with the R/
3 system.
application server
Server that executes a process from a machine running SAP front-end software.
authorized user
User who is authorized to execute an R/3 program (ABAP program or external
program).
background job
Job that is executed by the background processing function of the R/3 system. In this
manual, it is sometimes referred to as an R/3 job or a job.
BW - SCH interface
A SAP open interface used to control process chains in the SAP BW system from an
external system.
BW - STA interface
A SAP open interface used to control InfoPackage in the SAP BW system from an
external system.
custom job
Job that has a specific function (R/3 job in the case of JP1/AJS3 for EAP) and is
defined as a job that is executable by JP1/AJS. To use the JP1/AJS custom job function
from JP1/AJS3 for EAP, the custom job component for the R/3 system is required. The
R/3 system custom job component is automatically installed when JP1/AJS3 for EAP
is installed.
event
Specific event that occurs in the system.
For Windows, a JP1/AJS3 for EAP event that is displayed as an application log by the
Windows Event Viewer administrative tool.
261
D. Glossary
extended password
Password that is extended in SAP NetWeaver 7.0. The password can be up to 40 bytes
long. Alphabetic characters are case-sensitive.
external management interface
A generic term for the open interfaces provided by SAP. These include the XBP, BW
- STA, and BW - SCH interfaces.
external program
General program (batch program or OS command) that can be executed by the R/3
system.
InfoPackage
Definition used for transferring data to a SAP BW system. It indicates from which
system data is to be fetched and to which system the data is to be transferred.
Data can be transferred to a SAP BW system by executing InfoPackage.
job
Unit of processing that is executed by the background processing function of the R/3
system. In this manual, it is sometimes referred to as an R/3 job or a background job.
job count
Count assigned by the R/3 system to a created job.
job step
Element of a job. One job step consists of an ABAP program (or an external program).
jobnet
A set of jobs whose execution order is defined. Jobs within the jobnet are automatically
executed in a predefined order. The jobnet is a function provided by JP1/AJS.
JP1/Automatic Job Management System (JP1/AJS)
JP1/AJS is a program for running jobs automatically. JP1/AJS enables you to execute
processes in order routinely and to start process when a specific event occurs. After
jobs are created, processes are executed automatically so that jobs are performed by
regular personnel, or are performed by substitutes when the regular personnel are
absent. In this way the job still gets accomplished.
JP1/Base
JP1/Base is a program that provides the event service function. JP1/Base enables you
to control the order of startup of services, and lets you send and receive JP1 events.
JP1/Base is also a prerequisite program for JP1/IM, JP1/AJS, and JP1/Power Monitor.
When a system using JP1/IM and JP1/AJS is implemented, JP1/Base provides the
262
D. Glossary
function for restricting of JP1 users' operations.
JP1/IM
A program that centrally monitors a distributed system. You can monitor JP1 events
that express information, such as job-processing status or trouble in the distributed
system.
JP1/System Event Service (JP1/SES)
Program product that provides functions (system event service) for managing the
events issued by a program.
process chain
A method of automatically executing jobs in the SAP BW system. A process chain
consists of a series of processes (jobs) that are executed in the background. When a
process chain is executed, a series of processes is automatically executed based on a
predetermined execution sequence.
R/3 client
Virtual user environment in the R/3 system. In the R/3 system, users and jobs are
managed on an individual client basis.
R/3 destination information
Common argument for JP1/AJS3 for EAP commands. It is used for establishing a
connection to the R/3 system.
R/3 job
Job that is executed by the background processing function of the R/3 system or the
SAP BW system. In this manual, it is sometimes referred to as a background job or a
job.
R/3 job log
Job log managed by the R/3 system.
R/3 logon information
Common argument for JP1/AJS3 for EAP commands. It is used to specify user
information for logging on to an R/3 system.
request number
Number assigned by the SAP BW system when InfoPackage is started.
SAP BW client
Virtual user environment in the SAP BW system that is called a client. In the SAP BW
system, users and jobs are managed on an individual client basis.
263
D. Glossary
SAP BW destination information
Common argument of JP1/AJS3 for EAP commands. It is used for establishing a
connection to the SAP BW system.
SAP BW logon information
Common argument of JP1/AJS3 for EAP commands. It is used to specify user
information for logging on to a SAP BW system.
SAP front-end software
SAP client software that requests processing from an application server.
trace information
When a fault occurs in JP1/AJS3 for EAP, trace information is collected to identify the
cause of the problem.
variant
Argument that can be used in an ABAP program.
XBP interface
The XBP (eXternal Background Processing) interface is a SAP open interface used to
control background jobs in the R/3 system from an external system.
XMI interface session
The XMI (eXternal Monitor Interface) interface session is an R/3 system session that
monitors and records access between an external system (system external to the R/3
system) and an R/3 system.
264
Index
A
ABAP 261
ABAP program 6, 261
abbreviations defined iii
action to take when InfoPackage ends with warning,
setting 56
actions to be taken for problems 240
address 35, 55
address section 35, 55
application server 261
argument formats
command of InfoPackage/process chain
control function 112
common to job control function
commands 109
common to various commands 109
AuditLevel 28
authorized user 261
B
background job 3, 6, 261
canceling 7, 121
creating 7, 142
displaying information about 7, 137
executing, using JP1/AJS 59
releasing 7, 127
status transition of 6
BW - SCH interface 9, 261
BW - STA interface 9, 261
C
CheckLevel 25
Client 35, 55
client number 35, 55
Codepage
InfoPackage/process chain control 48
job control 27
command 24, 45
InfoPackage/process chain control 45
job control 24
command formats 106
command list 107
command section 24, 45
InfoPackage/process chain control 45
job control 24
command usage precautions 108
commands 105
common to all functions 108
InfoPackage/process chain control
function 107
job control function 107
completion monitoring of parent and child jobs 7, 85,
130, 152
conventions
abbreviations iii
diagrams vi
fonts and symbols vi
KB, MB, GB and TB viii
used in format explanations 106
version numbers viii
Cover dialog box 82
custom job 261
defining 62, 93
registering 60, 91
D
data to be collected
if problem occurs 225
InfoPackage control function 232
job control function 225
process chain control function 232
Dest 36
diagram conventions vi
directory list 254
UNIX 254
265
Index
E
enabling
parent and child function 37
XBP 2.0 interface 37
environment setup file
InfoPackage/process chain control 40
job control 20
event 23, 44, 261
event ID format 158
event section 23, 44
events 157
list of 158
maintenance information about 163
extended password 262
InfoPackage/process chain control 55
job control 35
external management interface 6, 9, 262
external program 262
F
features 2
folder list (Windows) 254
font conventions vi
G
GB meaning viii
glossary 261
H
headings in command explanations 106
Host 36
hosts file
adding R/3 system entries to 31
adding SAP BW system entries to 50
I
InfoPackage 9, 262
InfoPackage control function 9
trouble related to 246
InfoPackage control, trouble with 248
InfoPackage/process chain
executing 90
procedures for executing 90
266
InfoPackage/process chain control function
command for 107
JP1/AJS3 for EAP 9
setup 39
installation 13, 14
installing
UNIX version of JP1/AJS3 for EAP 15
UNIX-compliant JP1/AJS3 for EAP 15
Windows version of JP1/AJS3 for EAP 14
Windows-compliant JP1/AJS3 for EAP 14
interval for monitoring completion of InfoPackage/
process chain 45
J
jbwipsta 116
jbwipsta command 9
job 262
Job class 72
job class 36, 143
job completion monitoring interval 25
job control function 6
commands for 107
commands, common argument format
for 109
setup 18
trouble related to 240
job count 262
job release/completion monitoring 84
job step 143, 262
defining 75
Job Step dialog box 75
JoblogAddToStderr (job control) 27
jobnet 262
JP1 Series programs, linkage with 10
JP1/AJS 10, 11
JP1/AJS3 for EAP, overview of 1
JP1/Automatic Job Management System (JP1/
AJS) 262
JP1/Base 262
JP1/IM 263
JP1/Script 10
JP1/SES 263
JP1/System Event Service (JP1/SES) 263
jr3bjcan 121
Index
jr3bjcan command
jr3bjdel 124
jr3bjdel command
jr3bjrel 127
jr3bjrel command
jr3bjrep 135
jr3bjrep command
jr3bjsho 137
jr3bjsho command
jr3bjsub 142
jr3bjsub command
jr3chrfc 155
7
7
6, 7
8
7
7
K
KB meaning viii
L
Lang 35, 55
language type 35, 55
setting 49
Level 22, 43
logon 34, 54
logon section 34, 54
M
maintenance information about events 163
MB meaning viii
message explanations, format of 169
messages 167
format of 168
list of 170
output destinations of 169
output format of 168
modification made in each version 259
Monitor dialog box 83
MonitorInterval 25, 45
N
Note609462 (job control) 29
ntevent 24, 44
O
operating environment
setting (InfoPackage/process chain
control) 40
setting (job control) 20
setting, for JP1/AJS3 for EAP (InfoPackage/
process chain control) 40
setting, for JP1/AJS3 for EAP (job
control) 20
option (job control) 28
option section (job control) 28
Output Results dialog box (for execution result output
destination) 86
overview 1
P
Passwd 35, 55
Passwd2
InfoPackage/process chain control 55
job control 35
password 35, 55
characters that can be specified in 38, 57
PATH 30, 49
path, setting 29, 49
permitted direction of traffic when firewall is
used 258
port number 30, 257
InfoPackage/process chain control 50
job control 30
used for communication with R/3 system 257
used for communication with SAP BW
system 257
procedures for executing R/3 jobs 60
process chain 9, 263
process chain control function 9
trouble related to 246
process chain control, trouble with 250
Q
QMActionWaitTime (InfoPackage control) 48
R
R/3 client 263
R/3 destination information 109, 263
R/3 job 263
267
Index
R/3 Job Definition dialog box 66, 70
R/3 Job Definition page 70
R/3 job log 263
R/3 jobs
executing, by using JP1/AJS2 60
procedures for executing 60
R/3 logon information 110, 263
R/3 system entries
adding, to hosts file 31
adding, to services file 30
R/3 System page 66
R/3 system resources, acquiring information about 8,
135
R/3 system, trouble related to 240
r3defcon file 33, 110, 111, 114, 115
redirection information 111
report program created by using ABAP 6
request number 263
RequestMonitorTime 47
RetryCount
InfoPackage/process chain control 46
job control 26
RetryInterval 27, 47
RetryTime 26, 46
RFC library status management file 155
RFC_INI 32, 51
S
SAP BW client 263
SAP BW destination information 113, 264
SAP BW InfoPackage or Process Chain Definition
page 100
SAP BW InfoPackage/Process Chain Definition
dialog box 97, 100
SAP BW logon information 114, 264
SAP BW system custom job 91
SAP BW system entries
adding, to hosts file 50
adding, to services file 50
SAP BW System page 97
SAP BW system, trouble with connection to 247
SAP front-end software 264
SAP user
268
providing, for InfoPackage/process chain
control 56
providing, for job control 37
SAP user name 35, 55
saprfc.ini file 31, 51, 110, 113
service name 30
InfoPackage/process chain control 50
job control 30
services file
adding R/3 system entries to 30
adding SAP BW system entries to 50
setup 13
job control function 18
Size 22, 43
symbol conventions vi
syntax 106
syntax conventions vii
Syslog 24, 45
syslog messages 45, 217
format of 218
list of 219
Sysno 36
system configuration 3
T
TargetDir 23
TargetFile 23, 44
TB meaning viii
trace 22, 42
trace file (job control) 23
trace file size 22, 43
trace information 264
trace level 22, 43
trace section 22, 42
trouble
related to InfoPackage control function 246
related to job control function 240
related to process chain control function 246
with connection to R/3 system 240
with connection to SAP BW system 247
with InfoPackage control 248
with process chain control 250
with R/3 job control 241
troubleshooting procedure 224
Index
U
uninstalling 15, 16
User 35, 55
user type 38, 57
V
variant 264
version change 259
version number conventions viii
W
Windows events 44
work directory for command 45
work directory to be used for execution of JP1/AJS job
InfoPackage/process chain control 45
job control 24
WorkDir 24, 45
X
XBP 2.0 interface 36
XBP interface 6, 264
XMI 28
XMI interface session 264
XMI interface session audit level 28
XMI section 28
269
Reader’s Comment Form
We would appreciate your comments and suggestions on this manual. We will use
these comments to improve our manuals. When you send a comment or suggestion,
please include the manual name and manual number. You can send your comments
by any of the following methods:
• Send email to your local Hitachi representative.
• Send email to the following address:
[email protected]
• If you do not have access to email, please fill out the following information
and submit this form to your Hitachi representative:
Manual name:
Manual number:
Your name:
Company or
organization:
Street address:
Comment:
(For Hitachi use)
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Related manuals

Download PDF

advertisement