Contents

• Notices

• Summary of amendments

• Preface

• 1. Overview of Work Task Design

  • 1.1 Flow of work task design

  • 1.2 Automating work tasks

  • 1.3 Flow of work task automation

  • 1.4 Key decisions when planning work task automation

• 2. Job Definition and Job Execution Order Considerations

  • 2.1 Job definition considerations

    • 2.1.1 Investigating tasks to automate

    • 2.1.2 Designing executable files

    • 2.1.3 Job type considerations

    • 2.1.4 Job definition considerations

  • 2.2 Jobnet definition considerations

    • 2.2.1 Job execution order considerations

    • 2.2.2 Corrective action when job execution fails

    • 2.2.3 Jobnet definition considerations

    • 2.2.4 Using jobnet connectors to control the order of root jobnet execution

    • 2.2.5 Using wait conditions to control the order of unit execution

    • 2.2.6 Considerations regarding the use of macro variables

  • 2.3 Tips on work task automation

    • 2.3.1 Processing with a distributed load

    • 2.3.2 JP1/AJS3 functions useful for work task automation

  • 2.4 Jobnet definition examples

    • 2.4.1 Executing a process in a specified file (example of defining a jobnet consisting of standard jobs)

    • 2.4.2 Executing a process when one of multiple conditions is satisfied (example of defining a jobnet that uses an OR job)

    • 2.4.3 Dynamically changing a process depending on the result of a preceding job (example of defining a jobnet that uses a judgment job)

    • 2.4.4 Executing an event-driven process (example of defining a jobnet that uses an event job)

    • 2.4.5 Sending a JP1 event at completion of the preceding job or when an event occurs (example of defining a jobnet that uses a Send JP1 event job)

    • 2.4.6 Executing a specific process when a job ends abnormally (example of defining a jobnet that uses a recovery unit)

    • 2.4.7 Controlling the execution order of a root jobnet (example of defining a jobnet that uses a jobnet connector)

    • 2.4.8 Controlling the order of unit execution in different jobnets (example of defining a jobnet that uses a wait condition)

    • 2.4.9 Passing information that changes dynamically to a succeeding unit (example of defining a jobnet that uses a passing information setting job)

    • 2.4.10 Executing jobs in a cloud environment (example of defining a jobnet that uses flexible jobs)

    • 2.4.11 Executing a job on multiple execution agents simultaneously (example of defining a jobnet that uses flexible jobs)

    • 2.4.12 Linking with a business system on the web (example of defining a jobnet that uses HTTP connection jobs)

    • 2.4.13 Automatic retry for abnormally ending jobs

• 3. Operation Calendar and Execution Schedule Considerations

  • 3.1 Flow of calendar and schedule planning

  • 3.2 Considerations when defining a calendar for JP1/AJS3 operation

  • 3.3 Considerations when defining a jobnet execution schedule

  • 3.4 Start condition considerations

    • 3.4.1 Detailed considerations

  • 3.5 Setting schedules

    • 3.5.1 Establishing schedules for applications that extend over two days

    • 3.5.2 Setting multiple execution start times

    • 3.5.3 Defining a different schedule for some jobs in a jobnet

    • 3.5.4 Executing the same jobnet several times a day (defining cycle jobs)

    • 3.5.5 Shifting the scheduled execution date forward or back based on a calculated schedule (Schedule by days from start)

    • 3.5.6 Defining a schedule that has different behavior at different times of the month

    • 3.5.7 Defining a different calendar for each application

• 4. Execution Registration Method Considerations

  • 4.1 Jobnet execution registration methods

    • 4.1.1 Planned execution registration

    • 4.1.2 Fixed execution registration

    • 4.1.3 Immediate execution registration

• 5. Monitoring Method Considerations

  • 5.1 Monitoring methods in JP1/AJS3 - View

    • 5.1.1 Planning which work tasks to monitor in the Summary Monitor window

    • 5.1.2 Jobnet delay monitoring considerations

    • 5.1.3 End delay monitoring based on time-required-for-execution

  • 5.2 Considerations for monitoring by using a Web GUI

    • 5.2.1 Considering what to monitor in the Dashboard screen

  • 5.3 Considerations for monitoring by using an API-based user application

• 6. Access Permission Considerations

  • 6.1 Steps for considering work task access permissions

  • 6.2 Ranges for setting access permissions

  • 6.3 Setting registered users

  • 6.4 Setting access permissions

    • 6.4.1 Access permission considerations

  • 6.5 Mapping users

    • 6.5.1 Considerations when mapping users

• 7. Cautionary Notes on Designing Work Tasks

  • 7.1 Notes on the number of root jobnets registered for execution

  • 7.2 Relationship between number of logs to keep and performance

  • 7.3 Notes on using PC jobs

  • 7.4 Notes on using Unix jobs

  • 7.5 Notes on using a recovery unit

  • 7.6 Notes on using event jobs

    • 7.6.1 Notes on the Receive JP1 Event job

    • 7.6.2 Notes on the Monitoring Files job

    • 7.6.3 Notes on the Receive Mail job

    • 7.6.4 Notes on the Monitoring Log Files job

    • 7.6.5 Notes on the Monitoring Event Log job

    • 7.6.6 Notes on the Interval Control job

    • 7.6.7 Notes on defining passing information

    • 7.6.8 Notes on restarting the JP1/AJS3 service while event jobs are running

    • 7.6.9 Monitoring events or messages issued by JP1/AJS3

  • 7.7 Notes on using action jobs

    • 7.7.1 Notes on the Send JP1 Event job

    • 7.7.2 Notes on the Send Mail job

    • 7.7.3 Notes on the OpenView Status Report job

    • 7.7.4 Notes on the Local Power Control job and Remote Power Control job

  • 7.8 Notes on using flexible jobs

  • 7.9 Notes on using HTTP connection jobs

  • 7.10 Notes on defining jobs

    • 7.10.1 Notes on the standard output file and standard error output file

    • 7.10.2 Notes on the execution priority of jobs

    • 7.10.3 Checking the return code of a job

• 8. Definition Pre-Check

  • 8.1 Checking definitions before live JP1/AJS3 operation

    • 8.1.1 Overview of the definition pre-check function and cautionary notes

• Appendixes

  • A. Return Values from Event Jobs and Action Jobs

  • B. Information Passed by Event Jobs

  • C. Files Used for HTTP Connection Jobs

    • C.1 Connection configuration file

    • C.2 Transfer information file

    • C.3 Status file

    • C.4 Received header file

    • C.5 Received body file

  • D. Version Revisions

    • D.1 Revisions in 11-50

    • D.2 Revisions in 11-10

    • D.3 Revisions in 11-00

    • D.4 Revisions in 10-50

    • D.5 Revisions in 10-10

    • D.6 Revisions in 10-00

    • D.7 Revisions in 09-00

  • E. Reference Material for This Manual

    • E.1 Related publications

    • E.2 Conventions: Abbreviations for product names

    • E.3 Conventions: Acronyms

    • E.4 Conventions: Diagrams

    • E.5 Conventions: Fonts and symbols

    • E.6 Conventions: KB, MB, GB, and TB

    • E.7 Conventions: Meaning of "directory" and "folder"

    • E.8 Conventions: Version numbers

    • E.9 About administrator privileges

    • E.10 About the Start menu in Windows

    • E.11 Default installation folders of JP1/AJS3 for Windows

    • E.12 Online manual

    • E.13 Regular expressions available in JP1/AJS3

    • E.14 About the 3rd level and 4th level Kanji characters added in JIS 2004 (JIS X 0213:2004)

    • E.15 About NNM linkage

  • F. Glossary

• Index

To Page Top