Error code

Description

-1

Error while submitting the job. SBMJOB made by the EASYCOMD job failed. Additional error text coming from iSeries will is provided with this error.

The EASYCOMD job history should contain all information on that failure.

-2

Security not valid. This error can occur if wrong user, password, password disabled, etc. The detailed reason is specified as text.

-4

submitted job did not answer, or failed to initialize data queues

The most common reason for this is that the job failed to run. It was submitted, but ended before beginning to communicate with the client. This is usually caused by wrong user’s jobd.

The full reason can be found in the QZEJOBLOG OUTQ of the system. To see it, do the following commands:

o    WRKOUTQ OUTQ(QEZJOBLOG)

o    Type F18 (to go at the end), and then F11.

o    There should be a line with the station name, with the corresponding user, date and time.

o    Type 5 on it to see the errors.

-5

Password is expired. If the client program ‘catches’ this error, it can perform a custom password change dialog box, and send the password with the new connection request. The password send by the application will have the following form in this case: oldpassword@newpassword

-6

Internal reject 1. Unexpected error, caused by a bug in EASYCOMD. Please contact help support. Restarting EASYCOM subsystem is recommended.

-7

Failed to init the library list. Errors occurred when installing the libraries that are defined in the user’s jobd. You can consult the QEZJOBLOG outq for more information (see error -4)

-8

SSO error. SSO profile is expired (re-signoon required), or not supported by EASYCOMD.

-9

The server cannot accept Kerberos tickets. EIM SSO is not configured, or the EASYCOMD LDAP connection failed. Do DSPMSG EASYCOM/EACMSGQ to see if there are Kerberos-related messages. Check that you see ‘Eim=

-10

Timeout on read. Communication error: the read request timed out. The connection was probably broken.

-11

Logon cancelled. This error occurs when message boxes are enabled and when the user clicks on ‘cancel’.

-12

Connection broken. The connection was broken by peer.

-13

Kerberos negotiation protocol failure. There was an unexpected Kerberos error when connecting. Check EIM configuration, and check if the same user is working using IBM Client Access in EIM mode.

-14

Kerberos error on client. The client failed to generate a ticket to send to the server. Additional text should explain the reason.

-15

Kerberos error on server. The server did not recognize the ticket or failed to grant it.

-16

OS/400 incompatible version. The OS/400 version is not compatible with the current request.

-17

Unexpected error while submitting (state unknown). Unexpected error probably caused by a bug. Please contact help support.

-18

Kerberos authentication out of hours. See CFGEACSSO to setup the valid hours for Kerberos authentication.

-19

Out of hours by exit program. The EACLOG001 exit program returned that the login is not valid at this time.

-20

Denied by exit program. The EACLOG001 exit program return that the login is denied

-21

Not processed by exit program. The EACLOG001 exit program returned that the login is invalid.

-22

Kerberos authentication is not supported by the server. See that CFGEACSSO enabled *EIM mode and that EASYCOMD started properly (DSPMSG EASYCOM/EACMSGQ).

-23

Kerberos authentication is mandatory. The Easycom server was configured to accept only Kerberos authentication, but a regular login was attempted.

-24

Failed to use the target library. The library specified by the target program property (Program= in easycom.ini, in section [general]) was not usable, because nonexistent or other reason.

-25

Awake on private job failed. The application attempted awaking a job that was registered by the setting, but it fails. A new connection is required. Note: this error currently can appear only with Easycom For PHP.

-26

SSL required on this server. The SSL negotiation was not setup or failed, but is required on the server. This can be marked as required using the EACTCPP01 exit program or using CFGEAC command.

-27

SSL server error. The SSL negotiation failed because the server detected an error. There are probably some information in the EACMSGQ message queue (type DSPMSG EASYCOM/EACMSGQ on a terminal)

-28

SSL negotiation was made, but a failure is detected while passing the connection to the Easycom job.

-29

SSL client error. The SSL negotiation failed because of an error on the client. More additional information is provided in the error message text.

-30

SSL sequence error. The SSL negotiation sequence was detected as invalid

-31

SSL protocol error. An SSL error is detected during SSL handshake.

-32

SSL error: SSL not supported on the platform

-33

EIM was mandatory for login

-34

SSL authentication is mandatory

-35

SSL authentication error (bad certificate, expired, …)

-36

EIM error

-37

No valid authentication provided. This means that all kind of accepted authentication methods failed.

Windows error code

AS/400 error code

Description

10061

ECONNREFUSED 3425

Connection refused.
No connection could be made because the target machine actively refused it. This usually results from trying to connect to a service that is inactive on the foreign host - i.e. one with no server application running.

10060

ETIMEDOUT 3447

Connection timed out.
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

11001

HOST_NOT_FOUND 5

(host error category)

Host not found.
No such host is known. The name is not an official hostname or alias, or it cannot be found in the database(s) being queried. This error may also be returned for protocol and service queries, and means the specified name could not be found in the relevant database.

10053

ECONNABORTED 3424

Connection aborted.
An established connection was aborted by the software in your host machine, possibly due to a data transmission timeout or protocol error.

10064

EHOSTDOWN 3428

Host is down.
A socket operation failed because the destination host was down. A socket operation encountered a dead host. Networking activity on the local host has not been initiated. These conditions are more likely to be indicated by the error WSAETIMEDOUT.

10050

ENETDOWN 3433

Network is down.
A socket operation encountered a dead network. This could indicate a serious failure of the network system (i.e. the protocol stack that the WinSock DLL runs over), the network interface, or the local network itself.