Autostart AS-4565-SH Spezifikationen PDF herunterladen

Job Management Partner 1/Automatic JobManagement System 3 Messages 13021-3-329-10(E)Job Management Partner 1 Version 10

Changes LocationA function was added for changing the passwords of JP1 users by using JP1/AJS3 - View.--Command Reference 2:--Linkage Guide:--Messages

Seite 3 - ■ Trademarks

An attempt to display the business scope for the JP1 user specified in the -u option of the ajscmprint commandhas failed because another user is curre

Seite 4 - Excel Microsoft(R) Excel

(S)Cancels command execution.(O)Specify the correct option, and then re-execute the command.KAVC0200-EFailed to convert string (string-before-characte

Seite 5

(O)Set the environment setting parameter indicated in item-name correctly according to 2.8 Setting up the JP1/AJS3Console environment in the Job Manag

Seite 6 - ■ Copyright

- system-drive\Windows- system-drive\Program Files- system-drive\Program Files (x86) (for 64-bit Windows)• For Windows Server 2012 or Windows Server 2

Seite 7 - Summary of amendments

(S)Continues processing.KAVC0533-IReception processing from JP1/AJS2 Console View has ended. (PID: process-ID)The processing accepted from JP1/AJS3 Co

Seite 8

(O)Follow the instructions given by the KAVC4507-E error message that was displayed on JP1/AJS3 Console Viewwhen you logged on.KAVC0806-EEnvironment f

Seite 9

The system cancels the processing during which insufficient memory was detected. If insufficient memory was detectedduring allocation of memory for a

Seite 10

KAVC0905-EFailed to put message (message-ID).: maintenance-information-1 maintenance-information-2 maintenance-information-3 maintenance-information-4

Seite 11

(O)Check whether resources are insufficient. Also check the running status of Hitachi Network Objectplaza TraceMonitor.In UNIX, see Release Notes, and

Seite 12

(S)Cancels the process in which the error occurred.(O)Terminate unnecessary windows, dialog boxes, and processes, and delete unnecessary files to incr

Seite 13

Changes LocationA change was made so that when Jobnet Definition is selected fromFunction Menu, jobnets for which execution has been registered aredis

Seite 14 - ■ Intended readers

KAVC2081-IJP1/AJS2 Console Agent service has been installed.The JP1/AJS3 Console Agent service has been set up.(S)Terminates setup processing.KAVC2082

Seite 15

(O)Check whether the JP1/AJS3 Console Agent service has been set up.KAVC2086-EAn error occurred during installing JP1/AJS2 Console Agent service.: mai

Seite 16

One or more unnecessary arguments are specified.(S)Cancels command execution.(O)Delete unnecessary arguments, and then re-execute the command.KAVC2103

Seite 17

KAVC2127-ESpecified file (file-name) does not exist.The specified file does not exist.(S)Cancels command execution.(O)Specify the correct file name or

Seite 18

(S)Cancels command execution if the error occurred during command execution. For other cases, the system cancelsprocessing.(O)If the error occurred du

Seite 19 - (3021-3-327(E))

For details about the data you must collect, see 1.3 Data to be collected when a problem occurs in the manual JobManagement Partner 1/Automatic Job Ma

Seite 20 - Contents

KAVC2386-EAn invalid value exists in the monitoring properties.: maintenance-information-1 maintenance-information-2maintenance-information-3The monit

Seite 21 - Index 818

No more connections can be made because the number of connections from JP1/AJS3 Console Manager exceeded thevalue specified in the MAXSESSION environm

Seite 22 - Overview of JP1/AJS3 Messages

KAVC2534-IJP1/AJS2 Console Agent service will connect to the scheduler service (scheduler-service-name). JP1-user-nameprocess-informationThe JP1/AJS3

Seite 23 - 1.1 Types of messages

(S)Continues processing.KAVC2539-IThe command execution request will now end.: command-nameProcessing of a request has ended. The request, accepted fr

Seite 24 - 1.2 Message format

Changes LocationA function was added for preventing the history of previously-used login-usernames and connection-destination host names from appearin

Seite 25

KAVC2901-EI/O error occurred.: maintenance-information-1 maintenance-information-2 maintenance-information-3A file I/O error occurred during processin

Seite 26

KAVC2904-EUnexpected error occurred in JP1/AJS2 Console Agent.: maintenance-information-1 maintenance-information-2maintenance-information-3 maintenan

Seite 27

(O)Use the data collection tool to collect data and contact the system administrator (see 1.2.3 To the systemadministrators).KAVC2920-WMessage process

Seite 28 - Message ID

(S)Cancels the process in which the error occurred.(O)Terminate unnecessary windows, dialog boxes, and processes, and then re-execute the operation.In

Seite 29

(S)Terminates JP1/AJS3 Console View.(O)Collect the following data, and then contact the system administrator.• A hardcopy of the window• JP1/AJS3 Cons

Seite 30 - Manager)

KAVC4005-EAn unexpected error occurred in start processing.(Detailed information: (maintenance-information-1), (maintenance-information-2))An unexpect

Seite 31 - --: Is not output

(S)Cancels processing.(O)Compare ajscon2.conf against ajscon2.conf.model to check for any unnecessary options that have beenspecified.KAVC4011-EThe co

Seite 32

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

Seite 33

KAVC4018-EYou 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 execu

Seite 34

(S)Cancels automatic login, and displays the Login screen. Even if the password is specified, the password does notappear in the Login screen unless b

Seite 35

Changes LocationContent related to Solaris 11 (SPARC) was added. --Command Reference 2:2. ajsembdbsetup, 2. jajs_setup, 2. jajs_setup_clusterLinkage G

Seite 36

The copy destination folder (indicated by folder-name) for the files used for linkage with JP1/IM - View was not foundin the JP1/IM - View installatio

Seite 37

(O)Check whether the correct value is specified for keyword.KAVC4106-WThere is an ineffective parameter. [(invalid-parameter)]An invalid parameter was

Seite 38

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

Seite 39

KAVC4115-IAn error occurred, so an operation was not processed.This message indicates that the operation that was attempted before the message appears

Seite 40

(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 use

Seite 41

(S)Reports that the system disconnected JP1/AJS3 Console Manager, then reconnected it. It also informs that all thedisplayed Detailed Information dial

Seite 42

KAVC4224-IThe operation result is unknown because the connection with the connection destination was severed whileperforming the operation.This messag

Seite 43

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 t

Seite 44

(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-QThe specified co

Seite 45

KAVC4309-QThe icon image file ((file-name)) cannot be accessed. Are you sure you want to define the specified file name forthe icon image file?The use

Seite 46

PrefaceThis manual describes the format of messages for Job Management Partner 1/Automatic Job Management System 3(abbreviated hereafter to JP1/AJS3),

Seite 47

(S)Cancels processing.(O)A temporary network problem may have occurred. If this message appears during update of definition information,check whether

Seite 48

You can change the maximum number of connections in the environment settings for JP1/AJS3 Console Manager.Change the value of the MAXSESSION environme

Seite 49

KAVC4512-EThe Access Control Server at the connection destination could not be connected.User authentication is impossible because the Access Control

Seite 50

If the user started JP1/AJS3 Console View in JP1/IM - View, the user cannot log in with the current login informationbecause the authentication bloc a

Seite 51

(O)Collect the following data, and then contact the system administrator:• A hardcopy of the window• JP1/AJS3 Console View log information• JP1/AJS3 C

Seite 52

• JP1/AJS3 Console Manager log informationFor details on how to collect the logs, see 1.3 Data to be collected when a problem occurs in the manual Job

Seite 53

(O)Log out from JP1/AJS3 Console View. Then change the character set settings in a running JP1/AJS3 ConsoleManager at the connection destination, and

Seite 54

(S)Outputs, to the log, the information that data from JP1/AJS3 Console Manager was received.KAVC4538-IREQ_EXECCOMMAND: (maintenance-information)This

Seite 55

KAVC4542-ICLOSE (connection-information)This message indicates that the connection to JP1/AJS3 Console Manager was closed.(S)Outputs, to the log, the

Seite 56

(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 int

Seite 57

Text formatting ConventionMonospace• At the prompt, enter dir.• Use the send command to send mail.• The following message is displayed:The password is

Seite 58

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

Seite 59

KAVC4556-IERR_SDUMP (sent-data)If an error occurs during the transmission of a request from JP1/AJS3 Console View to JP1/AJS3 Console Manager,this mes

Seite 60

KAVC4560-EAn error occurred at the connection destination.Detailed information [(maintenance-information)]An error occurred in JP1/AJS3 Console Manage

Seite 61

(S)Cancels processing.(O)Use log information such as the Windows event log or the syslog on the host for JP1/AJS3 Console Manager toexamine the error.

Seite 62

KAVC4566-EAn error occurred in JP1/Base at the connection destination.Detailed information [(maintenance-information)]The system cannot perform proces

Seite 63

KAVC4569-WInterProcess : (maintenance-information)This message indicates that an error that allows processing to continue occurred during inter-proces

Seite 64

KAVC4603-EThe Definition mode is unavailable because the object is currently being monitored.You cannot set the object in the Definition mode because

Seite 65

(O)Wait until the monitoring status indication on the mode panel changes to Monitoring status, and then activatethe Definition mode.KAVC4607-EThe Moni

Seite 66

KAVC4610-EThe object could not be pasted because the maximum number of definitions was exceeded.The user cannot paste the object because the number of

Seite 67

(O)As required, from the menu, choose View, JP1/AJS3 - View, and JP1/AJS3 - View Window to activate the JP1/AJS3 - View window.KAVC4614-EAn upper-leve

Seite 68

Symbol Convention< >(angle brackets)<hexadecimal character>0, 1, 2, 3, 4, 5, 6, 7, 8, 9, A, B, C, D, E, or F<file name>A system-dete

Seite 69 - JP1 event: JP1 event

(O)Delete unnecessary display colors, and then create display colors.KAVC4618-EA color with the specified RGB element already exists, so you cannot sp

Seite 70

(S)Cancels processing.(O)Select a display color from the Available colors list.KAVC4622-EAn error occurred while displaying the message box.An error o

Seite 71

The user cannot create more objects because the number of definitions exceeded the maximum.(S)Cancels processing.In Automatic Creation of Monitored Ob

Seite 72

KAVC4631-EThe specified operation was not performed because the connection was severed during processing.The connection was severed while the system w

Seite 73

(O)Check whether the directory-name directory exists. Also check whether a file with the extension extension-nameexists in that directory.Even if the

Seite 74

The user cannot create the object because the maximum number of objects that can be defined in the business scope atthe definition destination has bee

Seite 75

KAVC4641-EMoving is not possible because the cut business scope and paste destination business scope are the same.The object does not move because the

Seite 76

KAVC4645-EThe (operation-name) is not possible because the execution ID is unknown.The system cannot perform the specified operation because the statu

Seite 77

(O)Use log information such as the Windows event log or the syslog on the host for JP1/AJS3 Console Manager toexamine the error. Then, correct the cau

Seite 78

KAVC6111-EThe host name of the monitoring destination could not be resolved.The system cannot display the status because JP1/AJS3 Console Manager at t

Seite 79

No. Manual Contents1 Overview(3021-3-318(E))• JP1/AJS3 features• Description of functions2 System Design (Configuration) Guide(3021-3-319(E))• Informa

Seite 80

(O)Check that JP1/AJS3 Console Agent on the monitoring destination host is normal. If the IPC_TIMEOUTenvironment setting parameter has been specified

Seite 81

(O)If there are two or more objects to be monitored on the same host, specify the same name for Host name for eachmonitored object.A maximum of 50 hos

Seite 82

The system cannot display the status because the file system or device in JP1/AJS3 Console Agent at the monitoringdestination does not have sufficient

Seite 83

The system cannot display the status because the JP1/Base settings on the monitoring destination host disablecommunication with the host name or IP ad

Seite 84

KAVC6232-EJP1/AJS3 Console Agent service needs the required permission.The system cannot display the status because the JP1/AJS3 Console Agent service

Seite 85

KAVC6243-EThe object to monitor is specified incorrectly.The system cannot display the status because the data entered in the monitored-object option

Seite 86

KAVC6301-EThe operation function is not supported at the monitoring destination.JP1/AJS3 Console Agent on the monitoring destination host does not sup

Seite 87

2.3 Messages beginning with KAVS (Messages about the scheduler andthe common processing)This section lists the messages that begin with KAVS (Message

Seite 88

KAVS0103-EInvalid value for option (option).The option contains an invalid value.(S)Cancels command execution.(O)Correct the value for the option, and

Seite 89

(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

Seite 90 - Messages

Purpose Required reading Read as necessaryTo learn about JP1/AJS3's functionalities • Overview(3021-3-318(E))• Linkage Guide(3021-3-328(E))To con

Seite 91 - KAJS7622-E

KAVS0110-EJobnet (jobnet-name) is in execution.The jobnet is being executed.(S)Cancels command execution.(O)Wait for the jobnet to terminate the execu

Seite 92 - KAJS7625-E

KAVS0113-ENo authority for Unit (unit-name).You do not have an authority for the unit.(S)Cancels command execution.(O)Execute the command with the aut

Seite 93 - KAJS7629-E

KAVS0117-EJob name not specified.A job name is missing.(S)Cancels command execution.(O)Specify a job name, and then re-execute the command.KAVS0119-EC

Seite 94 - KAJS7630-E

• 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

Seite 95 - KAVC0081-I

KAVS0130-ESpecified Jobnet (jobnet-name) is not registered.The jobnet is not registered.(S)Cancels command execution.(O)Register the jobnet, and then

Seite 96 - KAVC0086-E

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

Seite 97 - KAVC0101-E

(S)Cancels command execution. If you specify more than one job (including specifications of regular expression), thesystem continues processing.(O)Spe

Seite 98 - KAVC0108-E

(S)Cancels command execution.(O)Recheck the value of the relationship change option, and then re-execute the command.KAVS0159-WOption (option) has bee

Seite 99 - KAVC0150-E

(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

Seite 100 - KAVC0158-E

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 sche

Seite 101 - KAVC0331-E

Purpose Required reading Read as necessaryTo learn about operating JP1/AJS3 (3021-3-325(E)) (3021-3-326(E))• Command Reference 2(3021-3-327(E))Job Man

Seite 102 - KAVC0356-E

(S)Terminates processing.(O)Correct the temporary file directory name specified in the environment setting for the scheduler service, restart thesched

Seite 103 - KAVC0532-I

KAVS0177-EDatabase type is invalid.You cannot use the database.(S)Terminates processing.(O)Correct the database type, and then re-execute the command.

Seite 104 - KAVC0805-E

(O)Correct the execution ID, and then re-execute the command.KAVS0181-EExecution ID cannot be appointed.The execution ID cannot be specified.(S)Termin

Seite 105 - KAVC0902-E

(O)Correct the execution ID, and then re-execute the command.KAVS0185-ECannot operate - wait for activation condition.: unit-nameProcessing is impossi

Seite 106 - KAVC0904-E

The value specified for the abnormal threshold is equal to or greater than the lower limit of the return code forautomatic retry.• If -ej, -el, -eh, -

Seite 107 - KAVC0920-W

• To change the automatic retry setting (-rs, -re, -rc, or -ri option), specify cod for the -jd option tospecify end judgment by threshold.• If automa

Seite 108 - KAVC0951-E

For details about the environment variables, see 1.4 Environment variables in the manual Job Management Partner1/Automatic Job Management System 3 Com

Seite 109 - KAVC2002-I

(S)Cancels command execution.(O)Unregister the execution of the unit or suspend the unit, and then re-execute the command.KAVS0198-ECannot use - Unit

Seite 110 - KAVC2085-E

(S)Terminates the scheduler service.KAVS0202-ELog daemon ended abnormally. (code: code)The log daemon terminated abnormally.(S)Cancels the processing

Seite 111 - KAVC2102-E

(S)Terminates processing.KAVS0209-EScheduler service is inactive.The scheduler service has already stopped.(S)Terminates processing.KAVS0210-ILocal ti

Seite 112 - KAVC2119-E

Notices Relevant program productsFor details about the applicable OS versions, and the service packs and patches required for Job Management Partner

Seite 113 - KAVC2330-E

ContentsNotices 2Summary of amendments 7Preface 141 Overview of JP1/AJS3 Messages 221.1 Types of messages 231.2 Message format 241.2.1 Format of outpu

Seite 114 - KAVC2382-E

KAVS0214-IThe generation management sub-daemon (scheduler-service-name) started.This message indicates that the generation management sub-process has

Seite 115 - KAVC2385-E

Since the scheduler service for which a cold start was attempted was still accessing the database, database registrationinformation could not be delet

Seite 116 - KAVC2456-E

KAVS0221-IScheduler log output process ended.The scheduler log output process has ended.(S)The scheduler log output process has ended.KAVS0222-EHost n

Seite 117 - KAVC2533-I

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 D

Seite 118 - KAVC2538-I

KAVS0242-IThe execution request of the event job started. (name : jobnet-name : execution-ID)The execution request of the event job starts. execution-

Seite 119 - KAVC2805-E

(S)Continues processing.KAVS0246-EThe system failed to delete the execution result (execution-ID : execution-ID) of the jobnet (jobnet-name).:maintena

Seite 120 - KAVC2903-E

KAVS0249-WThe scheduler services stopped before execution of the job(job-name : execution-ID) began.The scheduler service stopped before the job was p

Seite 121 - KAVC2916-E

(O)Determine the cause of the error by checking the integrated trace log or the detailed log of the job, correct the causeof the error, and then resta

Seite 122 - KAVC2950-E

(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

Seite 123 - KAVC4001-E

If code 128 is displayed for a PC job, the job may have terminated abnormally due to a desktop heap that is toosmall.See 4.2.3 Changing the JP1/AJS3 s

Seite 124 - KAVC4004-E

B Reference Material for This Manual 797B.1 Related publications 797B.2 Conventions: Abbreviations for product names 799B.3 Conventions: Acronyms 801B

Seite 125 - KAVC4010-E

KAVS0269-WJob ended with warning. (name: job-name: exception-ID, code: code, host: host-name, JOBID: job-number)The job has terminated with a warning.

Seite 126 - KAVC4014-E

(O)See the message output before this message to examine the cause of the error and correct it. Then, unregister theblocked jobnet and reregister it.K

Seite 127 - KAVC4017-E

The jobnet is delayed stopping. execution-ID appears if you specified yes for the LOGINFOALL environment settingparameter.(S)Continues processing.KAVS

Seite 128 - KAVC4020-E

KAVS0289-EManager's host name not specified.The execution manager for the remote jobnet is not specified.(S)Abnormally terminates the remote jobn

Seite 129 - KAVC4028-W

• The calendar information about the jobnet schedule for execution registration does not contain the specified jobgroup.(S)Terminates processing.(O)Re

Seite 130 - KAVC4104-W

(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

Seite 131 - KAVC4110-I

(S)Terminates processing.(O)Close unnecessary windows and dialog boxes, and delete unnecessary files to increase available free space. Thenre-execute

Seite 132 - KAVC4114-I

If the target backup box or backup file was deleted by the ajsbkudel command while the Backup or Restoredialog box was displayed in JP1/AJS3 - View, c

Seite 133 - KAVC4117-W

(O)Start the JP1/AJS3 service, and then re-execute the command.KAVS0369-ECannot operate - version is different.Processing is impossible because the ve

Seite 134 - KAVC4220-I

KAVS0470-EAmong the generations registered in the specified period, there is no generation whose registration can be canceled.(unit-name)There is no i

Seite 135 - KAVC4223-I

1Overview of JP1/AJS3 MessagesThis chapter lists the manuals that contain information about messages output by JP1/AJS3, JP1/Base, and JP1/IM. This ch

Seite 136 - KAVC4234-I

KAVS0478-EScheduler log file name is too long.A scheduler log file name is specified using a character string of more than 255 bytes.(S)Cancels comman

Seite 137 - KAVC4305-Q

KAVS0532-IJP1/AJS2 Monitor service started accepted processing. (From: IP-address, To: logical-host-name, JP1-user-name, PID: process-ID)ajsinetd proc

Seite 138 - KAVC4308-Q

(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-ESpecified local time is n

Seite 139 - KAVC4502-E

KAVS0548-IThe shift processing of JP1/AJS3 to a standard composition has already been completed.The migration processing of JP1/AJS3 to the standard c

Seite 140 - KAVC4505-E

An invalid environment variable was specified.(S)Cancels command execution.(O)Correct the environment variable, and then re-execute the command.For de

Seite 141 - KAVC4511-E

KAVS0603-EIllegal character exists in option string (option-character-string).The option or the date information file contains an illegal character.(S

Seite 142 - KAVC4514-E

KAVS0621-ECannot delete - Unit (unit-name) is registered.The specified unit cannot be deleted because it is contained in a registered root jobnet or a

Seite 143 - KAVC4520-E

KAVS0631-ECannot move - Unit (unit-name) is already registered.The output destination unit cannot be moved because it has already been registered.(S)C

Seite 144 - KAVC4523-E

KAVS0635-ECannot copy - Unit (unit-name) does not exist.An attempt was made to copy more than one unit. However, copying was impossible because the de

Seite 145 - KAVC4526-E

KAVS0639-ECannot copy the Unit (unit-name) - currently used by another user.Another user is using the unit, preventing it from being copied.(S)Cancels

Seite 146 - KAVC4537-I

1.1 Types of messagesThis chapter lists the manuals that contain information about the messages output by JP1/AJS3, JP1/Base, and JP1/IM.When you ope

Seite 147 - KAVC4541-E

(O)Check whether the output destination is the planning group. Correct the unit name, and then re-execute the command.KAVS0648-EA unit other than a jo

Seite 148 - KAVC4546-W

The statement indicated by sentence-number in the message might follow the statement containing the error. If theindicated statement number is correct

Seite 149 - KAVC4551-I

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

Seite 150 - KAVC4555-I

KAVS0656-QOk 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 upd

Seite 151 - KAVC4559-I

KAVS0659-ENo authority to use definition unit (unit-name).The definition unit does not have any authority, preventing it from being defined.(S)Cancels

Seite 152 - KAVC4563-E

KAVS0668-EThe value of the parameter specification range has an error.(unit-name parameter-name-1 parameter-name-2)The value of the specifiable range

Seite 153 - KAVC4565-E

(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 unitdef

Seite 154 - KAVC4568-I

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 judgmentconditio

Seite 155 - KAVC4602-E

• The effective registration date expired.• The registration date exceeded the execution start date, but the process cycle or an alternate method is m

Seite 156 - KAVC4606-E

KAVS0694-EPermission 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

Seite 157 - KAVC4609-E

1.2 Message formatThis section explains the output format of JP1/AJS3 messages and the description format of messages in this manual.JP1/AJS3 support

Seite 158 - KAVC4613-E

A root jobnet in a planning group can only be registered for fixed execution by using the ajsentry command withthe -p option or the -b and -e options

Seite 159 - KAVC4617-E

KAVS0700-WA unit was deleted during the command processing.The specified unit no longer exists. It may have been deleted, or moved.(S)Cancels command

Seite 160 - KAVC4621-E

When a unit under a planning group is specifiedYou executed a command on an active unit automatically selected from under a planning group, but the ta

Seite 161 - KAVC4624-E

The unit ID is specified incorrectly.(S)Cancels command execution. If you specify more than one unit ID, the system continues processing of another un

Seite 162 - KAVC4629-E

(O)Specify an execution start date later than the current date, and then re-execute the command.KAVS0721-ISpecified Jobnet (jobnet-name) does not acce

Seite 163 - KAVC4634-E

(O)Specify a jobnet that has a future plan, and then re-execute the command.KAVS0729-ECannot change plan temporarily - specified execution start date

Seite 164 - KAVC4637-E

(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-

Seite 165 - KAVC4640-E

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, a

Seite 166 - KAVC4644-E

KAVS0780-ESpecified Jobnet (unit-name) has no information for display.The jobnet does not contain any information to be displayed. There might be no i

Seite 167 - KAVC6101-E

(S)Cancels command execution.(O)Re-execute the command without specifying the -g 0 option with the -l option.KAVS0785-EInsufficient options specified.

Seite 168 - KAVC6104-E

Message level Type of Windows event logLevel Meaning-IInformation Notice of holding a job, start of job execution, normal end of a job, start of monit

Seite 169 - KAVC6113-E

KAVS0829-IReporting the effective information of JP1/AJS has started.Output of the operating information for the JP1/AJS3 service has started.(S)Conti

Seite 170 - KAVC6116-E

• 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 detail

Seite 171 - KAVC6203-E

KAVS0853-ENo authority to use backup box (backup-box-name).The backup box does not have any authority.(S)Terminates processing.(O)Execute the process

Seite 172 - KAVC6212-E

KAVS0857-ECannot treat as backup file.: backup-file-namebackup-file-name cannot be a backup file.(S)Cancels command execution. If you specify more tha

Seite 173 - KAVC6231-E

If the JP1/AJS3 service at the connection destination has not started, start the appropriate service.If the ajsinetd process has not started, execute

Seite 174 - KAVC6242-E

(O)If a large jobnet is being executed or if many JP1/AJS3 commands are being executed, wait until the relevantprocessing terminates, and then re-exec

Seite 175 - KAVC6252-E

For details about the kernel parameters, see Release Notes, and the explanation of kernel parameters in the JobManagement Partner 1/Base User's G

Seite 176 - KAVC6303-E

KAVS0874-QOK 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 respo

Seite 177 - KAVS0102-E

(S)Terminates processing.(O)Remove the cause of the error, and then re-execute the command.KAVS0880-IRestoring unit (unit-name) to unit (unit-name).Th

Seite 178 - KAVS0106-E

• A communication error has occurred between the manager host where the jobnet is defined and the manager hoston which the jobnet is to be executed.•

Seite 179 - KAVS0108-E

Warning message. Processing continues after message output.• IInformation message. Reports information to the user.• QQuery message. Prompts the user

Seite 180 - KAVS0112-E

(O)Although the start notification is unsuccessful, it does not affect execution of the remote jobnet.Note, however, that an end notification might fa

Seite 181 - KAVS0116-E

recovery-information-4 recovery-information-5 recovery-information-6> ./ajsremnetrcv.log3. Make sure that the remote jobnet is placed in the end st

Seite 182 - KAVS0125-E

If you delete a suspended remote jobnet, the jobnet name is indicated as a number. However, no operational problemsoccur because processing is perform

Seite 183 - KAVS0129-E

An error that allows processing to continue occurred.(S)Continues processing.(O)If the maintenance information contains the character string SPMD comm

Seite 184 - KAVS0141-E

be written separately to the database. Alternatively, change the value of the pd_lck_pool_size for theembedded database.For details on the UNITDEFDIVI

Seite 185 - KAVS0145-E

(O)Take action according to the error information in the Windows event log or syslog output by the OS, and other OS-specific error information. If you

Seite 186 - KAVS0158-E

KAVS0909-EShared memory is not available.: maintenance-information-1 maintenance-information-2Shared memory, which is one of the system resources, can

Seite 187 - KAVS0162-E

(O)Check whether the resources are sufficient. Also check the running status of Hitachi Network Objectplaza TraceMonitor.In UNIX, recheck the followin

Seite 188 - KAVS0169-E

Cause 2When the OS is AIX and the ISAM lock table split function is used, the ISAM lock table cannot be allocated.ActionStop all the related JP1 servi

Seite 189 - KAVS0172-E

KAVS0932-EError occurred during database access.: maintenance-information-1 maintenance-information-2 maintenance-information-3An error occurred while

Seite 190 - KAVS0176-E

ZMessage type, as one of the following:• EError message. Processing is canceled. However, if you specify more than one name using a command, thesystem

Seite 191 - KAVS0180-E

ActionCheck the estimated file size in the kernel parameter, and set the appropriate value. For details about estimatingthe kernel parameters, see Rel

Seite 192 - KAVS0184-E

The user password may have been changed with the ajssetup command. If the password has been changed, userauthentication may fail and the database cann

Seite 193 - KAVS0188-E

(O)The schema has already been defined, so you do not need to use the ajssetup command to set up the schemaagain. If you want to discard and re-create

Seite 194 - 2. Messages

KAVS0943-ECannot connect to job status notification process.: maintenance-information-1 maintenance-information-2maintenance-information-3The status r

Seite 195 - KAVS0190-E

KAVS0946-EThe error occurred during scheduler service(scheduler-service-name) start processing. : maintenance-information-1 maintenance-information-2

Seite 196 - KAVS0194-E

KAVS0965-ESpecification of the exclusion schedule specified in the jobnet(jobnet-name-2) inside the jobnet(jobnet-name-1)includes an error.The definit

Seite 197 - KAVS0201-I

(O)Contact the system administrator, and collect data (see 1.2.3 To the system administrators).KAVS0981-EThe table is not found.The database table is

Seite 198 - KAVS0208-E

(O)Specify the user who has permission for the database, and then retry.KAVS0985-ECould not connect to the database.The database could not be connecte

Seite 199 - KAVS0213-I

KAVS0988-EInsufficient tablespace or RDAREA.The table area or RDAREA does not have any free space.(S)Terminates processing.(O)Reorganize the table are

Seite 200 - KAVS0218-E

• In AIX: LIBPATHKAVS0991-ENot supported on related programs (program-name).program-name does not support the requested function.If this error message

Seite 201 - KAVS0220-I

Characters in italic vary each time the system displays a message. Messages are explained in the ascending order ofmessage IDs.Message IDMessage text:

Seite 202 - KAVS0231-W

KAVS0994-ERecord existed in specified database table.The database table at the import destination contains a record.(S)Cancels command processing.(O)R

Seite 203 - KAVS0241-I

(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

Seite 204 - KAVS0245-W

KAVS1004-EScheduler service does not exist.The scheduler service does not exist.(S)Terminates processing.(O)Specify the correct name of the AJS servic

Seite 205 - KAVS0248-I

In UNIX, use the jajs_spmd_status command to make sure that the JP1/AJS3 service has stopped. Aftermaking sure that the services have stopped, go to s

Seite 206 - KAVS0253-E

KAVS1010-IThe password was successfully changed for a user (JP1-user-name).The password was successfully changed.(S)Continues processing.KAVS1011-EAn

Seite 207 - KAVS0262-E

A connection could not be established because the maximum number of concurrent sessions specified in theMAXSESSION environment setting parameter for t

Seite 208 - KAVS0265-E

(S)Continues processing.(O)Check whether the estimated values of the MAXSESSION and SERVICEMAXSESSION environment settingparameters are correct. If ne

Seite 209 - KAVS0268-W

(S)Cancels command execution.(O)Specify the value for the option and then re-execute the command.KAVS1103-EThe specified value (value) is already used

Seite 210 - KAVS0272-E

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

Seite 211 - KAVS0276-I

(S)Cancels command execution.(O)Specify the correct value for the option and then re-execute the command.KAVS1111-EThis function cannot be used with t

Seite 212 - KAVS0279-E

(P)Programmer action at message output(O)Operator action at message outputActionAction that the embedded database system administrator must take when

Seite 213 - KAVS0300-E

(S)Cancels command execution.(O)Specify the correct scheduler service name, and then re-execute the command.KAVS1115-EFailed to create shared director

Seite 214 - KAVS0311-E

(O)Specify the correct logical host, and then re-execute the command.KAVS1118-EScheduler service is active.The scheduler service is running.(S)Cancels

Seite 215 - KAVS0317-E

(O)Check whether read or higher permission has been given for the file shown in the message. If the permission is notset, give read or higher permissi

Seite 216 - KAVS0319-E

KAVS1126-EAn error occurred during scheduler service addition or deletion processing. (maintenance-information)An attempt to set up or remove the embe

Seite 217 - KAVS0358-E

KAVS1130-EAn attempt to read the configuration definition information failed.An attempt to obtain the configuration definition has failed.(S)Cancels c

Seite 218 - KAVS0439-E

• If Disaster recovery is indicated in setting-name, the feature that automatically starts the scheduler servicein disaster recovery mode when the JP1

Seite 219 - KAVS0477-E

(S)Cancels command execution.(O)Check for duplicate values and then re-execute the command.KAVS1137-EThe scheduler service specified for the option (o

Seite 220 - KAVS0531-I

(S)Cancels command execution.(O)In the unit configuration definition, only define parameters that conform to the compatible ISAM configuration.KAVS114

Seite 221 - KAVS0540-Q

KAVS1144-EThe specification of the wait condition is insufficient (unit-name).No units whose ends are being waited for are specified for a unit with w

Seite 222 - KAVS0547-E

(O)Specify the option value correctly, and then re-execute the command.In addition, change the value of the environment setting parameter indicated in

Seite 223 - KAVS0582-E

P-CC2A12-34AL Job Management Partner 1/Automatic Job Management System 3 - View version 10-10 (ForWindows 8, Windows Server 2012, Windows 7, Windows S

Seite 224 - KAVS0602-E

1.3 List of output destinations for messagesThis section lists the output destinations of the messages that are output by JP1/AJS3.1.3.1 Output dest

Seite 225 - KAVS0620-Q

(O)Check the following:• Check whether system resources are sufficient.• Check whether the permission environment of the started user is correct.• Che

Seite 226 - KAVS0630-E

(S)Lets the jobnet in Wait for start time status wait for the monitoring generation to terminate. When the monitoringgeneration has terminated, the jo

Seite 227 - KAVS0634-E

KAVS1503-IThe ISAM unused area size of the scheduler service (scheduler-service-name) is size-in-megabytes.The size of the unused area of the ISAM fil

Seite 228 - KAVS0638-E

(O)The database cannot be accessed because the size of the ISAM files exceeded 2 gigabytes. Reduce the size of theISAM files by unregistering or delet

Seite 229 - KAVS0647-E

KAVS1516-EConstruction is invalid.(maintenance-information)The configuration is invalid. The probable causes are:• The installation or migration of JP

Seite 230 - KAVS0650-E

also deleted. Before deleting the database environment, execute the ajsprint command to back up thedefinitions.If the value of the AJSCHARCODE environ

Seite 231 - KAVS0652-E

(O)Set the value indicated in item-name correctly.For details about output item names, see2. Environment Setting Parameters in the Job Management Part

Seite 232 - KAVS0655-E

KAVS1600-EThe specified unit name is invalid.The status could not be acquired because of one of the following reasons after you specified the unit nam

Seite 233 - KAVS0658-E

KAVS1703-EThe command executed during reorganization of the scheduler service (scheduler-service-name) database endedabnormally.: Jischk -l3 table-nam

Seite 234 - KAVS0665-E

KAVS1706-EAn attempt to create a backup directory during reorganization of the scheduler service (scheduler-service-name)database failed. (directory-n

Seite 235 - KAVS0669-E

stderr: Standard error outputY: Is output.--: Is not output.Table 1‒7: The output destinations of messages about JP1/AJS3 Console ManagerMessage ID O

Seite 236 - KAVS0674-E

The probable causes are:• More than one jajs_maintain command was executed at the same time for the scheduler service.• The scheduler service was star

Seite 237 - KAVS0683-E

(O)Execute Jischk -l3 table-name to check whether a problem exists with the table whose reorganization endedabnormally. For details about Jischk, see

Seite 238 - KAVS0686-E

(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 processesaccessing th

Seite 239 - KAVS0697-E

(S)Starts the jajs_maintain command.KAVS1722-Ijajs_maintain command ended normally.The jajs_maintain command ended normally.(S)Performs a normal termi

Seite 240 - KAVS0699-E

• Check whether the specified scheduler service name contains errors.• Check whether the specified scheduler service has been set up. If the specified

Seite 241 - KAVS0702-E

• A logical contradiction occurred in the manager.See KAVU0969-E.• That request is not supported by the requested manager.See KAVU0970-E.• The executi

Seite 242 - KAVS0711-E

KAVS1730-IThe maintenance mode of the scheduler service (scheduler-service-name) was canceled.Maintenance mode was canceled for the scheduler service

Seite 243 - KAVS0720-E

KAVS1735-ENeed to rerun this command.You need to re-execute this command.(S)Cancels command execution.(O)See the message output together with this mes

Seite 244 - KAVS0724-E

KAVS1739-EBackup failed. Failed to make directory (directory-name).: return code = return-value-from-mkdirSince the backup directory could not be crea

Seite 245 - KAVS0740-E

(O)The system could not compare the files at the backup source and the backup destination. The database for thescheduler service may have been updated

Seite 246 - KAVS0763-E

The table uses the following abbreviations for the output destinations:syslog: syslogEvent log: Windows event logHNTRLib2: Integrated trace logstdout:

Seite 247 - KAVS0771-E

KAVS1755-EA 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

Seite 248 - KAVS0784-E

(O)Check whether the disk has free space. Take action according to the error message of the cmp command outputtogether with this message.KAVS1759-ERes

Seite 249 - KAVS0800-E

KAVS1773-IThe adapter command unsetup completed normally.Adapter command unsetup ended normally.(S)Continues processing.KAVS1774-EThe logon account do

Seite 250 - KAVS0849-I

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

Seite 251 - KAVS0852-E

(S)Cancels command execution.(O)Check whether the adapter command exists.KAVS1782-EThe adapter command configuration file storage directory does not e

Seite 252 - KAVS0856-E

KAVS1786-EAn unexpected error occurred.An unexpected error occurred.(S)Cancels command execution.(O)Contact the system administrator.KAVS1790-EAn erro

Seite 253 - KAVS0863-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 contradict

Seite 254 - KAVS0865-E

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 log

Seite 255 - KAVS0868-E

KAVS1804-IThe queueless agent will now terminate.The queueless agent service accepted a request for forced termination of the ajsqlstop command.(S)Ter

Seite 256 - KAVS0873-E

(O)Use JP1/AJS3 - View to make sure that the number of queueless jobs waiting for execution for the queueless agentservice has not reached the maximum

Seite 257 - KAVS0877-E

(3) KAVC4001 to KAVC6000 (messages about JP1/AJS3 Console View)The following table lists the output destinations of messages about JP1/AJS3 Console V

Seite 258 - KAVS0889-E

(O)Execute the ajsqlattach command to attach the host indicated in host-name, and then re-execute the queuelessjob indicated in job-name that resulted

Seite 259 - KAVS0890-E

(O)Check the amount of memory available by using Task Manager in Windows or the top command or another meansin UNIX.Wait until the memory necessary fo

Seite 260 - KAVS0891-E

To identify the name of the service (process) that output this message, check the AP name that is output to theintegrated trace log concurrently with

Seite 261 - KAVS0892-E

• If Permission denied is indicated in maintenance-information-1, write permission for the status fileindicated in status-file-name might have been ch

Seite 262 - KAVS0900-W

• If Permission denied is indicated in maintenance-information-1, write and read permissions for the statusfile indicated in status-file-name might ha

Seite 263 - KAVS0902-E

• In the DNS settings, hosts file, jp1hosts file, or jp1hosts2 file, correctly register the host name and IPaddress of the host that executes queueles

Seite 264 - KAVS0903-E

write to the work path indicated in path-name. Then, re-execute the queueless job indicated in job-name that resultedin the error.KAVS1820-EMemory is

Seite 265 - KAVS0907-E

KAVS1823-ENo access permission is granted for the file (file-name) on the transmission host (host-name), so the job (job-name) cannot be executed.The

Seite 266 - KAVS0920-W

• If any message other than the above is indicated in maintenance-information-1, correct the error according tothe message.If you cannot correct the p

Seite 267 - KAVS0930-E

(O)Change the OS user who executes the queueless job indicated in job-name to a superuser, or change the executionorder to 1, 2, or 3. Then, re-execut

Seite 268 - KAVS0931-E

Message ID Output destinationDialog Log stderrKAVC4104 -- Y --KAVC4106 Y Y --KAVC4107 -KAVC4111-- Y --KAVC4112 Y -- --KAVC4113 -KAVC4114-- Y --KAVC411

Seite 269 - KAVS0932-E

• Standard input file name: 767 bytes• Standard output file name: 767 bytes• Standard error output file name: 767 bytes(S)Places the queueless job ind

Seite 270 - KAVS0933-W

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 insuffic

Seite 271 - KAVS0936-E

KAVS1834-EAn error occurred in the standard output file (file-name).: maintenance-information-1 (maintenance-information-2)An error occurred during ac

Seite 272 - KAVS0942-W

directory path so that the mapped OS user can read and write to the standard error output file indicated in file-name. Then re-execute the job.• If an

Seite 273 - KAVS0945-E

(O)Correct the value set in the label indicated in environment-setting-parameter-name on the host indicated logical-host-name. Then, for the physical

Seite 274 - KAVS0950-E

• If No such file or directory is indicated in maintenance-information-1, the judgment file indicatedin file-name does not exist. Make sure that the j

Seite 275 - KAVS0971-E

KAVS1842-EJob result information cannot be sent because an internal file (file-name) error occurred.: maintenance-information-1 (maintenance-informati

Seite 276 - KAVS0984-E

KAVS1844-EAn error occurred on the remote ftp host (host-name), so the job (job-name) cannot be executed.The queueless job indicated in job-name canno

Seite 277 - KAVS0987-E

(O)Recheck the job definition statement and correct the job definition. Then, execute the job.KAVS1847-WA job that was waiting for execution was forci

Seite 278 - KAVS0990-E

Examples:• In this example, the command detaches the logical host Lhost.Execute the ajsqldetach command as follows:ajsqldetach -h LhostFor details on

Seite 279 - KAVS0993-E

(4) KAVC6001 to KAVC7000 (messages for unknown status or operationfailure)These messages are displayed in a dialog box on JP1/AJS3 Console View. The

Seite 280 - KAVS0998-E

(S)Terminates the queueless file transfer service.(O)Take action according to the instructions given by the message that was output immediately before

Seite 281 - KAVS1003-E

An attempt to allocate shared memory or a system resource failed. If an account other than the service account is usedto execute jobs, jobs that use t

Seite 282 - KAVS1006-W

The queueless cluster process for the logical host (logical-host-name) terminated abnormally.(S)Terminates the queueless cluster process indicated in

Seite 283 - KAVS1009-W

(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

Seite 284 - KAVS1012-E

(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 hos

Seite 285 - KAVS1014-W

(O)Ensure that the manager host name and IP address are set in the hosts, jp1hosts, or jp1hosts2 file or in theDNS settings so that the IP address of

Seite 286 - KAVS1102-E

• Free disk space is insufficient.• Memory is insufficient.• The file indicated by file-name does not exist.• Access permission that allows the queuel

Seite 287 - KAVS1106-E

(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 queu

Seite 288 - KAVS1110-E

(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

Seite 289 - KAVS1114-E

KAVS1882-EThe 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

Seite 290 - KAVS1117-E

Message ID Output destinationsyslog EventlogHNTRLib2 stdout stderr Exec details JP1 eventKAVS0130 -- -- -- -- Y -- --KAVS0132 -KAVS0135Y Y Y -- -- --

Seite 291 - KAVS1122-E

This message is sometimes output if you register, delete, or change the password of an OS user while a job is startingor finishing. In this scenario,

Seite 292 - KAVS1124-E

KAVS1887-EInvalid data was received. (IPCID= IP-address)The system received invalid data from the connection source shown in IP-address.(S)Continues p

Seite 293 - KAVS1127-E

• If any message other than the above is indicated in maintenance-information-1, correct the error according tothe message.If you cannot correct the p

Seite 294 - KAVS1133-W

The shared-memory size is invalid.(S)Terminates the queueless agent service.(O)Take either of the following actions, and then restart the queueless ag

Seite 295 - KAVS1136-E

KAVS1896-EA log file (file-name) error occurred.: maintenance-information-1 (maintenance-information-2)An error occurred during processing required to

Seite 296 - KAVS1140-E

KAVS1898-IThe connection was reset by the peer.The connection between the queueless agent service and the queueless job request process or between the

Seite 297 - KAVS1143-E

KAVS1903-EThe queueless job request process (scheduler-service-name:identification-number) was blocked because themaximum number of abnormally ended q

Seite 298 - KAVS1200-E

(O)Correct the value of the concurrently-executable-job-limit, and then restart the scheduler service. For details on theenvironment setting parameter

Seite 299 - KAVS1302-I

KAVS1909-EThe queueless job (job-name) cannot be executed.The queueless job cannot be executed. The possible causes are:• The queueless job function h

Seite 300 - KAVS1420-I

KAVS1922-WThe connection with the queueless job execution agent (agent-name) was closed.: maintenance-informationThe connection to the queueless job e

Seite 301 - KAVS1502-E

Message ID Output destinationsyslog EventlogHNTRLib2 stdout stderr Exec details JP1 eventKAVS0247 -- -- Y -- -- -- --KAVS0248Y#5Y#5Y -- -- -- YKAVS024

Seite 302 - KAVS1512-E

(S)Stops forced termination of the job.(O)Retry forced termination of the job.KAVS1926-EA class name is specified for the execution destination host n

Seite 303 - KAVS1515-E

(S)If the message KAVS1922-W was output before this message, you need to check the status of the queueless job thatwas requested to be executed by the

Seite 304 - KAVS1516-E

Communication with the queueless job execution agent as indicated by agent-name was not recovered, so an attemptto send the job execution request fail

Seite 305 - KAVS1518-E

(O)The macro variable has not been inherited from the preceding job. Recheck the jobnet definition, and then re-executethe job.KAVS1940-EAn attempt to

Seite 306 - KAVS1572-W

KAVS1943-EThe 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

Seite 307 - KAVS1602-E

For details about AJSQL_CLUSTERREQ, see 2.7 Setting up the queueless job execution environment in the JobManagement Partner 1/Automatic Job Management

Seite 308 - KAVS1705-E

KAVS1955-EThe specified host (host-name)has already been attached.The specified host indicated in host-name has already been attached.(S)Cancels comma

Seite 309 - KAVS1713-E

Execute the ajsqlattach command as follows: ajsqlattach -h LhostFor details on the ajsqlattach command, see ajsqlattach in 3. Commands Used for Speci

Seite 310 - KAVS1715-E

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, s

Seite 311 - KAVS1718-E

If this message is output when the queueless cluster process is being started, execute the ajsqlstatus commandto make sure that the target host indica

Seite 312 - KAVS1721-I

Message ID Output destinationsyslog EventlogHNTRLib2 stdout stderr Exec details JP1 eventKAVS0500 Y Y Y -- -- -- --KAVS0530 -.KAVS0535Y#7Y#7Y -- -- --

Seite 313 - KAVS1724-E

KAVS1965-IThe 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

Seite 314 - KAVS1725-E

KAVS1969-IThe queueless cluster process (logical-host-name) will now stop.The queueless cluster process on the logical host (logical-host-name) will n

Seite 315 - KAVS1729-I

KAVS1973-EThe resources required for execution are insufficient, so the job (job-name) execution was not possible.The system could not execute the que

Seite 316 - KAVS1734-E

KAVS1976-ENo right is granted to access the execution file (file-name).The queueless job could not be executed because the OS user who executed the qu

Seite 317 - KAVS1738-E

(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 aUnix job. Then, re-execute the queu

Seite 318 - KAVS1742-E

KAVS1984-Imaintenance-informationA request for submitting a queueless job was accepted. For details about maintenance information, see C.2 Log entries

Seite 319 - KAVS1754-E

(S)Cancels command execution.(O)Check whether the OS user who executed the command has logged on as a member of the Administrators group (inWindows) o

Seite 320 - KAVS1758-E

If the service has started, wait a while and then retry the operation. If the retry does not correct the error, contact thesystem administrator and co

Seite 321 - KAVS1772-I

KAVS1991-EA communication timeout occurred during the communication with the service (service-name).: maintenance-informationA communication timeout e

Seite 322 - KAVS1777-E

If the error occurred when the queueless cluster process was being started, restart the JP1/AJS3 service.If the error occurred when the queueless clus

Seite 323 - KAVS1781-E

Message ID Output destinationsyslog EventlogHNTRLib2 stdout stderr Exec details JP1 eventKAVS0893 -- -- Y -- -- -- --KAVS0894 -KAVS0898-- -- -- -- Y -

Seite 324 - KAVS1785-E

KAVS1995-EThe command ended because an attempt to get the detailed information of the queueless agent service failed.The command ended, because an att

Seite 325 - KAVS1790-E

(S)Cancels the command.For the queueless cluster process, the system cancels the processing to attach the logical host. Then, by default, thesystem co

Seite 326 - KAVS1791-E

KAVS2030-IScheduler service (logical-host-name:scheduler-service-name) export started.Export of the scheduler service will now start.(S)Continues proc

Seite 327 - KAVS1803-E

KAVS2035-WScheduler service (logical-host-name : scheduler-service-name) import ended with warning. maintenance-informationImport of the scheduler ser

Seite 328 - KAVS1807-E

Import of the table will now start.(S)Continues processing.KAVS2040-ITable (table-name) import ended.Import of the table terminated.(S)Continues proce

Seite 329 - KAVS1809-E

KAVS2060-EEmbedded DB operation failed. (setup-identifier)(host-name)The database management process was unable to perform an embedded database operat

Seite 330 - KAVS1811-E

ActionTake action as described in 2.8 Troubleshooting problems related to the embedded database in the manual JobManagement Partner 1/Automatic Job Ma

Seite 331 - KAVS1813-E

KAVS2104-EEmbedded service is not set up.The embedded database has not been set up. Either the embedded database has not been set as the scheduler ser

Seite 332 - KAVS1815-E

A reloading attempt failed. This message appears when the embedded database does not have sufficient space duringexecution of the ajsembdbrorg -k reld

Seite 333 - KAVS1816-E

(S)Cancels command execution.(O)Use the ajsstatus command to check whether the embedded database is set as the scheduler service database.If the embed

Seite 334 - KAVS1817-E

Microsoft Exchange server is a product name of Microsoft Corporation in the U.S. and other countries.Microsoft Office and Excel are either registered

Seite 335 - KAVS1819-E

Message ID Output destinationsyslog EventlogHNTRLib2 stdout stderr Exec details JP1 eventKAVS0998 -KAVS0999Y Y Y -- -- -- YKAVS1002 -KAVS1008Y Y Y --

Seite 336 - KAVS1822-E

The specified option contains an error.One of the following is indicated in detailed-information:• Options (option) are needed.The mandatory or necess

Seite 337 - KAVS1825-E

For operations performed by an AJS administrator, permissions for the specified directory or file might beinsufficient. Check the access permissions f

Seite 338 - KAVS1828-E

KAVS2121-EDatabase file already exists.The file name of the file for the database area you attempted to create already exists. The file name already e

Seite 339 - KAVS1830-E

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

Seite 340 - KAVS1832-E

KAVS2128-EFailed to set up embedded service. : func code=function-code error code=error-codeAn attempt to set up the embedded database has failed.(S)T

Seite 341 - KAVS1833-E

• jajs_setup command• jajs_setup_cluster command• ajsembdbuninstl commandIn this case, take appropriate action for the message output to the standard

Seite 342 - KAVS1835-E

(S)Terminates setup processing.(O)Memory or free space on the disk may be insufficient. Terminate unnecessary applications or delete unnecessaryfiles

Seite 343 - KAVS1837-E

(O)Memory or free space on the disk may be insufficient. Terminate unnecessary applications or delete unnecessaryfiles to make more free space availab

Seite 344 - KAVS1839-E

KAVS3409-IAn attempt to connect to the Check Agent service (agent-name) has failed. : maintenance-informationAn attempt to connect the check agent ser

Seite 345 - KAVS1841-E

(O)Delete the specified host name, scheduler service name, and execution ID, and then re-execute the command.KAVS3413-IAn attempt to connect to the ch

Seite 346 - KAVS1843-E

Message ID Output destinationsyslog EventlogHNTRLib2 stdout stderr Exec details JP1 eventKAVS1602#10-- -- -- -- -- -- --KAVS1703 -KAVS1707-- -- -- --

Seite 347 - KAVS1846-E

(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 e

Seite 348 - KAVS1850-E

KAVS3420-IToo 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

Seite 349 - KAVS1854-E

KAVS3424-IThe setup of the function for pre-checking definitions execution environment could not be updated. : maintenance-information-1 maintenance-i

Seite 350 - KAVS1860-W

(O)Take action according to the instructions given by the message that was output immediately before this message. Ifa message beginning with KAVS34 t

Seite 351 - KAVS1864-E

(O)Set the value in the environment setting parameter correctly, and then restart JP1/AJS3 Check Manager or JP1/AJS3Check Agent.KAVS3431-IThe definiti

Seite 352 - KAVS1866-E

KAVS3433-IProcessing is cancelled due to failure to acquire agent information by using the function for pre-checkingdefinitions. : host-name maintenan

Seite 353 - KAVS1869-E

KAVS3436-IAn attempt to read the operation profile(profile-name) failed.The system could not load the operation profile specified at command execution

Seite 354 - KAVS1871-E

(O)To configure a new logical host to operate as the main site in disaster recovery mode, execute the jajs_rpsitecommand with the -m SET option specif

Seite 355 - KAVS1873-E

(S)Terminates command execution.KAVS3709-IThe logical host being used as the main site has been removed. (host: host-name)A message indicating that a

Seite 356 - KAVS1876-E

(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, pressN.KAVS

Seite 357 - KAVS1879-E

Message ID Output destinationsyslog EventlogHNTRLib2 stdout stderr Exec details JP1 eventKAVS1817 -KAVS1828Y Y Y -- -- Y --KAVS1829 Y Y Y -- Y Y --KAV

Seite 358 - KAVS1881-E

(S)Cancels execution of the command.(O)You cannot specify the following characters in command arguments:• In Windows^ & = ! @ ~ % " < >

Seite 359 - KAVS1884-E

• The file or directory cannot be createdIf you specified the -ld option for the ajsembdbbuild command in the exported environment, make surethat the

Seite 360 - KAVS1886-E

Command execution has been canceled.(S)Ends command execution.KAVS3800-EEmbedDB export processing ended abnormally. : maintenance-informationAn error

Seite 361 - KAVS1889-E

KAVS3803-EEmbedDB service is not installed.The embedded database is not installed.(S)Cancels execution of the command.(O)The probable causes are as fo

Seite 362 - KAVS1892-E

Create the directory after checking the path you specified in the -bl option when executing the ajsembdbbuildcommand.If you do not create this directo

Seite 363 - KAVS1894-E

KAVS3910-EInterprocess communication failed. : maintenance-information-1 maintenance-information-2 maintenance-information-3Interprocess communication

Seite 364 - KAVS1897-E

(O)Determine the cause of the error from the error message that was output before this message, and correct the causeof the error. Then specify the un

Seite 365 - KAVS1902-W

KAVS4203-EDeletion of an unnecessary macro variable failed during creating a generation of jobnet (jobnet-name). Generationcreation (execution-ID) is

Seite 366 - KAVS1905-W

An error occurred during restructuring of a file, such as the standard error output file under the job information storagefolder, for one of the follo

Seite 367 - KAVS1908-W

• 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 jobn

Seite 368 - KAVS1921-E

Message ID Output destinationsyslog EventlogHNTRLib2 stdout stderr Exec details JP1 eventKAVS1891 -KAVS1898Y Y Y -- -- -- --KAVS1900 -KAVS1908Y Y Y --

Seite 369 - KAVS1925-E

KAVS4608-ECannot delete the unit(unit-name) - jobnet connector exist.When you delete the registered unit information, a unit that contains a jobnet co

Seite 370 - KAVS1929-I

(S)Cancels command execution.(O)Check the registration status of the unit, and then re-execute the command.KAVS4612-EJobnet connector(unit-name) can o

Seite 371 - KAVS1931-E

(S)Terminates processing. However, if multiple units are specified, the system continues processing of other units.(O)Change the unit configuration, a

Seite 372 - KAVS1939-E

(S)Terminates processing. However, if multiple units are specified, the system continues processing of other units.(O)Change the unit configuration, a

Seite 373 - KAVS1942-E

KAVS4625-EThe type cannot be specified for the release target jobnet. : maintenance-informationSpecification of the release target jobnet contains an

Seite 374 - KAVS1953-E

KAVS4628-EThe state of release wait, delete wait, or release entry wait does not exist. : unit-nameAn attempt was made to cancel the release of a jobn

Seite 375 - KAVS1954-E

KAVS4631-WThe jobnet definition for the applied where the generation did not exist could not be deleted.Release entry terminated normally, but a jobne

Seite 376 - KAVS1956-E

(S)Cancels command execution.(O)Make sure that a jobnet definition whose status is Being applied exists, and then re-execute the command.KAVS4635-ECan

Seite 377 - KAVS1960-E

Operation is impossible because a jobnet with start conditions is specified as the connection-destination jobnet for therelease target or release sour

Seite 378 - KAVS1962-E

KAVS4646-EAn unnecessary jobnet was defined. Resolve the problem, cancel the release, and then entry the release again.An unnecessary jobnet definitio

Seite 379 - KAVS1964-E

Message ID Output destinationsyslog EventlogHNTRLib2 stdout stderr Exec details JP1 eventKAVS1970 -- Y Y -- -- -- --KAVS1971 -KAVS1977Y Y Y -- -- Y --

Seite 380 - KAVS1968-I

(O)Check whether the scheduler service is running. After checking the cause of the error, retry the operation.KAVS4650-ECannot operate - Jobnet has be

Seite 381 - KAVS1972-E

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-ENo

Seite 382 - KAVS1975-E

• The specified unit whose end is being waited for was deleted from the wait condition definition while the commandwas executing• No unit names match

Seite 383 - KAVS1979-E

(S)Cancels command execution. If you specify multiple units (including by regular expression), the system continuesprocessing from the next unit.(O)Sp

Seite 384 - KAVS1983-I

Temporary change information could not be deleted.(S)Cancels the deletion of temporary change information and continues processing.(O)The internal fil

Seite 385 - KAVS1986-E

KAVS4677-EAn error that cannot be recoverd by retry execution occurred.(name: job-name: execution-ID, code: return-code,host: host-name, JOBID: job-nu

Seite 386 - KAVS1989-E

KAVS4700-EThe jobnet connector (jobnet-name:execution-ID) ended abnormally because it failed to connect to the connectiondestination jobnet.The jobnet

Seite 387 - KAVS1990-E

The jobnet connector cannot be executed because the specified connection-destination jobnet is invalid. The probablecauses are:• The unit specified fo

Seite 388 - KAVS1992-E

• 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 connec

Seite 389 - KAVS1994-E

• The RJCUSE environment setting parameter is not set to yes.• The scheduler service inter-communication control process has stopped.The jobnet connec

Seite 390 - KAVS1998-E

Message ID Output destinationsyslog EventlogHNTRLib2 stdout stderr Exec details JP1 eventKAVS3411 -KAVS3413-- -- -- Y -- -- --KAVS3414 -KAVS3423-- --

Seite 391 - KAVS1999-E

KAVS4713-ECannot execute the jobnet connector (jobnet-name) because the connection range of the jobnet of the connectiondestination is invalid.The job

Seite 392 - KAVS2034-I

KAVS4716-ECannot execute the jobnet of the connection destination (jobnet-name) because the connection range of the jobnetconnector is invalid.The con

Seite 393 - KAVS2039-I

KAVS4722-IReconnection processing with the process controlling communication between scheduler services started.(scheduler-service-name)Reconnection p

Seite 394 - KAVS2046-I

• The number of connections that the scheduler service inter-communication control process uses for communicationhas exceeded the maximum.• The schedu

Seite 395 - KAVS2060-E

KAVS4732-ECannot execute the jobnet (jobnet-name) of the connection destination because it failed to resolved to the localhost name (host:host-name).T

Seite 396 - KAVS2103-E

(O)If the status of the jobnet definition that has the release ID indicated in release-ID is Release wait, follow theprocedure below:1. Unregister the

Seite 397 - KAVS2107-E

If the message appears when one of the following operations is performed, take appropriate action as shown below.• If the message appears during relea

Seite 398 - KAVS2113-E

(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

Seite 399 - KAVS2116-E

(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 Windo

Seite 400 - KAVS2117-E

(O)Take action according to the instructions given by the error message that was output before this message. See theoutput command line and take corre

Seite 401 - KAVS2120-E

Message ID Output destinationsyslog EventlogHNTRLib2 stdout stderr Exec details JP1 eventKAVS4624 -KAVS4630-- -- -- -- Y -- --KAVS4631 Y Y Y -- Y -- -

Seite 402 - KAVS2124-E

KAVS4836-EThe specified unit (unit-name) can not be exported either because it does not exist or execution registration hasnot been performed.The unit

Seite 403 - KAVS2127-E

(S)Continues the command.(O)Specify a root jobnet that has a scheduled generation.KAVS4900-IThe process controlling communication between scheduler se

Seite 404 - KAVS2128-E

KAVS4904-IThe management process for the process controlling communication between scheduler services has terminated.This message reports that the man

Seite 405 - KAVS3400-I

(S)Continues processing.Note that you cannot use the execution order control for root jobnets between processing scheduler services untilthe number of

Seite 406 - KAVS3404-I

(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, che

Seite 407 - KAVS3408-I

(S)Terminates communication.(O)Check the environment for communication with the process.KAVS4913-EThe port number could not be obtained. Confirm wheth

Seite 408 - KAVS3412-I

(S)Restarts the scheduler service inter-communication control process.KAVS4916-WThe process (host:host-name) controlling communication between schedul

Seite 409 - KAVS3416-I

Because the number of connections for the scheduler service inter-communication control process is below the maximumvalue, execution order control for

Seite 410 - KAVS3419-I

Setup of the AJS administrator will now start.(S)Continues installation.KAVS4934-EThe AJS administrator name is invalid.The AJS administrator name spe

Seite 411 - KAVS3423-I

(S)Cancels installation.(O)Specify an existing OS user as an AJS administrator, and then retry the installation.KAVS4938-EThe AJS administrator cannot

Seite 412 - KAVS3425-I

Message ID Output destinationsyslog EventlogHNTRLib2 stdout stderr Exec details JP1 eventKAVS4900 -KAVS4918Y Y Y -- -- -- --KAVS4931 -- -- -- -- Y --

Seite 413 - KAVS3430-I

• The user is neither an AJS administrator nor a superuser.• The JP1 administrators group name was changed.• The OS user specified as the AJS administ

Seite 414 - KAVS3432-I

KAVS4952-EWaiting for the end of the preceding unit (name: unit-full-name:execution-ID) was not possible because an erroroccurred. : maintenance-infor

Seite 415 - KAVS3435-I

KAVS4955-IThe wait conditions for the jobnet (name: unit-full-name:execution-ID) were approved. (approval factor: approval-factor)The wait conditions

Seite 416 - KAVS3702-E

The message outputs the execution ID of the jobnet that cannot finish waiting if yes is specified for the LOGINFOALLenvironment setting parameter.(S)C

Seite 417 - KAVS3708-I

to save one day's worth of execution results for the unit with wait conditions and the unit whose end is beingwaited for.If you cannot take this

Seite 418 - KAVS3752-Q

(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:Ca

Seite 419 - KAVS3755-E

KAVS4971-EA job (name: unit-full-name:execution-ID) cannot finish waiting because the unit whose end is to be waited for(name: unit-full-name:executio

Seite 420 - KAVS3757-E

3. The number of saved generations of the unit with wait conditions, the unit whose end is being waited for, orboth is not sufficient to save the exec

Seite 421 - KAVS3784-I

KAVS4975-EThe preceding unit wait function cannot be used (scheduler-service-name). : maintenance-information-1maintenance-information-2 maintenance-i

Seite 422 - KAVS3802-E

(O)The unit with wait conditions is an invalid type. For details about which units are capable of accepting waitconditions, see 2.2.5(1)(a) Units with

Seite 423 - KAVS3805-W

Message ID Output destinationsyslog EventlogHNTRLib2 stdout stderr Exec details JP1 eventKAVS8015 -KAVS8023-- --Y#13--Y#13-- --KAVS8028 -- -- Y -- Y -

Seite 424 - KAVS3853-I

(S)Cancels processing.(O)Review the contents of the operation profile, and apply it again. You can apply an operation profile by the following:• Execu

Seite 425 - KAVS4200-E

KAVS8008-EYou do not have the permissions required to use the operation profile. :maintenance-informationYou do not have access permission for the ope

Seite 426 - KAVS4202-E

(S)Terminates command processing.(O)Check the value specified for the UNITPROFMEMSIZE or AGENTPROFMEMSIZE environment setting parameters,and then re-e

Seite 427 - KAVS4209-W

DBERR: Take action according to the message beginning with KAVS that was output immediately before thismessage.LOCKERR: Check for disk failures or oth

Seite 428 - KAVS4602-E

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

Seite 429 - KAVS4607-E

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

Seite 430 - KAVS4611-E

For an execution agent profile:• One or more of the following entries is in the wrong location:@SYS_RESTRICT_STARTunit_pathViewViewCheckLevelJobExec@S

Seite 431 - KAVS4615-E

(O)Take action according to the message KAVS8004-E together with this message.KAVS8022-EThe specified of the executing agent exceeds the maximum. Line

Seite 432 - KAVS4619-E

(O)Check and, if necessary, revise the contents of the connection permission configuration file and then execute thejajs_pmtcon command. For details a

Seite 433 - KAVS4624-E

An error occurred during the processing of the connection source restriction function.The nature of the error is indicated as follows in cause-code:•

Seite 434 - KAVS4627-E

For details about the environment setting parameters, see 2.2 Setting up the scheduler service environment in the Job Management Partner 1/Automatic J

Seite 435 - KAVS4630-E

KAVS8034-EThe connection permitted hosts list cannot be refreshed because the connection source restriction function isdisabled.The list of hosts perm

Seite 436 - KAVS4634-E

(S)Continues processing.(O)Check and, if necessary, revise the contents of the connection permission configuration file, and then re-execute thecomman

Seite 437 - KAVS4639-E

2. Execute the jajs_pmtcon command to apply the change to the connection permission configuration file.3. If necessary, perform the request processing

Seite 438 - KAVS4645-E

2.4 Messages beginning with KAVT (Messages about the event/actioncontrol)This section lists the messages that begin with KAVT (Messages about the eve

Seite 439 - KAVS4649-E

• Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of theAdministrators group.• Check whether the con

Seite 440 - KAVS4655-E

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 u

Seite 441 - KAVS4660-E

KAVT0027-EThe cold start processing failed. (maintenance-information)An attempt to perform a cold start on the event/action control manager has failed

Seite 442 - KAVS4670-I

(O)Check the following, and then use the ajsname command with the -I option to identify the job name from theunit ID. Make sure that the status of the

Seite 443 - KAVS4673-W

KAVT0045-EThe icon will now end because an error occurred.An error occurred during the start of an event.(S)Continues processing.(O)The error is cause

Seite 444 - KAVS4676-I

KAVT0062-EAn error occurred during processing of the request to end start-condition monitoring. (maintenance-information)(AjsServiceName=scheduler-ser

Seite 445 - KAVS4699-I

Abbreviation Full name or meaningExcel Microsoft(R) Office ExcelExchange Server Microsoft(R) Exchange 2000 Enterprise ServerMicrosoft(R) Exchange 2000

Seite 446 - KAVS4703-E

Message ID Output destinationsyslogEventlogHNTRLib2stdout stderr ExecdetailsJP1eventKAVT0023 -- --Y#1-- -- -- --KAVT0025 -KAVT0027-- --Y#1-- -- -- --K

Seite 447 - KAVS4706-E

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 t

Seite 448 - KAVS4710-E

• Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of theAdministrators group.• Check whether the dir

Seite 449 - KAVS4712-E

(S)Continues processing.KAVT0101-EAn error occurred during resending of unreported information. (maintenance-information) (host=agent-host-name, AjsSe

Seite 450 - KAVS4715-E

• Check whether the IP address obtained by resolving the agent host name on the manager host is the same as theactual IP address of the agent host.If

Seite 451 - KAVS4721-E

KAVT0108-IThe start condition was satisfied. (AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID)The start condition was satis

Seite 452 - KAVS4725-E

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

Seite 453 - KAVS4731-E

KAVT0147-EAn error occurred during the processing of an event for reporting the shutdown of an agent machine. (maintenance-information) (host=agent-ho

Seite 454 - KAVS4750-E

• Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of theAdministrators group.• Check whether the dir

Seite 455 - KAVS4752-E

KAVT0193-WThe events that occurred during the maintenance mode are discarded because the option to improve event jobreliability is invalid. (scheduler

Seite 456 - KAVS4824-E

KAVT0250-WBecause the total of macro variables exceeded the maximum, part of the data was truncated.(maintenance-information)The total number of macro

Seite 457 - KAVS4828-E

Message ID Output destinationsyslogEventlogHNTRLib2stdout stderr ExecdetailsJP1eventKAVT0287 -- --Y#1-- -- -- --KAVT0288 -KAVT0289-- -- Y -- -- -- --K

Seite 458 - KAVS4832-E

For details on this time, see Table 2-3 in 2.2.2(5) Notes on manager/agent system configurations in the JobManagement Partner 1/Automatic Job Manageme

Seite 459 - KAVS4835-E

(O)On the manager host, use the jp1ping command to check whether the IP address of the host indicated by name-of-host-whose-IP-address-could-not-be-ob

Seite 460 - KAVS4839-I

(O)The error is caused by an internal factor of the event/action control. Contact the system administrator and collectdata (see 1.2.3 To the system ad

Seite 461 - KAVS4903-I

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

Seite 462 - KAVS4907-W

KAVT0288-IDisaster recovery start processing will be performed.The event/action control manager on the remote site is beginning the disaster recovery

Seite 463 - KAVS4909-E

If the IP address of the agent host indicated by host=agent-host-name cannot be acquired, configure DNS and hostsso that the IP address is resolved, a

Seite 464 - KAVS4912-E

(S)Deletes unreported information for the agent, beginning from the oldest item, each time the threshold is exceeded.This action might result in the f

Seite 465 - KAVS4915-I

In UNIX:The host name indicated after the jajs_spmd process that is displayed by executing the ps commandKAVT0297-WUnreported information will now be

Seite 466 - KAVS4918-I

event detection might be seriously delayed. To avoid these problems, cold-start the agent if 1,000 or more eventshave been detected within a few hours

Seite 467 - KAVS4933-I

The event/action control submanager will terminate because the event/action control manager has terminated.(S)Terminates the event/action control subm

Seite 468 - KAVS4937-E

Message ID Output destinationsyslogEventlogHNTRLib2stdout stderr ExecdetailsJP1eventKAVT0542 -- --Y#1-- -- Y --KAVT0544 -- --Y#1-- -- -- --KAVT0559 --

Seite 469 - KAVS4943-E

KAVT0333-WThe number of the reported events from agent-name exceeds threshold. Processing the events from agent-namemight be delayed. (maintenance-inf

Seite 470 - KAVS4951-I

KAVT0340-WCommunication to check the operation of the Event Action SubManager failed. The communication will be retried.(maintenance-information)A com

Seite 471 - KAVS4954-E

• Check whether communication is possible with all the target hosts displayed by the ajsagtshow command.• Check whether any process is accessing a fil

Seite 472 - KAVS4957-E

• Check whether any process is accessing a file in the JP1/AJS3 installation path.• Check whether memory is sufficient.Correct the above problems, and

Seite 473

KAVT0347-IA response from the Event Action Manager has been confirmed.(maintenance-information)A response from the event/action control manager has be

Seite 474 - KAVS4962-E

• If the message KAVT0353-I is output after this messageThe connection has recovered. Ignore the message and continue operation.• If the message KAVT0

Seite 475

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 intern

Seite 476 - KAVS4971-E

(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 co

Seite 477 - KAVS4973-I

(O)Wait until the change of the configuration definition information (environment setting) terminates, than then retry.KAVT0409-IThe data was sent to

Seite 478 - KAVS4977-E

#1For the compatible ISAM configuration, 30 minutes.#2For the compatible ISAM configuration, 15 minutes.(S)Continues processing.(O)Startup of a jobnet

Seite 479 - KAVS8004-E

Message ID Output destinationsyslogEventlogHNTRLib2stdout stderr ExecdetailsJP1eventKAVT0901 -- -- -- -- -- -- YKAVT0910 -KAVT0911-- --Y#1-- -- -- --K

Seite 480 - KAVS8007-I

KAVT0414-EThe request was rejected. (AjsServiceName=scheduler-service-name, UnitID=unit-ID, ExecID=execution-ID,maintenance-information)The request wa

Seite 481 - KAVS8011-E

KAVT0508-EA message-reception pipe could not be opened. (process type=process-type maintenance-information) (processname=process-name, maintenance-inf

Seite 482 - KAVS8013-E

KAVT0512-EThe socket could not be opened. (Manager=name-of-manager-at-send-destination) (maintenance-information)Communication with the manager host f

Seite 483 - KAVS8015-E

KAVT0515-EMain loop of an agent failed. (maintenance-information)An attempt to start the event/action control agent has failed.(S)Terminates the event

Seite 484 - KAVS8018-E

(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 an

Seite 485 - KAVS8020-E

• Check whether an executable file with the same name as the process name indicated in processname=process-name exists.• Check whether the user who st

Seite 486 - KAVS8021-E

KAVT0530-EThe end request for the pipe could not be written. (process type=process-type maintenance-information) (processname=process-name, maintenanc

Seite 487 - KAVS8028-E

KAVT0541-EThe pipe could not be written to. (process type=process-type maintenance-information)An attempt to write to a pipe file used in the event/ac

Seite 488 - KAVS8033-E

An attempt to read a communication information file for a monitoring process used in the event/action control agenthas failed.(S)Places the job in the

Seite 489

(S)Terminates the event/action control agent.KAVT0566-EThe size of the working path exceeds the limit.The length of any of the following directory nam

Seite 490 - KAVS8037-E

Message ID Output destinationsyslogEventlogHNTRLib2stdout stderr ExecdetailsJP1eventKAVT1062 -KAVT1067-- --Y#1-- -- -- --KAVT1068 -- --Y#1-- -- Y --KA

Seite 491 - KAVS8039-E

(S)Continues processing, but does not accept the jajs_spmd_stop command or a stop request from the JP1/AJS3service.(O)To terminate the event/action co

Seite 492 - KAVS8040-E

See the following supplementary notes and check whether the manager and agent can communicate witheach other.Supplementary notes• Check whether the ag

Seite 493

• The WaitInfFileOutDir environment setting parameter for the definition key ([JP1AOMAGENT])(S)Terminates processing.(O)Specify the following director

Seite 494 - KAVT0023-E

KAVT0593-WThe MS message queue monitoring function is unusable. (maintenance- information, process name=process-name, maintenance-information)The MSMQ

Seite 495 - KAVT0026-I

The agent attempted to report the status of an event job to the manager, but could not communicate with the managerindicated in manager-name due to a

Seite 496 - KAVT0036-E

(O)The job may remain in the queue or in the execution status while the event is established. Check the job executionstatus.KAVT0609-WThe socket recei

Seite 497 - KAVT0043-I

The agent reported the status of an event job to the manager, but could not confirm the arrival of data from the managerindicated in manager-name due

Seite 498 - KAVT0059-E

KAVT0615-WUnreported information resend max over. Unreported information will be abandoned. (Manager=manager-name)The agent retried communicating with

Seite 499 - KAVT0084-E

• Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of theAdministrators group.• Check whether the dir

Seite 500 - KAVT0092-E

(S)Terminates the event/action control agent.(O)Check the following, and then restart JP1/AJS3:• Check whether system resources are sufficient.• Check

Seite 501 - KAVT0099-I

Message ID Output destinationsyslogEventlogHNTRLib2stdout stderr ExecdetailsJP1eventKAVT3041 -- -- Y -- -- Y --KAVT3042 -KAVT3206-- -- Y -- -- -- --KA

Seite 502 - KAVT0103-E

KAVT0632-EThe agent pipe could not be written to. (code=maintenance-code) (host= manager-host-name,AjsServiceName=scheduler-service-name, UnitID=unit-

Seite 503 - KAVT0106-I

• Check whether the user who started JP1/AJS3 has superuser privileges or has logged on as a member of theAdministrators group.• Check whether the dir

Seite 504 - KAVT0116-E

(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 ou

Seite 505 - KAVT0145-E

• Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.KAVT0649-EA host name in the FQDN format could not be obtai

Seite 506 - KAVT0171-E

KAVT0654-EThe files will be deleted, because the internal files of event action control have been destroyed. (maintenance-information)The files will b

Seite 507 - KAVT0187-E

For details about the jpoagoec command, see jpoagoec in 2. Commands in the manual Job Management Partner1/Automatic Job Management System 3 Command Re

Seite 508 - KAVT0247-E

memory was output at the same time the error occurred. If a log indicating insufficient memory was output, recheckthe memory estimate. If other unnece

Seite 509 - KAVT0268-W

For details about the detail process termination option, see 2.4 Setting up the event/action control environmentin the Job Management Partner 1/Automa

Seite 510 - KAVT0272-E

KAVT0954-IOpenView Environment of JP1/AJS2 was uninstalled normally.HP NNM Link was uninstalled normally.(S)Continues processing.KAVT0955-ISymbol of J

Seite 511 - KAVT0281-E

KAVT0961-IResource status to be online.The resource is placed online.(S)Continues processing.KAVT0962-IResource monitoring bring to a termination.Reso

Seite 512 - KAVT0284-E

Message ID Output destinationsyslogEventlogHNTRLib2stdout stderr ExecdetailsJP1eventKAVT3513 Y Y Y -- -- Y --KAVT3514 Y Y Y -- -- -- --KAVT3515 Y Y Y

Seite 513 - KAVT0287-E

reduce the number of events to be generated. You can obtain the name of the jobnet with start conditions in thefollowing procedure:1. Check the schedu

Seite 514 - KAVT0293-W

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 queuin

Seite 515 - KAVT0296-W

If the name cannot be resolved, review the settings in the hosts file, jp1hosts information, orjp1hosts2 information on the manager host or in the DNS

Seite 516

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 connec

Seite 517 - KAVT0297-W

(O)Use the jbsgetcnf command to check whether you can acquire common definition information for the logicalhost that caused the error. If you cannot a

Seite 518 - KAVT0325-E

(O)Check whether the JP1/Base event service has started.KAVT1008-EInitialization error (maintenance-information) (maintenance-information)Initializati

Seite 519 - KAVT0332-W

KAVT1015-EThe log-file trap command could not start. (maintenance-information)An attempt to start the Monitoring Log Files job has failed.(S)Places th

Seite 520 - KAVT0333-W

KAVT1026-WThe end judgment file includes no data. (end-judgment-file-name)The end judgment file specified in the Receive JP1 Event job does not contai

Seite 521 - KAVT0341-W

KAVT1029-EThe event could not be created. (maintenance-information) (maintenance-information)An attempt to connect to the JP1/Base event service has f

Seite 522 - KAVT0344-W

(S)Interprocess communication failed. The system continues processing. If the error occurred during registration,registration of the event job will be

Seite 523 - KAVT0346-I

Message ID Output destinationsyslogEventlogHNTRLib2stdout stderr ExecdetailsJP1eventKAVT3845 -KAVT3846-- -- Y -- -- Y --KAVT3847 -KAVT3849-- -- Y -- Y

Seite 524 - KAVT0352-E

(S)Retries connection to the JP1/Base event service. No events can be monitored until the KAVT1004-I or KAVT1044-I message is output.(O)See the descri

Seite 525 - KAVT0401-E

(O)Check whether the system resources are sufficient, and then re-execute the Monitoring Log Files job.KAVT1046-EThe event ID is invalid. (maintenance

Seite 526 - KAVT0404-E

(O)Follow the instructions given by the message that was output immediately before this message, and then restart JP1/AJS3.KAVT1052-WThe log-file trap

Seite 527 - KAVT0408-E

KAVT1058-Iretry again.A temporary error occurred. The system re-executes the log file trapping command.(S)Continues processing.KAVT1059-IWatching star

Seite 528 - KAVT0412-W

(O)Check whether memory is sufficient.For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in ReleaseNotes

Seite 529 - KAVT0413-E

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

Seite 530 - KAVT0502-E

(S)Cancels processing.(O)Check whether memory is sufficient.For details on the amount of memory required, see JP1/Base Release Notes.KAVT1202-EThe rea

Seite 531 - KAVT0511-E

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

Seite 532 - KAVT0513-E

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 filt

Seite 533 - KAVT0521-W

KAVT1217-IAn instance was established by the search for events prior to execution. (job-name, Event Arrived Time=arrival-time-of-event-satisfying-cond

Seite 534 - KAVT0523-W

Message ID Output destinationsyslogEventlogHNTRLib2stdout stderr ExecdetailsJP1eventKAVT4198 -KAVT4202-- -- Y -- -- Y --KAVT4203 -KAVT4216-- -- Y -- -

Seite 535 - KAVT0526-E

KAVT2005-IThe file (file-name) was deleted.The file was deleted.(S)Continues processing.KAVT2006-IThe last modification time of file (file-name) has c

Seite 536 - KAVT0539-E

KAVT2014-EThe 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)Abno

Seite 537 - KAVT0544-E

The request to forcibly cancel a job is accepted. The job is forcibly canceled.(S)Forcibly cancel the job by the request.KAVT2019-EThe file monitoring

Seite 538 - KAVT0563-I

(S)Checks again whether there is a process that has opened the file at the next execution interval. Establishment of thefile monitoring event job is d

Seite 539 - KAVT0570-E

Specify at least ten seconds for the monitoring interval.(S)Abnormally terminates the file monitoring job due to the invalid monitoring interval speci

Seite 540 - KAVT0582-W

KAVT2029-EAn attempt to obtain pipe data failed. (maintenance-information) (maintenance-information)The pipe data could not be received from the agent

Seite 541 - KAVT0588-E

• Check whether the following message was output in the same time zone: KAVT2034-W The statuspassing option file cannot be opened. The status passing

Seite 542 - KAVT0591-E

(O)Check the following:• Check whether system resources are sufficient.• Check whether the directory created at JP1/AJS3 installation was unintentiona

Seite 543 - KAVT0606-W

A file with the specified monitoring condition was updated, but the sum of the size of the values specified in macrovariables exceeded 4,096 bytes.(S)

Seite 544 - KAVT0608-W

KAVT3002-IMail could not be received.Mail could not be received.(S)Cancels processing.(O)Check whether the environment is set up to send and receive m

Seite 545 - KAVT0612-W

Message ID Output destinationsyslogEventlogHNTRLib2stdout stderr ExecdetailsJP1eventKAVT4527 -KAVT4528-- --Y#1-- -- Y --KAVT4529 -KAVT4531-- --Y#1-- -

Seite 546 - KAVT0613-W

KAVT3006-EInitialization failed. (reason)Initialization was impossible.(S)Cancels processing.(O)Check whether the environment is set up to send and re

Seite 547 - KAVT0618-E

KAVT3015-IThe result of logon. (mapi_code=maintenance-information maintenance-information maintenance-informationmaintenance-information)This message

Seite 548 - KAVT0625-E

(S)Cancels processing.(O)If the error occurred due to insufficient memory, allocate sufficient memory for execution, and then retry. For detailson the

Seite 549 - KAVT0629-E

In addition, check whether Microsoft Outlook can send and receive email independently of JP1/AJS3 and whethera dialog box prompting the user to respon

Seite 550 - KAVT0635-E

job ends abnormally in the manual Job Management Partner 1/Automatic Job Management System 3Troubleshooting.In addition, check whether Microsoft Outlo

Seite 551 - KAVT0642-E

KAVT3038-EThe send processing could not be preprocessed.Preprocessing a send was impossible.(S)Cancels processing.(O)Check whether the environment is

Seite 552 - KAVT0646-E

Logoff for reception processing was impossible.(S)Cancels processing.(O)Check whether the mail server has gone down or a profile is created correctly.

Seite 553 - KAVT0651-E

KAVT3051-EMail could not be read. (reason)Reading mail was impossible.(S)Cancels processing.(O)Check whether the environment is set up to send and rec

Seite 554 - KAVT0663-W

KAVT3061-EThe received mail could not be read. (reason)Reading mail to receive was impossible.(S)Cancels processing.(O)Check whether the environment i

Seite 555 - KAVT0911-E

KAVT3070-EThe attached file could not be saved. (reason)Saving an attached file was impossible.(S)Cancels processing.(O)Check whether the environment

Seite 556 - KAVT0912-E

Abbreviation Full name or meaningWindows Server 2008 Windows Server 2008 Microsoft(R) Windows Server(R) 2008 EnterpriseMicrosoft(R) Windows Server(R)

Seite 557 - KAVT0953-I

Message ID Output destinationsyslogEventlogHNTRLib2stdout stderr ExecdetailsJP1eventKAVT4586 -KAVT4591-- --Y#1-- -- Y --KAVT4593 -- --Y#1-- -- -- --KA

Seite 558 - KAVT0960-I

(O)Take action according to the error code indicated in the message (return code from the WindowsGetLastError() function).KAVT3076-EThe opening-comple

Seite 559 - KAVT0980-W

KAVT3080-EDuring reception processing, a file could not be saved.Saving a file was impossible for reception processing.(S)Continues processing.(O)Chec

Seite 560

KAVT3086-EDuring reception processing, logoff failed. (reason)Logoff was impossible for reception processing.(S)Cancels processing.(O)Check whether th

Seite 561 - KAVT0981-W

(S)Continues processing.KAVT3201-IStart process of controlling MAPI (Receive).The MAPI receive control process starts.(S)Continues processing.KAVT3202

Seite 562 - KAVT0992-E

KAVT3205-EFailed to read a temporary file. file=file-name GetLastError=GetLastError-numberA temporary file to be used for mail system linkage could no

Seite 563 - KAVT1003-E

The specified email address was not found in the send destination mail system. Alternatively, the mail system in whichthe email address has been regis

Seite 564 - KAVT1007-W

• 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 addre

Seite 565 - KAVT1014-E

KAVT3273-IProcessing of mail sending will now start.The mail transmission starts.(S)Continues processing.KAVT3274-IProcessing of mail sending will now

Seite 566 - KAVT1025-W

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

Seite 567 - KAVT1028-E

(O)Check whether JP1/AJS3 is installed correctly and whether the information is correctly set for the environmentsetting parameters to be used for mai

Seite 568 - KAVT1032-E

Message ID Output destinationsyslogEventlogHNTRLib2stdout stderr ExecdetailsJP1eventKAVT7001 -KAVT7002-- --Y#1-- -- -- --KAVT7003 -- -- -- -- -- Y --K

Seite 569 - KAVT1040-E

KAVT3282-EAn unexpected error occurred. (return-code-of-GetLastError-function)An unexpected error occurred in the email sending job.(S)Cancels process

Seite 570 - KAVT1045-E

KAVT3286-ECommunication of mail information failed.Communicating the mail information was impossible.(S)Cancels processing.(O)Check whether the JP1/AJ

Seite 571 - KAVT1050-E

If you cannot take corrective action, contact the system administrator, and collect data (see 1.2.3 To the systemadministrators).KAVT3290-EMemory beca

Seite 572 - KAVT1056-W

(O)Check the error details by comparing return-code-of-MAPI-function with the following MAPI codes, and then takeaction. Also see the manual Job Manag

Seite 573 - KAVT1062-W

An invalid character is used in the environment settings for the mail linkage function.(S)Cancels processing.(O)Check the contents indicated in execut

Seite 574 - KAVT1067-E

KAVT3300-EThe folder specified for storing the list of attached files does not exist. (folder-name)A folder that stores the attached file lists does n

Seite 575 - KAVT1201-E

KAVT3304-EThe attached files or list of attached files could not be read.Reading the attached file or attached file list was impossible.(S)Cancels pro

Seite 576 - KAVT1205-E

KAVT3405-IThe JP1/AJS2 mail monitoring process will now end.The JP1/AJS3 mail monitoring process stops.(S)Continues processing.KAVT3406-IJP1/AJS2 Mail

Seite 577 - KAVT1211-E

(O)Check whether JP1/AJS3 is installed correctly and whether the information is correctly set for the environmentsetting parameters to be used for mai

Seite 578 - KAVT1214-E

KAVT3453-IThe mail linkage communication process stopped.The mail linkage communication process has stopped.(S)Terminates processing.KAVT3454-IMail re

Seite 579 - KAVT2004-I

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 int

Seite 580 - KAVT2013-E

KAVT3458-IMethod of mail monitor is "JP1/AJS2 Mail Service" -or- "JP1/AJS2 Mail Process".This message shows the method of mail mon

Seite 581 - KAVT2018-W

KAVT3462-WA macro variable exceeds 4096 bytes. Some macro variables could not be created.The macro variable exceeded 4,096 bytes. Some macro variables

Seite 582 - KAVT2022-W

The email reception monitoring job is defined incorrectly.(S)Cancels processing.(O)Correct the definitions of the email reception monitoring job, and

Seite 583 - KAVT2025-E

KAVT3473-EThe count of the mail monitoring job is over a max job's count. (Max job's count=maximum-registration-count)The number of register

Seite 584 - KAVT2028-E

KAVT3504-EFailed to analyze job data. (DB-data) (error-code-of-function)A failure occurred in the function that analyzes job data.(S)Cancels processin

Seite 585 - KAVT2031-E

(O)Check whether:• The system resources are sufficient.• The permission environment of the started user is correct.• The directory created during inst

Seite 586 - KAVT2034-W

KAVT3521-WAn error occurred during analysis of macro variables. (maintenance-information) (maintenance-information)An error occurred while analyzing a

Seite 587 - KAVT2037-W

(S)Cancels processing, and continues processing after a monitoring interval elapses.(O)If this message is output more than once, determine the cause o

Seite 588 - KAVT3001-I

(O)Determine the cause of the error from the maintenance information, and take appropriate action.KAVT3532-WMail File(maintenance-information)could no

Seite 589 - KAVT3005-E

(S)Continues processing.(O)Check the content of the environment definition, and then restart JP1/AJS3 and reload.KAVT3539-WNo monitoring user name is

Seite 590 - KAVT3014-E

Message ID Output destinationsyslog EventlogHNTRLib2 stdout stderr ExecdetailsJP1eventKAVU0236 -- --Y#1-- -- -- --KAVU0237 -KAVU0242Y#2Y#2Y#1-- -- --

Seite 591 - KAVT3019-E

(S)Continues processing.(O)Redefine the environment definition.KAVT3543-WThe mail file directory name exceeds (specified-byte-length) bytes.The mail f

Seite 592 - KAVT3025-E

(S)Continues processing.(O)Redefine the environment definition.KAVT3547-WInformation about mail file (maintenance-information) could not be obtained:

Seite 593 - KAVT3030-E

KAVT3550-WThe output file from the mail filtering application could not be read: (maintenance-information, system-error-message)Reading an input file

Seite 594 - KAVT3036-E

KAVT3554-WThe inherited mail file (file-name) could not be written to: (maintenance-information, system-error-message)Writing an inheritance mail file

Seite 595 - KAVT3042-E

(O)Use maintenance information and system error message to determine the cause of the error that prevented mail frombeing written. Then take action. R

Seite 596 - KAVT3050-E

Acquiring the output file information in the mail filter applications was impossible.(S)Continues processing.(O)Use maintenance information and system

Seite 597 - KAVT3060-E

No arrival data is found for the mail.(S)Continues processing.(O)Stop JP1/AJS3 and then check the mail system.KAVT3566-WMail File could not be compres

Seite 598 - KAVT3067-E

KAVT3569-WThe mail reception list file (file-name) could not be written to: (maintenance-information, system-error-message)Writing a mail reception li

Seite 599 - KAVT3075-E

(O)Use maintenance information and system error message to determine the cause of the error that prevented mail frombeing written. Then take action.KA

Seite 600 - KAVT3079-E

Writing a save file for mismatched mail was impossible.(S)Cancels processing, waits for the monitoring interval and continues processing.(O)Use mainte

Seite 601 - KAVT3085-E

Message ID Output destinationsyslog EventlogHNTRLib2 stdout stderr ExecdetailsJP1eventKAVU3105 Y -- Y -- -- -- --KAVU3110 -KAVU3111Y Y Y -- -- -- --KA

Seite 602 - KAVT3200-I

The environment definition does not specify the monitoring intervals.(S)Assumes ten minutes.(O)Redefine the environment definition as required.KAVT358

Seite 603 - KAVT3204-E

A storage directory for inheritance information is not specified to the environment definitions.(S)Assumes an inheritance information directory in uni

Seite 604 - KAVT3210-W

(S)Continues processing.(O)Check whether:• The maintenance information provides a file.• The system resources are sufficient.• The permission environm

Seite 605 - KAVT3212-E

sendmail starts.(S)Continues processing.KAVT3702-IMail was sent normally.Mail was sent normally.(S)Terminates processing.KAVT3703-Itemporary file:(&qu

Seite 606 - KAVT3271-E

KAVT3706-EA temporary file could not be created. (file: "temporary-file-name")Creating a temporary file for sending mail was impossible.(S)C

Seite 607 - KAVT3276-E

KAVT3710-EThe mail-destination address is invalid: ("mail-destination-address")An invalid mail destination address is specified.(S)Cancels p

Seite 608 - KAVT3279-E

KAVT3715-EThe 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

Seite 609 - KAVT3281-E

KAVT3719-Esendmail returned an unexpected error. (error: return-code-of-sendmail-command)The sendmail command for sending mail returned an unexpected

Seite 610 - KAVT3285-E

KAVT3723-EMessage Put error. (reason)An attempt was made to output a message, but memory became insufficient.(S)Cancels processing.(O)Check that there

Seite 611 - KAVT3289-E

KAVT3804-EInvalid value for option (-option).An invalid option was specified.(S)Cancels processing.(O)Specify the correct option.KAVT3805-EOption (-op

Seite 612 - KAVT3293-E

Message ID Output destinationsyslog EventlogHNTRLib2 stdout stderr ExecdetailsJP1eventKAVU4718 -- --Y#3-- -- -- --KAVU4720 -- --Y#3-- -- -- --KAVU4721

Seite 613 - KAVT3296-E

KAVT3810-EI/O error occurred: maintenance-information maintenance-information maintenance-information system-error-messageAn I/O error occurred in inp

Seite 614 - KAVT3299-E

KAVT3821-IMail Send Command finished.The mail delivery command terminated.(S)Terminates processing.KAVT3822-IRetrying.The mail delivery command retrie

Seite 615 - KAVT3303-E

• Check whether the correct profile name is specified.• Check whether the execution user permissions are set correctly for the profile name.• Check th

Seite 616 - KAVT3404-I

KAVT3830-EThe SMTP server rejected the login. (SMTP-server-name:port, SMTP-AUTH-type)(maintenance-information)The destination SMTP server rejected the

Seite 617 - KAVT3409-E

(S)Changes the status of the email sending job to Ended abnormally.(O)Check the authentication method in the profile, the authentication account name,

Seite 618 - KAVT3452-I

• A timeout occurred during processing of the email sending job.(S)Cancels processing.(O)Check the following, and then re-execute the job:• Check whet

Seite 619 - KAVT3457-I

(S)Cancels processing.(O)Check the following, and then re-execute the command:• Check whether there is sufficient free space on the disk.• Check wheth

Seite 620 - KAVT3461-W

• 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, CO

Seite 621 - KAVT3466-E

KAVT3845-EAn unexpected error occurred. (maintenance-information) (maintenance-information)An unexpected error occurred in the email sending job.(S)Ca

Seite 622 - KAVT3469-E

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

Seite 623 - KAVT3502-I

#1Messages with a message type of Error (-E) can also be output to syslog according to the specifications of the SYSLOGJOBMSG environmentsetting param

Seite 624 - KAVT3514-E

KAVT3852-EThe attached file could not be defined. (maintenance-information)The attached file for the email could not be configured.(S)Cancels processi

Seite 625 - KAVT3520-E

(O)Check whether JP1/AJS3 is installed correctly.KAVT4039-EThe TP1 service does not exist.The TP1 service is missing.(S)Cancels processing.(O)Check wh

Seite 626 - KAVT3525-W

KAVT4069-EUnable to open message body file. (error-code-of-GetLastError)The message body file could not be opened.(S)Cancels processing.(O)Check wheth

Seite 627 - KAVT3531-W

(O)Use the error code of GetLastError and the system error message to determine the cause that prevented the filefrom being closed, and then take appr

Seite 628 - KAVT3538-W

(O)Check whether the MQSeries service is started.KAVT4123-EThe MQSeries service does not exist.The MQSeries service does not exist.(S)Cancels processi

Seite 629 - KAVT3542-W

KAVT4135-IThe processing of message sending will now end.Message sending terminates.(S)Continues processing.KAVT4136-EThe parameter is specified incor

Seite 630 - KAVT3546-W

Reading the configuration definition was impossible.(S)Cancels processing.(O)Check whether JP1/Base and JP1/AJS3 are installed correctly.KAVT4141-EYou

Seite 631 - KAVT3549-W

KAVT4144-EThe send process (process-name) could not be started. (return-value-of-GetLastError)Stating a send process was impossible.(S)Cancels process

Seite 632 - KAVT3553-W

If it is running, see the documentation for the linked message queue system and determine the cause of the errorfrom the MQSeries error code, and then

Seite 633 - KAVT3557-W

KAVT4160-EThe queue cannot be opened because the specified remote queue name is invalid. (MQSeries-error-code, error-location)Opening a queue was impo

Seite 634 - KAVT3561-W

1.3.8 Output destinations of messages beginning with KNACMessages whose message ID begins with KNAC are output by communication control or agent mana

Seite 635 - KAVT3565-W

Opening a queue was impossible because the transfer queue could not be recognized.(S)Cancels processing.(O)Check whether the queue is specified correc

Seite 636 - KAVT3568-W

(O)Check whether the queue is specified correctly or the queue is created correctly. If the queue is specified or createdcorrectly, see the documentat

Seite 637 - KAVT3572-W

KAVT4171-EMessages cannot be sent because the message length exceeds the maximum length for the queue. (MQSeries-error-code)Sending a message was impo

Seite 638 - KAVT3576-W

(S)Cancels processing.(O)Check the disk space.KAVT4175-EMessages could not be sent. (MQSeries-error-code)Sending a message was impossible.(S)Cancels p

Seite 639 - KAVT3585-W

(S)Continues processing.KAVT4179-IA message was sent to the queue.A message was sent to the queue.(S)Continues processing.KAVT4180-EThe status of the

Seite 640 - KAVT3593-W

KAVT4183-EThe communication pipe with SUP could not be created. (GetLastError-return-code, output-location)Creating a communication pipe with SUP was

Seite 641 - KAVT3597-E

KAVT4187-EMessages cannot be sent because memory became insufficient. (error-code)The system cannot send a message because a memory shortage occurred.

Seite 642 - KAVT3701-I

(O)Check whether the environment is set up to send and receive messages.KAVT4192-EThe queue cannot be opened because the specified remote queue name i

Seite 643 - KAVT3705-E

(O)Check whether memory is sufficient.For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in ReleaseNotes

Seite 644 - KAVT3709-W

(S)Cancels processing.(O)Check the disk space.KAVT4201-EMessages cannot be sent because the message length exceeds the maximum length of the queue. (e

Seite 645 - KAVT3714-E

stdout: Standard outputstderr: Standard error outputExec details: Execution Result Details dialog boxJP1 event: JP1 eventY: Is output.--: Is not outpu

Seite 646 - KAVT3718-I

(S)Cancels processing.(O)Check whether the correct queue is specified.KAVT4205-EThe queue cannot be opened because the transfer queue cannot be recogn

Seite 647 - KAVT3722-E

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 co

Seite 648 - KAVT3803-E

(S)Cancels processing.(O)Start the queue manager.KAVT4213-EThe queue could not be re-opened because it was deleted. (error-code)The attempt to reopen

Seite 649 - KAVT3807-W

(S)Cancels processing.(O)Check whether the file can be written.KAVT4222-EThe queue could not be opened.Opening a queue was impossible.(S)Places the jo

Seite 650 - KAVT3820-I

(O)Check whether memory is sufficient.For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in ReleaseNotes

Seite 651 - KAVT3825-E

(S)Cancels processing.(O)Check whether the correct queue is specified.KAVT4238-EThe queue cannot be opened because the transfer queue cannot be recogn

Seite 652 - KAVT3829-E

(S)Cancels processing.(O)Check whether the correct queue is specified.KAVT4242-EThe queue cannot be opened because the default transfer queue is being

Seite 653 - KAVT3833-E

(S)Cancels processing.(O)Start the queue management program.KAVT4246-EMessages cannot be received because memory became insufficient.Receiving a messa

Seite 654 - KAVT3836-E

KAVT4249-EThe queue could not be disconnected.Disconnecting a queue was impossible.(S)Cancels processing.(O)Check whether the environment is set up to

Seite 655 - KAVT3838-E

KAVT4253-EThe queue manager program stopped.The queue management program stopped.(S)Cancels processing.(O)Start the queue management program.KAVT4254-

Seite 656 - KAVT3841-E

stderr: Standard error outputJP1 event: JP1 eventY: Is output.--: Is not output.Table 1‒15: The output destinations of system management messagesMess

Seite 657 - KAVT3844-E

KAVT4257-EThe 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

Seite 658 - KAVT3848-E

A request to restart the SUP was accepted.(S)Continues processing.KAVT4401-IJP1/AJS2 message queue monitoring process (TP1/Message Queue) will now sta

Seite 659 - KAVT3851-E

(S)Continues processing.KAVT4406-IThe JP1/AJS2 message queue monitoring process (TP1/Message Queue) stopped.The JP1/AJS2 message queue monitoring proc

Seite 660 - KAVT4037-E

(S)Continues processing.KAVT4411-IThe JP1/AJS2 SUP control process will now stop.The JP1/AJS2 SUP control process stops.(S)Continues processing.KAVT44

Seite 661 - KAVT4068-E

The message queuing function to be linked has started.(S)Continues processing.KAVT4418-WThe message queue function to be linked is stopped. (maintenan

Seite 662 - KAVT4072-E

(S)Continues processing.KAVT4453-IThe message queue linkage communication process stopped.The message queue linkage communication process has stopped.

Seite 663 - KAVT4122-E

Monitoring of message queue linkage terminates because the time-out period has elapsed.(S)Terminates processing.KAVT4458-IMessage Queue System to use

Seite 664 - KAVT4134-I

(O)Check whether the macro variable is correct.KAVT4462-WA macro variable exceeds 4096 bytes. Some macro variables could not be created.A macro variab

Seite 665 - KAVT4140-E

KAVT4467-EMemory became insufficient.A memory shortage occurred.(S)Cancels processing.(O)Check whether memory is sufficient.For details on the amount

Seite 666 - KAVT4143-E

KAVT4471-WThe JP1/AJS2 message queue monitoring process is not running.The JP1/AJS2 message queue monitoring process is not running. The system waits

Seite 667 - KAVT4152-E

Summary of amendmentsThe 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-3

Seite 668 - KAVT4159-I

Message ID Output destinationDialog syslog EventlogHNTRLib2 stdout stderr JP1eventKNAD3649 -- Y Y Y Y -- --KNAD3650 -KNAD3662-- -- -- Y Y -- --KNAD366

Seite 669 - KAVT4163-E

A message was received.(S)Continues processing.KAVT4502-EThe message queue will not be linked.The message queue linkage is not performed.(S)Suspends t

Seite 670 - KAVT4166-E

KAVT4506-IThe message queue monitoring process will now be suspended.The message queue monitoring process is suspended.(S)Terminates processing.KAVT45

Seite 671 - KAVT4170-E

KAVT4517-EAn internal table could not be created because of insufficient memory: maintenance-informationCreating an internal table was impossible beca

Seite 672 - KAVT4174-E

KAVT4524-EThe temporary file for storing messages (temporary-file-name) could not be written to: (maintenance-information, system-error-message)Writin

Seite 673 - KAVT4178-I

(O)Contact the system administrator.KAVT4528-EAn error occurred in the processing of synchronous multi-I/O: (maintenance-information, system-error-mes

Seite 674 - KAVT4182-E

(O)Use the system error message to determine the cause of the error, and then take action. Restart JP1/AJS3 as required.KAVT4532-EThe pipe could not b

Seite 675 - KAVT4186-E

(O)Check the cause of the error from the system error message. Then take action.KAVT4536-EThere is no reply to the pipe contact: maintenance-informati

Seite 676 - KAVT4190-E

(O)Use the system error message to determine the cause of the error, and then take action. Restart JP1/AJS3 as required.KAVT4540-WThe transaction proc

Seite 677 - KAVT4196-E

(S)Suspends the message queue monitoring process.(O)Investigate the cause of the error from the error message when issuing the startup command. Then t

Seite 678 - KAVT4200-E

(O)Specify only once the option that was specified more than once, and then re-execute the transmission of the messagequeue.KAVT4551-ENo value is spec

Seite 679 - KAVT4204-E

Message ID Output destinationDialog syslog EventlogHNTRLib2 stdout stderr JP1eventKNAD3873 -- -- -- -- Y -- --KNAD3874 -KNAD3875-- Y Y -- Y -- --KNAD3

Seite 680 - KAVT4208-E

(O)Check the cause of the error from the system error message. Then take action.KAVT4555-EThe file(file-name) could not be closed: (maintenance-inform

Seite 681 - KAVT4212-E

(S)Continues processing.KAVT4559-WThe specified dynamic queue (queue-name) already exists. The existing queue will be opened.The existing queue is ope

Seite 682 - KAVT4216-E

The system resources that are usable are insufficient.(S)Cancels processing. If an undeliverable queue (a dead letter queue) is specified, sends the m

Seite 683 - KAVT4230-E

(O)Check the return value for the MQI call of MQSeries or TP1/Message Queue and take action to make the connection.KAVT4566-EObject(queue-name) in the

Seite 684 - KAVT4237-E

(S)Cancels processing. If an undeliverable queue (a dead letter queue) is specified, sends the message to theundeliverable queue (the dead letter queu

Seite 685 - KAVT4241-E

KAVT4573-EThe 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-in

Seite 686 - KAVT4245-E

KAVT4576-EAn error occurred during sending of the message to the dead-letter queue (queue-name): processing-name reason-code-from-MQI-call-(when-proce

Seite 687 - KAVT4248-E

KAVT4582-EThe process could not be started: (maintenance-information, system-error-message)Starting a process was impossible.(S)Suspends the message q

Seite 688 - KAVT4252-E

KAVT4586-EThe pipe could not be closed: pipe-name (maintenance-information, system-error-message)Closing a pipe was impossible.(S)Continues processing

Seite 689 - KAVT4256-E

KAVT4590-EAfter the process started, waiting for the replay failed: (maintenance-information, system-error-message)Waiting for a response was impossib

Seite 690 - KAVT4261-I

1.4 List of Windows event logs and syslogs1.4.1 List of messages output to the Windows event log and syslogThis section lists the Windows event logs

Seite 691 - KAVT4405-I

KAVT4596-EThe transaction process failed, but SUP continues: SUP-function-name-with-error return-value-of-SUP-function-with-errorProcessing a transact

Seite 692 - KAVT4410-I

KAVT4632-EThere is not configuration definitions right to access to information. (return-code)The privilege of the user is invalid to access the confi

Seite 693 - KAVT4417-I

• Check whether the privilege of the user is valid.• Check whether the directory created at JP1/AJS3 installation was unintentionally deleted.KAVT4664

Seite 694 - KAVT4452-I

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

Seite 695 - KAVT4457-I

KAVT4685-WDefinitions parameter (parameter) is not specified.The required parameter is missing.(S)Terminates the job.(O)Check whether the job is defin

Seite 696 - KAVT4461-W

KAVT4690-IStop request was accepted.A stop request was accepted.(S)Requests to terminate the message queue monitoring.KAVT4691-IEnded normally.: proce

Seite 697 - KAVT4466-E

KAVT4695-ESending of the message queue is unusable.Unable to send a message queue.(S)Cancels the transmission of the message queue.(O)Check whether th

Seite 698 - KAVT4470-E

(S)Continues processing.KAVT4700-EThe processing of the message queue monitor process did not finish.: retry-countThe message queue monitoring did not

Seite 699 - KAVT4501-I

(S)Cancels command processing.(O)Specify an option, and then re-execute the command.KAVT4953-EAn invalid option is specified.An invalid option is spec

Seite 700 - KAVT4505-I

KAVT4957-ESUP could not be restarted.Restarting SUP was impossible.(S)Cancels command processing.(O)Check the cause of the error from the error messag

Seite 701 - KAVT4513-E

Message ID Windows (Application log) UNIX (syslog)Event ID Type Facility LevelKAVC2901-E12901Error LOG_DAEMON, LOG_USERLOG_ERRKAVC2902-E12902Error LOG

Seite 702 - KAVT4523-E

Closing a pipe was impossible.(S)Continues processing.(O)Check the cause of the error from the system error message. Then take action.KAVT4962-EFor ex

Seite 703 - KAVT4527-E

(O)Specify necessary items.KAVT5254-EThe parameter is specified incorrectly. (data-specified-in-environment-variable)The specified parameter is invali

Seite 704 - KAVT4531-E

(O)Start the MSMQ service.KAVT5265-EThe MSMQ service does not exist. (service-status-code)The MSMQ service does not exist.(S)Cancels processing.(O)Ins

Seite 705 - KAVT4535-E

(O)Check whether the MSMQ server is connected to MSMQ of the JP1/AJS3 - Agent machine.KAVT5269-EMessage sending will now stop because an error that st

Seite 706 - KAVT4539-E

(O)Check the queue access permission.KAVT5275-EThe queue could not be closed. (return-value-of-MQ-function)Closing a queue was impossible.(S)Continues

Seite 707 - KAVT4543-E

(O)Check whether the queue label name is correct.KAVT5279-EAn error occurred during an MSMQ access. (MQLocateNext) (return-value-of-MQ-function)An err

Seite 708 - KAVT4550-E

(O)Check whether the MSMQ service is running normally.KAVT5287-EMessage Reception Monitoring Interval is assumed because registry information was not

Seite 709 - KAVT4554-E

(O)Check whether memory is sufficient.For details on the amount of memory required by JP1/AJS3, see Memory and Disk Space Requirements in ReleaseNotes

Seite 710 - KAVT4558-I

(S)Cancels processing.(O)Check the variable, and then retry.KAVT5308-EThe registry information could not be acquired. (ErrCode=ErrorCode-number, GetLa

Seite 711 - KAVT4562-E

KAVT5312-EMessages cannot be received because an error that stops processing occurred. (ErrCode=ErrorCode-number,GetLastErrorCode=GetLastError-number)

Seite 712 - KAVT4565-E

Message ID Windows (Application log) UNIX (syslog)Event ID Type Facility LevelKAVS0230-E30230ErrorLOG_DAEMON LOG_ERRKAVS0231-W30231WarningLOG_DAEMON L

Seite 713 - KAVT4569-E

KAVT5338-EMessage reception will now end because an error that stops processing occurred. (ErrCode=ErrorCode-number,GetLastErrorCode=GetLastError-numb

Seite 714 - KAVT4572-E

KAVT5343-EThe entered code is invalid. (ASCII) (ErrCode=ErrorCode-number, GetLastErrorCode=GetLastError-number)The input code is invalid. (ASCII)(S)Ca

Seite 715 - KAVT4575-E

KAVT5352-ETerminating because the pipe connection thread did not end. (ErrCode=ErrorCode-number,GetLastErrorCode=GetLastError-number)Some internal thr

Seite 716 - KAVT4581-E

KAVT5364-EThere is no message: Maintenance-informationNo message exists.(S)Continues monitoring.(O)Check whether the monitoring conditions are correct

Seite 717 - KAVT4585-E

KAVT5372-EMessages could not be received because the queue could not be opened. (ErrCode=ErrorCode-number,GetLastErrorCode=GetLastError-number)The sys

Seite 718 - KAVT4589-E

(O)Check the queue status.KAVT5377-EThe queue was deleted. (ErrCode=ErrorCode-number, GetLastErrorCode=GetLastError-number)A queue was deleted.(S)Clos

Seite 719 - KAVT4595-E

(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 Requir

Seite 720 - KAVT4631-E

KAVT5384-EAn error occurred during an MSMQ access. (MQCreateCursor). (ErrCode=ErrorCode-number,GetLastErrorCode=GetLastError-number)An error occurred

Seite 721 - KAVT4663-E

KAVT5453-IThe MSMQ linkage communication process stopped.The MSMQ linkage communication stopped.(S)Terminates processing.KAVT5454-IThe MSMQ reception

Seite 722 - KAVT4681-W

KAVT5461-WAn error occurred during creation of a macro variable.An error occurred during creation of a macro variable.(S)Continues processing.(O)Check

Seite 723 - KAVT4684-E

Message ID Windows (Application log) UNIX (syslog)Event ID Type Facility LevelKAVS0314-E30314ErrorLOG_DAEMON LOG_ERRKAVS0315-E30315Error LOG_DAEMON, L

Seite 724 - KAVT4689-I

The job for the MSMQ reception monitoring is defined incorrectly.(S)Cancels processing.(O)Check the definition of the job.KAVT5467-EMemory became insu

Seite 725 - KAVT4694-I

(O)Check the definitions to see if an event ID is specified. When an event ID is specified, contact the systemadministrator.KAVT6004-EAn error occurre

Seite 726 - KAVT4699-I

(S)Cancels processing.(O)Check whether JP1 events can be sent in the current environment. Check also whether a problem has occurred inthe JP1/Base eve

Seite 727 - KAVT4952-E

(S)Cancels processing.(O)Check whether the network settings are correct and whether the host name is specified correctly. If you cannot solvethe probl

Seite 728 - KAVT4956-I

KAVT7005-WThe time-out period elapsed.A timeout occurred. The system cancels executing the job.(S)Cancels processing.KAVT7006-WA kill request was acce

Seite 729 - KAVT4961-E

KAVT7009-EMemory became insufficient. (maintenance-information)Memory became insufficient. The job terminates.(S)Terminates the job abnormally due to

Seite 730 - KAVT5253-E

(S)An error occurred during inter-process communication with the agent. The system terminates the execution intervalcontrol process depending on the l

Seite 731 - KAVT5264-E

(S)Sufficient resources for performing the next monitoring are not available. The system abnormally terminates theInterval Control job.(O)Check the fo

Seite 732 - KAVT5268-E

KAVT7502-EInvalid environment variable specification. (specified-environment-variable)An incorrect parameter is specified in the hp OpenView Status Re

Seite 733 - KAVT5274-E

(S)Cancels processing.(O)Install the SNMP service.KAVT7509-ECould not report status. SNMP service is not started.The job failed to report the status b

Seite 734 - KAVT5278-E

Message ID Windows (Application log) UNIX (syslog)Event ID Type Facility LevelKAVS0930-E30930ErrorLOG_USER LOG_ERRKAVS0932-E30932Error LOG_DAEMON, LOG

Seite 735 - KAVT5286-E

(S)Cancels processing.(O)If the code indicated in code-for-status-report-error is 10, check whether the hp OpenView Status Report job wasexecuted by a

Seite 736 - KAVT5293-E

(S)Starts processing.KAVT8002-IThe common environment definition command will now end.The common environment definition command terminates.(S)Terminat

Seite 737 - KAVT5307-E

KAVT8007-EThe configuration definition could not be read. (error-code)The system failed to write the configuration information.(S)Cancels processing.(

Seite 738 - KAVT5311-E

You are not authorized to access the configuration definition.(S)Cancels processing.(O)Check whether the environment is set up to access the configura

Seite 739 - KAVT5332-E

(S)Terminates the command.KAVT8016-IThe MSMQ environment setting command will now start.The command to set the environment of MSMQ starts.(S)Continues

Seite 740 - KAVT5342-E

(S)Cancels processing.(O)Check whether the data can be used in the current platform, and then retry.KAVT8021-EEnvironment setup did not end normally.T

Seite 741 - KAVT5346-E

KAVT8025-EThe data length is invalid. (error-code)The data length is incorrect.(S)Cancels processing.(O)Check whether the data length is within the sp

Seite 742 - KAVT5359-E

KAVT8301-IThe command terminated normally.Listing terminated normally.(S)Terminates command execution.KAVT8302-WThe command terminated abnormally.The

Seite 743 - KAVT5371-E

KAVT8305-EInvalid value for option (option)The option contains an invalid value.(S)Cancels command execution.(O)Correct the value for the option, and

Seite 744 - KAVT5376-E

KAVT8310-WBecause the data was long, the data was truncated and then displayed. (data-truncated (up-to-900-bytes)) (name-of-the-item-displayed)The dat

Seite 745 - KAVT5380-E

Message ID Windows (Application log) UNIX (syslog)Event ID Type Facility LevelKAVS1002-E31002ErrorLOG_DAEMON LOG_ERRKAVS1003-E31003ErrorLOG_DAEMON LOG

Seite 746 - KAVT5383-E

(S)Continues command execution. The system cannot display the name of the appropriate job and its jobnet name.(O)Check the following:• Check whether s

Seite 747 - KAVT5452-I

KAVT8316-EAn error occurred during the access of the agent information file. (error-code) (function-name) (maintenance-information)An error occurred w

Seite 748 - KAVT5457-I

KAVT8320-EThe host name could not be obtained. (error-code) (function-name) (maintenance-information)The host name could not be obtained.(S)Cancels co

Seite 749 - KAVT5466-E

• Check whether the environment of JP1/AJS3 and JP1/Base have been set correctly.KAVT8323-EThe registration file could not be read. (path-name) (funct

Seite 750 - KAVT6003-E

KAVT8327-WThere is no data so data cannot be displayed. (name-of-the-item-displayed) (maintenance-information)There is no data of the requested value.

Seite 751 - KAVT6100-E

• jpomanjobshow(S)Cancels command execution.(O)Check the following, and then re-execute the command:• Check whether system resources are sufficient.•

Seite 752 - KAVT6104-E

KAVT8333-EThe agent is not running.The agent has not been started.(S)Cancels command execution.(O)Check whether the agent has been started. Restart JP

Seite 753 - KAVT7004-I

(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 determin

Seite 754 - KAVT7008-W

KAVT8340-EThe main loop of the jpoagtjobshow command failed. (maintenance-information)The main loop of the jpoagtjobshow command could not be started.

Seite 755 - KAVT7012-E

• If you did not specify the -s option, information may still remain on the agent. Perform a cold start manuallyfor JP1/AJS3 on the agent.jpomanevshow

Seite 756 - KAVT7015-E

Message ID Windows (Application log) UNIX (syslog)Event ID Type Facility LevelKAVS1805-E31805ErrorLOG_DAEMON LOG_ERRKAVS1806-I31806InformationLOG_DAEM

Seite 757 - KAVT7501-E

KAVT8351-ESpecified Scheduler service not exist (scheduler-service-name)(maintenance-information).The scheduler service specified for the -F operand o

Seite 758 - KAVT7508-E

KAVT8402-EThe reading of requests from the jpoagtjobshow command failed. (return-code)Requests could not be read from the pipes for the jpoagtjobshow

Seite 759 - KAVT7512-E

KAVT8405-EThe reporting of information to the jpoagtjobshow command failed. (return-code)Pipes could not be written into the jpoagtjobshow command.(S)

Seite 760 - KAVT8001-I

KAVT8410-EAn attempt to obtain the environmental setting parameter information failed.(return-code)(line-number)An attempt to obtain environment setti

Seite 761 - KAVT8005-E

(S)Cancels command execution.(O)Check the following, and then re-execute the command:• Check whether the directory created by JP1/AJS3 during installa

Seite 762 - KAVT8011-E

2. Cold start the JP1/AJS3 service.For details on the jpomanevreset command, see jpomanevreset in 2. Commands in the manual Job ManagementPartner 1/Au

Seite 763 - KAVT8015-I

AppendixesJob Management Partner 1/Automatic Job Management System 3 Messages 1786

Seite 764 - KAVT8020-E

A. Version RevisionsThis appendix lists the changes in each version of the JP1/AJS series programs.A.1 Revisions in 10-00The following lists the rev

Seite 765 - KAVT8024-I

• The embedded database settings file is now generated when an embedded database is set up. If this file is specifiedwhen the ajsembdbbuild command is

Seite 766 - KAVT8107-E

(3) JP1/AJS3 - View• The Wait Conditions Settings List window and the Wait Conditions Statuses window have been added as means formanaging units with

Seite 767 - KAVT8304-E

Message ID Windows (Application log) UNIX (syslog)Event ID Type Facility LevelKAVS1839-E31839ErrorLOG_DAEMON LOG_ERRKAVS1840-E31840ErrorLOG_DAEMON LOG

Seite 768 - KAVT8308-E

• Because of the user authentication function added in JP1/AJS3 - Definition Assistant 09-10, specifying the JP1 username is now mandatory for startin

Seite 769 - KAVT8313-W

• NotificationRetryInterval• NotificationRetryCount• ClientConnectTimeout• A function has been added to support end delay monitoring based on how long

Seite 770 - KAVT8315-W

• A jobnet release function has been added for replacing the definition of a jobnet that is registered for execution withanother definition.• Function

Seite 771 - KAVT8319-E

A.3 Revisions in 08-00The following lists the revisions in 08-00 for each program.(1) JP1/AJS2 - Manager• The recommended values for the environment

Seite 772 - KAVT8322-E

• Judgment jobs can now perform variable judgment.• A function has been added that suppresses jobnet executions that follow an abnormally terminated j

Seite 773 - KAVT8325-W

• All the detailed processes of the event action function can now be stopped to terminate the agent process for theevent action function if any of the

Seite 774 - KAVT8330-E

• 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 de

Seite 775 - KAVT8332-E

B. Reference Material for This ManualThis appendix provides reference information, including various conventions, for this manual.B.1 Related public

Seite 776 - KAVT8336-E

• Job Management Partner 1 Version 10 Job Management Partner 1/Automatic Job Management System 3 - PrintOption Description, User's Guide (3021-3-

Seite 777 - KAVT8339-W

• Job Management Partner 1/Software Distribution Administrator Kit Description and Operator's Guide (3020-3-S84(E))• Job Management Partner 1/Sof

Seite 778 - KAVT8342-E

Changes LocationA function was added for checking the execution schedule of unregisteredunits in the Monthly Schedule window of JP1/AJS3 - View.System

Seite 779 - KAVT8347-E

Message ID Windows (Application log) UNIX (syslog)Event ID Type Facility LevelKAVS1877-E31877ErrorLOG_DAEMON LOG_ERRKAVS1878-E31878ErrorLOG_DAEMON LOG

Seite 780 - KAVT8401-E

Abbreviation Full name or meaningJP1/AJS3 - Web Operation Assistant Job Management Partner 1/Automatic JobManagement System 3 - Web Operation Assistan

Seite 781 - KAVT8404-E

• UNIX is sometimes used generically, referring to HP-UX, Solaris, AIX and Linux.B.3 Conventions: AcronymsThis manual also uses the following acronym

Seite 782 - KAVT8408-E

B.4 Conventions: KB, MB, GB, and TBThis manual uses the following conventions:• 1 KB (kilobyte) is 1,024 bytes.• 1 MB (megabyte) is 1,0242 bytes.• 1

Seite 783 - KAVT8413-E

B.9 Online manualJP1/AJS3 - View comes with an online manual that you can read in browsers.The HTML manual contains the same content as the Job Manag

Seite 784 - KAVT8416-W

C. Glossaryabnormal endA jobnet ends abnormally if one of the processes defined in the jobnet fails to execute properly. The jobnetis interrupted at

Seite 785 - KAVT8417-W

backup fileA file containing the units defined in JP1/AJS3.base dayA date specified as the starting day of the month in the calendar information.base

Seite 786 - Appendixes

custom jobA predefined job for executing a task with a specific purpose. JP1/AJS3 provides standard custom jobssuch as file transfer and job requests

Seite 787 - (1) JP1/AJS3 - Manager

embedded database system administratorThe owner of an embedded database practical directory and embedded database file system areas (dataarea and syst

Seite 788 - (2) JP1/AJS3 - Agent

execution IDA number assigned to an execution schedule of the uppermost jobnet.execution-locked resourceA means of preventing multiple jobs from execu

Seite 789 - (3) JP1/AJS3 - View

jobnetA set of jobs associated in execution order. When a jobnet is executed, the jobs in the jobnet areautomatically executed in their predetermined

Seite 790 - A.2 Revisions in 09-00

Message ID Windows (Application log) UNIX (syslog)Event ID Type Facility LevelKAVS1923-E31923ErrorLOG_DAEMON LOG_ERRKAVS1924-E31924ErrorLOG_DAEMON LOG

Seite 791

JP1/AJS3 Console ManagerA JP1/AJS3 component that stores definitions about monitored objects defined in JP1/AJS3 Console View,and gets status informat

Seite 792

JP1/ScriptA program for creating and executing scripts (batch files) that control jobs on Windows. Job operation canbe automated by linking JP1/Script

Seite 793

mail receipt parameter fileA file containing the mail receipt monitoring parameters defined by the user. The file extension is .prm.This file is creat

Seite 794 - (2) JP1/AJS2 - Agent

node switching systemSee cluster system.normal endA normal end of a jobnet occurs when all the processes defined in the jobnet have executed correctly

Seite 795 - (1) About JP1/AJS2 - Manager

The queue controls the number of jobs that the agent executes concurrently, thereby preventing anydegradation in performance caused by a large number

Seite 796 - (3) About JP1/AJS2 - View

scheduler serviceA service that manages the schedules for jobnet execution, and executes processes according to thoseschedules. Each scheduler service

Seite 797 - B.1 Related publications

succeeding jobnetA jobnet executed immediately after another job or jobnet.suspendTo suppress the execution of the root jobnet and lower units.When yo

Seite 798

Windows MessagingA facility that provides an interface for sending and receiving email. Using Windows Messaging, you canmanage, access, and share a va

Seite 799

IndexAabbreviations for products 799abnormal end 804abnormal threshold 804About the 3rd level and 4th level Kanji charactersadded in JIS 2004 (JIS X 0

Seite 800 - # Version 7

Iimmediate execution registration 808installation foldersdefault for JP1/AJS3 for Windows 802ISAMcompatible ISAM configuration, glossary definition805

Seite 801 - B.3 Conventions: Acronyms

Message ID Windows (Application log) UNIX (syslog)Event ID Type Facility LevelKAVS1981-I31981InformationLOG_DAEMON LOG_INFOKAVS1982-I31982InformationL

Seite 802

Oonline manualcontents 803open day 813Ppassing information 813passing information name 813physical host 813planned execution registration 813planning

Seite 803 - B.12 About NNM linkage

Message ID Windows (Application log) UNIX (syslog)Event ID Type Facility LevelKAVS4701-E34701ErrorLOG_DAEMON LOG_ERRKAVS4702-E34702ErrorLOG_DAEMON LOG

Seite 804 - C. Glossary

Message ID Windows (Application log) UNIX (syslog)Event ID Type Facility LevelKAVS4907-I34907InformationLOG_DAEMON LOG_INFOKAVS4908-E34908ErrorLOG_DAE

Seite 805

Message ID Windows (Application log) UNIX (syslog)Event ID Type Facility LevelKAVT1037-E11037ErrorLOG_DAEMON LOG_ERRKAVT1040-E11040ErrorLOG_DAEMON LOG

Seite 806

Message ID Windows (Application log) UNIX (syslog)Event ID Type Facility LevelKAVU0241-E20241Error LOG_DAEMON, LOG_USERLOG_ERRKAVU0242-E20242Error LOG

Seite 807

Message ID Windows (Application log) UNIX (syslog)Event ID Type Facility LevelKAVU5980-I25980InformationLOG_USER LOG_NOTICEKAVU5981-I25981InformationL

Seite 808

Message ID Windows (Application log) UNIX (syslog)Event ID Type Facility LevelKNAD3613-W2WarningLOG_USER LOG_WARNINGKNAD3614-E1ErrorLOG_USER LOG_ERRKN

Seite 809

Message ID Windows (Application log) UNIX (syslog)Event ID Type Facility LevelKNAD3992-E1ErrorLOG_USER LOG_ERRKNAD3993-E1ErrorLOG_USER LOG_ERRLegend:-

Seite 810

Changes LocationA function was added for preventing scheduler services for which the JP1user logged in to JP1/AJS3 - View has no access privileges fro

Seite 811

2MessagesThis chapter explains the messages output by JP1/AJS3 and how to take actions for them.Job Management Partner 1/Automatic Job Management Syst

Seite 812

2.1 Messages beginning with KAJS (Messages about passing informationsetting jobs)This section lists the messages that begin with KAJS (messages about

Seite 813

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 fo

Seite 814

(S)Cancels command execution.(O)Make sure that no lines exceed 1,024 bytes in the execution results of the preceding job.KAJS7626-WA null string was s

Seite 815

(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 fre

Seite 816

2.2 Messages beginning with KAVC (Messages about JP1/AJS3 Console)This section lists the messages that begin with KAVC (Messages about JP1/AJS3 Conso

Seite 817 - Windows Messaging

KAVC0082-IJP1/AJS2 Console Manager service has been removed.The JP1/AJS3 Console Manager service has been removed.(S)Removed the JP1/AJS3 Console Mana

Seite 818

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

Seite 819

KAVC0102-EExtra argument(s) exist.One or more unnecessary arguments were specified.(S)Cancels command execution.(O)Delete the unnecessary arguments, a

Seite 820

If the UAC function is enabled in Windows, the administrator must re-execute the command.In environments managed by AJS administrators, an AJS adminis

Autostart AS-4565-SH Spezifikationen

Stöbern Sie online oder laden Sie Spezifikationen nach Fernbedingungen Autostart AS-4565-SH herunter. Autostart AS-4565-SH Specifications Benutzerhandbuch

Inhaltsverzeichnis

Weitere Dokumente für Fernbedingungen Autostart AS-4565-SH

Kommentare zu diesen Handbüchern

Autostart AS-4565-SH Spezifikationen

Stöbern Sie online oder laden Sie Spezifikationen nach Fernbedingungen Autostart AS-4565-SH herunter. Autostart AS-4565-SH Specifications Benutzerhandbuch

Inhaltsverzeichnis

Weitere Dokumente für Fernbedingungen Autostart AS-4565-SH

Kommentare zu diesen Handbüchern

Verwandte Produkte und Handbücher für Fernbedingungen Autostart AS-4565-SH