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

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)

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.

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 Value selectable as a string Explanation

Level

0

No trace

1

Standard level

2

Detail level

3

Debug level

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.

Size 0 or 1 to 65,535 (in kilobytes) 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.

TargetDir

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.

TargetFile

Windows:

Character string beginning with (drive-name):\ or remote resource name coded in UNC (Universal Naming Convention) format^#2

UNIX:

Character string beginning with /

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.

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

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

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

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.

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.

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 Valid key

RetryCount key RetryTime key RetryCount key RetryTime key

Yes Yes Yes No

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 Value selectable as a string Explanation

AuditLevel

0

Records data write (change) operations.

1

Records data read errors.

2

Records data read operations.

3

Records external management system access.

Specify the XMI interface session audit level. If this key specification is omitted, the current XMI interface session audit level continues to be used.
 
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.

Table 2-5 Keys that can be specified for option

Key Value selectable as a string Explanation

Note609462 YES or NO 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).

Key	Value selectable as a string	Explanation
Level	0 No trace 1 Standard level 2 Detail level 3 Debug level	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.
Size	0 or 1 to 65,535 (in kilobytes)	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.
TargetDir	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.
TargetFile	Windows: Character string beginning with (drive-name):\ or remote resource name coded in UNC (Universal Naming Convention) format^#2 UNIX: Character string beginning with /	Trace information about all applications will be collected in the specified file. Note If you specify this key, any assignment to TargetDir is ignored.

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.

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

Specified key	Valid key
RetryCount key	RetryTime key	RetryCount key	RetryTime key
Yes	Yes	Yes	No
Yes	No	Yes	No
No	Yes	No	Yes
No	No	Yes	No

Key	Value selectable as a string	Explanation
AuditLevel	0 Records data write (change) operations. 1 Records data read errors. 2 Records data read operations. 3 Records external management system access.	Specify the XMI interface session audit level. If this key specification is omitted, the current XMI interface session audit level continues to be used.

Key	Value selectable as a string	Explanation
Note609462	YES or NO	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.

[Contents][Back][Next]

[Trademarks]