Job Management Partner 1/Automatic Job Management System 3 Administration Guide

[Contents][Glossary][Index][Back][Next]


Preface

This manual describes how to operate Job Management Partner 1/Automatic Job Management System 3 (abbreviated hereafter to JP1/AJS3). Read this manual in conjunction with the manual Job Management Partner 1/Automatic Job Management System 3 Overview, which describes the JP1/AJS3 functions, the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide, which describes JP1/AJS3 design, and the Job Management Partner 1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

Intended readers

This manual is intended for:

Organization of this manual

This manual organized into the following chapters. The manual is a common reference for all supported operating systems. Any platform-dependent differences in functionality are noted in the manual.

1. Overview of Operation Using JP1/AJS3
Chapter 1 provides an overview of system operation using JP1/AJS3.

2. Backup and Recovery
Chapter 2 describes how to perform backup and recovery in a system that uses JP1/AJS3.

3. Backing Up and Recovering Databases
Chapter 3 describes how to back up and recover JP1/AJS3 databases.

4. Backing Up and Restoring Jobnets
Chapter 4 describes how to back up and restore the definition information of jobnets and the registration status of each jobnet.

5. Monitoring Jobnets
Chapter 5 describes the execution results of jobnets and how to monitor jobnet execution time.

6. Monitoring Capacities
Chapter 6 describes how to monitor capacities in JP1/AJS3.

7. Starting and Stopping JP1/AJS3 Services
Chapter 7 describes how to start and stop JP1/AJS3 services.

8. Changing the Settings During Operation
Chapter 8 describes how to change the environment and settings during JP1/AJS3 operation.

9. Operating Methods
Chapter 9 provides know-how for operating JP1/AJS3 efficiently.

10. Database Maintenance
Chapter 10 describes how to maintain the JP1/AJS3 database.

11. Operation in a Cluster System
Chapter 11 describes the flow of processing when JP1/AJS3 is used in a cluster system.

Related publications

This manual is part of a related set of manuals. The manuals in the set are listed below (with the manual numbers):

About JP1/AJS:

About JP1:

Conventions: Abbreviations

This manual uses the following abbreviations for product names:

Abbreviation Full name or meaning
JP1/AJS3 JP1/AJS3 - Manager Job Management Partner 1/Automatic Job Management System 3 - Manager
JP1/AJS3 - Agent Job Management Partner 1/Automatic Job Management System 3 - Agent
JP1/AJS3 - View Job Management Partner 1/Automatic Job Management System 3 - View
JP1/AJS2 JP1/AJS2 - Manager Job Management Partner 1/Automatic Job Management System 2 - Manager
JP1/AJS2 - Agent Job Management Partner 1/Automatic Job Management System 2 - Agent
JP1/AJS2 - View Job Management Partner 1/Automatic Job Management System 2 - View
JP1/AJS2 - Advanced Manager Job Management Partner 1/Automatic Job Management System 2 - Advanced Manager#
JP1/AJS2 - Client Toolkit Job Management Partner 1/Automatic Job Management System 2 - Client Toolkit#
JP1/AJS3 - Definition Assistant Job Management Partner 1/Automatic Job Management System 3 - Definition Assistant
JP1/AJS3 - Web Operation Assistant Job Management Partner 1/Automatic Job Management System 3 - Web Operation Assistant
JP1/AJS3 for Enterprise Applications Job Management Partner 1/Automatic Job Management System 3 for Enterprise Applications
JP1/AJS2 for Oracle E-Business Suite Job Management Partner 1/Automatic Job Management System 2 for Oracle E-Business Suite
NNM HP NNM HP Network Node Manager Software version 7.5 or earlier
HP Network Node Manager Software Starter Edition version 7.5 or earlier
JP1/FTP Job Management Partner 1/File Transmission Server/FTP
JP1/IM JP1/IM - Manager Job Management Partner 1/Integrated Management - Manager
JP1/IM - View Job Management Partner 1/Integrated Management - View
JP1/IM - Central Console Job Management Partner 1/Integrated Manager - Central Console#
JP1/IM - Central Scope Job Management Partner 1/Integrated Manager - Central Scope#
JP1/OJE Job Management Partner 1/Open Job Entry
JP1/OJE for Midrange Computer Job Management Partner 1/Open Job Entry for Midrange Computer
JP1/SES Job Management Partner 1/System Event Service
JP1/OJE for VOS3 VOS3 Job Management Partner 1/Open Job Entry
MSCS Microsoft(R) Cluster Server
Excel Microsoft(R) Excel
Microsoft(R) Office Excel
Exchange Server Microsoft(R) Exchange 2000 Enterprise Server
Microsoft(R) Exchange 2000 Server
Microsoft(R) Exchange Server
IE Microsoft(R) Internet Explorer(R)
Microsoft Mail Microsoft(R) Mail
MSMQ Microsoft(R) Message Queue Server
Outlook Outlook 2000 Microsoft(R) Outlook(R) 2000
Outlook 2002 Microsoft(R) Outlook(R) 2002
Outlook 2003 Microsoft(R) Outlook(R) 2003
Outlook 2007 Microsoft(R) Outlook(R) 2007
Outlook Express Microsoft(R) Outlook(R) Express
Microsoft SQL Server Microsoft(R) SQL Server
Microsoft(R) SQL Server Enterprise Edition
Windows 7 Microsoft(R) Windows(R) 7 Enterprise
Microsoft(R) Windows(R) 7 Professional
Microsoft(R) Windows(R) 7 Ultimate
Windows Server 2003 Windows Server 2003 Microsoft(R) Windows Server(R) 2003, Enterprise Edition Operating System
Microsoft(R) Windows Server(R) 2003, Standard Edition Operating System
Windows Server 2003 (x64) Microsoft(R) Windows Server(R) 2003, Enterprise x64 Edition
Microsoft(R) Windows Server(R) 2003, Standard x64 Edition
Windows Server 2008 Microsoft(R) Windows Server(R) 2008 Datacenter
Microsoft(R) Windows Server(R) 2008 Enterprise
Microsoft(R) Windows Server(R) 2008 Standard
Windows Vista Microsoft(R) Windows Vista(R) Business
Microsoft(R) Windows Vista(R) Enterprise
Microsoft(R) Windows Vista(R) Ultimate
Windows XP Professional Microsoft(R) Windows(R) XP Professional Operating System
AIX AIX 5L 5.3
AIX V6.1
HP-UX HP-UX (IPF) HP-UX 11i V2(IPF)
HP-UX 11i V3(IPF)
Solaris Solaris 9(SPARC)
Solaris 10(SPARC)
SAP BW SAP Business Information Warehouse
SAP R/3 SAP R/3(R)

#: Version 7

This manual also uses the following abbreviations:

Abbreviation Full name or meaning
ACL Access Control List
DB Database
DBMS Database Management System
DNS Domain Name System
EUC Extended UNIX Code
FQDN Fully Qualified Domain Name
FTP File Transfer Protocol
GUI Graphical User Interface
IPF Itanium(R) Processor Family
ISAM Indexed Sequential Access Method
LAN Local Area Network
MAPI Messaging Application Programming Interface
MIB Management Information Base
MIME Multipurpose Internet Mail Extensions
NAT Network Address Translator
NFS Network File System
NIC Network Interface Card
OS Operating System
RDB Relational Database
SNMP Simple Network Management Protocol
SMTP Simple Mail Transfer Protocol
SUP Service Using Program
TCP/IP Transmission Control Protocol/Internet Protocol
UAC User Account Control
UNC Universal Naming Convention
WAN Wide Area Network
WOW64 Windows On Windows 64
WSDL Web Services Description Language

JP1 program reorganization in version 8

The following changes have been made to the JP1 product suite in version 8:

Conventions: Diagrams

This manual uses the following conventions in diagrams:

[Figure]

Conventions: Fonts and symbols

Font and symbol conventions are classified as:

These conventions are described below.

General font conventions

The following table lists the general font conventions:

Font 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.
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 Convention
StoreDatabase Code-font characters must be entered exactly as shown.
database-name This font style marks a placeholder that indicates where appropriate characters are to be entered in an actual command.
SD Bold code-font characters indicate the abbreviation for a command.
Perm Underlined characters indicate the default value.
[ ] Square brackets enclose an item or set of items whose specification is optional.
| Only one of the options separated by a vertical bar can be specified at the same time.
... 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 for mathematical expressions

This manual uses the following symbols in mathematical expressions:

Symbol Meaning
x Multiplication sign
/ Division sign
[Figure] [Figure] The calculation result is rounded up to the next whole number.
Example:
The result of [Figure] 34 / 3[Figure] is 12.
[Figure]
(tilde)
The item shown before this symbol must be specified in accordance with the conventions shown for angle brackets, double parentheses, and double angle brackets (below).
< >
(angle brackets)
Indicates the characters and lexical elements that can be specified.

<characters>
One or more Kanji characters, katakana characters, upper-case alphabetic characters, lower-case alphabetic characters, or numeric characters

<numeric>
0, 1, 2, 3, 4, 5, 6, 7, 8, or 9

<alphabetic character>
A, B, C, D, E, F, G, H, I, J, K, L, M, N, O, P, Q, R, S, T, U, V, W, X, Y, Z, \, #, or @

<alphanumeric character>
Alphabetic or numeric character

<symbolic name>
No more than eight alphanumeric characters beginning with an alphabetic character

<unsigned integer>
One or more numeric characters

<hexadecimal character>
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, A, B, C, D, E, or F

<file name>
A system-determined name assigned to a file

<path>
The directories contained in the path, with each name separated by a forward slash (/) or backslash (\). The path notation is OS-dependent.
(( ))
(double parentheses)
Indicates the range of specifiable values.
<< >>
(double angle brackets)
Indicates the default assumed by the system when a value is unspecified.
Example:
If you do not specify days-to-keep-form ~<numeric> ((0 to 365)) <<365>>, 365 is assumed as the number of days to keep the form.
MAX Choose the largest of the calculation results.
Example:
The result of MAX (3 x 6, 4 + 7) is 18.

Conventions: KB, MB, GB, and TB

This manual uses the following conventions:

Conventions: Meaning of "directory" and "folder"

As a general rule, Windows folder names are used in this manual if they are identical to UNIX directory names.

Conventions: Meaning of "member of the Administrators group"

The term member of the Administrators group in this manual refers to a user who is a member of the Administrators group on the local PC only. The privileges of local users, domain users, and Active Directory users are no different as long as these users are members of the Administrators group on the local PC.

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:

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.

Default installation folders of JP1/AJS3 for Windows

The default installation folders of JP1/AJS3 for Windows are as follows:

Default installation folders of JP1/AJS3 - Manager:
system-drive\Program Files#1\HITACHI\JP1AJS2
and
system-drive\Program Files#1\HITACHI\JP1AJS2CM

Default installation folder of JP1/AJS3 - Agent:
system-drive\Program Files#1\HITACHI\JP1AJS2

Default installation folder of JP1/AJS3 - View:
system-drive\Program Files#2\HITACHI\JP1AJS2V

#1
For 64-bit versions of Windows Server 2008 and Windows Server 2003 (x64), replace Program Files with Program Files (x86).

#2
For 64-bit versions of Windows 7, Windows Server 2008, Windows Vista, and Windows Server 2003 (x64), replace Program Files with Program Files (x86).

Online manual

JP1/AJS3 - View comes with an online manual that you can read in either of the following browsers:

The online manual has the same contents as the following manuals:

In JP1/AJS3 - View, you can view the manual by choosing Help and then Contents. You can also press the F1 key to view the manual contents. Your Web browser must be associated with a file that has the extension htm; otherwise, the online manual will not be displayed correctly. If this happens, associate the htm file with the Web browser.

Cautionary note
Depending on the OS settings, the online manual might appear in the active window of the browser when you launch the manual from the Start menu.

Organization of JP1/AJS3 manuals and choosing the right manuals

There are fourteen JP1/AJS3 manuals. The following table summarizes their contents.

Note that Job Management Partner 1/Automatic Job Management System 3 is not listed in the table.

No. Manual Contents
1 Overview
(3020-3-S02(E))

  • JP1/AJS3 features
  • Description of functions
2 System Design (Configuration) Guide
(3020-3-S03(E))

  • Information that must be considered when designing a system
  • Cautionary notes on designing a system
3 System Design (Work Tasks) Guide
(3020-3-S04(E))

  • Information that must be considered when constructing jobs and jobnets
  • Cautionary notes on designing jobs and jobnets
4 Configuration Guide 1
(3020-3-S05(E))

  • Installation and setup procedures
  • Environment setup procedure by operation type
5 Configuration Guide 2
(3020-3-S06(E))

  • Description of environment setting parameters
6 Administration Guide
(3020-3-S07(E))

  • Information required to operate a system
  • Know-how useful for JP1/AJS3 operation
7 Troubleshooting
(3020-3-S08(E))

  • How to troubleshoot errors
  • Data required when an error occurs
8 Operator's Guide
(3020-3-S09(E))

  • How to operate JP1/AJS3 - View
  • How to operate JP1/AJS3 Console View
  • Description of windows and dialog boxes
9 Command Reference 1
(3020-3-S10(E))

  • Command syntax
10 Command Reference 2
(3020-3-S11(E))

  • Syntax of commands used for setup and special operations
  • Syntax and coding examples of information definition files
11 Linkage Guide
(3020-3-S12(E))

  • Description of functions that can be used when linked with other products and the setup method
12 Messages 1
(3020-3-S13(E))

  • Messages output by JP1/AJS3 (messages beginning with KAVC to KAVT)
13 Messages 2
(3020-3-S14(E))

  • Messages output by JP1/AJS3 (messages beginning with KAVU to KNAD)

Use the following illustration and table as a guide to determine the manuals you need to read.

[Figure]

Purpose Required reading Read as necessary
To learn about JP1/AJS3's functionalities
  • Overview
    (3020-3-S02(E))

  • Linkage Guide
    (3020-3-S12(E))
To configure a system (including installation and setup) that automatically runs jobs
  • System Design (Configuration) Guide
    (3020-3-S03(E))
  • Configuration Guide 1
    (3020-3-S05(E))

  • Configuration Guide 2
    (3020-3-S06(E))
  • Linkage Guide
    (3020-3-S12(E))
To design work tasks that will be automated (including job definitions and schedule definitions)
  • System Design (Work Tasks) Guide
    (3020-3-S04(E))

  • Operator's Guide
    (3020-3-S09(E))
To learn about monitoring and maintaining a running system.
  • Administration Guide
    (3020-3-S07(E))

  • Troubleshooting
    (3020-3-S08(E))
  • Messages 1
    (3020-3-S13(E))
  • Messages 2
    (3020-3-S14(E))
To learn about what action to take for problems that occur during operation.
  • Troubleshooting
    (3020-3-S08(E))

  • Messages 1
    (3020-3-S13(E))
  • Messages 2
    (3020-3-S14(E))
To learn about operating JP1/AJS3
  • Operator's Guide
    (3020-3-S09(E))

  • Command Reference 1
    (3020-3-S10(E))
  • Command Reference 2
    (3020-3-S11(E))

Regular expressions available in JP1/AJS3

Regular expressions can be used in some items in dialog boxes and commands. For details about regular expressions in Windows, see the Job Management Partner 1/Base User's Guide. For details about regular expressions in UNIX, see your UNIX documentation.

The regular expressions that you can use when executing an event job on a Windows host depend on the JP1/Base settings. For details on setting regular expressions for event job execution, see the explanation about extending the available regular expressions in the Job Management Partner 1/Base User's Guide.

Searching may take a long time if you often use the regular expression .* (which means match any character or characters). In long messages, use .* only where necessary. In UNIX, you can use [^ ]* (repeat characters other than space characters) instead of .* when you want to find a match other than space characters. Using [^ ]* reduces the search time.

About NNM linkage

JP1/AJS3 supports linkage with the following products:

In this manual, these products are indicated as HP NNM.

Note that linkage with the following products is not supported:

[Contents][Back][Next]


[Trademarks]

Copyright (C) 2009, 2010, Hitachi, Ltd.
Copyright (C) 2009, 2010, Hitachi Solutions, Ltd.