A-AUTO for UNIX
A-AUTO for LinuxA-AUTO for Windows
V7. 2. 2

User’s Guide
2nd Edition

A-AUTO is a registered trade mark of BSP Inc. "This product includes software developed by the Apache
Software Foundation (http://www.apache.org/)." All other trademarks are property of their respective companies.
Product information specified in this manual is subject to change without notice.
©BSP Incorporated May 2012, 2nd Edition No part of this manual may be reproduced or transmitted in any form or by
any means.
EAUT-UW-722-020-2

About this ManualThis manual describes the operations of A-AUTO for UNIX A-AUTO for Windows A-AUTO for Linux systems. For
messages displayed by Windows application, please refer to the manual provided by the application.

Outline of this Manual
Outline of this manual is described below. Please refer to this manual in accordance with your operation.
In this manual, A-AUTO for UNIX and A-AUTO for Linux are referred to as A-AUTO for UNIX, and UNIX system andLinux system are referred to as UNIX System. In this manual, registry path of Windows system is expressed to fit 32
bit-environments. Therefore, "\HKEY_LOCAL_MACHINE\SOFTWARE\" in this manual should be expressed as"\HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\" in 64-bit environment. Section 3 is applicable for stand-alone
mode only. Please be advised that availability of certain utilities and functions of A-AUTO depends on the operation.
Remote Job Execution is available for both stand-alone mode and Mainframe connection mode.

Overview of A-AUTO for UNIX/Windows
Chapter 1

Introduction of System

Chapter 2

System Configuration and Workflow

Chapter 3

Master

Chapter 4

A-AUTO/Web ClientStand-alo
ne modeMainframeconnection
mode

○
○
○
○

○
○

○
○
○
○
○
○
○
○

○
○
○

○
○
○
○
○

○

○

○

○
○
○

○

RemoteJob Execution

○
○
○
○

Operations of A-AUTO for UNIX/ Windows
Chapter 5

Application Definition

Chapter 6

Operations

Chapter 7

Application Monitor

Chapter 8

Functions

Chapter 9

System Management

Chapter 10

Cross-Master

Chapter 11

Event Management

Chapter 12User Interface

Optional Products
Chapter 13

Remote Job Start Function

Chapter 14

Remote Job Start Function (System i)

Chapter 15

Limitation○

The Conventions of Marks/Special Expressions used in this document
The conventions of marks and special expressions included in the text are explained below.
■MarksMark

Description[]

Indicates a reference.

““

Indicates a title of the window.

Note)

Indicates additional information or explanation..

‘

Indicates an item displayed on the window.

“

Indicates an item defined by the user.

/

Separates a selection of items when it appears within {}.

■Special Expressions
Expression
yyyy, yy

Description
A number that represents year in 2 or 4 digits. When 2 digit, if 70<=yy<=99, yy represents
19yy year, else yy represents 20yy year.
[Example] 95: 1995

02: 2002

mm

A number that represents month (01-12) when referred in datedd

A number that represents date (01-31)

hh

A number that represents hour (00-23)mm

A number that represents minute (00-59) when referred in timess

A number that represents second (00-59)

The conventions of marks and special expressions included in command or parameter are explained below.
■The following marks have special meanings
Mark
{ }

Description
Indicates a selection of items. Items are separated by ‘/’.Select an appropriate item fromthe list.

[]

Indicates an item can be omitted. If omitted, a default value is applied.

…

Indicates repetitive items. Multiple commands or parameters can be specified. A single
specification is also accepted.

∆

Indicates blank.

■The following marks are specified as explained.
Mark

Description

,

Comma

=

Equal sign(

Left parenthesis)

Right parenthesis*

Asterisk－

Hyphen‘Apostrophe indicates items displayed on the window when it is used in the text.

/

Slash separates a selection of items when it appears within {}.

■ Please refer to the explanation when issuing commands and setting parameters.

A-AUTO for UNIX/Windows Manuals
The following is a list of manuals for A-AUTO for UNIX/Windows and a brief description of each manual.

A-AUTO for UNIX/Windows User’s Guide◆This document

Describes the functions of A-AUTO for UNIX/Windows system[Target audience: System Administrator / Operation Manager / Operator]

A-AUTO for UNIX/Windows System Administrator’s

Describes the system parameters and environment variables settings, system maintenance,
resources required to run the system, and limitations of the system.
[Target audience: System Administrator / Operation Manager / Operator]

A-AUTO for UNIX/Windows Operations Guide

Describes the operating procedures such as commands of the system and the utilities of
A-AUTO for UNIX/Windows.
[Target audience: System Administrator / Operation Manager / Operator]

A-AUTO for UNIX/Windows Setup Guide

Describes the procedures to install and setup the A-AUTO for UNIX/Windows System.
[Target audience: System Administrator / Operation Manager / Operator]

A-AUTO for UNIX/Windows Messages & Codes
Explanation of messages output by A-AUTO for UNIX/Windows and is provided in
html format.
[Target audience: System Administrator / Operation Manager / Operator]
To display messages & codes, login to A-AUTO/Web via client and open the Web help andselect "Messages & Codes".

Notes regarding Web browsers■ Supported browsers for A-AUTO for Windows/UNIX/LINUX are Microsoft Internet Explorer 6 andWindows Internet Explorer 7(Internet Explorer 7).
■ To view A-AUTO/Web screen as intended, do not use "back" button and "forward" button of the Webbrowser.
■ Also, opening a link in a new tab can cause trouble displaying the page. Therefore, do not use "open in
new tab" function of the Web browser.
■ Please refresh the page if page formatting fails and is displayed improperly.
■ If you want to use Web Client on Windows Server 2003 or Windows Server 2008, you need to set the
security settings of Internet Explorer. Please perform the following procedures(1) Start Internet Explorer, then to click “Tools(T)”-“Internet Options(O)” of tool bar. (After Internet Explorer
7, “Tools(O)”-“Internet Options(O)”.
(2) Click “Security” tab(3) Click “…Sites” button of “Trusted sites”.
(4) Type the following sites into “Add this Web site to the zone”, then click the “Add” button.
1. about: blank
2. Web address of A-AUTO Server
http://(IP Address or machine name of the installation destination of A-AUTO Server)

exp1:To set with IP address
http://192.168.27.140

exp2:To Set with machine namehttp://BSP00903

If Web sites that have been added to "Trusted sites" are included in local intranet zone, the following
warning dialog will be displayed.

[Site is located in the local intranet zone already. Are you sure you want to move to the site to the Trusted
sites zone?]
In this case, because you need not to move it, please click "No", then dialog will be closed.

Contents
1

The outline of A-AUTO for UNIX/Windows System
1.1

What is A-AUTO for UNIX/A-AUTO for Windows? ..................................................................... 1-1

1.2

Benefits from the Implementation of A-AUTO for UNIX/Windows .............................................. 1-4

2

System Configuration and Process Flow
2.1

2-1

System Configuration ................................................................................................................. 2-1
2.1.1

Stand-alone mode configuration and functions ......................................................................... 2-1

2.1.2

Mainframe Connection mode Configuration and Functions ...................................................... 2-5

2.1.3

Cross-Master Linkage Option ................................................................................................... 2-9

2.1.4

Remote Job Execute Function .................................................................................................2-11

2.2

Operation Flow ..........................................................................................................................2-13
2.2.1

Stand-alone mode(including Remote Job Execute Function) operation flow ...........................2-13

2.2.2

Mainframe Connection Option .................................................................................................2-19

2.2.3

Cross-Master Linkage Option ..................................................................................................2-27

2.2.4

Event Management ..................................................................................................................2-31

2.3

A-AUTO Monitor Process Structure ..........................................................................................2-34

2.4

AP-LINK Process Structure .......................................................................................................2-35

3

1-1

Master Files
3.1

3-1

Network Master .......................................................................................................................... 3-1
3.1.1

Purpose .................................................................................................................................... 3-1

3.1.2

Items to define .......................................................................................................................... 3-4

3.1.3

Valid Date and Expire Date Function .......................................................................................3-16

3.1.4

Job Branching Function ...........................................................................................................3-18

3.1.5

Parameter Management ..........................................................................................................3-25

3.1.6

Switch Job Execution User ID Function ...................................................................................3-28

3.2

Network Group Master ..............................................................................................................3-31
3.2.1

Purpose ...................................................................................................................................3-31-1-

3.2.2
3.3

Items to define ........................................................................................................................ 3-31
Data Wait Master ...................................................................................................................... 3-34

3.3.1

Purpose................................................................................................................................... 3-34

3.3.2

Items to define ........................................................................................................................ 3-34

3.3.3

Data Wait Management Function ............................................................................................ 3-37

3.4

Extended Job Master ................................................................................................................ 3-41
3.4.1

Purpose................................................................................................................................... 3-41

3.4.2

Items to define ........................................................................................................................ 3-41

3.4.3

Job ID Conversion Function .................................................................................................... 3-44

3.5

Annual Holiday Master.............................................................................................................. 3-46
3.5.1

Purpose................................................................................................................................... 3-46

3.5.2

Items to define ........................................................................................................................ 3-46

3.6

Holiday Master .......................................................................................................................... 3-48
3.6.1

Purpose................................................................................................................................... 3-48

3.6.2

Items to define ........................................................................................................................ 3-48

3.7

Schedule Master ....................................................................................................................... 3-52
3.7.1

Purpose................................................................................................................................... 3-52

3.7.2

Items to define ........................................................................................................................ 3-53

3.7.3

Process Pattern and Schedule Date ....................................................................................... 3-63

3.8

Network Schedule Master......................................................................................................... 3-65
3.8.1

Purpose................................................................................................................................... 3-65

3.8.2

Items to define ........................................................................................................................ 3-67

3.9

Daily Network Master................................................................................................................ 3-68
3.9.1

Purpose................................................................................................................................... 3-68

3.9.2

Items to define ........................................................................................................................ 3-69

3.10

Event Management Master....................................................................................................... 3-70
3.10.1

Purpose............................................................................................................................... 3-70

3.10.2Items to define .................................................................................................................... 3-71

-2-

3.11

4

Cross-Master Preceding Network Master ..................................................................................3-77
3.11.1

Purpose ...............................................................................................................................3-77

3.11.2Items to define .....................................................................................................................3-77

A-AUTO／Web Client
4.1

A-AUTO／Web Client ................................................................................................................. 4-1
4.1.1

Starting A-AUTO/Web Client .................................................................................................... 4-1

4.1.2

A-AUTO Main Window .............................................................................................................. 4-3

4.1.3

Stopping A-AUTO/Web Client................................................................................................... 4-5

4.1.4

A-AUTO/Web Client Page Layout ............................................................................................. 4-6

4.1.5

A-AUTO/Web Client Functions ................................................................................................4-15

4.1.6

When multiple users use A-AUTO/Web Client.........................................................................4-17

4.1.7

Copy-register Master ...............................................................................................................4-17

4.2

User Settings .............................................................................................................................4-19
4.2.1

Default Application Page Settings............................................................................................4-20

4.2.2

Display Settings of List ............................................................................................................4-20

4.2.3

Default Monitoring Setting at logging-in ...................................................................................4-20

4.3

5

4-1

Change Password .....................................................................................................................4-21

Application Definition
5.1

5-1

Network Master .......................................................................................................................... 5-1
5.1.1

Network ID List ......................................................................................................................... 5-1

5.1.2

Network Menu........................................................................................................................... 5-3

5.1.3

Create Network ......................................................................................................................... 5-4

5.1.4

Edit Network ............................................................................................................................5-30

5.1.5

Delete Network ........................................................................................................................5-34

5.1.6

Related Information Display .....................................................................................................5-36

5.1.7

Renumbering Job Number .......................................................................................................5-37

5.1.8

Show Script..............................................................................................................................5-38

5.1.9

Create Job ...............................................................................................................................5-40

-3-

5.2

Network Group Master.............................................................................................................. 5-46
5.2.1

Network Group List ................................................................................................................. 5-46

5.2.2

Create Network Group ............................................................................................................ 5-47

5.2.3

Edit Network Group ................................................................................................................. 5-49

5.2.4

Delete Network Group............................................................................................................. 5-52

5.3

Input Data Wait Master ............................................................................................................. 5-54
5.3.1

Input Data Wait Definition List ................................................................................................. 5-54

5.3.2

Create Data Wait .................................................................................................................... 5-55

5.3.3

Edit Data Wait ......................................................................................................................... 5-61

5.3.4

Delete Data Wait ..................................................................................................................... 5-63

5.4

Cross-Master Preceding Network Master ................................................................................. 5-65
5.4.1

Cross-Master Preceding Network Definition List ..................................................................... 5-65

5.4.2

Create Cross-Master Preceding Network................................................................................ 5-66

5.4.3

Edit Cross-Master Preceding Network .................................................................................... 5-68

5.4.4

Delete Cross-Master Preceding Network ................................................................................ 5-70

5.5

Extended Job Master ................................................................................................................ 5-72
5.5.1

Extended Job Definition List.................................................................................................... 5-72

5.5.2

Create Extended Job .............................................................................................................. 5-73

5.5.3

Edit Extended Job ................................................................................................................... 5-75

5.5.4

Delete Extended Job ............................................................................................................... 5-77

5.6

Annual Holiday Master.............................................................................................................. 5-79
5.6.1

Annual Holiday Definition List ................................................................................................. 5-79

5.6.2

Create Annual Holiday Information ......................................................................................... 5-80

5.6.3

Edit Annual Holiday Information .............................................................................................. 5-82

5.6.4

Delete Annual Holiday Information .......................................................................................... 5-84

5.6.5

Related Information Display .................................................................................................... 5-86

5.7

Holiday Master .......................................................................................................................... 5-87
5.7.1

Holiday Definition List.............................................................................................................. 5-87

5.7.2

Create Holiday Information ..................................................................................................... 5-88

-4-

5.7.3

Edit Holiday Information ...........................................................................................................5-91

5.7.4

Delete Holiday Information.......................................................................................................5-93

5.7.5

Related Information Display .....................................................................................................5-95

5.8

Schedule Master .......................................................................................................................5-96
5.8.1

Schedule Definition List ...........................................................................................................5-96

5.8.2

Create Schedule Information ...................................................................................................5-97

5.8.3

Edit Schedule Information ......................................................................................................5-121

5.8.4

Delete Schedule Information..................................................................................................5-123

5.9

Network Schedule Master .......................................................................................................5-125
5.9.1

Network Schedule List ...........................................................................................................5-127

5.9.2

Network Schedule Menu ........................................................................................................5-129

5.9.3

Create Network Schedule Information ...................................................................................5-130

5.9.4

Edit Network Schedule Information ........................................................................................5-134

5.9.5

Delete Network Schedule Information ...................................................................................5-136

5.9.6

About Exclusion Schedule Setting .........................................................................................5-138

5.9.7

Adjust Schedule .....................................................................................................................5-140

5.9.8

Network Schedule Modification Log .......................................................................................5-159

5.9.9

Display Period Setting ...........................................................................................................5-160

5.9.10

Network Information Temporary Change ...........................................................................5-163

5.9.11

Daily Network Schedule List ..............................................................................................5-167

5.9.12

Daily Network Menu ...........................................................................................................5-168

5.10

Mainframe Connection's Application Definition .......................................................................5-169
5.10.1

6

Application Content Definition ............................................................................................5-169

Operations
6.1

6-1

Auto Scheduling Function .......................................................................................................... 6-1
6.1.1

The Purpose of Auto Scheduling .............................................................................................. 6-1

6.1.2

autosche utility .......................................................................................................................... 6-3

6.1.3

Starting autosche utility ............................................................................................................. 6-6

6.1.4

remakesche utility ....................................................................................................................6-10-5-

6.1.5
6.2

Starting remakesche utility ...................................................................................................... 6-11
Finalized Schedule Function..................................................................................................... 6-12

6.2.1

The purpose of Finalized Schedule Function .......................................................................... 6-12

6.2.2

sfin utility ................................................................................................................................. 6-12

6.2.3

Starting sfin utility .................................................................................................................... 6-15

6.2.4

Record Format of Intermediate Files ....................................................................................... 6-24

6.3

Mainframe Connection Scheduling ........................................................................................... 6-26

6.4

Queuing .................................................................................................................................... 6-28
6.4.1

Network Queuing (Stand Alone Mode).................................................................................... 6-28

6.4.2

Network Queuing (Mainframe Connection Mode) ................................................................... 6-31

6.5

Monitoring ................................................................................................................................. 6-36
6.5.1

Networks in Wait State ............................................................................................................ 6-36

6.5.2

Networks being executed ........................................................................................................ 6-55

6.5.3

Terminated Networks .............................................................................................................. 6-57

6.5.4

Abnormally ended Network ..................................................................................................... 6-59

6.6

Rerunning Networks ................................................................................................................. 6-60
6.6.1

Rerun Normally Terminated Network ...................................................................................... 6-60

6.6.2

Rerun Abnormally Terminated Networks ................................................................................ 6-60

6.7

Executing Unscheduled Networks ............................................................................................ 6-62
6.7.1

Time Interval Execution Function ............................................................................................ 6-63

6.7.2

Rerun Recovery Function ....................................................................................................... 6-71

6.8

A-AUTO Monitor ....................................................................................................................... 6-77
6.8.1

7

Monitor Detail .......................................................................................................................... 6-77

Application Monitor
7.1

7.2

7-1

Monitor Condition ....................................................................................................................... 7-1
7.1.1

Monitor Condition Setting .......................................................................................................... 7-1

7.1.2

Monitor Condition Item .............................................................................................................. 7-2
Event Monitor ............................................................................................................................. 7-5-6-

7.2.1Work Monitor List Page ............................................................................................................ 7-5

7.2.2

Work Monitor Detail List Dialog................................................................................................. 7-7

7.2.3

Event Detail Windows ..............................................................................................................7-11

7.2.4

Action Detail Windows .............................................................................................................7-13

7.2.5

Change the Monitor Condition of Running "Work" ...................................................................7-15

7.2.6

Update the Status of Work (Valid/Invalid) ................................................................................7-17

7.2.7

Delete Completion Information ................................................................................................7-18

7.3

Application Monitor, Application Monitor Flowchart, Application Monitor Time Chart ................7-19
7.3.1

Application Monitor ..................................................................................................................7-20

7.3.2

Application Monitor Flowchart ..................................................................................................7-22

7.3.3

Application Monitor Time Chart................................................................................................7-27

7.3.4

Network Monitor Menu .............................................................................................................7-28

7.3.5

Network Monitoring Search......................................................................................................7-30

7.4

Monitor Detail Information .........................................................................................................7-32
7.4.1

Job Log Display .......................................................................................................................7-35

7.4.2

Show Script..............................................................................................................................7-36

7.5

File Transfer ..............................................................................................................................7-37

7.6Time Simulation.........................................................................................................................7-40

7.7Alert ...........................................................................................................................................7-45
7.7.1

Alert Setting .............................................................................................................................7-48

7.7.2

Alert Log ..................................................................................................................................7-48

7.8

8

Monitor Commands ...................................................................................................................7-49
7.8.1

List of commands.....................................................................................................................7-49

7.8.2

Items to be specified for Issuing Commands ...........................................................................7-50

7.8.3

Confirm Message Display ........................................................................................................7-58

7.8.4

Command Log .........................................................................................................................7-58

Functions
8.1

8-1

Job Log Management Function .................................................................................................. 8-1

-7-

8.2

Batch Maintenance Function ...................................................................................................... 8-4

8.3

Resource Management .............................................................................................................. 8-7

8.4

Exclusive Control Function ......................................................................................................... 8-9

8.5

Event Timer Function ............................................................................................................... 8-11

8.6

Message Pop-up Function ........................................................................................................ 8-15

8.7

Adjusting Alert Pop-up .............................................................................................................. 8-17

8.8Child Job Cancellation Function ............................................................................................... 8-18

8.9

Date Transfer Function ............................................................................................................. 8-20

8.10

Test Run Function .................................................................................................................... 8-22

8.11

Previous Month Schedule Function .......................................................................................... 8-24

9System Management
9.1

9-1

Management of Agent Information ............................................................................................. 9-1
9.1.1

Monitoring A-AUTO Monitor ID Settings ................................................................................... 9-4

9.1.2

Setting automated issuing menu command .............................................................................. 9-7

9.1.3

Setting of A-AUTO/Event ........................................................................................................ 9-10

9.2

Management of Server Information .......................................................................................... 9-11
9.2.1

Data Management .................................................................................................................. 9-12

9.2.2

Log management .................................................................................................................... 9-16

9.2.3

File Transfer ............................................................................................................................ 9-22

9.2.4

Simulation ............................................................................................................................... 9-23

9.2.5

Replicate ................................................................................................................................. 9-24

9.3

Monitor Information Management ............................................................................................. 9-25
9.3.1

Settings of Monitor .................................................................................................................. 9-25

9.3.2

Job Library Detail .................................................................................................................... 9-27

9.3.3

System Qualifier Definition ...................................................................................................... 9-30

9.3.4

System Group Qualifier Definition ........................................................................................... 9-30

9.3.5

Resource Definition ................................................................................................................. 9-31

9.3.6

Plug-in Definition ..................................................................................................................... 9-33

-8-

9.4

In the Case of Use Server Function from Console ....................................................................9-35

10 Cross-Master Linkage

10-1

10.1

Summary of Cross-Master Linkage ...........................................................................................10-1

10.2

System Configuration ................................................................................................................10-2
10.2.1

Operation Flow ....................................................................................................................10-3

10.2.2Master Maintenance ............................................................................................................10-4

10.2.3

Scheduling ...........................................................................................................................10-6

10.2.4

Cross-Master Linkage Control (monitoring) .........................................................................10-7

10.2.5

Operation ...........................................................................................................................10-16

10.2.6

Monitor Setting ...................................................................................................................10-16

10.2.7

Application Execution Monitor ............................................................................................10-17

10.3

Abnormally Processing ............................................................................................................10-18
10.3.1

Cross-Master Inconsistency...............................................................................................10-18

10.3.2AML ID Inconsistency ........................................................................................................10-19

10.3.3

No Network Master Record................................................................................................10-19

10.3.4

No Network Check File Record ..........................................................................................10-19

10.3.5In the Case that failed to Update NCONNECT File (Mainframe Only) ...............................10-19

10.3.6In the Case that the Losing of Notice in UDP/IP Occurs ....................................................10-20

10.3.7In the Case that the Writing to SYSREC is failed (Mainframe Only) ..................................10-21

10.3.8In the Case that A-AUTO Monitor Was Stopped when the Writing to SYSREC is failed (Mainframe

Only)

10-21

10.3.9There is no A-AUTO/Connect Component Definition that Should be connected Communications

Setting

10-21

10.3.10In the Case that Notice Request Storage Table Number is Overflow ................................10-21

10.3.11

The Processing of A-AUTO Monitor when A-AUTO/Connect Component Does Not Run (Mainframe

Only)

10-21

10.4

The Notes of Using Cross-Master Function ............................................................................10-22
10.4.1The Notes of Platform Common ........................................................................................10-22

10.4.2The Notes in Mainframe.....................................................................................................10-24-9-10.4.3

The Notes in UNIX/Windows ............................................................................................. 10-24

11 Event Management

11-1

11.1

Overview of Event Management ............................................................................................... 11-1

11.2

System Configuration ............................................................................................................... 11-2
11.2.1

11.3

Operation flow ..................................................................................................................... 11-3
Master Maintenance ................................................................................................................. 11-4

11.3.1

Defining Event master ......................................................................................................... 11-4

11.3.2

Registering Works ............................................................................................................... 11-5

11.4

Utility ......................................................................................................................................... 11-9
11.4.1

Transferring Event occurrence information ....................................................................... 11-10

11.4.2

Generating an Event utility ................................................................................................ 11-12

11.4.3

Monitoring log files utility ................................................................................................... 11-15

11.4.4

Sending an mail utility ....................................................................................................... 11-19

12 User Interface

12-1

12.1

Network End Exit ...................................................................................................................... 12-1

12.2

Network Start Exit ..................................................................................................................... 12-8

13 Remote Job Execute Function
13.1

13-1

Settings for Job Execution ........................................................................................................ 13-1
13.1.1

Setting System Qualifier ...................................................................................................... 13-1

13.1.2

Setting System Parameter .................................................................................................. 13-4

13.2

Starting and Stopping Remote System ..................................................................................... 13-5
13.2.1

Starting Remote Job Execute Function(UNIX) .................................................................... 13-5

13.2.2Ending Remote Job Execute Function(UNIX) ..................................................................... 13-5

13.2.3

Starting Remote Job Execute Function(Windows) .............................................................. 13-6

13.2.4Ending Remote Job Execute Function (Windows) .............................................................. 13-8

13.3

Job End Code ........................................................................................................................... 13-8

13.4

System Log............................................................................................................................... 13-9

- 10 -

13.5

Remote Job Cancellation at the Time of an A-AUTO Monitor Problem ...................................13-10

13.6

A-REMOTE Job Outcome Management at the Time of Communication Unusual Detection ..13-12

13.7

Remote Job Recovery Function ..............................................................................................13-16

13.8

Load Balancing Function .........................................................................................................13-21
13.8.1

System Group Qualifier Definition ......................................................................................13-22

13.8.2Checking the Status and Controlling Load Balance ...........................................................13-25

13.9

Job Log Management Function ...............................................................................................13-26

13.10

KeepAlive Function .................................................................................................................13-27

13.11

Date Pass function ..................................................................................................................13-33

13.12

Sample Job .............................................................................................................................13-35

13.12.1

Remote Job Execute Function (UNIX) examples ...............................................................13-35

13.12.2

Sample Job for A-Remote for Windows .............................................................................13-35

13.13

Example of System Configuration ...........................................................................................13-36

14 Remote Job Execute Function (System i)
14.1

Settings for Job Execution (A-AUTO Monitor) ...........................................................................14-1
14.1.1

14.2

Setting System Qualifier ......................................................................................................14-1
Settings for Starting Job (System i) ...........................................................................................14-4

14.2.1

Initial Menu Screen ..............................................................................................................14-4

14.2.2

Setting System Parameter ...................................................................................................14-5

14.2.3

Setting Job Parameter .......................................................................................................14-10

14.3

Remote System Start and End ................................................................................................14-15
14.3.1

Remote Job Execute Function (System i) Start .................................................................14-15

14.3.2

Remote Job Execute Function (System i) End ..................................................................14-17

14.4

System Log .............................................................................................................................14-19
14.4.1

Remote Job Execute Function (System i) System Log ......................................................14-19

14.5

End Code ................................................................................................................................14-19

14.6

Max return code ......................................................................................................................14-20- 11 -

14-1

14.7

Cancel (Return Code 4) Job End ............................................................................................ 14-20

14.8

Message Resend Message Function ..................................................................................... 14-21

14.9

Utility ....................................................................................................................................... 14-22

14.10

Sample Job............................................................................................................................. 14-23

14.10.1

Job Parameter .................................................................................................................. 14-23

14.10.2

CL Program ....................................................................................................................... 14-23

14.11

Example of System Configuration .......................................................................................... 14-24

15 Limitations

15-1

15.1

Precautions and Limitations to execution of Auto Scheduling .................................................. 15-1

15.2

Precautions and Limitations to execution of sfin utility .............................................................. 15-5

15.3

Precautions and Limitations to Exclusion Schedule ................................................................. 15-8

15.4

Precautions and Limitations of A-AUTO/Web client and AP server .......................................... 15-9

GlossaryiAbout Glossary ...................................................................................................................................................i

Master Information Input Item List

- 12 -

1

- 13 -

Overview of A-AUTO for UNIX / Windows System

Overview of A-AUTO for UNIX/Windows

1 The outline of A-AUTO for UNIX/Windows System
1.1 What is A-AUTO for UNIX/A-AUTO for Windows?
A-AUTO for UNIX/Windows is a computer operations management tool that supports automatedapplication scheduling and operations on UNIX/Windows.
Developed in Japan for mainframe computers, A-AUTO was designed to enhance efficiency in daily
operations of batch processing in mainframe and to improve reliability of computer operations.
A-AUTO for UNIX/Windows is a stand-alone system that operates in UNIX/Windows environment. A-AUTO
for UNIX/Windows enables users to implement a distributed environment with the same operations
management and the system administration as those in A-AUTO for Mainframe. A-AUTO for
UNIX/Windows supports and integrates its system operations with other A-AUTO products. Integrated
system operations* throughout mainframe, Windows and Unix environments enable high-quality system
operation.
*

Integrated system operation with A-AUTO for mainframe is offered as an option.

The A-AUTO family comprises the following optional products; A-AUTO/X8, A-AUTO for OS400, A-AUTO
for Windows®, A-AUTO for Linux, an A-AUTO for UNIX remote license, A-AUTO for Windows remotelicense, and A-AUTO for OS400 remote license.

TargetApplications that A-AUTO manages or processes are batch jobs to be processed in computer system.
These applications include updating databases, creating reports, etc. A minimum unit of an application
comprises a shell script in UNIX environment, or a batch file, exe, or command in the Windows
environment. In A-AUTO, a collection of Jobs is called a Network.

1-1

1. The outline of A-AUTO for UNIX/Windows System■Operations management using A-AUTO for UNIX/Windows
A-AUTO for UNIX/Windows offers the following computer operations management facilities.
①

Schedule Management
A-AUTO for UNIX/Windows automatically generates monthly, weekly, and daily execution
schedules of Networks based on information stored in the Master Files. All Networks are
executed under its control according to these schedules. In addition, it facilitates automatic
updates of the schedules and modification of the daily schedules.

②

Control of application processing
All Networks are automatically executed under its control and the processing of these Networks
is monitored to ensure orderly execution; i.e., the preceding Networks are checked to be
successfully completed before the succeeding Network is executed.

③

Data Wait management
Data Wait Control facility enables the users to automatically execute Networks when specificdata is generated or a designated event occurs outside of A-AUTO for UNIX/Windows.

④

Event management
By using Event management facility, A-AUTO for UNIX/Windows can detect occurrence of adesignated event as a trigger to execute Job, issue commands, or activate applications.

⑤

Log management
For each Network that has been executed, it records the Network information and completion
status for audit trail purpose.

⑥

Master management
All the information required for automated computer processing, such as the operational andschedule information regarding Networks, are stored into master files. Therefore mastermanagement facility allows centralized management of information regarding automatedapplications processing.

1-2

Overview of A-AUTO for UNIX/Windows■ Monitoring, Control, and Management of A-AUTO
Monitoring, control, and management facilities of A-AUTO for UNIX/Windows are enabled by using thefollowing subsystems.
①

A-AUTO/Agent (Agent)
Using its proprietary communication system, Agent transmits information regarding applications(Network/Job) running under A-AUTO in UNIX, Linux, or Windows environment to the Server.

②

A-AUTO/AP Server (Server)
All the data transmitted by A-AUTO/Agent is managed by A-AUTO/AP Server. Because data istransmitted at regular intervals, the operator can know the latest condition at all times.

③

A-AUTO/Event Agent, A-AUTO/Event Server (A-AUTO/Event Agent , A-AUTO/Event Server )A-AUTO/Event Agent monitors the occurrence of designated events and executes the specified
actions when the events occurred.
A-AUTO/Event Agent transmits information regarding detected events and executed actions to
A-AUTO/Event Server and A-AUTO/Event Server manages this information.
Data managed by A-AUTO/Event Server can be browsed from A-AUTO/Web client, which is
explained below.

④

A-AUTO/Web Server, A-AUTO/Web client (Web Server, Web Client).
The Web Server and Web client provide a facility that enables users to display graphical userinterface of A-AUTO via Web.
Information that the Server manages, such as Master files, applications (Network/Job)
information, and monitoring information of A-AUTO Monitor are provided.
For monitoring information, the following display styles are provided. Operators can choose
which display style to use according to the requirements of monitoring environment.
 List format
 Flowchart format
 Time chart format
It provides a facility to display an alert when an application (Network/Job) ends abnormally. In
addition, the operator can issue commands such as Monitor commands to A-AUTO Monitor.

1-3

1. The outline of A-AUTO for UNIX/Windows System

1.2 Benefits from the Implementation of A-AUTO for UNIX/Windows
The use of A-AUTO for UNIX/Windows has the following benefits.
①

Support unattended computer operation
For application operations, A-AUTO for UNIX/Windows monitors and controls the processing of
Networks.
The implementation of A-AUTO for UNIX/Windows allows the users to automate application
processing on Windows and UNIX environments and therefore enables automated computer
operations.

②

Improve reliability of application processing and reduce workload of operators
A-AUTO for UNIX/Windows provides facilities such as automatic scheduling and controlling of
Network execution, which have to be manually handled without A-AUTO. The implementation of
A-AUTO for UNIX/Windows will substantially reduce workload as well as human errors and therefore,
it will improve reliability of the application operations.

③

Reduce operating cost and personnel expenses
As a result of the benefits from A-AUTO for UNIX/Windows mentioned above, operating cost will besignificantly reduced.
Users of A-AUTO for UNIX/Windows need not have knowledge about Windows operation. As long as
the user has knowledge about A-AUTO, he/she can operate A-AUTO on either mainframe or
Windows. In the case of distributed environments, system administrators need not be assigned
individually for mainframe and Windows. Therefore, training of system administrators is minimized.

④

Provide accesses to applications on any machine in the system
A-AUTO/Web client enables the user to monitor and control applications running on mainframe
environment, UNIX environment or any other environments in the system from their PC.

⑤

User-friendly interface
Thanks to GUI interface, A-AUTO Web/client provides user with intuitive interface for application
progress and framework.

Also, the features of Windows enable even the end-user to use A-AUTO

for UNIX/Windows easily. Information to display on A-AUTO/Web client can be customized for eachuser according to requirements of the operations.
⑥

Supports smooth troubleshooting
Information regarding abnormality is getting attention of many system administrators.
Delays or troubles of applications can lead to operation abnormality if wrong decision is made whilehandling the troubles. If a delay or an abnormality occurs during execution of application, A-AUTO for
UNIX/Windows detects and notifies the operator immediately, leading to quick, precise decision
making.

1-4

Overview of A-AUTO for UNIX/Windows⑦

Prevent operational mistakes
Although the applications processing is automated by installing A-AUTO system, issuance ofcommands to A-AUTO Monitor is still dependent on the operational personnel. Manual operation
leads to higher risk for operational mistakes. Education on operating A-AUTO is also necessary to
avoid such risk. A-AUTO for UNIX/Windows is designed to provide interactive GUI command mode
when issuing Monitor Commands. As a result, the operator can issue commands to A-AUTO Monitor
without regard to input format of Monitor Commands.

(1) About the Benefits from the implementation of Mainframe Connection Option①

Executing applications without delay
With A-AUTO Mainframe Connection, you can create preceding relationship between Networks ofUNIX/Windows and Mainframe.

Applications across mainframe, UNIX and Windows environments

can be executed without any delay; time usually required in checking for completion of dependent
Networks in different environments.
②

Centralized control in Mainframe
Because all registrations for Masters and schedules will be operated solely in Mainframe, you canperform the centralized control of Masters and schedules information.

③

Centralized monitoring in Mainframe
Monitoring of Networks that are executed in UNIX, Windows and/or Mainframe are centralized inmainframe and this reduces the workload of operation.

④

Improve service for end-user
You can now support automated scheduling and monitoring of applications in the distributed
UNIX/Windows systems that are used by end-user department. This will improve service for end-user.

⑤

Reduce operation mistakes through integrated schedules and integrated operations
Applications in A-AUTO for UNIX/Windows are registered, scheduled and monitored by A-AUTO for
Mainframe, so there is no change in the way of scheduling and operations.
This reduces operation mistakes such as error in execution of schedules and error in issuingcommands.

(2) About the Benefits from the implementation of Cross-Master Linkage Option①

Independence and linkage of applications
With Cross-Master Linkage option, you are able to link a Network in one platform with one or more
Networks in another platform while scheduling and executing these Networks in their own platforms.
This enables the operation management to design the schedules and the execution of the logicallylinked Networks separately and independently for different platforms.
Because these linked Networks are independent, they can be modified individually and independentlyof each other.

1-5

1. The outline of A-AUTO for UNIX/Windows System②

Flexible and progressive migration of applications
The transition of the application systems are progressing towards the trend of open systems but thesystems cannot be migrated all at once. As applications are progressively migrated to A-AUTO
system in their respective platforms, Cross-Master Linkage can be updated to reflect the link between
current Networks and the new Networks of the migrated applications.

1-6

2. System Configuration and Process Flow

2 System Configuration and Process Flow
2.1

System Configuration

2.1.1 Stand-alone mode configuration and functions
A-AUTO for UNIX/Windows is configured as follows when it is used in stand-alone mode.

PC

Web Client

A-AUTO

A-AUTO Server

Web Server

A-AUTO/Event

A-AUTO/Event

A-AUTO

ServerAgent

MONITORAP Server

A-AUTO
Master Files

RDBMS
Agent

UNIX/Windows

Windows

Support Utilities* A-AUTO/Event Server, A-AUTO/Web Server, and A-AUTO/AP Server may be operated only on Windows.
* A-AUTO/Event Server, A-AUTO/Web Server, and A-AUTO/AP Server are hereafter referred to as A-AUTO
Server.

2-1

2. System Configuration and Process Flow

A-AUTO for UNIX/Windows consists of the following nine components(1) A-AUTO/Web Client(Web Client)

Web Client is the GUI of A-AUTO for Unix/Windows that runs on web browser. A collection of application
Jobs is called a Network in A-AUTO for UNIX/Windows. A-AUTO for UNIX/Windows has 11 master files tomanage information on Network processes and schedules.
Network MasterNetwork Group Master

Annual Holiday Master

Holiday Master

Schedule MasterNetwork Schedule Master

Daily Network MasterEvent Management Master

Cross-Master Preceding Network Master

Data Wait MasterExtended Job Master

Master files are located in the environment where A-AUTO Monitor is running. A-AUTO Client allows users
to register, update, delete, and search the information stored in master files.
To use master maintenance facility, AP-LINK must be activated and must be accessible by A-AUTO Client
through TCP/IP protocol. Communication settings have to be defined in advance.
Execution statuses of Networks may be monitored. Monitoring conditions may be set on Web Client to view
and monitor execution statuses of only specific Networks available from the Network information centrally
controlled by A-AUTO/AP Server. Also, commands to A-AUTO Monitor may be sent from Web Client.

2-2

2. System Configuration and Process Flow

(2) A-AUTO Monitor
A-AUTO Monitor automatically executes scheduled Networks according to the execution conditions andthe preceding relationships defined for the Networks. When these defined execution and preceding
relationship conditions are met, A-AUTO Monitor dynamically allocates Networks to available NP partitions.
If any free JP partition exists, the job(s) of the Network shall be executed immediately. As these operations
are performed automatically by A-AUTO Monitor, it enables users to save time and reduce the number of
mistakes in operation.
Automatic Job management by A-AUTO Monitor reduces the burden for operators and increases theefficiency of computer usage. NP partitions and JP partitions are definitions that control multi processing of
Networks and Jobs under A-AUTO.

(3) AP-LINK
AP-LINK controls the communication among the components of A-AUTO Server and the communication
between A-AUTO Server and A-AUTO Monitor. Basically, the operation for AP-LINK is simple, which isstarting and stopping of AP-LINK. AP-LINK must be activated for A-AUTO/Web Client to maintain Master
files and monitor status of Network execution. Also, communication settings have to be defined in advance.

(4) A-AUTO/Event
A-AUTO/Event Server performs the following main functions of A-AUTO/Event system.
Manages the editing of Event data in the database by Web Client.

Manages information of detected Event or executed Action in the database.

Sends instructions for Event Monitoring and Actions to A-AUTO/Event Agent.

Only one A-AUTO/Event server may be installed in the system. The information of A-AUTO/Event Agent iscentrally controlled by Server. A-AUTO/Event is provided as a service.

(5) A-AUTO/Event Agent
A-AUTO/Event Agent receives requests from A-AUTO/Event Server. It monitors the events and executes
the actions. It notifies the occurrence of detected events or the execution of actions information to
A-AUTO/Event Server. A-AUTO/Event Agent that runs on Windows is provided as a service.

(6) A-AUTO/Agent
Agent monitors the statuses of Networks executed on UNIX/Linux/Windows, and transmits the Network
execution information to the A-AUTO/AP Server at regular intervals. Delays of Networks are also
monitored by Delay Monitor task of Agent. Also, Agent receives A-AUTO commands issued from Web
Client via A-AUTO/AP Server and processes the commands. Agent is a resident in the system.

2-3

2. System Configuration and Process Flow

(7) A-AUTO/AP Server (Server)
The Network information transmitted from Agent to the Server is stored and maintained in Server(Windows ® / Linux). Using this information, Network execution may be simulated. Information exchanges
between Agent and Web Client are processed via Server. An A-AUTO/AP Server may be connected tomultiple Agents and Web Clients.

(8) A-AUTO/Web Server (Web Server)
Web Server receives requests from Web Client, initiates the appropriate processing, and sends the result
to Web Client. It may send requests to Server to get or update information from or to the database.
Information exchanges between AP Server and Web Client are processed via Web Server.

(9) Support utilities
The following utilities are available.


Network Delay Monitor utility :asvform utility

Utility for monitoring delays in Network execution.
: Utility for initializing files on UNIX.

2-4

2. System Configuration and Process Flow

2.1.2 Mainframe Connection mode Configuration and Functions
A-AUTO for UNIX/Windows is configured as follows when it is used with Mainframe Connection Option.

UNIX/Windows

Mainframe

A-AUTO for UNIX/Windows

A-AUTO

A-LOCAL

A- AUTO Monitor

armt

A-AUTO
Agent

PC

Windows
A-AUTO/AP Server

RDBMS

A-AUTO/Web
ClientWeb Server* For V610 or later version, armt runs under AP-LINK.

2-5

2. System Configuration and Process Flow

One mainframe can operate with one or more UNIX/Windows systems.
The maximum number of UNIX/Windows systems that can be connected with one mainframe is 16.
`
UNIX/Windows

Execution
Mainframe

UNIX/Windows

Schedule network
Request to execute
network
UNIX/Windows

You need to install the necessary components of A-AUTO for UNIX/Windows system on every
UNIX/Windows system of the above illustration.

2-6

2. System Configuration and Process Flow

Mainframe Connection option consists of the following nine components.
(1) A-AUTO Monitor
A-AUTO Monitor automatically executes scheduled Networks according to the execution conditions andpreceding relationships defined for the Networks. When these defined execution and preceding
relationship conditions are met, A-AUTO Monitor dynamically allocates Networks to available NP partitions.
If any free JP partition exists, the job(s) of the Network shall be executed immediately. As these operations
are performed automatically by A-AUTO Monitor, it enables users to save time and reduce the number of
mistakes in operation.
With this option, you can define preceding relationships between Networks in mainframe and Networks in
UNIX/Windows. For users who are already using A-AUTO on mainframe environment, they can centrally
register, schedule, control and monitor Networks using A-AUTO on mainframe. Therefore, they do notneed to create new procedures for UNIX/Windows environments.
The administrators of mainframe can operate it without regard to OS of the computers.
In this way, A-AUTO Monitor can reduce the workload of the operator by managing jobs of UNIX /Windows automatically, and use computers more effectively.

(2) AP-LINK (armt)
Armt is a bridge which connect A-AUTO Monitor that is running on UNIX/Windows to A-LOCAL that is
running on mainframe. The following are data exchanged between A-AUTO Monitor and A-LOCAL.
■ A-AUTO Monitor to A-LOCAL
・Notification of end of Networks
・Query to request for information on ended status of Network on mainframe・Response to its commands from A-LOCAL■ A-LOCAL to A-AUTO Monitor
・Commands to A-AUTO Monitor
・Data of Master during queuing process
・Information on ended status of Network on mainframe(3) A-LOCAL
A-LOCAL runs on the mainframe where A-AUTO for Mainframe resides.It manages the preceding andsucceeding relationships of Networks that are to be executed on a mainframe and on UNIX/Windows.
In addition, commands to be issued to an A-AUTO Monitor are transmitted via A-LOCAL.

(4) A-AUTO/Agent (Agent)
Agent monitors the statuses of Networks executed on mainframe, and transmits the Network execution
information to the A-AUTO/AP Server at regular intervals.
Also, Agent receives A-AUTO commands issued from Web Client via A-AUTO/AP Server and processes
the commands. Agent is a resident in the system.
2-7

2. System Configuration and Process Flow

An Agent can monitor multiple A-AUTO.

(5) A-AUTO/AP Server (Server)
The Network information transmitted from Agent to the Server is stored, maintained and centrally
controlled in Server (Windows ® / Linux). Using this information, Network execution may be simulated.
Information exchanges between Agent and Web Client are processed via Server. An A-AUTO/AP Server
may be connected to multiple Agents and Web Clients.

(6) A-AUTO/Web Client (Web Client)
Execution statuses of Networks may be monitored. Monitoring conditions may be set on Web Client to view
and monitor execution statuses of only specific Networks available from the Network information centrally
controlled by A-AUTO/AP Server. Also, commands to A-AUTO Monitor may be sent from Web Client.

(7) A-AUTO/Web Server (Web Server)
Web Server receives requests from Web Client, initiates the appropriate processing, and sends the result
to Web Client. It may send requests to Server to get or update information from or to the database.
Information exchanges between AP Server and Web Client are processed via Web Server.

(8) A-AUTO on mainframe
To monitor execution statuses of Networks of A-AUTO and collect information about Networks.

(9) Support utilities
The following utility is available.
 Delay Monitor utility: Utility for monitoring delays in Network execution.

■ The relationship with Cross-master Option
You cannot use Mainframe Connection Option with Cross-master Linkage Option at the same time.
If you use them at the same time, may cause unpredictable results.

2-8

2. System Configuration and Process Flow

2.1.3

Cross-Master Linkage Option
A-AUTO for UNIX/Windows is configured as follows when it is used with Cross-master Linkage Option.

UNIX/Windows/

UNIX/Windows/

mainframe

mainframe

A-AUTO or

A-AUTO or

A-AUTO for UNIX/Windows

A-AUTO for UNIX/Windows

A-AUTO Monitor

A-AUTO/

A-AUTO/

Connect

Connect

A-AUTO Monitor

scheduleschedule

systemsystemCross-Master Linkage Option consists of the following two components.

2-9

2. System Configuration and Process Flow

(1) A-AUTO Monitor
A-AUTO Monitor automatically executes scheduled Networks according to the execution conditions andpreceding relationships defined for the Networks.
Other basic functions and roles are the same as A-AUTO Monitor described in "2.1.1 Stand-alone mode
configuration and functions".
The additional function of A-AUTO Monitor with Cross-master Linkage Option is to communicate with
A-AUTO/Connect that will be described later.

(2) A-AUTO/Connect

If a Network is dependent on other Network that belongs to another A-AUTO system i.e. there is
Cross-master preceding Network, A-AUTO/Connect will manage the ended information of this preceding
Network and notify the respective A-AUTO Monitor. This enables this Network to be released automaticallyfor execution. Networks with Cross-master preceding Network(s) can therefore be treated in the samemanner as any other scheduled Network.
A-AUTO/Connect must reside in the same server where A-AUTO Monitor resides.
For mainframe environment where multiple A-AUTOs operate in multi-CPU mode, A-AUTO/Connect isrequired in only one of the A-AUTOs.
(A-AUTO/Connect should be installed in the A-AUTO where you will be issuing Start command, Queuingcommand, Reset command (PNET).)■ The relationship with mainframe connection version
You cannot use Cross-master Linkage Option with Mainframe Connection Option at the same time.
If you use them at the same time, may cause unpredictable results.

2-10

2. System Configuration and Process Flow

2.1.4 Remote Job Execute Function
This function is an optional product.
Remote Job Execute function enables:Centralized management of Master files and schedule information for applications on multiple
platforms.



The control of application processing on multiple platforms from one A-AUTO Monitor.

UNIX/Windows

A-AUTO for UNIX/Windows

A-AUTO Monitor

A-AUTO/Event

AP-LINK

MCP

Agent
NCP

NJP

NEP

TMR

LBP

jslinkrj

A-AUTO/Event
execscrServerexecscr

execscrPC

UNIX

A-AUTO for Windows
Remote Licences

A-Remote for UNIX
Remote Licences

AUTO/Event
Agent

AUTO/Event
Agent

execscr

AS400

A-Remote for OS400
Remote Licences* A-AUTO/Event Server may be operated only on Windows.

2-11

2. System Configuration and Process Flow

Remote Job Execute function requires A-AUTO for UNIX/Windows stand-alone mode and one or more of the following
components depending on customer’s environment.

(1) A-AUTO for UNIX Remote License
A-Remote for UNIX is for UNIX environments which are connected to A-AUTO for UNIX/Windows by
TCP/IP. A-AUTO for UNIX/Windows automatically schedules and dispatches jobs for execution in theUNIX servers. To support this, A-Remote must be installed on UNIX environment.

(2) A- AUTO for Windows Remote License
A-Remote for Windows is for Windows PC environments which are connected to A-AUTO for
UNIX/Windows by TCP/IP. A-AUTO for UNIX/Windows automatically schedules and dispatches jobs for
execution in the Windows servers. To support this, A-Remote for windows must be installed on Windows
PC environment.

(3) A- AUTO for OS400 Remote License
A-Remote for OS/400 is for OS/400 environments which are connected to A-AUTO for UNIX/Windows by
TCP/IP. A-AUTO for UNIX/Windows automatically schedules and dispatches jobs for execution in the
AS400 servers. To support this, A-Remote for OS400 must be installed on OS400 environment. When thisfunction is used, an additional component jslinkrj is added to stand-alone mode AP-LINK.

(4) A-AUTO/Event Agent
A-AUTO/Event Agent receives requests from A-AUTO/Event Server. It monitors the events and executes
the actions. It also notifies the occurrence of specified events or execution of actions to A-AUTO/Event
Server. A-AUTO/Event Agent that runs on Windows is provided as a service.

2-12

2. System Configuration and Process Flow

2.2

Operation Flow

2.2.1 Stand-alone mode(including Remote Job Execute Function) operation flow
Performing the procedures described below will enable A-AUTO for UNIX/Windows to automate
application processing.

Execute Network,
Monitoring

Define Network

Calendar

Schedule Network(1) Defining Network
A collection of application Jobs is called a Network. First, application Jobs are defined as Networks andstored into the Network Master using the Web Client. In addition to Job configurations in a Network,
Network and Job attributes such as wait conditions and dependencies are also defined for the Network.

(2) Scheduling Network
Next, Networks are scheduled. A facility for scheduling Networks in A-AUTO for UNIX/Windows is Auto
Scheduling facility. It enables users to automatically schedule Networks for a year by associating Networks
with Schedule Patterns. After Auto Scheduling, the schedules of Networks can be easily modified, i.e.
changed, added, and deleted, using Network Schedule window of Web Client. Scheduling of Networks is
performed as follows:①

Defining Holiday Information
One or more calendars can be defined. Holiday information for each calendar is defined into Holiday
Master using Holiday Master window of Web Client.

2-13

2. System Configuration and Process Flow②

Defining Schedule Pattern
Schedule patterns are defined into Schedule Master using “Schedule Definition List” of Web Client. A
calendar defined in ① is linked to each Schedule pattern.

③

Scheduling Network
By defining the association between a Network registered in Network Master and a schedule pattern
defined in Schedule Master using Web Client’s Network Schedule window, the schedule of the
Network for a year is automatically generated. This schedule is called Network Schedule. After thegeneration of the Network Schedule, the Web Client’s Network Schedule window allows users tomodify the generated Network Schedule, i.e. add, move, delete and/or change the attributes of the
Network Schedule. For Networks with irregular schedule, those defined without anassociatedschedule pattern, the users can specify specific dates for scheduling.

④

Auto Updating Network Schedule
Network Schedule for a Network is generated for a year when the Network is associated with one ormore Schedule Patterns. A utility program is to be executed to add further schedule information.This
process is called Auto Scheduling. By periodically running Auto Scheduling, the schedule of
Networks will be updated and kept current for one whole year.

⑤

Finalizing daily schedule
Finalized Daily Schedule, sfin utility, extracts Networks scheduled for the day for execution. This
process can be automated in advance so that A-AUTO Monitorwill automatically execute scheduled
Networks.
Monitoring information is created in this procedure.

(3) Executing Network
To begin execution of Networks under A-AUTO for UNIX/Windows, issue a command to transfer thescheduled Network information created by sfin utility to A-AUTO Monitor’s Network Queue. This process iscalled Queuing. Networks in the Network Queue will be orderly executed on UNIX/Windows once the
Networks become executable.
The facility is called Monitoring.
When A-Remote is used, A-AUTO Monitor determines on which computer a Network should be executed,
and requests the appropriate A-Remote to execute it.

2-14

2. System Configuration and Process Flow

■ Example

Application A is to produce a sales report based on the figures entered into the database by sales
persons on the previous day.
This application is used by Sales Department at 10:00 am every morning.
Application B is to produce a weekly sales report based on the sales reports produced by daily
execution of application A.
This application is used by the Accounting Department every Friday.
Application B is also used on the 20th of every month in order to produce a monthly sales report.
The Accounting Department and the Sales Department refer to different calendars that have different
holidays.
The Sales Department is closed every Sunday, while the Accounting Department is closed every
Saturday and Sunday.
Sales
Accounting
CalendarApplication A
CalendarApplication B

2-15

2. System Configuration and Process Flow

■ Operation Flow
Using example on previous page, the required operation flow is as follows.

Network Master

Network

Window

Window

Schedule

NETA：Application

Schedule Master

Holiday Master

Window

Window

SCHED：Daily

HOL01：Sales Dept.
calendar
SundaySCHEW：Every Friday
NETB：Application

HOL02：Acct'g Dept.
calendar

SCHEM：Every 20th
Saturday①

Defining Network④

Scheduling Network③

Register Application A andDefining Schedule②

Pattern

Register holidays of Sales

Defining Holiday

Application B into Network

Register Schedule Patterns

department andMaster as NETA and NETB.

into Schedule Master.

Accounting department

Link Schedule Patterns to
Networks
NETA is scheduled every

Link Holiday information to

day and NETB is

Schedule Patterns.

scheduled on every Friday
and the 20th of eachmonth. Networks arescheduled for one year.

⑤

Auto scheduling
When Auto scheduling utility (autosche or remakesche) is executed, the schedule information will be
added to the Network Schedules created in the above item ④⑥

Finalizing daily schedule
Finalized Daily Schedule, sfin utility, extracts scheduled Networks for the operation day. NETA isextracted every day except Sunday. NETB is extracted every Friday and on the 20th of every month.
(If 20th falls on either Saturday or Sunday, NETB is not included in finalized schedule)⑦

Executing Network
When Queuing command is issued, the finalized Networks will be queued and then executed under
A-AUTO Monitor.

2-16

2. System Configuration and Process Flow

(4) Monitoring Network
As explained in the sections below on ’File Transfer’, ‘Monitoring', and ‘Transmit Network Execution
Information' processing, the Network information is transmitted from Agent to Server and is available formonitoring by a Client.
When the Server is started up and ’File Transfer’ is requested, the Network information in the files of
A-AUTO for UNIX/Windows ® is transmitted to the Server. After which, the current Network execution
information is regularly transmitted to update the files at the Server. This information is available formonitoring by a Client.

■ File Transfer
When the files are transmitted, the Network information from A-AUTO for UNIX/Windows is written to thefiles at the Server. The information in the files at the Server is available for monitoring by a Client. ’File
Transfer’ may be requested from the Server or a Client. The request may define a range of Schedule Dateand a specific Execution ID as criteria. Information of Networks for the specified Schedule Date range andExecution ID is transmitted and written to Network Information File, Job Information File and Succeeding
Network Information File at the Server.

■ Monitoring
A-AUTO Monitor and Delay Monitor Task monitor the progress of Networks that have been queued forexecution.
①

A-AUTO Monitor for UNIX/Windows ®

Network execution information is written to Network Start Monitor File and Network Termination Monitor
File via A-AUTO interface when any of the following activities occurs
 When Network is executed.
 When Network normally ends.
 When Network abnormally ends.
 When Network is canceled.
 When Network is canceled in queue.
 When Network is freed on.
②

Delay Watch Task

When there is a delay in starting or completing the execution of a Network, the information is recorded in
Network Delay Monitor File.

2-17

2. System Configuration and Process Flow

■ Transmit Network Execution Information
The information of Networks’ execution statuses is automatically transmitted to the Server at a regularinterval, which is specified in system parameter (auto_sysconf). The parameter for the transmission interval
may be set or modified by Web Client. Information sent by this transmission is taken from Network Start
Monitor File, Network Termination Monitor File, and Network Delay Monitor. However, for Networks thatare queued by S command, their Network execution information and statuses are available only in Network
Information File and Job Information File of A-AUTO for UNIX/Windows ®
The information regularly transmitted by A-AUTO for UNIX/Windows replaces the corresponding
information in Network Information File, Job Information File, and Succeeding Network Information File atthe Server.

■ Time Simulation
The approximate start time and end time of Networks may be simulated based on the historical andschedule information stored for each Network.
The Server or Client may request for simulation with Schedule Date, Execution ID, and Simulation Start
Date/Time criteria. The execution schedule of the Networks, for the specified Schedule Date andExecution ID, is simulated by referring to Network Information File and Succeeding Network Information
File at the Server. The simulation data are written to Time Simulation File and can be displayed on
Network Time Chart at Client.

■ Display Network Information at Client
Monitoring criteria may be specified to filter and select Networks for display. When monitoring criteria are
specified at Client, only the information of the Networks that meet the specified criteria is retrieved from the
Network Information File, Job Information File, Succeeding Network Information File, and Time Simulation
File at the Server.

Display on ‘Network List’, ‘Network Flowchart’ and ‘Network Time Chart' willshow only Networks selected by the monitoring criteria.
■ Log FileLog information is recorded in Event Log File, Alert Log File, Command Log File, and Security Log File in
the Server. The log information may be displayed using Client.

2-18

2. System Configuration and Process Flow

■ Event execution status
Occurrence and execution of registered events and actions can be monitored and controlled via Web
Client.

2.2.2 Mainframe Connection Option
The following is the basic operation flow of A-AUTO for UNIX/Windows system with Mainframe Connection Option.

Mainframe

UNIX/Windows

Register Networks thatare to be executed on
mainframeorUNIX/Windows。
UNIX/Windows
Define Network

calendarNetworks will bescheduled for both ofUNIX/Windows andmainframe.

calendar

Schedule Network

Schedule Network of
UNIX/Windows

Schedule forUNIX/Windows

Networks will be
added to queues ofboth UNIX/Windows
and mainframe.
Networks ofUNIX/Windows will be
added to queue.

Execute Network,
Monitoring
Execute Network,
Monitoring

2-19

2. System Configuration and Process Flow

(1) Defining Network of UNIX/Windows
With Mainframe Connection Option, all Networks for UNIX/Windows and mainframe are registered into
Network Master file of A-AUTO for Mainframe using A-DICTIONARY.
◆You should set System Qualifier attribute of each Network to indicate the target server, UNIX/Windows
or mainframe, to execute the Network.
◆For UNIX/Windows, you should specify shell script name or batch file name.as the Job name of the
Network’s Job definition.
In A-AUTO for UNIX/Windows, one Network can be defined with a maximum of 32 jobs.

(2) Scheduling Network
Scheduling of networks is performed using the following procedures.
This function is called Scheduling.

①

Defining Schedule (A-DICTIONARY)
Use A-DICTIONARY of A-AUTO for Mainframe to define schedules for Networks of UNIX/Windows aswell as mainframe.
◆ Remember to allocate one Execution ID for Networks of mainframe and another different Execution
ID for Networks of each UNIX/Windows.

②

Creating Schedule
Perform the following operations for all Networks on mainframe.
・Standard Schedule (Long-range Schedule Function)・Schedule Confirmation (Pre-finalized Daily Schedule Function)
・ Finalized Daily Schedule Function③

Creating Schedule for UNIX/Windows
Perform the operations for Networks of UNIX/Windows on mainframe
・Schedule Confirmation (Pre-finalized Daily Schedule Function) for UNIX/Windows・ Finalized Daily Schedule Function for UNIX/Windows(3) Executing Network
Networks that have been extracted and finalized for the operation date are added to the respective queues
as follows.

①

Queuing for mainframe Issue Queuing command to transfer the scheduled Network information createdby Finalized Daily Schedule Function to Network Queue of A-AUTO for Mainframe.

②

Queuing for UNIX/Windows Issue Queuing command to A-LOCAL to transfer the scheduled Network
information created by Finalized Daily Schedule Function to Network Queue of each A-AUTO Monitor.

2-20

2. System Configuration and Process Flow

■ Mechanism of connection of Networks

Mainframe①Ended Notification of

UNIX/Windows

Preceding Network
Succeeding

Preceding
Network①confirmation of received Ended

Network

Notification of preceding
Succeeding
Network

Network

Preceding②Ended Notification of

Network

Preceding Network①

If Preceding Network is in mainframe and Succeeding Network is in UNIX/Windows
When A-LOCAL performs queuing to A-AUTO Monitor, A-AUTO Monitor will transmit "This preceding
Network does not exist in local node" to A-LOCAL of mainframe. Upon receiving this message, A-LOCAL
will write the necessary information of this preceding Network to "Area of Inquiry Storage".
At regular intervals, A-LOCAL checks the network that is stored in the Area of Inquriy Storage todetermine whether it has ended in A-AUTO for Mainframe. If it has ended, A-LOCAL sends the Ended
Notification information to A-AUTO Monitor. When A-AUTO for Mainframe confirms that the Ended
Notification information has been received, it will start the succeeding network.

②

If Preceding Network is in UNIX/Windows and Succeeding Network is in mainframe
When the Preceding Network has ended in UNIX/Windows, A-AUTO Monitor will send the Ended
Notification of the preceding Network to A-LOCAL.

Upon receiving the Ended Notification, A-LOCAL will

instruct A-AUTO for Mainframe to “Cancel&Free On” this Network. A-AUTO for Mainframe will start thesucceeding Network that is dependent on the Network that has been Freed On.
* Both of Networks of mainframe and Networks of UNIX/Windows will be added to Network Queue of
A-AUTO for Mainframe.

2-21

2. System Configuration and Process Flow

■ Detailed operation flow
With Mainframe Connection Option, Networks of UNIX/Windows are defined into the existing Network
Master of A-AUTO for Mainframe.

Similarly, the Schedule Confirmation, Finalized Daily Schedule andQueuing command are also performed on the mainframe server.

Mainframe

A-AUTO

UNIX/Windows

A-LOCAL

armt

A-AUTO Monitor

Registering
Networkss

Scheduling

QueuingStarting
Networks

EndingNetworks

Scheduling forUNIX/Windows
Sending information of
Networks which havebeen added to queueof UNIX/windows

Area of Storage for
information of Networks
which have been added
to Queue ofUNIX/windows
TCP/IP
Sending statusesof Preceding
Networks

Commun-ication

Updating ended
information of
Networks

Sending
confirmation ofreceived Ended
Notification ofPreceding Networks
Starting Networks
Ending Networks

Ended informationof Network* For V610 or later version, armt runs under AP-LINK

2-22

2. System Configuration and Process Flow

(4) Monitoring Network
As explained in the sections below on ’File Transfer’, ‘Monitoring', and ‘Transmit Network Execution
Information' processing, the Network information is transmitted from Agent to Server and is available formonitoring by a Client.
When the Server is started up and ’File Transfer’ is requested, the Network information in the files of
A-AUTO for Mainframe is transmitted to the Server.
After which, the current Network execution information is regularly transmitted to update the files at theServer.

This information is available for monitoring by a Client.

■ File Transfer
When the files are transmitted, the Network information from A-AUTO for mainframe is written to the files
at the Server. The information in the files at the Server is available for monitoring by a Client. ’File Transfer’
may be requested from the Server or a Client. The request may define a range of Schedule Dates and a
specific Execution ID as criteria.
Referring to Sub-Schedule Master, Network Master and Network Check File, information of Networks forthe specified Schedule Date range and Execution ID is transmitted to the Server. The Server will write
transmitted information to Network Information File, Job Information File and Succeeding Network
Information File at the Server.

■ Monitoring
A-AUTO on mainframe and Network Delay Monitor Utility monitor the progress of Networks that havebeen queued for execution.
①

A-AUTO on mainframe

Network execution information is written to Network Start Monitor File and Network Termination Monitor
File via A-AUTO interface when any of the following activities occurs.
 When Network is executed.
 When Network normally ends.
 When Network abnormally ends.
 When Network is canceled.
 When Network is canceled in queue When Network is freed on②

Network Delay Monitor Utility

When there is a delay in starting or completing the execution of a Network, the information is recorded in
Network Delay Monitor File.

2-23

2. System Configuration and Process Flow■

Transmit Network Execution Information

The information of Networks’ execution statuses is automatically transmitted to the Server at a regularinterval, which is specified in system parameter (auto_sysconf). The parameter for the transmission interval
may be set or modified by Web Client.
The information sent by this transmission is taken from Network Start Monitor File, Network Termination
Monitor File, and Network Delay Monitor. However, for Networks that are queued by S command, their
Network execution information and statuses are available only in Sub-Schedule Master File, Network
Master File and Network Check File of A-AUTO for Mainframe.
The information regularly transmitted by A-AUTO for Mainframe replaces the corresponding information in
Network Information File, Job Information File, and Succeeding Network Information File at the Server.
Referring to System Administrator’s Guide.

■ Time Simulation
The approximate start time and end time of Networks may be simulated based on the historical andschedule information stored for each Network.
The Server or Client may request for simulation with Schedule Date, Execution ID, and Simulation Start
Date/Time criteria.
The execution schedule of the Networks, for the specified Schedule Date and Execution ID, is simulated byreferring to Network Information File and Succeeding Network Information File at the Server.
The simulation data are written to Time Simulation File and can be displayed on Network Time Chart at
Client. (Refer to “7.6 Time Simulation”)■

Display Network Information at Client

When monitoring criteria are specified at Client, only the information of the Networks that meet the
specified criteria is retrieved from the Network Information File, Job Information File, Succeeding Network
Information File, and Time Simulation File at the Server. Display on ‘Network Monitor List’ , ‘Network
Flowchart’ and ‘Network Time Chart' will show only Networks selected by the monitoring criteria.
(Refer to “7.1 Monitor Condition” and ”7.3 Application Monitor, Application Monitor Flowchart,
Application Monitor Time chart”)■

Log File

Log information is recorded in Event Log File, Alert Log File, Command Log File, and Security Log File in
the Server. The log information may be displayed using Client. (Refer to “9.2.2 Log Management”)

2-24

2. System Configuration and Process Flow

■ Job Log Display
If you have installed A-LOG *1, the log information of jobs that have normally ended or abnormally ended
may be displayed using Client.

(Refer to ”7.4.1 Job Log Display”)*1 Job Log Management System of BSP Inc.

However, you cannot display the program which is connecting with A-LOG

2-25

2. System Configuration and Process Flow

◆ To monitor multiple A-AUTOs(for mainframe only)
A Server may be connected with multiple Agents and multiple Clients.
For mainframe environment where multiple A-AUTOs operate in multi-CPU mode, an Agent can beconnected to one or more A-AUTOs.
The following diagram illustrates the connections between multiple Agents, multiple Clients and multiple
A-AUTOs in multi-CPU mode.

Sub-Schedule Master File
Network Master File
Network Check File

A-AUTO in

A-AUTO

A-AUTO

A-AUTO

multi-CPU mode

1

2

3

Agent1

Network Start Monitor File、
Network End Monitor File

A-AUTO

A-AUTO

Agent2Agent3

The files which an agent uses are
created per agent.

Network Delay Monitor File

Network Information FileJob Information File

ServerSucceeding Network Information File
Time Simulation File
Event Log File
Alert Log File
Command Log FileWeb Server

Security Log FileFTP Information File
Simulation Information File

The files which a server uses are created per server.
There are multiple Agents' information in the files of a Server.

Client 1

Client 2

Client 3

Client 4

Client 5

The diagram shows the connections between multiple A-AUTOs in multi-CPU mode and multiple Agents/Clients.

Note
Up to 36 Agents can be connected with the Server. Only one Web Server can be connected with theServer.

2-26

2. System Configuration and Process Flow

2.2.3 Cross-Master Linkage Option
The following is the basic operation flow of A-AUTO for UNIX/Windows system with Cross-Master Linkage
Option.

A-AUTO system 1

NET1

NET2

A-AUTO system 2

NET3

NET1

NET2

NET3

Maintenance of master

Maintenance of masterTo register execution order andschedule pattern for Network.
You should register the systemname for those networks that are
to be executed in another
A-AUTO system.

To register execution order andschedule pattern for Network.
You should register the systemname for those networks that are
to be executed in another
A-AUTO system.

Schedule

Schedule

To finalize the schedule of a specific day.

To finalize the schedule of a specific day.

Queuing

Queuing

To add the Networks of a specific day
to queue.

To add the Networks of a specific day
to queue.

Controlling preceding relationshipof Networks of another A-AUTO
systemExecuting Networks
Executing Networks
To add Networks of A-AUTO system
1 to queue and execute it.

To add Networks of A-AUTO system
2 to queue and execute it.

A-AUTO/Web Client
Monitoring Networks

NET1

NET2

2-27

NET3

To perform an
integrated monitoring
for networks which are
executed in A-AUTO
system 1 and A-AUTO
system 2.

2. System Configuration and Process Flow

Highlighted text: The differences in the flow with previous operation(1)

Defining Preceding Network that belongs to another A-AUTO System

Cross-Master preceding Network refers to a Network that belongs to another A-AUTO System and is to be
used as a Preceding Network for a Network in current A-AUTO System. Use the Master Maintenancefunction to set a Cross-Master preceding Network.
Do not register a Cross-Master preceding Network into the Network Master of the current A-AUTO System.
Also, the Network Master of the current A-AUTO System must not have any Network with the same nameas a Cross-Master preceding Network. To ensure that there is no conflict in the name, you should use
Preceding Network of Cross-Master Checking (pnetchk) utility to check for such error in current Network
Master File.

Any conflict in naming may cause unpredictable results.

The following is an example of Networks with Cross-Master Linkage: NET1(to be executed in AUTO1) →NET2(to be executed in AUTO2) → NET3(to be executed in AUTO1)
For the registration of Master File of AUTO1 system, set NET2 to be Preceding Network for NET3. NET2 isregistered in Master File of AUTO2 system. In addition, ensure that NET2 must not exist in the Master Fileof A-AUTO1 system.

NET1

NET2

NET3

AUTO1

Methods to maintain Master File depends on the platform where A-AUTO system resides.
■ A-AUTO for UNIX or Windows:①Use Master Maintenance Function of Web Client.
②Use Import Function of A-AUTO/Web Client.
③Use mastercsv utility and Cross-Master Preceding Network Master Maintenance (pnetuty) utility
together.
To perform maintenance, use any one of the above methods ①～③.
■ A-AUTO for mainframe：
Use A-DICTIONARY utility andCross-Master Preceding Network Master Maintenance (pnetuty)utility
together.

(2) Scheduling Network
Next, Networks are scheduled. Scheduling is as normal and is not affected by the platform where an
A-AUTO system resides.
Scheduling of Networks with Cross-Master Option is almost the same as that of Stand-Alone mode.

2-28

2. System Configuration and Process Flow

(3) Executing Networks
To add networks of which operation date is extracted by last schedule to queue.

①

Queuing
Performs the Queuing as usual for each A-AUTO System to add Networks to their respective Network
Queues.

②

Sending preceding information to other A-AUTO Systems
When Queuing is performed with A-AUTO/Connect, Networks with preceding Networks that belong toother A-AUTO Systems are identified.

The necessary information of these Networks is then sent to theirrespective A-AUTO systems that will execute the preceding Networks.
③

Sending ended information of Network
If there a Network in another system that is dependent on the Network in the current system,
A-AUTO/Connect will send the ended information to the Network in the other system when the Network in
the current system has ended.

④

Receiving ended information of Network
On the other hand, when A-AUTO/Connect receives the ended information of a Network that has been
executed in another A-AUTO System, the current A-AUTO will start the succeeding Networks that are
dependent on this Network.

2-29

2. System Configuration and Process Flow

■ Detailed operation flow

For Cross-Master Linkage environment, register the System Name of those Networks that are to be
executed in other A-AUTO Systems as usual.
For A-AUTO for mainframe， you can register such Networks using Cross-Master Preceding Network
Master Maintenance (pnetuty) utility only.
After Queuing, A-AUTO/Connect automatically manages and controls the processing of succeeding andpreceding relationships of Networks that belong to other A-AUTO Systems.

A-AUTO1
A-AUTO
MonitorRegistering
MasterScheduling

Queuing

A-AUTO2

A-AUTO/
Connect

A-AUTO/
Connect

A-AUTO
Monitor

Requesting forended information of
Cross-Master
Network

Requesting forended information of
Cross-Master
Network

Registering

Receiving request
for ended
information of
Cross-Master
Network
Checking andnotifying end of
Cross-Master
Network

Receiving request
for ended
information of
Cross-Master
Network
Checking andnotifying end of
Cross-Master
Network

Starting
Network

Receiving ended
information of
Cross-Master
NetworkEnding Network

Responding toReceiving ended
information of
Cross-Master
Network

TCP/IP
communication

Receiving ended
information of
Cross-Master
Network
Responding toReceiving ended
information of
Cross-Master
Network

2-30

MasterScheduling

QueuingStarting
NetworkEnding Network

2. System Configuration and Process Flow

2.2.4 Event Management
The basic workflow of Event Management of A-AUTO for UNIX/Windows System is described in thissection.

Register Events

Executing Network(1) Setting Event Information
Event information can be defined using either Input Data Wait Definition window or Work Definition windowof A-AUTO/Web client.
To define Event using Input Data Wait Definition window, an Input Data Wait that represents an event

ID

must first be defined. Then define an event that will automatically trigger a utility, dsfo, to reset Input Data
Wait Attribute.
If Event information is registered via Work Definition window, the Event can be associated with any Action.
■ Associating Event with Data Wait Attribute①

When defining Event for Data Wait Attribute, the operator must first define the Data Wait ID and thetriggering event using Input Data Wait Definition pane of Web client. Then, A-AUTO/Event Server
associates the execution of dsfo utility as an action for the Event and stores the information in the
Master file that resides in A-AUTO/Event Server.

②

A-AUTO/Event Agent monitors the events in reference to event information registered in
A-AUTO/Event Server.

③

When A-AUTO/Event Agent detects an occurrence of a specified event, A-AUTO/Event Server sends
an execution request to perform the associated dsfo utility to A-AUTO/Event Agent.

④

A-AUTO/Event Agent runs the dsfo utility as requested by A-AUTO/Event Server.

2-31

2. System Configuration and Process Flow

■ Registering Event from Work window①

When triggering events and corresponding actions to be executed are registered via Work Definition
window, A-AUTO/Event Server stores the information in Master file that resides in the Server.

②

A-AUTO/Event Agent starts monitoring events from the start time specified in the Master file. The
start time is defined by 'Start Time' in Work Definition window of A-AUTO/Web client. * Note that if'Monitoring' is defined as 'Invalid' in Work Definition window, the event is ignored and not monitored.

③

When A-AUTO/Event Agent detects an occurrence of a specified event, A-AUTO/Event Server refers
to the Master file for the associated action to be executed.

④

Then A-AUTO/Event Server sends an execution request to perform the specified action to
A-AUTO/Event Agent. * Note that if 'Action Execution' of an Event is defined as 'Invalid' in WorkDefinition window, the action is ignored and not executed even if A-AUTO/Event Agent detects an
occurrence of the event.

⑤

A-AUTO/Event Agent performs the action as requested by A-AUTO/Event server. * A-AUTO/Event
Agent stops monitoring events when the time defined by 'End Time' has passed. 'End Time' is definedin Work Definition window. ※If 'Every' is defined for 'Action Execution pattern' of an Event in the WorkDefinition window, the specified action is performed each time the specified event is detected during
steps ② to ⑤. If 'First time' of an Event is defined, the action is performed only when the occurrenceof the specified event is detected for the first time. The action is not performed thereafter even if theevent is detected again.

2-32

2. System Configuration and Process Flow

(2) Flow of Automatic Execution of Events and Actions
The flow of automatic execution of events and actions is described in the diagram below.
A-AUTO/Event

A-AUTO/Event

ServerAgent

EventsActions

Master MaintenanceStarts monitoring event

Registers
EventsandActions
information via Web client and defines
association between them.

Starts monitoring the event inreference to the information stored in
A-AUTO/Event server.

！
Action search
Detects an Event
Refers to the Master file for the action
to perform in response to the event.

Detects an occurrence of an event.

Action execution

Execution of Action

Sends request to perform the specified
Action to A-AUTO/Event Agent.

Performs the specified action.

A-AUTO/Web
ClientEvent Monitor

Event

Action2-33

Monitors occurrence of events
basedoninformation
gathered from
A-AUTO/Event Server and
A-AUTO/Event Agent.

2. System Configuration and Process Flow

2.3

A-AUTO Monitor Process Structure

A-AUTO Monitor’s process structure is shown below.

cip
mcp

ncp

njp

execscrNon resident

nep

execscrtmr

lbp

execscr

Functions of each process are described below.

(1) Resident processes①

mcp (MASTER CONTROL PROCESSOR)
A- MONITOR's main process.

②

ncp(NETWORK CONTROL PROCESSOR)
Processes Network start and Network control commands.

③

njp(NETWORK JOB CONTROL PROCESSOR)
Processes Job start, Job end, and Job control commands.

④

nep(NETWORK END CONTROL PROCESSOR)
Processes Network end.

⑤

tmr(TIMER CONTROL PROCESSOR)
Monitors and controls Start Time and Data Wait.

⑥

lbp(LOAD BALANCE PROCESSOR)
Collects load information from each A-Remote periodically and stores the results in shared memory.

(2) Non resident processes①

execscr
Executes Job. It is created by njp.

②

cip(COMMAND INPUT PROCESSOR)
Accepts A-AUTO Monitor commands.

2-34

2. System Configuration and Process Flow

2.4

AP-LINK Process Structure

AP-LINK’s process structure is shown below

apcip
apcomdapsctrl
aplinkaptimer

aptmrcld

tcpipux

tcpchildconslux

conchild

asvagent
asvdelayicom
asvutil
jslinkrj
armt

Starts only when
Mainframe

armt1

Connection

Mode is usedamlpreq
amlrrcv
amlpchkamlercv

Starts only when
Cross-Mastermode is usedamldelpr
amlcip2-35

linkage2. System Configuration and Process Flow

Functions of each process are described below.

(1) Resident processes①

aplinkAP-LINK’s main process.

②

aptimer
Parent process of timer routine③

aptmrcld
Child process of timer routine④

tcpipux
Parent process of TCP/IP driver⑤

tcpchildChild process of TCP/IP driver⑥

conslux
Parent process of console driver.

⑦

conchildChild process of console driver.

⑧

asvagent
A-AUTO Agent.
Sends Job and Network execution statuses to Server for jobs being monitored.

⑨

asvdelay
Network Delay Monitor. Sends Network delay information to Server.
The process is created even when Network Delay Monitor is not used.

⑩

jslinkrj
When A-Remote for OS400 is used, it sends request for Job execution instructed by A-AUTO Monitor
to A-Remote for OS400. Also, it receives Job end information from A-Remote for OS400 and passes
the information to A-AUTO Monitor.
The process is not created when A-Remote for OS400 is not used.

2-36

2. System Configuration and Process Flow⑪

Armt (* For V610 or later version, armt runs under AP-LINK)When Mainframe Connection Mode is used, it routes various messages transmitted between A-AUTO
Monitor and A-LOCAL. It does not start when Mainframe Connection Mode is not used.

⑫

armt1 ( * for V610 or later version, armt1 runs under AP-LINK.)
When Mainframe Connection Mode is used, it replaces Master information of A-AUTO Monitor with
the Master information transmitted from A-LOCAL. It does not start when Mainframe Connection
Mode is not used.

⑬

amlpreq
When Cross-Master Linkage is used, it checks Cross-master Preceding Networks.
It does not start if Cross-Master Linkage mode is not used.

⑭

amlrrcv
When Cross-Master Linkage mode is used, it receives information request from other
A-AUTO/Connect. It does not start if Cross-Master Linkage is not used.

⑮

amlpchk
When Cross-Master Linkage mode is used, it checks if Cross Master Preceding ends. It does notstart if Cross-Master Linkage mode is not used.

⑯

amlercv
When Cross-Master Linkage mode is used, it receives end information of Cross-Master Preceding
Network and requests A-AUTO Monitor to reset the preceding Network. It does not start if
Cross-Master Linkage is not used.

⑰

amldelpr
When Cross-Master Linkage mode is used, it removes Cross-master Network information of those
preceding Networks that are released from Notification request table. It does not start if Cross-Master
Linkage mode is not used.

⑱

amlcipWhen Cross-Master Linkage mode is used, it receives commands for Cross-master, analyzes themand then dispatches these commands for execution.
It does not start if Cross-Master Linkage mode is not used.

⑲

asvutil
The task that changes the setting, executes utilities and issues commands.

2-37

2. System Configuration and Process Flow

(2) Non resident processes①

apsctrl
Controls AP-LINK’s termination.
It is initiated when close command is entered and ends after AP-LINK ends.

②

icom
Accepts commands for AP-LINK.

③

apcip
Analyzes commands. Analyzes commands accepted by icom.

④

apcomdAnalyzes commands. Analyzes commands accepted by icom.

2-38

3. Master Files

3 Master Files
A-AUTO for UNIX/Windows has 11 master files as follows.
 Network Master Network Group Master Data Wait Master Cross-Master Preceding Network Master Extended Job Master Annual Holiday Master Holiday Master Schedule Master Network Schedule Master Daily Network Master Event Management Master
This chapter explains each master file in detail.

3.1

Network Master
Network information is defined and registered in Network Master.
Users can register, update, delete and search application Jobs using “Network Definition List” on
A-AUTO/Web Client.
The following are the roles of Network Master and the items to be defined.

3.1.1 Purpose
Network Master manages the following information required to execute a Network.
(1)

Which application to execute(2)

On which computer an application is to be executed(3)

How an application is to be executed

3-1

3. Master Files(1) Which application to execute‘Which application to execute’ is equivalent to ‘which batch file to execute’ in operation. Batch files aregrouped (minimum 1 to maximum 32 batch files) into units. A unit is called a "Network" in A-AUTO for
UNIX/Windows and its purpose is to increase efficiency in application execution (Refer to a chart below).
Each group of batch files is then registered in Network Master as a Network with unique Network ID.
A Network is the minimum unit to be registered in Network Master.
By registering the following items in Network Master, ‘Which application to execute’ is defined.


Network ID



Job ID

NetworkJob ID
Application

Shell script

Job ID

Program (exe/bat/cmd)
Job ID* In A-AUTO for UNIX, Job means shell script.
* In A-AUTO for Windows, Job means batch file (bat), program (exe), or command (cmd).

User may register some comments for each application.
Comments that can be defined in Network Master are as follows.
Network Expanded Name

User Information

Document Information

Job User Field

User may register Valid Period for each application.
By defining the following items, valid period may be set for the Network Master information of a Network.
Valid Date

Expiry Date

3-2

3. Master Files(2) On which computer an application is to be executed
Depending on where an application resides, define on which computer the Network is to be executed. Thissetting is defined for each Network. If not defined, A-AUTO for UNIX/Windows will determine on which
computer to execute the Network.
By registering the following item in Network Master, ‘On which computer an application is to be executed’
may be defined.
System Qualifier(3) How an application is to be executed
The conditions to execute a Network may be defined in A-AUTO for UNIX/Windows.
Some conditions that may be defined are listed below.
 Start execution of a Network at hh hour mm minute. (Start Time).
 When a Network/Job that updates DB is completed, start the execution of another Network/Job
that takes back-up copies. (Preceding Network, or Preceding Job)
 When all data are ready to print, start the execution of a Network. (Data ID)
 When the operator issues a command, start the execution of Network. (Hold Code) When needed resource is ready, start the execution of Network. (Resource Name, Number ofResource)
By registering the following items in Network Master, ‘How an application is to be executed’ may be
defined.
Start Time

Hold Code

Priority

Parallel Processing Job

Preceding Network ID

Data ID

Network Max Executing TimeMaximum Return Code

Resource NameStart Type

Number of Resources

Parallel processing of the job

Job Executing User ID

 Response To Max Time

3-3

3. Master Files

3.1.2 Items to define
The following are the explanations of the items that can be defined in Network Master.

(1) [Network Attribute 1] Tab① Valid Date
Valid Date is the date that this Network information in Network Master becomes valid. If Valid Date is
specified, the Network becomes effective from the Valid Date. The same Network ID with different Valid
Date may be registered, up to a maximum of 5 different Valid Dates. If Valid Date is not specified, Valid
Date is set to Operation Date automatically.

② Network ID
Network ID is an identifier for a Network. Network ID can be any arbitrary name with the following
limitations.


Use alphanumeric characters, minimum of 2 and maximum of 8 characters (without blankcharacters). Only special characters @, $, # can be used.
[Example]［○］ANET01、ANET#001［×］ANET

01

When Network ID begins with #, the Network will not be scheduled in Finalized Daily Schedule,
asvsfin.



In UNIX system, "$" has special meaning (for example an environment variable or end-of-line setting).
When a command is issued for a Network that has $ in its Network ID, the result of the command isunpredictable.
For Network ID with $, please enclose the character $ in single quotation marks (') when issuingcommand for the Network[Example]［○］cip s’$’ANET01
3-4

3. Master Files［×］cip s$ANET 01


The following are reserved words for A-AUTO Monitor and cannot be used for Network ID.
ATE, LMCP, LOSE, LOSEE, LOSET, NPNumber (Numbers in 3 digits), JPNumber (Numbers in 3
digits), PARM、SCVT、START、SYS、TSK[Example]［×］ATE, LMCPNET, NP001, JP010 etc.

Network ID must be unique in Network Master.
* However, registration is allowed for Networks with the same Network ID but different Valid Dates.

③ Network Expanded Name
Description for the Network may be given in the field of Network Expanded Name, up to a maximum of 20
characters.

④ Network Group ID
Network Group ID is used to assign a Network to a Network Group. This field can be specified only duringinitial registration.

⑤ Start Time
Start Time indicates the time to start the execution of a Network. Start Time from 00h01m to 47h59m may
be specified. The application will start the execution on or after the specified time.

⑥ User Information
User Information is comment information for a Network.
User Information may be defined up to a maximum of 12 characters.

⑦ System Qualifier
System Qualifier defines under which A-AUTO Monitor a Network is to be executed. Also, System Qualifier
is used as one of the selection criteria of target Networks for Auto Scheduling utility to update Network
Schedule.

⑧ Class
Class is a single character alphanumeric class code that defines which class a Network is to be executed.
The default value is ‘A’.

⑨ Hold CodeSpecify an arbitrary hold code if a Network is to be held when queued into Network Queue. Application thathas a Hold Code may be released for execution by Release command. Hold Code can be either analphabet A to Z or a number 1 to 9 (1 digit).

3-5

3. Master Files⑩ Priority
Priority determines the order of Network execution. Priority to be assigned may range from the highest
priority of “15” to the lowest priority of “01”.

⑪ Parallel Run for processing of Jobs
Parallel Run attribute defines whether Jobs that are independent of each other in a Network are to be
executed concurrently. To select Parallel Run attribute, check on this option for the Network.

⑫ Input Data Wait
Input Data Wait attribute may be assigned to a Network that waits for data to arrive or events to occur. To
select Input Data Wait attribute, check on this option for the Network.
When this option is selected, Data ID(s) must be specified in Input Data Wait tab.

⑬ Monitor On
Monitor On option defines whether the succeeding Networks of a Network with Input Data Wait attributeare to be released automatically for execution when the Network ends normally. If Monitor On field of thisNetwork is selected (set to ON), when this Network normally ends, A-AUTO Monitor automatically releases
the Monitor On Wait condition and the Succeeding Networks will be executed without waiting for acommand input from the operator.(Please refer the section”3.3.3 Data Wait Management Function”.)⑭ Resource
If a Network is to wait for one or more resources before it can start execution, please check this Resource
field.
If Resource is selected, this Network will not be started until all Resources and their required quantities areavailable.

⑮ Document Information
Document Information may be defined as comments for a Network, up to a maximum of 50 characters.

⑯ Job Executing User ID
Job Executing User ID defines the OS User ID to be used to execute the Job if you want to use Switch Job
Execution User ID Function.
In this case, you specify Job Executing User ID to be used at Network level, i.e. it is to be used for all Jobs
defined in this Network.
You also can specify Job Executing User ID at Job level using [Job] tab, which will be described later.
If you specify it in both [Network Attribute1] tab and [Job] tab, the content specified in [Job] tab takeprecedence.
If you do not specify it in both [Network Attribute1] tab and [Job] tab, A-AUTO will execute the Job using
the account (User ID) that is used to startup A-AUTO Monitor and A-REMOTE.

3-6

3. Master Files* This is available only in A-AUTO Monitor and A-REMOTE version V7.2.2Lv00 or later.

(2) ［Network Attribute 2］Tab① Start Delay Watch Time
If a Network is to be monitored for Start Delay, check the Start Delay Watch Time check box, and specify
the time within the range from 00h00m to 47h59m. If the Network has not started by the specified time, theexecution of this Network will be treated as a delay.

② End Delay Watch Time
If a Network is to be monitored for End Delay, check the End Delay Watch Time check box, and specify thetime within the range from 00h00m to 47h59m.
If the Network has not ended by the specified time, the execution of this Network will be treated as a delay.

③ Time Interval End Time
If a Network is to be triggered at a regular interval, check the Time Interval End Time check box, andspecify the Time Interval End Time within the range from 00h00m to 47h59m. This is Time Interval
Execution function.

④ Time Interval (min)This field applies to Time Interval Execution function. It specifies the time interval in minutes for triggeringor queuing the same Network again. Network will start again after it has ended normally and the specified
time interval has passed.

⑤ Plug-in Before Start
Before a Network starts, if you want to start a Plug-in, check the Plug-in Before Start field and specify the
Plug-in.

⑥ Start Before Plug-in Parameter
This is the parameter to be passed to the Plug-in to be initiated before Network starts.

3-7

3. Master Files⑦ Plug-in After End
Immediately after a Network ends, if you want to start Plug-in, check the Plug-in After End field.

⑧ Plug-in Parameter After End
This is the Plug-in Parameter after Network ends.

⑨ Max Executing TimeIf you want a Network to complete its execution within a specific duration, check the Max Executing Time
field and specify the maximum duration (in minutes) the Network is expected to be completed. If theexecution of the Network is completed within the specified maximum duration, no action will be taken.
Otherwise, the action specified in Response To Max Time field will be taken. If you do not specify a time for"Max Executing Time", there will be no check on the execution duration for the Network.

⑩ Response to Max TimeThe action to be taken when a Network continues to execute past the maximum duration specified in "MaxExecuting Time". You should set this item only if "Max Executing Time" is selected.

As for Time Interval Execution function, please refer to”6.7.1 Time Interval Execution Function”.

3-83. Master Files(3) ［Job］Tab① Job Number
Job Number is any number to be assigned to a Job ID. Within a Network, Job Number must be a unique
number from 001 to 999 for each Job ID. The Jobs in a Network will be executed according to ascendingorder of Job Number.

ANET01
Job Number

Job ID

010

JOBA

020

JOBB

030

JOBC

040

JOBA

050

JOBC

Even if multiple Jobs with the sameJob ID are included in a Network,
each Job is unique and can be
identified by its Job ID and unique
Job Number.

3-9

3. Master Files② Dummy Job
A Job may be assigned a Dummy Job attribute if it is not to be executed. Dummy Job is particularly usefulwhen more than 16 Preceding Networks or more than 6 Preceding Jobs are to be defined.

③ Job ID(Job)
Job ID is the name of the Job, shell script or program to be executed. For A-AUTO for UNIX, Job meansshell script to be executed. For A-AUTO for Windows, Job means program (exe・bat・cmd) to be executed.
Maximum of 32 Job IDs may be defined for one Network.

④ Max Return Code(MAX-RC)
When a Job ends with a return code equal to or greater than Max Return Code, the Job, as well as the
Network, is considered as abnormally ended by A-AUTO Monitor. Therefore, the succeeding Jobs in thesame Network will not be executed. If the return code of a Job is used to determine whether the Job has
ended normally, please specify a value for the return code within the range 0 - 127. When a Job ends witha return code that is equal to or more than that of Max Return Code, A-AUTO Monitor treats the Job asabnormally ended. If a Job ends abnormally, the Network that contains the Job will be treated asabnormally ended too.
If the return code of a Job is not to be used to determine whether the Job has ended normally, specify “0”for Max Return Code.
(For the Job that is executed by Remote Job Execute Function (System i), the Max Return Code is notapplicable.)⑤ Job User Field
Specify any comment for the Job.

⑥ Parameter to be passed upon Normal Run
Please specify the parameter to be passed to a Job when Parameter Management function is used.
A user can pass different parameter for a Job depending on the Run Type of the Job, Normal Run or
Rerun type. The parameter specified here is for Job of Normal Run type.

⑦ Parameter to be passed upon Rerun
Please specify the parameter to be passed to a Job when Parameter Management function is used.
A user can pass different parameter for a Job depending on the Run Type of the Job, Normal Run or
Rerun type. The parameter specified here is for Job of Rerun type.

⑧ Preceding Job and Return CodeIf this job, i.e. succeeding Job, is to be executed depending on the return code of a preceding Job, selectthe [Preceding Job and Return Code] field.

⑨ Preceding Job Number
Select the Job Number(Job ID) to be defined as a preceding Job. Preceding Jobs have to be successfully
3-10

3. Master Files

executed before this Job, i.e. succeeding Job, will be executed. A maximum of 6 Job Numbers may be
defined as the Preceding Jobs. The succeeding Job will not be executed until all of the Preceding Jobs
have normally end.

⑩ Execution Condition
If using the Job Branching function, Execution Condition needs to be specified for the Preceding Job.
When the return code of a Preceding Job matches the Execution Condition, the condition to start this job,i.e. the succeeding Job, is fulfilled or met. If this field is not specified (No Condition), end status of thePreceding Job execution will be the Execution Condition. When all Execution Conditions are met or fulfilled,
the succeeding Job will be executed.

⑪ Recovery Job
Select [Execute as Recovery Job] field if this Job is to be defined as a Recovery Job.

A Recovery Job is a

Job that is to be executed only when the specified target Job ends abnormally. Abnormal end includes Job
cancelling or starting error. The target job is defined in the [Target Job for Recovery] field.
Although this Job is not executed when the target Job ends normally, it is treated as normally ended status.

⑫ Plug-in Before Start
If Plug-in needs to be started before Job starts, please check the Plug-in Before Start checkbox andspecify the Plug-in.

⑬ Start Before Plug-in Parameter
Specify the parameter for Plug-in Before Start.

⑭ Plug-in After End
If Plug-in needs to be started after Job ends, please check the Plug-in After End checkbox and specify the
Plug-in.

⑮ Plug-in Parameter
Specify the parameter for Plug-in After End.

⑯ Job Execution User ID

Job Executing User ID defines the OS User ID to be used to execute the Job if you want to use Switch Job
Execution User ID Function.
In this case, you specify Job Executing User ID to be used at Job level, i.e. it is to be used only for this Job.
You also can specify Job Executing User ID at Network level using [Network Attribute 1] tab, which has
been described above.
If you specify it in both [Network Attribute1] tab and [Job] tab, the content specified in [Job] tab takeprecedence.
3-11

3. Master Files

If you do not specify it in both [Network Attribute1] tab and [Job] tab, A-AUTO will execute the Job using
the account (User ID) that is used to startup A-AUTO Monitor and A-REMOTE.
* This is available only in A-AUTO Monitor and A-REMOTE version V7.2.2Lv00 or later.

(4) ［Preceding Network］Tab① Selected Network ID
Network IDs appearing here will be the Preceding Networks for this Network.
Preceding Networks have to be normally ended prior to the execution of this Network. Up to 16 Preceding
Networks may be defined.

② Network ID
Network IDs appearing here are available to be selected as Preceding Network.

3-12

3. Master Files(5) ［Resource］Tab① Resource ID
If the availability of Resource(s) is a Start Condition of a Network, select the Resource Name.
A user can select a resource from a list of resources defined in the Master file under the column "Resource
Name(Resource ID)".

② Maximum Number of Resource
The maximum quantity available for each Resource is displayed. This field is automatically shown when aResource Name is selected, and it cannot be edited.

③ Number of Resources
Specify the quantity of a Resource to be available before a Network can start. The number specified must
be within the [Maximum Number of Resource] of the selected Resource. Until all the Resources and theirrequired quantities are available, the Network will not be executed.

④ Start Type
This field indicates how the Resource is to be released at the end of a Network execution.


Auto：A-AUTO Monitor automatically releases the Resource when the Network has ended.

Manual：Use the Utility to release the Resource when the Network has ended.

* The maximum of the number of resources that can be associated with a Network is 10.

3-13

3. Master Files(6) ［Input Data Wait］Tab① Selected Data
Data ID(s) appearing here are the data or/and event(s) that a Network ID will be associated with and will
wait for.
Associating a Network ID with one or more Data IDs will automatically define Input Data Wait attribute for
the Network. A Network that has Input Data Wait attribute cannot be executed before arrival of the Data
ID(s). A data or event is set as arrived by executing a utility.

② Non-select data list
Data IDs appearing here are available to be selected or associated with the Network ID.
.

3-14

3. Master Files(7) "Expire Date Modify" Screen① Expire Date
On [Network Definition List] Windows, click on the checkbox of the target Network whose Expiry Date is tobe defined/updated/deleted and then click “Expire Date Modify” button. The "Expire Date Modify" dialog
screen of the selected Network will be displayed. Expire Date may be registered, modified or deleted on
this screen. Please select the required Expire Date and then click "Apply". To delete Expire Date, click"Delete" button.
Expire Date field specifies the date when the Network information of a Network in the Network Master is to
be expired or not usable.
When a Network is registered in the Network Master and the Expire Date of the Network is specified, thisNetwork becomes valid only for the period from Valid Date to Expire Date.
Only one Expire Date can be defined for a Network ID. If no Expire Date is defined, this Network will never
be expired.

(8) “Valid Date” Screen
On [Network Definition List] Windows, click on the checkbox of the target Network whose Valid Date is to
be updated/deleted and then click on [Valid Date List] button. The "Valid Date" screen of the selected
Network will be displayed. Existing Valid Date may be modified or deleted on this screen. Please select thecheck box of the target Valid Date and then click "Valid Date Modify" button to change the Valid Date or"Delete" button to remove the Valid Date.

3-15

3. Master Files

3.1.3 Valid Date and Expire Date Function
Valid Date field specifies when the Network information of a Network in Network Master becomes valid or
usable. By using the concept of Valid Date, it is possible to define several records of the same Network in
Network Master. For example, if a user wants to change the order of Job execution in a Network during a
specific period, defining the same Network ID with a different Valid Date enables you to change the content
of Network information in advance. This function is available in Version 7.1.0 and later.

If Valid Date is left blank during registration, Valid Date is automatically set to Operation Date.
Expire Date field specifies the date when the Network information of a Network in Network Master is to be
expired or not usable. Network will be valid until the date specified in Expire Date.
If Expire Date is not defined, this Network will never be expired.
[Example]
To register a Network "NETWK001" that has the following conditions
Condition 1

Condition 2

NETWK001 that consists of the following

NETWK001 that consists of the following Jobs

Jobs is to be executed during the period

has Parallel Run Attribute during the period

between 2008/6/20 and 2008/6/30.

between 2008/7/1 and 2008/7/10.

NETWK001

NETWK001

P

JOB001
JOB001

JOB010

JOB002

Condition 3

NETWK001 will not be executed after 2008/7/11.

Valid Dates of NETWK001 are: 2008/6/20 and 2008/7/1

08/6/20

Expire Date of NETWK001 is: 2008/7/10
7/1

NETWK001
NETWK001

P

JOB001
JOB001
JOB002Note

3-16

JOB0107/11

NETWK001 is
excluded from theexecution.

3. Master Files

For one Network, a maximum of 5 Valid Dates and only 1 Expire Date can be specified.



Expire Date can be the same date as Valid Date.



If a Network already has Expire Date, Valid Date to be added or modified cannot be a date after the
Expire Date.

Expire Date cannot be a date before the Valid Date. If more than one Valid Date exist, the Expire
Date cannot be a date before the latest Valid Date.



If Expire Date is registered, the Network will be expired from the next day of the Expire Date. (The
Network will still be valid on the date of the Expire Date itself.)When the Network Schedule information is updated, the schedules are created for only those dates
that the Network is valid based on the Valid Date and Expire Date specified.



If the Network Schedule is already created but the Network has expired when Daily Schedule is
executed, the Network will not be selected for execution.



After the Network Schedule for a Network has been created, the schedule information will remainunchanged even if the valid period for the Network is changed by registering, updating or deleting
Valid Date or Expire Date.



If a Network that has been selected into Daily Schedule expired before its Queuing, the Network will
not be the target of Queuing and end abnormally.



If a Network is already expired when it is about to be executed, A-AUTO Monitor cancels the Network.



To have the authority to view or manage Expire Date, request system manager to turn on the checkbox of Network Master Resource (※Network ID) on the User Management screen.

3-17

3. Master Files

3.1.4 Job Branching Function
Job Branching function allows a user to determine which succeeding Job to execute based on the returncode or end status of one or more preceding Jobs and/or User Plug-ins. By using this function, a user cancontrol the flow of Job execution according to the execution status of preceding Jobs and/or User Plug-ins.
This function is available in Version 7.1.0 and later. There are 3 types of Job Branching.

① Branching by the end status of Preceding Job
This type determines which succeeding Job to execute according to the end status (Normal End or
Abnormal End) of one or more preceding Jobs.

② Branching by the return code
This type determines which succeeding Job to execute based on the return code of one or more preceding
Jobs after the preceding Jobs have ended normally.

③ Status Control by User Plug-in
This type enables a user to change the status (Cancel, Hold, Continue, Normal End, and Abnormal End) ofa Network or Job according to the return code of a User Plug-in after the Plug-in is executed. A Plug-in canbe executed in the following situations, "Before Network starts", "After Network ends", "Before Job starts"or "After Job ends".

(1) Branching by the end status of Preceding Job
This type determines which succeeding Job to execute according to the end status (Normal End or Abnormal End) of
one or more preceding Jobs. For this type, preceding Jobs have to be successfully executed i.e. Normal End status
before a succeeding Job can be executed.
For Abnormal End status, a Recovery Job may be defined. In this case, the preceding Job is the target Job, defined in[Target Job for Recovery] field. When the preceding Job ends abnormally, the Recovery Job is executed. The Network ofthis Job is treated as abnormally ended at the end of the execution.
【Example】

1

2‘A’ ended abnormallytherefore ‘B’ is not executed

Abnormal End

B

B

Abnormal EndA

Not executed

A
C

3

C
4

Abnormal EndA

Not executed

B
Not executed

B

Abnormal End
ACC

Executed

Normal End‘A’ ended abnormallytherefore‘C’
isexecuted.

Network ends
abnormally.

3-18

3. Master Files

If the preceding Job ends normally, the Recovery Job will not be executed. The Recovery Job ends without
execution. Even if there is a remaining Recovery Job in the Network, the Network ends normally.
【Example】
2

1‘A’ ended normallytherefore‘B’
executed.

‘A’ ended normally.
B

Normal End
A

is

Executed
B

Normal End
A

C

3

C

4 Network：Normal End
Normal End

Running
B

Normal End
A

B

Normal End
A

C

C

End
i h
‘C’ is Recovery Job of ‘A’,so ‘C’ ends without execution.

Endi hEven if there is a remaining
Recovery Job in Network,
this Network ends normally.

Note
To define more than one Recovery Job for one Job, register the first Recovery Job as usual. For thesecond and subsequent Recovery Jobs, register them as succeeding jobs of the first Recovery Job definedearlier.
A user cannot register a Normal Job as the succeeding Job of the Recovery Job.

3-19

3. Master Files(2) Branching by the return code
This Job Branch type determines which succeeding Job to execute based on the return code of one ormore preceding Jobs after the preceding Jobs have ended normally.
You may specify a condition and its threshold value for each preceding Job. If the return code of apreceding Job fulfills this condition, the succeeding Job will be executed. If the specified condition is not
fulfilled, the succeeding Job will not be executed but treated as ended.
If there are several preceding Jobs, the succeeding Job will be started only after the condition of every
preceding Job is fulfilled.
The conditions that can be defined are as follows.
・Return Code is equal to a threshold value, up to a maximum of 5 values.
・Return Code is not equal to a threshold value.
・Return Code is bigger than a threshold value.
・Return Code is bigger than or equal to a threshold value.
・Return Code is smaller than a threshold value.
・Return Code is smaller than or equal to a threshold value.
・Return Code is bigger than threshold value 1 and smaller than threshold value 2.
・Return Code is bigger than or equal to threshold value 1, and smaller than threshold value 2.
・Return Code is bigger than threshold value 1 and smaller than or equal to threshold value 2.
・Return Code is bigger than or equal to threshold value 1, and smaller than or equal to threshold value 2.
* The upper limit of a threshold value that can be set is 127 and the lower limit is 0.
【Example】
Specify the Branching Conditions as follows.
(1) If the Return Code of Job A is bigger than ‘a’, Job B will be executed.
(2) If the Return Code of Job A is smaller than or equal to ‘a’ and bigger than ‘b’, Job C will be executed.
(3) If the Return Code of Job A is smaller than or equal to ‘b’, Job D will be executed.

(assumption: ‘a’>’b’)
RCa>a

A

B

b<RCa<=aRCa<=bCD

3-20

3. Master Files

・ For a case where RCa (Return Code of Job A)>’a’(1)Job B：preceding Job is Job A. Because RCa fulfills the Branching Condition, Job B is executed.
(2) Job C：preceding Job is Job A. Because RCa does not fulfill the Branching Condition, Job C ends
without execution.
(3) Job D：preceding Job is Job A. Because RCa does not fulfill the Branching Condition, Job D ends
without execution.

①

②
Exec

"RCa>a"therefore
executeNormal End

B

B

Normal End
RCa>aNormalEnd
C

A

Regarded as ended

A

D

C

D
Not "RCa<=a" notexecuted but
regarded
as
ended

③
Normal End
B
Normal End
RCa>aRegarded as endedA

C

Not "RCa<=b" notexecutedbutregarded as ended

D
Regarded as ended(3) Branching Control by User Plug-in
Job (or Network) End status and processing can be controlled by the return code of a Plug-in. These
Controls are different depending on the timing of executing a Plug-in and its Return Code.
A Plug-in must be registered in Plug-in Master in advance. When a Network is registered, a user may thendefine a Plug-in for the Network and/or for each Job of the Network.
A Plug-in may be executed in the following timing.
 "Before Network starts"
 "After Network ends"
 "Before Job starts"
 "After Job ends"
The Network (or Job) status and processing that can be controlled at each timing are as follows.

3-21

3. Master Files① Execution before Network starts
Plug-in RC

Status/Processing control

0

Continue the processing

8

Hold the Network

12

Cancel the Network* Will continue the processing if the Return Code is none of the above.
* If you issue Release command to the Network which has been held, plug-in will be executed
before restarting the Network.

② Execution after Network ends
When defined for this timing, a Plug-in is executed only when a Network ends with Network End Status of
Normal End (0) or Abnormal End (12). Otherwise, the Plug-in will not be executed and the Network will end
abnormally. If the Return Code of Plug-in is either Normal End (0) or Abnormal End (12), this Return Codewill be set into the Network End Status at the end of Network execution.

Plug-in RC

Status/Processing control

0

The Network End status is set to Normal End

12

The Network End status is set to Abnormal End* The Return Code is ignored if Return Code is none of the above.

③ Execution before Job starts
Plug-in RC

Status/Processing control

0

Continue the processing

8

Cancel the Job

10Treat the Job as Dummy Job* Will continue the processing if the Return Code is none of the above.

④ Execution after Job ends
When defined for this timing, a Plug-in is executed only when a Job ends with Job End Status of Normal
End (0) or Abnormal End (12). Otherwise, this Plug-in will not be executed and the Job will end abnormally.
If the Return Code of Plug-in is either Normal End (0) or Abnormal End (12), this Return Code will be set
into the Job End Status.

Plug-in

Status/Processing control

0

The Job End status is set to Normal End

12

The Job End status is set to Abnormal End* The Return Code is ignored if Return Code is none of the above.

3-22

3. Master Files■ How to make Plug-in
Plug-in can be a batch file, a shell script or an executable file. It should be registered in System
Management Windows of A-AUTO/Web Client in advance. When A-AUTO executes a Plug-in, informationof several A-AUTO environment variables are set and made available to the Plug-in. Plug-in may use
these information on environment variables for its processing. On the next page, there is the list ofenvironment variables that Plug-in can use.
On Windows Server, if Plug-in is executed when A-AUTO Monitor is started as a Windows Service,
A-AUTO Monitor will output the Plug-in Log in the Job Log directory. This Log records the result of theprocessing for the Plug-in. Please view the System Administration Guide for further information of settingof the Job Log directory.

If A-AUTO Monitor is started from the console window (not as a Windows Service), the Job Log setting
must be activated in order for A-AUTO Monitor to output the Plug-in Log in the Job Log directory for therecording.

NoteThe processing of A-AUTO Monitor will be halted during the execution of a Plug-in. If the processingof the Plug-in takes a long time, the performance of A-AUTO Monitor may deteriorate.

The owner of the shell script of Plug-in has to be the same user as the user by which A-AUTO isstarted.

3-23

3. Master Files

List of the Available environment variables

1

BSP_PLG_PARAM

2

BSP_NET_ID

Network Plug-in
Before Network
After Network
startsEnds
Parameter which
Parameter whichis registeredis registeredin Masterin Master
Network ID
Network ID

3

BSP_NET_GRPID

Network Group ID

Network Group ID

4

BSP_NET_CLASS

5

BSP_NET_SYSQ

6

BSP_NET_PRTY

7

BSP_NET_STARTATTR

8

BSP_NET_INPUTATTR

9

BSP_NET_HOLDATTR10

BSP_NET_PRRATTR

11

BSP_NET_UFIELD

12

BSP_NET_ETYPE

13

BSP_NET_STADATE14

BSP_NET_STATIME

Network Class
SystemQualifierPriority
Start Time
Attribute
Input Data Wait
Attribute
Hold Attribute
Parallel Run
attribute
Network
User Field
Execution Typefor Network
Network Start
Date
Network
Start Time15

BSP_NET_ENDDATE

Network Class
SystemQualifierPriority
Start Time
Attribute
Input Data Wait
Attribute
Hold Attribute
Parallel Run
attribute
Network
User Field
Execution Typefor Network
Network Start
Date
Network
Start Time
Network
End Date

16

BSP_NET_ENDTIME

17

BSP_NET_NPNO

18

BSP_NET_STATE

19
20
21
22
23

BSP_JOB_NETWORKID
BSP_JOB_JOBNO
BSP_JOB_JOBID
BSP_JOB_DUMMY
BSP_NET_JFIELD

24

BSP_JOB_MAXRC

25
26
27
28
29
30
31
32
33

BSP_JOB_JPNO
BSP_JOB_STADATEBSP_JOB_STATIMEBSP_JOB_ENDDATEBSP_JOB_ENDTIMEBSP_JOB_RC
BSP_JOB_STATEBSP_JOB_JOBLOGPATH
BSP_JOB_ESYSQPR

34

BSP_AUTODATE

35

BSP_SDATENo

Name of the environment
variable

Job Plug-in
Before Job starts

After Job Ends

Parameter which isregisteredin Master

Parameter which isregisteredin Master

Network ID
Job Number
Job ID
Dummy Job
Job User Field
Maximum Return
Code
JP Number
Job Start Date
Job Start Time

Network ID
Job Number
Job ID
Dummy Job
Job User Field
Maximum Return
Code
JP Number
Job Start Date
Job Start Time
Job End Date
Job End Time
Return CodeJob End Status
Full path of Job Log
System Qualifier
Monitor Operation
Date
Schedule Date

Network End Date
NP Number

NP Number
Network End
StatusMonitor Operation
Date
Schedule Date

3-24

Monitor Operation
Date
Schedule Date

Monitor Operation
Date
Schedule Date

3. Master Files

3.1.5 Parameter Management(1) Function Overview
Parameter Management Function allows a user to pass one or more parameters, which are defined in
Network Master or Parameter Definition File, to a Job before execution. Using this function enables
A-AUTO Monitor to pass these parameters to a Job when it is started. Depending on the run type of theJob, i.e. Normal type or Rerun type, different parameters can be passed.
* Depending on the system, you can use different ways to define parameters that are to be passed to Jobs.

UNIX/Windows

A-AUTO Monitor

Job

Limitation
If there are several Jobs with the same Job name in one Network, A-AUTO Monitor passes the same
parameters to each of these Jobs.

(2) Network Definition (in case of Stand-alone version)
Define the parameter(s) on the "Job" tab of [Network-Create] dialog when creating a Network.

For

Remote Job Execute environment and if the system parameter ARMT_LOCAL_INFO is set to 0, you must
define the parameters for Jobs using this method.
For each Job, a user can define one or more parameters.

■ Network Master Format
Parameter1
Parameter2

Parameter3…

Separate each parameter with a space.

The place to define the Parameter is different depending on the Execute Type of the Job (Normal type,
Rerun type). On the "Job" tab of [Network-Create] dialog, please define the parameter(s) in "Parameter tobe passed upon Normal Run" field (in case of Normal type) or in "Parameter to be passed upon Rerun"
field (in case of Rerun type).
3-25

3. Master Files(3) Parameter Definition File (In case of Stand-alone)
In Parameter Definition file, parameters are defined and identified uniquely by the Network ID and Job ID.
For Remote Job Execute environment and if the system parameter ARMT_LOCAL_INFO is set to 1, youmust define the parameters for Jobs using this method. For each Job ID and Network ID, a user can define
one or more parameters.

■ Definition Format in Parameter Definition File
Network ID
Network ID
Network ID
Network ID：：


Job ID Parameter1 Parameter2
Job ID Parameter
Job ID Parameter1 Parameter2 Parameter3
Job IDIn Parameter Definition file, define the values for "Network ID", "Job ID" and "Parameter” in that orderfor each row. Separate each value with a space.

Insert a Carriage Return before defining another Network ID and Job ID.

■ File name of Parameter Definition file
Different Parameter Definition files are defined for different run types (normal type, rerun type) of the Job. If
there is no Parameter Definition file defined for rerun type Job, Parameter Definition file for normal type Job
will be used for both types. File name convention for Parameter Definition file is as follows.
■For Normal Type
System Parameter ‘FILES_PREFIX’ ＋ ‘paranormal’■For Rerun Type
System Parameter ‘FILES_PREFIX’ ＋ ‘pararerun’

In the case of A-AUTO for UNIX
Example for Normal Type) In the case of FILES_PREFIX = /home/auto/files/aux_→/home/auto/files/aux_paranormal

Example for Rerun Type) In the case of FILES_PREFIX = /home/auto/files/ aux_→

/home/auto/files/aux_pararerun

In the case of A-AUTO for Windows
Example for Normal Type) In the case of FILES_PREFIX = c:\bsp\AUW\FILES\auw_→c:\bsp\AUW\FILES\auw_paranormal

Example for Rerun Type) In the case of FILES_PREFIX = c:\bsp\AUW\FILES\auw_
3-26

3. Master Files→

c:\bsp\AUW\FILES”\auw_pararerun”

Note
How parameters are passed differs depending on the System Parameter AUTO_RESON.
AUTO_RESON = 0

AUTO_RESON = 1

Parameter which is passed to the Job
in ”$0／%0”Job ID with full path

Job ID with full path

Parameter which is passed to the Job
in ”$1／%1”Parameter1

Network ID

Parameter which is passed to the Job
in ”$2／%2”Parameter2

Parameter1

Parameter which is passed to the Job
in ”$3／%3”Parameter3

Parameter2【Example】Parameter passing (When AUTO_RESON is set to ’0’)Parameter Definition file
NET001 JOB1 PARM1 PARM2

Job ‘JOB1’When executed$1:PARM1$2:PARM2(4) Setting of System Parameter
To use the Parameter Management Function, the following system parameters need to be defined.
System Parameters can be changed using the "Settings of Monitor" screen of [System Management]
Windows. How to specify the system parameters is explained in “9.3.1 Settings of Monitor”.

NJP_PARAON
The default value of ‘0’ indicates that the Parameter Management function is inactive. To use this function,
specify ‘1’. The value of ‘1’ indicates this function is active.
NJP_PARA_CHARSET*This system parameter is necessary for A-AUTO for UNIX system. Please refer to "2.9.1 autoenv(.csh)
Setting" of System Administrator's Guide to set autoenv(.csh).
3-27

3. Master Files

3.1.6 Switch Job Execution User ID Function
This function is supported in A-AUTO Monitor and A-REMOTE version V7.2.2Lv00 or later.
If you want to use this function, you need to start A-REMOTE Monitor and A-AUTO Monitor as services.
Please note that this function cannot be used in Mainframe Connection Option and A-AUTO for Mainframe.

(1) Function Overview

In a standard operation, A-AUTO Monitor uses the OS User ID of the user that starts up the A-AUTO
Monitor to start Jobs for execution. The permissions and access rights of the job is therefore the same as
the OS User ID that starts up A-AUTO Monitor. The Switch Job Execution User ID Function allows you to
use a different User ID to start a Job for execution. If you use this function, A-AUTO Monitor uses the UserId identified by [Job Execution User ID] attribute of Job or Network to start a Job. In this case, permissions
and access rights of the job are switched to the User ID identified by [Job Execution User ID]. This function
provides for a safer computer environment. You can refer to [Network Monitoring] screen of [Application
Monitor] Windows and [Network Log List] screen of [A-AUTO Monitor] Windows to display the User ID thatis used to execute the Job.
[Job Execution User ID] attribute may be specified at Network level or Job level.
You need to perform the following procedures when you use this function.
1.

Defining System Qualifier（System administrator to perform this）(Please refer to "13.1.1 Setting System Qualifier")

2.

Creating User Information Definition File（System administrator to perform this)(Please refer to "3.7.9 User Information Definition File Setting" of System Administrator's Guide and"5. ■ mkusrdef Utility" of Operation's Guide.)

3.

Applying User Information Definition File and System Qualifier Definition（System administrator toperform this）(Please refer to "3.7.6 Settings for SYSQCONF File" and "3.7.9 User Information Definition File
Setting" of System Administrator's Guide.)4.

Register [Job Execution User ID] into Master (all users）[Job Execution User ID] must be specified in [Job] tab or [Network Attribute 1] tab of Network Master.
Specify [Job Execution User ID] in [Network Attribute 1] tab for Network level and in [Job] tab for Job
level.
About the explanation of each item, please refer to "3.1.2 Items to Define".

Note* In step ”3. Applying User Information Definition File and System Qualifier Definition", you need to
3-28

3. Master Filesissue esys command or restart A-AUTO Monitor (WARM Start or COLD Start).
*In Daily Network Master, you can only modify [Job Execution User ID] which is specified at Network
level.
*The following setting of Job Execution User ID depending on OS Version may act incorrectly.

Windows Server 2003

Windows Server 2008

Assigned Network Driver

Does not detect

Does not detect

Default printer

Does not detect

DetectCan useCannot use

Using foreign letters* If your environment has the following two conditions, you need to enable [Allow the service to interact
with desktop].
(1)The environment is Windows Server 2003.
(2) Use " Switch Job Execution User ID" Function.
Open "properties" of "A-AUTO" from Service Manager and check [Allow service to interact withdesktop] in [Log On] tab.

(2)About the relevance between Job Execution User ID and user account

A-AUTO Monitor

Job Execution
information

Taking information of corresponding user accountUser Definition
information

Taking Job Execution information

To open the information of User Definition
User Definition File

Network Master

Job Execution User ID,・・・,User ID,・・・・・・

Job Execution User ID is an identifier to refer to an actual user account (User ID).
A-AUTO System will use the user account to start a job for execution.
Job Execution User IDs and their related user accounts are defined in User Information Definition File.

3-29

3. Master Files

A-AUTO Monitor gets the User Information Definition File and built it in the memory. It then performs thefollowing procedures whenever a Job is ready to execute.

① Get the content of [Job Execution User ID] of the Network or Job from Network Master.
② Search the memory of User Information Definition File for a matching [Job Execution User ID]
information. If found, get the corresponding user account.
③ Execute the job using the user account that was obtained.

3-30

3. Master Files

3.2

Network Group Master
Network Group is used to group applications or Networks.
To register, update, delete or search Network Group, use the [Network Group List] window on Web Client.
The following describes the roles and definitions of the Network Group Master and its fields.

3.2.1 Purpose
Network Group allows a user to define several Network IDs as belonging to a group. It is the broader
concept of Network.
Network Group consists of one level. It may be used as a criterion to search or choose Networks. A user
can modify or delete Networks by the unit of Network Group. In addition, Network Group may be specified
as a criterion to select Networks when generating schedules (makesche utility) or re-generating schedules(remakesche).
The Network Group Master comprises information about Network Groups and the Network IDs that belong
to the Network Groups. One Network Group ID may consist of several Network IDs.
This function can be used in Version 7.1.0 or later.

3.2.2 Items to define
The items that can be defined in Network Group Master are as follows.

3-31

3. Master Files(1)"Network Group" screen① Group ID
Group ID is an identifier for a Network Group. Group ID can be any arbitrary name with the following
limitations.


Use alphanumeric characters, minimum of 2 and maximum of 8 characters (without blank characters).
Only special characters @, $, # can be used.
[Example]［○］ANET01、ANET#001［×］ANET01

If Group ID begins from "#", the Group ID will not be scheduled in Finalized Daily Schedule, asvsfin.

In UNIX system, "$" has special meaning (for example an environment variable or end-of-line
setting).When a command is issued for a Network Group that has $ in its Network Group ID, theresult of the command is unpredictable. For Network Group ID with $, please enclose the character$ in single quotation marks (') when issuing command[Example]［○］cip s’$’ANET01［×］cip s$ANET 01



The following are reserved words for A-AUTO Monitor and cannot be used for Network Group ID.
ATE, LMCP, LOSE, LOSEE, LOSET, NPNumber(3 digits number), JPNumber(3digits number),
PARM, SCVT, START, SYS, TSK[Example]［×］ATE, LMCPNET, NP001, JP010 etc

Network Group ID must be unique in Network Group Master.

② Network Group Expanded Name
Network Group Expanded Name may contain any comments for Network Group.
Network Group Expanded Name may be defined up to a maximum of 20 characters.

3-32

3. Master Files③ Selected Network ID
This shows the Network IDs belonging to the Network Group.

④ Network ID
This shows the Network IDs that are available and can be selected to be included in the Network Group.
Note

A Network ID may belong to only one Network Group ID.

Even if the Network has more than one Valid Date, it may also belong to only one Network Group ID.

Networks which are not in any Network Group are automatically placed in the Network Group called"Unregistered Group".



To delete a Network Group on the Web Client, the Network Group must contain no Network ID.

Only Network Group Expanded Name can be updated. Network Group ID cannot be changed.

3-33

3. Master Files

3.3

Data Wait Master
Data Wait Master stores the Data Wait information used in the Data Wait Management Function. Data Wait
is an internal flag that can be used to represent an event, such as arrival of input data or Job terminationthat happens outside the control of A-AUTO System.
User can register, update, delete, and search Data Wait IDs using the [Input Data Wait Definition List]
window of Web Client.
The following are the roles of Data Wait Master and the items that can be defined.

3.3.1 Purpose
Data Wait Management function allows a Network to wait for conditions or events, outside the control of
A-AUTO Monitor, before it can be executed. Examples of such conditions or events are arrival of input data
and termination of a Job. These events or conditions are registered as Data Waits in Data Wait Master.

3.3.2 Items to define
The followings are the items that can be defined in Data Wait Master.

(1)"Data Wait detail" screen① Data ID
Data ID or Data Wait ID is an identifier for a Data Wait, which is an internal flag that is used to represent an
event, such as arrival of input data or Job termination that happens outside the control of A-AUTO for
UNIX/Windows. Data ID can be any arbitrary name with the following limitations.


Up to a maximum of 8 alphanumeric characters with no intervening blank. Only special characters(@, $, #) are allowed.
[Example]［○］DS01、D@001
［×］DS

01

3-34

3. Master Files

Data ID must be unique in Data Wait Master.

② Comment
Comment is any description for Data Wait, up to a maximum of 44 characters ("%" or "&" cannot be used).
If “Input Data Wait Reset Event” is selected (check box is ticked), Comment Information is limited to a
maximum of 32 characters ("%" or "&" cannot be used).

③ Input Data Wait Reset Event
Check this check box if the event to set this Data Wait is to be monitored by A-AUTO/Event.
By selecting this “Input Data Wait Reset Event” option, A-AUTO/Event will monitor the specified event andset the Data Wait flag automatically when the event occurs. The triggering event is specified as described
below. If this option is not selected, a user will have to set the Data Wait flag using dsfo utility.

④ Event TypeOne of the following 4 Event Types may be monitored.
1.

Job Event
A-AUTO/Event will monitor for the termination of a process whose name is given inProcess Name field of Event Detail information.

2.

Message Event
A-AUTO/Event will monitor for an output message that has a Message ID matching the ID
field of Event Detail or that has a message text matching the specified String of Event
Detail.

3.

File Event
A-AUTO/Event will monitor for creation or update of a file whose file name is given in File
Name field of Event Detail information.

4.

Application Event
This event is generated by an application.
A-AUTO/Event will monitor for Application Event ID and Event Parameter that match thevalues specified in Application Event ID and Application Event Parameter of Event Detail
information.

⑤ A-AUTO/Event Agent Name
A-AUTO/Event Agent Name where the event is to be monitored. A-AUTO/Event Agent must be registeredin [A-AUTO/Event settings] tab of Agent Management Windows.

3-35

3. Master Files⑥ Data Arrival Event Agent nameSpecify the A-AUTO/Event Agent Name that gives an instruction when data arrived. A-AUTO/Event Agentmust be registered in [A-AUTO/Event settings] tab of Agent Management Windows.

⑦ Process Name
Specify name of the process when the Job Event is to be monitored, up to a maximum of 63 alphanumericcharacters.

⑧ File Name
Specify the name of the file when the File Event is to be monitored, up to a maximum of 63 alphanumericcharacters.

⑨ ID
Specify the Message ID when the Message Event is to be monitored, up to a maximum of 63 alphanumericcharacters.

⑩ UNIX system log offset
Specify this item when Message Event is to be monitored and message text is to be matched. Specify theUNIX system log offset where the string to be matched is located. The log offset is specified as numberthat indicates the position from the beginning (the first position of the log is 0).

⑪ String
Specify the alphanumeric string to match. The total length of the string and the offset must be less than 18
characters.

⑫ Application event ID
Specify the Application Event ID when the Application Event is to be monitored, up to a maximum of 63
alphanumeric characters.

⑬ Application event parameter
Specify the Application Event parameter when the Application Event is to be monitored, up to a maximumof 20 alphanumeric characters.

3-36

3. Master Files

3.3.3 Data Wait Management Function
Data Wait Management function allows a Network to wait for conditions or events, outside the control of
A-AUTO Monitor, before it can be executed. Examples of such conditions or events are arrival of input data
and termination of a Job outside A-AUTO.

These events or conditions are represented by Data Wait IDs

or Data Wait flags, which are defined in Data Wait Master.
The following attributes and condition are available in Data Wait Management function.
(1)

Input Data Wait Attribute(2)

Monitor On Wait condition(3)

Monitor On Operation(1)Input Data Wait Attribute
Input Data Wait attribute is one of the wait conditions that may be defined for a Network. A Network with
Input Data Wait attribute will not be executed until Monitor command is issued or the dsfo utility is executed
to notify that the event has happened or arrived.

DATA1

When dsfo utility notifies A-AUTO
Monitor of the arrival of Data, Data
ANET01
Data ID = DATA1

Wait condition is released and theInput Data Wait

Network ANET01 is started.

When dsfo utility notifies the data arrival, the Data Wait condition of the Network is released. By using dsfl
utility, Data Wait information list can be output.

3-37

3. Master Files(2)Monitor On Wait condition
For a Network with Input Data Wait attribute, the Monitor On Wait condition is automatically effective.
Monitor On Wait condition means the succeeding Networks of a Network with Input Data Wait attribute will
be placed on wait state even if the Network with Input Data Wait ends normally. Succeeding Networks will
not be executed until the wait condition is released.
(Please refer to "(3)Monitor On Operation" on how to release the succeeding Networks.)
The following is an example.
Referring to the illustration below, Network ANET01 with Input Data Wait attribute is defined as Preceding
Network for ANET02. After Input Data Wait condition for ANET01 has been released, ANET01 is executedand ends normally. ANET02 will not be executed but will be put on Monitor On Wait condition. Monitor On
Wait condition has to be released in order to execute ANET02.

DATA1

ANET01
Data ID = DATA1

If the Monitor On Wait
conditionisreleased,
ANET02 will be started.

Input Data Wait

Monitor On Wait

ANET02Preceding Network = ANET01

3-38

3. Master Files(3)Monitor On Operation
To release Monitor On Wait condition, you can select one of the following two operation proceduresIssue a command to release Monitor On Wait condition
After the Network with Input Data Wait ended normally, issue a Monitor On command on this Network.
The succeeding network(s) will be started (For Monitor On command, please refer to “6.5.1 Networks
in Wait State”).

Define Monitor On attribute for Network
In usual operation, if Succeeding Networks do not have to be put on Monitor On Wait condition, set
Monitor On attribute to ‘ON’ (selected) when defining the Network with Input Data Wait. When a
Network, whose Monitor On attribute is set to ‘ON’, ends normally, the Monitor On Wait condition will
be automatically released for the succeeding Networks.

Releasing by Monitor command

Releasing

by

DATA1

MonitorOn

DATA1

ANET01

ANET01

Data ID = DATA1 Input Data Wait

Data ID = DATA1 Input Data Wait
Monitor On Attribute

Monitor On Wait

AANET02 will wait. When Monitor On

When ANET01 normally ends, thecommand is issued, ANET02 will be

succeeding Network ANET02 will

started.

be automatically started.

ANET02

ANET02Preceding Network = ANET01

Preceding Network = ANET01

3-39

3. Master Files■How to relate the Data Wait Master to Network Master[Network-Create] dialog of Network Definition List Windows may be used to associate a Network with
Data Wait IDs. Up to 5 Data IDs may be specified for a Network ID in A-AUTO for UNIX/Windows. Up to 13
Network IDs may be associated with the same Data ID.

RelatedANET001

ANET001

ANET002

ANET003

ANET004

ANET005

ANET006

ANET007

ANET008

ANET009

ANET010

ANET011

ANET012DATA01

DATA02

DATA03

DATA04

DATA05Up to 5 Data IDs can be
related to a Network.

Related
DATA01Up to 13 Networks can be
related to a Data ID.

ANET013For details, refer to the section "3.1 Network Master".

3-40

3. Master Files

3.4

Extended Job Master
Extended Job Master stores Job ID Conversion and Resource Requirement information for Jobs.
To register, update, delete or search the information that is defined in the Extended Job Master, use theExtended Job Definition List screen of the Web Client. The following are the roles of Extended Job Masterand the items that can be defined.

3.4.1 Purpose
Information required for Job ID Conversion function and information on the Resource requirements for a
Job are stored in the Extended Job Master. Only Jobs that use either or both of these functions need to beregistered in the Master.
This function is available in Version 7.1.0 or later.

3.4.2 Items to define
The followings are the items that can be defined in the Extended Job Master.

(1)［Extended Job Detail］Tab① Job ID
Job ID is the name of a Job defined in a Network. For A-AUTO for UNIX, a Job means a shell script. For
A-AUTO for Windows, a Job means a program (exe, bat, cmd). The maximum number of shell scripts thatcan be defined for one Network is 32.
Job ID registered in the Extended Job Master must be defined in the ‘Job’ tab of the Network Masterregistration.

② Enable Resource
If Resource availability is a condition to execute Network, check the "Enable Resource" check box.
A job with Resource availability condition will not be started until the required quantities of the specified
Resources are available.

3-41

3. Master Files③ Standard
Select this when the Job does not use Job ID Conversion function.

④ Enable Job Name Converter
Select this if Job ID Conversion function is to be used.(As for Job ID Conversion function, refer to thesection "3.4.3 Job ID Conversion Function".)⑤ Full path
Specify a full path and Job file name to be executed in the server when using Job ID Conversion function.

3-42

3. Master Files(2)［Resource Management］Tab① Resource ID
If the availability of Resource(s) is a Start Condition of a Job, select the Resource Name.
A user can select a resource from a list of resources defined in the Master file under the column "Resource
Name(Resource ID)".

② Maximum Number of Resource
The maximum quantity available for each resource is displayed. This field is automatically shown when aResource Name is selected, and it cannot be edited.

③ Number of Resouces
Specify the quantity of a Resource to be available before a Job can start. The number specified must bewithin the Maximum Number of Resource of the selected Resource.
When all the Resources and their required quantities are available, A-AUTO Monitor starts the Job.

④ Start Type
This field indicates how the Resource is to be released at the end of a Job execution.


Auto：A-AUTO Monitor automatically releases the Resource when the Job has ended.

Manual：Use the Utility to release the Resource when the Job has ended.

* Up to 10 Resources can be defined.

3-43

3. Master Files

3.4.3 Job ID Conversion Function(1) Function Overview
For A-AUTO Monitor, Job ID can have a maximum of 8 alphanumeric characters. But by using this function
it becomes possible to specify more than 8 characters, double bytes characters and/or special characters
for Job ID. Job ID using this function is defined in Extended Job Master or Job Name Definition File.

(2) Extended Job Master
Job ID Conversion function is defined in Extended Job Master as follows.
① Select "Enable Job Name Converter"② Job ID：This is the Job ID that is registered in Network Master and is to be converted using the function.
The file name for the conversion is defined in the Full Path field.
③ Full path：This is the Job file name to be executed in the Server and may comprise
Converted Job ID

The job name that may exceed 8 characters (Max 256 byte)

Available

Special Character, Double byte characters, Space(*)

Character
Full path

When a job is stored in a directory other than the one specified by
NJP_TEMPSCRIPT or NJP_PRIMSCRIPT* For A-AUTO for UNIX, blank can be included in the Job name if the version is v5007 or later. If a blankexists in the Job name, enclose the Job name in double quotation (" ").
(3) Job Name Definition FileJob Name Definition file is defined in the following format. (When you define the system parameter
ARMT_LOCALINFO to 1 in Remote Job Execute Function, you must use Job Name Definition file for thisfunction)
 Definition Format in Job Name Definition file.
Network ID：
Job ID① = new Job ID②①This is the Job ID that is registered in Network Master and is to be converted using the function.
② The actual name of the Job to be executed and may comprise
Converted Job ID

Up to 256 byte

UsableSpecial characters, double byte characters, blanks(*)

characters
Full path

When a file is stored in a directory other than one specified by NJP_TEMPSCRIPT
or NJP_PRIMSCRIPT* For A-AUTO for UNIX, blank can be included in the Job name if the version is v5007 or later. If a blank
3-44

3. Master Files

exists in the Job name, enclose the Job name in double quotation (" ").
■ In the case of A-AUTO for UNIX, file name is
System Parameter, "AUTODIR"＋"JOBNAMETB"
Example) In the case AUTODIR = /home/auto→/home/auto/JOBNAMETB【Definition example】
NETNAME:JOBNAME = new_jobname
TESTNET:TESTJOB = /full/path/ok
TESTNETB:TESTJOB = UpdateProcess■ In the case of A-AUTO for Windows, file name is
System Parameter, "AUTODIR"＋"JOBNAMETB"
Example) In the case AUTODIR = c:\bsp\AUW→

c:\bsp\AUW\JOBNAMETB【Definition example】[NETNAME1]JOBNAME = new_jobname.bat[TESTNET]TESTJOB = c:\full_pass_ok\new_jobname2.bat[TESTNETB]TESTJOB = UpdateProcess.bat(4) System Parameter setting
To enable Job ID Conversion function, the following system parameter must be defined.
This system parameter can be modified using A-AUTO/Web client.

NJP_JOBNAMEON
The installation default value is 0, which indicates that Job ID Conversion function is inactive. A value of 1
indicates that the function is enabled. Specify 1 to use this function.

3-45

3. Master Files

3.5

Annual Holiday Master
Annual Holiday Master stores the Annual Holiday information.
A user can register, update, delete or search the Annual Holiday information in the Annual Holiday Masterusing A-AUTO/Web client. The purpose of Annual Holiday Master and the items to be defined aredescribed below.

3.5.1 Purpose
Annual Holiday is one of the considerations when scheduling applications in A-AUTO for UNIX/Windows.
A-AUTO system uses the Holiday Master to determine whether a calculated schedule date is a Holiday ornot.
In the Annual Holiday Master, holidays that fall on fixed calendar dates each year such as the National
holiday or Anniversary of foundation are defined. The Annual Holidays defined in this master are updated
automatically into a Holiday Table by the Auto Scheduling Function. Also in “Detail” pane, [Substituted if
falls on a Holiday] attribute may be defined so that if the defined holiday falls on Sunday, the following
Monday will become a holiday. Holidays that do not fall on fixed calendar dates each year have to be
defined in the “Holiday Detail” pane of Holiday Master screen.
The information of Annual Holiday may be included and used in multiple Holiday Tables in Holiday Master.
An Annual Holiday cannot be deleted if it is used in any Holiday Table.

3.5.2 Items to define
The items to be defined in Annual Holiday Master are described below.

(1)"Annual Holiday Detail" window① DateThe Date of the Annual Holiday to be defined. An Annual Holiday is a holiday that falls on a fixed calendar
date each year

3-46

3. Master Files② CommentThis field is for the comment or explanation of the Annual Holiday. Comment may be defined up to a
maximum of 50 characters.

③ Substituted if falls on a Holiday
If an Annual Holiday falls on a Sunday and Sunday is defined as a Weekly Holiday, selecting "Substituted if
falls on a Holiday" check box will shift the Annual Holiday to the next day. (Substitution will not occur if
Sunday is not defined as a Weekly Holiday) This "Substituted if falls on a Holiday" can be applied to each
Annual Holiday individually.
Note
Substitution of holiday may be effective only when Sunday is defined as a Weekly Holiday.

3-47

3. Master Files

3.6

Holiday Master
The Holiday Master stores defined holiday information. Holiday information can be added, changed,
deleted, and searched using A-AUTO/Web client.
The following are the role of Holiday Master and items that can be defined.

3.6.1 Purpose
Holiday Master manages the holiday information required for Auto Scheduling. Holidays represent the daysof no business operation. A-AUTO for UNIX/Windows generates Network Schedules by referring to defined
Schedule Pattern (described later) and Holiday information.
In the Holiday Master, there are fixed date and non-fixed date Holiday information.

A fixed date holiday

refers to a holiday that falls on the same calendar date each year while a non-fixed date holiday refers to aholiday that does not fall on the same calendar date each year.
Fixed date holidays are updated automatically into a calendar when Auto Scheduling facility is executed.
Weekly Holidays and Annual Holidays (to be defined in Annual Holiday Master) fall into this holiday type.
Non-fixed date holidays have to be set manually. To define a non-fixed date holiday, please double-click on
the calendar date in "Holiday Control" pane of Holiday Master Window. Non-fixed date holidays will have tobe defined again in the next calendar year.

3.6.2 Items to define
The items to be defined in Holiday Master are described below.

(1)［Holiday Detail］Tab① Holiday ID
Holiday ID is an identifier for each Holiday Table to be registered. Holiday ID can be any arbitrary namewith the following limitations

3-48

3. Master Files

Up to a maximum of 20 alphanumeric characters without intervening blank. Only special
characters @, $, and # are allowed.
[Example]［○］HOLTBL01、HOL#001［×］HOL 01



Holiday ID must be unique.

② CommentThis field is for the comment or explanation of the Holiday Table. A maximum of 50 characters may be
defined.

③ Weekly Holiday
A Weekly Holiday refers to a holiday that occurs every week. For example, if every Monday is a holiday,
Monday can be defined as the Weekly Holiday by selecting [Mon} checkbox. Weekly Holiday may be
defined for each Holiday Table.

3-49

3. Master Files④ Substituted if falls on a Holiday
If an Annual Holiday falls on a Sunday and Sunday is defined as a Weekly Holiday, selecting "Substituted
if falls on a Holiday" check box will shift the Annual Holiday to the next day. (Substitution will not occur if
Sunday is not defined as a Weekly Holiday.) To use this function, a user must set "Substituted if falls on a
Holiday” attribute of Annual Holidays and also set this attribute for the Holiday Table. In the example that
follows, if May 5 is a Sunday and Holiday Table HOL1 is specified with the "Substituted if falls on a
Holiday" setting, then May 6 will be a holiday. On the contrary, Holiday Table HOL2 is not specified with
"Substituted if falls on a Holiday" setting, then May 6 will not be a holiday.

Annual Holiday
May 3 ： "Substituted if falls on a Holiday"

This annual event isdefined as holiday

Constitution Memorial Day

For all 3 holidays,"Substituted if falls
on a Holiday"
setting is specified.

May 4 ： "Substituted if falls on a Holiday"
This annual event is
not defined as holiday

National Holiday
May 5 ： "Substituted if falls on a Holiday"
Child's Day

HOL1

HOL2



Substituted if falls on a Holiday

Substituted if falls on a Holiday

Annual Holiday
Annual Holiday

May 3 ：Constitution Day

May 3 ： Constitution Day

May 4 ：National HolidayMay 5 ：Child's Day

May 4 ： National Holiday
May 5 ： Child's Day



May
Mon

⑥

Tue

May

Wed

Thu

Fri

Sat

Sun

1

2

③

4

⑤

7

Mon

6

Tue

Wed

Thu

Fri

Sat

Sun

1

2

③

4

⑤

7

Note
“Substituted if falls on a Holiday" attribute is effective only when Sunday is defined as a Weekly Holiday.

3-50

3. Master Files(2)［Holiday Setting］tab① Selected Annual Holiday
This shows the Annual Holidays that are used by this Holiday Table.

② Unselected
This shows the Annual Holidays that are defined in Annual Holiday Master and available for selection.

(3)[Holiday Control] Window
Holiday information generated based on information defined in steps (1) and (2) is displayed in ［Holiday
Control］pane, which is shown on the right side of the window.
That is, the defined weekly and annual holiday information is displayed in calendar shown on the Holiday
Control pane. Non-fixed date holidays can be defined for the Holiday Table by double clicking on thespecific dates on [Holiday Control] pane.


14 months calendar information is kept and displayed.

When registered Holiday ID is displayed in edit mode, calendar is automatically updated based on
holiday information that has been defined earlier. Calendar information is generated for 14 months,
starting from previous month of CPU date.

3-51

3. Master Files

3.7

Schedule Master
Schedule Master stores information regarding schedule patterns, which is the information on how Networks
are to be scheduled.
Schedule information can be added, changed, deleted, and searched using Schedule Definition List
Window of A-AUTO/Web client.
The purpose of Schedule Master and items that can be defined are described below.

3.7.1 Purpose
Schedule Master stores and manages the following schedule information.
 Schedule Pattern Network Schedule(1) Schedule Pattern
Schedule Master stores Schedule Patterns that are referred to by Networks. A Schedule Pattern contains
schedule information that A-AUTO for UNIX/Windows uses to generate an execution schedule for a
Network, i.e. the dates when the Network will execute. Schedule information to be registered includes
frequency of executing the network e.g. daily, weekly, and the reference to Holiday Table.
A Schedule Pattern can be defined by specifying the following items.
Holiday ID

Process PatternReference Date

Standard Processing Date

Process CycleExecution Period

Shift Pattern(2) Network Schedule
A-AUTO for UNIX/Windows manages Network information and Schedule Patterns separately. The
information of Networks is stored in Network Master and the information of Schedule Patterns is stored in
Schedule Master. To generate an execution schedule for a Network, i.e. the dates when the Network will
execute, the Network has to be associated with (linked to) one or more Schedule Patterns. The execution
schedule generated is called Network Schedule. Schedule Master information and Network Schedule
Master information are stored and managed in the same physical file.

3-52

3. Master Files

3.7.2 Items to define
The items that can be defined in Schedule Master are described below, except items ⑨ ‘Irregular’ and ⑩‘Execution ID’ which can be defined at the linking of a Network to Schedule Pattern(s).

(1)［Schedule］ tab① Schedule ID
Schedule ID is an identifier given to a Schedule Pattern. A user must define Schedule ID in compliancewith the following naming convention.
Up to a maximum of 20 alphanumeric characters without intervening blanks. Only special
characters @, $, and #, are allowed.
[Example]［○］ HOLTBL01 , S#001［×］SCHE01

Schedule ID must be unique.

② CommentThis field is for comments or description of the Schedule Pattern. Up to a maximum of 50 characters may
be defined.

③ Holiday ID
Specify the Holiday ID of the Holiday Table to be used for Network Schedule generation. Click on SelectHoliday button to select an existing Holiday Table. Otherwise, click on [Holiday Definition] button to define a
new Holiday Table. Please refer to "3.6.2 Items to define" for details.

④ Process Pattern
There are two types of Process Patterns.
3-53

3. Master Files

CalendarThis Process Pattern treats the date specified as the actual date in the calendar. The date may thenbe adjusted according to the Holiday Table and Shift Pattern given, described in more detail below.

Working Day
This calculates the date using working days in the calendar and a Reference Date. Working days arecomputed based on holidays in the Holiday Table. The schedule is computed as follows: xx days fromthth
the Reference Date(④), excluding Holidays. In the below example, the 5 Working Day is the 8 ofCalendar Date.
Differences between Calendar Date and Working Day
Calendar Date

1

2

Holiday
Working Day

Reference

3

4

H

H

1

Date

3-54

5

6

7

8

9

2

3

4

5

6

3. Master Files⑤ Reference DatethReference date means closing date of a month. For example, if closing date of payroll system is 20 andfiscal month starts 21st, Reference Date is 20.
Reference Date can be specified by date or week.
Specifying by dateSpecify a date between ‘01’ and ‘31’.
If specified date does not exist in the month, end of month is assumed.
If end of month is a closing date, specify ‘EOM’.

Note‘31’ and ‘EOM’ are treated as the same. Both are shown as ‘Last Day’ in later display.

Specifying by day of week
Specify a day of a week in a month, first Monday of the month for example. Week number is specified
as 1st week to 4th week or ‘The Final’ (last week).



Week number
1st week: 1st to 7th day in a month; 2nd week: 8th to 14th day in a month
3rd week: 15th to 21st day in a month;

4th week: 22nd to 28th day in a month

Last week: from Last day to – 6 from last day【Example 1】 When 1st Monday is specified as Reference Date
May
April

S M T W T F
S
1
3
4
5
6
7
2
8 9 10 11 12 13 14
15 16 17 18 19 20 21
22 23 24 25 26 27 28
29 30 (1) (2) (3) (4) (5)S M T W T F(29)(30) 1 2 3 4
7 8 9 10 11
6 ⑦
13 14 15 16 17 18
20 21 22 23 24 25
27 28 29 30 31

S
5
12
19
26

Reference Date in April is April 2nd. Reference Date in May is May 7th.
【Example 2】 When last Thursday is specified as Reference Date
May
April

S M T W T F
S
1 2 3 4 5 67
8 9 10 11 12 13 14
15 16 17 18 19 20 21
22 23 24 25 26
26 27 28
29 30 (1) (2) (3) (4) (5)S M T W T F(29)(30) 1 2 3 4
6 7 8 9 10 11
13 14 15 16 17 18
20 21 22 23 24 25
27 28 29 30 31
31

Reference Date in April is April 26th. Reference Date in May is May 31st.

3-55

S
5
12
19
26

3. Master Files

A month to a Reference Date is called Fiscal month. In above example 1, from April 3rd to May 7th is
Fiscal month May.
Difference between calendar month and fiscal monthFiscal month starts 21st and ends 20th.
Reference Date: 20

Fiscal month starts 21st and ends 20th.
Aug

Sep

1

31 1

Reference Date: 5

31 1

20 21

Sep

30

20 21

Oct

20 21

Nov

Dec

Fiscal month starts 6th and ends 5th.
Aug

Sep

1

31 1
5 6

Oct
31 1
5 6

Sep

Reference Date: 1st Monday

Nov

30 1
5 6

Aug

30
5 6

Oct

Nov

Dec

Fiscal month starts 1st Tuesday ends 1st Monday.
Aug

1

Sep
31 1

6 7

Aug

Nov

30 1

20 21

Aug

Oct

Oct

Nov

30 1
3 4

Sep

31 1
1 2

Oct

30
5 6

Nov

Dec

⑥ Process Cycle Process Cycle defines the processing frequency of a Network, for example, daily,
weekly, monthly. There are different Process Cycle options available with A-AUTO for
UNIX/Windows. A-AUTO for UNIX/Windows computes schedule dates for a Network based on theselected Process Cycle as well as other schedule information.
⑦ Execution Period
Execution Period allows a user to limit the scheduling of a Network to certain days within a monthor certain months within a year. A-AUTO for UNIX/Windows decides whether a Network isscheduled on the computed date based on the defined Execution Period as well as otherschedule information. Values that can be defined differ depending on the Process Cycle asfollows.
When the Process Cycle is 'Daily',
Execution Period is the days within a month to include a Network for scheduling. Specify a value from"01" to "31".



If the Process Cycle is other than 'Daily',
Execution Period is the months within a year to include a Network for scheduling. Specify a value
3-563. Master Filesfrom "01" to "12".

⑧ Shift Pattern
When Process Pattern is Calendar, Shift Pattern refers to how the schedule of a Network is to be handled
when its schedule date falls on a holiday, as determined in Holiday Table. The schedule of a Network is
generated based on the other schedule information described above.
When Process Pattern is Working Day, Shift Pattern refers to how the Reference Date is to be handled
when it falls on a holiday, as determined in Holiday Table.
Types of Shift Pattern
CalendarWorking Day

Schedule date falls on a holiday

Reference Date falls on a holiday

Do not process

Network is not executed if it falls on a holiday―

The Day Before

Execution date is shifted to a working day

Reference Date is shifted to a

before the holiday

working day before the holiday.

Execution date is shifted to a working day

Reference Date is shifted

after the holiday

working day after the holiday

Execution date is shifted to the next day if theReference Date is shifted to thenext day is a working day. Otherwise,

next day if the next day is aschedule it to the last working day before theworking day. Otherwise,

holiday.

Reference Date is shifted to theProcess Pattern

Shift Pattern

The Day After

to a

After: Before if 2-day
offlast working day before theholiday.
After: Before if 3-dayoff

If there are three consecutive holidays fromIf there are three consecutive

the schedule date, shift it to the last working

holidays from the Reference Date,day before the schedule date. Otherwise,

shift it to the last working day

shift it to the next working day after the

before the Reference Date.

schedule date.

Otherwise, shift it to the next
working day after the Reference
Date.

On the day

Execute Network even on holiday

Does not shift reference Date

* Definitions of 2-day off/3-day off
2-day off：Two holidays in a row, starting from the Schedule date/Reference date.
3-day off：Three holidays in a row, starting from the Schedule date/Reference data.

3-57

3. Master Files⑨ Irregular
If a Network has no specific processing frequency, or the Process Cycle is yet to be decided, ‘Irregular’
option may be selected instead of linking the Network to a Schedule Pattern. If Irregular is checked,
Execution ID (explained in ⑩) is set to "0" automatically.

⑩ Execution ID
Execution ID is used to divide Networks into groups. Networks may then be selected as a group using thisExecution ID during scheduling. For example, if Execution IDs are specified for Finalized utility, asvsfin,
only Networks with specified Execution IDs are extracted for execution. Execution ID can be specified bysingle-character code identifier from 1 to 9 or from A to Z. ‘0’ is assigned automatically if Irregular scheduleis checked.

3-58

3. Master Files(2)［Standard Processing Date］ tabStandard Processing Date
Standard Processing Date is used to define from which date onward the scheduling of a Network may
begin. A-AUTO for UNIX/Windows computes the dates on which a Network is to be scheduled based onStandard Processing Date and Process Cycle as well as other schedule information. There are three typesof format for defining Standard Processing Date.
Specify in YYYY/MM/DD format
This format is available only when 'Calendar' is specified for Process Pattern.
However, this format cannot be selected when the Process Cycle is either 'Weekly' or 'Biweekly'.

Specify in YYYY/MM/WW/DD of the week format
This format can be specified when Calendar is specified for Process Pattern and the Process Cycle isother than ‘Daily’ or ‘at intervals of n days’.

Specify in Year, Fiscal month, and ＋－ day format
This format can be specified when Working day is specified for Process Pattern.
【Example】 Working Day of June 2001 (Reference Date = 25)
May 2001 June 2001
Date

24

25

26

Executing dateSpecify ＋or －

27

28

H
-2

-1

+1

+2

29

30

H

H

1

2

…

+3

+4

…

Specify +1 for the first Working Day of the Fiscal month. Specify -1 for the last Working Day of the
Fiscal month. Holidays are ignored.

3-59

3. Master Files【 Example 】 +/- of Working Day of June 2001(Reference Date = 25)(Monthly schedule ・Mainframe compatible mode)
May 2001 June 2001
Date

25

26

27

Executing dateSpecify ＋or －

July
28

…

23

24

25

+2

…

-3

-2

-1

26

27

H
-

+1

In Monthly schedule・Mainframe compatible mode, if you specify "-1", the Reference Date of June will
be become Standard Processing Date.



Week number
1st week: 1st to 7th day in a month; 2nd week: 8th to 14th day in a month
3rd week: 15th to 21st

day in a month;

4th week: 22nd to 28th day in a month

5th week:29th to 29th + 6 day in a month; Last week: from Last day to – 6 from last day【Example 1】When first Monday is specified as Reference DateApril

S M T W T F
S
1 2 3 4 5 67
8 9 10 11 12 13 14
15 16 17 18 19 20 21
22 23 24 25 26 27 28
29 30 (1) (2) (3) (4) (5)May

S M T W T F(29)(30) 1 2 3 47
6 ⑦
8 9 10 11
13 14 15 16 17 18
20 21 22 23 24 25
27 28 29 30 31

S
5
12
19
26

Reference Date in April is April 2nd. Reference Date in May is May 7th.
【Example 2】When last Thursday is specified as Reference Date
May

April

S M T W T F
S
1 2 3 4 5 67
8 9 10 11 12 13 14
15 16 17 18 19 20 21
22 23 24 25 26
26 27 28
29 30 (1) (2) (3) (4) (5)S M T W T F(29)(30) 1 2 3 4
6 7 8 9 10 11
13 14 15 16 17 18
20 21 22 23 24 25
27 28 29 30 31
31

Reference Date in April is April 26th. Reference Date in May is May 31th.

3-60

S
5
12
19
26

3. Master Files

A month to a Reference Date is called Fiscal month. In above example 1, from April 3rd to May 7th is
Fiscal month May.
Difference between calendar month and fiscal monthFiscal month starts 21st and ends 20th.
Reference Date: 20

Fiscal month starts 21st and ends 20th.
Aug

Sep

1

31 1

Reference Date: 5

31 1

20 21

Sep

30

20 21

Oct

20 21

Nov

Dec

Fiscal month starts 6th and ends 5th.
Aug

Sep

1

31 1
5 6

Oct
31 1
5 6

Sep

Reference Date: 1st Monday

Nov

30 1
5 6

Aug

30
5 6

Oct

Nov

Dec

Fiscal month starts 1st Tuesday ends 1st Monday.
Aug

1

Sep
31 1

6 7

Aug

Nov

30 1

20 21

Aug

Oct

Oct

Nov

30 1
3 4

Sep

Oct

3-61

31 1
1 2

30
5 6

Nov

Dec

3. Master Files* Fiscal month schedule・Mainframe compatibility mode(This function is available on V710Lv13 or later (for Windows) and V710Lv11 or later (for UNIX/Linux).)
The calculation method of the reference date which is specified by Year/Month/+- is the same as A-AUTO
for Mainframe.

The following procedures explain how to switch to this function mode.
1.

Please close the Network Definition List Screen if it is displayed.

2.

You should modify the following entry of Monitor Setting; change the setting to Monthly Schedule
Mainframe Compatibility mode, COMPAT_WORKING_DAY, to 1. About details on Monitor Setting,please refer to “9.3.1 Setting of Monitor”. About the details of Monthly Schedule Mainframe
Compatibility mode, please refer to “auto_sysconf parameters” of System Administrator’s Guide.

3.

Reconnect A-AUTO/AP Server to A-AUTO Agent again to reflect the new setting of Monitor.
(1)"Agent List" screen will be displayed by clicking "Agent" on the list menu of System Management
Windows.
(2)To select the A-AUTO Agent whose settings for A-AUTO Monitor have been modified. Then, select"Disconnect" from toolbar and to click "Execute" button.
(3) Select "Connect" and to click "Execute" button.

4.

You are now on Monthly Schedule Mainframe Compatibility mode.
Monthly Schedule Mainframe Compatibility mode will be applied to any schedules which areregistered from hereon.
* If you want to apply Monthly Schedule Mainframe Compatibility mode to the schedules that havebeen registered before, you should execute remakesche utility or update the schedules using
Schedule Definition List Windows.
(About remakesche utility, please refer to "6.1 Auto Scheduling Function".)3-62

3. Master Files

3.7.3 Process Pattern and Schedule Date
For Process Pattern specified as Calendar, the Shift Pattern affects schedule dates. For this Process
Pattern, schedule dates are computed based on Process Cycle and Execution Period.
If a computed Schedule Date falls on a holiday defined by Holiday Table, the Schedule date is shiftedbased on the defined Shift Pattern.
For Process Pattern specified as Working Day, the Shift Pattern affects the Reference Date. For thisProcess Pattern, schedule dates are computed based on Process Cycle, Execution Period and Reference
Date. If the Reference Date falls on a holiday defined by Holiday Table, the Reference Date is shiftedbased on defined Shift Pattern.
【Example 1】Shift Pattern when Calendar is defined for Process Pattern

Process Pattern ： Calendar

Standard Processing Date：27th

Process Cycle： Monthly

Shift Pattern：The Day After

Calendar Date

26

Holiday information

Execution Period：From January to December

27

28

H

H

29

30

Following month/1

2

3

4

･･･

H

on Holiday ID○

Schedule Date

As shown in the above example, if the 27th falls on a holiday, the Schedule Date is shifted to the 29th inaccordance with the Shift Pattern. This shifting also applies to exclusion schedule setting, which is
described later. (Refer to "5.9.6 About Exclusion Schedule Setting")【Example 2】Reference Date Shift Pattern when Working Day is specified for Process Pattern

Process Pattern：Working Day

Standard Processing Date ：+5 days

Process Cycle：Monthly

Execution Period：From January to December

Shift Pattern：After: Before if 2-day off

Calendar Date
Holiday information

26

27

28

H

H

29

30

Reference Date：27th

Following month/1

2

3

H

on Holiday ID
Reference Date
Working Day

4

○
1

2

Schedule Date

3-63

3

4

5

･･･

3. Master Files

As shown in the above example, if the 27th falls on a holiday, the Reference Date is shifted to the 26th inaccordance with the Shift Pattern. The 29th becomes the 1st Working Day and the 5th Working Day, whichis the 3rd of the following month becomes the Schedule Date. This shifting also applies to exclusion
schedule setting, which is described later. (Refer to "5.9.6 About Exclusion Schedule Setting")【例 3】処理パターンを「営業日」にした場合の基準日のシフト（月度スケジュール・メインフレーム互換モード）
Process Pattern：Working Day

Standard Processing Date ：- 1 day

Process Cycle：Monthly

Execution Period：From January to December

Shift Pattern：On the Day

Reference Date

：27th

30

2

Calendar Date

26

Holiday information

27

28

H

H

29

Following month/1

3

4

･･･

H

on Holiday ID○

Reference Date
Working Day

-1

1

2

3

4

5

Schedule Date

As shown in the above example, if the 27th falls on a holiday, the Reference Date is shifted to the 26th inaccordance with the Shift Pattern. The 29th becomes the 1st Working Day and the -1th Working Day,
which is the 26th of the month becomes the Schedule Date. This shifting also applies to exclusion
schedule setting, which is described later. (Refer to "5.9.6 About Exclusion Schedule Setting")

3-64

3. Master Files

3.8

Network Schedule Master
Network Schedule Master stores the association information between Networks and Schedule patterns,
and the resulting Network Schedules generated. A Network Schedule contains the dates of when a
Network is scheduled to execute.
Network Schedule Master can be added, changed, deleted, and searched using Network Schedule
Windows of A-AUTO/Web client.
The purpose of Network Schedule Master and the items that can be defined are described below.

3.8.1 Purpose
When a Network is linked or associated with one or more Schedule Patterns, A-AUTO for UNIX/Windows
automatically generates a Network Schedule for the Network, i.e. the dates when the Network will execute,based on schedule information of the Schedule Patterns. The computed dates of a Network Schedule may
be displayed on [Network Schedule] Windows. Network Schedules may be generated or maintained by oneof the following operation procedures.

①

Associate Network with Schedule Pattern(s)②Assign a execution date to a Network③

Modify a Network Schedule that is already created① Associate Network with Schedule ID
By associating a Network with one or more Schedule Patterns, a Network Schedule will be generated. The
Network Schedule generated in this case will be a one-year schedule (starting from the date the Network
Schedule was generated) and is stored in Network Schedule Master. For example, an operator associatesa Network named GYOUMUA with Schedule Pattern, DAYLYE1 on April 5th, 2004. As a result, a Network
Schedule for GYOUMUA is automatically generated for the period from April 1st, 2004 to March 31st, 2005
in accordance with Schedule Pattern DAYLYE1.
The Network Schedule that is generated by the association of a Network and its Schedule Pattern(s) may
be updated by executing Auto Scheduling facility. Auto Scheduling facility uses the information of theassociated Schedule Patterns when updating the Network Schedule.

② Assign an execution date to a Network
Without associating with a Schedule Pattern, schedule or execution date(s) can be manually assigned to
the Network Schedule of a Network. This type of execution schedule is called Irregular Schedule.
Because there is no Schedule Pattern defined, Auto Scheduling facility cannot update such Network
Schedule. To define an Irregular Schedule for a Network, select the Network and check [Irregular] checkbox on the [Network Schedule-edit] dialog of A-AUTO/Web client.
Then, double click on those dates of the calendar for which the Network is to be scheduled for execution.

3-65

3. Master FilesThe highlighted dates on the calendar indicate that the Network will be scheduled for execution. Click[Apply] button, then Network Schedule is added in Network Schedule Master.

③ Modify a Network Schedule that is already created
Operator can modify an existing Network Schedule by using either Network Schedule List pane or Network
Schedule dialog.
There are two types of Schedule Modification.
Adding, deleting, or moving a Schedule date
Schedule date can be added, deleted, or moved using either Network Schedule List pane or the
Calendar on Network Schedule dialog of A-AUTO/Web client.
There are differences in operation between using Network Schedule List pane and using the
Calendar of Network Schedule dialog.


If a Network schedule is modified using Network Schedule dialog, the Network Schedule will be
updated by Auto Scheduling facility to reflect the latest change.
Therefore, if the operator does not want to execute Auto Scheduling, he/she must update
schedule using Network Schedule List pane.



If Network Schedule List pane is used, update is done in one single operation. On the other hand,
update using Network Schedule dialog requires several steps. The operator must first click a
Network ID, perform the update and then click ［Apply］button. Several changes can be made toa Network Schedule before clicking [Apply] to confirm modifications.



Change a specific Network attribute for a specific schedule date
Network attributes of a Network can be modified for a specific schedule date using [Daily
Network-edit] dialog. For example, an operator can change the Start Time of a Network only for a
specific schedule date.

3-66

3. Master Files

3.8.2 Items to define
Network Schedule information that can be defined or modified are listed below.

(1)

Network Schedule window① Irregular
If a Network has no regular processing frequency, or the Process Cycle is yet to be decided, ‘Irregular’
option may be selected instead of linking a Network to a Schedule Pattern. If Irregular is checked,
Execution ID (explained in ②) is set to "0" automatically.
② Execution ID
Execution ID is used to divide Networks into groups. Networks may then be selected as a group using thisExecution ID during scheduling. For example, if Execution IDs are specified for Finalized utility, asvsfin,
only Networks with specified Execution IDs are extracted for execution. Execution ID can be specified bysingle-character code identifier from 1 to 9 or from A to Z. ‘0’ is assigned automatically if Irregular scheduleis checked.
③ Selected Schedule ID
This lists the Schedule IDs that are associated with the selected Network.
If more than one Schedule ID is assigned, execution schedule dates generated for each Schedule pattern
will be merged to form the Network Schedule for the Network.
④ Schedule ID
This lists Schedule IDs that are available for association with the Network.
⑤ Exclusion Schedule setting
Exclusion Schedule is used to exclude or remove certain execution schedule dates generated by theselected Schedule Patterns (without Exclusion Schedule option). Schedule dates generated by the
Schedule Patterns without Exclusion Schedule option that match the execution schedule dates generated
by Schedule Pattern with Exclusion Schedule option are excluded. All Schedule IDs except irregular
Schedule can be selected as Exclusion Schedule.

3-67

3. Master Files

3.9

Daily Network Master
Daily Network Master stores Network information for each date that a Network is scheduled to execute, as
reflected in the Network Schedule of the Network. Daily Network Master can be added or updated from
Network Schedule Master Windows and updated only in Daily Network Master window of A-AUTO/Web
client.
The purpose of Daily Network Master and the items that can be added/updated are described below.

3.9.1 Purpose
In day to day operation, there may be instances where execution conditions of a Network need to bechanged temporarily. However, changing the Network Master directly has the following implications:

If changes are temporary and are to be effective for some future execution dates of a Network,changes cannot be made immediately. Without Daily Network Master, changes have to bemade just before the actual date of execution.



After the temporary changes to Network information, problem may arise if a user forgets torevert the temporary changes to their original definitions.

Daily Network Master allows the operator to temporarily change Network information of a specific Networkof a specific date without changing the original master information in the Network Master.

3-68

3. Master Files

3.9.2 Items to define
The following Network attributes can be changed in the Daily Network Master. For detailed information oneach item, please refer to "3.1.2 Items to define" (Network Master) and "3.7.2 Items to define" (Schedule
Master).
(1) Execution ID(2) Parallel run attribute(3) Preceding Network ID(4) Input Data Wait(check box only)(5) Monitor On(6) Number of Resouces(check box only)(7) Job Execution User ID(Set it only in Network Attribute 1)(8) Start Delay Watch Time(check box only)(9) End Delay Watch Timecheck box only)(10) Plug-in Before Start(check box only)(11) Plug-in After End(check box only)(12) Max Executing Time(13) Response to Max Time
(14) Start Tme(15) User Information(16) System Qualifer(17) Class(18) Hold Code(19) Priority(20) Time Interval End Time(21) Interval(min)(check box only)

Notes
Input Data Wait, Monitor On, and Resource attributes can only be changed if those attributes are defined in
the Network Master. Operator can remove the check (tick) from the Start Time Limit, End Time Limit,
Plug-in Before Start, and Plug-in After End attributes if those attributes are defined on the Network Master.
Network attributes that are not listed above cannot be modified from Daily Network Master.
To modify such attribute, the operator must modify the Network Master.

To stop the execution of a Network temporarily, for example for rerun operation, it can be done by storing adummy script in the path specified in the [Job Library Detail] dialog of Monitor Management Windows.

3-69

3. Master Files

3.10 Event Management Master
Event Management Master stores the events that are to be monitored on each server and corresponding
actions to be taken when these events are detected.

3.10.1 Purpose
Event Management allows a user to define events to be monitored on each server and the corresponding
actions to be taken when such events are detected. A collection of events and their corresponding actions
is managed as a unit or group called Work. Each unit of Work can have up to one hundred Event IDs andup to one hundred Action IDs.

Event Management performs the following functions.
(1) Link with Input Data Wait attribute
If “Input Data Wait Reset Event” option is selected for a Data Wait in Data Wait Master, EventManagement will monitor the event defined for the Data Wait. The information defined for “Input Data Wait
Reset Event” such as event type, the server where the event is to be monitored and event data is stored inthis master.

(2) Monitor events
Event Management also monitors events of Work units that are registered directly into EventManagement Master. For example, it can be used to monitor if a file, which is to be used by a Network, iscreated.
(3) Detect events and automatically run an action program
When an event is detected or has happened, it can trigger an action to perform certain tasks such as
executing another program. Such action or task may not necessarily be related to application runningon A-AUTO.

3-70

3. Master Files

3.10.2 Items to define
The following items can be defined in Event Management Master.

(1)［Basic Settings］tab① Work ID
Work ID identifies a unit of Work, which is a collection of events and their corresponding actions. More than
one event/action can be specified for one Work unit. Work ID must be less than or equal to 13 characters,
and must not include special symbols(<>,'"&%\+#) or blank.
Work IDs that begin with prefix $D are all regarded as events associated with Data Wait ID.

② CommentThis field is for comment or description of the Work unit.
Comment must be less than or equal to 32 characters and must not include special symbols(%, &).

③ Monitoring
Specify whether monitoring for the Work unit is to be activated.

④ Start Time
Specify the time to start monitoring for the events in the Work unit.
The monitoring will not begin until the specified time passes.

⑤ End Time
Specify the time to stop monitoring for the events in the Work unit.

⑥ Action execution
Valid ：Specify whether Action Execution for the Event is to be activated Valid indicates that the action is
to be executed when the Work completes.
Invalid ：Indicates that Action Execution for the Event is not activated i.e. no action is executed when theWork completes.

3-71

3. Master Files⑦ Action execution pattern
Specify whether to run the Action each time the Work completes or only when the Work completes for the
first time.
Every ：The Action is executed every time when the Work ends.
First time ：The Action is executed when the Work completes for the first time only.

3-72

3. Master Files(2)［Event］ tab① Event ID
Event ID is an identifier for an Event. A Unique ID is automatically generated and assigned to each Event.

② CommentThis field is for comment or description of the Event. Comment must be less than or equal to 32 charactersand must not include special symbols(%, &).

③ Type of Event
Select the type of the Event from the following.
1.

Job Event
A-AUTO/Event will monitor for the termination of a process whose name is given inProcess Name field of Event Detail information.

2.

Message Event
A-AUTO/Event will monitor for an output message that has a Message ID matching the ID
field of Event Detail or that has a message text matching the specified String of Event
Detail.

3.

File Event
A-AUTO/Event will monitor for creation or update of a file whose file name is given in File
Name field of Event Detail information.

4.

Application Event
This event is generated by an application.
A-AUTO/Event will monitor for Application Event ID and Event Parameter that match thevalues specified in Application Event ID and Application Event Parameter of Event Detail
information.

④ Event occurring computer name
A-AUTO/Event Agent Name where the event is to be monitored. A-AUTO/Event Agent must be registeredin [A-AUTO/Event settings] tab of Agent management Windows.

3-73

3. Master Files⑤ Process Name
Specify name of the process when the Job Event is to be monitored, up to a maximum of 63 alphanumericcharacters.

⑥ File Name
Specify the name of the file when the File Event is to be monitored, up to a maximum of 63 alphanumericcharacters.

⑦ ID
Specify the Message ID when the Message Event is to be monitored, up to a maximum of 63 alphanumericcharacters.

⑧ UNIX system log offset.
Specify this item when Message Event is to be monitored and message text is to be matched. Specify theUNIX system log offset where the string to be matched is located. The log offset is specified as numberthat indicates the position from the beginning (the first position of the log is 0).

⑨ Message
Specify the alphanumeric string to match. The total length of the string and the offset must be less than 18
characters.

⑩ Application event ID
Specify the Application Event ID when the Application Event is to be monitored, up to a maximum of 63
alphanumeric characters.

⑪ Application event parameter
Specify the Application Event parameter when the Application Event is to be monitored, up to a maximumof 20 alphanumeric characters.

3-74

3. Master Files(3)［Action］ tab①

Action ID

Action ID is an identifier for an Action or task. A Unique ID is automatically generated and assigned to each
Action.

② CommentThis field is for comment or description of the Action. Comment must be less than or equal to 32 charactersand must not include special symbols(%, &).

③ Action Type
Select the type of the Action from the following.
1.

Job Execution
After confirming that the Work has completed, the Job or program specified by [Action
Execution Information] is executed on the specified computer. Parameter will also be
passed to the Job or program, if specified.

2.

Message Output
After confirming that the Work has completed, the message specified by [Action Execution
Information] is displayed on the console of the computer executing the Action.

3.

Send Mail
After confirming that the Work has completed, a mail will be sent in accordance with [SendInformation Parameter File] of [Action Execution Information].

4.

Send Start Command
After confirming that the Work has completed, Start Command for the Network, specified
by [Action Execution Information], will be issued to A-AUTO Monitor.

④ Computer Name
A-AUTO/Event Agent Name where the action is to be executed. A-AUTO/Event Agent must be registeredin [A-AUTO/Event settings] tab of Agent management Windows.

3-75

3. Master Files⑤ Job Name
This field is available only when Job Execution is specified as Action Type. Specify the name of the Job(Shell script, Batch file) to execute, up to a maximum of 256 alphanumeric characters.

⑥ Parameter
This field is available only when Job Execution is specified as Action Type. Specify the Parameter, up to a
maximum of 256 alphanumeric characters.

⑦ Message
This field is available only when Message Output is specified as Action Type. Specify the message in lessthan or equal to 256 alphanumeric characters.

⑧ Send Information Parameter File
This field is available only when Send Mail is specified as Action Type. Specify the Send Information
Parameter File in less than or equal to 256 alphanumeric characters.

⑨ Network Name
This field is available only when Send Start Command is specified as Action Type. Specify the Network
Name in less than or equal to 256 alphanumeric characters.

3-76Overview of A-AUTO for UNIX/Windows

4 A-AUTO/Web Client
4.1

A-AUTO/Web Client
A-AUTO/Web Client (refer to as Web Client) is the GUI of A-AUTO for UNIX/Windows that runs on Web
browser.
The information managed by Server such as Master File Information, System Information, Monitoring
Information of A-AUTO Monitor, may be displayed on the Web Client.
Note on operation
Depending on the availability of memory, A-AUTO/Web Client may take some time to display screens.
Please perform operations on a screen only when it is displayed completely.

4.1.1

Starting A-AUTO/Web Client
To login A-AUTO/Web Client, follow the procedures as described below.
①

Start Web browser and enter A-AUTO/Web Server address.

http://(IP Address or machine name of installation destination of A-AUTO Server)/a-auto
Example 1: Specifying by IP Address
http://192.168.27.140/a-auto
Example 2: Specifying by machine namehttp://BSP00903/a-auto
If you set Web Port number of Web Server to a number other than 80 when you customized the setting
during installation, you need to explicitly specify the port number.
e.g.: Setting 8080 for Web port number
http://127.0.0.1:8080/a-auto

4-1

4. A-AUTO/Web Client②③

Login window is displayed.

Enter User ID and Password, and click [Login].
If the wrong User ID or Password is entered, an error message is displayed on [Login] window.
Enter correct User ID and Password and log in again.

④

If log in is successful, ‘A-AUTO Main’ window is displayed.

4-2Overview of A-AUTO for UNIX/Windows

4.1.2

A-AUTO Main Window
If log in is successful, ‘A-AUTO Main’ Windows is displayed.
A-AUTO Main window includes the following panes and information.

① User ID
The User ID of the current user is displayed. If the expiration date is set for the password, the number ofthe valid days remaining is shown next to the User ID.

② Change Password[Change Password] dialog is displayed when you click on the link.
About the procedures to change password, please refer to “4.3 Change Password”.

③ User Settings[User Settings] dialog is displayed when you click on the link.
About the settings that can be customized for a user, please refer to “4.2 User Settings”.

④ Logout
Click the link to logout.

(1)

Application Monitor① [Create] button
Clicking on this button displays the Application Monitor’s [Settings] dialog for creating a new setting.

② User-defined Setting
A list of Monitoring Settings that the logged-in user has registered is displayed. A specific Setting may bedisplayed on Application Monitor Windows by clicking on the link of the name of a Monitoring Setting. A

4-3

4. A-AUTO/Web Client

Setting may be deleted by clicking the [Delete] icon next to the name of a Monitoring Setting.

③ Common Setting
A list of Monitoring Settings that are common and can be used by all users is displayed.

A specificcommon Setting may be displayed on Application Monitor screen by clicking the link of the name of aMonitoring Setting. A setting may be deleted by clicking the [Delete] icon next to the setting name.

(2)

Application Definition① Monitor Name
A list of Monitor IDs of the A-AUTO Monitors is displayed. Master Management Windows of a specific
A-AUTO Monitor may be displayed by clicking the link of Monitor ID.

(3)

System Management① System Management
System Management Windows may be displayed by clicking the link. For details, please refer to "9 System
Management."② User Management
User Management Windows may be displayed by clicking the link. For details, please refer to Chapter 8‘User Management' in System Administrator's Guide.

③ A-AUTO Monitor
A-AUTO Monitor window may be displayed by clicking the link. For details, please refer to ‘6.8 A-AUTO
Monitor.’4-4

Overview of A-AUTO for UNIX/Windows

4.1.3

Stopping A-AUTO/Web Client
To stop A-AUTO/Web Client, follow the procedures as described below.
①

Close all the Windows except [A-AUTO Main] Windows.

②

Click [Logout] on [A-AUTO Main] Windows.

③

If log out is successful, [Login] Windows is displayed.

④

Click the Close button [X] at the upper-right corner of the browser

4-5

4. A-AUTO/Web Client

4.1.4
(1)

A-AUTO/Web Client Page Layout

Page Layout
Each Windows of A-AUTO/Web Client consists of a List Menu (left side) and a Definition List pane (rightside).

Definition List pane

List Menu

Click on a link or [Create] button of Definition List pane, a detailed Windows is displayed. You may use thisWindows to view the details of an item that has been registered and to perform maintenance on an item.
.
Detailed Window

4-6

Overview of A-AUTO for UNIX/Windows(2)

Definition List Pane
Registered items will be displayed in this pane in list format.
The following functions are available in Definition List pane.

① [Create] button
Click [Create] button to create a new item.

②[Copy] button

Create a new item by copying the information from an existing item. Check the check box of an item in
Definition List pane and click "Copy" button, the information of the selected item will be copied to the newitem. For more information, please refer to "4.1.7 Copy-register Master".

③[Delete] button

Check the check box of an item in Definition List pane and click "Delete" button, the selected item will bedeleted.

④[Valid Date List] button

Check the check box of an item in Definition List pane and click [Valid Date List] button, "Valid Date" dialog
will be displayed. You can view the Valid Dates which are set for the selected Network item.

⑤[Expiry Date Modify] button

Check the check box of an item in Definition List pane and click [Expiry Date Modify] button, you canregister, modify or delete expiry date of the selected Network item.

⑥[Switch] icon

Click "Switch" icon to change the display format of the pane.
4-7

4. A-AUTO/Web Client

The items displayed in list format in the pane will switch to display in flowchart format and vice versa.

⑦[Refresh] icon

Click "Refresh" icon to update the information on the Definition List pane with the latest information from
the Master.

⑧[Search] icon

Search dialog will be displayed by clicking "search" icon.

⑨[Display Settings] icon

Display Settings dialog will be displayed by clicking "Display Settings" icon.
This function allows you to customize the layout of Definition List pane, such as the attributes to display
and column width of each displayed attribute.

⑩ [Menu] icon
Menu dialog of each pane will be displayed by clicking "Menu" icon.

⑪[Help] icon

Help dialog will be displayed by clicking "Help" icon.

⑫ Page Control
Page Control may be used to display a specific page using the page number or change the number of
items that are displayed in one page.

⑬

Column Header of list

Items displayed in the list can be sorted in ascending or descending order of an attribute by clicking thecolumn header of the attribute.

(3)

Page Control
Below is an illustration of Page Control in Definition List pane.

① Result for Display
This shows the total number of items selected for display and the item numbers of the items that are
currently being displayed in the pane.

② Arrow icons
These arrow icons are used to scroll the items displayed in the pane forward by a page, backward by apage, to the first page or last page.
4-8

Overview of A-AUTO for UNIX/Windows③ Number of items to be dispalyed in one page
This is used to set how many items to be displayed in one page.
To change the number of items to be displayed in one page, type the number into this text box and thenclick [Display] button.

④ The Current page number
The current page number will be displayed.
To display a specific page using a page number, type the page number into this text box and then click[Display] button.

(4)

Chart Window
In Network Definition Windows or Network Monitoring Windows, selected Networks or Jobs can bedisplayed in flowchart or list format. When these Windows are displayed in flowchart format, you can use
page drag to move the chart being displayed.
For details of Network information, please refer to "3.1 Network Master" and for details of Network
Monitoring, please refer to "7 Application Monitor".

① Issue Monitor commands
You can issue Monitor Commands in this window. First, select a target Network for the command. Then,
select a command from pull-down menu and click "Execute" button. The selected command dialog will be
displayed.
* The Command pull-down menu is only available in Network Monitoring Windows.

4-9

4. A-AUTO/Web Client② Current Page Position
The current page position of the display is shown by X and Y values. X value shows the vertical scale andY value shows the horizontal scale.
To change the page position to be displayed, type the X and Y values into the text box and then click[Locate] button.

③ Display Magnification
On the right of the toolbar, [100], [50] and [30] buttons represent the display magnification of the flowchart
screen in 100%, 50%, and 30% respectively. To display the flowchart in the desired size, click theappropriate buttons. Alternatively, you may use the magnification pull-down menu to select othermagnification percentage for the flowchart display.

④ Switch
In Network Monitoring List window, the List Menu (on the left-hand side) shows a list of available display
formats; List, Chart and Time Chart. You can switch the display to a desired format by clicking theappropriate display format name in the List Menu.

* For Network Definition Windows, switching the display format is performed by clicking [Switch] icon.

⑤ Chart Editor
You can create a new Network, add a new Job, or modify the preceding relationship between Networks on
the Chart Editor. Creating and setting preceding relationship can be performed by clicking the respective
icons of the Chart Editor.
In addition to the above-mentioned functions, you can set branch of a Job on the chart editor.
* The icons of the Chart Editor are only available in Network Definition Windows.

⑥ Area Search

Area Search enables you to move the position in the flowchart to be displayed on the Windows.
Position in the flowchart can be moved by either dragging the pointer in the Area Search pane using amouse or by clicking the arrow icons on the toolbar.
Type a Network ID in the textbox and click [Search] icon on the toolbar of Area Search pane, the Windows
will display the position of the flowchart with that Network, if found.

(5)

Detailed Window

Detailed Windows of an item will be displayed by clicking [Create] button, [Copy] button, or the link of the
ID of a Master record item. The information of an item displayed on the Windows depends whether the

4-10

Overview of A-AUTO for UNIX/Windows

item is to be created or edited. Clicking [Create] button or [Copy] will display a “Create” detailed Windows
while clicking the link of an item will display [Edit] detailed Windows.
A detailed Windows has the following function.

①[Apply] button

The information of the item on the detailed Windows will be registered or updated by clicking [Apply] button.
When all necessary information for an item has been filled or updated, please click [Apply] Button.

(6)

List Menu
The List Menu is displayed on the left side of A-AUTO/Web Client’s Windows.
The List Menu shows the available functions or display screens for the Windows.

Clicking on a function

name or display screen name will display the appropriate Windows or dialog for the function or display
screen.

4-11

4. A-AUTO/Web Client

(7)

Menu
This dialog will be displayed by clicking [Menu] icon on the toolbar of
Definition List Windows.
It provides auxiliary functions for Definition List Windows and Detailed
Windows. The functions that are provided depend on the items being
displayed on the Definition List Windows. You can specify a date or agroup to filter the items to be displayed the Definition List Windows.
Types of Menu Windows:
Network Monitor Menu, Network Menu, Network Schedule Menu, Daily
Network Menu

4-12Overview of A-AUTO for UNIX/Windows(8)

List Dialog
When you register data in Detailed Windows, clicking on a certain icon may display a list of registered
items for selection, as illustrated in the display below.
Select an item from the list and click [Apply] button. The information of the selected item will be displayedin the text box of the Detailed Windows① Search
Type the search condition into the text box on toolbar and click [Search] button.

The items that match thespecified search conditions will be displayed in list.
Wild Card ("*", "?") can also be used in the search condition.

② Page Control
Page control can be used to specify the number of items to be shown in a page as well as to display thenext or previous page.

(9)

Select ID Windows
This is the Windows to select ID(s) of data in the current Master file or other Master files to be linked to thecurrent item to be registered or edited.

Type the search condition into the search field and click [Search]

button, the items that match the specified search conditions will be displayed in ID list.

4-13

4. A-AUTO/Web Client

Search Field

ID ListThen you open the window of another Master ID, the result of previous searching will be displayed.
Wild Card ("*", "?") can also be used in the search condition.

(10) Maintenance (Register,

Edit,

Delete)Register, edit and delete Master record or data by using the following procedures.
■ Register
・Click [Create] button on toolbar
・ If the information of an existing Master data is to be copied for the new Master record to be created,check the check box of the existing item and then click [Copy] button.
■ Edit・On the Definition List pane, click the link of the ID of the target Master data which you want to modify.
■ Delete
・On the Definition List pane, check the check box of the ID of the target Master data which you want todelete.
・Click [Delete] button on toolbar.

4-14Overview of A-AUTO for UNIX/Windows

4.1.5
(1)

A-AUTO/Web Client Functions

RefreshReread the latest information from the appropriate Master file and display the latest information on the
Windows.
You will use this function when you want to confirm the information of the registered data on the list after
you have modified or added the items.
Click [Refresh] icon on toolbar of the window to perform the refresh.

(2)

Search
You may use this to specify conditions or criteria to select items to be displayed on the list.
Click [Search] icon on the toolbar of the apprpriate Windows to invoke the search function. Type the search
conditions in [Search] dialog displayed and click [Search] button.
If you do not type any search condition, all of the items will be selected and displayed in list window.
If you want to reset all the values that you have typed, please click [Clear] button.

All items that match the specified conditions will be displayed in list window (AND is applied to the specified
conditions).
Search string is sensitive to uppercase and lowercase specifications.
Wild Card ("*", "?") can also be used in the search condition When no wildcard is specified, Search will lookfor exact match.

(3)

Sort
Items displayed in the list can be sorted in ascending or descending order of an attribute by clicking thecolumn header of the attribute.

4-15

4. A-AUTO/Web Client(4)

Display Settings
You can customize the display settings of the items shown in list Windows. Display Setting, whencustomized, applies to your User ID only. The settings will be also reflected in your next log in.
Click [Display Settings] icon on tool bar of appropriate List window that you want to customize.
The [Display Settings] dialog shows the current settings in the list. [Display Items] refers to items to beshown on the list and [Items] refers to items not to be shown on the list. The order in which the items areshown in the [Display Items] is the same order these items will be displayed on List window.
Click on the Left and Right arrows to move the items between [Display Items] (to be shown box) and[Items] (not to be shown box). Similarly, click on the Up and Down arrows to move order of display for theitems in [Display Items].
You can change the display width of the display items. The value for "width" can be specified from 1 to 999(pixels).

Click [Apply] button, the content that you set will be reflected. Click the [Default] button to reset to the initial
settings for the display.

4-16

Overview of A-AUTO for UNIX/Windows

4.1.6

When multiple users use A-AUTO/Web Client
Information on A-AUTO system may be viewed by multiple users. However, users are not allowed to
update or delete the same data at the same time.
For example, while a user is updating GYOUMUE (Network ID) from a client (ACLIENT) and, if anotheruser tries to update GYOUMUE (Network ID) from another client (BCLIENT), an error message will be
displayed and the change or update is abandoned.
If this happens, please try again at a later time.

4.1.7

Copy-register MasterCopy-register Master refers to creating a new Master record by copying the information of an existing(already registered) Master record.
The Master files listed below support Copy-register function. There is an unique item, which is called "KeyItem", in each Master. "Key Item" will not be copied.
For details of items, please refer to "Items to Define" of section "3 Master".
Master Name

Key Item (will inherit from the target Master record
to be copied from)

Network

Network ID, Valid Date(*1)

Network Job

Job Number(*2)

Schedule Master

Schedule ID

Work

Work ID

Extended Job

Job ID*1 When you copy a network ID that has more than one valid date, information of valid date is not copied.
The information for a new Network to be created is copied from the information of the Network which
is displayed in "Network Definition List" Windows.
*2 The target Job to be copied must be an existing Job in the same Network.
How to Copy-register Master(1)Open Definition List window of the appropriate master from List Menu.
(2) Check the check box of the target master record whose information is to be copied and then click [Copy]
button.
The information of the target Master record will be displayed in Detailed Windows of the new Masterrecord to be created. But "Key Items" will be blank.
(Copy-register of a record from Work Master file is different with other master files, In the case of Work
Master, [Create] dialog will be displayed first. Enter Work ID and click [OK] button. The Detailed Windows
will be displayed.)(3)Input "Key Items".

4-17

4. A-AUTO/Web Client(4)Click "Apply" button. If the message is displayed, click [OK] button.
Then, the registration is completed.

4-18

Overview of A-AUTO for UNIX/Windows

4.2

User Settings
Each user can define the contents to be displayed when the user logins to the A-AUTO/Web Client. Beloware explanations of the items that can be defined.

Set items in "User Settings" dialog.
Click [User Settings] on the top of [A-AUTO Main] Windows, "User Settings" dialog will be displayed.

4-19

4. A-AUTO/Web Client

4.2.1

Default Application Page Settings
You can select the initial display pane of the Application Definition Windows and Application Monitor
Windows. Initial display pane for Application Definition is specified in "Default Application Definition" andinitial display pane for Application Monitor is specified in "Default Application Monitor".
Select the initial display pane from select box and then, click [Apply] button. The content will be reflected.

4.2.2

Display Settings of List
The following is the explanation of the items that can be set in [Display List Settings] fields. Set the values
and click [Apply] button. The content will be reflected.

(1)

Number of List Items
Set the number of items to be displayed in a page of each Definition List Windows. Items to be displayed
are segmented into pages according to the specified number. Default value is 20. The number that can be
set is from 1 to 1000.

(2)

Interval to Auto Update Monitor Display
This setting allows you to define the time interval to automatically refresh the Application Monitor display.
The monitoring display will be refreshed after the specified time interval. Default value is 60 sec. Time thatcan be specified is from 10 to 999 sec.
*Shorter time interval incurs higher load on the memory. To reduce the load on memory, please set a
longer time interval time.

4.2.3

Default Monitoring Setting at logging-in
You can define which Monitoring Settings to be activated when you login. Application Monitor Windows of
the selected Monitoring Settings will be displayed each time you login.
Monitoring Settings that you want to activate automatically when you login is specified in "Selected Monitor
Setting". Monitoring Settings that are available to be selected for automatic activation is in "Unselected".
Click on the appropriate arrow icons to move Monitoring Settings between "Selected Monitor Setting" boxand "Unselected" box.

4-20

Overview of A-AUTO for UNIX/Windows

4.3

Change Password
You can change password in [A-AUTO Main] Windows.
The following are the steps to change password.
①

Click [Change Password] on the top of [A-AUTO Main] Windows.
[Change Password] dialog will be displayed.

②

Type the current password and new password.

③

Click [Execute] button.
The password is changed.

4-21

Operations of A-AUTO for UNIX / Windows

Operations of A-AUTO for UNIX / Windows

5 Application Definition
This chapter explains the maintenance procedures for the various Master files and provides examples toillustrate these maintenance procedures.

5.1 Network MasterUse [Network Definition List] page to create new application (Job) information, or to edit, delete or search
the registered application.

5.1.1

Network ID List
Login to A-AUTO/Web Client. On the [A-AUTO Main] Windows, click on a Monitor ID on [Application
Definition] pane. The information of the Networks in the Network Master is displayed in list format. This list
is called [Network Definition List] page (refer to the picture below). [Network Definition List] page allows you
to perform maintenance on the displayed Networks.

Alternatively, you may switch the display from list format to flowchart format, referred to as [Network
Definition List Chart] page. To switch between the two formats, click theon the right side of toolbar.

Please refer to [Network Registration using the Flowchart Page] for details on using flowchart.
.

5-1

5 Application Definition

5-2

Operations of A-AUTO for UNIX / Windows

5.1.2

Network Menu
Click the [Menu] icon on the toolbar of [Network Definition List] page to display the [Network Menu] page.

(1) Reference Date
Reference Date is displayed at the top of [Network Menu] dialog. The date highlighted in the calendar is
the Reference Date used for [Network Definition List] page. The Networks that are valid on Reference Dateare displayed on [Network Definition List] page. When you click a calendar date to change the ReferenceDate, the display on the list will change accordingly to show Networks that are valid for the selected
Reference Date.
You can change the selection of the Networks to be displayed on list page by using Reference Date’s
check box.
When the check box is checked
Display Networks which are valid on the selected calendar date on list page.

When the check box is not checked
Display all registered Networks in the Network Master. For those Networks with multiple Valid Dates,
the information of these Networks with the latest Valid Date will be displayed.

(2) Network GroupA list of Network Groups is displayed for selection.
Clicking a Group ID link will select only Networks that belong to the specified Group to display on the[Network Definition List] page.

5-3

5 Application Definition

5.1.3

Create Network
Create a new Network in Network Master when you want to process a new application using A-AUTO for
UNIX/Windows.
The following describe the steps for creating a new Network in Network Master.
(1) Click the [Create] button of [Network Definition List] page.
(2) The [Create] page of Network Definition is displayed. Set the necessary items in each tab according
to the execution information of the Network.
(3) After setting all the required items, click the [Apply] button to save the setting.
Alternatively, you can also create a Network using Flowchart format.
Please refer to [Network Registration using the Flowchart Page] of this chapter for

details on using thismethod.
The following are examples of creating Networks for different application job requirements.

e.g. 5-1Network Creating 1
e.g. 5-2Network Creating 2

e.g. 5-3Network Creating 3
e.g. 5-4Network Creating 4e.g. 5-5Network Creating 5e.g. 5-6Network Creating 6
e.g. 5-7Network Creating 7
e.g. 5-8Network Creating 8

Set the start time of an application
Run multiple Jobs in the Network
Set the Preceding Relationship of an application (Network)
Parallel run for multiple Jobs
Set the Preceding Relationship for Jobs
Control the processing of a succeeding application Job by Job’s
Return Code.
Start an application only when Data arrived.
Set a Job that has more than 7 dependent application Jobs
(Dummy Job)
Set the Valid Date and Expiry Date
Set an application that is using Resource Management function
Set an application (Job) that has a preceding Relationship with a
Job which is in another A-AUTO System.
Set the execution condition according to the Job’s return code.

5-4

Operations of A-AUTO for UNIX / Windows

e.g. 5-1

Network Creating 1
Application A is to start at 10AM. Thisapplication consists of two Jobs. Job names are GYOUMUA1 andGYOUMUA2. Application A’s Network ID is GYOUMUA.
follows.
(1)

Click the [Create] button of [Network
Definition List] page.
The [Create] page of Network definition
is displayed. (Right down)(2)

Input the required items.

Network ID
GYOUMUA
Start Time
10 : 00(The Valid Date can be blank if system dateis used.)The Network attribute you set here issufficient.

Next, create Jobs.
(3)

Click the [Job] tab and click the[Create] button.

(4)

Input the required items.

Job Number
010
Job IDGYOUMUA1(5)

Click [Apply] button.

5-5

A Network for this application can be created as

5 Application Definition

e.g. 5-1

Network Creating 1 continuation

Job created will be shown on the [JobDefinition List] page. (Right Side)
Next,

register

Job“GYOUMUA2”

byfollowing the procedure in Step (3).

(6)

When you have finished creating Jobs,
click [Apply] button.

5-6

Operations of A-AUTO for UNIX / Windows

e.g. 5-2

Network Creating 2
Application B is to be processed after Application A (GYOUMUA) has been executed successfully. Thisapplication consists of 3 Jobs. The Job names are GYOUMUB1, GYOUMUB2 and GYOUMUB3.
GYOUMUB2 and GYOUMUB3 are to be processed after GYOUMUB1 has been executed successfully.
Jobs that are not dependent on each other may execute concurrently. Name this application as
GYOUMUB. A Network for this application can be created as follows.

(1)

Click [Create] button on the [Network
Definition List] page.

The [Create] page of Network Definition isdisplayed. (Right down)(2)

Input the required items.

Network ID
GYOUMUB
Check the Parallel Run(The Valid Date can be blank if system dateis used.)The Network attribute you set here issufficient.
Next, define the Preceding Network.
(3)

(4)

Click the [Preceding Network] tab.

Select GYOUMUA from [Network ID];
click the [←] button.

GYOUMUA is displayed in [Selected Network
ID]. (Below)

At this point, the definition of Preceding
Network is done. Next, register Job.

5-7

5 Application Definition

e.g. 5-2(5)Network Creating 2 continuation

Click the Job tab and then click [Create]
button.

The [Job-Create] page is displayed. (Right)(6)

Input the required items.

Job Number
010
Job IDGYOUMUB1
Click [Apply] button.

The Job registered will be shown on [JobDefinition List] page. (Right)
Next, register Job “GYOUMUB2”.
(7)

Click [Create] button.

(8)

Input the required items.

Job Number
020

5-8

Operations of A-AUTO for UNIX / Windows

Job IDGYOUMUB2
Because

it

is

to

be

executed

after

GYOUMUB1 has normally ended, select thePreceding

Job

Numberon[Execution

Condition].
<Execution Condition>
Preceding Job Number
010 (GYOUMUB1)(9)

Click [Apply] button.

e.g. 5-2

Network Creating 2 continuation

Next, create “GYOUMUB3” with the same
Execution Condition.
(10) Select [GYOUMUB2] on [Job Definition
List] page and click [Copy] button.
(Copy-register)
The content of [GYOUMUB2] is displayed on[Job-Create] page.

(11) Input the required items.
Job Number
030
Job IDGYOUMUB3
The same content of GYOUMUB2 hasalready been set and no change to thecontent is required.
(12) Click [Apply] button.

At this point, the creating of Job is finished.
(13) Click [Apply] button.

5-9

5 Application Definition

e.g. 5-3

Network Creating 3
Application C is to be processed after Application A (GYOUMUA) has been executed successfully. Thisapplication consists of 3 Jobs. The Job names are GYOUMUC1, GYOUMUC2 and GYOUMUC3. The Jobs
are to run in the following order, GYOUMUC1→GYOUMUC2→GYOUMUC3. GYOUMUC2 should not run
when the return code of GYOUMUC1 upon completion is more than 004. Name this application as
GYOUMUB. A Network for this application can be created as follows.
e.g.5-3 The following is a summary description of the steps.

(1)

Click [Create] button on the [Network
Definition List] page.

The [Create] page of Network Definition isdisplayed. (Right down)(2)

Input the required items.

Network ID
GYOUMUC

Next, define the Preceding Network.
(3)

Click the [Preceding Network] tab.

5-10

Operations of A-AUTO for UNIX / Windows

e.g. 5-3

Network Creating 3 continuation(4) Select GYOUMUA.
At this point, the definition of Preceding
Network is completed.
(5)

Next, Click [Job] tab.

(6)

Click [Create] button.

(7)

Input the required items.

Job Number
010
Job IDGYOUMUC1(8)

Click [Apply] button.

(9)

Register

GYOUMUC2

andGYOUMUC3 in the similar way.
Job Number
020
Job IDGYOUMUC2
Max Return Code004
Preceding Job Number
010 (GYOUMUC1)
Job Number
030
Job IDGYOUMUC3
Preceding Job Number
020 (GYOUMUC2)

5-11

5 Application Definition

e.g. 5-3

Network Creating 3 continuation(10) Click [Apply] button.

At this point, the definition of a Network
Master record is completed.

5-12

Operations of A-AUTO for UNIX / Windows

e.g. 5-4

Network Creating 4
Application D is to wait for some data, which will be created by a related company. This applicationconsists of 7 Jobs. The Job names are GYOUMUD1, GYOUMUD2, GYOUMUD3, GYOUMUD4,
GYOUMUD5, GYOUMUD6 and GYOUMUD7. The Jobs are to run in the following order, GYOUMUD1 →GYOUMUD2 → GYOUMUD3, GYOUMUD4 → GYOUMUD5 → GYOUMUD6 and GYOUMUD7. Jobs thatare not dependent on each other may execute concurrently. Name this application as GYOUMUD, andname the data as DDATA01, which will be created by a related company. A Network for this application
can be created as follows.

※ The following steps described below assumed that the Data Wait [DDATA01] has already been registered in the Input
Data Wait Master before you register this Network. For the definition of Input Data Wait Master, refer to the [3.3 Data
Wait Master].

(1) Register Network Attributes.
(Refer to [e.g. 5-1] (1) for detailed
steps)

Network ID
GYOUMUD
Check Parallel Run
Check Input Data Wait
Check Monitor On*Please refer to step (3), which is
described later, for the registeringof Input Data Wait.
(2) Register Jobs.
(Refer to [e.g.5-2] (5) for detailed
steps). When copying, choose a Job
that does not have Preceding Job.
This will avoid copying the content of
the Preceding Job from the target Job.
Set each Job as follows.

GYOUMUD1 : none
GYOUMUD2 : 010 (GYOUMUD1)
GYOUMUD3 : 020 (GYOUMUD2)
GYOUMUD4 : none
GYOUMUD5 : 040 (GYOUMUD4)
GYOUMUD6 : 050 (GYOUMUD5)
GYOUMUD7 : 050 (GYOUMUD5)

5-13

5 Application Definition

Next, define the Input Data Wait.

5-14

Operations of A-AUTO for UNIX / Windows

e.g. 5-4

Network Creating 4 continuation(3) Click the [Input Data Wait] tab.

(4) Select DDATA01 from [Data].
At this point, the definition of Input
Data Wait is completed.

(5) Click [Apply] button.
At this point, the definition of Network
Master is completed.

5-15

5 Application Definition

e.g. 5-5

Network Creating 5
Application E is to be processed after Applications C (GYOUMUC) and D (GYOUMUD) have been
executed successfully. This application consists of 8 Jobs. The Job names are GYOUMUE1~8 (Refer tothe diagram below) . After GYOUMUE1~7 has been executed, run GYOUMUE8. Jobs GYOUMUE1~7 canbe executed concurrently.
GYOUMUE8 depends on 7 Jobs, which are to be defined as its Preceding Jobs. This exceeds the
maximum of 6 Preceding Jobs that can be defined for a Job in Job Definition. Create a Dummy (imaginary)

GYOUMUE6

GYOUMUE2
GYOUMUE1

GYOUMUE7
GYOUMUE4

GYOUMUE5GYOUMUE3DUMMY

GYOUMUE8
Job as shown in the steps below and use this Dummy Job as Preceding Job.

Named this application as GYOUMUE. A Network for this application can be created as follows.
(1) Register Network Attributes.
(Refer to [e.g.5-1] (1) for detailed
steps)

Network ID
GYOUMUE
Check Parallel Run
Check Input Data Wait
Check Monitor On(2) Define the Preceding Network.
As it depends on applications C(GYOUMUC) and D (GYOUMUD) to
be executed successfully], select thefollowing.
GYOUMUCGYOUMUD

5-16

Operations of A-AUTO for UNIX / Windows

e.g. 5-5

Network Creating 5 continuation

Next, register Jobs.
(Refer to [e.g.5-2] (5) for detailed
steps).
(3) Register
GYOUMUE1~GYOUMUE7(4) Register Dummy Job.
Job Number
080
Job ID
DUMMY
Preceding Job Number
060 (GYOUMUE6)
070 (GYOUMUE7)
Check Dummy(5) Register GYOUMUE8
Job Number
090
Job IDGYOUMUE8
Select the following Preceding
Job Number
010 (GYOUMUE1) ~050 (GYOUMUE5), 080 (DUMMY)(6) Click [Input Data Wait] tab.

(7) Selected DDATA01 from [Data].
Here, the definition of Input Data
Wait has been finished.
(8) Click [Apply] button.
At this point, the Definition of
Network Master is completed.

5-17

5 Application Definition

e.g. 5-6

Network creating 6
Create a new Network with a different Valid Date for the registered Application B (GYOUMUB) byperforming the following steps. Note that Application B is already registered in (e.g. 5-2).
The new Network will require 2 Resources. The Resource IDs of the two Resources are “testing machine(BSPSTA00)” and “own machine (BSPSTA01)”. After the execution of the application has ended,“(BSPSTA00)” is to be released by Manual mode and “(BSPSTA01)” is to be released by Auto mode. Thischange is effective from November 30, 2010. The Network is to operate in the original setting before thisdate. This application will no longer be used from December 30, 2010. A new Network, which has the same
Network ID but different Valid Date as GYOUMUB, for this application can be created as follows.

(1) Select “GYOUMUB” on the [Network
Definition List] page and click [Copy]
button.
The content of [GYOUMUB] isdisplayed on [Network-Create] page.

(2) Input the following.
Valid Date
2010/11/30
Network ID
GYOUMUB
Check Resource

5-18

Operations of A-AUTO for UNIX / Windows

e.g. 5-6

Network Creating 6 continuation(3) Click on [Resource] tab and register thefollowing.
Resource Name
own machine (BSPSTA01)
Number of Resources
1
Start Type
Auto(4) Click [Add] button, a new register row
for Resource registration is displayed.
(5) Register the following in the similar way.
Resource Name
Testing machine (BSPSTA00)
Number of Resources
1
Start Type
Manual(6) Click [Apply] button.
The registration of [GYOUMUB] with adifferent Valid Date is completed.
Next, set the Expiry Date of GYOUMUB.
(7) Select GYOUMUB on [Network
Definition List] page and click the[Expiry Date Modify] button.
[Expiry Date Modify] dialog is displayed.

(8) Enter the Expiry Date 2010/12/30.
(9) Click [Apply] button.
The Expiry Date of GYOUMUB has been
set.

5-19

5 Application Definition

After the registration of examples e.g.5-1~ e.g.5-6, the configuration of the Networks and their Jobs in the
Network Master is as follows.

GYOUMUB will be switched to use
the new settings (GYOUMUB withGYOUMUA

Valid Date 2012/11/30) fromGYOUMUA1

GYOUMUDGYOUMUD1
GYOUMUD4

2010/11/30. The Network will end its

GYOUMUA2

operation on 2010/12/30.

GYOUMUD2
GYOUMUD5GYOUMUD3

GYOUMUBGYOUMUCGYOUMUB1GYOUMUC1

GYOUMUB2

GYOUMUB3

GYOUMUD6
GYOUMUD7

GYOUMUC2

GYOUMUC3

GYOUMUEGYOUMUE1
GYOUMUE5GYOUMUE2

GYOUMUE6

GYOUMUE3

GYOUMUE4DUMMY

GYOUMUE8

5-20

GYOUMUE7

Operations of A-AUTO for UNIX / Windows

e.g. 5-7

Network Creating 7
Application F is to be processed after Application E (GYOUMUE) has been executed successfully. This
Application F is also dependent on the normal end of Application X, which runs on another A-AUTO system,
as a condition. Name the Network ID of the Application F as GYOUMF and the Application X as
GYOUMUX. A Network for this application can be created as follows.

A-AUTO System 2(AUTO02)

A-AUTO System 1

GYOUMUXGYOUMUEGYOUMUF(1)

Define the Network attributes andJobs. (Please refer to e.g.5-1 fordetailed steps.)(2)

Define the Preceding Network.
Select [GYOUMUE] because thisNetwork is to be run after the
successful end of [GYOUMUE].

Next, define the application X, whichruns on another A-AUTO system, as its
preceding Network.

(3)

Click [Cross-Master] button.

5-21

5 Application Definition

e.g. 5-7[List

Network Creating 7 continuationof

Cross-Master

Preceding

Network Definition] dialog is displayed.
(Right)(4)

Click [Create] button.

(5)

Input the following.

Network ID
GYOUMUXAML ID
AUTO02
Expanded Name
Application X(6)

Click [Apply] button.
Click the [×] to close [ List of
Cross-Master Preceding Network
Definition] dialog.

(7)

Select GYOUMUX, then click [←]button.

(8)

Click [Apply] button.

At this point, the definition of Network iscompleted.

5-22

Operations of A-AUTO for UNIX / Windows

e.g. 5-8

Network Creating 8
Application R consists of 3 Jobs. Job Names are GYOUMUR1,GYOUMUR2 andGYOUMUR3. Jobs run in
the following order, GYOUMUR1→GYOUMUR2 or GYOUMUR3.
If return code of GYOUMUR1 is 0, then run GYOUMUR2. Otherwise, run GYOUMUR3. Name thisapplication as GYOUMUR. A Network for this application can be created as follows.

GYOUMURRun GYOUMUR2
when the Return

Run GYOUMUR3

GYOUMUR1

code is 0.

is not 0.

GYOUMUR3

GYOUMUR2(1) Define the attributes of Network.
(For

detailed

steps.

Refer

when the Return codeto[e.g.5-1])

Next, register Job.
(2) Register GYOUMUR1.
Job Number
010
Job IDGYOUMUR1
Execution Condition
None(3) Register GYOUMUR2
Job Number
020
Job IDGYOUMUR2
Preceding Job Number
010 (GYOUMUR1)

5-23

5 Application Definition

e.g. 5-8

Network Creating 8 continuation(4) Click [Modify] button of [Execution
Condition].
[Job execution condition] dialog isdisplayed.

(5) Please set the following
Condition
RC = Value
Value
0(6) Click[Apply]buttonof[Job

execution condition] dialog.
(7) Click [Apply] button of [Job-Create ]page.

(8) Register GYOUMUR3
Job Number
030
Job IDGYOUMUR3
Preceding Job Number
010 (GYOUMUR1)(9) Click [Modify] button of [Execution
Condition].
Condition
RC is Not Eq. to Value
Value
0

(10)

Click [Apply] button of [Jobexecution condition] dialog.
(11)[Click [Apply] button of[Job-Create] page.
(12)

Click [Apply] button Of[Network-Create] page.
At this point, the definition of Network iscompleted.

5-24

Operations of A-AUTO for UNIX / Windows

Using Flowchart Page (To register Network ID only)
You can create a Network on [Network Definition Chart] page and define its Network ID.

[Chart Editor] Pane

[Area Search] Pane

<1> Click the [Create] icon on [Chart Editor] pane
<2> An empty rounded rectangle representing a new
Network is displayed on [Chart Editor] pane.

<3> Enter GYOUMUB in the empty rectangle.
<4> Click [Save] icon.
<5> The new Network is registered.
Note■

For a new Network that is registered in this case, the Valid Date will be set to system date and Job in
the Network will be automatically set as a Dummy Job.

5-25

5 Application Definition

You can locate a Network and view its Preceding Relationship using [Area Search]. Enter a Network ID in
Textbox and click [Search] icon.

Textbox[Search] icon

The Network found will be positioned to the top left on the flowchart display and its flow (succeeding andpreceding relationships) will be displayed in blue.
* It’s enable to search Network ID by the search function of Internet Explorer.

5-26

Operations of A-AUTO for UNIX / Windows

Using Flowchart Page (Create the Preceding Relation)
You can create / edit Network on [Network Definition Chart] page.
The following describe the steps for creating preceding relationship on [Network Definition Chart].
Create GYOUMUB in the same way as [e.g.5-2].

<1> Select GYOUMUB on the [Network Definition Chart]
page.
<2> GYOUMUB rectangle is displayed on [Chart Editor]
pane.

5-27

5 Application Definition<3> Select GYOUMUB on [Chart Editor] pane and click[Create Preceding Network] icon.
<4> A empty rectangle is displayed on left side of
GYOUMUB.

<5> Click GYOUMUR rectangle on [Network Definition
Chart] page
<6> GYOUMUR appears in the new rectangle on [Chart
Editor] pane.

<7> Click [Save] icon.
<8> GYOUMUB is updated with the preceding relationshipsetting.

5-28

Operations of A-AUTO for UNIX / Windows

Using Flowchart Page (Delete the Preceding Relation)
Please perform the following steps when you want to delete a Preceding Relation between GYOUMUR and
GYOUMUB.

<1> Select GYOUMUB on the [Network Definition Chart]
page.
<2> GYOUMUB rectangle is displayed on [Chart Editor]pane.

<3> Click GYOUMUR rectangle on [Chart Editor] pane.
Click Precede Delete icon.
<4> GYOUMUR rectangle is removed from [Chart Editor]pane.

<5> Click [Save] icon.
<6> GYOUMUB is updated with the preceding relationshipsetting.

5-29

5 Application Definition

5.1.4

Edit Network
When there is any change to the requirements of an application, the Network that has been registered in
Network Master has to be modified accordingly.
The following describe the steps for modifying the information of a registered Network.
① Click the Network ID link of the target Network on [Network Definition List] page.
② [Network-Edit] page is displayed.
③ Change the information of the Network accordingly.
④ Click the [Apply] button to save the changing.
To change the Valid Date of a Network, perform the following steps.
① Check the check box of the Network ID of the target Network to be updated on [Network Definition
List] page. Then, click [Valid Date List] button on toolbar.
②[Valid Date] dialog is displayed.

③ Check the check box of Valid Date to be updated and then, press [Valid Date Modify] button.
④[Valid Date Modify] dialog is displayed. Change the Valid Date accordingly and then, click [Apply]
button.

The following are examples of updating a Network.
e.g. 5-9 Network Editing 1
e.g. 5-10 Network Editing 2
e.g. 5-11 Network Editing 3

Add Input Data Wait
Change the Preceding Relation
Add a new job and set its Job preceding relationship.
Edit (delete) the Preceding Relation of application Job.

5-30

Operations of A-AUTO for UNIX / Windows

e.g. 5-9

Network Editing 1
Edit the registered application D (GYOUMUD) as follows.
Because the related company produces 2 more types of data, it is required to add one more Data ID.
Set [Monitor On] to be released manually.
Adding Data ID : DDATA02
Perform the following steps to change the Network GYOUMUD.

①

Click

GYOUMUD

link

on[Network Definition List] page.

[Edit] page of Network definition isdisplayed.

②

Remove

the

check

box

of

Monitor On.
③

Click [Input Data Wait] tab.

Select DDATA02④

Click [←] button.

At this point, Wait Data is added.
⑤

Click [Apply] button.

At

this point, Network Editing iscompleted.

5-31

5 Application Definition

e.g. 5-10

Network Editing 2
Edit the registered application E (GYOUMUE) as follows.
Currently, application E is defined with application C (GYOUMUC) and application D (GYOUMUD) as
Preceding Networks.
Remove GYOUMUD as its Preceding Network, so that GYOUMUE will be processed after (GYOUMUC)
has executed successfully. And add 1 Job. Name it as GYOUMUE9 and define it to run after GYOUMUE8
has normally ended.
Perform the following steps to change the Network GYOUMUE.

①

Click GYOUMUE link on [Network
Definition List] page.

[Edit] page of Network definition isdisplayed. (Right Side)②

Click [Preceding Network] tab.

③

Select [GYOUMUD] from [Selected
Network ID] list and then, click the[→] button.

At this point, the Preceding Network
GYOUMUD is removed.

Next, to add a Job.
④

Click [Job] tab.

⑤

Next, register Job.

Job Number
100
Job IDGYOUMUE9
Preceding Job Number
090 (GYOUMUE8)⑥

Click [Apply] button.

At

this

point,

Network

Editing

iscompleted.

5-32

Operations of A-AUTO for UNIX / Windows

e.g. 5-11

Network Editing 3
Edit the registered application E (GYOUMUE) as follows.
Remove the Job GYOUMUE1 of GYOUMUE. The preceding relationship defined in Job GYOUMUE8 for
GYOUMUE1 is to be removed as well.
Perform the following steps to change the Network GYOUMUE.

①

Click GYOUMUE link on [Network
Definition List] page

[Edit] page of Network definition isdisplayed.

②

Click [Job] tab.

③

Select GYOUMUE1 and then, click[Delete] button.

* The relation, which GYOUMUE1 isdefinedasthePreceding

Job

of

GYOUMUE8, is also removed along with
this.

④

Click [Apply] button.

At

this

point,

Network

Editing

iscompleted.

5-33

5 Application Definition

5.1.5

Delete Network
Delete the Network in Network Master when you do not require the application.
The following describe the steps for deleting a Network.
① Check the check box of the Network ID of the target Network to be deleted on [Network Definition
List] page.
② Click [Delete] button on the toolbar
The selected Network ID is deleted in the Network Master and removed from [Network Definition
List] page.

The following is an example of deleting a Network.
e.g. 5-12 Network Deleting

Delete application

5-34

Operations of A-AUTO for UNIX / Windows

e.g. 5-12

Network Deleting
Delete the registered application D (GYOUMUD) as follows.
①

Check the check box of GYOUMUD on [Network Definition List] page, then click [Delete] button.

②

Confirmation message is displayed.
* If this Network is the Preceding Network of any other Network already, double check it and thencontinue deleting.

③

Click [OK] button.

At this point, Network is deleted.

5-35

5 Application Definition

5.1.6

Related Information Display
You can check which group a Network belongs to by following the procedures given below.

①

Click [Network Group ] on the [List Menu] of [Master Management] Windows.

②

Click

③

[Network Group - Search] dialog (Refer to the picture below) is displayed.

④

In [Network ID] textbox, type a Network ID that you want to check on, and click [Search] button.

Search icon.

The search result is displayed on [Network Group List] page.

5-36

Operations of A-AUTO for UNIX / Windows

5.1.7

Renumbering Job Number
There may be occasions when you need to change the Job configuration in a Network and one or more
new Jobs have to be added and inserted between two existing Jobs. Job Numbers of Jobs are usuallyassigned sequentially in a Network. As a result, Job Numbers between two Jobs may be consecutive andno new Job Number can be assigned. In such a case, use Renumber function to re-number all the Jobs in
the Network.
The following describe the Renumber function.
Renumber function performs the following processing.
① In the Preceding Job Numbers field, check for Job Numbers that are no longer in use. Delete these
non-existent Job Numbers if there are any.
② Renumber the registered Job’s Job Number in increment of 10 starting from 010.
Then, Preceding Job Numbers of the Jobs are also automatically updated to reflect the newly
assigned Job Numbers of the Jobs.
e.g.

Click [Renumber] button

5-37

5 Application Definition

5.1.8

Show Script
You can display the batch file or script shell of the Job from A-AUTO application Definition page orapplication Monitor page. The object script is Job of A-AUTO Monitor or A-REMOTE for
Windows/Linux/UNIX.
This function is available from version v710.

The following describe the steps to be performed to display the script.
① Display [Job Detail] page.
② Select the character code on the toolbar of [Job Detail] page.
③

Click [Show Script] button on the toolbar of [Job Detail] page.

④ [Script] dialog is displayed.

5-38

Operations of A-AUTO for UNIX / Windows(1) Script that Can Be Referenced
Currently, Jobs that can be defined in a Network are [.exe], [.bat], [.cmd] (Windows) or Shell script (UNIX).
Show Script can display only [.bat], [.cmd] and Shell script. As [.exe] cannot be opened by a text editor, itcannot be displayed by Show Script.

(2) Character Code
It is necessary to set the character code when you display the script because native character code used
is different depending on the environment of Web client or A-AUTO Agent.
When display the contents, which have been sent to Web Server, on the page, Web server is responsible
for conversion of character code. Character code sets supported are Shift-JIS, EUC and UTF-8.

5-39

5 Application Definition

5.1.9

Create Job
The actual Job to be executed must be stored in the fixed directory which is specified in
TEMPSCRIPT_PATH and PRIMSCRIPT_PATH of Job Library Definition file (Joblibdef).
A-AUTO Monitor searches for the Job in the directory defined in TEMPSCRIPT_PATH first, and, if not
found, then search the directory defined in PRIMSCRIPT_PATH.

(1) Job Naming RuleJob name of an actual Job must follow the following naming conventions.

①

Job names of Jobs must be in all lowercase or all uppercase. The setting in the system parameter
NJP_SCRIPTFILE determines whether uppercase or lowercase is used.

②

A Job name must be 8 or less alphanumeric characters.

③

The first byte of Job name must not be a numeric character.

(2) About MAX-RC
The maximum value of MAX-RC that can be defined for a Job during registration is 127. For a Job whose
MAX-RC is defined with a value other than 0, A-AUTO Monitor will treat it as an abnormally ended Job(ABEND) if the Job ended its execution with a Return Code that is equal or greater than the specified
value.

(3) About Plug-in Before Start / After Start
You can run Plug-in before or after Job start.
Plug-in file must be created by the same user who starts A-AUTO Monitor. This file must be saved in the“A-AUTO Monitor’s installation directory”\PLUGIN folder.
Plug-in parameters that you specified during the registration using Web Client are passed to the Plug-in as
the value in environment variable [BSP_PLG_PARAM].

5-40

Operations of A-AUTO for UNIX / Windows(3) A-AUTO for UNIX Case
In a UNIX environment, a Job is a Shell script to be executed by A-AUTO Monitor. Please note thefollowing points.
<1> Comment statement of Line 1
Depending on the type of Shell, 1st line in the Shell script has to be set as follows.
C Shell“#!∆/bin/csh” note)

B Shell“#!∆/bin/sh”

K Shell“#!∆/bin/ksh” note)Note) If C shell or K shell, it reads the shell startup file.

<2> Run Shell script by the owner authority
Usually, A-AUTO Monitor runs a Shell script using the User ID of the user who started the A-AUTO Monitor.
To run a Shell script using the owner account of the Shell script, perform the following authorization settingfor A-AUTO modules.
＜Setting Method＞a)

Set the owner and group of 2 modules, njp and execscr, to super account ID.
When you issue an id command using super account ID to check for the group and User ID of
super account.

b) Define the Set User ID bit permission for of modules execscr and njp. Set the authority to 6755.
% su Password:## id
uid=0 (root) gid=1 (sys)# chown root : sys njp execscr# chmod 6755 njp execscr# ls -al-rwsr-sr-x 1 root sys Apr 2 20 : 17 execscr-rwsr-sr-x 1 root sys Apr 2 20 : 17 njpc) Shell script must have minimum permission of 500.
-r-x------ 1 auto bsp Apr 05 15 : 06 TESTJOB1-r-x------ 1 auto bsp Apr 03 16 : 05 TESTJOB2

5-41

5 Application Definition<3> About Job (Shell script) Action
With Set User ID bit turned on, A-AUTO Monitor starts a Job using owner ID that the shell Script belongs toand the authorization of the Shell Script is therefore the same as the owner/group. If the Job is csh, ksh or
bash script, the respective startup script (.cshrc / .kshrc * / .bashrc) will be read into the owner’s
environment (csh/ksh/bash) before starting the script.

* Solaris10(or lower) does not offer the start

function [.kshrc].
Please set the necessary authority to start the application with the owner/group of the Job.

Owner : bsp

A-AUTO Monitor

Start Job

Because the job started is csh script, start the job
after reading .Cshrc of owner bsp. csh is defined by#! / Bin / csh.

[ .cshrc ]set path = (/bin /usr/bin /etc /usr/ucb /home/bin.¥/usr/bin/X11 /home/openint/bin )set term=vt100
set history=64 savehist=64
set filec
set fignore= ( .o )set system = `hostname`setenv NAME bsp
・・#!/bin/csh
echo “BSPSTA01 START”
idecho “NAME=” $NAME
echo “BSPSTA01 END”
exit 0execution result of
BSPSTA01 Job of csh script"owner bsp / group bsp01"
BSPSTA01 START
uid=900 (bsp) gid=301 (bsp01)
NAME= bsp
BSPSTA01 END

A-AUTO Monitor is Resident mode and operates in the background of the UNIX system. For a UNIXsystem, you cannot run the foreground processing by the background task. Therefore, any Job that runs
under A-AUTO Monitor cannot have foreground processing. If a Job accidentally run a foreground process,all related background processes will stop.
Foreground processing refers to processing that requests for or requires a general standard input,
commands such as the read and stty, functions such as the scanf (), etc. It is foreground processing when
an output message requires a response e.g. file deleting.
Message: rm : ./testksh the protection mode has become 700, do you want to remove?
“stty” can be defined for the login environment. If stty definition is defined in .kshrc or .cshrc startup file,
Script may not execute correctly in the background. For this reason, it is recommended that you define stty
definition in .profile or .login.

5-42

Operations of A-AUTO for UNIX / Windows<4> About Return Code Setting
For A-AUTO to determine the outcome of an application or Job, the Shell script (Job) must end or exit witha value, referred as End Code. End Code must be from 0 to 255. If the End Code is less than zero or
greater than 255, it will not be recognized by A-AUTO. For such cases, A-AUTO will set the End Code to
the value defined for system parameter AUTO_JOB_EXEC_ERRORCODE (Default value 100). Thissystem parameter defines the End Code that is to be used to identify any internal errors encountered by
A-AUTO during Job execution (e.g. if you do not have permission to run Jobs). The value defined for thissystem parameter should not be set as End Code for any Shell script executed by A-AUTO. Any Job that
ends with an End Code value that is the same as the value of AUTO_JOB_EXEC_ERRORCODE will betreatedasabnormally

ended

(RC

=

08)

by

A-AUTO.

Pleasechange

the

value

of

AUTO_JOB_EXEC_ERRORCODE to another value if you want to use the existing value in the Job End
Code.
Although HP-UX environment allows an exit code value between -128 to 127, A-AUTO does notrecognizes negative values. It is recommended to change Jobs that use an exit code value between -128
and -1 to a suitable positive value. (For example, you may change End Code of a Job that used -1 to 255
when this Job is executed by A-AUTO)
The following are samples of the ksh and csh scripts for the same Job.

The Job is registered with a

MAX-RC of 0001 (exit code that is greater than or equal to 1, then set it to abnormally ended, “ABEND”).
■ csh Case#!/bin/csh
echo “SAMPLE JOB START”
Application Start
switch ($status)
case ‘0’echo “SAMPLE JOB NORMAL ENDED”
exit ( 0 )defaultecho “SAMPLE JOB ABNORMAL ENDED”
exit ( 1 )
endsw

5-43

5 Application Definition■ ksh Case#!/bin/ksh
echo “SAMPLE JOB START”
Application Startcase $? In‘0’)echo “SAMPLE JOB NORMAL ENDED”
exit 0;;*)echo “SAMPLE JOB ABNORMAL ENDED”
exit 1
;;
esac

5-44

Operations of A-AUTO for UNIX / Windows(4) A-AUTO for Windows Case
In a Windows environment, a Job to be executed by A-AUTO Monitor must be a file with one of thefollowing extension types.
.exe .bat .cmd
The Job Name of a Job registered in A-AUTO is specified without its extension.
When there are several files with the same file name but different extension types in the same directory,
A-AUTO will select a file according to the following order .exe → .bat → .cmd.
■ About End Code Setting
The value of End Code must be from 0 to 255. When file extension of a Job is .bat or .cmd, aexit, an
A-AUTO utility, must be used to set the End Code just before exit. Otherwise, Job’s End Code isunpredictable. If the value specified for aexit is not between 0 and 255, aexit will set the End Code to 255.
aexit is an A-AUTO utility whose function is to set the End Code only and cannot be use to end a Job.
Please use exit to end a Job. If you end a job without using the exit, the job may return an improper End
Code. In addition, do not use exit with “/ b” option as the End Code will also be set incorrectly
If the file extension of a Job is exe, the program itself will be set the End Code for the Job. In this case,ensure that the program set a value between 0 and 255. Job’s End Code is unpredictable if the value of
the End Code is less than 0 or greater than 255.
Sample bat@echo offecho “TESTJOB.BAT STARTED”
rem Customer Application
c : \bsp\auto\testapp.exe
if errorlevel 1 goto ABENDif errorlevel 1 goto NORMAL: ABEND
echo “TESTJOB.BAT ABENDED”
aexit 99
GOTO DONE: NORMAL
echo “TESTJOB.BAT NORMAL ENDED”
aexit 0: DONEexit

5-45

5 Application Definition

5.2

Network Group MasterUse [Network Group List] page of A-AUTO/Web Client to register a new Network Group, or to
edit/delete/search for a registered Network Group.

5.2.1

Network Group List
After starting A-AUTO/Web Client, click on a Monitor ID on [Application Definition] pane of the [A-AUTO
Main] Windows. Then, click [Network Group] on [List Menu] pane. The information of the Network Groups
in Network Group Master will be displayed in list form. This list is called [Network Group List] page ( refer tothe picture below).
[Network Group List] page allows you to perform maintenance on the displayed Network Groups.

5-46Operations of A-AUTO for UNIX / Windows

5.2.2

Create Network Group
When several Networks are to be operated or managed frequently as a group, you can create a Network
Group to include the Network IDs of these Networks.
The following describe the steps for creating a new Network Group in Network Group Master.
①

Click [Create] button of [Network Group List] page.

②[Create] page is displayed. Select the Networks you want to include in the group.

③ Click the [Apply] button, when you have finished setting up the required items, to save the setting.
The following is an example of creating a Network Group.
e.g. 5-13Network Group Creating

Network Group Creating

5-47

5 Application Definition

e.g. 5-13 Network Group Creating
Create a Network Group NETGRP01 and include these Networks GYOUMUA, GYOUMUC, GYOUMUD
and GYOUMUE in the Group.
Please perform following.

<1> Click [Create] button on [Network Group List]
page.
<2> The [Create] page of Network Group isdisplayed.

<3> Input the required items.
■■

Input NETGRP01 in Group ID
Input NetworkGroup01 in Network Group
Expanded Name

<4> Select GYOUMUA, GYOUMUC,
GYOUMUD, GYOUMUE on Network ID list
<5> Click [←] button.
<6> Selected Network IDs are moved to Selected Network
ID list.

<7> Click [Apply] button.
<8> Setting is created into Network Group Master.

5-48

Operations of A-AUTO for UNIX / Windows

5.2.3

Edit Network GroupTo change Network IDs in a Network Group, edit that Network Group’s information.
The following describe the steps for changing the information of a registered Network Group (Network
Group Editing).
① Click the Group ID link of the target Network Group on [Network Group List] page.
②[Edit] page of Network Group is displayed.

③ Change the information of the Network Group ID accordingly.
④ Click the [Apply] button to save the changes into the Master.

The following are examples of updating a Network Group.
e.g. 5-14Network Group Master
Editing 1
e.g. 5-15Network Group Master
Editing 2

Modify Network Group Expanded Name
Remove a Network from a Network Group.

5-49

5 Application Definition

e.g. 5-14 Network Group Master Editing 1
When you want to change the Expanded Name of the registered Network Group, NETGRP01, to “businessdepartment”, perform the following steps.

<1> Click NETGRP01 link from [Network Group List] page.
<2> [Edit] page of Network Group is displayed.

<3> Input the required items.
■

Input Business department in Network Group
Expanded Name.

<4> Click [Apply] button.
<5> Setting is updated into Network Group Master.

5-50

Operations of A-AUTO for UNIX / Windows

e.g. 5-15 Network Group Master Editing2
When you want to remove Network GYOUMUA from the Network Group NETGRP01, perform the following
steps.

<1> Click NETGRP01 link on [Network Group List] page .
<2> [Edit] page of Network Group is displayed.

<3> Select GYOUMUA on Selected Network ID list.
<4> Click [→] button.
<5> Selected Network ID is moved to Network ID list.

<6> Click [Apply] button.
<7> Setting is updated into Network Group Master.

5-51

5 Application Definition

5.2.4

Delete Network Group
Delete the Network Group in Network Group Master when you do not need the Network Group.
The following describe the steps for deleting a Network Group.
① Check the check box of the Network Group ID of the target Network Group to be deleted on[Network Group List] page.
② Click [Delete] button on the toolbar.
The selected Network Group ID is deleted in the Network Group Master and removed from
[Network Group List] page.

The following is an example of deleting a Network Group.
e.g. 5-16Network Group Deleting

Network Group Deleting

5-52

Operations of A-AUTO for UNIX / Windows

e.g. 5-16 Network Group Deleting
When you want to delete NETGRP01, perform the following steps.

<1> Check the check box of NETGRP01 on [Network
Group List] page.
<2> Click [Delete] button.

<3> Click [OK] button on the displayed confirmation
message.
<4>

NETGRP01 is deleted from [Network Group List]

page.

* A Network Group that has Network IDs cannot be deleted.
Remove all Network IDs associated with a Network Group first before deleting the Network Group.

5-53

5 Application Definition

5.3

Input Data Wait Master
Input Data Wait Master stores the Data Wait information, an internal flag that can be used to represent an
event, such as arrival of input data or Job termination that happens outside the control of A-AUTO System.
Use [Input Data Wait Definition List] page of A-AUTO/Web client to create information, or to edit, delete or
search the registered Data Wait information in Input Data Wait Master.

5.3.1

Input Data Wait Definition List
After starting A-AUTO/Web Client, click on a Monitor ID on [Application Definition] pane of the [A-AUTO
Main] Windows. Then, click [Input Data Wait] on [List Menu] pane. The information of the Data Waits in
Input Data Wait Master will be displayed in list form. This list is called [Input Data Wait Definition List] page( refer to the picture below).
[Input Data Wait Definition List] page allows you to perform maintenance on the displayed Data Waits.

5-54

Operations of A-AUTO for UNIX / Windows

5.3.2

Create Data Wait
When an event that happens outside the control of A-AUTO System is required as a Start Condition of a
Network, you can create a Data Wait to represent it.
The following describe the steps for creating a new Data Wait.
① Click [Create] button of [Input Data Wait Definition List] page.
②[Create] page of Input Data Wait is displayed. Set the necessary items for the Data Wait.

③ Click the [Apply] button to save the setting.

The following are examples of creating Data Waits for different event requirements.
e.g. 5-17 Data Wait Creating 1
e.g. 5-18 Data Wait Creating 2
e.g. 5-19 Data Wait Creating 3
e.g. 5-20 Data Wait Creating 4e.g. 5-21 Data Wait Creating 5

Create Data Wait for input data
Create Data Wait based on the occurrence of the Job Event.
Create Data Wait based on the occurrence of the File Event.
Create Data Wait based on the occurrence of the Message Event
Create Data Wait based on the occurrence of the Application
Event.

5-55

5 Application Definition

e.g. 5-17

Data Wait Creating 1
When you want to register Data ID, DDATA01, to represent an event for the arrival of input data, performthe following steps.

<1> Click [Create] button of [Input Data Wait Definition List]
page.
<2> [Create] page of Input Data Wait is displayed.

<3> Input the required items.
■

Input DDATA01 in Data ID.

<4> Click [Apply] button.
<5> Setting is registered into Input Data Wait Master.

5-56

Operations of A-AUTO for UNIX / Windows

e.g. 5-18

Data Wait Creating 2
When you want to register a Data ID, DDATA02, to monitor the termination of the mcp process on machine
CZ1, perform the following steps.

<1> Click [Create] button on [Input Data Wait Definition
List] page.
<2> [Create] page of Input Data Wait definition is displayed.

<3> Input the required items.
■

Input DDATA02 in Data ID■

Check Input Data Wait Reset Event.

■Select Job Event for Event Type.

■

Select CZ1 for A-AUTO Event Agent Name■

Select CZ1 for Data Arrival Event Agent Name■

Input mcp in Process Name

<4> Click [Apply] button.
<5> Setting is registered into Input Data Wait Master.

5-57

5 Application Definition

e.g. 5-19

Data Wait Creating 3
When you want to register a Data ID, DDATA03, to monitor the creation of a file (/home/bsp/auto/ddata01)
on machine CZ1, perform the following steps.

<1>Click [Create] button on [Input Data Wait Definition List]
page.
<2> [Create] page of Input Data Wait definition is displayed.

<3> Input the required items.

<4> Click [Apply] button.
<5> Setting is registered into Input Data Wait Master.

5-58

■

Input DDATA03 in Data ID■

Check Input Data Wait Reset Event.

■Select File Event for Event Type.

■

Select CZ1 for A-AUTO Event Agent Name■

Select CZ1 for Data Arrival Event Agent Name■

Input /home/bsp/auto/ddata01 in File NameOperations of A-AUTO for UNIX / Windows

e.g. 5-20

Data Wait Creating 4
To define a Data Wait, DDATA04, to monitor for a specific message that will be displayed on the event log
of a computer named CZ1. The message has an Event ID of “ARB001” and contains a text string “START”
at 9th column of the message. To register this Data Wait, perform the following steps.

<1>Click [Create] button on [Input Data Wait Definition List]
page.
<2> [Create] page of Input Data Wait definition is displayed.

<3> Input the required items.
■

Input DDATA04 in Data ID■

Check Input Data Wait Reset Event.

■Select Message Event for Event Type.

■

Select CZ1 for A-AUTO Event Agent Name■

Select CZ1 for Data Arrival Event Agent Name■

Input ARB001 in ID■

Input 9 in UNIX System Log Offset■

Input START in String<4> Click [Apply] button.
<5> Setting is registered into Input Data Wait Master.

5-59

5 Application Definition

e.g. 5-21

Data Wait Creating 5
To define a Data Wait, DDATA05, to represent an Event that is triggered or set when Monitoring Log Files
Utility detects a specific text string “ABCDEFG” in the log file on a computer named CZ1. (For details of
Monitoring Log Files Utility please refer to “11.4.3 Monitoring Log Files Utility”). To register this Data Wait,
perform the following steps.

<1>Click [Create] button on [Input Data Wait Definition List]
page.
<2> [Create] page of Input Data Wait definition is displayed.

<3> Input the required items.
■

Input DDATA05 in Data ID■

Check Input Data Wait Reset Event.

■Select Application Event for Event Type.

■

Select CZ1 for A-AUTO Event Agent Name■

Select CZ1 for Data Arrival Event Agent Name■

Input ABCDEFG in Application Event ID■

Input ABC in Application Event Parameter<4>Click [Apply] button.
<5> Setting is registered into Input Data Wait Master.

5-60

Operations of A-AUTO for UNIX / Windows

5.3.3

Edit Data Wait
When there are changes to the requirements for Data Waits, you may edit the Data Wait information in
Input Data Wait Master.
The following describe the steps for changing the information of a registered Data Wait.
① Click Data ID link on [Input Data Wait Definition List] page.
② [Edit] page of Input Data Wait is displayed.
③ Change the Data Wait information accordingly.
④ Click the [Apply] button to save the updated content into the Master.

The following is an example of updating Data Wait infromation.
e.g. 5-22 Data Wait Editing

Change computer name to be monitored for an event.

5-61

5 Application Definition

e.g. 5-22

Data Wait Editing
Change the computer name to be monitored for the registered Data ID, DDATA02, to CZ2.
To change Data Wait information of DDATA02, perform the following steps.

<1> Click DDATA02 link on [Input Data Wait
Definition List] page.
<2> [Edit] page of Input Data Wait Definition isdisplayed.

<3> Change the content■<4> Click [Apply] button.
<5> Setting is updated into Input Data Wait Master.

5-62

Change A-AUTO Event Agent Name to CZ2 .

Operations of A-AUTO for UNIX / Windows

5.3.4

Delete Data Wait
When a Data Wait is no longer required, delete the registered Data ID in Input Data Wait Master.
The following describe the steps for deleting a Data ID.
①

Check the check box of the Data ID of the target Data Wait to be deleted on [Input Data Wait
Definition List] page.

② Click [Delete] button on the toolbar.
The selected Data ID is deleted in Input Data Wait Master.

The following is an example of deleting a Data Wait.
e.g. 5-23 Input Data Wait Deleting

Data Wait Deleting

5-63

5 Application Definition

e.g. 5-23 Data Wait Deleting
Delete the Data ID, DDATA01, as follows.
<1> Check the checkbox of DDATA01 on [Input Data
Wait Definition List] page<2> Click [Delete] button.

<3> Confirmation message is displayed.
<4> Click [OK] button.
<5> DDATA01 is deleted from Input Data Wait Definition
List.

5-64

5 Application Definition

5.5

Extended Job MasterUse [Extended Job Definition List] page of A-AUTO/Web Client to create Extended Job information, or toedit, delete or search the registered Extended Job information.

5.5.1

Extended Job Definition List
After starting A-AUTO/Web Client, click on a Monitor ID on [Application Definition] pane of the [A-AUTO
Main] Windows. Then, click [Extended Job] on [List Menu] pane. The information of the Extended Jobs inExtended Job Master will be displayed in list format. This list is called [Extended Job Definition List] page(refer to the picture below).
[Extended Job Definition List] page allows you to perform maintenance on the displayed Extended Jobs.

5-72

Operations of A-AUTO for UNIX / Windows

5.5.2

Create Extended Job
Create an Extended Job if you want to use either Job ID Conversion or Resource Management for a Job.

The following describe the steps for creating a new Extended Job.
① Click [Create] button of [Extended Job Definition List] page.
②[Create] page of Extended Job is displayed. Set the necessary items for the Extended Job.

③ Click the [Apply] button to save the setting.

The following is an example of creating an Extended Job.
e.g. 5-27 Extended Job Creating

Create an Extended Job

5-73

5 Application Definition

e.g. 5-27 Extended Job Creating
When

you

want

to

use

Job

Name

Convertfunctiontoreplace

Job

ID,

JOB01,

with“C:\daily\DailyApplication.bat” as the directory and file name (Job), perform the following steps.

<1> Click [Create] button on [Extended Job Definition List]
page<2> [Create] page of Extended Job Definition is displayed.

<3> Input the required items.
■

Input JOB01 in Job ID.

■

Select Enable Job Name Converter■

Set C:\daily\DailyApplication.bat in Full path.

<4> Click [Apply] button.
<5> Setting is registered into Extended Job Master.

5-74

Operations of A-AUTO for UNIX / Windows

5.5.3

Edit Extended Job
When there are changes to the requirements for Extended Jobs, you may edit the Extended Job
information in Extended Job Master.
The following describe the steps for changing the information of a registered Extended Job (Extended Job
Editing).
① Click Job ID link of the target Extended Job on [Extended Job Definition List] page.
②[Edit] page of Extended Job is displayed.

③

Change the information of the Extended Job accordingly.

④ Click the [Apply] button to save the updated content into the Master.

The following is an example of updating Extended Job information.
e.g. 5-28 Extended Job Editing

Change Full Path

5-75

5 Application Definition

e.g. 5-28 Extended Job Editing
When you want to change the Full Path for a registered Job, JOB01, to “C: \weekly\WeeklyApplication.bat”,
perform the following steps.

<1> Click JOB01 link on [Extended Job Definition List]
page.
<2> Extended Job information of JOB01 is displayed on[Edit] page of Extended Job Definition.

<3> Edit Job Name Convert Function■

Change Full Path to
C:\weekly\WeeklyApplication.bat.

<4> Click [Apply] button.
<5> Setting is updated into Extended Job Master.

5-76

Operations of A-AUTO for UNIX / Windows

5.5.4

Delete Extended Job
When an Extended Job is no longer required, delete the registered Extended Job in Extended Job Master.
The following describe the steps for deleting an Extended Job① Check the check box of the Job ID of the target Extended Job on [Extended Job Definition List]
page.
②

Click [Delete] button on the toolbar, the selected Job ID is deleted in Extended Job Master.

The following is an example of deleting an Extended Job.
e.g. 5-29 Extended Job Deleting

Delete an Extended Job

5-77

5 Application Definition

e.g. 5-29 Extended Job Deleting
When you want to delete JOB01(Job ID), perform the following steps.

<1> Check the checkbox of JOB01 on[Extended Job Definition List] page.
<2> Click [Delete] button.

<3> Confirmation message is displayed.
<4> Click [OK] button.
<5> JOB01 is deleted from [Extended Job Definition List]
page.

5-78

Operations of A-AUTO for UNIX / Windows

5.6

Annual Holiday Master
Annual Holiday is a holiday that falls on the same date every year. A-AUTO for UNIX/Windows uses thethis information to determine whether a calculated schedule date is a holiday or not and then decides theaction to be taken.
Use [Annual Holiday Definition List] page of A-AUTO/Web client to create Annual Holiday information, or toedit, delete or search for registered Annual Holiday information.

5.6.1

Annual Holiday Definition List
After starting A-AUTO/Web Client, click on a Monitor ID on [Application Definition] pane of the [A-AUTO
Main] Windows. Then, click [Annual Holiday] on [List Menu] pane. The information of the Annual Holidays
in Annual Holiday Master will be displayed in list format. This list is called [Annual Holiday Definition List]
page (refer to the picture below).
[Annual Holiday Definition List] page allows you to perform maintenance on the displayed Annual Holidays.

5-79

5 Application Definition

5.6.2

Create Annual Holiday Information①

Click [Create] button of [Annual Holiday Definition List] page.

②[Create] page of Annual Holiday is displayed. Set the necessary items for the Annual Holiday.

③ Click the [Apply] button to save the setting.
The following is an example of creating an Annual Holiday.
e.g.5-30 Annual Holiday Creating

Create Annual Holiday

Note■

You cannot set February 29 as a Holiday in Annual Holiday Master. When you need to define
February 29 as a holiday, set it in the calendar of the Holiday Master.

■

If “Substituted if falls on a Holiday” option is selected in an Annual Holiday, a Holiday Table (calendar)that uses (refer to) this Annual Holiday must also specify Sunday as a Weekly Holiday for thesubstitution to be effective. Otherwise, the substitution is invalid.

5-80

Operations of A-AUTO for UNIX / Windows

e.g. 5-30 Annual Holiday Creating
When you want to create January 1, New Year’s Day as an Annual Holiday, perform the following steps.
<1> Click [Create] button on [Annual Holiday
Definition List] page<2> [Create] page of Annual Holiday Definition isdisplayed.

<3> Input the required items.
■

Input 01/01 in Date.

■

Input New Year’s Day in Comment.

■

Check “Substituted if falls on a
Holiday”.

<4> Click [Apply] button.
<5> Setting is registered into Annual Holiday Master.

5-81

5 Application Definition

5.6.3

Edit Annual Holiday Information
When there are changes to the information for Annual Holidays, you may edit the Annual Holiday
information in Annual Holiday Master
The following describe the steps for changing the information of a registered Annual Holiday.
①

Click Date link on [Annual Holiday Definition List] page.

②[Edit] page of Annual Holiday Definition is displayed.

③

Change the information of the Annual Holiday accordingly.

④

Click the [Apply] button to save the updated content into Master.

The following is an example of updating Annual Holiday information.
e.g.5-31 Annual Holiday Editing

Change the comment of Annual Holiday

5-82Operations of A-AUTO for UNIX / Windows

e.g. 5-31 Annual Holiday Editing
Add “(Substituted)” to the Comment “New Year’s Day“ of the Annual Holiday, 01/01. To make the change,
perform the following steps<1> Click Annual Holiday 01/01 link on [Annual Holiday
Definition List] page.
[Edit] page of Annual Holiday Definition is displayed.

<2> Input the required item.
■

Input New Year’s Day (Substituted) in
Comment<3> Click [Apply] button.
<4> Setting is updated into Annual Holiday Master.

5-83

5 Application Definition

5.6.4

Delete Annual Holiday Information
When Annual Holiday information is no longer required, delete the registered Annual Holiday in Annual
Holiday Master.
The following describe the steps for deleting an Annual Holiday.
①

Check the check box of the date of the target Annual Holiday to be deleted on [Annual Holiday
Definition List] page.

②

Click [Delete] button on the toolbar.

③

Confirmation Message box is displayed. Click [OK] button to delete, otherwise click [Cancel] button
to abort the delete. If you click [Delete], the selected Annual Holiday will be deleted in Annual
Holiday Master.

The following is an example of deleting an Annual Holiday.
e.g.5-32 Annual Holiday Deleting

Delete Annual Holiday

5-84Operations of A-AUTO for UNIX / Windows

e.g. 5-32 Annual Holiday Deleting
When you want to delete Annual Holiday (January 1), perform the following steps.
<1> Check the checkbox of [January 1] on [Annual
Holiady Definition List] page.
<2> Click [Delete] button.

<3> Confirmation message is displayed.
<4> Click [OK] button.
<5> January 1 is deleted from [Annual Holiady
Definition List] page.

5-85

5 Application Definition

5.6.5

Related Information Display
When you want to check which Annual Holidays are used (referred to) by a Holiday Table, use the [Annual
Holiday-Search] function.
Click [Search] icon on [Annual Holiday Definition List] page. [Annual Holiday-Search] dialog is displayed.
Enter the Holiday ID of the Holiday Table, which you want to check, in [Holiday ID] textbox of[Holiday-Search] page as a keyword and click [Search] button. The Annual Holiday dates used by theHoliday Table are displayed on [Annual Holiday Definition List] page.

5-86

Operations of A-AUTO for UNIX / Windows

5.7

Holiday Master
Holiday is use to define which day the application should take a day off, when you want to set the Scheduleof application on A-AUTO for UNIX/Windows. It has two way. One is set the day off on [Holiday Detail] tab,the other is to relate with Annual Holiday on [Holiday Setting] tab. Holidays represent the days of nobusiness operation. A-AUTO for UNIX/Windows uses the this information to determine whether acalculated schedule date is a holiday or not and then decides the action to be taken. A calendar or Holiday
Table may define fixed date and non-fixed holidays. Fixed date holidays refer to Annual Holidays while
non-fixed date holidays are holidays that do not fall on the same date every year.
Use [Holiday Definition List] page of A-AUTO/Web client to create Holiday Table information, or to edit,
delete or search for registered Holiday Table information.

5.7.1

Holiday Definition List
After starting A-AUTO/Web Client, click on a Monitor ID on [Application Definition] pane of the [A-AUTO
Main] Windows. Then, click [Holiday] on [List Menu] pane. The information of the Holiday Tables orcalendars in Holiday Master will be displayed in list format. This list is called [Holiday Definition List] page( refer to the picture below). [Holiday Definition List] page allows you to perform maintenance on thedisplayed Holiday Tables. Click [Create] button or a Holiday ID link on [Holiday Definition List] page,[Holiday Detail] dialog is displayed.

5-87

5 Application Definition

5.7.2

Create Holiday Information
Create a new Holiday Table when you want to define a new calendar and its holiday information.
Remember to include the necessary Annual Holidays in your new Holiday Table.
The following describe the steps for creating a new Holiday Table or calendar into Holiday Master.
①

Click [Create] button of [Holiday Definition List] page.

②[Create] page of Holiday Definition is displayed.
Set Holiday ID and the necessary non-fixed holidays, Weekly holidays and Annual Holidays.

③ Click the [Apply] button to save the setting.
The following are examples of creating Holiday Tables.
e.g.5-33Holiday Creating 1
e.g.5-34Holiday Creating 2

Set weekly day off
Set weekly day off and Annual Holiday

5-88Operations of A-AUTO for UNIX / Windows

e.g.5-33

Holiday Creating 1
The day off for Business department is every Tuesday. Set Holiday ID of the calendar for Businessdepartment as HOL01. Perform the following steps to create a new Holiday Table.
<1> Click [Create] button on [Holiday Definition List]
page.
<2> [Create] page of Holiday Definition is displayed.

<3> Input the required items.
■

Input HOL01 in Holiday ID■

Check Tue in Holiday<4>Click [Apply] button.
<5> Setting is registered into Holiday Master.

5-89

5 Application Definitione.g.5-34

Holiday Creating 2
Management department’s day off is every Saturday, every Sunday and the National holiday. Set Holiday
ID of the calendar for the Management department as HOL02. Perform the following steps to create a new
Holiday Table.
<1> Click [Create] button on [Holiday Definition List] page.
<2> [Create] page of Holiday Definition is displayed.

<3> Input the required items.
■

Input HOL02 in Holiday ID■

Check Sat and Sun in Holiday<4> Click [Holiday Setting] tab<5> [Holiday Setting] page is displayed.

<6> Select Annual Holiday (01/01) from [Unselected] list
<7> Click [←] button.
<8> The selected Annual Holiday is moved to [Selected]
list.

<9> Click [Apply] button.
<10> Setting is created into Holiday Master.

5-90

Operations of A-AUTO for UNIX / Windows

5.7.3

Edit Holiday Information
When there are changes to the holiday information for a calendar, you may edit the Holiday information in
Holiday Master
The following describe the steps for changing the information of a registered Holiday Table.
①

Click Holiday ID link on [Holiday Definition List] page.

②

The information of the selected Holiday Table is displayed on [Edit] page. Change the informationof the Holiday Table accordingly.

③ Click the [Apply] button to save the updated content into the Master.

Note■ If a Holiday Table is already used (associated) by a Schedule Pattern and you make changes to theholidays in the calendar, the information of the new holidays will apply only to the new Network Schedules
created by Auto Scheduling. Network Schedules that have already been created will not be updated. If you
want to reflect the changes in Holiday Table information to existing Network Schedules, you must firstremove and then re-establish the association between the Schedule Pattern and the Holiday Table.
For example, a created Holiday Table HOL00 (Holiday ID), which defines Sunday as weekly day off, isassociated with a Schedule Pattern SCHE00 (Schedule ID). SCHE00 is then associated with a Network
NETWK000 (Network ID). As the result, NETWK000 is scheduled on May 8 (Wed.). After Network
Schedule for NETWK000 is created, Annual Holiday of HOL00 is changed. The change in holiday will not
be reflected to the existing Network Schedule result. It will be reflected to the new Network Schedule result
after the change.
Changes to the information of a Holiday Table can also be reflected immediately to all Network Schedules,
both existing and new, by using Reschedule utility.
However, Reschedule utility will discard the modifications that have been done to existing Network
Schedules. So, you must re-apply the modifications to the Network Schedules after Reschedule utility.
Details of Reschedule utility will be explained later. Read the detailed explanation of this utility before usingit.
■ You may not modify dates shown in [Holiday Detail] that are after the current CPU Date of the Web
Server.

The following is an example of updating Holiday Table information.
e.g.5-35 Holiday Editing 1

Set non-fixed Holiday.

5-91

5 Application Definitione.g.5-35

Holiday Editing
HOL03 (Holiday ID ) has been created with day off, every Saturday, every Sunday and National Annual
Holiday.
6th and 7th of Golden Week, which are holidays, are to be set as working days. To compensate, set 13thand 20th as holidays. Perform the following steps to make the required changes.
① Click HOL03 link on [Holiday Definition List] page② HOL03 details are displayed on [Edit] page of Holiday
Definition.

<3> Double click 6 and then 7 on the calendar.
<4> This cancels the days off.
<5> Double click 13 and then 20 on the calendar.
<6> This set them as days off<7> Click [Apply] button.
<8> Setting is updated into Holiday Master.

5-92

Operations of A-AUTO for UNIX / Windows

5.7.4

Delete Holiday Information
When an Extended Job is no longer required, delete the registered Holiday information in Holiday Master.
The following describe the steps for deleting Holiday information.

① Check the check box of the Holiday ID of the target Holiday Table on [Holiday Definition List] page.
②

Click [Delete] button on the toolbar.

③ Confirmation Message box is displayed. Click [OK] button to delete. Otherwise, click [Cancel] button
to abort the delete operation. If you click [Delete], the selected Holiday will be deleted in Holiday
Master.

Note
You cannot delete a Holiday Table that has association with a Schedule Pattern (Please refer to Schedule
Master).
In this case, you have to remove the association before deleting the Holiday Table.

The following is an example of deleting a Holiday Table.
e.g.5-36 Holiday Deleting

Delete Holiday

5-93

5 Application Definitione.g.5-36

Holiday Deleting
When you want to delete HOL01 (Holiday ID ), perform the following steps.

<1> Check the checkbox of HOL01 on [Holiday
Definition List] page.
<2> Click [Delete] button.

<3> Confirmation message is displayed.
<4> Click [OK] button.
<5> HOL01 is deleted from Holiday Definition List.

5-94

Operations of A-AUTO for UNIX / Windows

5.7.5

Related Information Display
When you want to check which kind of Schedule ID the Holiday ID related. It’s necessary to perform
Search, by inputting Holiday ID, which you want to check, in Holiday ID of [Schedule-Search] page as a
keyword. When you want to check which Schedule Patterns are referred to by or associated with a Holiday
Table, use the [Schedule-Search] function.
Click [Search] icon on [Schedule Definition List] page. [Schedule-Search] dialog is displayed. Enter theHoliday ID of the Holiday Table, which you want to check, in [Holiday ID] textbox of [Schedule-Search]
page as a keyword and click [Search] button. The Schedule Patterns that used the Holiday Table aredisplayed on [Schedule Definition List] page.

5-95

5 Application Definition

5.8

Schedule Master
Schedule Master stores Schedule Patterns that are referred to by Networks. A Schedule Pattern contains
schedule information that A-AUTO for UNIX/Windows uses to generate an execution schedule for a
Network, i.e. the dates when the Network will execute.

5.8.1

Schedule Definition List
After starting A-AUTO/Web Client, click on a Monitor ID on [Application Definition] pane of the [A-AUTO
Main] Windows. Then, click [Schedule] on [List Menu] pane. The information of the Schedule Patterns in
Schedule Master will be displayed in list format. This list is called [Schedule Definition List] page ( refer tothe picture below).
[Schedule Definition List] page allows you to perform maintenance on the displayed Schedule Patterns.
Click [Create] button or a Schedule ID link on [Schedule Definition List] page, [Schedule-Create] or[Schedule-Edit] page is displayed.

5-96

Operations of A-AUTO for UNIX / Windows

5.8.2

Create Schedule Information
When you want to define a new set of schedule information, create a new Schedule Pattern in Schedule
Master. Schedule information to be registered includes frequency of executing the network e.g. daily,
weekly, and the Holiday Table to use.
The following describe the steps for creating Schedule Pattern information in Schedule Master.
① Click [Create] button of [Schedule Definition List] page.
②[Create] page of Schedule Definition is displayed. Set the necessary items in each tab according to
the requirements of the schedule information.

③ Click the [Apply] button to save the setting.
The following are examples of creating Schedule Patterns for different scheduling requirements.
Examplee.g. 5-37 Schedule Creating 1

Cycle
Daily

e.g. 5-38 Schedule Creating 2
e.g. 5-39 Schedule Creating 3

Every ndays
Weeklye.g. 5-40 Schedule Creating 4

Biweeklye.g. 5-41 Schedule Creating 5

Monthlye.g. 5-42 Schedule Creating 6

Scheduling requirements
Processing is every day
except holiday
Processing is every 5 days
Processing is on every Friday

Processing is on Wednesdayof every other week
Processing is on a specificday of every month
Processing is on the last dayof every monthe.g. 5-43 Schedule Creating 7

Processing is on the first
Wednesday of every monthe.g. 5-44 Schedule Creating 8

Processing is on a Reference
Date of every monthe.g. 5-45 Schedule Creating 9

Processing is on the next
WorkingDay
afteraReference Date of eachmonth
Processing is on a date thatis two Working Day before a
Reference Date of eachmonth
Processing is on Friday of
the final week of October toMarch every year

e.g. 5-46 Schedule Creating 10e.g. 5-47 Schedule Creating 11

e.g. 5-48 Schedule Creating 12

Months(Execution
Period)Semi-annually

Processing on a specific dayof March and September
every year

5-97

Shift Pattern
If the Processing Date is a holiday, do
not process
If the Processing Date is a holiday, do
not process
If the Processing Date is a holiday,
processing is shifted to the firstworking day after the holiday
Process even if the Processing Dateis a holiday
Process even if the Processing Dateis a holiday
If the Processing Date is a holiday,
processing is shifted to the lastworking day before the holiday
If the Processing Date is a holiday,
and the next day is also a holiday,
processing is shifted to the lastworking day before the holiday.
If the Reference Date is a holiday,
use the last Working Day before theholiday as the Reference Date.
If the Reference Date is a holiday,
use the next Working Day after theholiday as the Reference Date
Use the date as the Reference Dateeven if it is a holiday.

If the Processing Date is a holiday, do
not process

If the Processing Date is a holiday,
processing is shifted to the firstworking day after the holiday

5 Application Definition

e.g. 5-37

Schedule Creating 1 (Daily)
This Schedule Pattern is for daily processing and is to be effective from May 1, 2004. The Holiday
information is based on AUTOHOLT (Holiday ID). Do not process the application if it is a holiday. Name
this Schedule Pattern as DAILY01. A Schedule Pattern with these scheduling requirements can be createdas follows.
Schedule ID
Holiday Info (Holiday
ID )Process Cycle
Shift Pattern
Schedule Start Date
Schedule Period

DAILY01
AUTOHOLT
Daily Processing
Do not process, if Processing date is a holiday.
May 1, 2004
All year<1> Click [Create] button on [Schedule Definition List]
page.
<2> [Create] page of Schedule Definition is displayed.

<3> Input the required items.
■

Input DAILY01 in Schedule ID■

Input AUTOHOLT in Holiday ID■

Select Calendar on Process Pattern■

Select Daily for Process Cycle■

Select Do not process for Shift Pattern■

Select 1 to 31 for Execution Period<4> Click [Standard Processing Date] tab.

* You can enter the ID of a Holiday Table in [Holiday ID] textbox or select a registered Holiday Table fromthe Holiday Master.
To select a registered Holiday Table, click Holiday ID icon. [Select Holiday ID] dialog is displayed.

5-98Operations of A-AUTO for UNIX / Windows

Select the Holiday ID of a Holiday Table and then click the [Apply] button on the toolbar.
The selected Holiday ID is displayed in [Holiday ID] textbox<5> Click [Create] button.
<6> [Create] page of Standard Processing Date definition
is displayed.

<7> Input the required items.
■

Select yyyy/mm/dd for Standard Processing Day
Type■

Input 2004/5/1 for date of Standard Processing
Date<8>Click [Apply] button of [Standard Processing Date]
page.
<9> Standard Processing Date is registered.

<10> Click [Apply] button of [Schedule-Create] page.
<11> Setting is created into Schedule Master.

5-99

5 Application Definition

e.g. 5-38

Schedule Creating 2 (Every n days)
This Schedule Pattern is for any process that is to be executed every 5 days (Interval 4 days) and is to beeffective from April 5, 2008. The Holiday information is based on HOLT00 (Holiday ID). Do not process theapplication if it is a holiday. Name this Schedule Pattern as DAILY05. A Schedule Pattern with thesescheduling requirements can be created as follows.
Schedule ID
Holiday Info (Holiday
ID )Processing Cycle

DAILY05
HOLT00Every 5 days, Interval 4 days

Shift Pattern
Schedule Start Date
Schedule Period

If the Processing Date is a holiday, do not process
April 5, 2008
All year<1> Click [Create] button on [Schedule Definition List]
page.
<2> [Create] page of Schedule Definition is displayed.

<3> Input the required items.
■

Input DAILY05 in Schedule ID■

Input HOLT00 in Holiday ID■

Select Calendar for Processing Pattern■

Select Every n days for Process Cycle■

Select Do not process for Shift Pattern■

Select 1 to 31 for Execution Period<4> Click [Standard Processing Date] tab.
<5> Click [Create] button.
<6> [Create] page of Standard Processing Date definition isdisplayed.

<7> Input the required items.
■

Select yyyy/mm/dd for Standard Processing Day
Type■

Input 2008/04/05 for date of Standard Processing
Date<8>Click [Apply] button of [Standard Processing Date]page.
<9> Click [Apply] button of [Schedule-Create] page.
<10> Setting is created into Schedule Master.
5-100

Operations of A-AUTO for UNIX / Windows

e.g. 5-39

Schedule Creating 3 (Weekly)This Schedule Pattern is for any process that is to be executed every Friday and is to be effective from thefirst Friday of April 2004. The Holiday information is based on AUTOHOLT (Holiday ID). If the Processing
Date is a holiday, processing is to be shifted to the first working day after the holiday. Name this Schedule
Pattern as WEEKLY01. A Schedule Pattern with these scheduling requirements can be created as follows.

Schedule ID
Holiday Info (Holiday
ID )Processing Cycle
Shift Pattern
Schedule Start Date
Schedule Period

WEEKLY01
AUTOHOLT
Every Friday
If the Processing Date is a holiday, processing is to be shifted to thefirst working day after the holiday
The first Friday of April 2004
All year<1> Click [Create] button on [Schedule Definition List]
page.
<2> [Create] page of Schedule Definition is displayed.

<3> Input the required items.

<4> Click [Standard Processing Date] tab.

5-101

■

Input WEEKLY01 in Schedule ID■

Input AUTOHOLT in Holiday ID■

Select Calendar for Processing Pattern■

Select Weekly for Process Cycle■

Select The Day After for Shift Pattern■

Select 1/ to 12/ for Execution Period

5 Application Definition<5> Click [Create] button.
<6> [Create] page of Standard Processing Date definition isdisplayed.

<7> Input the required items.
■

Selectyyyy/mm/wk/wday

forStandard

Processing Day Type■

Input 2004/4/The First for date of Standard■

Check Fri for the day of week of Standard

Processing Date
Processing Date
<8>Click [Apply] button of [Standard Processing Date]page.
<9> Click [Apply] button of [Schedule-Create] page.
<10> Setting is created into Schedule Master.

5-102

Operations of A-AUTO for UNIX / Windows

e.g. 5-40

Schedule Creating 4 (Biweekly)This Schedule Pattern is for any process that is to be executed on Wednesday of every other week and is
to be effective from the first Wednesday of June 2004. The Holiday information is based on AUTOHOLT(Holiday ID). Processing is to be performed even if the Processing Date is a holiday. Name this Schedule
Pattern as WEEKLY02. A Schedule Pattern with these scheduling requirements can be created as follows.
Schedule ID
Holiday Info (Holiday
ID )Processing Cycle
Shift Pattern
Schedule Start Date
Schedule Period

WEEKLY02
AUTOHOLT
Wednesday of every other week
To be processed even if the Processing Date is a holiday
the first Wednesday of June 2004
All year<1> Click [Create] button on [Schedule Definition List]
page.
<2> [Create] page of Schedule Definition is displayed.

<3> Input the required items.

<4> Click [Standard Processing Date] tab.

5-103

■

Input WEEKLY02 in Schedule ID■

Input AUTOHOLT in Holiday ID■

Select Calendar for Processing Pattern■

Select Biweekly for Process Cycle■

Select On the day for Shift Pattern■

Select 1/ to 12/ for Execution Period

5 Application Definition<5> Click [Create] button.
<6> [Create] page of Standard Processing Date definition isdisplayed.

<7> Input the required items.
■

Selectyyyy/mm/wk/wday

forStandard

Processing Day Type■

Input 2004/6/The First for date of Standard
Processing Date■

Check Wed for the day of week of Standard
Processing Date

<8>Click [Apply] button of [Standard Processing Date]page.
<9> Click [Apply] button of [Schedule-Create] page.
<10> Setting is created into Schedule Master.

5-104

Operations of A-AUTO for UNIX / Windows

e.g. 5-41

Schedule Creating 5 (Monthly, Specific day of every month)This Schedule Pattern for any process that is to be executed on 20th of every month and is to be effectivefrom May 20, 2004. The Holiday information is based on AUTOHOLT (Holiday ID). Processing is to be
performed even if the Processing Date is a holiday. Name this Schedule Pattern as MONTHLY01. A
Schedule Pattern with these scheduling requirements can be created as follows.
Schedule ID
Holiday Info (Holiday
ID )Processing Cycle
Shift Pattern
Schedule Start Date
Schedule Period

MONTHLY01
AUTOHOLT
20th of every month
To be processed even if the Processing Date is a holiday
May 20, 2004
All year<1> Click [Create] button on [Schedule Definition List]
page.
<2> [Create] page of Schedule Definition is displayed.

<3> Input the required items.
■

Input MONTHLY01 in Schedule ID■

Input AUTOHOLT in Holiday ID■

Select Calendar for Processing Pattern■

Select Monthly for Process Cycle■

Select On the day for Shift Pattern■

Select 1/ to 12/ for Execution Period<4> Click [Standard Processing Date] tab.

5-105

5 Application Definition<5> Click [Create] button.
<6> [Create] page of Standard Processing Date isdisplayed.

<7> Input the required items.
■

Select yyyy/mm/dd for Standard Processing Day

■

Input

Type
2004/5/20

for

the

date

of

Standard

Processing Date
<8>Click [Apply] button of [Standard Processing Date]page.

<9> Click [Apply] button of [Schedule-Create] page.
<10> Setting is created into Schedule Master.

5-106

Operations of A-AUTO for UNIX / Windows

e.g. 5-42

Schedule Creating 6 (Monthly, End of Month)This Schedule Pattern for any process that is to be executed on the last day of every month and is to beeffective from July 2004. The Holiday information is based on AUTOHOLT (Holiday ID). If the Processing
Date is a holiday, processing is to be shifted to the last working day before the holiday. Name thisSchedule Pattern as MONTHLY02. A Schedule Pattern with these scheduling requirements can be createdas follows.
Schedule ID
Holiday Info (Holiday
ID )Processing Cycle
Shift Pattern
Schedule Start Date
Schedule Period

MONTHLY02
AUTOHOLT
Last day of every month
If the Processing Date is a holiday, processing is to be shifted to the lastworking day before the holiday
The last day ( 31 ) of July 2004
All year<1> Click [Create] button on [Schedule Definition List]
page.
<2> [Create] page of Schedule Definition is displayed.

<3> Input the required items.

<4> Click [Standard Processing Date] tab.

5-107

■

Input MONTHLY02 in Schedule ID■

Input AUTOHOLT in Holiday ID■

Select Calendar for Processing Pattern■

Select Monthly for Process Cycle■

Select The Day Before for Shift Pattern■

Select 1/ to 12/ for Execution Period

5 Application Definition<5> Click [Create] button.
<6> [Create] page of Standard Processing Date definition isdisplayed.

<7> Input the required items.
■

Select yyyy/mm/dd for Standard Processing Day
Type

■

Input

2004/7/EOM

for

date

of

Standard

Processing Date
<8>Click [Apply] button of [Standard Processing Date]page.
<9> Click [Apply] button of [Schedule-Create] page.
<10> Setting is created into Schedule Master.

5-108

Operations of A-AUTO for UNIX / Windows

e.g. 5-43

Schedule Creating 7 (Monthly, Specific day of a specific week)
This Schedule Pattern is for any process that is to be executed on the first Wednesday of every month andis to be effective from the first Wednesday of April 2004. The Holiday information is based on AUTOHOLT(Holiday ID). If the Processing Date is a holiday and the next day is also a holiday, processing is to be
shifted to the last Working Day before the holiday. Name this Schedule Pattern as MONTHLY03. A
Schedule Pattern with these scheduling requirements can be created as follows.
Schedule ID
Holiday Info (Holiday
ID )Processing Cycle
Shift Pattern
Schedule Start Date
Schedule Period

MONTHLY03
AUTOHOLT
The first Wednesday of every month
If the Processing Date is a holiday and the next day is also a holiday, theprocessing is to be shifted to the last Working Day before holiday
The first Wednesday of April 2004
All year<1> Click [Create] button on [Schedule Definition List]
page.
<2> [Create] page of Schedule Definition is displayed.

<3> Input the required items.
■

Input MONTHLY03 in Schedule ID■

Input AUTOHOLT in Holiday ID■

Select Calendar for Processing Pattern■

Select Monthly for Process Cycle■

Select After: Before if 2-day off for Shift
Pattern■<4> Click [Standard Processing Date] tab.

5-109

Select 1/ to 12/ for Execution Period

5 Application Definition<5> Click [Create] button.
<6> [Create] page of Standard Processing Date definition isdisplayed.

<7> Input the required items.
■

Selectyyyy/mm/wk/wday

forStandard

Processing Day Type■

Input 2004/4/The First for date of Standard
Processing Date■

Check Wed for the day of the week of Standard
Processing Date

<8>Click [Apply] button of [Standard Processing Date]page.
<9> Click [Apply] button of [Schedule-Create] page.
<10> Setting is created into Schedule Master.

5-110

Operations of A-AUTO for UNIX / Windows

e.g. 5-44

Schedule Creating 8 (Monthly, On the day of Reference Date)
This Schedule Pattern is for any process that is to be executed every month on the Reference Date, whichis to be set as (25th) of every month, and is to be effective from April 2004. The Holiday information isbased on AUTOHOLT (Holiday ID). If the Reference Date is a holiday, use the last Working Day before theholiday as the Reference Date. Name this Schedule Pattern as MONTHLY04. A Schedule Pattern withthese scheduling requirements can be created as follows.
Schedule ID
Holiday Info (Holiday
ID )Processing Cycle
Reference Date
Shift Pattern
Schedule Start Date
Schedule Period

MONTHLY04
AUTOHOLT
Every month on the Reference Date
25th
If the Reference Date is a holiday, use the last Working Day before theholiday as the Reference Date.
April 2004
All year<1> Click [Create] button on [Schedule Definition List]
page.
<2> [Create] page of Schedule Definition is displayed.

<3> Input the required items.

<4> Click [Standard Processing Date] tab.

5-111

■

Input MONTHLY04 in Schedule ID■

Input AUTOHOLT in Holiday ID■

Select Working Day for Processing Pattern■

Select 25 for Set Date of Reference Date■

Select Monthly for Process Cycle■

Select The Day Before for Shift Pattern■

Select 1/ to 12/ for Execution Period

5 Application Definition<5> Click [Create] button.
<6> [Create] page of Standard Processing Date definition is<7> Input the required items.
■

Select yyyy/mm/+- for Standard Processing Day
Type■

Select 2004/4FiscalMonth/-1 for date of Standard
Processing Date

<8> Click [Apply] button of [Standard Processing Date]page.

<9> Click [Apply] button of [Schedule-Create] page.
<10> Setting is created into Schedule Master.

5-112

Operations of A-AUTO for UNIX / Windows

e.g. 5-45

Schedule Creating 9 (Monthly, Next Working Day of Reference Date)
This Schedule Pattern is for any process that is to be executed every month on the next working day of theReference Date, which is to be set as (Friday of last week ), and is to be effective from 4th Fiscal Month of
2004. The Holiday information is based on AUTOHOLT (Holiday ID). If the Reference Date is a holiday,
use the next Working Day after the holiday as the Reference Date. Name this Schedule Pattern as
MONTHLY05. A Schedule Pattern with these scheduling requirements can be created as follows.
Schedule ID
Holiday Info (Holiday
ID )Processing Cycle
Reference Date
Shift Pattern
Schedule Start Date
Schedule Period

MONTHLY05
AUTOHOLT
Every month on the next Working Day of the Reference Date
Friday of last week
If the Reference Date is a holiday, use the next Working Day before theholiday as the Reference Date
4th Fiscal Month of 2004
All year<1> Click [Create] button on [Schedule Definition List]
page.
<2> [Create] page of Schedule Definition is displayed.

<3> Input the required items.
■

Input MONTHLY05 in Schedule ID■

Input AUTOHOLT in Holiday ID■

Select Working Day for Processing Pattern■

Select The Final Fri for Designation Day ofMonth of Reference Date

<4> Click [Standard Processing Date] tab.

■

Select Monthly for Process Cycle■

Select The Day After for Shift Pattern■

Select 1/ to 12/ for Execution Period

5-113

5 Application Definition<5> Click [Create] button.
<6> [Create] page of Standard Processing Date definition isdisplayed.

<7> Input the required items.
■

Select yyyy/mm/+- for Standard Processing Day
Type■

Select 2004/4FiscalMonth/+1 for date of Standard
Processing Date■
<8> Click [Apply] button of [Standard Processing Date].

<9> Click [Apply] button of [Schedule-Create] page.
<10> Setting is created into Schedule Master.

5-114

Operations of A-AUTO for UNIX / Windows

e.g. 5-46

Schedule Creating 10 (Monthly, 2 Working Day before Reference Date)
This Schedule Pattern is for any process that is to be executed every month on a date that is two working
days before the Reference Date, which is to be set as Last day of Every month, and is to be effective from4th Fiscal Month of 2004. The Holiday information is based on AUTOHOLT (Holiday ID). Use the samedate as the Reference Date even if it is a holiday. Name this Schedule Pattern as MONTHLY06. A
Schedule Pattern with these scheduling requirements can be created as follows.
Schedule ID
Holiday Info (Holiday
ID )Processing Cycle
Reference Date
Shift Pattern
Schedule Start Date
Schedule Term

MONTHLY06
AUTOHOLT
Every month on a date that is 2 Working Days before the Reference Date
Last day of every month
Use the same date as the Reference Date even if it is a holiday.
4th Fiscal Month of 2004
All year<1> Click [Create] button on [Schedule Definition List]
page.
<2> [Create] page of Schedule Definition is displayed.

<3> Input the required items.
■

Input MONTHLY06 in Schedule ID■

Input AUTOHOLT in Holiday ID■

Select Working Day for Processing Pattern■

Select The Final for Set Date of Reference
Date■

Select Monthly for Process Cycle■

Select On the day for Shift Pattern■

Select 1/ to 12/ for Execution Period<4> Click [Standard Processing Date] tab.

5-115

5 Application Definition<5> Click [Create] button.
<6> [Create] page of Standard Processing Date definition isdisplayed.

<7> Input the required items.
■

Select yyyy/mm/+- for Standard Processing Day
Type■

Select 2004/4FiscalMonth/-3 for date of Standard
Processing Date■
<8> Click [Apply] button of [Standard Processing Date].

<9> Click [Apply] button of [Schedule-Create] page.
<10> Setting is created into Schedule Master.

5-116

Operations of A-AUTO for UNIX / Windows

e.g. 5-47

Schedule Creating 11 (Monthly, Execution Period Limit)
This Schedule Pattern is for any process that is to be executed on last Friday of every month, but limited tomonths of October to March every year, and is to be effective fromOctober 2004. The Holiday information
is based on AUTOHOLT (Holiday ID). If the Processing Date is a holiday, do not process. Name thisSchedule Pattern as MONTHLY07. A Schedule Pattern with these scheduling requirements can be createdas follows.
Schedule ID
Holiday Info (Holiday
ID )Processing Cycle
Reference Date
Shift Pattern
Schedule Start Date
Schedule Period

MONTHLY07
AUTOHOLT
Last Friday of every month but limited to months of October to March
every year
None
If the Processing Date is a holiday, do not process
Last Friday of October 2004
October ~ March<1> Click [Create] button on [Schedule Definition List]
page.
<2> [Create] page of Schedule Definition is displayed.

<3> Input the required items.

<4> Click [Standard Processing Date] tab.

5-117

■

Input MONTHLY07 in Schedule ID■

Input AUTOHOLT in Holiday ID■

Select Calendar for Processing Pattern■

Select Monthly for Process Cycle■

Select Do not Shift for Shift Pattern■

Select 10/ to 3/ for Execution Period

5 Application Definition<5> Click [Create] button.
<6> [Create] page of Standard Processing Date definition is<7> Input the required items.
■

Select yyyy/mm/wk/wday for Standard
Processing Day Type■

Select 2004/10/The Final for date of Standard
Processing Date■

Check Fri for the day of the week of Standard
Processing Date

<8> Click [Apply] button of [Standard Processing Date]page.

<9> Click [Apply] button of [Schedule-Create] page.
<10> Setting is created into Schedule Master.

5-118

Operations of A-AUTO for UNIX / Windows

e.g. 5-48

Schedule Creating 12 (Semi-annually)
This Schedule Pattern is for any process that is to be executed on 28th of March and September every
year and is to be effective from September 2004. The Holiday information is based on AUTOHOLT(Holiday ID). If the Processing Date is a holiday, processing is to be shifted to the first working day after
holiday. Name this Schedule Pattern as HALF01. A Schedule Pattern with these scheduling requirements
can be created as follows.
Schedule ID
Holiday Info (Holiday
ID )Processing Cycle
Reference Date
Shift Pattern
Schedule Start Date
Schedule Term

HALF01
AUTOHOLT
Every year on 28th of March and September
None
If the Processing Date is a holiday, the processing is to be shifted to thefirst working day after the holiday
September 28, 2004
All year<1> Click [Create] button on [Schedule Definition List] page<2> [Create] page of Schedule Definition is displayed.

<3> Input the required items.

<4> Click [Standard Processing Date] tab.

5-119

■

Input HALF01 in Schedule ID■

Input AUTOHOLT in Holiday ID■

Select Calendar for Processing Pattern■

Select Semiannually for Process Cycle■

Select The Day After for Shift Pattern■

Select 1/ to 12/ for Execution Period

5 Application Definition<5> Click [Create] button.
<6> [Create] page of Standard Processing Date definition is<7> Input the required items.
■

Select yyyy/mm/dd for Standard Processing Day
Type■

Select 2004/9/28 for date of Standard Processing
Date<8> Click [Apply] button of [Standard Processing Date]page.

<9> Click [Apply] button of [Schedule-Create] page.
<10> Setting is created into Schedule Master.

5-120

Operations of A-AUTO for UNIX / Windows

5.8.3

Edit Schedule Information
When there are changes to the Scheduling information, you may edit the Schedule Pattern in Schedule
Master.
The following describe the steps for changing the schedule information of a registered Schedule Pattern.
①

Click the Schedule ID link on [Schedule Definition List] page.

②[Edit] page of Schedule Definition is displayed.

③ Change the information of the Schedule Pattern accordingly.
④ Click the [Apply] button to save the updated content into Master.

Note

If you change the information of Schedule ID that have been related with Network. The changing
won’t be reflected to the Network Schedule. If you want to reflect the changing, please remove therelation and relate again. However, the changed Schedule Master Information will be reflected if the
it’s was added by Auto Scheduling. If a Schedule Pattern is already associated with a Network andyou make changes to the schedule information in the Schedule Pattern, the updated schedule
information will apply only to the new Network Schedules created by Auto Scheduling. Network
Schedules that have already been created will not be updated. If you want to reflect the changes inschedule information to existing Network Schedules, you must first remove and then re-establish theassociation between the Schedule Pattern and the Network.



Changes to the information of a Schedule Pattern can also be reflected immediately to all Network
Schedules, both existing and new, by using Reschedule utility.
However, Reschedule utility will discard the modifications that have been done to existing Network
Schedules. So, you must re-apply the modifications to the Network Schedules after Reschedule utility.
Details of Reschedule utility will be explained later. Read the detailed explanation of this utility before
using it.

The following is an example of updating Schedule Pattern information.
e.g.5-49 Schedule Editing

Update the Standard Processing Date

5-121

5 Application Definition

e.g. 5-49 Schedule Editing
The Schedule Pattern WEEKLY01 (Schedule ID ), which has been registered in Schedule Master, is to bechanged from Friday of every week to Wednesday and Friday of every week.

<1> Go to [Schedule Definition List] page<2> Click WEEKLY01 link
<3> [Edit] page of Schedule Definition is displayed.

<4> Click [Standard Processing Date] tab.

<5> [Edit] page of Standard Processing Date isdisplayed.

<6> Input the required items.
■

Check Wed for the week of day of Standard
Processing Date

<7> Click [Apply] button of Standard Processing Date.

<8> Click [Apply] button of [Schedule-Create]page.
<9> Updated content is saved into Schedule
Master.

5-122

Operations of A-AUTO for UNIX / Windows

5.8.4

Delete Schedule Information
When schedule information is no longer required, delete the registered Schedule Pattern in Schedule
Master.
The following describe the steps for deleting a Schedule Pattern.
① Check the check box of the Schedule ID of the target Schedule Pattern to be deleted on [ScheduleDefinition List] page.
②

Click [Delete] button on the toolbar.
Confirmation Message box is displayed. Click [OK] button to delete, otherwise click [Cancel] button
to abort the delete. If you click [Delete], the selected Schedule Pattern will be deleted in Schedule
Master.

Note
You cannot delete a Schedule Pattern that has association with a Network.
In this case, you have to remove the association before deleting the Schedule Pattern.

The following is an example of deleting a Schedule Pattern.
e.g.5-50 Schedule Deleting

Delete Schedule Pattern

5-123

5 Application Definition

e.g. 5-50 Schedule Deleting
When you want to delete DAILY01 (Schedule ID ), perform the following steps.

<1> Check the checkbox of DAILY01 on [ScheduleDefinition List].
<2> Click [Delete] button.

<3> Confirmation message is displayed.
<4> Click [OK] button.
<5> DAILY01 is deleted from Schedule Definition List.

5-124

Operations of A-AUTO for UNIX / Windows

5.9

Network Schedule Master
This section describes creation and modification of application schedules (refer to as Network Schedules).
A Network Schedule of a Network contains the dates of when a Network is scheduled to execute, based onschedule information of one or more Schedule Patterns. Network Schedules are displayed on [Network
Schedule List] page.
There are 3 ways of creating and modifying a Network Schedule.
①

Associate a Network with one or more Schedule Patterns to create Network Schedules②

Manually setting date(s)③Adjusting or modifying existing Network Schedules<1> Associate a Network with one or more Schedule
Patterns
Create a Network Schedule for a Network by associating its Network ID with one or more Schedule IDs of
Schedule Patterns. Using this method, the Network Schedule information of 12 months, starting from themonth that the association is performed, will be created into Schedule Master.
(If you use the Previous Month Schedule Function, the Network Schedule information of 12 months,
starting from one month before the month that the association is performed. For more information on thisfunction, please refer to [8.11 Previous Month Schedule Function])
For example, if you associate Network [GYOUMUA] with Schedule Pattern [DAYLYE1] on April 5, 2004,
the resulting Network Schedule createdwill contain schedule dates from April 1, 2004 to the last day of

Match 2005.
The Network Schedule of a Network that is associated with one or more Schedule Patterns can be updated
by executing Auto Scheduling.
<2> Set any date
Create a Network Schedule for a Network by manually setting Schedule Dates. In this case, a Network is
not associated with any Schedule Pattern. This is referred to as Irregular Schedule.
Such Network Schedules will not be updated when you perform Auto Scheduling.
To create an Irregular Schedule, check the Irregular check box on [Network Schedule-Create] or [Network
Schedule-Edit] page.
Double clicking on a date in the calendar of this dialog to highlight it will mark the schedule to be added forthat date.

Similarly, double clicking on a highlighted date will remove the schedule for that date.

The highlighted dates shown on calendar in the final display are the schedule dates for the Network. Click[Apply] button and the result is displayed on [Network Schedule Definition List] page.

5-125

5 Application Definition<3>

Adjustingor

Modifying

Existing

Network

Schedules
You can use either the Network Schedule on [Network Schedule List] page, the calendar on [Network
Schedule-Edit] page or [Daily Network Schedule Detail] page to adjust or modify the Network Schedules.
There are 2 categories of changes that can be performed on Network Schedules, modifying schedule
dates and making temporary changes to Network attributes of the related Network Schedules.
Adding/Deleting/Moving Schedule Dates
You can perform the adding/deleting/moving of Schedule Dates on [Network Schedule-Edit]

page or[Network Schedule List] page.
There are differences in operation between using [Network Schedule List] page and using the
Calendar of [Network Schedule-Edit] page.


If a Network schedule is modified using [Network Schedule-Edit] page, the Network Schedule
will be updated by Auto Scheduling facility to reflect the latest change.
Therefore, if the operator does not want to execute Auto Scheduling, he/she must update
schedule using [Network Schedule List] page.



If [Network Schedule List] page is used, update is done in one single operation. In contrast,
update using [Network Schedule-Edit] page requires several steps. The operator must first clicka Network ID, perform the update and then click ［Apply］button. Several changes can be madeto a Network Schedule before clicking [Apply] to confirm modifications. Until the [Apply] is clicked,
no change is made to the Network Schedule Master.



Temporary Changes to the Network information of a Network for certain schedule dates.
You can perform temporary update to Network attributes of a Network using [Daily Network Schedule
Detail] page. Changes to Network attributes using [Daily Network Schedule Detail] page will apply to
the Network for a specific schedule date being changed. Original attributes of the Network in Network
Master remain unchanged.
(e.g. Change the Start Time of a Network for a specific day)
* The Network Schedule, which with different Valid Date in the same Network Name, the authority ofeach Valid Date must be granted. About the granting of authority, please refer to “8. User
Management Faction” of System Administrator's Guide.

5-126

Operations of A-AUTO for UNIX / Windows

5.9.1

Network Schedule List
After starting A-AUTO/Web Client, click on a Monitor ID on [Application Definition] pane of the [A-AUTO
Main] Windows. Then, click [Network Schedule] on [List Menu] pane.
Use [Network Schedule List] page of A-AUTO/Web Client to register Network Schedule information, or to
edit/delete/search the registered Network Schedule.
The information of the Network Schedules in Network Schedule Master will be displayed in list form. This
list is called [Network Schedule List] page ( refer to the picture below). This Windows shows the assigned[Network Schedule List] page i.e. Network Schedules that have been registered by associating Networks
with one or more Schedule Patterns, or Irregular Schedule.

You can switch to unassigned [Network Schedule List] page by clicking the [Switch] icon on the toolbar.
The differences between unassigned [Network Schedule List] and assigned [Network Schedule List] will be
explained and shown later.
Assigned [Network Schedule List] page allows you to perform maintenance on the displayed registered
Network Schedules. Unassigned [Network Schedule List] page allows you to perform maintenance on
Networks that have not been associated with any Schedule Pattern or Irregular Schedule.

5-127

5 Application Definition■ Network Schedule List
The following diagrams show assigned [Network Schedule List] page and the [Detail] page of Network
Schedule.

Assigned [Network Schedule List] will display one-month calendar showing the dates that each Network
are scheduled for execution. The column lists Network IDs of Networks with Network Schedules and eachrow shows an icon on each cell of the date. The icon represents the schedule status as follows.
(blank) : Has not been scheduled for execution: Has been scheduled for execution: Has been scheduled and Network information of this Network Schedule has been changed
temporarily
The calendar to the right of [Network Schedule Detail] page highlights dates in different colors, showing thedifferent schedule status as follows..
Calendar background color: Has not been scheduled (Depending PC’s setting the color may bedifferent)(Green Highlight) : Has been scheduled(Pea Green Highlight) : Has been scheduled and Network information of this Network Schedule has
been changed temporarily
The possible period for display is from 1 day to 2 year.
(2 years (24 Months) starting from the CPU date (Year/Month))

5-128

Operations of A-AUTO for UNIX / Windows

5.9.2

Network Schedule Menu
Click the [Menu] icon on the toolbar of [Network Schedule List], the [Network Schedule Menu] page isdisplayed.

(1) Queuing
You can perform the Queuing by clicking the [Queuing] button on the dialog. For information on Queuing,please refer to [6.4 Queuing].

(2) Display Period
You can set the necessary Display Period on [Network Schedule List] page .
(Please refer [5.9.9 Display Period Setting] for details)(3) Network GroupA list of Network Groups is displayed.
Click a Group ID link and Networks that belong to the specified Group will be displayed on the [Network
Schedule List] page.

5-129

5 Application Definition

5.9.3

Create Network Schedule Information
When you want to define a new schedule for a Network, create a new Network Schedule in Network
Schedule Master.
The following describe the steps for creating a new Network Schedule in Network Schedule Master.
① Click the Network ID link of the Network that you want to create a Network Schedule on Unassigned[Network Schedule List].
②[Edit] page of [Network Schedule Detail] is displayed.
If there is a regular cycle for processing the Network, select the appropriate Schedule Pattern(s) tobe associated. Otherwise, check the Irregular check box to process it as Irregular Schedule.

③ The schedule dates of the Network based on the associated Schedule Pattern(s) will be displayedon the calendar. If you check the Irregular, please double click each date on calendar directly to
select the schedule dates for the Network. Adjust Network Schedule, if necessary. For adjustment
or modifications of Schedule, please refer to [5.9.7 Adjust Schedule].
④ Click the [Apply] button to save the setting.
The following are examples of creating Network Schedules.
e.g. 5-51 Network Schedule Creating
1
e.g. 5-52 Network Schedule Creating
2
e.g. 5-53 Network Schedule Creating3

Schedule according to Single Schedule Pattern
Schedule according to Multiple Schedule Patterns
Irregular Schedule

5-130

Operations of A-AUTO for UNIX / Windows

e.g. 5-51 Network Schedule Creating 1
If you want to create a daily Network Schedule to process application named GYOUMUA (Network),
perform the following steps.

<1> Click GYOUMUA link on unassigned [Network
Schedule List] page<2> [Edit] page of [Network Schedule Definition] isdisplayed.

<3> Select DAILY01 on Schedule ID list.
<4> Click [←] button.
<5> DAILY01 is moved to Selected Schedule ID list

<6> The Schedule Dates for the Network are highlighted on
the calendar.
<7> Click [Apply] button.
<8> Setting is registered into Network Schedule Master.

5-131

5 Application Definition

E.g. 5-52 Network Schedule Creating 2
If you want to create Network Schedule for application named GYOUMUB (Network), which is based on 2
Schedule Patterns, WEEKLY01 (Schedule ID) and MONTHLY01 (Schedule ID), perform the following
steps.

<1> Click GYOUMUB link on the unassigned [Network
Schedule List] page.
<2> [Edit] page of [Network Schedule Definition] isdisplayed.

<3> Select WEEKLY01 and MONTHLY01 from Schedule ID list.
<4> Click [←] button.
<5> WEEKLY01 and MONTHLY01 are moved to Selected
Schedule ID list

<6> The Schedule Dates for the Network are highlighted
on the calendar.

<7> Click [Apply] button.
<8> Setting is registered into Network Schedule Master.

5-132

Operations of A-AUTO for UNIX / Windows

e.g. 5-53 Network Schedule Creating 3
If you want to create Network Schedule for GYOUMUC (Network) whose processing does not follow a
regular cycle, Network Schedule has to be an Irregular Schedule. Perform the following steps to create anirregular Schedule.
<1> Click GYOUMUC link on the unassigned [Network
Schedule List] page.
<2> [Edit] page of [Network Schedule Definition] isdisplayed.

<3> Check the checkbox of [Irregular].
<4> Set Execution ID to “0”<6> Double click each date on the calendar that you wantto schedule the Network for processing. The ScheduleDates set are highlighted on the calendar.

<7> Click [Apply] button.
<8> Setting is registered into Network Schedule Master.

5-133

5 Application Definition

5.9.4

Edit Network Schedule Information
When there are changes to the Scheduling information for a Network, you may edit the Network Schedule
information in Network Master.
The following describe the steps for changing the information of a registered Network Schedule.

① Click Network ID link of the target Network Schedule on assigned [Network Schedule List] page.
② [Edit] page of Network Schedule Definition is displayed.
③ Change the information of the Network Schedule accordingly.
④ Click the [Apply] button to save the updated content into Master.
The following is an example of updating Network Schedule information.
e.g. 5-54 Network Schedule Editing1

Schedule Pattern Updating

5-134

Operations of A-AUTO for UNIX / Windows

e.g. 5-54 Network Schedule Updating
Network Schedule of GYOUMUB (Network) has been created by associating the Network with Schedule
Patterns “WEEKLY01” and “MONTHLY01”. If you want to change the scheduling of GYOUMUB to“WEEKLY01” only, perform the following steps.

<1> Click GYOUMUB link on assigned [Network ScheduleList] page.
<2> [Edit] page of Network Schedule Definition isdisplayed.

<3> Select MONTHLY01 on [Selected Schedule ID] list
<4> Click [→] button.
<5> MONTHLY01 is moved to [Schedule ID] list.

<6>Click [Apply] button.
<7> Setting is updated into Network Schedule Master.

5-135

5 Application Definition

5.9.5

Delete Network Schedule Information
When Network Schedule information is no longer required, delete the registered Network Schedule in
Network Schedule Master. When you delete a Network Schedule, all schedule dates that the Network isscheduled for execution will be deleted.

Auto Scheduling will no longer create or update the Network

Schedule of the Network.
The following describe the steps for deleting a Network Schedule.
① Check the check box of the Network ID of the target Network Schedule to be deleted on [Network
Schedule Definition List] page.
② Click [Delete] button on the toolbar.
When the selected Network Schedule of a Network is deleted, the related Network information in
Daily Network Master will also be deleted.
If the [Network Schedule Detail] page is non-displayed status, you can delete plural Network Schedule inthe same time.

The following is an example of deleting a Network Schedule.
e.g. 5-55 Network Schedule Deleting

Delete Network Schedule

5-136

Operations of A-AUTO for UNIX / Windows

e.g. 5-55 Schedule Deleting
If you want to delete the Network Schedule of GYOUMUB (Network), perform the following steps.

<1> Check the checkbox of GYOUMUB on assigned[Network Schedule List].
<2> Click [Delete] button.

<3> Confirmation message is displayed.
<4> Click [OK] button.
<5> GYOUMUB is deleted from assigned [Network
Schedule List]. If you click the [Switch] icon, it will be
displayed on unassigned

5-137[Network Schedule List].

5 Application Definition

5.9.6

About Exclusion Schedule Setting
Exclusion Schedule is used to exclude or remove certain execution schedule dates generated by theselected Schedule Patterns (without Exclusion Schedule option).

The following is an example of using Exclusion Schedule and the procedures to define it.
In the example, an existing Network is scheduled to execute daily using Schedule Pattern SCH01 with
Process Cycle “Daily”.

The new requirement specifies that the Network is not to execute on 3rd Saturday

and the last day of every month. To meet the new scheduling requirement of the Network, create a new
Schedule Pattern, SCH03. The new Schedule Pattern is registered with Process Cycle “Monthly” and two
Standard Processing Dates of “End of Month” and “3rd Saturday”.

(To register Schedule Pattern, pleaserefer to “5.8 Schedule Master”)<1> Click Network ID link of the target Network Scheduleon assigned [Network Schedule List].
<2> [Edit] page of Network Schedule Definition isdisplayed.

<4> Set the Exclusion Schedule on SCH03 (Schedule ID).
Select SCH03 (running on the third Sat and last day ofmonth.)<5> Click [←] button.

5-138

Operations of A-AUTO for UNIX / Windows

SCH03 is added to [Selected Schedule ID] list and theSimulation result is displayed on [Schedule Simulation]
calendar on the right side.

<6> Make sure the SCH03 has been set as ”ON” on[Selected Schedule ID] list and then click [Apply] button.

5-139

5 Application Definition

5.9.7

Adjust Schedule
You can perform the temporary modification by adding, deleting or removing the Schedule Date of created
Network Schedule.

Note
Adjustable period schedule will be in the following ranges.
From one day before Web Client running OS’ CPU Date.



Until the end of the Scheduled Term Network Schedule of the individual to hold.
(Scheduled Term is present one year; the period is different for each Network in the context of an
automatic schedule.)

For example, for maintaining the Network’s Schedule information that from April 2004 to March 2005. If tomodify the schedule in April 21, 2004, the range is April 2004 20 to 2005 March 31.
As well, in the case of modifying the schedule in May 21, 2004, the range is May 20, 2004 to March 31,
2005.
* If the described Previous Month Schedule Function is enable, the modifying range is (one month before
Web Client running OS’ CPU Date.) -1 day hereafter ~Will be the end of the Scheduled Term Network Schedule individual holds.
(About this function, please refer to [8.11 Previous Month Schedule Function])

5-140

Operations of A-AUTO for UNIX / Windows(1) Schedule Date Adding
The following describe the steps of adding a Schedule Date on [Network Schedule List] page.
① Display the assigned [Network Schedule List] page.
② Click the cell of the target Network Schedule’s date that you want to add a schedule date on
assigned [Network Schedule List].
③ The Pop-up menu of the selected cell is displayed. Select [Add Schedule Date]. ( You can display
Pop-up menu by pressing the left mouse key)
④ The schedule date is added to the selected date.

The following is an example of adding a Schedule Date.
e.g.5-56 Schedule Date Adding 1

Add Schedule Date on Network Schedule List

5-141

5 Application Definition

e.g. 5-56 Schedule Date Adding 1
When you want to add a single Schedule Date to GYOUMUB, perform the following steps.

<1> Click the cell of the target date of GYOUMUB on assigned[Network Schedule List] page<2> Pop-up Menu is displayed.
<3> Select [Add Schedule Date].

<4> The schedule date is added

5-142

Operations of A-AUTO for UNIX / Windows(2) Schedule Date Deleting
The following describe the steps of deleting a Schedule Date on [Network Schedule List] page.
① Display the assigned [Network Schedule List] page.
② Click the cell of the target Network Schedule’s schedule date that you want to delete on assigned[Network Schedule List] page.
③ The Pop-up menu of the selected cell is displayed. Select [Delete Schedule Date]. ( You can also
display Pop-up menu by pressing the left mouse key)
④ Confirmation Message dialog is displayed. Click [OK] button to delete, or [Cancel] to abort thedelete. When you click [OK] button on confirmation message, the selected Schedule Date is deleted
from [Network Schedule List] page.
⑤ The selected cell’s Schedule Date is deleted in Network Schedule Master.

The following is an example of deleting a Schedule Date.
e.g.5-57 Schedule Date Deleting 1

Deleting a Schedule Date on Network Schedule List

5-143

5 Application Definition

e.g. 5-57 Schedule Date Deleting1 (Network Schedule List, Single Day Deleting)
When you want to delete a single Schedule Date of GYOUMUB, perform the following steps.

<1> Select the cell of the target Schedule Date of GYOUMUB
on assigned [Network ScheduleList] page<2> Pop-up Menu is displayed.
<3> Select [Delete Schedule Date].

<4> Click the [OK] button on confirmation message.

<5> The schedule date is deleted

5-144

Operations of A-AUTO for UNIX / Windows(3) Adjusting on Network Schedule Detail page
You can adjust the schedule date(s) on [Network Schedule Detail] page.
The following describe the steps of adjusting a Network Schedule on [Network Schedule Detail] page.
① Display the assigned [Network Schedule List] page.
② Click the Network ID link of the target Network Schedule on assigned [Network Schedule List] page.
③[Edit] page of Network Schedule Definition is displayed.
Perform the adjusting (Adding/Deleting/Moving Operation)④ Click [Apply] button to save the updated Network Schedule.

Hint
You can check the operation of add/delete/move, when you click [Apply] button on [Network Schedule
Detail] page.

5-145

5 Application Definition(4) Schedule Date’s All Adjust (Term Set)
You can add or delete a range of Schedule Dates of a single Network Schedule in a single operation.
The following describe the steps to add or delete a range of Schedule Dates of a Network Schedule using[Term Set] dialog.
① Display the assigned [Network Schedule List] page.
② Check the check box of [All Adjust Mode].
③ Check the check box of the Network ID whose Network Schedule you want to modify.
④ Click the [Term Set] button on the toolbar.
[Term Set] dialog is displayed.
⑤ Set a range of dates for the operation in [Period] and then click [Add] button or [Delete] button.

Note
If a Network Schedule already has a Schedule Date in the specified period, “Add” of [Term Set] will ignore
the addition for that date. Delete for [Term Set] can be performed using the similar process as above.
The start date of [Period] on [Term Set] dialog may be set to refer to the previous day or the next day. For
more details on the setting, please refer to “4.3.1 A-AUTO/Web Server” of System Administrator's Guide.

Note

If the A-AUTO Agent’s version you use is earlier than V7.2.2Lv02, do not use [All Adjust Mode]function.

The following is an example of deleting a range of Schedule Dates.
e.g.5-58 Schedule Date Deleting2

All Delete by Term Set

5-146

Operations of A-AUTO for UNIX / Windows

e.g. 5-58 Schedule Date Deleting2 (All Delete by Term Set)
When you want to delete a range of Schedule Dates in the Network Schedule of GYOUMUA, perform thefollowing steps.

5-147

5 Application Definition(5) Schedule Date’s All Adjust (Date Select)
You can add or delete a specific Schedule Date in multiple Network Schedules in a single operation.
The following describe the steps to add or delete a specific Schedule Date in multiple Network Schedules
using Date Select.
① Display the assigned [Network Schedule List] page.
Please use [Search] function to select and display all Network IDs whose Network Schedules are to
be operated on. The selected Network Schedules will be displayed on [Network Schedule List]
page.
② Check the check box of [All Adjust Mode].
③ Click a Date on [Network Schedule List] page.
④[OK:Select the network of all pages. Cancel:Only select the network of current page.] dialog isdisplayed. Click [OK] or [Cancel] button according to whether the operation is to be applied to all
pages or the current page.

⑤ Click [All Add] or [All Delete] button on the toolbar.
⑥ [Selected Items Confirmation] dialog is displayed. Ensure the selected items are correct and clickon [Yes] to proceed with the operation.

⑦ [Schedule Adjust result] dialog is displayed. Click [OK] button and the list Windows is refreshed toshow the modifications made.

NoteWhen you do the content refresh operation by clicking [Refresh] icon or change the page display, theNetwork Schedules selected will be removed.



You can select a maximum of 3,000 Network Schedules at one time. Otherwise, only the Network
Schedules displayed on the page at that time will be selected.



If you select any date that is not in range of the period, an error message will be displayed and theDate Select operation is aborted. For the possible period, please refer to “5.9.7 Adjust Schedule”

When a large number of Network Schedules is selected for operation, it may take longer to process. It
is recommended to perform the same operation multiple times on a smaller number of selected
Network Schedules.



You cannot select multiple dates for the operation.

5-148

Operations of A-AUTO for UNIX / WindowsThe scope of All Adjust
You can perform All Adjust operation to the Network Schedules of the current page or all pages.
Before the operation, always remember to use [Search] function to select and display only Network
IDs whose Network Schedules are to be operated on, and confirm the selected Network Schedules
displayed on [Network Schedule List] page.If the target Network Schedules for All Adjust operation
are displayed in more than one page, the confirmation dialog is displayed as shown below.

Click [OK] button for all pages, or click [Cancel] button for current page only.
If operation is for the current page only, you can select or remove Network Schedules for theoperation by checking Network ID’s check box. However, this selection or removal is not available if
the operation is all pages.

[Selected Items Confirmation] dialog

A confirmation dialog showing all the Network IDs of the selected Network Schedules for the specified
operation is displayed.
The descriptions of the display items are as follow.

5-149

5 Application Definition[Non-Target]
A list of the Network Schedules and their Schedule Dates that have been selected but are nottargets for the operation is displayed. For “All Add” operation, non-target Network Schedules willbe those Network Schedules that are selected but have already a Schedule for the specified
date. For “All Delete” operation, non-target Network Schedules will be those Network Schedules
that are selected but do not have a Schedule for the specified date.

[Target]A list of the Network Schedules and their Schedule Dates that have been selected and aretargets for the operation is displayed.



Title bar
The number of target and non-target Network IDs is displayed. If the same Network is shown as[Non-Target] and [Target] at the same time. It also be counted as 1.



Schedule Adjust Result Dialog

After the All Adjust has completed operation, the Schedule Adjust Result Dialog is displayed

The descriptions of the display items are as follows.
[Error]
The Network IDs and Schedule Dates that were not successfully performed by All Adjust
operation are displayed with the corresponding error message. In this case, please solve theproblem and retry the operation.

5-150

Operations of A-AUTO for UNIX / Windows

When one of the following messages is displayed,

the All Adjust operation for all target

Network Schedules has failed. In this case, no Network ID and Schedule Date are displayed andthe update result would not be recorded in Security Log.
Code
10100005
10100002
10100006
10400030


MessageCannot Execute. Timeout error has occurred.
Cannot Execute. Disconnected from the target system.
Failed to connect to AP Server.
Failed to access to the ISAM file.

[Success]
The Network IDs and Schedule Dates are displayed for those Network Schedules that weresuccessfully completed by All Adjust operation.



Title BarThe number of successful and not successful Network IDs is displayed. If the same Network isshown as [successful] and [not successful] at the same time. It also be counted as 1.

The following is an example of deleting a Schedule Date for multiple Network Schedules.
e.g.5-59 Schedule Date Deleting 3

All Delete by Date Select5-151

5 Application Definition

e.g. 5-59 Schedule Date Deleting 3 (All Delete by Date Select)
If you want to delete a specific date of multiple Network Schedules, perform the following steps.
<1> Display target Network IDs of the Network Schedules for
All Adjust operation by using search function on list page.
<2> Check the [All Adjust Mode] check box.

<3> Click a target Date on calendar for the operation.

<4> Confirmation message is displayed.
Click [OK] button to apply operation to all pages, or click[Cancel] button to apply operation to current page only.
Click [OK] button for all pages, or click[Cancel] button for current page please.

<5> Selected Date Schedule is highlighted.

5-152Operations of A-AUTO for UNIX / Windows<6> If the current page is selected for the operation, you canremove any selected Network Schedule by checking on
Network ID to de-select it.
For example, check GYOUMUB check box to remove it
as a target for deletion.

<7> Click [All Delete] button.

<8> Selection confirmation dialog is displayed.
Verify the selection is right and click [Yes] button.

<9> The Schedule Adjust Result dialog is displayed.
Confirm the information, and click the [Close] button.

5-153

5 Application Definition<10> The list is refreshed and Network Schedules
for the specified are deleted.

5-154

Operations of A-AUTO for UNIX / Windows(6) Schedule Date’s All Adjust (Cell Select)
You can add or delete multiple Schedule Dates of multiple Network Schedules by selecting their date cellson [Network Schedule List] page.
The following describes the steps to add or delete multiple Schedule Dates of multiple Network Schedules
by Cell Selecting.
① Display the assigned [Network Schedule List] page.
② Check the [All Adjust Mode]’s check box.
③ Click a target Date Cell of a Network Schedule to select it. Repeat this for each date cell to be
selected for operation. The Date Cell of any Network Schedule can be selected.
④ Click [All Add] or [All Delete] button on the toolbar.
⑤ [Selected Items Confirmation] dialog is displayed. Ensure the selected items are correct and clickon [Yes] to proceed with the operation.

⑥ Schedule Adjust result dialog is displayed. . Click [OK] button and the list Windows is refreshed toshow the modifications made.
For details about [Selected Items Confirmation] and [Schedule Adjust result] dialogs, please refer to [ (5)Schedule Date’s All Adjust (Date Select) ]NoteWhen you do the content refresh operation by clicking [Refresh] icon or change the page display, theNetwork Schedules selected will be removed.



A date cell whose date is before the Network’ Valid Date or after the Network’s Expiry Date cannot be
selected for the operation. If such a date cell is selected, an error message is displayed and operation
is aborted. About the of possible term, please refer to [5.9.7 Adjust Schedule]You can select a maximum of 3,000 Network Schedules at one time. Otherwise, only the Network
Schedules displayed on the page at that time will be selected.

The following is an example of deleting multiple Schedule Dates for multiple Network Schedules.
e.g.5-60 Schedule Date Deleting 4

All Delete by Cell Selecting

5-155

5 Application Definition

e.g. 5-60 Schedule Date Deleting4 (All Delete by Cell Selecting)
When you want to delete multiple Network Schedules of multiple Network Schedules by cell selecting,perform the following steps.

<1> Check the [All Adjust Mode] check box.

<2> Select the target Date Cells of the Network Schedules
to be included in the operation by clicking on them one
at a time<3> Click [All Delete] button.

<4> Selection Confirmation message is displayed.
Click [YES] button* If there is no Schedule on August 10 for
GYOUMUC to be deleted, then it becomes a
Non-target.

5-156

Operations of A-AUTO for UNIX / Windows<5> The Schedule Adjust Result dialog is displayed.
Confirm the information, and click the [Close] button.

<6> The list is refreshed and Network Schedules
for the selected dates are deleted.

5-157

5 Application Definition

5.9.8

Network Schedule Modification Log
When Network Schedules are changed, the changes will be recorded into Security Log. Information in
Security Log can be displayed by A-AUTO/Web Client. The details of the message are as follows.
#1

Operation
Schedule Date Adding/Deleting2

Scheduled Term Shift3

The changes of Association with
Schedule

Changes
Output Sample :Date Schedule
2010/01 --A--D----A---A----A---DDDD-A-2010/03 -----A------D--------AAA------* Schedule of the month there is a change will be output.
A : Schedule Date Adding
D : Schedule Date Deleting- : None
Scheduled Term Start Date is updated from YYYYMM toYYYYMM
Deleted the Association of Network and XXXXX.
Added the Association of Network and XXXXX.
XXXXX is Schedule ID.

*.If you want to obtain the Security Log, set [Security Log Getting] Item to ON.

5-158

Operations of A-AUTO for UNIX / Windows

5.9.9

Display Period Setting
You can set the display period to be shown on [Network Schedule List] page.
If you want to view Network Schedules for the previous month or the next month, please click the[Previous] or the [Next] link.

Note
When the Start Date of Display Period is the 31st and you click [Previous] or the [Next] link, and that datedoes not exist for that month, the Start Date will be automatically adjusted to 1st of that month.
Start Date is July 31, 2012 and click [Previous]: Adjusted it to July 1, 2012

Start Date is December 31, 2012 and click [Previous]: Adjusted it to December 1, 2012

Start Date is January 31, 2012 and click [Next]: Adjusted it to March 1, 2012

When you want to set a specific Start Date for Display Period, use [Network Schedule Menu] of the[Network Schedule List] page as follows.
①

Display the [Network Schedule List] page.

②

Click [Menu] icon of the toolbar. [Menu] page is displayed.

③

Click [Display Date] icon on Display Period dialog to display the calendar④ Select a Start Date for the display⑤

A one-month period of Network Schedules starting from the selected Date is displayed on[Network Schedule List] page.

Hint
The possible [ Display Period ] is 1 month. For example, The PC CPU Date is July 10, 2004., and thepossible Display Period is August 9, 2004 - July 10, 2003.
Note
When the Display Period changed, the newest data won’t be updated. If you want it updated, please click[Refresh] Refresh
The following is an example of setting the Display Date for [Network Schedule List] page.
e.g.5-61 Display Period Setting

Display Period Setting
5-159

5 Application Definition

e.g. 5-61

Display Period Setting
When you want to change the Display Period of Network Schedule, perform the following steps.
<1> Click the [Display Period] icon on Menu page.
<2> Calendar is displayed.

<3> Click a Start Date on Calendar.

<4> [Network Schedule List] page displays the Network
Schedules for 1 month period.

5-160

Operations of A-AUTO for UNIX / Windows

5.9.10 Network Information Temporary Change
You can modify Network attributes for a specific schedule date of a Network i.e. modifications that are tobe applied or used for only a specific date that the Network is scheduled to execute. The original Network
information in the Network Master or other schedule dates remains unaffected. This is referred to as
temporarily change of a Network.
The temporary changes of Networks are saved in Daily Network Master.
The following describe the steps to perform

temporary change.

① Display the assigned [Network Schedule List] page.
②

Click the Schedule Date cell whose Network information is to be temporarily changed.

③ Pop-up Menu is displayed. Select [Show Detail] and [Daily Network Detail] page is displayed.
④ Change the information of Network accordingly.
⑤ Click the [Apply] button to save the setting.
⑥ That Schedule Date cell icon of Network Schedule List is changed to [changed temporarily] icon.

Hint
The detail of Daily Network, comes later.

Note
Click the [Apply] button on [Daily Network Detail] page to effect the changes to Daily Network Master. Click[×] button to abort the changes and close the dialog.
The items that can be modified on [Daily Network Detail] page are as follows
 Start Time Parallel Run

 Execution ID

 Input Data Wait

 Monitor On

 Resource Preceding Network Start Delay Watch Time End Delay Watch Time Time Interval End Time Interval (min) Plug-in Before Start Plug-in After Start

 Response To Max Time Job Executing User ID

 User Information

 Class

 Priority

 System/Qualifier Max Executing Time Hold code

The items that cannot be modified on [Daily Network Detail] page are as follows
 Network ID

 Expanded Name Plug-in Parameter Before Start

 All job information

 Input Data Wait page

 Plug-in Parameter After Start

 Resource page

5-161

5 Application Definition

These items can only be modified in Network Master.
All other items cannot be changed in Daily Network Master.

e.g.5-62
Network

TemporarychangeofTemporary change of Network

5-162

Operations of A-AUTO for UNIX / Windows

e.g. 5-62 Temporary change of Network
When you want to add GYOUMUA as GYOUMUB’s Preceding Network on a specific date, perform thefollowing steps.
<1> Click the cell of the target schedule date of
GYOUMUB on assigned [Network Schedule List]
page.
<2>Select [Show Detail] .

<3> [Edit] page of Daily Network is displayed.
<4> Click [Preceding Network] tab.

5-163

5 Application Definition<5>Select GYOUMUA from [Network ID] list
<6> Click [←] button<7> GYOUMUA is moved to [Selected Network ID] list.

<8> Click [Apply] button.

<9> The Schedule Date cell icon of GYOUMUB is changed
into [changed temporarily] icon.

5-164Operations of A-AUTO for UNIX / Windows

5.9.11 Daily Network Schedule List
After starting A-AUTO/Web Client, click on a Monitor ID on [Application Definition] pane of the [A-AUTO
Main] Windows. Select [Daily Network] on [List Menu] pane. The Network information of those Networks
that are scheduled for the specified schedule date will be displayed in list form. This list is called [Daily
Schedule] page (refer to the picture below)

Click the Network ID link on list to display the [Daily Network Detail] page of that Network.

5-165

5 Application Definition

5.9.12 Daily Network Menu
When you click the Menu icon on the toolbar on list page, [Daily Network Menu] page is displayed.

(1) Schedule Date
Click any Schedule Date on the Calendar of page, the Network information of those Networks that arescheduled for the specified schedule date will be displayed on [Daily Schedule] page.

(2) Network GroupA list of available Network Groups is displayed.
Click a Group ID link and only Networks that belong to the specified Group will be displayed on the [Daily
Schedule] page.

5-166

Operations of A-AUTO for UNIX/Windows

6 Operations
6.1

Auto Scheduling Function
Auto Scheduling Function generates year-round Network Schedules, which are the execution schedules of
Networks. Network Schedule information stored in Network Schedule Master (Schedule Master) and Calendar
information stored in Holiday Master are updated automatically by this function, and as a result, year-roundschedule is maintained for each master.

6.1.1

The Purpose of Auto Scheduling
A new Network Schedule is created whenever a Network is associated with one or more Schedule Patterns.
The new Network Schedule is generated for a one-year period, starting from the month when the associationis performed. In other words, a one-year execution schedule for each Network is stored and managed in the
Network Schedule Master. Daily execution schedule, which are Networks scheduled to be executed for theday, isextracted each day based on the information stored in Network Schedule Master. If there is no

maintenance performed on Network Schedules, there will be no schedule dates for the Network Schedules
beyond the one-year period. Therefore, these Networks will not be scheduled for execution after the one-year
period. To avoid such situation, A-AUTO for UNIX/Windows provides a function that automatically updates the
Network Schedule information and this is Auto Scheduling Function.
Auto Scheduling Function automatically updates Network Schedules at the timing defined by the user. The
Schedule Master and Holiday Master that contain the Schedule and Holiday Information are updated asfollows.
Schedule Master

Auto Scheduling Function will generate Schedule information for 12 months,
starting from the month when Auto Scheduling is executed.

Holiday Master

Auto Scheduling Function will generate Holiday information for 14 months,
starting from 1 month before the month when Auto Scheduling is executed.

(If you use the Previous Month Schedule Function, the generated Network Schedule information is for
12-month period starting from one month before the month when Auto Scheduling is executed. For more
information on this function, please refer to [8.11 Previous Month Schedule Function])
Auto Scheduling is performed by executing either autosche utility or remakesche utility.
■the differences between autosche utility and remakesche utility
The schedule dates of a Network schedule, which is created by associating a network with one or more
Schedule Patterns, are calculated based on the information of the holiday and the Schedule Patterns. Network
Schedules are created differently by these two utilities.
6-1

6 Operations

autosche utility extends the execution schedules of a Network in the Network Schedule and the existing
execution schedules remain. This means that modifications that have been performed on existing execution
schedules of a Network Schedule will remain even after executing autosche utility.
Similarly, if information of Holiday Table and/or Schedule Pattern associated with a Network is changed, thechanges will not be reflected in the existing execution schedules that remain in the Network Schedule.
remakesche utility, on the other hand, regenerates Network Schedule and replaces existing Network Schedule
information. remakesche utility will delete all existing execution schedules of a Network Schedule andgenerates new execution schedules for the Network Schedule for a one-year period, starting from the day of
execution.
As the Network Schedule is generated based on the current information of Holiday Table and Schedule
Patterns, previous Network Schedule information that has been modified manually will not be reflected in the
new Network Schedule and has to be re-applied, if necessary.
Auto Scheduling can be run by executing the utility or it can also be executed from “A-AUTO Monitor” screenof Web client. Please refer to “6.8.1(10) Basic Schedule Setup” (autosche) or “6.8.1(11) Reschedule”(remakesche) for execution of Auto Scheduling via Web client. The following section describes execution ofAuto Scheduling utility.

6-2

Operations of A-AUTO for UNIX/Windows

6.1.2

autosche utility(1) Function overview
autosche utility performs the following.
 Automatic updating of master files
The utility provides users with automatic updating of the Network Schedule information registered in
Network Schedule Master (Schedule Master) and the Holiday information in the Holiday Master.
 Recording and displaying the execution result of Auto Scheduling
The execution result of autosche utility and the information regarding the Network or the Holiday Table that
could not be updated successfully are recorded in a log file. This information is also displayed on the
console.
Network Schedule Master (Schedule Master) and Holiday Master are updated by executing autosche utility.
autosche utility allows users to select the target Network Schedules for Auto Scheduling processing by using
the following criteria.
 Execution ID
 Network ID (Prefix)
 System Qualifier Network Group(2) Outline of processing
The figure below shows the autosche utility’s processing outline.

Command input
Log file
Extract Fileautosche utility

Holiday
MasterSchedule
Master

Process
information file

Network
Master

Reference to Network Master
if System Qualifier
is a selection criterion

Network
Group Master

Reference to Network Master
if Network Groupis a selection criterion

The following files are used by autosche utility to automatically update the Network Schedule.

6-3

6 Operations①

Holiday Master
The autosche utility automatically extends and stores holiday information in the Holiday Master for a period of
14 months, i.e., from one month before to 13 months after the month of the utility execution. For example, if
autosche utility is executed on May 10, 1997, Holiday information for the period from April 1997 to May 1998 iscreated in the Holiday Master.
Note Execution of autosche utility does not change the existing holiday information that has previously beencreated or modified. For example, even if autosche utility is executed on May 10, 1997 and Holiday
information for period from April 1997 to May 1998 already exists in the Master, the Holiday Master will not
be updated or extended.
 It is recommended to execute Auto Scheduling every month. If the execution interval is longer than 2months, holiday information is added to the period for which Holiday Information has not been created. In
the above example, if autosche utility was executed on May 10, 1997 and then on July 1, 1997, Annual
Holiday information for June and July 1998 will be added and Holiday Master now has Holiday informationfrom June 1997 to July 1998.

②

Schedule Master
Referring to schedule information of the Schedule Patterns associated with the respective Networks, Auto
Scheduling facility extends and stores the information of the Network Schedules in Network Schedule Master(Schedule Master) for a period of 12 months, from the month of utility execution. For example, if autoscheutility is executed on May 10th, 2004, the information of the Network Schedules is extended and stored for theperiod from May 2004 to April 2005.
Note
Execution of autosche utility does not change the existing Network Schedule information that has previously
been created or modified. For example, if autosche utility is executed on May 10, 1997 and Network Schedule
information for period from May 1997 to April 30, 1998 already exists in the Master, the Network Schedule
Master (Schedule master) will not be updated or extended.

③

Daily Network MasterOld records corresponding to the schedule dates of a Network Schedule that are deleted from Schedule
Master are deleted automatically.

④

Network Master
If System Qualifier is used as a selection criterion (refer to “6.1.3 Starting autosche utility” for details), Network
Master is used.

⑤

Network Group Master
If Group ID is used as a selection criterion (refer to “6.1.3 Starting autosche utility” for details), Network Group
Master is used. This function is available only for v710 or later.
6-4

Operations of A-AUTO for UNIX/Windows⑥

Extract File
The selection criteria of Network ID and Execution ID are specified in this file. The Extract File name may havea maximum of 12 alphanumeric characters and must begin with ‘AUT’ or ‘aut’. (The directory path in which
Extract File is stored is defined by system parameter, AUX_FILES_PATH.)⑦

Log file
Log file is the file in which log information is written. File extension is .log. (The directory path in which log fileis stored is defined by system parameter, AUX_FILES_PATH.) . Settings of System Parameters may bechanged using [Monitor Setting] page of [System Management]. For more details, please refer to [9.3.1
Settings of Monitor].

6-5

6 Operations

6.1.3

Starting autosche utility
For Auto Scheduling, autosche utility must be run on server where A-AUTO Monitor resides. The target ofAuto Scheduling is defined by startup parameter.

(1) Parameter
For Auto Scheduling when autosche utility is started, define the parameter as follows.
autosche∆-f file name[∆-q system qualifier][∆-l file name][∆-g group ID]
<1>
<2>
<3>
<4>
<1> File name: Defines the name of the Extract File that contains the target Network IDs andtarget Execution IDs to be used as criteria for Auto Scheduling.
The File name may have a maximum of 12 alphanumeric characters andmust begin with ‘AUT_’ or ‘aut_’.

<2> System qualifier: Defines the target System Qualifier for Auto Scheduling (up to a maximumof 8 alphanumeric characters). If not specified, all System Qualifiers are
selected.

<3> File name: Defines the name of the file in which log information is to be written (up to a
maximum of 8 alphanumeric letters). File extension is .log. (Theinstallation default value is: autosche)<4> Group ID: Defines the target Group ID for Auto Scheduling (up to a maximum of 8alphanumeric characters). If not specified, all Group IDs are selected.

Example 6-1 autosche utility parameter(1)

In the case where only Extract File name is specified
Extract File name:aut_def

Targeted System Qualifier:

All System Qualifiers(default)

Log file name:autosche.log(default)

Targeted Group ID:

All Group IDs(default)

autosche∆-faut_def(2) In the case where Extract File name and System Qualifier are specified
Extract File name:aut_defex

Targeted System Qualifier:

sysqp01

Log file name:autosche.log(default)

Targeted Group ID:

All Group IDs(default)

autosche∆-faut_defex∆-qsysqp01

6-6

Operations of A-AUTO for UNIX/Windows(3)

In the case where Extract File, System Qualifier, Log file name, and Group ID are specified.
Extract File name:aut_bs1

Targeted System Qualifier:

sysqp99

Log file name:log2.log

Targeted Group ID:

ntwkgp01

autosche∆-faut_bs1∆-qsysqp99∆-llog2∆-gntwkgp01

6-7

6 Operations(2) The format of Extract File
The autosche utility allows users to specify Network IDs and the Execution IDs as criteria to be used to selectNetwork Schedules for Auto Scheduling. The selection criteria specification is stored in Extract File. In the
Extract File, which is a text file, parameters may be specified in the format listed below. The file may becreated using any text editor.
inc=(Network ID, Execution ID)<1><2><1> Network ID: Defines the target Network IDs of Network Schedules for Auto Scheduling.
Generic Network ID may be specified by prefixing the name with *(asterisk mark).

<2> Execution ID: Defines the target Execution IDs of Network Schedules for Auto
Scheduling. Specify * (asterisk mark) for all Execution IDs.

Example 6-2

How to define parameters in Extract File
(1) To Include all Network Schedules regardless of Network IDs and Execution IDs
Inc∆=∆(∆*,*∆)(2)

To include only Network Schedules with Execution ID A

Inc∆=(∆*,A∆)(3)

To include Network Schedules with Execution IDs A, B, and C

Inc∆=(∆*,ABC∆)(4)

To include Network Schedules with Network ID starting with BSPNET

Inc∆=(∆BSPNET*,*∆)(5)

To include Network Schedules with Network IDs starting with BSPNET and has the Execution ID A or Zinc∆=(∆BSPNET*,AZ∆)(6)

To include Network Schedules with Network ID starting with GUMA or GUMBInc∆=(∆GUMA*,*∆)
inc∆=(∆GUMB*,*∆)

6-8

Operations of A-AUTO for UNIX/Windows

Note

Make sure every line is ended with a carriage return. The maximum data length for a line must be lessthan or equal to 250 bytes.

More than one combination of Network ID and Execution ID can be specified.

Auto Scheduling will be executed for Network Schedules that meet the criteria of Network ID AND
Execution ID. If a selection criterion for all Network IDs and Execution IDs is already specified, Auto
Scheduling will be executed for all Network Schedules even if additional selection criteria to selectspecific Network ID and/or Execution ID are specified.

AND condition is applied in the search criteria if Extract File, System Qualifier, and Group ID are defined.
For example, if Extraction file specifies Network ID ANET*, Execution ID of 1, and System Qualifier of
SYSQPA and group ID of NETGRP are specified parameters, autosche utility will select Network
Schedules that meet all the search criteria for Auto Scheduling.

6-9

6 Operations

6.1.4

remakesche utility
Similar to autosche utility, remakesche utility is executed in the environment where A-AUTO Monitor isoperating.

■ Function overview
The remakesche utility provides automatic scheduling function similar to the autosche utility but it re-generates
and replaces existing Network Schedules.
remakesche utility deletes Network Schedule and Holiday information that have previously been created. Itthen re-creates them either for a one-year period, starting from the day of remakesche utility execution, or forthe period specified in the parameter for remakesche execution. It is important to note the following when
executing remakesche utility.
Modifications, including additions and changes, performed manually to Network Schedules for the
specified period are not reflected in the newly created Network Schedules. Network schedules are
re-created according to the Schedule Patterns associated with the Networks.

Modifications, including additions and changes, performed manually to Holiday information for the
specified period via Holiday Master maintenance Window are not reflected in the newly created holiday
information.



Depending on the month of execution of remakesche utility and specification of Standard Processing
Date, the starting schedule date of Network Schedule may be different in some cases.
Example Reference Date = 30th, Standard Processing Date = September +31, Holiday = Sat, Sun
When Network Schedule is created in September, the Network will be scheduled on 10/15 for September,
12/13 for October, and 2/12 for November. However, when remakesche is executed on October 1st, theNetwork will be scheduled starting from 12/13 for October because 10/15 is for September fiscal month
although it is after the execution date.

6-10

Operations of A-AUTO for UNIX/Windows

6.1.5

Starting remakesche utility(1) Parameterremakesche∆-f file name[∆-q system qualifier][∆-l file name]
<1>

<2>

<3>

[∆-t Schedule period][∆-g Group ID]<4><5><1> File name: Defines the name of the Extract File that contains the target Network IDs andtarget Execution IDs to be used as criteria for Auto Scheduling. The Filename may have a maximum of 12 alphanumeric characters and must begin
with ‘AUT_’ or ‘aut_’.

<2> System qualifier: Defines the target System Qualifier for Auto Scheduling(up to a maximum of
8 alphanumeric characters) . If not specified, all System Qualifiers are
selected.

<3> File name: Defines the name of the file in which log information is to be written (up to a
maximum of 8 alphanumeric letters). File extension is .log. (The installation
default value is : autosche)<4> Schedule period: Defines the period for which Network Schedules and Holiday information are
to be re-created.
Specify the period in one of the following format.
Ifthe

periodis

specifiedineither“yyyymmddyyyymmdd”

or“yymmddyymmdd” format,
Network Schedules and Holiday information are re-created for the period
starting from the 1st date to the 2nd date.
If the period is specified in either “yyyymmdd” or “yymmdd” format,
Network Schedules and Holiday information are re-created from thespecified date to the end of the 11th month. If the value is omitted, Networks
Schedules and Holiday information are re-created from the 1st day of thecurrent CPU month to the end of the 11th month.
<5> Group ID: Defines the target Group ID for Auto Scheduling (up to a maximum of 8alphanumeric characters) . If not specified, all Group IDs are selected.
This function is available only for v710 or later.

(2) The format of Extract File
Specification of the Extract File is the same as the autosche utility. (Please refer to “6.1.3 Starting autoscheutility“ for details)

6-11

6 Operations

6.2

Finalized Schedule Function

6.2.1

The purpose of Finalized Schedule Function
The Finalized Schedule function extracts the information from Network Schedules and prepares the finalschedule of Networks to be executed for the day’s operation. This information will be transferred to A-AUTO
Monitor. Intermediate files will be created during this process. These intermediate files are available andnon-secured so that users can modify them. (Refer to “6.2.4 Record Format of Intermediate File“ of record
format of the intermediate file) Finalized Schedule function is performed by executing sfin utility.
Finalized Schedule function can be performed by either executing the utility or executing the function via“A-AUTO Monitor” screen of A-AUTO/Web client. Please refer to “6.8.1 (9) Daily Schedule・Queuing “ forprocedure on executing Auto Scheduling via A-AUTO Web client.
The procedures for executing Finalized Schedule function using utility are explained in the following section.

6.2.2

sfin utility
sfin utility must be executed on the environment where A-AUTO Monitor resides.

(1) Function overview
sfin utility creates a Network Stock File based on the Network Schedules, which are maintained in the
Schedule Master, and on information in Network Master. Networks become ready for execution and can bemonitored by A-AUTO Monitor after executing sfin. Intermediate files are created and will be available andnon-secured so that users can modify them.

6-12

Operations of A-AUTO for UNIX/Windows(2) Process overview
sfin utility consists of the following programs:
 schexrt
Based the parameter specified in Extract File, Network Schedules are extracted from the Network
Schedule Master (Schedule Master) and a Schedule Intermediate file is created.
 auwninf
Extracts necessary information from the Schedule Intermediate file created by schexrt, the Network Masterand the Daily Network Master to create a Stock Intermediate file.
 auwfin
Writes the content of the Stock Intermediate file created by auwninf to the Network Stock file.
 crtajaCreates Schedule Analysis files (Network Information File and Job Information file) based on theinformation in the Stock Intermediate file created by auwninf, the Network Master and the Daily Network
Master. This function is available only when a value of 1 is specified for the system parameter
AUTO_ASV_CORRESPOND.

6-13

6 Operations(3) Processing overview diagram of the processes

Schedule
MasterDaily Network
MasterNetwork
Group Master

Extract File

Check Point
File

schexrt

Network
MasterDaily Network
MasterSchedule
Intermediate Fileauxninf

Stock
Intermediate FileauxfinNetwork Stock

Network
Master

Stock Intermediate
File

Daily Network
MastercrtajaNetwork
Information FileJob Information

6-14

Check Point FileOperations of A-AUTO for UNIX/Windows

sfin utility uses the following files in order to facilitate Finalized Schedule function.
①

Schedule Master
Extracts information for the specified date from Network Schedule Master.

②

Daily Network Master
Extracts information on Networks whose Network attributes may have been modified for the specified
execution date.

③

Network Master
Extracts information on Networks that exist in Schedule Intermediate file.

④

Network Group
Extracts information on Networks that are defined with a Group ID.

⑤

Extract File
The selection criteria of Network ID and Execution ID are specified in this file. The File name may have amaximum of 12 alphanumeric characters and must begin with ‘FIN_’ or ‘fin_’.(The file format of Extract
File is the same as the format used in Auto Scheduling Function)
The directory path in which Extract File is stored is defined by the System Parameter
AUT_FILES_PATH.

⑥

Schedule Intermediate file,

Stock Intermediate file

Intermediate files created by Finalized Schedule Function are for data passing. Intermediate files areavailable and non-secured so that users can modify them. (Please refer to section 6.2.4 for record format
of Intermediate File)
The path of the directory in which intermediate files are stored is defined by the System Parameter,
AUT_FILES_PATH.
⑦

Environment Check Point File
Retrieves the Operation date of A-AUTO Monitor. crtaja program retrieves the processor name of
A-AUTO Monitor.

6.2.3

Starting sfin utility
There are two ways of executing sfin utility.
 Executing Finalized Schedule Function when editing of the Intermediate file(s) is required.
Modules that make up sfin are executed one by one.
 Executing Finalized Schedule Function when no editing of the Intermediate file(s) is required.
Modules that make up sfin are executed continuously in one shell script or batch file.

6-15

6 Operations(1) Executing Finalized Schedule Function when editing of the Intermediate file(s)is required■ schexrt
schexrt[∆-mType]∆-dDate∆-fExtract File name∆-wIntermediate File name[∆-gGroup ID]
<1>
<2>
<3>
<4>
<5>
<1> Type: Select the exclusive control method for accessing Schedule Master and Daily
Network Master from the following.
u: schexrt will read Schedule Master and Daily Network Master only when
Automatic Scheduling function or A-AUTO/Web client or other A-AUTO for
UNIX/Windows programs are not accessing the files. (The installation default
value)
schexrt will stop with open exclusive error if other A-AUTO for UNIX/Windows
program is accessing Schedule Master or Daily Network Master.
f: schexrt will read Schedule Master and Daily Network Master even though Auto
Scheduling

Functionor

A-AUTO/Web

clientorother

A-AUTOfor

UNIX/Windows programs are accessing the files.
If other A-AUTO for UNIX/Windows programs update Schedule Master or
Daily Network Master while schexrt is reading the data, schexrt may write
incorrect or incomplete data to the Schedule Intermediate file. Therefore, theoperator must be careful not to update Schedule Master or Daily Network
Master when using any A-AUTO for UNIX/Windows program while executing
schexrt.
(Please refer to “15.2 Precautions and Limitations to execution of sfin utility” for
information regarding exclusive control of sfin)<2> Date: Defines the Schedule Date in either of the following formats: yymmdd or
yyyymmdd.
If autodate is specified, the Operation Date of A-AUTO Monitor is used as theschedule date.

<3> Extract File name: Defines the name of the Extract file that contains the target Networks andExecution IDs to be used as criteria for Finalized Schedule. The File name may
have a maximum of 12 alphanumeric characters and must begin with ‘FIN_’ or‘fin_’. (The format of the Extract File is the same as described above for the
Extract File of Auto Scheduling.)<4> Intermediate file name: Defines the name of the Schedule Intermediate file.
The File name may have a maximum of 12 alphanumeric characters andmust begin with ‘FIN_’ or ‘fin_’.
<5> Group ID: Defines the target Group ID for Finalized Schedule (up to maximum of 8alphanumeric characters). If not specified, all Group IDs are selected. This

6-16

Operations of A-AUTO for UNIX/Windows

function is available only in v710 or later.

Example 6-3

How to define parameters for schexrt(1)

To execute Finalized Schedule for schedule date 2008/07/01

schexrt∆-d20080701∆-ffin_def∆-wfin_temp1(2)

To execute Finalized Schedule using Operation Date of A-AUTO Monitor (Make sure that A-AUTO
Monitor is started.)schexrt∆-dautodate∆-ffin_def∆-wfin_temp1(3)

To execute Finalized Schedule for a specific schedule Date and Groupschexrt∆-d20080701∆-ffin_def∆-wfin_temp1∆-gNETGRP

Note
Please specify unique file names for Extract File and Schedule Intermediate File.
The following messages are displayed when schexrt ends normally.
schexrt -dautodate-wfin_def-wfin_temp1
SFIN006I
schexrt STARTS
SFIN023I
EXTRACTING NETWORK-ID COUNT 26
SFIN007I
schexrt TERMINATE WITH DUE TO 0

6-17

6 Operations■ auwninf
auwninf[∆-mType][∆-qSystem Qualifier]∆-wSchedule Intermediate File Name
<1>
<2>
<3>
∆-rStock Intermediate File
<4>
<1> Type: Select the exclusive control method for accessing Network Master and Daily
Network Master from the following.
u: auwninf will read Network Master and Daily Network Master only when
Automatic Scheduling function or A-AUTO/Web client or other A-AUTO for
UNIX/Windows programs are not accessing the files. (The installation default
value)
auwninf will end with open exclusive error if other A-AUTO for UNIX/Windows
program is accessing Network Master or Daily Network Master.
f: auwninf will read Network Master and Daily Network Master even though Auto
Scheduling

Functionor

A-AUTO/Web

clientorother

A-AUTOfor

UNIX/Windows programs are accessing the files.
If other A-AUTO for UNIX/Windows program updates Network Master or Daily
Network Master while auwninf is reading the data, auwninf may write incorrect
or incomplete data to the Stock Intermediate file. Therefore the operator must
be careful not to update Network Master or Daily Network Master when using
any A-AUTO for UNIX/Windows program while executing auwninf.
(Please refer to “15.2 Precautions and Limitations to execution of sfin utility” for
information regarding exclusive control of sfin)<2> System Qualifier: Defines the target System Qualifier name.

<3> Schedule Intermediate File name: Defines the name of the Schedule Intermediate file to bereferred to. This is the output file of schexrt module.
<4> Stock Intermediate File name: Defines the name of the Stock Intermediate file to be referred. The
File name may have a maximum of 12 alphanumeric characters andmust begin with ‘FIN_’ or ‘fin_’.

6-18

Operations of A-AUTO for UNIX/Windows

Example 6-4

How to define parameters for auwninf(1)

To execute Finalized Scheduling without specifying System Qualifier

auwninf∆-wfin_temp1∆-rfin_temp2(2)

To execute Finalized Scheduling with specified System Qualifier

auwninf∆-qsyssp01∆-wfin_temp1∆-rfin_temp2
The following messages are displayed when auwninf normally ends.
auwninf -wfin_temp1 -rfin_temp2
SFIN006I auxninf STARTS
SFIN023I EXTRACTING NETWORK-ID COUNT 26
SFIN007I auxninf TERMINATE WITH DUE TO 0

6-19

6 Operations■ auwfin
auwfin∆-mType∆-rStock Intermediate File Name
<1>
<2>
<1> Type: Select one of the following options when writing into Network Stock file.
n: Will write information only if Network Stock file has been cleared.
r: Will append information to Network Stock file.
f: Will overwrite information in Network Stock file.

<2> Stock Intermediate File name : Defines the name of the Stock Intermediate file to be referred. This is
the output file of auwninf.

Note 6-5 How to define parameters for auwfin(1)

Define the parameter as follows if information is to be appended to Network Stock file.

auwfin∆–mr∆-rfin_temp2(2)

Define the parameter as follows if information is to be written only when Network Stock file has alreadybeen cleared.

auwfin∆-mn∆-rfin_temp2
The following messages are displayed when auwfin normally ends.
auwfin -mf -rfin_stkm
SFIN006I auxfin STARTS
SFIN023I EXTRACTING NETWORK-ID COUNT 26
SFIN007I auxfin TERMINATE WITH DUE TO 0

6-20

Operations of A-AUTO for UNIX/Windows■ crtaja
crtaja[∆-q System Qualifier]∆-r Stock Intermediate File<1><2>
<1> System Qualifier: Defines the name of the target System Qualifier.

<2> Stock Intermediate File name : Defines the name of the Stock Intermediate file. This is the output fileof auwninf.

Example 6-6

How to define parameters for crtaja(1)

To execute Finalized Scheduling without specifying System Qualifiercrtaja∆-rfin_temp2(2)

To execute Finalized Scheduling with specified System Qualifiercrtaja∆–qsyssp01∆-rfin_temp2
The following messages are displayed when crtaja normally ends.
criaja -rfin_stkm
SFIN006I crtaja STARTS
SFIN024I ADDED ESVNFILE RECORD(S) COUNT IS 26
SFIN025I ADDED ESVJFILE RECORD(S) COUNT IS 130
SFIN007I crtaja TERMINATE WITH DUE TO 0
Note
Since the Network Information File and Job Information File are cumulative files and records are accumulated
and files are increasing every day, please delete the files regularly. However, A-AUTO Monitor writes to thesefiles whenever Networks are started or terminated. Depending on the timing for deleting files, A-AUTO Monitor
may fail to write monitoring information into these files. Therefore, please do not delete the files when starting
and termination of Networks take place frequently.
The followings are recommended for deleting Network Information file/Job Information file.
ExampleIf there are no leftover networks for execution for the following day

Include a command to delete Network Information file/Job Information file in sfin batch shell. Then execute sfin
everyday before running the applications so that Information files are deleted every day.

ExampleIf there are leftover networks for execution for the following day

Delete Network Information file/Job Information file using delete command every three months by suspending
temporarily the starting and termination of Networks.

6-21

6 Operations

Executing Finalized Schedule function when no editing of intermediate
file(s) is required<1> In the case of A-AUTO for UNIX
The following is a sample csh.
#!/bin/csh
set FIN_SCHE_WORKFILE = fin_schem
set FIN_STK_WORKFILE = fin_stkm
set FIN_EXRT_FILE = fin_exrt
set FIN_SDATE = autodate
set FIN_MSTR_READ = u
set FIN_STK_MODE = r
schexrt -m$FIN_MSTR_READ -f$FIN_EXRT_FILE -w$FIN_SCHE_WORKFILE -d$FIN_SDATE
if ($status > 0) then
exit
endif
auwninf -m$FIN_MSTR_READ -w$FIN_SCHE_WORKFILE -r$FIN_STK_WORKFILE
if ($status > 0) then
exit
endif
auxfin -m$FIN_STK_MODE -r$FIN_STK_WORKFILE
if ($status > 0) then
exit
endif
crtaja r$FIN_STK_WORKFILE
if ($status > 0) then
exit
endif

6-22

Operations of A-AUTO for UNIX/Windows<2> In the case of A-AUTO for Windows
The following is a sample batch program.
@ECHO OFFSET AUTODIR=\BSP\AUW\2.0
SET AUTOBIN=%AUTODIR%\BIN
SET AUTOFILE=%AUTODIR%\FILESSET PATH=%PATH%;%AUTOBIN%
REM----- Delete temporary file ----FORM -l -tnetwkstk
DEL %AUTOFILE%\fin_temp
DEL %AUTOFILE%\fin_temp2: SCHEXRTSCHEXRT -mf -ffin_def -wfin_temp -dautodate
IF ERRORLEVEL 1 GOTO SCHEXRT99: AUWNINF
AUWNINF -mf -wfin_temp -rfin_temp2
IF ERRORLEVEL 1 GOTO AUWNINF99: AUWNFIN
AUWFIN -mr -rfin_temp2
IF ERRORLEVEL 1 GOTO AUWNFIN99: CRTAJACRTAJA -rfin_temp2
IF ERRORLEVEL 1 GOTO CRTAJA99
GOTO EXIT99
REM ----- Display error message ----: SCHEXRT99
ECHO ##### SCHEXRT ABNOMAL END ######
GOTO EXIT99: AUWNINF99
ECHO ##### AUWNINF ABNOMAL END ######
GOTO EXIT99: AUWNFIN99
ECHO ##### AUWNFIN ABNOMAL END ######
GOTO EXIT99: CRTAJA99ECHO ##### CRTAJA ABNOMAL END ######
GOTO EXIT99: EXIT99
PAUSE
EXIT

6-23

6 Operations

6.2.4

Record Format of Intermediate Files
The following two intermediate files are created during the execution of Finalized Schedule function.
 Schedule Intermediate File
 Stock Intermediate File
Both of the Intermediate files are available and non-secured so that users can modify them, if required.

(1) Schedule Intermediate file
Schedule Intermediate file is created during the first step (schexrt) of Finalized Schedule.
The record format of Schedule Intermediate File is as follows.
No.

ColumnItem Name

Type

LengthDescription- Not used by auwninf

1

1

Sequence
NumberAlphanumeric6- Duplicated numbers are acceptable- This number is not mandatory
Retrieve from input parameter

2

9

Schedule Datenumeric

8

3

21

NetworkAlphanumeric

20

Retrieved from Schedule Master

4

45

Execution ID

Alphanumeric1

Retrieved from Schedule Master5

46Group ID

Alphanumeric

8

Retrieved from Network Group Master

6-24(yyyymmdd format)

Operations of A-AUTO for UNIX/Windows(2) Stock Intermediate File
Stock Intermediate File is an intermediate file created during the second step (auwninf) of Finalized Schedule.
The record format of Stock Intermediate File is shown below.

No.

ColumnItem Name

Type

LengthDescription
Sequence Number

11 Not used by auwfin

Sequence

numeric

Number6

 Duplicated numbers are acceptable This number is not mandatory
Retrieved from input parameter

2

9

Schedule Datenumeric

8

3

21

NetworkAlphanumeric 8

 (yyyymmdd format)
Retrieved from Schedule Intermediate
File

4

30

Class

Alphanumeric 1

Retrieved from Network Master

5

31

Type

Alphabetic

1‘N’ is set

6

32

Hold CodeAlphabetic

1

Retrieved from Network Master7

35

Priority

numeric2

Retrieved from Network Master
Retrieved from Network Master

8

38

Wait attribute

Alphabetic

H: Hold attribute

I: Input Data Wait attributeT: Start time wait

3

Retrieved from Network Master９

44

NetworkAlphabetic

attributes

H: Hold attribute

I: Input Data Wait attributeT: Start time waitR

: Parallel run attributeM: Monitor On attribute

5

10

51

System Qualifier

Alphanumeric 8

Retrieved from Network Master

11

61

Start Timenumeric

4

Retrieved from Network Master

12

67

Process Datenumeric

8(yyyymmdd format)

13

77

User Field

Alphanumeric 12

Network
14

89

duplication
flag(usedby

Alphabetic

1

D : Will not be processed*

crtaja only)
15

90Group ID

Alphanumeric 8

Retrieved from Network Group MasterNot for execution because duplicated Network exists (Network ID and Scheduled Date are the same) .

6-25

6 Operations

6.4

Queuing
Network information is written to the Network Stock file after the Finalized Schedule is executed. To being theexecution of Networks in A-AUTO Monitor, Queuing (‘Q’) Command must be issued to A-AUTO Monitor.
When ‘Q’ command is issued, Networks are transferred from the Network Stock file to A-AUTO Monitor. Thisis termed ‘Queuing’. The queued Networks will be in wait state until their wait conditions are cleared or met.
When their wait conditions are cleared, Jobs in the Networks will be released for execution. A-AUTO Monitor
automatically executes Networks in an orderly sequence according to the preceding relationships definedamong Networks and the availability of Network and Job Partitions.
When all Jobs in a Network finish normally, the Network ends normally. If any Job in the Network finishes
abnormally, the information will be recorded in Abnormally Terminated Network file and the Network will beplaced in Abnormally Ended state that requires the operator’s intervention. While the operator is handling theabnormally ended Network, A-AUTO Monitor continues to process other Networks with no relationship withthe abnormally ended Network. If the system goes down, it will recover automatically to the state at the time of
the failure when the system is restarted.
Therefore, A-AUTO Monitor enables users to operate computers most efficiently and effectively.
In the case where Cross-Master linkage mode is used, A-AUTO Monitor will communicate with
A-AUTO/Connect during its processing but this has no impact on monitoring performance.
A-AUTO Monitor for Mainframe may operate differently if Mainframe Connection mode is used (i.e.
communication of A-AUTO system with mainframe).

Queuing can be executed by issuing ‘Q’ Command or via A-AUTO Monitor and other screens of A-AUTO/Web
client. Please refer to “6.8.1 A-AUTO Monitor details (9)” for executing queuing via A-AUTO/Web client.
Refer to the following section for how to execute Queuing by issuing command.

6.4.1

Network Queuing (Stand Alone Mode)
Networks that are scheduled for execution are transferred to Network Queue file when Queuing process isperformed.
Network Queue file therefore contains Networks in the queued state and waiting for execution.

(1) Queuing Command
Queuing command is issued to transfer the scheduled Networks to the queue. The queued Networks aremonitored and controlled under A-AUTO Monitor. The result of Queuing process is displayed on console.

6-28

Operations of A-AUTO for UNIX/Windows(2) Notes on Network Queuing①

A Network will not be queued under the following conditions.
 The Network is not registered in the Network Master (could have been deleted) A Network with the same Network ID and Schedule date is already in the queue A Network with the same Network ID and Schedule date is currently running under A-AUTO
Monitor②

During the queuing process, A-AUTO Monitor displays abnormally ended Networks which are stored in
Abnormally Terminated Network File. If a Network to be queued exists in this file, that Network will bequeued in Rerun mode based on the information stored in the Abnormally Terminated Network file. The
operator will be prompted whether to continue with queuing process. To execute the abnormally ended
Network in Normal mode, i.e. iwthout Network recovery processing, the queuing should be aborted. The
operator may then delete the Network from Abnormally Terminated Network File by issuing TOM
command and re-execute the queuing process.

③

When queuing finishes normally, Network information stored in Network Stock File is automaticallydeleted or cleared.

④

After Queuing, A-AUTO Monitor will immediately execute any Network that has all its wait conditions
cleared or met. If the operator does not want immediate execution of Networks after queuing, theoperator can suspend A-AUTO Monitor operations by issuing Hold command (H Command) .

⑤

A-AUTO Monitor does not accept certain commands until Queuing is completed. Such commands will beprocessed after Queuing is finished.

6-29

6 Operations⑥

Except for Job information, modifications made to all other attributes of a Network in the Network Master
after Queuing are not reflected or updated to the Network in the queue (these modifications areapplicable from the next queuing process) .
For Job information, because the information stored in Network Master is referred only upon execution,
modifications made in the period between queuing and execution are applicable upon execution.
For Mainframe Connection Mode, both Network information and Job information at the time of queuing
are transmitted to A-AUTO Monitor. Modifications made to Job or other attributes of a Network will not bereflected to the Network in the queue.

Network
MasterNetwork
MasterNetwork Master

Job Information

Upon Job execution

Upon Queuing(3) Source of information
The following describes the source of information upon queuing.
 Network Attributes (except for Preceding Network information): Abnormally Terminated Network File is first referred to and then Network Stock file isreferred to.
The information defined in the first file is used.
 Network information (Preceding Networks): Daily Network Master is referred to if the Network exists and then Network Master isreferred to.
 Job information: Always Network Master

6-30

Operations of A-AUTO for UNIX/Windows

6.5

Monitoring

6.5.1

Networks in Wait StateThe queued Networks will be in wait state till their wait conditions are cleared. A-AUTO Monitor dispatches the
Network, which is ready to run i.e. all its wait conditions are cleared, to a Network Partition and executes it.

(1) Conditions to execute the Networks
The following are the possible wait conditions of a Network and the requirements to clear them for the Network
to be started for execution.
<1> If Hold code is defined for the Network, it has to be released<2> If Start Time is defined for the Network, the time has passed.
<3> Preceding Networks have to be completed normally.
Also, if there is Data Wait specified for the preceding Network, Monitor On Wait condition must be
released.
<4> If Data Waits are specified for the Network, all Data Waits have to be set as arrived or “ON”.
<5> The same Network has completed normally at its previous execution.
A-AUTO Monitor treats a Network, which meets all of the above requirements, as executable.

6-35

6 Operations

Example 6-7

Requirements to execute Networks
The diagram on the left shows the order in which the
NETWORK1

Networks are to be executed. Network NETWORK1

DS01

precedes NETWORK2 and NETWORK3. NETWORK2 and2004/01/05

NETWORK3 precede NETWORK4. NETWORK3 precedes
NETWORK2

NETWORK5.

NETWORK3
2004/01/05

2004/01/05

Each Network becomes ready for execution by meeting

H
NETWORK4
2004/01/05

15:00

following conditions.

NETWORK5
2004/01/05

Network

Condition

NETWORK1

 Normally ended at previous execution

NETWORK2

 NETWORK1 normally ends
 Normally ended at previous execution

NETWORK3

 Data ID DS01 is set as arrived
 NETWORK1 normally ends
 Normally ended at previous execution

NETWORK4

 Hold status is released Both NETWORK2 and NETWORK3 normally end
 Monitor On Wait of NETWORK3 is released
 Normally ended at previous execution

NETWORK5

 Time is past Start Time (15: 00)
 NETWORK3 normally ends
 Monitor On Wait of NETWORK3 is released
 Normally ended at previous execution

Requirements of conditions <1> to <4> are explained in detail below.

6-36

Operations of A-AUTO for UNIX/Windows<1> Hold attribute and Hold Code
Hold condition is one of the wait conditions that can be set for a Network. It can be set by the following threedifferent ways.
Register the Hold Code in Network Master
Hold code is an attribute that can be specified when defining a Network. If a Network that is defined with
Hold Code attribute is queued by the Queuing command or the Start command, the Network will bequeued in wait state with the Hold Code.



Specify the Hold code during Schedule Modification
Hold code can be specified temporarily for a Network for a specific schedule date. Operator can do so by
selecting a schedule date of a Network and defining the Hold attribute via [Daily Network Detail]Windows. When the Network is queued by the Queuing command or the Start command, the Network
will be queued in wait state with the Hold Code.



Specify the Hold Code using Hold Command
Hold code can be applied to a Network in the Network Queue by issuing Hold Command (H Command).
In this case, the Network is placed in a wait condition with the Hold Code immediately after thecommand.

Hold Code can be any alphanumeric one-byte code. Networks can be assigned different Hold Codes. Different
Hold Codes may be used to differentiate different conditions or reasons for holding different Networks. For
example, an operator specifies a Hold Code of “O” for a Network. Operator can use this Hold code “O” torepresent that the Network should be released when on-line processing finishes. By issuing display command(D Command), the Networks in wait state may be displayed together with their Hold Codes, if any.

6-37

6 Operations<2> Start Time Wait attribute
A Network with Start Time defined will become ready for execution when the defined Start Time has passed.
The Start Time is calculated based on the Schedule Date. For instance, a Network scheduled on May 20,
1997 with Start Time 33: 00 and another Network scheduled on May 21, 1997 with Start Time 9: 00 will starton the same time. Start time can be set by the following ways.
Register the Start Time in Network MasterStart Time is an attribute that can be defined when registering a Network to Network Master.

Specify the Start Time during Schedule Modification
Start Time can be specified temporarily for a Network for a specific schedule date. Operator can do so by
selecting a scheduled date of a Network and defining the Start Time via [Daily Network Detail] Windows.
When the Network is queued by the Queuing command or the Start command, the Network will bequeued in wait state with the Start Time.

Specify the Start Time parameter when issuing Start command
Start Time can be set when issuing Start Command (S Command) by specifying it in Time parameter ofthe command.



Change the Start Time when issuing Reset command
If a Start Time has been set in a queued Network, it can be modified by issuing Reset Command (Ecommand) with Time parameter.

<3> Preceding Network Wait
Preceding Network Wait condition of a Network is cleared only if all its specified Preceding Networks havecompleted normally. However, the Preceding relationship between Networks may differ from day to day
depending on their respective Network Schedules i.e. certain preceding Networks may not be scheduled forexecution on some days. If a preceding Network is not scheduled, A-AUTO Monitor will decide whether to
execute its succeeding Network based on its previous execution result. That is, the Preceding Network Wait
condition of a Network will be cleared if its preceding Network has been completed normally at the previous
execution, even if the preceding Network is not scheduled on that day. A-AUTO Monitor refers to the Network
Check File for the information of the previous execution of the Preceding Network.

Example 6-8

Preceding Network
6-38

Operations of A-AUTO for UNIX/Windows

Diagram on the left is an illustration of the above preceding relationship.
Network to be executed
NETWORK1

on every Monday
2004/01/05

NETWORK1 is defined as the preceding Network of NETWORK2. On
Monday, January 5, 2004, both Networks are scheduled. NETWORK2
is executed after NETWORK1. On January 6, 2004, NETWORK1 is notscheduled. In this case, A-AUTO Monitor refers to Network Check File.

NETWORK2

Network to be executed

If the Preceding NETWORK1, which is not scheduled on January 6,

everydaynormally ended on Monday January 5, A-AUTO Monitor assumes that

2004/01/06

succeeding NETWORK2 is executable.

Preceding relationships between Networks
Preceding relationships between Networks are specified in Network Master

NET1

NET2

NET4

NET3

NET6

NET5

In above example, Network NET3 will not start until Networks NET1 and NET2 end normally. Also, NET6 will
not be executed until both NET4 and NET5 end normally.
Preceding Networks may not be scheduled every day. For example, if NET5 is scheduled to be executed oncea month, then on those days that NET5 is not scheduled, A-AUTO monitor decides whether to start NET6 forexecution based on the previous execution status of NET5. .

6-39

6 Operations

Network Check File
A-AUTO Monitor uses Network Check file to control preceding relationships between Networks.
In the Network Check file, Latest Queued Schedule Date, Latest End Schedule Date, and Latest End Codedata fields are recorded for each Network. This information can be listed by the chkl utility. In the above
example, when NET1 and NET2 end, End Schedule Dates and End Codes of these Networks are recorded in
the Network Check file.
A-AUTO Monitor decides whether to start current NET3 based on the End Codes and End Schedule Dates ofboth NET1 and NET2 recorded in the Network Check file and the execution status of previous NET3 (NET3 ofprevious schedule date) .
Current NET3 is executable if NET1 and NET2 end normally and NET3 ends normally at its previous
execution, i.e. NET3 of previous schedule date ended normally. However, if schedule date of NET1 or NET2 islater than schedule date of NET3, it is not regarded as Preceding Network i.e. A-AUTO Monitor does notcheck END Code of NET1 or NET2.
To determine the status of a preceding Network, A-AUTO Monitor will check the Network Queue and then theactive or executing queue for Preceding Network. If the Preceding Network is not in either queue, it will get the
information from the Network Check File.

6-40

Operations of A-AUTO for UNIX/Windows

Ended Date of Network Check File
The last schedule date of a Network (End Schedule Date) is also recorded in the Network Check File.
A-AUTO Monitor determines end status of Preceding Networks by comparing the schedule date of a
succeeding Network with End Schedule Dates of preceding Networks and then checking their End Codes asfollows.
Network Schedule Date < End Schedule Date of preceding Network

Assume as normal end
Assume as normal end

Network Schedule Date = End Schedule Date of preceding Network

if End Code = ‘0’Assume as normal end

Network Schedule Date > End Schedule Date of preceding Network

if End Code = ‘0’

Network Check File

Start schedule of Network
Network

A-AUTO Monitor

Queue
Preceding relationships
Network Check

Network
Check search list

Preceding Networks can be specified by the following two methods.
Register the preceding Networks in Network Master
Preceding Networks can be defined when registering Network to Network Master.

Specify the Preceding Networks during Schedule Modification
Preceding Networks can be specified temporarily for a Network for a specific schedule date. Operator
can do so by selecting a scheduled date of a Network and defining Preceding Networks via [Daily
Network Detail] Windows. When the Network is queued by the Queuing command or the Start command,
the Network will be queued in wait state with the specified Preceding Networks.

6-41

6 Operations

Recording End Schedule Date and End code
End Schedule Date and End Code are recorded in Network Check file in the following three cases.

Ⅰ . When a Network has normally ended
A Network is queued into the Network Queue when Queuing command or Start Command (S Network name)is issued. When the Network normally ends, the End Schedule Date and End Code are written in Network
Check file.

Ⅱ . When Free command (F Network name) is used
When Free command (F Network name) is used to force a Network to normally ended status, the End
Schedule Date and End Code are written on Network Check file.
The following diagram describes a preceding relationship. Assume Network NET020 is set to normally end by
issuing Free Command (F Network name).

NET010NET020

NET030Usage example of Free Command[Mainframe side]F∆ ALOCALUX , A , FNET020 , ON , NAME = { ALL/AUTOXX }[UNIX side]cip∆ fnet020 , on

Ⅲ . When Network Check Write utility (chkd) is used
chkd utility writes End Code and other information into Network Check file for all Networks registered in
Network Master.
NoteThis utility must not be executed while A-AUTO Monitor is active.

6-42

Operations of A-AUTO for UNIX/Windows

Recording Queued Schedule Date
Queuing date is recorded in the following three cases.

Ⅰ . When a Network is queued by Queuing command
The Queuing date on the Network Check file is updated when a Network is passed from Daily Schedule
processor to Network Queue using Queuing Command (Q Command).

Ⅱ . When Network is queued by Start command (S Network ID)
The Queuing date on the Network Check file is updated when a Network is put into Network Queue using
Start Command (S Network ID).

6-43

6 Operations

Precedence check of Mainframe Connection ModeIn the case of Mainframe Connection Mode, preceding Network check is done as described below.

Mainframe
A-AUTO

A-LOCAL

A-LOCAL accesses thePreceding Network Inquiry
List at certain intervals tocheck
if
preceding
Networks
haveterminated.

Inquiry List

Preceding
Network
Inquiry List is created in
the local memory when
A-LOCAL starts.

②

UNIX/Windows

Preceding Network①

armt(AP-LINK)②①

A-AUTO Monitor

When Queuing command is issued from A-LOCAL to A-AUTO Monitor(<2> ) , Networks are added to thequeue and preceding Networks are checked on the UNIX side. Preceding Network check refers to theprocessing in which the information of preceding Networks that are stored in other nodes (Inquiry Message)
are transmitted to A-LOCAL(<1> ) . A-LOCAL stores the preceding Network information received in a memoryarea called Preceding Network Inquiry List. Inquiry Message is not only transmitted upon Queuing, but also
when Start Command is issued or upon warm start. ADD command also allows transmission of the Inquiry
Message if required. A-LOCAL checks the Preceding Network Inquiry List at intervals to determine whether
preceding Networks have ended. The interval time is defined by parameter INTERVAL in ALOCALUX. If
A-LOCAL confirms that a preceding Network has finished, it will send a message indicating that the preceding
Network has finished to A-AUTO Monitor(<2> ) . A-AUTO Monitor then sends back a confirmation for themessage to A-LOCAL and proceeds to execute succeeding Networks. A-LOCAL deletes the Network entry
from the list after receiving the confirmation.

6-44

Operations of A-AUTO for UNIX/Windows

Notes on Mainframe Connection Mode

■ When A-LOCAL is stopped and restarted during operation
When A-LOCAL is stopped and restarted, the Preceding Network Inquiry List is initialized. In such case, thefollowing operations are necessary to re-send Preceding Network Inquiry message.
<1> Restart A-LOCALS∆ALOCAL
Note that if the following message is displayed during the start-up process, initialization of TCPIP PORT has
failed.
MCS104W TCP/IP DRIVER RC=00000025 REASON=00000030
Wait about 5 minutes for TIME_WAIT status of the port to be released and then restart A-LOCAL.
<2> Confirm connections with all armts
F∆ALOCAL,A,DT,NAME=ALL
Confirm AUX739I message is returned from all connected armts.
<3> Hold Network QueueF∆ALOCAL,A,HQ,NAME=ALL
Large quantity of data is transmitted from A-AUTO Monitor to A-LOCAL during re-sending of Preceding
Network Inquiry Message.
To reduce network traffic load, the operator must Hold the Network Queues at the A-AUTO Monitors.
<4> Request re-send of Preceding Network Inquiry Message
F∆ALOCAL,A,XR,NAME=ALL
Preceding Network Inquiry Messages are re-sent from A-AUTO Monitor to A-LOCAL by issuing Timer Queue
rebuild request (XR). AUX839I message is displayed when rebuild is completed.
<5> <5> Release Network QueueF∆ALOCAL,A,AQ,NAME=ALL
Confirm AUX839I message is returned from all connected armts before the Release Network Queuecommand.

6-45

6 Operations■ If A-AUTO Monitor is started with warm option during operation
When A-AUTO Monitor is stopped and restarted with warm option, confirm the connection between A-LOCAL
and armt is successful. If disconnected, Preceding Network Inquiry Messages will be stored into
auw_netendfile. If System Parameter ARMT_KEEPNEND is set to ‘1’, the messages will be sent to A-LOCAL
from auw_netendfile automatically after connection is successful.
■ When ALC017W message is displayedPreceding Network Inquiry List is created when A-LOCAL is started. Maximum allowable number of Preceding
Network Inquiry messages that can be stored is specified by MAXQUERY1 keyword of ALOCALUX parameter.
Data in Preceding Network Inquiry List is added during Queuing, Start Command, and XR command and isremoved when succeeding Networks of the Preceding Networks on other node are started.
When the usage of the list is over 80%, ALC019W message is displayed. When the usage is 100% and no
more inquiry message can be stored, ALC017W message is displayed. In such case, the following operations
are necessary to restore the Preceding Networks Inquiry List.
<1> Take a memory dump of Preceding Network Inquiry ListF∆ALOCAL,O,DUMP<2> Hold Network QueueF∆ALOCAL,A,HQ,NAME=ALL<3> Stop A-LOCAL<4> Expand Preceding Network Inquiry List
Increase the value of MAXQUERY1 parameter.
<5> Restart A-LOCALS∆ALOCAL
Note that if the following message is displayed during the start-up process, initialization of TCPIP PORT has
failed. MCS104W TCP/IP DRIVER RC=00000025 REASON=00000030
Wait about 5 minutes for TIME_WAIT status of the port to be released and then restart A-LOCAL.
<6> Confirm connections with all armts
F∆ALOCAL,A,DT,NAME=ALL
Confirm AUX739I message is returned from all connected armts.

6-46

Operations of A-AUTO for UNIX/Windows<7> Request re-send of Preceding Network Inquiry Message
F∆ALOCAL,A,XR,NAME=ALL
This Timer Queue rebuild command (XR) sends a request to A-AUTO Monitor to re-send Preceding Networks
Inquiry Message to A-LOCAL.AUX839I message is displayed when the rebuild is completed.
<8> Release Network QueueF∆ALOCAL,A,AQ,NAME=ALL
Confirm AUX839I message is returned from all connected armts before the Release Network Queuecommand.

6-47

6 Operations

Explanations regarding usage and syntax of commands are described in the following section.
■ How to use Commands
F∆Modify name, O, Command[, parameter １]…

- DUMP command
Output ALOCAL system tables and Preceding Network Inquiry List in character image to DD name ALDUMP.
F∆ALOCAL,O,DUMP-REPLY command
The specified information is sent to A-AUTO Monitor as Network End information.
When a succeeding Network does not start in A-AUTO Monitor, use REPLY command to send Network End
information to start the succeeding Network.
F∆ALOCAL,O,REPLY,Network ID,Preceding Network ID,Schedule Date,Monitor ID
Example)F ALOCAL,O,REPLY,OLTM01,BSPSTA,20040730,AUTO74- ADD command
The specified information is added into Preceding Network Inquiry List.
F∆ALOCAL,O,ADD,Network ID,Preceding Network ID,Schedule Date,Monitor ID
Example)F∆ALOCAL,O,ADD,OLTM04,OLTM01, 20041007,AUTO75

6-48

Operations of A-AUTO for UNIX/Windows-DEL command
The specified information is removed from Preceding Networks Inquiry List. Wild card can be specified foreach item. Please note entries cannot be recovered once they are removed.
F∆ALOCAL,O,DEL,Network ID,Preceding Network ID,Schedule Date,Monitor ID
Example)F ALOCAL,O,DEL,OLTM04,OLTM01, 20041007,AUTO75
When wild card is used <1> <1>
F ALOCAL,O,DEL,B*,OLTM01, 200410*,AUTO75
When wild card is used <2> <2>
F ALOCAL,O,DEL,*,*,*,*-INTERVAL command
To change the Interval time to search Preceding Network Inquiry List by A-LOCAL.
As the reset is done by interval, it may not be reflected immediately.
F∆ALOCAL,O,INTERVAL,new interval
Example)F ALOCAL,O,INTERVAL,120

6-49

6 Operations<4> Input Data Wait
A Network that is defined with Data Waits will automatically be released for execution when all its defined Data
Waits arrive or are set on. A Data Wait is an internal flag that can be used to represent an event, such asarrival of input data, Job termination. A Data Wait can be set on by dsfo utility to indicate that the represented
event has happened or arrived. A-AUTO Monitor clears the Input Data Wait condition of a Network when all its
defined data Waits are set on. The Network becomes executable and the Data Waits will be set off.
Association between Networks and Data Waits is stored in the Data Wait Master file. A-AUTO Monitor refers
to the Master for information on the association. Therefore, if the association between a Network and a Data
Wait is changed in the Master, A-AUTO Monitor is able to get the updated information even if the Network with
input Data Wait attribute is already in Network Queue. This is applicable only if the Data Wait attribute isdefined in the Master at the queuing time (Queuing command or Start command) .
A Network defined with Data Waits may also be released for execution by issuing Reset command (ECommand). Reset command clears the Input Data Wait condition regardless of whether the defined Data
Waits are set on or off.
Using [Daily Network Detail] dialog, the operator can cancel Input Data Wait attribute for a Network for a
specific schedule date. (However, Data Waits already defined for the Network cannot be modified in this
dialog.)

6-50

Operations of A-AUTO for UNIX/Windows

NP Partition assignment
Similar to what OS does in Job execution, A-AUTO Monitor extracts executable Networks from Network
Queue to execute. Network Queue contains Networks that are scheduled for execution but may be waiting fortheir wait conditions to be cleared before they become executable. A-AUTO Monitor searches the Network
Queue for executable Networks and then executes the Networks.
After selecting an executable Network from Network Queue, A-AUTO Monitor allocates the Network to apartition. This partition is called NP (Network Partition). A-AUTO Monitor constantly checks the condition of
NPs and assigns executable Networks in Network Queue to available NPs. Executable Networks are assigned
to NPs according to the following conditions.
1.

Chronological order of Schedule Date

2.

Ascending order of Class

3.

Priority

4.

Ascending order of Network ID

When a NP partition has been assigned to a Network, one or more JP partitions (Job Partition) may be
assigned to the Jobs in the Network. A-AUTO Monitor searches for the JP partition having the same class as
the NP Network class. If there is no JP partition with the same class available, the Job will wait for theavailability of JP but the Network still remains in the NP partition.
The following describes the processing flow on how A-AUTO Monitor assigns Networks and Jobs to the NP
and JP partitions.
①

Extracts an executable Network from Network Queue.

②

Searches for a NP partition that has the class identical to the one defined for the Network.
If there is no identical class, the Network cannot be executed.

③

Checks if the NP partition, which has the class identical to the one defined for the Network, is available
or not (whether another Network is running in the NP partition).
If available, allocates the Network to the NP partition. In the event that the NP partition is not available(another Network is running), repeat the search for the next NP.

④

Searches for a JP partition to execute the Job. First, searches for a JP partition that has the class
identical to the class of the NP partition. If there is no identical class, the Job cannot be executed but the
Network still remains in the NP partition. (This may lead to a decrease in processing efficiency of
A-AUTO Monitor)

6-51

6 Operations

Relationships among NP Partition, JP Partition, and assigned Networks are shown in below diagram, which
are messages displayed when “DA, ALL” is entered.
%host: > cip da,all
AUX426I *** ACTIVE NETWORK DISPLAY *** TIME=15: 36: 29
AUX024I AUTOPROC: AUTO21 MODE: PRODUCTION
AUX429I NP# C NST NETWK SDATE
JP# N O JOB-NAME
AUX430I 1 A NET01 2004/01/16
1
A A JOB00001
AUX430I 2 A NET02 2004/01/16
2
A A JOB00002
AUX430I 3 C
3A A
AUX430I 4 A NET03 2004/01/16
4
B A
AUX430I 5 A H
5A A JOB00004
AUX430I 6 A NET04 2004/01/16
6
A A JOB00008
AUX430I 7 A NET05 2004/01/16
7
A A JOB00005
AUX430I 8 A NET06 2004/01/16
8
A A
AUX430I 9 A
9AA
AUX430I 10 A 10 A A
NP Number
NP Class

ActiveNetwork ID

Schedule Date
JP Number

15: 36: 27
15: 36: 28
15: 36: 29

Start Time
Active Job ID

JP Class
NP in Hold status

S STIME
15: 36: 25
15: 36: 26
H

OS Class (Not used)

6-52

JP in Hold status

Operations of A-AUTO for UNIX/Windows(2) Commands issuable for Networks in wait condition
The following commands can be issued for Networks in wait state.
Cancel Command (C Command)
Cancels the Network i.e. remove or discard it from Network Queue.



Release Command (A Command)
Releases the Hold Code condition.



Display Command (D Command)
Displays the detailed information and status of the Network.



Reset Command (E Command)
Resets or changes Network attributes such as Start time and Priority.

Free Command (F Command)
Forced change the execution status of the Network to normally ended.



Monitor On Command (M Command)Set or releases Monitor On Wait condition.

6-53

6 Operations

6.5.2

Networks being executed
A-AUTO Monitor monitors the wait conditions of Networks and runs executable Networks according to the Job
attributes defined for the Networks.

(1) Job execution
A-AUTO Monitor runs Jobs in a Network according to the Job information in Network Master, such as
preceding relationship among Jobs, i.e. A-AUTO Monitor refers to Network Master when it executes Jobs.
A-AUTO Monitor reads the Job information, which is stored in Network Master, when a Network is executed.
For a Network in Network Queue, it is important to note that any modification to its Job information stored in
Network Master will be applicable when the Network is executed.

Example 6-9

Parallel Run
The diagram below describes the execution flow of Jobs in NETWORK1.

NETWORK1

 The preceding Job of JOB012(Job Number: 020) is
JOB011(Job Number: 010)

Job Number:010

 The preceding Job of JOB013(Job Number: 030) is

JOB011

JOB012(Job Number: 020)
Job Number:020

 The preceding Job of JOB014(Job Number: 040) is

JOB012

JOB012(Job Number: 020)
Job Number:
040
Job Number:
030①

JOB013

JOB014

If Parallel Run attribute is not defined for NETWORK1
In the above execution flow of NETWORK1, when JOB011 and JOB012 end normally in that order,
JOB013 is executed. When JP partition is released after the execution of JOB013 finishes (regardless ofNormal End／Abnormal End) , JOB014 will be executed.

②

If Parallel Run attribute is defined for NETWORK1
In the above execution flow of NETWORK1, when JOB011 and JOB012 end normally, JOB013 is
executed. Then, JOB014 may be executed in parallel with JOB013 if there is an available JP partition.

6-54

Operations of A-AUTO for UNIX/Windows(2) Commands issuable for active Networks
The following commands can be issued for Networks that are currently being executed.
 Cancel Command(C Command)
Cancels the execution of currently running Network.
 Stop Command(P Command)
Suspends the execution of currently running Network.
 Go Command(G Command)
Restarts the execution of the Network that has been suspended using Stop Command.

6-55

6 Operations

6.5.3

Terminated Networks
A-AUTO Monitor monitors execution status of Networks. When a Network ends, A-AUTO Monitor writes its
termination information (when, where, how and which Network/Job terminated) to a Network Log File (written
for each Job) and Network Check File (written for each Network).
Termination information of each Job is recorded in the Network Log file and the contents of the log file can bedisplayed using log0 utility or by issuing Display Log command.

(1) What is termination of a Network
A Network is considered to be ended under the following conditions.

①

All of the Jobs that make up the Network finish normally.

②

Free Command(F Command) is issued to the Network and the Network is treated as an ended (Free-On)
Network.

③

A Job that makes up the Network abnormally ends
and no other executable Jobs are left in the Network.

④

Cancel Command(C Command) is issued to the Network and the execution of the Network is canceled.

In A-AUTO Monitor,
A Network which ended as described in <1> or <2> is regarded as Normally Terminated or Normally
Ended Network

A Network which ended as described in <3> or <4> is regarded as Abnormally Terminated or Abnormally
Ended Network

6-56

Operations of A-AUTO for UNIX/Windows(2) Commands issuable for terminated Network
The following command can be issued to normally ended Networks.
 Start Command(S Command)(Rerun the Network)
A-AUTO Monitor has 5 possible Job termination statuses or Return Codes as explained below. If a Recovery Job isdefined for the executed Job, this Recovery Job will be executed if the return code other than 00 is returned.

Termination of Job

Return CodeNormally ended.

00

Job was canceled by Cancel (C) command during the execution.

04

The Job ended with 'NOT RUN' due to batch file error or because of some08

other error reason.
The Job ended due to ABEND of system or the user

12

The return code of the Job itself is equal to or greater than the defined12

MAX Return Code, so the Job was abnormally ended.

6-57

6 Operations

6.5.4

Abnormally ended Network
A-AUTO Monitor constantly monitors the execution status of the Network. When a Network abnormally ends,
the execution result is recorded to Network Log file, Abnormally Terminated Network File, and Network CheckFile.
In particular, exit state of the abnormally ended Network (when, where, how, and which Network/Job has
abended) is recorded to Abnormally Terminated Network file. The Network may be re-executed (rerun) basedon the record in the Abnormally Terminated Network file. When the Network ends normally at rerun, the record
is deleted from the file.

■ What is abnormal termination of a Network
Any one of the following conditions indicates that the Network has abnormally ended.
 Any Job that makes up the Network was not executed due to script error and so on.

 Any Job that makes up the Network has abnormally ended and, as a result, the Network is treated asabnormally ended.
 Any Job that makes up the Network has returned a return code that exceeds the Max Return Codedefined and, as a result, the Network is treated as abnormally ended.
 The Network/Job was cancelled by Cancel Command (C Command).

If any of the Jobs in a Network ends abnormally, A-AUTO Monitor will regard this Network as abnormallyended and the information regarding the Network (when, where, how, and which Network/Job has abnormallyended) is recorded in Abnormally Terminated Network File.
Example 6-10

Abnormal Termination of a Network
The diagram below describes the execution flow of Jobs in NETWORK2.

 JOB022 (Job No: 020) is dependent on the

NETWORK2

successful completion of the preceding JOB021 (Job
Job Number:
010

No: 010).

JOB021 JOB023 (Job No: 030) is dependent on the
Job Number:020

successful completion of the preceding JOB022 (Job
JOB022

No: 020).
Job Number:
040

Job Number:
030

JOB023

 JOB024 (Job No: 040) is dependent on the
successful completion of the preceding JOB022 (Job

JOB024

No: 020).

If JOB022 abends or does end normally due to script error and so on, JOB023 and JOB024 will not be
executed and the Network NETWORK2 will abnormally end.

6-58

Operations of A-AUTO for UNIX/Windows

6.6

Rerunning Networks
A user may rerun any Network that ended normally or abnormally under A-AUTO Monitor.
Rerun of a Network can be executed by issuing Start Command (S Command).
Networks in the following conditions can be re-executed as needed.

6.6.1

Rerun Normally Terminated Network
In A-AUTO for UNIX/Windows, a normally ended Network under A-AUTO Monitor may be rerun. This type ofrerun is called Normal Rerun. In this case, the following options can be selected.
 Rerun a Network with some of its attributes (Start Time, Priority, etc.) modified.
 Rerun certain Jobs in the Network.

6.6.2

Rerun Abnormally Terminated Networks
A Network that has been executed and abnormally ended under A-AUTO Monitor can be re-executed after
resolving the problem by issuing Start Command (S Command). When a Network is rerun under this condition,
it will restart its execution from the last abnormally ended Job(s). When all of the Jobs in the Network end
normally during rerun, the Network will be considered as normally ended.
(In this case, the abnormal termination information of the Network will be deleted from the Abnormally
Terminated Network file.)
The information regarding abnormally ended Network is recorded in the Abnormally Terminated Network File.
Using the information in this file, the rerun of a Network is executed from the abnormally ended Job(s). If you
want to rerun all the Jobs as registered in the Network Master file instead of from the abnormally ended Job,
delete the record of the Network from Abnormally Terminated Network file by issuing Tom Command (TCommand). Then, rerun the Network by Start Command (S Command).
The procedure to rerun abnormally ended Network under A-AUTO Monitor is explained in the following
section.
Note
Do not issue Tom Command (T Command) to delete record from Abnormally Terminated Network File while
the abnormally ended Network that is rerun is executing.
In the case of rerun, A-AUTO monitor ignores the preceding relationship of the rerun Network. For example,
even if a Network that is defined as a preceding Network of the abnormally ended Network exists in Network
Queue, the abnormally ended Network will start execution (rerun) , regardless of the execution status of thispreceding Network.

6-59

6 Operations■ The procedure to rerun the Network①

Determine and resolve the cause of the abnormal end.

②

To rerun the Network from the abended Job, issue Start Command(S Command) and rerun the Network.

③

If you want to rerun all the Jobs as registered in the Network Master file instead of from the abnormallyended Job, delete the record of this Network in Abnormally Terminated Network File using Tom
Command(T Command). Issue Start Command(S Command) to rerun the Network beginning from the first Job in the Network Master.

④

In the case of rerun from the abended Job, the information of the abnormally terminated Network is
automatically deleted from Abnormally Terminated Network File when rerun finishes normally.

Example 6-11

Rerunning Abnormally Terminated Network＜Condition>
NETWORK3NETWORK3 consists of 5 Jobs, ‘JOB300’, ‘JOB301’,‘JOB302’, ‘JOB311’, ‘JOB312’. Preceding relationships

JOB300among Jobs are shown on the left.
NETWORK3 has parallel run attribute.
JOB301JOB311JOB302JOB312

Example of a rerun after ‘JOB301’ ends abnormally is given below. Note that ‘JOB311’ after ‘JOB312’ areindependent of ‘JOB301’ and therefore, A-AUTO Monitor executes them even though ‘JOB301’ ends
abnormally. Assume ‘JOB311’ after ‘JOB312’ also end normally.
① Determine and resolve causes of abnormal end.
② Issue Start Command.
③ NETWORK3 is executed with Rerun Type.
④ AUTO Monitor first executes JOB301. It then executes ‘JOB302’ after ‘JOB301’ ends normally.
⑤ After JOB301 and JOB302 finish normally, NETWORK3 ends normally.
※

6-60

Operations of A-AUTO for UNIX/Windows

6.7

Executing Unscheduled Networks
In a standard operation, Networks which are not extracted or finalized by the Finalized Schedule function are
not queued for execution. However, an unexpected requirement may occur to execute unscheduled Networks.
In order to address the issue, you can request A-AUTO Monitor to execute unscheduled Networks using Start
command.
A-AUTO Monitor refers to Network Master or Daily Network Master for Network information as follows.

Refers to the Daily Network Master for the target Schedule date
Records do not exist for
the target Schedule date

Records exist for the target
Schedule date

Daily Network
Master

Refers to Network Master for all

Refers to Daily Network Master for

the Network information.

Network information and refers to
Network
information.

6-61

MasterforJob

6 Operations

6.7.1

Time Interval Execution Function
Time Interval Execution function allows a user to repeat or trigger the execution of the same Network at a
specified time interval. The Network is re-queued and executed again at a calculated time if it ends normally.
However, a Network will not be re-queued in the following cases.
<1> The calculated start time of the next repeat-execution exceeds the specified end time of Time Interval
Execution for the Network.
The start time of the next repeat-execution is calculated using the following formula.
“Start Time of the Network” + (“Time interval” * “Number of times triggered for execution” ) .
*The Network is re-queued if the calculated start time of the next repeat-execution is equal to the end time ofTime Interval Execution.
<2> The end time of the Network exceeds the end time of Time Interval Execution.
<3> If a Network ends abnormally
To use Time Interval Execution function, the following setup is needed.
<1> Set a value of 1 or 2 for system parameter, AUTO_TMITVLON.
(The computation for repeat-execution timing for the function is different for values 1 and 2.)<2> Specify a start time for the Start Time Attribute of the Network in Network Master.
<3> Specify the repeat-execution time interval and the end time (start time for the final repeat-execution) ineither Time Interval Execution Definition file (TMITVLDEFFILE) or Network Master.

Differences between AUTO_TMITVLON values of 1 and 2・ In the case of AUTO_TMITVLON = 1
A-AUTO Monitor calculates the start time of the next repeat-execution using the following formula:“The start time of the next repeat-execution =”The start time of the Network (defined in Start Time attribute) ”+(“Specified time interval” * “Number of times
triggered for execution” ) ”
When there is a processing delay, e.g. the processing of the Network takes longer than the defined timeinterval or a delay in start time of the Network occurs, the calculated start time for the next repeat-execution
may be past the current CPU time. In such a case, the Network will be executed immediately when it isre-queued.
(Please refer to example 2 “When Processing delay occurs”)

・ In the case of AUTO_TMITVLON = 2
A-AUTO Monitor calculates the start time of the next repeat-execution using the following formula:“The start time of the next repeat-execution = “The start time of the Network (defined in Start Timeattribute) ”+(“Specified time interval” * ｎ ) > current CPU time “(*n indicates the smallest assignable value)
When there is a processing delay, e.g. the processing of the Network takes longer than the defined time

6-62

Operations of A-AUTO for UNIX/Windowsinterval or a delay in start time of the Network occurs, n value is adjusted such that the calculated start time forthe next repeat-execution is greater than or equal to the current CPU time.

(Please refer to example 2 “When processing delay occurs”)
System Parameter, AUTO_TMITVLON, can be modified via “Settings of Monitor” screen of System
Management of A-AUTO/Web client.

(1) Network Master
Please refer to “3.1 Network Master” for explanation on how to define Time Interval Execution Function setting
in Network Master.

(2) Time Interval Execution Definition file Defining Time Interval Execution Definition file
[Network ID]
ENDTIME = HH.MM<1>

INTVL = Interval<2><1> Specify the end time (the last start time for the final repeat-execution) for ENDTIME . (HH.MM:
hour.minute)<2> Specify the time interval in minutes to trigger the Network again for repeat execution.

In the case of A-AUTO for UNIX
The definition file must be stored in the directory defined in System parameter AUX_FILES_PATH and the filename is “TMITVLDEFFILE”
Example) If AUX_FILES_PATH = /home/auto/files/ ,The definition file is “TMITVLDEFFILE” under /home/auto/files/【Example of definition】Network with Network ID of “ANET001” is re-queued every 60 minutes from start timetoend time of 21: 30.
ANET001:
ENDTIME = 21.30
INTVL = 60

In the case of A-AUTO for Windows
The definition file must be stored in the directory defined in System parameter FILES_PATH and the file nameis “TMITVLDEFFILE”

6-63

6 Operations

Example) If FILES_PATH = c: \bsp\auw\files\ ,The definition file is “TMITVLDEFFILE” under c: \bsp\auw\files【Example of definition】Network with Network ID of “ANET001” is re-queued every 60 minutes from start timetoend time of 21: 30.
[ANET001]
ENDTIME = 21.30
INTVL = 60

6-64

Operations of A-AUTO for UNIX/Windows(3) The flow of Time Interval Execution of Network
Network ID: NET325
Start time: 13: 20
End time of Time Interval Execution(ENDTIME) : 14: 00
Execution time interval(INTVL) : 20
Suppose the processing time of the Network usually takes 5 minutes.
Example 1 Normal condition
13

14

Scheduled
Actual1. 08: 30 : Queuing
2. 13: 20 : Execution of NET325 starts
3. 13: 25 : NET325 finishes normally and re-queued for execution on 13: 40
4. 13: 40 : Execution of NET325 starts
5. 13: 45 : NET325 finishes normally and re-queued for execution on 14: 00.
6. 14: 00 : Execution of NET325 starts
7. 14: 05 : NET325 finishes normally

6-65

15

6 Operations

Example 2 When processing delay occurs◆ If AUTO_TMITVLON = 1,
The start time of the next repeat-execution is calculated using the following formula:““The start time of the Network (defined in Start Time attribute) ” + (“Specified time interval” * Number oftimes triggered for execution ) ”.

１３

１４

30

30

１５

Scheduled
Actual

1．13: 45 : Queuing
2．13: 45 : Execution of NET325 starts
3．13: 50 : NET325 finishes normally and re-queued for execution on 13: 40
4．13: 50 : Execution of NET325 starts
5．13: 55 : NET325 finishes normally and re-queued for execution on 14: 00
6．14: 00 : Execution of NET325 starts
7．14: 05 : NET325 finishes normally＊As shown in the above example, execution time interval will not be 20 minutes if processing delay occurs.

◆ If AUTO_TMITVLON = 2,
The start time of the next repeat-execution is calculated using the following formula:““The start time of the Network (defined in Start Time attribute) ”＋((“Specified time interval” × ｎ ) >Current CPU time “.
In this case, the start time of the next trigger for execution must always be greater or equal to current CPU
time. Unlike the case of AUTO_TMITVLON = 1, the time interval of execution is kept even when application
delay occurs.
１３

１４

30

Scheduled
Actual

1．13: 45 : Queuing
2．13: 45 : Execution of NET325 starts
3．13: 50 : NET325 ends normally and re-queued for execution on 14: 00
4．14: 00 : Execution of NET325 starts
5．14: 05 : NET325 ends normally

6-66

30

１５

Operations of A-AUTO for UNIX/Windows

Example 3 If the actual end time of Network exceeds the specified End Time
13

14

15

Scheduled
Actual

1. 14: 30 : Queuing
2. 14: 30 : Execution of NET325 starts
3. 14: 35 : NET325 ends normally*As shown in the above example, the Network is not re-queued if the actual end time exceeds the specified
End Time.

Example 4 When a Network ends abnormally
13

14

Scheduled
Actual1. 08: 30 : Queuing
2. 13: 20 : Execution of NET325 starts
3. 13: 25 : NET325 ends normally and re-queued for execution on 13: 40
4. 13: 40 : Execution of NET325 starts
5. 13: 45 : NET325 ends abnormally

6-67

15

6 Operations

Time Interval Start for Network with Preceding Relation
When you define Networks that have Preceding Relation for Time Interval Execution function, the number of
repeat executions for the Preceding Network and the Succeeding Network may be different. An example is asfollows.
Network ID: NET1ST, NET2ND (NET1ST is NET2ND’s Preceding Network)
Start Time: Both NET1ST and NET2ND are defined with Start Time of 17:00.
Time Interval(INTVL) : Both NET1ST and NET2ND are defined with Time Interval of 3 minutes.
Processing Time: The processing time for NET1ST is 1 minute and for NET2ND is 2 minutes.
AUTO_TMITVLON = 2 is assumed.

e.g. When the repeat executions of Preceding Network and Succeeding Network are different.
17H
NET1ST

01

03

05

07

09

*1 unit 1 min

・・・

NET2ND・・・

For example, NET1ST start running at 17:00:01, the Networks will be executed as follows.

1. 17:00:01 : NET1ST (Time 1) starts running
2. 17:01: 01 : NET1ST (Time 1) ends normally
NET1ST (Time 2) is re-queued for execution with Start time 17:03:00.
NET2ND (Time 1) starts running
3. 17:03:01 : NET1ST (Time 2) starts running
When NET2ND (Time 1) ends normally, the time has passed 17:03:00.
NET2ND (Time 2) is re-queued for execution with Start time 17:06:00.
4. 17:04:01: NET1ST (Time 2) ends normally
NET1ST (Time 3) is re-queued for execution with Start time 17:06:00.
5. 17:06:01: NET1ST (Time 3) starts running
NET2ND (Time 2) Start Time condition is met but, because the Preceding Network(NET1ST) has not finished yet, NET2ND cannot be started and is placed in “Execute
Wait” status.
6. 17:07:01: NET1ST (Time 3) ends normally
NET1ST (Time 4) is re-queued for execution with Start time 17:09:00.
NET2ND (Time 2) starts running

In the above case, NET2ND (Time 2) starts after NET1ST (Time 3) has ended. NET1ST has run for 3 times
while the succeeding Network NET2ND (Time 2) has not run for 2 times yet.

6-68

Operations of A-AUTO for UNIX/Windows

When you define Networks that have Preceding Relation for Time Interval Execution function, you should
consider the time required to process the Networks.
Notes
Start time of re-queued Network is calculated based on the Start Time specified in Network Master.
However,

if

the

start

time

is

modifiedusing

E

Command(Resetcommand,cip

eNETNAME,time=HHMM) , the start time is calculated based on the modified time.


If the Network Master is modified for a Network using Time Interval Execution, the changes made to the
Master record are reflected to the Network only when it is next re-queued after the modification. However,modifications made are not applicable to Network that is already in queue.

When a Network ends normally and is re-queued, its status is displayed as Normally Ended (not “InQueue” status) on A-AUTO/Web client. To show the latest status, re-issue File Transfer Request (FTP).



If a Network of a past schedule date finishes normally, the Network will be re-queued under following
condition: End time of the Network ≤ specified End Time. In such case, the schedule date of there-queued Network will be the original schedule date.



If a Network with no Start Time attribute is specified, the assumed start time is 00: 00.

The schedule date of Queuing must be the same as the Operation Date.



The same Job Library ID is used when Network is re-queued by Time Interval Execution Function.
Please refer to “8.10 Test Run Function” for defining Job Library ID.

6-69

6 Operations

6.7.2

Rerun Recovery Function*This function is not recommended for V710 or later. In V710 or later, Recovery Job can be defined in Network
Master. (Please refer to “3.1.4 Job Branching Function” for Recovery Job.)
Before rerunning an abnormally ended Job, some recovery process may be necessary. A-AUTO for
UNIX/Windows provides a function to specify the recovery Network for the Job in advance, and to execute thisrecovery Network automatically before an abnormally ended Job is rerun. This is called the Rerun Recovery
function.
Jobs that use this function may define their Recovery Networks in the Recovery Definition file.

(1) The flow to rerun the Network
Below are the Rerun Recovery procedure and the process flow when a Job defined with Recovery Network
abnormally ends.

①

Rerun the abnormally ended Network by issuing Start Command.

②

When A-AUTO Monitor receives the Start Command,
it first executes the specified Recovery Network.

③

When the Recovery Network ends, A-AUTO Monitor starts the abnormally ended Network.

Example6-12

Rerun processing example of a Network defined with Recovery Network＜Condition>

NETWORK4NETWORK4 (Network ID) consists of “JOB401”,“JOB402” and “JOB403”. Figure1 shows preceding

JOB401

relationships between these Jobs.
Recovery

RNET4

Network

RNET4

isspecified

Job402.

JOB402

Figure 2 shows Job configuration of RNET4.

RJOB401
JOB403RJOB402
Figure 1
Figure 2

6-70

for

Operations of A-AUTO for UNIX/Windows

If “JOB402” ends abnormally, the flow of execution is as follows.
① Determine and resolve the cause of abnormal end of “JOB402”.
② Start the abnormally ended Network by issuing Start command.
③ Recovery Network, RNET4 starts and“RJOB401” and then “RJOB402” are executed.
④ After RNET4 ends, NETWORK4 is queued. When ready to execute, abnormally ended Job (“JOB402”)
runs first. Execution of Network NETWORK4 ends when the execution of succeeding Job (“JOB403”)
completes.
* NETWORK4 will be executed even if the Recovery Network does not end normally.

6-71

6 Operations(2) Recovery Definition File
Recovery Networks are specified in the Recovery Definition file.
To use Rerun Recovery function, the following setup is needed.
・System Parameter AUTO_REREON should be set to 1. System Parameter AUTO_RERERPT should be set to 0.
・Jobs that use the Rerun Recovery function are defined in Recovery Definition file, RRNDEFFILE.
・Recovery Networks themselves are registered in Network Master.

 Specification of Recovery Definition file
[Network ID／Job ID]:RNET ＝ Recovery Network ID

<1>
<2>

<1> For each Job that requires recovery when it ends abnormally, specify the Job ID and the Network ID
that the Job belongs to.
<2> Specify Recovery Network ID following this keyword ‘RNET =’. Note that this Recovery Network must
be registered in Network Master.
In the case of A-AUTO for UNIX
The definition file must be stored in the directory defined in System Parameter (AUX_FILES_PATH) and thefile name is ‘RRNDEFFILE‘
Example) If AUX_FILES_PATH = /home/auto/files/, Recovery Definition file, RRNDEFFILE, is stored in thefollowing directory:→ /home/auto/files

 【Definition example】
NETWORK4/JOB402:
RNET ＝ RNET4

In the case of A-AUTO for Windows
The definition file must be stored in the directory defined in System Parameter (FILES_PATH) and the filename is ‘RRNDEFFILE‘
Example) If AUX_FILES_PATH = c: \bsp\auw\files\, Recovery Definition file, RRNDEFFILE, is stored in thefollowing directory:→ c: \bsp\auw\files\

 【Definition Example】[NETWORK4/JOB402]
RNET = RNET4

6-72

Operations of A-AUTO for UNIX/Windows

Notes


Recovery Network must be defined in Network Master similar to other standard Networks. However, do
not register Recovery Network in Network Schedule Master (do not define an execution schedule for
Recovery Network).



Recovery Network for a Job is automatically executed by A-AUTO Monitor and therefore it should not be
executed by Start Command.



If a Recovery Network is canceled, the abnormally ended Network will not be started and it remains asabnormally ended status

Any changes in the Recovery Definition file are reflected immediately and A-AUTO Monitor does nothave to be restarted.



The maximum number of Recovery Networks that can be run at the same time is 16. The 17th Network
will not be queued, the following message is displayed
AUX659E NG PCCB IS FULL. SECTION Network/Job RRN Recovery NetworkWhen there are Networks started by Start command with Job Option and these Networks are executing,then the maximum number of Recovery Networks will be limited as follows[The number of Recovery Network + Network with Job Option defined]must be less than or equal to 16.



If an abnormally ended Network is rerun by Start Command with Job Option defined, Rerun Recovery
function is not applicable even if the Network is a Rerun type.



To run a recovery for Network that has abnormally ended on a past schedule date,specify the schedule date in the Start command when rerunning this Network:
cip s Network ID,sdate=20010701



Execution result of Recovery Network is not recorded in Network Check File (chkl utility) or Abnormally
Terminated Network File (Except for cases where the Recovery Network is canceled).

The Same Recovery Network can be specified for different Jobs but only one such Network can exist in
the Network Queue at the same time. The following message is displayed if the operator attempts tostart the abnormally ended Networks that have Jobs with the same Recovery Network at the same time:“AUX662I RNET Recovery Network/abnormally ended Job NOT QUEUED, SDATE=2001/07/01
ALREADY QUEUED (BLK XX OFFSET XX) “.



When a Recovery Network is queued or being executed, the abnormally ended Network is in status of“waiting queuing”. If a Start command for a Network in that status is issued, the command is not
accepted and the following message is displayed.
AUX803I NETWORK Network ID SDATE=yyyy/mm/dd ALREADY QUEUED (BLK XX OFFSET XX) ,6-73

6 Operations

NOT QUEUEING

Recovery Network will be queued with the same Job Library ID as the abnormally ended Network.
However, the operator can specify a different Job Library ID when issuing the Start Command (SCommand).
After the execution of the Recovery Network, the target Network is queued at the Job Library ID where
the Recovery Network was executed.
Please refer to “8.10 Test Run Function” for Job Library ID.

6-74

Operations of A-AUTO for UNIX/Windows

6.8

A-AUTO Monitor
Users can browse and manage the information of each A-AUTO Monitor in the System via A-AUTO Monitor
screen of A-AUTO/Web client. This function is available in v710 or later.

6.8.1

Monitor Detail
A-AUTO Monitor screen consists of “Monitor List” Windows and “Monitor Detail” Windows.

Click a Monitor ID link on the [Monitor List] Windows to display [Monitor Detail] Windows for the selected
A-AUTO Monitor.
The Agent ID that monitors the selected A-AUTO Monitor and its connection status are displayed in the[Monitor Detail] Windows.
The following operations are available via [Monitor Detail] Windows.

6-75

6 Operations

 Changing the Operating State (Running status)
The operator can Start/Stop the A-AUTO Monitor.
The operator can select either COLD start or WARM start when starting the A-AUTO Monitor.
 Update Parameter
The operator can reload the updated parameters and Monitor settings via [Monitor Detail] Windows.
Modifications on parameters and Monitor settings can be made via [Settings of Monitor] dialog of [System
Management] Windows.

 Change Operation Date
Operation Date can be changed via [Monitor Detail] Windows.
Select a date and click [Change Date].

In addition, the operator can browse and manage the following information of the A-AUTO Monitor. Select anitem from the select box on the toolbar and click [Execute].
 Executing Network Information
 Wait Network Information
 Resource Information
 Load Balance Information
 Abnormal End Information List
 Input Data Wait Information
 Timer Queue Information
 Network Check File Information List
 Schedule Confirmation (Finalized Daily Schedule) and Queuing Basic Schedule Setup
 Reschedule Setup Network Log List

Details of the above information and commands are explained in the following section.

6-76

Operations of A-AUTO for UNIX/Windows(1) Executing Network Information
Information on Networks that are currently running or executing is displayed.

The following items are displayed.
 NP Number
 NP Class NP and Executing Network Status Network ID
 Schedule Date JP Number JP Class OS Execute Class Job Name JP Status
 Job Start Time Process ID of execscr

6-77

6 Operations

The following dialogue is displayed by clicking the link of [NP Number].

The operator can issue the following commands from this dialogue.
 Hold NP or JP Release NP or JP
 Reset NP or JP Class (Change the class of NP or JP)
 Go Network
 Stop Network

Select the command to issue from “Type” select box.
Type in the necessary information and click [Apply].
Please refer to the “Operation Guide” for detailed information of each command.

6-78

Operations of A-AUTO for UNIX/Windows(2) Wait Network Information
Information on Networks that are in the Network Queue i.e. in waiting state is displayed.

The following items are displayed.
 Schedule Date Network Class Network ID
 Network Group ID
 Unreleased Execute Condition Hold Unreleased Execute Condition Wait
 Unreleased Execute Condition Start TimeThe following commands can be issued to a Network in the Network Queue.
 Hold Network Release Network

Select a target Network by clicking the check box of the Network ID. Then, select a command from the selectbox on the toolbar and click [Execute].
Please refer to the “Operation Guide” for detailed information of each command.
Also, users can select Networks that match the search (selection) criteria such as Network ID, Scheduled
Date, and/or Execute ID to be displayed on Wait Network Information. Type-in the search (selection) criteria
and click [Search].

6-79

6 Operations(3) Resource Information
If Resource Management Function is used, the operator can browse Resource Information.

The following items are displayed.
 Resource ID
 Resource name Maximum Number of Resource Network/Job Type Network ID
 Job Number Job ID
 Number of Resources Release Type Status
 Resource Setup Date Remaining Resource

6-80

Operations of A-AUTO for UNIX/Windows

The following dialogue is displayed by clicking the link of “Resource ID”.

The operator can issue the following commands from this dialogue.
 Manually Release Resource Resource Forced Release Cancel Resource Wait

Select the command and type in the necessary information, and click [Apply].
Please refer to the “Operation Guide” for detailed information of each command.

6-81

6 Operations(4) Load Balance Information
If Load Balance function is used, the operator can browse Load Balance Information.

The following items are displayed.
 System Qualifier Name
 Load Balancing Status Host Name (IP) (Class S) Port Number (Class S)
 APLINK (Class A)
 Remote OS (Class A)
 Information Retrieval Type Execute Wait Queue List
 CPU utilization

Users can turn ON/OFF the Load Balance function by selecting the check box of the System Qualifier Nameof target A-AUTO Monitor and then clicking [Edit] button on the toolbar i.e. Load Balance function can bedisabled or enabled.

6-82

Operations of A-AUTO for UNIX/Windows(5) Abnormal End Information
The operator can browse Information regarding abnormally ended Networks.

The following items are displayed.
 Scheduled Date Network ID
 Job ID
 Job Number Network Start Type Job End Status
 Job Return Code
 Job Start CPU Date Job End CPU Time Job status
 Job Execution User ID

6-83

6 Operations

The following dialogue is displayed by clicking the link of “Schedule Date” of a Network.

The operator can delete the record of abnormally ended Network using this dialogue.
Type in the necessary information and click [Apply].
To apply Free-On to the Network when the record is deleted, check “Free-On when Deleted”.
Please refer to the “Operation Guide” for detailed information of each command.

6-84

Operations of A-AUTO for UNIX/Windows(6) Data Wait Information
The operator can browse Data Wait Information of Networks with Input Data Wait attribute.

The following items are displayed.
 Network ID
 Network Status
 Data ID
 Data Comment Data Arrival Flag Data Arrival Date
 Data Arrival TimeThe following dialogue is displayed by clicking the link of “Data ID” of the target Network.
The operator can issue the following commands from this dialogue.
 Data Arrival Reset Data Arrival

6-85

6 Operations

Select which command to issue from “Type” select box.
 When Data Arrival is selected When Reset Data Arrival is selected

Type in the necessary information and click [Apply].
Please refer to the “Operation Guide” for detailed information of each command.

6-86

Operations of A-AUTO for UNIX/Windows(7) Timer Queue Information
The operator can browse information regarding Networks in wait state such as Input Data Wait and Start Timewait conditions.

The following items are displayed.
 Network ID
 Attribute Status
 Start Time Schedule Date

Confirmation dialogue is displayed if [Re-create Timer Queue] button on the toolbar is clicked.

The operator can recreate Timer Queue by clicking OK button in this dialogue.
Please refer to the “Operation Guide” for detailed information of each command.

6-87

6 Operations(8) Network Check File Information List
The operator can browse the content of Network Check File.

The following items are displayed.
 Network ID
 Last Queuing Schedule Date
 Last Operation Date
 Last Start Time
 Last End Time Monitoring On Attribute Return Code
 Status End

6-88

Operations of A-AUTO for UNIX/Windows

The following dialogue is displayed by clicking the link of “Network ID”.

The operator can issue the following commands from this dialogue.
 Delete the record of a Network in Network Check File Apply Free-On to the Network
 Apply Free-Off to the Network

Type in the necessary information and click [Apply].
Please refer to the “Operation Guide” for detailed information of each command.

6-89

6 Operations(9) Schedule Confirmation (Finalized Daily Schedule) andQueuing
The operator can execute Finalized Daily Schedule and Queuing from this window.

The following items are displayed.
 Agent ID
 Monitor ID

The following items may be defined for the command.
 Schedule Date
 System Qualifier Network Group ID
 Network ID
 Execution ID

Schedule Date is required when issuing the command.

6-90

Operations of A-AUTO for UNIX/Windows

After defining the necessary items, specify the target Network ID and Execution ID for Finalized Dailyschedule and Queuing processing as follows.
①

Blank line is displayed by clicking [Create] button.

②

Network ID. A generic Network ID may be specified by appending * (asterisk mark) to the end of theprefix Network ID.

③

Define the Execution ID. Specify the Execution ID by either typing in the value(s) or selecting from thedialogue displayed when the button on the right end column is clicked.

If you want to select several Execution IDs in [Execution ID] dialog, you can select the Execution IDs
while pressing “Ctrl” key. In the case of entering the Execution IDs manually, enter a comma to separate
each Execution ID.
* "0" classification can be specified in conjunction with other characters can not be classified.
"*" Classification to select all Execution IDs.

④

After specifying the Network IDs and Execution IDs, click [Execute] button on the toolbar.

⑤

Finalized Daily Schedule and Queuing are executed.

Please refer to “6.2 Finalized Schedule Function” and “6.4 Queuing” for detailed information on Finalized Daily
Schedule and Queuing.

6-91

6 Operations(10) Basic Schedule Setup
The operator can execute Basic Schedule.

The following items are displayed.
 Agent ID
 Monitor ID

The following items may be defined for the command.
 Schedule Date
 System Qualifier Network Group ID
 Network ID
 Execution ID

Agent ID and Monitor ID cannot be changed.
Schedule Date, Network ID and Execution ID are required when issuing the command.

6-92

Operations of A-AUTO for UNIX/Windows

After defining the necessary items, specify the target Network ID and Execution ID for Basic Schedule
processing.
①

Blank line is displayed by clicking [Create] button.

②

Type in the Network ID. A generic Network ID may be specified by appending * (asterisk mark) to theend of the prefix Network ID.

③

Define the Execution ID. Specify the Execution ID by either typing in the value(s) or selecting from thedialogue displayed when the button on the right end column is clicked.

If you want to select several Execution IDs in [Execution ID] dialog, you can select the Execution IDs
while pressing “Ctrl” key. In the case of entering the Execution IDs manually, enter a comma to separate
each Execution ID.
* "0" classification can be specified in conjunction with other characters can not be classified.
"*" Classification to select all Execution IDs④

After specifying the Network IDs and Execution IDs, click [Execute] button on the toolbar.

⑤

Basic Schedule processing is performed and Network Schedule is generated.

Please refer to “6.1.2 autosche utility” for information regarding Basic Schedule.

6-93

6 Operations(11) Reschedule
The operator can “Reschedule” (re-create) the Network Schedule from this Windows.

The following items are displayed.
 Agent ID
 Monitor ID

The following items may be defined for the command.
 Schedule Date
 System Qualifier Network Group ID
 Network ID
 Execution ID

Agent ID and Monitor ID cannot be changed.
Schedule Date, Network ID and Execution ID are required when issuing the command.

6-94

Operations of A-AUTO for UNIX/Windows

After defining the necessary items, specify the target Network ID and Execution ID for Reschedule processing.
①

Blank line is displayed by clicking [Create] button.

②

Type in the Network ID. A generic Network ID may be specified by appending * (asterisk mark) to theend of the prefix Network ID.

③

Define the Execution ID. Specify the Execution ID by either typing in the value(s) or selecting from thedialogue displayed when the button on the right end column is clicked.

If you want to select several Execution IDs in [Execution ID] dialog, you can select the Execution IDs
while pressing “Ctrl” key. In the case of entering the Execution IDs manually, enter a comma to separate
each Execution ID.
* "0" classification can be specified in conjunction with other characters can not be classified.
"*" Classification to select all Execution IDs④

After specifying the Network IDs and Execution IDs, click [Execute] button on the toolbar.

⑤

Reschedule is executed and Network Schedule is re-generated.

Please refer to “6.1.4 remakesche utility” for information regarding Reschedule.

6-95

6 Operations(12) Network Log Information List
The operator can browse the content of Network Log file.

The following items are displayed.
 Network ID
 Job ID
 Job end status
 Job end code OS Execute Class Execute Type Start Date
 CPU time when the Job started
 CPU time when the Job ended
 Job Execution Time CPU Time Schedule Date Job Library ID
 Job Execution User ID

Backup file of Network Log is created by Automatic Backup function at the timing when log file size reaches
the value specified by the System Parameter, MCP_MAXNWKLOG. This is called Long-term Storage functionof Network Log. Whether to use this function is defined by parameter, AUTO_JOBLOGBACKUP_USE.
Parameters can be modified via “Settings of Monitor” screen of [System Management] of A-AUTO/Web client.

6-96

7. Application Monitor

7 Application Monitor
7.1

Monitor Condition
Before you begin monitoring applications (Networks) using A-AUTO/Web client, you need to set the criteria
or conditions for selecting the applications (Networks) which you want to monitor first. This is called
Monitor Condtion.
Only Networks which match all of the conditions specified in the Monitor Condition will be displayed in the
Windows.

7.1.1

Monitor Condition Setting(1) Create a new application monitor
Click [Create] button on toolbar of “Application Monitor” pane of A-AUTO Main Windows. The [Settings]
dialog of “Application Monitor” Windows will be displayed. Please define the necessary items here.
(For more details of items, please refer to “Monitor Condition Item” and “3.1 Network Master”, “3.7
Schedule Master”.)

Click [Apply] button to save the Monitor Condition and display “Application Monitor” Windows which meetsthe Monitor Condition.

(2) Use existing monitor condition
Click an Application Monitor Setting Name in the "User-defined Setting" list or "Common Setting" list of“Application Monitor” pane of A-AUTO Main Windows. The selected “Application Monitor” Windows is
displayed. If you want to modify the existing Monitor Condition, Click[Settings] icon from toolbar of[Network Monitoring] pane, “Settings” dialog will be displayed. You can modify Monitor Condition
accordingly and click [Apply] button to save the changes to Monitor Condition.

7-1

7. Application Monitor

7.1.2

Monitor Condition Item
The following are the items in Monitor Condition.

(1) Basic Settings
Set basic settings for Monitor Condition. Set the following items.

① Application Monitor Setting Name
This is an identifier of the Monitor Condition for the Application Monitor. Up to 64 characters can be
specified.

② Save asSpecify whether to save the setting as user-defined (only available to the user who registered the setting)or common setting (available to all users).

③ Default Display Style
Select the default display style from the following options.
 List Chart Time Chart④ Close the alert dialogue automatically
Select whether to automatically close the Alert dialog after it is displayed.

If user does not check thecheck box, the dialog will not be closed automatically.

⑤ Close afterIf you select “Close the alert dialogue automatically”, specify the elapsed time after the dialog display toclose it.

⑥ Watch List
Set the types of exception to be monitored.
 Abend Start Delay End Delay T-Delay(2) Agent
Select the Agent(s) which you want to monitor. (Multiple Agents can be specified)

7-2

7. Application Monitor(3) Monitor ID
Specify the Monitor ID of A-AUTO Monitor which you want to monitor. (Multiple Monitor IDs can be
specified)
The client will monitor and control the Networks of Monitor ID that you specified. A generic Monitor ID may
be specified by appending * (asterisk mark) to the end of the prefix Monitor ID.

(4) Network
Specify the Network ID of the Network which you want to monitor. (Multiple Network IDs can be specified)A generic Network ID may be specified by appending * (asterisk mark) to the end of the prefix Network ID.

(5) Process Cycle
Select the Process Cycle which you want to monitor from the following options. Networks with the specified
Process Cycle will be selected for monitoring. (Multiple options can be selected)
 Daily Weekly Every 10 days
 Monthly Semiannually Annual Bimonthly
 Quarterly Every 4 months
 NoneThese Process Cycles are the same as Process Cycles defined for a Schedule Pattern in Network
Schedule Master.

(6) Execution ID
Specify the Execution ID which you want to monitor. Networks with the specified Execution ID will beselected for monitoring. (Multiple Execution IDs can be specified)This Execution ID is the same as Execution ID defined for a Network Schedule in Network Schedule
Master.

7-3

7. Application Monitor(7) Attribute
Select the Network Attribute which you want to monitor from the following options. Networks with thespecified attribute will be selected for monitoring. (Multiple options can be selected)
 Hold Input Data Wait
 Time Wait
 Parameter Run
 Monitor On Wait
 Parameter No Attribute
All of these attributes (except for "No Attribute") are the attributes that can be defined for a Network in
Network Master. To monitor those Networks that have no attribute defined, please choose "No Attribute".

(8) ClassSpecify the Class which you want to monitor. Networks with the specified Network Class will be selected formonitoring. (Multiple Classes can be specified)This Class is the same as the Network Class defined for a Network in Network Master.

(9) Job Status
Select the Network Status which you want to monitor from the following options. Networks with thespecified status will be selected for monitoring. (Multiple options can be selected)
 Schedule Queuing Canceled in Queue
 Running Normal End
 Free On Abend Not Scheduled
If you want to monitor the status of other than those listed above, select the "Not Scheduled".

7-4

7. Application Monitor

7.2

7.2.1

Event Monitor

Work Monitor List Page
Execution status of Works will be displayed "Work Monitor List" pane.
"Work Monitor List" pane will be displayed by clicking "Work" on [List Menu] of Application Monitor
Windows.

"Work Monitor List" pane will be automatcially refreshed at intervals, according to the interval time definedby the user.
Set "Interval to Auto Update Monitor" in [User Settings] dialog.
About User Settings, please refer to "4.2 User Settings".

(1) Operation of Work Monitor List Pane
Update Status :Set whether to enable or disable the monitoring of the Work ID.
(Please refer to "7.2.6 Update the Status of Work (Valid/Invalid)".)Delete:Delete the completion information regarding the Work.
（Please refer to "7.2.7 Delete Completion Information".）

7-5

7. Application Monitor(2) Display items of Work Monitor List Window
Work ID
Display Work ID of the Work.
“Work Monitor Detail List” dialog will be displayed by clicking a Work ID.

Comment
Comment for work.

WatchIndicates whether or not the Work is currently being monitored by A-AUTO/Event, Valid or
Invalid.



Number of completion
A-AUTO/Event considers a work has completed when all the events that are defined in the work
have occurred. This displays how many times the Work has completed since A-AUTO/Event has
started monitoring.
(Figure 9-1①)



Event Achievement Rate
Indicates the rate of event achievement, which is ratio of events that have actually occurred out of
events defined in the Work. The rate is displayed in both graph and fraction formats ("Number of
events that occurred/Number of Events registered for the Work").
(Figure9-1②)② Achievement rate1/2
Event1

Event2
2

WorkFirst complete①

Second complete

Complete times 2

Figure 9-1 Event Achievement Rate and Number of Completion
Note
Whenever a Work is updated from disable to enable and vice versa or AUTO/Event Server is shutdown,
the “Number of Completion” will be reset to 0.

7-6

7. Application Monitor

7.2.2

Work Monitor Detail List Dialog
The following information will be displayed in this dialog.



Execution Information
Display the status of each event in the Work that is currently being monitored i.e. whether the event
has occurred, error in processing the event or the date and time the event occurred. (Figure9-2 ①)Competition Information
This displays the log records of events in the Work, each time the Work is completed either
successfully or not successfully. The information displayed includes the date and time the Work wascompleted and the date and time the event in the Work occurred.. Information is displayed in the orderof latest to earliest date and time of completion. (Figure 9-2 ②)

Execution and Completion information of a Work can be displayed by clicking the target Work ID in"Work Monitor List" pane.

7-7

7. Application Monitor(1) Display items of Execution Information
When a Work is being monitored i.e. Watch is “Valid”, the following items will be displayed.
Work IDWork ID of the target Work that is currently being monitored"Edit Work information" dialog will be displayed by clicking the Work ID.

StatusIn Process: Work is in process.

Event ID
Event ID of the event in this Work. The icon on the right of the Event ID indicates the current status of
the event. The icon representations are as follows.
Have yet to happen
Applying: This event has not occurred yet.

: This event is now being applied to the target Agent which is to monitor thisevent.

Failed to Apply: Failed to apply this event to the target Agent.
Please check the status of the agent which is to monitor this event.

Normal End : This event has occurred.
Occurrence Time
Display date and time the event occurred.

7-8

7. Application Monitor(2) Completion Information
The following information will not be available for display if the Completion information is removed ordeleted.


Work IDWork ID of the target Work. The icon on the right of the Work ID indicates the status of the Work.
"Detail Work information" dialog will be displayed by clicking the Work ID. The icon representations
are as follows.
Action Failure:

The Work has completed but an error has occurred while applying to
the target Agent which is to execute the Action. Please check thestatus of the target Agent.

Applying:

Work has completed but execution of action was pending in the target
Agent.



Normal End:

This work has completed and actions have been performed.

Cancel:The monitoring of this Work has been canceled.

End Date
Displays the time when work was completed.



Event ID
The event ID of Event defined in this Work. The icon on the right of the Event ID indicates the statusof the Event. The icon representations are as follows.
Normal End :This event has occurred.

CancelThe monitoring of this event has been canceled.

:"Event Detail" dialog will be displayed by clicking the event ID.
(About "Event Detail", please refer to "7.2.3 Event Detail Windows".)Occurrence Time
Display the time the event occurred.

7-9

7. Application Monitor

Event1
8:20

Event2
2

8:40

9:00

12:00

12:20

13:00

13:30

Unoccured

8:20

Work
9:00

Running

12:00(1) completion information(2) Execution Status

Figure 9-2 End time of Work and Start time of Event*Below is an example of "Detail Work Information" dialog.

"Action Detail" dialog will be displayed by clicking the Action ID.
(About " Action Detail ", please refer to "7.2.4 Action Detail Windows".)

7-10

7. Application Monitor

7.2.3

Event Detail Windows
This dialog provides the detailed information about the "event" which has occurred.
Click an event ID displayed on the [Completion Information] tab of "Work Monitor Detail List" dialog.
" Event Detail" will be displayed.

7-11

7. Application Monitor■ Display Item of Event Detail Window

Event ID
Display the event ID of the selected event.



Comment
To display the comments of this event data.



Event Type
Display the type of event that occurred.



Event Occurring Computer Name
Display the name of the agent where this event occurred.



Event Detail
Display information for the detection of this event.

Event Detection Parameter
Display the additional information used to identify the event in addition to the information for event
detection.

Occurrence Date
Display the date when this event occurred.

Occurrence Time
Display the time when this event occurred.



Event Occurrence Information
Display the information received by A-AUTO/Event when this event occurred.

For more information about the item, please refer to the "3.10 Event Management Master".
Depending on type of Event, Event Occurrence Information is different as shown in the table below.
Event Type

WindowsNT

UNIX

Job Event－－Message Event

File Event

Application Event

Full-text messages that are output

Full-text messages that are output

detailed description of the application log

ex. ARB001I

of Event Viewer

INITIALIZE SUCCESSFULLY

Generated file name, updated file name

Generated file name, updated file nameex. F:

ex. /home/ABC/test/hp8701\Docs\note\note.doc

Identifier of application

7-12

ARWCHSRV

Identifier of application

7. Application Monitor

7.2.4

Action Detail Windows
This dialog provides the detailed information about the Action ID that is selected.
"Action Detail" window will be displayed by clicking an Action ID on "Edit Work Information" dialog or "DetailWork Information".

7-13

7. Application Monitor■ Display Items of Action Detail Window

Action ID
Display the action ID that you selected.

Comment
Display the comment of this action.

Action Type
Display the type of action that occurred.

Action Executing Computer Name
Display the name of the agent that executed this action.

Action Execution Information
Display the information that was used to perform this action.

Action execution parameter
Display the additional information that was used to execute the action.

For more information about the items, please refer to the "3.10 Event Management Master".

7-14

7. Application Monitor

7.2.5

Change the Monitor Condition of Running "Work"
Click a Work ID of a Work that is being monitored in "Execution Information" tab of "Work Monitor DetailList".
"Edit Work Information" window is displayed.

The content is changed when you click [Apply] button.

7-15

7. Application Monitor

The items that can be changed in [Edit Work Information]
Item Name

UpdateContent

or NotWork ID-

ID of work data

Comment-

Comments about the work data

Start Time○Time to start the event detection by A-AUTO/Event

End time○

Time to end the event detection by A-AUTO/Event

Action Execution○

Define whether or not to execute the Action when the Event occurs
Yes:

When the "work" is completed, execute the "action".

No:

When the "work" is completed, do not execute the"action".

Action Execution Pattern○

Specifies whether you want to execute the "action" for eachcompletion of the Work, or whether to execute only at the firstcompletion of the Work.
Every

:

Execute the "Action" specified for each time theWork is completed.

First time

: Execute the "action" only on the first completion of
the Work. Action ID displays a list of actions to
execute after the Work is completed.

Action ID-

A list of IDs of the actions to be executed when the Work
completes.
When you click on an action ID, the screen "Action Detail" will be
displayed. (refer to "Action Detail Windows")

NoteThis change is effective only for the duration of the monitoring while the Work is enabled. Whenever a
Work is updated from disable to enable and vice versa or AUTO/Event Server is shutdown, the informationof the Work registered in Event Management Master will be used.

7-16

7. Application Monitor

7.2.6

Update the Status of Work (Valid/Invalid)-Use the [Update] button (toggle switch) to enable or disable the monitoring of a Work.
Check Work ID check box of the target Work that you want to enable or disable on "Work Monitor List"
pane.
Click "Update Status" button on toolbar.
A confirmation message is displayed.
When you click the [OK] button, the status will be changed.

The display on the list is updated to show the change.
Note
If a Work is change from “Valid” to “Invalid”, the progress information about the work will no longer be
updated.
For a Work that has no Event defined, you cannot update it to "Valid".
When A-AUTO/Event Server is stopped, the original settings in the Event Management Master will be
used when the server is next started. For permanent changes, please change settings in EventManagement Master.

7-17

7. Application Monitor

7.2.7

Delete Completion Information[Delete] button will delete all the completion information, up to the time when delete is requested,regardless of the completion information displayed on the dialog.
Check the Work ID check box of the target Work that you want to delete the completion information on"Work Monitor List" pane.
Click [Delete] button on the toolbar.
A confirmation message is displayed.
Completion information is deleted when you click [OK] button.

Note
Information once removed cannot be recovered.

7-18

7. Application Monitor

7.3

Application Monitor, Application Monitor Flowchart, Application Monitor Time
Chart
After you have created a new Monitor Condition or when you open an existing Monitoring Condition(Application Monitor Setting Name), information of Networks that meet the defined conditions is transferredfrom A-AUTO Server to A-AUTO/Web Client and displayed in Application Monitor Windows. You may
choose one of these formats to display this information; Network Monitoring List, Network Monitoring Chartor Network Monitoring Time Chart

Click the link on [List Menu] on the left side of the Windows to select the format of display.

7-19

7. Application Monitor

7.3.1

Application Monitor
Application Monitor is a Windows that displays the list of Networks and their execution statuses.
The items to display and the order to display them can be customized accordingly to suit the preferences ofindividual users.
For customization of display items, please refer to the "4.1.5 A-AUTO/Web Client Function".

7-20

7. Application Monitor

The following items can be displayed in Application Monitor.
Schedule Date

Total Job

Start Time Wait*

User Field

Status *Number of Preceding Network Hold Code *Duplicate Key

Attribute

Estimate Process Time

Priority *Holiday ID

Execution ID

Monitor ID *Network Partition *Reference Date ID

Class *

System Qualifier *Estimate End Date

Process Pattern

Estimate Start Time

Estimate Start Date

Estimate End Time

Shift CodeActual Start Time*

Actual Start Date *Setup Time

Standard Processing
Date

Actual End Time*

Actual End Date *Process Cycle

Scheduled Day of
Week

Agent Name

Unmet Execution Attribute*

Job Library ID

Actual processingtime*

Job Execution User ID

Network Max Executing Time

Response To Max
Time* Information items is reflected performance■Status of Network
In A-AUTO system, a Network can be in one of the following execution statuses.
 Network that is scheduled.
 Network that is “In Queue”.
 Network that has been canceled in the queue.
 Network that is currently running in A-AUTO Monitor.
 Normally ended Network.
 Network that is Freed On.
 Abnormally ended Network.
Note
Estimate Start Time and Estimate End Time that are displayed on the Application Monitor are taken from
Sub-Schedule Master. They are not the simulated timings of simulation function. Therefore, sometimes
Estimate Start Time/Estimate End Time displayed on the Application Monitor do not match Estimate Start
Time/Estimate End Time displayed on Time Chart Simulation.

7-21

7. Application Monitor

7.3.2

Application Monitor Flowchart[Network Monitoring Chart] pane displays selected Networks in the form of a flowchart.
The display provides you with a view of preceding / succeeding relations among Networks at a glance.

Click << at the right end of "Network Monitoring List" pane to expand "Area Search" pane.

“Area Search” Window
Enter the Network ID of a Network, which you want to locateand display on the flowchart, in the textbox and click [Search]
icon.
Use the arrows on the toolbar to scroll the flowchart display
vertically or horizontally.
Use your mouse to drag the cursor to position the display
range of the flowchart.

7-22

7. Application Monitor(1) Status of Network
A Network is displayed in one of the following colors to represent its status or type.
Network

Status・Type

NET001

Scheduled

NET001In Queue

NET001

Cancelled

NET001

Running

NET001

Normally ended

NET001

Freed On

NET001

Abnormally ended

NET001

Not Scheduled Preceding

XXX

Display restriction

7-23

7. Application Monitor(2) Not Scheduled Preceding Network
A preceding network that falls under any of the following conditions is displayed in gray.
 A Network is scheduled but its preceding Network is not scheduled on the schedule date that is
specified in “Display Period” of [Network Monitor Menu] dialog.
 The Network is selected by the Monitor Condition but its preceding Network does not meet theconditions and is not selected..
Such a preceding Network is called Not Schedule Preceding Network.
(Example)
Below is an example of Networks with relationship and different Schedule Patterns.


For GYOUMU03 and GYOUMU01, their executions are to be performed every day

For GYOUMU02, its execution is performed on 10th day of each month
GYOUMU01
GYOUMU03
GYOUMU02

For 10th of the month display, GYOUMU02 will be displayed in gray in the flowchart.

7-24

7. Application Monitor(3) Network with display restriction
A preceding network that falls under the following condition is displayed in black.


A Network belongs to a group but it has a preceding Network that does not belong to the group.
When selection for display is by group, the display is limited to only Networks in the group.

(Example)
Below is an example of Networks with relationship but do not belong to the same group.


GYOUMU06 and GYOUMU04 belong to the group "GRP_A" but GYOUMU05 does not belong to“GRP_A”.



Select the "GRP_A" to be displayed on [Network Monitoring List Chart] pane.
GYOUMU04
GYOUMU06
GYOUMU05"GRP_A" may be selected from “Network Group” on [Network Monitor Menu] dialog.

(4) Attribute display
Attributes that are defined for a Network will be displayed as follows.
Network

Status・Type
Attribute display

Branch job*
*When you define Job Branching Function for Jobs in a Network, the settings will be displayed.
Note
Network has been revoked at the time of monitoring, will be treated as canceled.

7-25

7. Application Monitor(5) Display Settings
When you select a specific network in the flowchart, the following menu is displayed. Select one of thedisplay options in the menu that appears, you can display various information of the selected network.

・For information about Monitor commands, please refer to the "7.8 Monitor Commands".

・"Display Both Preceding and Subsequent", "Display Subsequent Only", "Display Preceding Only"
These options in the pop-up menu allows you to select a target Network and display its preceding
and succeeding flow only, its succeeding flow only or its preceding flow only repectively. All otherunrelated Networks in the flowchart will be suppressed and not displayed. Click a Network to select itas the target Network and then select one of these options in the pop-up menu.

・

Display all the Networks This option in the pop-up menu allows you to return to display all Networks inflowchart after a change in the display.

・“Display ON when outside the condition”, ” Display OFF when outside the condition”
You can choose to show / hide the Preceding Network of outside conditions set by setting "Settings".

・“Go to Preceding Network” Selecting this option will display the Preceding Network(s) of the target
Network. When you select a Preceding Network name, the display in the flowchart will shift accordingly
to position the selected Preceding Network as the focus. This option is available in A-AUTO
V710Lv17-2.

・“Go to Subsequent Network” Selecting this option will display the Succeeding Network(s) of the target
Network. When you select a Succeeding Network name, the display in the flowchart will shiftaccordingly to position the selected Succeeding Network as the focus. This option is available in
A-AUTO V710Lv17-2.

7-26

7. Application Monitor

7.3.3

Application Monitor Time Chart
To view the results of the Time Simulation. (Please refer to "7.6 Time Simulation")

7-27

7. Application Monitor

7.3.4

Network Monitor Menu
On the toolbar of "Network Monitoring List" pane of the Application Monitor Windows, click "Menu" icon and"Network Monitor Menu" dialog will be displayed.

(1) Display Period
Enter a Schedule Date or Schedule Period (range) and then click the "Display" button, Networks for the
relevant period will be displayed on the "Network Monitoring List" pane.
Note
For [Network Monitoring List] pane, you can specify a schedule period.For [Network Monitoring List Chart]
pane or [Network Monitoring List Time Chart] pane, you can specify only a specific schedule date.

(2) Network GroupA list of available Network Groups is displayed.
When you click on the link of a Group ID, only Networks that belong to the selected Group will be displayedon "Network Monitoring List" screen.

(3) File Transfer
Select the "File Transfer" in the select box on the toolbar and then click the "Execute" button. Dialog will be
displayed for you to run the File Transfer. For file transfer, please refer to "7.5 File Transfer".

7-28

7. Application Monitor(4) Queuing
Select the "Queuing" in the select box on the toolbar and then click the "Execute" button. Dialog will be
displayed for you to run the Queuing. For file transfer, please refer to "6.4 Queuing".

(5) Delete the monitoring records
This option will delete information of all completed Networks regardless of the number of completed
Networks currently being displayed.
Select the "Delete Record" in the select box on the toolbar and then click the "Execute" button.
Confirmation Message will be displayed. If you click the [OK] button, all monitoring records will be deleted.

7-29

7. Application Monitor

7.3.5

Network Monitoring Search
For [Network Monitoring List] pane or [Network Monitoring List Time Chart] pane, you can select Networks
for the display using Search function.
Click [Search] iconon the toolbar of "Network Monitoring List", "Network Monitoring-Search" dialog

will be displayed. Enter the search condition, please click on the "Search" button. If you do not specify any
search condition, all Networks will be selected for display on the list screen.
If you want to reset all the values you have entered, please click the “Clear” button.

The list screen will display only Networks that meet the search criteria (AND conditions are applied).
Search string is sensitive to uppercase and lowercase specifications.
The wildcards ("*"."?") can be also used in search string. When no wildcard is specified, Search will lookfor exact match.
The following sections describe each input item on the screen.

①

Network ID
Specify the network ID.

②

Hold CodeYou can choose Networks with a particular Hold code for display.
Hold Code that can be selected is one of the following; blank, 1 ~ 9, A ~ Z.
If you select a blank, all Networks will be selected.

③

Expanded Name
Networks with the specified Expanded Name will be displayed.

④

System Qualifier
Specify the System Qualifier.

⑤

Class
7-30

7. Application Monitor

You can choose a specific class.
Class can be 0 to 9 or A ~ Z.

⑥

Priority
You can choose a specific Priority.
Priority can be from 01 to 15 or blank.
If you select a blank, all Networks will be selected.

⑦

Start Time
Specifying Start Time will select Networks with Start Time attribute that falls within the range of Start Time
(From) ~ Start Time (To)for display. If the value of 00: 00 is specified for both Start Time (From) andStart Time (To), all Networks will be selected.
*If you specify a time 00:00 for Start Time (From), Networks with no Start Time attribute will also be
selected.

⑧

Job Status
You can choose Networks with a specific execution status for display.
If you select a blank, all Networks will be selected.
The statuses available for selection are as follows.
Blank (do not specify): All Networks to be selected regardless of status

Schedule: The Network whose status is "Scheduled"

Queuing: The Network whose status is "In Queue"

Canceled in Queue : The Network whose status is "Canceled in Queue"⑨

Running: The Network whose status is "Running"

Normal End: The Network whose status is "Normally Ended"

Free-On: The Network whose status is "Abend

: The Network whose status is "Abnormally Ended"

Freed On"

Network Group ID
Only Networks belonging to the specified group ID will be selected for display.

⑩

Job Executing User ID
Only Network with the specified Job Executing User ID will be selected for display.
Note
Search function is not available for [Network Monitoring List Chart] pane. If you run a search on the
flowchart Windows, the screen display switches to the [Network Monitoring List] screen and the search
result will be displayed.

7-31

7. Application Monitor

7.4

Monitor Detail Information
For Networks displayed on [Network Monitoring List] pane, [Network Monitoring List Chart] pane and[Network Monitoring List Time Chart] pane, you can display Network information in more detail as follows.
 Detailed Network Info :Detailed information of Network Detailed Job Info

Detailed information of the Job(s) defined for the Network:(1) Detailed Network Info

Select a Network ID in "Network Precedence Relationship" and click the appropriate arrow icon, thedetailed information of the selected preceding or succeeding Network ID will be displayed on the“Registered Information” textbox. The display on [Network Monitoring List] pane or [Network Monitoring List
Chart] pane will shift accordingly to position the selected preceding or succeeding Network as the focus.

7-32

7. Application Monitor(2) Detailed Job Info
Display the Job(s) of the Network in list format.

Click “Switch” icon, Jobs in the Network will be displayed in flowchart format.

7-33

7. Application Monitor① About Log Information
Display of log information, on the main frame, the status of the job network is displayed only when runningor abnormal end. In addition, UNIX, Windows, the status of the Network is running the network, and then
only in case of successful and unsuccessful. (Job status are excluded)
Table Job Status and Log Information
Job Status

Item
UnexecutedRunning

Job Status○○

End Status×

End Code

AbnormalEnd

Unknown

○

○

○

×

○

○

×

×

×

×

∆

×

Aborted Step *2

×

×

×

∆

×

OS-JOB Number *2 *3

×

∆

○

○

×

Start Date

×

○

○

○

×

Start Time

×

○

○

○

×

End Date

×

×

○

○

×

End Time

×

×

○

○

×

○:
∆:

Normal End(Gray)

Display ×: Hidden
Hidden by case (Different depending on the type ofabnormal end)
If you are using the A-REMOTE , the display of OS-JOB number of jobs that are running on a remote monitor
does not take place.

※1※2

Under XSP are not always visible.

※3

Under the UNIX environment, and "UNIX" always, under Windows, it displays "WINDOWS" always.

② About the color of the box for the job
A Job is displayed in the flowchart format in one of the following colors to represent its status.
Job Status

Display Color

Unexecuted Job

It is the same color as “In Queue” Network

Running Job

It is the same color as Running Network

Normally Ended Job

It is the same color as Normally Ended Network

Abnormally Ended

It is the same color as Abnormally Ended Network

Job
Unknown Status Job

It is the same color as Unknown Status Network

It should be noted, will be displayed in same color as the following cases, regardless of the status of thejob network, that are outside the conditions set for the job network.
 When the server does not monitor the Agent About Abnormally Ended Network, when the state of the job can not get on the Agent side.
(Get the progress of Job from Check Point File , Abnormally Ended Network File of A-AUTO)

7-34

7. Application Monitor

7.4.1

Job Log Display* Not available in XSPYou can display the Job Log. which is composite of Running Network and Abnormally Ended Network.
“Job Log” dialog will be displayed by clicking [View Job Log] of “Detail Job Info” window.

Reference
If you want to display Job Log, you must filfull the following requirements.
Mainframe

Jobs are executed by A-AUTO for Mainframe*.
* Not available in XSP A-LOG interface that has been defined.


A-LOG (V3.8) must be running in the same server as the agent.

Job logs of Jobs must be stored in the A-LOG.

UNIX/Windows The Job Log function is set ON to collect Job logs.
 Set NJP_JOBLOGON to 1.
 You have correctly specified the job log storage directory NJP_JOBLOGDIR.
Parameters can be changed in "Settings of Monitor" Windows of System Management. Please refer to"9.3.1 Settings of Monitor".

7-35

7. Application Monitor

7.4.2

Show Script
You can display the batch file or script shell of a Job using the "Network Monitor" dialog and the "Network
Definition" Windows. Show Script is available for only jobs that are to be executed under the A-AUTO
Monitor and not available for Jobs to be executed under the remote.
This function is available from V710.
“Script” dialog will be displayed by clicking [Show Script] button of “Detailed Job Info” dialog.

Refer to Show Script function of the “Network Definition” in "5.1.8 Show Script".

7-36

7. Application Monitor

7.5

File Transfer

By performing the file transfer, information of
Networks in A-AUTO for UNIX / Windows ® or
A-AUTO for Mainframe is transferred and written to
the files on A-AUTO Server. Information of Networks
in A-AUTO Server is then made available to
A-AUTO/Web clients that perform monitoring of
applications.
File transfer is done by specifying a date range andExecution

ID

classification.(1)MethodofFileTransfer
You can perform the File Transfer using "File Transfer Request" dialog.
You can display "File Transfer Request" dialog by the following steps.
 Select the "File Transfer" from [List Menu] of System Management Windows to open the "File Transfer
Log List" dialog. "File Transfer Request" dialog will be displayed by clicking "File Transfer" button.
 Click "Menu" icon on the toolbar that is located on [Network Monitoring List] pane. "Network Monitoring
Menu" will be displayed. Select “File Transfer” from the select box on toolbar and click “Execute” button,"File Transfer Log List" will be opened. “File Transfer Request” dialog will be displayed by clicking “FileTransfer” button.

Specify Execution ID and Schedule Date, and then click “Execute” button.
File Transfer is performed to trnasfer Networks that meet the specified Execution ID and Schedule Date(s).

7-37

7. Application Monitor

Reference
 You can automate File Transfer operation by setting “automatically issue a menu command” in System
Management Windows.(Refer to “9.1.2 Setting Automated Issuing Menu Command”)
 The following function(s) are performed for "Start Monitoring" and "File Transfer" operations.
[Start Monitoring]:

File Transfer＋Starting Monitoring[File Transfer]:

Only transfer files

Therefore, these menu commands will be used for the following two cases.
1.

After starting Server, select [Start Monitoring].

2.

Subsequently, select [File Transfer].

(2) Timing to File Transfer
 When you start the server
 If you want to change the Schedule Date or/and Execution ID which you are currently monitoring

Note In order to perform file transfer, you must be connected to the agent.
Perform connect to Agent using "Agent List" pane of System Management.
 Please note that for the following cases, the file transfer is not performed.
・You have requested a file transfer to an agent that is currently processing a file transfer.
・You have requested a file transfer to an agent that is currently processing a Time Simulation.

7-38

7. Application Monitor(3) Support for operations to All Agents
For any of the four operations of "End Monitoring", "File Transfer", "Start Monitoring" and"Connection to the Agent" that can be performed from the Web client, you can request for the operation
to be performed to all agents at the same time. .
On the dialog of any of these operations, you can select an individual agent or “All” in [Agent Name] selectbox. Select "All" to request for the operation to be performed to all agents.
When an operation is requested for all agents, whether the operation is performed for each agent depends
on the session status of the agent.
Type of operation to All

Session Status of Agent at the time of “All agent” operation

AgentsConnection to Agent

Perform on only agents with Session Status of “disconnect”

Start Monitoring

Perform on only agents with Session Status of “connect”

File Transfer

Perform on only agents with Session Status of “connect” or“Monitoring”

End Monitoring

Perform on only agents with Session Status of “Monitoring”

7-39

7. Application Monitor

7.7

Alert
This feature provides a function to display an alert in the [Alert] dialog whenever a network terminates
abnormally, the execution of a network has been delayed, or the processing duration of a Network has
exceeded the maximum processing time (Max Executing Time attribute) defined for the Network. The Alertdialog shows information about the Network and its processing.
Delay setting for a Network is done during th registration of the Network. For information on how to
configure, please refer to the "3.1.2 Items to Define".
In the case of Mainframe Connection mode, delay setting is defined in the parameter file, PARMDELY.
Please refer to Chapter 6 A-SUPERVISION Support Tools of Operation Guide for information on Network
Delay Monitor utility.
*Mainframe Connection mode does not support the monitoring for the maximum processing time (Max
Executing Time attribute) of a Network.

Ways to show Alert List
In the event of abnormal termination of a Network or a delay in processing of a network, Alert List dialog is
automatically displayed. Alternatively, you can click icon

on each type of Application Monitor Windows,[Alert List] dialog will be displayed.

On [Alert List] dialog, click a network ID of the target Alert. One of the [Alert] dialogs described below will
be displayed. After verifying the details of an Alert, you can remove or delete the Alert.To delete, check thebox of the Network ID of the target Alert to be deleted and click the [Delete] button. If you check the checkbox at the top, you can select and delete all the alerts.

7-45

7. Application Monitor

The following four types of [Alert] dialog.
 Alert when there is an abnormally ended Network Alert when there is a delay in the starting of a network Alert when there is a delay in the ending of the execution of a network* End Delay exception will not happen if the status of a Network is [Normally Ended] or [Free On].
 Alert when the processing duration of a network has exceeded the maximum processing time(MaxExecuting Time attribute).

(1) Abnormally ended Network

7-46

7. Application Monitor(2) Start Delayed Network(3) End Delayed Network

7-47

7. Application Monitor(4) Network that has exceeded the maximum processing
time

7.7.1

Alert Setting
For these three types of alerts, you can define whether a pop-up dialog is to be displayed, whether tosound an alarm whenever an Alert is displayed as well as to set the display time.
[Server Settings] pane of System Management Windows allows you to set the presence or absence of awarning sound at the time of alert notification.
(For information on how to configure, see "9.2 Management of Server Information")
The "basic setting" tab of "Settings" dialog allows you to set whether the different Alert dialogs are to be
displayed and the time duration a dialog will remain displayed. (For information on how to configure, see"7.1 Monitor Condition")

7.7.2

Alert Log
Information about alerts that have been reported to the client is logged in the Alert Log file.
You can view this Alert Log file to check for alerts that have been reported.
For information on how to set up the alert log, about obtaining the Alert Log, please refer to "9.2Management of Server Information".

7-48

7. Application Monitor

Note
Recording in the alert log file is done only if you set “on” the recording option of the alert log.

7.8

Monitor Commands
You can issue the Monitor commands for the A-AUTO monitor from A-AUTO/Web Client.
Note

7.8.1



Types of commands that the user can issue depends on user privileges.

Commands can be issued to only A-AUTO Monitor that is connected to agent.

List of commands
The command can be issued from the client are as follows.
Table List of commands that can be issued from the client

Command Explaination

Form when it is issued to the A-AUTO Monitor

A

Release Network

A Network Name, SDATE=yymmdd

Release Queue

A｛Q/E｝

Cancel Network

C Network Name, SDATE=yymmdd

C,[{C/W/F},FREE={Y/N}]E

Modify the attribute of

E Network Name, SDATE=yymmdd

Network(Reset)[,{TIME=hhmm/I=N/PRTY=priority /CLASS=class/JOBLIB=Job Library ID}]

ESYS

Modify System Qualifier

ESYS,SYSQ= System Qualifier Name,

Name(*)
Modify System Qualifier

NEWP={*/ANY/Monitor id}
ESYS,NET= Network Name,

Name(Network)(*){NEWQ= System Qualifier Name /NEWP={*/ANY/Monitor id}}

Modify Job Library ID

ESYS,JOBLIB=Job Library ID

FFree On Network/OFFF Network Name, SDATE=yymmdd,{ON/OFF}H

Hold Network

H Network Name, SDATE=yymmdd

Hold Queue

H{Q/E}M

Monitor on/off

M Network Name, SDATE=yymmdd,{ON/OFF}S

Start Network

S Network name,SDATE=yymmdd[,TIME=hhmm/

PRTY=Priority /CLASS=Class/

JOBLIB=Job Library ID/{F=Job name /T= Job name /O= Job name /E= Job name /B=(Job name, Job name)}][,TYPE=A]

7-49

7. Application Monitor

Command Explaination

Form when it is issued to the A-AUTO Monitor

T

T Network name, SDATE=yymmdd

Delete from abnormallyended information fileR

Run Job(*)[,FREE={Y/N}],C
R Network name,JOB= Job name[,JNO=Job Number]*Commands can be issued only to A-AUTO/MF.When these commands are issued to A-AUTO Opensystem, they are invalid commands for A-AUTO Monitor even though the issuing of these commands
itself may be successful. In this case, the commands are ignored and no operation is performed.

7.8.2

Items to be specified for Issuing Commands
Select a command from select box and click [Execute] button on the toolbar of "Network Monitoring List"
window. A dialog will be displayed.
 Agent Name:

Select the name of the agent to receive the issued command.

 Monitor ID:

Select the Monitor ID that actually processes the command.

Specify the other required information depending on the command.
Below are images of the dialog that will appear when you select a command.

Note

When issued from A-AUTO/Web client, the dialog checks the format or syntax of the command but
does not verify the validity of the command. For example, if a [Release] command is issued to a
Network that is not in Hold status, Release command will still be issued by the Client even if it isinvalid. In this case, the command will be ignored by A-AUTO Monitor.



The Monitor ID selected for the command to be issued must be one of a valid Monitor IDs of theselected Agent.
Refer to "9.1 Management of Agent Information" for information on agent and its Monitor ID setting.

7-50

7. Application Monitor(1) Release
Release Network

Release Queue

7-51

7. Application Monitor(2) Cancel

Type：

C(Cold Cancel)
W(Warm Cancel)
Ｆ(Force Cancel),
Note
When “force cancel” is performed, no pop-up Alert will be displayed.

(3) Reset

7-52

7. Application Monitor(4) System Reset
Modify Monitor ID of System Qualifier

Modify Application Monitor ID/System Qualifier Name

Note
The above-mentioned system-reset command is not supported by A-AUTO for UNIX.

7-53

7. Application Monitor

Modify Job Library ID(5) FreeType:

ON (Free on)
OFF (Free off)

7-54

7. Application Monitor(6) Hold
Hold Network

Hold Queue(7) Monitor

7-55

7. Application Monitor(8) Start(9) Tom

7-56

7. Application Monitor(10) Rerun
You can issue this command from “Detail Job Info” tab of [Detailed Network Info] dialog.

7-57

7. Application Monitor

7.8.3

Confirm Message Display
When the necessary items for the command dialog have been specified, click [OK] button and aconfirmation dialog is displayed for you to verify the command to be issued.

The dialog shows A-AUTO command in actual command line format. Click [OK] to issue the command.

7.8.4

Command Log
The information about the commands that have been issued from the client is recorded on a Command
Log File.
Use this log to check whether a command issued from the client has been received by the A-AUTO
monitor.
Please refer to "9.2.2 Log management" for the setting and obtaining of command log.
Note
Commands issued by all A-AUTO/Web clients linked to A-AUTO Server will be recorded on the Command
Log File.

7-58

8.Functions

8 Functions
8.1

Job Log Management Function(1) Function overview
Job Log Management Function manages Job Log records or files, which contains standard and error output of
Jobs. If this function is activated, A-AUTO Monitor obtains log information of the executed Jobs and stores themas Job Log Files in the specified directory.

UNIX/Windows

A-AUTO Monitor

AP-LINK

Job

CreateRefer

Directory to store Job Logs

Job Log file

Job Log file

Job Log file

Job Log file(2) Job Log file
Job Log files contain the standard output and standard error output that are output by Jobs during their execution.
Job Log files are created and stored in the directory specified by system parameter, ‘NJP_JOBLOGDIR’(described below). The operator can browse the contents of Job Log files using A-AUTO/Web client.

8-1

8.Functions(3) System Parameter Setting
To use Job Log Management function, the following system parameters must be set. These system parameters
can be modified using A-AUTO/Web client.

NJP_JOBLOGON
The installation default value is ‘0’, which indicates that Job Log Management function is inactive. Specify either 1
or 2 to activate Job Log Management function. A value of ‘1’ or ‘2’ indicates the generated Job Log file name to be
used as follows.
NJP_JOBLOGON

File name‘1’

Job ID.CPU Start Date(YYYYMMDD).Start Time(hhmmss)‘2’

Job ID.Schedule Date(YYYYMMDD).Start Time(hhmmss)* A setting of 2 is applicable for v6010 or later.
Please note that if A-AUTO Monitor is started as a service, this parameter is assumed as ‘1’ even if ‘0’ isspecified.

Note
Suppose there are two Networks that contain Job with the same Job ID. If those Jobs start at the same date/time,
the name of the log file will be the same.
[Example] Execution of the same Job ID at the same time
Network ID

Job ID

10/01 9:00

NETWK001
JOB0100

NETWK002
JOB0100

Start

Start

As shown in the above diagram, if Jobs with the same Job IDs are executed at the same time, the names of the
Job Logs will be the same. In such case, the Job Log of NETWK001/JOB0100 is overwritten by the log of
NETWK002/JOB0100. As a result, the Job log record for NETWK001/JOB0100 is not stored correctly in Job Log
file.

8-2

8.Functions

NJP_JOBLOGDIR
This parameter defines the directory name where the Job Log files are to be stored.
【Example】$AUTODIR/files/JLOG/ (In the case of A-AUTO for UNIX)
c: \bsp\auw\JOBLOG\ (In the case of A-AUTO for Windows)
Note For information about specifying the directory
Directory name specified in NJP_JOBLOG DIR must be terminated with "/" or "\", depending on whether it is UNIXor Windows.

8-3

8.Functions

8.3

Resource Management(1) Function overview
Resource Management

Function refers to a function of A-AUTO which manages and controls Resource

allocation.
The Resources and their quantities required for a Network/Job execution are defined when registering the
Network and Job information into the Master file. A-AUTO Monitor ensures that the resources and the quantities
requested by the Network/Job are available before releasing the Network/Job for execution.
The Network/Job will not execute till the requested resources and their quantities are available.
This function is available only in v710 or later.

(2) Flow of control
1.

Setup Resource Definition using "Resource List" screen of System Management Windows. Resource
Definition stores the information about Resources and their maximum quantities available.

2.

For each Network/Job that requires Resource(s), specify the name(s) of the resource(s) and the quantity ofresource(s) required when registering Network/Job Information.

JOB1

JOB2

Resource ID=RES01
Resources used=1
Releasetype=Automatic

Resource ID=RES01
Resources used=1
Release type=Manual

JOB3
Resource ID=RES01
Resources used=1
Releasetype=Automatic

Resource Definition
Resource ID=RES01
Maximum resource=2

For RES01, the maximum number of this resource available is 2 and therefore no more than 2 unitsof the Resource can be used at one time. If JOB1 and JOB2, which both use one unit of Resource
ID:RES01 is running, JOB3, which also requires the same Resource ID, is suspended. JOB3 isreleased for execution when execution of JOB1 finishes and the resource is automatically releasedor when execution of JOB2 finishes and the resource is released using resm utility (manual).

8-7

8.Functions(3)

Related utility
The following utility is used by Resource Management Function.
resm utility

Please refer to "Operation Guide" for explanation on how to use the utility.

8-8

8.Functions

8.7

Adjusting Alert Pop-up* This function is available only when A-AUTO/Web client is used.
(1) Function overview
When a Network ends abnormally or execution delay occurs (if Network delay is monitored), an alert pop-up isdisplayed on A-AUTO/Web client.
By changing the following System Parameters, the timing to send a pop-up message can be customized.
Parameters can be modified via "Settings of Monitor" dialog of System Management of A-AUTO/Web client.

(2) If Parallel run attribute is enabled
If a Network has parallel run attribute and if one of its active Job ends abnormally, alert pop-up indicating that the
Job has abnormally ended is displayed on A-AUTO/Web client. The alert pop-up is displayed only after all the
Jobs in the Network are completed.
However, a user may choose to have the alert pop-up to be displayed immediately after a Job ends abnormallyregardless of whether the other Jobs in the Network are still executing or not. This means that the alert pop-up
may appear even if other Jobs in the Network are still executing. The timing of displaying the alert pop-up can bechanged by the following System Parameter.
AUTO_ASV_EXPFUNC1(A-AUTO for UNIX)
ASV_EXPFUNC1(A-AUTO for Windows)
If a value of 1 is specified for this Parameter, the alert pop-up is displayed immediately when one of the Jobs in a
Network with parallel run attribute abnormally ends regardless of whether the other Jobs are still executing. 0 on
the other hand indicates that, when one of the Jobs in a Network with parallel run attribute abnormally ends, thepop-up is displayed only when all Jobs in the Network have completed. (Installation default value)(3) Warning notification
If a Job ends with a return code equal to or greater than MAX-RC, the Job is considered as abnormally ended.
This function enables a user to display an alert pop-up as a warning notification when the Job did not end
abnormally because its return code is less than MAX-RC but not equal to 0, i.e. " 0 ＜ n ＜ MAX-RC " (nindicates the return code of the Job).
AUTO_ASV_EXPFUNC2(A-AUTO for UNIX)
ASV_EXPFUNC2(A-AUTO for Windows)
A value of 1 indicates that the warning pop-up is displayed on A-AUTO/Web client when the return code of a Job
is " 0 ＜ n ＜ MAX－RC ". If a value of ‘0’ is set (Installation default value), a warning pop-up message will not
be sent.

8-17

8.Functions

8.8

Child Job Cancellation Function(1) Function outline
When canceling an active Job of A-AUTO Monitor, this function enables a user to also cancel processes that arestarted by the Job.

■ In the case of A-AUTO for UNIX

System Parameter setting
To use Child Job Cancellation Function, the following System Parameter must be set. The Parameter can be
modified via "Settings of Monitor" dialog of System Management Windows of A-AUTO/Web client.
NJP_APCANCEL
Specify whether Child processes (processes started by a Job) should be canceled when canceling an active Job.
The installer default is ‘0’. A value of 0 indicates that even when an active Job is cancelled, its Child processes are
not to be cancelled. To use Child Job Cancellation function, a value of 1 must be specified for this parameter. Thisfunction is available in V6007a or later for Linux.
This function is not available for NCR.

8-18

8.Functions■In the case of A-AUTO for Windows
This function uses the dojo utility.
Example in which JOBLOOP cannot be

Example in which JOBLOOP

canceled

can be canceled
A-AUTO Monitor

A-AUTO Monitor

Start

Start
JOBA1

JOBB1

Start

Start
dojo

JOBLOOPStart
JOBLOOPJOBA1.bat

JOBB1.batecho #### START JOB ####

echo #### START JOB ####

rem
loop

rem
loop

jobloop will go into an infinite

jobloop will go into an infinite

jobloop.bat

dojo jobloop.bat

aexit 0aexit 0exit

exit
Both JOBB1 and JOBLOOP are canceled

JOBA1 is canceled, but
JOBLOOP will not be canceled

Note
Processes activated not through dojo utility, or processes activated by jobloop.bat in the above example cannot becanceled. Remaining processes have to be terminated by the Windows task manager.
dojo can cancel Jobs activated by dojo only.
Use dojo utility within the batch file executed by A-AUTO for Windows.

8-19

8.Functions

8.9

Date Transfer Function(1) Function overview
Date Transfer function is designed to pass Operation Date and Schedule Date of the Network to Jobs of the
Network. This function is available in v6010 or later.
Date information can be retrieved using following variables in the Job.
Variable

Description

BSP_AUTODATE

Operation Date of A-AUTO Monitor

BSP_SDATE

Schedule Date of the Network(2) System Parameter setting
Format of the date returned is specified by System Parameter. The Parameter can be modified via "Settings ofMonitor" dialog of System Management Windows of A-AUTO/Web client.
Please refer to “9.3.1 Settings of Monitor”.

AUTO_DELIMITER
Date format can be selected from the following. Specify the value of the parameter according to desired format
given in the following list. The default is ‘0’, which returns the date in the format [YYYYMMDD].
0YYYYMMDD

1

YYYY/MM/DD

2

YYYY-MM-DD

3DDMMYYYY

4

DD-MM-YYYY

8-20

8.Functions(3) Example

In the case of A-AUTO for UNIXIf a value of 1 is specified for AUTO_DELIMITER.
#! /bin/csh
echo "TESTJOB STARTED"
echo "TESTJOB BSP_SDATE:$BSP_SDATE"
echo "TESTJOB BSP_AUTODATE:$BSP_AUTODATE"
echo "TESTJOB ENDED"
exit 0
OutputTESTJOB STARTEDBSPSTA01 BSP_SDATE:
2005/01/28
BSPSTA01 BSP_AUTODATE:
2005/01/28
TESTJOB ENDED

In the case of A-AUTO for Windows
If a value of 0 is specified for AUTO_DELIMITER.
@echo offecho TESTJOB STARTED
echo MONITER-DATE %BSP_AUTODATE%
echo SCHEDULE-DATE %BSP_SDATE%
echo TESTJOB ENDED
exit
OutputTESTJOB STARTEDMONITER-DATE 20050128
SCHEDULE-DATE 20050128
TESTJOB ENDED

8-21

8.Functions

8.10

Test Run Function(1) Function overview
Test Run function enables a user to use a production environment of A-AUTO to run test Jobs without the need tochange Network definitions or create additional Networks. To perform test run, test shell scripts/test batch files
must be stored in a directory other than the actual directory that stores Job scripts/batch files for production
environment. Test directory must be defined in Job Library file. To direct A-AUTO system to use the test directory,change the Job Library ID after queuing or specify the Job Library ID for test run when issuing Start command.
Start the test run. This function is available in V7 and later.

A-AUTO Monitor
Job Library
Definition fileStart

Job Library 0

Job Library 1

Job Library 2

Job Library 9･･･

Job Library for

Job Library for test run

production(2) Flow of control
When a Job is ready to start, A-AUTO Monitor first obtains the Job Library ID of the Job (or the Network) and thensearches for the Job in directories specified in TEMPSCRIPT_PATH and PRIMSCRIPT_PATH, which are definedfor each Job Library ID. If the Job is found, it executes the Job. Directory specified in TEMPSCRIPT_PATH isalways searched first before directory specified in PRIMSCRIPT_PATH. A set of TEMPSCRIPT_PATH and
PRIMSCRIPT_PATH is called "Job Library" and an ID assigned to each "Job Library" is called "Job Library ID". An
ID is a numeric value from 0 to 9. Job Library ID of '0' is used for production environment and A-AUTO Monitor
usually executes Jobs from this Job Library ID.

Job Library ID

Explanation

0

Job Library ID for production environment

1 to 9Job Library IDs for test run
8-22

8.Functions* Job Library can be defined using [Job Library Detail] dialog of System Management Windows of A-AUTO/Web
client or in Job Library file. Please refer to Web Help for defining Job Library via A-AUTO/Web client, and refer toSystem Administrator's Guide for defining from Job Library file.

A-AUTO Monitor usually assigns Job Library ID of 0 to Networks during Queuing but the Job Library ID can bechanged after Queuing by one of the following methods.
System Reset command (ESYS Command) :Reset command (E Command) :Changes the Job Library ID of all the Networks in Queue.

Changes the Job Library ID of a specific Network in Queue.

Job Library ID can also be defined when issuing Start command.
Please refer to Operation Guide on how to issue these commands.

Note

A Job Library ID other than 0 cannot be specified for Networks executed by AUTO for OS/400 Remote
License or if the Network includes R/3 Job.



If a Network has abnormally ended at the previous execution, the Job Library ID used for the previous
execution is used. However, if Job Library ID is specified in Start command, the specified ID overwrites Job
Library ID of the previous execution.



Rerun Recovery function queues the recovery Network with Job Library ID of the abnormally ended Job. If
Job Library ID is specified in Start command, queuing of recovery Network is done with the specified Job
Library ID.
Queuing of rerun Network after its recovery Network has completed, is done with the Job Library ID used forrecovery Network.

Time Interval Execution Function is re-queued with the Job Library ID used for the previous run.

8-23

9. System Management

9 System Management
9.1

Management of Agent Information
A-AUTO Server manages information of Agents in A-AUTO System.
A list of the Agents and their information is displayed on the below Windows.

① Status
The [Status] shows the status of the communication link between A-AUTO Server and the Agent. Status
can be one of the following types.
 Connected: Server and Agent are connected.

 Disconnected: Server and Agent are disconnected.

 Monitoring: File Transfer operation has ended and information has beensaved into Server files.
Progress Information will be sent by Agent at regular intervals.
 File Transferring: Information is being transferred from Agent to Server formonitoring.

 Simulating:Time Simulation is in progress.

② Monitoring Monitor ID
Monitor IDs of the A-AUTO Monitors that are being monitored by the Agent are displayed.

9-1

9. System Management③ Network Queue, Execute Network Queue[Network Queue] and [Execute Network Queue] items show the status of Scheduled Network Queue andExecution Network Queue respectively. [Network Queue] can be in one of the following statuses.
 Hold:Network Queue is being held.

 Release :Network Queue is released.

 Unknown :Accurate status is unknown.

[Execute Network Queue] is not supported in A-AUTO for UNIX/Windows and is always displayed as [-].

④ Version
Displays the version of the appropriate agent.
Notes

While [Status] is [File Transferring], do not execute [Disconnect Agent] for the Agent.

[Version] is the version that is displayed when Server and Agent were first connected.

When the Version of Agent is “V721”, [Version] is displayed as “V710”.

9-2

9. System Management

Start Monitoring (File Transfer)
On [Agent list] Windows, Start Monitoring (File Transfer) command can be issued. Check the check box ofthe target Agent. From pull-down menu of the toolbar on [Agent list] Windows, select [Start Monitoring] andclick [Execute] button.
[Request Start Monitoring] dialog will be displayed.

Specify the necessary items and click [Execute] button.
[Execute Result] dialog is displayed and File Transfer starts. Network information of Networks withspecified Execution ID and schedule date(s) will be transferred and monitored.
* “Started to process the request” message is displayed on [Execute Result] dialog to inform you that File
Transfer has been started.

Setting Agent information
On [Agent Detail] dialog, the following items related to an Agent can be set.
 Monitor IDs of A-AUTO Monitors to be monitored and number of Partitions (multiplicity) for each
A-AUTO Monitor.
 Specify a time for setting Operation Date and, if you are using automated command function, specify
date and time to issue these commands.
 Setup for A-AUTO/Event

9-3

9. System Management

9.1.1

Monitoring A-AUTO Monitor ID SettingsSpecify the Monitor IDs of A-AUTO Monitors that are to be monitored by the Agent. The Agent will monitor
and control Networks under specified A-AUTO Monitors.

(1) Items to define① Monitor ID
Identifier of A-AUTO Monitor. Up to 8 alphanumeric characters can be specified.

② Multiplicity or Number of concurrent processing
Number of Partitions (Multiplicity) means maximum number of Networks that can run concurrently at any
one time for a class. Each Class may be assigned a different number of Partitions.

③ Install directory of A-AUTO Monitor
Specify installation directory of A-AUTO Monitor.

(2) What is number of Partitions (Multiplicity)?
Number of Partitions (Multiplicity) means maximum number of Networks that can run concurrently at any
one time for a Class. For example, if number of Partitions for Class A is 6 and the number of Partitions forClass B is 2. Then, the maximum number of Networks, defined with Class A attribute, that can run
concurrently is 6 while the maximum number of Networks, defined with Class B attribute, that can run
concurrently is 2. When a Network ends, another Network with same Class can be run. The larger thenumber defined for the number of Partitions (Multiplicity) for a Class, the faster A-AUTO Monitor can
9-4

9. System Management

complete its execution of Networks.

(3) Setting number of Partitions (Multiplicity)
To execute Time Simulation function, number of Partitions (Multiplicity) must be set for each A-AUTO
Monitor. It is used just for Time Simulation and there is no impact on the processing in Mainframe A-AUTO
and A-AUTO for UNIX/Windows ® .
Therefore, it is not mandatory to match this definition with the definition defined for the processing in
Mainframe A-AUTO or A-AUTO for UNIX/Windows ® environment. But it is recommended to simulate theexecution of the Networks as close to the real environment as possible.

Setting example of monitoring Monitor ID
Monitor ID:AUTO01

Number of multi processing:Class A

Install directory of A-AUTO Monitor:C:\BSP\AUW\BIN

6, Class B

2(1) Click [Create] button on [Monitoring A-AUTO
Monitor ID Settings] window.
(2) [Create] window will be displayed.

(3) Enter the necessary items.
■

Monitor ID: Enter AUTO01■

Input 6 for ClassA.

■

Input 2 for ClassB.

■

Input C:\BSP\AUW\BIN in Install Directory of A-AUTO.

(4) Click ［Apply］ button.
(5) Monitor ID is added as specified.

9-5

9. System Management(6) Click [Apply] button.
(7) Setting is saved.

9-6

9. System Management

9.1.2

Setting automated issuing menu command
The following menu commands can be automated to be issued automatically at specified day and time.
 Connect Agent Disconnect Agent Start Monitoring
Menu Command can be set to be issued Daily, Weekly (a specific day of every week) or Monthly (aspecific date of every month) and at a specific time. If the server is connected to multiple Agents, you haveto perform the setting for each Agent individually.

Items to define① Command
Select the Menu Command that you want to set to be issued automatically.

② Execution ID
Specify a value for this field only if the command to be set is [Start Monitoring].

③ Set ScheduleSet the day for the selected command to be issued.

9-7

9. System Management④ Set Time
Set the time for the selected command to be issued for the specified day (set schedule).

Schedule Date, when ‘Start Monitoring’ command is issued
automatically
If ‘Start Monitoring’ command is set to be automatically issued, Schedule Date used for the automated‘Start Monitoring’ command will be the A-AUTO Operation Date. The information of the Networks for that
Schedule Date will be transmitted from Agent to Server and monitored at Client. A-AUTO Operation Dateat the time of the command depends on the current CPU date of the server and the time set in ’Change
Operation Date at’field. Because of this reason, Schedule Date used for ‘Start Monitoring’ may bedifferent from A-AUTO Monitor Date. An illustration is given below.
’Change Operation Date at’ specifies the time to reset A-AUTO Operation Date to the current CPU date ofServer.
<Example>
Assume that”8:00 AM” is specified in “Change Operation Date at” field, and that:(A) ‘Start Monitoring’ command is automatically issued at 7:00AM(B) ‘Start Monitoring’ command is automatically issued at 9:00AM
Case (A): ‘Start Monitoring’ command is issued before the time specified in “Change Operation Date at” field. At thispoint, A-AUTO Monitor Operation Date is not updated to the Server CPU date yet. Therefore, Schedule Date used is(CPU Date – 1), which is one day behind the current Server CPU date.
Case (B): ‘Start Monitoring’ command is issued after the time specified in “Change Operation Date at” field and A-AUTO
Monitor Operation Date is already updated to the Sever CPU date. Therefore, Schedule Date for the ‘Start Monitoring’
used is the same as A-AUTO Monitor Operation Date, which is now the current Server CPU date.
Start Monitoring command (A)Schedule Date=970803
Start Monitoring command (B)Schedule Date=970804
Server CPU Date

97/08/03

97/08/04
AM0:00

AM7:00

AM9:00
AM8:00A-AUTO Operation Date

97/08/03

97/08/04
DATE command

Schedule Date, when ‘Start Monitoring’ commands is issued automatically

9-8

9. System Management

Notes


When menu command is automatically issued, the command will be ignored in the following cases.
Menu command

Status of Agent

Connect

Already connected

Disconnect

Already disconnectedStart Monitoring

Agent is being monitored or transferring file

9-9

9. System Management

9.1.3

Setting of A-AUTO/Event
The following are the necessary settings to be made when Event Triggering function is used.

Items to define① A-AUTO/Event Agent ID
Specify A-AUTO/Event Agent name to be used for monitoring events. Any registered A-AUTO/Event Agentname can be selected.

Settings of Send Mail

② A-AUTO/Event Agent ID
Specify A-AUTO/Event Agent name that sends e-mail.

③ Path of A-AUTO/Event to send mailSpecify path of A-AUTO/Event that is used to send e-mail. Path Name of the Agent can be defined up to a
maximum of 260 characters
The information set here is used when Work is defined in Event Management Master. Also, information set at② and ③ is used when Actions are executed.

Setting for Monitor connection④ A-AUTO/Event Agent ID
Specify A-AUTO/Event Agent name that executes Data Arrival instruction and issues Start Command

9-10

9. System Management

9.2

Management of Server Information
Server information is displayed on the following window.

In the Server pane, Server name and number of Agents to be monitored are displayed at the top of thepane. Other information shown in Server pane are server management information such as setting for data
management and log management and a log of file transfers that have been performed.

9-11

9. System Management

9.2.1

Data Management
The following information used by Server are created and stored for each day of operation. The datastored is cumulative and the files that stored the data will increase with each day of operation.
 Network Monitoring Information
 Event Monitoring Information

Because these data are not automatically deleted, you must delete these data periodically.
If more than one Agent is managed by the Server, data can be deleted only when the status of all theAgent is [Disconnect] or [Connect]. As long as the [Status] of any of the Agents is [Monitoring] or [FileTransferring], data cannot be deleted.
Methods to change an Agent’s [Status] to [Disconnect] or [Connect].
Select [Agent] on [List Menu] of System Management Windows. [Agent List] pane will be displayed.
Select the checkbox of the target Agent, select [Connect] or [Disconnect] from pull-down menu on the
toolbar and then click [Execute].



Automate [Disconnect] menu command using [Automatic Command Issue Settings] tab of [Agent
Detail] dialog. (Refer to “9.1.2 Setting Automated Issuing Menu Command”)(1) Backup of Data
If you want to save the monitoring information for future reference, you can set the archival information.
Please refer to “9.2.1(3) (Automatic Deletion)”(2) Manual Deletion
Check the [Status] of all Agents is [Disconnect] or [Connect] on [Agent List] Windows.
（Refer to the above ”Methods to change an Agent’s [Status] to [Disconnect] or [Connect].”)Manual Deletion of Network Monitoring Information and Event Monitoring Information can be performed on[Network Monitoring List] and [Work Monitor List] of the target [Application Monitor] Windows respectively.
For more about deleting Network Monitoring information, please refer to [7.3.4 (5) Delete the Monitoring
Records].
For more about deleting Event Monitoring information, please refer to [7.2.7 Delete Completion
Information].

9-12

9. System Management(3) Automatic Deletion
You must ensure that the status of all the Agents is [Disconnect] or [Connect] before automatic deletion isstarted. Automatic deletion will fail if the [Status] of any of the Agents is [Monitoring] or [File Transferring].
To avoid this problem, it is recommended to automate Menu Command “Disconnect” to be issued allagents prior to starting automatic deletion.
(Refer to “9.1.2 Setting Automated Issuing Menu Command”)
In addition, you may want to automate Menu Command “Connect” to be issued to all agents after the
automatic deletion so that the agents are automatically connected and ready for use by A-AUTO system.
(Refer to [9.1.2 Automated Issuing Menu Command Setting])
Choose the timing to initiate automatic deletion, which can be once a month / once a week / once a day
according to the hard disk capacity of your PC. (Refer to System Administrator's Guide to estimate thecapacity of file space)

Click [Server Settings] of [List Menu] of System Management Windows to display [Server Settings] pane.
In Data Management, there are [Network Monitoring Initialize Settings] and [Event Monitoring Initialize
Settings]. Click the [Automatic Initialize Settings] icon and Initialization Settings dialog will be displayed.

Set the automatic deletion for Network Monitoring information or Event Monitoring information accordingly.

9-13

9. System Management

The following explain the items of the dialog.

① Set ScheduleSpecify the cycle for the automatic deletion processing. Cycle can be one of the following; Daily, a specificday of every Week (Monday to Sunday), and a specific date of every Month (1 to 31).
If you do not want to automatically delete the information, please select [Delete Ineffective].

② Set Time
Set the time to start the automatic deletion. The time that can be specified is from 00 hour to 23 hour andfrom 00 min to 59 min.

③ Set Retention Days
Specify the retention days for the monitoring information before the information is deleted. Retention daysof 1 to 31 can be specified.
* Data to be deleted will be any Monitoring Information that is created earlier than (24 hours × Retention
Days value)*.
E.g. If you specify 3 days, the data that are created 72 hours prior to automatic deletion execution are
extracted and then deleted.

④ Archive Deleted Data
If you want to save the Monitoring information, check the check box of [Archive Deleted Data].

⑤ Archive Folder
If [Archive Deleted Data] is selected, specify the path where the archived file is to be saved.

Network Monitoring Initialize Settings example
Set Schedule:Weekly Wed

Set Time:AM11:00

Set Retention Days

:15

Archive Folder:Do not select [Archive Deleted Data]

9-14

9. System Management(1)Enter the necessary items.

(2) Click [Apply] button.
(3) The settings have been registered.

9-15

■

Select Weekly of Set Schedule■

Select Wed from pull-down menu■

Set Time: 11:00■

Set Retention Days: 15

9. System Management

9.2.2

Log management
The Server records various events between Agent, Server, and Client in Event Log, Alert Log, Command
Log File, and Security Log. This section describes of the procedures to view the Logs, to turn the logging
on/off and to perform the maintenance for the Logs.

Viewing of Logs
Click [System Management] on [A-AUTO Main] Windows to open [System Management] Windows.
Click a Log link on [List Menu] of the [System Management] Windows to display the respective Log.

Settings about Log
The following explain the types of Logs that A-AUTO can obtain and the items in these logs.

(1) Log can be retrieved
You can get the following logs from the Web client① Event Log
In the Event Log, the information will be recorded when the following events occur.
 Agent Session
 Start Monitor
 Event / Network Monitoring Initialize Settings
 Delete Log
 Replicate Data
9-16

9. System Management

 Time Simulation
 Start Server② Alert Log
Alert Log records the information whenever an alert (Job Abnormally End, Job Network Start / End Delay)
is reported on Web Client③ Command Log
Command Log records the information whenever a command is issued by Web Client.

④ Security Log
Security Log records the operation whenever master maintenance is performed.

9-17

9. System Management*Utility of master maintenance, such as Security Log of the operation that runs from the A-AUTO monitors, is created in
the installation folder of the A-AUTO Monitor. Open [SECURITY.LOG] of Installation folder ( by default C: \ BSP \ AUW \FILES \ LOG) in a text editor, and check it please.

On [Security Log List] pane, you can search for logs based on the specified criteria.
Click the Search iconon the the toolbar on [Security Log List] window.

[Security Log - Search] window will be displayed.
[Security Log - Search] window

Enter the search conditions and click [Search] button on the top left please. The logs thatmatched the search conditions are displayed on the list pane.
The following explain the items of [Search] dialog.
①

From (Date Set)
You can specify the start date of the search range by clicking the calendar icon.
If you specify the start date only, all Logs beginning from the start date will be selected.

②

To (Date Set)
You can specify the end date of the search range by clicking the calendar icon.
If specify the end date only, the Logs from the beginning to the end date will be selected.

9-18

9. System Management③

User ID
You can specify a specific User ID.

④

Agent NameYou can specify a specific Agent name.

⑤Type
You can specify the type of processing that was performed on the master. If not specified, all types will beselected.
0: Create
1: Update2: Delete
3: Login/Logout⑥

Master NameYou can specify a specific Master Name. If not specified, all Master Names will be selected.
The value for Master Name can be one of the following.
The list of Master Names that can be specified.
User
Password
Asv Server Management Information
Agent Information
Monitor Information
A-AE Information
AAUTO Command Information
Job Library Information
System Qualifier
System Group Qualifier
Plug-in Information
Resource Setting Information
Preceding Network Master
Network Master
Input Data Wait
Resource Master
Job Information Master
Network Group Information
Cross-Master Preceding Network ?
Schedule Definition
Network Schedule
Daily Network Schedule Information
Holiday Definition
Holiday DefinitionWork
Event Definition
Action Definition
Job Master
Resource Management MasterR3 Job Master
Monitor Setting
User Information
User Resource
Resource GroupResource Group Detail
User Profile detail

9-19

9. System Management(2) Items can be set
For each log, you can turn the logging on or off, and set the timing of initialization.

① Whether to acquire the Log
You can select whether to turn on or off the logging for Alert Log and Security Log.
Please select ON/OFF of [Write Security Log] and [Write Alert Log].

② Initialize Settings
You can automate the deletion process for all logs.
Click [Initialize Settings] icon of each Log, Initialize Settings dialog is displayed.
*About Initialize Settings, please refer to [9.2.1 Data Management].

③ Whether to play-back Alert sound
Set whether to play-back a recorded sound when Alert occurs.
Please select ON / OFF of [Play back sound on alert]④ Logging Event
About Event Log, you can select which Log to capture.
Please select the Log to capture from [Logging Event]9-20

9. System Management(3) Manually Initialize the Log
On the respective log list panes, click [Delete] button to delete the log.
[Request Delete Log] dialog is displayed.

Select the date for the log deletion and click [Execute] button.
If you want to save the log prior to the deletion, select the check [Archive Delete Data] check box. If
Automatic Deletion has been set, it will be saved in the directory specified for [Archive Folder] of therespective [Initialize Settings] dialog. If [Archive Folder] of the respective [Initialize Settings] is not set, it will
be saved in [Install directory \A-AUTO_APServer\data].

9-21

9. System Management

9.2.3

File Transfer
Server Management provides the File Transfer information between the server and Agents. This
information is displayed in [File Transfer Log List] pane as shown below.
For items that are displayed in the Windows, please refer to [9.1 Management of Agent Information].

The [Status] will show one of the following.
 Valid:

The data of this File Transfer request is periodically monitored and updated withinformation from the agent.
 Invalid:

The data of this File Transfer request is no longer monitored.

How to Perform File Transfer
 File Transfer can be performed from [File Transfer Request] dialog. [File Transfer Request]
dialog can be invoked in one of the following ways.
・

Select [File Transfer] on [List Menu] of [System Management] Windows to display [FileTransfer Log List] pane. Click [File Transfer] button.

・On [Network Monitoring List] pane of [Application Monitor] Windows, click [Menu] icon on
the toolbar. [Network Monitor Menu] dialog is displayed. Select [File Transfer] from theselect box on the the toolbar and click [Execute] button to display [File Transfer Log List]
dialog. [File Transfer Request] dialog is displayed by clicking [File Transfer] button.

 On [File Transfer Request] dialog, specify the necessary items on the dialog and click [Execute]button.
For more about File Transfer function, please refer to [7.5 File Transfer].

9-22

9. System Management

9.2.4

Simulation
According to the schedule information of Networks, you can simulate the estimate start time and theestimate end time of Network execution. Time Simulation is performed on Server.

(1) How to Perform Time Simulation
Simulation can be executed from the [Simulation Log List] pane of [System Management] Windows.

Select [Simulation] on [List Menu] of [System Management] Windows. [Simulation Log List] pane isdisplayed. Click [Simulation] button on the toolbar of the Windows. [Simulation Request] dialog is displayed.
Specify the necessary items and click [Execute] button. [Execution Result] dialog is displayed andSimulation starts execution.
*[The command was processed successfully] is displayed on [Execution Result] dialog and Simulation
starts execution.
For more about Time Simulation function and how to run Time Simulation from [Network Monitor List]
Windows, please refer to [7.6 Time Simulation].
(2) Result of Time Simulation
The result of Time Simulation can be displayed on [Network Monitor List Time Chart] pane of [Application
Monitor] Windows on Web Client.
For more about [Network Monitor List Time Chart], please refer to [7.6 Time Simulation].

9-23

9. System Management

9.2.5

ReplicateServer Management provides information on Replication logs. Replication Information can be displayed on[Replication History] pane of [System Management] Windows as shown below.

Replication Function
Replication compares Master information stored on the A-AUTO Monitor with the information stored on
A-AUTO Database. If there are inconsistencies between the data of both Master files, Master file on the
Database will be updated with Master file on the A-AUTO Monitor.
Under normal condition, replication will be executed automatically when Master is updated. Replication
request from the Web Client must be done only when Master cannot be updated automatically due tomachine down or connection error and so on.
How to Perform Replication
You can execute Replication from the [Replicate History] pane of [System Management] Windows.
Select [Replicate] on [List Menu] of [System Management] Windows to display [Replicate History] pane. Click[ Replicate] button on the toolbar of [Replicate History] pane, [Replicate Request] dialog is displayed. After
specify the necessary item, click [Execute] button. [Started to process the request] is displayed on [Execution
Result] dialog and Replication starts execution.
*[Started to process the request] is displayed on [Execution Result] dialog and Replication starts execution.［

9-24

9. System Management

9.3

Monitor Information Management[Monitor Management] Windows enables users to manage A-AUTO Monitors installed on each platform via
A-AUTO/Web client. A-AUTO/Web Client can change the settings and definition information of an A-AUTO
Monitor.

This function is available in V710 or later.

9.3.1

Settings of Monitor
You can view and, if required, set the definitions and System Parameters of an A-AUTO Monitor using[Settings of Monitor] dialog.
Select [Monitor] on [List Menu] of [System Management] Windows. [Monitor Lost] pane is displayed. On[Monitor List] pane, click Monitor ID link of the target A-AUTO Monitor whose definitions and System
Parameters are to be updated. [Monitor Edit] dialog is displayed. Select [Settings of Monitor] on [List Menu]
of [Monitor Edit] dialog. [Settings of Monitor] pane is displayed.

You must set the character code set according to the OS of the server where A-AUTO Monitor is installed.
Select character code set on the toolbar and click [Refresh] button.
One of the following character code sets can be selected.
 Shift-JIS
 EUC-JP UTF-8

9-25

9. System Management

Definition Item
For details of the items, their possible values and examples of settings for the items, please refer to“auto_sysconf Parameter List” of System Administrator's Guide.

Update Setting
Select the item to be updated from list on the tree on [Settings of Monitor] pane. The parameters andvalues of the selected item are displayed on the right side of the page.
Change the values of the parameters accordingly and click the [Apply] button to update the changes.
* For the changes to take effect, you must restart A-AUTO Monitor.
For details on restarting A-AUTO Monitor, please refer to “2.10 Update A-AUTO System Parameter” of
System Administrator's Guide.

9-26

9. System Management

9.3.2

Job Library Detail
When a Job is ready for execution, A-AUTO Monitor uses Job ID of the Job to search for the job in libraries
defined by Job Library Definition. It searches for the Job in the library defined for the temporary path
(TEMPSCRIPT_PATH) first, and if not found, searches the library defined for the main path
(PRIMSCRIPT_PATH). A set of main path and temporary path definitions is called "Job Library" and an ID
assigned to each Job Library is called "Job Library ID".
Job Library IDs that may be defined are from 0 to 9. ID "0" is assigned to the Job Library for production
environment. ID from 1 to 9 should be assigned to Job Library for test run.
For details about Test Run, please refer to [8.10 Test Run Function].
Select [Monitor] on [List Menu] of [System Management] Windows. [Monitor List] pane will be displayed.
On [Monitor List] pane, click Monitor ID link of the target A-AUTO Monitor whose Job Library Definition is to
be updated. [Monitor Edit] dialog is displayed. Select [Job Library Detail] on [List Menu] of [Monitor Edit]dialog and [Job Library Detail] is displayed.

Definition Item
The following explain the items that can be defined.
*Each value displayed under column [#]corresponds to the Job Library ID.

① Main Path
This is the path of the directory where A-AUTO Monitor will search for scripts/batch files of Jobs if it cannot
find the Jobs in Temporary Path. Specify the path of the main library or directory where A-AUTO Monitor
will search for scripts/batch files of Jobs.
You can specify up to 256 alphanumeric characters.

② Temporary Path
This is the path of the directory where A-AUTO Monitor will search for scripts/batch files of Jobs first.
9-27

9. System Management

Specify the path of the temporary library or directory where A-AUTO Monitor will search for scripts/batch
files of Jobs
You can specify up to 256 alphanumeric characters.

9-28

9. System Management

Example for Job Library
Job Library ID:1Main Path: C:\ BSP\AUW\INSTALL\PRIMSCRIPT1

Temporary Path

: C:\BSP\AUW\INSTALL\TEMPSCRIPT1(1) Display [Job Library Detail] window.

(2) Enter the necessary items.
■ Main Path
C:\BSP\AUW\INSTALL\PRIMSCRIPT1■ Temporary Path
C:\BSP\AUW\INSTALL\TEMPSCRIPT1(3) Click [Apply] button.
(4) The setting is registered9-29

9. System Management

9.3.3

System Qualifier Definition
System Qualifier is the identifier used by a Network to identify in which A-AUTO Monitor the Network is to
be executed.
Every Network registered into Network Master is defined with a System Qualifier. A-AUTO Monitor uses
the System Qualifier of the Network to determine the environment to execute a Network, which may be a
local environment or A-Remote environment. Local environment refers to the environment where A-AUTO
Monitor resides while A-Remote environment refers to the environment where the Remote Job Execution
Function resides.
For more details about the definition items and examples on specifying these items, please refer to [13.1.1
Setting System Qualifier].

9.3.4

System Group Qualifier Definition
System Group Qualifier is a group of System Qualifiers. It is defined when using the Load Balancing
function.
If a System Group Qualifier name is specified in the System Qualifier attribute of a Network, A-AUTO
Monitor automatically selects on which an A-Remote environment to run the Network from the group of
A-Remote environments (System Qualifiers) defined in the specified System Group Qualifier.
For more details about the definition items and examples on specifying these items, please refer to [13.8.1
System Group Qualifier Definition].

9-30

9. System Management

9.3.5

Resource Definition
Resources are defined when Resource Management function is used.
Resource Management

Function manages and controls Resources allocation. The Resources and theirquantities required for a Network/Job execution are defined when registering the Network and Job
information into the Master file. A-AUTO Monitor ensures that the resources and the quantities requestedby the Network/Job are available before releasing the Network/Job for execution.
For details on how to define Resources, please refer to “3.1 Network Master” and “3.4 Extended Job
Master”. For more details about Resource Management function, please refer to [8.3 Resource
Management].
Select [Monitor] on [List Menu] of [System Management] Windows. [Monitor List] pane is displayed. On[Monitor List] pane, click Monitor ID link of the target A-AUTO Monitor whose Resource Definition is to be
updated. [Monitor Edit] dialog is displayed. Select [Resource] on [List Menu] of [Monitor Edit] dialog and[Resource List] is displayed.

Definition Item
The following explain the items that can be defined.

① Resource ID
This is the identifier for each Resource to be registered. Up to 8 alphanumeric characters (Capital Letter
Only) can be specified.

② Resource Name
Comment information for the Resource. Up to 128 alphanumeric characters can be specified.

③ Maximum Number of Resource
Specify the maximum quantity available for the resource.

9-31

9. System Management

Example for Resource
Resource ID:RES01

Resource Name

:CO001

Maximum Number of Resource:20(1) Click [Create] button of [Resource List](2) [Create] dialog of Resource Definition is displayed.

(3) Enter the necessary items.

(4) Click [Apply] button.
(5) RES01 has been registered.

9-32

■

Resource ID: RES01■

Resource Name: CO001■

Maximum Number of Resource: 20

9. System Management

9.3.6

Plug-in Definition
Plug-in is defined when using Job Branching function.
"Job Branching" function is a function that determines how to execute a job according to the return code or
the end status of the preceding job. Users can control the status of the Job (or Network) according to thereturn code of plugin
For more details about return code of user Plug-in and Job Branching, please refer to [3.1.4(3) Job
Branching Function].
Select [Monitor] on [List Menu] of [System Management] Windows. [Monitor List] pane is displayed. On[Monitor List] pane, click Monitor ID link of the target A-AUTO Monitor whose Plug-in Definition is to be
updated. [Monitor Edit] dialog is displayed. Select [Plug-in] on [List Menu] of [Monitor Edit] dialog and[Plug-in List] is displayed.

Definition Item
The following explain the items that can be defined.

① Plug-in ID
This is the identifier for each Plug-in to be registered. Up to 8 alphanumeric characters(Capital Letter

Only) can be specified.

② Plug-in Name
Comment information for Plug-in. Up to 32 alphanumeric characters can be specified.

③ Plug-in Execution Module
Specify the executable Module/file/script/batch file name for the Plug-in. Up to 16 alphanumeric characters
can be specified.

④ Plug-in Type
Select the type of Plug-in. One of the following types may be selected.
9-33

9. System Management

 Batch file of Windows Executable file of Windows Shell script of UNIX Executable file of UNIX
Example for Plug-in
Plug-in ID: PLG01

Plug-in Name

: CO001 Machine

Plug-in Execution Module: plugPlug-in Type

: Batch file of Windows①Click [Create] button of [Plug-in List] dialog②[Create] dialog is displayed.

③Enter the necessary items.
■

Plug-in ID: PLG01■

Plug-in Name: CO001 Machine■

Plug-in Execution Module: plug■

Plug-in Type: Batch file of Windows(4) Click [Apply] button.
(5) The Plug-in has been registered.

*Plug-in Execution Module is configured in PLUGIN directory of A-AUTO install directory. Then, set Plug-in
Execution Module as same as the name of Plug-in Start Module/Plug-in Type.
The above, [plug.bat] is configured in PLUGIN directory.
*Plug-in shell scripts, please create it by the same user as A-AUTO start user.

9-34

9. System Management

9.4

In the Case of Use Server Function from Console
You can perform some Server functions on the console of A-AUTO/AP Server using Server commands.
Functions and commands available are as follows.
File Transfer:FTP CommandDisplay Agent information:DAGT CommandInitialization Monitoring file :INITFILE Command

For more details about each command, please refer to “2 A-AUTO/Agent & A-AUTO/AP Server
Commands” of Operation Guide.

9-35

11. Event Management

11 Event Management
11.1 Overview of Event Management


Event Management
Triggering events and the corresponding actions to be executed can be registered using Work
Windows of A-AUTO/Web client. Registered events are monitored and actions will be executed when
the related events occur. This is called Event Management function. Event Management function is
supported by a component called A-AUTO/Event.

Event monitoring function with Web client
Occurrence and execution of registered events and actions can be monitored and controlled withWeb client.

A-AUTO/Event connection setting function
When Event Monitoring function is used, which A-AUTO/Event Server is connected and which port isused can be set with Web client. Click [Agent] tab on System Management window, and selectA-AUTO Agent name to be set.

11-1

11. Event Management

11.2 System Configuration
System Configuration of Event management is shown below.

11-2

11. Event Management

11.2.1 Operation flow
Operation flow of Event Management is shown below.

Editing registered data

Event Definition
Registering Works

Updating Event Management data

Registering Event Management data
Deleting Event Management data

Changing monitoring data
Changing monitoring conditions
Confirming execution status
Monitoring events

Executing actions

Switch monitoring and notmonitoring processes
Deleting completed events

Event Monitor: Execute Event Control function: Functions realized automatically by registering data11-3

11. Event Management

11.3 Master Maintenance
Maintenance of Event Management Master is carried out using Web client the same way as other master files.



Maintenance of Event Management master
Event management information is registered into Event Management Master.
Operation flow of Event Management is shown below.
■ Adding events and actions■ Viewing events and actions■ Updating events and actions■ Deleting events and actions■ Enabling or disabling monitoring function■ Setting monitoring start time and end time
■ Executing or not executing actions■ Setting action execution patterns

11.3.1 Defining Event master
Web Client Work Windows is used to register, modify, delete or search triggering events and actions to be
executed.
When Web client is initiated, information related to registered Work IDs in Event Management Master are
displayed in list format. This list is called ‘Work Definition List’ (Below figure)Work Windows is used to maintain Works displayed on ‘Work Definition List’.

11-4

11. Event Management

11.3.2 Registering Works
When new events are to be monitored and processed by A-AUTO for UNIX/Windows, new Works have tobe registered into Event Management Master. Procedures to add or register a new Work are described
below.
①

Click on [Create] button on Work Definition List window.

② Work detail dialog is displayed. Specify the items on the Work detail dialog according to events andthe corresponding actions required for the Work.
③

Click on [Apply] button to save the new Work after setting the necessary items.

The following is an example of adding a new Work.
Example11-1 Adding a new Work
Between 9:00-13:00, when a process mcp ends on event occurring computer (CZ1), a message(END) will be displayed on A-AUTO/Event console window. Register above scenario as follows.

11-5

11. Event Management

Example 11-1 Adding a new Work
1 Click [Create] on Work Definition List window.
The Work Detail window will be displayed.
2 Enter necessary items.
Enter "AAWORK01" for Work ID.

Enter comments for Comment.



Select 09:00 for Start Time.



Select 13:00 for End Time.

3 Click [Event] tab.
The Event List window will be displayed.(below)

4 Click [Create] button
The [Event Create] window will be displayed.

5 Enter necessary items.


Select Job Event for Event Type.



Select CZ1 for Computer Name.

Enter "mcp" for Process Name.

6 Click [Apply] button.
An Event is added as specified.

※Event Type can be one of the following 4 types, Job Event, File Event, Message Event, or Application
Event. Please refer to “3.3.2 Items to define (Data Wait)” for example of new registered Work.

11-6

11. Event Management

7 Click [Action] tab.
[Action List] window will be displayed.

8 Click [Create] button.
[Action Create] window will be displayed.

9 Enter necessary items.


Select Message Output for Action Type.



Select CZ1 for Computer Name.

Enter "END" for Message

10 Click [Apply] button.
11 Click [Basic Settings] tab, Click [Apply] button
Registration of the work definition by the above is completed.

※Action type can be one of the following 5 types, Job Execution, Message Output, Send Mail, and Send
Start Command. Setting examples are explained below. Refer to example 11-1 for setting Message
Output.
1. When Job Execution is selected
Example: To execute a Job (/home/bsp/auto/bin/abc) with a parameter (01) on Computer name (CZ1).

11-7

11. Event Management

2. When Send Command is selected
Example: Computer name (CZ1), Command (/home/bsp/auto/bin/abc) , Parameter(01)2. When Send Mail is selected
Example: To send an e-mail according to Send Information Parameter file (EMAILINFO01) with keyword(TIME=1030), when a related Event occurs.

3. When Send Start Command is selected
Example: To send a Start command for Network (NET001) when a related Event occurs.

11-811. Event Management

11.4 Utility
A-AUTO/Event includes the following 4 utilities.
Transferring Event occurrence information
Information of occurred Events is transferred to the corresponding Actions that are being executed.

Generating an Event utility
Events are generated at specified time by users.



Monitoring log files utility
Log files are monitored and appearance of specified characters is recognized as an Event.



Sending an mail utility
Send mail as "Action"

11-9

11. Event Management

11.4.1 Transferring Event occurrence information
A-AUTO/Event can transfer information of an Event to an Action that is defined in the same Work unit.
With this function, an Action can be executed using information of an Event.

Information of an Event such as Job end time and event occurring computer, can be transferred to an
Action to be executed.

Completion

Event1

Notification

ActionAutomated execution

Transferring Event occurrence information to an Action.
For example, using this function, Job end time can be notified by an e-mail.
Information to be transferred is set at Action definition.

(1) Procedure of setting① Specify information to be transferred
When an Action is defined, specify the required Event occurrence information in the following format at any
position in Action execution information or Action execution parameter.

$Event ID．

SITENAME
OCCURDATE$OCCURTIMERESPONSE

Event ID: Specify Event ID of the Event whose information is to be transferred.
Keyword: Specify keyword for the requested Event occurrence information.
Event Occurrence information that are transferred to Action

Keyword

Description

SITENAME

Event occurring computer name

OCCURDATE

Date when the Event occurred

OCCURTIME

Time when Event occurred

RESPONSE

Event occurrence information② Relating to Work
A-AUTO/Event can transfer information of an Event to an Action that is defined in the same Work unit.
Event ID specified in ① and Action that refers to the transferred information must be registered in the same
Work unit.

11-10

11. Event Management(2) About symbols used in Event Occurrence information
If symbols representing Event Occurrence information (‘$’ ‘.’) are used as characters in the text of Action
execution information, precede the symbol with a \ (backslash).

①

In the case of '$':'$' is used to indicate start position and end position of Event Occurrence information.
If it is used for other than Event Occurrence information, precede it with \ (backslash) as '\$'. Otherwise, it is notinterpreted as a character.
Example: When an Event ID to be transferred is 'EVENT$'$EVENT\$.SITENAME $②In the case of '.':'.' is used as a separator between Event ID and keyword in Event Occurrence information. If it is to be used as acharacter in Event Occurrence information, precede it with a '\.'.

Example: When an Event ID of Event Occurrence information is 'ABC.EFG'$ABC\.EFG.SITENAME$
Example: When used in a character string 'ABC.EFG'
ABC.EFG$EVENT\$.SITENAME $③

In the case of '\':'\' is used as an escape character for '$' or '.' when these symbols are used as characters in Event Occurrence
information. If '\' is to be used as a character just before '$' or '.', use '\\' instead. In all other cases, '\' is recognized
as a character.
Example: When an action to be executed is 'C:\Program Files\$EVENT.SITENAME $.exe'
C:\Program Files\\$EVENT.SITENAME $.exe

11-1111. Event Management

11.4.2 Generating an Event utility
When this utility is executed, an Event (Application Event) occurs.

［Example］

In a batch Job (shell), specify the necessary environment information for this utility to be executed.

Windows
set APLKPARM = C:\Program Files\BSP\A-AUTO_Event\Parmset ARB_PARM = C:\Program Files\BSP\A-AUTO_Event\Parm

UNIX
APLKPARM = /bsp/A-AUTO_Event/parmexport APLKPARM
ARB_PARM = /bsp/A-AUTO_Event/parmexport ARB_PARM
BSPXLIB_XSYSTEM = /bsp/A-AUTO_Event/parmexport BSPXLIB_XSYSTEM
Notes
Underlined part depends on installation.
Above settings refer to settings for A-AUTO/Event at installation.
Do not insert any blank between variables and values.

(1) Defining shared library (In case of UNIX)Specify path of BSP shared library.
BSP shared library is in “/bsp/A-AUTO_Event/lib”.
(Note: Underlined part depends on installation of an Agent.)
Solaris
LD_LIBRARY_PATH =/bsp/A-AUTO_Event/lib
export LD_LIBRARY_PATHHP-UXSHLIB_PATH = XXX/A-AUTO_Event/lib
export SHLIB_PATH

11-12

11. Event Management

AIX
set ARB_PARM = C:\Program Files\BSP\A-AUTO_Event\lib［Example］ In a batch Job (shell), specify execution step of this utility.
Depending on the platform, specify the utility to be executed as described below.

Windows
Execute the following module at the appropriate place in the batch file.
AREVENT.exe∆Application event ID∆Application event parameter

UNIX
Execute the following command at the appropriate place in the shell script.
AREVENT∆Application event ID∆Application event parameter

Application event ID
ID for A-AUTO/Event to recognize the Event. Specify any character string. It may be
defined up to a maximum of 63 alphanumeric characters.
Notes
<

>

,

&

% “

‘ +

# katakana characters cannot be used.

Application event parameter
Additional information of the Event in addition to Application event ID. Specify any
character string.
It may be defined up to a maximum of 20 alphanumeric characters.

Notes< > , & % “ ‘ + # katakana characters cannot be used.

［Example］

For Application Event ID to be recognized as an Event, Event data should be defined in the EventManagement Master as follows.

11-13

11. Event Management

Item Name

Description

Event ID

Specify any character string.

Comment

Specify any character string.

Event Type

Application

Event occurring computer name

Agent Name of server in which this utility is executed.

Event Detail

Application event ID must match the above specification for
the utility execution.(Any character string)

Event detection parameter

Application event parameter must match the above
specification for the utility execution.(Any character string)(2) Occurrence Event information
In Event Occurrence information on 'Event detail' window, Application event ID is displayed.

11-14

11. Event Management

11.4.3 Monitoring log files utility
The specified log files in text format are monitored and appearance of specified characters in the log files isrecognized as an Event.

(1) Setting parameter file

［Example］

SetTarget parameter fileSpecify Agent name of the server where the log files to be monitored and the monitoring conditions files reside.
［Example］

Monitoring conditions fileIn this file, specify monitoring conditions for each log file. Specify file name of the Log File to be monitored and thecharacter string in the file to be detected.
Create one file for each Log File to be monitored. File name can be any name less than 255 letters.
WATCHINFO section
Keyword

RequiredSpecifiable value
or length

Description

FILENAME○

Up to 255 letters

Monitored Log File Name (Full path)(*1)
NAME[X] ※○(*2)

Up to 135 letters

Detecting conditions for character string(Starting position isStart column(*3),Character string(*4)

excluded.)
EVENTNAMEｎ

×

Up to 63 letters

Event Detail(*5)※ 1 Up to 63 letters if EVENTNAME is not specified.
※ 2 Letter X indicates sequential number starting from 1. Users can define multiple conditions by assigning
different number. If not specified, no detection and event will occur.
※ 3 Start column value can be specified as follows.
■ -1
■ 0

: Start column is not specified.
: From the first column■ ｎ(Any number) : ｎ column※ 4 Wild card can be specified for character string to be detected.
Example: AUT???E※ 5 n is specified by the consecutive number from 1.

11-15

11. Event Management

The same number as the number of WATCHTARGET which set up the conditions of the corresponding
detection character string is set up.
When not specifying EVENTNAME, a log file name serves as event detection information.

(2) Defining an Event
For Log File Name or EVENTNAME to be recognized as an Event, Event data should be defined in the
Event Management Master as follows.
Defining an Event for Monitoring log files utility

Item Name

Description

Event ID

Specify any character string.

Comment

Specify any character string.

Event Type

Application

Event occurring computer name

Agent Name of the server in which this utility is executed.

Event Detail

Monitored Log File Name (including path and extension)or EVENTNAME specified in Monitoring Conditions file.
(Up to 63 characters)

Event detection parameter-(3) Occurred Event information
In Event Occurrence information on 'Event detail' window, all characters written into the log file aredisplayed.

(4) Changing monitoring condition of log file
When changing monitoring conditions, change settings of parameter files or/and definition of the Event.
If parameter files are changed, restart of Monitoring Log Files utility is necessary.

11-16

11. Event Management

Example: Defining and occurring an Event of log file monitoring① Specify monitored Log File Name and character string to be detected in Monitoring Conditions file.
Target Log (This file name is specified in SetTarget parameter file.)
WATCHINFO:FILENAME=C:¥Log¥Log.txt
WATCHTARGET0 =-1,ERROREVENTNAME0 = Error*② Event Definition

Item Name

Description

Event ID

Specify any character string.

Comment

Specify any character string.

Event Type

Application

Event occurring computer name

Agent Name of server in which this utility is
executed.

Event Detail *Error

Event detection parameter-③ If following characters are written into the log file（C:\Log\Log.txt）, the Event occurs.

APPLICATION INTERNAL ERROR④ Confirm Event Detail of the occurred Event.
Contents on 'Event detail' window
Item Name

Description

Event ID

Specified character string.

Comment

Specified character string.

Event Type

Application

Event occurring computer name

Agent Name of server in which this utility is
executed.

Event Detail

Error

Event detection parameter-

Occurred Date

Date on the Event was detected

Occurrence TimeTime at the Event was detected

Event occurrence information

APPLICATION INTERNAL ERROR

11-17

11. Event Management

Notes※EVENTNAME is not mandatory.
If EVENTNAME is not specified in Monitoring Conditions file, specify log file name for Event Detail of Eventdefinition.(C:\Log\Log.txt in above example)

11-18

11. Event Management

11.4.4 Sending an mail utility
Sending an e-mail can be specified in an Action.
Notes
POPBeforeSMTP and an AuthSMTP protocol are not supported.

(1) Setting parameter files［Example］

Setting Send Information Parameter file

It is used to set up contents for sending e-mail. Each agent can have more than one parameter file.
Parameter files can be any name up to 16 characters and saved in the following folder.
C:\Program Files\BSP\A-AUTO_Event\parm\emlparm(Note: Underlined part depends on installation of the Agent)
SEND section
Specifiablevalue
or length

Keyword

Required

FROM_DOMAIN○

Sender's domain name

FROM_ADD○

Sender's e-mail address

FROM_NAME○

Sender's e-mail user name

TO_ADD○SUBJECT×

MESSAGE×

APPEND_PATHｎ(*)

×

Up to 1000
characters.

Description

Recipient's e-mail address
Subject of the e-mailMessage body of the mailAttached file name (Full path)* n indicates sequential number starting from 0.

11-19

11. Event Management(2) Defining Action
To send an e-mail, define Action data in the Event Management Master.
Input items for Action when using Sending an e-mail utility
Item Name

Description

Action ID

Specify any character string.

Comment

Specify any character string.

Action Type

Send Mail

Action executing computer name

Agent Name of server in which this utility is executed.

Action execution information

C:\Program Files\BSP\A-AUTO_Event\Bin\aremlsend.exe(Note: Underlined part depends on installation of the Agent)

Action execution parameter

Send Information Parameter File (Up to 16 characters)

11-20

11. Event Management(3) Replacing sending message
Contents specified in Send Information Parameter file can be replaced using keywords.
With this function, contents in sending e-mail can be changed without having to edit the parameter filemanually.

［Example］

Specify $keyword$ at any place in Send Information Parameter file.*A keyword can be up to 16

characters.
［Example］

Replacing information should be specified after the Send Information File name as follows.
Send Information Parameter File; keyword=value[;keyword=value…]
keyword: Any characters specified as a keyword in Send Information Parameter file. (Up to 16 characters)
value: Replacing information for the keyword in Send Information Parameter file. (Up to 256 characters)* More than one keyword=value can be specified, separated by ';'.

11-21

11. Event Management

Example: Replacing contents of e-mail using keywords① Specify keyword in Send Information Parameter file.
EMAILINFO01//A-AUTO/Event MAIL INFO FILE
SEND :
FROM_DOMAIN = BSP00428
FROM_ADD= t_bsp@bsp.co.jp

FROM_NAME= “Bsp Tarou”

TO_ADD= john@bbc.com

SUBJECT= “End of Job”

MESSAGE= “Job FINA1010 ended at $TIME$. from ITS Div.”APPEND_PATH0 = AAAAA\BBBB\CCCC② Specify replacing value of the keyword for Action execution parameter.
Item Name

Description

Action ID

Specify any character string.

Comment

Specify any character string.

Action Type

Send mailAction executing computer name

Agent Name of server in which this utility is
executed.

Action execution information

C:\Program Files\BSP\A-AUTO_Event\Binaremlsend.exe

Action execution parameter

EMAILINFO01;TIME=10:30③ An e-mail message is modified by the value specified for Action execution parameter and sent.

11-22

11. Event Management(4) Sending an e-mail of Event occurrence information
To send an e-mail with replacing information from Event Occurrence information, when an Event occurred［Example］

Specify $keyword$ at places in Sending Information Parameter file, where Event occurrence information

is to be inserted.*A keyword can be up to 16 characters.
［Example］

Specify Action execution parameter as follows.
Send Information Parameter File name;keyword=$EventID.EventOccurence keyword$

Example: Inserting Event Occurrence Time into a message body.
① Specify keyword in Send Information Parameter file.
EMAILINFO01//A-AUTO/Event MAIL INFO FILE
SEND :
FROM_DOMAIN = BSP00428
FROM_ADD= t_bsp@bsp.co.jp

FROM_NAME= “Bsp Tarou”

TO_ADD= john@bbc.com

SUBJECT= “End of Job”

MESSAGE= “Job FINA1010 ended at $TIME$. from ITS Div.”APPEND_PATH0 = AAAAA\BBBB\CCCC② Specify keyword, Event ID, and replacing item for Action execution parameter.
Item Name

Description

Action ID

Specify any character string.

Comment

Specify any character string.

Action Type

Send Mail

Action executing computer name

Agent Name of server in which this utility is
executed.

Action execution information

C:\Program Files\BSP\A-AUTO_Event\Binaremlsend.exe

Action execution parameter

EMAILINFO01;TIME=$EVENT01.OCCURTIME$

11-23

11. Event Management③ TIME keyword in an e-mail message is replaced by the Event Occurrence Time and the e-mail message
is sent.

11-24

Optional Products

12. User Interface

12

User Interface

12.1

Network End Exit

(1) Overview
Network End Exit (neex) is an interface to pass Network completion information to a user written exit
program (autonend). When a Network completes, Network End Exit (neex) initiates autonend and passes
Schedule Date, Network ID, Network End Code and Job Library ID to it.

A-AUTO for UNIX/Windows

Network End Exit

User Exitneexautonend(able to edit)

the information
when Network
End

NetworkEnd

information

Overview Figure(2) Information passed to the Exit
Argument 1
Argument 2
Argument 3

Argument 4

Schedule Date
Schedule Date of End Network
Network Name
Network Name of End Network
End Code
End Code of End Network:
00 Normal End
04 Cancel
08 Abnormal End of Shell Script Error and Remote impediment
12 Abnormal End
Job Library ID
Job Library ID of End Network

Create User Exit with necessary function to perform operations based on this information. You can
incorporate any function.

12-1

12. User Interface(3)How to Use■ In A-AUTO for UNIX
System Parameter setting
Set NEP_NEEXON as follows. (You can set it using [Settings of Monitor] page of [System Management]
Windows on Web Client )NEP_NEEXON = 1
It is necessary to read file again after updated System parameter.(The specify can be from Monitor
Monitoring page on Web Client.)
Create User Exit(autonend)
Create User Exit (autonend) in bin directory of home directory of A-AUTO Monitor.
(Refer to [Sample for User Exit] on the following page.)
Set the Permission of User Exit
Please change the permission of autonend created into more than 500. Change Owner and Group to be
the same as those for A-AUTO Monitor.
-r-x------

1 autobsp

445 Apr 7 13:54 autonend

Start Network End Exit(neex)
To use this function, it is necessary to start Network End Exit(neex) as resident process. After A-AUTO
Monitor has started, enter the following command to start Network End Exit(neex).

Once autonend iscreated, Network End Exit(neex) will automatically initiate autonend whenever a Network ends. (Log output
destination is optional)
In the case of using csh shellneex∆>&∆/aaa/bbb/ccc/neex.log∆&
In the case of using ksh or sh shellneex∆>∆/aaa/bbb/ccc/neex.log∆2>&1 &12-2

12. User Interface

Stop Network End Exit(neex)
Use kill command to stop Network End Exit(neex).
ps∆-ef | grep∆neex
auto 87018 102068
kill∆87018
(1)0 16:10:03 pts/26 0:00 neex

Please use process number (1) of Network End Exit(neex) as the parameter for kill command.


Even if Network End Exit(neex) is stopped while A-AUTO Monitor is active, there will be no impact tothe operation of A-AUTO Monitor.

Once Network End Exit(neex) is stopped, autonend will not be initiated.

Sample for User Exit
autonend sample when using csh
setenv SDATE$1
Assigned Schedule Date of the end Network to a variable SDATE.
setenv NETWORK $2
 Assigned Network Name of the end Network to a variable NETWORK.
setenv RC$3
 Assigned End Code of the end Network to a variable RC.
echo "### ARG1("$1") ARG2("$2") ARG3("$3") ###"
switch($RC)
Judge End Code of Network.
case '00'
 End Code from 00 and the process when normal end.
echo "NETWORK NORMAL END(AUTONEND)"
Output message of normal end.
default
The process of abnormal end.
echo "NETWORK ABNORMAL END(AUTONEND)" Output message of abnormal end.
setenv NET_PREFIX `echo $NETWORK |cut -c0-5`
 Gain the first 5 byte of Network name from argument
NET_PREFIX.
switch($NET_PREFIX) Determine the name of the prefix of the network namecase 'KEIRI' for example, he first 5 byte of Network name is LEIRI
echo “Network Abnormally end !!!“
echo “Call the person in charge please. Inner line number(.xxx)“
default
 Processing other than KEIRI.
endsw
endsw
exit

12-3

12. User Interface

autonend sample when using ksh#!/bin/ksh#!/bin/sh
SDATE=$1
 Assigned Schedule Date of the end Network to a variable SDATE.
NETWORK=$2
 Assigned Network Name of the end Network to a variable NETWORK.
RC=$3
 Assigned End Code of the end Network to a variable RC.
Echo
echo "### ARG1("$1") ARG2("$2") ARG3("$3") ###"
case $RC in Judge End Code of Network.
'00')
 End Code from 00 and the process when normal end.
echo "NETWORK NORMAL END(AUTONEND)"
 Output message of normal end.
;;*) Output message of abnormal end
echo "NETWORK ABNORMAL END(AUTONEND)"
 Output message of abnormal end
NET_PREFIX=`echo $NETWORK |cut -c0-5`  Gain the first 5 byte of Network name from argument
NET_PREFIX
case $NET_PREFIX in Determine the name of the prefix of the network name
'KEIRI') for example, he first 5 byte of Network name is LEIRI
echo “Network Abnormally end !!! “echo :Call the person in charge please. Inner line number(.xxx)”;;*)
 Processing other than KEIRI.
;;
esac
;;
esac
exit

12-4

12. User Interface■ In A-AUTO for Windows
Create User EXIT(autonend.bat)
Create User Exit (autonend.bat) in bin directory of home directory of A-AUTO Monitor. Usually specify as
the following.
C:\bsp\auw\bin\autonend.bat
Start Network End Exit (neex)
To use this function, it is necessary to start Network End Exit(neex) as resident process. After A-AUTO
Monitor has started, double click the following execution file to start Network End Exit (neex). Once
autonend is created, Network End Exit (neex) will automatically initiate autonend whenever a Network
ends..
C:\bsp\auw\bin\neex.exe
Stop Network End Exit(neex)
Close the Windows of Network End Exit (neex) startup to stop Network End Exit(neex).
Even if Network End Exit(neex) is stopped while A-AUTO Monitor is active, there will be no impact tothe operation of A-AUTO Monitor.

Once Network End Exit(neex) is stopped, autonend will not be initiated.

12-5

12. User Interface

Sample for User Exit

autonend.bat sample@echo offecho ### ARG1(%1) ARG2(%2) ARG3(%3) ###if "%3" == "00" goto ret00_proc
goto not_ret00_proc

Check End Code

:ret00_proc
echo NETWORK NORMAL END(AUTONEND)
goto all_end

 Output message of normal end.

:not_ret00_proc
echo NETWORK ABNORMAL END(AUTONEND) Output message of abnormal end.
if "%2" == "KEIRI" goto KEIRI_proc
 Gain the first 5 byte of Network name from argument
NET_PREFIX.
:KEIRI_proc
echo Network Abnormally end !!!
echo Call the person in charge please.
goto all_end:all_end
exit

Inner line number(.xxx)

12-6

12. User Interface(4) Start ServerThis utility can be used to register a service from Ver4Lv06.
To register Network End Exit (neex) as a service, use REGSVC.EXE in .. ¥BSP¥COMMON.

System Parameter
When Network End Exit (neex) is started as a service, even if the System Parameter NEEX_JOBLOGON
is set to ‘0’, it will still create a Job Log for autonend, each time it is initiated. Job Logs of autonend arestored in the directory specified in the System Parameter NJP_JOBLOGDIR.
The

file

name

of

the

Job

log

will

be

in

this

format,[NEEX_JOBLOG_PREFIX(Systemparameter)+.+Network ID+.+Schedule Date+.+Network Start Time+.+RC]
E.G.: NEEX.BSPSTA.20030329.123456.04

12-7

12. User Interface

12.2

Network Start Exit

(1) Overview
Network Start Exit (autonint) is a User Exit that will be initiated by A-AUTO Monitor before a Network in
Network Queue is started. If autonint returns a value of 8 for return code, A-AUTO Monitor suspends
starting the Network and assigns a Hold Wait to the Network. To use autonint, create a batch fileautonint.bat or script file autonint, and store it in bin directory of home directory of A-AUTO Monitor. You
can incorporate any function in the batch or script file.

About to Start Network for
execution

A-AUTO Monitor

User Exit

NCP
autonint(able to edit)
NetworkQueue

If the return code value of autonint is[8], A-AUTO Monitor suspends
starting of the Network and assigns a
Hold Wait to it.

(2) limitation
Between autonint starts and terminates processing, the operation of A-AUTO Monitor will be stopped
during that duration.
The operation of A-AUTO Monitor cannot be assured during this duration.

(3) Return Value
Return Code value from autonint will determine the processing of A-AUTO Monitor as follows.
8

Suspends the starting of the Network and assigns a Hold Wait to the Network.

apart

Continue with the processing for the Network.

from 8(4) System Parameter
NCP_AUTONINTON
If set to be 1, initiate autoninit. If set to be 0, do not initiate autoninit.

12-8

12. User Interface

NCP_AUTONINT_DEFCHARThe System Qualifier and Network User Field attributes are not the mandatory items when a Network is
registered into Network Master. If either of these items is blank, this value of this System Parameter will bepassed in the item when autoninit is initiated. Specify the value (1 character) to be passed in the item. The
default is [@].
You can set System Parameter using [Settings of Monitor] page of [System Management] Windows.

(5) Information passed to the Exit
No.

Item

Long

0

Full path of autoninit

256

1

Network Name

82

Execution Type *1

1

Content

N:Normal Type
R: Rerun Type
A:Normal Rerun Type
F:Force Type

3

Network Class

1

4

Hold Attribute

1

Y:Yes
N:No

5

Data Wait Attribute

1

Y:Yes
N:No

6

Start Time Wait Attribute

1

Y:Yes
N:No

7

Parallel Run Attribute

1

Y:Yes
N:No

8

Network Partition Number

3001~255

9

Network Start Date

8

CPU Date(YYYYMMDD)

10Network Start Time

6

CPU Time(HHMMSS）

11

System Qualifier *2

812Monitor ID

8

13

Schedule Date

8

14

Network User Field *2

1215

Job Library ID

1

YYYYMMDD

0~9*1 Execution Type If conditions match more than one type, the run type is determined by using the following
priority.
Normal Rerun Type(A) > Force Type(F) > Normal Type, Rerun Type(N or R)*2 Network User Field
If System Qualifier or Network User Field is not specified in Network Master, a character specified in System
Parameter NCP_AUTONINT_DEFCHAR is passed.

12-9

12. User Interface

autonint sample■ In A-AUTO for UNIXecho "Start AUTONINT"
echo 0 $0echo 1 $1echo 2 $2echo 3 $3echo 4 $4echo 5 $5echo 6 $6echo 7 $7echo 8 $8echo 9 $9shiftecho 10 $9shiftecho 11 $9shiftecho 12 $9shiftecho 13 $9shiftecho 14 $9shiftecho 15 $9echo "End AUTONINT"
exit 012-10

12. User Interface

Output sample
Start AUTONINT
0 /BSPT1/TEST00/bin/autonint1 BSPSTA2 N3 A4 N5 Y6 N7 N8 0019 2004041610 02135911 UNIX0112 AUTO5513 2004041614 @15 0End AUTONINT

12-11

12. User Interface■ In A-AUTO for Windows@echo offecho Start AUTONINT
echo 0 %0echo 1 %1echo 2 %2echo 3 %3echo 4 %4echo 5 %5echo 6 %6echo 7 %7echo 8 %8echo 9 %9shiftecho 10 %9shiftecho 11 %9shiftecho 12 %9shiftecho 13 %9shiftecho 14 %9shiftecho 15 %9echo End AUTONINT
exit

12-12

12. User Interface

Output sample
START AUTONINT
0 C:\BSP\AUW\BIN\autoninit.bat1 BSPSTA2 N3 A4 N5 Y6 N7 N8 0019 2004041610 02135911 UNIX0112 AUTO5513 2004041614 @15 0End AUTONINT

12-13

13. Remote Job Execute Function

13 Remote Job Execute Function※Remote Job Execute Function is supported by an optional product, A-Remote. A-Remote is available ondifferent platforms.
The following table shows the optional product name for each platform.
Platform

License nameName in this manual

UNIX

A-AUTO for UNIX Remote License

A-Remote for UNIX

Windows

A-AUTO for Windows Remote License

A-Remote for Windows

System i

A-AUTO for OS400 Remote License

A-Remote for System i

For information on Remote Job Execute function (System i), refer to “14 Remote Job Execute function (Systemi)”.

13.1 Settings for Job Execution

13.1.1 Setting System Qualifier
In Network Master, System Qualifier is specified for each Network. A-AUTO Monitor uses the System
Qualifier of a Network to determine on which computer, local or remote, Jobs in the Network are to be
executed.
Relationship between a System Qualifier and a Remote system may be defined using [System Qualifier
List] pane of [System Management] Windows.
※Local environment : A-AUTO Monitor has been installed in the environment※Remote environment : Remote Job Execute Function has been installed in the environment13-1

13. Remote Job Execute Function(1) Defining System Qualifier.
Define relationship between a System Qualifier and a Remote system.
[List Menu]- [Monitor] -[System Qualifier] of [System Management] Windows. [System Qualifier List] pane
is displayed. Click [Create] button or a System Qualifier Name link to display [System Qualifier Detail]dialog as shown below.

① System QualifierThis is a System Qualifier ID. ID specified must be less than 8 alphanumeric characters of capital letters.

② Information Type
Select the Information Type of A-Remote.
If the version of the A-Remote is V722 or later.
A-REMOTE for Windows/Linux/UNIX (V722 After.)If the version of the A-Remote is V710 –V721.
A-REMOTE for Windows/Linux/UNIX (V710 –V721.)
If the version of the A-Remote is V700 or before
A-REMOTE for Windows/Linux/UNIX (V700 or before)③ Load Information
Specify whether load information is to be obtained. If you want to obtain load information, please check thecheck box.

④ Host Name (IP Address)
Specify TCP/IP Address, which must be between 10 to 16 alphanumeric characters⑤ Port No
Specify TCP/IP Port number used to communicate with A-AUTO Monitor.

13-2

13. Remote Job Execute Function

Example: Setting System Qualifier
System Qualifier:RWINNT01

Host Name:RWINNTREMOTE01

Port No:9999① Click [Create] on [System Qualifier List] Windows.
② [System Qualifier Detail] dialog is displayed.

③ Enter the required information.


System Qualifier:

Information Type:

Host Name:Port No: Enter 9999

Enter RWINNT01

A-REMOTE for Windows/Linux/UNIX(V722 After)
Enter RWINNTREMOTE01④ Click [Apply].
⑤ Entered information is registered.

Note

Do not specify System Qualifier for Networks that are to be executed by A-AUTO Monitor itself.

The specified host name must be defined in hosts file of the server where A-AUTO Monitor resides.



System Qualifier information may also be registered by parameter file, SYSQCONF. For details, refer
to “3.7.6 Settings for SYSQCONF File” in System Administrator's Guide.

13-3

13. Remote Job Execute Function

13.1.2 Setting System Parameter
To use A-Remote, it is necessary to set the following System Parameters.
Parameter settings may be changed using [Settings of Monitor] window.
Please refer to “9.3.1 Settings of Monitor”.

(1) A-AUTO Monitor side
NJP_REMON
This specifies whether A-Remote is used. ’1'

indicates the function is used. ‘0' indicates it is not used.

‘0’ : not used.
‘1’ : used.
NJP_MONITORDOWN_CANCEL
If communication between A-Remote and the A-AUTO Monitor is disconnected, specifies whether or not tocancel the remote job that is running. The initial value set by installation is1 (cancel).
0 : Allows Job to complete execution without canceling the job running in the A-REMOTE.
1 : To cancel the job that is running on the A-REMOTE.

(2) A-Remote side
NJP_LISTENPORT
This specifies TCP/IP port on A-Remote side that is used when A-AUTO Monitor is communicating with
A-Remote. Specify the value for this parameter must be the same as the port number specified in
SYSQCONF file of A-AUTO Monitor. Make sure to assign the TCP/IP port that is not used by any otherproducts.
MCP_MAXJPSMCP_MAXNPSMCP_MAXTMRQ
The initial value of this parameter is set to UNIX version only. the setting same value as the parametername in the A-AUTO Monitor side. Please remove the parameter.
※By setting to match the settings of the A-AUTO Monitor the values of the above parameters , reduce theuse of shared memory can be expected.

13-4

13. Remote Job Execute Function

13.2

Starting and Stopping Remote System

13.2.1 Starting Remote Job Execute Function(UNIX)
You may start Remote Job Execute Function (UNIX) using the following procedure.
Starting Remote Job Execute Function (UNIX)
armtux△&
The following messages will be output during startup.
% armtux &AUX916I A-REMOTE(V7.2.2.00) STARTED
AUX010I INITIALIZING ArmtUX ...
AUX012I INITIALIZING ArmtUX SUCCESSFUL
armtux start failed
If the following message is output, starting of armtux fails. Check the possible cause of the problem.
AUX016W FUNCTION CALL Socket() FAILED AT ArmtUX DUE TO 125
・Port is occupied
Please check whether the port specified as NJP_LISTENPORT is being used. Use " netstat-a " command to

perform the check.
AUX975E THE SHARED MEMORY OF A-REMOTE IS ALREADY BEING USED・armtux has been started already
Please check whether armtux is already started in the server by using " ps-ef | start user name" command.

13.2.2 Ending Remote Job Execute Function(UNIX)To end or terminate Remote Job Execute Function (UNIX), use kill command.
The following messages are output during the termination and armtux stops processing. Please check that theshared memory which armtux uses does not remain by using ipcs command after stopping armtux with the killcommand.
armtux uses the shared memory with key 0x7f0000xx.
xx is the hexadecimal value of the 2-digit Monitor ID specified in MESSAGES_AUTOPROC.
% ps -ef | grep armtux
auto 28065 25724 0 18:15:19 pts/0 0:00 armtux% kill 28065% AUX026I PROCESS ArmtUX TERMINATED[1]
1
armtux End% ipcs13-5

13. Remote Job Execute Function

13.2.3 Starting Remote Job Execute Function(Windows)
Remote Job Execute Function (Windows) can be started either as a service or as a console application.
Please select a suitable method for your environment.
When using the Switch Job Execution User ID Function,
it is necessary to start A-REMOTE as a service.

(1) Starting from command prompt
To start A-Remote for Windows on command prompt, execute ARMTNT.EXE under the directory where
A-Remote for Windows is installed. In this case, messages from A-Remote for Windows are output to theconsole of command prompt.
armtnt

C:\BSP\ARMTNT>armtnt
AUX916I A-REMOTE(V7.2.2.00) STARTED
AUX010I INITIALIZING ArmtUX ...
AUX012I INITIALIZING ArmtUX SUCCESSFUL

13-6

13. Remote Job Execute Function(2) Starting as a service
Open [Services] dialog of Control Panel and confirm armtnt is listed. Click on [Log On] tab of [Properties] ofarmtnt, select [This account] and specify Account name and password.
※Please select an account with Administrators authority.

Please start in either of the following ways:
・To start manually from the Services dialog.
・By service type, the service type is set as "automatic", and is automatically started at PC start..
・Started from the command line.

13-7

13. Remote Job Execute Function

13.2.4 Ending Remote Job Execute Function (Windows)
To stop A-Remote for Windows, type Ctrl+C, or click ‘X’ on armtnt command Windows.
C:\BSP\ARMTNT>armtnt
AUX916I A-REMOTE(V7.2.2.00) STARTED
AUX010I INITIALIZING ArmtUX ...
AUX012I INITIALIZING ArmtUX SUCCESSFUL
AUX026I PROCESS ArmtUX TERMINATED
C:\BSP\ARMTNT>

13.3

Job End Code
When a Job ends at A-Remote side, exit code of the Job is returned to A-AUTO Monitor.
The exit code is displayed under Code column on the output of log0 utility.

A-AUTO

V7.2.2.00
PAGE 1
DATE:2011/12/20 TIME:17:30:31(C)Copyright BSP INC. 1994
OPERATION DATE:11/12/20
RC CODE C T ST-DATE START END
ELAPSE******* NETWORK LOG LIST ******NETWORKGROUPID JOBNAME
LID RSYSQ
USER-ID
BSPSTAGRP01
BSPSTA01 00
A N 11/12/20 172932 172933
AUTOUSR
BSPSTAGRP01
BSPSTA02 00
A N 11/12/20 172933 172933
AUTOUSR
OLTM01
GRP01
OLTM0101 00
A N 11/12/20 172956 172957
0.01
OLTM04GRP01
OLTM0401 12 0030 A N 11/12/20 173002 173003
0.01
OLTM02
GRP01
OLTM0201 08 0002 A N 11/12/20 172957 173018
0.21****** END OF PRINT ******

CPU

SDATE

0.01

0.030 11/12/20

0

0.00

0.010 11/12/20

00.010 11/12/20 00.070 11/12/20 00.000 11/12/20 0

LB01
LB02

However, if a Job cannot be initiated in A-Remote, the Job End Status is set to 8, and this error code isdisplayed on Code column.
For contents of the "CODE", Please refer to "■ log0 utility " in the " Operation Guide ".

13-8

13. Remote Job Execute Function

13.4

System Log
System log Is a log recording of all messages output by the A-REMOTE.
A-REMOTE output a system log by the file name (here, referred to as armtrace.log) define in the
AUTO_TLOG_FILE parameter. "X", "Y", and "Z" are added to this file defined in the parameter. The actual
physical file names are armtrace.logX, armtrace.logY, and armtrace.logZ. ( The file, armtrace.logZ, is a tracelog output for internal use only.).
If armtrace.logX exceeds the maximum allowable number of records specified for AUTO_TLOG_MAXLINE
parameter, logging will be switched to write to armtrace.logY. Similarly when armtrace.logY exceeds maximum
allowable number of records, armtrace.logX is cleared and logging is written to armtrace.logX.
Since armtrace.logX and armtrace.logY are the files of text format, any editor can be used to view it.

13-9

13. Remote Job Execute Function

13.5

Remote Job Cancellation at the Time of an A-AUTO Monitor Problem
This section explains the possible setup and the action taken for A-Remote Jobs when a problem occurs at
A-AUTO Monitor and the session between the remote environment and the A-AUTO Monitor is disconnected.
(The explanation is valid for A-AUTO for UNIX/Windows V710 Lv15 or later.

Remote Job Cancel
The default setting, for the action to be taken for A-Remote Jobs when a problem occurs at A-AUTO Monitor
and the session between the remote environment and the A-AUTO Monitor is disconnected, is to cancel all
executing Jobs at A-Remote.

If it is required to change this setting to allow the executing Jobs at A-Remote

to complete their processing, refer to the following procedure.

Setup Steps of the Remote Job Control of an A-AUTO Monitor Problem
Use [Monitor Edit] dialog of [System Management] Windows of the Web client.
( For details about [Monitor Edit] dialog, refer to "9.3.1 Settings of Monitor")
In order to reflect the change in Monitor Settings, it is necessary to restart A-AUTO Monitor.
Please check that there are no networks executing.

①"System Management" is clicked from [A-AUTO Main] Windows (screen immediately after login).

②

Click the "Monitor" from the [ List Menu].

③

Click Monitor ID link of the target A-AUTO Monitor on [Monitor List] screen, "Monitor Edit" screen isdisplayed④

Click the “ Monitor Settings " from the [List Menu] of Monitor Edit dialog.

⑤

Select the "Remote Job" from the tree on the left side of the screen.
On the right side of the screen , the item of "Remote Job " section will be displayed.

⑥

The value of "existence of the remote job cancellation at the time of a monitor obstacle" is changed.
0 : Not cancel jobs running in the A-REMOTE.
1 : To cancel jobs running on the A-REMOTE.

⑦

Click the “Apply” button.

The parameter file "auto_sysconf" can be edited and it can also change similarly.
①

auto_sysconf open the file.

②

To change the following parts of remote section.

NJP_MONITORDOWN_CANCEL
0 : Not cancel jobs running in the A-REMOTE.
1 : To cancel jobs running on the A-REMOTE.
Then, restart the A-AUTO Monitor.

13-10

13. Remote Job Execute Function⑧

Click the [ A-AUTO Monitor] from the main screen.

⑨

Monitor ID is selected from "monitor list" screen, "monitor detail " screen is displayed.

⑩

click the [Stop] button from the [Running Status] -[monitor detail] screen.
The message "by which demanded processing was performed correctly" is displayed.

⑪[Start] Click a button and it starts an A-AUTO Monitor.
The message "by which demanded processing was performed correctly" is displayed.

A setup of the remote job control by the above of operation is completion.

13-11

13. Remote Job Execute Function

13.6
A-REMOTE Job Outcome Management at the Time of Communication
Unusual Detection
This function is offered by A-REMOTE after V722.

(1) Function overview
When a job that is instructed by A-AUTO Monitor to be executed at an A-Remote has completed, A-Remote willtransmit Job End Notification to A-AUTO Monitor. If it fails to send Job End Notification to the A-AUTO Monitor
because of some problems, such as A-AUTO Monitor was shutdown or there was some communication failure,
A-REMOTE will record the information about this job into the file described below. When automatic recovery bya remote job recovery function (described later) is not used, the execution result and status of a job can bechecked by using this file.
Job Execution Status File (jobstatus.log)
The information on the remote job which transmission of during execution or execution result has not completed
is recorded. This file is used by the remote job recovery function mentioned later and a session recovery
function. In these functions, the contents recorded on this file are updated to the following timing.
When the session was re-established and it succeeds in transmission of the notice of the end of a job
on an A-AUTO monitor, the information on the remote job is deleted.



If received job section number with job execution request from A-AUTO Monitor session.
The information on the remote job of relevance is moved to the notice error log file of the end of a job.

A-REMOTE restart
All the information on the recorded remote job is moved to the notice error log file of the end of a job.

13-12

13. Remote Job Execute Function

Job End Notification Error Log File (jnotifyerr.log)
The information on the remote job that A-Remote was not able to transmit the Job End Notification to an A-AUTO
Monitor is recorded. The remote job whose information was recorded on this file is treated as an aborted job by
A-AUTO Monitor. Automatic recovery by a remote job recovery function (described later) cannot be performed.
※Job End Notification Error Log file supports file generation.
When the number of records in the current error log file reaches the maximum number of records specified in the
RCVY_JOBENDLOG_MAX parameter, the file name of the current error log file will be changed to "jnotifyerrXX.log"(XX is a generation number). A new jnotifyerr.log file is then created and error log will be recorded into this new file.
The number of file generation is specified in RCVY_JOBENDLOG_GEN parameter.
2 Generation management for a generation is performed（RCVY_JOBENDLOG_GEN = 2）
① The number of records reached the maximum

jnotifyerr.logjnotifyerr
01.logjnotifyerr
02.log⑤Creat④Renamejnotifyerr.log③Renamejnotifyerr
01.log②Deletejnotifyerr
02.log

The above file is output in the directory specified by the system parameter RCVY_JOBLOG_DIR.

13-13

13. Remote Job Execute Function(2) The view of a Job Execution Status File(jobstatus.log)

Job execution status file is output in the following format..
(1) (2)

(3)

(4)

(5)

(6)

(7)

(8)

(9)

(10) (11)(12)
001 NET03

20111129TERMINATE

00 0000

002 NET101

20111129TERMINATE

00 0000

003 NET102

20111129TERMINATE

00 0000

8156 NET0301 20111129/203724 20111129/203810 20111129/203912 JOB

6340 NET10101 20111129/203724 20111129/203810 20111129/203912 JOB

9700 NET10201 20111129/203724 20111129/203810 20111129/203913 JOB

No

Item

Place

Size

Explanation

1

Job partition number

1

3

Job partition number

2

Network ID

5

8

Network ID that Job belong to3

Schedule Date

14

8

Schedule Date

4

Process ID

23

10

The process ID of the job runningthe case before generation of a process "----------“ It is displayed as ".

5

Job Code34

8

The job name of an object job

6

Execution start date

43

15

Start date and time of Job execution in the A-AUTO Monitor(Monitor side)
7

Execution start date

(YYYYMMDD/HHMMSS)
59

15(Remote side)
8

Execution end date

Start date and time of Job execution in the A-REMOTE(YYYYMMDD/HHMMSS)

75

15(Remote side)

End date and time of Job execution in the A-REMOTE(YYYYMMDD/HHMMSS)
It is displayed "-------- /--------" when job is running.

9

10

StatusEnd status

91

107

15

2

Job status


EXECUTE : Running

JOB TERMINATE: Normal

JOB ABENDED: AbendedJOB CANCEL: Abended (cancel)



SCRIPT ERROR: Abended (script error)



FAILED TO LOGON : Abended (user login failed)

End status
It is displayed "--" when job is running.

11

Job end code110

4Job end code
It is displayed "----" when job is running.

12

Reserve

114

5(Not used)13-14

13. Remote Job Execute Function(3) The view of a Job End Notification Error Log File (jnotifyerr.log)
Job end notification error log file is output in the following format.
(1)

(2)

(3) (4)(5)(6) (7)

(8)

(9)

(10)

(11)

(12)(13)(14)20111129 162923 001 NET02

20111129 2158 NET0201 20111129/162745 20111129/162736 20111129/162806 JOB TERMINATE 00 0000

20111129 163831 001 NET03

20111129 3728 NET0301 20111129/163655 20111129/163645 20111129/163716 JOB TERMINATE 00 0000

20111129 164822 001 NET04

20111129384 NET0401 20111129/164659 20111129/164645 20111129/164615 JOB TERMINATE 00 0000

No

Item

Place

Size

Explanation

1

Date

1

8

Date the record was written (YYYYMMDD)

2

Time

10

6

Time the record was written (HHMMSS)

3

Job partition number

17

3

Job partition number

4

Network ID

21

8

Network ID that Job belong to

5

Schedule Date30

8

Schedule Date

6

Process ID

39

10

The process ID of the job runningthe case before generation of a process "----------“ It is displayed as ".

7

Job Code50

8

The job name of an object job

8

Execution start date

59

15

Start date and time of Job execution in the A-AUTO Monitor(Monitor side)
9

Execution start date

(YYYYMMDD/HHMMSS)
75

15(Remote side)
10

Execution end date

Start date and time of Job execution in the A-REMOTE(YYYYMMDD/HHMMSS)

91

15(Remote side)

End date and time of Job execution in the A-REMOTE(YYYYMMDD/HHMMSS)
It is displayed "-------- /--------" when job is running.

11

12

StatusEnd status

107

123

15

2

Job status


EXECUTE : Running

JOB TERMINATE: Normal

JOB ABENDED: AbendedJOB CANCEL: Abended (cancel)



SCRIPT ERROR: Abended (script error)



FAILED TO LOGON : Abended (user login failed)

End status
It is displayed "--" when job is running.

13

Job end code

126

4

Job end code
It is displayed "----" when job is running.

14

Reserve

130

5(Not used)13-15

13. Remote Job Execute Function

13.7

Remote Job Recovery Function
This function is available for A-Remote used in conjunction with the A-AUTO Monitor V722 or later.
When this function is used, the KeepAlive function is automatically enabled. The function that performs
cancellation of remote jobs when a session failure is detected will be set to “not to cancel remote jobs”(1) Functional overview
When the A-AUTO Monitor is restarted after A-AUTO Monitor system down, it re-establishes the A-AUTO
Monitor’s session with A-REMOTE. Any remote jobs which were running just before A-AUTO Monitor systemdown are then recovered.
For automatic recovery, it obtains the current execution status of jobs, which were running on A-REMOTE, fromthe A-REMOTE.
With this function, users no longer need to perform the recovery processing manually when the A-AUTO Monitor
is down and this reduces the recovery time required.
However, the remote jobs will be treated as abnormally ended, if session with A-REMOTE cannot be
re-established in the number of retry time specified by (NJP_CONNRETRY) parameter.
The status of the Networks that have jobs running in A-Remote will be “running” until a new session isre-established.

Remote Job Recovery example
This illustration shows the execution situations of the following jobs when A-AUTO Monitor down.
A-AUTO Monitor

A-REMOTE1

Network

RJOB011

Running

RJOB021

Running

RNET01
Remote Job
RJOB011

Running

RJOB012

Running Wait

RJOB021

Running

jobstatus.log FileRJOB011：Running
RJOB021：Running

RNET02

A-REMOTE2

RNET03
RJOB031

RJOB031

Running

Running

jobstatus.log FileRJOB031：Running

LNET10Local Job
LJOB011

Running

Remote Job Recovery Function is ON

13-16

13. Remote Job Execute Function

When the Remote Job Recovery function is on, get the execution status of Jobs which is running on A-REMOTE.
Treat the Job and Network, which is running on A-AUTO Monitor, as ABEND.

A-AUTO Monitor

A-REMOTE1
Execute RJOB012 after
RJOB011 normal end
RNET01 running

RNET01RJOB011

STT :Normal End

RJOB012

STT :Running

RJOB021

Normal End

RJOB012

Running

RJOB021

Running

RecordretrieveRJOB021 Running
RNET02 Running

RNET02RJOB011

jobstatus.log FileRJOB011：Normal End

STT :Running

RJOB012：Running
RJOB021：Running

RJOB031 Abended,
Job is inexistence,
RNET03 Abended

RNET03

RJOB031

A-REMOTE2

STT :Abended
retrieveRJOB031
Job abended in local,
Linet10 abended(cancel)

LNET10Abendedjobstatus.log FileRJOB031：Abended

LJOB011

STT :Abended

13-17

13. Remote Job Execute Function

Remote Job Recovery Function is OFF
When this function is off, the system will cancel all the running Networks (Jobs), regardless of whether they are
run on A-AUTO Monitor or A-Remote, and treat them as ABEND.

A-AUTO Monitor

A-REMOTE1
All
NetworkAbended

RJOB011

Normal End

RJOB011

STT :Abended

RJOB021

Running

RJOB012

STT:Execute wait

RNET01

Recordjobstatus.log FileRNET02RJOB011:Normal End
RJOB021：Running
RJOB021

STT :Abended

RNET03A-REMOTE2
RJOB031

STT :Abended
RJOB031

AbendedLNET10LJOB011

STT :Abended

jobstatus.log FileRJOB031：Abended(2) Automatic Recovery does not Become Effective
The system cannot perform automatic recovery and treats jobs as ABEND in the following cases.


The A-REMOTE is stopped or shutdown while the A-AUTO Monitor is doing after-down-restart.



The A-AUTO Monitor is re-started in COLD mode.

The session cannot be re-established in the number of retry time specified by (NJP_CONNRETRY)
parameterThe njp is ABEND at the moment when the execscr has got the Job execution signal from A-REMOTE ,but has not send the Job end signal to njp.

In these cases , it is necessary to perform manual recovery.
In order to simplify the manual recovery, the system will record the information of Job , whenever it failed to send
signal when it is running or ended, in Job execution status file and Job end notification log file. (Detail refer to“13.6 A-REMOTE Job Outcome Management at the Time of Communication Unusual Detection”). Please
perform recovery after checking the end status of an applicable job by each file.

13-18

13. Remote Job Execute Function(3) Automatic Recovery Job End TimeJob recovery end time will depend on the running status of remote job when it is recovered.


The remote job is not completed at the recovery time.
Time when the end message of the remote job is received from A-REMOTE.

The remote job is completed at the recovery time.
Calculated according to the start time and the actual processing time of the job execution.



Recovery fails
Time the recovery failed.

(4) It is treatment of a network during the execution which is not performing the job.
When the A-AUTO monitor is end to the following special timing, After recovery completed the status will bechanged as following.
#

Abnormal ending timing

Status after recovery

1

When the running jobs in a network are

Recovery the job execution.

completed, but the following job is notstarted2

When all the jobs in a network are

The job end status of a network is recovery to a normal end

completed, but the displayedor abnormal end state.

network status is not completed

Note

When the job is Delay Watch Network Job, the recovery time it passed over the delay watch start time,
the network delay information will be notified.



According to the remote job connection information change execution time, the recovery of a remote
job may fail. When you use this function, When A-AUTO monitor is down, please do not change the
SYSQCONF parameter until recovery is finished.

13-19

13. Remote Job Execute Function(4) System Parameter Setting
System parameters can be changed in the System Management "Monitor".
Please refer to “9.3.1 Settings of Monitor”.
AUTO_RJOB_RCVY
If you wish to use the Remote Job Recovery Function, Please specify “1”.
NCP_NTWK_STOP
For a network that is recovered in Remote Job Recovery Function, a stop command can be generated
automatically internally and automatic execution of the following job can be deferred. When you want use thisstop function. Please specify “1”.
NJP_MONITORDOWN_CANCEL
When you use a Remote Job Recovery Function, please specify 0 (The job under execution is not canceled).
NJP_KEEPALIVE_RMT
NJP_KEEPALIVE_TMR
NJP_CONNRETRY
NJP_CONNINTERVALOn the above parameters, Please refer to "System Administrator's Guide" "auto_sysconf parameter list".
When

NJP_KEEPALIVE_RMT

andJP_KEEPALIVE_TMR

value

is

invalid

or

not

set,

and

the

NJP_KEEPALIVE_RMT set value is greater than the NJP_KEEPALIVE_TMR,
NJP_KEEPALIVE_RMT and NJP_KEEPALIVE_TMR values set as follows
NJP_KEEPALIVE_RMT = 30
NJP_KEEPALIVE_TMR = 60
NCP_AUTORECOVERYNCP_HOLDQUEUEWARM
NCP_HOLDNETWARM
Please specify NCP_HOLDQUEUEWARM value is “0” if you want A-AUTO Monitor to automatically continue
with the execution of the remaining Networks in the Queue.
When NCP_AUTORECOVERY value is specified as "1", A-AUTO Monitor will automatically queue the Networks
that have been running at the time of abnormal shutdown into Network Queue for execution. And if
NCP_HOLDQUEUEWARM is 0, the re-queued network will be started immediately. It is therefore recommended
that you hold the network queue by using HOLDNETWARM. Please set according to the actual situation.

13-20

13. Remote Job Execute Function

13.8

Load Balancing Function(1) Overview of Function
With Load Balancing Function, A-AUTO Monitor determines the CPU utilization of A-Remote servers andautomatically assigns a Network to the server with the lower CPU utilization. Servers to be included in Load
Balancing function are pre-registered. A-AUTO Monitor receives load information from these servers anduses this information to determine the CPU utilization. Using this function, one of the registered servers on
A-Remote side is automatically assigned to execute Networks.
This function is available for A-AUTO v710 or later version.
To use load balancing function, the following settings are required.


Set System ParameterRegister System QualifierRegister System Group Qualifier
Define where the Networks are to be executed and how to assign Job executions.



Define association with Network ID.Associate the Load Balancing settings to Network ID.

(2) Setting for System Parameter
To start using Load Balancing Function, it is necessary to set the system parameter as follows.
System Parameter may be changed using “Settings of Monitor” window under “System Management.”
AUTO_LBP
Default is ’0’ which indicates that Load Balancing function is inactive. Specify ‘1' to use the function(3) Registering System Qualifier
For information on how to register System Qualifier, please refer to “13.1.1 Setting System Qualifier”

13-21

13. Remote Job Execute Function

13.8.1 System Group Qualifier Definition
System Group Qualifier can be defined as follows.
Use [System Group Qualifier Detail] dialog of [System Management] Windows to define System Group Qualifier.
To define a System Group Qualifier, enter necessary information and select the members for the group.

① System Group Qualifier name
This is a System Group Qualifier ID. ID specified must be less than 8 alphanumeric characters of capitalletters.

② Evaluation Type
Select the evaluation criteria to be used to determine how a Network is to be assigned to a server for
execution

Execute Wait Queue List
Jobs are assigned to a server for execution based on the length of Execute Wait Queue List.



Round Robin
Jobs are assigned to a server for execution according to the order of the System Qualifiers registeredin the System Group Qualifier.



Expression
A-AUTO Monitor receives CPU utilization information from registered servers and assigns Jobs to theservers from the one with a lower CPU utilization to the one with higher CPU utilization. Detailed
settings for Expression are done in parameter file SYSQCONF.

13-22

13. Remote Job Execute Function

Not Distributed

The System Qualifier may be temporarily eliminated from the candidates, and Job execution is not
assigned.

③

Weight Value
When [Expression] is selected as Evaluation Type, select the pattern from Weight Value.

④

Monitoring Span
Specify the time interval to receive Load Information.

⑤

Selected Item
This column shows System Qualifiers that are included in the Group.

⑥

Unselected Item
This column shows System Qualifiers that are available to be selected for the Group.

13-23

13. Remote Job Execute Function

Example of defining System Group Qualifier
System Group Qualifier name

：RWINGP01

Evaluation Type：Round Robin

Monitoring Span

：30

① Click [Create] on [System Group Qualifier list] pane.
② System Group Qualifier Detail is displayed.

③ Enter required information.


System Group Qualifier：Enter RWINGP01
Evaluation Type： Select Round Robin

Monitoring Span： Enter 30④ Select the System Qualifier to be added from Unselected
Item⑤ Click ［←］⑥ The selected System Qualifier is moved to Selected Item.

⑦ Click ［Apply］.
⑧ The settings are registered.

Note

System Qualifier information may also be registered by parameter file, SYSQCONF. For details,
please refer to System Administrator's Guide.

13-24

13. Remote Job Execute Function

Defining association of Network ID
When the ID defined in ’System Qualifier’ attribute of a Network matches the System Group Qualifier ID,
A-AUTO Monitor selects a server from those registered in System Group Qualifier ID to execute the
Network. (For details, please refer to "3.1 Network Master.")

13.8.2 Checking the Status and Controlling Load Balance
Status may be checked using [A-AUTO Monitor] Windows.
① Display [A-AUTO Monitor] Windows② Click a Monitor ID on [Monitor List], and [Monitor Detail] pane is displayed.
③ Select [Load Balance Information] from the select box located on the toolbar and click [Execute].
④ Load balance information is displayed.

13-25

13. Remote Job Execute Function

13.9

Job Log Management Function(1) Overview
Job Log Management function is designed to store Job Log records (standard output, standard error
output) of application Job executed under A-Remote. If this function is activated, A-Remote obtains theoutput of the executed Jobs and stores them in the Job Log files which are created in the specified
directory.
The Job Log files are not deleted automatically. The number of Job Log files will keep increasing day byday. It is therefore a good practice to delete the unnecessary files regularly. The Job Log files may beviewed on Web Client.

(2) Setting System Parameter
To use Job Log Management function, it is necessary to set the following system parameters.
NJP_JOBLOGON
This Parameter may be changed using [Monitor Edit] pane of System Management Windows. Installation
default is ‘0’ which indicates that Job Log Management function is inactive. To use the function, specify ‘1’
or ‘2’. A value of ‘1’ or ‘2’ indicates the generated Job Log file name to be used as follows.
Parameter

Job Log File name‘1’

Job ID.Start Date(YYYYMMDD).Start Time(hhmmss)‘2’

Job ID.Schedule Date(YYYYMMDD).Start Time(hhmmss)※Setting 2 is available with the v6010 or later version.
Please note that when A-Remote is started as a service, even if JOBLOGON is set to ‘0’, the setting is
automatically changed to ‘1’ that indicates Job Log Management function is active.
Note
If two Jobs with same Job ID are executed at the same time, even if their Network IDs are different, Job
Log File name generated will be the same. This means one Job Log is overwritten by the other.
NJP_JOBLOGDIR
Job Log files are stored in a directory specified for this parameter.
' \ ' (backslash) must be entered at the end of a path as c:\bsp\ARMTNT\JOBLOG\ (A-Remote forWindows) and $AUTODIR/files/JLOG/ (A-Remote for UNIX)13-26

13. Remote Job Execute Function

13.10

KeepAlive Function(1) Overview
In Windows NT or Windows 2000, it is possible that physical network connection between computers is
disconnected, for example due to power failure.

When this happens, socket API is not reset. In this case,even if the communication with A-Remote is disconnected, A-AUTO Monitor is not able to detect thedisconnection. As a result, a remote Job remains in active status in A-AUTO Monitor’s side even if the Job
has terminated at the A-Remote server. KeepAlive Function is designed to avoid the above situation, by
checking the connection regularly. This function is available for v2049, v2101, Lv06 (A-Remote forWindows) or later version. Both sides of A-AUTO Monitor and A-Remote need to have this function.

(2) Process Flow

Job Execution Request

Job execution① Confirm Connection②

A-Remote for
UNIX

Responseor

A-AUTO Monitor① Confirm Connection

A-Remote forWindows② Response

Job end message

When a Network is executed by A-AUTO Monitor, it sends Job Execution Request to A-Remote to execute a
Job. After A-Remote initiates the Job, it sends connection confirmation message to A-AUTO Monitor at aninterval specified in System Parameter ‘NJP_KEEPALIVE_RMT’ (in seconds).

Detection of cutting of a session
A-AUTO Monitor expects to receive the connection confirmation message regularly after it sends Job execution
request. If A-AUTO Monitor does not receive the message for a time longer than the interval specified in‘NJP_KEEPALIVE_TMR’, it assumes that the communication is disconnected and treats the Job as canceled
after displaying the following messages.

13-27

13. Remote Job Execute Function

AUX911I NO RESPONSE FROM [Node Name] FOR [NJP_KEEPALIVE_TMR] SECONDS
AUX915E CONNECTION ERROR. JOB(Job) CODE=終了コード JP(JP Partition number)
The return code of the job in this case is set to "08", and a completion code is set to "0007."In the A-REMOTE side, when the response message from an A-AUTO Monitor is not received after
transmitting the connection confirmation message, it recognizes it as connection problem. The following
message is output and a session is disconnected.
AUX980W CLOSE THE SESSION WITH A-MONITOR BECAUSE CAN'T RECEIVE THE RESPONSE(3) System Parameter
Parameters may be changed using [Monitor Edit] window of System Management. Please refer to “9.3.1
Settings of Monitor”.
NJP_KEEPALIVE_TMR
System Parameter for A-AUTO Monitor
The time interval (in seconds) that A-AUTO Monitor does not receive connection confirmation message
from A-Remote and treats the communication with A-Remote as disconnected.

The default setting is ’0’

that indicates this function is not used.
NJP_KEEPALIVE_RMTSystem Parameter for A-AUTO Monitor
The time interval (in seconds) that A-Remote sends a connection confirmation message to A-AUTO
Monitor. The default setting is ’0’.
If this function is not used, set the both parameters to ’0’
No parameter exists for A-Remote.
Note■ NJP_KEEPALIVE_TMR must be longer than NJP_KEEPALIVE_RMT.
(As a guide, more than twice the value of NJP_KEEPALIVE_RMT)
If NJP_KEEPALIVE_TMR is not longer than NJP_KEEPALIVE_RMT, the following message is output andthe function is set off.
AUX913W 'NJP_KEEPALIVE_TMR' MUST BE LARGER VALUE THAN 'NJP_KEEPALIVE_RMT'■ If NJP_KEEPALIVE_TMR is not 0 and NJP_KEEPALIVE_RMT is 0, the following message is output andthe function is set off.
AUX912W INVALID 'NJP_KEEPALIVE_RMT' VALUE■ If NJP_KEEPALIVE_TMR and NJP_KEEPALIVE_RMT are not set, the function is set off

13-28

13. Remote Job Execute Function■When the following message is output even though there is no problem in physical network connection and thesession between an A-AUTO Monitor and A-REMOTE is disconnected, it could be resolved by increasing theparameter values of NJP_KEEPALIVE_RMT and NJP_KEEPALIVE_TMR.

[A-AUTO Monitor side]
AUX911I NO RESPONSE FROM 172.22.XXX.XX FOR 20 SECONDS[A-REMOTE side]
AUX980W CLOSE THE SESSION WITH A-MONITOR BECAUSE CAN'T RECEIVE THE RESPONSE

13-29

13. Remote Job Execute Function

KeepAlive usage example
NJP_KEEPALIVE_TMR : 120 (seconds)
NJP_KEEPALIVE_RMT : 30 (seconds)
Execute a Job that sleeps for 110 seconds.

Job execution
Job execution request

30sec
A-AUTO
Monitor

A-REMOTE for
UNIXor

Confirm

A-REMOTE for
Windows

Response
30sec

communication
problem
30sec

The problem
detection for job
abnormal end at

120 secThe

problem

detectionfor

A-Remotejob

abnormal end at
A-AUTO monitor

If 120 seconds (NJP_KEEPALIVE_TMR) has passed after receiving the last message of a connection
check, A-AUTO Monitor will treat it as there is a problem with communication and will perform termination
processing (when a session recovery function is effective, it will perform session recovery processing) of ajob.
When termination processing of a job is performed, a job will be completed 150 seconds after a job isstarted.
When A-REMOTE does not receive a response message from A-AUTO Monitor 30 seconds(NJP_KEEPALIVE_RMT) after it has sent its last confirmation message, it will treat the communication as
disconnected and exit the session.
13-30

13. Remote Job Execute Function(4) Session Recovery Function
This function can be used

for A-AUTO Monitor V722 or later and with A-REMOTE.

When this function is used, KeepAlive function becomes effective automatically.
When a Session Recovery Function detects session cutting between an A-AUTO Monitor and A-REMOTE bya KeepAlive function, it is a function to re-establish a session from an A-AUTO Monitor. By using this function,even when a temporary session obstacle occurs, the execution result of the job which was under execution at
the time of cutting can be acquired, and the automatic renewal of the processing can be carried out.
Function recovery session , the session cannot be opened if the number of A-AUTO is specified in theparameter monitor even if you (NJP_CONNRETRY) retry , will treat the job as an abnormal termination.
In order to use a session recovery function, it is necessary to perform the following setup. Change of aparameter is possible on the "monitor edit" screen of a system management. Please refer to "9.3.1 Settings ofMonitor."

AUTO_SESS_RCVY
When you use a session recovery function, please specify 1 (Function is used).
NJP_MONITORDOWN_CANCEL
When you use a session recovery function, please specify 0 (the job under execution is not canceled by
A-REMOTE). Even if 1 is specified, the setting is automatically set to 0 if AUTO_SESS_RCVY is set to 1..
NJP_KEEPALIVE_RMT
NJP_KEEPALIVE_TMR
NJP_CONNRETRY
NJP_CONNINTERVAL
A value must be specified for each of the above-mentioned parameters. Refer to "auto_sysconf parameter list"of System Administrator’s Guide.
If no value is set for both NJP_KEEPALIVE_RMT and NJP_KEEPALIVE_TMR (0 is an invalid value), or thevalue of NJP_KEEPALIVE_TMR is set smaller than NJP_KEEPALIVE_RMT, the following values are
assigned.
NJP_KEEPALIVE_RMT = 30
NJP_KEEPALIVE_TMR = 60

13-31

13. Remote Job Execute Function

Session Recovery Function example
NJP_KEEPALIVE_TMR : 90 (seconds)
NJP_KEEPALIVE_RMT : 30 (seconds)
NJP_CONNINTERVAL: 15 seconds

Execute a Job that sleeps for 150 seconds.
Job execution
Job execution request

30sec

A-REMOTE for
UNIX

Confirm

A-AUTO
MonitorResponseor
A-REMOTE for
Windows
30sec

communication
problem

30sec

90sec

The problem
detection for job
abnormal end at

The problem detection

A-Remote

for job abnormal end at
A-AUTO monitor

15sec

Create session
request①

15sec

Create session
request②
Recovery request

Job end message.

If 90 seconds (NJP_KEEPALIVE_TMR) pass after receiving the message of a connection check at the last, an
A-AUTO Monitor will judge that communication is cut and will perform re-establishment of a session.
A-AUTO Monitor gives a session establishment demand to every 15 seconds (NJP_CONNINTERVAL) to
A-REMOTE. If a session is re-established, as soon as a job is completed, A-REMOTE performs the notice ofan end, and an A-AUTO Monitor will also usually pass along it, and it will perform termination processing of a
job.
13-32

13. Remote Job Execute Function

13.11

Date Pass function(1) Overview
Date Pass Function is designed to pass Operation Date and Schedule Date of a Network to Jobs.
This function is available with Level v6010 or later version.
The following variables can be used to obtain dates information.
Variable

Description

BSP_AUTODATE

Operation Date of A-AUTO Monitor

BSP_SDATE

Schedule Date of the Network(2) Setting System Parameter
This System Parameter is set for the function to indicate date format to be passed.
Parameters may be changed on [Monitor Edit] of System Management.
AUTO_DELIMITER
Date format can be selected as follows.
The default is ‘0’. The date format is "YYYYMMDD".
The format for date that may be set for A-Remote.
0

YYYYMMDD

1

YYYY/MM/DD

2

YYYY-MM-DD

13-33

13. Remote Job Execute Function

Sample

A-Remote for UNIX
When AUTO_DELIMITER is set to ‘1’:#! /bin/csh
echo "TESTJOB STARTED"
echo "TESTJOB BSP_SDATE: $BSP_SDATE"
echo "TESTJOB BSP_AUTODATE: $BSP_AUTODATE"
echo "TESTJOB ENDED"
exit 0
Output example
TESTJOB STARTEDBSPSTA01 BSP_SDATE: 2005/01/28
BSPSTA01 BSP_AUTODATE: 2005/01/28
TESTJOB ENDED

A-Remote for Windows
When AUTO_DELIMITER is set to 2
@echo offecho TESTJOB STARTED
echo MONITER-DATE %BSP_AUTODATE%
echo SCHEDULE-DATE %BSP_SDATE%
echo TESTJOB ENDED
exit
Output example
TESTJOB STARTEDMONITER-DATE 2005-01-28
SCHEDULE-DATE 2005-01-28
TESTJOB ENDED

13-34

13. Remote Job Execute Function

13.12

Sample Job

13.12.1 Remote Job Execute Function (UNIX) examples
Remote Job Execute Function (UNIX), job is a shell script。
#!/bin/xxx
echo “JOB START”
bspappcase $? In‘0’)echo “JOB NORMAL ENDED”
exit 0;;*)echo “JOB ABNORMAL ENDED
exit 1;;esac

13.12.2 Sample Job for A-Remote for Windows
Jobs to be executed under A-Remote for Windows should be programs. File extension of these programs
should be either .exe or .bat. A-Remote searches for Job files in the following sequence until the one to be
executed is found.
① *.exe file in a directory specified for System Parameter TEMPSCRIPT② *.bat file in a directory specified for System Parameter TEMPSCRIPT③ *.exe file in a directory specified for System Parameter PRIMSCRIPT④ *.bat file in a directory specified for System Parameter PRIMSCRIPT
If a Job is an executable file, return code of the exe file is Job End Code. If a Job is a batch file, use aexit
utility to pass Job End Code to A-Remote after checking result of application programs using
ERRORLEVEL and end the bat file with ‘exit’ command. Make sure to use the exit command to end a
program. The maximum number of concurrent Jobs for one A-Remote is 255.
echo "BSPSTA01.BAT STARTTED"
ping ihost1
IF ERRORLEVEL 0 GOTO NORMALIF ERRORLEVEL 1 GOTO ABEND:ABENDecho "BSPSTA01.BAT ABENDED"
aexit 1GOTO DONE:NORMALecho "BSPSTA01.BAT NORMAL ENDED"
aexit 0
:DONE
exit

13-35

13. Remote Job Execute Function

13.13

Example of System Configuration

A-AUTO Monitor
A-AUTO for UNIX Remote License
MCP
armtux
NCP

NJP

NEP

TMR

LBP

execscr

SYSQCONF：
UNIX01

execscr

Local Job

execscr

SYSQCONF：
WIN01

execscrrmtscrJob Execution

rmtscrJob Execution

rmtscrJob Execution

SYSQCONF：UNIX01
hostname：host01
NJP_LISTENPORT ：7000
TEMPSCRIPT_PATH ：$AUTODIR/tempshell/
PRIMSCRIPT_PATH ：$AUTODIR/primeshell/

Local Job

SYSQCONF
UNIX01：KIND= S
HOST = host01
PORT= 7000LBTYPE = 0
WIN01：
KIND
HOST
PORT
LBTYPE

A-AUTO for Windows Remote License

armtnt= S= SERVER01= 5000= 0

rmtscrJob Execution

rmtscrJob Execution

rmtscrJob Execution

SYSQCONF：WIN01hostname：SERVER01
NJP_LISTENPORT ：5000
TEMPSCRIPT_PATH ：C:\BSP\ARMT\TEMP\PRIMSCRIPT_PATH ：C:\BSP\ARMT\PRIME\

13-36

15 Limitations

15

Limitations

15.1 Precautions and Limitations to execution of Auto Scheduling① Backups of the Schedule Master, Holiday Master and the Daily Network Master are theresponsibility of the customer. It is recommended to take a backup before executing autoscheduling.
② If Auto Scheduling is executed after one-year or more, there may be a period which is not coveredby the Network Schedule.
③ If updates of the Schedule Master, or Holiday Master fail after number of retries specified by
System Parameter AUTSCHE_MAXRETRY, autosche utility will stop to prevent inconsistency in
Master files.
④ The maximum number of retries and the retry interval are specified by System Parameter
AUTOSCHE_MAXRETRY and AUTOSCHE_RETRYINTERVAL respectively.
⑤ Even if the autosche utility is executed more than once in the same month, neither the Holiday
information nor the Network Schedule will be updated by the second or succeeding execution. It
only records the date on which Auto Scheduling was executed in the log files.
⑥ If a data inconsistency is detected in the Schedule Master, Holiday master and Network Master, amessage will be displayed and the master files will not be updated with the inconsistent data.
⑦ autosche utility is never executed redundantly.
⑧ If the log file is not successfully opened, a message will be displayed and autosche utility will stop
without executing Auto Scheduling.
⑨ If an existing file name is specified for the log file, the existing file will be deleted first. Therefore, it isrecommended that log files be backed up. If autosche utility is erroneously started redundantly theexisting log file will not be deleted.
⑩ If a Network is scheduled by working day over 2 months from the Reference Date, it may not bescheduled by Auto Scheduling.

15 Limitations(1) In the case of A-AUTO for UNIX

■autosche sample shell <sgen>
When sgen (.sh) is executed with parameter '0' or without parameter, autosche is executed. When sgen(.sh) is executed with '1' parameter, remakesche is executed.
C shell.

#!/bin/csh
source $AUTODIR/autoenv.csh
switch ( $1 )case 0:echo ">>Start autosche"autosche -faut_def
set STATUS = $status
breaksw
case 1:echo ">>Start remakesche"remakesche -faut_def
set STATUS = $status
breaksw
default:echo ">>No parameter specified"echo ">>Start autosche"autosche -faut_def
set STATUS = $statusendsw
switch ( $STATUS )case 0:echo ">>Schedule Generation COMPLETED($STATUS)"
exit 0breaksw
default:echo ">>Schedule Generation FAILED($STATUS)"
exit 1endsw

15 Limitations

Bourne shell, Korn shell#!/bin/ksh#!/bin/sh. $AUTODIR/autoenv
case $1 in0)echo ">>Start autosche"autosche -faut_def
STATUS=$? ;;1)
echo ">>Start remakesche"remakesche -faut_def
STATUS=$? ;;*)echo ">>No parameter specified"echo ">>Start autosche"autosche -faut_def
STATUS=$? ;;esaccase $STATUS in0)echo ">>Schedule Generation COMPLETED($STATUS)"
exit 0 ;;*)echo ">>Schedule Generation FAILED($STATUS)"
exit 1 ;;esac

15 Limitations(2) In the case of A-AUTO for Windows■autosche sample batch <sgen.bat>
When sgen.bat is executed with parameter '0' or without parameter, autosche is executed. When sgen.bat
is executed with '1' parameter, remakesche is executed.

@echo off
if "%1" EQU "1" ( goto :REMAKESCHE ) else ( goto :AUTOSCHE ):AUTOSCHE
echo Start autosche
autosche -faut_def
goto :ALLEND:REMAKESCHE
echo Start remakescheremakesche -faut_def
goto :ALLEND:ALLEND
pause

15 Limitations

15.2 Precautions and Limitations to execution of sfin utility①

Do not issue queuing command while Finalized Schedule function is being executed.

②

Do not execute Finalized Schedule function until A-AUTO Monitor has completed the processing of a queuingcommand.

③

Do not execute Finalized Schedule function redundantly.

④

When schexrt is executed with –mu parameter, schexrt accesses Schedule Master and Daily Network Masterexclusively. When auwninf is executed with –mu parameter, auwninf accesses Network Master and Daily Network
Master exclusively. In addition, crtaja accesses Network Master exclusively. Therefore, when schexrt, auwninf, or
crtaja is executed and if other A-AUTO for UNIX/Windows programs are accessing these master files exclusively, it
is possible that schexrt, auwninf, or crtaja may stop with exclusive error.
The default value for Type parameter of schexrt and auwninf is (-mf).

15 Limitations

The following table shows which processes of A-AUTO for UNIX/Windows access Network Master,
Schedule Master, or Daily Network Master exclusively.

No.

1

2

3

4

5

6

A-AUTO for UNIX/Windows

Daily Network

Network Master

Schedule Master

Web Client

○

○

○

(*1)

(*2)

(*3)

(*4)

○

○

○

○

○

○

○

Process

Auto Scheduling(autosche utility)
Auto Scheduling○(remakesch utility)(*5)

Finalized Schedule(schexrt module)
Finalized Schedule(auwninf module)
Finalized Schedule(crtaja module)

Master

○

○

○
○

7

A-AUTO Monitor

8

auxunlk utility○

9

esvcrt utility○

10

rmakdnwk utility

(*6)
○

○
○
○

(*1)Actual process which accesses master files exclusively is auxrfs under AP-LINK.
(*2)When Network Master Detail Window’s Apply or Network Master List Window’s Delete is executed.
(*3)When Schedule Master Detail Window’s Apply, Schedule Master List Window’s Delete, Network
Schedule Detail Window’s Apply, Network Schedule List Window’s Delete of Network Schedule,
Add/Delete/Move of Schedule Date, or Network Schedule Batch Setting Window’s Add/Delete of
Schedule Date is executed.
(*4)When Daily Network Master Detail Window’s Apply, Network Schedule Detail Window’s Apply,
Network Schedule List Window’s Delete of Network Schedule, Delete/Move of Schedule Date,or Network Schedule Batch Setting Window’s Delete of Network Schedule is executed.
(*5) Only when System Qualifier is specified.
(*6)When Queuing, Start, Display Network, or Free On command is processed.
started or ended.

Or when a Network

15 Limitations⑤

When schexrt and auwninf are executed with –mf parameter, schexrt accesses Schedule Master and Daily Network
Master without exclusive control while auwninf accesses Network Master and Daily Network Master without
exclusive control. Therefore, while schexrt or auwninf is running, it is recommended that you do not execute other
A-AUTO for UNIX/Windows programs that change Network Master, Schedule Master or Daily Network Master.
Otherwise, it may cause data inconsistency.
The default value for Type parameter of schexrt and auwninf is (-mf).
The following table shows which processes of A-AUTO for UNIX/Windows change Network Master, Schedule
Master, or Daily Network Master file.

No.

1

2

3

A-AUTO for UNIX/Windows

Daily Network

Network Master

Schedule Master

Web Client

○

○

○

(*1)

(*2)

(*3)

(*4)

○

○

○

○

Process

Auto Scheduling(autosche utility)
Auto Scheduling(remakesch utility)

Master(*1)Actual process which changes master files is auxrfs under AP-LINK.
(*2)When Network Master Detail Window’s Apply or Network Master List Window’s Delete is executed.
(*3)When Schedule Master Detail Window’s Apply, Schedule Master List Window’s Delete, Network
Schedule Detail Window’s Apply, Network Schedule List Window’s Delete of Network Schedule,
Add/Delete/Move of Schedule Date, or Network Schedule Batch Setting Window’s Add/Delete of
Schedule Date is executed.
(*4)When Daily Network Master Detail Window’s Apply, Network Schedule Detail Window’s Apply,
Network Schedule List Window’s Delete of Network Schedule, Delete/Move of Schedule Date,or Network Schedule Batch Setting Window’s Delete of Network Schedule is executed.

15 Limitations

15.3 Precautions and Limitations to Exclusion Schedule①

An Exclusion schedule must be defined together with at least one normal schedule.

②

When an exclusion schedule that is without a normal schedule is added using mastercsv utility, it ends normally.

③

As there is no check by mastercsv utility, ensure input data to define exclusion schedule is added together with atleast one normal schedule before executing mastercsv utility. If exclusion schedule is added incorrectly, change
input data and rerun the utility. Or, change Network Schedule Master using Web Client.

15 Limitations

15.4 Precautions and Limitations of A-AUTO/Web client and AP serverIn the following cases, Job/Network cannot be monitored or controlled using Client.
When Cancel command is issued for a Network in Network Queue that was queued by Start
command.
When FREE ON command is issued for a Network in Network Queue that was queued by Start
command.
For a Network that was queued by Start command, monitoring is not available until Job/Network
information is transferred from Agent to Client, or until the Network starts.

In the following cases, displayed status may be different from actual status after file transfer.
When a Job/Network was being

It is displayed as “In Queue”. The status will be updated

executedwhen the Network ends.

When FREE ON command was

It is displayed as “Canceled in Queue”.

issued for a Network after the
Network was canceled in Network
Queue.
When a Job/Network was FREE ON

It is displayed as “In Queue”.

while it was in Network Queue.

*

When FREE OFF command is issued for a Job/Network, the status of the Network is not updated.

*

Multiple Jobs/Networks with same name cannot be displayed on the same Network Flow Chart. For
example, if there are multiple Jobs/Networks with same name from multiple Agents, a message box isdisplayed and only one Job/Network, the one that is read from Network Information file (ESVNFILE)
first, is displayed.

*

One Web Server and maximum 36 Agents can be connected to AP Server.

Glossary

Glossary
This section explains the terminologies used in A-AUTO for UNIX/Windows.
In A-AUTO for UNIX/Windows, there are many product specific terms being used. These terms are explained here to assist you
to easily understand the product.
In particular, if you are using A-AUTO for UNIX/Windows for the first time, you may want to use this section as reference while
reading through the product manuals.

About Glossary This glossary publishes the terms which occurs frequently in the screens, functions and manuals for A-AUTO for
UNIX/Windows. A print-out of this may be useful so that it can be referred to it whenever you need it.
 The term is published at the alphabet and the order of the Japanese syllabify.

iGlossary

Term

Explanation

A-AUTO Event

This is the generic name of the component that performs event management
function.
It consists of the following four components.
A-AUTO Event Server
A-AUTO Event AgentWeb Client
Support Utility

A-AUTO Event AgentThis component takes the instructions on monitoring events from the A-AUTO
Event server and performs the monitoring of events. Occurrence of an event is
detected and occurrence of an event is notified to an A-AUTO Event server.
Takes instructions to execute action from A-AUTO Event server and performs theaction.

A-AUTO Event ServerThis component manages master data defined by the Web client and stores theminto a database.
It directs A-AUTO Event agents to monitor events and perform the actions.
It manages the results of the event monitoring and action execution from A-AUTO
Event agents and store this information in the database.

A-AUTO Web ServerThis component displays the following information managed by the server, Master
file information, work (Job Network) information and A-AUTO Monitor
information.

A-AUTO ServerThis is a generic name to refer to A-AUTO Web Server、A-AUTO Event Server、and AP server together.

A-AUTO Monitor

This is a core component of A-AUTO.
It performs the starting of Network for execution, end of Network and commandcontrol, and job execution..
It also directs and control the starting of jobs that are to be performed in the serverwith Remote Job Execute Function (A-REMOTE).

ii

Glossary

Term

Explanation

A-AUTO Agent

It is a component which works in the mainframe, UNIX, Linux, or Windows, andplays the following roles.
The master update process by master maintenance
Master data synchronization process with the A-AUTO ServerTransferred to the AP Server, the execution status (Job Network) work
Processing of monitor delay
Data routing processing in host-A-AUTO Monitor in the mainframe
cooperation (armt)
Other master precedence operating control at the time of the operating
cooperation between masters
A-AUTO/400（AS400）Remote job start
Refer to job log

ABASINIT

It is a resident process required in order that A-AUTO may start.。
It is required in order for another BSP product to work, Windows service
processing, UNIX/LINUX demon processing to work.

aexit(Only Windows) One of A-AUTO utilities. It is a utility to set the return code to the
A-AUTO prior to exit of a batch job.

A-LOCAL

It is a component for the mainframe Connection Option, it works on a mainframe.
A network preceding relation information is managed so that the preceding andsucceeding relation of the network between a mainframe andUNIX/Windows/Linux can be maintained.
A-LOCAL is an armt running on UNIX / Windows / Linux. It sends and receives
various types of data using the TCP / IP protocol.
Moreover, A-AUTO Monitor of A-LOCAL to UNIX/Windows/Linux, the receiving
command issue is attained.

AML ID

It is an identifier assigned to the component of A-AUTO/Connect which works forevery A-AUTO system.
When specifying the preceding networks that belong to other A-AUTO Systems
under Cross-Master Linkage function, it is used to identify which A-AUTO system
the Network belongs.

AP Server

This component provides centralized management of data that has beentransferred from other agents.
It performs many roles, such as a master maintenance, collection of monitoring
information, command issue to an A-AUTO Monitor, and maintenance of DB(PostgreSQL).

iii

Glossary

Term

Explanation

armtThis is a component for the mainframe Connection Option. It is similar to A-AUTO
Agent but with limited functions.
It performs routing processing of the various messages transmitted and received
between an A-AUTO Monitor and A-LOCAL.

ASVPOP

This is the name of the module of message handling routine.
It display a Pop-up dialog when a job abend or Job delay is detected,
It can also set by the environment which the WEB client has not started.

autosche Utility

It is a utility which creates the schedule information for those periods that Network
Schedule has not been created. Data is created for a one-year period startingfrom the CPU date the utility is executed. It is used when the schedule associatedwith a network is changed.

autosmod Utility

It is a utility which adjusts the already created Network Schedules. Addition,
shifting, and deletion based on Schedule Date can be performed.

COLD Start

This is the startup mode of the A-AUTO Monitor. (There are two modes, COLD /WARM)
In COLD start, the following are the additional processing as compared to WARM
start.
1, Operation date of A-AUTO is set to CPU date.
2, All the not executed networks that remain in the Network Queue file are cleared.
3, All log records of executed Networks that are recorded in the Network Log arecleared.
4, The A-AUTO Monitor's operation configuration is updated with the informationin system parameter file (auto_sysconf).
* Abend information that is recorded in Abnormally Terminated Network File willremain intact as in WARM start.

Event File Monitoring

It is one of the event monitoring functions of A-AUTO/Event to monitor for thecreation or updating of a specific file in a specified folder.

Event Message Monitoring

It is one of the event monitoring functions of A-AUTO/Event to detect a message
in the output of system console.

Event Log File Monitoring

One of the event monitoring functions of A-AUTO/Event to detect for pre-defined
string in a log file.

JP

It is a concept on A-AUTO for managing concurrent Jobs.
In A-AUTO, when starting one job, one JP has to be assigned.
The number of JPs that can be defined – is 255. It is used in order to control thenumber of the jobs that can be performed simultaneously.
When there is no JP, a Job that is ready to execute will have to wait for next
available JP..

iv

Glossary

Term

ExplanationNP

It is a concept on A-AUTO for managing concurrent Jobs.
In A-AUTO, when starting one network, one NP has to be assigned.
The number of NPs can be defined – is 255. It is used in order to control thenumber of the networks that can be performed simultaneously. When there is noNP, a Network that is ready to execute will have to wait for next available NP.
When defining partitions, you define a class for each partition. The Class attributeof a Network must match the NP Class before it is selected to be executed in theNP.

Remakesche Utility

Schedule information is re-created and replaced the already created network
schedule.

WARM Start

This is the startup mode of the A-AUTO Monitor. (There are two modes, COLD /WARM)
A WARM start is in starting mode that resumes operation with the operation
configuration at the time it was shutdown. A-AUTO Monitor usually starts with
WARM start.
The following are the processing when you start the A-AUTO Monitor with WARM
start.
1, Operation date of A-AUTO is the same as the date at the time it was shutdown.
2, All the not executed networks that remain in the Network Queue file willcontinue to be executed.
3, All log records remain and logging continues.
4,Operation resumes with the operation configuration at the time it was shutdown.

Web Client

It is a component which performs master maintenance, schedule control,
execution watch, etc. by GUI. Command issue to an A-AUTO Monitor can also be
performed.

ActionAction is a task to be performed automatically when an event is detected. An
action can be Job start, output message, sends mail, start command issuing.

Action ID

It is a unique name assigned to every action.

After Down Recovery

It is the function to perform recovery when A-AUTO Monitor is started after asystem failure such as a machine trouble, etc..

Recovery is for active Jobs whensystem failure occurred.
All AdjustThis is to do all adjust of schedule adjustment.
The target schedule date can be chosen by term Set, set date, or cell
specification, and addition and deletion of a schedule can be performed.

Event ID

It is a unique name assigned to every event.

Event Monitoring

To manage the occurrence of an event in event management function.
In event monitoring, you can choose from four events.

v

Glossary

Term

Explanation

Event Management Function

It is the function to perform management and control of the events and theircorresponding actions to be performed. Events and Actions can be registeredusing "work" definition screen of a Web client.

Event TypeIt is a type of event. There are 4 types, job event, message event, file event andapplication event,

Event Timer Function

It is a function that repeatedly triggers a Network at a specified interval defined in
Event Definition File.

Event Notification Function

When an event occurs, event occurrence is informed in Mail or a message dialog..
It is one of the actions that can be specified for the event.

Event Coordination Function

When an event is detected, it is the ability to cancel the attribute Input Data Waitof a network. This is one of the event management capabilities.

Operation Date

This is the date in A-AUTO system. This date is used to record a log for executed
Network into Network Log File. It can be used as an extraction condition at thetime of carrying out the list output of the network log.

Working Day (Schedule)This is one of the processing patterns that can be used in scheduling. Working
Day refers to only those dates that are not marked as holidays in a calendar tocompute the schedule date for a Network.

End Delay

It is the delay classification in a delay monitoring function.
End delay happens when the execution of a Network does not end by a specified
time (free-on is included).

Extended Job

It is a job using resource management, Job name convert function and extension
function.

Extended Job Master

This is the Master file that stores information about the extended function of a job.
Extended Job information includes Job Name Convert information and resource
management information.

Schedule Confirmation

Extraction of Networks that are to be executed by A-AUTO for Mainframe for a(AUTOSDEF)

day is performed.
Moreover, in Schedule Confirmation, assignment etc. of the tape volume assigned
by File Management Function is performed.
It is possible to outré-execute Schedule Confirmation before Finalized Schedule isperformed.
When using Mainframe Connection Option, it is necessary to carry out Schedule
Confirmation for UNIX/Windows/Linux in addition to the usual Schedule
Confirmation for the mainframe side.

Fiscal Month

The period for one month based reference date to final day.

Running Date

On the calendar of Holiday Master Table, refers to a day other than the holiday.

viGlossary

Term

Explanation

Calendar (Schedule)This is one of the processing patterns that can be used in scheduling. Calendar
Day refers to the actual dates in a calendar regardless of holidays to compute theschedule date for a Network.

Audit trail

The history which is captured when managing master information (Security Log).

Reference Date

When performing processing by Working Day, the minimum unit of a schedule is amonth unit. At this time, reference date serves as final date of the month. For
example, like a payroll calculation system, when the beginning of the month will
start on the 21st, Reference Date will be 20 days.

Execute Condition

These are the conditions that a Network has to meet or satisfy before it is released
for execution.
Examples are Preceding Job, Start Time Wait, Hold Attribute, Input Data Wait,
Preceding Network (Monitoring On)

Queuing

This is a process where the Networks to be executed for the day is transferredfrom output of Finalized Schedule to the A-AUTO Monitor so that execution can
begin.

Queue Search

For Networks in Network Queue, A-AUTO Monitor searches for a Network thatmeets the Starting Conditions. If found, it will check whether its Execution
Conditions are fulfilled and release the Network for execution when the conditions
are fulfilled.

Annual Holiday Information

This is the information that defines holidays that fall on the same dates every year.

Annual Holiday Master

It is a master which manages Annual Holiday Master.

Class

It is used to control the simultaneous execution of Networks. A Network can only
be executed if its Class matches the Class defined for a NP.

Monthly Processing

It is the processing carried out every month on a specific date.

Monitor On Wait

Monitor On is one of the Starting Conditions that can be defined for a Network(attribute).
When a network with Input Data Wait, its succeeding Networks will have Monitor
On Wait condition. Command (Monitor On) must be issued to release thiscondition. Alternatively, set “Monitor On” attribute to “ON” to cancel Monitor On
Wait Condition during registration.

Monitor On

It is the setting of the Monitoring On Attribute to “ON” so that Monitor On Wait
Condition is automatically cancelled after the end of execution of a network with
Input Data Wait Attribute.

Sub Job Cancel

When canceling Job under execution, it is the function to also terminate theprocess started from Job.

Command Log

It is a history of the Monitor commands issued from the Web client. You can use
this log to check whether a command has been received by the A-AUTO Monitor.
[A-AUTO Main] Screen‐[System Management]‐[Log]‐[Command Log]

vii

Glossary

Term

Explanation

Final schedule (AUTOSFIN)

It is to finalize the schedule for the day to prepare Networks for execution by
A-AUTO for Mainframe.
It is also necessary to carry out the Finalized Schedule for UNIX/Windows/Linux inthe mainframe with Mainframe Connection Option environment.

Final schedule (sfin)

It is to finalize the schedule for the day to prepare Networks for execution by
A-AUTO Monitor for UNIX/Windows/Linux. Finalized SChedule processing is
performed by sfin utility. Intermediate file is created and make available for user.

Interval Start

It is to repeat the same network to trigger at a specified time interval.

Start Time Wait

Start Time wait is a wait condition for the arrival of time to release a Network for
execution. The time is specified in "Start Time" attribute of the network.

System Qualifier

It is an attribute defined in a Network to identfy on which computer the network is
to be processed. SYSQCONF file defines System Qualifiers and its computer
information (IP address).

System Group QualifierThis is used in Load Balancing function. It defines System Qualifiers to be
included in a group and the criteria for the Load Balancing Function.

Execution Period

This is defined in a Schedule Pattern to restrict scheduling to a limited period. The
value which can be specified differs according to Process Cycle as follows.
Processing cycle "every day" : Specifies the period in ("01"-"31") date
Other than processing cycle "every day": Specifies the period in ("01"-"12")month.

Execution partition

It is a generic name of NP / JP

Execution ID

This is used to group Networks by execution classification. Scheduling can be
performed based on Execution ID. If execution classification is specified when
performing scheduling (asvsfin), only networks with the execution classification isscheduled. Execution classification can be selected from one of these characters:
1 ~ 9, A ~ Z. For “Irregular” schedule, execution classification is automatically set
to "0.".

Execution condition

Network execution condition] They are the conditions whose execution is enabledto the network where all starting conditions were fulfilled.
Priority, a class, and resource (exclusion) etc. -- they are the conditions for
performing a [job execution condition] job.
System Qualifier, Class, Resource (exclusion)

Execution Multiplicity

etc.

Networks or jobs that can be executed concurrently.
Set of multiplicity in number of Network Partitions, number of Network Partitions
and the class for Partitions.

Expiry Date

This is a date when a Network becomes invalid. It is invalidated from the day
following the registered Expiry Date.

viii

Glossary

Term

Explanation

Shift Pattern

One of the items in the definition of Schedule Master. It defines how the scheduleof a Network is to be handled when its schedule date falls on a holiday or how theReference Date is to be handled when it falls on a holiday.
[ Do not Shift] [The Day Before] [The Day After] [After: Before if 2-day off] [After:
Before if 3-day off] [On the day].
Whether it is a shift in schedule date or Reference Date depends on Process
Pattern.
Processing pattern "Calendar" :Schedule Date determined by standard
processing date and a processing cycle
Processing pattern “”Working Day” : Reference Date

Use Rights

Permission to run the operation for master and (View, Edit, Register, Delete,
Execute) for the commandJob

Is the smallest unit that can be executed in the A-AUTO operations.
If an application Network is unsuccessful, then this is the smallest unit that will bererun.
For a Windows system, bat (file), exe (file), and cmd (command) can be specified
as a job while for UNIX it is a shell script. One network can consist of 1 to 32 jobs.

Job ID

Job ID (it is also called a job code) is an identifier of the job.
Depending on platform, Job ID to be specified is as follows.
UNIX/Linux : name of Shell Script
Windows: name of Batch file

AS400

: CL (Job Parameter Name)

Mainframe : name of JCL
In Windows, the name is specified without the extension of bat (file), exe (file) andcmd (command).
Job Executing Status File

The information on the remote job which transmission of under execution or an(jobstatus.log)

execution result has not completed at the time of session cutting is recorded.

Job Executing User ID

This is the User ID to be used to execute a Job if Switch Job Execution User ID
Function is used. It can be specified in "The network attribute 1" tab and a "Job"tab of Network Definition.

Job Termination Notification Error

The information on the remote job which was not able to transmit the notice of the

Log File (jnotifyerr.log)

end of a job to an A-AUTO Monitor is recorded.

Job Network

Is a term that is used to distinguish from common network, "Network" in the
A-AUTO system.

Job Number

The job number is a number attached to the job code. Each Job must be assigned
a unique number within a Network. The number can be between 001 and 999.
If do not specify the " Parallel Run" attribute for a Network, jobs in the network will
be run one at a time in ascending order of job number.

ix

Glossary

Term

Explanation

Job Branch Function

This is the function to determine the job to be executed next using the return codeor exit status of the preceding job.

Change Job Name Function

In A-AUTO system, Job ID can have a maximum of 8 alphanumeric characters.
But by using this function it becomes possible to specify more than 8 characters,
double bytes characters and/or special characters for Job ID.
Example: (actually performed job) -- job.bat change (on network master)processing .bat.

Job Library ID

A set of main path and temporary path definitions is called "Job Library" and an ID
assigned to each Job Library is called "Job Library ID". Job Linrary ID is a number
from 0 to 9.
A-AUTO Monitor chooses the batch file or shell script from the path specified bylibrary ID 0 at the Queuing time.
Library ID can be changed for a network using a reset command.
ID "0" is assigned to the Job Library for production environment. ID from 1 to 9
should be assigned to Job Library for other environments such as test run
environment.

Process Cycle

One of the items in the definition of Schedule Master. Process cycle can be every
day, weekly, monthly, etc.. Based on the process cycle is selected, the schedule
to run a Network is calculated.

Process Pattern

One of the items in the definition of Schedule Master. Process Pattern can beeither calendar (schedule) or Working Day (schedule).
When calculating the processing schedule dates using Process Pattern"calendar", days are counted according to the date of a calendar regardless ofholidays.
When calculating the processing Schedule Date by [Working Day], It calculates
using Reference Date and dates in the calendar that are not marked as holidays.

Schedule

The execution schedule for the operation of a Network. In A-AUTO, the execution
schedule is defined in the network schedule.

Schedule PatternA

Schedule

Patterncontains

schedule

information

that

A-AUTOfor

UNIX/Windows uses to generate an execution schedule for a Network, i.e. thedates when the Network will execute. Schedule information defines in a Schedule
Pattern includes Holiday ID, Process Pattern, Reference Date, Standard
Processing Date, Process Cycle, Execution Period, and Shift Pattern.

Schedule ID

It is an identifier assigned to a Schedule Pattern.

Schedule Master

It is a Master stores Schedule Pattern information. It references Holiday Tables
that are stored in the Holiday Master.

x

Glossary

Term

Explanation

Schedule Conditions

This is synonymous with Schedule Pattern

Schedule Adjustment

The schedule created by the automatic schedule of Network Schedule screen,
autosche, etc. is adjusted.
In schedule adjustment, the following things can be performed.
An addition and movement of a scheduled date
For any network of any schedule date, change the network attributes
temporarily.

Start Command

Start command is a command that queued (add) a Network into Network Queuefor execution.
It is used when performing rerun of the network that has been terminatedabnormally or when starting an unscheduled network.

Start Time Wait

Set to launch in one of the conditions of the network, but want to run at a specifictime operation. Progress of the specified start time will start business.
It specifies with the values from 00:01 to 47:59.

Start Delay

It is the delay classification in a delay monitoring function. Start Delay happens
when the execution of a Network is not released for execution by a specified time.

Stand-alone Version

The system configuration of the A-AUTO for UNIX / Windows / Linux.
A master is maintained by a Web client and master information is managed on
UNIX/Windows/Linux. (Basic license)
There is the mainframe cooperation version as a form over this.

Second Resource

In user management, you can use Second Resource to restrict the operation of amaster maintenance for various users on a Web screen to certain objects of the
Master..
Objects used in Second Resource are referred to by Identifiers, such as Network
ID, a class, execution classification.

Security Log

This is a log on the activities performed by master maintenance. The contents ofthe master that has been changed on the Web client can be checked. It can also
be exported to the file of csv format.
[A-AUTO Main] screen‐[System Management]‐[Log]‐[Security Log]

Session Recovery Function

When a session disconnection between an A-AUTO Monitor and A-REMOTE is
detected by KeepAlive Function, this is the function to re-establish a session from
A-AUTO Monitor.

Previous Schedule

It is the function to count the schedule range which A-AUTO manages from theprevious month of a CPU date, and to change it by 12 months.

Timer Queue

This is a Queue created in the system memory to enable an A-AUTO Monitor to
manage networks with Data Wait and/or Start Time attributes.
Timer Queue can be re-created by using the XR command.

xiGlossary

Term

Explanation

Time Simulation

This is the function to simulate the scheduled start time and end time of Network
processing using Network Information file, Job Information file and Succeeding
Network Information file). The results of Time Simulation can be viewed on[Network Monitoring List Time chart] screen.

Time chart

One of display formats of the [Network Monitoring List] screen.
It is a Gantt chart that displays the simulated start time and end time of the
networks based on previous execution durations of these Networks.

Multiplicity

Multiplicity refers to concurrent execution of non-dependent Networks or Jobs.

Dummy Job

Dummy job is an imaginary job that is not performed.
Example, it is used when you need to define more than 6 preceding jobs or morethan 16 preceding Networks.

Dummy Network

It is a network which consists of only dummy jobs.

Delay Watch Function

It is a function to detect Start Delay and End Delay.

Chart Editor

It is a flowchart editor that can be used to add a new network or a new job. It canalso used to change of preceding relation between Jobs or Networks in graphicallyformat. This editor is available when performing a network and a job definition..

Chart Screen

It is a screen which displays the preceding and succeeding relation between
networks as well as between jobs in flowchart format. Chart screens include thefollowing screens.
[Network Definition Chart], [Job in Network Definition], [Network Monitoring List
Chart], [Detailed Job Info].

Data ID

It is an identifier for Input Data Wait information.

Input Data Wait

It is an attribute that can be defined for a Network. It is used to represent a wait for
arrival of the data created externally or an external event.

Network

It is the smallest unit of business to be managed by A-AUTO
It may consist of one or more jobs and is a unit of processing on A-AUTO in all
master maintenance / schedule / instruction execution time
The network attribute / job attribute concerning execution by A-AUTO Monitor canbe defined.

Network Schedule

A Network Schedule contains the dates of when a Network is scheduled to
execute i.e. the schedule of a Network. When a Network is linked or associatedwith one or more Schedule Patterns, A-AUTO for UNIX/Windows automaticallygenerates a Network Schedule for the Network based on schedule information of
the Schedule Patterns.

Network ID

It is the identifier for a Network.

xii

Glossary

Term

Explanation

Network Queue

Network Queue refers to both the memory (Network Queue buffer) and a file(network Queue file) that store the information of Networks that are waiting forexecution by A-AUTO Monitor.

Network Queue Buffer

Refers to an area in the memory management that stores the information of the
Network Queue.
It is for attaining improvement in the speed of search of network queue.

Network Queue File

Is a file that stores information about the Network Queue.
It is a control file that is used to resume the execution of Networks when A-AUTO
Monitor is restarted.

Network Group

It is a group for simplifying network management.
One Network may belong to only one group.

Network Group ID

The identifier for a Network Group.

Network Group Master

It is a master that stores Network Group information.

Network Group Name

It is an identifier for a Network Group.

Max Executing Time

It is maximum permissible processing time for a Network.
When the duration of execution of a Network exceeds this time, an alert can besent or the Network can be cancelled, depending on setting during registration.

Network Attribute / Job Attribute

This refers to the conditions and characteristics that are defined for a Network or
job in the Network Master.

Network Master

It is a master stores network information / job information.

Expanded Name

It is the comment information for a network.

Network Log (Network Log File)

It is a log that records the details of each Network that was executed by A-AUTO
Monitor. The size of the log file is specified in System Parameter file. When thenumber of log records reaches the specified size of the file, a backup file isautomatically created. This prevents the file from becoming too large. * Whether
backup is performed or not depends on system setting.

Exclusion Schedule.

Exclusion Schedule is used to exclude or remove certain execution schedule
dates from the Network Schedule that is generated by associating a Network with
one or more Schedule Patterns

Exclusive Control Function

This function provides the same facilities as Resource Management Function.

Valid Date

This is the date for the Network Information of a Network to become effective. You
can specify up to 5 Valid Dates for a single Network.

Parameter Transfer

It is a function that passes pre-defined parameters to a job.
Depending on the run type of job (reruns type and normal type), you can passdifferent parameters.

xiiiGlossary

Term

Explanation

Parallel Run (Job Parallel Process)This is an attribute that can be defined for a Network. If defined, it allows Jobs thatare not dependent on each other to be executed in parallel (concurrently) as muchas possible.

For non-dependent Jobs in a Network that is not defined with Parallel Run
attribute, A-AUTO Monitor performs one job at a time according to the order of the
Job Number defines for the Job.
Daily Network Schedule

It is a Network Schedule for a specific day. It provides information of networks thatare scheduled for that day.

Daily Schedule Change Network

It is a master which manages Daily Network Schedule. Information to add change

Masterto temporarily is managed to the arbitrary networks of arbitrary days.

Standard Processing Date

Standard Processing Date is used to define from which date onward thescheduling of a Network may begin. A-AUTO for UNIX/Windows computes thedates on which a Network is to be scheduled based on Standard Processing Dateand Process Cycle as well as other schedule information. There are three types offormat for defining Standard Processing Date.
Specify in YYYY/MM/DD format. This format is available only when
'Calendar' is specified for Process Pattern. However, this format cannot be
selected when the Process Cycle is either 'Weekly' or 'Biweekly'.

Specify in YYYY/MM/WW/DD of the week format. This format can be
specified when Calendar is specified for Process Pattern and the Process
Cycle is other than ‘Daily’ or ‘at intervals of n days’.

Specify in Year, Fiscal month, and ＋－ day format. This format can be
specified when Working day is specified for Process Pattern.

Specify +1 for the first Working Day of the Fiscal month. Specify -1 for the last
Working Day of the Fiscal month. Holidays are ignored.
Load Balance

Is the same meaning as defined load balancing capabilities.

Irregular Schedule

An Irregular Schedule refers to a schedule that does not have a regular or fixed
cycle.

Priority

It is an attribute that can be defined for a Network.

When two or more Networks are ready to be executed, the one with higher priority
will be started first.

A priority of "15" is the highest while "01" is the lowest.
Default assigned at the time of registration is "06".
For a Network queued by the Start command, the priority assigned to the Network
is "08".

xiv

Glossary

Term

Explanation

Substituted if Falls on a Holiday

If an Annual Holiday falls on a Sunday and Sunday is defined as a Weekly
Holiday, selecting "Substituted if falls on a Holiday" function will shift the Annual
Holiday to the next day. (Substitution will not occur if Sunday is not defined as a
Weekly Holiday.).

Job Execution Condition

It is a value of the return code of a job or user plug-in. A following job will be
performed if conditions are fulfilled. When not specified, the end status of apreceding job becomes the condition.

Hold Code

Hold code is an identifier specified when adding a hold attribute.
By employing some company’s specific convention, different Hold Code can beused to represent different reasons for holding Networks.

Hold Attribute

It is an attribute that can be defined for a Network. Hold attribute is one of the
network Starting Conditions.
Network with Hold attribute will not be run after queuing process. It must be
manually released by Monitor command.

Holiday ID

It is an identifier assigned to a Calendar, which contains holiday information, in
Holiday Master.

Holiday Master

It is a master that stores calendars containing different the holiday information.
Three types of holiday can be defined.
Day of the week (weekly), A specific day each year (Annual holiday) andSpecific date.
You can also change the working days of the date of a particular holiday

Cross-Master Linkage

Cross-Master Linkage is a function that enables the processing of Networks withpreceding relations across different A-AUTO systems, which can be on the sameor different platforms.
* In order to use the Cross-Master Linkage, A-AUTO/Connect option is required.

Cross-Master Preceding Network

Cross-Master Preceding Network refers to a Network that is stored in other
A-AUTO system but is defined as a preceding Network for a Network in thecurrent A-AUTO System.

xv

Glossary

Term

Explanation

Max Return Code

Max Return Code is a value that is used by A-AUTO Monitor to determine the end
status of a Job. If the return code of a Job is used to determine whether the Job
has ended normally, please specify a value for the return code within the range 0 127. When a Job ends with a return code that is equal to or more than that of Max
Return Code, A-AUTO Monitor treats the Job as abnormally ended. Therefore, thesucceeding Jobs in the same Network will not be executed. If a Job ends
abnormally, the Network that contains the Job will be treated as abnormally ended
too.
If the return code of a Job is not to be used to determine whether the Job has
ended normally, specify “0” for Max Return Code.

Unmet Execution Attribute

It is an attribute which has not been canceled yet among the attributes added to
the network. It can check from an operating surveillance monitor.

Mainframe Connection

It is an A-AUTO system configuration where A-AUTO for Mainframe schedules,(Mainframe Connection Option)

manages and controls the operations for A-AUTO for UNIX/Windows/Linux
residing in servers of Open System.
This enables preceding and succeeding relation to be defined for Network acrossMainframe, UNIX, Windows and Linux servers. All of master information(maintenance) and schedule information are managed in a unified manner on amainframe.
Consists of a mainframe version A-AUTO Monitor, A-LOCAL, armt, and an open
version A-AUTO Monitor.

Monitor Attribute

This is an attribute that can be defined for a Network with Input Data Wait
attribute. It can be set “ON” so that Monitor On Wait Condition is automaticallycancelled after the end of execution of a network with Input Data Wait Attribute.

Monitor Command

A command that is issued to the A-AUTO Monitor. It is issued using a Web client
or a cip utility. It instructs A-AUTO Monitor to perform some operations such as
starting a Network.

User Plug-in

This is a user program that is created to perform an additional function at specifictiming of a Job execution.

Recovery Job

One of the Job Branching function. It is a job to execute if a specific job has
terminated abnormally.

Recovery Network

This is a Network (for recovery) to be started when a Network that has abnormallyended is rerun. This Network (for recovery) is started and executed. The actual
Network that has abnormally ended will be started only after this Network (forrecovery) has ended. This function is not recommended for V710 or later. In V710
or later, Recovery Job can be defined in Network Master.

xvi

Glossary

Term

Explanation

Reset Command

It is a command which changes attributes of a Network in Network Queue.
Attributes such as Class, and Priority can be changed.
Example :Resource Groupe_Network ID class=C

Resource Group is the definition patterns of authorization types and resources.
Users with the same authorization for the same resources can then be linked tothe same group. This enables easy maintenance.

Resource Management Function

Resource Management

Function manages and controls Resources allocation.

Resources in A-AUTO refers to logical resources that are defined in advance in
Job Extended Master.
Job Return Code Divergent Function

When an A-AUTO top preceding job carries out a normal end, a following job isbranched by one of the Job Return Code Divergent Function by the return code.

Remote Job Execute

When an A-AUTO System has to schedule and execute Networks on its own
server as well as other servers, each of the other servers will require acomponent, called Remote Job Execute, to be installed. This component will
execute Job based on instruction from A-AUTO Monitor. When the executed Job
has completed processing, it will return information about the ended Job to
A-AUTO Monitor.
It is also called a remote license or A-REMOTE.

Remote Job Recovery Function

When an A-AUTO Monitor After down restart, it is a function which carries out
continuous execution of the job of A-REMOTE.
After down restart after, an A-AUTO Monitor establishes a session with
A-REMOTE, acquires the execution situation of the job of A-REMOTE, andrestores the remote job used as the end of execution during execution during astop.

Remote Job Suspension of

A stop command is automatically published about the unperformed job by which

Recovered Network

recovery was carried out by an remote job recovery function. It is a function which
is made not to be performed immediately even if it meets an execution condition.

Rerun

It is to re-execute a Network that has abnormally ended.

Rerun Type

This is the Run Type assigned to a Network when it is started again after it has
abnormally ended.
The end check of a preceding network is not performed.

Rerun Recovery Function

This is a function that will automatically start a Recovery Network when a Networkthat has abnormally ended is rerun. The Recovery Network must be pre-defined.
xvii

Glossary

Term

Explanation

Release Command

This is the command to release the hold state of the Network Queue, a Network or
Partition.
Example : a_Network ID 20100315

Replicate Function

This function performs a synchronization process of information (database) masterserver to be managed by A-AUTO master and monitors to be managed by
A-AUTO.
Replicated processing will be conducted in the following timing.
AP Server is connected to the A-AUTO Agent ( automatic )When renewal of the masters by a utility is performed (automatic)
Compulsive replicate by manual operation from a Web client is performed

Load balance function

It is also called a Load Distribution Function.. This function distributes Networks toservers (System Qualifiers) defined in a System Group Qualifier for execution.
One of the following methods can be specified as a criterion to be used for the
distribution; round-robin system, Waiting Queue length, Evaluation of CPU
utilization

Long Job Name Function

It is also refer to as Job Name Conversion Function.

Work

A Work unit refers to a set of events to be monitored and actions to be taken.

Work IDWork ID is an identifier assigned to a Work unit.

Work Monitoring

This refers to the monitoring of the execution of works. In the Web client, you canmonitor the status using [Work Monitor List] screen.

xviii

Master Information Input Item List

Master Information Input Item List
The information of input values for the various master and their limitation are given in this list. When deciding naming
conventions for Master items, entering information from Web Client and editing Master information in CSV format, please
use the list as a guide.

Master Name
Network Group Master

Item Name

Size

Network Group ID

Valid Date

8 digits or
less
32 digits or
less
10 digits

Network ID

2~8 digits

Network Expanded Name

20 digits or
less-

Network Group Comment
Network MasterStart Time
Preceding Network Number-

System Qualifier
System Group Qualifier
User Information
Document Information
Class
Hold CodeJob Executing User ID

Interval (min)Max number of Network is 16

1 digit

1~9、A~Z(One-byte), or, not specified

1~8 digits

One-byte Capital Letter, Number, #,$, @,or, not specified
1~2879 (Number)

Max Executing Time
Response To Max Time

Job Number

1~3 digits

i00:01~47:59

One-byte Capital Letter, Number, #,$, @,\
One-byte Capital Letter, Number, #,$, @,\
Optional

64 digits or
less
64 digits or
less
1~4 digits-

Plug-in After Start

yyyy/mm/dd
yyyymmdd
One-byte Capital Letter and Number,#, $, @
But it cannot be registered with thereserved word of A-AUTO as thefollowing ID.
ATE、LMCP、LOSE、LOSEE、LOSET、NP001~NP999、
JP001~JP999、PARM、SCVT、START、SYS、TSK(NP, JP and NP(JP)+3 digits Number
are reserved word, but JP1,NP99 canbe registered)
optional

8 digits or
less
8 digits or
less
12 digits or
less
50 digits or
less
1 digit-Plug-in Before Start

Characters/ scope may be
specified
One-byte Capital Letter, Number, #,$, @optional

Optional
1~9、A~Z(One-byte)

Optional
Optional
1~2880(Number), or, not specified
Select one of the followings.
W: Only Display Warning Message
C: Display Warning Message And
Network Cancel
not specified
1~999 (Number)
Job Number specified must be uniquein the same Network.

Master Information Input Item List

Master Name

Item Name

Size

Job ID

1~8 digits

Characters/ scope may be
specified
One-byte Capital Letter, Number, #,$, @,But the first digit must be alphabetic
letters or #, $, @.

(Number cannot be used for the first
digit)
Job User Field
Preceding Job Number(Specify
Preceding Job Number)

Number of Jobs in 1 Network

Max number of Job is 6
Specify Job Number that must be
lesser than the registered Number.

Max number of Job is 32.

Max Return Code

1~3 digits

0~127(One-byte Number)

Plug-in Before Start

64 digits or
less
64 digits orless
2 digits

Optional

8 digits or
less
44 digits or
less-One-byte Capital Letter, Number, #,$, @Optional

Priority
Data ID
Comment(Input Data Wait Master)
The relations between Network
ID and Data ID

Holiday Master

Holiday ID

Schedule Master

Comment(Holiday Master(Holiday))
Date that can be registered in
Holiday List
Comment(Holiday Master(Holiday
Setting))
Schedule ID
Comment(Schedule Master)
Associated Schedule MasternumberExecution ID

Work

optional-

Plug-in After Start

Input Data Wait Master12 digits or
less-Standard Processing Date thatyou can register.
Work ID
Comment(Event Management Master)Start Time(Event Management Master)
End Time(Event Management Master)
Event ID number
Action ID number
Comment(Event ID)ii

20 digits or
less
50 digits or
less
50 digits or
less

Optional
01~15

1 Network ID can related with Data
ID: Max 5
1 Data ID can related with Network
ID: Max 13
One-byte Capital Letter, Number, #,$, @Optional
January 1 ~ December 31
But, February 29 cannot be specified.
Optional

20 digits or
less
50 digits or
lessOne-byte Capital Letter, Number, #,$, @Optional-

Max number of Schedule ID is 32.

1 digits

0、1~9、A~Z
In the case of Irregular: 0
In the case of not Irregular: 1~9,A~Z
Max number is 32.

13 digits or
less
32 digits or
less-

Cannot use <>,'"&%¥+# and space
Optional
00:00~23:55-

00:00~23:59

32 digits or
less

Max is 100
Max is 100
Optional

Master Information Input Item List

Master Name

Item Name

Size

Event occurring computer name

16 digits or
less
63 digits or
lessProcess File
(Job Event)File Name(File Event)ID(Message Event)
Starting position(Message Event)

String(Message Event)Application Event ID(Application Event)Application Event Parameter(Application Event)
Comment(Action ID)
Job Name(Job Execution)
Parameter(Job Execution)
Message(Message Output)
Send Information Parameter File
(Send Mail)
Network Name
(Send Start Command)iii

256 digits
or less
63 digits or
less
Togetherwith Stringis 18 digits
or less
Togetherwith Stringis 18 digits
or less
63 digits or
less
20 digits or
less
32 digits orless
256 digits
or less
256 digits
or less
256 digits
or less
256 digits
or less
256 digits
or less

Characters/ scope may be
specifiedEnglish Number(only One-byte)
Optional
Optional
Optional
English Number(only One-byte)

Optional

Optional
Optional
Optional
Optional
Optional
Optional
Optional
One-byte Number,#,$,@