Job Management Partner 1 Version 10 Job Management Partner 1/Automatic Job Management System 3 Messages 1 3021-3-329-10(E)
Notices ■ Relevant program products For details about the applicable OS versions, and the service packs and patches required for Job Management Partner 1/Automatic Job Management System 3, see the Release Notes.
P-CC2A12-34AL Job Management Partner 1/Automatic Job Management System 3 - View version 10-10 (For Windows 8, Windows Server 2012, Windows 7, Windows Server 2008 and Windows Vista) P-CC2412-34AL Job Management Partner 1/Automatic Job Management System 3 - View version 10-10 (For Windows Server 2003, Windows Server 2003(x64), and Windows XP Professional) Job Management Partner 1/Base# (For Windows): P-2W2C-6LAL Job Management Partner 1/Base# version 10-10 The above product includes the following: P-CC2A2C-6L
Microsoft Exchange server is a product name of Microsoft Corporation in the U.S. and other countries. Microsoft Office and Excel are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. MQSeries is a trademark of International Business Machines Corporation in the United States, other countries, or both. MVS is a trademark of International Business Machines Corporation in the United States, other countries, or both.
Abbreviation Full name or meaning Excel Microsoft(R) Office Excel Exchange Server Microsoft(R) Exchange 2000 Enterprise Server Microsoft(R) Exchange 2000 Server Microsoft(R) Exchange Server IE Internet Explorer Microsoft(R) Internet Explorer(R) Windows(R) Internet Explorer(R) Microsoft Mail Microsoft(R) Mail Microsoft SQL Server Microsoft(R) SQL Server Microsoft(R) SQL Server Enterprise Edition MSCS Microsoft(R) Cluster Server MSMQ Microsoft(R) Message Queue Server Outlook Outlook 2003 Mi
Abbreviation Windows Server 2008 Full name or meaning Windows Server 2008 Microsoft(R) Windows Server(R) 2008 Enterprise Microsoft(R) Windows Server(R) 2008 Standard Windows Server 2008 R2 Microsoft(R) Windows Server(R) 2008 R2 Datacenter Microsoft(R) Windows Server(R) 2008 R2 Enterprise Microsoft(R) Windows Server(R) 2008 R2 Standard Windows Server 2012 Microsoft(R) Windows Server(R) 2012 Datacenter Microsoft(R) Windows Server(R) 2012 Standard Windows Vista Microsoft(R) Windows Vista(R) Business Mi
Summary of amendments The following table lists changes in the manuals (3021-3-318-10(E), 3021-3-319-10(E), 3021-3-320-10(E), 3021-3-321-10(E), 3021-3-322-10(E), 3021-3-323-10(E), 3021-3-324-10(E), 3021-3-325-10(E), 3021-3-326-10(E), 3021-3-327-10(E), 3021-3-328-10(E), 3021-3-329-10(E), and 3021-3-330-10(E)) and product changes related to these manuals. Changes Location A function was added that restricts, by using IP addresses, the hosts that are able to connect to a manager host and an agent host.
Changes Location A function was added for checking the execution schedule of unregistered units in the Monthly Schedule window of JP1/AJS3 - View. System Design (Work Tasks) Guide: -Configuration Guide 1: -Configuration Guide 2: -Administration Guide: -Troubleshooting: -Operator's Guide: 6.1, 6.4, 11.1.2, 11.3.9, 11.9, 11.9.8, 15.3.2(1), 15.3.42(4), 15.7.2, 15.7.3, 15.8.1, 15.8.2, 15.8.3 Command Reference 1: -Command Reference 2: -Linkage Guide: -Messages 1: -Messages 2: 1.
Changes Location A function was added for preventing scheduler services for which the JP1 user logged in to JP1/AJS3 - View has no access privileges from appearing in JP1/AJS3 - View. 1.2 KAVV187-E A function was added for restricting the maximum number of allowed JP1/ AJS3 - View concurrent sessions for a scheduler service. Overview: -System Design (Configuration) Guide: -System Design (Work Tasks) Guide: -Configuration Guide 1: 6.1.10, 15.1.11 Configuration Guide 2: 2.2.1, 2.2.2(13), 2.2.
Changes Location A function was added for changing the passwords of JP1 users by using JP1/ AJS3 - View. -Command Reference 2: -Linkage Guide: -Messages 1: 2.2 KAVC4511-E 2.3 KAVS1010-I, KAVS1011-E, KAVS1015-I Messages 2: 1.2 KAVV457-E, KAVV3342-I to KAVV3349-E The way in which the Register Custom Job dialog box and the Set Properties of Custom Job dialog box are displayed was changed.
Changes Location A change was made so that when Jobnet Definition is selected from Function Menu, jobnets for which execution has been registered are displayed in the list area of the JP1/AJS3 - View window (main window). -Configuration Guide 2: -Administration Guide: -Troubleshooting: -Operator's Guide: 11.1.2, 11.4, 11.4.17, 15.3.1(1) Command Reference 1: -Command Reference 2: -Linkage Guide: -Messages 1: -Messages 2: 1.
Changes Location A function was added for preventing the history of previously-used login-user names and connection-destination host names from appearing on the Login screen. Overview: -System Design (Configuration) Guide: 2.7, 4.5, 4.5.2, 4.5.3 System Design (Work Tasks) Guide: -Configuration Guide 1: -Configuration Guide 2: -Administration Guide: 2.2.4(1), 2.3.5(2) Troubleshooting: A.3, A.6 Operator's Guide: 3.1, 11.1.1, 11.1.2, 11.2, 11.2.6, 13.2.1, 14.1, 14.1.1, 14.2, 14.2.6, 15.2, 16.
Changes Location Content related to Solaris 11 (SPARC) was added. -Command Reference 2: 2. ajsembdbsetup, 2. jajs_setup, 2. jajs_setup_cluster Linkage Guide: 2.5.4 Messages 1: -Messages 2: 1.
Preface This manual describes the format of messages for Job Management Partner 1/Automatic Job Management System 3 (abbreviated hereafter to JP1/AJS3), and lists the messages beginning from KAJS to KAVT. This manual also describes how to take actions for the messages. ■ Intended readers This manual is intended for: • Those who wish to operate an automatic job execution system with JP1/AJS3 and those who design automatic job execution systems.
Text formatting Monospace Convention • At the prompt, enter dir. • Use the send command to send mail. • The following message is displayed: The password is incorrect. The following table explains the symbols used in this manual: Symbol Convention | In syntax explanations, a vertical bar separates multiple items, and has the meaning of OR. For example: A|B|C means A, or B, or C. { } In syntax explanations, curly brackets indicate that only one of the enclosed items is to be selected.
Symbol Convention <> (angle brackets) 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, A, B, C, D, E, or F A system-determined name assigned to a file The directories contained in the path, with each name separated by a forward slash (/) or backslash (\). The path notation is OS-dependent. (( )) (double parentheses) << >> (double angle brackets) MAX Indicates the range of specifiable values. Indicates the default assumed by the system when a value is unspecified.
No.
Purpose Required reading Read as necessary To learn about JP1/AJS3's functionalities • Overview (3021-3-318(E)) • Linkage Guide (3021-3-328(E)) To configure a system (including installation and setup) that automatically runs jobs • System Design (Configuration) Guide (3021-3-319(E)) • Configuration Guide 1 (3021-3-321(E)) • Configuration Guide 2 (3021-3-322(E)) • Linkage Guide (3021-3-328(E)) To design work tasks that will be automated (including job definitions and schedule definitions) • System
Purpose Required reading To learn about operating JP1/AJS3 Job Management Partner 1/Automatic Job Management System 3 Messages 1 (3021-3-325(E)) Read as necessary (3021-3-326(E)) • Command Reference 2 (3021-3-327(E)) 19
Contents Notices 2 Summary of amendments Preface 7 14 1 Overview of JP1/AJS3 Messages 22 1.1 Types of messages 1.2 Message format 1.2.1 Format of output messages 1.2.2 Format of message explanations 1.2.3 To the system administrators 1.3 List of output destinations for messages 1.3.1 Output destinations of messages beginning with KAJS 30 1.3.2 Output destinations of messages beginning with KAVC 30 1.3.3 Output destinations of messages beginning with KAVS 35 1.3.
B Reference Material for This Manual 797 B.1 Related publications B.2 Conventions: Abbreviations for product names B.3 Conventions: Acronyms B.4 Conventions: KB, MB, GB, and TB B.5 Conventions: Meaning of "directory" and "folder" B.6 Conventions: Meaning of "member of the Administrators group" B.7 Default installation folders of JP1/AJS3 for Windows B.8 About the Start menu in Windows B.9 Online manual B.10 Regular expressions available in JP1/AJS3 B.
1 Overview of JP1/AJS3 Messages This chapter lists the manuals that contain information about messages output by JP1/AJS3, JP1/ Base, and JP1/IM. This chapter also explains the format of the JP1/AJS3 messages, and lists the output destinations and the Windows event logs and syslogs.
1.1 Types of messages This chapter lists the manuals that contain information about the messages output by JP1/AJS3, JP1/Base, and JP1/IM. When you operate a system using JP1/AJS3, the system also outputs messages for JP1/Base that is a prerequisite program, in addition to JP1/AJS3 messages. If you link JP1/AJS3 with JP1/IM, the system also outputs JP1/IM messages.
1.2 Message format This section explains the output format of JP1/AJS3 messages and the description format of messages in this manual. JP1/AJS3 supports both Japanese and English messages. In UNIX, you can use the LANG environment variable to specify for each user which language is to be used to display messages. 1.2.1 Format of output messages (1) Messages beginning with KAJ This subsection describes the format of messages related to JP1/AJS3 passing information setting jobs.
Message level Type of Windows event log Level Meaning -I Information Notice of holding a job, start of job execution, normal end of a job, start of monitoring, etc. -Q Not applicable Not applicable The following table shows the correspondence between the message levels and the priority levels of UNIX syslogs. Table 1‒3: Message levels and priority levels of syslogs Message level Priority level of syslog Level Meaning -E LOG_ERR System error, abnormal end of a job, monitoring failure, etc.
Warning message. Processing continues after message output. • I Information message. Reports information to the user. • Q Query message. Prompts the user to respond. • K Continuation message. Processing continues. The following table shows the correspondence between the message levels and the Windows event logs. Table 1‒4: Message levels and Windows event logs Message level Type of Windows event log Level Meaning -E Error System error, abnormal end of a job, monitoring failure, etc.
Z Message type, as one of the following: • E Error message. Processing is canceled. However, if you specify more than one name using a command, the system outputs this message for each name and continues command processing. • W Warning message. Processing continues after message output. • I Information message. Reports information to the user. • Q Query message. Prompts the user to respond. • K Continuation message. Processing continues.
Characters in italic vary each time the system displays a message. Messages are explained in the ascending order of message IDs. Message ID Message text: message text Explanation of the output message text. (S) System action (O) Operator action at message output (2) Messages beginning with KAV Messages are explained in the following format in this manual. Characters in italic vary each time the system displays a message. Messages are explained in the ascending order of message IDs.
(P) Programmer action at message output (O) Operator action at message output Action Action that the embedded database system administrator must take when the message is received. # Output destination of the message. For details, see 1.3.7 Output destinations of messages beginning with KFP. (4) Messages beginning with KNA Messages beginning with KNA are explained in the following format in this manual. Characters in italic vary each time the system displays a message.
1.3 List of output destinations for messages This section lists the output destinations of the messages that are output by JP1/AJS3. 1.3.1 Output destinations of messages beginning with KAJS The table below lists the output destinations of messages beginning with KAJS (messages about passing information setting jobs ).
stderr: Standard error output Y: Is output. --: Is not output.
The table uses the following abbreviations for the output destinations: syslog: syslog Event log: Windows event log HNTRLib2: Integrated trace log stdout: Standard output stderr: Standard error output Y: Is output. --: Is not output.
(3) KAVC4001 to KAVC6000 (messages about JP1/AJS3 Console View) The following table lists the output destinations of messages about JP1/AJS3 Console View. The table uses the following abbreviations for the output destinations: Dialog: Message dialog box Log: JP1/AJS3 Console View log file# stderr: Standard error output Y: Is output. --: Is not output.
Message ID Output destination Dialog Log stderr KAVC4104 -- Y -- KAVC4106 Y Y -- KAVC4107 KAVC4111 -- Y -- KAVC4112 Y -- -- KAVC4113 KAVC4114 -- Y -- KAVC4115 KAVC4116 Y Y -- KAVC4117 KAVC4119 -- Y -- KAVC4220 Y Y -- KAVC4221 -- Y -- KAVC4222 Y Y -- KAVC4223 Y -- -- KAVC4224 Y Y -- KAVC4232 -- Y -- KAVC4233 Y Y -- KAVC4234 -- Y -- KAVC4302 KAVC4523 Y Y -- KAVC4524 -- Y -- KAVC4525 KAVC4530 Y Y -- KAVC4537 KAVC4559 -- Y -- KAVC45
(4) KAVC6001 to KAVC7000 (messages for unknown status or operation failure) These messages are displayed in a dialog box on JP1/AJS3 Console View. The output destination differs depending on the situation in which the message is output. • If the status of the monitored object displayed in JP1/AJS3 Console View is Unknown: A message indicating the cause of the error is output to the Information text area in the Detail Information - [AJS3 Unit Monitored Objects] dialog box.
Message ID Output destination syslog Event log HNTRLib2 stdout stderr Exec details JP1 event KAVS0130 -- -- -- -- Y -- -- KAVS0132 KAVS0135 Y Y Y -- -- -- -- KAVS0141 KAVS0167 -- -- -- -- Y -- -- KAVS0168 Y Y Y -- Y -- -- KAVS0169 KAVS0175 -- -- -- -- Y -- -- KAVS0176 Y Y Y -- Y -- -- KAVS0177 KAVS0188 -- -- -- -- Y -- -- KAVS0189 Y Y Y -- Y -- -- KAVS0190 KAVS0199 -- -- -- -- Y -- -- KAVS0200 KAVS0201 Y#1 Y#1 Y -- -- --
Message ID Output destination syslog Event log HNTRLib2 stdout stderr Exec details JP1 event KAVS0247 -- -- Y -- -- -- -- KAVS0248 Y#5 Y#5 Y -- -- -- Y KAVS0249 -- -- Y#4 -- -- -- -- KAVS0260 KAVS0262 Y#3 Y#3 Y -- -- -- Y KAVS0263 KAVS0264 Y#5 Y#5 Y -- -- -- Y KAVS0265 Y#5, #6 Y#5 Y -- -- -- Y KAVS0266 Y#5 Y#5 -- -- -- -- Y KAVS0267 Y Y Y -- -- -- -- KAVS0268 Y#3 Y#3 Y -- -- -- Y KAVS0269 Y#5 Y#5 Y -- -- -- Y KAVS0270 Y
Message ID Output destination syslog KAVS0500 Event log HNTRLib2 stdout stderr Exec details JP1 event Y Y Y -- -- -- -- KAVS0530 -.
Message ID Output destination syslog Event log HNTRLib2 stdout stderr Exec details JP1 event KAVS0893 -- -- Y -- -- -- -- KAVS0894 KAVS0898 -- -- -- -- Y -- -- KAVS0900 Y Y Y -- -- -- -- KAVS0901 Y Y Y -- Y -- -- KAVS0902 Y Y Y -- Y Y -- KAVS0903 KAVS0904 Y Y Y -- Y -- -- KAVS0905 Y Y Y -- -- -- -- KAVS0907 Y Y Y -- Y -- -- KAVS0909 Y Y Y -- Y -- -- KAVS0915 Y Y Y -- Y -- -- KAVS0916 Y -- -- -- -- -- -- KAVS0920
Message ID Output destination syslog Event log HNTRLib2 stdout stderr Exec details JP1 event KAVS0998 KAVS0999 Y Y Y -- -- -- Y KAVS1002 KAVS1008 Y Y Y -- Y -- -- KAVS1009 Y#8 Y#8 Y -- -- -- -- KAVS1010 KAVS1015 -- -- Y -- -- -- -- KAVS1100 -- -- -- Y -- -- -- KAVS1101 KAVS1118 -- -- -- -- Y -- -- KAVS1119 KAVS1120 -- -- -- Y -- -- -- KAVS1121 KAVS1131 -- -- -- -- Y -- -- KAVS1132 -- -- -- Y -- -- -- KAVS1133 KAVS1139 -- -- -
Message ID Output destination syslog Event log HNTRLib2 stdout stderr Exec details JP1 event KAVS1602#10 -- -- -- -- -- -- -- KAVS1703 KAVS1707 -- -- -- -- Y -- -- KAVS1709 Y Y -- -- Y -- -- KAVS1713 Y Y -- -- Y -- -- KAVS1714 KAVS1718 -- -- -- -- Y -- -- KAVS1719 -- -- Y Y -- -- -- KAVS1720 -- -- Y -- Y -- -- KAVS1721 KAVS1723 -- -- Y -- -- -- -- KAVS1724 -- -- -- -- Y -- -- KAVS1725 Y Y -- -- Y -- -- KAVS1726 -- --
Message ID Output destination syslog Event log HNTRLib2 stdout stderr Exec details JP1 event KAVS1817 KAVS1828 Y Y Y -- -- Y -- KAVS1829 Y Y Y -- Y Y -- KAVS1830 Y Y Y -- Y Y -- KAVS1831 Y#11 Y#11 Y#11 -- Y -- -- KAVS1832 KAVS1836 Y Y Y -- -- Y -- KAVS1837 KAVS1838 Y Y Y -- -- -- -- KAVS1839 KAVS1841 Y Y Y -- -- Y -- KAVS1842 KAVS1845 Y Y Y -- -- -- -- KAVS1846 Y Y Y -- -- Y -- KAVS1847 -- -- Y -- Y Y -- KAVS1848 KAVS185
Message ID Output destination syslog Event log HNTRLib2 stdout stderr Exec details JP1 event KAVS1891 KAVS1898 Y Y Y -- -- -- -- KAVS1900 KAVS1908 Y Y Y -- -- -- -- KAVS1909 Y Y Y -- -- Y -- KAVS1920 Y Y Y -- -- -- -- KAVS1921 Y Y Y -- -- Y -- KAVS1922 Y Y Y -- -- -- -- KAVS1923 Y Y Y -- -- Y -- KAVS1924 Y Y Y -- -- -- -- KAVS1925 Y Y Y -- Y Y -- KAVS1926 -- -- Y -- Y Y -- KAVS1927 Y Y Y -- Y Y -- KAVS1928 -- -
Message ID Output destination syslog Event log HNTRLib2 stdout stderr Exec details JP1 event KAVS1970 -- Y Y -- -- -- -- KAVS1971 KAVS1977 Y Y Y -- -- Y -- KAVS1978 Y Y Y -- -- -- -- KAVS1979 Y Y Y -- -- Y -- KAVS1980 KAVS1983 Y Y Y -- Y -- -- KAVS1985 KAVS1988 -- -- -- -- Y -- -- KAVS1989 KAVS1993 Y Y Y -- Y -- -- KAVS1994 -- -- -- -- Y -- -- KAVS1995 Y Y Y -- Y -- -- KAVS1996 -- -- -- Y -- -- -- KAVS1997 -- -- -- -
Message ID Output destination syslog Event log HNTRLib2 stdout stderr Exec details JP1 event KAVS3411 KAVS3413 -- -- -- Y -- -- -- KAVS3414 KAVS3423 -- -- Y -- -- -- -- KAVS3424 -- -- Y Y -- -- -- KAVS3425 KAVS3430 -- -- Y -- -- -- -- KAVS3431 -- -- Y Y -- -- -- KAVS3432 KAVS3437 -- -- Y -- -- -- -- KAVS3701 KAVS3702 -- -- -- -- Y -- -- KAVS3704 -- -- -- -- Y -- -- KAVS3706 -- -- -- -- Y -- -- KAVS3707 KAVS3709 Y Y Y Y --
Message ID Output destination syslog Event log HNTRLib2 stdout stderr Exec details JP1 event KAVS4624 KAVS4630 -- -- -- -- Y -- -- KAVS4631 Y Y Y -- Y -- -- KAVS4632 KAVS4646 -- -- -- -- Y -- -- KAVS4647 KAVS4656 -- -- Y -- -- -- -- KAVS4657 KAVS4658 -- -- -- -- Y -- -- KAVS4660 KAVS4662 -- -- -- -- Y -- -- KAVS4670 -- -- -- -- Y -- -- KAVS4671 Y Y Y -- Y -- -- KAVS4672 KAVS4673 Y Y Y -- -- -- -- KAVS4674 -- -- -- -- Y --
Message ID Output destination syslog Event log HNTRLib2 stdout stderr Exec details JP1 event KAVS4900 KAVS4918 Y Y Y -- -- -- -- KAVS4931 -- -- -- -- Y -- -- KAVS4933 -- -- -- Y -- -- -- KAVS4934 KAVS4938 -- -- Y -- Y -- -- KAVS4939 Y -- Y Y -- -- -- KAVS4941 -- -- -- -- Y -- -- KAVS4943 Y Y Y -- Y -- -- KAVS4944 -- -- Y -- Y -- -- KAVS4950 Y#3 Y#3 -- -- -- -- Y KAVS4951 Y#5 Y#5 -- -- -- -- Y KAVS4952 -- -- Y -- --
Message ID Output destination syslog Event log HNTRLib2 stdout stderr Exec details JP1 event KAVS8015 KAVS8023 -- -- Y#13 -- Y#13 -- -- KAVS8028 -- -- Y -- Y -- -- KAVS8029 -- -- Y -- -- Y -- KAVS8030 -- -- -- Y -- -- -- KAVS8032 -- -- -- Y -- -- -- KAVS8033 Y Y Y -- Y -- -- KAVS8034 -- -- -- -- Y -- -- KAVS8036 KAVS8037 -- -- Y -- Y -- -- KAVS8038 -- -- -- -- Y -- -- KAVS8039 -- -- Y -- -- -- -- KAVS8040 Y#15 Y#15 Y
For details about the environment setting parameters, see 2.2 Setting up the scheduler service environment in the Job Management Partner 1/ Automatic Job Management System 3 Configuration Guide 2. #9 This message is output to the reorganization log. #10 This message is output to the Information text area in the Detail Information - [object-type] dialog box. For details about this dialog box, see 16.3.
Message ID Output destination syslo g Event log HNTRLib 2 stdout stderr Exec details JP1 event KAVT0023 -- -- Y#1 -- -- -- -- KAVT0025 KAVT0027 -- -- Y#1 -- -- -- -- KAVT0034 KAVT0036 -- -- Y#1 -- -- -- -- KAVT0039 -- -- -- -- -- Y -- KAVT0042 -- -- Y#1 -- -- -- -- KAVT0043 KAVT0045 -- -- -- -- -- Y -- KAVT0058 KAVT0094 -- -- Y#1 -- -- -- -- KAVT0098 KAVT0099 -- -- Y#1 -- -- -- -- KAVT0101 KAVT0106 -- -- Y#1 -- -- -- -- KAVT0108
Message ID Output destination syslo g Event log HNTRLib 2 stdout stderr Exec details JP1 event KAVT0287 -- -- Y#1 -- -- -- -- KAVT0288 KAVT0289 -- -- Y -- -- -- -- KAVT0293 KAVT0297 -- -- Y#1 -- -- -- -- KAVT0301 KAVT0303 -- -- Y#1 -- -- -- -- KAVT0325 KAVT0333 -- -- Y#1 -- -- -- -- KAVT0340 KAVT0347 -- -- Y -- -- -- -- KAVT0352 -- -- Y#1 -- -- -- -- KAVT0353 KAVT0357 -- -- Y -- -- -- -- KAVT0401 -- -- -- -- -- Y -- KAVT0402 KAV
Message ID Output destination syslo g Event log HNTRLib 2 stdout stderr Exec details JP1 event KAVT0542 -- -- Y#1 -- -- Y -- KAVT0544 -- -- Y#1 -- -- -- -- KAVT0559 -- -- Y#1 -- -- -- -- KAVT0562 KAVT0563 Y Y Y -- -- -- -- KAVT0566 -- -- Y#1 -- -- -- -- KAVT0567 -- -- Y#1 -- -- Y -- KAVT0570 Y Y Y -- -- -- -- KAVT0572 Y Y Y -- -- -- -- KAVT0582 -- -- Y#1 -- -- -- -- KAVT0588 KAVT0590 -- -- Y#1 -- -- -- -- KAVT0591 -- -
Message ID Output destination syslo g Event log HNTRLib 2 stdout stderr Exec details JP1 event KAVT0901 -- -- -- -- -- -- Y KAVT0910 KAVT0911 -- -- Y#1 -- -- -- -- KAVT0912 Y Y Y -- -- -- -- KAVT0950 KAVT0963 -- -- -- Y -- -- -- KAVT0980 KAVT0981 -- -- Y#1 -- -- -- -- KAVT0992 -- -- Y -- -- -- -- KAVT1001 KAVT1002 -- -- Y#1 -- -- -- -- KAVT1003 Y Y Y -- -- -- -- KAVT1004 KAVT1006 -- -- Y#1 -- -- -- -- KAVT1007 -- -- Y#1 --
Message ID Output destination syslo g Event log HNTRLib 2 stdout stderr Exec details JP1 event KAVT1062 KAVT1067 -- -- Y#1 -- -- -- -- KAVT1068 -- -- Y#1 -- -- Y -- KAVT1069 -- -- Y#1 -- -- -- -- KAVT1200 KAVT1205 -- -- Y#1 -- -- Y -- KAVT1206 KAVT1213 -- -- Y#1 -- -- Y -- KAVT1214 -- -- Y#1 -- -- -- -- KAVT1217 -- -- Y#1 -- -- Y -- KAVT1226 -- -- Y#1 -- -- -- -- KAVT2001 -- -- Y#1 -- -- -- -- KAVT2004 KAVT2007 -- -- -- --
Message ID Output destination syslo g Event log HNTRLib 2 stdout stderr Exec details JP1 event KAVT3041 -- -- Y -- -- Y -- KAVT3042 KAVT3206 -- -- Y -- -- -- -- KAVT3207 -- -- Y -- -- Y -- KAVT3210 KAVT3212 -- -- Y -- -- -- -- KAVT3268 KAVT3271 -- -- Y -- -- Y -- KAVT3273 KAVT3274 -- -- Y -- -- Y -- KAVT3275 -- -- Y -- -- -- -- KAVT3276 KAVT3295 -- -- Y -- -- Y -- KAVT3296 KAVT3304 -- -- Y -- -- -- -- KAVT3401 -- Y Y -- --
Message ID Output destination syslo g Event log HNTRLib 2 stdout stderr Exec details JP1 event KAVT3513 Y Y Y -- -- Y -- KAVT3514 Y Y Y -- -- -- -- KAVT3515 Y Y Y -- -- Y -- KAVT3519 -- -- Y#1 -- -- Y -- KAVT3520 Y Y Y -- -- -- -- KAVT3521 -- -- Y#1 -- -- Y -- KAVT3522 -- -- Y#1 -- -- -- -- KAVT3523 KAVT3524 -- -- Y#1 -- -- Y -- KAVT3525 KAVT3533 -- -- Y#1 -- -- -- -- KAVT3534 Y Y Y -- -- -- -- KAVT3538 KAVT3555 -- --
Message ID Output destination syslo g Event log HNTRLib 2 stdout stderr Exec details JP1 event KAVT3845 KAVT3846 -- -- Y -- -- Y -- KAVT3847 KAVT3849 -- -- Y -- Y -- -- KAVT3850 KAVT3852 -- -- Y -- -- Y -- KAVT4031 -- -- Y -- -- -- -- KAVT4036 KAVT4037 -- -- Y -- -- Y -- KAVT4039 -- -- Y -- -- Y -- KAVT4057 -- -- Y -- -- -- -- KAVT4058 -- -- Y -- -- Y -- KAVT4068 KAVT4072 -- -- Y -- -- Y -- KAVT4075 KAVT4076 -- -- Y -- --
Message ID Output destination syslo g Event log HNTRLib 2 stdout stderr Exec details JP1 event KAVT4198 KAVT4202 -- -- Y -- -- Y -- KAVT4203 KAVT4216 -- -- Y -- -- Y -- KAVT4222 KAVT4223 -- -- Y -- -- Y -- KAVT4230 -- -- Y -- -- Y -- KAVT4232 -- -- Y -- -- Y -- KAVT4235 KAVT4253 -- -- Y -- -- Y -- KAVT4254 KAVT4256 -- -- Y -- -- Y -- KAVT4257 KAVT4258 -- -- Y -- -- -- -- KAVT4259 -- -- Y -- -- Y -- KAVT4260 KAVT4414 -- -- Y
Message ID Output destination syslo g Event log HNTRLib 2 stdout stderr Exec details JP1 event KAVT4527 KAVT4528 -- -- Y#1 -- -- Y -- KAVT4529 KAVT4531 -- -- Y#1 -- -- -- -- KAVT4532 KAVT4533 -- -- Y#1 -- -- Y -- KAVT4534 KAVT4537 -- -- Y#1 -- -- -- -- KAVT4538 KAVT4539 -- -- Y#1 -- -- Y -- KAVT4540 KAVT4543 -- -- Y#1 -- -- -- -- KAVT4547 -- -- Y#1 -- -- Y -- KAVT4548 KAVT4551 -- -- -- -- -- Y -- KAVT4552 KAVT4554 -- -- Y#1 -- --
Message ID Output destination syslo g Event log HNTRLib 2 stdout stderr Exec details JP1 event KAVT4586 KAVT4591 -- -- Y#1 -- -- Y -- KAVT4593 -- -- Y#1 -- -- -- -- KAVT4595 -- -- Y#1 -- -- Y -- KAVT4596 -- -- Y#1 -- -- -- -- KAVT4597 KAVT4598 -- -- Y#1 -- -- Y -- KAVT4631 KAVT4685 -- -- Y#1 -- -- -- -- KAVT4687 -- -- Y#1 -- -- Y -- KAVT4688 KAVT4694 -- -- Y#1 -- -- -- -- KAVT4695 -- -- -- -- -- Y -- KAVT4696 KAVT4701 -- -- Y
Message ID Output destination syslo g Event log HNTRLib 2 stdout stderr Exec details JP1 event KAVT7001 KAVT7002 -- -- Y#1 -- -- -- -- KAVT7003 -- -- -- -- -- Y -- KAVT7004 -- -- Y#1 -- -- -- -- KAVT7005 KAVT7006 -- -- -- -- -- Y -- KAVT7007 KAVT7011 -- -- Y#1 -- -- -- -- KAVT7012 KAVT7016 -- -- Y#1 -- -- Y -- KAVT7017 -- -- -- -- -- Y -- KAVT7501 KAVT7514 -- -- Y#2 -- -- Y -- KAVT7515 -- -- -- -- -- Y -- KAVT8001 KAVT8340 --
For details on the settings for outputting error messages for jobs to syslog, see 15.6.1 Settings for outputting error messages for jobs to syslog in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1. 1.3.5 Output destinations of messages beginning with KAVU The following table lists the output destinations of the messages beginning with KAVU (messages for the job execution control).
Message ID Output destination syslog Event log HNTRLib2 stdout stderr Exec details JP1 event KAVU0236 -- -- Y#1 -- -- -- -- KAVU0237 KAVU0242 Y#2 Y#2 Y#1 -- -- -- -- KAVU0243 -- -- Y#1 -- -- -- -- KAVU0244 Y#2 Y#2 Y#1 -- -- -- -- KAVU0245 KAVU0247 -- -- Y#1 -- -- -- -- KAVU0248 KAVU0252 Y#2 Y#2 Y#1 -- -- -- -- KAVU0253 KAVU0268 -- -- Y#1 -- -- -- -- KAVU0269 -- -- Y#1 -- -- Y -- KAVU0270 -- -- Y#1 -- -- -- -- KAVU0300 KAVU0467
Message ID Output destination syslog Event log HNTRLib2 stdout stderr Exec details JP1 event KAVU3105 Y -- Y -- -- -- -- KAVU3110 KAVU3111 Y Y Y -- -- -- -- KAVU3112 Y -- Y -- -- -- -- KAVU3200 KAVU3212 -- -- Y#3 -- -- -- -- KAVU3213 KAVU3217 -- -- Y -- -- -- -- KAVU3221 KAVU3599 -- -- Y#3 -- -- -- -- KAVU3296 -- -- Y -- -- -- -- KAVU3500 KAVU3599 -- -- Y#3 -- -- -- -- KAVU3800 -- -- -- Y -- -- -- KAVU3900 KAVU3906 -- -- --
Message ID Output destination syslog Event log HNTRLib2 stdout stderr Exec details JP1 event KAVU4718 -- -- Y#3 -- -- -- -- KAVU4720 -- -- Y#3 -- -- -- -- KAVU4721 -- -- Y -- -- Y -- KAVU5002 KAVU5007 -- -- -- -- Y -- -- KAVU5009 Y Y -- -- Y -- -- KAVU5012 KAVU5014 -- -- -- -- Y -- -- KAVU5015 -- -- Y#1 Y -- -- -- KAVU5016 -- -- Y#1 -- Y -- -- KAVU5100 Y Y Y -- -- -- -- KAVU5200 KAVU5296 -- -- Y#1 -- -- -- -- KAVU5309 KA
#1 Messages with a message type of Error (-E) can also be output to syslog according to the specifications of the SYSLOGJOBMSG environment setting parameter. The value of Facility for these messages is LOG_DAEMON or LOG_USER. For details about the environment setting parameters, see 15.6.1 Settings for outputting error messages for jobs to syslog in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.
1.3.8 Output destinations of messages beginning with KNAC Messages whose message ID begins with KNAC are output by communication control or agent management. The tables in the following subsections list the output destinations for each type of message. (1) KNAC0001 to KNAC0999 (messages output by communication control) The table below lists the output destinations of messages output by communication control.
stdout: Standard output stderr: Standard error output Exec details: Execution Result Details dialog box JP1 event: JP1 event Y: Is output. --: Is not output.
stderr: Standard error output JP1 event: JP1 event Y: Is output. --: Is not output.
Message ID Output destination Dialog syslog Event log HNTRLib2 stdout stderr JP1 event KNAD3649 -- Y Y Y Y -- -- KNAD3650 KNAD3662 -- -- -- Y Y -- -- KNAD3663 -- -- -- -- -- Y -- KNAD3669 -- -- -- -- Y -- -- KNAD3670 KNAD3678 -- -- -- Y Y -- -- KNAD3686 -- Y Y Y -- -- -- KNAD3687 -- -- -- -- Y -- -- KNAD3688 KNAD3694 -- -- -- -- Y -- -- KNAD3695 -- -- -- -- Y -- -- KNAD3699 -- -- -- Y -- -- -- KNAD3705 KNAD3736 -- --
Message ID Output destination Dialog syslog Event log HNTRLib2 stdout stderr JP1 event KNAD3873 -- -- -- -- Y -- -- KNAD3874 KNAD3875 -- Y Y -- Y -- -- KNAD3876 -- -- -- Y -- -- -- KNAD3877 KNAD3880 -- -- -- Y -- -- -- KNAD3899 -- Y Y -- Y -- -- KNAD3905 KNAD3910 -- -- -- Y -- -- -- KNAD3911 KNAD3914 -- -- -- Y Y -- -- KNAD3935 -- -- -- Y -- -- -- KNAD3953 -- Y Y Y -- -- Y KNAD3960 -- -- -- -- Y -- -- KNAD3961 -- -- -
1.4 List of Windows event logs and syslogs 1.4.1 List of messages output to the Windows event log and syslog This section lists the Windows event logs and syslogs that JP1/AJS3 outputs.
Message ID Windows (Application log) UNIX (syslog) Event ID Type Facility Level KAVC2901-E 12901 Error LOG_DAEMON, LOG_USER LOG_ERR KAVC2902-E 12902 Error LOG_DAEMON, LOG_USER LOG_ERR KAVC2903-E 12903 Error LOG_DAEMON, LOG_USER LOG_ERR KAVC2904-E 12904 Error LOG_DAEMON, LOG_USER LOG_ERR KAVC2905-E 12905 Error LOG_DAEMON, LOG_USER LOG_ERR KAVC2907-E 12907 Error LOG_DAEMON, LOG_USER LOG_ERR KAVC2916-E -- -- LOG_DAEMON, LOG_USER LOG_ERR KAVC2920-W 12920 Warning LOG_
Message ID Windows (Application log) UNIX (syslog) Event ID Type Facility Level KAVS0230-E 30230 Error LOG_DAEMON LOG_ERR KAVS0231-W 30231 Warning LOG_DAEMON LOG_WARNING KAVS0232-W 30232 Warning LOG_DAEMON LOG_WARNING KAVS0240-I 30240 Information LOG_DAEMON LOG_INFO KAVS0241-I 30241 Information LOG_DAEMON LOG_INFO KAVS0243-E 30243 Error LOG_DAEMON LOG_ERR KAVS0244-E 30244 Error LOG_DAEMON LOG_ERR KAVS0245-W 30245 Warning LOG_DAEMON LOG_WARNING KAVS0246-E 30246
Message ID Windows (Application log) UNIX (syslog) Event ID Type Facility Level KAVS0314-E 30314 Error LOG_DAEMON LOG_ERR KAVS0315-E 30315 Error LOG_DAEMON, LOG_USER LOG_ERR KAVS0317-E 30317 Error LOG_DAEMON, LOG_USER LOG_ERR KAVS0318-E 30318 Error LOG_DAEMON LOG_ERR KAVS0319-E 30319 Error LOG_DAEMON, LOG_USER LOG_ERR KAVS0500-E 30500 Error LOG_DAEMON LOG_ERR KAVS0530-I 30530 Information LOG_DAEMON LOG_INFO KAVS0531-I 30531 Information LOG_DAEMON LOG_INFO KAVS0
Message ID Windows (Application log) UNIX (syslog) Event ID Type Facility Level KAVS0930-E 30930 Error LOG_USER LOG_ERR KAVS0932-E 30932 Error LOG_DAEMON, LOG_USER LOG_ERR KAVS0933-W 30933 Warning LOG_USER LOG_WARNING KAVS0934-E 30934 Error LOG_DAEMON, LOG_USER LOG_ERR KAVS0935-E 30935 Error LOG_DAEMON, LOG_USER LOG_ERR KAVS0936-E 30936 Error LOG_USER LOG_ERR KAVS0940-E 30940 Error LOG_DAEMON LOG_ERR KAVS0941-E 30941 Error LOG_DAEMON LOG_ERR KAVS0942-W 30942
Message ID Windows (Application log) UNIX (syslog) Event ID Type Facility Level KAVS1002-E 31002 Error LOG_DAEMON LOG_ERR KAVS1003-E 31003 Error LOG_DAEMON LOG_ERR KAVS1004-E 31004 Error LOG_DAEMON LOG_ERR KAVS1005-E 31005 Error LOG_DAEMON LOG_ERR KAVS1006-W 31006 Warning LOG_DAEMON LOG_WARNING KAVS1007-E 31007 Error LOG_DAEMON LOG_ERR KAVS1008-E 31008 Error LOG_DAEMON LOG_ERR KAVS1009-W 31009 Warning LOG_USER LOG_WARNING KAVS1300-I 31300 Information LOG_DAE
Message ID Windows (Application log) UNIX (syslog) Event ID Type Facility Level KAVS1805-E 31805 Error LOG_DAEMON LOG_ERR KAVS1806-I 31806 Information LOG_DAEMON LOG_INFO KAVS1807-E 31807 Error LOG_DAEMON LOG_ERR KAVS1808-E 31808 Error LOG_DAEMON LOG_ERR KAVS1809-E 31809 Error LOG_DAEMON LOG_ERR KAVS1810-E 31810 Error LOG_DAEMON LOG_ERR KAVS1811-E 31811 Error LOG_DAEMON LOG_ERR KAVS1812-E 31812 Error LOG_DAEMON LOG_ERR KAVS1813-E 31813 Error LOG_DAEMON LOG_
Message ID Windows (Application log) UNIX (syslog) Event ID Type Facility Level KAVS1839-E 31839 Error LOG_DAEMON LOG_ERR KAVS1840-E 31840 Error LOG_DAEMON LOG_ERR KAVS1841-E 31841 Error LOG_DAEMON LOG_ERR KAVS1842-E 31842 Error LOG_DAEMON LOG_ERR KAVS1843-E 31843 Error LOG_DAEMON LOG_ERR KAVS1844-E 31844 Error LOG_DAEMON LOG_ERR KAVS1845-E 31845 Error LOG_DAEMON LOG_ERR KAVS1846-E 31846 Error LOG_DAEMON LOG_ERR KAVS1848-W 31848 Warning LOG_DAEMON LOG_WARNI
Message ID Windows (Application log) UNIX (syslog) Event ID Type Facility Level KAVS1877-E 31877 Error LOG_DAEMON LOG_ERR KAVS1878-E 31878 Error LOG_DAEMON LOG_ERR KAVS1879-E 31879 Error LOG_DAEMON LOG_ERR KAVS1880-E 31880 Error -- -- KAVS1881-E 31881 Error LOG_DAEMON LOG_ERR KAVS1882-E 31882 Error LOG_DAEMON LOG_ERR KAVS1883-E 31883 Error LOG_DAEMON LOG_ERR KAVS1884-E 31884 Error LOG_DAEMON LOG_ERR KAVS1885-E 31885 Error LOG_DAEMON LOG_ERR KAVS1886-E 318
Message ID Windows (Application log) UNIX (syslog) Event ID Type Facility Level KAVS1923-E 31923 Error LOG_DAEMON LOG_ERR KAVS1924-E 31924 Error LOG_DAEMON LOG_ERR KAVS1925-E 31925 Error LOG_DAEMON LOG_ERR KAVS1927-E 31927 Error LOG_DAEMON LOG_ERR KAVS1929-I 31929 Information LOG_DAEMON LOG_INFO KAVS1930-W 31930 Warning LOG_DAEMON LOG_WARNING KAVS1932-E 31932 Error LOG_DAEMON LOG_ERR KAVS1940-E 31940 Error LOG_DAEMON LOG_ERR KAVS1941-E 31941 Error LOG_DAEMON
Message ID Windows (Application log) UNIX (syslog) Event ID Type Facility Level KAVS1981-I 31981 Information LOG_DAEMON LOG_INFO KAVS1982-I 31982 Information LOG_DAEMON LOG_INFO KAVS1983-I 31983 Information LOG_DAEMON LOG_INFO KAVS1989-E 31989 Error LOG_DAEMON LOG_ERR KAVS1990-E 31990 Error LOG_DAEMON LOG_ERR KAVS1991-E 31991 Error LOG_DAEMON LOG_ERR KAVS1992-E 31992 Error LOG_DAEMON LOG_ERR KAVS1993-E 31993 Error LOG_DAEMON LOG_ERR KAVS1995-E 31995 Error LO
Message ID Windows (Application log) UNIX (syslog) Event ID Type Facility Level KAVS4701-E 34701 Error LOG_DAEMON LOG_ERR KAVS4702-E 34702 Error LOG_DAEMON LOG_ERR KAVS4703-E 34703 Error LOG_DAEMON LOG_ERR KAVS4704-E 34704 Error LOG_DAEMON LOG_ERR KAVS4705-E 34705 Error LOG_DAEMON LOG_ERR KAVS4706-E 34706 Error LOG_DAEMON LOG_ERR KAVS4707-E 34707 Error LOG_DAEMON LOG_ERR KAVS4708-E 34708 Error LOG_DAEMON LOG_ERR KAVS4711-E 34711 Error LOG_DAEMON LOG_ERR KA
Message ID Windows (Application log) UNIX (syslog) Event ID Type Facility Level KAVS4907-I 34907 Information LOG_DAEMON LOG_INFO KAVS4908-E 34908 Error LOG_DAEMON LOG_ERR KAVS4909-E 34909 Error LOG_DAEMON LOG_ERR KAVS4910-E 34910 Error LOG_DAEMON LOG_ERR KAVS4911-E 34911 Error LOG_DAEMON LOG_ERR KAVS4912-E 34912 Error LOG_DAEMON LOG_ERR KAVS4913-E 34913 Error LOG_DAEMON LOG_ERR KAVS4914-E 34914 Error LOG_DAEMON LOG_ERR KAVS4915-I 34915 Information LOG_DAEMON
Message ID Windows (Application log) UNIX (syslog) Event ID Type Facility Level KAVT1037-E 11037 Error LOG_DAEMON LOG_ERR KAVT1040-E 11040 Error LOG_DAEMON LOG_ERR KAVT1042-E 11042 Error LOG_DAEMON LOG_ERR KAVT1050-E 11050 Error LOG_DAEMON LOG_ERR KAVT3401-I 13401 Information -- -- KAVT3403-I 13403 Information -- -- KAVT3406-I 13406 Information -- -- KAVT3408-I 13408 Information -- -- KAVT3504-E -- -- LOG_DAEMON LOG_ERR KAVT3513-E 13513 Error LOG_DAEMON
Message ID Windows (Application log) UNIX (syslog) Event ID Type Facility Level KAVU0241-E 20241 Error LOG_DAEMON, LOG_USER LOG_ERR KAVU0242-E 20242 Error LOG_DAEMON, LOG_USER LOG_ERR KAVU0244-E 20244 Error LOG_DAEMON, LOG_USER LOG_ERR KAVU0248-E 20248 Error LOG_DAEMON, LOG_USER LOG_ERR KAVU0249-E 20249 Error LOG_DAEMON, LOG_USER LOG_ERR KAVU0250-E 20250 Error LOG_DAEMON, LOG_USER LOG_ERR KAVU0251-E 20251 Error LOG_DAEMON, LOG_USER LOG_ERR KAVU0252-E 20252 Error
Message ID Windows (Application log) UNIX (syslog) Event ID Type Facility Level KAVU5980-I 25980 Information LOG_USER LOG_NOTICE KAVU5981-I 25981 Information LOG_USER LOG_NOTICE KAVU5982-E 25982 Error LOG_USER LOG_ERR KAVU5983-I 25983 Information LOG_USER LOG_NOTICE KAVU5984-W 25984 Warning LOG_USER LOG_WARNING KAVU6100-I 26100 Information LOG_DAEMON, LOG_USER LOG_NOTICE KAVU6101-I 26101 Information LOG_DAEMON, LOG_USER LOG_NOTICE KAVU6102-E 26102 Error LOG_DAEMO
Message ID Windows (Application log) UNIX (syslog) Event ID Type Facility Level KNAD3613-W 2 Warning LOG_USER LOG_WARNING KNAD3614-E 1 Error LOG_USER LOG_ERR KNAD3620-E 1 Error LOG_USER LOG_ERR KNAD3621-E -- -- LOG_USER LOG_ERR KNAD3623-E -- -- LOG_USER LOG_ERR KNAD3624-E 1 Error LOG_USER LOG_ERR KNAD3625-E 1 Error LOG_USER LOG_ERR KNAD3626-E 1 Error LOG_USER LOG_ERR KNAD3642-E 1 Error LOG_USER LOG_ERR KNAD3643-E 1 Error LOG_USER LOG_ERR KNAD3644-E 1
Message ID Windows (Application log) UNIX (syslog) Event ID Type Facility Level KNAD3992-E 1 Error LOG_USER LOG_ERR KNAD3993-E 1 Error LOG_USER LOG_ERR Legend: -- : Not applicable # If yes is specified for the LOGINFOALL environment setting parameter, this message is output with a parenthesized event ID. 1.4.2 Information about the Windows event log For the events output by JP1/AJS3, JP1/AJS2 is usually set as the source.
2 Messages This chapter explains the messages output by JP1/AJS3 and how to take actions for them.
2.1 Messages beginning with KAJS (Messages about passing information setting jobs) This section lists the messages that begin with KAJS (messages about passing information setting jobs). KAJS7620-E An error occurred in internal processing. : maintenance-information An error occurred during internal processing. (S) Cancels execution of the passing information setting job.
The standard output file of the preceding job does not exist or is 0 bytes. (S) Cancels execution of the passing information setting job. (O) Check the following: • Is the preceding job a PC job, Unix job, or custom job? • Is the standard output file name specified in the preceding job? • Did the preceding job output at least 1 byte of data to the standard output file? Note that the information in the Execution Result Details dialog box was output by the job to standard error output.
(S) Cancels command execution. (O) Make sure that no lines exceed 1,024 bytes in the execution results of the preceding job. KAJS7626-W A null string was set for the value of the global macro variable (macro-variable-name) because, in the standard output file of the preceding job, no line matched the regular expression (regular-expression). A null string was set as the value of the global macro variable because no line in the standard output file of the preceding job matched the regular expression.
(S) Cancels execution of the passing information setting job. (O) Make sure that the disk where the global macro file is to be created has sufficient free space. The global macro file is created in the job information storage folder. If disk space was insufficient, make more space available and execute the job again. If the disk has sufficient free space, execute the job again in case the error was temporary.
2.2 Messages beginning with KAVC (Messages about JP1/AJS3 Console) This section lists the messages that begin with KAVC (Messages about JP1/AJS3 Console). The JP1/AJS3 component that displays messages that begin with KAVC is determined based on the message ID. The following table lists message IDs and the component that displays those messages.
KAVC0082-I JP1/AJS2 Console Manager service has been removed. The JP1/AJS3 Console Manager service has been removed. (S) Removed the JP1/AJS3 Console Manager service. KAVC0083-I Stopping JP1/AJS2 Console Manager service. Now stopping the JP1/AJS3 Console Manager service. (S) Stops the JP1/AJS3 Console Manager service. KAVC0084-E JP1/AJS2 Console Manager service is set up already.
An error occurred during setup of the JP1/AJS3 Console Manager service. (S) Terminates setup processing. (O) Execute the setup command while logged on as an OS user who is a member of the Administrators group. If the UAC function is enabled in Windows, the administrator must re-execute the command. Memory or disk space may be insufficient. Terminate unnecessary applications, and then re-execute the setup command. KAVC0087-E An error occurred during removing JP1/AJS2 Console Manager service.
KAVC0102-E Extra argument(s) exist. One or more unnecessary arguments were specified. (S) Cancels command execution. (O) Delete the unnecessary arguments, and then re-execute the command. KAVC0103-E Invalid value for option (option). The option contains an invalid value. (S) Cancels command execution. (O) Correct the value for the option, and then re-execute the command. KAVC0104-E Option (option) appears twice or more. The same option was specified more than once. (S) Cancels command execution.
If the UAC function is enabled in Windows, the administrator must re-execute the command. In environments managed by AJS administrators, an AJS administrator or a user who has superuser privileges must execute the command. KAVC0119-E Cannot use - in use by other user. : file-name The operation is impossible because another user is using the file that you attempted to manipulate. (S) Cancels command execution. (O) Wait for the other user to finish using the file, and then re-execute the command.
An attempt to display the business scope for the JP1 user specified in the -u option of the ajscmprint command has failed because another user is currently defining that business scope. Alternatively, access permissions for the data directory have not been assigned. (S) Cancels command execution. (O) Set the monitoring mode to the JP1/AJS3 Console View to which the JP1 user specified in the -u option has logged on. Alternatively, terminate JP1/AJS3 Console View then re-execute the command.
(S) Cancels command execution. (O) Specify the correct option, and then re-execute the command. KAVC0200-E Failed to convert string (string-before-character-set-conversion) : maintenance-information-1 maintenanceinformation-2 maintenance-information-3 Character set conversion failed. (S) Cancels processing. (O) If the KAVC0902-E message was output before this message, memory is insufficient. Take action according to the instructions given by the KAVC0902-E message.
(O) Set the environment setting parameter indicated in item-name correctly according to 2.8 Setting up the JP1/AJS3 Console environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2. If DATADIRECTORY is indicated in item-name, make sure that the directory specified in the DATADIRECTORY environment setting parameter exists. If it does not exist, create a directory.
- system-drive\Windows - system-drive\Program Files - system-drive\Program Files (x86) (for 64-bit Windows) • For Windows Server 2012 or Windows Server 2008 in which an installation folder other than the above is used: JP1/AJS3 Console-installation-folder\database • For Windows Server 2003: JP1/AJS3 Console-installation-folder\database • In UNIX: /var/opt/jp1ajs2cm/database If you are using the JP1/AJS3 Console Manager service on a logical host or specify a path other than the default, see the value of the
(S) Continues processing. KAVC0533-I Reception processing from JP1/AJS2 Console View has ended. (PID: process-ID) The processing accepted from JP1/AJS3 Console View has terminated. The process indicated by process-ID has terminated. (S) Terminates processing that was accepted from JP1/AJS3 Console View. KAVC0802-E Cannot connect to Access Control Server. The access control server could not be connected. (S) Continues processing, determining the connection from JP1/AJS3 Console View to be an error.
(O) Follow the instructions given by the KAVC4507-E error message that was displayed on JP1/AJS3 Console View when you logged on. KAVC0806-E Environment file name length exceeds 255 bytes. The name of the environment variable file is more than 255 bytes, which is the maximum length of the host name. (S) Cancels execution of the command. (O) Check the setting of the JP1_HOSTNAME environment variable. KAVC0807-E An error exists in the certification server setting of the host (host-name).
The system cancels the processing during which insufficient memory was detected. If insufficient memory was detected during allocation of memory for a key component that could not continue processing, the system aborts the process. (S) Cancels the process in which the error occurred. (O) Check the following settings. Then, if necessary, re-execute the processing for which memory was insufficient.
KAVC0905-E Failed to put message (message-ID).: maintenance-information-1 maintenance-information-2 maintenanceinformation-3 maintenance-information-4 The system attempted to output an error message because an error occurred, but it failed. (S) Cancels the process in which the error occurred. (O) Take actions according to the displayed message and the error message provided by the system. KAVC0907-E No more space in file (file-name).
(O) Check whether resources are insufficient. Also check the running status of Hitachi Network Objectplaza Trace Monitor. In UNIX, see Release Notes, and check the following items in the kernel parameters: • Maximum number of files allowed to be open for a process or system • Maximum number of file descriptors allowed (a limit value related to the file system) KAVC0943-E Environment of the practice authority is injustice. maintenance-information The execution permission environment is invalid.
(S) Cancels the process in which the error occurred. (O) Terminate unnecessary windows, dialog boxes, and processes, and delete unnecessary files to increase available free space. Then re-execute the operation. In UNIX, see Release Notes, and check the following items in the kernel parameters: • Maximum number of files allowed to be open for a process or system • Maximum number of file descriptors allowed (a limit value related to the file system) KAVC0953-E System resources became insufficient.
KAVC2081-I JP1/AJS2 Console Agent service has been installed. The JP1/AJS3 Console Agent service has been set up. (S) Terminates setup processing. KAVC2082-I JP1/AJS2 Console Agent service has been removed. The JP1/AJS3 Console Agent has been removed. (S) Terminates setup processing. KAVC2083-I Stopping JP1/AJS2 Console Agent service. The system is stopping the JP1/AJS3 Console Agent service. (S) Is stopping the JP1/AJS3 Console Agent service.
(O) Check whether the JP1/AJS3 Console Agent service has been set up. KAVC2086-E An error occurred during installing JP1/AJS2 Console Agent service.: maintenance-information-1 maintenanceinformation-2 An error occurred during setup of the JP1/AJS3 Console Agent service. (S) Terminates setup processing. (O) Execute the setup command while logged on as an OS user who is a member of the Administrators group. If the UAC function is enabled in Windows, the administrator must re-execute the command.
One or more unnecessary arguments are specified. (S) Cancels command execution. (O) Delete unnecessary arguments, and then re-execute the command. KAVC2103-E Invalid value for option (option). An incorrect value is specified for the option. (S) Cancels command execution. (O) Specify the correct value for the option, and then re-execute the command. KAVC2108-E Only super user or administrator can execute.
KAVC2127-E Specified file (file-name) does not exist. The specified file does not exist. (S) Cancels command execution. (O) Specify the correct file name or create a file, and then re-execute the command. KAVC2158-E Invalid options are specified. Invalid options are specified. (S) Cancels command execution. (O) Specify the correct options, and then re-execute the command.
(S) Cancels command execution if the error occurred during command execution. For other cases, the system cancels processing. (O) If the error occurred during execution of a command, execute the command as a user who has the required privileges. For other cases, check the privileges required for a user who wants to execute the service. KAVC2331-E Invalid specification in configuration definition. (item-name) The environment setting for JP1/AJS3 Console Agent contains an invalid specification.
For details about the data you must collect, see 1.3 Data to be collected when a problem occurs in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting and 1.4 Collecting data for troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting. KAVC2383-E JP1/AJS2 Console Agent service has already stopped monitoring.
KAVC2386-E An invalid value exists in the monitoring properties.: maintenance-information-1 maintenance-information-2 maintenance-information-3 The monitoring property values received from JP1/AJS3 Console Manager are invalid. (S) Cancels the communication with JP1/AJS3 Console Manager and continues processing. (O) The monitoring method specified in JP1/AJS3 Console Manager may not be supported in JP1/AJS3 Console Agent.
No more connections can be made because the number of connections from JP1/AJS3 Console Manager exceeded the value specified in the MAXSESSION environment setting parameter. (S) Continues processing, determining any connection exceeding the maximum to be an error. (O) If JP1/AJS3 Console View monitors hosts on the machine unnecessarily, terminate JP1/AJS3 Console View. If necessary, respecify a value in MAXSESSION. KAVC2457-E Cannot connect to host.
KAVC2534-I JP1/AJS2 Console Agent service will connect to the scheduler service (scheduler-service-name). JP1-user-name process-information The JP1/AJS3 Console Agent service connected to the scheduler service (scheduler-service-name), and started collecting information. (S) Continues processing. KAVC2535-I JP1/AJS2 Console Agent service will disconnect from the scheduler service (scheduler-service-name).
(S) Continues processing. KAVC2539-I The command execution request will now end.: command-name Processing of a request has ended. The request, accepted from JP1/AJS3 Console Manager, was to execute the command. (S) Terminates command execution and continues processing. KAVC2804-E The user-mapping has failed. maintenance-information-1 maintenance-information-2 maintenance-information-3 User mapping failed. (S) Releases the connection with JP1/AJS3 Console Manager and continues processing.
KAVC2901-E I/O error occurred.: maintenance-information-1 maintenance-information-2 maintenance-information-3 A file I/O error occurred during processing. (S) Cancels processing for the file in which the error occurred, and continues the process. However, the system cancels the process if it cannot continue the process because of a system file I/O error. (O) Collect the syslog, and then contact the system administrator. KAVC2902-E Insufficient memory occurred.
KAVC2904-E Unexpected error occurred in JP1/AJS2 Console Agent.: maintenance-information-1 maintenance-information-2 maintenance-information-3 maintenance-information-4 An unexpected error occurred during processing. (S) Terminates the process in which the error occurred. If possible, the system outputs the core dump of the process. (O) Contact the system administrator and collect data. For details about the data you must collect, see 1.
(O) Use the data collection tool to collect data and contact the system administrator (see 1.2.3 To the system administrators). KAVC2920-W Message process failed to initialize. (maintenance-information) The message output could not be initialized. (S) The message is output without text. If HNTR_Initialize Failure is shown in maintenance-information, no message is output to the integrated trace log. (O) Check whether resources are insufficient.
(S) Cancels the process in which the error occurred. (O) Terminate unnecessary windows, dialog boxes, and processes, and then re-execute the operation. In UNIX, see Release Notes, and check the following items in the kernel parameters: • Maximum number of files allowed to be open for a process or system • Maximum number of file descriptors allowed (a limit value related to the file system) KAVC2951-E Not enough space in file system. The file system does not have sufficient space.
(S) Terminates JP1/AJS3 Console View. (O) Collect the following data, and then contact the system administrator. • A hardcopy of the window • JP1/AJS3 Console View log files Click the OK button in this message dialog box, and then collect the JP1/AJS3 Console View log files. KAVC4002-E During (process-name), Memory became insufficient. JP1/AJS3 Console View will now end. Detailed information [(maintenance-information)] Memory became insufficient during the execution of process-name.
KAVC4005-E An unexpected error occurred in start processing. (Detailed information: (maintenance-information-1), (maintenance-information-2)) An unexpected error occurred during the start of JP1/AJS3 Console View. (S) Cancels processing. (O) Memory or free space on the disk may be insufficient. Terminate unnecessary applications, and then restart JP1/ AJS3 Console View. If the error persists, the configuration of JP1/AJS3 - View may have been corrupted. Perform a repair installation.
(S) Cancels processing. (O) Compare ajscon2.conf against ajscon2.conf.model to check for any unnecessary options that have been specified. KAVC4011-E The command line parameter is too long. JP1/AJS3 Console View cannot start because the command line parameter specified in the ajscon command is too long. (S) Cancels processing. (O) Correctly specify the command line parameter, and then re-execute the ajscon command. KAVC4012-E There is an invalid parameter.
The same parameter was specified more than once in the ajscon command. (S) Terminates JP1/AJS3 Console View. (O) Delete the duplicate parameter, and then re-execute the command. KAVC4015-E The port number could not be obtained. Confirm whether the service name is defined correctly. The port number to connect to JP1/AJS3 Console Manager could not be obtained. (S) Terminates JP1/AJS3 Console View.
KAVC4018-E You do not have permission to execute the setup program. A user who did not log on as a member of the Administrators group attempted to execute the JP1/AJS3 Console View setup command. (S) Cancels processing. (O) Execute the JP1/AJS3 Console View setup command as a member of the Administrators group. KAVC4019-E Setup failed. (Detailed information: (maintenance-information)) The setup command could not be executed. (S) Cancels processing. (O) Memory or free space on the disk may be insufficient.
(S) Cancels automatic login, and displays the Login screen. Even if the password is specified, the password does not appear in the Login screen unless both user name and host name are specified. (O) In the Login screen, a blank field appears for a value of keyword that is not specified in the login information file. Enter a proper value in the blank field, and then log in. Also check the contents of the login information file, referring to ajscon in 3.
The copy destination folder (indicated by folder-name) for the files used for linkage with JP1/IM - View was not found in the JP1/IM - View installation folder. (S) Automatically creates the folder indicated by folder-name in the JP1/IM - View installation folder, and then continues processing. (O) Check whether JP1/IM - View is installed correctly. If it is, you do not need to take any action. Note that a folder that is automatically created will not be deleted when JP1/IM - View is uninstalled.
(O) Check whether the correct value is specified for keyword. KAVC4106-W There is an ineffective parameter. [(invalid-parameter)] An invalid parameter was specified in the ajscon command. (S) Continues processing, ignoring the invalid parameter. (O) Check the command line parameters for errors. KAVC4107-I JP1/AJS3 Console View was started. (Version: (version), OS user name: (OS-user-name)) This message indicates that JP1/AJS3 Console View started.
This message indicates that the dialog box shown in dialog-box-name closed. (S) Outputs, to the log, the information that the dialog box shown in dialog-box-name closed. KAVC4111-I The "(button-name)" button was chosen in the "(dialog-box-name)" dialog box. This message indicates that the button shown in button-name was clicked in the dialog box shown in dialog-box-name. (S) Outputs, to the log, the information that the button shown in button-name was clicked in the dialog box shown in dialog-box-name.
KAVC4115-I An error occurred, so an operation was not processed. This message indicates that the operation that was attempted before the message appears was skipped due to an error. (S) Informs that the operation attempted before this message appears has been skipped due to an error. After sending this information, the system displays information defined in JP1/AJS3 Console Manager.
(S) Outputs, to the log, the information that the setting file could not be read. Continues processing with assumed defaults. (O) Check whether the OS user who started JP1/AJS3 Console View has the authority to read the setting file. KAVC4118-W (keyword) could not be updated. This message indicates that information such as the window size that JP1/AJS3 Console View automatically saved could not be updated.
(S) Reports that the system disconnected JP1/AJS3 Console Manager, then reconnected it. It also informs that all the displayed Detailed Information dialog boxes were closed because the definition information when the connection was severed may be inconsistent with the definition information when the reconnection was performed. (O) Reopen the Detailed Information dialog box. KAVC4221-W The background image file ((file-name)) cannot be accessed.
KAVC4224-I The operation result is unknown because the connection with the connection destination was severed while performing the operation. This message indicates that the system displayed the KAVC4223-I message and waited for the completion of an operation specified on JP1/AJS3 Console Agent, but whether the specified operation was performed successfully is unknown because the connection destination was disconnected while the operation was being performed.
This message indicates that the business scope shown in the Scope window was changed. (S) Outputs, to the log, the information that the system changed the business scope shown on the Scope window. KAVC4302-Q Are you sure you want to log out? This message asks the user whether to terminate JP1/AJS3 Console View. (S) Waits for the user's response. (O) Click the Yes button to terminate, or the No button to cancel.
(S) Waits for the user's response. (O) Click the Yes button to open the JP1/AJS3 - View window or the No button to cancel. KAVC4306-Q The specified color ((created-color)) is in use. Are you sure you want to delete it? The user attempted to delete a user-created color in the Select Color dialog box, but that color is assigned as the status indication color. This message asks the user whether to delete that color. (S) Waits for the user's response.
KAVC4309-Q The icon image file ((file-name)) cannot be accessed. Are you sure you want to define the specified file name for the icon image file? The user attempted to set an icon image, but the icon image file cannot be accessed. This message asks the user whether to define the specified icon file name. (S) Waits for the user's response. (O) Click the Yes button to validate the setting even if the specified icon image is not displayed, or the No button to cancel.
(S) Cancels processing. (O) A temporary network problem may have occurred. If this message appears during update of definition information, check whether the definition information has been updated. If it has not been updated successfully, re-execute the same operation. If this message appears frequently, an error may have occurred in JP1/AJS3 Console Manager. Use log information such as the Windows event log or the syslog on the host for JP1/AJS3 Console Manager to examine the error.
You can change the maximum number of connections in the environment settings for JP1/AJS3 Console Manager. Change the value of the MAXSESSION environment setting parameter as required. KAVC4506-E A timeout occurred while waiting for the response from the connection destination. A timeout error occurred while the system was waiting for a response from JP1/AJS3 Console Manager. (S) Cancels processing. (O) Check whether JP1/AJS3 Console Manager is normal.
KAVC4512-E The Access Control Server at the connection destination could not be connected. User authentication is impossible because the Access Control server cannot be connected at the connection destination. The user can neither log in nor connect. The possible causes are as follows: • An incorrect host name of the Access Control server is specified in the JP1/Base settings at the connection destination. • The Access Control server specified at the connection destination is inactive.
If the user started JP1/AJS3 Console View in JP1/IM - View, the user cannot log in with the current login information because the authentication bloc at the connection destination is different or because the Access Control server restarted before JP1/AJS3 Console View started. If the user started JP1/AJS3 Console View in the usual way, the user cannot log in with the current login information because the Access Control server restarted during login processing to JP1/AJS3 Console View.
(O) Collect the following data, and then contact the system administrator: • A hardcopy of the window • JP1/AJS3 Console View log information • JP1/AJS3 Console Manager log information For details on how to collect the logs, see 1.3 Data to be collected when a problem occurs in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting and 1.4 Collecting data for troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting.
• JP1/AJS3 Console Manager log information For details on how to collect the logs, see 1.3 Data to be collected when a problem occurs in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting and 1.4 Collecting data for troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting. KAVC4524-W The login information could not be released.
(O) Log out from JP1/AJS3 Console View. Then change the character set settings in a running JP1/AJS3 Console Manager at the connection destination, and check whether the data before you made changes still remains. Even if this message is not displayed, take the above actions if data displayed by JP1/AJS3 Console View contains character errors. KAVC4527-E An error occurred in session processing. Detailed information [(maintenance-information)] Data sent from JP1/AJS3 Console View contains errors.
(S) Outputs, to the log, the information that data from JP1/AJS3 Console Manager was received. KAVC4538-I REQ_EXECCOMMAND: (maintenance-information) This message indicates that JP1/AJS3 Console Manager was requested to perform an operation. (S) Outputs, to the log, the information that the system requested JP1/AJS3 Console Manager to perform an operation. KAVC4539-I NOTIFY_EXECCOMMAND: (maintenance-information) This message indicates that the system was informed of operation completion.
KAVC4542-I CLOSE (connection-information) This message indicates that the connection to JP1/AJS3 Console Manager was closed. (S) Outputs, to the log, the information that the connection shown in connection-information was closed. KAVC4543-W CLOSE_ERR ((maintenance-information)) [(connection-information)] This message indicates that the connection to JP1/AJS3 Console Manager could not be closed.
(S) Outputs the message to the log for examination when a failure occurs, and continues processing. (O) No action is required because this message is internal log information. KAVC4547-I SEND (maintenance-information) This message indicates that the system sent data to JP1/AJS3 Console Manager. (S) Outputs, to the log, the information that the system sent data to JP1/AJS3 Console Manager. KAVC4548-I SDUMP (sent-data) This message indicates that the data was transmitted to JP1/AJS3 Console Manager.
This message indicates the value of the communication option specified in JP1/AJS3 Console View. (S) Outputs, to the log, the value of the communication option specified in JP1/AJS3 Console View. KAVC4552-E SEND_ERR ((maintenance-information)) This message indicates that the system could not send data to JP1/AJS3 Console Manager. (S) Outputs, to the log, the information that the system could not send data to JP1/AJS3 Console Manager, and continues processing.
KAVC4556-I ERR_SDUMP (sent-data) If an error occurs during the transmission of a request from JP1/AJS3 Console View to JP1/AJS3 Console Manager, this message indicates the data sent from JP1/AJS3 Console View. (S) Outputs to the log the data sent from JP1/AJS3 Console View when an error occurred during the transmission of a request from JP1/AJS3 Console View to JP1/AJS3 Console Manager.
KAVC4560-E An error occurred at the connection destination. Detailed information [(maintenance-information)] An error occurred in JP1/AJS3 Console Manager at the connection destination. (S) Cancels processing. (O) Use log information such as the Windows event log or the syslog on the host for JP1/AJS3 Console Manager to examine the error. Then, correct the cause of the error according to the check results. KAVC4561-E Memory became insufficient at the connection destination.
(S) Cancels processing. (O) Use log information such as the Windows event log or the syslog on the host for JP1/AJS3 Console Manager to examine the error. Then, correct the cause of the error according to the check results. KAVC4564-E JP1/AJS3 Console Manager service needs the required permission. The JP1/AJS3 Console Manager service at the connection destination cannot perform processing because it does not have the required permission. (S) Cancels processing.
KAVC4566-E An error occurred in JP1/Base at the connection destination. Detailed information [(maintenance-information)] The system cannot perform processing because an error occurred in JP1/Base at the connection destination. (S) Cancels processing. (O) Use log information such as the Windows event log or the syslog on the host for JP1/AJS3 Console Manager to examine the error. Then, correct the cause of the error according to the check results.
KAVC4569-W InterProcess : (maintenance-information) This message indicates that an error that allows processing to continue occurred during inter-process communication. (S) Outputs, to the log, the information that an error that allows processing to continue occurred during inter-process communication. (O) No action is required because this message is internal log information.
KAVC4603-E The Definition mode is unavailable because the object is currently being monitored. You cannot set the object in the Definition mode because some other software or hardware is now monitoring it. (S) Cancels processing (the object remains in the Monitoring mode). (O) Check that no other software or hardware is monitoring the object, and then set it in the Definition mode.
(O) Wait until the monitoring status indication on the mode panel changes to Monitoring status, and then activate the Definition mode. KAVC4607-E The Monitoring mode is unavailable because the monitoring status is "Stopped Monitoring". The user cannot activate the Monitoring mode because the monitoring status at the connection destination is not Stopped Monitoring. (S) Cancels processing.
KAVC4610-E The object could not be pasted because the maximum number of definitions was exceeded. The user cannot paste the object because the number of definitions exceeds the maximum. (S) Performs pasting until the number of definitions reaches the maximum. (O) Business scopes are also counted as definitions. Recheck the hierarchy, and cancel any group of unnecessary hierarchy levels with business scopes. KAVC4611-E Select one object.
(O) As required, from the menu, choose View, JP1/AJS3 - View, and JP1/AJS3 - View Window to activate the JP1/ AJS3 - View window. KAVC4614-E An upper-level business scope does not exist. The user attempted to display an upper-level business scope while the root business scope was displayed. (S) Cancels processing. (O) Check the hierarchy level of the business scope currently displayed. KAVC4615-E An object with the same name already exists. Rename the object.
(O) Delete unnecessary display colors, and then create display colors. KAVC4618-E A color with the specified RGB element already exists, so you cannot specify the RGB element. The user cannot create display colors that have the same RGB element values as those of the basic colors or existing user-created colors. (S) Cancels processing. (O) Create a color by specifying RGB element values different from those of existing display colors.
(S) Cancels processing. (O) Select a display color from the Available colors list. KAVC4622-E An error occurred while displaying the message box. An error occurred while the system was displaying a message box. (S) Outputs, to the log, the information that an error occurred while the system was displaying a message box. (O) Collect the following data, and then contact the system administrator: • JP1/AJS3 Console View log information KAVC4623-E The log could not be output.
The user cannot create more objects because the number of definitions exceeded the maximum. (S) Cancels processing. In Automatic Creation of Monitored Objects mode, continues the creation process until an error is detected. (O) Business scopes are also included in the number of definitions. Recheck the hierarchy and if there are unnecessary hierarchical levels, cancel grouping based on business scopes. KAVC4626-E The help is not installed. The system cannot display help because it has not been installed.
KAVC4631-E The specified operation was not performed because the connection was severed during processing. The connection was severed while the system was displaying a confirmation message dialog box and a dialog box. As a result, the system did not perform any further update or operation on the AJS3 unit-monitored object. (S) Cancels processing. (O) Re-execute the update and the operation on the AJS3 unit-monitored object. KAVC4632-E The available file extensions are .jpg and .gif.
(O) Check whether the directory-name directory exists. Also check whether a file with the extension extension-name exists in that directory. Even if the user creates a directory or adds a file with the above-mentioned extension to the directory immediately after the above error message appeared, clicking the ...
The user cannot create the object because the maximum number of objects that can be defined in the business scope at the definition destination has been exceeded. (S) Cancels processing. In Automatic Creation of Monitored Objects mode, the system continues the creation process until an error is detected. (O) Increase the map size of the business scope at the definition destination, and then redefine the object.
KAVC4641-E Moving is not possible because the cut business scope and paste destination business scope are the same. The object does not move because the cutting business scope and the pasting business scope are the same. (S) Cancels processing. (O) Paste the object to a business scope different from the cutting business scope. KAVC4642-E A business scope cannot be moved to a lower hierarchy level. The user cannot paste a cut business scope to a lower hierarchy level.
KAVC4645-E The (operation-name) is not possible because the execution ID is unknown. The system cannot perform the specified operation because the status of the target object being monitored for the operation is Not registered or Not scheduled. (S) Cancels processing. (O) Re-execute the operation after the status of the target object is obtained correctly and the status becomes something other than Not registered or Not scheduled. KAVC4646-E The operation failed.
(O) Use log information such as the Windows event log or the syslog on the host for JP1/AJS3 Console Manager to examine the error. Then, correct the cause of the error according to the result in the log. KAVC6102-E Memory became insufficient at the connection destination. The system cannot display the status because memory became insufficient in JP1/AJS3 Console Manager at the connection destination. Alternatively, the system could not perform the operation.
KAVC6111-E The host name of the monitoring destination could not be resolved. The system cannot display the status because JP1/AJS3 Console Manager at the connection destination cannot determine the host name specified in the monitored-host's name in the Define Details dialog box. (S) Sets Unknown as the status of the object and continues processing. (O) In the monitored-host's name in the Define Details dialog box, specify a host name that JP1/AJS3 Console Manager can determine.
(O) Check that JP1/AJS3 Console Agent on the monitoring destination host is normal. If the IPC_TIMEOUT environment setting parameter has been specified in the environment settings in JP1/AJS3 Console Manager at the connection destination, check also whether the timeout period is too short. KAVC6114-E The connection was reset at the monitoring destination.
(O) If there are two or more objects to be monitored on the same host, specify the same name for Host name for each monitored object. A maximum of 50 hosts can be monitored using a root business scope. To monitor more than 50 hosts, create another root business scope and define the monitored objects. KAVC6201-E An error occurred at the monitoring destination.
The system cannot display the status because the file system or device in JP1/AJS3 Console Agent at the monitoring destination does not have sufficient free space for writing a file. Alternatively, the system cannot perform the operation. (S) Sets Unknown as the status of the object and continues processing if the error occurred during status acquisition. If the error occurred during an operation, the system determines that the operation is an error and continues processing.
The system cannot display the status because the JP1/Base settings on the monitoring destination host disable communication with the host name or IP address that was specified in the Define Details dialog box as the name of the host to be monitored, and thus connection cannot be made. (S) Sets Unknown as the status of the object and continues processing.
KAVC6232-E JP1/AJS3 Console Agent service needs the required permission. The system cannot display the status because the JP1/AJS3 Console Agent service on the monitoring destination host does not have permission to perform processing. (S) Sets Unknown as the status of the object and continues processing. (O) Check the permission of the JP1/AJS3 Console Agent service on the monitoring destination host. • In Windows: Check that the account of the JP1/AJS3 Console Agent service is a local-system account.
KAVC6243-E The object to monitor is specified incorrectly. The system cannot display the status because the data entered in the monitored-object option in the Define Details dialog box contains format errors. (S) Sets Unknown as the status of the object and continues processing. (O) For an AJS3 unit-monitored object, specify the monitored object (AJS3 unit name) in the Define Details dialog box as follows: scheduler-service-name:/unit-name KAVC6251-E The specified monitoring method is not supported.
KAVC6301-E The operation function is not supported at the monitoring destination. JP1/AJS3 Console Agent on the monitoring destination host does not support the operation function. (S) Continues processing, determining the operation to be an error. (O) Upgrade the version of JP1/AJS3 - Manager at the monitoring destination to the version that supports the operation function. Note that JP1/AJS2 - Manager 06-71 at the monitoring destination does not support the operation function.
2.3 Messages beginning with KAVS (Messages about the scheduler and the common processing) This section lists the messages that begin with KAVS (Messages about the scheduler and the common processing). When using JP1/AJS3 in a compatible ISAM configuration, see the JP1/AJS2 manuals. Supplementary note Messages that begin with KAVS also include messages about the queueless job execution facility. KAVS0100-E Illegal option (option) exists. An invalid option was specified. (S) Cancels command execution.
KAVS0103-E Invalid value for option (option). The option contains an invalid value. (S) Cancels command execution. (O) Correct the value for the option, and then re-execute the command. KAVS0104-E Option (option) appears twice or more. The same option was specified more than once. (S) Cancels command execution. (O) Specify the option only once, and then re-execute the command. KAVS0105-E Jobnet name not specified. A jobnet name is missing. (S) Cancels command execution.
(O) When name is displayed, specify a unit name that the system can handle as a unit, and then re-execute the command. When name is not displayed, check the jobnet name for invalid characters. Delete the invalid characters, and then re-execute the command.
KAVS0110-E Jobnet (jobnet-name) is in execution. The jobnet is being executed. (S) Cancels command execution. (O) Wait for the jobnet to terminate the execution, and then re-execute the command. KAVS0111-E Unit name not specified. A unit name is missing. (S) Cancels command execution. (O) Specify a unit name, and then re-execute the command. KAVS0112-E Cannot treat as Unit.: name The system cannot handle name as a unit. (S) Cancels command execution.
KAVS0113-E No authority for Unit (unit-name). You do not have an authority for the unit. (S) Cancels command execution. (O) Execute the command with the authority for the unit. KAVS0115-E Unit (unit-name) already registered as Jobnet. The unit has already been registered as a jobnet. The probable causes are: • A relationship change option is specified for the registered unit. • A jobnet connector information change option is specified for the planning group that contains the registered unit.
KAVS0117-E Job name not specified. A job name is missing. (S) Cancels command execution. (O) Specify a job name, and then re-execute the command. KAVS0119-E Cannot use - in use by other user.: unit-name or file-name Operation is impossible because another user is using the job, jobnet or job group that you attempted to execute with a command. Alternatively, another user is using the file that you attempted to manipulate. (S) Cancels command execution.
• Invalid characters are specified for a file name or directory name. • A directory is specified. • There is not enough free space on the file system or device to which you attempted to write a file. • The number of files that can be handled by the process or system exceeds the maximum. • Memory is insufficient. (S) Cancels command execution. (O) Correct the information about the file, and then re-execute the command. KAVS0126-E Operand value exceeds prescribed length.
KAVS0130-E Specified Jobnet (jobnet-name) is not registered. The jobnet is not registered. (S) Cancels command execution. (O) Register the jobnet, and then re-execute the command. KAVS0132-E Job error information directory (directory-name) does not exist. The job error information directory specified in the JOBINFDIR environment setting parameter does not exist. (S) Cancels command execution. (O) Create the job error information directory, and then re-execute the command.
The probable causes are: • An attempt was made to re-execute a jobnet that has not been executed. • An attempt was made to re-execute a job that was not placed in the termination status. • With the hold option specified, an attempt was made to re-execute a root jobnet that was being executed. • An attempt was made to re-execute a root jobnet that was both being executed and contained in the remote jobnet. (S) Cancels command execution.
(S) Cancels command execution. If you specify more than one job (including specifications of regular expression), the system continues processing. (O) Specify a job name as the unit name, and then re-execute the command. KAVS0146-E Options (option) are specified too many times. Too many options were specified. (S) Cancels command execution. (O) Check the number of options that can be specified concurrently, and then re-execute the command.
(S) Cancels command execution. (O) Recheck the value of the relationship change option, and then re-execute the command. KAVS0159-W Option (option) has been ignored which is incompatible with the Unit (unit-name). The system invalidates an option that cannot be specified for the unit. (S) Continues processing. KAVS0161-I Unit does not found for selected option.: unit-name The probable causes are: • There is no unit for the specified unit name that meets the selected option.
(O) Correct the scheduler service name, and then re-execute the command. For details on the environment variables, see A.1 Notes on defining environment variables in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1. KAVS0166-E Cannot create a plan for the specified period.: jobnet-name A plan cannot be created for the specified period of time. (S) Cancels processing. (O) Recheck the schedule definition of the jobnet, and then re-execute the command.
The jobnet is blocked. The probable causes are: • The unit defined in the calendar to be viewed does not exist. • The unit defined in the exclusive schedule does not exist. (S) Terminates processing. (O) Unregister the blocked jobnet, and then check and re-register the schedule definition. Re-execute the command as required. KAVS0170-E No authority for schedule definition file (schedule-information-file-name). You do not have permission for the schedule information file. (S) Terminates processing.
(S) Terminates processing. (O) Correct the temporary file directory name specified in the environment setting for the scheduler service, restart the scheduler service, and then re-execute the command. • In Windows, the invalid characters for a directory name are: \ / ; * ? " < > | : , • In UNIX, the invalid characters for a directory name are: \ / ; * ? " < > | space . & ' ` ~ ( ) KAVS0173-E No authority to use temporary directory (directory-name).
KAVS0177-E Database type is invalid. You cannot use the database. (S) Terminates processing. (O) Correct the database type, and then re-execute the command. If you want to specify advanced settings and perform a data migration to a standard configuration in an environment in which multiple scheduler services are set up, make sure that the JP1/AJS3 database setup has been completed for all the scheduler services. Then, re-execute the jajs_migrate command with the -S option specified.
(O) Correct the execution ID, and then re-execute the command. KAVS0181-E Execution ID cannot be appointed. The execution ID cannot be specified. (S) Terminates processing. (O) You do not need to specify the execution ID. KAVS0182-E Logical host name cannot be appointed. The logical host name cannot be specified. (S) Terminates processing. (O) You cannot execute the command remotely. Execute the command on the desired host without specifying the logical host name.
(O) Correct the execution ID, and then re-execute the command. KAVS0185-E Cannot operate - wait for activation condition.: unit-name Processing is impossible because of the start-condition wait status. (S) Terminates processing. (O) Specify a unit which is not in the start-condition wait status, and then re-execute the command. KAVS0186-E Package file name not specified. A package file name is missing. (S) Terminates processing. (O) Specify a package file name, and then re-execute the command.
The value specified for the abnormal threshold is equal to or greater than the lower limit of the return code for automatic retry. • If -ej, -el, -eh, -jS, -jG, -lP, or -uP is output for option: There is no integer value in the range of values for judging the return code or variable (numeric). • If-NL or -Nt is output for option: - The log type specified for the -NL option is not oth, and a log type is specified for the -Nt option.
• To change the automatic retry setting (-rs, -re, -rc, or -ri option), specify cod for the -jd option to specify end judgment by threshold. • If automatic retry is disabled, do not specify an automatic retry setting (-rs, -re, -rc, or -ri option). • If automatic retry is enabled, make sure that the lower limit (-rs option) and the upper limit (-re option) of the return code for automatic retry are greater than the abnormal end threshold (-th option).
For details about the environment variables, see 1.4 Environment variables in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2. KAVS0191-E Cannot communicate with scheduler service. Communication with the scheduler service was disabled because the service stopped during communication with the scheduler service or other reasons. (S) Terminates processing. (O) Make sure that the scheduler service is running.
(S) Cancels command execution. (O) Unregister the execution of the unit or suspend the unit, and then re-execute the command. KAVS0198-E Cannot use - Unit (unit-name) is currently setting or releasing the suspend setting. Another user is suspending the unit or releasing it from the suspended state. You cannot use the unit. (S) Cancels command execution. If you specify more than one unit (including specifications of regular expression), the system continues command execution.
(S) Terminates the scheduler service. KAVS0202-E Log daemon ended abnormally. (code: code) The log daemon terminated abnormally. (S) Cancels the processing of the log daemon, but continues the operation by the scheduler service. (O) Contact the system administrator, and collect data (see 1.2.3 To the system administrators). KAVS0203-I Log file (scheduler-log-file-name-before-replacement) has been changed to scheduler-log-file-name-afterreplacement.
(S) Terminates processing. KAVS0209-E Scheduler service is inactive. The scheduler service has already stopped. (S) Terminates processing. KAVS0210-I Local time has been changed from local-date-and-time-before-change to local-date-and-time-after-change. The local date and time of the scheduler service has been changed. (S) Terminates processing. KAVS0211-W Standstill of last scheduler service (process-name) was incomplete. The previous termination of the scheduler service was incomplete.
KAVS0214-I The generation management sub-daemon (scheduler-service-name) started. This message indicates that the generation management sub-process has started. (S) Continues processing. KAVS0215-I The generation management sub-daemon (scheduler-service-name) ended. This message indicates that the generation management sub-process has ended. (S) Continues processing. KAVS0216-E The generation management sub-daemon (scheduler-service-name) ended abnormally.
Since the scheduler service for which a cold start was attempted was still accessing the database, database registration information could not be deleted and the cold start of the scheduler could not be performed. The possible causes are: • JP1/AJS3 - View is connected to the object scheduler service. • A JP1/AJS3 command is executing on the object scheduler service. You can use the ajsstatus or jajs_status command to check the connection status of JP1/AJS3 - View. For details about each command, see 2.
KAVS0221-I Scheduler log output process ended. The scheduler log output process has ended. (S) The scheduler log output process has ended. KAVS0222-E Host name (host-name) is too long. A host name is specified using a character string of more than 32 bytes. (S) Terminates processing. (O) Specify a host name that has fewer than 33 bytes, and then re-execute the command. For details on the jajs_migrate command, if it has been executed, see jajs_migrate in 2.
For details on the ports that JP1/AJS3 uses, see A.1 Tables of port numbers in the Job Management Partner 1/ Automatic Job Management System 3 System Design (Configuration) Guide. KAVS0232-W Cannot read host name information.: maintenance-information-1 maintenance-information-2 Since information about the local host cannot be obtained, nothing will be set for the host name in termination messages for judgment jobs and OR jobs. (S) Continues processing.
KAVS0242-I The execution request of the event job started. (name : jobnet-name : execution-ID) The execution request of the event job starts. execution-ID appears if you specified yes for the LOGINFOALL environment setting parameter. (S) Continues processing. KAVS0243-E Cannot terminate the jobnet(jobnet-connector-name : execution-ID) - jobnet for the connection destination is not registered.
(S) Continues processing. KAVS0246-E The system failed to delete the execution result (execution-ID : execution-ID) of the jobnet (jobnet-name).: maintenance-information The system could not delete the execution result of one generation. (S) Continues processing. (O) Take actions according to the Windows event log or syslog message output immediately before this error message.
KAVS0249-W The scheduler services stopped before execution of the job(job-name : execution-ID) began. The scheduler service stopped before the job was placed in Running status. As a result, if execution of the job begins on the agent, the job status changes to Running when the scheduler service is started. This might cause a delay during delay detection for the required execution time for a job. (S) Continues processing.
(O) Determine the cause of the error by checking the integrated trace log or the detailed log of the job, correct the cause of the error, and then restart the appropriate job. KAVS0254-W maintenance-information The queueless job completed with a warning. For details on maintenance information, see C.2 Log entries output by the queueless agent service in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting. (S) Continues processing.
(O) Check the execution status of the units contained in the jobnet to examine the cause of the unsuccessful execution, and then take action to correct it. KAVS0263-I Job started.(name: jobnet-name: execution-ID, host: host-name, JOBID: job-number) The job starts. (S) Continues processing. execution-ID, host-name, and job-number appear if you specified yes for the LOGINFOALL environment setting parameter. KAVS0264-I Job ended normally.
If code 128 is displayed for a PC job, the job may have terminated abnormally due to a desktop heap that is too small. See 4.2.3 Changing the JP1/AJS3 service settings (Windows only) in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide and, if necessary, check the account of the JP1/AJS3 service.
KAVS0269-W Job ended with warning. (name: job-name: exception-ID, code: code, host: host-name, JOBID: job-number) The job has terminated with a warning. The job has terminated with a warning. execution-ID and job-number appear if you specified yes for the LOGINFOALL environment setting parameter. (S) Continues processing. (O) Examine the cause of the warning and take action to correct it. For details on the job execution results, check the Execution Result Details dialog box for JP1/AJS3 - View.
(O) See the message output before this message to examine the cause of the error and correct it. Then, unregister the blocked jobnet and reregister it. KAVS0273-E Jobnet (jobnet-name: execution-ID) cannot be scheduled - error (maintenance-information) occurred. The error, that prevented processing, indicated by maintenance-information occurred. The jobnet cannot be scheduled.
The jobnet is delayed stopping. execution-ID appears if you specified yes for the LOGINFOALL environment setting parameter. (S) Continues processing. KAVS0277-I Start time for next execution schedule has been reached. (name: jobnet-name: execution-ID) Since the start time for the next execution schedule was reached or because the start condition was satisfied, an attempt was made to start a new jobnet during execution of another jobnet. However, the multiple startup was not specified.
KAVS0289-E Manager's host name not specified. The execution manager for the remote jobnet is not specified. (S) Abnormally terminates the remote jobnet. (O) Correctly specify the execution manager for the remote jobnet, and then register the remote jobnet for execution. KAVS0291-E Specified host name does not exist.: host-name The specified host name does not exist. (S) For job execution: Abnormally terminates the job (as unsuccessful startup) and continues processing.
• The calendar information about the jobnet schedule for execution registration does not contain the specified job group. (S) Terminates processing. (O) Re-open the window. KAVS0301-E No authorization. The probable causes are as follows: • You do not have authorization for the unit (including the lower-level unit) or the associated file (such as the standard error output file).
(O) Specify the unit definition file correctly, and then re-execute the command. For details about how to set up unit definition files, see 4. Creating Information Definition Files in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2. KAVS0314-E File processing count exceeds the limit. The number of files to be processed exceeded the limit. (S) Cancels processing.
(S) Terminates processing. (O) Close unnecessary windows and dialog boxes, and delete unnecessary files to increase available free space. Then re-execute the operation. In UNIX, check the following items in the kernel parameters: • Maximum number of files allowed to be open for a process or system • Maximum number of file descriptors allowed (a limit value related to the file system) Also see Release Notes, and change the settings for the file system. KAVS0318-E System resources became insufficient.
If the target backup box or backup file was deleted by the ajsbkudel command while the Backup or Restore dialog box was displayed in JP1/AJS3 - View, close the Backup or Restore dialog box in JP1/AJS3 - View, and then redisplay it. For any other case, recheck the settings of the semaphores and shared memory in the kernel parameters. For details about the kernel parameters, see Release Notes. KAVS0322-E Cannot operate - Scheduler service has not started.
(O) Start the JP1/AJS3 service, and then re-execute the command. KAVS0369-E Cannot operate - version is different. Processing is impossible because the version of JP1/AJS3 that manages the unit to be processed does not match that of JP1/AJS3 on the operating side. (S) Continues processing. (O) Contact a user who has superuser privileges or is logged on as a member of the Administrators group to check the version. KAVS0435-E Environment file name length exceeds 255 bytes.
KAVS0470-E Among the generations registered in the specified period, there is no generation whose registration can be canceled. (unit-name) There is no information registered in the specified period. This prevented the registration from being canceled. (S) Cancels command execution. (O) Check the period specified for canceling the registration, and then re-execute the command. KAVS0475-I There is no log record that satisfies the specified conditions.
KAVS0478-E Scheduler log file name is too long. A scheduler log file name is specified using a character string of more than 255 bytes. (S) Cancels command execution. (O) Specify a scheduler log file name that has fewer than 256 bytes, and then re-execute the command. KAVS0500-E Scheduler service has already started. The scheduler service has already started. (S) Cancels command execution. (O) Use the jajs_spmd_status command to check the status of the process.
KAVS0532-I JP1/AJS2 Monitor service started accepted processing. (From: IP-address, To: logical-host-name, JP1-username, PID: process-ID) ajsinetd process starts the processing that is accepted. The monitor server that ajsinetd accepted from IP-address has started on logical-host-name. (S) Continues processing. KAVS0533-I JP1/AJS2 Monitor service ended accepted processing. (From: IP-address, To: logical-host-name, JP1-username, PID: process-ID) ajsinetd process terminated the processing that was accepted.
(S) Waits for a response. (O) Enter y to change the local date and time. Enter n not to change the local date and time. KAVS0541-E Specified local time is not acceptable. The local date and time to be changed was specified outside the range (between the year 1994 and 2036). (S) Cancels processing. (O) Set the local date and time within the range from the year 1994 to 2036. KAVS0545-I The shift processing of JP1/AJS3 to a standard composition has started.
KAVS0548-I The shift processing of JP1/AJS3 to a standard composition has already been completed. The migration processing of JP1/AJS3 to the standard configuration has already been completed. (S) Cancels command execution. KAVS0549-E Because the JP1/AJS3 service has started, the shift processing of JP1/AJS3 to a standard composition has been discontinued. The migration processing of JP1/AJS3 to the standard configuration has been canceled because the JP1/AJS3 service has started.
An invalid environment variable was specified. (S) Cancels command execution. (O) Correct the environment variable, and then re-execute the command. For details on the environment variables, see 1.4 Environment variables in the manual Job Management Partner 1/ Automatic Job Management System 3 Command Reference 1. KAVS0600-E Valid calendar definition options not specified. The calendar definition does not contain the required option. (S) Cancels command execution.
KAVS0603-E Illegal character exists in option string (option-character-string). The option or the date information file contains an illegal character. (S) Continues command execution. The system invalidates the illegal character. (O) Correct the character in the option or in the date information file. Then, re-execute the command. KAVS0604-E Cannot read date information file (file-name) - error occurred. An error occurred during input into the date information file. (S) Continues command execution.
KAVS0621-E Cannot delete - Unit (unit-name) is registered. The specified unit cannot be deleted because it is contained in a registered root jobnet or a registered jobnet. (S) Cancels command execution. (O) Unregister the unit, and then re-execute the command. To delete jobnets and jobs defined in a suspended root jobnet, re-execute the command with the -S option. KAVS0622-E Cannot delete - Unit (unit-name) has registered Jobnet. The unit that contains a registered jobnet cannot be deleted.
KAVS0631-E Cannot move - Unit (unit-name) is already registered. The output destination unit cannot be moved because it has already been registered. (S) Cancels command execution. (O) Unregister the output destination unit, and then re-execute the command. To move jobnets and jobs into a suspended root jobnet, re-execute the command with the -S option. KAVS0632-E Cannot move - Unit (unit-name) contains a registered Jobnet. The output destination unit cannot be moved because it contains a registered jobnet.
KAVS0635-E Cannot copy - Unit (unit-name) does not exist. An attempt was made to copy more than one unit. However, copying was impossible because the destination unit does not exist. (S) Cancels command execution. (O) Create the destination unit, and then re-execute the command. KAVS0636-E Cannot move - Unit (unit-name) does not exist. An attempt was made to move more than one unit. However, moving was impossible because the destination unit does not exist. (S) Cancels command execution.
KAVS0639-E Cannot copy the Unit (unit-name) - currently used by another user. Another user is using the unit, preventing it from being copied. (S) Cancels command execution. (O) Wait for the other user to complete using the unit, and then re-execute the command. KAVS0640-E Cannot move the Unit (unit-name) - currently used by another user. Another user is using the unit, preventing it from being moved. (S) Cancels command execution.
(O) Check whether the output destination is the planning group. Correct the unit name, and then re-execute the command. KAVS0648-E A unit other than a jobnet in the planning-group cannot be copied.: unit-name An attempt was made to copy a unit other than the jobnet or the remote jobnet into the planning group. (S) Terminates processing. If you specify more than one unit, the system continues processing of the units of the jobnet or the remote jobnet.
The statement indicated by sentence-number in the message might follow the statement containing the error. If the indicated statement number is correct, review the definition parameters in the unit containing the indicated sentence number to identify the location of the error. (S) Cancels command execution. If you specify more than one unit definition parameter file name, the system continues processing. (O) For a unit definition file, see 4.
Perform the following: - Delete the unit at the copy destination, and then retry the copy. 4. If JP1/AJS3 - View was used to restore a unit: Perform the following: - Delete the unit you attempted to restore, and then retry the restoration. KAVS0653-E Cannot treat as definition Unit.: unit-name unit-name cannot be the definition-destination unit. The possible causes are: • The unit specified as the definition-destination does not exist.
KAVS0656-Q Ok to update Unit (unit-name) ? (y:OK/n:NG) This message checks whether you want to update the unit. (S) Waits for a response. (O) Enter y to update the unit. Enter n not to update the unit. KAVS0657-E Cannot treat as a unit definition parameter file.: file-name The file was specified in a format that the unit definition parameter file cannot use, preventing it from being analyzed. (S) Cancels command execution.
KAVS0659-E No authority to use definition unit (unit-name). The definition unit does not have any authority, preventing it from being defined. (S) Cancels command execution. (O) Execute the command with the authority for the definition unit. KAVS0660-E Unit (unit-name) left over. An error occurred while creating the units. An attempt to delete them was unsuccessful, and some of them could not be deleted. (S) Cancels command execution. (O) Use the ajsdelete command to delete the remaining units.
KAVS0668-E The value of the parameter specification range has an error.(unit-name parameter-name-1 parameter-name-2) The value of the specifiable range of values for related parameters has an error. The probable causes are: • If tho, rjs, or rje is output for parameter-name: - The upper or lower limit of the return code for automatic retry is equal to or smaller than the abnormal end threshold. - The lower limit of the return code for automatic retry is greater than the upper limit.
(S) Cancels command execution. (O) A parameter that can be specified only for a unit defined in a start condition might have been specified for a unit defined in an ordinary jobnet. Check the unit definition parameters, and then re-execute the command. KAVS0670-E Definition is invalid. (Jobnet: jobnet-name) Schedule definition information about the jobnet contains errors. The possible causes are: • The specified job group does not exist in the calendar to be referenced.
The probable causes are: • When end judgment for a job was to be performed in a range of condition values, the range to be used as the judgment condition was not specified. • When monitoring is set to monitor logs of a type other than the any-log-type (when parameters other than oth are set for the unit definition parameter ntlgt) for the Windows event-log monitoring job, a log type is specified for anylog-type as the monitoring condition.
• The effective registration date expired. • The registration date exceeded the execution start date, but the process cycle or an alternate method is missing. • The execution start date is a holiday, but the process cycle is missing. • The next execution date is the year 2037 or later. (S) Cancels command execution. (O) Remove the cause of the error, and then re-execute the command. KAVS0684-E Exclusion Jobnet definition of Jobnet (jobnet-name) is invalid.
KAVS0694-E Permission for the file (file-name) is lacking, so a jobnet-end wait is impossible. The jobnet-end wait option (-w) cannot be used, since the jobnet-end wait file does not have update permission. (S) Cancels command processing. (O) The jobnet-end wait file is AJSNETWT.LCK in the directory storing the database. Give update permission to the file, and then reenter the command. KAVS0695-E The file (file-name) does not exist, so a jobnet-end wait is impossible.
A root jobnet in a planning group can only be registered for fixed execution by using the ajsentry command with the -p option or the -b and -e options specified. (S) Cancels command execution. If you specify more than one unit, the system continues processing of the units of the other jobnets. (O) Check the unit to register and the command option, correct the error, and then re-execute the command.
KAVS0700-W A unit was deleted during the command processing. The specified unit no longer exists. It may have been deleted, or moved. (S) Cancels command execution. If you specify more than one unit (including specifications of regular expression), the system continues command execution. (O) Check whether the specified unit exists. Specify the unit, and then re-execute the command. KAVS0701-E A unit that is the target of the operation was not found.
When a unit under a planning group is specified You executed a command on an active unit automatically selected from under a planning group, but the target generation could not be found. The probable causes are as follows: • When executing the ajsplan command, there is no unit to execute for the next time. • When executing the ajskill, ajsintrpt, ajschgstat, or ajsrerun command, there is no unit that has started execution.
The unit ID is specified incorrectly. (S) Cancels command execution. If you specify more than one unit ID, the system continues processing of another unit ID. (O) Correctly specify the unit ID, and then re-execute the command. KAVS0712-E The specified Unit ID (unit-ID) does not exist. A unit with the specified unit ID does not exist. (S) Cancels command execution. If you specify more than one unit ID, the system continues processing of another unit ID.
(O) Specify an execution start date later than the current date, and then re-execute the command. KAVS0721-I Specified Jobnet (jobnet-name) does not accept temporary change in plan. The plan of the jobnet has not been temporarily changed. (S) Cancels command execution. (O) Specify another jobnet, and then re-execute the command. KAVS0722-E Specified Jobnet (jobnet-name) has already terminated. The execution of the jobnet has terminated. (S) Cancels command execution.
(O) Specify a jobnet that has a future plan, and then re-execute the command. KAVS0729-E Cannot change plan temporarily - specified execution start date of Jobnet (jobnet-name) is different from that of higher Jobnet. The execution start date of the jobnet differs from the next execution date of an upper-level jobnet. The plan could not be temporarily changed. (S) Cancels command execution.
(S) Cancels command execution. (O) As required, use the ajssuspend command with the -C option to release the jobnet from the suspended state, and then re-execute the ajssuspend command with the -S option. KAVS0741-E Jobnet (jobnet-name) is not suspended. An attempt was made to release the suspended state on the jobnet that was no longer suspended. (S) Cancels command execution.
The jobnet is being executed. It cannot be re-executed for suspending. (S) Cancels command execution. (O) Wait for the jobnet to complete the execution, and then re-execute the command. KAVS0764-E Specified Unit (unit-name) cannot rerun. The unit cannot be re-executed. The probable causes are: • The status of the job or nested jobnet that you attempted to rerun is one of the following: Now running, Running + Abend, Running + Warning, Wait for prev. to end, Wait for start time, or Being held.
KAVS0780-E Specified Jobnet (unit-name) has no information for display. The jobnet does not contain any information to be displayed. There might be no information to output for the specified period, or the information might have been lost because the unit specified in the command was executed during command execution. (S) Cancels processing for the target unit. If you specify multiple units (including specifications of regular-expressions), the system continues processing from the next unit.
(S) Cancels command execution. (O) Re-execute the command without specifying the -g 0 option with the -l option. KAVS0785-E Insufficient options specified. The required option is missing. (S) Cancels command execution. (O) Specify the option, and then re-execute the command. KAVS0787-E Cannot execute - the system management daemon is busy.
KAVS0829-I Reporting the effective information of JP1/AJS has started. Output of the operating information for the JP1/AJS3 service has started. (S) Continues processing. KAVS0830-I Reporting the effective information of JP1/AJS has terminated. Output of the operating information for the JP1/AJS3 service has terminated. (S) Terminates processing. KAVS0831-I Cannot get View connection information because the JP1/AJS2 service is not started.
• An attempt to send an SNMP trap has failed. (S) Terminates processing. (O) Recheck the SNMP service settings, and then re-execute the command. For details on the SNMP service settings, see A.2 Setup for linking HP NNM (for a Windows host) in the Job Management Partner 1/Automatic Job Management System 3 Linkage Guide or A.3 Setup for linking HP NNM (for a UNIX host) in the Job Management Partner 1/Automatic Job Management System 3 Linkage Guide.
KAVS0853-E No authority to use backup box (backup-box-name). The backup box does not have any authority. (S) Terminates processing. (O) Execute the process with the authority for the backup box. KAVS0854-E Specified backup file (backup-file-name) already exists. The backup file has already been created. (S) Cancels command execution. (O) Check the backup box name, and then re-execute the command. KAVS0855-E Specified backup file (backup-file-name) does not exist. The backup file does not exist.
KAVS0857-E Cannot treat as backup file.: backup-file-name backup-file-name cannot be a backup file. (S) Cancels command execution. If you specify more than one backup file, the system continues processing. (O) Correct the backup file name, and then re-execute the command. KAVS0858-E Backup box name not specified. A backup box name is missing. (S) Cancels command execution. (O) Specify the backup box name, and then re-execute the command. KAVS0863-E Interprocess communication failed.
If the JP1/AJS3 service at the connection destination has not started, start the appropriate service. If the ajsinetd process has not started, execute the jajs_hstd command to start the process. For details on the jajs_hstd command, see jajs_hstd in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1. If the message "Failed to put Event.
(O) If a large jobnet is being executed or if many JP1/AJS3 commands are being executed, wait until the relevant processing terminates, and then re-execute the operation. If a timeout occurred during a request to another host, enable communication with other hosts, and then re-execute the operation. KAVS0866-E Remote connection failed.: maintenance-information-1 maintenance-information-2 The connection destination host cannot be connected during remote connection due to a network error or routing error.
For details about the kernel parameters, see Release Notes, and the explanation of kernel parameters in the Job Management Partner 1/Base User's Guide. KAVS0869-E Invalid data was received.: (IP-address) maintenance-information-1 maintenance-information-2 Invalid data was received from the connection source indicated in IP-address. (S) Stops communication. KAVS0870-I Saving unit (unit-name) to backup box (backup-box-name). The backup command starts processing. (S) Continues processing.
KAVS0874-Q OK to update backup file (backup-file-name) ? (y:OK/n:NO) This message checks whether you want to update the backup file. (S) Waits for a response. (O) Enter y to update the backup file. Enter n not to update the backup file. KAVS0875-Q OK to clear backup box (backup-box-name) ? (y:OK/n:NO) This message checks whether you want to delete the backup box. (S) Waits for a response. (O) Enter y to delete the backup box. Enter n not to delete the backup box.
(S) Terminates processing. (O) Remove the cause of the error, and then re-execute the command. KAVS0880-I Restoring unit (unit-name) to unit (unit-name). The recovery command starts processing. (S) Continues processing. KAVS0885-E Restoration unit (unit-name) does not exist. The restoration unit does not exist, preventing it from being restored. (S) Cancels unit restoration. (O) Create the restoration unit or correct the restoration unit. Then, re-execute the command.
• A communication error has occurred between the manager host where the jobnet is defined and the manager host on which the jobnet is to be executed. • A memory shortage (including a desktop heap that is too small in Windows) has occurred on the manager host where the jobnet is defined or on the manager host where the jobnet is to be executed. • The scheduler service has not started on the manager host where the jobnet is to be executed.
(O) Although the start notification is unsuccessful, it does not affect execution of the remote jobnet. Note, however, that an end notification might fail for the same reason. Correct the cause of the error on the manager host where the jobnet is defined and the manager host where the jobnet is to be executed. If the KAVS0891-E message is output for the target jobnet after this message, end notification has failed.
recovery-information-4 recovery-information-5 recovery-information-6 > ./ajsremnetrcv.log 3. Make sure that the remote jobnet is placed in the end status. If the remote jobnet has not been placed in the end status, collect the following data and then contact the system administrator: - An error message, if any, output by the ajsremnetrcv command - ajsremnetrcv.log 4. Delete the ajsremnetrcv.log file.
If you delete a suspended remote jobnet, the jobnet name is indicated as a number. However, no operational problems occur because processing is performed normally on the manager host where the jobnet is defined. Unregister the jobnet and delete the job group as described above. KAVS0893-E An error occurred in the process that kills the remote jobnet (service-name:jobnet-name:execution-ID). : maintenance-information An error occurred during processing to forcibly terminate the remote jobnet.
An error that allows processing to continue occurred. (S) Continues processing. (O) If the maintenance information contains the character string SPMD communication error, check whether the jajs_spmd process is operating normally. This error message might be output when a system error occurs and the jajs_spmd process terminates first. In such a case, there is no problem with the operation, despite the output of the message.
be written separately to the database. Alternatively, change the value of the pd_lck_pool_size for the embedded database. For details on the UNITDEFDIVIDEUPDATE environment setting parameter, see 2.2.2(100) UNITDEFDIVIDEUPDATE in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2. For details about pd_lck_pool_size, see the description of the single server definition in C.
(O) Take action according to the error information in the Windows event log or syslog output by the OS, and other OSspecific error information. If you cannot take corrective action, contact the system administrator, and collect data (see 1.2.3 To the system administrators). KAVS0904-E Unexpected error occurred in JP1/AJS2.: maintenance-information-1 maintenance-information-2 maintenanceinformation-3 maintenance-information-4 The probable causes are: • An unexpected error occurred during processing.
KAVS0909-E Shared memory is not available.: maintenance-information-1 maintenance-information-2 Shared memory, which is one of the system resources, cannot be obtained, or required shared memory does not exist. (S) Terminates the process where the error occurred. (O) If the size of the system's shared memory is insufficient, increase the value in the kernel parameter. If the shared memory necessary for running the scheduler service has been deallocated, you need to restart the scheduler service.
(O) Check whether the resources are sufficient. Also check the running status of Hitachi Network Objectplaza Trace Monitor. In UNIX, recheck the following items in the kernel parameters: • Maximum number of files allowed to be open for a process or system • Maximum number of file descriptors allowed (a limit value related to the file system) For details about the kernel parameters, see Release Notes. Then, change the settings for the file system.
Cause 2 When the OS is AIX and the ISAM lock table split function is used, the ISAM lock table cannot be allocated. Action Stop all the related JP1 services, set ON for the EXTSHM environment variable, and then retry the operation that resulted in the error. Cause 3 The status of the ISAM lock table has become invalid. Action Delete the ISAM lock table, and then retry the operation that resulted in the error.
KAVS0932-E Error occurred during database access.: maintenance-information-1 maintenance-information-2 maintenanceinformation-3 An error occurred while accessing the database. (S) Terminates processing. (O) The probable causes are as follows. Take action according to the cause of the error. If an error message was output before or after this message, also see the instructions given by that message. Cause 1 Database files were corrupted due to a disk error, CPU error, or other hardware error.
Action Check the estimated file size in the kernel parameter, and set the appropriate value. For details about estimating the kernel parameters, see Release Notes. Cause 7 The size of the ISAM file used for the scheduler database or job execution environment database reached 2 GB. Action Decrease the size of the ISAM file according to 9.3 Notes on the JP1/AJS3 database in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.
The user password may have been changed with the ajssetup command. If the password has been changed, user authentication may fail and the database cannot be accessed. (S) Since an existing user was found, the system resets the password as described below by manipulating the ajssetup command: • When the RDBPASSWORD environment setting parameter is specified, the password is reset to the value of RDBPASSWORD.
(O) The schema has already been defined, so you do not need to use the ajssetup command to set up the schema again. If you want to discard and re-create the existing schema, delete it on the DBMS and then re-execute the ajssetup command. KAVS0940-E Event Action Manager is busy.: maintenance-information maintenance-information maintenance-information maintenance-information The event/action control manager is busy status. Events cannot be processed.
KAVS0943-E Cannot connect to job status notification process.: maintenance-information-1 maintenance-information-2 maintenance-information-3 The status report process could not be connected. The scheduler service cannot start. (S) Stops the scheduler service. (O) Use the messages that are output before and after this message to determine the cause of the unsuccessful connection, and then take action. Also make sure that the port number for job status notification is set correctly in the services file.
KAVS0946-E The error occurred during scheduler service(scheduler-service-name) start processing. : maintenanceinformation-1 maintenance-information-2 maintenance-information-3 maintenance-information-4 An error occurred during startup of the scheduler service. (S) Terminates the scheduler service. (O) If you specified the setting that automatically restarts the scheduler service when it terminated abnormally, the scheduler service is restarted automatically.
KAVS0965-E Specification of the exclusion schedule specified in the jobnet(jobnet-name-2) inside the jobnet(jobnet-name-1) includes an error. The definition of the exclusion schedule specified in the jobnet or nested jobnet contains an error. (S) Cancels allocation of the schedule for the jobnet. (O) Specify the correct jobnet name in the exclusive-schedule definitions, and allocate the schedule with temporary change specified. Alternatively, re-register the jobnet.
(O) Contact the system administrator, and collect data (see 1.2.3 To the system administrators). KAVS0981-E The table is not found. The database table is not found. (S) Terminates processing. (O) Check the values of the TABLENAMEPREFIX and TABLENAMEPOSTFIX environment setting parameters. If there are no tables, use the ajssetup command with the -t option specified to create the table. KAVS0982-E Could not connect to the database because the upper limit of a server setting was exceeded.
(O) Specify the user who has permission for the database, and then retry. KAVS0985-E Could not connect to the database. The database could not be connected. (S) Terminates processing. (O) Check whether the database is running. KAVS0986-E Column size was exceeded because of character set conversion. Because of character code conversion (for example, from Shift JIS to EUC), an attempt was made to write data longer than the column size. (S) Terminates processing.
KAVS0988-E Insufficient tablespace or RDAREA. The table area or RDAREA does not have any free space. (S) Terminates processing. (O) Reorganize the table area or RDAREA or expand the area to make a free area, and then retry. Detailed error messages for the database will be output to the Windows event log or syslog. For an embedded database, the message KFPH00211-I appears. For details on how to reorganize databases, see 2.
• In AIX: LIBPATH KAVS0991-E Not supported on related programs (program-name). program-name does not support the requested function. If this error message appears when using the ajsdbcond command with the -L option specified, you need to install JP1/Base version 06-71 or later versions. (S) Cancels command processing. (O) Check the supported version of a prerequisite program, and upgrade the version of the program. KAVS0992-E There is no permission for object-name.
KAVS0994-E Record existed in specified database table. The database table at the import destination contains a record. (S) Cancels command processing. (O) Re-execute the command with the -c option specified. Executing the command with the -c option deletes all the records in the specified table and then imports the records in the specified database backup file. Once the records are deleted, they cannot be restored.
(S) Terminates processing. (O) Check whether the database is running. For details about how to check this, see the manual for the appropriate database. If the database is starting, recheck the value of the maximum wait time. KAVS0999-W The database could not be connected within the specified time. (Scheduler service : scheduler-service-name, Waittime : maximum-wait-time, Host : host-name) The system will wait because the database could not be connected.
KAVS1004-E Scheduler service does not exist. The scheduler service does not exist. (S) Terminates processing. (O) Specify the correct name of the AJS service to be processed, and then re-execute the command. In addition, check the following: • The environment settings for the started JP1/AJS3 service (on a physical or logical host) contain scheduler service settings.
In UNIX, use the jajs_spmd_status command to make sure that the JP1/AJS3 service has stopped. After making sure that the services have stopped, go to step 3. 3. Execute the ajsshmdel command. 4. Restart JP1/AJS3. For details on the ajsshmdel command, see 15.1.1 Settings for starting multiple scheduler services in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1. KAVS1007-E Host name cannot be resolved. (logical-host-name) The logical host name could not be resolved.
KAVS1010-I The password was successfully changed for a user (JP1-user-name). The password was successfully changed. (S) Continues processing. KAVS1011-E An attempt to change the password for a user (JP1-user-name) failed. Detailed information : maintenanceinformation-1, maintenance-information-2 An attempt to change the password failed.
A connection could not be established because the maximum number of concurrent sessions specified in the MAXSESSION environment setting parameter for the host indicated in host-name was exceeded. If nothing is indicated in host-name, the physical host name was specified. (S) Terminates processing. (O) Check whether the estimated value of the MAXSESSION environment setting parameter is correct. If necessary, change the value. For details on the environment setting parameter, see 2.
(S) Continues processing. (O) Check whether the estimated values of the MAXSESSION and SERVICEMAXSESSION environment setting parameters are correct. If necessary, change the values. For details on the environment setting parameter, see 2.2 Setting up the scheduler service environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2. If you changed the value of a MAXSESSION environment setting parameter, restart the scheduler service on the applicable host.
(S) Cancels command execution. (O) Specify the value for the option and then re-execute the command. KAVS1103-E The specified value (value) is already used with other logical hosts or another scheduler service. The specified value is already used for another logical host or another scheduler service. (S) Cancels command execution. (O) Specify a unique value, and then re-execute the command. KAVS1104-W The specified directory or file (file-name or directory-name) does not exist.
The same option is specified more than once. (S) Cancels command execution. (O) Specify the indicated option only once, and then re-execute the command. KAVS1107-E The specified definition key cannot be set. The specified definition key cannot be set. (S) Cancels command execution. (O) Specify the correct definition key and then re-execute the command. KAVS1108-E An environmental parameter that cannot be set in the specified definition key has been specified.
(S) Cancels command execution. (O) Specify the correct value for the option and then re-execute the command. KAVS1111-E This function cannot be used with the compatible ISAM configuration. This function cannot be used with the compatible ISAM configuration. (S) Cancels command execution. (O) Use a function that can be used with the compatible ISAM configuration. KAVS1112-E The specified directory (directory-name) does not exist. The specified directory does not exist. (S) Cancels command execution.
(S) Cancels command execution. (O) Specify the correct scheduler service name, and then re-execute the command. KAVS1115-E Failed to create shared directory (directory-name). An attempt to create a shared directory has failed. (S) Cancels command execution. (O) Make sure that the following jp1ajs2 directory indicated in the message does not already exist.
(O) Specify the correct logical host, and then re-execute the command. KAVS1118-E Scheduler service is active. The scheduler service is running. (S) Cancels command execution. (O) Stop the scheduler service and then re-execute the command. KAVS1119-Q OK to rename Scheduler service from (scheduler-service-name) to (scheduler-service-name)? (Y: OK/N: NO) This message confirms whether or not you want to continue to rename the scheduler service. (S) Waits for a response.
(O) Check whether read or higher permission has been given for the file shown in the message. If the permission is not set, give read or higher permission for the file, and then re-execute the command. For UNIX, see the Release Notes and make sure that the value of the kernel parameter for memory is greater than the estimated value. If the file does not exist, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).
KAVS1126-E An error occurred during scheduler service addition or deletion processing. (maintenance-information) An attempt to set up or remove the embedded database by executing the command has failed. (S) Cancels command execution. (O) Correct the error according to the cautionary notes for the executed command, and then re-execute the command. KAVS1127-E An attempt to access the log file (file-name) failed. An attempt to access the log file has failed.
KAVS1130-E An attempt to read the configuration definition information failed. An attempt to obtain the configuration definition has failed. (S) Cancels command execution. (O) Contact the system administrator, and collect data (see 1.2.3 To the system administrators). KAVS1131-E Cannot use this option(option-name) with the compatible ISAM configuration. This option cannot be used with the compatible ISAM configuration. (S) Cancels command execution.
• If Disaster recovery is indicated in setting-name, the feature that automatically starts the scheduler service in disaster recovery mode when the JP1/AJS3 service starts will not work. Take the following actions: - Configure the target scheduler service not to start automatically when the JP1/AJS3 service starts. For details, see the description of the AUTOSTART environment setting parameter in 2.
(S) Cancels command execution. (O) Check for duplicate values and then re-execute the command. KAVS1137-E The scheduler service specified for the option (option) does not exist (scheduler-service-name). The scheduler service specified in an option does not exist. (S) Cancels command execution. (O) Specify the correct scheduler service name and then re-execute the command. KAVS1138-E The directory (directory) specified for the option (option) does not exist.
(S) Cancels command execution. (O) In the unit configuration definition, only define parameters that conform to the compatible ISAM configuration. KAVS1141-E Too many parameters are specified. (unit-name parameter-name) A repeatable parameter was specified more than the maximum number of times. (S) Cancels command execution. (O) Check the unit configuration definition, and make sure that no repeatable parameters are specified more times than permitted.
KAVS1144-E The specification of the wait condition is insufficient (unit-name). No units whose ends are being waited for are specified for a unit with wait conditions. (S) Cancels command execution. (O) Check the unit configuration definition and the wait condition settings. KAVS1145-E A parameter value that cannot be defined by the compatible ISAM configuration exists.
(O) Specify the option value correctly, and then re-execute the command. In addition, change the value of the environment setting parameter indicated in parameter-name, and then re-execute the command. • When the environment setting parameter indicated in parameter-name is "MAXSAVEGEN" Check and, if necessary, change the value of the MAXSAVEGEN environment setting parameter. For details on the settings, see 2.
(O) Check the following: • Check whether system resources are sufficient. • Check whether the permission environment of the started user is correct. • Check whether the directory created at JP1/AJS3 installation was unintentionally deleted. KAVS1400-E The status of the jobnet (jobnet-name) whose start condition was being monitored could not be confirmed. (execution-ID) The status of the jobnet of which the start condition is being monitored could not be confirmed.
(S) Lets the jobnet in Wait for start time status wait for the monitoring generation to terminate. When the monitoring generation has terminated, the jobnet starts monitoring of the start condition. (O) Perform either of the following according to the needs of the operation. To immediately start monitoring: Kill the current monitoring generation. To wait for the monitoring generation to terminate and start monitoring: No action is required.
KAVS1503-I The ISAM unused area size of the scheduler service (scheduler-service-name) is size-in-megabytes. The size of the unused area of the ISAM file of the scheduler service is output. (S) Outputs the size of the unused area of the ISAM file. KAVS1504-W The ISAM unused area size of the scheduler service (scheduler-service-name) is size-in-megabytes, which exceeds the size-in-megabytes threshold value.
(O) The database cannot be accessed because the size of the ISAM files exceeded 2 gigabytes. Reduce the size of the ISAM files by unregistering or deleting units unnecessary for operation or by reducing the number of days for storing job information in the job execution environment. KAVS1513-E An error occurred during command processing.: maintenance-information An error occurred when JP1/AJS3 and OS commands were executed in a script. (S) Check whether the script execution environment is correct.
KAVS1516-E Construction is invalid.(maintenance-information) The configuration is invalid. The probable causes are: • The installation or migration of JP1/AJS3 might not have finished. • The value of the DEFLENTYPE environment setting parameter is different from the value of DEFLENTYPE in shared memory. • The value of the DEFLENTYPE environment setting parameter does not match the format of the scheduler service database. • The value of the AJSCHARCODE environment setting parameter is invalid.
also deleted. Before deleting the database environment, execute the ajsprint command to back up the definitions. If the value of the AJSCHARCODE environment setting parameter is invalid: If sjis is specified for the DEFLENTYPE environment setting parameter, you need to specify UTF-8 for the AJSCHARCODE environment setting parameter. KAVS1517-E An error occurred during an attempt to acquire the configuration definition of the host (host-name).
(O) Set the value indicated in item-name correctly. For details about output item names, see2. Environment Setting Parameters in the Job Management Partner 1/ Automatic Job Management System 3 Configuration Guide 2 KAVS1570-I Adapter command (maintenance-information-1) started. The adapter command started. The following information is shown in maintenance-information. maintenance-information-1: The adapter command name and the specified option value (S) The adapter command started.
KAVS1600-E The specified unit name is invalid. The status could not be acquired because of one of the following reasons after you specified the unit name. • The unit does not exist. • You have no permission for the unit. • The unit exists under the manager job group, manager jobnet, or the root jobnet. The status of the unit is unavailable. This message is output to the Information text area in the Detail Information - [object-type] dialog box. For details about this dialog box, see 16.3.
KAVS1703-E The command executed during reorganization of the scheduler service (scheduler-service-name) database ended abnormally.: Jischk -l3 table-name : return code = return-code-from-Jischk (Please look at maintenance-log-file-name) While maintenance was being performed by the jajs_maintain command, invalid data was detected by the Jischk command, which verifies consistency between ISAM files. For details of the error message output by Jischk, see the maintenance log file. (S) Cancels command execution.
KAVS1706-E An attempt to create a backup directory during reorganization of the scheduler service (scheduler-service-name) database failed. (directory-name): return code = return-code While maintenance was being performed with the jajs_maintain command, the working directory could not be created. (S) Cancels command execution. If there are other services being processed, the system continues command execution.
The probable causes are: • More than one jajs_maintain command was executed at the same time for the scheduler service. • The scheduler service was started during execution of the jajs_maintain command. (S) Cancels command execution. If, however, any other services remain unexecuted, the system continues command execution. (O) Wait until the jajs_maintain command terminates. Then manually start the scheduler service that could not be started.
(O) Execute Jischk -l3 table-name to check whether a problem exists with the table whose reorganization ended abnormally. For details about Jischk, see the Job Management Partner 1/Base User's Guide. After collecting the result of Jischk, contact the system administrator (see 1.2.3 To the system administrators). KAVS1716-E An attempt to prepare for reorganization of the scheduler service (scheduler-service-name) database failed.
(S) Cancels command execution. (O) Log off from programs such as JP1/AJS3 - View or JP1/AJS3 Console to make sure that there are no processes accessing the database. KAVS1719-I The maintenance processing of the scheduler service ended normally. The maintenance of the scheduler service ended normally. (S) Performs a normal termination of the maintenance of the scheduler service. KAVS1720-E The maintenance processing of the scheduler service ended abnormally.
(S) Starts the jajs_maintain command. KAVS1722-I jajs_maintain command ended normally. The jajs_maintain command ended normally. (S) Performs a normal termination of the jajs_maintain command. KAVS1723-E jajs_maintain command ended abnormally. The jajs_maintain command ended abnormally. (S) Terminates the jajs_maintain command. (O) Check the following items to determine the cause of the abnormal termination of the maintenance process. Then, re-execute the maintenance process.
• Check whether the specified scheduler service name contains errors. • Check whether the specified scheduler service has been set up. If the specified scheduler service has not been set up yet, set it up by executing the ajssetup command. • If this message was output after you upgraded the version, start the JP1/AJS3 service. Starting the JP1/AJS3 service creates control files for all the scheduler services on the physical or logical object host.
• A logical contradiction occurred in the manager. See KAVU0969-E. • That request is not supported by the requested manager. See KAVU0970-E. • The execution environment is invalid. See KAVU0972-E. KAVS1726-I The scheduler service (scheduler-service-name) was shifted to maintenance mode. The scheduler service was put into maintenance mode. (S) Continues processing. KAVS1727-I The scheduler service (scheduler-service-name) was stopped. The scheduler service was stopped. (S) Continues processing.
KAVS1730-I The maintenance mode of the scheduler service (scheduler-service-name) was canceled. Maintenance mode was canceled for the scheduler service . (S) Continues processing. KAVS1731-E Back up scheduler database (unit information only). The system started the backup process only for the unit definition table of the scheduler service. (S) Continues processing. KAVS1732-E Succeeded in backup of a scheduler service ISAM file. The system backed up the ISAM files for the scheduler service successfully.
KAVS1735-E Need to rerun this command. You need to re-execute this command. (S) Cancels command execution. (O) See the message output together with this message, and then take proper action. KAVS1736-E Backup failed. Command ended abnormally.: ajsgtroot -F service-name option : return code = return-value-fromajsgtroot-command The ajsgtroot command could not be executed. (S) Cancels command execution.
KAVS1739-E Backup failed. Failed to make directory (directory-name).: return code = return-value-from-mkdir Since the backup directory could not be created, the ISAM files for the scheduler service could not be backed up. (S) Cancels command execution. (O) If you specified the -b option, check whether the parent directory of the specified directory has write permission and is a directory.
(O) The system could not compare the files at the backup source and the backup destination. The database for the scheduler service may have been updated. Take actions according to the error message of the cmp command output together with this message. KAVS1751-E Restoring scheduler database (unit information only). The system restores the unit definition table for the scheduler service. (S) Continues processing. KAVS1752-E Succeeded in restoring of a scheduler service ISAM file.
KAVS1755-E A file (file-name) is not found. The file is not found. (S) Cancels command execution. (O) The unit definition table for the scheduler service is not stored in the directory specified as the recovery source directory. KAVS1756-E Failed to delete ISAM file (file-name).: return code = return-value-from-rm The system could not delete the ISAM file. (S) Cancels command execution. (O) Take actions according to the error message of the rm command output together with this message.
(O) Check whether the disk has free space. Take action according to the error message of the cmp command output together with this message. KAVS1759-E Restore failed. Command ended abnormally.: command-name option : return code = return-value-from-command The system could not execute the command, so restoration failed. (S) Cancels command execution.
KAVS1773-I The adapter command unsetup completed normally. Adapter command unsetup ended normally. (S) Continues processing. KAVS1774-E The logon account does not have permission to setup. Since you do not have permission to execute the command, you cannot execute it. (S) Cancels command execution. (O) Re-execute the command as a user with permission to execute it. KAVS1775-E The argument arguments is incorrect. The command argument is invalid. (S) Cancels command execution.
You cannot perform setup and unsetup at the same time. (S) Cancels command execution. (O) Check the command arguments, and then re-execute the command. KAVS1778-E A duplicated command argument cannot be specified. You cannot specify a command argument more than once. (S) Cancels command execution. (O) Check the command arguments, and then re-execute the command. KAVS1779-E JP1/Base is not installed, so the adapter command setup failed.
(S) Cancels command execution. (O) Check whether the adapter command exists. KAVS1782-E The adapter command configuration file storage directory does not exist. The directory containing the adapter command configuration file does not exist. (S) Cancels command execution. (O) Check whether the directory containing the adapter command configuration file exists. KAVS1783-E An attempt to delete the configuration-file adapter command configuration file failed.
KAVS1786-E An unexpected error occurred. An unexpected error occurred. (S) Cancels command execution. (O) Contact the system administrator. KAVS1790-E An error occurred in the processing which acquires the process state of job execution environment. : maintenanceinformation An error occurred during the processing for acquiring the operating status of the job execution environment. (S) Cancels command execution.
• Memory became insufficient at the manager. See KAVU0966-E. • A fatal error occurred in the manager. See KAVU0968-E or KAVU4335-E. • A logical contradiction occurred in the manager. See KAVU0969-E. • That request is not supported by the requested manager. See KAVU0970-E. • The execution environment is incorrect. See KAVU0972-E. KAVS1791-E An error occurred in the processing which usually requires operation of job execution environment.
See KAVU0954-E. • Memory became insufficient at the manager. See KAVU0966-E. • A fatal error occurred in the manager. See KAVU0968-E or KAVU4335-E. • A logical contradiction occurred in the manager. See KAVU0969-E. • That request is not supported by the requested manager. See KAVU0970-E. • The execution environment is invalid. See KAVU0972-E. KAVS1801-I The queueless agent will now start. The queueless agent service starts. (S) The queueless agent service starts.
KAVS1804-I The queueless agent will now terminate. The queueless agent service accepted a request for forced termination of the ajsqlstop command. (S) Terminates the queueless agent service. KAVS1805-E The port (port-name) cannot be used because another user is already using the port. The service that output this message cannot start because the port indicated in port-name is being used. (S) Terminates the service that output this message.
(O) Use JP1/AJS3 - View to make sure that the number of queueless jobs waiting for execution for the queueless agent service has not reached the maximum number of waiting jobs. Make sure that the number of waiting queueless jobs is within the maximum, and re-execute the queueless job indicated in job-name that caused an error. The current setting of the maximum number of concurrently executable jobs and the maximum number of waiting jobs might not suit the current operation.
(O) Execute the ajsqlattach command to attach the host indicated in host-name, and then re-execute the queueless job indicated in job-name that resulted in the error. Example: In this example, the command attaches the logical host Lhost. Execute the ajsqlattach command as follows: ajsqlattach -h Lhost For details on the ajsqlattach command, see ajsqlattach in 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.
(O) Check the amount of memory available by using Task Manager in Windows or the top command or another means in UNIX. Wait until the memory necessary for job execution can be allocated, and then re-execute the queueless job indicated in job-name that resulted in the error. KAVS1812-E The configuration definition of the logical host (logical-host-name) does not exist. The environment of the logical host indicated in logical-host-name is not set up.
To identify the name of the service (process) that output this message, check the AP name that is output to the integrated trace log concurrently with this message. For details about the output content of the integrated trace log file, see 1.2.1(2) Integrated trace log in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting. KAVS1814-E The host name is invalid.
• If Permission denied is indicated in maintenance-information-1, write permission for the status file indicated in status-file-name might have been changed. Change the permission so that the user who started the queueless agent service and the OS user who executes the queueless job can write to the status file indicated in status-file-name.
• If Permission denied is indicated in maintenance-information-1, write and read permissions for the status file indicated in status-file-name might have been changed. Change the permissions so that the user who started the queueless agent service and the OS user who executes the queueless job can read and write to the status file indicated in status-file-name.
• In the DNS settings, hosts file, jp1hosts file, or jp1hosts2 file, correctly register the host name and IP address of the host that executes queueless jobs. • Use the ping command or another means to check the network status and correct the network failure. • Use Task Manger in Windows or the top command or another means in UNIX to make sure that memory is sufficient. If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.
write to the work path indicated in path-name. Then, re-execute the queueless job indicated in job-name that resulted in the error. KAVS1820-E Memory is insufficient, so the job (job-name) cannot be executed. The queueless job indicated in job-name cannot be executed because of insufficient memory. (S) Places the queueless job indicated in job-name into Failed to start status. (O) Check the amount of memory available by using Task Manager in Windows or the top command or another means in UNIX.
KAVS1823-E No access permission is granted for the file (file-name) on the transmission host (host-name), so the job (jobname) cannot be executed. The queueless job indicated in job-name cannot be executed because there is no access permission for the file indicated in file-name on the manager host indicated in host-name. (S) Places the queueless job indicated in job-name into Failed to start status. (O) A directory path name might have been specified in the file indicated in file-name.
• If any message other than the above is indicated in maintenance-information-1, correct the error according to the message. If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators). KAVS1826-E An IPC error occurred during file transmission, so the job (job-name) cannot be executed.
(O) Change the OS user who executes the queueless job indicated in job-name to a superuser, or change the execution order to 1, 2, or 3. Then, re-execute the queueless job indicated in job-name that resulted in the error. KAVS1829-E A system call (function-name) error occurred in the Queueless Agent service. : maintenance-information-1 maintenance-information-2 A system call error occurred in the queueless agent service. (S) Cancels the service startup processing or the requested processing.
• Standard input file name: 767 bytes • Standard output file name: 767 bytes • Standard error output file name: 767 bytes (S) Places the queueless job indicated in job-name into Failed to start status. (O) Edit the job definition so that the lengths of the items do not exceed their maximums after substitutions for the variables, and then re-execute the queueless job indicated in job-name that resulted in the error KAVS1831-E An attempt to attach the logical host (logical-host) has failed.
A wait for a response timed out. Possible causes are as follows: • The CPU load on the host to be connected is very high. • System resources are insufficient. (S) If the error occurred when an attempt was made to start the queueless job, the system places the queueless job indicated in job-name into Failed to start status. If the error occurred when an attempt was made to terminate the queueless job, the system places the queueless job indicated in job-name into ended abnormally status.
KAVS1834-E An error occurred in the standard output file (file-name).: maintenance-information-1 (maintenance-information-2) An error occurred during access to the standard output file. (S) Places the queueless job into Failed to start status. (O) Correct the error as follows, and then re-execute the queueless job that resulted in the error. • If No such file or directory is indicated in maintenance-information-1, the standard output file indicated in file-name does not exist.
directory path so that the mapped OS user can read and write to the standard error output file indicated in filename. Then re-execute the job. • If any message other than the above is indicated in maintenance-information-1, correct the error according to the message. If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).
(O) Correct the value set in the label indicated in environment-setting-parameter-name on the host indicated logicalhost-name. Then, for the physical host, restart the queueless agent service. For a logical host, execute the ajsqlattach command to attach the host indicated in logical-host-name. If this message appears during startup of a queueless cluster process, correct the value of the label indicated in environment-setting-parameter-name, and then restart the JP1/AJS3 service.
• If No such file or directory is indicated in maintenance-information-1, the judgment file indicated in file-name does not exist. Make sure that the judgment file indicated in file-name exists, and then re-execute the job. • If Permission denied is indicated in maintenance-information-1, an attempt to read the judgment file indicated in file-name has failed. Set appropriate permissions for the file and directory path so that the mapped OS user can read the judgment file indicated in file-name.
KAVS1842-E Job result information cannot be sent because an internal file (file-name) error occurred.: maintenanceinformation-1 (maintenance-information-2) The system could not report the contents of the result file to the manager host because an error occurred during processing of the internal file indicated in file-name that is used for execution of the queueless job. (S) Places the queueless job into Failed to start status if this message appears before the queueless job is started.
KAVS1844-E An error occurred on the remote ftp host (host-name), so the job (job-name) cannot be executed. The queueless job indicated in job-name cannot be executed due to unsuccessful file transmission from the manager host indicated in host-name to the agent host. (S) Places the queueless job indicated in job-name into Failed to start status.
(O) Recheck the job definition statement and correct the job definition. Then, execute the job. KAVS1847-W A job that was waiting for execution was forcibly terminated. This message is output when a queueless job that is waiting for execution is forcibly terminated. (S) Places the queueless job into Failed to start status. KAVS1848-W The job (job-name) was forcibly terminated. (process-ID) This message indicates that the queueless job indicated in job-name was forcibly terminated.
Examples: • In this example, the command detaches the logical host Lhost. Execute the ajsqldetach command as follows: ajsqldetach -h Lhost For details on the ajsqldetach command, see ajsqldetach in 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2. • In this example, the command attaches the logical host Lhost.
(S) Terminates the queueless file transfer service. (O) Take action according to the instructions given by the message that was output immediately before this message, and then restart the queueless file transfer service. KAVS1855-W Character code conversion failed. : maintenance-information-1 (maintenance-information-2) Character set conversion failed, causing the following problems: • Data displayed in the Execution Result Details dialog box contains unreadable characters.
An attempt to allocate shared memory or a system resource failed. If an account other than the service account is used to execute jobs, jobs that use the jp1exec command might not be able to be stopped. (S) Continues request processing. (O) If you need to stop a job that uses the jp1exec command, stop other unnecessary applications, and then restart the JP1/AJS3 Queueless Agent service. KAVS1861-E The file transmission failed.
The queueless cluster process for the logical host (logical-host-name) terminated abnormally. (S) Terminates the queueless cluster process indicated in logical-host-name. (O) The probable causes of the abnormal termination of the queueless cluster process are: • The logical host name contains more than 255 bytes. • Memory was insufficient during startup of the process. • An attempt to attach the logical host has failed. • An attempt to detach the logical host has failed.
(S) Cancels execution of the worker process for queueless file transmission. (O) Check the amount of memory available by using Task Manager in Windows or the top command or another means in UNIX. Wait until the memory necessary for file transfer can be allocated, and then re-execute the queueless job that resulted in the error. KAVS1867-E The file transmission service of the host (host-name) cannot be connected, so the job (job-name) cannot be executed.
(S) Places the queueless job indicated in job-name into Failed to start status. (O) Execute the ping and jp1ping commands to make sure that the agent host can communicate with the manager host indicated in host-name. Then, re-execute the queueless job that resulted in the error. If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).
(O) Ensure that the manager host name and IP address are set in the hosts, jp1hosts, or jp1hosts2 file or in the DNS settings so that the IP address of the manager host name indicated in host-name can be resolved on the agent host. Then, if necessary, re-execute the queueless job job-name that caused the error. If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).
• Free disk space is insufficient. • Memory is insufficient. • The file indicated by file-name does not exist. • Access permission that allows the queueless agent service account or the user executing the job to write to or read the directory is not set for the directory in which the file is to be created. • A directory having the same name as the file has already been created in the directory in which the status file is created. • The name of the file indicated by file-name has 255 or more characters.
(S) Continues startup of the queueless agent service. (O) Make sure that there is no duplicate class name for the logical host, and then restart the queueless agent service. Even if you do not restart the queueless agent service, however, the class can be used as a class for which the job is executed. KAVS1877-E Memory is insufficient, so the class (class-name) cannot be used. (logical host =logical-host) The class indicated in class-name cannot be used due to insufficient memory.
(O) Possible causes of the error in the file (file-name) are as follows: • Free disk space is insufficient. • Memory is insufficient. • There is no write permission for the directory in which the file is created. • A directory having the same name as the file has already been created in the directory in which the status file is created. • The file name (file-name) has 255 or more characters.
KAVS1882-E The user mapping definition of the JP1 user (JP1-user-name) on the host (host-name) was not found. (logical host =logical-host-name) The user mapping definition for the JP1 user indicated in JP1-user-name on the manager host indicated in host-name is not found. (S) Places the queueless job into Failed to start status.
This message is sometimes output if you register, delete, or change the password of an OS user while a job is starting or finishing. In this scenario, re-execute the job after the OS user registration, deletion, or password change operation has concluded. You can avoid this problem altogether by setting the AJSQL_GETPASSWD_FTPRETRYINTERVAL or AJSQL_GETPASSWD_AGTRETRYINTERVAL environment setting parameter. For details, see 15.2.
KAVS1887-E Invalid data was received. (IPCID= IP-address) The system received invalid data from the connection source shown in IP-address. (S) Continues processing. (O) Determine the connection source from the IP address, and check that the connection source does not have a problem. KAVS1888-E An error occurred during the reading of the passwd file.: maintenance-information-1 (maintenance-information-2) An error occurred during a read from the password file.
• If any message other than the above is indicated in maintenance-information-1, correct the error according to the message. If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators). KAVS1890-E An attempt to write to the file (file-name) failed.: maintenance-information-1 (maintenance-information-2) An attempt to write to the file indicated in file-name has failed.
The shared-memory size is invalid. (S) Terminates the queueless agent service. (O) Take either of the following actions, and then restart the queueless agent service: • Reduce the maximum number of concurrently executable jobs according to the shared memory size that is currently set. • Increase the shared memory size set in the kernel parameter according to the maximum number of concurrently executable jobs.
KAVS1896-E A log file (file-name) error occurred.: maintenance-information-1 (maintenance-information-2) An error occurred during processing required to open or write to the log file indicated in file-name. (S) • If this message is output during startup of a queueless agent service, the system continues startup of the service. However, no log data is output to the log file indicated in file-name. • If this message is output during execution of a queueless job, the system continues queueless job execution.
KAVS1898-I The connection was reset by the peer. The connection between the queueless agent service and the queueless job request process or between the queueless agent service and the queueless file transfer service was reset. (S) Continues processing. (O) If the connection was reset due to an error, a message indicating the cause of the error was output before this message. Take action according to the instructions given by that message.
KAVS1903-E The queueless job request process (scheduler-service-name:identification-number) was blocked because the maximum number of abnormally ended queueless job request abends was exceeded. Since the number of times the queueless job request process ended abnormally exceeded the threshold, the queueless job request process is blocked. (S) Blocked the queueless job request process because the threshold value was exceeded. (O) Memory may be insufficient.
(O) Correct the value of the concurrently-executable-job-limit, and then restart the scheduler service. For details on the environment setting parameters, see 2.2 Setting up the scheduler service environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2. KAVS1906-E Initialization of a queueless job request process failed.: maintenance-information The system could not initialize a queueless job request process. (S) Stops the scheduler service.
KAVS1909-E The queueless job (job-name) cannot be executed. The queueless job cannot be executed. The possible causes are: • The queueless job function has not been set up correctly. • The maximum number of concurrently-executable queueless job request processes is set to 0. (S) Sets the status of the queueless job to Failed to start. (O) Use the ajsqlsetup command to set up the queueless job execution environment, and then restart the scheduler service.
KAVS1922-W The connection with the queueless job execution agent (agent-name) was closed.: maintenance-information The connection to the queueless job execution agent was severed. (S) Reconnects the queueless job execution agent. (O) Determine the cause of the error according to the messages output by the manager and the agent. Then, take proper actions. KAVS1923-E A queueless job function cannot be used, processing to the job (job-name) cannot be performed.
(S) Stops forced termination of the job. (O) Retry forced termination of the job. KAVS1926-E A class name is specified for the execution destination host name of a Jobnet. A class name is specified as the target host name of a jobnet. (S) Places the job into Failed to start status. (O) Remove the class name specified as the target host name, from the jobnet that includes this job. KAVS1927-E The queueless job definition is invalid. The definition of the queueless job is invalid.
(S) If the message KAVS1922-W was output before this message, you need to check the status of the queueless job that was requested to be executed by the relevant agent. If the message KAVS1930-W was output, re-send the execution, forcible termination, or confirmation request that failed to be sent previously. KAVS1930-W Could not connect with the queueless job execution agent (agent-name). Reconnection processing started.
Communication with the queueless job execution agent as indicated by agent-name was not recovered, so an attempt to send the job execution request failed. (S) Terminates the job execution request, and then sets the job status to Failed to start. (O) Check the logs for the manager host and the agent host, and the network status. Remove the cause of the connection error, and then re-request the job execution if necessary.
(O) The macro variable has not been inherited from the preceding job. Recheck the jobnet definition, and then re-execute the job. KAVS1940-E An attempt to initialize the job-ID acquisition processing failed.: maintenance-information An error occurred when the job ID acquisition process was initialized. (S) Cancels the initialization of the job ID acquisition process. (O) Contact the system administrator, and determine the cause of the error according to maintenance-information.
KAVS1943-E The job-ID management file (file-name) does not exist. The job ID management file does not exist. (S) Cancels the initialization of the job ID acquisition process. (O) Use the ajsqlsetup command to re-create a job ID management file. Then, restart the scheduler service by a cold start. For details on the ajsqlsetup command, see ajsqlsetup in 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.
For details about AJSQL_CLUSTERREQ, see 2.7 Setting up the queueless job execution environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2. (O) If this message appears during command execution, correct the error and then re-execute the command. If this message is output for the queueless cluster process, correct the error and then restart the JP1/AJS3 service on the logical host that caused the error.
KAVS1955-E The specified host (host-name)has already been attached. The specified host indicated in host-name has already been attached. (S) Cancels command execution. (O) Execute the ajsqlstatus command to check the status of the host indicated in host-name. If the host indicated in host-name has been detached, execute the ajsqlattach command to attach this host. Examples: • In this example, the command outputs detailed information for the logical host Lhost.
Execute the ajsqlattach command as follows: ajsqlattach -h Lhost For details on the ajsqlattach command, see ajsqlattach in 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2. KAVS1957-E The number of simultaneous job executions is invalid. The maximum number of concurrently executable jobs is invalid. (S) Cancels command execution.
A logical-host name and a class name are not specified together. (S) Cancels command execution. (O) When you specify a logical host name in the command, specify the logical host name and a class name together, and then re-execute the command. KAVS1961-E The candidate host (host-name) is not attached. The specified logical host indicated in host-name is not attached. (S) Cancels command execution. For the queueless cluster process, the system cancels the processing to attach the logical host.
If this message is output when the queueless cluster process is being started, execute the ajsqlstatus command to make sure that the target host indicated in host-name has already been detached. Then restart the JP1/AJS3 service on the target host indicated in host-name. If this message is output when the queueless cluster process is being stopped or when the ajsqldetach command is executed, no action is required. Example: In this example, the command outputs detailed information for the logical host Lhost.
KAVS1965-I The queueless log file (file-name-before-change) has been changed to file-name-after-change. The queueless log file will be switched to a new queueless log file, because its current size has exceeded the maximum specified in an environment parameter. (S) Continues processing. (O) If necessary, back up the current queueless log file. KAVS1966-I The queueless cluster process (logical-host-name) received a forced termination request from the start daemon.
KAVS1969-I The queueless cluster process (logical-host-name) will now stop. The queueless cluster process on the logical host (logical-host-name) will now terminate. (S) Terminates the queueless cluster process indicated in logical-host-name. KAVS1970-I The queueless cluster process (logical-host-name) has ended. The queueless cluster process on the logical host (logical-host-name) has terminated. (S) Terminated the queueless cluster process indicated in logical-host-name.
KAVS1973-E The resources required for execution are insufficient, so the job (job-name) execution was not possible. The system could not execute the queueless job indicated in job-name because resources necessary for execution were insufficient. (S) Places the queueless job indicated in job-name in the Failed to start status. (O) The probable causes of the error in the queueless job indicated in job-name are: • Memory was insufficient. • The disk did not have sufficient free space.
KAVS1976-E No right is granted to access the execution file (file-name). The queueless job could not be executed because the OS user who executed the queueless job indicated in job-name did not have access permission for the executable file indicated in file-name. (S) Places the queueless job in the Failed to start status.
(O) As the host on which the job is to be executed, specify a Windows host for a PC job or specify a UNIX host for a Unix job. Then, re-execute the queueless job that resulted in the error. KAVS1980-I The detach processing for the logical host (host-name) has been changed from planned detach to forced detach. The detach processing for the logical host indicated in host-name has been changed from planned detach to forced detach. (S) Performs forced detach processing.
KAVS1984-I maintenance-information A request for submitting a queueless job was accepted. For details about maintenance information, see C.2 Log entries output by the queueless agent service in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting. (S) Continues processing. KAVS1985-E The setup of the queueless job execution environment could not be updated.
(S) Cancels command execution. (O) Check whether the OS user who executed the command has logged on as a member of the Administrators group (in Windows) or has superuser privileges (in UNIX), and has write permission for the services file. Then re-execute the command. KAVS1987-I The service (service-name) stopped. This message indicates that the system will stop the service indicated in service-name. (S) Stops the service indicated in service-name.
If the service has started, wait a while and then retry the operation. If the retry does not correct the error, contact the system administrator and collect data (see 1.2.3 To the system administrators). You can use either of the following methods to check whether the service has started: In Windows: In Control Panel or Administrative Tools, double-click Services, and check the status of the service. In UNIX: Use the ps command to make sure that the service for the process exists.
KAVS1991-E A communication timeout occurred during the communication with the service (service-name).: maintenanceinformation A communication timeout error occurred during communication with the service indicated in service-name. (S) Cancels command execution. For the queueless cluster process, the system cancels the processing to attach the logical host. Then, by default, the system continues startup processing without abnormally terminating the queueless cluster process.
If the error occurred when the queueless cluster process was being started, restart the JP1/AJS3 service. If the error occurred when the queueless cluster process was being stopped, execute the ajsqldetach command to detach the logical host that caused the error. If you cannot correct the problem by taking the above actions, contact the system administrator, and then collect data (see 1.2.3 To the system administrators).
KAVS1995-E The command ended because an attempt to get the detailed information of the queueless agent service failed. The command ended, because an attempt to acquire the detailed information for the queueless agent service has failed. (S) Cancels command execution. (O) Resolve the problem, following the instructions given in the message that was output before this one. Then, reexecute the command.
(S) Cancels the command. For the queueless cluster process, the system cancels the processing to attach the logical host. Then, by default, the system continues startup processing without abnormally terminating the queueless cluster process. If you want to abnormally terminate the queueless cluster process, specify error for the AJSQL_CLUSTERREQ environment setting parameter. For details about AJSQL_CLUSTERREQ, see 2.
KAVS2030-I Scheduler service (logical-host-name:scheduler-service-name) export started. Export of the scheduler service will now start. (S) Continues processing. KAVS2031-I Scheduler service (logical-host-name:scheduler-service-name) export ended normally. Export of the scheduler service terminated normally. (S) Continues processing. KAVS2032-E Scheduler service (logical-host-name:scheduler-service-name) export ended abnormally. maintenanceinformation Export of the scheduler service terminated abnormally.
KAVS2035-W Scheduler service (logical-host-name : scheduler-service-name) import ended with warning. maintenanceinformation Import of the scheduler service terminated with warning. (S) Continues processing even though some information cannot be transferred. (O) Take action according to the message that was output before or after this error message. KAVS2036-E Scheduler service (logical-host-name : scheduler-service-name) import ended abnormally.
Import of the table will now start. (S) Continues processing. KAVS2040-I Table (table-name) import ended. Import of the table terminated. (S) Continues processing. KAVS2041-E Environment setting parameters could not be obtained. maintenance-information The environment setting parameters cannot be obtained. (S) Cancels processing. (O) Correct the error in the environment settings according to the message that was output before or after this error message, and then re-execute the command.
KAVS2060-E Embedded DB operation failed. (setup-identifier)(host-name) The database management process was unable to perform an embedded database operation. (S) Terminates processing. (O) The probable causes are below. Take action according to the cause of the error. Cause 1 The JP1/AJS3 service was started while the JP1/AJS3 Database service was being stopped. Action If you are performing JP1/AJS3 Database service operations manually, stop the JP1/AJS3 Database service, and then start the JP1/AJS3 service.
Action Take action as described in 2.8 Troubleshooting problems related to the embedded database in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting. If you cannot correct the problem, collect data and then contact the system administrator (see 1.2.3 To the system administrators). KAVS2101-E Embedded service is inactive. The embedded database is not running. (S) Cancels command execution. (O) Make sure that the embedded database has started.
KAVS2104-E Embedded service is not set up. The embedded database has not been set up. Either the embedded database has not been set as the scheduler service database, or the setup ID specified in -id is invalid. (S) Cancels command execution. (O) Check whether the value of the setup ID specified in -id is correct. Alternatively, use the ajsstatus command to check whether the embedded database has been set as the scheduler service database.
A reloading attempt failed. This message appears when the embedded database does not have sufficient space during execution of the ajsembdbrorg -k reld command. (S) Cancels command execution. (O) Execute the ajsembdbstatus -s prc command to make sure that the command you executed has stopped, and then retry. When unloaded data is reloaded, the embedded database allocates the space required for the operation, sometimes resulting in a shortage of free space in the area that was used before unloading.
(S) Cancels command execution. (O) Use the ajsstatus command to check whether the embedded database is set as the scheduler service database. If the embedded database is set as the scheduler service database, check whether the setup ID has been set. If the setup ID is not set correctly, use the jbssetcnf command to set it. KAVS2114-E Cannot create directory or file (directory-name or file-name). An attempt to create a directory or file has failed because you do not have permissions for the directory.
The specified option contains an error. One of the following is indicated in detailed-information: • Options (option) are needed. The mandatory or necessary option was not found. • Illegal option (option) exists. An invalid option is specified. • Extra option (option) exist. An extra option is specified. • Invalid value for option (option). The value of the option is invalid. If -F is indicated in (option), the logical host specified for the -mh option might be invalid.
For operations performed by an AJS administrator, permissions for the specified directory or file might be insufficient. Check the access permissions for the specified directory or file. For details about required permissions, see C.2 Access permissions for directories or files required for command operations by the AJS administrator in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1, or B.
KAVS2121-E Database file already exists. The file name of the file for the database area you attempted to create already exists. The file name already exists in the directory specified in the -d option of the ajsembdbaddlog or ajsembdbaddarea command. (S) Cancels command execution. (O) Re-execute the command. KAVS2122-E A temporary file already exists. A temporary file that has the same name as the file that you attempted to create by using the embedded database operation command already exists.
and then execute the ajsembdbbuild command. For details about the error messages and the applicable actions, see Actions to be taken if an error occurs in the ajsembdbbuild in 2. Commands Used during Setup in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2. KAVS2125-E Cannot create directory or file. The directory or file cannot be created because, for example, you do not have access permission for the embedded database practical directory.
KAVS2128-E Failed to set up embedded service. : func code=function-code error code=error-code An attempt to set up the embedded database has failed. (S) Terminates processing. (O) If an attempt to install JP1/AJS3 has failed, take the following action, and then uninstall JP1/AJS3 and install it again. If an attempt to uninstall JP1/AJS3 has failed, take the following action, and then uninstall JP1/AJS3 again.
• jajs_setup command • jajs_setup_cluster command • ajsembdbuninstl command In this case, take appropriate action for the message output to the standard output according to the action to be taken when an error occurs in each command. KAVS2129-I The Embedded DB configuration file does not exist. The embedded database configuration file does not exist. (S) Cancels command execution.
(S) Terminates setup processing. (O) Memory or free space on the disk may be insufficient. Terminate unnecessary applications or delete unnecessary files to make more free space available. Then re-execute the setup command. KAVS3401-I An error occurred while deleting the JP1/AJS2 Check Manager service. : code=return-value api=API-name err=API-return-value An error occurred while the JP1/AJS3 Check Manager service was being deleted. (S) Terminates setup processing.
(O) Memory or free space on the disk may be insufficient. Terminate unnecessary applications or delete unnecessary files to make more free space available. Then re-execute the setup command. KAVS3405-I An error occurred while deleting the JP1/AJS2 Check Agent service. : code=return-value api=API-name err=APIreturn-value An error occurred while the JP1/AJS3 Check Agent service was being deleted. (S) Terminates setup processing. (O) Memory or free space on the disk may be insufficient.
KAVS3409-I An attempt to connect to the Check Agent service (agent-name) has failed. : maintenance-information An attempt to connect the check agent service has failed. (S) Assumes the pre-checking of definitions for the agent to be an error, and continues processing for other check agent services. (O) Make sure that the check agent service has started normally on the agent where the error occurred, and then precheck the definitions again.
(O) Delete the specified host name, scheduler service name, and execution ID, and then re-execute the command. KAVS3413-I An attempt to connect to the check manager service has failed. : maintenance-information An attempt to connect to the check manager service has failed. (S) Cancels execution of the command. (O) Make sure the check manager service is running normally, and then pre-check the definitions again. KAVS3414-I The Check Agent ended abnormally. The check agent service terminated abnormally.
(O) Set up the environment for the logical host indicated in logical-host-name, and then restart the check agent service. If the error occurred during execution of a command, make sure that the correct logical host name is specified in the argument. KAVS3417-I An error occurred during an attempt to acquire the configuration definition of the logical host (logical-host).
KAVS3420-I Too many processes exist, so the job (job-name) cannot be checked. The job indicated in job-name cannot be checked because there are too many processes. (S) Cancels checking of the job. (O) Wait until the number of processes decreases so that the check is available, and then pre-check the definitions again. KAVS3421-I The shared memory size is invalid. (size=size) The size of shared memory is invalid. (S) Terminates the check agent service.
KAVS3424-I The setup of the function for pre-checking definitions execution environment could not be updated. : maintenanceinformation-1 maintenance-information-2 maintenance-information-3 The execution environment settings for the definition pre-check function could not be updated because the ajschksetup command failed. (S) Cancels execution of the command. (O) The setup environment may be invalid. Make sure that the setup of JP1/AJS3 has been completed normally, and then re-execute the command.
(O) Take action according to the instructions given by the message that was output immediately before this message. If a message beginning with KAVS34 that indicates the cause of the error was not output immediately before this message, contact the system administrator, and then collect data (see 1.2.3 To the system administrators). KAVS3428-I Failed in the request transmission of the definition check function in JP1/AJS2 Check Agent(agentname).
(O) Set the value in the environment setting parameter correctly, and then restart JP1/AJS3 Check Manager or JP1/AJS3 Check Agent. KAVS3431-I The definitioncheck function error detected while processing process-name. (maintenance-information-1, maintenance-information-2) An error occurred during processing of the definition pre-check function. (S) Continues processing.
KAVS3433-I Processing is cancelled due to failure to acquire agent information by using the function for pre-checking definitions. : host-name maintenance-information-1 maintenance-information-2 maintenance-information-3 Processing is canceled because an attempt to acquire agent information by using the definition pre-check function has failed. The probable causes are: • The JP1/AJS3 service is not running on the host indicated in host-name.
KAVS3436-I An attempt to read the operation profile(profile-name) failed. The system could not load the operation profile specified at command execution or assigned to the scheduler service into memory. (S) Cancels processing. (O) Review the number of work tasks assigned to the operation profile. KAVS3437-I The operation profile contains no valid information.
(O) To configure a new logical host to operate as the main site in disaster recovery mode, execute the jajs_rpsite command with the -m SET option specified. If the shared disk of the logical host is not mounted, mount it and then re-execute the command. Depending on the hardware, you might be unable to mount the disk at the remote site while the disk copy and mirroring functions are being used. See the documentation for your hardware to find out whether this is possible.
(S) Terminates command execution. KAVS3709-I The logical host being used as the main site has been removed. (host: host-name) A message indicating that a logical host used as the main site has been deleted. (S) Terminates command execution. KAVS3750-E Export processing ended abnormally. : maintenance-information The export process failed. (S) Cancels execution of the command. (O) If an error message was output before or after this message, take action according to the contents of the error message.
(S) Waits for a response. (O) To delete the logical host settings and proceed with the import process, press Y. To cancel the import process, press N. KAVS3753-E Cannot operate - JP1/AJS3 service has not stopped. The operation cannot be performed because JP1/AJS3 has not completely stopped. (S) Cancels execution of the command. (O) The probable causes are as follows. Take the appropriate action depending on the cause.
(S) Cancels execution of the command. (O) You cannot specify the following characters in command arguments: • In Windows ^ & = ! @ ~ % " < > | , ; * ? • In UNIX ^ & = ! @ ~ % " < > | , ; * ? \ ' $ Specify the correct character and then re-execute the command. KAVS3756-E Contradiction between environment setting parameters and real environment. An environment setting parameter conflicts with the actual operating environment. (S) Cancels execution of the command.
• The file or directory cannot be created If you specified the -ld option for the ajsembdbbuild command in the exported environment, make sure that the directory can be created with the same path when imported into the target environment. After resolving the problem, execute the command again. KAVS3780-I Export processing has started. The export process has started. (S) Begins command execution. KAVS3781-I Import processing has started. The import process has started. (S) Begins command execution.
Command execution has been canceled. (S) Ends command execution. KAVS3800-E EmbedDB export processing ended abnormally. : maintenance-information An error occurred when exporting the embedded database. (S) Cancels execution of the command. (O) If an error message was output before or after this message, take action according to the contents of the error message. If you cannot determine the cause of the error, collect data and then contact the system administrator (see 1.2.3 To the system administrators).
KAVS3803-E EmbedDB service is not installed. The embedded database is not installed. (S) Cancels execution of the command.
Create the directory after checking the path you specified in the -bl option when executing the ajsembdbbuild command. If you do not create this directory, the message KFPS01150-E is output to the Windows event log or syslog when the embedded database starts. The database will go down if the system runs out of space for embedded database logs before the directory can be created. KAVS3850-I EmbedDB export processing has started. The process of exporting the embedded database configuration has started.
KAVS3910-E Interprocess communication failed. : maintenance-information-1 maintenance-information-2 maintenanceinformation-3 Interprocess communication failed. (S) Connects to the JP1/Base event service the next time that an event is output (if yes is specified in the COMMANDEVENT environment setting parameter). (O) Determine the cause of the error, and then re-execute the command. If the JP1/Base event service has stopped, start it. If a message Failed to put Event.
(O) Determine the cause of the error from the error message that was output before this message, and correct the cause of the error. Then specify the unit indicated in unit-name and retry. KAVS4201-E Failed to save the macro variable specified during jobnet (jobnet-name) execution registration. Execution registration cancelled.
KAVS4203-E Deletion of an unnecessary macro variable failed during creating a generation of jobnet (jobnet-name). Generation creation (execution-ID) is canceled. : maintenance-information-1 maintenance-information-2 The system cancels creation of a new generation because an attempt to delete an unnecessary macro variable file or record failed during creation of the new generation of the jobnet. (S) Cancels processing.
An error occurred during restructuring of a file, such as the standard error output file under the job information storage folder, for one of the following reasons: • You do not have update permission for the job information storage folder and the files in that folder. • The file system does not have sufficient free space. (S) Continues processing. (O) If this error message appears, the following may occur. • After operation starts, a job using a queue terminates abnormally.
• The unit containing the execution order control information is created in a unit that is not either of the following: - A planning group - A root jobnet (except for a root jobnet under a planning group) • Although a root jobnet or planning group is specified so that connection with a jobnet connector is not established, one of the following information items is specified: - A value is specified for Jobnet Connector. - Synchro is specified for Exec. order method.
KAVS4608-E Cannot delete the unit(unit-name) - jobnet connector exist. When you delete the registered unit information, a unit that contains a jobnet connector cannot be deleted. To delete the jobnet connector and the unit that contains the jobnet connector, first unregister the unit. (S) Cancels command execution. (O) Check the registration status of the unit, and then re-execute the command. KAVS4609-E Cannot copy the unit(unit-name) - jobnet connector exist.
(S) Cancels command execution. (O) Check the registration status of the unit, and then re-execute the command. KAVS4612-E Jobnet connector(unit-name) can only be copy into jobnet. You cannot copy a jobnet connector into a unit other than a jobnet. (S) Cancels command execution. (O) Check the copy destination of the unit, and then re-execute the command. KAVS4613-E Jobnet connector(unit-name) can only be move into jobnet. You cannot move a jobnet connector into a unit other than a jobnet.
(S) Terminates processing. However, if multiple units are specified, the system continues processing of other units. (O) Change the unit configuration, and then re-execute the command. KAVS4616-E Cannot operate - Jobnet connector exist in the jobnet for the connection destination. : unit-name Operation is impossible because a jobnet connector is defined in the connection-destination jobnet. (S) Terminates processing. However, if multiple units are specified, the system continues processing of other units.
(S) Terminates processing. However, if multiple units are specified, the system continues processing of other units. (O) Change the unit configuration, and then re-execute the command. KAVS4620-E Cannot operate - Root remote jobnet exist in the planning group for the connection destination. : unit-name Operation is impossible because a jobnet connector is defined in the connection-destination planning group. (S) Terminates processing.
KAVS4625-E The type cannot be specified for the release target jobnet. : maintenance-information Specification of the release target jobnet contains an error. The type of the unit specified as the release source or release target might be one of the following: 1. Other than a root jobnet 2. Remote jobnet 3. Recovery jobnet 4. Manager jobnet 5. Root jobnet in a planning group (S) Cancels command execution. (O) Check the release target jobnet, and then re-execute the command.
KAVS4628-E The state of release wait, delete wait, or release entry wait does not exist. : unit-name An attempt was made to cancel the release of a jobnet definition whose status was not Release wait, Delete wait, or Release entry wait. (S) Cancels command execution. (O) Check the unit for which you want to cancel the release, and then re-execute the command. KAVS4629-E The type cannot be specified for the release source jobnet.
KAVS4631-W The jobnet definition for the applied where the generation did not exist could not be deleted. Release entry terminated normally, but a jobnet definition that had no generation and whose status was Applied could not be deleted. (S) Continues processing. The jobnet definition in Applied status remains in the database. (O) The jobnet definition in Applied status that could not be deleted will be deleted automatically when release entry is performed next time.
(S) Cancels command execution. (O) Make sure that a jobnet definition whose status is Being applied exists, and then re-execute the command. KAVS4635-E Cannot operate - Outside the release period. Operation that extends beyond the release date cannot be performed. (S) Cancels command execution. (O) Check the release date of the target unit, and then re-execute the command. KAVS4636-E Cannot operate - A remote jobnet exists in the specified unit.
Operation is impossible because a jobnet with start conditions is specified as the connection-destination jobnet for the release target or release source jobnet. (S) Cancels command execution. (O) Check the definition of the release target or release source jobnet, and then re-execute the command. KAVS4640-E Cannot operate - A jobnet connector exists in the specified jobnet for the connection destination.
KAVS4646-E An unnecessary jobnet was defined. Resolve the problem, cancel the release, and then entry the release again. An unnecessary jobnet definition was created. After correcting the problem, cancel the release and then perform the release entry again. (S) Cancels command execution. (O) Take action according to the instructions given by the message that was output immediately before this message.
(O) Check whether the scheduler service is running. After checking the cause of the error, retry the operation. KAVS4650-E Cannot operate - Jobnet has been shutdown. The status of the specified jobnet is Shutdown. The probable causes are: • The unit defined in the calendar to be referenced does not exist. • The unit defined in the exclusive schedule does not exist. (S) Cancels processing. (O) Unregister the jobnet in Shutdown status, review the schedule definition, and then retry the operation.
Another user is using the unit. (S) Cancels processing. (O) Wait until the other user ends the use of the unit, and then retry the operation. KAVS4656-E No authority for Unit. You do not have authority for the unit. (S) Cancels processing. (O) Execute the command as a user who has the required authority for the unit. KAVS4657-E A unit type that cannot be added is specified in the jobnet where release entry is complete. A unit type that cannot be added to a jobnet entered for release is specified.
• The specified unit whose end is being waited for was deleted from the wait condition definition while the command was executing • No unit names match the regular expression (S) Cancels command execution. If you specify multiple units (including by regular expression), the system continues processing from the next unit. (O) Check the unit whose end is being waited for and then re-execute the command. KAVS4661-E This option (option) cannot be used because the preceding unit wait function is not enabled.
(S) Cancels command execution. If you specify multiple units (including by regular expression), the system continues processing from the next unit. (O) Specify a unit for which a temporary change has been executed, or change the start date to a date before temporary changes were made. Then, re-execute the command. KAVS4671-E Information about temporary change operations for the unit (unit-name) could not be saved.
Temporary change information could not be deleted. (S) Cancels the deletion of temporary change information and continues processing. (O) The internal files remain on the disk until you re-register the jobnet for execution, or perform a cold start of the scheduler service. KAVS4674-E The command cannot be executed because the operation management function for temporary changes is not enabled. The command could not be executed because the function for managing temporary changes is not enabled.
KAVS4677-E An error that cannot be recoverd by retry execution occurred.(name: job-name: execution-ID, code: return-code, host: host-name, JOBID: job-number, retry:number-of-retry-executions, cause code: cause-code) A job that was specified to be retried if it ended abnormally terminated, because retrying was not possible. For details, see cause-code. The following explains the cause codes: FATALERR The job terminated in an end status that does not allow a retry.
KAVS4700-E The jobnet connector (jobnet-name:execution-ID) ended abnormally because it failed to connect to the connection destination jobnet. The jobnet connector cannot be executed because an attempt to connect to the connection-destination jobnet has failed. (S) Places the jobnet connector into Ended abnormally status.
The jobnet connector cannot be executed because the specified connection-destination jobnet is invalid. The probable causes are: • The unit specified for the connection-destination jobnet does not exist. • The type of the unit specified for the connection-destination jobnet is invalid. (S) Places the jobnet connector into Ended abnormally status. (O) Correct the error, and then re-execute the jobnet connector.
• The unit specified for the jobnet connector does not exist. • The type of the unit specified for the jobnet connector is invalid. (S) Places the connection-destination jobnet into Ended abnormally status. (O) Correct the error, and then re-execute the connection-destination jobnet. KAVS4707-E Cannot execute the jobnet for the connection destination(jobnet-name) because the jobnet connector is not defined to connect.
• The RJCUSE environment setting parameter is not set to yes. • The scheduler service inter-communication control process has stopped. The jobnet connector or connection-destination root jobnet for which execution was attempted terminates abnormally after a KAVS4701-E or KAVS4700-E message is output, respectively. (S) Places the connection-destination jobnet into Ended abnormally status. (O) Check the value of the RJCUSE environment setting parameter.
KAVS4713-E Cannot execute the jobnet connector (jobnet-name) because the connection range of the jobnet of the connection destination is invalid. The jobnet connector cannot be executed because the connection range specified for the connection-destination jobnet is invalid. The probable cause is: • The connection range specified for the connection-destination jobnet does not match the connection range for the jobnet connector. (S) Places the jobnet connector into Ended abnormally status.
KAVS4716-E Cannot execute the jobnet of the connection destination (jobnet-name) because the connection range of the jobnet connector is invalid. The connection-destination jobnet cannot be executed because the connection range specified for the jobnet connector is invalid. The probable cause is: • The connection range specified for the jobnet connector is different from the connection range for the connectiondestination jobnet. (S) Places the connection-destination jobnet into Ended abnormally status.
KAVS4722-I Reconnection processing with the process controlling communication between scheduler services started. (scheduler-service-name) Reconnection processing with the scheduler service inter-communication control process will now start. (S) Starts the reconnection processing with the scheduler service inter-communication control process. KAVS4723-I Reconnect to the process has finished. (scheduler-service-name) The scheduler service inter-communication control process is reconnected.
• The number of connections that the scheduler service inter-communication control process uses for communication has exceeded the maximum. • The scheduler service inter-communication control process failed to resolve the host name. • The scheduler service specified for the connection service name for the jobnet connector or connection-destination jobnet is not running.
KAVS4732-E Cannot execute the jobnet (jobnet-name) of the connection destination because it failed to resolved to the local host name (host:host-name). The connection-destination jobnet cannot be executed because an attempt to resolve the local host name has failed. (S) Places the connection-destination jobnet into Ended abnormally status. (O) Confirm that the name of the host for which the jobnet has been defined is set correctly in the hosts, jp1hosts, and jp1hosts2 files.
(O) If the status of the jobnet definition that has the release ID indicated in release-ID is Release wait, follow the procedure below: 1. Unregister the jobnet indicated in unit-name. 2. Cancel the release for the jobnet indicated in unit-name. 3. Correct the error in the schedule definition. 4. Enter the corrected jobnet definition for release again for the jobnet indicated in unit-name.
If the message appears when one of the following operations is performed, take appropriate action as shown below. • If the message appears during release entry for the jobnet indicated in the message, cancel the execution registration of the jobnet, cancel the release, and then perform the release entry again. After the release entry is performed, re-register the jobnet for execution.
(O) Check the user who executes the command, and then execute the command. If multiple users have registered the root jobnet for fixed execution, only a user who has logged on as a member of the Administrators group (in Windows) or has superuser privileges (in UNIX) can perform the import.
(S) Cancels processing for the file in which the error occurred, and then terminates the command. (O) Take action as shown below. In Windows: See the Windows event log and take action according to the output message. If you cannot take corrective action, contact the system administrator. In UNIX: See the syslog and take action according to the output message. If you cannot take corrective action, contact the system administrator. KAVS4829-E Specified file name (file-name) is too long.
(O) Take action according to the instructions given by the error message that was output before this message. See the output command line and take corrective action for the problem. Then re-execute the command. KAVS4833-I Information that is temporarily changed in the plan for the unit (unit-name) is not exported. A unit in which changes were made by using Change Plan is exported. The information that is changed by using Change Plan is not exported. (S) Continues the command.
KAVS4836-E The specified unit (unit-name) can not be exported either because it does not exist or execution registration has not been performed. The unit could not be exported. The probable causes are: • A unit that does not exist is to be exported. • A unit other than a root jobnet is to be exported. (S) Continues the command. (O) The specified unit does not exist or is not registered for execution. Check the status of the unit, and then re-execute the command.
(S) Continues the command. (O) Specify a root jobnet that has a scheduled generation. KAVS4900-I The process controlling communication between scheduler services has started. This message reports that the scheduler service inter-communication control process has started. (S) Continues processing. KAVS4901-I The process controlling communication between scheduler services has terminated. This message reports that the scheduler service inter-communication control process has terminated.
KAVS4904-I The management process for the process controlling communication between scheduler services has terminated. This message reports that the management process for the scheduler service inter-communication control process has terminated. (S) Continues processing. KAVS4905-E The management process for the process controlling communication between scheduler services has terminated abnormally (maintenance-information).
(S) Continues processing. Note that you cannot use the execution order control for root jobnets between processing scheduler services until the number of connections has dropped below the maximum. Also note that either of the following occurs until a KAVS4918-I message is output. • The connection-destination jobnet for which Synchro is specified for Exec. order method is placed into Ended abnormally status. • The jobnet connector is placed into Ended abnormally status.
(O) Take action according to the Windows event log or syslog message that was output immediately before this message. If no such message was output, check whether the scheduler service inter-communication control process indicated in the message is running. If you cannot correct the problem, contact the system administrator, and collect data (see 1.2.3 To the system administrators).
(S) Terminates communication. (O) Check the environment for communication with the process. KAVS4913-E The port number could not be obtained. Confirm whether the service name is defined correctly. An attempt to acquire the port number used by the scheduler service inter-communication control process has failed (S) Terminates the scheduler service inter-communication control process. (O) Check whether the service name and the port number for jp1ajs2gw are set correctly in the services file.
(S) Restarts the scheduler service inter-communication control process. KAVS4916-W The process (host:host-name) controlling communication between scheduler services failed to start (maintenanceinformation). An attempt to start the scheduler service inter-communication control process has failed. A probable cause is insufficient system resources. (S) Terminates the scheduler service inter-communication control process.
Because the number of connections for the scheduler service inter-communication control process is below the maximum value, execution order control for root jobnets between different scheduler services is now possible. (S) Continues processing. KAVS4931-I The TCP/IP port number is not set, because the AJS administrator executed this command. Set TCP/IP port number. : command-name The TCP/IP port number was not set because the AJS administrator executed the indicated command.
Setup of the AJS administrator will now start. (S) Continues installation. KAVS4934-E The AJS administrator name is invalid. The AJS administrator name specified in the JP1AJS3_ADMINUSR_NAME environment variable is invalid. (S) Cancels installation. (O) Specify the correct AJS administrator name for the JP1AJS3_ADMINUSR_NAME environment variable, and then retry the installation. KAVS4935-E The JP1 administrators group is not set up. The JP1 administrators group has not been set up.
(S) Cancels installation. (O) Specify an existing OS user as an AJS administrator, and then retry the installation. KAVS4938-E The AJS administrator cannot specify the OS user of a primary group that is not the JP1 administrators group. An OS user whose primary group is not the JP1 administrators group is specified as an AJS administrator. (S) Cancels installation. (O) Change the primary group of the OS user specified as an AJS administrator to the JP1 administrators group, and then retry installation.
• The user is neither an AJS administrator nor a superuser. • The JP1 administrators group name was changed. • The OS user specified as the AJS administrator was deleted. • The primary group name of the OS user specified as the AJS administrator was changed. (S) Cancels the command. (O) Configure the execution permission environment correctly, and then re-execute the operation. KAVS4944-E Failed to set the AJS administrator.
KAVS4952-E Waiting for the end of the preceding unit (name: unit-full-name:execution-ID) was not possible because an error occurred. : maintenance-information-1 maintenance-information-2 maintenance-information-3 maintenanceinformation-4 The unit with wait conditions indicated in the message could not wait for the unit whose end is being waited for because an error occurred.
KAVS4955-I The wait conditions for the jobnet (name: unit-full-name:execution-ID) were approved. (approval factor: approvalfactor) The wait conditions for the jobnet indicated in the message have been satisfied. The execution ID is output if yes is specified for the LOGINFOALL environment setting parameter. Approval factor: 1 The wait condition was satisfied according to the AND wait method. Approval factor: 2 The wait condition was satisfied according to the OR wait method.
The message outputs the execution ID of the jobnet that cannot finish waiting if yes is specified for the LOGINFOALL environment setting parameter. (S) Continues processing. (O) Take action according to the cause number output in the message. The appropriate action for each cause number is as follows: Cause number: 1 The wait condition (wait method AND) was not satisfied because the status of the unit whose end is being waited for indicated in the message does not allow the wait condition to be satisfied.
to save one day's worth of execution results for the unit with wait conditions and the unit whose end is being waited for. If you cannot take this approach, perform a temporary change operation to disable waiting for the unit to be waited for indicated in the message. For this cause, asterisks (***) appear as the execution ID of the unit in the message whose end is being waited for.
(S) Cancels processing. (O) Take action according to the cause number output in the message. The appropriate action for each cause number is as follows: Cause number: 1 The unit whose end is being waited for indicated in the message cannot be waited for. Determine the cause from the error message output before this one, and remove the cause of the error. Then, perform the following procedure: 1. Check the execution start date of the unit whose end is being waited for indicated in the message. 2.
KAVS4971-E A job (name: unit-full-name:execution-ID) cannot finish waiting because the unit whose end is to be waited for (name: unit-full-name:execution-ID) is in a state for which waiting is not possible. (cause number: cause-number) The status of the unit whose end is being waited for has prevented the job with wait conditions indicated in the message from finishing the waiting process.
3. The number of saved generations of the unit with wait conditions, the unit whose end is being waited for, or both is not sufficient to save the execution results from one day of operation. Add an execution schedule that satisfies the waiting rule to the unit whose end is being waited for indicated in the message. Alternatively, in the case of 3. above, the system might have been unable to obtain generation information because generations were being deleted.
KAVS4975-E The preceding unit wait function cannot be used (scheduler-service-name). : maintenance-information-1 maintenance-information-2 maintenance-information-3 maintenance-information-4 A unit assigned a wait condition cannot be executed. The probable causes are as follows: • The JP1/AJS3 database uses a compatible ISAM configuration • yes is not set for the PREWAITUSE environment setting parameter Each unit you attempted to execute ends abnormally with the message KAVS4952-E.
(O) The unit with wait conditions is an invalid type. For details about which units are capable of accepting wait conditions, see 2.2.5(1)(a) Units with wait conditions and units whose ends are being waited for in the Job Management Partner 1/Automatic Job Management System 3 System Design (Work Tasks) Guide. KAVS8001-I The operation profile function was enabled. :maintenance-information An operation profile was applied to a scheduler service. (S) Continues processing.
(S) Cancels processing. (O) Review the contents of the operation profile, and apply it again. You can apply an operation profile by the following: • Executing the ajsprofalter command • Restarting the scheduler service to which the operation profile is to be applied • Restarting the JP1/AJS3 service KAVS8005-I The operation profile function was disabled. :maintenance-information-1 maintenance-information-2 The operation profile of a scheduler service was disabled. (S) Continues processing.
KAVS8008-E You do not have the permissions required to use the operation profile. :maintenance-information You do not have access permission for the operation profile. (S) Terminates command processing. (O) Grant access permission for the operation profile and then re-execute the command. KAVS8009-E The operation profile cannot be opened. :maintenance-information-1 maintenance-information-2 maintenanceinformation-3 An I/O error occurred with respect to the operation profile.
(S) Terminates command processing. (O) Check the value specified for the UNITPROFMEMSIZE or AGENTPROFMEMSIZE environment setting parameters, and then re-execute the command. For details about the environment setting parameters, see 2.2 Setting up the scheduler service environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2. KAVS8012-E Exclude error occurred.
DBERR: Take action according to the message beginning with KAVS that was output immediately before this message. LOCKERR: Check for disk failures or other problems on the disk where the execution agent profile is located. SHMERR: Review the shared memory size set in the kernel parameter. MEMERR: Make sure that sufficient memory is available. See the Release Notes for details about the amount of memory required. SYSERR: Contact the system administrator and collect data.
The line in the operation profile indicated by line-number is invalid. The probable cause is as follows: • The operation profile contains an error in a line that is not commented or blank. (S) Cancels processing. (O) Take action according to the message KAVS8004-E together with this message. KAVS8016-E The same setting is in multiple lines. Line=line-number The line in the operation profile indicated by line-number is invalid.
The line in the operation profile indicated by line-number is invalid. The probable causes are as follows: For an execution agent profile: • The profile does not begin with a @SYS_RESTRICT_START line For a unit attribute profile: • The profile does not begin with a @SYS_PROFILE_START line (S) Cancels processing. (O) Take action according to the message KAVS8004-E together with this message. KAVS8019-E The description is insufficient.
For an execution agent profile: • One or more of the following entries is in the wrong location: @SYS_RESTRICT_START unit_path View ViewCheckLevel JobExec @SYS_AGENTLIST_START @SYS_AGENTLIST_END For a unit attribute profile: • One or more of the following entries is in the wrong location: @SYS_PROFILE_START unit_path InheritUnitAttr FixedExecUser (S) Cancels processing. (O) Take action according to the message KAVS8004-E together with this message. KAVS8021-E The value is invalid.
(O) Take action according to the message KAVS8004-E together with this message. KAVS8022-E The specified of the executing agent exceeds the maximum. Line=line-number The line in the operation profile indicated by line-number is invalid. The probable cause is as follows: • More than 2,048 permitted execution hosts are specified. (S) Cancels processing. (O) Take action according to the message KAVS8004-E together with this message. KAVS8023-E There is no valid executing agent.
(O) Check and, if necessary, revise the contents of the connection permission configuration file and then execute the jajs_pmtcon command. For details about the connection permission configuration file, see 4.4 Settings for restricting connections to JP1/AJS3 in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows), or 14.
An error occurred during the processing of the connection source restriction function. The nature of the error is indicated as follows in cause-code: • LOCKERR: An error relating to internal locking occurred. • FILEERR: A file access error occurred. • IPERR: An attempt to acquire an IP address failed. • SHMERR: An error relating to shared memory access occurred. • MEMERR: There is insufficient memory. • SYSERR: A conflict occurred in the internal logic of JP1/AJS3.
KAVS8034-E The connection permitted hosts list cannot be refreshed because the connection source restriction function is disabled. The list of hosts permitted to connect cannot be updated because the connection source restriction function is disabled. The probable causes are: • The connection source restriction function was not set.
(S) Continues processing. (O) Check and, if necessary, revise the contents of the connection permission configuration file, and then re-execute the command. For details about the connection permission configuration file, see 4.4 Settings for restricting connections to JP1/AJS3 in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows), or 14.
2. Execute the jajs_pmtcon command to apply the change to the connection permission configuration file. 3. If necessary, perform the request processing again. - If reason is Error: Follow the instructions given by the KAVS8033-E message that was output immediately before this message. KAVS8040-E The request sent from the host(connection-source-IP-address) was ignored. (reason, host-name) A request from the host (connection-source-IP-address) was ignored.
2.4 Messages beginning with KAVT (Messages about the event/action control) This section lists the messages that begin with KAVT (Messages about the event/action control). KAVT0001-I Event Action Manager will now start.(maintenance-information) The event/action control manager starts. (S) Continues processing. KAVT0002-I Finish Event Action Manager.(maintenance-information) The event/action control manager has terminated. (S) Terminates the event/action control manager.
• Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group. • Check whether the contents of the environment settings are correct. In particular, check whether the name of the directory for output of the wait information file is set correctly. After correcting any errors, stop the JP1/AJS3 service and then restart it. KAVT0009-E Failed to initialize socket.
An error occurred while event job monitoring was starting. (S) Terminates the event job in the Failed to start status. (O) Check the following, and then use the ajsname command with the -I option to identify the job name from the unit ID. Retry operation on the identified event job: • Check whether the system resources are sufficient. Especially, check whether there is sufficient space on the disk that contains the directory for output of the wait information file.
KAVT0027-E The cold start processing failed. (maintenance-information) An attempt to perform a cold start on the event/action control manager has failed. (S) Starts the event/action control manager while some of the event jobs being monitored are still running. (O) Check the following, and then re-execute the cold start: • Check whether the system resources are sufficient. • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.
(O) Check the following, and then use the ajsname command with the -I option to identify the job name from the unit ID. Make sure that the status of the identified event job has not changed, and then use the ajschgstat command or the Change Job Status dialog box to change the status of the event job: • Check whether the system resources are sufficient. • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.
KAVT0045-E The icon will now end because an error occurred. An error occurred during the start of an event. (S) Continues processing. (O) The error is caused by an internal factor of the event/action control. Contact the system administrator and collect data (see 1.2.3 To the system administrators). KAVT0058-E An error occurred during processing of the request to monitor the start condition.
KAVT0062-E An error occurred during processing of the request to end start-condition monitoring. (maintenance-information) (AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID, maintenance-information) An error occurred during the termination of monitoring the start condition. (S) Cancels the forced termination of the jobnet with start conditions, and continues processing.
Output to the macro variable storage file failed. (S) Continues processing. (O) Check the following, and then use the ajsname command with the -I option to identify the unit name from the unit ID: • Check whether the system resources are sufficient. • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group. • Check whether the directory created during installation of JP1/AJS3 was deleted inadvertently.
• Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group. • Check whether the directory created during installation of JP1/AJS3 was deleted inadvertently. • Check whether the target host and JP1/AJS3 have started. KAVT0094-E The send source is invalid. (RequestPP=send-source) (maintenance-information) Invalid data was received. (S) Discards the invalid data received, and continues processing.
(S) Continues processing. KAVT0101-E An error occurred during resending of unreported information. (maintenance-information) (host=agent-hostname, AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID, maintenanceinformation) An error occurred while re-sending the unreported information to the agent. (S) Continues processing without changing the status of the unit (a jobnet with start conditions or an event job).
• Check whether the IP address obtained by resolving the agent host name on the manager host is the same as the actual IP address of the agent host. If the IP addresses are different, specify the settings in the hosts file, jp1hosts information, or jp1hosts2 information on the manager host or in the DNS settings so that the correct IP address can be obtained by resolving the name. • Check whether the JP1/AJS3 service on the agent host is running or whether the agent host machine itself is running.
KAVT0108-I The start condition was satisfied. (AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=executionID) The start condition was satisfied. (S) Continues processing. KAVT0110-E An error occurred during resending of unreported information to scheduler service. (maintenance-information) (AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID) An error occurred while resending the unreported information to the scheduler service.
Check the following: 1. Check that the file in the output directory for the queued information has not been deleted. 2. Check whether there is a unit (a jobnet with start conditions or an event job) whose status has not changed. Take the following action: 1. If the condition shown in check item 1 is met, perform a cold start. 2.
KAVT0147-E An error occurred during the processing of an event for reporting the shutdown of an agent machine. (maintenanceinformation) (host=agent-host-name, maintenance-information) An error occurred during the processing in response to the shutdown report from an agent host. (S) Continues processing without changing the status of the event job that is running on the agent. (O) Check the following, and then check the event job whose status has not changed.
• Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group. • Check whether the directory created during installation of JP1/AJS3 was deleted unintentionally. If the above conditions are not satisfied, contact the system administrator and collect data (see 1.2.3 To the system administrators). KAVT0178-E An error occurred during child process creation.
KAVT0193-W The events that occurred during the maintenance mode are discarded because the option to improve event job reliability is invalid. (scheduler-service-name) The reliability improvement option is invalid, so events occurring in maintenance mode are discarded. (S) Continues processing. Discards events occurring in maintenance mode. (O) If no event occurs in maintenance mode, you to not need to take any actions. If an event occurs in maintenance mode, validate the reliability improvement option.
KAVT0250-W Because the total of macro variables exceeded the maximum, part of the data was truncated.(maintenanceinformation) The total number of macro variables exceeded the limit. A part of the data was truncated. (S) Inherits the macro variables with the part of data truncated. (O) Redefine the macro variables so that the sum of the size of the values specified in the macro variables does not exceed 4,096 bytes.
For details on this time, see Table 2-3 in 2.2.2(5) Notes on manager/agent system configurations in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide. (O) A communication error may have occurred due to one of the following reasons.
(O) On the manager host, use the jp1ping command to check whether the IP address of the host indicated by nameof-host-whose-IP-address-could-not-be-obtained can be obtained. For details on the jp1ping command, see the Job Management Partner 1/Base User's Guide. If the IP address cannot be obtained, specify the settings in the hosts file, jp1hosts information, or jp1hosts2 information on the manager host or in the DNS settings so that the correct address can be obtained by resolving the name.
(O) The error is caused by an internal factor of the event/action control. Contact the system administrator and collect data (see 1.2.3 To the system administrators). The unit (a jobnet with start conditions or an event job) indicated by AjsServiceName=scheduler-servicename, UnitID=unit-ID, and ExecID=execution-ID may not have been registered, executed, or operated, or processing may not have been done in response to the event.
Memory was insufficient. (S) Continues processing without changing the status of the unit (a jobnet with start conditions or an event job). (O) See 3. Estimates in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide, and make sure that the required amount of memory for executing JP1/AJS3 has been allocated.
KAVT0288-I Disaster recovery start processing will be performed. The event/action control manager on the remote site is beginning the disaster recovery start process. (S) Continues processing. KAVT0289-E Failed to perform the disaster recovery start process.(maintenance-information) The event/action control manager on the remote site failed to perform the disaster recovery start process. (S) One or more event job that was running on the main site remains in Now running status.
If the IP address of the agent host indicated by host=agent-host-name cannot be acquired, configure DNS and hosts so that the IP address is resolved, and restart JP1/AJS3. KAVT0294-W Unreported information for scheduler-service-name will now be deleted, because the total amount of unreported information for the scheduler service has exceeded threshold.
(S) Deletes unreported information for the agent, beginning from the oldest item, each time the threshold is exceeded. This action might result in the following symptoms: • When an event job is registered for execution, the status of the job does not change from now queuing to now running. • When an event job (including an event job defined in the start conditions) is forcibly terminated, the now running status of the job does not change.
In UNIX: The host name indicated after the jajs_spmd process that is displayed by executing the ps command KAVT0297-W Unreported information will now be deleted, because the amount of unreported information for agent-host-name has exceeded threshold.(maintenance-information) Unreported information will be deleted because the amount of unreported information for the agent indicated in agenthost-name exceeded the value indicated in threshold.
event detection might be seriously delayed. To avoid these problems, cold-start the agent if 1,000 or more events have been detected within a few hours after the relevant message was output. # • For a physical host: For DNS operation, the host name in the FQDN format.
The event/action control submanager will terminate because the event/action control manager has terminated. (S) Terminates the event/action control submanager. (O) Confirm that the directory for output of the wait information file can be accessed, and then restart JP1/AJS3. If the KAVT0187-E message was also output at the same time this message was output, the probable cause is that the directory for output of the wait information file cannot be accessed.
KAVT0333-W The number of the reported events from agent-name exceeds threshold. Processing the events from agent-name might be delayed. (maintenance-information) The number of events reported from the agent indicated in agent-name exceeded the value indicated in threshold. Processing for the events from the agent might be delayed. (S) Continues processing. (O) Check whether: • Check the definition of the event job or the jobnet with start conditions for which the agent is defined as the execution host.
KAVT0340-W Communication to check the operation of the Event Action SubManager failed. The communication will be retried. (maintenance-information) A communication error occurred during processing to periodically check whether the event/action control submanager is running. The communication will be retried. (S) Continues processing. (O) Check the following: • Check whether a mass of events has been detected.
• Check whether communication is possible with all the target hosts displayed by the ajsagtshow command. • Check whether any process is accessing a file in the JP1/AJS3 installation path. • Check whether memory is sufficient. Correct the above problems, and then check whether the event jobs and start conditions work normally. If they do not work normally after a while, there might be a problem with the status monitoring of the event jobs and start conditions.
• Check whether any process is accessing a file in the JP1/AJS3 installation path. • Check whether memory is sufficient. Correct the above problems, and then check whether the event jobs and start conditions work normally. If they do not work normally after a while, there might be a problem with the status management of event jobs and start conditions. Cold-start the scheduler service indicated in maintenance-information, or execute the jpomanevreset command.
KAVT0347-I A response from the Event Action Manager has been confirmed.(maintenance-information) A response from the event/action control manager has been confirmed. (S) Continues processing. KAVT0352-E The connection to the network service was released. (maintenance-information) The connection with the communication control process was lost. (S) Continues processing without changing the status of the event job or the jobnet with start conditions.
• If the message KAVT0353-I is output after this message The connection has recovered. Ignore the message and continue operation. • If the message KAVT0353-I is not output after this message Identify the cause of the error from the errno value in the maintenance information, and take action to correct it.
An error occurred due to an internal factor of the event/action control. (S) Determines the event job to be an error. (O) The error is caused by an internal factor of the event/action control. Contact the system administrator and collect data (see 1.2.3 To the system administrators). KAVT0402-E Memory became insufficient. (maintenance-information) (maintenance-information) Memory became insufficient. (S) Determines the event job to be an error. (O) See 3.
(S) Determines the event job to be an error. (O) Check the following: • Check whether the target host and JP1/AJS3 have started. • If the agent uses the connection source restriction function, check whether the manager's IP address is registered in the agent connection permission configuration file. KAVT0405-W Because communication with the agent failed, it will be retried. An attempt to communicate with the agent has failed due to a temporary communication error.
(O) Wait until the change of the configuration definition information (environment setting) terminates, than then retry. KAVT0409-I The data was sent to the agent. The data was sent to the agent. (S) Continues processing. KAVT0410-E The parameter (parameter) after replacing a macro variable is too long (length=parameter-length). The parameter, after replacing a macro variable, is too long. (S) Determines the event job to be an error.
#1 For the compatible ISAM configuration, 30 minutes. #2 For the compatible ISAM configuration, 15 minutes. (S) Continues processing. (O) Startup of a jobnet with start conditions takes a long time due to heavy loading on the schedule control. The probable causes are: • Many events being monitored by the jobnet with start conditions have occurred. • Many jobnets in a batch or a jobnet containing many jobs was registered for execution or terminated forcibly.
KAVT0414-E The request was rejected. (AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID, maintenance-information) The request was rejected because the IP address of the connecting host was not registered in the agent connection permission configuration file on the destination host. (S) Continues processing. (O) Take action according to the instructions given by the KAVT0992-E message that was output to the integrated trace log of the host where the job is to be executed.
KAVT0508-E A message-reception pipe could not be opened. (process type=process-type maintenance-information) (process name=process-name, maintenance-information) An attempt to create a pipe file used in the event/action control agent has failed. (S) Continues processing while the function of the process indicated in process-type is disabled.
KAVT0512-E The socket could not be opened. (Manager=name-of-manager-at-send-destination) (maintenance-information) Communication with the manager host failed. (S) Terminates the process if the error occurred during startup of the event/action control agent process. If the error occurred after the process started, the system continues processing without changing the status of the event job or the jobnet with start conditions. (O) Check whether: • A network failure occurred.
KAVT0515-E Main loop of an agent failed. (maintenance-information) An attempt to start the event/action control agent has failed. (S) Terminates the event/action control agent. (O) Check the following, and then restart JP1/AJS3: • Check whether the system resources are sufficient. • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group. KAVT0520-W The event monitoring function is unusable.
(O) If you want to use this function, check the following and then restart JP1/AJS3. If you do not intend to use these functions, ignore this message and continue operation. • Check whether an executable file with the same name as the process name indicated in process name=process-name exists. • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group. • Check whether memory is sufficient.
• Check whether an executable file with the same name as the process name indicated in process name=process-name exists. • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group. • Check whether memory is sufficient. For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes. KAVT0524-W The timer monitoring function is unusable.
KAVT0530-E The end request for the pipe could not be written. (process type=process-type maintenance-information) (process name=process-name, maintenance-information) An attempt to write to a pipe file used in the event/action control agent has failed. (S) Continues processing while the function of the process indicated in process-type is disabled.
KAVT0541-E The pipe could not be written to. (process type=process-type maintenance-information) An attempt to write to a pipe file used in the event/action control agent has failed. (S) Continues processing while the function of the process indicated in process-type is disabled.
An attempt to read a communication information file for a monitoring process used in the event/action control agent has failed. (S) Places the job in the Ended abnormally status, and continues processing. (O) Check the following, and then retry: • Check whether system resources are sufficient. • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.
(S) Terminates the event/action control agent. KAVT0566-E The size of the working path exceeds the limit. The length of any of the following directory names exceeded 228 bytes: After correcting the error, stop the JP1/AJS3 service and restart it. • The JP1/AJS3 installation directory name • The WaitInfFileOutDir environment setting parameter for the definition key ([JP1AOMAGENT]) (S) Terminates processing. (O) Correct the length of the following directory names to 228 bytes or smaller.
(S) Continues processing, but does not accept the jajs_spmd_stop command or a stop request from the JP1/AJS3 service. (O) To terminate the event/action control agent in UNIX, use the kill command to terminate the jpoagent process. In Windows, restart the system. The JP1/AJS3 process monitor may not operate correctly. Reinstall JP1/AJS3 and then restart. KAVT0572-E A report to the process monitor failed. (maintenance-information) Communication with the JP1/AJS3 process monitor failed.
See the following supplementary notes and check whether the manager and agent can communicate with each other. Supplementary notes • Check whether the agent host name# can be resolved on the manager host. If the name cannot be resolved, specify the settings in the hosts file, jp1hosts information, or jp1hosts2 information on the manager host or in the DNS settings so that the agent host name can be resolved. • Check whether the manager host name# can be resolved on the agent host.
• The WaitInfFileOutDir environment setting parameter for the definition key ([JP1AOMAGENT]) (S) Terminates processing. (O) Specify the following directory names. • The JP1/AJS3 installation directory name • The WaitInfFileOutDir environment setting parameter for the definition key ([JP1AOMAGENT]) KAVT0590-W During end processing, an event request (event-request-type) from the manager (manager-name) cannot be accepted.
KAVT0593-W The MS message queue monitoring function is unusable. (maintenance- information, process name=processname, maintenance-information) The MSMQ monitoring function is unusable. (S) Continues processing in a reduced mode for the functions. (O) Refer to the message that describes the cause of the error, and then follow the instructions. KAVT0600-E Failed in creation of status file.
The agent attempted to report the status of an event job to the manager, but could not communicate with the manager indicated in manager-name due to a temporary communication error. # The IP address is output only when the LOGIPV6INFOALL environment setting parameter is set to yes. If the LOGIPV6INFOALL environment setting parameter is set to yes and the IP address is unknown, unknown is displayed. (S) Retries communication after the predefined period of time. For details on this time, see Table 2-3 in 2.2.
(O) The job may remain in the queue or in the execution status while the event is established. Check the job execution status. KAVT0609-W The socket receiving failed. (IP Address=IP-address host=host-name) The connection is severed while the socket is receiving data. (S) Continues processing. (O) The job may remain in the queue or in the execution status while the event is established. Check the job execution status of host-name. KAVT0610-W The socket receive error occurred.
The agent reported the status of an event job to the manager, but could not confirm the arrival of data from the manager indicated in manager-name due to a temporary communication error. # The IP address is output only when the LOGIPV6INFOALL environment setting parameter is set to yes. If the LOGIPV6INFOALL environment setting parameter is set to yes and the IP address is unknown, unknown is displayed. (S) Retries communication after the predefined period of time.
KAVT0615-W Unreported information resend max over. Unreported information will be abandoned. (Manager=manager-name) The agent retried communicating with the manager for the predefined period of time, but could not send the status of the event job. For details on this time, see Table 2-3 in 2.2.2(5) Notes on manager/agent system configurations in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide. (S) Continues processing without reporting the event job status.
• Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group. • Check whether the directory created at JP1/AJS3 installation was unintentionally deleted. KAVT0620-E The subagent pipe could not be written to. (code=maintenance-code) An attempt to write to a pipe file used in the event/action control subagent has failed. (S) Continues processing without changing the status of the unit (a jobnet with start conditions or an event job).
(S) Terminates the event/action control agent. (O) Check the following, and then restart JP1/AJS3: • Check whether system resources are sufficient. • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group. • Check whether the directory created at JP1/AJS3 installation was unintentionally deleted. • Check whether any other program has forcibly terminated the jpoagtsub process illegally. KAVT0628-E The subagent function is unusable.
KAVT0632-E The agent pipe could not be written to. (code=maintenance-code) (host= manager-host-name, AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID, maintenance-information) The pipe file of the event/action control agent could not be written. (S) Continues processing without changing the status of the unit (a jobnet with start conditions or an event job). (O) Check the following, and then use the ajsname command with the -I option to identify the unit name from the unit ID.
• Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group. • Check whether the directory created at JP1/AJS3 installation was unintentionally deleted. KAVT0637-E An agent-message-reception pipe could not be read. (code=maintenance-code) (host=manager-host-name, AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID, maintenance-information) The information could not be obtained from the event/action control agent.
(O) Confirm that the directory for output of the wait information file can be accessed, and then restart JP1/AJS3. If the KAVT0643-E message was also output at the same time this message was output, the probable cause is that the directory for output of the wait information file cannot be accessed. Confirm that the directory for output of the wait information file can be accessed. If there are any problems, correct them.
• Check whether the directory created at JP1/AJS3 installation was unintentionally deleted. KAVT0649-E A host name in the FQDN format could not be obtained. Processing is canceled. (code=maintenance-code) (host=host-name, maintenance-information) The system could not obtain a host name in the FQDN format. (S) Terminates processing. (O) Check whether the DNS has been set up correctly. KAVT0650-W Port information about the event action function cannot be read, so the default port number is used.
KAVT0654-E The files will be deleted, because the internal files of event action control have been destroyed. (maintenanceinformation) The files will be deleted because the internal files used for event action control have been corrupted. If this message appears, the following phenomena may have occurred: • Information about the events that occurred before JP1/AJS3 stopped was lost. • Monitoring was not resumed for the jobnets with start conditions and event jobs that were running before JP1/AJS3 stopped.
For details about the jpoagoec command, see jpoagoec in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1. For details about limit values, see B. List of Limits in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide. KAVT0900-I JP1/AJS2 event action agent will now start. The event/action control agent will now start. (S) Continues processing. KAVT0901-I JP1/AJS2 event action agent will now end.
memory was output at the same time the error occurred. If a log indicating insufficient memory was output, recheck the memory estimate. If other unnecessary applications are running, stop them. If the cause of the error is not insufficient memory, collect the internal trace log and then contact the system administrator. KAVT0912-E Event Action process ended abnormally.
For details about the detail process termination option, see 2.4 Setting up the event/action control environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2. (O) Examine the cause of the error from the system error message that was output before or after the message, and then take action. If you cannot determine the cause of the error, collect data and then contact the system administrator (see 1.2.3 To the system administrators).
KAVT0954-I OpenView Environment of JP1/AJS2 was uninstalled normally. HP NNM Link was uninstalled normally. (S) Continues processing. KAVT0955-I Symbol of JP1/AJS2 was deleted normally. The symbol was deleted normally. (S) Continues processing. KAVT0958-I Resource monitoring will now start. Resource monitoring starts. (S) Continues processing. KAVT0959-I Resource not found. The resource is not found. (S) Continues processing. KAVT0960-I Resource status to be offline. The resource is placed offline.
KAVT0961-I Resource status to be online. The resource is placed online. (S) Continues processing. KAVT0962-I Resource monitoring bring to a termination. Resource monitoring terminated. (S) Terminates processing. KAVT0963-I Resource monitoring will now end. Resource monitoring terminates. (S) Terminates processing. KAVT0980-W Unreported information will now be deleted, because the amount of unreported information for manager-hostname has exceeded threshold.
reduce the number of events to be generated. You can obtain the name of the jobnet with start conditions in the following procedure: 1. Check the scheduler service name and unit ID indicated in AJSServiceName=scheduler-service-name, UnitID=unit-ID in the message. 2. On the manager host, execute the ajsname command with the scheduler service name and unit ID you obtained in step 1 specified. Example: ajsname -F scheduler-service-name -I unit-ID /name-of-the-jobnet with start conditions/.
Also check the following and take action if necessary: • If an event job is registered for execution but the job status does not change from Now queuing to Now running, check the items described in (O), forcibly terminate the job, and then retry the operation. • If a jobnet with start conditions or an event job is forcibly terminated but the job status remains Now running, check the items described in (O), and then forcibly terminate the job or jobnet again.
If the name cannot be resolved, review the settings in the hosts file, jp1hosts information, or jp1hosts2 information on the manager host or in the DNS settings so that the agent host name can be resolved. • Check whether the manager host name# can be resolved on the agent host. If the name cannot be resolved, review the settings in the hosts file, jp1hosts information, or jp1hosts2 information on the agent host or in the DNS settings so that the manager host name can be resolved.
For a physical host, JP1_DEFAULT is indicated in host-name. If the connection source IP address was not obtained, null characters are output for connection-source-IP-address. (S) Ignores the request and continues processing. (O) - If reason is Restricted: If the request from the IP address indicated in connection-source-IP-address must be accepted, perform the following: 1.
(O) Use the jbsgetcnf command to check whether you can acquire common definition information for the logical host that caused the error. If you cannot acquire the common definition information, re-install JP1/Base. If you can collect it, contact the system administrator and collect data (see 1.2.3 To the system administrators). KAVT1004-I The event sever was connected. (event-server-name) The JP1/Base event service was connected. (S) Continues processing.
(O) Check whether the JP1/Base event service has started. KAVT1008-E Initialization error (maintenance-information) (maintenance-information) Initialization required for acquiring information has failed. (S) Continues processing. The system terminates the event (such as JP1 event and log trap) monitoring process depending on the location where the error occurred. A Receive JP1 Event job, a Monitoring Log Files job, or a Monitoring Event Log job cannot be monitored.
KAVT1015-E The log-file trap command could not start. (maintenance-information) An attempt to start the Monitoring Log Files job has failed. (S) Places the log file monitoring job into Ended abnormally status. (O) An error message for the JP1/Base log-file trap function has been output to the Execution Result Details dialog box. Take action according to the instructions given by that message.
KAVT1026-W The end judgment file includes no data. (end-judgment-file-name) The end judgment file specified in the Receive JP1 Event job does not contain data. (S) Ignores information about end judgment and continues processing. If Normal if message matches or Normal if details match is specified for End judgement, the system terminates the relevant JP1 event reception monitoring job abnormally.
KAVT1029-E The event could not be created. (maintenance-information) (maintenance-information) An attempt to connect to the JP1/Base event service has failed. (S) Retries until the JP1/Base event service is connected. The JP1 event reception monitoring job, log file monitoring job, and Windows event log monitoring job cannot be monitored during the retries. (O) Check whether the JP1/Base event service can start.
(S) Interprocess communication failed. The system continues processing. If the error occurred during registration, registration of the event job will be unsuccessful. If the error occurred after registration, the job execution status may be incorrect. (O) Check the following, and then retry the event job that caused the error: • Check whether the system resources are sufficient. • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.
(S) Retries connection to the JP1/Base event service. No events can be monitored until the KAVT1004-I or KAVT1044I message is output. (O) See the description of the API settings file (api) in the Job Management Partner 1/Base User's Guide, and check whether the api file is set correctly. Also check whether the JP1/Base event service is running. If the JP1/Base event service has been terminated unintentionally, contact the system administrator, and collect data (see 1.2.
(O) Check whether the system resources are sufficient, and then re-execute the Monitoring Log Files job. KAVT1046-E The event ID is invalid. (maintenance-information) The event ID defined for the Receive JP1 Event job is invalid. (S) Abnormally terminates the Receive JP1 Event job. (O) Define the event ID correctly, and then retry. KAVT1047-W An error occurred during analysis of macro variables. (maintenance-information) (maintenance-information) An error occurred while analyzing the macro variable.
(O) Follow the instructions given by the message that was output immediately before this message, and then restart JP1/ AJS3. KAVT1052-W The log-file trap daemon (service) ended. The JP1/Base log-file trap management daemon (UNIX) or log file trap management service (Windows) stopped during execution of the log-file trap monitoring job.
KAVT1058-I retry again. A temporary error occurred. The system re-executes the log file trapping command. (S) Continues processing. KAVT1059-I Watching start. The log file trapping command was successfully executed. The system starts monitoring the log file. (S) Continues processing. KAVT1060-W A forced-termination request was accepted. The system accepted a forced-termination request. The job is forcibly terminated. (S) Accepts the kill request and forcibly terminates the job. KAVT1061-W Cancel time up.
(O) Check whether memory is sufficient. For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes. KAVT1065-W The log-file trap command could not stop. (process-ID-of-log-file-trap (thread-ID) (operation-definition-filename-at-executing-log-file-trap-command) The Monitoring Log Files job terminated normally, but the process for monitoring log files could not stop or the termination could not be confirmed.
A monitoring condition using a regular expression may not work correctly. Check the generated JP1 event again, and change the status of the Receive JP1 Event job. KAVT1068-W The specified event server is inactive. (EventServerName=event-server-name) The JP1/Base event service specified in the EventServerName environment setting parameter has not yet started. (S) Because the JP1/Base event service has not started, the system continues processing while retrying the connection.
(S) Cancels processing. (O) Check whether memory is sufficient. For details on the amount of memory required, see JP1/Base Release Notes. KAVT1202-E The reading of JP1 event search conditions from the file was not possible. (maintenance-information) The system could not read from a file the search conditions for the JP1 event to be searched for by the pre-execution event search function. (S) Cancels processing. (O) Check the file system for errors.
An error occurred while the search result output file was being opened. (S) Cancels processing. (O) Based on the system error message, determine the cause that disabled the read operation. Then, remove the cause. KAVT1206-E An error occurred during status file making process. maintenance-information, system-error-message An error occurred during the creation of a status file. (S) Cancels processing. (O) Based on the system error message, determine the cause that disabled the read operation.
The system could not create an event search filter file. (S) Cancels processing. (O) Correct the cause that disabled the creation of the event search filter file, and then re-execute the operation. KAVT1212-E An attempt to start the event search process failed. file-name, error-code, maintenance-information The system could not start the event search process. (S) Cancels processing. (O) Correct the cause that disabled the start of the event search process, and then re-execute the operation.
KAVT1217-I An instance was established by the search for events prior to execution. (job-name, Event Arrived Time=arrivaltime-of-event-satisfying-conditions) As a result of the pre-execution event search, the system found an event that satisfies the job conditions. (S) Continues processing. KAVT1226-W Old JP1 events will be discarded because the number of preserved JP1 events issued during a search of pre-execution events has exceeded the threshold.
KAVT2005-I The file (file-name) was deleted. The file was deleted. (S) Continues processing. KAVT2006-I The last modification time of file (file-name) has changed. The last modification time of the file has changed. (S) Continues processing. KAVT2007-I The size of the file (file-name) has changed. The size of the file has changed. (S) Continues processing. KAVT2012-I The file monitoring process will now end. The file monitoring process terminates. (S) Terminates the file monitoring process.
KAVT2014-E The specified name of the file to be monitored is not a full path name. The name of the file to be monitored is specified incorrectly. (S) Abnormally terminates the job. (O) Check the name of the file to be monitored, and then specify the full path name using the correct format. KAVT2015-E You cannot specify an asterisk (*) in a directory name. A wildcard (*) cannot be specified in the directory name. (S) Abnormally terminates the job.
The request to forcibly cancel a job is accepted. The job is forcibly canceled. (S) Forcibly cancel the job by the request. KAVT2019-E The file monitoring process ended. (maintenance-information) The file monitoring process detected an error and terminated. (S) Terminated the file monitoring process because an error that prevents further processing occurred during processing. A Monitoring Files job cannot be monitored. (O) The error is caused by an internal factor of the event/action control.
(S) Checks again whether there is a process that has opened the file at the next execution interval. Establishment of the file monitoring event job is delayed until the check finishes. (O) If this message appears repeatedly, check whether there is sufficient memory for executing the program, and then try again to change the status of the file indicated in file-name. KAVT2023-E Memory became insufficient. (maintenance-information) Memory became insufficient.
Specify at least ten seconds for the monitoring interval. (S) Abnormally terminates the file monitoring job due to the invalid monitoring interval specified. (O) Check whether the conditions for specifying a 10-second or smaller monitoring interval are satisfied. KAVT2026-E The name of the file to be monitored cannot be obtained. (maintenance-information-1) (maintenanceinformation-2) The name of the file to be monitored could not be obtained.
KAVT2029-E An attempt to obtain pipe data failed. (maintenance-information) (maintenance-information) The pipe data could not be received from the agent. (S) Terminates the file monitoring process because an error occurred during pipe processing with the agent. (O) Check the following, and then restart JP1/AJS3: • Check whether system resources are sufficient. • Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of the Administrators group.
• Check whether the following message was output in the same time zone: KAVT2034-W The status passing option file cannot be opened. The status passing cannot be executed. (file-name, maintenance-information). If this message was output, follow the instructions given by the KAVT2034-W message. • Check whether the size of the file to be monitored is smaller than 2 gigabytes. To monitor a file equal to or greater than 2 gigabytes, use the large file support option to specify monitoring of large files.
(O) Check the following: • Check whether system resources are sufficient. • Check whether the directory created at JP1/AJS3 installation was unintentionally deleted. • For a cluster system, check whether the setting of the status passing option for a Monitoring Files job between the primary node and the secondary node matches. • For a cluster system that uses event jobs for DNS operation, check whether the setting for operation using the FQDN format between the primary node and the secondary node matches.
A file with the specified monitoring condition was updated, but the sum of the size of the values specified in macro variables exceeded 4,096 bytes. (S) The maximum amount of data that can be used for all macro variables per event is 4096 bytes (includes variable names). If the macro variable data exceeds 4096 bytes, the system uses only the first 4096 bytes and continues processing. (O) Check the execution status of the succeeding jobnet or job. If you find any problem, recheck the job definition.
KAVT3002-I Mail could not be received. Mail could not be received. (S) Cancels processing. (O) Check whether the environment is set up to send and receive mail. KAVT3003-E Mail could not be saved. Saving mail was impossible. (S) Cancels processing. (O) Check whether the environment is set up to save files for the disk size or authorization. KAVT3004-E JP1/AJS2 Mail monitoring Service stopped. Stop processing. The system stops processing since the JP1/AJS2 mail monitoring service stopped.
KAVT3006-E Initialization failed. (reason) Initialization was impossible. (S) Cancels processing. (O) Check whether the environment is set up to send and receive mail. If the error occurred due to insufficient memory, allocate sufficient memory for execution, and then retry. KAVT3012-E MAPI could not be initialized. (reason) MAPI used for sending and receiving email could not be initialized. (S) Cancels processing.
KAVT3015-I The result of logon. (mapi_code=maintenance-information maintenance-information maintenance-information maintenance-information) This message indicates the results of logon to the profile. (S) Continues processing. KAVT3016-E Profile name used in send processing during logon is not within the definition. A profile name used during logon is not defined for send processing. (S) Cancels processing. (O) Check whether the profile name specified in setup is correct, and then retry.
(S) Cancels processing. (O) If the error occurred due to insufficient memory, allocate sufficient memory for execution, and then retry. For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes. If reason indicates mapi_code = xxxxxxxx (eight hexadecimal numbers), resolve the problem and then re-execute the job. For details on how to resolve the problem, see 2.10.
In addition, check whether Microsoft Outlook can send and receive email independently of JP1/AJS3 and whether a dialog box prompting the user to respond appears during email sending or receiving. If Microsoft Outlook cannot send or receive email independently or the dialog box appears, review the profile and mail account settings. KAVT3027-E Mail to be sent could not be created. (reason) Creating mail to send was impossible. (S) Cancels processing.
job ends abnormally in the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting. In addition, check whether Microsoft Outlook can send and receive email independently of JP1/AJS3 and whether a dialog box prompting the user to respond appears during email sending or receiving. If Microsoft Outlook cannot send or receive email independently or the dialog box appears, review the profile and mail account settings. KAVT3033-I The text was re-processed.
KAVT3038-E The send processing could not be preprocessed. Preprocessing a send was impossible. (S) Cancels processing. (O) Check whether the environment is set up to send and receive mail. If the error occurred due to insufficient memory, allocate sufficient memory for execution, and then retry. For details on the amount of memory required by JP1/ AJS3, see Memory and Disk Space Requirements in Release Notes. KAVT3039-E During send processing, logoff failed.
Logoff for reception processing was impossible. (S) Cancels processing. (O) Check whether the mail server has gone down or a profile is created correctly. KAVT3044-E The reception processing could not be initialized. (reason) Initializing the reception processing was impossible. (S) Cancels processing. (O) Check whether the environment is set up to send and receive mail. If the error occurred due to insufficient memory, allocate sufficient memory for execution, and then retry.
KAVT3051-E Mail could not be read. (reason) Reading mail was impossible. (S) Cancels processing. (O) Check whether the environment is set up to send and receive mail. If the error occurred due to insufficient memory, allocate sufficient memory for execution, and then retry. KAVT3054-E The text could not be acquired. (reason) Acquiring the text was impossible. (S) Cancels processing. (O) Check whether the environment is set up to send and receive mail or the text is specified correctly.
KAVT3061-E The received mail could not be read. (reason) Reading mail to receive was impossible. (S) Cancels processing. (O) Check whether the environment is set up to send and receive mail. If the error occurred due to insufficient memory, allocate sufficient memory for execution, and then retry. KAVT3064-E The list of attached files could not be acquired. (reason) Acquiring an attached file list was impossible. (S) Cancels processing. (O) Check whether the attached file list is correct.
KAVT3070-E The attached file could not be saved. (reason) Saving an attached file was impossible. (S) Cancels processing. (O) Check whether the environment is set up to save the attached file. If the error occurred due to insufficient memory, allocate sufficient memory for execution, and then retry. KAVT3073-E The attached file could not be saved. Saving an attached file was impossible. (S) Continues processing. (O) Refer to the message output previously and determine the cause.
(O) Take action according to the error code indicated in the message (return code from the Windows GetLastError() function). KAVT3076-E The opening-completed setting failed. (reason) Setting a piece of opened mail was impossible. (S) Cancels processing. (O) Check whether the environment is set up to send and receive mail. If the error occurred due to insufficient memory, allocate sufficient memory for execution, and then retry. KAVT3078-E The text could not be saved. The email text could not be saved.
KAVT3080-E During reception processing, a file could not be saved. Saving a file was impossible for reception processing. (S) Continues processing. (O) Check whether the environment is set up to save a file. KAVT3081-E During reception processing, the icon could neither be sent nor received. Communicating with the icons was impossible for reception processing. (S) Cancels processing. (O) Check whether the environment is set up to send and receive mail. KAVT3083-E Failed to delete mail.
KAVT3086-E During reception processing, logoff failed. (reason) Logoff was impossible for reception processing. (S) Cancels processing. (O) Check whether the environment is set up to log in the mail server. If the error occurred due to insufficient memory, allocate sufficient memory for execution, and then retry. KAVT3106-I Mail reception will now start. Mail reception starts. (S) Continues processing. KAVT3107-I Mail sending will now start. Mail sending starts. (S) Continues processing.
(S) Continues processing. KAVT3201-I Start process of controlling MAPI (Receive). The MAPI receive control process starts. (S) Continues processing. KAVT3202-I End process of controlling MAPI (Send). The MAPI send control process terminates. (S) Continues processing. KAVT3203-I End process of controlling MAPI (Receive). The MAPI reception control process terminates. (S) Continues processing. KAVT3204-E Failed to create a temporary file.
KAVT3205-E Failed to read a temporary file. file=file-name GetLastError=GetLastError-number A temporary file to be used for mail system linkage could not be read. (S) Cancels processing. (O) Determine the cause of the error that prevented the file indicated in file=file-name GetLastError=GetLastError-number from being read. KAVT3206-E Failed to create a folder. folder-name A folder could not be created. (S) Cancels processing.
The specified email address was not found in the send destination mail system. Alternatively, the mail system in which the email address has been registered was not found. maintenance-information indicates the number of email addresses that are specified in the email sending job but were not found. (S) Ignores the email address that was not found, and continues processing.
• None of the specified email addresses can be found in the send destination mail system. • None of the mail systems in which the specified email addresses have been registered can be found. (S) Cancels processing. (O) If email addresses are not specified for the email sending job, specify them. Check whether the specified email address was registered in the send destination mail system, and whether the mail system is running and ready for communication. For details about the contents of mapi_code, see 2.
KAVT3273-I Processing of mail sending will now start. The mail transmission starts. (S) Continues processing. KAVT3274-I Processing of mail sending will now end. The mail transmission terminates. (S) Terminates processing. KAVT3275-E The environment variable is specified incorrectly. (specified-data) The environment variables are specified incorrectly. (S) Cancels processing. (O) Check the system resources, and then retry. KAVT3276-E The data is specified incorrectly.
The name of a list file for attached files is invalid. (S) Cancels processing. (O) Check the following according to the data type: • "Platform" PC is specified as the platform type. • "Additional Information of Destination" TO:, CC:, or BCC: appear before the recipient. • "Text File", "Attach File", "Attach File List" The file is specified by full path name and in the correct format for Windows. After making the necessary corrections, rerun the email sending job. KAVT3277-E A required item is missing.
(O) Check whether JP1/AJS3 is installed correctly and whether the information is correctly set for the environment setting parameters to be used for mail system linkage. For details, see 2.3.4 Setting up the environment for the mail system linkage in the Job Management Partner 1/Automatic Job Management System 3 Linkage Guide.
KAVT3282-E An unexpected error occurred. (return-code-of-GetLastError-function) An unexpected error occurred in the email sending job. (S) Cancels processing. (O) Take action according to the message that was output immediately before this message, or by checking the return code of the Windows GetLastError() function. KAVT3283-E The process will now stop because the mail monitoring process or service terminated. Processing is stopped due to the mail monitoring process or service halt.
KAVT3286-E Communication of mail information failed. Communicating the mail information was impossible. (S) Cancels processing. (O) Check whether the JP1/AJS3 mail monitoring process or service is running. KAVT3287-E The communication pipe could not be created. Creating a communication pipe was impossible. (S) Cancels processing. (O) Check whether the JP1/AJS3 mail monitoring process or service is running. KAVT3288-E The thread could not be created.
If you cannot take corrective action, contact the system administrator, and collect data (see 1.2.3 To the system administrators). KAVT3290-E Memory became insufficient. There is not enough memory. (S) Cancels processing. (O) Allocate sufficient memory to execute, and then retry. KAVT3291-E JP1/AJS2 mail monitoring process or service is not running. (return-code-of-GetLastError-function) The JP1/AJS3 mail monitoring process or service is not running. (S) Cancels processing.
(O) Check the error details by comparing return-code-of-MAPI-function with the following MAPI codes, and then take action. Also see the manual Job Management Partner 1/Automatic Job Management System 3 Troubleshooting. • 8004010D: The disk space is insufficient. • 8004010E: The resources are insufficient. • 80040111: Logon failed. • 80040115: A network error occurred. • 80040116: A disk I/O error occurred. • 80040124: The mail account is invalid. • 8004010F: The destination mail address is not found.
An invalid character is used in the environment settings for the mail linkage function. (S) Cancels processing. (O) Check the contents indicated in execution-mode in the message. Then, on the Mail Linkage page in the Manager Environment Settings dialog box or Agent Environment Settings dialog box, specify the setting requiring use of the mail linkage function on the desktop or on the service. KAVT3297-E The length of the text exceeds the maximum. The length of the text exceeded the upper limit.
KAVT3300-E The folder specified for storing the list of attached files does not exist. (folder-name) A folder that stores the attached file lists does not exist. (S) Cancels processing. (O) Check whether a storage folder for the file exists. KAVT3301-E The specified mail text file does not exist. (file-name) A text file does not exist. (S) Cancels processing. (O) Check whether the specified file exists. KAVT3302-E The text file could not be read. (file-name) Reading a text file was impossible.
KAVT3304-E The attached files or list of attached files could not be read. Reading the attached file or attached file list was impossible. (S) Cancels processing. (O) Check whether the specified file is correct. KAVT3401-I Start JP1/AJS2 Mail monitor process. The JP1/AJS3 mail monitoring process is started. (S) Continues processing. KAVT3402-I The JP1/AJS2 mail monitoring process started. The JP1/AJS3 mail monitoring process has started. (S) Continues processing.
KAVT3405-I The JP1/AJS2 mail monitoring process will now end. The JP1/AJS3 mail monitoring process stops. (S) Continues processing. KAVT3406-I JP1/AJS2 Mail monitoring process stopped. The JP1/AJS3 mail monitoring process stopped. (S) Cancels processing. KAVT3407-I The JP1/AJS2 mail monitoring service will now end. The JP1/AJS3 mail monitoring service stops. (S) Continues processing. KAVT3408-I JP1/AJS2 Mail service stopped. The JP1/AJS3 mail monitoring service was stopped. (S) Cancels processing.
(O) Check whether JP1/AJS3 is installed correctly and whether the information is correctly set for the environment setting parameters to be used for mail system linkage. For details, see 2.3.4 Setting up the environment for the mail system linkage in the Job Management Partner 1/Automatic Job Management System 3 Linkage Guide.
KAVT3453-I The mail linkage communication process stopped. The mail linkage communication process has stopped. (S) Terminates processing. KAVT3454-I Mail reception monitoring will now start. Monitoring of mail reception starts. (S) Continues processing. KAVT3455-E Mail reception monitoring will now stop. Mail reception monitoring stops. (S) Continues processing. (O) Refer to the error message output previously and determine the cause of the error.
KAVT3458-I Method of mail monitor is "JP1/AJS2 Mail Service" -or- "JP1/AJS2 Mail Process". This message shows the method of mail monitoring. (S) Continues processing. KAVT3459-E Method of mail monitor is not established. Please set up environment. Check the environment definition, and then retry. (S) Cancels processing. (O) Check the environment definition, and then retry. KAVT3460-E Cannot recognize method of mail monitoring. Please set up environment again.
KAVT3462-W A macro variable exceeds 4096 bytes. Some macro variables could not be created. The macro variable exceeded 4,096 bytes. Some macro variables could not be created. (S) Continues processing. (O) Set a macro variable that does not exceed 4,096 bytes. KAVT3463-E The platform is specified incorrectly. A platform is specified incorrectly. (S) Cancels processing. (O) Check the platform, and then retry. KAVT3464-W The mail monitoring process or service is not running.
The email reception monitoring job is defined incorrectly. (S) Cancels processing. (O) Correct the definitions of the email reception monitoring job, and then retry. KAVT3467-E Memory became insufficient. A memory shortage occurred. (S) Cancels processing. (O) Allocate sufficient memory for execution, and then retry. KAVT3468-E An event for canceling registration of a job could not be created. Creating an event for canceling job registration was impossible. (S) Cancels processing.
KAVT3473-E The count of the mail monitoring job is over a max job's count. (Max job's count=maximum-registration-count) The number of registered email reception monitoring jobs has exceeded the limit value. (S) Cancels processing. (O) If necessary, unregister the email reception monitoring jobs so that the number of registered jobs is below the limit value. For details about the limit values, see the cautionary notes in 2.6.
KAVT3504-E Failed to analyze job data. (DB-data) (error-code-of-function) A failure occurred in the function that analyzes job data. (S) Cancels processing. (O) Check whether the job is defined correctly. KAVT3512-E Memory became insufficient. (maintenance-information) A memory shortage occurred. (S) Cancels the process without enough memory and continues processing. (O) Check the system for free space. KAVT3513-E Failed to get Pipe Data.
(O) Check whether: • The system resources are sufficient. • The permission environment of the started user is correct. • The directory created during installation of JP1/AJS3 is not deleted inadvertently. KAVT3515-E An auxiliary file could not be opened. (maintenance-information) (maintenance-information) Unable to open an auxiliary file from the agent. (S) Abnormally terminates the job request. (O) Check whether: • The system resources are sufficient.
KAVT3521-W An error occurred during analysis of macro variables. (maintenance-information) (maintenance-information) An error occurred while analyzing a macro variable. (S) Does not create a macro variable and abnormally terminates the job. (O) Re-execute the job as required. KAVT3522-W Information could not be output. (maintenance-information) (maintenance-information) Outputting the information to the standard error output was impossible.
(S) Cancels processing, and continues processing after a monitoring interval elapses. (O) If this message is output more than once, determine the cause of the error from the maintenance information. KAVT3526-W Mail File(maintenance-information)can not be locked, because the file is being used by another application. The lock processing failed because the monitored mail file was already locked. (S) Cancels processing, and continues processing after a monitoring interval elapses.
(O) Determine the cause of the error from the maintenance information, and take appropriate action. KAVT3532-W Mail File(maintenance-information)could not be deleted.( maintenance-information)( maintenance-information) A mail file could not be deleted. (S) Cancels the processing, and continues processing. (O) Determine the cause of the error from the maintenance information, and take appropriate action. KAVT3533-W A mail file (mail-file-name) could not be written.
(S) Continues processing. (O) Check the content of the environment definition, and then restart JP1/AJS3 and reload. KAVT3539-W No monitoring user name is specified. A monitoring user name is not specified in the environment definitions. (S) Continues processing. (O) Redefine the environment definitions. KAVT3540-W No mail file directory is specified. A mail file directory is not specified in the environment definitions. (S) Continues processing. (O) Redefine the environment definition.
(S) Continues processing. (O) Redefine the environment definition. KAVT3543-W The mail file directory name exceeds (specified-byte-length) bytes. The mail file directory name in the environment definition exceeds the maximum byte length. (S) Continues processing. (O) Redefine the environment definition. KAVT3544-W The name of the file for saving mail exceeds (specified-byte-length) bytes. The length of the mail for saving file names in the environment exceeds the maximum byte length.
(S) Continues processing. (O) Redefine the environment definition. KAVT3547-W Information about mail file (maintenance-information) could not be obtained: maintenance-information (maintenance-information, system-error-message) Obtaining the file information for the mail files was impossible. (S) Cancels processing, waits for the monitoring interval and continues processing.
KAVT3550-W The output file from the mail filtering application could not be read: (maintenance-information, system-errormessage) Reading an input file was impossible from the mail filter applications. (S) Cancels processing, waits for the monitoring intervals, and continues processing. (O) Use maintenance information and system error message to determine the cause of the error that prevented mail from being read. Then take action. KAVT3551-E An error occurred in the mail filtering application.
KAVT3554-W The inherited mail file (file-name) could not be written to: (maintenance-information, system-error-message) Writing an inheritance mail file was impossible. (S) Terminates the job without inheritance information. (O) Use maintenance information and system error message to determine the cause of the error that prevented mail from being written. Then take action.
(O) Use maintenance information and system error message to determine the cause of the error that prevented mail from being written. Then take action. Re-execute the job if needed. KAVT3558-W The file for saving mail (file-name) could not be closed: (maintenance-information, system-error-message) Closing a mail save file was impossible. (S) Terminates the job and continues processing.
Acquiring the output file information in the mail filter applications was impossible. (S) Continues processing. (O) Use maintenance information and system error message to determine the cause of the error that prevented the file information from being obtained. Then take action. KAVT3562-E The file output from the mail filtering application contains no mail. No mail is found in the output file of the mail filter applications. (S) Continues processing. (O) Check the mail filter application.
No arrival data is found for the mail. (S) Continues processing. (O) Stop JP1/AJS3 and then check the mail system. KAVT3566-W Mail File could not be compressed.: maintenance-information (maintenance-information, system-error-message) Compressing the mail file was impossible. (S) Continues processing. (O) Use maintenance information and system error message to determine the cause of unsuccessful rewriting. Then take action. KAVT3567-W The mail reception list file (file-name) could not be created.
KAVT3569-W The mail reception list file (file-name) could not be written to: (maintenance-information, system-error-message) Writing a mail reception list file was impossible. (S) Continues processing. (O) Use maintenance information and system error message to determine the cause of the error that prevented the mail reception list from being written. Then take action.
(O) Use maintenance information and system error message to determine the cause of the error that prevented mail from being written. Then take action. KAVT3573-W The error mail file (file-name) could not be closed: (maintenance-information, system-error-message) Closing an error mail file was impossible. (S) Cancels processing, waits for the monitoring interval and continues processing.
Writing a save file for mismatched mail was impossible. (S) Cancels processing, waits for the monitoring interval and continues processing. (O) Use maintenance information and system error message to determine the cause of the error that prevented mail from being written. Then take action. KAVT3577-W The file for storing mismatched mail (file-name) could not be closed: (maintenance-information, system-errormessage) Closing a save file for mismatched mail was impossible.
The environment definition does not specify the monitoring intervals. (S) Assumes ten minutes. (O) Redefine the environment definition as required. KAVT3586-W Specify a monitoring interval from 1 to 1,440. The monitoring interval for the environment definition exceeds the range of 1 to 1,440. (S) Assumes ten minutes. (O) Redefine the environment definition as required. KAVT3587-W The inherited mail file could not be created. (file-name) Creating an inheritance mail file was impossible.
A storage directory for inheritance information is not specified to the environment definitions. (S) Assumes an inheritance information directory in units of a logical host. (O) Redefine the environment definition as required. KAVT3594-I Mail will be monitored. Mail will be monitored in response to the request from the job. (S) Continues processing. KAVT3595-W Mail cannot be monitored. Mail cannot be monitored in the current state. (S) Continues processing and accepts the job request.
(S) Continues processing. (O) Check whether: • The maintenance information provides a file. • The system resources are sufficient. • The permission environment of the started user is correct. KAVT3598-E An error occurred during mail reception monitoring: maintenance-information maintenance-information maintenance-information maintenance-information An error occurred during monitoring of mail reception. (S) Continues processing.
sendmail starts. (S) Continues processing. KAVT3702-I Mail was sent normally. Mail was sent normally. (S) Terminates processing. KAVT3703-I temporary file:("temporary-file-name") The working file name was created. (S) Continues processing. KAVT3704-E The command was interrupted. The command was interrupted. (S) Cancels processing. (O) Determine the cause of the interruption by referring to another output message, and then retry.
KAVT3706-E A temporary file could not be created. (file: "temporary-file-name") Creating a temporary file for sending mail was impossible. (S) Cancels processing. (O) Check that there is sufficient disk spaces, and then retry. KAVT3707-E The specified platform is invalid. (Platform: "platform-name") The specified platform is invalid. (S) Cancels processing. (O) Check the definitions and re-execute the job. KAVT3708-E No platform is specified. No platform is specified. (S) Cancels processing.
KAVT3710-E The mail-destination address is invalid: ("mail-destination-address") An invalid mail destination address is specified. (S) Cancels processing. (O) Check the definitions and then re-execute the job. KAVT3711-E No mail-destination address is specified. A mail destination address is not defined. (S) Cancels processing. (O) Check the definitions and then re-execute the job.
KAVT3715-E The mail text file cannot be read. A mail text file name was specified, but the file could not be read. (S) Cancels processing. (O) Check whether the file can be read. KAVT3716-W Mail text was too long, so it was truncated. Mail text was too long, so it was truncated. (S) Continues processing. (O) Check the length and contents of text you want to send.
KAVT3719-E sendmail returned an unexpected error. (error: return-code-of-sendmail-command) The sendmail command for sending mail returned an unexpected error. (S) Cancels processing. (O) Use the return code of the sendmail command to determine the cause of the error. Re-execute the job if needed. KAVT3720-E A required program is missing. (program: program-name) A program necessary for sending mail does not exist. Check whether the sendmail command is provided. (S) Cancels processing.
KAVT3723-E Message Put error. (reason) An attempt was made to output a message, but memory became insufficient. (S) Cancels processing. (O) Check that there are sufficient disk spaces, and then retry. KAVT3801-E Illegal option (-character) exists. You specified an illegal option. (S) Cancels processing. (O) Specify a correct option. KAVT3802-E Value for option (-option) is not specified. A value is not specified for the option. (S) Cancels processing. (O) Specify the necessary option.
KAVT3804-E Invalid value for option (-option). An invalid option was specified. (S) Cancels processing. (O) Specify the correct option. KAVT3805-E Option (-option) appears twice or more. An option was specified more than once. (S) Cancels processing. (O) Specify only one option among the choice of options. KAVT3806-E Monitoring User name not specified. A monitoring user name is missing. (S) Cancels processing. (O) Specify the monitoring user name. KAVT3807-W Retry processing is canceled.
KAVT3810-E I/O error occurred: maintenance-information maintenance-information maintenance-information system-errormessage An I/O error occurred in inputting/outputting a file while executing the mail delivery command. (S) Cancels processing. (O) Check whether: • The system resources are sufficient. • The permission environment of the started user is correct. • The directory created during installation of JP1/AJS3 was deleted inadvertently.
KAVT3821-I Mail Send Command finished. The mail delivery command terminated. (S) Terminates processing. KAVT3822-I Retrying. The mail delivery command retries to create a lock file. (S) Continues processing. KAVT3823-I Read a mail. The mail delivery command reads mail from standard input. (S) Continues processing. KAVT3824-I Wrote a mail. The mail delivery command is written mail into the mail file. (S) Continues processing. KAVT3825-E Failed to access (profile-name).
• Check whether the correct profile name is specified. • Check whether the execution user permissions are set correctly for the profile name. • Check that the jpomailprof command is not being executed. KAVT3826-E Failed to bind (IP-address). (maintenance-information) An attempt to bind IP-address failed. (S) Changes the status of the email sending job to Ended abnormally. (O) Check the following, and then re-execute the job: • Check whether the IP address to be bound is correct.
KAVT3830-E The SMTP server rejected the login. (SMTP-server-name:port, SMTP-AUTH-type)(maintenance-information) The destination SMTP server rejected the login. (S) Changes the status of the email sending job to Ended abnormally. (O) Check the authentication method in the profile, the authentication account name, and the authentication password, and then re-execute the job. KAVT3831-E A timeout occurred during a connection to the POP3 server.
(S) Changes the status of the email sending job to Ended abnormally. (O) Check the authentication method in the profile, the authentication account name, and the authentication password, and then re-execute the job. KAVT3834-E The profile could not be read because it is corrupted. (profile-name)(maintenance-information) The profile cannot be accessed because it is corrupted. (S) Cancels processing. (O) Use the jpomailprof command to delete the profile, and the re-create the profile.
• A timeout occurred during processing of the email sending job. (S) Cancels processing. (O) Check the following, and then re-execute the job: • Check whether the destination domain section is correct. • Check whether TO information is specified for the destination. • Check whether the mail server is running. • Check whether the authentication method set on the mail server is the same as the authentication method defined in the profile. • Check whether memory is sufficient.
(S) Cancels processing. (O) Check the following, and then re-execute the command: • Check whether there is sufficient free space on the disk. • Check whether Administrator permissions are set in the profile. • Make sure that the email sending job is not being executed. KAVT3839-E Failed to delete (profile-name). (maintenance-information) An attempt to delete the profile indicated in (profile-name) failed. (S) Cancels processing.
• Names that begin with a one-byte space symbol. • Names that contain only one period (.) • CON, PRN, AUX, CLOCK$, NUL, COM0, COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9, LPT0, LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, LPT9 KAVT3842-E The profile could not be read because it is corrupted. (profile-name)(maintenance-information) An attempt to read the profile failed because it is corrupted. (S) Cancels processing.
KAVT3845-E An unexpected error occurred. (maintenance-information) (maintenance-information) An unexpected error occurred in the email sending job. (S) Cancels processing. (O) Contact the system administrator. KAVT3846-E The list of attached files could not be acquired. (maintenance-information) Acquiring an attached file list was impossible. (S) Cancels processing. (O) Check the following, and then re-execute the job: • Check whether the attached file list is correct.
The profile indicated in profile-name was not found. (S) Cancels processing. (O) Confirm that the profile name is correct, and then re-execute the command. KAVT3849-E An unexpected error occurred. (maintenance-information) An unexpected error occurred in the command. (S) Cancels processing. (O) Contact the system administrator. KAVT3850-E The SMTP host name cannot be resolved. (host-name)(maintenance-information) The SMTP host name cannot be resolved. (S) Cancels processing.
KAVT3852-E The attached file could not be defined. (maintenance-information) The attached file for the email could not be configured. (S) Cancels processing. (O) Check the following, and then re-execute the command: • Check whether the specified path to the attached file is correct. • Check whether the execution user permissions for the attached file are set correctly. • Make sure that no more than 20 files are specified in the attached file list.
(O) Check whether JP1/AJS3 is installed correctly. KAVT4039-E The TP1 service does not exist. The TP1 service is missing. (S) Cancels processing. (O) Check whether OpenTP1 is installed correctly. KAVT4057-I A message was received. A message was received. (S) Continues processing. KAVT4058-I A message was sent. A message was sent. (S) Continues processing. KAVT4068-E Insufficient memory. (error-code-of-GetLastError) Memory cannot be allocated. (S) Cancels processing.
KAVT4069-E Unable to open message body file. (error-code-of-GetLastError) The message body file could not be opened. (S) Cancels processing. (O) Check whether the correct file is specified. If the correct file is specified, use the error code of GetLastError to determine the cause that prevented the file from being opened, and then take appropriate action. KAVT4070-E Unable to ascertain size of a message body file. (error-code-of-GetLastError) The size of the message body file could not be obtained.
(O) Use the error code of GetLastError and the system error message to determine the cause that prevented the file from being closed, and then take appropriate action. KAVT4075-E Unable to send message. The message could not be sent. (S) Cancels processing. (O) Check whether the correct queue is specified. KAVT4076-E Failed to close the queue. The queue could not be closed. (S) Cancels processing. (O) Check whether the correct queue is specified. KAVT4080-E Unexpected error occurred.
(O) Check whether the MQSeries service is started. KAVT4123-E The MQSeries service does not exist. The MQSeries service does not exist. (S) Cancels processing. (O) Check whether MQSeries is installed correctly. KAVT4124-E The status of the MQSeries service could not be acquired. Acquiring the MQSeries service status was impossible. (S) Cancels processing. (O) Check whether MQSeries is installed correctly. KAVT4125-I The MQSeries service was started. The MQSeries service has started.
KAVT4135-I The processing of message sending will now end. Message sending terminates. (S) Continues processing. KAVT4136-E The parameter is specified incorrectly. The specified parameter is invalid. (S) Cancels processing. (O) Check whether the variable is correct. KAVT4138-E The data is specified incorrectly. (specified-data) The specified data is invalid. (S) Cancels processing. (O) Check whether how to specify the variable is correct. KAVT4139-E A required item is missing.
Reading the configuration definition was impossible. (S) Cancels processing. (O) Check whether JP1/Base and JP1/AJS3 are installed correctly. KAVT4141-E You are not authorized to access the configuration definition. (maintenance-information) The access permission to the configuration definition does not exist. (S) Cancels processing. (O) Handle the system with a privilege to the configuration definition. KAVT4142-E The specified key does not exist in the configuration definition.
KAVT4144-E The send process (process-name) could not be started. (return-value-of-GetLastError) Stating a send process was impossible. (S) Cancels processing. (O) Check whether JP1/AJS3 is installed correctly. If JP1/AJS3 is installed correctly, use the code of GetLastError to determine the cause of the error that prevented the send process from being started, correct the error, and then retry. KAVT4148-E The installation path for JP1/AJS2 was not found. The JP1/AJS3 installation destination is not found.
If it is running, see the documentation for the linked message queue system and determine the cause of the error from the MQSeries error code, and then take appropriate action. KAVT4155-E An error that stops processing occurred during message sending. (MQSeries-error-code) A fatal error that stops processing occurred during the sending of messages. (S) Cancels processing. (O) Check whether the environment is set up to send and receive messages.
KAVT4160-E The queue cannot be opened because the specified remote queue name is invalid. (MQSeries-error-code, errorlocation) Opening a queue was impossible because the remote queue name is invalid. (S) Cancels processing. (O) Check whether the environment is set up to be connected to the remote queue.
Opening a queue was impossible because the transfer queue could not be recognized. (S) Cancels processing. (O) Check whether the queue is specified correctly or the queue is created correctly. If the queue is specified or created correctly, see the documentation for the linked message queue system and determine the cause of the error from the MQSeries error code, and then take appropriate action. KAVT4164-E The queue cannot be opened because the specified remote queue manager program cannot be recognized.
(O) Check whether the queue is specified correctly or the queue is created correctly. If the queue is specified or created correctly, see the documentation for the linked message queue system and determine the cause of the error from the MQSeries error code, and then take appropriate action. KAVT4167-E The queue cannot be opened because the default transfer queue is being used incorrectly.
KAVT4171-E Messages cannot be sent because the message length exceeds the maximum length for the queue. (MQSeries-errorcode) Sending a message was impossible because the message length exceeded the maximum for a queue. (S) Cancels processing. (O) Check the message length to send.
(S) Cancels processing. (O) Check the disk space. KAVT4175-E Messages could not be sent. (MQSeries-error-code) Sending a message was impossible. (S) Cancels processing. (O) Check whether the environment is set up to send and receive messages. KAVT4176-E The message's priority exceeds the maximum. (MQSeries-error-code) The message priority exceeds the maximum you can specify. (S) Cancels processing. (O) Check whether the message priority is specified correctly.
(S) Continues processing. KAVT4179-I A message was sent to the queue. A message was sent to the queue. (S) Continues processing. KAVT4180-E The status of the TP1 service could not be acquired. (error-code) Acquiring the TP1 service status was impossible. (S) Cancels processing. (O) Check whether OpenTP1 is installed correctly. KAVT4181-E The TP1 service is not running. The TP1 service is not running. (S) Cancels processing. (O) Start the OpenTP1 service.
KAVT4183-E The communication pipe with SUP could not be created. (GetLastError-return-code, output-location) Creating a communication pipe with SUP was impossible. (S) Cancels processing. (O) Check whether JPOMQSUP is set up correctly. KAVT4184-E Messages cannot be sent because the message data file could not be opened. (error-code) The system cannot send a message because opening a message data file failed. (S) Cancels processing. (O) Check whether the specification of the message data file is correct.
KAVT4187-E Messages cannot be sent because memory became insufficient. (error-code) The system cannot send a message because a memory shortage occurred. (S) Cancels processing. (O) Check whether memory is sufficient. For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes. KAVT4188-E Messages cannot be sent because memory could not be allocated. (error-code) The system cannot send a message because memory allocation failed. (S) Cancels processing.
(O) Check whether the environment is set up to send and receive messages. KAVT4192-E The queue cannot be opened because the specified remote queue name is invalid. (error-code) Opening a queue is impossible because the specified remote queue name is invalid. (S) Cancels processing. (O) Check whether a correct queue is specified. KAVT4193-E Messages could not be received. (error-code) Receiving a message was impossible. (S) Cancels processing.
(O) Check whether memory is sufficient. For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes. KAVT4197-E Messages cannot be received because memory could not be allocated. (error-code) The system cannot send a message because of the memory allocation problem. (S) Cancels processing. (O) Check whether memory is sufficient. For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.
(S) Cancels processing. (O) Check the disk space. KAVT4201-E Messages cannot be sent because the message length exceeds the maximum length of the queue. (error-code) The system cannot send a message because the message length exceeds the maximum queue length. (S) Cancels processing. (O) Check the message length to send. KAVT4202-E Messages cannot be sent because memory became insufficient. (error-code) The system cannot send a message because there is insufficient memory. (S) Cancels processing.
(S) Cancels processing. (O) Check whether the correct queue is specified. KAVT4205-E The queue cannot be opened because the transfer queue cannot be recognized. (error-code) The system cannot open the queue because the transfer queue cannot be recognized. (S) Cancels processing. (O) Check whether the correct queue is specified. KAVT4206-E The queue cannot be opened because the specified remote queue manager program cannot be recognized.
The system cannot open a queue because the specified queue name or model queue name cannot be recognized. (S) Cancels processing. (O) Check whether the correct queue is specified. KAVT4209-E The queue cannot be opened because the default transfer queue is being used incorrectly. (error-code) The system cannot open a queue because the use of the default transfer queue is invalid. (S) Cancels processing. (O) Check whether the correct queue is specified.
(S) Cancels processing. (O) Start the queue manager. KAVT4213-E The queue could not be re-opened because it was deleted. (error-code) The attempt to reopen the queue was impossible because a queue was deleted. (S) Cancels processing. (O) Check whether the correct queue is specified. KAVT4214-E Messages could not be sent because an error occurred in SUP. (error-code) Sending a message was impossible because an error occurred in SUP. (S) Cancels processing. (O) Check whether JPOMQSUP is set up correctly.
(S) Cancels processing. (O) Check whether the file can be written. KAVT4222-E The queue could not be opened. Opening a queue was impossible. (S) Places the job in the Ended abnormally status if it was an event job, or places the job in the Monitor terminated status if it was a jobnet with start conditions. (O) Take action according to the instructions given by the message "KAVT4419-W An error occurred during an MQSeries access.
(O) Check whether memory is sufficient. For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes. KAVT4232-E The file for storing messages could not be output. Outputting a message storage file was impossible. (S) Cancels processing. (O) Check whether the environment is set up to write a file. KAVT4235-E The queue cannot be opened because the specified remote queue name is invalid.
(S) Cancels processing. (O) Check whether the correct queue is specified. KAVT4238-E The queue cannot be opened because the transfer queue cannot be recognized. Opening a queue is impossible because a transfer queue cannot be recognized. (S) Cancels processing. (O) Check whether the correct queue is specified. KAVT4239-E The queue cannot be opened because the specified remote queue manager program cannot be recognized.
(S) Cancels processing. (O) Check whether the correct queue is specified. KAVT4242-E The queue cannot be opened because the default transfer queue is being used incorrectly. Opening a queue is impossible because the use of the default transfer queue is incorrect. (S) Cancels processing. (O) Check whether the correct queue is specified. KAVT4243-E The queue cannot be opened because the default transfer queue cannot be recognized.
(S) Cancels processing. (O) Start the queue management program. KAVT4246-E Messages cannot be received because memory became insufficient. Receiving a message became impossible because a memory shortage occurred. (S) Cancels processing. (O) Check whether memory is sufficient. For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes. KAVT4247-E Messages cannot be received because memory could not be allocated.
KAVT4249-E The queue could not be disconnected. Disconnecting a queue was impossible. (S) Cancels processing. (O) Check whether the environment is set up to send and receive messages. KAVT4250-E The queue could not be connected. Connection to the queue was impossible. (S) Cancels processing. (O) Check whether the environment is set up to send and receive messages. KAVT4251-E Messages could not be received because an error occurred in the access process.
KAVT4253-E The queue manager program stopped. The queue management program stopped. (S) Cancels processing. (O) Start the queue management program. KAVT4254-E Failed to execute SUP. (error-code) Starting SUP was impossible. (S) Cancels processing. (O) Check whether JP1MQSUP is set up correctly. KAVT4255-E The data length is invalid. (data-name) The character string length is invalid. (S) Cancels processing. (O) Check whether the data is correct. KAVT4256-E The specified file does not exist.
KAVT4257-E The queue could not be opened, so the data was sent to the dead-letter queue instead. Since the queue could not be opened, the data was sent to the dead-letter queue. (S) Cancels processing. (O) Check whether the correct queue is specified and whether messages can be sent to that queue. KAVT4258-E Messages could not be sent, so data was sent to the dead-letter queue instead. (error-code) Since messages could not be sent, the data was sent to the dead-letter queue. (S) Cancels processing.
A request to restart the SUP was accepted. (S) Continues processing. KAVT4401-I JP1/AJS2 message queue monitoring process (TP1/Message Queue) will now start. The JP1/AJS2 message queue monitoring process (TP1/Message Queue) starts. (S) Continues processing. KAVT4402-I The JP1/AJS2 message queue monitoring process (TP1/Message Queue) started. The JP1/AJS2 message queue monitoring process (TP1/Message Queue) has started. (S) Continues processing.
(S) Continues processing. KAVT4406-I The JP1/AJS2 message queue monitoring process (TP1/Message Queue) stopped. The JP1/AJS2 message queue monitoring process (TP1/Message Queue) has stopped. (S) Terminates processing. KAVT4407-I The JP1/AJS2 message queue monitoring process will now stop. (MQSeries) The JP1/AJS2 message queue monitoring process (MQSeries) stops. (S) Continues processing. KAVT4408-I The JP1/AJS2 message queue monitoring process (MQSeries) stopped.
(S) Continues processing. KAVT4411-I The JP1/AJS2 SUP control process will now stop. The JP1/AJS2 SUP control process stops. (S) Continues processing. KAVT4412-I The JP1/AJS2 SUP control process stopped. The JP1/AJS2 SUP control process has stopped. (S) Terminates processing. KAVT4413-I Message Queue System to use it is message-queuing-system-to-use This message indicates the message queuing system to use. (S) Continues processing. KAVT4414-E The message queuing system to be used is not defined.
The message queuing function to be linked has started. (S) Continues processing. KAVT4418-W The message queue function to be linked is stopped. (maintenance-information) The message queuing function to be linked has stopped. (S) Cancels monitoring of the message queue reception, and then resumes monitoring after the message queuing function to be linked is started. (O) No action is required if the message queuing function to be linked stopped according to the schedule.
(S) Continues processing. KAVT4453-I The message queue linkage communication process stopped. The message queue linkage communication process has stopped. (S) Terminates processing. KAVT4454-I The monitoring of message queue reception will now start. The monitoring of message queue reception starts. (S) Continues processing. KAVT4455-E The monitoring of message queue reception will now stop. The message queue reception monitoring is stopped. (S) Cancels processing.
Monitoring of message queue linkage terminates because the time-out period has elapsed. (S) Terminates processing. KAVT4458-I Message Queue System to use it is message-queuing-system-to-use This message indicates the message queuing system to use. (S) Continues processing. KAVT4459-E No message queuing system has been established. Set up the environment. A message queuing system to use is not set. Define the environment settings. (S) Cancels processing. (O) Check the environment settings.
(O) Check whether the macro variable is correct. KAVT4462-W A macro variable exceeds 4096 bytes. Some macro variables could not be created. A macro variable exceeds 4,096 bytes and some could not be created. (S) Cancels processing. (O) Decrease the number of macros to be specified. KAVT4464-W A service of the message queuing system is not running. The message queuing system service is not started. (S) Cancels processing. (O) Starts the OpenTP1 or MQSeries service.
KAVT4467-E Memory became insufficient. A memory shortage occurred. (S) Cancels processing. (O) Check whether memory is sufficient. For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes. KAVT4468-E An event for canceling registration of a job could not be created. Creating an event for job registration cancellation was impossible. (S) Cancels processing. (O) Check whether the environment is set up to send and receive messages.
KAVT4471-W The JP1/AJS2 message queue monitoring process is not running. The JP1/AJS2 message queue monitoring process is not running. The system waits until the process can run. (S) Cancels processing. (O) Determine the cause of the error from the error message output before this one, and take appropriate action. KAVT4472-I The startup of the JP1/AJS2 message queue monitoring process was confirmed. The JP1/AJS2 message queue monitoring process started. (S) Continues processing.
A message was received. (S) Continues processing. KAVT4502-E The message queue will not be linked. The message queue linkage is not performed. (S) Suspends the message-queue message reception monitoring process. (O) Use the JP1/AJS3 internal log to determine the cause of the error, and then restart JP1/AJS3 as required. KAVT4503-E Message queue linkage cannot start. (maintenance-information, cause-of-error) The message queue linkage cannot start. (S) Terminates the message queue monitoring process.
KAVT4506-I The message queue monitoring process will now be suspended. The message queue monitoring process is suspended. (S) Terminates processing. KAVT4507-E The argument when the message queue monitoring process was called is invalid. The argument is invalid when calling the message queue monitoring process. (S) Terminates the message queue monitoring process. (O) Contact the system administrator.
KAVT4517-E An internal table could not be created because of insufficient memory: maintenance-information Creating an internal table was impossible because of insufficient memory. (S) Suspends the message queue monitoring process. (O) Check whether memory is sufficient. If memory is insufficient, allocate memory, and then restart JP1/AJS3. For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes.
KAVT4524-E The temporary file for storing messages (temporary-file-name) could not be written to: (maintenanceinformation, system-error-message) Writing a temporary file for message storage was impossible. (S) Transfers a message to the undeliverable queue (the dead letter queue). (O) Check the cause of the error from the system error message. Then take action. KAVT4525-E The file (file-name) could not be closed: (maintenance-information, system-error-message) Closing a file was impossible.
(O) Contact the system administrator. KAVT4528-E An error occurred in the processing of synchronous multi-I/O: (maintenance-information, system-error-message) An error occurred in the synchronous multiple processing of input or output. (S) Terminates the message queue monitoring process. (O) Check the cause of the error from the system error message. Then take action. KAVT4529-E Invalid data was written to the pipe: (maintenance-information) maintenance-information Pipe data is invalid.
(O) Use the system error message to determine the cause of the error, and then take action. Restart JP1/AJS3 as required. KAVT4532-E The pipe could not be opened: pipe-name (maintenance-information, system-error-message) Opening a pipe was impossible. (S) Suspends the message queue monitoring process. (O) Use the system error message to determine the cause of the error, and then take action. Restart JP1/AJS3 as required.
(O) Check the cause of the error from the system error message. Then take action. KAVT4536-E There is no reply to the pipe contact: maintenance-information The system does not respond to the pipe report. (S) Suspends the message queue monitoring process. Continues processing at the next monitoring interval. (O) Check the status of the prerequisite message queuing system. KAVT4537-E The reply-wait failed: (maintenance-information, system-error-message) Waiting for a response was impossible.
(O) Use the system error message to determine the cause of the error, and then take action. Restart JP1/AJS3 as required. KAVT4540-W The transaction process failed, but SUP continues: name-of-SUP-function-with-error return-code-SUP-functionwith-error Processing of a transaction was impossible, but SUP continues. (S) Cancels the current processing, and then continues the next processing. (O) Investigate the cause of the error from the SUP function name and return value where an error occurred.
(S) Suspends the message queue monitoring process. (O) Investigate the cause of the error from the error message when issuing the startup command. Then take action to correct the error. KAVT4547-I Messages are sent to the queue (queue-name). Messages are sent to the queue. (S) Continues processing. KAVT4548-E The value for option (option) is invalid. The option value has an error. (S) Cancels the transmission of the message queue.
(O) Specify only once the option that was specified more than once, and then re-execute the transmission of the message queue. KAVT4551-E No value is specified for the option (option). A value is not specified for the option that needs a value. (S) Cancels the transmission of the message queue. (O) Specify an option value, and then re-execute the transmission of the message queue.
(O) Check the cause of the error from the system error message. Then take action. KAVT4555-E The file(file-name) could not be closed: (maintenance-information, system-error-message) Closing a file was impossible. (S) Continues the transmission of the message queue. (O) Check the cause of the error from the system error message. Then take action. KAVT4556-E Memory became insufficient: maintenance-information A memory shortage occurred. (S) Cancels the transmission of the message queue.
(S) Continues processing. KAVT4559-W The specified dynamic queue (queue-name) already exists. The existing queue will be opened. The existing queue is opened because a queue having the same name as the specified dynamic queue already exists. (S) Sends a message to the existing queue. (O) Check the queue status. KAVT4560-E An error occurred in the message queuing system: queue-name MQI-call-name reason-code-from-MQI-call maintenance-information An error occurred while processing a message queuing system.
The system resources that are usable are insufficient. (S) Cancels processing. If an undeliverable queue (a dead letter queue) is specified, sends the message to the undeliverable queue (the dead letter queue), and then cancels the transmission of the message queue. (O) Check the MQRC_RESOURCE_PROBLEM error for the MQI call of MQSeries or TP1/Message Queue and take action.
(O) Check the return value for the MQI call of MQSeries or TP1/Message Queue and take action to make the connection. KAVT4566-E Object(queue-name) in the message queuing system was destroyed: MQI-call-name maintenance-information The object was destroyed. (S) Cancels processing. If an undeliverable queue (a dead letter queue) is specified, sends the message to the undeliverable queue (the dead letter queue), and then cancels the transmission of the message queue.
(S) Cancels processing. If an undeliverable queue (a dead letter queue) is specified, sends the message to the undeliverable queue (the dead letter queue), and then cancels the transmission of the message queue. (O) Check the MQRC_PUT_INHIBITED error for the MQI call of MQSeries or TP1/Message Queue and take action. KAVT4570-E The queue(queue-name) was deleted: MQI-call-name maintenance-information A queue was deleted. (S) Cancels processing.
KAVT4573-E The message could not be sent to the queue (queue-name) because there is no more disk space free for that queue: MQI-call-name maintenance-information Sending message is impossible because there is no space for a queue on the disk. (S) Cancels the transmission of the message queue. If an undeliverable queue (a dead letter queue) is specified, sends the message to the undeliverable queue (the dead letter queue), and then cancels the transmission of the message queue.
KAVT4576-E An error occurred during sending of the message to the dead-letter queue (queue-name): processing-name reasoncode-from-MQI-call-(when-processing-name-is-MQI-call-name) -or-maintenance-information-(for-other-cases) An error occurred in the message send processing to the undeliverable queue (the dead letter queue). (S) Cancels processing.
KAVT4582-E The process could not be started: (maintenance-information, system-error-message) Starting a process was impossible. (S) Suspends the message queue monitoring process. (O) Check the cause of the error from the system error message. Then take action. KAVT4583-E The pipe could not be opened: pipe-name (maintenance-information, system-error-message) Opening a pipe was impossible. (S) Cancels processing. (O) Check the cause of the error from the system error message. Then take action.
KAVT4586-E The pipe could not be closed: pipe-name (maintenance-information, system-error-message) Closing a pipe was impossible. (S) Continues processing. (O) Check the cause of the error from the system error message. Then take action. KAVT4587-E There is no reply to the pipe contact: maintenance-information No response is provided to pipe contact. (S) Cancels processing. (O) Contact the system administrator.
KAVT4590-E After the process started, waiting for the replay failed: (maintenance-information, system-error-message) Waiting for a response was impossible after starting a process. (S) Suspends the message queue monitoring process. (O) Check the cause of the error from the system error message. Then take action. KAVT4591-E The process could not be created: (maintenance-information, system-error-message) Creating a process was impossible. (S) Cancels the transmission of the message queue.
KAVT4596-E The transaction process failed, but SUP continues: SUP-function-name-with-error return-value-of-SUP-functionwith-error Processing a transaction was impossible, but SUP continues. (S) Cancels the current processing and continues the next processing. (O) Check the cause of the error from the SUP function names where an error occurred and the return value. Then take action to correct the error.
KAVT4632-E There is not configuration definitions right to access to information. (return-code) The privilege of the user is invalid to access the configuration definitions. (S) Cancels processing. (O) A user who sends or receives messages does not have permission to access the JP1/AJS3 information. Log on as a user who has the access permission. KAVT4633-E Specification key does not exist in configuration definitions information. (return-code) The configuration definitions are missing.
• Check whether the privilege of the user is valid. • Check whether the directory created at JP1/AJS3 installation was unintentionally deleted. KAVT4664-E Failed to send Pipe Data (maintenance-information) (maintenance-information) Unable to send pipe data to the agent. (S) Cancels sending the pipe data and continues processing. The status of job execution may be incorrect. (O) Check the following: • Check whether system resources are sufficient. • Check whether the privilege of the user is valid.
An error occurred during the analysis of the macro variable. (S) Abnormally terminates the job without creating the macro variable. (O) Re-execute the job as required. KAVT4682-W Length of a macro value exceed 4096 bytes. The macro variable exceeded 4,096 bytes after conversion. (S) The length of the macro variable exceeded 4,096 bytes after conversion. Truncates the subsequent macro variables and continues processing. (O) The macro variables that has been truncated are not inherited.
KAVT4685-W Definitions parameter (parameter) is not specified. The required parameter is missing. (S) Terminates the job. (O) Check whether the job is defined correctly. KAVT4687-E There was an error in the prerequisite program. An environment may be set incorrectly for linking the prerequisite program, or the prerequisite program may not be installed. (S) Terminates the transmission of the message queues.
KAVT4690-I Stop request was accepted. A stop request was accepted. (S) Requests to terminate the message queue monitoring. KAVT4691-I Ended normally.: process-name queue-name maintenance-information) The process indicated by process-name succeeded. (S) Continues processing. KAVT4692-I Queue (queue-name) is opened again. The MQRC_Q_DELETE or MQRC_OBJECT_CHANGED error occurred during the MQI call of MQSeries or TP1/ Message Queue. The queue is opened again. (S) Continues processing.
KAVT4695-E Sending of the message queue is unusable. Unable to send a message queue. (S) Cancels the transmission of the message queue. (O) Check whether the environment is set up for using the message queue linkage. KAVT4696-I The MQSeries process stopped. The MQSeries process stopped. (S) Continues processing. KAVT4697-I The SUP stopped. The SUP stopped. (S) Continues processing. KAVT4698-W The message queue monitoring process will now be retried.
(S) Continues processing. KAVT4700-E The processing of the message queue monitor process did not finish.: retry-count The message queue monitoring did not terminate. (S) Continues processing. (O) Recheck the response time and the retry count of the message queue monitoring. Also, stop JP1/AJS3, and terminate the jpocwtmqmaii and jp1mqsup processes. Then, restart JP1/AJS3. KAVT4701-W The status report of the message queue monitoring process failed.
(S) Cancels command processing. (O) Specify an option, and then re-execute the command. KAVT4953-E An invalid option is specified. An invalid option is specified. (S) Cancels command processing. (O) Specify the correct option, and then re-execute the command. KAVT4954-I A SUP stop was requested. The termination of SUP was requested. (S) Continues processing. KAVT4955-E SUP could not be stopped. Requesting to stop SUP was impossible. (S) Cancels command processing.
KAVT4957-E SUP could not be restarted. Restarting SUP was impossible. (S) Cancels command processing. (O) Check the cause of the error from the error message issued for the startup command. Then take action. KAVT4958-E The pipe could not be opened: pipe name: pipe-name (error-number, error-message) Opening a pipe was impossible. (S) Cancels command processing. (O) Check the cause of the error from the error message and take action.
Closing a pipe was impossible. (S) Continues processing. (O) Check the cause of the error from the system error message. Then take action. KAVT4962-E For execution, you must have permissions. The privilege of the user is invalid to execute the command. (S) Cancels processing. (O) Check the permission of the logged-in user, and then retry. KAVT5251-I The processing of MSMQ sending will now start. The transmission of the MSMQ starts. (S) Starts processing.
(O) Specify necessary items. KAVT5254-E The parameter is specified incorrectly. (data-specified-in-environment-variable) The specified parameter is invalid. (S) Cancels processing. (O) Specify necessary items. KAVT5255-E The data is specified incorrectly. (data-checked-for-character-string) The specified data is incorrect. (S) Cancels processing. (O) Specify necessary items. KAVT5256-E A required item is not designated. A required item is missing. (S) Cancels processing. (O) Specify necessary items.
(O) Start the MSMQ service. KAVT5265-E The MSMQ service does not exist. (service-status-code) The MSMQ service does not exist. (S) Cancels processing. (O) Install MSMQ. KAVT5266-E Information about the MSMQ service could not be acquired. (service-status-code) Acquiring the MSMQ service status was impossible. (S) Cancels processing. (O) Check whether the MSMQ service is running normally. KAVT5267-E The MSMQ server is not connected. Connection to the MSMQ server is impossible. (S) Continues processing.
(O) Check whether the MSMQ server is connected to MSMQ of the JP1/AJS3 - Agent machine. KAVT5269-E Message sending will now stop because an error that stops processing occurred. The system cancels sending a message because a fatal error that stops processing occurred. (S) Cancels processing. (O) Check whether the MSMQ service is running normally. KAVT5272-E The queue with the specified queue label name was not found. The queue in the queue label name is missing. (S) Cancels processing.
(O) Check the queue access permission. KAVT5275-E The queue could not be closed. (return-value-of-MQ-function) Closing a queue was impossible. (S) Continues processing. (O) Check whether sending or receiving a message terminated. KAVT5276-E The format name could not be acquired from the path name of the queue. (return-value-of-MQ-function) Acquiring a format name from the queue path name was impossible. (S) Cancels processing. (O) Check whether the queue path name is correct.
(O) Check whether the queue label name is correct. KAVT5279-E An error occurred during an MSMQ access. (MQLocateNext) (return-value-of-MQ-function) An error occurred during the accessing of MSMQ. (S) Cancels processing. (O) Check whether the MSMQ service is running normally. KAVT5280-E An error occurred during an MSMQ access. (MQLocateEnd) (return-value-of-MQ-function) An error occurred during the accessing of MSMQ. (S) Cancels processing. (O) Check whether the MSMQ service is running normally.
(O) Check whether the MSMQ service is running normally. KAVT5287-E Message Reception Monitoring Interval is assumed because registry information was not acquired successfully. Since the registry information could not be acquired, the interval for the message reception monitoring is assumed. (S) Assumes the default interval of the message reception monitoring and continues processing. (O) Determine the cause of the error preventing you from acquiring the registry information.
(O) Check whether memory is sufficient. For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes. KAVT5294-E The message text file could not be read. Reading a message text file was impossible. (S) Cancels processing. (O) If memory is not enough, allocate memory. Otherwise, check the file status. KAVT5295-E The message text file could not be closed. Closing a message text file was impossible. (S) Continues processing. (O) Check the file status.
(S) Cancels processing. (O) Check the variable, and then retry. KAVT5308-E The registry information could not be acquired. (ErrCode=ErrorCode-number, GetLastErrorCode=GetLastErrornumber) Acquiring the registry information was impossible. (S) Assumes a value and continues processing. (O) Check whether the registry information is correct. KAVT5309-I Message Reception Monitoring Interval is assumed because registry information was not acquired successfully.
KAVT5312-E Messages cannot be received because an error that stops processing occurred. (ErrCode=ErrorCode-number, GetLastErrorCode=GetLastError-number) A fatal error that stops processing occurred. (S) Cancels processing. (O) Check the content of the previous message. KAVT5313-E An error occurred in the end processing. (ErrCode=ErrorCode-number, GetLastErrorCode=GetLastErrornumber) An error occurred in a termination. (S) Continues processing. (O) Check the file or queue status.
KAVT5338-E Message reception will now end because an error that stops processing occurred. (ErrCode=ErrorCode-number, GetLastErrorCode=GetLastError-number) The message reception terminates because a fatal error that stops processing occurred. (S) Cancels processing. (O) Check the content of the previous message. KAVT5339-I Although notification of Monitoring Interval failed, the message continued to be received.
KAVT5343-E The entered code is invalid. (ASCII) (ErrCode=ErrorCode-number, GetLastErrorCode=GetLastError-number) The input code is invalid. (ASCII) (S) Cancels processing. (O) Check the code. KAVT5344-E The entered code is invalid. (EBCDIC) (ErrCode=ErrorCode-number, GetLastErrorCode=GetLastError-number) The input code is invalid. (EBCDIC) (S) Cancels processing. (O) Check the code. KAVT5345-E The entered code is invalid.
KAVT5352-E Terminating because the pipe connection thread did not end. (ErrCode=ErrorCode-number, GetLastErrorCode=GetLastError-number) Some internal threads did not terminate during the termination of the MSMQ monitoring. Forcibly terminates the internal threads. (S) Continues processing. (O) If the system outputs this message during the termination of JP1/AJS3, check whether the MSMQ reception monitoring works normally at the next start of JP1/AJS3.
KAVT5364-E There is no message: Maintenance-information No message exists. (S) Continues monitoring. (O) Check whether the monitoring conditions are correct if a message is sent to the monitoring queue. KAVT5367-E Initialization failed. (ErrCode=ErrorCode-number, GetLastErrorCode=GetLastError-number) Initialization failed. (S) Cancels processing. (O) Restart the service and the OS. KAVT5368-E There was an error in the prerequisite program.
KAVT5372-E Messages could not be received because the queue could not be opened. (ErrCode=ErrorCode-number, GetLastErrorCode=GetLastError-number) The system could not receive a message because opening a queue was impossible. (S) Cancels processing. (O) Check the queue path name and access permission. KAVT5373-E An error occurred during message reception. (ErrCode=ErrorCode-number, GetLastErrorCode=GetLastErrornumber) An error occurred during the reception of a message. (S) Cancels processing.
(O) Check the queue status. KAVT5377-E The queue was deleted. (ErrCode=ErrorCode-number, GetLastErrorCode=GetLastError-number) A queue was deleted. (S) Closes and reopens a queue, and then continues monitoring. (O) Use the MSMQ explorer to create a queue. KAVT5378-E The MSMQ service is not running. (ErrCode=ErrorCode-number, GetLastErrorCode=GetLastError-number) The MSMQ service is not running. (S) Continues processing. (O) Start the MSMQ service. KAVT5379-E The MSMQ server cannot be connected.
(S) Cancels processing. (O) Check whether memory is sufficient. For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes. KAVT5381-E Message could not be received because an error that stops processing occurred during message reception. A fatal error that stops processing occurred during the reception of the message. (S) Cancels processing. (O) Check the content of the previous message. KAVT5382-E The file for storing messages could not be output.
KAVT5384-E An error occurred during an MSMQ access. (MQCreateCursor). (ErrCode=ErrorCode-number, GetLastErrorCode=GetLastError-number) An error occurred during the accessing of MSMQ. (S) Cancels processing. (O) Check the queue status. KAVT5385-E The inherited information file could not be output. (ErrCode=ErrorCode-number, GetLastErrorCode=GetLastError-number) Outputting an inheritance information file was impossible. (S) Cancels processing. (O) Check whether there is sufficient disk space.
KAVT5453-I The MSMQ linkage communication process stopped. The MSMQ linkage communication stopped. (S) Terminates processing. KAVT5454-I The MSMQ reception monitoring will now start. The MSMQ reception monitoring starts. (S) Terminates processing. KAVT5455-E The MSMQ reception monitoring will now stop. The system stops the MSMQ reception monitoring. (S) Cancels processing. (O) See the message output before this message to examine the cause of the error.
KAVT5461-W An error occurred during creation of a macro variable. An error occurred during creation of a macro variable. (S) Continues processing. (O) Check whether the macro variables to be taken over are correct. KAVT5462-W A macro variable exceeds 4096 bytes. Some macro variables could not be created. The number of bytes used in macro variables reached 4096. The system failed to create some macro variables. (S) Continues processing. (O) Check whether the macro variables to be taken over are correct.
The job for the MSMQ reception monitoring is defined incorrectly. (S) Cancels processing. (O) Check the definition of the job. KAVT5467-E Memory became insufficient. Memory became insufficient. (S) Cancels processing. (O) Check whether memory is sufficient. For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in Release Notes. KAVT6001-I The JP1 event send command has started. The JP1 event send command starts. (S) Continues processing.
(O) Check the definitions to see if an event ID is specified. When an event ID is specified, contact the system administrator. KAVT6004-E An error occurred in the event service. (return-code-of-jevsend-command) An error occurred in the event service. (S) Cancels processing. (O) Find the cause of the error from the return code of the jevsend command, correct the error, and then retry. KAVT6005-E The installation path of JP1/Base could not be obtained.
(S) Cancels processing. (O) Check whether JP1 events can be sent in the current environment. Check also whether a problem has occurred in the JP1/Base event service. KAVT6101-E Confirmation of JP1 event arrival was not possible. The system checked JP1 event arrival for the specified number of times, but it could not confirm the arrival of any JP1 event. (S) Cancels processing. (O) Check whether JP1 events can be sent in the current environment.
(S) Cancels processing. (O) Check whether the network settings are correct and whether the host name is specified correctly. If you cannot solve the problem, specify the event transmission destination host and then re-execute the operation. KAVT7001-I Timer monitoring process will now start. The execution interval control process will now start. (S) Continues processing. KAVT7002-I Timer (timer-value min) monitoring will now start. The timer monitoring starts. (S) Continues processing.
KAVT7005-W The time-out period elapsed. A timeout occurred. The system cancels executing the job. (S) Cancels processing. KAVT7006-W A kill request was accepted. The system received a request to terminate the job forcibly, so it terminates the job forcibly. (S) Cancels processing. KAVT7007-E Timer monitoring process ended. (maintenance-information) The execution interval control process terminated because it detected an error.
KAVT7009-E Memory became insufficient. (maintenance-information) Memory became insufficient. The job terminates. (S) Terminates the job abnormally due to insufficient memory. (O) Check whether there is sufficient memory for executing the program. Then, use JP1/AJS3 - View to examine the event job that caused the error, and then re-execute that job. KAVT7010-E An attempt to start the timer monitoring process failed.
(S) An error occurred during inter-process communication with the agent. The system terminates the execution interval control process depending on the location where the error occurred. If this process is terminated, the Interval Control job cannot be monitored. The Interval Control job may have failed to detect an event. (O) Check whether the system resources are sufficient and whether the directory created at JP1/AJS3 installation was unintentionally deleted.
(S) Sufficient resources for performing the next monitoring are not available. The system abnormally terminates the Interval Control job. (O) Check the following: • Check whether system resources are sufficient. After the check, use JP1/AJS3 - View to check the event job that caused the error, and then re-execute that job. KAVT7016-W A macro variable exceeds 4096 bytes. A converted macro variable has exceeded 4,096 bytes. (S) Truncates the portion after the 4,096th byte and continues processing.
KAVT7502-E Invalid environment variable specification. (specified-environment-variable) An incorrect parameter is specified in the hp OpenView Status Report job. (S) Cancels processing. (O) Check the definition of the specified parameter, and then retry. KAVT7503-E Invalid data specification. (specified-data) An incorrect parameter is specified in the hp OpenView Status Report job. (S) Cancels processing. (O) Check the definition of the specified parameter, and then retry.
(S) Cancels processing. (O) Install the SNMP service. KAVT7509-E Could not report status. SNMP service is not started. The job failed to report the status because the SNMP service was not started. (S) Cancels processing. (O) Start the SNMP service. KAVT7510-E Could not report status. SNMP service community name is not established. The job failed to report the status because the community name for the SNMP service was not specified. (S) Cancels processing.
(S) Cancels processing. (O) If the code indicated in code-for-status-report-error is 10, check whether the hp OpenView Status Report job was executed by a JP1 user with superuser privileges. If the code is other than 10, contact the system administrator. KAVT7513-E Error in status specification. (string-specified-as-status) An incorrect status is specified. (S) Cancels processing. (O) Specify a correct status. KAVT7514-I The status was reported.
(S) Starts processing. KAVT8002-I The common environment definition command will now end. The common environment definition command terminates. (S) Terminates the command. KAVT8003-E The parameter is specified incorrectly. An incorrect parameter is specified. (S) Cancels processing. (O) Specify correct definition parameters, and then retry. KAVT8004-E The environment variable is specified incorrectly. (specified-environment-variable) An incorrect environment variable is specified. (S) Cancels processing.
KAVT8007-E The configuration definition could not be read. (error-code) The system failed to write the configuration information. (S) Cancels processing. (O) Check whether the user has the superuser privilege. KAVT8008-E A required item is missing. A required item is not specified. (S) Cancels processing. (O) Check whether all the required items are specified. KAVT8009-I The mail linkage setting was canceled. The settings for the mail linkage were canceled. (S) Terminates the command.
You are not authorized to access the configuration definition. (S) Cancels processing. (O) Check whether the environment is set up to access the configuration information, and then retry. KAVT8012-E The specified key does not exist in the configuration definition. (error-code) The specified key does not exist in the configuration definition. (S) Cancels processing. (O) Check whether JP1/AJS3 is correctly installed. KAVT8013-E An unexpected error occurred. (error-code) An unexpected error occurred.
(S) Terminates the command. KAVT8016-I The MSMQ environment setting command will now start. The command to set the environment of MSMQ starts. (S) Continues processing. KAVT8017-I The MSMQ environment setting command will now end. The command to set the environment of MSMQ terminates. (S) Terminates the command. KAVT8018-I The mail environment setting command will now start. The command to set the mail environment starts. (S) Continues processing.
(S) Cancels processing. (O) Check whether the data can be used in the current platform, and then retry. KAVT8021-E Environment setup did not end normally. The setup of the environment terminated abnormally. (S) Terminates the command. (O) See the message output before this message to examine the cause of the error. KAVT8022-E For execution, you must have Administrator permissions. The command must be executed by a user who has Administrator permissions. (S) Cancels processing.
KAVT8025-E The data length is invalid. (error-code) The data length is incorrect. (S) Cancels processing. (O) Check whether the data length is within the specifiable range. KAVT8026-E Memory became insufficient. (Maintenance-information) Memory is insufficient. (S) Cancels processing. (O) Get enough memory to process and re-execute. KAVT8027-E The data length is invalid.(option)(maintenance-information) The data length is incorrect. (S) Cancels processing.
KAVT8301-I The command terminated normally. Listing terminated normally. (S) Terminates command execution. KAVT8302-W The command terminated abnormally. The command terminated abnormally due to an error. (S) Terminates command execution. (O) See the message output before this message to examine the cause of the error and correct it. Then, re-execute the command. KAVT8303-E Value for option (option) is not specified. A value is missing for the option that needs a value. (S) Cancels command execution.
KAVT8305-E Invalid value for option (option) The option contains an invalid value. (S) Cancels command execution. (O) Correct the value for the option, and then re-execute the command. KAVT8306-E Option (option) appears twice or more. The same option is specified more than once. (S) Cancels command execution. (O) Specify the option only once, and then re-execute the command. KAVT8307-E Cannot specify these options together. You specified the options that could not be used simultaneously.
KAVT8310-W Because the data was long, the data was truncated and then displayed. (data-truncated (up-to-900-bytes)) (nameof-the-item-displayed) The data to be displayed was unexpectedly long. The data is truncated and then displayed. (S) Continues command execution. (O) Check whether JP1/AJS3 runs correctly. KAVT8311-W The deleting of files failed. (maintenance-information) The work file could not be deleted during termination. (S) Continues command execution.
(S) Continues command execution. The system cannot display the name of the appropriate job and its jobnet name. (O) Check the following: • Check whether system resources are sufficient. • Check whether the privilege of the user is valid. • Check whether the directory created at JP1/AJS3 installation was unintentionally deleted. • If maintenance is in progress, wait until the maintenance finishes and then re-execute the command. KAVT8314-E An error occurred during communication with the agent.
KAVT8316-E An error occurred during the access of the agent information file. (error-code) (function-name) (maintenanceinformation) An error occurred while accessing (opening, etc.) the information file of the agent. (S) Cancels command execution. (O) Check the following: • Check whether system resources are sufficient. • Check whether the privilege of the user is valid. • Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.
KAVT8320-E The host name could not be obtained. (error-code) (function-name) (maintenance-information) The host name could not be obtained. (S) Cancels command execution. (O) Check the following: • Check whether system resources are sufficient. • Check whether the privilege of the user is valid. • Check whether JP1/AJS3 and JP1/Base have been installed correctly. • Check whether the environment of JP1/AJS3 and JP1/Base have been set correctly. KAVT8321-E The installation path could not be acquired.
• Check whether the environment of JP1/AJS3 and JP1/Base have been set correctly. KAVT8323-E The registration file could not be read. (path-name) (function-name) (maintenance-information) The registration file could not be read. (S) Cancels command execution. (O) Check the following: • Check whether system resources are sufficient. • Check whether the privilege of the user is valid. • Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.
KAVT8327-W There is no data so data cannot be displayed. (name-of-the-item-displayed) (maintenance-information) There is no data of the requested value. The data cannot be displayed. (S) Continues command execution. (O) Check whether the JP1/AJS3 service has been started or whether maintenance is being performed on the service. KAVT8328-E There is no specified host name. (host-name) (function-name) There is no host name that is specified by the -h operand or the JP1_HOSTNAME environment variable.
• jpomanjobshow (S) Cancels command execution. (O) Check the following, and then re-execute the command: • Check whether system resources are sufficient. • Check whether the privilege of the user is valid. • Check whether the directory created at JP1/AJS3 installation was unintentionally deleted. • Check whether an attempt was made to concurrently execute more than one command with the same name. • For a cluster system, check whether the command was executed on the standby node.
KAVT8333-E The agent is not running. The agent has not been started. (S) Cancels command execution. (O) Check whether the agent has been started. Restart JP1/AJS3 as required. For a cluster system, make sure that the command is not executed in the standby system, and then re-execute the command in the active system. KAVT8334-E The manager name storage file could not be created. (error-code) (function-name) (maintenance-information) The manager name storage file could not be created or written into.
(S) Lists the event jobs (the system may not display some data), and then abnormally terminates the command. (O) Use the integrated trace log to determine the cause of the error which prevented the information to be written and take action to correct it. KAVT8337-W Some monitoring process information could not be written. (monitoring-process-name) Some information about the monitoring process could not be written. (S) Continues command execution. The system may not display Status correctly.
KAVT8340-E The main loop of the jpoagtjobshow command failed. (maintenance-information) The main loop of the jpoagtjobshow command could not be started. (S) Cancels command execution. (O) Check whether the system resource is sufficient or the privilege of the user is valid. Then, retry. KAVT8341-E This command cannot be executed because the JP1/AJS2 service is running. This command cannot be executed because the target JP1/AJS3 scheduler service is running. (S) Cancels execution of the command.
• If you did not specify the -s option, information may still remain on the agent. Perform a cold start manually for JP1/AJS3 on the agent. jpomanevshow command Check the following and then re-execute the command: • Check whether the system resources are sufficient. • Check whether the permission environment of the starting user is correct. • Check whether the directory created during installation of JP1/AJS3 was deleted unintentionally. KAVT8343-W An attempt to communicate with the agent has failed.
KAVT8351-E Specified Scheduler service not exist (scheduler-service-name)(maintenance-information). The scheduler service specified for the -F operand or the DEFAULTSERVICENAME environment setting parameter does not exist. (S) Cancels command execution. (O) Check whether: • The scheduler service specified in the -F option, AJSCONF environment variable, or DEFAULTSERVICENAME environment setting parameter exists on the host specified for the -h option. • The JP1/AJS3 environment settings are correct.
KAVT8402-E The reading of requests from the jpoagtjobshow command failed. (return-code) Requests could not be read from the pipes for the jpoagtjobshow command. (S) Continues processing. The system cannot provide the information for the jpoagtjobshow command. (O) Check the following: • Check whether system resources are sufficient. • Check whether the privilege of the user is valid. • Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.
KAVT8405-E The reporting of information to the jpoagtjobshow command failed. (return-code) Pipes could not be written into the jpoagtjobshow command. (S) Continues processing. The system cannot provide the information for the jpoagtjobshow command. (O) Check the following: • Check whether system resources are sufficient. • Check whether the privilege of the user is valid. • Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.
KAVT8410-E An attempt to obtain the environmental setting parameter information failed.(return-code)(line-number) An attempt to obtain environment setting parameter information has failed. (S) Cancels command execution. (O) Check the following, and then re-execute the command: • Check whether the environment setting parameters for JP1/AJS3 and JP1/Base are specified correctly. • Check whether memory is sufficient. If memory is insufficient, see 3.
(S) Cancels command execution. (O) Check the following, and then re-execute the command: • Check whether the directory created by JP1/AJS3 during installation has been improperly deleted. • Check whether memory is sufficient. If memory is insufficient, see 3. Estimates in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide, and make sure that the required amount of memory has been allocated. KAVT8415-E An attempt to move the file failed.
2. Cold start the JP1/AJS3 service. For details on the jpomanevreset command, see jpomanevreset in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1. KAVT8417-W An attempt to back up an invalid file failed.(filename=file-name)(return-code)(line-number) When the KAVT8416-W message was output, an attempt to rename the file with an invalid data format to a name suffixed with _bak failed. (S) Continues migration processing.
Appendixes Job Management Partner 1/Automatic Job Management System 3 Messages 1 786
A. Version Revisions This appendix lists the changes in each version of the JP1/AJS series programs. A.1 Revisions in 10-00 The following lists the revisions in 10-00 for each program. (1) JP1/AJS3 - Manager • IPv6 addresses are now supported for communication. • Mirroring by copying a disk is now supported to enable disaster recovery operations.
• The embedded database settings file is now generated when an embedded database is set up. If this file is specified when the ajsembdbbuild command is used to build another embedded database, the other embedded database will be set up with the settings in the file. • Execution user name and Execution time have been added as extended attributes that can be output for JP1 events (specific information) so that JP1 events indicating job termination can be used as job operating information.
(3) JP1/AJS3 - View • The Wait Conditions Settings List window and the Wait Conditions Statuses window have been added as means for managing units with wait conditions and units whose end is being waited for. • A dialog box which lists temporary change operations that have already been performed and which allows users to re-execute (re-apply) specific temporary change operations has been added.
• Because of the user authentication function added in JP1/AJS3 - Definition Assistant 09-10, specifying the JP1 user name is now mandatory for starting JP1/AJS3 - Definition Assistant from JP1/AJS3 - View. With this specification change, User name has been added as an item that can be selected from the Replace drop-down list in the Tool Entry dialog box. • Windows 8 has been added as platforms supported by JP1/AJS3 - View. • Windows Server 2012 has been added as platforms supported by JP1/AJS3 - View.
• NotificationRetryInterval • NotificationRetryCount • ClientConnectTimeout • A function has been added to support end delay monitoring based on how long a job takes to execute. • The jobnet connector functionality has been enhanced to enable control of the execution order of root jobnets managed by different scheduler services.
• A jobnet release function has been added for replacing the definition of a jobnet that is registered for execution with another definition. • Function menus have been added to the JP1/AJS3 - View window to facilitate task-oriented operation. • The JP1/AJS3 - View window (Summary Monitor window) has been added. In this window, you can view the progress of jobnets and other information.
A.3 Revisions in 08-00 The following lists the revisions in 08-00 for each program. (1) JP1/AJS2 - Manager • The recommended values for the environment settings are now set during installation and setup. • A Monitoring Files job can now monitor files larger than 2 gigabytes (large files). • The ajsstatus command can now output the connection status of JP1/AJS2 - View.
• Judgment jobs can now perform variable judgment. • A function has been added that suppresses jobnet executions that follow an abnormally terminated jobnet and that will be started when their start conditions are satisfied. • A definition pre-check function has been added for conducting a final check before starting production in the production environment after the unit definitions are migrated from the development environment.
• All the detailed processes of the event action function can now be stopped to terminate the agent process for the event action function if any of the detailed processes have terminated upon receiving a signal. • A function has been added that performs a synchronized write when updating event job information or the wait information file. (3) JP1/AJS2 - View • Macro variables can now be used during registration for execution to specify information to be passed.
• The number of logs to keep for a jobnet has been changed from 99 to 999. • For a cold start of JP1/AJS2, the job execution environment database is deleted so that the startup time of JP1/AJS2 becomes shorter. • A function is now supported for validating the user profile information in the environment setup for job execution control. • By setting the number of days that job information is held to 0 days, jobs that terminate abnormally can now be handled by changing the save time.
B. Reference Material for This Manual This appendix provides reference information, including various conventions, for this manual. B.1 Related publications This manual is part of a related set of manuals.
• Job Management Partner 1 Version 10 Job Management Partner 1/Automatic Job Management System 3 - Print Option Description, User's Guide (3021-3-331(E)) • Job Management Partner 1 Version 10 Job Management Partner 1/Automatic Job Management System 3 - Definition Assistant Description, Operator's Guide and Reference (3021-3-332(E)) • Job Management Partner 1/Automatic Job Management System 3 - Web Operation Assistant Description, Operator's Guide and Reference (3020-3-S18(E)) • Job Management Partner 1 Vers
• Job Management Partner 1/Software Distribution Administrator Kit Description and Operator's Guide (3020-3S84(E)) • Job Management Partner 1/Software Distribution Client Description and User's Guide (3020-3-S85(E)), for UNIX systems • Job Management Partner 1/Software Distribution SubManager Description and Administrator's Guide (3020-3L42(E)), for UNIX systems • Job Management Partner 1/Software Distribution Manager Description and Administrator's Guide (3000-3-841(E)) • Job Management Partner 1/Consolida
Abbreviation Full name or meaning JP1/AJS3 - Web Operation Assistant Job Management Partner 1/Automatic Job Management System 3 - Web Operation Assistant JP1/DH - AJE Job Management Partner 1/Data Highway Automatic Job Executor JP1/DH - Server Job Management Partner 1/Data Highway - Server JP1/FTP Job Management Partner 1/File Transmission Server/ FTP JP1/IM JP1/IM - Manager Job Management Partner 1/Integrated Management Manager JP1/IM - View Job Management Partner 1/Integrated Management View
• UNIX is sometimes used generically, referring to HP-UX, Solaris, AIX and Linux. B.
B.4 Conventions: KB, MB, GB, and TB This manual uses the following conventions: • 1 KB (kilobyte) is 1,024 bytes. • 1 MB (megabyte) is 1,0242 bytes. • 1 GB (gigabyte) is 1,0243 bytes. • 1 TB (terabyte) is 1,0244 bytes. B.5 Conventions: Meaning of "directory" and "folder" As a general rule, Windows folder names are used in this manual if they are identical to UNIX directory names. B.
B.9 Online manual JP1/AJS3 - View comes with an online manual that you can read in browsers. The HTML manual contains the same content as the Job Management Partner 1/Automatic Job Management System 3 Operator's Guide. In JP1/AJS3 - View, you can view the manual by choosing Help and then Contents. You can also press the F1 key to view the manual contents. Your Web browser must be associated with a file that has the extension htm; otherwise, the online manual will not be displayed correctly.
C. Glossary abnormal end A jobnet ends abnormally if one of the processes defined in the jobnet fails to execute properly. The jobnet is interrupted at that point and subsequent processes are not executed. A job ends abnormally if it fails to execute properly. The process is interrupted at that point. The embedded database system ends abnormally when an error causes its status to change from active to stopped or paused, without any intervention by the user. For details, see D.
backup file A file containing the units defined in JP1/AJS3. base day A date specified as the starting day of the month in the calendar information. base time The time that marks when a day ends and the next day begins in a JP1/AJS3 system. For example, if 8:00 a.m. is set as the base time, the previous day is regarded as lasting until 7:59 a.m. calendar information Information about open days and closed days for jobnet execution. You can define calendar information separately for each job group.
custom job A predefined job for executing a task with a specific purpose. JP1/AJS3 provides standard custom jobs such as file transfer and job requests to a mainframe. In addition, you can register your own frequently used jobs as custom jobs. When registering a custom job, you can represent it by creating an icon with a special shape and design, and you can create a dialog box for entering job information. To use a custom job, the requisite program for the job must be installed.
embedded database system administrator The owner of an embedded database practical directory and embedded database file system areas (data area and system area). The embedded database system administrator can execute commands for an embedded database. The OS manages embedded database system administrators. end with warning A status indicating that a jobnet finished, but some of the processes defined in the jobnet were executed incorrectly. The jobnet continues to the end without interruption.
execution ID A number assigned to an execution schedule of the uppermost jobnet. execution-locked resource A means of preventing multiple jobs from executing at the same time, by specifying the same resource name (execution-locked resource name) for each job. fixed execution registration A method of registering a jobnet so that it starts and runs at a predetermined date and time calculated by the system from schedule definitions.
jobnet A set of jobs associated in execution order. When a jobnet is executed, the jobs in the jobnet are automatically executed in their predetermined order. jobnet connector A unit for controlling the execution order of root jobnets. A jobnet connector establishes connections between root jobnets and controls their execution order by having connected generations wait for their counterparts to start or finish. Jobnet Editor window A window in which you can create new jobnets or edit existing jobnets.
JP1/AJS3 Console Manager A JP1/AJS3 component that stores definitions about monitored objects defined in JP1/AJS3 Console View, and gets status information about monitored objects by issuing requests to JP1/AJS3 Console Agent. JP1/AJS3 Console View A JP1/AJS3 component that allows you to define objects to be monitored, using a graphical user interface. The definitions are stored in JP1/AJS3 Console Manager.
JP1/Script A program for creating and executing scripts (batch files) that control jobs on Windows. Job operation can be automated by linking JP1/Script with JP1/AJS3. JP1/Software Distribution A general term for a system that distributes software and manages clients using batch operations over a network. By linking with JP1/AJS3 using the JP1/Software Distribution command interface, the user can automate software distribution and other tasks.
mail receipt parameter file A file containing the mail receipt monitoring parameters defined by the user. The file extension is .prm. This file is created automatically when the user defines a Receive Email Event job. mail send parameter file A file containing the mail send parameters defined by the user. The file extension is .prm. This file is created automatically when the user defines a Send Email Action job.
node switching system See cluster system. normal end A normal end of a jobnet occurs when all the processes defined in the jobnet have executed correctly and the jobnet has completed. A normal end of a job occurs when the job has executed correctly. open day A day when jobnets run.
The queue controls the number of jobs that the agent executes concurrently, thereby preventing any degradation in performance caused by a large number of jobs being executed at the same time. queueless job A job transferred directly from the manager to an agent host for execution, without using a queue. Queueless jobs simplify processing because they are not managed in a queue by the job execution control.
scheduler service A service that manages the schedules for jobnet execution, and executes processes according to those schedules. Each scheduler service manages all the units in the root job group whose name matches the scheduler service name. Multiple scheduler services can be activated in a single manager. This allows root job groups to be managed individually.
succeeding jobnet A jobnet executed immediately after another job or jobnet. suspend To suppress the execution of the root jobnet and lower units. When you change a definition under a root jobnet that has been registered for execution, you should suspend the root jobnet to prevent erroneous operation such as the execution control processing running with the old definition. By suspending the root jobnet, the redefinition processing can be synchronized with the execution control processing.
Windows Messaging A facility that provides an interface for sending and receiving email. Using Windows Messaging, you can manage, access, and share a variety of information such as data received from an online service. C.
Index dependent job 806 dependent jobnet 806 directory term defined 802 disaster recovery 806 A abbreviations for products 799 abnormal end 804 abnormal threshold 804 About the 3rd level and 4th level Kanji characters added in JIS 2004 (JIS X 0213:2004) 803 About the Start menu in Windows 802 acronyms 801 action job 804 agent host 804 AJS3 unit monitored object 804 AJS administrator 804 AJSPATH 804 automatic retry 804 E embedded database administrator, glossary definition 806 glossary definition 806 opera
I L immediate execution registration 808 installation folders default for JP1/AJS3 for Windows 802 ISAM compatible ISAM configuration, glossary definition 805 database, glossary definition 808 list file 811 list of output destinations for messages 30 list of windows event logs and syslogs 72 logical host 811 J job 808 job execution environment 808 job group 808 jobnet connector 809 Jobnet Editor window 809 Jobnet Monitor window 809 jobnets glossary definition 809 job network element 808 JP1/AJS3 Console
submit 815 submit job 815 substitute schedule 815 succeeding job 815 succeeding jobnet 816 suspend 816 symbol conventions 14 O online manual contents 803 open day 813 P passing information 813 passing information name 813 physical host 813 planned execution registration 813 planning group 813 preceding job 813 preceding jobnet 813 processing cycle 813 T TB meaning 802 threshold 816 timeout period 816 to system administrators TP1/Server Base 816 types of messages 23 Q queue 813 queueless job 814 queueles
