Job Management Partner 1/Automatic Job Management System 3 for Enterprise Applications Description, User's Guide and Reference

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.

Organization of this subsection

(1) Making sure that the -d option for R/3 destination information is usable

(2) Specifying the defaults for command common arguments (R/3 destination information and R/3 logon information)

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

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.

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.

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.

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.

[Contents][Back][Next]

[Trademarks]